Results for “bug_no”

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

Overview

FND_IMP_PFILEINFO_VL is a database view owned by the APPS schema in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It belongs to the FND — Application Object Library product family, which provides the foundational infrastructure for the entire EBS technology stack, including concurrent processing, patching utilities, and the Oracle Universal Message System (UMS). This view exposes consolidated information about bug fixes, their associated file versions, and the patch records that delivered them. Its primary role is to serve the Oracle Applications patching and file-version metadata framework, allowing administrators, support engineers, and diagnostic utilities to correlate bug numbers with specific file version GUIDs and the patches that carry them. Rather than serving as a general business reporting object, it functions as a technical metadata view supporting patch management, bug-fix tracking, and file-version verification activities.

Underlying Base Objects

The view is defined over three synonymous base objects documented in the ETRM metadata: AD_PM_PATCHES, FND_UMS_BUGFIXES, and FND_UMS_BUGFIX_FILE_VERSIONS. Each corresponds to a distinct layer of the patching metadata model. FND_UMS_BUGFIXES stores bug-fix definitions, including the bug number, baseline, and bugfix GUID. FND_UMS_BUGFIX_FILE_VERSIONS stores the file-level detail, mapping a bugfix GUID to a specific file version GUID. AD_PM_PATCHES is the Applications DBA patch-management table holding patch identifiers and their associated bug numbers and baselines. The view joins these three sources: it links FND_UMS_BUGFIXES to FND_UMS_BUGFIX_FILE_VERSIONS on BUGFIX_GUID, and links FND_UMS_BUGFIXES to AD_PM_PATCHES where both BUG_NUMBER and BASELINE match. This composite join produces a de-normalized record set associating each bugfix file version with its originating patch.

Key Columns

• BUG_NO — sourced from A.BUG_NUMBER in FND_UMS_BUGFIXES; the bug or defect number that the fix addresses. It is also the join key to AD_PM_PATCHES.
• FILEID — sourced from B.FILE_VERSION_GUID in FND_UMS_BUGFIX_FILE_VERSIONS; the globally unique identifier (GUID) of the specific file version delivered by the bugfix. This identifies exactly which version of a file the fix provides.
• PATCH_ID — sourced from C.PATCH_ID in AD_PM_PATCHES; the identifier of the patch that carries this bugfix, enabling traceability from a file version back to a deployable patch.

Common Use Cases and Queries

Typical uses include determining which patch delivered a given file version, auditing which bug numbers are covered by a patch, and verifying that expected file versions are present after patching. Because the view is a technical metadata object, queries are generally run by DBAs, support personnel, or diagnostic scripts.

• Retrieve all file versions associated with a specific bug:

  SELECT bug_no, fileid, patch_id
  FROM   apps.fnd_imp_pfileinfo_vl
  WHERE  bug_no = :bug_number;

• Identify all bugs and file versions delivered by a patch:

  SELECT bug_no, fileid
  FROM   apps.fnd_imp_pfileinfo_vl
  WHERE  patch_id = :patch_id;

• Confirm traceability across the full chain:

  SELECT bug_no, fileid, patch_id
  FROM   apps.fnd_imp_pfileinfo_vl
  ORDER BY patch_id, bug_no;

Because the view resolves joins across UMS bugfix tables and AD patch metadata, it should be queried with the APPS schema context and appropriate privileges. In 12.2.2, the Online Patching (adop) architecture continues to rely on this class of metadata to reconcile file versions during patching cycles.