Search Results mrp_line_schedule_algorithm




Overview
Explore in AI Chat

Overview

The APPS.MRP_LINE_SCHEDULE_ALGORITHM package body implements the line scheduling algorithm used by Oracle E-Business Suite manufacturing and planning modules. Its business purpose is to sequence and time production orders against a production line, respecting line capacity, resource constraints, calendar availability, and the applicable scheduling rule. It is one of the core computational engines behind repetitive scheduling, flow schedule creation, and mixed-model line sequencing in Oracle Manufacturing and Oracle Advanced Supply Chain Planning.

The package is classified as an OTHER API in the ETRM registry and holds a VALID status in the APPS schema. It is documented as referencing fifteen database objects through APPS synonyms and as being referenced by six other packages, which confirms its role as a shared scheduling service rather than a standalone utility. All scheduling activity is performed inside the APPS schema, with no evidence of public synonyms beyond those already exposed through the standard product schemas.

Key Procedures and Functions

ETRM documents nineteen procedures and functions within the package body. They are best understood in functional groups.

Tables Accessed

The package reads and writes through APPS synonyms. Scheduling rules and line parameters are sourced from MRP_SCHEDULING_RULES, MTL_PARAMETERS, and MTL_SYSTEM_ITEMS. Calendar and resource availability are read from BOM_CALENDAR_DATES, BOM_RESOURCE_FLEX_FENCES, and MRP_CALENDAR. Order and line entities are handled through WIP_DISCRETE_JOBS, WIP_REPETITIVE_SCHEDULES, WIP_FLOW_SCHEDULES, WIP_LINES, WIP_ENTITIES_S, and BOM_REVISIONS. Query metadata for the scheduling forms is held in MRP_FORM_QUERY and MRP_FORM_QUERY_S. DBMS_SQL, DUAL, and PLITBLM are used for dynamic SQL execution and internal PL/SQL table handling.

Usage Notes

This package is an internal engine rather than a user-facing API. It is normally invoked through the Oracle Manufacturing scheduling forms, through concurrent programs that generate flow schedules and repetitive schedules, and by the six dependent packages identified in the ETRM dependency listing. Custom code should avoid calling individual internal procedures directly, because the algorithm depends on consistent setup of scheduling rules, calendars, and line definitions. Where integration is required, the supported entry points are the higher-level scheduling procedures. The presence of FND_API and FND_MSG_PUB in the dependency list indicates that error handling and messages follow the standard Oracle Application Object Library conventions, and callers should expect scheduling failures to be reported through the standard message stack.