Results for “cdl_line_num”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_XLA_UPG_LINES_GT is a Global Temporary Table (GT) owned by the PA (Projects) schema in Oracle E-Business Suite. It serves as a transient staging structure used during the upgrade and migration of Subledger Accounting (XLA) data for project-related transactions. In the context of the 12.1.1 to 12.2.2 upgrade path, this table facilitates the transformation of expenditure items and related accounting events into the XLA schema, specifically supporting the conversion of project cost distributions into Subledger Accounting journal entry lines. The table is populated programmatically during upgrade and posting processes, then consumed by the XLA Accounting Program to generate final accounting entries in the SLA tables.

From a Data Vault modeling perspective, the mined heuristic classification for PA_XLA_UPG_LINES_GT is standalone. This reflects its nature as a temporary, processing-oriented structure rather than a persistent hub, link, or satellite. It does not participate in a permanent dimensional model; instead, it acts as a transient staging area whose contents mirror the line-level attributes of project expenditure distributions awaiting conversion into the XLA data model.

Key Information Stored

The table contains 27 documented columns in ETRM 12.2.2. The most significant columns and their roles are as follows:

Because this is a Global Temporary Table, rows are scoped to the session or transaction and no permanent surrogate primary key is enforced; uniqueness is effectively defined by the combination of EXPENDITURE_ITEM_ID, CDL_LINE_NUM, and the ledger/legal entity context during a given processing run.

Common Use Cases and Queries

PA_XLA_UPG_LINES_GT is primarily used during the upgrade of Projects accounting to Subledger Accounting and during routine cost distribution posting. Typical scenarios include diagnosing failed upgrade lines, verifying accounted amounts prior to transfer, and reconciling project costs against GL balances.

  • Identifying staging lines for a specific expenditure item: 
    SELECT expenditure_item_id, cdl_line_num, gl_date,
       acct_raw_cost, code_combination_id
  FROM pa.pa_xla_upg_lines_gt
 WHERE expenditure_item_id = :item_id;
  • Reconciling accounted cost totals per ledger and period: 
    SELECT ledger_id, gl_period_name, SUM(acct_raw_cost)
  FROM pa.pa_xla_upg_lines_gt
 GROUP BY ledger_id, gl_period_name;
  • Detecting currency conversion discrepancies by comparing CONVERSION_RATE against DENOM_RAW_COST and ACCT_RAW_COST.

Related Objects

The following objects are most significant to PA_XLA_UPG_LINES_GT based on documented foreign-key relationships:

  • PA_EXPENDITURE_ITEMS_ALL — Joined via EXPENDITURE_ITEM_ID; the source of project cost transactions.
  • FV_LEGAL_ENTITIES — Joined via LEGAL_ENTITY_ID; provides legal entity context.
  • XLA_EVENTS and XLA_AE_LINES — Consume the staged data via ENTITY_ID/EVENT_ID to create final subledger journal lines.
  • GL_CODE_COMBINATIONS — Resolves CODE_COMBINATION_ID to valid accounting flexfield combinations.
  • GL_LEDGERS — Validates LEDGER_ID and supplies ledger currency and period information.