Search Results op_ordr_hdr

Overview

The OP_ORDR_HDR table is the central Sales Order Header table within the Process Manufacturing Logistics (GML) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It serves as the master record for a sales order, storing high-level transactional and administrative information that governs the entire order lifecycle. As a core transactional entity, it establishes the business context—such as customer, organization, currency, and terms—for all associated line items and subsequent fulfillment, shipping, and invoicing processes. Its integrity is maintained through a complex network of foreign key relationships to foundational master data tables across the EBS suite.

Key Information Stored

The table's primary key is ORDER_ID, a unique system-generated identifier. A critical composite unique key (OP_ORDR_HDR_U1) enforces business uniqueness across the combination of ORDER_TYPE, ORGN_CODE, ORDER_NO, and RELEASE_NO. This structure directly supports the user's search context for "release_no," indicating that the RELEASE_NO column is integral for identifying specific releases or revisions of an order number within a given organization and order type. Other pivotal columns include ORDER_STATUS, which links to the status codes table (OP_ORDR_STS_B), and various customer identifiers (SOLDTOCUST_ID, SHIPCUST_ID, BILLCUST_ID) that link to the customer master (OP_CUST_MST). Additional key fields manage shipping (SHIP_MTHD, SHIPPER_CODE), financial terms (TERMS_CODE, BILLING_CURRENCY), and organizational context (ORGN_CODE).

Common Use Cases and Queries

This table is fundamental for order management reporting, data validation, and integration workflows. A common use case is retrieving a specific order and its header details using the business key, which is particularly relevant for release-based order tracking. For example, to find a specific order release:

• SELECT * FROM GML.OP_ORDR_HDR WHERE ORGN_CODE = 'ORG1' AND ORDER_TYPE = 'SO' AND ORDER_NO = '1000' AND RELEASE_NO = '1';

Another frequent scenario involves joining with the detail lines (OP_ORDR_DTL) for comprehensive order analysis:

• SELECT hdr.ORDER_NO, hdr.RELEASE_NO, hdr.ORDER_STATUS, dtl.LINE_NO, dtl.ITEM_ID FROM GML.OP_ORDR_HDR hdr JOIN GML.OP_ORDR_DTL dtl ON hdr.ORDER_ID = dtl.ORDER_ID WHERE hdr.ORGN_CODE = :p_org;

Reporting on order status summaries or validating customer and organizational data integrity against referenced master tables are also standard operational queries.

Related Objects

OP_ORDR_HDR is a pivotal hub with extensive relationships. Its primary child tables, which store dependent transactional data, include:

• OP_ORDR_DTL: Stores the line items for the order, joined on ORDER_ID.
• OP_ORDR_CHG: Tracks changes to the order, joined on ORDER_ID.
• OP_AUDT_MST: References the order for audit purposes via ORDER_ID.

It references numerous master data and code tables via foreign keys, including:

• OP_CUST_MST: For customer data (SOLDTOCUST_ID, SHIPCUST_ID, etc.).
• SY_ORGN_MST / SY_ORGN_MST_B: For organization data (ORGN_CODE).
• OP_ORDR_TYP_B: For order type (ORDER_TYPE).
• OP_ORDR_STS_B: For order status (ORDER_STATUS).
• GL_CURR_MST: For currency (BILLING_CURRENCY).
• IC_WHSE_MST: For warehouse data (FROM_WHSE, TO_WHSE).
• OP_TERM_MST, OP_SHIP_MTH, OP_FRGT_MTH, OP_SLSR_MST: For terms, shipping, freight, and salesperson data.