Search Results up_fnd_ums_bugfixes

Overview

FND_UMS_LOADER is an Oracle E-Business Suite internal PL/SQL package owned by the APPS schema that implements the loader layer of the Oracle Universal Module Specification (UMS) framework. UMS provides the metadata and file-versioning backbone used by Oracle Applications patch delivery, enabling the E-Business Suite to record which bugfixes, patchsets, and internal patches exist, how they relate to one another, and which files and file versions each one delivers. The package is declared AUTHID CURRENT_USER, so its SQL executes with the privileges of the calling user, and it is classified as OTHER in the ETRM API catalogue.

The specific user search term "up_fnd_ums_bugfixes" corresponds directly to the UP_FND_UMS_BUGFIXES procedure documented in this package. The package is not intended for end-user or customer extension; it exists to populate and maintain the UMS repository tables during patch application and patch metadata loading.

Key Procedures and Functions

• SET_DEBUGGING — Sets the package-level debug flag (for example 'Y' or 'N') controlling diagnostic output during load operations.
• UP_FND_UMS_BUGFIX — Uploads or refreshes a single bugfix record into the UMS repository.
• UP_FND_UMS_BUGFIX_FILE — Uploads file-level metadata associated with a bugfix, populating the file and file-version records.
• UP_FND_UMS_BUGFIX_RELATIONSHIP — Uploads relationships between bugfixes, such as prerequisites, includes, replacements, and their indirect variants.
• UP_FND_UMS_ONE_BUGFIX — Handles the load of one bugfix entity, typically invoked as a unit-of-work helper by the bulk procedure.
• UP_FND_UMS_BUGFIXES — The bulk entry point that drives the upload of multiple bugfixes and their associated files and relationships.
• NEWLINE — A utility function returning a newline character sequence used when composing UMS metadata output.

The package also declares public constants defining bugfix types (BUGFIX, PATCHSET, INTERNAL), relationship types (PREREQS, INDIRECTLY_PREREQS, INCLUDES, INDIRECTLY_INCLUDES, REPLACED_BY, REPLACES, REPLACED_BY_FIRST_NON_OBSOLETE), and download modes (NONE, FILES_ONLY, REPLACEMENTS_ONLY, REPLACEMENTS_FILES, PREREQS_ONLY, PREREQS_FILES, LINKS_ONLY, LINKS_FILES).

Tables Accessed

• FND_UMS_BUGFIXES — Master bugfix/patchset records written by the UP_FND_UMS_BUGFIX routines.
• FND_UMS_BUGFIX_FILE_VERSIONS — Maps bugfixes to the specific file versions they deliver.
• FND_UMS_BUGFIX_RELATIONSHIPS — Stores prerequisite, include, and replacement relationships between bugfixes.
• FND_UMS_FILES and FND_UMS_FILE_VERSIONS — File and version catalogues referenced when resolving delivered files.
• FND_ORACLE_USERID, FND_PRODUCT_INSTALLATIONS — Installation and database-user context used to scope loads.
• DBA_TABLES, DBMS_LOCK, DBMS_UTILITY — Used for object existence checks, concurrency serialization, and utility routines such as formatting and error retrieval.

Usage Notes

FND_UMS_LOADER is invoked internally rather than through a standard concurrent program or form. It is called during patch application and UMS metadata refresh cycles, and it is referenced by two other packages in the ETRM inventory, confirming its role as a shared loader service. Debug output is enabled via SET_DEBUGGING before bulk loads to aid diagnosis. Because the package is undocumented for customer use and its header carries an noship designation, it should not be called directly from custom code; any extension should instead rely on supported patch and AD utilities.