Results for “po_rels_sch”

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

Overview

PO_RELS_SCH is a table owned by the GML schema and is part of the Process Manufacturing Logistics (GML) product within Oracle E-Business Suite 12.1.1 and 12.2.2. As documented in the ETRM metadata, the table stores release schedules for a blanket purchase order. In Oracle EBS, blanket purchase agreements function as long-term commitments against which individual release orders are issued. PO_RELS_SCH captures the scheduling detail associated with those releases — quantities, delivery dates, shipment routing, receiving information, and unit-of-measure conversions — allowing supply chain planners to model the timing and destination of goods covered by a blanket purchase order.

The documented physical schema in 12.2.2 defines 54 columns under the GML owner. Based on the foreign key structure mined from the metadata, the ETRM Data Vault classification heuristic suggests a link classification. This is consistent with the table's role: it connects blanket purchase order lines to their scheduled release details across multiple dimension tables such as warehouses, shippers, shipping methods, and UOM definitions, rather than representing an independent business entity.

Key Information Stored

The primary key is defined by the PO_RELS_SCH_PK unique index, which comprises the composite columns BPOLINE_ID and AGREED_DLVDATE. This combination acts as the business-key candidate — linking a blanket purchase order line to a specific agreed delivery date.

The most significant columns include:

• BPOLINE_ID — Identifier of the blanket purchase order line; part of the primary key.
• AGREED_DLVDATE — The agreed delivery date for the release schedule line; the second component of the primary key.
• POLINE_ID — References the purchase order line in PO_ORDR_DTL, linking the schedule to a specific order line.
• LINE_STATUS — Status of the release schedule line.
• ORDER_QTY1 and ORDER_QTY2 — Primary and secondary ordered quantities.
• ORDER_UM1 and ORDER_UM2 — Primary and secondary units of measure, referencing SY_UOMS_MST.
• FROM_WHSE and TO_WHSE — Originating and destination warehouses, referencing IC_WHSE_MST.
• RECV_LOCT, RECVADDR_ID, and RECV_DESC — Receiving location, address identifier (referencing SY_ADDR_MST), and receiving description.
• SHIP_MTHD and SHIPPER_CODE — Shipping method (referencing OP_SHIP_MTH) and shipper (referencing OP_SHIP_MST).
• TEXT_CODE — Reference to descriptive text stored in PO_TEXT_HDR.
• DELETE_MARK and TRANS_CNT — Standard EBS deletion flag and transaction counter columns.
• ATTRIBUTE1 through ATTRIBUTE30 and ATTRIBUTE_CATEGORY — The descriptive flexfield storage columns available for client-specific extensibility.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — Standard EBS audit columns.

Common Use Cases and Queries

Typical reporting scenarios include reviewing upcoming blanket purchase order release schedules by delivery date, analyzing quantities by warehouse or receiving location, and reconciling shipments against shipper and shipping method configuration. A representative query joining the schedule to its blanket purchase order detail line follows:

• SELECT s.BPOLINE_ID, s.AGREED_DLVDATE, s.ORDER_QTY1, s.ORDER_UM1, s.TO_WHSE, s.SHIP_MTHD FROM PO_RELS_SCH s WHERE s.DELETE_MARK = 0 AND s.AGREED_DLVDATE BETWEEN :start_date AND :end_date;
• SELECT s.*, w.WHSE_NAME FROM PO_RELS_SCH s, IC_WHSE_MST w WHERE s.TO_WHSE = w.WHSE_CODE AND s.LINE_STATUS = :status;
• SELECT s.BPOLINE_ID, b.ITEM_ID, s.ORDER_QTY1 FROM PO_RELS_SCH s, PO_BPOS_DTL b WHERE s.BPOLINE_ID = b.BPOLINE_ID;

Because the table carries a DELETE_MARK column, queries should consistently filter on this flag to exclude logically deleted records. The 30 attribute columns support downstream reporting on flexfield-enabled attributes populated at implementation.

Related Objects

PO_RELS_SCH has ten documented foreign key relationships. The most significant related objects are:

• PO_BPOS_DTL — Joined on BPOLINE_ID; the parent blanket purchase order line definition.
• PO_ORDR_DTL — Joined on POLINE_ID; the purchase order line detail.
• IC_WHSE_MST — Referenced twice via FROM_WHSE and TO_WHSE for warehouse definitions.
• OP_SHIP_MTH — Joined on SHIP_MTHD; shipping method master data.
• OP_SHIP_MST — Joined on SHIPPER_CODE; shipper master data.
• SY_ADDR_MST — Joined on RECVADDR_ID; address master for receiving addresses.
• SY_UOMS_MST — Referenced twice via ORDER_UM1 and ORDER_UM2; unit of measure definitions.
• PO_TEXT_HDR — Joined on TEXT_CODE; descriptive text headers.

These relationships confirm the table's role as a scheduling detail repository anchored to blanket purchase order lines and extended into logistics, warehousing, and receiving reference data within the GML module.