Import Subledger Journals

Oracle E Business Suite: Import Subledger Journals


Import Subledger Journals



What is Journal Import:

General Ledger is a main ledger where all the subledger data and main ledger data are consolidata for reporting purposes. Journal Import creates journal entries from accounting data you transfer from other applications. Oracle applications which transfer transactions to the General Ledger for example: Accounts Payable, Accounts Receivable, Fixed Assets, Purchasing, Inventory, Projects, and Payroll.

Oracle Assets creates journal entries directly in General Ledger, it does not use the GL interface like other subledgers.

We can also use Journal Import to create journals from external subledger systems if the transactions are loaded into the GL_INTERFACE table using custom interface programs.

Note: It is strongly recommended that subledger journals are not adjusted in GL as it would cause reconciliation problems. Whenever possible, we should make adjustments in the subledger and allow the correcting entries to flow to the GL in the next transfer. For this reason, all subledger Sources have the Frozen flag enabled to prevent changes. However, this can be changed based on the requirement using Setup>Journals>Sources .


Import Subledger Journals

Navigate to: Journals>Import>Run


Source: Select the Source for which you want journal import to create journals

Group ID: Optionally, specify a unique Group Id for each request.

Post Errors to Suspense: If suspense posting is allowed in the Set of Books, you can choose Post Errors to Suspense. If this option is chosen, journal import will create journals with account errors in the source data. If this option is not chosen, journal import will reject any source that contains account errors.

Create Summary Journals: If Summary Journals is chosen, journal import summarizes all transactions into one debit and credit line for the same account, period, and currency.
Note: Best practice is to create summary journals. If you do not, you will generate a large number of journal lines.

Date Range: Enter a Date Range to have General Ledger import only journals with accounting dates in that range. If you do not specify a date range, General Ledger imports all journal data.


Example: Import Purchasing Transactions

Source: Select Purchasing.

Group ID: This can be left blank.

Create Summary Journals: Check this box so those summary journals will be created.
Note: If a business decision has been made during implementation that detail transactions will be transferred to the GL, then you should not check this box.

Click the Import button.


Click on Yes to commit import. A Note window will display a request ID.

Review Journal Import Execution Report and ensure that the status is Success. If there are errors, determine how to correct them.

If you have only a few Journal Import errors, correct the errors from the Correct Journal Import Data window, then rerun Journal Import on the corrected data. Navigate to: Journals>Import>Correct

If the number of Journal Import errors is high, delete all of the import data for your journal entry source and Group Id. Correct the errors then repopulate the GL_INTERFACE table before rerunning Journal Import using Journals>Import>Delete


Another different example for Project

Import Projects Transactions

Source: Select Projects

Group ID: For Projects this must be selected from the field poplist.

Create Summary Journals: Check this box so summary journals will be created.
Note: If a business decision has been made during implementation that detail transactions will be transferred to the GL, then you should not check this box.

Click the Import button.

Note: For Projects, unlike for Purchasing and Inventory, the Group Id must be selected. The reason for requiring a Group id is that there are four interfaces from Projects to the General Ledger: Labor Costs, Usage and Miscellaneous Costs, Total Burdened Cost, and Revenue. There are reports in Projects that identify the interface for a Group id.

A Note will appear, that asks “Are you sue you want to start Journal Import”.

Click Yes to commit the import. A Note window displays the concurrent request ID.

Review Journal Import Execution Report and ensure that the status is Success. If there are errors, determine how to correct them.

Follow the same step as explained above for the purchasing transactions import.