Search Results ad_bugs_s

Overview

The APPS.AD_PATCH package body is a core component of the Oracle E-Business Suite patching and patch-tracking infrastructure, delivered as part of the AD (Application DBA) product family. Its business function is to record, evaluate, and manage the application of patches, bug fixes, and associated file copies against an EBS environment. The package provides the runtime logic that determines whether a given patch or code-line patch has already been applied, whether a specific file copy operation has occurred, and it persists state transitions for patches, bugs, and their associated actions.

In an EBS 12.1.1 or 12.2.2 environment the package underpins the metadata that Oracle's patching utilities, such as adpatch, and related tracking entities rely upon. It acts as a bridge between the physical patch application performed by the AutoPatch engine and the persistent records stored in the AD patch-tracking tables. The dependency metadata confirms a status of VALID and shows that AD_PATCH is referenced by two other packages, while it depends on a broad set of AD dictionary and snapshot objects.

Key Procedures and Functions

The ETRM documentation records ten procedures and functions within this package. The principal entry points include:

• IS_PATCH_APPLIED — Determines whether a specified patch has already been applied to the current environment, returning the result for use by patching logic.
• IS_CODELINE_PATCH_APPLIED — Establishes whether a code-line level patch (a patch applied on a specific codeline) has been recorded as applied.
• IS_FILE_COPIED — Reports whether a particular file has been copied as part of a patch application, supporting file-version reconciliation.
• MARK_PATCH_SUCC — Records a successful completion state for a patch, updating the patch tracking records accordingly.
• MARK_BUG_SUCC — Persists the successful application state for an individual bug fix associated with a patch.
• SET_PATCH_STATUS — Assigns or updates the status of a patch within the patch run tracking structures.
• GETAPPLTOPID — Retrieves the application top identifier for a given application, resolving the APPL_TOP context used during patching.
• COMPARE_VERSIONS — Compares file or object versions, enabling the package to determine whether a file copy is required or whether a version mismatch exists.

These routines collectively support both the query side (has this been applied?) and the write side (mark this as applied) of patch tracking.

Tables Accessed

The package references the following tables via APPS synonyms, as documented:

• AD_APPL_TOPS — Resolves application top identifiers used to locate files.
• AD_BUGS and AD_BUGS_S — Store bug fix definitions and their translated (seed) rows, used to associate fixes with patches.
• AD_FILES and AD_FILE_VERSIONS — Hold file definitions and version history, supporting file copy and version comparison logic.
• AD_PATCH_RUNS, AD_PATCH_RUN_BUGS, and AD_PATCH_RUN_BUG_ACTIONS — Record patch run executions, the bugs within each run, and the actions performed, forming the core tracking structures updated by the MARK and SET procedures.
• AD_SNAPSHOTS, AD_SNAPSHOT_BUGFIXES, AD_SNAPSHOT_BUGFIXES_S, and AD_SNAPSHOT_FILES — Maintain snapshot baselines of bug fixes and files used to detect changes and support version comparison.
• AD_TRACKABLE_ENTITIES — Identifies entities subject to patch tracking.
• FND_PRODUCT_GROUPS — Supplies product group context for the environment.

References to DUAL, DBMS_STANDARD, and STANDARD reflect standard PL/SQL constructs.

Usage Notes

AD_PATCH is internal infrastructure rather than an end-user API. It is invoked primarily by the AutoPatch engine and by dependent AD packages during patch application and driver processing. Because the ETRM record shows the package is referenced by two other database objects, those dependents rely on its procedures when orchestrating patch runs and status updates.

Customers and integrators generally do not call AD_PATCH directly; custom code should treat it as Oracle-maintained and subject to change across releases. Diagnostic queries against the AD patch-tracking tables are the usual way to inspect the states this package writes. Any reference to AD_BUGS_S — the seed table searched by the user — occurs through this package's bug fix resolution logic.