Results for “transaction_attribute_category”

34 results




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

Overview

CST_XLA_WIP_HEADERS_V is an APPS-owned database view that consolidates Work in Process (WIP) transaction accounting data into a Subledger Accounting (XLA) header format. Its name reflects its dual heritage: the CST prefix identifies it as a Cost Management object, the XLA infix indicates it feeds Oracle Subledger Accounting event and journal-line processing, and the WIP_HEADERS suffix denotes its role as the header-level driver for WIP transaction distributions. Within Oracle EBS 12.1.1 and 12.2.2 it is used primarily by the Cost Management and Bills of Material modules to supply the Create Accounting process with transaction attributes required to derive accounting entries for WIP issues, completions, resource charges, overhead applications, and move transactions.

The view transforms raw WIP transaction records into a structure that pairs each accounting event with the distribution context needed for SLA rule evaluation. It is not an end-user data-entry object; rather it is an internal integration view consumed by costing and accounting programs, and by developers building extracts against WIP accounting data.

Underlying Base Objects

The ETRM metadata for 12.2.2 documents the following referenced base objects:

  • WIP_TRANSACTIONS (synonym) — the primary source of transaction rows, including transaction quantities, rates, entity references, and resource details.
  • XLA_EVENTS_GT (synonym) — the global temporary table holding XLA event identifiers and event headers used to bind each WIP transaction to its accounting event.
  • CST_DEPARTMENT_OVERHEADS (synonym) — supplies departmental overhead definitions used to resolve activity identifiers for overhead-basis transactions.
  • MTL_PARAMETERS (synonym) — provides organization-level cost and accounting parameters such as currency context.
  • GL_LEDGERS (synonym) — supplies ledger currency information, used in the NVL and DECODE logic that reconciles transaction currency against ledger currency.

The view text shows an inline skeleton that aggregates these sources, with the outer query mapping the consolidated inline result to the WIP_TRANSACTION_ACCOUNTS distribution type. Currency conversion columns are derived with DECODE logic comparing WT.CURRENCY_CODE to GL.CURRENCY_CODE to suppress redundant conversion rates when the transaction is already in ledger currency.

Key Columns

Common Use Cases and Queries

Typical uses include auditing WIP accounting events, diagnosing why a resource charge used a standard versus actual rate, and validating currency conversion on WIP distributions.

Retrieve standard-rate resource transactions for an organization:

SELECT EVENT_ID, TRANSACTION_ID, ORGANIZATION_ID,
       RESOURCE_ID, STANDARD_RATE_FLAG,
       STANDARD_RESOURCE_RATE, ACTUAL_RESOURCE_RATE,
       TRANSACTION_QUANTITY
FROM   APPS.CST_XLA_WIP_HEADERS_V
WHERE  ORGANIZATION_ID = :org_id
AND    STANDARD_RATE_FLAG = 'Y';

Join to WIP entity context for accounting analysis:

SELECT V.EVENT_ID, V.WIP_ENTITY_ID, V.TRANSACTION_DATE,
       V.CURRENCY_CODE, V.CURRENCY_CONVERSION_RATE
FROM   APPS.CST_XLA_WIP_HEADERS_V V
WHERE  V.TRANSACTION_DATE BETWEEN :from_date AND :to_date;

Because the view exposes project and DFF attribute columns, it is also used in custom SLA rule validation and reconciliation reports against XLA_AE_HEADERS. Query performance depends on WIP_TRANSACTIONS indexes and on the XLA_EVENTS_GT population preceding invocation.