Results for “order_date”

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

Overview

OP_ORDR_HDR is the sales order header table in the Process Manufacturing Logistics (GML) module of Oracle E-Business Suite, residing in the GML schema and marked VALID in the ETRM 12.2.2 catalog. It serves as the master record for every process manufacturing sales order, capturing order-level attributes such as the ordering organization, customer identities, ship-to address, pricing currency, warehousing, transportation, and lifecycle status. Each order is identified by a surrogate primary key, ORDER_ID, and a single row represents one order/release combination.

From a dimensional modeling perspective, the metadata's heuristic Data Vault classification is satellite-leaning. This suggests OP_ORDR_HDR functions well as a descriptive satellite attached to a business key hub, with the natural business key expressed through the unique index OP_ORDR_HDR_U1. Because headers change over time, a raw vault design would typically model the header as one or more satellites keyed on the U1 columns.

Key Information Stored

With 90 columns, OP_ORDR_HDR is wide, but the most operationally significant fields cluster into identification, customer, logistics, status, and audit categories.

• ORDER_ID — surrogate primary key (OP_ORDR_HDR_PK); the FK target for all dependent detail tables.
• ORDER_TYPE, ORGN_CODE, ORDER_NO, RELEASE_NO — the business-key composite defined by unique index OP_ORDR_HDR_U1.
• BILLCUST_ID, SHIPCUST_ID, SOLDTOCUST_ID, ULTIMATE_SHIPCUST_ID, CONSIGNEE_ID — the customer role references into OP_CUST_MST.
• SHIPADDR_ID — ship-to address (SY_ADDR_MST); CONTACT_ID — customer contact (OP_CUST_CON).
• ORDER_STATUS — status code from OP_ORDR_STS_B; ORDER_DATE, REQUESTED_SHIPDATE, PROMISED_SHIPDATE, SCHED_SHIPDATE, REQUIRED_DLVDATE — scheduling dates.
• FROM_WHSE, TO_WHSE — warehouse endpoints (IC_WHSE_MST); SHIPPER_CODE, SHIP_MTHD — carrier and shipping method.
• TERMS_CODE, BILLING_CURRENCY, LOCKBOX_CODE, FOB_CODE — commercial terms.
• TOTAL_OPEN_AMOUNT — open value; COMPLETED_IND, DELETE_MARK, IN_USE — lifecycle flags.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — standard audit columns.

Common Use Cases and Queries

Typical reporting includes open-order backlogs, shipment scheduling, and customer-facing order status inquiries. The U1 index supports efficient lookup by business key:

• SELECT ORDER_ID, ORDER_NO, RELEASE_NO FROM GML.OP_ORDR_HDR WHERE ORDER_TYPE = :p_type AND ORGN_CODE = :p_org AND ORDER_NO = :p_no;
• Backlog: filter on ORDER_STATUS and COMPLETED_IND, joining OP_ORDR_DTL for line detail.
• Scheduling: query REQUESTED_SHIPDATE, PROMISED_SHIPDATE and SCHED_SHIPDATE ranges by ORGN_CODE.
• Customer view: join BILLCUST_ID and SHIPCUST_ID to OP_CUST_MST for names and addresses.
• Change auditing: join ORDER_ID to OP_ORDR_CHG or OP_AUDT_MST to trace modifications.

Related Objects

OP_ORDR_HDR sits at the center of the OPM order model. The most significant relationships are:

• OP_ORDR_DTL.ORDER_ID — order lines; the primary child table.
• OP_ORDR_CHG.ORDER_ID — header change history.
• OP_AUDT_MST.ORDER_ID — audit trail records.
• OP_CUST_MST — joined via BILLCUST_ID, SHIPCUST_ID, SOLDTOCUST_ID, ULTIMATE_SHIPCUST_ID, CONSIGNEE_ID.
• OP_ORDR_STS_B.ORDER_STATUS and OP_ORDR_TYP_B.ORDER_TYPE — code validations.
• IC_WHSE_MST via FROM_WHSE and TO_WHSE; SY_ORGN_MST via ORGN_CODE; SY_ADDR_MST via SHIPADDR_ID.
• OP_TERM_MST, OP_SHIP_MTH, OP_SLSR_MST, OP_PRSL_HDR — terms, shipping, salesrep, and pre-sales references.