Search Results prp_proposals




Overview
Explore in AI Chat

Overview

The PRP_PROPOSALS table is the central master data repository within the Oracle E-Business Suite (EBS) Proposals (PRP) module for versions 12.1.1 and 12.2.2. It stores the core definition and header-level attributes of every proposal created in the system. A proposal is a formal document, often generated from a template, used to present business offerings, such as bids, quotes, or project plans, to customers or partners. This table's integrity is maintained by its primary key and a network of foreign key relationships that link it to foundational EBS entities, including customers, users, languages, and content management systems. Its role is critical for the lifecycle management of proposals, from creation and versioning to final output.

Key Information Stored

The table's primary identifier is the PROPOSAL_ID column, which is the unique key for each proposal record. Based on the documented foreign key relationships, other critical columns define the proposal's context and ownership. The PARTY_ID and CONTACT_PARTY_ID columns link to the HZ_PARTIES table, storing the target customer organization and specific contact, respectively. The USER_ID column references FND_USER, identifying the proposal owner or creator. The PROPOSAL_LANGUAGE column links to FND_LANGUAGES, defining the document's output language. The TEMPLATE_ID column self-references the PRP_PROPOSALS table, indicating the base template used for generation. Finally, the CONTENT_ITEM_ID column links to IBC_CONTENT_ITEMS, integrating the proposal with the EBS Content Manager for storage and version control of the actual document content.

Common Use Cases and Queries

This table is fundamental for reporting and data extraction related to proposal activity. Common operational queries include listing all proposals for a specific customer, identifying proposals created by a particular user within a date range, or finding proposals based on their status or language. For instance, to retrieve a basic proposal header report, a query would join PRP_PROPOSALS with HZ_PARTIES and FND_USER. Technical support often queries this table to trace the lineage of a proposal back to its original template. Furthermore, integration with other modules, such as Order Management or Projects, may require querying PRP_PROPOSALS to fetch proposal details associated with a converted order or project.

  • Listing proposals by customer: SELECT pp.proposal_id, hp.party_name FROM prp_proposals pp, hz_parties hp WHERE pp.party_id = hp.party_id;
  • Finding proposals created from a specific template: SELECT child_proposal_id FROM prp_proposals WHERE template_id = <template_proposal_id>;

Related Objects

The PRP_PROPOSALS table has extensive relationships within the Proposals schema and with core EBS applications. As per the metadata, it is the parent table for several key child entities: PRP_PROPOSAL_CTNTVERS (for content versions), PRP_PROPOSAL_OBJECTS (for embedded objects), PRP_PROPOSAL_TOKENS (for variable data), and PRP_PROP_STYLE_CTNTVERS (for style sheet versions). Externally, it integrates with Trading Community Architecture (HZ_PARTIES for customers), the application foundation (FND_USER, FND_LANGUAGES), and the content repository (IBC_CONTENT_ITEMS). These relationships underscore that PRP_PROPOSALS is not an isolated table but the hub of a complex data model supporting rich, structured business documents.