Search Results reason_context_code

Overview

The CST_XLA_TXN_REASON_REF_V view is an Oracle E-Business Suite (EBS) dictionary object owned by the APPS schema. It belongs to the Bills of Material (BOM) product family, though its underlying data is drawn from Oracle Inventory's transaction reason infrastructure and is heavily consumed by the Cost Management and Subledger Accounting (XLA) layers. In both EBS 12.1.1 and 12.2.2 the object remains a simple, valid view with a status of VALID.

The view exposes transaction reason reference data — reason identifiers, names, descriptions, reason type codes, and their user-facing display values — in a denormalized, XLA-readable form. Its primary role is to provide Subledger Accounting, Cost Management reporting, and integration components with a stable, column-renamed projection of the transaction reason master so that downstream accounting events can be linked to the reason that justified a material transaction. Because the view is defined with a straightforward SELECT and no aggregation or joins, it is lightweight and safely queryable for reporting, extracts, and inbound/outbound interfaces.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, the view is defined over a single referenced base object: the synonym MTL_TRANSACTION_REASONS, which resolves to MTL_TRANSACTION_REASONS in the Oracle Inventory schema. The view performs no joins and no filtering; it is a pure column-aliasing projection. Each row in the base table maps to exactly one row in the view.

Because the view inherits the base table's multi-organization characteristics, reason records are typically scoped to an inventory organization (or defined globally, depending on the record). The view text confirms the projection pattern: REASON_ID is aliased to TRANSACTION_REASON_ID, REASON_NAME to TRANSACTION_REASON_NAME, and REASON_TYPE_DISPLAY to TXN_REASON_TYPE_DISPLAY, with the fifteen descriptive flexfield ATTRIBUTE columns renamed accordingly.

Key Columns

• TRANSACTION_REASON_ID — Primary key from REASON_ID; the unique surrogate identifier for the reason.
• TRANSACTION_REASON_NAME — The reason name (REASON_NAME); the value most frequently surfaced to users.
• TXN_REASON_DESCRIPTION — Free-text description (DESCRIPTION) of the reason.
• TXN_REASON_TYPE — The internal reason type code (REASON_TYPE).
• TXN_REASON_TYPE_DISPLAY — The user-facing display value for the reason type (REASON_TYPE_DISPLAY); this is the column associated with the search term reason_type_display.
• TXN_REASON_CONTEXT_CODE — The descriptive flexfield context (REASON_CONTEXT_CODE) governing the attribute columns.
• TXN_REASON_ATTRIBUTE_CATEGORY and TXN_REASON_ATTRIBUTE1–15 — The DFF context and attribute segments (ATTRIBUTE_CATEGORY and ATTRIBUTE1…ATTRIBUTE15) carried through from the base table.

Common Use Cases and Queries

Typical scenarios include resolving a reason ID to its display name during cost or accounting reconciliation, validating reason codes in interfaces, and extracting the full reason reference set for a reporting feed. The TXN_REASON_TYPE_DISPLAY column is particularly useful when users require the translated or descriptive type rather than the internal code.

Example retrieval of all active reasons:

• SELECT TRANSACTION_REASON_ID, TRANSACTION_REASON_NAME, TXN_REASON_TYPE, TXN_REASON_TYPE_DISPLAY FROM CST_XLA_TXN_REASON_REF_V;

Example lookup by display type with DFF context:

• SELECT TRANSACTION_REASON_ID, TRANSACTION_REASON_NAME, TXN_REASON_CONTEXT_CODE FROM CST_XLA_TXN_REASON_REF_V WHERE TXN_REASON_TYPE_DISPLAY = :p_type;

Because the view is a direct projection, it should be queried with the same organizational awareness applied to MTL_TRANSACTION_REASONS, and its results joined to inventory or accounting transaction tables via TRANSACTION_REASON_ID.