Search Results save_sch_attributes




Overview

OE_CONFIG_SCHEDULE_PVT is a private PL/SQL package in the APPS schema that supports the scheduling of configured (ATO, PTO, and hybrid) order lines within Oracle Order Management. Its central business function is to translate configured item structures into schedulable supply and demand so that the ordering engine can perform available-to-promise checks, reservation, and scheduling across the components that constitute a configuration. The package works in close partnership with the public scheduling infrastructure, notably OE_SCHEDULE_UTIL, OE_GROUP_SCH_UTIL, OE_SCHEDULE_GRP, and OE_ORDER_PUB, and it depends on the FND_API foundation layer for the standard API programming model. Because it is classified as a private (PVT) package, it is not intended as a public extension point; Oracle application logic and other scheduling utilities in the same product call it internally rather than customers calling it directly.

Key Procedures and Functions

The documented package exposes nine procedures and functions, each targeting a specific step in the configuration scheduling flow.

  • SCHEDULE_ATO — Drives scheduling for assemble-to-order configurations, where the parent is built from components and the schedule must respect the configuration's structure.
  • SCHEDULE_SMC — Performs scheduling for ship-model-complete (or single-model-complete) style configurations, where the parent line is the shipped entity.
  • SCHEDULE_NONSMC — Handles scheduling for non-SMC configurations, where components rather than the parent carry the shippable quantities.
  • PROCESS_GROUP — Processes a related group of lines as a scheduling unit, coordinating the results returned by the ATO, SMC, and non-SMC paths.
  • QUERY_SET_LINES — Retrieves the set of order lines associated with a configuration or scheduling request so they can be evaluated together.
  • SAVE_SCH_ATTRIBUTES — Persists the scheduling attributes (such as scheduled dates and ship dates) calculated during the scheduling run back onto the order lines.
  • DELETE_ATTRIBUTE_CHANGES — Removes or reverses previously recorded scheduling attribute changes, supporting re-scheduling and rollback scenarios.
  • UPDATE_RESERVATION — Updates reservation information in conjunction with the scheduling outcome for configured demand.
  • LOG_CONFIG_SCH_REQUEST — Writes diagnostics and audit information for configuration scheduling requests, supporting troubleshooting of scheduling failures.

Tables Accessed

The package operates against the core order line tables through APPS synonyms. OE_ORDER_LINES and its _ALL base synonym, OE_ORDER_LINES_ALL, are read and updated to obtain the configuration line identifiers, existing schedule dates, and to write back recalculated scheduling attributes. PLITBLM (the PL/SQL integer table synonym) is used as a PL/SQL bulk collection type for passing sets of line identifiers between the package's internal routines and the surrounding scheduling utilities, rather than as persistent storage.

Usage Notes

OE_CONFIG_SCHEDULE_PVT is invoked indirectly throughout the scheduling call stack. It is referenced by OE_SCHEDULE_UTIL, OE_GROUP_SCH_UTIL, OE_SCHEDULE_GRP, OE_DELAYED_REQUESTS_PVT, and OE_RSCH_SETS_CONC_REQUESTS, meaning it participates in both interactive Order Management form scheduling and batch scheduling performed by concurrent programs such as the scheduling and rescheduling concurrent requests. Custom code that needs configuration scheduling behavior should call the supported public scheduling utility or the OE_ORDER_PUB order API rather than this private package, since Oracle reserves the right to change PVT signatures between patch levels. The user search term "oe_schedule_util" confirms the common entry point: OE_SCHEDULE_UTIL is the public-facing utility that in turn depends on OE_CONFIG_SCHEDULE_PVT to complete configuration-level scheduling. Administrators diagnosing schedule failures on configured items should enable logging through the package's LOG_CONFIG_SCH_REQUEST path and inspect the order line records in OE_ORDER_LINES_ALL for consistent date and reservation values.