Search Results p_autoschedule_flag

Overview

CHV_BUILD_SCHEDULES is a server-side PL/SQL package owned by the APPS schema and defined with AUTHID CURRENT_USER. It encapsulates the server-side logic of the Oracle E-Business Suite Supplier Scheduling APIs used to build supplier schedules. Its documented purpose is to generate the three schedule categories supported by Supplier Scheduling: planning schedules, shipping schedules, and inquiry schedules.

The package operates as the common build engine for Supplier Scheduling. It is invoked both from the Scheduler Workbench, where a user performs a manual schedule build, and from the AutoSchedule concurrent program (SRS process). Because both entry points converge on the same package, scheduling rules, horizon handling, and schedule numbering behavior remain consistent regardless of how the build is initiated. The header records the original source version as 115.4 (2002/11/26), consistent with the long-standing lineage of this component across EBS 11i, 12.1.1, and 12.2.2.

Key Procedures and Functions

The ETRM metadata identifies the documented program units as NAME and GET_SCHEDULE_NUMBER, with the package specification additionally declaring build_schedule and create_items. The excerpted comments describe the following:

• build_schedule — the primary schedule build procedure. It generates planning, shipping, and inquiry schedules and is the entry point used by both the Scheduler Workbench manual build and the AutoSchedule SRS process. Its parameter list is extensive and follows the package convention that all concurrent-program-supplied parameters are prefixed with p_, while locally declared variables are prefixed with x_. Documented inputs include the schedule category, the AutoSchedule flag, the AutoConfirm flag, schedule type and subtype, schedule number, horizon start date, bucket pattern, the include-future-releases indicator, MRP/MPS/DRP compile or schedule designators, ship-to organization, multi-org flag, and a set of optional selection parameters covering vendor, vendor site, category set, category, item, scheduler, buyer, and planner.
• get_schedule_number — a function that returns the schedule number to be assigned during a build, centralizing schedule number derivation so that manual and automatic builds do not collide.
• create_items — a supporting routine that creates or materializes the schedule item rows required for the generated schedules.
• NAME — a documented program unit listed in the package metadata, conventionally used to report the package or component name for diagnostics and logging.

Tables Accessed

The package reaches its data exclusively through APPS synonyms. The principal documented tables are:

• CHV_SCHEDULE_HEADERS and its intersections CHV_SCHEDULE_HEADERS_S and CHV_SCHEDULE_HEADERS_S2 — the header records for each generated schedule, holding schedule type, subtype, number, horizon, and status.
• CHV_SCHEDULE_ITEMS and CHV_SCHEDULE_ITEMS_S — the item-level schedule lines produced by the build, including bucket-level quantities.
• CHV_SCHEDULE_ORGANIZATIONS — determines which ship-to organizations participate in a build, supporting the multi-org flag.
• CHV_BUCKET_PATTERNS — supplies the bucket pattern used to lay quantities into time buckets.
• CHV_CUM_PERIODS — cumulative receipt periods used in supplier scheduling calculations.
• CHV_ITEM_ORDERS — item/order relationships considered when assembling schedule content.
• CHV_ORG_OPTIONS — organization-level Supplier Scheduling setup options that govern build behavior.
• MTL_ITEM_CATEGORIES and MTL_PLANNERS — item category assignments and planner definitions used to filter the selected items and planners.
• ECE_TP_HEADERS, ECE_TP_DETAILS, and ECE_OUTPUT_RUNS_S — trading partner and output-run data used when schedules are transmitted to suppliers through the e-commerce gateway.

Usage Notes

CHV_BUILD_SCHEDULES is not intended for direct ad hoc execution by end users. It is invoked from the Supplier Scheduling Scheduler Workbench when a user initiates a manual build, and from the AutoSchedule concurrent program for batch or scheduled builds. The AutoSchedule path is controlled by the AutoSchedule and AutoConfirm flags passed into build_schedule, which is the parameter most commonly referenced in troubleshooting and custom integration work.

The package is referenced by two other packages within the application, confirming its role as a shared build service rather than a terminal program. Custom code should call build_schedule rather than manipulating the underlying CHV_SCHEDULE_HEADERS and CHV_SCHEDULE_ITEMS tables directly, because the procedure enforces schedule numbering through get_schedule_number, applies bucket pattern and horizon logic, and maintains the ECE trading partner output records. Developers extending or debugging the build should preserve the package's parameter naming conventions and remain aware that the package executes with the privileges of the calling user (AUTHID CURRENT_USER).