Search Results ad_releases_pvt




Overview
Explore in AI Chat

Overview

AD_RELEASES_PVT is a private PL/SQL package in the APPS schema that supports the Oracle E-Business Suite Applications Database (AD) product. Its role is to encapsulate the insert logic for release definitions within the AD_RELEASES and AD_RELEASES_S tables. Releases in the AD schema describe the application patch levels made available to an E-Business Suite environment — for example, the major and minor version combinations that correspond to consolidated updates distributed on physical media or delivered electronically. The package carries an AUTHID CURRENT_USER declaration, meaning that it executes with the privileges of the calling user rather than the defining user, a common design pattern in AD utilities where the invoker is an administrative account such as SYSTEM or APPLSYSPUB operating under the APPS schema context. The $Header revision string indicates a file whose last significant revision occurred in 2004, consistent with the package being part of the stable, long-lived infrastructure that spans the 11i and R12 (12.1.1 / 12.2.2) code lines. Because the API classification is PVT, the package is not intended as a public integration point; it exists to serve other AD components that need to register or record release metadata.

Key Procedures and Functions

One documented program unit is exposed by the specification:

  • CreateRelease — Inserts a release record into the AD release tables. Based on the documented parameter metadata, it accepts a major version, a minor version, and a tape version, together with a source comments string, a base release flag, a start date, an optional end date (defaulting to null), and the creating user identifier. It returns the newly generated release identifier through an OUT parameter so that the caller can subsequently reference the created row. No other procedures or functions are documented for this package.

Tables Accessed

The ETRM metadata records three tables referenced through APPS synonyms:

  • AD_RELEASES — the primary table holding release header information; CreateRelease writes the new release row here.
  • AD_RELEASES_S — the corresponding translated or shadow table populated alongside the base table, preserving release descriptive text in the standard AD patterns.
  • DUAL — used for single-row selection, typically to obtain a sequence next value or to evaluate expressions necessary before insertion.

Read access in the release resolution path is implicit in the version parameters passed to CreateRelease; the procedure itself is oriented toward insert activity rather than query activity.

Usage Notes

Because AD_RELEASES_PVT is a private package, it is not intended for direct invocation by customer-written concurrent programs or forms. It is referenced by two other AD packages, which are the actual entry points invoked during release registration and release maintenance activities. Typical contexts in which the underlying functionality is exercised include the AD administration utilities used during patching and upgrade operations, and any internal AD routine that must establish a baseline release definition before applying patches. In Oracle E-Business Suite 12.1.1 and 12.2.2, the online patching architecture introduced in 12.2 changes the physical file system layout but does not alter the fundamental role of the AD release tables; release metadata remains a prerequisite for determining which patches are applicable to a given environment. Custom code should not call CreateRelease directly, since doing so bypasses any validation or sequencing logic applied by its parent wrappers. Administrators investigating release-related data should query AD_RELEASES and AD_RELEASES_S, and developers seeking an integration point should locate the two calling packages identified in the dependency metadata rather than binding to this private specification.