Search Results proposal_status

Overview

PRP_PROP_CUSTOMERS_V is a reporting and integration view owned by the APPS schema within the PRP - Proposals product module of Oracle E-Business Suite. The view's documented purpose is to provide proposal and proposal version details, presenting a denormalized, query-ready projection of proposal header data joined to version, resource, and lookup information. Rather than requiring consumers to reassemble this information from multiple base tables, the view exposes a single relational surface suitable for Oracle Reports, BI Publisher datasets, OAF pages, and custom SQL used by ETRM (Oracle EBS Technical Reference Manual) practitioners. The view is documented as VALID, indicating that it compiles successfully and can be queried without recompilation. Its principal design characteristic is that it resolves the proposal status code into a user-facing meaning through a lookup join, which makes it a natural target for status-driven reporting.

Because the searched term is "proposal_status", it is significant that the view is the documented access point for the proposal status value: the SELECT list includes the raw PROPOSAL_STATUS column from PRP_PROPOSALS and the derived MEANING column obtained from FND_LOOKUP_VALUES using the lookup type PRP_PROPOSAL_STATUS. Users therefore retrieve both the code and its translated display value from one query.

Underlying Base Objects

The documented ETRM metadata lists the referenced base objects as PRP_PROPOSALS, PRP_PROPOSAL_CTNTVERS, PRP_PROPOSAL_ACCESSES, PRP_PROP_CTNTVER_FORMATS, JTF_RS_RESOURCE_EXTNS_VL, and FND_LOOKUP_VALUES, together with the FND_GLOBAL package. These are exposed under APPS through synonyms and views.

The view text joins PRP_PROPOSALS (aliased PRP) as the driving table, PRP_PROPOSAL_CTNTVERS (VERS) as an outer-joined table restricted to the maximum version flag, JTF_RS_RESOURCE_EXTNS_VL (JRS) on USER_ID to resolve the owning resource name, and FND_LOOKUP_VALUES (LUP) to translate the proposal status code. The lookup join is constrained to VIEW_APPLICATION_ID = 0, LOOKUP_TYPE = 'PRP_PROPOSAL_STATUS', matching LOOKUP_CODE to PRP.PROPOSAL_STATUS, and LANGUAGE = USERENV('LANG'), ensuring the description is returned in the session language. FND_GLOBAL supplies the runtime USER_ID used by the UPDATE_FLAG expression, which returns 'Y' when the proposal's user identifier matches the currently connected user.

Key Columns

• PROPOSAL_ID — Primary identifier of the proposal; the principal join key to related PRP tables.
• OWNER_USER_ID / PARTY_ID / CONTACT_PARTY_ID — Identifiers for the proposal owner and the associated party and contact party records.
• OWNER_NAME — Resource name of the owner, sourced from JTF_RS_RESOURCE_EXTNS_VL.
• PROPOSAL_NAME / PROPOSAL_DESC — Descriptive attributes of the proposal header.
• PROPOSAL_STATUS_CODE — The stored status code from PRP_PROPOSALS.
• PROPOSAL_STATUS — The decoded, language-specific meaning returned by the PRP_PROPOSAL_STATUS lookup; this is the column most relevant to status reporting.
• DUE_DATE — Target or due date associated with the proposal.
• UPDATE_FLAG — 'Y' when the proposal belongs to the connected user, supporting row-level ownership logic.
• FILE_ID / CITEM_VERSION_ID / CONTENT_ITEM_ID — Version and content-item linkage for the proposal's current content version.
• PROPOSAL_LANGUAGE — Language attribute carried on the proposal record.

Common Use Cases and Queries

Typical uses include proposal status dashboards, owner workload listings, and custom concurrent programs or BI Publisher reports that must display the status description rather than the code.

Listing proposals by status:

SELECT proposal_id, proposal_name, proposal_status,
       owner_name, due_date
FROM   apps.prp_prop_customers_v
WHERE  proposal_status = 'Approved'
ORDER  BY due_date;

Identifying proposals owned by the connected user:

SELECT proposal_id, proposal_name, proposal_status_code,
       proposal_status, due_date
FROM   apps.prp_prop_customers_v
WHERE  update_flag = 'Y';

Joining the view to proposal tables for detailed version reporting:

SELECT v.proposal_id, v.proposal_name, v.proposal_status,
       v.citem_version_id, v.content_item_id
FROM   apps.prp_prop_customers_v v
WHERE  v.proposal_language = USERENV('LANG');

Because the status lookup is bound to USERENV('LANG'), the PROPOSAL_STATUS value is returned in the session language, which is appropriate for localized output. Queries should be schema-qualified with APPS, and the outer join on the version table means proposals without a currently flagged maximum version are still returned with null version columns.