Skip to main content

'Transfer Journal Entries to GL program' Functionality and FAQs

1. What are the tables involved in the Transfer to GL and GL posting? 

Subledger Tables



Transfer Journal Entries to GL (XLAGLTRN) process takes the Subledger journals and inserts records into the Interface Tables.

Interface Tables 
          GL_INTERFACE / XLA_GLT_<groupid>
          Journal Import (GLLEZL) then reads from the interface table and creates records in the GL Tables

GL Tables


2. What are the different methods to transfer Subledger journals to GL?

GL Transfer can be spawned during Online Accounting using the "Final Post" option for a specific document (Example: AP Invoice and AR Transaction).

Example: Navigation in Payables: Invoices/Entry/Invoices: Action: Create Accounting/Final Post. This spawns the GL Transfer, the Journal Import, Data Manager and the GL Posting processes. This request transfers ALL the final accounted data for that document. This method of transfer uses the interface table GL_INTERFACE to move the journals to the general ledger.

GL Transfer can also be spawned by the Create Accounting concurrent request when submitted with the "Transfer to GL" parameter set to Y.

Example:  Navigation in Payables: Other/Request/Run: Create Accounting.
This spawns the journal import and the data manager processes. The GL Posting process is spawned if the Post to GL parameter is set to Yes when submitting the Create Accounting. This request transfers all the final accounting created by the Create Accounting request that spawned it. This method uses the interface table XLA_GLT_<groupid>. 


GL Transfer can be submitted in standalone mode using the concurrent request "Transfer Journal Entries to GL".

Example: Navigation in Payables: Other/Request/Run: Transfer Journal Entries to GL.
This spawns the Journal Import and the Data Manager programs. This request transfers all the final accounting that exists for the given ledger and end date. This method uses the interface table XLA_GLT_<groupid>.

3. What columns indicate the Transfer Status of accounting data in Subledger?

The XLA_AE_HEADERS table shows the transfer status of the accounting data, after successful transfer to the GL and Journal Import:
§                     XLA_AE_HEADERS.gl_transfer_status_code = Y 
§                     XLA_AE_HEADERS.gl_transfer_date is not null 
§                    XLA_AE_HEADERS.group_id is not null

For 11i data upgraded to R12, the transfer status can be determined using the following
§                   XLA_AE_HEADERS.gl_transfer_status_code = Y 
§                  XLA_AE_HEADERS.gl_transfer_date is null 
§                  XLA_AE_HEADERS.group_id is null 
§                 XLA_AE_HEADERS.upg_batch_id is not null  --> indicates 11i data

4. What is the setup option that determines the level of detail in the accounting lines created for a specific transaction in XLA_AE_LINES?

Each Journal Line Type (JLT) can be setup as required to result in either detailed or merged lines in XLA_AE_LINES. 

Navigation: Accounting Setups: Subledger Accounting Setup: Accounting Methods Builder: Journal Entry Setups
 Form: “Define Journal Line Types" 
 Field: "Merge Matching Lines" 

The different options are as follows: 

1) ALL - The matching lines in XLA_DISTRIBUTION_LINKS for the specific accounting header and specific journal line type (example: LIABILITY) are merged to create records in XLA_AE_LINES. 

2) DR/CR - The matching lines in XLA_DISTRIBUTION_LINKS, for the specific accounting header and specific journal line type (example: LIABILITY) with debit side entries, are merged to create one debit entry in XLA_AE_LINES. The matching lines with credit side entries are merged to create one credit side entry in XLA_AE_LINES.

3) NO - Lines in XLA_DISTRIBUTION_LINKS for the specific accounting header and specific journal 
line type (example: LIABILITY) are not merged and copied into XLA_AE_LINES. 
  NOTE: This setup applies to merging lines within a specific transaction.

5. What is the setup option that determines if transfer to GL is in detail or summarized mode?

There are two variables that determine how the data is transferred to GL from the Subledger tables XLA_AE_HEADERS and XLA_AE_LINES. These setups determine whether accounting data from across multiple transactions in the Subledger will be merged or not merged while inserting into rows in the GL_JE_HEADERS and GL_JE_LINES tables.

      a)    Subledger Accounting Options 
