Search Results order_line_status




Overview
Explore in AI Chat

Overview

APPS.GMF_XLA_SO_TXNS_V is a reporting view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that consolidates process manufacturing (OPM) transaction and order information for Subledger Accounting (XLA) purposes. The view joins extract header records from the GMF XLA extract process with order management, inventory, and customer master data to produce a denormalized result set suitable for accounting event analysis, reconciliation, and downstream integration. The "SO" in the name denotes Sales Order, and the "TXNS" denotes transactions, reflecting the view's focus on sales-order-related material movements that must be accounted for in the subledger. The presence of the column order_line_status — the term the user searched — indicates the view exposes the OE order line flow status, enabling report authors and accountants to filter, group, or reconcile by the state of the sales-order line at the time of the underlying transaction.

Underlying Base Objects

The view is constructed from a UNION of at least two SELECT statements. The documented base objects referenced by the view include:

  • GMF_XLA_EXTRACT_HEADERS (SYNONYM) — the driving table holding extract header records produced by the OPM XLA pre-processor.
  • OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL (SYNONYMs) — sales order header and line data, sourced via header_id/line_id.
  • MTL_MATERIAL_TRANSACTIONS (SYNONYM) — inventory material transactions providing shipment numbers and transaction linkage.
  • MTL_SYSTEM_ITEMS_B_KFV (VIEW) — the key flexfield value view supplying the item number (concatenated segments), description, and UOM codes.
  • MTL_PARAMETERS (SYNONYM) — the inventory organization definition supplying organization_code.
  • XLE_ENTITY_PROFILES (SYNONYM) — the legal entity profile providing the legal entity name.
  • HZ_PARTIES (SYNONYM) — the customer (sold-to) party used for party number and party name.
  • RCV_TRANSACTIONS (SYNONYM) — receiving transactions, referenced in the RMA / logical receipt portion of the UNION.

Because the extract header links to material transactions via transaction_id and source_line_id, the view is effectively a bridge between OPM subledger extract data and core EBS order management and inventory tables.

Key Columns

  • reference_no, ledger_id, transaction_id, event_class_code, operating_unit, transaction_date — identification and accounting context for the extract event.
  • primary_quantity (a concatenation of quantity and UOM), primary_uom_code, secondary_uom_code, transaction_uom — quantity and unit-of-measure information.
  • valuation_cost_type_id, valuation_cost_type — cost type context for valuation.
  • lot_number, source_document_id, source_line_id — lot tracking and document/line linkage.
  • legal_entity_id, legal_entity_name — legal entity identification.
  • inventory_item_id, item_number, item_description, organization_id, organization_code — item and organization context.
  • order_number, ordered_date, order_status_code, order_line_number, ordered_quantity, unit_selling_price, order_line_status — sales order header and line attributes; order_line_status reflects the OE order line flow status.
  • shipment_number — from MTL_MATERIAL_TRANSACTIONS.
  • customer_number, customer_name — from HZ_PARTIES, populated via an outer join (hz.party_id(+)) so transactions without a matching party are still returned.

Common Use Cases and Queries

Typical uses include subledger reconciliation, sales-order-to-shipment-to-invoice tie-out, and accounting event analysis by order line status. A sample query filtering on the searched column is shown below:

  • Reconcile shipped order lines by status: 
    SELECT order_number,
       order_line_number,
       order_line_status,
       item_number,
       primary_quantity,
       customer_name
FROM   apps.gmf_xla_so_txns_v
WHERE  order_line_status = 'CLOSED'
AND    transaction_date >= :from_date;
  • Group transaction quantities by order status: aggregate primary_quantity grouped by order_status_code and order_line_status for period-end reporting.
  • Legal entity and ledger analysis: filter by ledger_id and legal_entity_name to produce XLA extract summaries.
  • Customer-facing shipment reports: join output to additional reporting tables using customer_number and shipment_number.

Because the view is defined over OPM extract headers and restricts transaction_source_type_id to sales orders (2) and internal orders (8), and transaction_action_id to issue-from-stores (1) and in-transit shipment (21), queries against it return only accounting-relevant material movements, making it well suited to subledger reporting rather than general order-management inquiry.