| ... |
... | ... |
UVA UBO Budget Developer
None.
The Director of the Budget is responsible for ensuring that this document is necessary, that it reflects actual practice, and that it supports University policy.
1. Modify an existing Excel spreadsheet submitted by a departmental unit and located in a local drive.
|
Header field |
Comments |
|
GM_PROJECT |
Enter GM projects here. Do not enter GL project values here. |
|
TASK_NUMBER |
|
|
AWARD_NUMBER |
|
|
EXPENDITURE_TYPE |
|
|
GL_ENTITY |
|
|
GL_PROJECT |
Enter GL project values here |
|
GL_FUND_SOURCE |
|
|
GL_OBJECT_CODE |
|
|
Amount |
|
|
FTE |
|
|
PERIOD_YEAR |
|
|
VERSION |
If user is loading a version of “R” (Revised), all data with same Period Year and a version of “R” that currently exists in the table will be deleted. |
2. Save the Excel spreadsheet as a comma separated file on your C: drive or local network drive.
NOTE: The first line of this file should always be a header line listing the column titles. The program skips the first line regardless of whether or not it is actually a header line. As a result, if the first line is actual data to be loaded, the program will not load this data.
5. Connect to Production Host - isp-ods.admin.virginia.edu.

7. Enter username and password. This is your Unix password which has to be reset each year. Call the ITC helpdesk for assistance (4-3731).


10. Drag .dat file icon from Local directory screen to Remote directory screen to copy:

11. Select ASCII (text) and press OK.

12. Confirm that the file is now in Remote directory. The file size on remote host may not match the size on local directory.

Once the upload to the IS budget development table is complete, the file is moved from the data file folder to the Archive folder and the date and time is appended to the file name. If the file has bad data, it is deleted from the data file folder. You must then correct the original spreadsheet and rerun the FTP process.
UVA Budget
M ® Requests
Find Requests
13. Open the Integrated System and log on with the UVA UBO Budget Developer responsibility.
14. From the menu, select Requests.

15. Click the [Submit a New Request] button from the ‘Find Requests’ screen.

Note: The upload from the UNIX directory to the IS table is a two-step process. First, the data is loaded into a staging table where the file format is validated. Second, the data is pulled from the staging table, where the PTAEO validation and CCID validation occurs before it is loaded into the UVA_BUDGET_DEV table. These steps have been combined into one request set so that both steps will run at once.
13. Select 'Request Set' from the 'Submit a New Request screen.'

18. Since this is currently the only request set under this responsibility, it automatically populates the Request Set field with the UVA Budget Dev request set when the LOV is selected. Click the ‘Submit’ button.

19. The Requests screen pops up. The user should occasionally click on the Refresh Data button for an update of the Phase and Status.

Note: The Request shows up on the screen as ‘UVA Budget Dev (Report Set). The results show up on the screen as a set of four lines: two ‘Load Budget Data to Stage’ and two ‘Load Budget Data to Dev’.
Once the Phase has completed, the user can click on the 'View Log...' button to verify that all lines were loaded or to see any error messages if the file completed with a Status = Error. The log should be viewed for both the “Load Budget Data to Stage” step and for the “Load Budget Data to Dev” step.
Generally, if there is an ‘Error’ in the Status column of the ‘Load Budget Data to Stage’ steps, the error is related to the file. For example, the file wasn’t properly renamed with a .dat extension and wasn’t moved to the correct UNIX directory:
|
Error Message |
Definition / Action |
|
Budget Data File Not Found Please FTP your Data files to the UNIX directory =>/interface/inbound/datafile |
The program could not locate any files to upload. Check that the file was appropriately moved to the correct UNIX directory. |
|
ORA=00001: unique constraint (UVA.UVA_BUDGET_PTAEO_GL_U1) violated insert_into_budget_table |
A duplicate PTAEO or GL String was identified. Correct the appropriate line. |
|
Amount and FTE both have values |
An amount and FTE were entered on the same line. Correct the file by creating a second line with the appropriate expenditure type and associated value. |
|
Invalid Project, Invalid Task, Invalid Award |
The PTA combination is invalid. Verify that the correct values have been entered. |
If there is an ‘Error’ in the Status column of the ‘Load Budget Data to Dev’ steps, the error is generally related to the data being transferred:
|
Error Message |
Definition / Action |
|
ORA=00001: unique constraint (UVA.UVA_BUDGET_PTAEO_GL_U1) violated insert_into_budget_table |
A duplicate PTAEO or GL String was identified. Correct the appropriate line. |
|
Amount and FTE both have values |
An amount and FTE were entered on the same line. Correct the file by creating a second line with the appropriate expenditure type and associated value. |
|
Invalid Project, Invalid Task, Invalid Award |
The PTA combination is invalid. Verify that the correct values have been entered. |
If
the process completes with a Status =
Effective: 06/02/05
Revision: 4 mr/rsp
Oracle Tutor can be licensed to modify and add to this content, documenting all of your business process documentation in the Oracle Tutor format.
Oracle® Tutor Copyright © 1997, 2009, Oracle. All rights reserved.