Search Results mrp_validate_flow_schedule




Overview
Explore in AI Chat

Overview

The APPS.MRP_VALIDATE_FLOW_SCHEDULE package is a validation utility within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 manufacturing and planning modules base schema. Its primary business function is to enforce data integrity rules on flow schedule definitions before they are committed to the database. Flow schedules represent repetitive manufacturing work orders in a flow (continuous or high-volume) production environment, and the accuracy of their associated entities, such as schedule groups, lines, and items, is critical to downstream planning, WIP execution, and cost collection.

The package is classified as an OTHER API in the ETRM metadata, meaning it is not a public, published interface intended for direct customer invocation, but rather an internal validation layer consumed by other EBS packages. Specifically, the dependency information shows a bidirectional relationship with APPS.MRP_FLOW_SCHEDULE_PVT: the private package references MRP_VALIDATE_FLOW_SCHEDULE, and MRP_VALIDATE_FLOW_SCHEDULE references MRP_FLOW_SCHEDULE_PVT. This architecture indicates that MRP_FLOW_SCHEDULE_PVT delegates validation responsibilities to this package when processing flow schedule create, update, or delete operations through the Flow Manufacturing workbench and related concurrent programs.

Key Procedures and Functions

The ETRM metadata documents three procedures or functions within the package:

  • ENTITY — Validates the core flow schedule entity being processed. This likely confirms that the referenced flow schedule record exists, that required identifying attributes are populated, and that the schedule is in a state that permits the requested operation.
  • ATTRIBUTES — Performs attribute-level validation for the flow schedule, checking the consistency and validity of descriptive and control attributes against system-defined rules and reference data.
  • ENTITY_DELETE — Handles validation logic specific to the deletion of a flow schedule entity, verifying that deletion is permissible, for example that dependent records such as WIP lines or schedule group assignments would not be orphaned or violated.

No parameter lists are documented in the available metadata; parameter details are contained within the package specification in the EBS schema and should be inspected directly when integration work is required.

Tables Accessed

The package reads and writes against the following documented tables via APPS synonyms:

  • WIP_FLOW_SCHEDULES — The primary flow schedule master table, holding the schedule definition being validated.
  • WIP_LINES — Flow schedule lines associated with the schedule entity, validated for consistency with the parent schedule.
  • WIP_SCHEDULE_GROUPS — Schedule groupings used to organize flow schedules; validated for valid assignment.
  • MTL_SYSTEM_ITEMS — Item master validation to ensure referenced items are valid and enabled for the organization.
  • MTL_ITEM_LOCATIONS — Validates that referenced item locations exist and are valid for the inventory organization.
  • MTL_PARAMETERS — Organization-level inventory parameters used to confirm organizational context and defaults.
  • MRP_PROJECT_PARAMETERS — Project-related planning parameters supporting project-aware flow schedule validation.
  • DUAL — Standard single-row utility table used for scalar or default-value retrievals.

Usage Notes

MRP_VALIDATE_FLOW_SCHEDULE is an internal validation package and is not intended for direct invocation by end users or custom applications. It is invoked indirectly through APPS.MRP_FLOW_SCHEDULE_PVT, which serves as the programmatic gateway for flow schedule operations. It is also referenced by itself, indicating internal recursive or helper calls within the package implementation.

Typical invocation occurs during Flow Manufacturing transactions entered through the Oracle Forms-based flow schedule workbench, during concurrent programs that import or process flow schedules, and during any PL/SQL code path that calls MRP_FLOW_SCHEDULE_PVT. Because the package is owner-schema sensitive and depends on SYS.STANDARD, custom code should not call it directly; instead, developers should use the public MRP_FLOW_SCHEDULE_PVT interfaces, which in turn trigger this validation logic. When troubleshooting validation errors in flow schedule processing, this package is a useful diagnostic reference point for understanding which entity, attribute, or delete-related rule was violated.