Search Results order_status_code

Overview

The GMF_XLA_SO_TXNS_V view, owned by the APPS schema in Oracle E-Business Suite, is a Process Manufacturing Financials (GMF) reporting object that presents Subledger Accounting (XLA) transaction data originating from sales order and internal order inventory movements. Its name reflects its purpose: it surfaces GMF-related XLA Sales Order transactions in a flattened, human-readable form suitable for reconciliation, audit, and custom reporting. The view is a UNION ALL query, combining at least two logical branches — one for standard sales order issues and intransit shipments, and additional branches for RMA transactions and logical/RMA receipts sourced from the XLA pre-processor. It is defined as VALID and is exposed to reporting and integration consumers that need to join accounting event data to inventory, order, item, and party master information without constructing the underlying multi-table joins themselves.

Underlying Base Objects

The view is defined over a union of extracts from several base objects. The driving table is GMF_XLA_EXTRACT_HEADERS (EH), which holds the accounting event header rows written by the Subledger Accounting extract process. It is joined to OE_ORDER_HEADERS_ALL (OH) and OE_ORDER_LINES_ALL (OL) for sales order header and line attributes, and to MTL_MATERIAL_TRANSACTIONS (MMT) for the inventory transaction itself, joined on TRANSACTION_ID, TRX_SOURCE_LINE_ID, ORGANIZATION_ID, and INVENTORY_ITEM_ID. MTL_TRANSACTION_LOT_NUMBERS (MTLN) is outer-joined to supply lot information. MTL_SYSTEM_ITEMS_B (via the _KFV key flexfield view) provides item number and description, MTL_PARAMETERS supplies the inventory organization code, XLE_ENTITY_PROFILES provides the legal entity, and HZ_PARTIES is outer-joined for customer number and name. The RMA branch additionally references RCV_TRANSACTIONS. The documented 12.2.2 base object list confirms these relationships, including the substitution of MTL_SYSTEM_ITEMS_B_KFV for the item flexfield view.

Key Columns

• LEGAL_ENTITY_ID / LEGAL_ENTITY_NAME — The legal entity responsible for the transaction, sourced from XLE_ENTITY_PROFILES. LEGAL_ENTITY_NAME is the human-readable name users typically search for.
• LEDGER_ID, TRANSACTION_ID, REFERENCE_NO — Accounting ledger, XLA transaction identifier, and the reference number identifying the event.
• EVENT_CLASS_CODE, TRANSACTION_DATE, OPERATING_UNIT — Classification and timing attributes of the accounting event.
• ITEM_NUMBER, ITEM_DESCRIPTION, INVENTORY_ITEM_ID — Item identification from the system items key flexfield view.
• ORDER_NUMBER, ORDERED_DATE, ORDER_STATUS_CODE, ORDER_LINE_NUMBER, ORDER_LINE_STATUS, ORDERED_QUANTITY, UNIT_SELLING_PRICE — Sales order header and line context.
• CUSTOMER_NUMBER, CUSTOMER_NAME — Sold-to party details from HZ_PARTIES.
• PRIMARY_QUANTITY, TRANSACTION_UOM, PRIMARY_UOM_CODE, SECONDARY_UOM_CODE — Quantities and units of measure.
• LOT_NUMBER, SHIPMENT_NUMBER, ORGANIZATION_CODE — Inventory and shipment identifiers.

Common Use Cases and Queries

A frequent requirement is locating transactions by legal entity, which is the context in which LEGAL_ENTITY_NAME is most often queried. For example:

SELECT LEGAL_ENTITY_NAME, ORDER_NUMBER, ITEM_NUMBER, TRANSACTION_DATE, PRIMARY_QUANTITY FROM APPS.GMF_XLA_SO_TXNS_V WHERE LEGAL_ENTITY_NAME = :p_legal_entity AND TRANSACTION_DATE BETWEEN :p_from AND :p_to;

Other practical scenarios include reconciling XLA extract headers to inventory transactions for a given item and organization, reviewing sales order revenue-driving movements for audit, and joining the view back to GMF_XLA_EXTRACT_HEADERS on TRANSACTION_ID for detailed accounting line analysis. Because the view performs extensive joins across order, inventory, and party tables, queries should be filtered on indexed columns such as LEGAL_ENTITY_ID, ORDER_NUMBER, or TRANSACTION_DATE to control performance in high-volume environments.