Search Results transaction_reason_name




Overview
Explore in AI Chat

Overview

APPS.CST_XLA_TXN_REASON_REF_V is a reporting and integration view in the Oracle E-Business Suite Cost Management (CST) and Subledger Accounting (XLA) schema. It exposes the transaction reason reference data used throughout Oracle Inventory and Cost Management, presenting the contents of the MTL_TRANSACTION_REASONS table under a naming convention aligned with the XLA (eXtended Ledger Architecture) reference model. In Oracle EBS 12.1.1 and 12.2.2 the view is owned by APPS and is intended to supply transaction reason identifiers, names, types, and descriptive flexfield segments to subledger accounting definitions, reconciliation reports, and third-party integrations.

The defining characteristic of the view is its column aliasing. Source columns such as REASON_ID, REASON_NAME, and DESCRIPTION are re-projected with the TRANSACTION_ or TXN_ prefixes that XLA reference views use, so that consumers of the view can identify each attribute's accounting context without ambiguity. The column TRANSACTION_REASON_NAME, corresponding to the source REASON_NAME column, is the attribute most frequently queried by users searching for a transaction reason by its display name.

Underlying Base Objects

The view is defined over a single documented base object, MTL_TRANSACTION_REASONS, accessed through a synonym in the APPS schema. The definition performs no joins, unions, or aggregations: it is a straight projection of the base table's columns with aliases applied. Consequently, the view is not materialized, holds no data of its own, and inherits all referential and validation characteristics of the underlying table. Row multiplicity in MTL_TRANSACTION_REASONS is preserved exactly; the view does not filter by reason type, organization, or enabled/disabled status. Any change to the aliasing in a future patch could affect dependent custom code, so implementers should treat the view as a stable but patch-sensitive interface.

Key Columns

  • TRANSACTION_REASON_ID — the primary key of the transaction reason, sourced from REASON_ID. This is the value stored on inventory and cost transactions that reference a reason.
  • TRANSACTION_REASON_NAME — the user-visible reason name, sourced from REASON_NAME. This is the column most commonly used in lookup and reporting queries.
  • TXN_REASON_DESCRIPTION — the long description of the reason, sourced from DESCRIPTION.
  • TXN_REASON_TYPE and TXN_REASON_TYPE_DISPLAY — the internal reason type code and its translated display value, used to distinguish reason categories.
  • TXN_REASON_CONTEXT_CODE — the descriptive flexfield context associated with the reason record.
  • TXN_REASON_ATTRIBUTE_CATEGORY — the descriptive flexfield structure name.
  • TXN_REASON_ATTRIBUTE1 through TXN_REASON_ATTRIBUTE15 — the fifteen descriptive flexfield segment values, exposed verbatim with the TXN_REASON_ prefix.

Common Use Cases and Queries

The view is typically used to resolve a stored reason identifier into a readable name, to list all reasons available for a given transaction type, or to join reason data to inventory transactions and subledger accounting lines. A common pattern is to join the view to MTL_MATERIAL_TRANSACTIONS on TRANSACTION_REASON_ID to report the reason name against material movements.

A typical lookup by name is:

SELECT transaction_reason_id, transaction_reason_name, txn_reason_description, txn_reason_type
FROM apps.cst_xla_txn_reason_ref_v
WHERE transaction_reason_name = :p_reason_name;

To enumerate reasons by type:

SELECT transaction_reason_id, transaction_reason_name, txn_reason_type_display
FROM apps.cst_xla_txn_reason_ref_v
WHERE txn_reason_type = :p_reason_type
ORDER BY transaction_reason_name;

Because no organization filter exists on the view, reports requiring organization-specific behavior must apply that restriction from the referencing transaction table rather than from the view itself.