Search Results op_prsl_hdr_pk




Overview
Explore in AI Chat

Overview

The OP_PRSL_HDR table is a core data object within the Oracle E-Business Suite Process Manufacturing Logistics (GML) module. It serves as the master header table for two distinct but related transactional entities: Order Profiles and Blanket Sales Orders. An Order Profile is a template or pre-configured order that standardizes terms and conditions for recurring sales, while a Blanket Sales Order is a long-term agreement defining pricing and terms for a specific item over a period. This table stores the overarching contractual and administrative data for these agreements, acting as the parent record for associated lines, charges, and subsequent standard sales orders. Its role is critical for managing pre-sales agreements and streamlining the order-to-cash process within manufacturing and distribution environments.

Key Information Stored

The table's primary identifier is the PRESALES_ORD_ID, which is the system-generated primary key (OP_PRSL_HDR_PK). For application-level uniqueness, a composite key (OP_PRSL_HDRI1) is also defined using ORGN_CODE, PRESALES_ORD_NO, and PRESALES_ORD_TYPE. Key stored information includes customer identifiers (SOLDTOCUST_ID, SHIPCUST_ID, BILLCUST_ID, ULTIMATE_SHIPCUST_ID, CONSIGNEE_ID), defining the complex customer relationships in a transaction. It holds logistical data such as warehouse codes (FROM_WHSE, TO_WHSE), shipping methods (SHIP_MTHD, SHIPPER_CODE), and port details (EMBARKATION_PORT, DEBARKATION_PORT). Commercial terms are captured via columns for currency (BILLING_CURRENCY), payment terms (TERMS_CODE), FOB (FOB_CODE), freight billing method (FRTBILL_MTHD), and commission (COMMISSION_CODE). Status management is supported through fields like HOLDREAS_CODE and CONTACT_ID.

Common Use Cases and Queries

A primary use case is generating reports on all active blanket agreements for a specific customer or sales representative. For example, to list open blanket sales orders for a customer, one might query: SELECT presales_ord_no, creation_date, terms_code FROM gml.op_prsl_hdr WHERE soldtocust_id = :cust_id AND presales_ord_type = 'BLANKET' AND sysdate BETWEEN start_date AND NVL(end_date, sysdate);. Another common scenario involves tracing the fulfillment of a blanket agreement by joining to the standard order header: SELECT o.ord_no, o.ord_date, p.presales_ord_no FROM gml.op_prsl_hdr p, apps.oe_order_headers_all o WHERE p.presales_ord_id = o.presales_ord_id;. Data fixes or validations often require queries that join to referenced master tables, such as validating customer IDs against OP_CUST_MST or currency codes against GL_CURR_MST.

Related Objects

The OP_PRSL_HDR table maintains extensive foreign key relationships, primarily through the PRESALES_ORD_ID column. Key child transactional tables include:

  • OP_PRSL_DTL: Stores the line-level details (items, quantities) for the order profile or blanket agreement.
  • OP_PRSL_CHG: Holds any special charges or adjustments associated with the header.
  • OP_ORDR_HDR: The standard sales order header table, which references the PRESALES_ORD_ID to indicate the source blanket agreement or profile.
It references numerous master data tables to enforce integrity, including:
  • OP_CUST_MST (Customer Master): For various customer IDs (SOLDTOCUST_ID, SHIPCUST_ID, etc.).
  • OP_PRSL_TYP_B: For the PRESALES_ORD_TYPE.
  • IC_WHSE_MST (Warehouse Master): For FROM_WHSE and TO_WHSE.
  • GL_CURR_MST: For BILLING_CURRENCY.
  • OP_TERM_MST, OP_FOBC_MST, OP_SHIP_MTH, OP_SLSR_MST: For terms, FOB, shipping method, and sales representative data.