Results for “prp_proposals”

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

Overview

PRP_PROPOSALS is the master transactional table in the Oracle EBS Proposals (PRP) module, which is part of the Oracle E-Business Suite Advanced Outbound / iMarketing family of applications. The table stores header-level information for every proposal record created within the application, serving as the anchor object from which proposal content versions, tokens, objects, and style definitions derive. Each row represents a single proposal authored by or assigned to a system user, optionally tied to a customer party and contact, and optionally generated from a reusable template. Because the table is referenced by multiple child tables through PROPOSAL_ID, it functions as the parent in a classic header-to-detail hierarchy.

The supplied ETRM metadata classifies PRP_PROPOSALS using a Data Vault heuristic as satellite-leaning. In modelling terms, this reflects the fact that the table carries its own descriptive attributes plus several foreign keys pointing to reference and master data (FND_USER, FND_LANGUAGES, HZ_PARTIES, IBC_CONTENT_ITEMS, and a template reference). It is not a pure hub, since it does not simply hold a business key in isolation, nor is it exclusively a link, since it carries substantive descriptive columns. Treating it as a satellite in a Data Vault construct — keyed on a hub representing the proposal and enriched with descriptive attributes — is a reasonable analytical approach.

Key Information Stored

The table contains 37 documented columns in the 12.2.2 physical schema. The most operationally significant columns are:

• PROPOSAL_ID — surrogate primary key (PRP_PROPOSALS_PK and unique index PRP_PROPOSALS_U1). It uniquely identifies each proposal and is the join key to all child tables.
• PROPOSAL_NAME and PROPOSAL_DESC — business-facing identity and descriptive text for the proposal.
• PROPOSAL_STATUS — lifecycle state of the proposal (e.g., draft, active, published, inactive).
• USER_ID — owner/author of the proposal; foreign key to FND_USER.
• PROPOSAL_LANGUAGE — language in which the proposal is rendered; foreign key to FND_LANGUAGES.
• TEMPLATE_ID — source template from which the proposal was generated, if any.
• PARTY_ID and CONTACT_PARTY_ID — customer party and contact party associated with the proposal; both foreign keys to HZ_PARTIES.
• CONTENT_ITEM_ID — reference to the content item backing the proposal content; foreign key to IBC_CONTENT_ITEMS.
• DUE_DATE — target date for the proposal.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF framework.
• The standard EBS WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and the program/request columns (PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_LOGIN_ID, REQUEST_ID), plus the 15 ATTRIBUTE / ATTRIBUTE_CATEGORY descriptive flexfield columns.

Common Use Cases and Queries

Typical reporting and integration scenarios include listing active proposals for a given user, extracting proposal headers for a customer, and reconciling proposals against their content versions.

Sample: retrieve proposals by owner and status:

• SELECT p.proposal_id, p.proposal_name, p.proposal_status, p.due_date FROM prp.prp_proposals p WHERE p.user_id = :user_id AND p.proposal_status = 'ACTIVE';

Sample: proposals for a specific customer party, joined to HZ_PARTIES:

• SELECT p.proposal_name, hp.party_name FROM prp.prp_proposals p, hz_parties hp WHERE p.party_id = hp.party_id AND p.party_id = :party_id;

Sample: count of content versions per proposal:

• SELECT p.proposal_id, p.proposal_name, COUNT(c.proposal_id) FROM prp.prp_proposals p LEFT JOIN prp.prp_proposal_ctntvers c ON c.proposal_id = p.proposal_id GROUP BY p.proposal_id, p.proposal_name;

Common use cases include proposal status dashboards, template adoption analysis (grouping by TEMPLATE_ID), customer engagement reporting via PARTY_ID, and migration/audit extracts keyed on PROPOSAL_ID and the date-tracked WHO columns.

Related Objects

The following objects have documented relationships to PRP_PROPOSALS:

• PRP_PROPOSAL_CTNTVERS — child table; join on PROPOSAL_ID. Stores content versions of the proposal.
• PRP_PROPOSAL_OBJECTS — child table; join on PROPOSAL_ID. Stores objects associated with the proposal.
• PRP_PROPOSAL_TOKENS — child table; join on PROPOSAL_ID. Stores merge tokens/placeholders.
• PRP_PROP_STYLE_CTNTVERS — child table; join on PROPOSAL_ID. Stores style/content versions.
• FND_USER — referenced via USER_ID; provides creator/owner identity.
• FND_LANGUAGES — referenced via PROPOSAL_LANGUAGE.
• HZ_PARTIES — referenced twice, via PARTY_ID and CONTACT_PARTY_ID.
• IBC_CONTENT_ITEMS — referenced via CONTENT_ITEM_ID; ties the proposal to its repository content item.

These relationships establish PRP_PROPOSALS as the central header object of the PRP module, with dependent detail tables keyed on PROPOSAL_ID and inbound references to shared EBS master and reference data.