Search Results process_flow_schedule




Overview
Explore in AI Chat

Overview

MRP_FLOW_SCHEDULE_PVT is a private PL/SQL package in the Oracle EBS Applications (APPS) schema that supports the flow scheduling functionality within Oracle Flow Manufacturing. It provides the programmatic backbone for creating, validating, locking, and retrieving flow schedule records — the execution-level documents that drive discrete production on a flow (lean) line. A flow schedule ties a demand source to a specific assembly, organization, BOM revision, alternate BOM designator, alternate routing designator, and completion subinventory/locator, and carries a build sequence that determines line sequencing.

The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling session rather than the definer, which is standard for private (PVT) helper packages invoked from a public API or concurrent program context. Its private classification confirms it is not intended as a supported integration point; external interfaces should call the public wrapper packages that in turn delegate to these routines. The internal header notes the API name as Process_Flow_Schedule and records enhancement 2665434, which introduced PL/SQL-standards-compliant record types.

Key Procedures and Functions

The package exposes seven documented units: five conversion/validation helpers, one processing entry point, one locking routine, and one retrieval function.

  • PUB_FLOW_SCHED_VAL_REC_TO_PVT — Converts a validated public-format flow schedule record into the internal private record structure.
  • PUB_FLOW_SCHED_REC_TO_PVT — Converts a public-format flow schedule record into the private record structure without the validation variant.
  • PVT_FLOW_SCHED_VAL_REC_TO_PUB — Converts a validated private record back into the public record structure, supporting the outbound direction of the API.
  • PVT_FLOW_SCHED_REC_TO_PUB — Converts a private record to the public record structure for return to the caller.
  • PROCESS_FLOW_SCHEDULE — The core processing routine that performs the create/update logic for a flow schedule, applying the translated record data to the underlying scheduling tables. This is the procedure users reference when searching "process_flow_schedule."
  • LOCK_FLOW_SCHEDULE — Acquires a lock on the flow schedule record to serialize concurrent modification, protecting against lost updates during processing.
  • GET_FLOW_SCHEDULE — Retrieves an existing flow schedule record, presumably returning it through the public record structure for read access.

The Flow_Schedule_PVT_Rec_Type record defines the payload, encompassing demand source attributes (type, header ID, line, delivery), scheduling fields (build sequence, MPS net quantity, MPS scheduled completion date), BOM/routing designators and revisions, completion location, accounting flexfields (material, overhead, variance, outside processing accounts), multitenancy/audit columns, and descriptor flexfield attributes 1–15.

Tables Accessed

The ETRM metadata does not enumerate specific base tables; the package operates through APPS synonyms. Functionally, the record layout implies access to the flow schedule base table (WIP_FLOW_SCHEDULES) and its dependent demand/accounting detail tables, since the payload mirrors those columns directly, including line_id, organization_id, and the various accounting account identifiers written during schedule processing.

Usage Notes

Because it is a private package, MRP_FLOW_SCHEDULE_PVT is not directly called by customers. It is referenced by six other packages, which is consistent with its role as a helper layer beneath a public flow scheduling API. Typical invocation paths are Oracle Flow Manufacturing forms performing schedule creation or maintenance, and concurrent programs or public APIs that process flow schedules in batch. Developers extending flow scheduling should use the supported public API rather than calling PROCESS_FLOW_SCHEDULE directly, as the private interface carries no compatibility guarantee across 12.1.1 and 12.2.2.