Troubleshooting Inter-Entity Errors: Loan Accounts & G/L Triggers

This article focuses on error types specific to Inter-Entity Transactions (Loan Account entry automation, and G/L Triggers). If you are looking for other error types:

• For XAPI errors, refer to Troubleshooting XAPI Errors, as these are common to Inter-Entity Transactions and Inter-Entity Trade.
• For troubleshooting other error types, refer to Introduction to Inter-Entity Errors .

Common Audit Log errors (after batch posted)

These errors appear in the IET Audit Log once the source G/L Batch has posted. To view the log:

• Go to Inter-Entity Transactions \ IET Inquiries
• Open IET Audit Inquiry (or IET G/L Triggers Audit Inquiry)
• Filter using Ctrl-F on any column. (E.g. Transaction Status = Error)
• You can filter Date/Time Created or Amended columns to check for recent errors.

Error Message	Resolution
Period X in fiscal year YYYY is locked for General Ledger in Common Services’ Fiscal Calendar	Open the Fiscal Period, then re-process through IET Periodic Processing
Fiscal Year YYYY does not exist	Option the Fiscal Year, then re-process through IET Periodic Processing
Account AAA-BB-CC does not exist	Create the G/L Account, then re-process through IET Periodic Processing
Account AAA-BB-CC is inactive	Make the G/L Account active, then re-process through IET Periodic Processing
Account AAA-BB-CC is a Control Account	De-select “Control Account", then and re-process through IET Periodic Processing
Error creating document header.  Customer number “xxxx” does not exist. (Applies to G/L Triggers: AR Reallocations)	Create Customer, then re-process through IET Periodic Processing
Error creating document header.  Vendor “xxxx"is not defined in A/P Vendors. (Applies to G/L Triggers: AP Reallocations)	Create Vendor, then re-process through IET Periodic Processing

 

After resolving the cause of the error, you should re-process the error transactions.

In some cases, when Inter-Entity Transactions does not create transactions, please check the G/L Posting Errors report for details on the issues.

Re-Processing Error Transactions using Periodic Processing

• Open Inter-Entity Transactions \ IET Periodic Processing

• Select the Periodic Processing tab

• Check ‘IET Periodic Processing’ (or 'G/L Triggers Periodic Processing')
• Select the Posting Sequence and other options

• Check ‘Process Error Entries’ (or 'Process G/L Trigger Error Entries')

• Click ‘Process’

Inter-Entity will attempt to re-process. You can then return to the Audit Log to check that the status has changed to ‘Exported’ for the problem entries.

Note: This only applies to G/L Batches across databases and when using G/L Triggers. Periodic Processing does not apply when posting G/L Batches in a single database and not using G/L Triggers. You need to use the GL Posting journal errors as described below.

Common errors preventing the G/L Batch from posting

• These error messages will be displayed as you are posting (not in the Audit Log).
• An Error Batch will be created.

• You can view details of the errors in the G/L Reports > G/L posting journal errors.

Error Message	Resolution
No Entity Route Defined	Create the IET Route (or correct the G/L Journal Entry), and re-post.
Entity DR, CR unbalanced	Ensure all accounts use the entity segment.  Correct the G/L Journal Entry, and re-post
Account “xxxx-y” does not exist or is inactive	Create the G/L Account (or make it active), and re-post