Results for “op_prsl_dtl”

50+ results




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

Overview

OP_PRSL_DTL is a GML (Process Manufacturing Logistics) base table that stores order profile lines and blanket sales order lines within Oracle E-Business Suite 12.1.1 and 12.2.2. In OPM/Process Manufacturing terminology, a "presales order" is the profile or blanket agreement header, and OP_PRSL_DTL carries its individual line items. Each row represents one prospect or blanket order line that defines the requested item, quantities, pricing constraints, ship-to information, and release rules that downstream sales order and release scheduling processes consume.

Under a heuristic Data Vault classification, this table leans toward a satellite, since it describes attributes and descriptive context attached to a parent business entity (the profile/blanket header) rather than acting as an independent hub or a pure associative link. This is a modeling suggestion only; the table is physically a conventional EBS detail table with a composite unique key.

Key Information Stored

The documented physical schema contains 112 columns. Among the most operationally significant:

The ATTRIBUTE1 through ATTRIBUTE30 and ATTRIBUTE_CATEGORY columns provide the standard EBS DFF extension mechanism, while CREATION_DATE, LAST_UPDATE_DATE, CREATED_BY, and LAST_UPDATED_BY supply audit lineage.

Common Use Cases and Queries

  • Listing all lines for a given profile or blanket order:
    SELECT d.presales_ordline_no, d.item_id, d.order_qty1, d.status_ind
    FROM   gml.op_prsl_dtl d
    WHERE  d.presales_ord_id = :ord_id
    AND    d.delete_mark = 0
    ORDER BY d.presales_ordline_no;
  • Reporting open release capacity by comparing LINE_MAX_VALUE and LINE_RELEASE_VALUE against actual releases scheduled in OP_RELS_SCH.
  • Customer/consignee analysis by joining BILLCUST_ID, SHIPCUST_ID, and CONSIGNEE_ID to OP_CUST_MST.
  • UoM conversion validation by joining ORDER_UM1 and ORDER_UM2 to SY_UOMS_MST.
  • Identifying lines on hold through HOLDREAS_CODE and HOLD_EXPIRATION to drive exception reporting.

Queries should always filter DELETE_MARK = 0, and it is prudent to qualify the GML schema explicitly.

Related Objects