Search Results quote_rev_nbr




Overview
Explore in AI Chat

Overview

The CZ_PROP_QUOTE_HDRS table is a core data object within the Oracle E-Business Suite Configurator (CZ) module. It functions as a join table, establishing and managing the many-to-many relationship between proposals and quotes. In the context of Oracle Configurator, a proposal is a configured solution or offering, while a quote is the commercial document derived from that proposal. This table is essential for tracking which specific quote revisions are linked to which proposal headers, thereby maintaining a complete audit trail of the sales configuration and quoting process. Its role is critical for ensuring data integrity between the configuration engine and downstream order management activities.

Key Information Stored

The table's structure is designed to store the minimal yet essential keys required to link the two entities. The primary key is a composite of three columns, ensuring a unique relationship between a proposal, a quote header, and a specific revision of that quote. The key columns are:

  • PROPOSAL_HDR_ID: Foreign key referencing the CZ_PROPOSAL_HDRS table. This identifies the specific proposal or configuration instance.
  • QUOTE_HDR_ID: Foreign key referencing the CZ_QUOTE_HDRS table. This identifies the quote document header.
  • QUOTE_REV_NBR: Foreign key, paired with QUOTE_HDR_ID, referencing the revision number within the CZ_QUOTE_HDRS table. This column is crucial as it tracks which specific revision of a quote is associated with the proposal, allowing the system to manage multiple iterations of a quote for the same configured solution.
Together, these columns form the primary key (CZ_PROP_QUOTE_HDRS_PK), guaranteeing that each proposal-quote-revision combination is recorded only once.

Common Use Cases and Queries

A primary use case is auditing and reporting on the lifecycle of a configured proposal. For instance, users can determine all quotes and their revisions generated from a single proposal. Conversely, it allows tracing a quote back to its original configured source. The table is frequently queried in joins for custom reports or data extracts. A sample query to retrieve all linked records for a specific proposal would be: 

SELECT pqh.QUOTE_HDR_ID, pqh.QUOTE_REV_NBR, qh.QUOTE_NUM
FROM CZ_PROP_QUOTE_HDRS pqh,
     CZ_QUOTE_HDRS qh
WHERE pqh.PROPOSAL_HDR_ID = :p_proposal_hdr_id
AND pqh.QUOTE_HDR_ID = qh.QUOTE_HDR_ID
AND pqh.QUOTE_REV_NBR = qh.REVISION_NBR;
Another common pattern involves finding the most recent quote revision linked to a proposal, which would require filtering or analytic functions on the QUOTE_REV_NBR in conjunction with the related CZ_QUOTE_HDRS table.

Related Objects

The CZ_PROP_QUOTE_HDRS table has direct foreign key dependencies on two primary header tables, forming the core of its relationship model:

  • CZ_PROPOSAL_HDRS: Links via the PROPOSAL_HDR_ID column. This table stores the header information for configuration proposals.
  • CZ_QUOTE_HDRS: Links via the composite foreign key of QUOTE_HDR_ID and QUOTE_REV_NBR. This table stores the header information for commercial quotes, including revision history.
This table is typically accessed indirectly through the Configurator's public user interfaces and APIs. Direct manipulation should be avoided in favor of using the supported module logic to maintain referential integrity and business rule validation.