Navigation: Accounting Setups : Ledger Setup : Define : Accounting Setups 
Choose the ledger  Click on "Update Accounting Options" Scroll to Subledger Accounting Options in the Primary Ledger section  Click on Update Icon  Click on Update Icon against the Application to be setup(Example: Payables) 

Field: General Ledger Journal Entry Summarization
This can be set to ONE of the following:
§  Summarize by GL Period 
§  Summarize by GL Date 
§  No Summarization
This setup determines if the accounting header is summarized or not.

b) Journal Line Types
Navigation: Accounting Setups: Subledger Accounting Setup: Accounting Methods Builder: Journal 
Entry Setups 
Form: “Define Journal Line Types" 
Field: Transfer to GL 
This can be set to Summary or Detail 

This setup determines if the accounting lines in XLA_AE_LINES are summarized during transfer to GL. 

Note 1: Lines cannot be summarized if the headers are not summarized. 
If "General Ledger Journal Entry Summarization" is set to No Summarization, the "Transfer to GL" setup in the Journal Line Types are irrelevant. The lines and headers are not summarized in this scenario. 

Note 2: Irrespective of transfer in Detail or Summary, there is always a one-to-one correspondence between the XLA_AE_LINES and GL_IMPORT_REFERENCES tables.

GL Posting process then posts to the GL_BALANCES table.

6. What columns associate GL data back to the SLA data?

Since there is always a one-to-one correspondence between XLA_AE_LINES and GL_IMPORT_REFERENCES, they are used to link GL and the Subledger. 
GL_IMPORT_REFERENCES.gl_sl_link_id => XLA_AE_LINES.gl_sl_link_id 
GL_JE_BATCHES.group_id => XLA_AE_HEADERS.group_id

7. Why are reference columns in GL_IMPORT_REFERENCES not populated by the R12 Transfer to GL process, which is unlike 11i?

In R12, until recently, the reference columns were not populated by the transfer process. With patch 7512923:R12.XLA.A (for R12.0.x), 6 reference columns REFERENCE5 to REFERENCE10 in GL_IMPORT_REFERENCES are now populated with entity_id, event_id, ae_header_id, ae_line_num, accounted_cr, accounted_dr. 

This will help with troubleshooting when the link between Subledger and GL is broken due to missing gl_sl_link_id.

8. What is the default value for the Transfer to GL in the seeded journal line types (JLT)?

There is no specific default value across the application.  Depending on the product, the JLTs may be seeded as Detail or Summary for the Transfer to GL option.

9. If a customer's business requires a different setup than the default, can the seeded JLT be updated?

The seeded JLT cannot be updated.  However, the seeded JLT can be copied and a new custom JLT can be created, where changes can be made on the custom JLT.

10. How many group_ids are created during the transfer process when there is a primary ledger and associated ALC/reporting ledger?

The primary ledger data and associated ALC/reporting ledger data goes into one group_id. Data from this one group_id can be split across multiple GL Batches based on other criteria, such as je_category/date/period. However, one GL Batch can only be associated to one group_id.

11. How many group_ids are created during transfer process when there is a primary ledger and a secondary ledger?

Two group IDs are created--One for the primary ledger and one for the secondary ledger. Two journal import processes are spawned in this case, one for each group_id. If there is failure in the journal import for either ledger, the transfer is rolled back for both ledgers.

12. Is there a setup to prevent spawning the Journal Import on instances where a third party (e.g., Peoplesoft) GL is used?

The profile option "Disable Journal Import" (when set to Yes) prevents the GL Transfer from invoking the Journal Import. The interface table used in this case is GL_INTERFACE. Setting this profile option is not recommended if you are using Oracle General Ledger. The profile option is hidden and disabled in the latest code.

13. Is there a diagnostics script available to detect issues with transfer process?

With the application of patch 8513940:R12.XLA.A (for R12.0.x), there is a diagnostics script that allows you to troubleshoot issues with the Transfer to GL.
Some of the issues this script detects are as follows:
    ·         Negative ledger_id in GL tables
    ·         SLA data marked as transferred but not in GL
    ·         GL data exists but SLA data marked as untransferred
    ·         SLA data transferred multiple times to GL.
The following two questions are specific to Payables Subledger.

