Results for “transfer_type”

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

Overview

The CST_XLA_INV_EVENT_MAP table is a mapping table owned by the BOM schema in Oracle E-Business Suite. Its purpose is to associate material transactions with their corresponding Subledger Accounting (SLA/XLA) event types. In EBS Release 12, inventory and cost management transactions are accounted for through the Subledger Accounting engine rather than directly writing to the General Ledger. For each qualifying material transaction, XLA must determine which event class and event type to apply so that the correct accounting lines are generated. CST_XLA_INV_EVENT_MAP provides the lookup mechanism that translates the characteristics of a material transaction — its source, its action, and various transfer and organizational attributes — into a specific event class and event type.

From a modeling perspective, the heuristic Data Vault classification supplied in the metadata is standalone, meaning the table is not strongly integrated into a broader hub-and-link web via foreign key relationships and can be treated independently. The single documented foreign key, on TRANSACTION_SOURCE_TYPE_ID referencing MTL_TXN_SOURCE_TYPES, is the only outward dependency captured. This classification should be regarded as a suggestion rather than a definitive model, since the table functions principally as a reference or lookup set consumed during the event-mapping process.

Key Information Stored

The table comprises ten documented columns, which together act as a composite business key rather than a single surrogate identifier. The most operationally significant columns are:

• EVENT_CLASS_CODE — identifies the accounting event class (for example, inventory or cost management) that the mapped transaction belongs to.
• EVENT_TYPE_CODE — the specific accounting event type applied to the transaction within its event class.
• TRANSACTION_SOURCE_TYPE_ID — the source of the material transaction; this is the documented foreign key to MTL_TXN_SOURCE_TYPES.
• TRANSACTION_ACTION_ID — the action performed on the transaction (for example, issue, receipt, or transfer).
• ORGANIZATION — the inventory organization context under which the mapping applies.
• TRANSFER_TYPE — distinguishes transfer scenarios, which frequently drive different accounting treatment.
• FOB_POINT — the free-on-board point governing transfer of ownership and thus the timing of accounting recognition.
• TP — a transfer pricing indicator used to select the correct event mapping for inter-organization movements.
• ATTRIBUTE — a flexible discriminator allowing additional transaction characteristics to participate in the mapping.
• ZD_EDITION_NAME — the editioning column associated with the EBS editioning model in Release 12.2.

No single-column surrogate primary key is documented. Instead, the unique index CST_XLA_INV_EVENT_MAP_U1 defines the business key as the combination of 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 guarantees that any given combination of transaction characteristics resolves deterministically to one event class and event type.

Common Use Cases and Queries

The primary use case is diagnostic: when a material transaction is not creating the expected accounting entries, consultants inspect this table to confirm whether a mapping row exists for the relevant combination of source, action, organization, and transfer attributes.

SELECT event_class_code, event_type_code
FROM   cst_xla_inv_event_map
WHERE  transaction_source_type_id = :source_id
AND    transaction_action_id      = :action_id
AND    organization              = :org_id;

Reporting scenarios include auditing the completeness of the mapping configuration, comparing mappings across organizations, and identifying which event types are reachable for a given transfer type, FOB point, or transfer pricing flag. A join to MTL_TXN_SOURCE_TYPES enriches the output with a readable source type name:

SELECT m.event_class_code, m.event_type_code, s.transaction_source_type_name
FROM   cst_xla_inv_event_map m,
       mtl_txn_source_types   s
WHERE  m.transaction_source_type_id = s.transaction_source_type_id;

Related Objects

The following objects are most significant in relation to this table:

• MTL_TXN_SOURCE_TYPES — referenced through TRANSACTION_SOURCE_TYPE_ID; supplies the descriptive name of each transaction source.
• MTL_MATERIAL_TRANSACTIONS — the principal source of material transactions whose characteristics are matched against this mapping.
• MTL_TRANSACTION_TYPES — defines transaction action and type context used in the mapping criteria.
• XLA_EVENTS — the Subledger Accounting events ultimately generated after mapping resolution.
• XLA_EVENT_TYPES — the event type definitions referenced by EVENT_TYPE_CODE.
• XLA_EVENT_CLASSES — the event class definitions referenced by EVENT_CLASS_CODE.
• CST_TRANSACTION_COST_DETAILS — provides cost detail context that accompanies inventory accounting.

Because the mapping governs which accounting events are created for inventory activity, errors or omissions here directly affect the accuracy of inventory and cost subledger entries posted to the General Ledger.