Results for “tp_header_id”

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

Overview

GML_GPOAO_ORDERS_V is a database view owned by the APPS schema in Oracle E-Business Suite, defined within the GML (Process Manufacturing Logistics) product family. It is documented as a Sales Order Header view and is designed primarily to support outbound electronic data interchange (EDI) and trading partner communication. The view flattens the process manufacturing sales order header, its associated trading partner definition, and a broad set of descriptive attribute columns into a single denormalized result set suitable for consumption by EDI translation or integration processes.

Because the view is defined with a hardcoded literal 'EC' for COMMUNICATION_METHOD and '00' for DOCUMENT_PURPOSE_CODE, it is clearly oriented toward the "e-commerce" outbound mapping path, producing a fixed transaction envelope for sales order export. The object carries a VALID status and is exposed as APPS.GML_GPOAO_ORDERS_V for both 12.1.1 and 12.2.2 environments, though its base object dependencies are documented against the 12.2.2 ETRM metadata set.

Underlying Base Objects

The view is built over a mix of GML synonyms, ECE (e-commerce) objects, and shared process manufacturing master tables. The documented referenced base objects are:

• OP_ORDR_HDR — the process manufacturing sales order header; supplies ORDER_ID, ORDER_NO, ORGN_CODE, order dates, ports, FOB, shipper, shipping method, and status.
• OP_ORDR_STS — order status lookup; joined to derive ORDER_STATUS_CODE.
• ECE_TP_HEADERS and ECE_TP_DETAILS — trading partner header/detail definitions; these supply the TP_HEADER_ID, TP_DETAIL_ID, TP_CODE, and TP_REFERENCE columns that are central to the view's EDI purpose. The user's search term, tp_header_id, originates here.
• OP_CUST_MST, OP_PORT_MST (PRTM1/PRTM2), OP_FOBC_MST, OP_SHIP_MST, OP_FRGT_MTH, OP_SHIP_MTH, IC_WHSE_MST — descriptive master tables resolving codes into alphanumeric descriptions such as port descriptions, FOB names, shipper names, and freight billing descriptions.
• GML_EC_CONTACT_V — a companion contact view, and SY_ADDR_MST — address master data associated with the trading partner.
• FND_PROFILE — the standard EBS profile option package, used for runtime environment or organizational context.

The presence of both OP_ORDR_HDR and ECE_TP_HEADERS indicates the view joins the internal sales order to the external trading partner configuration, which is the standard GML-EDI mapping pattern.

Key Columns

• TP_HEADER_ID — the trading partner header identifier from ECE_TP_HEADERS; the driving foreign key for outbound EDI partner resolution and the column most frequently searched by developers.
• TP_DETAIL_ID, TP_CODE, TP_LOCATION_CODE_EXT — trading partner detail, code, and external location identifiers.
• DOCUMENT_ID, DOCUMENT_CODE, DOCUMENT_PURPOSE_CODE — the EDI document envelope; DOCUMENT_CODE maps to OH.ORDER_NO.
• ORDER_ID, ORDER_NO, ORGN_CODE, ORDER_DATE — the sales order identity and organization context.
• ORDER_STATUS, ORDER_STATUS_CODE — decoded and coded order status values.
• CUSTPO_NO, ORDER_COMMENT — customer reference and free-text comments.
• EMBARKATION_PORT / DEBARKATION_PORT (internal and description), FOB_CODE/FOB_NAME, SHIPPER_CODE/SHIPPER_NAME, FRTBILL_MTHD/FRTBILL_DESC — logistics routing attributes resolved to readable text.
• ATTRIBUTE_CATEGORY / ATTRIBUTE1..15 (both TP_HEADER_ and TP_DETAIL_ prefixed) — descriptive flexfield segments for the trading partner header and detail.
• TRANSACTION_DATE — a SYSDATE-derived column, so it always reflects query execution time.

Common Use Cases and Queries

Typical uses include troubleshooting outbound EDI sales order extracts, verifying that a trading partner is correctly linked to an order, and building custom interface queries for integration middleware. Because TRANSACTION_DATE is SYSDATE, consumers should not treat it as a stored business date.

To find all order-level EDI data for a specific trading partner:

SELECT tp_header_id, order_no, orgn_code, order_date,
       tp_code, document_code, order_status_code
FROM   apps.gml_gpoao_orders_v
WHERE  tp_header_id = :tp_header_id;

To list orders by organization and status:

SELECT order_no, custpo_no, order_status,
       embarkation_port_desc, debarkation_port_desc
FROM   apps.gml_gpoao_orders_v
WHERE  orgn_code = :orgn_code
AND    order_status_code = :status_code;

For shipment routing analysis, selecting FOB_NAME, SHIPPER_NAME, and FRTBILL_DESC alongside ORDER_NO provides a readable logistics view directly from the sales order header context.