Search Results mrp_flow_schedule_pvt




Overview
Explore in AI Chat

Overview

MRP_DEFAULT_FLOW_SCHEDULE is an APPS-owned PL/SQL package within the Oracle E-Business Suite 12.1.1 and 12.2.2 application schemas. It belongs to the manufacturing planning family of packages that supports flow scheduling and repetitive manufacturing functionality. Its primary role is to establish default flow schedule definitions for items that are produced under repetitive or line-based manufacturing environments, ensuring that the planning engine can generate and maintain valid flow schedules without requiring manual entry of every scheduling attribute.

The package operates in close coordination with MRP_FLOW_SCHEDULE_PVT, which is the private API layer that performs the core flow schedule processing. The dependency listing confirms a bidirectional relationship: MRP_DEFAULT_FLOW_SCHEDULE references MRP_FLOW_SCHEDULE_PVT, and MRP_FLOW_SCHEDULE_PVT in turn references MRP_DEFAULT_FLOW_SCHEDULE. This mutual dependency reflects a design in which defaulting logic and schedule processing call into one another to resolve scheduling parameters, accounting classes, and line-level attributes. The user search term "mrp_flow_schedule_pvt" is directly relevant because the private package is the principal collaborator of this object, and much of the functional behavior of the defaulting package is exposed through that private layer rather than through standalone public APIs.

Key Procedures and Functions

The ETRM metadata for EBS 12.2.2 documents one procedure or function within this package:

  • ATTRIBUTES — The documented entry point of the package. It is associated with the resolution and assignment of scheduling attributes required when defaulting a flow schedule record. In practice, this routine supplies the attribute set that the flow scheduling layer uses to populate or validate a schedule, including item, routing, line, and accounting-related defaults. Parameter lists are not published in the available metadata and are therefore not reproduced here; the routine is described by purpose only.

The small public surface of the package is consistent with its role as a supporting defaulting utility. Detailed procedural logic resides in MRP_FLOW_SCHEDULE_PVT, and MRP_DEFAULT_FLOW_SCHEDULE contributes the default-value resolution that the private package invokes during flow schedule creation and maintenance.

Tables Accessed

The package reads and, where applicable, writes data through APPS synonyms across several manufacturing and planning base tables. The documented tables and their functional significance are:

  • BOM_CALENDAR_DATES — Provides manufacturing calendar dates used to align flow schedule start and end dates with valid working days.
  • BOM_OPERATIONAL_ROUTINGS — Supplies routing information, including the operational sequence associated with the item being scheduled.
  • MRP_PROJECT_PARAMETERS_V — A view of project-level planning parameters consulted when the schedule is associated with a project or task.
  • MTL_PARAMETERS — Organizational inventory parameters that establish default behavior for the inventory organization.
  • MTL_SYSTEM_ITEMS — Item master attributes, such as planner, planning attributes, and item status, used to validate and default schedule fields.
  • WIP_ACCOUNTING_CLASSES — Accounting class definitions needed to derive the correct work-in-process accounting treatment for the schedule.
  • WIP_ENTITIES_S — The WIP entity definition, linking the flow schedule to the appropriate work-in-process entity.
  • WIP_LINES — Repetitive manufacturing line definitions, including line attributes and rates that govern flow scheduling.
  • WIP_PARAMETERS — WIP module parameters that control defaulting behavior for work-in-process and flow schedule transactions.
  • DUAL — The standard single-row pseudo-table, used for constant evaluation and single-value lookups.

Usage Notes

MRP_DEFAULT_FLOW_SCHEDULE is not intended as a standalone end-user API. It is invoked indirectly by Oracle Manufacturing and Planning forms and concurrent programs that create or modify flow schedules, and it is referenced by one other package, MRP_FLOW_SCHEDULE_PVT, which performs the substantive schedule processing. The object status is VALID in the referenced ETRM versions, indicating the package is compiled and operational.

Custom code should generally avoid calling this package directly; the supported integration path is through the flow schedule public API layer. Where customization is unavoidable, developers should preserve the dependency contract with MRP_FLOW_SCHEDULE_PVT and account for the organization-specific defaults drawn from MTL_PARAMETERS, WIP_PARAMETERS, and WIP_LINES, since these values determine the outcome of the ATTRIBUTES routine. Testing should confirm that calendar, routing, and accounting class defaults resolve correctly for each inventory organization in scope.