Results for “gmf_xla_extract_lines_u1”

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

Overview

GMF.GMF_XLA_EXTRACT_LINES is the Subledger Accounting (SLA) Extract Lines table within the Process Manufacturing Financials (GMF) product of Oracle E-Business Suite. Its role is to capture, at the individual accounting line level, all transaction data required for the creation of subledger journal entries for process inventory organizations. As process manufacturing transactions are processed, the necessary cost, quantity, and accounting attributes are staged in this and its related header table. When the SLA accounting program executes, it reads the rows held here as the authoritative source for constructing journal lines under the Create Accounting process.

From a data modeling perspective, the heuristic Data Vault classification for this object is standalone. Because the table contains no dependent child tables that reference it, and it references PO_COST_MST on only a single optional attribute, it functions most naturally as a satellite-like record capturing descriptive and financial measures keyed to an extract header, rather than as a hub or a link.

Key Information Stored

The documented physical schema comprises 36 columns in the GMF schema. The most significant are summarized below.

• LINE_ID — Surrogate primary key for the table. It is the sole column in unique index GMF_XLA_EXTRACT_LINES_U1, making it the documented business-key candidate and the authoritative join key to the extract header.
• HEADER_ID and EVENT_ID — Link the line to its parent extract header and to the underlying subledger accounting event.
• LEDGER_ID — Identifies the ledger set in which the accounting is performed.
• LINE_NUMBER and JOURNAL_LINE_TYPE — Sequence and classification of the generated journal line.
• TRANS_AMOUNT_RAW, BASE_AMOUNT_RAW, TRANS_AMOUNT, BASE_AMOUNT — The transactional and base-currency amounts, provided in both raw and processed forms.
• DR_CR_SIGN and ENTERED_AMOUNT/ACCOUNTED_AMOUNT — Sign indicator and entered/accounted values used when the journal line is constructed.
• COST_CMPNTCLS_ID, COST_ANALYSIS_CODE, COMPONENT_COST, COST_LEVEL, and AQUI_COST_ID — Cost element detail, with AQUI_COST_ID carrying the documented foreign-key relationship to PO_COST_MST.
• ORGANIZATION_ID, SUBINVENTORY_CODE, LOCATOR_ID, LOT_NUMBER, and SUBINV_ORGANIZATION_ID — Inventory context identifying where the transaction occurred.
• TRANSACTION_ACCOUNT_ID, REFERENCE_NO, and USAGE_IND — Account assignment, source document reference, and usage indicator.
• CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, PROGRAM_ID, and REQUEST_ID — Standard audit and concurrent program columns.

Common Use Cases and Queries

The table is most frequently used for SLA reconciliation, cost accounting period-close analysis, and diagnostic investigation of journal lines that failed to account. A typical pattern joins lines to the header to reconcile extracted amounts against the posted GL balances:

SELECT l.LINE_ID, l.HEADER_ID, l.LEDGER_ID,
       l.TRANS_AMOUNT, l.BASE_AMOUNT, l.DR_CR_SIGN,
       l.ORGANIZATION_ID, l.SUBINVENTORY_CODE
FROM   GMF.GMF_XLA_EXTRACT_LINES l
WHERE  l.LEDGER_ID = :ledger_id
AND    l.CREATION_DATE >= :period_start
ORDER BY l.LINE_ID;

Cost analysts query by AQUI_COST_ID to trace a line back to its source cost record, and inventory accountants filter on ORGANIZATION_ID and SUBINVENTORY_CODE to isolate activity for a specific process plant or subinventory. Because REQUEST_ID is populated, DBAs commonly trace failures back to the specific Create Accounting concurrent request that generated the rows.

Related Objects

Relationships documented in the ETRM metadata and typical join paths include the following.

• PO_COST_MST — Referenced by GMF_XLA_EXTRACT_LINES.AQUI_COST_ID; provides the source acquisition cost record.
• GMF_XLA_EXTRACT_HEADERS — Parent header table joined on HEADER_ID, supplying document-level SLA context.
• XLA_EVENTS — Joined on EVENT_ID to access subledger event metadata.
• GL_LEDGERS — Joined on LEDGER_ID to resolve ledger names and currencies.
• XLA_ACCOUNTING_ENTRIES / XLA_AE_LINES — The downstream SLA tables into which this extract data is transformed during Create Accounting.
• GL_CODE_COMBINATIONS — Joined on TRANSACTION_ACCOUNT_ID to resolve the accounting flexfield string.
• MTL_SYSTEM_ITEMS and MTL_ITEM_LOCATIONS — Referenced indirectly via ORGANIZATION_ID and LOCATOR_ID for item and locator context.