Results for “cz_rp_prj_directory_v”

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

Overview

CZ_RP_PRJ_DIRECTORY_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the CZ (Configurator) product family. The view presents an information-oriented directory of Models held in the Configurator repository, consolidating project-level definition data with repository entry metadata and cross-organizational import detail. Its documented purpose is to expose "Information view of Models in Repository," providing a denormalized, query-friendly representation of development projects that have been classified as repository entries of type PRJ.

The view is marked VALID in the ETRM metadata and is replicated across both EBS 12.1.1 and 12.2.2 releases with the same column footprint. It is not a transactional entity; rather, it is an inquiry surface intended for reporting, diagnostics, and integration extracts where a synopsis of each Configurator model is required. Because the underlying data is assembled from four distinct repository structures, the view serves as a convenient single point of access for administrators and developers who need to inventory models without navigating the individual base tables.

Underlying Base Objects

The documented base objects referenced by the view, all exposed through synonyms, are:

• CZ_DEVL_PROJECTS — the primary development project definition, holding project name, description, deletion status, audit columns, and the last structural update timestamp.
• CZ_RP_ENTRIES — the repository entry register that classifies objects by type and associates them with an enclosing folder and object identifier.
• CZ_PS_NODES — the product structure nodes that link a development project to its model structure.
• CZ_XFR_PROJECT_BILLS — the transfer/import bill of materials records that capture organization and top-item context when a project has been imported from another organization.

Joins are established on DEVL_PROJECT_ID between CZ_DEVL_PROJECTS, CZ_RP_ENTRIES, and CZ_PS_NODES, and on MODEL_PS_NODE_ID between CZ_PS_NODES and CZ_XFR_PROJECT_BILLS. A filter restricts OBJECT_TYPE to the literal value 'PRJ', ensuring only development projects are returned. The join to CZ_XFR_PROJECT_BILLS is effectively an outer relationship in practice, since the SYNOPSIS text handles a NULL ORGANIZATION_ID through a DECODE expression.

Key Columns

• OBJECT_TYPE — always 'PRJ' for rows returned by this view, confirming the repository classification.
• OBJECT_ID — the development project identifier, corresponding to CZ_DEVL_PROJECTS.DEVL_PROJECT_ID.
• ENCLOSING_FOLDER — the repository folder in which the model is cataloged.
• NAME — the project name, optionally suffixed with import provenance and top-item details.
• SYNOPSIS — a concatenated display string combining the name, any import origin and top item, the structure last-modified timestamp, and the first 150 characters of the description.
• DESCRIPTION — the complete descriptive text for the project.
• DELETED_FLAG — indicates whether the project has been logically deleted.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard audit columns.

Common Use Cases and Queries

The view is typically used for model inventory reporting, orphaned-project auditing, and reconciliation of imported models. A basic listing of active models follows:

SELECT name, enclosing_folder, synopsis FROM cz_rp_prj_directory_v WHERE deleted_flag = 'N' ORDER BY name;

To identify models imported from other organizations, filter on the synopsis text:

SELECT object_id, name FROM cz_rp_prj_directory_v WHERE synopsis LIKE '%IMPORTED FROM ORG%';

For audit purposes, recently modified structures can be isolated:

SELECT name, last_update_date, last_updated_by FROM cz_rp_prj_directory_v WHERE last_update_date > SYSDATE - 30;

Because no organization security or operating unit predicate is embedded in the view definition, callers should apply any required access restrictions explicitly. Queries returning large result sets should consider indexing or filtering on OBJECT_ID, ENCLOSING_FOLDER, or DELETED_FLAG to avoid full scans of the underlying repository tables.