Results for “content_node_type”

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

Overview

PRP_PERZ_FILES is a transactional table in the PRP (Proposals) product family of Oracle E-Business Suite, residing in the PRP schema. It stores the personalized files that sales representatives attach to a proposal, enabling pre-sales teams to associate supplementary content — such as custom documents, presentations, or supporting artifacts — with a specific proposal line or configuration item version. Personalization here refers to representative-authored attachments rather than system-generated proposal output.

From a Data Vault modeling perspective, the heuristic classification of PRP_PERZ_FILES is a link: the table's foreign keys connect an external file object (FND_LOBS) to a configuration item version (IBC_CITEM_VERSIONS_B), with the personalized file record acting as the associating entity between those two references. The table is independent of the descriptive attributes of either parent, which is characteristic of a link construct.

Key Information Stored

• PERZ_FILE_ID — Surrogate primary key, enforced by PRP_PERZ_FILES_PK and reinforced by the unique index PRP_PERZ_FILES_U1. This is the internal identifier for each personalized file row.
• FILE_ID — Foreign key to FND_LOBS, identifying the physical file content stored in the shared Oracle LOB repository. This is the second documented unique key component (PRP_PERZ_FILES_UK1), reflecting the one-row-per-file association.
• CITEM_VERSION_ID — Foreign key to IBC_CITEM_VERSIONS_B, tying the personalized file to a specific configuration item version within the proposal structure.
• PERZ_FILE_NAME — The display name given to the personalized file.
• PERZ_FILE_DESC — Free-text description supplied by the sales representative for the file.
• CONTENT_NODE_TYPE — Classifies the content node context in which the file participates, supporting rendering and validation logic in the proposal UI.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the ADF/BC4J framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE — Standard audit columns capturing the creating user and timestamp.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns recording the most recent modification user, date, and login session.

The table contains 12 documented columns. The surrogate key (PERZ_FILE_ID) is distinct from the two business-key candidates exposed through the unique indexes, and the remaining attributes are descriptive or audit-related.

Common Use Cases and Queries

The most frequent operational pattern joins PRP_PERZ_FILES to FND_LOBS to resolve file names and content references for a given proposal, and to IBC_CITEM_VERSIONS_B to locate the file within the proposal's configuration hierarchy. A representative query returns all personalized files attached to a configuration item version:

• SELECT p.perz_file_id, p.perz_file_name, p.perz_file_desc, l.file_name FROM prp.prp_perz_files p JOIN fnd_lobs l ON l.file_id = p.file_id WHERE p.citem_version_id = :citem_version_id;

Reporting use cases include auditing which representatives attach the most personalized content, counting attachments per proposal, and identifying orphaned FND_LOBS entries. Bulk extraction for archival or migration can be driven by the PERZ_FILE_ID unique index, while change tracking leverages LAST_UPDATE_DATE and OBJECT_VERSION_NUMBER for incremental extracts.

Related Objects

• FND_LOBS — Parent repository of binary file content; joined on PRP_PERZ_FILES.FILE_ID = FND_LOBS.FILE_ID.
• IBC_CITEM_VERSIONS_B — Configuration item version base table defining the proposal structure node; joined on PRP_PERZ_FILES.CITEM_VERSION_ID = IBC_CITEM_VERSIONS_B.CITEM_VERSION_ID.
• IBC_CITEM_VERSIONS_TL — Translated descriptive attributes for configuration item versions, commonly joined for reporting labels.
• PRP_PERZ_FILES_PK / PRP_PERZ_FILES_UK1 / PRP_PERZ_FILES_U1 — Primary and unique constraints enforcing identity and the file association.
• Proposal header and line tables in the PRP schema — Provide the broader proposal context in which personalized files are surfaced.
• FND_ATTACHED_DOCUMENTS — Companion attachment framework, relevant when reconciling personalized files against standard EBS attachment records.