Search Results action_required

Overview

FND_IMP_AFFECTEDFILES_VL is a validation-level (VL) database view owned by the APPS schema in Oracle E-Business Suite. It belongs to the FND – Application Object Library product and is classified as VALID in the ETRM repository for both release 12.1.1 and 12.2.2. The view exposes the set of Java Server Page (JSP) files that are affected when an Oracle patch or patch snapshot is applied to an EBS environment, together with an indication of the remediation action that the administrator or DBA must perform. The name AFFECTEDFILES reflects its purpose: to enumerate dependent JSP artifacts whose parent container has changed as a result of an applied patch, so that those pages can be regenerated or recompiled.

The view is primarily consulted during patch analysis and post-patch validation activities. Unlike a simple metadata listing, it derives its rows by correlating patch master records, patch dependency relations, and dependent object definitions. The presence of the literal ACTION_REQUIRED column set to the constant value 'RECOMPILE' means the view is designed to emit a prescriptive instruction for each affected file rather than a purely descriptive listing. This makes it a convenient driver for automated remediation scripts and for patch-impact reporting.

Underlying Base Objects

The view is defined over three documented base objects, all exposed through APPS synonyms in the EBS data dictionary:

• FND_IMP_PSMASTER2 (aliased A) — the patch master table holding applied patch and file information, including BUG_NO, SNAPSHOT_ID, APP_SHORT_NAME, DIRECTORY, FILENAME, TYPEID, FILE_TYPE and PATCH_ID.
• FND_IMP_DEPOBJECTS (aliased P) — dependent object definitions supplying the parent object's APP_SHORT_NAME, FILE_DIRECTORY and FILENAME, joined via OBJECT_ID.
• FND_IMP_DEPRELATIONS (aliased R) — the dependency relation table linking parent and child objects through SNAPSHOT_ID, DEPENDENCY_TYPE, CHILD_OBJECT_NAME, CHILD_APP_SHORT_NAME and PARENT_OBJECT_ID.

Tracing the SQL shows that the view is effectively a restricted join: the child object name is reconstructed as A.DIRECTORY || '/' || A.FILENAME and matched against the dependency relation, while only rows with DEPENDENCY_TYPE = 'JSP_INCLUDE' and FILE_TYPE = 'JSP' survive the filter. Rows where TYPEID = 'NOT APPLIED' are excluded, so only files whose patch status reflects an actual application are reported.

Key Columns

• BUG_NO / PATCH_ID / SNAPSHOT_ID — identify the originating patch, the patch record and the snapshot context of the affected file.
• DEP_APP_SHORT_NAME, DEP_DIRECTORY, DEP_FILENAME — the dependent (parent) JSP file coordinates that drive the JSP_INCLUDE relation.
• PATCHED_APP_SHORT_NAME, PATCHED_DIRECTORY, PATCHED_FILENAME — the patched child object, i.e. the file actually delivered or altered by the patch.
• TYPEID — patch application status; the view filters out the value 'NOT APPLIED'.
• ACTION_REQUIRED — a constant expression returning 'RECOMPILE' for every row, signalling the required remediation step.
• OBJECTS_AFFECTED — exposed as the constant 0, and OBJECT_TYPE as the literal 'NULL', indicating the parent JSP_INCLUDE relation is treated as a single-file concern rather than a multi-object set.

Common Use Cases and Queries

Typical uses include patch impact assessment, generating recompilation worklists, and QA verification after patching. A basic listing of affected files for a given patch might be:

• SELECT BUG_NO, SNAPSHOT_ID, PATCHED_APP_SHORT_NAME, PATCHED_DIRECTORY, PATCHED_FILENAME, ACTION_REQUIRED FROM FND_IMP_AFFECTEDFILES_VL WHERE BUG_NO = :bug_no;
• SELECT DISTINCT PATCHED_APP_SHORT_NAME, PATCHED_FILENAME FROM FND_IMP_AFFECTEDFILES_VL ORDER BY 1,2;
• SELECT ACTION_REQUIRED, COUNT(*) FROM FND_IMP_AFFECTEDFILES_VL GROUP BY ACTION_REQUIRED;

Because every row carries ACTION_REQUIRED = 'RECOMPILE', the view lends itself to shell and SQL*Plus scripting where the output is piped into JSP recompilation or page-regeneration routines. It is also useful as a diagnostic source when investigating JSP inclusion failures, since the join conditions expose the exact parent-child file naming that the dependency engine evaluated.