Results for “pobv_rfq_price_breaks”

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

Overview

POBV_RFQ_PRICE_BREAKS is an APPS-owned database view in the Oracle E-Business Suite Purchasing (PO) module, documented in ETRM for releases 12.1.1 and 12.2.2 (retrofitted). It exposes RFQ (Request for Quotation) price break and shipment scheduling information by flattening data that originates in the purchasing line, shipment, and header tables, together with operating unit and quotation attributes.

The view is one of the business views (the POBV prefix denotes the Oracle Purchasing Business View family) used for reporting and integration, particularly for extracting RFQ catalog quotation price break details — quantity thresholds, discounted pricing, effective dates, receiving controls, lead time, and lead time UOM LEAD_TIME_UOM, terms, and carrier information. The view is defined WITH READ ONLY, so it should be treated as a query-only source; no DML is permitted against it.

Underlying Base Objects

The documented metadata lists four synonym-referenced base objects: PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, and HR_ALL_ORGANIZATION_UNITS. In the view text, the aliases map as follows:

• PO_LINE_LOCATIONS_ALL (QB) — the primary driver, supplying the price break / shipment records and the majority of the columns, including quantity, price override, discount, effective dates, receiving controls, lead time, and lead time unit.
• PO_LINES_ALL (QL) — supplies the line-level context, joined on PO_LINE_ID.
• PO_HEADERS_ALL (QU) — supplies document-level attributes such as SEGMENT1 (document number) and the RFQ / catalog classification, joined on PO_HEADER_ID.
• HR_ALL_ORGANIZATION_UNITS (OP) — supplies the operating unit name, joined on QB.ORG_ID = OP.ORGANIZATION_ID.

The view filters to quotations of TYPE_LOOKUP_CODE = 'RFQ' and QUOTATION_CLASS_CODE = 'CATALOG', restricts shipments to SHIPMENT_TYPE = 'RFQ', and enforces an organization security predicate on QB.ORG_ID.

Key Columns

• PRICE_BREAK_ID, PRICE_BREAK_NUMBER — identifier and display number for the price break record.
• RFQ_LINE_ID, LINE_NUMBER, RFQ_ID, RFQ_DOCUMENT_NUMBER — line and document identification for the parent RFQ.
• OPERATING_UNIT_ID, OPERATING_UNIT_NAME — the owning operating unit.
• PRICE_BREAK_QUANTITY, DISCOUNTED_PRICE, PRICE_DISCOUNT_PERCENTAGE — the quantity threshold and the resulting price or discount.
• START_EFFECTIVE_DATE, END_EFFECTIVE_DATE — validity window of the price break.
• LEAD_TIME, LEAD_TIME_UOM — the negotiated lead time and its unit of measure; the searched attribute lead_time_uom corresponds to this column, sourced from QB.LEAD_TIME_UNIT.
• UNIT_OF_MEASURE — the unit of measure for the quantity.
• QUANTITY_RECEIVED_TOLERANCE, "_LA:QTY_RECEIVED_EXCEPTION" (QTY_RCV_EXCEPTION_CODE) — receiving control settings.
• "_LA:INVOICE_MATCHING", "_LA:FREIGHT_TERM", "_LA:FREE_ON_BOARD_POINT", "_LA:TAXABLE_FLAG" — descriptive lookup-derived attributes (matching type, freight terms, FOB, taxable flag).
• CARRIER, PAYMENT_TERMS_ID (TERMS_ID), SHIP_VIA_LOOKUP_CODE — shipping and payment terms.
• CREATED_DATE, CREATED_BY, LAST_UPDATED_DATE, LAST_UPDATED_BY — audit columns.

Common Use Cases and Queries

The view is typically used to report RFQ catalog price breaks and associated lead times for sourcing analysis, price list validation, and vendor negotiation review. A representative query returning price ranges, lead time, and lead time UOM for a given RFQ is:

• SELECT RFQ_DOCUMENT_NUMBER, LINE_NUMBER, PRICE_BREAK_QUANTITY, DISCOUNTED_PRICE, PRICE_DISCOUNT_PERCENTAGE, LEAD_TIME, LEAD_TIME_UOM, UNIT_OF_MEASURE FROM POBV_RFQ_PRICE_BREAKS WHERE RFQ_DOCUMENT_NUMBER = :p_doc;
• To list effective price breaks as of a date: WHERE SYSDATE BETWEEN START_EFFECTIVE_DATE AND END_EFFECTIVE_DATE.
• To aggregate by operating unit for sourcing spend analysis: SELECT OPERATING_UNIT_NAME, COUNT(*) FROM POBV_RFQ_PRICE_BREAKS GROUP BY OPERATING_UNIT_NAME;
• To identify items with long quoted lead times: WHERE LEAD_TIME > 30 ORDER BY LEAD_TIME DESC;

Because the view enforces row-level organization security through the QB.ORG_ID predicate, results are automatically limited to the operating units accessible to the querying user. The read-only nature and its dependence on synonym-referenced base tables mean the view should be queried directly rather than modified, and any performance tuning should target the underlying PO_LINE_LOCATIONS_ALL, PO_LINES_ALL, and PO_HEADERS_ALL structures.