Search Results unlink_order_line

Overview

The APPS.MRP_FLOW_SCHEDULE_PUB package is the public PL/SQL API for Oracle Flow Manufacturing flow schedules in Oracle E-Business Suite releases 12.1.1 and 12.2.2. Declared with AUTHID CURRENT_USER and carrying the @rep:scope public designation, it exposes a stable, supported interface for programmatic maintenance of flow schedule records that would otherwise be manipulated only through the Flow Manufacturing workbench forms. The package belongs to product FLM (Flow Manufacturing) and is registered against the business entity FLM_FLOW_SCHEDULE.

Functionally, the API supports the complete lifecycle of a flow schedule: creation of new schedules, retrieval of existing schedule records, locking of schedule rows for concurrent modification, line-level scheduling, computation of scheduling dates, and unlinking of order lines that have been attached to a flow schedule. This last capability is significant because flow schedules are frequently created in response to sales order demand, and the relationship between a flow schedule and its originating order line must be severable without deleting the schedule itself.

Key Procedures and Functions

The documented interface comprises seven procedures and functions:

• PROCESS_FLOW_SCHEDULE — The primary maintenance routine, responsible for creating and updating flow schedule records based on the Flow_Schedule_Rec_Type record structure and its corresponding table type.
• LOCK_FLOW_SCHEDULE — Acquires a lock on a specified flow schedule, preventing conflicting concurrent updates from other sessions.
• GET_FLOW_SCHEDULE — Retrieves the current attribute values of a flow schedule into the public record type for inspection or downstream processing.
• LINE_SCHEDULE — Performs scheduling at the flow schedule line level, applying scheduling logic to the associated order lines.
• GET_FIRST_UNIT_COMPLETION_DATE — Returns the projected completion date of the first unit for a flow schedule, derived from routing and scheduling data.
• GET_OPERATION_OFFSET_DATE — Returns the calculated date offset for a specific operation within the flow routing.
• UNLINK_ORDER_LINE — Dissociates a sales order line from its flow schedule, removing the demand linkage without deleting the schedule. This procedure corresponds directly to the search term unlink_order_line and is the supported mechanism for breaking the flow schedule-to-order line association.

Tables Accessed

The package operates against four documented base tables through APPS synonyms:

• WIP_FLOW_SCHEDULES — The primary entity table, holding flow schedule header records. It is the principal target of PROCESS_FLOW_SCHEDULE and the source for GET_FLOW_SCHEDULE.
• BOM_OPERATIONAL_ROUTINGS — Provides routing header information used to derive scheduling attributes and operation-level dates.
• BOM_OPERATION_SEQUENCES — Supplies the operation sequence steps and offsets required by GET_OPERATION_OFFSET_DATE and line scheduling logic.
• OE_ORDER_LINES_ALL — Holds the sales order line records involved in the schedule-to-demand relationship; this is the table affected by UNLINK_ORDER_LINE.

Usage Notes

This package is a server-side API and is normally invoked from PL/SQL rather than from a client interface directly. It is referenced by six other packages within the EBS schema, indicating that it serves as a shared foundation for higher-level Flow Manufacturing functionality. Typical callers include Flow Manufacturing workbench forms, order-to-schedule integration routines, and custom extensions that must create or amend flow schedules in bulk. The header comment identifies a fixed file version (MRPPWFSS.pls 120.1), and the API remains classified as active under the 12.2.2 documentation set. Standard API conventions apply: callers should initialize the record structure to FND_API.G_MISS_* defaults, populate only the attributes being changed, and check the returned API status before committing. When severing demand linkage, UNLINK_ORDER_LINE should be used rather than direct DML against OE_ORDER_LINES_ALL or WIP_FLOW_SCHEDULES, preserving data integrity and validation logic.