{"id":604,"date":"2026-10-16T09:12:52","date_gmt":"2026-10-16T09:12:52","guid":{"rendered":"https:\/\/selatechnologyacademy.com.tr\/?p=604"},"modified":"2026-10-16T17:03:04","modified_gmt":"2026-10-16T17:03:04","slug":"oracle-fusion-financials-troubleshooting-subledger-accounting","status":"publish","type":"post","link":"https:\/\/selatechnologyacademy.com.tr\/?p=604","title":{"rendered":"Oracle Fusion Financials: Troubleshooting Subledger Accounting"},"content":{"rendered":"

Oracle Fusion Financials: Troubleshooting Subledger Accounting<\/h1>\n

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.<\/p>\n

1. Identify the source transaction<\/h2>\n

Record the transaction number, business unit, ledger, accounting date, and source module. Confirm that the transaction is complete and eligible for accounting.<\/p>\n

2. Review accounting status<\/h2>\n

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.<\/p>\n

3. Validate accounting configuration<\/h2>\n

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.<\/p>\n

4. Check transfer to General Ledger<\/h2>\n

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.<\/p>\n

5. Confirm the reporting context<\/h2>\n

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.<\/p>\n

Good practice<\/h2>\n