Search Results pa_schedule_pvt




Overview
Explore in AI Chat

Overview

PA_SCHEDULE_GLOB is a global constants and reference-data package in the Oracle Projects (PA) module of Oracle E-Business Suite, owned by the APPS schema and shipped in a VALID state in both 12.1.1 and 12.2.2. Its name and dependency footprint identify it as the shared "globals" layer for the project scheduling subsystem: it centralizes literal values, lookup codes, and enumerated constants that the scheduling, calendaring, duration, and forecasting packages reference instead of hard-coding them individually. This design isolates site-independent values in a single compilation unit, so scheduling logic reused across the schedule workbench, forecast generation, and exception handling remains internally consistent.

The ETRM documentation classifies the package as API classification OTHER, reflecting that it is an internal implementation dependency rather than a public, supported integration API. It exposes no documented procedures or functions and references only the SYS.STANDARD package, confirming that its content is declarative — package-level constants, subtypes, and simple initialization logic — with no direct SQL access against application tables.

Key Procedures and Functions

The ETRM metadata for PA_SCHEDULE_GLOB documents zero procedures or functions. The package specification and body are therefore composed of global declarations rather than callable program units. In Oracle Projects, packages bearing the _GLOB suffix typically publish constants for schedule status codes, exception category identifiers, calendar and duration type indicators, and date-boundary values used when computing working-day intervals. Consumers reference these declarations directly in their own PL/SQL, which explains why no procedure-level documentation exists.

Because no parameterized entry points are documented, the package should not be treated as an invocable API. Any customization that calls into PA_SCHEDULE_GLOB must rely on the shipped constant names and must be regression-tested during patching, since Oracle does not guarantee the stability of undocumented globals across releases or patch levels.

Tables Accessed

No tables are referenced by PA_SCHEDULE_GLOB through APPS synonyms, and the only listed dependency is SYS.STANDARD. This is consistent with a pure constants package: it performs no DML and no queries, and therefore holds no table-level privileges beyond those inherited from the APPS schema. All persistence for scheduling data — calendars, schedule definitions, exceptions, and forecast items — resides in the database objects owned by the dependent packages rather than in this globals unit.

Usage Notes

PA_SCHEDULE_GLOB is referenced by ten documented packages, including PA_SCHEDULE_PKG, PA_SCHEDULE_PUB, PA_SCHEDULE_PVT, PA_SCHEDULE_UTILS, PA_CALENDAR_UTILS, PA_DURATION_UTILS, PA_FORECASTITEM_PVT, PA_FORECAST_GRC_PVT, PA_SCH_EXCEPT_PKG, and PA_SCH_EXCEPT_HIST_PKG. Notably, the user search term "pa_schedule_pvt" appears in this dependency list, confirming that PA_SCHEDULE_PVT — the private scheduling implementation layer — depends on the globals package for its constant definitions.

The package is never invoked directly by an Oracle Forms screen or concurrent program. Instead, it is compiled into the dependency chain of the scheduling and forecasting APIs and is loaded implicitly whenever those packages execute. A common operational consequence is invalidation cascades: recompiling PA_SCHEDULE_GLOB invalidates all ten dependent packages, so DBAs should recompile the scheduling package set after any change to it. Custom code that duplicates scheduling constants should be aligned with the values published here to avoid behavioral drift from standard Oracle Projects functionality.