Search Results analyze_dependencies




Overview
Explore in AI Chat

Overview

FND_UMS_ANALYSIS_ENGINE is an APPS-owned PL/SQL package within the Oracle E-Business Suite Foundation (FND) layer, associated with the Oracle Utilities Management System (UMS) subsystem that supports the patching and bug-fix remediation infrastructure. Its principal business function is to perform analysis of dependency relationships among registered bug fixes and prerequisite patches, and to produce reporting output describing that dependency landscape. The package is classified as OTHER within the ETRM documentation, indicating that it is not published as a supported public API but is instead an internal engine consumed by other components of the UMS framework.

Because the package is documented as VALID in the 12.2.2 metadata, it is an active part of the database tier and is present in both Oracle EBS 12.1.1 and 12.2.2 environments, the latter of which is consistent with the Online Patching architecture that makes the UMS analysis engine relevant during patching cycles.

Key Procedures and Functions

The ETRM documentation lists four procedures and functions within the package. Names and purposes follow.

  • ANALYZE_DEPENDENCIES — Executes the core analysis of dependency relationships for the bug fixes and related objects tracked by UMS. It is the engine that resolves how fixes relate to one another and to prerequisite sets.
  • GET_PREREQ_LIST — Returns the list of prerequisites associated with a given analysis context or fix set, exposing the dependency chain determined during analysis.
  • GET_REPORT_COUNT — Returns a count of records that would be produced by the reporting routine, typically used to size or validate the report output before retrieval.
  • GET_REPORT — Returns the report dataset produced by the analysis engine, allowing callers to retrieve the formatted results of dependency analysis.

The package body is documented, and the package is referenced by itself, consistent with internal recursion in the analysis logic. No formal parameter lists are documented in the ETRM metadata; the above descriptions reflect conceptual purpose only.

Tables Accessed

The ETRM metadata lists the following tables referenced through APPS synonyms.

  • FND_UMS_BUGFIXES — The primary registry of bug fixes known to UMS; the engine reads this to identify the fixes subject to dependency analysis.
  • FND_UMS_BUGFIX_RELATIONSHIPS — Stores the relationships between fixes and their prerequisites; this is the core input for ANALYZE_DEPENDENCIES and GET_PREREQ_LIST.
  • AD_APPL_TOPS — The Applications topology table, used to resolve product installation locations and application context needed during analysis.

The metadata also lists DBMS_UTILITY and PLITBLM as referenced objects; these are standard Oracle-supplied utilities rather than application tables and support internal processing within the package body.

Usage Notes

FND_UMS_ANALYSIS_ENGINE is an internal component and is not intended for direct invocation by end users. It is typically invoked by the UMS framework itself, either from other PL/SQL callers within APPS or from concurrent programs that drive patch and bug-fix dependency reporting. Because the package is not documented as an API and exposes relatively low-level procedures such as ANALYZE_DEPENDENCIES and GET_REPORT, custom code should not depend on it directly; support boundaries and signatures are not guaranteed across releases. The ETRM metadata records that the package is referenced by no other packages in the documented dependency set, which further indicates that its consumers are runtime callers rather than packaged APIs, and that any integration should be treated as an internal implementation detail of the Oracle EBS patching infrastructure.