Results for “prp_proposal_objects”

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

Overview

PRP_PROPOSAL_OBJECTS is a transactional association table within the PRP - Proposals module of Oracle E-Business Suite, residing in the PRP schema. Its documented purpose is to store the association between a proposal and the native objects it references, such as Oracle Advanced Sales and Pricing (ASO) quotes. In practical terms, it functions as the bridging mechanism that allows a single proposal record to point at one or more downstream or upstream business entities without duplicating their content.

A Data Vault classification heuristic derived from its foreign key structure labels this object as a link table. This is a modeling suggestion based on observed relationships rather than a formal Oracle construct. The table carries its own surrogate key and a small set of descriptive attributes, which is consistent with a link that also carries limited context such as display ordering and a primary-object indicator.

Key Information Stored

The table is documented with twelve columns in the ETRM 12.2.2 physical schema. The most operationally significant are:

• PROPOSAL_OBJECT_ID — the surrogate primary key, enforced by index PRP_PROPOSAL_OBJECTS_PK (also exposed as PRP_PROPOSAL_OBJECTS_U1). This is the technical identifier for each association row.
• PROPOSAL_ID — the foreign key to PRP_PROPOSALS, identifying the owning proposal.
• OBJECT_TYPE — the discriminator describing which kind of native object is referenced (for example, a quote).
• OBJECT_ID — the foreign key to the referenced entity, documented as pointing to ASO_QUOTE_HEADERS_ALL.
• PRIMARY_FLAG — indicates whether the association is the principal object for the proposal.
• DISPLAY_ORDER — controls the sequence in which associated objects are presented in the proposal UI and reports.
• OBJECT_VERSION_NUMBER — supports optimistic locking during concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns (who/when columns) recording row provenance.

The business-key candidate is the unique index PRP_PROPOSAL_OBJECTS_U2 on (PROPOSAL_ID, OBJECT_TYPE, OBJECT_ID), which guarantees that a given native object is associated with a proposal only once. This pairing of a surrogate PK with a composite unique business key is a standard EBS pattern.

Common Use Cases and Queries

Typical scenarios include determining all objects attached to a proposal, identifying which proposals reference a specific quote, and enforcing the single-primary-object rule. A common join pattern resolves the proposal-to-quote relationship:

• Join PRP_PROPOSAL_OBJECTS to PRP_PROPOSALS on PROPOSAL_ID to retrieve proposal header context.
• Join PRP_PROPOSAL_OBJECTS to ASO_QUOTE_HEADERS_ALL on OBJECT_ID (filtering by OBJECT_TYPE) to pull quote details.
• Filter on PRIMARY_FLAG = 'Y' to return only the primary association for each proposal.
• Order by DISPLAY_ORDER when reproducing the UI sequence in custom reports.

Reporting use cases include auditing orphaned associations, counting associated objects per proposal, and validating that no proposal carries more than one primary object. Because the table is a pure link, most reporting queries resolve it through joins rather than reading it standalone.

Related Objects

• PRP_PROPOSALS — parent table; joined via PRP_PROPOSAL_OBJECTS.PROPOSAL_ID.
• ASO_QUOTE_HEADERS_ALL — referenced native object; joined via PRP_PROPOSAL_OBJECTS.OBJECT_ID.
• PRP_PROPOSAL_OBJECTS_PK / U1 / U2 — primary and unique indexes enforcing identity and the business key.
• Other PRP module tables (proposal lines, parties, and status history) that share PROPOSAL_ID and are commonly queried alongside this association table.
• ASO quote line and header APIs, which are relevant when the referenced OBJECT_TYPE identifies a quote and downstream processing is required.

Because the foreign key to ASO_QUOTE_HEADERS_ALL is documented explicitly, any query joining quotes to proposals should treat PRP_PROPOSAL_OBJECTS as the authoritative bridge rather than deriving the relationship indirectly.