Results for “accounting_line_type_code”

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

Overview

CST_XLA_WIP_LINES_V is an APPS-owned database view within Oracle E-Business Suite, categorized under the BOM (Bills of Material) product family. It serves as a reporting and integration bridge between Work in Process (WIP) transaction accounting data and the Subledger Accounting (XLA) event model. The view exposes accounting line detail for WIP accounting events, presenting amounts, accounting line types, cost elements, and distribution identifiers in a single result set that conforms to the XLA line interface pattern.

For users searching on wip_transaction_accounts, this view is significant because it is defined directly over the WIP_TRANSACTION_ACCOUNTS table and joins it to the XLA events global temporary table. Rather than querying the base transaction accounts table in isolation, the view correlates each accounting line with its originating XLA event, ledger, and event identifier. This makes it a convenient access point for reconciliation, diagnostics, and custom reporting where event-level context is required alongside the underlying WIP accounting amounts.

Underlying Base Objects

According to the documented view metadata for 12.2.2, CST_XLA_WIP_LINES_V is defined over two referenced base objects, both accessed through APPS synonyms:

• WIP_TRANSACTION_ACCOUNTS (aliased as WTA) — the primary source of accounting line data, supplying amounts, cost element, rate or amount, reference account, WIP sub-ledger identifier, and WIP entity identifier.
• XLA_EVENTS_GT (aliased as XEG) — the XLA events global temporary table, supplying EVENT_ID and LEDGER_ID and acting as the event context for each line.

The join correlates the two sources on transaction identity and resource/basis discriminators: WTA.TRANSACTION_ID equals XEG.SOURCE_ID_INT_1, with NVL-guarded equality on SOURCE_ID_INT_2 against WTA.RESOURCE_ID and SOURCE_ID_INT_3 against WTA.BASIS_TYPE. The join is restricted to events where XEG.ENTITY_CODE equals 'WIP_ACCOUNTING_EVENTS'. Because XLA_EVENTS_GT is a global temporary table, the view is meaningful only when populated within the context of an XLA accounting program run.

Key Columns

• ACCOUNTED_AMOUNT — maps to WTA.BASE_TRANSACTION_VALUE, expressed in the ledger's base currency.
• ENTERED_AMOUNT — maps to NVL(WTA.TRANSACTION_VALUE, WTA.BASE_TRANSACTION_VALUE), providing the entered-currency amount with fallback to the base value.
• ACCOUNTING_LINE_TYPE_CODE — maps to WTA.ACCOUNTING_LINE_TYPE, identifying the type of accounting line.
• CODE_COMBINATION_ID — maps to WTA.REFERENCE_ACCOUNT, the accounting flexfield combination associated with the line.
• COST_ELEMENT_ID and RATE_OR_AMOUNT — carry the cost element reference and the applicable rate or amount.
• EVENT_ID and LEDGER_ID — obtained from the XLA events source, tying the line to its event and ledger.
• LINE_NUMBER — generated using ROW_NUMBER() OVER (PARTITION BY EVENT_ID ORDER BY EVENT_ID), producing a sequential line index within each event.
• DISTRIBUTION_IDENTIFIER — maps to WTA.WIP_SUB_LEDGER_ID.
• LINE_WIP_ENTITY_ID — maps to WTA.WIP_ENTITY_ID, identifying the WIP entity for the line.

Common Use Cases and Queries

Typical scenarios include reconciling WIP accounting lines to XLA events, validating accounted versus entered amounts, and troubleshooting WIP accounting event generation. Because the view depends on the XLA events global temporary table, queries are usually executed within the session context of the accounting program that populated it.

To list WIP accounting lines for a specific event:

• SELECT event_id, line_number, accounting_line_type_code, code_combination_id, accounted_amount, entered_amount FROM cst_xla_wip_lines_v WHERE event_id = :p_event_id ORDER BY line_number;

To summarize accounted amounts by ledger and cost element:

• SELECT ledger_id, cost_element_id, SUM(accounted_amount) FROM cst_xla_wip_lines_v GROUP BY ledger_id, cost_element_id;

To inspect distribution-level detail for a WIP entity:

• SELECT line_wip_entity_id, distribution_identifier, accounting_line_type_code, accounted_amount FROM cst_xla_wip_lines_v WHERE line_wip_entity_id = :p_wip_entity_id;

These examples reflect the documented column set and join semantics of the view. Custom code should account for the fact that some columns, such as TRANSACTION_VALUE in the base table, may be null, which is why ENTERED_AMOUNT falls back to the base transaction value.