Oracle Fusion Financials: Troubleshooting Subledger Accounting
Oracle Fusion Financials: Troubleshooting Subledger Accounting
When a transaction does not appear in General Ledger as expected, investigate its processing status before rerunning jobs. The precise cause depends on the module, transaction, accounting setup, and period controls.
1. Identify the source transaction
Record the transaction number, business unit, ledger, accounting date, and source module. Confirm that the transaction is complete and eligible for accounting.
2. Review accounting status
Check whether accounting has not been created, completed with warnings, or failed. Review the process output and transaction-level error details for invalid accounts, missing setup, or date and period issues.
3. Validate accounting configuration
Review the relevant accounting rules, account derivation, mapping sets, journal line rules, and supporting reference data. Confirm that the account combination is valid and enabled for the intended date and ledger.
4. Check transfer to General Ledger
If accounting exists in the subledger, verify whether transfer to General Ledger was requested and completed. Then review journal import status and locate any rejected or unprocessed journal lines.
5. Confirm the reporting context
Verify the ledger, accounting period, source, category, currency, and journal status in the report or inquiry. A filter mismatch can make a successfully processed journal appear missing.
Good practice
- Capture process IDs and error messages before changing setup.
- Correct the root cause before rerunning accounting or transfer.
- Follow approved controls for reversals, adjustments, and period close.
This is general troubleshooting guidance. Explore our Oracle Fusion Financials training for structured learning.