Embedded Files
Home > Automatic Transaction Submission (ATS) > Job Aids > Uploading an ATS Spreadsheet
Process:
The following covers how to upload an ATS template in FUD (this page takes the place of ADS in 3.9), as well as three possible outcomes and how to check for results. These scenarios are:
Scenario #1: A successful upload (contains all instructions to upload a template with pictures)
Navigate to FUD: This can be done in the jump to field at the top of the screen or by selecting the Upload Transaction Spreadsheet quick link at the top of the home page
Highlight the FIN ATS UPLOADS option on the left.
For most people, this should be the only option on this page
Once highlighted, select the upload icon on the left hand side of the page
Once the new window appears, you can either drag and drop your template or use browse to search your folders and upload it.
Once the name of your template shows up, select the Upload button in the lower/right hand side of the window.
Once the green bar is full, you’ll get a message that the upload is done and you can close the window.
When you return to the previous page, you’ll see two files in this folder. Your template and a CamelLock folder. These are part of processing.
Some notes about file uploads
It may take a little time to process depending on how busy the system is.
It will be important to use the templates in CORE Help for testing and working later after go live.
Some naming conventions cannot be used as they cause issues with uploads. These will be added to the instructions tab of our templates. That’s the only thing changing on the templates themselves. Combinations that cannot be used are as follows (asterisks denote anything being entered before or after the text provided):
FPCTable(.*)
FPCTran1(.*)
FPCTran2(.*)
FPCTran3(.*)
(.*)TIMEI(.*)
(.*)TIMEG(.*)
(.*)PaidDisb(.*)
(.*)OutAdv(.*)
I377(.*)
I378(.*)
ADDocExcepRep(.*)
The completion alert messages work differently in CORE 4 vs the current environment.
After some time (depending on the upload size), you can check the alerts page to see if the upload is complete. Once you open that page, they should show
CORE 4 can’t immediately display alerts as a number in a red bubble as shown in image. Once they are on this page, a refresh of some type needs to take place. Going to a different page or entering the Alerts page will refresh that data. This is different than 3.9 but part of how alerts are engineered in CORE 4.
Here is an example of three messages:
One that states the file was picked up.
One that states it validated successfully in the process.
A third that either tells you the upload was successful or that you have issues.
We are working with CGI to include the BATJOB number for successful entries so you can search for them in BATJOBS by using that value. Right now, that only appears for entries with errors.
Navigate to BATJOBS: When we navigate to BATJOBS, things will look similar to 3.9.
Two slight differences
First one is that there is a parent job and a child job for these entries in 4.x. There is only one job in 3.9.
The user id of the tester shows up in the Parent job name, not in the user id. Those are all created by the SA (System Admin) login but your user ID will show up under your user ID in the Transaction Catalog when you search for them.
Begin first by searching for your parent job. It is recommended that you utilize fields for Start Date (which will be the date you uploaded your ATS), and then you can put your CORE user ID into the Job Name field, with a wildcard * after it, to locate your specific ATS uploads for that date. You must put "SA" in the User ID field. From there, you can click the 3-dot for your specific ATS record in the grid results and look for information on the child job(s) created that will actually generate your CORE transactions.
Navigate to a Child Job: The log data looks very similar to what you see in 3.9. Each child job was successful in this example.
Look up the job(s) using Parent # and wild card: When the job # is provided on the alert, you’ll be able to do a wild card search to find all child jobs. Ex: <asterisk> Job Number <Asterisk>.
Navigate to GAX in the transaction catalog: Successful uploads go to workflow.
Scenario #2: Upload with error code that is rejected
The example below was taken from an upload for a department that is not associated with the user
Run through the same process as Scenario #1.
Once Alerts are viewed, you will see that the 3rd alert identifies an upload that failed with an Error Code 8 (same as 3.9).
This third alert provides a job #3341341.
Navigate to BATJOBS: Search for child jobs using the number in the alert.
Logs detail the reason for the issue (no access to used dept).
NOTE: This example details an upload that did not create any documents because of the severity of the error. Others may still generate docs in a Ready state that need to be corrected (also like 3.9).
Page updated
Report abuse