Results for “pobv_requests_for_quotation”

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

Overview

The POBV_REQUESTS_FOR_QUOTATION view is an APPS-owned database object in the Oracle E-Business Suite Purchasing (PO) module, classified as a business view (indicated by the POBV prefix). It presents a consolidated, security-enabled reporting layer over Requests for Quotation (RFQs) stored in the procurement tables, exposing header-level RFQ data alongside descriptive lookups and descriptive flexfield references. The view is documented as "Valid" and "Retrofitted," indicating it is maintained for backward compatibility, typically to preserve the column interfaces expected by Oracle Reports, BLV-style business views, or OAF-based inquiry pages across release 12.1.1 and 12.2.2.

A defining characteristic is its filter QU.TYPE_LOOKUP_CODE = 'RFQ', which restricts the result set to RFQ documents only, excluding quotations and other purchasing document types residing in PO_HEADERS_ALL. The view also embeds row-level security through the predicate '_SEC:QU.ORG_ID' IS NOT NULL, which the EBS security engine substitutes at runtime with the set of operating units accessible to the current user, and terminates with WITH READ ONLY to prevent DML.

Underlying Base Objects

The view is defined over three documented base objects, each accessed through public synonyms in the APPS schema:

• PO_HEADERS_ALL (alias QU) — the primary source, supplying all RFQ header attributes including document number, dates, vendor references, buyer, currency, and terms.
• PO_DOCUMENT_TYPES_ALL (alias QT) — joined with an outer join on QU.QUOTE_TYPE_LOOKUP_CODE = QT.DOCUMENT_SUBTYPE(+) to retrieve the document subtype name (TYPE_NAME), yielding the QUOTATION_TYPE column.
• HR_ALL_ORGANIZATION_UNITS (alias OP) — joined on QU.ORG_ID = OP.ORGANIZATION_ID to resolve the operating unit name.

Key Columns

The view maps RFQ attributes to business-friendly column names, several of which are descriptive flexfield or lookup references expressed as _LA: tokens:

• REQUEST_FOR_QUOTATION_ID — the RFQ header identifier (PO_HEADER_ID).
• DOCUMENT_NUMBER — the RFQ number (SEGMENT1).
• OPERATING_UNIT_ID / OPERATING_UNIT_NAME — the owning operating unit.
• QUOTATION_TYPE — the document subtype name from PO_DOCUMENT_TYPES_ALL, directly relevant to users searching on "quotation_type."
• "_LA:QUOTATION_CLASS" and "_LA:STATUS" — lookup-derived quotation class and RFQ/quote status values.
• START_EFFECTIVE_DATE, END_EFFECTIVE_DATE, CLOSED_DATE, REPLY_DUE_DATE — key RFQ lifecycle dates.
• SUPPLIER_ID, SUPPLIER_SITE_ID, SUPPLIER_CONTACT_ID, BUYER_ID — sourcing party and buyer references.
• CURRENCY_CODE, CURRENCY_CONVERSION_RATE, CURRENCY_CONVERSION_RATE_TYPE, PAYMENT_TERMS_ID, CARRIER — commercial terms.
• "_LA:REPLY_METHOD", "_LA:FREIGHT_TERM", "_LA:FREE_ON_BOARD_POINT" — lookup-driven attributes.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — audit columns.

Common Use Cases and Queries

This view is typically used in custom reports, concurrent programs, and integrations that need a secured list of RFQs with decoded status and type. A representative query filtering on quotation_type is:

• SELECT document_number, operating_unit_name, quotation_type, "_LA:STATUS" status, reply_due_date, supplier_id FROM apps.pobv_requests_for_quotation WHERE quotation_type = 'Standard RFQ' ORDER BY document_number;
• SELECT document_number, quotation_type, closed_date FROM apps.pobv_requests_for_quotation WHERE closed_date IS NULL; — to identify open RFQs.

Because the view enforces ORG_ID security and is read-only, it is suitable for inquiry and extraction but not for maintenance; updates must target PO_HEADERS_ALL directly. Note that QUOTATION_TYPE derives from the outer-joined PO_DOCUMENT_TYPES_ALL table and may be null where no document subtype is defined.