Results for “request_set_id”

2 results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AD_PA_ANALYSIS_RUN_BUGS is an Oracle Applications DBA (AD) repository table owned by the APPLSYS schema. It stores the list of bugs identified as a result of a patch analysis criteria run — the diagnostic process that evaluates an E-Business Suite environment against known issues and prerequisites before or after applying patches. Each row represents a specific bug detected for a given analysis run and APPL_TOP combination, together with metadata describing its severity, current analysis status, and the recommended remediation.

The table operates as a child of the analysis run framework, partitioned logically by ANALYSIS_RUN_ID. Its foreign key to AD_APPL_TOPS (via APPL_TOP_ID) ties each detected bug to a specific application tier file system, enabling environment-specific results. Based on the mined FK structure, the table is flagged as standalone under the heuristic Data Vault classification. This suggests a modeling approach where the object behaves as a hub-like or satellite-like structure keyed on the run and bug combination, rather than a classic associative link table. The classification is heuristic only and should be validated against the full criteria analysis schema.

Key Information Stored

The table contains 15 documented columns. The most significant are:

  • ANALYSIS_RUN_ID — Identifier of the parent criteria analysis run; the primary grouping key for all bugs detected in a single execution.
  • ANALYSIS_RUN_BUG_ID — Surrogate primary key uniquely identifying each detected bug record.
  • BUG_NUMBER — The Oracle bug or issue number returned by the analysis; a core business-key element.
  • BASELINE — Indicates whether the bug applies to the baseline (delivered) code level; part of the unique index.
  • APPL_TOP_ID — Foreign key to AD_APPL_TOPS, identifying the application tier where the bug was detected.
  • IS_HIGH_PRIORITY — Flag indicating whether the analysis classified the bug as high priority.
  • ANALYSIS_STATUS — Current state of the bug within the run (e.g., open, reviewed, resolved).
  • RECOMMENDED_PATCH_TYPE — The patch category recommended to remediate the issue.
  • PRODUCT_ABBREVIATION — Product short name associated with the affected code.
  • HAS_MSI_STEPS — Indicates whether the analysis identified Manual Setup Instructions (MSI) steps.
  • REQUEST_SET_ID — Links the bug to an associated request set used during analysis.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — Standard audit columns.

The unique index AD_PA_ANALYSIS_RUN_BUGS_U1 on (ANALYSIS_RUN_ID, BUG_NUMBER, BASELINE) is the documented business-key candidate, distinguishing the surrogate ANALYSIS_RUN_BUG_ID from the natural business key.

Common Use Cases and Queries

Typical usage centers on patch analysis reporting and remediation tracking. DBAs query this table to list all bugs detected in a run, filter high-priority issues, or determine which APPL_TOP is affected.

  • Listing high-priority bugs for a run: SELECT BUG_NUMBER, PRODUCT_ABBREVIATION, ANALYSIS_STATUS FROM AD_PA_ANALYSIS_RUN_BUGS WHERE ANALYSIS_RUN_ID = :run_id AND IS_HIGH_PRIORITY = 'Y';
  • Joining to AD_APPL_TOPS to resolve the application tier: SELECT b.BUG_NUMBER, a.APPL_TOP_NAME FROM AD_PA_ANALYSIS_RUN_BUGS b JOIN AD_APPL_TOPS a ON b.APPL_TOP_ID = a.APPL_TOP_ID;
  • Counting bugs per product across runs for trend reporting.
  • Identifying bugs with MSI steps (HAS_MSI_STEPS = 'Y') that require manual intervention.
  • Filtering by RECOMMENDED_PATCH_TYPE to plan patch cycles.

Related Objects

  • AD_APPL_TOPS — Referenced via APPL_TOP_ID; the parent application tier definition.
  • AD_PA_ANALYSIS_RUNS — Parent analysis run header (by ANALYSIS_RUN_ID), the logical driver of each bug list.
  • AD_PA_ANALYSIS_CRITERIA — Criteria definitions evaluated during the run.
  • AD_BUGS — Cross-reference for bug detail and patch information.
  • AD_PATCH_RUN_BUGS — Sibling table recording bugs encountered during patch application, useful for reconciliation.
  • FND_REQUEST_SETS — Referenced indirectly through REQUEST_SET_ID for analysis job context.

Together these objects form the criteria-driven analysis and remediation reporting chain within the AD product.