Search Results wip_comp_issue

Overview

APPS.CST_XLA_INV_HEADERS_V is a Cost Management (CST) view that exposes inventory transaction header information in the structure required by the Subledger Accounting (XLA) engine. It supplies the accounting-relevant attributes that XLA uses to create and derive accounting entries for inventory and Cost Group (CG) transfer events routed through the Create Accounting process.

In the context of the search term cost_group_accounting, this view is significant because it explicitly resolves cost group identifiers for both sides of an inventory movement. The view uses DECODE expressions on XEG.SOURCE_ID_INT_2 against MMT.ORGANIZATION_ID to determine whether the event's organization corresponds to the "from" or "to" side of a transfer, and then emits the appropriate cost group. When the source organization matches the transaction organization, the view returns MMT.COST_GROUP_ID (the issued-from cost group); otherwise it returns MMT.TRANSFER_COST_GROUP_ID (the received-into cost group). This dual resolution is the mechanism by which Cost Group transfer accounting obtains correct cost group attribution, including the case—noted in the view's inline comment—where the from and to organizations are the same in Process Manufacturing.

Underlying Base Objects

The documented base objects referenced by the view are:

• XLA_EVENTS_GT (synonym) — aliased as XEG; supplies the accounting event identifier, ledger, event type code, and source identifiers driving the DECODE logic.
• MTL_MATERIAL_TRANSACTIONS (synonym) — aliased as MMT; the transaction-level source of item, quantity, organization, subinventory, locator, and cost group attributes.
• MTL_PARAMETERS (synonym) — organization parameter context used in the view's joins and filters.
• WSH_SHIPPING_PARAMETERS (synonym) — shipping parameter context used for transfer/receiving scenarios.
• CSTPSCHK (package) — Cost Management package referenced in the view definition for validation/lookup logic.

The view joins these objects so that each XLA event produced from material transactions is presented with a consistent, header-level attribute set. The cardinality(xeg,1) hint reflects the join assumption that one event row drives each header output row.

Key Columns

• EVENT_ID — XLA event identifier; primary join key to the accounting event.
• H_LEDGER_ID — ledger under which the event is accounted.
• DISTRIBUTION_TYPE — literal 'MTL_TRANSACTION_ACCOUNTS', identifying the transaction accounting distribution type.
• TRANSACTION_ID — material transaction identifier.
• TRANSACTION_TYPE_ID, TRANSACTION_SOURCE_TYPE_ID, TRANSACTION_ACTION_ID — transaction classification, overridden for Cost Group transfers (CG_TXFR) to type 86, source 13, action 55.
• PRIMARY_QUANTITY, INVENTORY_ITEM_ID, REVISION — item and quantity attributes.
• ORGANIZATION_ID and TRANSFER_ORGANIZATION_ID — from and to organizations, resolved via the SOURCE_ID_INT_2 DECODE.
• H_COST_GROUP_ID and H_TRANSFER_COST_GROUP_ID — from and to cost groups, the core columns for cost group accounting.
• H_SUBINVENTORY_CODE, H_TRANSFER_SUBINVENTORY, H_LOCATOR_ID, H_TRANSFER_LOCATOR_ID — from/to subinventory and locator pairs.

Common Use Cases and Queries

Typical uses include reconstructing accounting headers for inventory events, validating from/to cost group mapping on transfers, and diagnosing cost group accounting discrepancies.

• Retrieve header detail for a given event:
  SELECT event_id, transaction_id, organization_id, transfer_organization_id, h_cost_group_id, h_transfer_cost_group_id FROM apps.cst_xla_inv_headers_v WHERE event_id = :p_event_id;
• Find Cost Group transfer events with mismatched cost groups:
  SELECT transaction_id, h_cost_group_id, h_transfer_cost_group_id FROM apps.cst_xla_inv_headers_v WHERE distribution_type = 'MTL_TRANSACTION_ACCOUNTS' AND h_cost_group_id <> h_transfer_cost_group_id;
• Join to XLA event/distribution data to audit generated entries for CG transfer events by event_id and ledger.

Because the view assumes one event row per output (per the cardinality hint), queries should always constrain by EVENT_ID or TRANSACTION_ID to avoid Cartesian-like expansion when joined to event granularity tables.