Search Results cst_xla_inv_event_map_u1

Overview

CST_XLA_INV_EVENT_MAP is a reference table owned by the BOM schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is a core component of the Subledger Accounting (SLA) engine and is consulted when material transactions are processed. The table acts as a lookup that resolves which Subledger Accounting event class and event type should be assigned to a given inventory transaction, based on a combination of attributes derived from the source transaction.

The mapping logic accounts for transaction action, transaction source type, FOB point, organization context, transfer pricing flag, and transfer type. An additional ATTRIBUTE column distinguishes special situations, such as an implicit cost group transfer occurring during a common issue to Work in Process (CITW) versus a regular inventory issue. The table resides in the APPS_TS_SEED tablespace, confirming its role as seeded reference data rather than transactional data.

From a Data Vault modeling perspective, the mined metadata classifies this object as standalone. This heuristic suggests the table behaves as a reference or lookup structure with no dependent child tables inside the documented relationship set. It could reasonably be modeled as a hub-like reference entity keyed by its composite business key, with descriptive SLA classification attributes attached directly to it, since it carries no foreign-key dependencies on transactional parents beyond the source type lookup.

Key Information Stored

The table exposes ten documented columns. The most significant for querying and interpretation are:

• TRANSACTION_ACTION_ID — The transaction action identifier inherited from MTL_MATERIAL_TRANSACTIONS, indicating the action performed (for example, issue, receipt, or transfer).
• TRANSACTION_SOURCE_TYPE_ID — The source type identifier from MTL_TRANSACTION_ACCOUNTS, identifying the originating transaction category.
• EVENT_CLASS_CODE — The SLA event class assigned to the resolved transaction.
• EVENT_TYPE_CODE — The SLA event type assigned to the resolved transaction.
• ATTRIBUTE — Differentiates special cases such as common issue to WIP versus a regular inventory issue, and variance transfers.
• FOB_POINT — The FOB point value from MTL_MATERIAL_TRANSACTIONS used to qualify the mapping.
• ORGANIZATION — Indicates whether the organization or the transfer organization of the corresponding MMT transaction should be used.
• TRANSFER_TYPE — Holds either SHIP or RCPT, qualifying inter-organization shipment or receipt lines.
• TP — Holds Y or N based on the CST: Transfer Price Option profile value.
• ZD_EDITION_NAME — The edition name supporting the Oracle EBS editioning/ZD schema construct.

The documented surrogate-style business key is the unique index CST_XLA_INV_EVENT_MAP_U1, defined over EVENT_CLASS_CODE, EVENT_TYPE_CODE, TRANSACTION_SOURCE_TYPE_ID, TRANSACTION_ACTION_ID, ORGANIZATION, TRANSFER_TYPE, FOB_POINT, TP, ATTRIBUTE, and ZD_EDITION_NAME. This composite uniqueness confirms that no surrogate single-column primary key is documented; the business identity is the full attribute combination.

Common Use Cases and Queries

The primary use case is diagnostic and configuration verification: determining why a particular material transaction was assigned a specific SLA event class and event type. Support and implementation teams query this table to trace SLA event resolution, to validate seeded mappings after an upgrade, or to audit custom mappings created for specific transfer types.

A representative query resolves the event class and type for a given action and source:

• SELECT event_class_code, event_type_code, attribute FROM cst_xla_inv_event_map WHERE transaction_action_id = :action_id AND transaction_source_type_id = :source_type_id AND transfer_type = :ship_or_rcpt;

Reporting scenarios include listing all mapped combinations for a given event class, examining which actions map to a CITW attribute, and confirming whether transfer pricing (TP = Y) changes the resolved event type. Because the table is seeded reference data, such reports are typically read-only and used for reconciliation against SLA event records.

Related Objects

The documented foreign-key relationship links TRANSACTION_SOURCE_TYPE_ID to MTL_TXN_SOURCE_TYPES, establishing the source-type reference chain. The broader dependent object set includes:

• MTL_TXN_SOURCE_TYPES — referenced via TRANSACTION_SOURCE_TYPE_ID, supplying the valid transaction source type definitions.
• MTL_MATERIAL_TRANSACTIONS — the originating transaction table supplying TRANSACTION_ACTION_ID and FOB_POINT values used to qualify mappings.
• MTL_TRANSACTION_ACCOUNTS — supplies TRANSACTION_SOURCE_TYPE_ID for accounting-line resolution.
• XLA_EVENTS / XLA_ACCOUNTING_EVENTS — the SLA event repository where resolved event classes and types are ultimately recorded.
• CST_TRANSACTION_COST_DETAILS — the cost detail table linked to the same inventory transactions that drive SLA event creation.

Together these objects form the inventory-to-SLA processing chain in which CST_XLA_INV_EVENT_MAP supplies the critical resolution logic.