Search Results bom_copy_calendar




Overview
Explore in AI Chat

Overview

BOM_COPY_CALENDAR is an Oracle EBS PL/SQL package owned by the APPS schema and classified under the OTHER API category. Its purpose is to support the duplication and maintenance of manufacturing calendar definitions used by Oracle Bills of Material and Oracle Work in Process. Manufacturing calendars define the working and non-working days, shifts, and shift times that drive capacity planning, scheduling, and shop floor execution. Rather than requiring users to re-enter an entire calendar definition manually, this package provides the programmatic means to copy a calendar—or a specific range of shifts within a calendar—from a source identifier to a target identifier, including the associated exception sets, workday patterns, and shift exceptions.

The package was introduced under an early source header (BOMPCPCS.pls, version 115.1) and remains a documented object in ETRM 12.2.2. It is declared AUTHID CURRENT_USER, meaning that privilege and synonym resolution for referenced BOM tables occurs under the calling user's security context rather than the definer's.

Key Procedures and Functions

The package exposes three documented procedures:

  • COPY_CALENDAR — The primary procedure. It performs the actual copy operation, accepting a copy type, a source calendar code and target calendar code, a source shift number and target shift number, an exception set name, a start date, an end date, and a user ID. Its parameters allow either a whole-calendar copy or a scoped copy of selected shifts and date ranges, with the user ID typically captured for audit and concurrency tracking.
  • DROP_CAL_CANCELLED_EXCEPTS — A housekeeping procedure that removes cancelled calendar-level exception records. This supports cleanup of exception definitions that have been logically cancelled but not physically purged.
  • DROP_SHIFT_CANCELLED_EXCEPTS — The shift-level counterpart, removing cancelled shift exception records so that obsolete or superseded exceptions do not accumulate in the underlying tables.

No other public or private procedures are documented in the supplied metadata.

Tables Accessed

The package reads and writes the core BOM calendar tables through APPS synonyms:

Collectively these tables constitute the full manufacturing calendar model that the package clones and maintains.

Usage Notes

BOM_COPY_CALENDAR is typically invoked from the Oracle Bills of Material calendar maintenance forms or from custom concurrent programs and PL/SQL scripts that automate calendar rollout across organizations. It is not referenced by any other documented package, so callers interact with it directly. Because the package is AUTHID CURRENT_USER, custom code invoking it must ensure the calling schema has appropriate privileges on the underlying BOM tables. The DROP procedures are commonly scheduled as periodic cleanup jobs to prevent cancelled exception data from accumulating. When copying calendars, users should verify that target calendar and shift codes do not already exist, and that date ranges and exception set names are valid, since the procedure assumes well-formed input and does not itself validate naming collisions.