Results for “op_prsl_hdr”

50+ results




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

Overview

OP_PRSL_HDR is a core table in the Oracle Process Manufacturing Logistics (GML) module, owned by the GML schema. It stores header-level information for two closely related business constructs: the Order Profile Header and the Blanket Sales Order Header. In Oracle EBS 12.1.1 and 12.2.2, this table anchors the pre-sales / blanket order process, capturing the commercial, logistical, and financial attributes that govern how a long-lived sales agreement is administered across releases. It holds values such as the sold-to and ship-to customers, pricing currency, shipping and freight methods, commission and sales representative assignments, and the running value accumulators (open, shipped, available, and schedule values) that track a blanket order through its lifecycle. Because each header can spawn multiple detail lines, changes, and downstream operational orders, OP_PRSL_HDR functions as the entry point for pre-sales order reporting and release processing.

A heuristic Data Vault classification derived from the foreign-key structure suggests this object is satellite-leaning. The table’s wide attribute set—95 documented columns, including 30 descriptive attributes—reinforces this characterization, as the structure is descriptive and attributable rather than purely relational.

Key Information Stored

OP_PRSL_HDR is defined with a surrogate primary key, PRESALES_ORD_ID, exposed by the OP_PRSL_HDR_PK index. A second unique index, OP_PRSL_HDRI1, exposes the natural business key composed of ORGN_CODE, PRESALES_ORD_NO, and PRESALES_ORD_TYPE. Mapping surrogate versus business keys is essential when integrating or writing queries.

The most significant columns include:

Common Use Cases and Queries

Typical scenarios include reporting on open blanket orders by customer, validating release eligibility against remaining open value, and reconciling downstream operational orders and changes. A representative query joins the header to its child details and the customer master:

SELECT h.presales_ord_no, h.presales_ord_type, h.orgn_code,
      c.customer_name, h.order_max_value, h.order_open_value, h.status_ind
 FROM gml.op_prsl_hdr h, gml.op_cust_mst c
 WHERE h.soldtocust_id = c.cust_id
   AND h.orgn_code = :orgn
   AND NVL(h.delete_mark,0) = 0;

Common reports include blanket order value utilization, release counts by header, hold and expiration tracking, and pre-sales order audit trails. Because child tables OP_PRSL_DTL, OP_PRSL_CHG, and OP_ORDR_HDR all carry PRESALES_ORD_ID, most transactional queries drive from the header ID.

Related Objects

The following subordinate and reference tables interact most directly with OP_PRSL_HDR:

  • OP_PRSL_DTL — Detail lines; joins on PRESALES_ORD_ID.
  • OP_PRSL_CHG — Change history; joins on PRESALES_ORD_ID.
  • OP_ORDR_HDR — Operational sales order header that references the blanket order via PRESALES_ORD_ID.
  • OP_CUST_MST — Customer master supplying the sold-to, ship-to, bill-to, ultimate ship-to, and consignee roles.
  • OP_PRSL_TYP_B — Blanket order type validation.
  • GL_CURR_MST — Currency validation for BILLING_CURRENCY.
  • OP_TERM_MST, OP_SHIP_MTH, OP_SHIP_MST, OP_FRGT_MTH, OP_FOBC_MST — Terms, shipping, freight, and FOB reference data.
  • IC_WHSE_MST — Warehouse master referenced by FROM_WHSE and TO_WHSE.