Results for “prp_prop_objects_v”

42 results




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

Overview

PRP_PROP_OBJECTS_V is a seeded, dictionary-valid view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the PRP – Proposals product family and exposes consolidated proposal header information joined to the proposal objects (documents, content items, and related entities) attached to those proposals. As documented in the ETRM metadata, the view "provides proposal and proposal objects details," combining proposal-level attributes such as name, description, status, due date, and language with object-level attributes including OBJECT_ID, OBJECT_TYPE, and the current content item version identifiers.

The view also enriches the result set with the resource (owner) name resolved from JTF_RS_RESOURCE_EXTNS_VL, the decoded status meaning from FND_LOOKUP_VALUES, and a row-level security style flag (UPDATE_FLAG) computed against FND_GLOBAL.USER_ID. Because it is a view over synonyms rather than a table, it carries no data of its own and inherits the security and grants of the underlying base objects. It is most often consumed by concurrent programs, Oracle Reports/BI Publisher layouts, and custom integrations that need a flat, ready-to-query presentation of proposal content without performing the multi-table join manually.

Underlying Base Objects

The view is defined over the following documented objects:

The joins are effectively inner joins to PRP_PROPOSALS, PRP_PROPOSAL_OBJECTS, JTF_RS_RESOURCE_EXTNS_VL, and FND_LOOKUP_VALUES, with an outer join to PRP_PROPOSAL_CTNTVERS, so proposals lacking a current content version still appear, but proposals with no matching resource or lookup row are excluded.

Key Columns

  • PROPOSAL_ID — primary identifier of the proposal; join key to PRP_PROPOSAL_OBJECTS and PRP_PROPOSAL_CTNTVERS.
  • OWNER_USER_ID / OWNER_NAME — the FND user who owns the proposal and the corresponding resource name.
  • PARTY_ID / CONTACT_PARTY_ID — trading partner and contact associated with the proposal.
  • OBJECT_ID / OBJECT_TYPE — the attached object and its type classification.
  • PROPOSAL_NAME / PROPOSAL_DESC — descriptive text for the proposal.
  • PROPOSAL_STATUS_CODE / PROPOSAL_STATUS — raw status code and decoded lookup meaning.
  • DUE_DATE / PROPOSAL_LANGUAGE — deadline and language of the proposal.
  • UPDATE_FLAG — 'Y' when the proposal owner matches the current FND_GLOBAL.USER_ID, otherwise 'N'.
  • FILE_ID / CITEM_VERSION_ID / CONTENT_ITEM_ID — links to the current content version and its stored file.

Common Use Cases and Queries

Typical scenarios include listing every object attached to open proposals, reporting proposals owned by or updateable by the current user, and exporting proposal content versions for document management or archival.

  • All objects for a given proposal: SELECT object_id, object_type, owner_name, proposal_status FROM prp_prop_objects_v WHERE proposal_id = :p_id;
  • Current user's updateable proposals: SELECT proposal_id, proposal_name, due_date FROM prp_prop_objects_v WHERE update_flag = 'Y' ORDER BY due_date;
  • Open proposals with status meaning: SELECT proposal_name, proposal_status, owner_name FROM prp_prop_objects_v WHERE proposal_status = 'OPEN';
  • Proposals with their current content version: SELECT proposal_id, content_item_id, citem_version_id, file_id FROM prp_prop_objects_v WHERE file_id IS NOT NULL;

Because the view filters the lookup by USERENV('LANG') and computes UPDATE_FLAG from FND_GLOBAL.USER_ID, results are session-dependent; queries should be executed from an initialized EBS session so that language and user context resolve correctly.