Results for “cto_flow_schedule”

35 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CTO_FLOW_SCHEDULE is a PL/SQL package owned by the APPS schema that supports Configure-to-Order (CTO) flow scheduling within Oracle E-Business Suite manufacturing and order fulfillment. It is classified under the ETRM API taxonomy as OTHER, indicating it is an internal utility package rather than a formally published open interface. The package operates at the intersection of Oracle Order Management, Oracle Bills of Material, and Oracle Work in Process, providing the logic required to translate configured sales order demand into flow schedule records used on the shop floor.

Flow scheduling is a lean manufacturing technique in which production is paced to customer demand rather than to discrete work orders. In an EBS CTO environment, configured items must be scheduled against routing and scheduling rules that are valid for the specific configuration selected by the customer. CTO_FLOW_SCHEDULE encapsulates the logic that evaluates those conditions and creates the corresponding flow schedule. The package is recorded as VALID in both 12.1.1 and 12.2.2 environments, and the documented dependency list shows it references only the SYS.STANDARD schema object, meaning it does not depend on other APPS packages for its core behavior.

Key Procedures and Functions

The ETRM metadata documents three procedures or functions within the package. Parameter lists are not published and are therefore not reproduced here.

  • CTO_FS — The primary entry point associated with flow schedule processing. It serves as the orchestrating routine that drives the package's scheduling activity, evaluating the scheduling context and delegating to the creation and scheduling routines.
  • CTO_CREATE_FS — Responsible for creating the flow schedule record itself. This routine assembles the required scheduling attributes and inserts the flow schedule into the WIP flow schedule structures.
  • CTO_SCHEDULE_FS — Performs the scheduling step on an existing flow schedule, applying scheduling rules and routing-derived timing so that the flow schedule reflects valid production dates and sequence.

The separation of creation from scheduling allows the flow schedule record to be established first and subsequently re-scheduled as order quantities, dates, or routing assumptions change.

Tables Accessed

The documented table references, resolved through APPS synonyms, reflect the full span of data the package requires:

  • OE_ORDER_LINES_ALL — Source of configured sales order line detail; supplies the demand being scheduled.
  • BOM_OPERATIONAL_ROUTINGS — Provides the routing definition for the configured assembly, including operations used to derive flow schedule steps.
  • BOM_PARAMETERS — Supplies Bills of Material setup values that govern routing and scheduling behavior.
  • MRP_SCHEDULING_RULES — Provides the scheduling rules that determine how production dates and lead times are calculated for the flow schedule.
  • WIP_FLOW_SCHEDULES — The primary target table; holds the flow schedule records created and maintained by the package.
  • WIP_LINES — Used to associate and maintain the flow schedule's line-level execution detail.

Usage Notes

CTO_FLOW_SCHEDULE is an internal package and is not exposed as a documented open interface. It is referenced by two other packages, CTO_WIP_WRAPPER and CTO_WORKFLOW, which indicates that in practice the package is invoked indirectly through the CTO work-in-process workflow rather than called directly from concurrent programs or forms. Typical invocation occurs when a configured order line progresses through the CTO order-to-production flow and a flow schedule must be generated or refreshed.

Because the package is not designated as a public API, direct calls from custom code carry upgrade risk across 12.1.1 and 12.2.2. Customers requiring flow schedule automation should prefer invoking the documented CTO workflow or the wrapping packages, and any direct dependency on CTO_FLOW_SCHEDULE should be reviewed during patching and upgrades.