Journal Import in GL

Journal Import

In R12 the Create Accounting for each subledger populates the common XLA tables (Sub ledger Accounting). When the accounting is Final then the Transfer Journal Entries to GL process populates the GL interface and automatically submits the Journal Import. It can also submit the Post for the imported journals automatically.

Journal import loads data from the subledgers into the GL_INTERFACE table and then after performing validation on the data into GL_JE_BATCHES, GL_JE_HEADERS and GL_JE_LINES tables.

Submit Journal Import Run

Once the data is in the GL_INTERFACE table, you can manually submit the import process from the Import Journals form

Responsibility: General Ledger Super User
Navigation: Journals > Import > Run

Source: Select the Source from which source you want Journal Import to create journal entries, it can be Receivables, Payables, or spreadsheet etc.

Group ID: When the information comes from Oracle Applications subledgers, the value for this field is assigned automatically and is defined by the sequence GL_INTERFACE_CONTROL_S. The Journal Import process selects records based on SOURCE and optionally GROUP_ID. If you do not specify a Group ID, General Ledger imports data from the specified journal entry source with no corresponding Group ID (null Group ID)

Caution: Do not specify more than 20 Source/Group ID combinations per import. Journal Import cannot process more than 20 Source/Group ID combinations at once

Post Error to Suspense: If you allow suspense posting in your set of books, you can Post Errors to Suspense. With this option, Journal Import creates journal entries with suspense journal lines for account errors in the source data. If you choose not to post errors to suspense, Journal Import rejects any source/group ID combination that contains account errors.

Create Summary Journals: Choose to Create Summary Journals to summarize all transactions for the same account, period, and currency into one debit or credit journal line. This makes your reports more manageable in size, but you lose the one-to-one mapping of your detail transactions to the summary journal lines created by Journal Import.

If you choose to create summary journals, you cannot import descriptive flexfields.

 

Journal Import Correct

If your Journal Import run resulted in relatively few errors, you can correct the data that was rejected by Journal Import. After making your corrections, you can rerun Journal Import to create journals from your corrected accounting data.

In R12, the rows coming from subledger accounting are rolled back to the XLA tables and removed from the interface, so they must be corrected at subledger level and then transferred again, to avoid reconciliation problems between GL and the subledgers

Responsibility: General Ledger Super User
Navigation: Journals > Import > Correct