14. When is data inserted into the XLA_TRIAL_BALANCES table?

The XLA_TRIAL_BALANCES table is populated after successful journal import. 
Data from XLA_DISTRIBUTION_LINKS is used to populate the XLA_TRIAL_BALANCES table. It can also be repopulated during a trial balance rebuild using the "Open Account Balances Data Manager" process.

15. Why are the original encumbrance entries not transferred to GL before the reversal encumbrance journals?

This happens because of the mode used for Transfer to GL. When using the Online mode from a document to Final post to GL, all accounting entries including the encumbrance accounting created during validation, and the actual and reversal encumbrance created during accounting are transferred to GL. 

However, when you run the batch Create Accounting with Transfer to GL parameter set to Yes, only the actual accounting and encumbrance reversals that are generated during that specific accounting process are transferred to GL.  This leaves the original encumbrance created during invoice validation to remain untransferred. This should then be transferred by submitting the "Transfer Journal Entries to GL" request.


Popular posts from this blog

SQL Query to extract Oracle Purchase Order Information

SELECT   poh.po_header_id,    poh.type_lookup_code PO_TYPE,   poh.authorization_status PO_STATUS,   poh.segment1 PO_NUMBER,   pov.vendor_name SUPPLIER_NAME,   povs.vendor_site_code Location,   hrls.location_code Ship_To,   hrlb.location_code Bill_to,   pol.line_num ,   msib.segment1 Item,   pol.unit_price,   pol.quantity,   pod.amount_billed Amount,   pod.destination_subinventory,   ppf.full_name Buyer_Name,   poh.closed_Code  FROM   PO_HEADERS_ALL poh,   PO_LINES_ALL pol,   mtl_system_items_b msib,   PO_LINE_LOCATIONS_ALL poll,   PO_DISTRIBUTIONS_ALL pod,   po_vendors pov,   po_vendor_sites_All povs,   hr_locations_all hrls,   hr_locations_all hrlb,   per_all_people_f ppf,   po_line_types polt WHERE   1                         =1 AND polt.line_type_id    = pol.line_type_id AND povs.vendor_site_id     = poh.vendor_site_id AND pov.vendor_id           = poh.vendor_id AND pol.item_id             = msib.inventory_item_id AND msib.organization_id  

Query to find Operating Unit, Business Group and Legal Entity Information

SELECT   DISTINCT   hrl . country ,                  hroutl_bg . name              bg ,                  hroutl_bg . organization_id ,                  lep . legal_entity_id ,                  lep . name                    legal_entity ,                  hroutl_ou . name              ou_name ,                  hroutl_ou . organization_id   org_id ,                  hrl . location_id ,                  hrl . location_code ,                  glev . flex_segment_value FROM     apps . xle_entity_profiles   lep ,         apps . xle_registrations   reg ,         apps . hr_locations_all   hrl ,         apps . hz_parties   hzp ,         apps . fnd_territories_vl   ter ,         apps . hr_operating_units   hro ,         apps . hr_all_organization_units_tl   hroutl_bg ,         apps . hr_all_organization_units_tl   hroutl_ou ,         hr_organization_units   gloperatingunitseo ,         apps . gl_legal_entities_bsvs   glev WHERE    lep . transacting_entity_flag   =   'Y'         AND   l

List of iExpenses Tables

List of iExpenses Tables  Table Name Description AP_EXPENSE_REPORT_HEADERS_ALL Expense report header information AP_EXPENSE_REPORT_LINES_ALL Expense report lines information AP_EXP_REPORT_DISTS_ALL Expense report distribution information. It contains the accounts against each expense report line. AP_CREDIT_CARD_TRXNS_ALL Table to store the corporate credit card transactions that are sent by the banks. These lines are saved as expense lines when the user creates the expense lines for credit cards AP_NOTES Table to store the comments entered by approvers and auditors     Setup tables   AP_EXPENSE_REPORTS_ALL This table contains the header level information about the expense templates AP_EXPENSE_REPORT_PARAMS_ALL This table contains the detail level information about the expense templates AP_POL_CAT_OPTIONS_ALL Table to store the policy options AP_POL_CONTEXT Table to store the policy context     AP_POL_LOCATIONS_TL Table