Search Results chv_schedule_items_s

Overview

APPS.CHV_BUILD_SCHEDULES is a valid PL/SQL package body in the Oracle E-Business Suite Applications schema. It belongs to the CHV product family, which governs supplier scheduling and the creation of planning, release, and authorization schedules within Oracle Purchasing and the Advanced Supply Chain Planning scheduling flows. Its principal business purpose is to construct the schedule records that drive supplier communication: given an organization, supplier, and scheduling context, the package assembles schedule headers, schedule lines, buckets, cumulative period data, and the item-level authorization detail required for release to trading partners through the EDI/ECE gateway.

The status of the package is VALID in both EBS 12.1.1 and 12.2.2, and the 12.2.2 metadata classifies it as an OTHER object rather than a formal public API. It is not referenced by any database object, indicating that it is invoked at runtime rather than through declarative dependency chains. Configured reference documentation records four callable entry points, including NAME and GET_SCHEDULE_NUMBER.

Key Procedures and Functions

The documented callable surface is deliberately small. Only two names are exposed in the metadata:

• NAME — a package-level identifier routine that returns the name of the schedule or schedule entity being processed, used internally for messages, logging, or header derivation.
• GET_SCHEDULE_NUMBER — returns the schedule number assigned to a given schedule context. This is the primary public accessor used by downstream scheduling and confirmation logic to obtain a valid schedule reference before writing items, buckets, or cumulative periods.

Beyond these, the package body contains internal subprograms that orchestrate bucket creation, cumulative period derivation, authorization generation, order loading, and confirmation handling. These are reflected by the dependency list, which shows self-references to CHV_CREATE_BUCKETS, CHV_CREATE_AUTHORIZATIONS, CHV_CONFIRM_SCHEDULES, and CHV_LOAD_ORDERS. Parameter lists are not documented and must not be assumed.

Tables Accessed

The package reads and writes the core CHV scheduling tables, all accessed through APPS synonyms:

• CHV_SCHEDULE_HEADERS, _S, _S2 and CHV_SCHEDULE_ITEMS, _S — the primary schedule header and line entities. The user search term chv_schedule_items_s corresponds directly to the schedule items synonym referenced here. These tables receive the constructed schedule output.
• CHV_SCHEDULE_ORGANIZATIONS — defines which inventory organizations participate in the schedule build.
• CHV_BUCKET_PATTERNS and CHV_CUM_PERIODS, _S2 — supply the bucket and cumulative period definitions used to shape the schedule horizon.
• CHV_ITEM_ORDERS and CHV_ORG_OPTIONS — item-level demand and organization scheduling options.
• MTL_ITEM_CATEGORIES, MTL_PLANNERS, MTL_SYSTEM_ITEMS, MTL_UNITS_OF_MEASURE, ORG_ORGANIZATION_DEFINITIONS — item master, planner, UOM, and organization validation data.
• PO_HEADERS, PO_LINES, PO_VENDORS, PO_VENDOR_SITES, PO_VENDOR_SITES_ALL, PO_ASL_DOCUMENTS, PO_ASL_ATTRIBUTES_VAL_V — purchasing document and approved supplier list context.
• ECE_TP_HEADERS, ECE_TP_DETAILS, ECE_OUTPUT_RUNS_S — trading partner and EDI output run information for schedule transmission.
• FND_GLOBAL, FND_MESSAGE, FND_PROFILE, FND_REQUEST and DUAL — environment, message, profile, and concurrent request support.

Usage Notes

CHV_BUILD_SCHEDULES is invoked during supplier scheduling runs, typically through the concurrent programs that generate planning and release schedules for a supplier and organization combination. It is called from companion packages — the metadata records that it is referenced by two other packages — such as the schedule confirmation and load order routines. Because it is not a registered API and has no external dependents, custom code should not call it directly; instead, integration should use the supported CHV schedule APIs or the concurrent manager entry points. The _S and _S2 synonyms indicate multi-org and possibly partition-aware access, so all calls operate under a validated FND_GLOBAL organization context. Developers reviewing or debugging schedule generation should treat the package as internal implementation, while noting that CHV_SCHEDULE_ITEMS_S is the alias ultimately populated by this logic.