Search Results debug_stats

Overview

FND_OAM_UMS_LOADER is an Oracle EBS Applications Technology (ATG) package body owned by APPS and used by the Oracle Applications Manager (OAM) Update Management Service (UMS). Its principal business function is to load, upload, and reconcile Oracle bug fix metadata into the EBS environment. The package parses downloaded bugfix containers, relates them to products and installations, and populates the FND_UMS_* tables that underpin the "Bug Fixes" and patching views available through OAM. In EBS 12.1.1 and 12.2.2 the package remains an internal, unsupported API; it is not intended for direct customer invocation outside the supported OAM and patching tooling.

Key Procedures and Functions

• SET_DEBUGGING — Controls the diagnostic verbosity used throughout the package, toggling between the debug modes declared as DEBUG_OFF, DEBUG_ON, DEBUG_STATS, and DEBUG_ABORT.
• UP_FND_UMS_BUGFIX — Primary orchestration entry point for uploading bug fix information for a single bug into the UMS repository; it validates the incoming file data against existing database content and raises documented errors such as ERROR_UNKNOWN_UPLOAD_PHASE and ERROR_ABORT when rules such as "database data is at least as complete as file data" apply.
• UP_FND_UMS_BUGFIX_FILE — Loads the file-level records associated with a bug fix, populating file and file-version information used by the UMS loader.
• UP_FND_UMS_BUGFIX_RELATIONSHIP — Loads prerequisite, include, and link relationships between bug fixes, honouring the PIL_LEVEL_NONE, PIL_LEVEL_PREREQS_INCLUDES, and PIL_LEVEL_LINKS level constants.
• UP_FND_UMS_ONE_BUGFIX — Processes a single bug fix record end to end, applying the forced-bugfix lookup collection type and the abort/date rules defined in the package body.
• UP_FND_UMS_BUGFIXES — Batch driver that iterates over multiple bug fixes, invoking the single-bug logic per record.
• NEWLINE — Returns the platform-appropriate line separator (g_newline) used when generating loader output and diagnostic messages.

Tables Accessed

• FND_UMS_BUGFIXES, FND_UMS_BUGFIX_FILE_VERSIONS, FND_UMS_BUGFIX_RELATIONSHIPS — Core UMS bugfix repository tables read and written by the UP_FND_UMS_* procedures.
• FND_UMS_FILES, FND_UMS_FILE_VERSIONS — Store file-level and version-level content for each loaded bug fix.
• FND_ORACLE_USERID, FND_PRODUCT_INSTALLATIONS — Provide Oracle user and product installation context used during upload processing.
• DBA_TABLES — Queried to determine whether UMS tables require analysis, based on TABLE_ANALYZE_PERIOD (28 days) and TABLE_ANALYZE_PERCENTAGE (5%).
• DBMS_LOCK, DBMS_UTILITY — Invoked for serialisation and utility routines, including invocation of the lock_entity behaviour governed by G_LOCK_LIFETIME (24 hours) and G_LOCK_WAITTIME (5 minutes).
• DUAL — Used for singleton queries such as the default date (g_default_date) and time-mask formatting.

Usage Notes

The package is invoked indirectly by OAM and the patching infrastructure rather than by end users. Operators trigger bugfix uploads through the OAM Update Management interface or through supporting concurrent programs on EBS 12.1.1 and 12.2.2. The package relies on string lock entities derived from the bug number and uses DBMS_LOCK to enforce mutual exclusion; failures to acquire a lock surface as ERROR_UNABLE_TO_LOCK (-20003). Because APPS.FND_OAM_UMS_LOADER is documented as API classification OTHER and referenced by no other packages, it should be treated as an internal implementation detail. Custom development should not call these procedures directly; upgrades may change signatures or remove them without notice.