Front end split errors

This list shows the two types of errors that occur when the Journalize Front End Split Distributions action is run:

Data errors can occur for Invalid pairs, inactive statuses, or invalid project dates
Budget edit errors occur when the remaining budget amount is exceeded

Use these options to correct budget edit errors:

Add additional budget to the affected funding sources and run the Interface Transactions action
Change the funding source on the GLTransactionInterface and run the Interface Transactions action

If one transaction in the journal group fails, then all transactions in the journal group remain on the interface table. When the journalize action is run en masse, each contract has a unique journalize group. If errors occur during journalize, then GLTransactionDetail is not created from a GLTransactionInterface record. The GLTransactionInterface record status is Error.

On the Front End Split Results tab, Drill Around® to the Global Ledger Interface Results to correct the errors. Because transactions are editable, errors can be corrected from the list. After the errors are corrected, the interface action can be run to create GLTransactionDetail.

Note: The Billed and Recognized fields on the original transaction that was split are set to Processed before the GLTransactionInterface records are created.

If the interface fails and you delete the records, then you cannot re-split the original records. We do not recommend delete as an option to correct errors. If the Reference field is Front End Split, then the user is required to use a double transmit for the delete action in GLTransactionInterface.