Troubleshooting Unit Defined Commitment Load Errors

Overview

There are two times when you can encounter an error or warning message throughout the UDC upload process:

Errors/Warnings when Creating the Data File

When you run the macro process (i.e., click the Create UDC Commitments Load ASCII button), the system checks for field formatting and missing data.  The system may return warning or error messages:

Warning messages alert you that the data you entered in a field will be automatically changed (i.e., truncated) to fit the field format when the data is loaded into M-Pathways. They do not prohibit the creation of the data file.

Error messages indicate which field(s) in the Load Template contains an error.  Error messages prevent the data file from being created.

The system doesn’t load any rows from the data file when an error occurs.  All errors need to be corrected before the data file can be successfully loaded into M-Pathways.

Use the Error; Control Report described in the Using the Unit Defined Commitments Load Template procedure to verify whether or not a UDC load was successful.

The following table describes the potential macro process errors:

Field Error Description Error Message
Business Unit If not UMICH ERROR - Business Unit on row # is required. File not created.
Commitment # If the field is blank ERROR - Commitment number on row # is required. File not created.
Commitment # If the field is not blank, but the value is not a six-digit number or NEXT ERROR - Commitment number on row # must be 6 digits or NEXT. File not created.
Commitment # If the value is six digits, but not numeric ERROR - Existing commitment number on row # must be 6-digit numeric. File not created.
Reference If the value is more than 10 characters WARNING - Commitment reference on row # must be 10 characters or less. Commitment reference will be truncated.
Begin Date If the field is blank ERROR - Begin date on row # is required. File not created.
Begin Date If the field is not blank, but the value is not a valid date (i.e., 13/40/2003) ERROR - Begin date on row # is not a valid date. File not created.
End/Pay Date If the field is not blank, but the value is not a valid date (i.e., 13/40/2003) ERROR - End date on row # is not a valid date. File not created.
End/Pay Date If the date is prior to the (i.e., less than) Begin Date ERROR - End date on row # must be greater than or equal to begin date. File not created.
Description 1 If the description contains more than 30 characters WARNING - Description 1 on row # must be 30 characters or less. Description will be truncated.
Description 2 If the description contains more than 30 characters WARNING - Description 2 on row # must be 30 characters or less. Description will be truncated.
Notes If the notes contain more than 254 characters WARNING - Notes on row # must be 254 characters or less. Notes will be truncated.
Notes If you pressed Tab or Enter on your keyboard while entering notes WARNING - Notes on row # have carriage returns and/or tabs. They've been replaced with a space.
Fund If the field is blank ERROR - Fund on row # is required. File not created.
Fund If the field is not blank, but the value is not five characters ERROR - Fund on row # must be 5 characters. File not created.
Deptid If the field is blank ERROR - Deptid on row # is required. File not created.
Deptid If the field is not blank, but the value is not six characters ERROR -Fund on row # must be 6 characters. File not created.
Program If the field is not blank, but the value is not five characters ERROR - Program on row # must be 5 characters. File not created.
Proj/Grt If the field is not blank, but the value is greater than 15 characters ERROR - Project/Grant on row # must be 15 characters or less. File not created.
Account If the field is blank ERROR - Account on row # is required. File not created.
Account If the field is not blank, but the value is not a six-digit number ERROR - Account on row # must be 6 numeric. File not created.
Account If the value is less than 400000, greater than 799999, or not numeric ERROR - Account on row # is not a revenue or expense account. File not created.
Account If the value is less than −9,999,999,999.99 or greater than 9,999,999,999.99 ERROR – Amount on row # must be between
−9,999,999,999.99 and 9,999,999,999.99. File not created.

Errors When Uploading the Data File

The following table describes the possible errors that may appear on the Error & Control Report.

Field Error Description Error Message
Commitment # The Commitment # entered on the data file to update an existing commitment is not found in the database. Invalid commitment number
Fund Fund value used is not an active value on the Fund table as of the commitment Begin Date.. Invalid fund
Program The Program value used is not an active value on the Program table as of the commitment Begin Date. Invalid program
Proj/Grt The Project/Grant value used is not an active value on the Project Header table as of the commitment Begin Date. Invalid proj/grant
Account The Account value used is not an active value on the GL Revenue Account View table as of the commitment Begin Date. Invalid account