Search Results reason_context_code

Overview

The GMF_XLA_TXN_REASONS_V view is a reporting and integration object owned by the APPS schema in Oracle E-Business Suite, delivered under the GMF — Process Manufacturing Financials product family. It exposes inventory transaction reason codes in a denormalized, subledger-friendly shape intended to serve as an Application Data Repository (ADR) source for Subledger Accounting (SLA) and related reporting flows. In release 12.1.1 and 12.2.2, SLA uses ADR sources to surface descriptive and transactional attributes into accounting event models, journal line definitions, and supporting references. This view provides a single, stable interface for those reason-based attributes rather than requiring consumers to query the underlying inventory table directly.

A practical benefit of the view is naming normalization. The base table columns such as REASON_NAME and REASON_TYPE are aliased with a TXN_REASON_ prefix (for example, TXN_REASON_NAME and TXN_REASON_TYPE), making it unambiguous in ADR contexts where multiple reason-like sources may coexist. The view is marked VALID and is documented for ETRM 12.2.2.

Underlying Base Objects

The view is defined over a single referenced base object, MTL_TRANSACTION_REASONS, which is exposed to the APPS schema as a synonym. The definition is a straightforward projection: every column is selected directly from the base table, with only the column aliases changed. No joins, filters, or DISTINCT operations are applied, so the view is effectively a renaming layer over the base table and preserves its row cardinality exactly.

Because there is no aggregation or restriction, the view inherits all data characteristics of MTL_TRANSACTION_REASONS, including its setup-driven content, its context-sensitive descriptive flexfield attributes, and its dependence on the underlying inventory reason code configuration. Any change to the base table row is immediately visible through the view.

Key Columns

• REASON_ID — Primary identifier of the transaction reason. Retains its original name and joins back to the base table.
• TXN_REASON_NAME — Aliased from REASON_NAME; the user-visible reason code name presented to SLA.
• TXN_REASON_DESCRIPTION — Aliased from DESCRIPTION; free-text description of the reason.
• TXN_REASON_TYPE — Aliased from REASON_TYPE; the internal reason type value.
• TXN_REASON_TYPE_DISPLAY — Aliased from REASON_TYPE_DISPLAY; the display form of the reason type and the column most commonly sought by users searching for reason_type_display. It presents the human-readable reason type rather than the coded value.
• TXN_REASON_CONTEXT_CODE — Aliased from REASON_CONTEXT_CODE; the descriptive flexfield context governing the attribute columns.
• TXN_REASON_ATTRIBUTE_CATEGORY and TXN_REASON_ATTRIBUTE1 through TXN_REASON_ATTRIBUTE15 — Aliased from ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15; the descriptive flexfield segments for the reason code.

Common Use Cases and Queries

The view is typically used to resolve a REASON_ID from an inventory transaction into its descriptive reason details for SLA event enrichment, journal line descriptions, or custom reporting. A representative query retrieving reason detail including the display type is:

• SELECT reason_id, txn_reason_name, txn_reason_description, txn_reason_type, txn_reason_type_display FROM apps.gmf_xla_txn_reasons_v WHERE reason_id = :p_reason_id;
• Filtering by flexfield context: SELECT reason_id, txn_reason_name, txn_reason_type_display FROM apps.gmf_xla_txn_reasons_v WHERE txn_reason_context_code = :p_context;
• Listing distinct display types for reporting: SELECT DISTINCT txn_reason_type_display FROM apps.gmf_xla_txn_reasons_v ORDER BY 1;
• Joining to SLA or inventory transaction data on reason_id to append reason descriptions and flexfield attributes to accounting extracts.

Because the view performs no transformation beyond aliasing, queries against it return the same rows as MTL_TRANSACTION_REASONS, and standard inventory reason code query performance characteristics apply.