Search Results fnd_imp_filetypecount_vl




Overview
Explore in AI Chat

Overview

The FND_IMP_FILETYPECOUNT_VL view is a reporting object in the Oracle E-Business Suite Application Object Library (FND) product. It resides in the APPS schema and holds a VALID status in both Oracle EBS 12.1.1 and 12.2.2. The view aggregates upgrade impact data by counting how database objects of each file type fall into specific disposition categories, providing a summarized inventory of applied and pending changes associated with a given patch or bug fix.

In the context of Oracle EBS reporting and integration, FND_IMP_FILETYPECOUNT_VL is primarily a diagnostic and analysis construct rather than a transactional interface. It is used during patch application, upgrade assessment, and impact analysis workflows, where DBAs and technical consultants need to understand which file types are affected by a set of files and how many of those objects are new, upgradeable, or not yet applied. The view is also a searchable object for the keyword "file_type," reflecting the central role of the FILE_TYPE column in its definition.

Underlying Base Objects

The view is defined exclusively over a single base object documented as FND_IMP_PSMASTER2, which is exposed in the APPS schema as a synonym. FND_IMP_PSMASTER2 is part of the patch and upgrade file tracking infrastructure. It records the encountered files during patch processing along with a TYPEID classification describing each object's disposition.

FND_IMP_FILETYPECOUNT_VL does not exist as a stored table; it is a virtual view whose results are derived at query time. Because it aggregates its base data, it presents one row per unique combination of SNAPSHOT_ID, BUG_NO, PATCH_ID, and FILE_TYPE, with the HAVING clause filtering out any group that contains zero UPGRADE and zero NEW objects, ensuring only meaningful, actionable rows are returned.

Key Columns

  • SNAPSHOT_ID — Identifier of the snapshot under which the file type counts were captured, allowing comparison across points in time.
  • BUG_NO — The bug or patch reference number associated with the tracked files.
  • FILE_TYPE — The category of file being counted, such as SQL, PL/SQL, forms, or other object types. This is the column most commonly queried.
  • NOT_APPLIED — Sum of objects whose TYPEID equals 'NOT APPLIED', indicating files identified but not yet processed.
  • UPGRADE — Sum of objects whose TYPEID equals 'UPGRADE', indicating existing objects to be modified during the upgrade.
  • NEW — Sum of objects whose TYPEID equals 'NEW', indicating newly introduced objects.
  • PATCH_ID — Identifier of the patch to which the aggregated files belong.

Note the "_VL" suffix, which by convention indicates a translated or language-aware view variant.

Common Use Cases and Queries

Typical scenarios include assessing patch impact before applying it, comparing upgrade versus new object counts, and identifying file types that carry pending work. A representative query listing impact by file type is:

SELECT patch_id, bug_no, file_type, not_applied, upgrade, new
FROM   apps.fnd_imp_filetypecount_vl
WHERE  patch_id = :p_patch_id
ORDER  BY file_type;

To isolate patch-affected file types, query where NEW or UPGRADE exceeds zero, which the view guarantees anyway. To review pending work for a snapshot:

SELECT snapshot_id, file_type, SUM(not_applied) pending
FROM   apps.fnd_imp_filetypecount_vl
GROUP  BY snapshot_id, file_type
HAVING SUM(not_applied) > 0;

These queries support upgrade planning, verification of patch scope, and reconciliation between expected and observed object counts.