Search Results header_min_release_amount

Overview

PO_NEGOTIATED_SOURCES_V is an APPS-owned database view in the Oracle E-Business Suite Purchasing (PO) module, described in ETRM metadata as "Negotiated Sources." It consolidates blanket purchase agreements, quotations, and planned purchase orders—the negotiated, non-standard sourcing documents—together with their vendor, contact, line, and shipment details into a single denormalized query surface. Its principal role is to serve as the data source for negotiated-source inquiry, sourcing reference reports, and integrations that require vendor price and sourcing information without navigating the many normalized purchasing tables directly.

The object is reported as VALID under ETRM 12.2.2 metadata and exists in the same form in 12.1.1, since Purchasing's negotiated-document schema is largely unchanged across the two releases.

The user's search term, header_freight_terms_code, does not appear as a column name in the view text. The view instead exposes PH.FREIGHT_TERMS_LOOKUP_CODE at the header level and PLL.FREIGHT_TERMS_LOOKUP_CODE at the line-location level, so callers searching for that term should query these columns.

Underlying Base Objects

The view is built primarily over PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, and PO_LINE_TYPES, and joins outward to supporting entities:

• Vendor data: AP_SUPPLIERS, AP_SUPPLIER_CONTACTS, AP_SUPPLIER_SITES_ALL, HZ_PARTIES.
• Terms and financials: AP_TERMS, GL_SETS_OF_BOOKS, FINANCIALS_SYSTEM_PARAMETERS, MTL_PARAMETERS, PO_SYSTEM_PARAMETERS.
• Document classification: PO_DOCUMENT_TYPES_ALL_B, PO_DOCUMENT_TYPES_ALL_TL, PO_LOOKUP_CODES, PO_GA_ORG_ASSIGNMENTS.
• Personnel and locations: PER_ALL_PEOPLE_F, HR_ALL_ORGANIZATION_UNITS_TL, HR_LOCATIONS_ALL_TL.

It additionally relies on the FND_GLOBAL package for session-level context such as org and user identification.

Key Columns

• PO_HEADER_ID, SEGMENT1 — document identifier and document number.
• VENDOR_ID, VENDOR_NAME, VENDOR_CONTACT_ID — supplier identity and contact.
• TYPE_LOOKUP_CODE, TYPE_NAME — negotiated document type (e.g., BLANKET, QUOTATION, PLANNED).
• AGENT_ID, FULL_NAME — buyer/agent responsible for the document.
• TERMS_ID, NAME — payment terms.
• FREIGHT_TERMS_LOOKUP_CODE, FOB_LOOKUP_CODE, SHIP_VIA_LOOKUP_CODE — header and line-location shipping and freight attributes.
• CURRENCY_CODE, BLANKET_TOTAL_AMOUNT, AMOUNT_LIMIT, MIN_RELEASE_AMOUNT — pricing and commitment limits.
• PO_LINE_ID, LINE_NUM, ITEM_ID, UNIT_PRICE, QUANTITY — line-level sourcing details.
• LINE_LOCATION_ID, SHIP_TO_LOCATION_ID, LEAD_TIME, START_DATE, END_DATE — shipment scheduling and lead time.

Common Use Cases and Queries

Typical reports list active blanket agreements by supplier, show negotiated pricing by item, or extract freight and FOB terms for sourcing analysis.

SELECT po_header_id, segment1, vendor_name, freight_terms_lookup_code,
       terms_id, currency_code, start_date, end_date
FROM   po_negotiated_sources_v
WHERE  type_lookup_code = 'BLANKET'
AND    NVL(freight_terms_lookup_code,'X') = 'X';

Integrations frequently filter by vendor and item to retrieve the latest negotiated price:

SELECT segment1, item_id, unit_price, currency_code
FROM   po_negotiated_sources_v
WHERE  vendor_id = :p_vendor_id
AND    item_id  = :p_item_id;