Search Results jsp_include

Overview

APPS.FND_IMP_AFFECTEDFILES_VL is a reporting view in the Oracle E-Business Suite Applications (APPS) schema that resolves the set of files affected by an applied patch, filtered specifically to JSP file dependencies of type JSP_INCLUDE. In the context of Oracle EBS 12.1.1 and 12.2.2, the view is part of the patch-information and dependency-tracking infrastructure used by AutoPatch, AD Online Patching (in 12.2.x), and the Oracle Applications DBA (AD) utilities. Its practical purpose is to expose, for a given patch snapshot, the deployed ("patched") JSP file alongside the parent file that includes it, so that dependent artifacts can be identified and recompiled or revalidated after a patch is applied.

The _VL suffix follows the standard EBS convention for a "value" or validation view, though in this case the view functions as a query-only projection over three underlying implementation tables rather than a translated lookup. The view returns one row per affected JSP file whose dependency relationship was recorded as a JSP include, and it is most relevant when tracing the ripple effects of a patch across the file system and the database-stored dependency graph.

Underlying Base Objects

The view is defined over three documented base objects, all presented through APPS synonyms:

• FND_IMP_PSMASTER2 — the primary source of patched-file metadata, supplying bug number, snapshot, patched application short name, directory, filename, file type, type ID, and patch ID.
• FND_IMP_DEPOBJECTS — supplies the parent (dependency) object information, including the parent application short name, file directory, and filename.
• FND_IMP_DEPRELATIONS — supplies the snapshot ID, dependency type, child object name, child application short name, and parent object ID that link patches to their dependencies.

The join is driven by the dependency relation: the parent object is resolved through P.OBJECT_ID = R.PARENT_OBJECT_ID, while the child is matched by concatenating the patched file's directory and filename (A.DIRECTORY || '/' || A.FILENAME) and application short name against the relation's child object name and child application short name. Only rows whose DEPENDENCY_TYPE equals JSP_INCLUDE, whose FILE_TYPE equals jsp, and whose TYPEID is not 'not applied' are returned.

Key Columns

• BUG_NO — the bug or patch reference associated with the affected file.
• SNAPSHOT_ID — identifies the patch snapshot within which the dependency was captured.
• DEP_APP_SHORT_NAME, DEP_DIRECTORY, DEP_FILENAME — the parent (including) application and file that depends on the patched JSP.
• PATCHED_APP_SHORT_NAME, PATCHED_DIRECTORY, PATCHED_FILENAME — the patched JSP file that forms the dependency child.
• TYPEID — the patch application state; rows with 'not applied' are excluded.
• ACTION_REQUIRED — a constant value of 'Recompile', indicating the remedial action implied for the affected dependent file.
• OBJECTS_AFFECTED — returned as a literal 0, a placeholder column.
• OBJECT_TYPE — returned as the literal string 'null'.
• PATCH_ID — the patch identifier to which the affected file belongs.

Common Use Cases and Queries

The view is typically queried to enumerate JSP files affected by a patch and to locate the parent files that include them, supporting post-patch recompilation checks and impact analysis.

• Identify all patched JSP files and their dependent includes for a given snapshot.
• Determine which parent applications or directories must be revisited after patching.
• Correlate affected files with a specific bug number or patch ID during troubleshooting.

Illustrative query:

SELECT bug_no,
       snapshot_id,
       dep_app_short_name,
       dep_directory,
       dep_filename,
       patched_app_short_name,
       patched_directory,
       patched_filename,
       action_required,
       patch_id
  FROM apps.fnd_imp_affectedfiles_vl
 WHERE snapshot_id = :snapshot_id
   AND bug_no = :bug_number
 ORDER BY dep_app_short_name, patched_filename;

Because the view pre-filters DEPENDENCY_TYPE = 'JSP_INCLUDE', FILE_TYPE = 'jsp', and excludes TYPEID = 'not applied', it returns only actionable JSP include dependencies, making it suitable for automation scripts and diagnostic reports in both 12.1.1 and 12.2.2 environments.