Results for “jtf_imp_psmaster_vl”
6 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
JTF_IMP_PSMASTER_VL is a consolidated reporting view within the JTF (CRM Foundation) module of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. The name and column structure indicate that the object supports the CRM patch- and snapshot-management infrastructure, specifically the tracking of implementation artefacts such as application files, directories, and versions. The "_VL" suffix conventionally denotes a view that has undergone translation or validation handling in EBS, though in this case the view acts as a unified master list combining base implementation data with newly detected content.
The view presents a harmonised dataset of patch-snapshot implementation records. Records from the common implementation table are merged with records describing new versions, and a computed TYPEID column classifies each row as UPGRADE, OVERWRITE, NOT APPLIED, NEW, or UNKNOWN. This makes JMaster_VL useful whenever a report or interface must reconcile the currently installed file set against the expected set delivered by a patch or snapshot.
Underlying Base Objects
The documented ETRM metadata lists no referenced base objects, and the view text is therefore the authoritative source for its definition. The SELECT statement unions two sources:
- JTF_IMP_PSCOMMON — aliased as X, this table holds the common implementation snapshot records, including the OLD_VERSION and NEW_VERSION columns used for comparison.
- JTF_IMP_PSNEW — aliased as Y, this table holds records for newly introduced implementation files.
Both branches share the same column footprint, enabling the UNION ALL to produce a single result set. The first branch passes X.* through unchanged and derives TYPEID via JTF_IMP_CONV_PKG.COMPARE_RCSID, a PL/SQL packaged function that compares old and new revision-control identifiers. The second branch supplies Y.*, sets OLD_VERSION to NULL, and hard-codes TYPEID as 'NEW'. Note that the ETRM excerpt renders the closing clause ambiguously; operationally the view is defined as the union of the two branches described above. Because the view depends on the JTF_IMP_CONV_PKG package, schema grants on that package must be in place for the view to compile and query successfully.
Key Columns
- BUG_NO — the associated bug or patch identifier that introduced or affects the implementation record.
- SNAPSHOT_ID — unique identifier of the snapshot to which the file record belongs.
- APP_SHORT_NAME — short name of the application (for example, JTF) that owns the file.
- DIRECTORY — target directory path for the delivered or tracked file.
- FILENAME — name of the implementation file.
- NEW_VERSION — the version delivered by the incoming snapshot or patch; central to the comparison logic described below.
- OLD_VERSION — the version currently present on the instance; NULL for records sourced from JTF_IMP_PSNEW.
- TYPEID — the computed disposition of the file: 'UPGRADE' (return code 1), 'OVERWRITE' (2), 'NOT APPLIED' (3), 'UNKNOWN' (any other return), or 'NEW' for net-new files.
Common Use Cases and Queries
Typical uses include auditing which files a patch will upgrade versus overwrite, identifying files that were never applied, and listing newly introduced files ahead of a deployment. A representative query counts records by disposition for a given snapshot:
SELECT TYPEID, COUNT(*) FROM JTF_IMP_PSMASTER_VL WHERE SNAPSHOT_ID = :snapshot_id GROUP BY TYPEID;SELECT APP_SHORT_NAME, DIRECTORY, FILENAME, OLD_VERSION, NEW_VERSION FROM JTF_IMP_PSMASTER_VL WHERE TYPEID = 'OVERWRITE';SELECT * FROM JTF_IMP_PSMASTER_VL WHERE BUG_NO = :bug_no ORDER BY APP_SHORT_NAME, FILENAME;
Because the TYPEID values are driven by JTF_IMP_CONV_PKG.COMPARE_RCSID, results reflect the current state of the instance at query time, making the view suitable for pre- and post-patch validation reporting. For diagnostic or reconciliation reporting where typing issues arise, referencing JTF_IMP_PSCOMMON and JTF_IMP_PSNEW directly can isolate the underlying rows.
-
View: JTF_IMP_PSMASTER_VL 12.2.2
Not implemented in this database·Explore JTF module →
-
View: JTF_IMP_PSMASTER_VL 12.1.1
Not implemented in this database·Explore JTF module →
-
View: JTF_IMP_PSMASTER2_VL 12.2.2
Not implemented in this database·Explore JTF module →
-
View: JTF_IMP_PSMASTER2_VL 12.1.1
Not implemented in this database·Explore JTF module →
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2