Search Results maximum_order_quantity




Overview
Explore in AI Chat

Overview

POBV_RFQ_LINES is a read-only view owned by the APPS schema in Oracle E-Business Suite, registered under the Purchasing (PO) product family. It is documented in ETRM as "Retrofitted," indicating it was carried forward from an earlier release into the 12.1.1 and 12.2.2 code lines rather than being introduced as a new object. The view presents request-for-quotation (RFQ) line detail — the individual solicitation lines on which suppliers are invited to quote — in a denormalized form suited to reporting and integration consumption.

Functionally, POBV_RFQ_LINES answers the question "what are the quotable lines on each RFQ?" by joining RFQ lines to their parent documents, their line types, and their operating units in a single select. Because it exposes descriptive attributes such as item description, unit price, supplier product number, and quantity boundaries without requiring consumers to resolve foreign keys manually, it is well suited to ad hoc reporting, downstream extracts, and interfaces that must read RFQ structure without touching the base transaction tables directly. The view is defined with the WITH READ ONLY clause and therefore cannot be used for DML.

Underlying Base Objects

The view definition selects from four base objects, all accessed through APPS synonyms:

The definition also carries an internal operating-unit security predicate ('_SEC:QL.ORG_ID' IS NOT NULL) that applies the MOAC/security profile of the executing user, so results are automatically restricted to the operating units the user is authorized to access.

Key Columns

The most directly relevant column for the search term maximum_order_quantity is MAXIMUM_ORDER_QUANTITY, sourced as QL.MAX_ORDER_QUANTITY from PO_LINES_ALL. It caps the quantity a supplier may quote or that may be ordered against the RFQ line. Its companion, MINIMUM_ORDER_QUANTITY, sets the lower bound; together they define a quantity band that receiving, pricing, and supplier-response validation can enforce. Other significant columns include RFQ_LINE_ID (PO_LINE_ID), the primary key of the line; LINE_NUMBER; RFQ_ID and RFQ_DOCUMENT_NUMBER (from QU.SEGMENT1); OPERATING_UNIT_ID/OPERATING_UNIT_NAME; LINE_TYPE; ITEM_DESCRIPTION; UNIT_PRICE; SUPPLIER_NOTE (NOTE_TO_VENDOR); SUPPLIER_PRODUCT_NUMBER (VENDOR_PRODUCT_NUM); and the item, category, UOM, project, task, hazard class, and UN number identifiers, plus standard audit columns.

Common Use Cases and Queries

Typical uses include auditing RFQ quantity boundaries, extracting RFQ lines for supplier-portal or sourcing interfaces, and joining to award or quotation tables to compare quoted quantities against the permitted maximum.

  • Locate lines whose quantity ceiling is unusually low or null.
  • Report all RFQ lines for a given operating unit or document number.
  • Feed item, UOM, and price data into integration staging tables.

Sample query:

SELECT rfq_document_number, line_number, item_description,
       minimum_order_quantity, maximum_order_quantity, unit_price
  FROM apps.pobv_rfq_lines
 WHERE operating_unit_name = :p_org
   AND maximum_order_quantity IS NOT NULL
 ORDER BY rfq_document_number, line_number;

Because the view is read-only and security-filtered, it can be queried safely by reporting users without risk of modifying RFQ data.