Results for “net_tax”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GML_GPOAO_DETAILS_V is a dictionary view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the GML — Process Manufacturing Logistics product family. Its documented description is "Sales Order Detail view," and it serves as a consolidated read interface over Process Manufacturing sales order data. Rather than exposing the raw OP_ORDR_DTL and OP_ORDR_HDR tables directly, the view joins header, line, status, item, warehouse, customer, address, and pricing reference objects into a single denormalized result set suitable for reporting, concurrent programs, and external integrations.

The view is marked VALID in the ETRM 12.2.2 metadata and mirrors the APPS.GML_GPOAO_DETAILS_V definition in the 12.1.1 documentation. Because it is an APPS-owned view rather than a base table, consumers can query it with standard privileges granted to the APPS schema and rely on EBS patching to maintain its definition.

Underlying Base Objects

The documented referenced objects are:

• OP_ORDR_HDR (SYNONYM) — sales order header, providing ORDER_ID.
• OP_ORDR_DTL (SYNONYM) — sales order lines, source of LINE_ID, LINE_NO, ship dates, hold information, and the ATTRIBUTE1–30 SO_DETAIL_* columns.
• OP_ORDR_STS (SYNONYM) — order status code used for LINE_STATUS_CODE.
• OP_PRCE_CDS (SYNONYM) — price code / pricing reference, relevant to base_price resolution.
• OP_CUST_MST (SYNONYM) — customer master.
• OP_GNRC_ITM, IC_ITEM_MST (SYNONYMS) — generic and item master data.
• IC_WHSE_MST (SYNONYM) — warehouse master.
• SY_ADDR_MST (SYNONYM) — address master.
• ECE_TP_HEADERS, ECE_TP_HEADERS/ECE_TP_DETAILS and GML_EC_CONTACT_V (VIEW) — trading partner header/detail and contact view used for export/EDI context.
• FND_PROFILE (PACKAGE) and OP_CUST_MST/OP_PRCE_CDS — supporting profile and pricing lookups.

The view text confirms a primary join between OH (headers) and OD (details) on ORDER_ID, with lookup joins to OS for status code. The remaining base objects supply descriptive attributes.

Key Columns

• ORDER_ID, LINE_ID, SO_LINE_NO — header/line identifiers.
• LINE_STATUS, LINE_STATUS_CODE, SHIP_STATUS — line-level state indicators.
• CREATION_DATE, LAST_UPDATE_DATE, EXPORTED_DATE, HOLD_EXPIRATION — lifecycle timestamps.
• ACTUAL_SHIPDATE, REQUESTED_SHIPDATE, PROMISED_SHIPDATE, SCHED_SHIPDATE, ACTUAL_DLVDATE, REQUIRED_DLVDATE — shipping and delivery scheduling.
• TRANS_CNT — transaction count for the line.
• SHIP_METHOD_INT, BASE_CURRENCY_INT, BILLING_CURRENCY — logistics and currency context. BASE_CURRENCY_INT is the closest documented analogue to a base_price currency basis.
• SO_DETAIL_CATEGORY, SO_DETAIL_ATTRIBUTE1–30 — the DFF (descriptive flexfield) columns from OP_ORDR_DTL, mapped as OD.ATTRIBUTE1–30.
• LINE_COMMENT — free-form line note.

Notably, no column named BASE_PRICE appears in the documented view text. Users searching for "base_price" should map the requirement onto BASE_CURRENCY_INT, the OP_PRCE_CDS price code reference, or a DFF attribute column depending on their implementation.

Common Use Cases and Queries

Typical uses include extract programs, order-detail reports, and EDI/export feeds that require joined header and line data.

• Order line extract for a customer: SELECT ORDER_ID, LINE_ID, SO_LINE_NO, LINE_STATUS_CODE, PROMISED_SHIPDATE, BASE_CURRENCY_INT FROM APPS.GML_GPOAO_DETAILS_V WHERE ORDER_ID = :p_order_id;
• Open lines pending shipment: SELECT ORDER_ID, SO_LINE_NO, SHIP_STATUS, REQUESTED_SHIPDATE FROM APPS.GML_GPOAO_DETAILS_V WHERE SHIP_STATUS = 'READY';
• Locating price-related context via DFF: SELECT ORDER_ID, SO_LINE_NO, SO_DETAIL_ATTRIBUTE1 FROM APPS.GML_GPOAO_DETAILS_V WHERE SO_DETAIL_ATTRIBUTE1 IS NOT NULL;
• Export audit: SELECT ORDER_ID, LINE_ID, EXPORTED_DATE FROM APPS.GML_GPOAO_DETAILS_V WHERE EXPORTED_DATE IS NOT NULL;

Because the view is not indexed directly, restrict predicates to the underlying OP_ORDR_HDR/OP_ORDR_DTL keys (ORDER_ID, LINE_ID) to benefit from base-table indexes in both 12.1.1 and 12.2.2.