Results for “bug_list”
6 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
AD_UMS_ENGINE_RESULTS is a table owned by the APPLSYS schema in Oracle E-Business Suite, registered under the Applications DBA (AD) product family. Its documented purpose is to store the results of the UMS (Unified Matching Service or Upgrade Management Service, depending on release context) environment analysis. In practice the table captures, per application tier node (APPL_TOP), the outcome of running the UMS engine against a given release level, together with the set of patches or bugs the engine identified or applied for that run. It is therefore an operational metadata table used by AD utilities and upgrade/diagnostics tooling rather than an end-user or transactional business table.
From a Data Vault modeling perspective, the mined metadata classifies this object as standalone — that is, no downstream tables reference it and only a single outbound foreign key exists. A heuristic modeling suggestion would treat it as a satellite attached to the AD_APPL_TOPS hub: the APPL_TOP_ID and RELEASE_NAME together form a natural (business) key that keys the descriptive attributes (STATUS, BUG_LIST, audit columns) describing the analysis for that node and release. It is not a link table, since it resolves to one parent.
Key Information Stored
The documented physical schema for 12.2.2 comprises eight columns:
- APPL_TOP_ID — Foreign key to AD_APPL_TOPS; identifies the application tier file system (node) whose environment was analyzed.
- RELEASE_NAME — The release or patch-set level against which the UMS engine performed its analysis (e.g., a specific EBS release identifier).
- BUG_LIST — The list of bug or patch identifiers relevant to the analysis result for that node and release. This is the substantive payload of the row.
- STATUS — The outcome state of the UMS engine run (for example whether the environment was compliant, needed action, or failed).
- CREATED_BY / CREATION_DATE — Standard EBS WHO-column audit trail recording who created the row and when.
- LAST_UPDATED_BY / LAST_UPDATE_DATE — Standard WHO-column audit trail recording the last modification user and timestamp.
With only eight columns, the table has no separate surrogate primary key beyond its unique index. The documented unique index AD_UMS_ENGINE_RESULTS_U1 covers (BUG_LIST, APPL_TOP_ID, RELEASE_NAME), making this combination the business-key candidate that guarantees one result row per node, release, and bug list. The APPL_TOP_ID to AD_APPL_TOPS foreign key is the sole documented referential relationship.
Common Use Cases and Queries
Typical usage centers on diagnostics and reporting around environment readiness. A DBA may query the table to determine which APPL_TOP nodes have outstanding bugs for a target release:
- Joining to AD_APPL_TOPS to translate APPL_TOP_ID into a human-readable node name and path.
- Filtering by RELEASE_NAME to see all environments analyzed for a given upgrade target.
- Filtering by STATUS to isolate nodes that failed or require remediation.
- Examining BUG_LIST to correlate required patches with the AD patch inventory.
A representative pattern is: SELECT a.APPL_TOP_ID, t.NAME, a.RELEASE_NAME, a.STATUS, a.BUG_LIST FROM APPLSYS.AD_UMS_ENGINE_RESULTS a JOIN APPLSYS.AD_APPL_TOPS t ON t.APPL_TOP_ID = a.APPL_TOP_ID WHERE a.RELEASE_NAME = :release AND a.STATUS <> 'COMPLETE' ORDER BY t.NAME. Reporting use cases include readiness dashboards, patch-compliance summaries, and historical trend analysis using the audit date columns.
Related Objects
- AD_APPL_TOPS — The parent of the documented foreign key (AD_UMS_ENGINE_RESULTS.APPL_TOP_ID → AD_APPL_TOPS); the primary join partner for node-level context.
- AD_APPL_TOP — The session/context view or synonym family for the current application tier, often used to resolve the active APPL_TOP in queries.
- AD_PATCH_RUN_BUGS / AD_BUGS — Patch and bug registry tables useful for resolving BUG_LIST entries to patch details.
- AD_PATCH_DRIVER_MIN_PATCHES — Minimum patch requirements that UMS-style analysis frequently validates against.
- AD_ZDLRA_RESULTS — Companion AD result/metadata table following a similar per-node result pattern.
- FND_NODES — Node inventory providing host and tier context for APPL_TOP-based joins.
Because the Data Vault classification is standalone, no dependent child tables exist; the object is consumed as a leaf reporting and diagnostics source.
-
Stores the results of the UMS environment analysis
-
eTRM - AD Tables and Views 12.2.2
Oracle Applications products installed at your site