Resolve Issues with Transferring Journal Entries to General Ledger

When attempting to transfer journal entries from subledgers to the general ledger, you may encounter issues that prevent successful processing, such as journal entries remaining untransferred in the subledger and failures in the Create Accounting Process to transfer these entries to the General Ledger.

The Create Accounting process offers two modes: Final and Draft. If Final mode is selected, the Transfer to General Ledger parameter can be used to automatically transfer the accounting entries generated by that particular run. However, this process only transfers entries created during the specific run that initiates the transfer. The accounting entries generated by previous runs that were not transferred remain unprocessed and require the Post Subledger Journal Entries program to be executed separately for transfer.

Note: If accounting is created in error by any mode, they are treated as draft entries. These entries can be viewed but not transferred until corrected. Any changes will need to be made to the transaction or journal line definition/rules to correct the accounting. After corrections, entries can be recreated in either draft or final mode, depending on their accuracy.

Possible Causes of Untransferred Journal Entries:

• The accounting is created in Draft mode and can’t be transferred.
• The accounting is created in error and can’t be transferred.
• The accounting was created by the Create Accounting process without selecting the Transfer to General Ledger option.
• Journal Import failed/had errors. If the Journal Import spawned by the Post Subledger Journal Entries program fails/has errors, ALL data included in the transfer and import is rolled back/not transferred. However, if the Subledger Lookup Code XLA_PROMO_31776850_ON is activated, only entries with errors are rolled back.

Resolution

Here’s how you can resolve this issue:

1. Submit the Post Subledger Journal Entries process to transfer any accounting that is created in Final mode, but not transferred.
2. Navigate to Scheduled Processes.
3. Select and Submit the Post Subledger Journal Entries process, ensuring to include the parameters to transfer the journal entries that were created in Final mode but not transferred.

Note: If the Post Subledger Journal Entries process triggers a Journal Import: Child process, this indicates that subledger entries have been selected for transfer. Examine the Journal Import: Child process report (.txt) output for any import errors. If any errors are detected, the entire import and transfer is rolled back. However, if the Subledger Lookup Code XLA_PROMO_31776850_ON is enabled, only entries with errors are rolled back. Hence the Create Accounting subprocess summarizes and transfers the subledger accounting entries to the General Ledger without launching the Post Subledger Journal Entries and Journal Import processes.