Search Results releaseline_id

Overview

The OP_RELS_SCH table is a core data object within the Oracle E-Business Suite (EBS) Process Manufacturing Logistics (GML) module. It serves as the primary repository for storing release schedule information associated with blanket sales orders. A blanket sales order is a long-term agreement with a customer that specifies terms and pricing, from which specific releases or shipments are scheduled over time. This table is therefore critical for managing the fulfillment side of these agreements, tracking the planned quantities, dates, and logistical details for each scheduled release against a blanket order line. Its role is to bridge the high-level sales agreement with the detailed execution of individual shipments.

Key Information Stored

The table's primary key, RELEASELINE_ID, uniquely identifies each scheduled release record. Key data points stored include references to the originating blanket sales order line (PRESALES_ORDLINE_ID), shipment logistics such as the source and destination warehouses (FROM_WHSE, TO_WHSE), and the shipping method (SHIP_MTHD). It also holds the scheduled quantity and date for the release, along with unit of measure information (ORDER_UM1, ORDER_UM2). Additional columns manage associated text instructions (TEXT_CODE), specific ship-to addresses (SHIPADDR_ID), and links to shipping documents (SHIPPER_CODE). The structure is designed to support detailed planning and execution tracking for each release.

Common Use Cases and Queries

A primary use case is generating a report of all pending releases for a specific blanket order or customer to facilitate warehouse picking and shipping planning. Another common scenario involves querying releases scheduled for a specific date range to manage production or procurement planning. Data from this table is also integral to the shipping process, where releases are converted into actual shipments. A typical query might join OP_RELS_SCH with the blanket order detail table (OP_PRSL_DTL) and customer information to create a release schedule report.

• Sample Query Pattern: SELECT oprs.releaseline_id, oprs.schedule_date, oprs.order_qty1, opd.order_number, opd.line_num FROM gml.op_rels_sch oprs JOIN gml.op_prsl_dtl opd ON oprs.presales_ordline_id = opd.presales_ordline_id WHERE oprs.schedule_date BETWEEN :p_start_date AND :p_end_date ORDER BY oprs.schedule_date;

Related Objects

OP_RELS_SCH has significant integration within the GML and Order Management (OM) modules, as evidenced by its foreign key constraints. The most direct relationship is with the OP_PRSL_DTL (Blanket Sales Order Details) table, which is the parent for the PRESALES_ORDLINE_ID. Logistics are managed through foreign keys to IC_WHSE_MST (warehouses), OP_SHIP_MTH (shipping methods), and SY_ADDR_MST (addresses). It also references OP_SHIP_MST for shipper data and SY_UOMS_MST for units of measure. The link to OP_TEXT_HDR allows for attaching standard notes or instructions to a release schedule. These relationships ensure data integrity and enable comprehensive transactional reporting across the order-to-ship cycle.