Search Results get_first_unit_completion_date

Overview

APPS.MRP_FLOW_SCHEDULE_PUB is the public PL/SQL API package for flow scheduling within Oracle E-Business Suite's Manufacturing and Supply Chain modules. Flow scheduling governs repetitive and flow manufacturing environments, where discrete production is sequenced by rate and line capacity rather than by discrete work orders. This package serves as the programmatic gateway for creating, retrieving, locking, and unlinking flow schedule records that tie production lines to sales order demand.

The package follows the standard EBS PL/SQL API architecture, exposing a thin public specification (PUB) that delegates validation and persistence logic to a private implementation layer (MRP_Flow_Schedule_PVT). It adheres to the FND_API conventions of Oracle's Application Object Library, including the standard parameter set of p_api_version_number, p_init_msg_list, p_return_values, and p_commit, with corresponding x_return_status, x_msg_count, and x_msg_data output parameters. Record structures are converted between internal identifiers and external values through a pair of helper routines, Id_To_Value and Value_To_Id, both of which were refactored under enhancement 2665434 to consume the private MRP_Flow_Schedule_PVT.Flow_Schedule_PVT_Rec_Type record type rather than the legacy public record type. The header indicates a last modification in August 2008, meaning the same body ships essentially unchanged through the 12.1.1 and 12.2.2 releases.

Key Procedures and Functions

Seven procedures and functions are exposed through the documented specification:

• PROCESS_FLOW_SCHEDULE — The primary workhorse API. It accepts the standard FND_API control parameters plus a flow schedule record, and drives the create, update, and delete lifecycle for a flow schedule entry. It performs all validation, invokes the private layer for persistence, and optionally commits.
• LOCK_FLOW_SCHEDULE — Places a logical lock on a specified flow schedule, typically to prevent concurrent modification while a downstream process reads or updates it.
• GET_FLOW_SCHEDULE — Retrieves a flow schedule record, populating the caller's record structure with IDs and, where requested via the value-conversion routines, with denormalized descriptive values.
• LINE_SCHEDULE — The routine most directly associated with the search term line_schedule. It communicates line-level scheduling data, mapping a flow schedule to the production line on which the repetitive or flow order is to be sequenced.
• GET_FIRST_UNIT_COMPLETION_DATE — Returns the completion date of the first unit on a flow schedule, a key input to capacity planning and promise-date calculations.
• GET_OPERATION_OFFSET_DATE — Calculates the date of a given routing operation by applying the operation's offset (lead time) to the schedule start. This supports component availability and material pull timing.
• UNLINK_ORDER_LINE — Removes the association between a flow schedule and an order line, used when demand is re-sequenced, cancelled, or moved to a different line.

Tables Accessed

• WIP_FLOW_SCHEDULES — The base schedule table holding line, schedule group, start and completion dates, and status for each flow schedule. It is the primary insert/update/delete target of PROCESS_FLOW_SCHEDULE.
• BOM_OPERATIONAL_ROUTINGS — Supplies routing header information for the assembly being scheduled, giving the operation sequence context used by GET_OPERATION_OFFSET_DATE.
• BOM_OPERATION_SEQUENCES — Provides individual operation definitions and offset percentages required for operation-date calculations.
• OE_ORDER_LINES_ALL — The order management line table that flow schedules are linked to. Functions such as LINE_SCHEDULE and UNLINK_ORDER_LINE read and update order line scheduling attributes, such as the scheduled ship date and line assignment.

Usage Notes

The package is invoked almost exclusively in a server-side context. In standard EBS, it supports flow manufacturing workbenches and line scheduling forms within Oracle Flow Manufacturing and Oracle Order Management, and it is called by concurrent programs that sequence repetitive production. It is also referenced by six other PL/SQL packages, indicating it acts as a shared dependency in the MRP/WIP scheduling chain rather than a purely form-driven API.

Custom code should call this package only through its public specification, supplying a valid API version and checking x_return_status before relying on any output record. Because the record type contract changed in enhancement 2665434, integrations that were built against the older Flow_Schedule_Rec_Type must pass records conforming to the MRP_Flow_Schedule_PVT types. Callers performing multi-step operations should defer commit control by passing p_commit = FND_API.G_FALSE and commit at the transaction boundary. The package does not expose a bulk interface; large scheduling loads are normally driven through concurrent programs that loop over this API.