Search Results pa_schedule_glob




Overview
Explore in AI Chat

Overview

PA_SCHEDULE_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the "OTHER" API category. It serves as the core implementation package for managing project schedule data within the Oracle Projects (PA) module. Project schedules in EBS represent the time-phased breakdown of project work, resource assignments, and planned versus actual effort across schedule versions and date ranges. This package provides the foundational data manipulation routines that the higher-level public and private APIs rely upon to persist schedule records into the underlying base tables.

The package sits within a layered dependency hierarchy. It references PA_SCHEDULE_GLOB, a global variables package that holds package-level state shared across the schedule subprograms, along with the SYS.STANDARD library. It is itself referenced by PA_SCHEDULE_PKG (its own package body), PA_SCHEDULE_PUB (the public API layer), and PA_SCHEDULE_PVT (the private API layer). This arrangement indicates that PA_SCHEDULE_PKG performs the low-level transactional work, while the PUB and PVT packages expose validated, business-rule-enforced entry points to callers.

Key Procedures and Functions

ETRM documents eight procedures and functions in this package. The explicitly named entries are the three core DML procedures:

  • INSERT_ROWS — Creates new schedule records, inserting schedule detail rows into the base and translation tables. It is the entry point used when new schedule versions, date ranges, or schedule lines are added.
  • UPDATE_ROWS — Modifies existing schedule records, applying changes to previously created schedule data such as adjusted dates, quantities, or descriptive attributes.
  • DELETE_ROWS — Removes schedule records, supporting cleanup of obsolete schedule versions or lines and maintaining referential consistency with related schedule data.

The remaining documented entries are not individually described in the available metadata; they are referenced under the package's dependent-code listings rather than as named API routines. Callers should treat INSERT_ROWS, UPDATE_ROWS, and DELETE_ROWS as the primary documented interface, with the understanding that they are intended for internal use by the PUB and PVT layers rather than direct invocation from custom code.

Tables Accessed

The package operates against the following documented tables through APPS synonyms:

  • PA_SCHEDULES — The primary schedule table, storing schedule header and detail information. INSERT_ROWS, UPDATE_ROWS, and DELETE_ROWS perform their principal DML against this table.
  • PA_SCHEDULES_S — The multilingual translation table for schedule records. Writes to schedule data are typically mirrored here so that descriptive fields are available in each installed language.
  • PLITBLM — A generic PL/SQL index-by table type used within the package for bulk processing and array handling, supporting the set-based DML performed by the row procedures.

The use of the _S translation table confirms that this package follows standard EBS MLS (Multi-Language Support) patterns, and the use of PLITBLM indicates bulk bind processing for efficiency when large schedule sets are manipulated.

Usage Notes

PA_SCHEDULE_PKG is an internal implementation package, not a public API. In practice it is invoked indirectly: Oracle Projects forms and concurrent programs call PA_SCHEDULE_PUB or PA_SCHEDULE_PVT, which in turn delegate the actual row manipulation to PA_SCHEDULE_PKG. Custom integrations that need to create or modify project schedules should use the public API layer (PA_SCHEDULE_PUB) to obtain validation, security checks, and business-rule enforcement, rather than calling this package directly.

Because the package depends on PA_SCHEDULE_GLOB for shared state, any caller context must ensure that the global variables are initialized by the enclosing PUBLIC or PRIVATE layer before these routines are exercised. Direct DML through this package bypasses validations performed at higher layers and can leave PA_SCHEDULES and PA_SCHEDULES_S inconsistent if both are not maintained together. The package is marked VALID in the documented ETRM metadata for both 12.1.1 and 12.2.2, indicating it remains a supported and active component of the Oracle Projects scheduling architecture across both release lines.