Results for “release_status”

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

Overview

OP_RELS_SCH is a Process Manufacturing Logistics (GML) table that stores blanket sales order release schedules. In Oracle EBS 12.1.1 and 12.2.2, it holds the individual release lines generated against a blanket sales agreement, capturing the scheduling detail — shipment quantities, requested delivery and ship dates, warehouse routing, and release status — that drives downstream fulfillment and shipping activity. The table resides in the GML schema and is documented as VALID, with 26 columns at the 12.2.2 release.

From a modeling perspective, the metadata's Data Vault classification heuristic identifies OP_RELS_SCH as a link. This is consistent with its FK profile: the table records associations between a contract, a presales order line, warehouses, a shipper, a ship method, an address, a text reference, and units of measure. Modeling guidance would therefore treat OP_RELS_SCH as connecting multiple business hubs rather than as a standalone hub or a descriptive satellite.

Key Information Stored

The surrogate primary key is RELEASELINE_ID, enforced by unique index OP_RELS_SCH1_PK. This is the sole documented business-key candidate; the same column serves as both the technical key and the unique index, so no separate natural business key is declared in the metadata.

• RELEASELINE_ID — Surrogate primary key and unique identifier for each release schedule line.
• CONTRACT_ID — Reference to the blanket sales agreement against which the release is generated.
• PRESALES_ORDLINE_ID — Links the release back to the originating presales order line (OP_PRSL_DTL).
• SCHED_SHIPDATE and REQD_DLVDATE — Scheduled ship date and required delivery date, the core scheduling attributes.
• ORDER_QTY1, ORDER_QTY2, ORDER_UM1, ORDER_UM2 — Ordered quantities and their corresponding units of measure, supporting dual-UOM ordering.
• RELEASE_STATUS — Current lifecycle status of the release line.
• RELEASE_NO and RELEASE_VALUE — Release number and monetary value associated with the line.
• FROM_WHSE and TO_WHSE — Source and destination warehouses, both referencing IC_WHSE_MST.
• SHIP_MTHD and SHIPPER_CODE — Shipping method and designated shipper.
• SHIPADDR_ID — Ship-to address referencing SY_ADDR_MST.
• EXPECTED_NET_PRICE — Anticipated net price for the released quantity.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and TRANS_CNT; DELETE_MARK provides logical deletion.

Common Use Cases and Queries

Typical reporting covers open release schedules by contract, shipment planning by warehouse and ship date, and reconciliation of scheduled versus required delivery dates. A representative query joins the release to its blanket contract context and warehouse master:

• Open releases by status: SELECT RELEASELINE_ID, CONTRACT_ID, SCHED_SHIPDATE, ORDER_QTY1 FROM OP_RELS_SCH WHERE RELEASE_STATUS = :status AND DELETE_MARK = 0;
• Shipment pipeline by destination: join TO_WHSE to IC_WHSE_MST to report pending releases per warehouse.
• Delivery variance: compare SCHED_SHIPDATE against REQD_DLVDATE to flag late or at-risk releases.
• Value rollup: aggregate RELEASE_VALUE and ORDER_QTY1 grouped by CONTRACT_ID for contract-level exposure reporting.

Related Objects

The following objects are documented as referenced by OP_RELS_SCH through foreign keys:

• IC_WHSE_MST — referenced twice, via FROM_WHSE and TO_WHSE.
• OP_PRSL_DTL — via PRESALES_ORDLINE_ID.
• OP_SHIP_MST — via SHIPPER_CODE.
• OP_SHIP_MTH — via SHIP_MTHD.
• OP_TEXT_HDR — via TEXT_CODE.
• SY_ADDR_MST — via SHIPADDR_ID.
• SY_UOMS_MST — referenced twice, via ORDER_UM1 and ORDER_UM2.