Results for “prp_proposal_status”

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

Overview

APPS.PRP_PROP_OBJECTS_V is a PL/SQL view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments that consolidates proposal header, object, version, format, resource, and status information from the Oracle Trade Management / Proposal (PRP) module. It is owned by the APPS schema and serves as a reporting and integration surface for proposal records, joining the proposal master row to its associated business objects. The view exposes the PROPOSAL_STATUS column in encoded form and its decoded MEANING from the lookup PRP_PROPOSAL_STATUS, which is the attribute most commonly sought by users searching for "prp_proposal_status."

Underlying Base Objects

The view is defined over the following documented base objects:

• PRP_PROPOSALS (synonym) — the proposal header, supplying proposal_id, user_id, party_id, and status.
• PRP_PROPOSAL_OBJECTS (synonym) — the association between proposals and business objects (object_id, object_type).
• PRP_PROPOSAL_CTNTVERS (synonym) — content versions; the join is outer ((+)) with max_version_flag = 'Y', retrieving the latest version.
• PRP_PROP_CTNTVER_FORMATS (synonym) — file formats per content version, outer-joined to the version.
• PRP_PROPOSAL_ACCESSES (synonym) — access records; the view restricts to owner_flag = 'Y'.
• JTF_RS_RESOURCE_EXTNS_VL (view) — resource name, joined to accesses by resource_id.
• FND_LOOKUP_VALUES (synonym) — lookup meanings, filtered to lookup_type = 'PRP_PROPOSAL_STATUS', view_application_id = 0, and the session language.
• FND_GLOBAL (package) — used to derive updateFlag by comparing user_id to the current session user.

Key Columns

• proposal_id, proposal_name, proposal_desc, proposal_language, due_date — core proposal attributes.
• proposal_status and meaning — the encoded status code and its translatable lookup meaning, respectively.
• object_id, object_type — the associated business object identified by the proposal.
• resource_name — the proposal owner's resource name from JTF_RS_RESOURCE_EXTNS_VL.
• updateFlag — 'Y' when the current session user owns the proposal, else 'N'.
• file_id, file_format — format metadata for the latest content version; defaults to 'RTF' unless a single 'PDF' format exists, in which case 'PDF' is returned.
• citem_version_id, content_item_id — hard-coded NULL placeholders for compatibility with content item interfaces.

Common Use Cases and Queries

The view is typically queried to report proposals by status, to drive list-of-values and integration extracts, and to resolve the owner and latest output file. A representative query filtering on decoded status follows:

• SELECT proposal_id, proposal_name, proposal_status, meaning, due_date FROM apps.prp_prop_objects_v WHERE meaning = 'Approved';
• SELECT proposal_id, proposal_name, resource_name, updateFlag FROM apps.prp_prop_objects_v WHERE updateFlag = 'Y';
• SELECT object_type, COUNT(*) FROM apps.prp_prop_objects_v GROUP BY object_type;

Because the view applies outer joins for content versions and formats, proposals without versions still appear, returning NULL file metadata. Consumers should therefore expect, and handle, nulls in file_id and file_format when a proposal has no generated version.