Skip to main content

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


Labels:

Comments

Post a Comment

Popular posts from this blog

O2C Cycle with Accounting Entries

  ORDER    TO  CASH  PARTICULARS  DR  CR SPL NOTES ACCOUNT IS PULLED FROM Sales order entry No Accounting Sales Order Pick From Sub Inventory A/c 100 At Standard Cost Sub-inventory Material A/c Setup To Sub Inventory A/c 100 At Standard Cost(Staging) Sub-inventory Material A/c Setup Sales Order Issue COGS 100 It can be fetched from five places Master Item/Org/Order Type/Line Type/Shipping Params To Sub Inventory A/c 100 At Standard Cost Sub-inventory Material A/c Setup Transaction level Receivable A/c 120 Auto Accounting Tax A/c 10 Auto Accounting Freight A/c 10 Auto Accounting Revenue A/c 100 Auto Accounting Receipts Receipts with no remittance method Cash 100 Before application of the receipt Receipt class Unapplied A/c 100 Receipt class Unapplied A/c 100 After application of the receipt to the transaction Receipt class Receivables A/c 100 Receipt class Cash A/c 100 Receipt class Unidentified A/c 100 In case of receipt without customer...
Post a Comment
Read more

Oracle Subledger Accounting (SLA) Tables, Views

Oracle Subledger Accounting (SLA) Tables, Views Oracle Subledger Accounting Tables: TABLE NAME DESCRIPTION XLA_AAD_GROUPS The XLA_AAD_GROUPS table stores the merge dependencies analyzed during the merge analysis.  All application accounting definitions with the same GROUP_NUM must be merged together. XLA_AAD_HDR_ACCT_ATTRS The XLA_AAD_HDR_ACCT_ATTRS stores standard, system and custom sources assigned to an accounting attribute at the AAD level. XLA_AAD_HEADER_AC_ASSGNS Store the analytical criteria for the application accounting definitions. XLA_AAD_LINE_DEFN_ASSGNS This table stores the journal lines definitions for the application accounting definitions. XLA_AAD_LOADER_DEFNS_T The XLA_AAD_LOADER_DEFNS_T table is the interface table that facilitates the data transfer from data files and the database. XLA_AAD_LOADER_LOGS The XLA_AAD_LOADER_LOGS table stores the errors and logs generated by the application accounting definitions loader. XLA_AAD_SOURCES XLA_AAD_SOURCES table stores a...
1 comment
Read more

Number to Word conversion in RTF

<?xdofx: expression ?> for extended SQL functions <?xdoxslt: expression ?> for extended XSL functions. You cannot mix xdofx statements with XSL expressions in the same context This function enables the conversion of numbers to words for RTF template output. This is a common requirement for check printing. The new function is “to_check_number”. The syntax of this function is <?xdofx:to_check_number(amount, precisionOrCurrency, caseType, decimalStyle)?> The following table describes the function attributes:   Attribute Description Valid Value amount The number to be transformed. Any number precisionOrCurrency For this attribute you can specify either the precision, which is the number of digits after the decimal point; or the currency code, which will govern the number of digits after the decimal point. The currency code does not generate a currency symbol in the output. An integer, such as 2; or a currency code, such as ‘USD’. caseType The case type of th...
Post a Comment
Read more