Search Results po_rels_sch_pk




Overview
Explore in AI Chat

Overview

The PO_RELS_SCH table is a core data structure within the Oracle E-Business Suite (EBS) Process Manufacturing Logistics (GML) module, specifically for releases 12.1.1 and 12.2.2. It serves as the primary repository for storing release schedules associated with blanket purchase orders (BPOs). A blanket purchase agreement establishes long-term terms with a supplier, and individual releases are issued against it for specific quantities and delivery dates. This table manages the detailed scheduling information for those releases, enabling precise control over material planning, procurement, and logistics execution within a manufacturing context. Its role is integral to linking high-level procurement agreements with the operational execution of material receipts.

Key Information Stored

The table's primary key, PO_RELS_SCH_PK, is a composite of BPOLINE_ID and AGREED_DLVDATE, uniquely identifying a scheduled release line for a specific delivery date. Key columns, as indicated by its foreign key relationships, store critical logistical and transactional data. The BPOLINE_ID links the release schedule back to its parent blanket purchase order line in PO_BPOS_DTL. The POLINE_ID can link the release to a standard purchase order line in PO_ORDR_DTL upon creation. Logistics data includes FROM_WHSE and TO_WHSE (referencing IC_WHSE_MST), SHIPPER_CODE (OP_SHIP_MST), and SHIP_MTHD (OP_SHIP_MTH). It also stores unit of measure information (ORDER_UM1, ORDER_UM2 from SY_UOMS_MST), a receiving address (RECVADDR_ID from SY_ADDR_MST), and a text code (TEXT_CODE from PO_TEXT_HDR) for additional instructions.

Common Use Cases and Queries

A primary use case is generating reports on upcoming material releases against blanket agreements for production planning. Procurement analysts run queries to monitor release adherence and forecast supplier demand. Common SQL patterns involve joining PO_RELS_SCH to its parent blanket order lines and header tables to provide context. For example, to find all scheduled releases for a specific blanket agreement number requiring shipment in the next 30 days, a query would join PO_RELS_SCH to PO_BPOS_DTL and PO_BPOS_HDR, filtering on AGREED_DLVDATE. Another critical use case is the transactional process of converting a scheduled release into a standard purchase order release, where the data in PO_RELS_SCH is used to populate lines in PO_ORDR_DTL.

Related Objects

PO_RELS_SCH has extensive dependencies, primarily as a child table to the blanket purchase order line. Its key related objects, as defined by its foreign keys, include:

  • PO_BPOS_DTL: The primary parent table, providing the blanket purchase order line context.
  • PO_ORDR_DTL: Links to a standard purchase order line if the release has been executed.
  • IC_WHSE_MST: References for the source (FROM_WHSE) and destination (TO_WHSE) warehouses.
  • OP_SHIP_MST / OP_SHIP_MTH: Define the shipper and shipping method for the release.
  • SY_UOMS_MST, SY_ADDR_MST, PO_TEXT_HDR: Master data tables for units of measure, addresses, and descriptive text.
These relationships ensure data integrity and enable comprehensive reporting across procurement and logistics functions.