Search Results receive_close_tolerance

Overview

The view ICX_PO_RFQ_LINE_LOC_V belongs to the Oracle iProcurement (ICX) product family and is documented in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. Its ETRM description is recorded simply as Obsolete, and the implementation metadata states that it is not implemented in the database. This means the object is a vestigial definition retained in the data model documentation but no longer compiled or deployed in a standard installation. Historically, the view served to expose RFQ (Request for Quotation) shipment and line-location information — quantity, pricing, discount, lead time, ship-to details, and terms — to iProcurement sourcing and requisitioning screens. Because it is obsolete, no supported reporting or integration path should depend on it in 12.1.1 or 12.2.2; it is retained here primarily for impact analysis and migration awareness.

Underlying Base Objects

Although the ETRM "Referenced base objects" field is blank, the documented view text shows the view is defined over the following base tables:

• PO_LINE_LOCATIONS (alias PLL) — the driving table supplying shipment-level detail.
• PO_HEADERS (alias POH) — joined on PO_HEADER_ID and restricted to TYPE_LOOKUP_CODE = 'RFQ', ensuring only quotation documents are returned.
• HR_LOCATIONS (alias HRL) — outer-joined to provide the ship-to location code.
• ORG_ORGANIZATION_DEFINITIONS (alias OOD) — outer-joined to supply ship-to organization code and name.
• AP_TERMS (alias APT) — outer-joined on TERMS_ID for payment terms name.
• AP_TAX_CODES (alias ATC) — outer-joined on TAX_CODE_ID for the tax code name.

The view performs no filtering beyond the RFQ document-type restriction in PO_HEADERS, and exposes the full set of line-location columns.

Key Columns

The projection mirrors the PO_LINE_LOCATIONS structure. Relevant columns include:

• ROWID, PO_HEADER_ID, PO_LINE_ID, LINE_LOCATION_ID — primary identifiers for the header, line, and shipment.
• SHIPMENT_NUM, SHIPMENT_TYPE — shipment sequencing and classification.
• SHIP_TO_ORGANIZATION_ID, ORGANIZATION_CODE, ORGANIZATION_NAME, SHIP_TO_LOCATION_ID, LOCATION_CODE — destination details.
• QUANTITY, UNIT_MEAS_LOOKUP_CODE — quoted quantity and unit of measure.
• PRICE_OVERRIDE, PRICE_DISCOUNT — the pricing fields that match the "price_discount" search term. PRICE_DISCOUNT holds the discount applied to the shipment price, while PRICE_OVERRIDE records a negotiated override.
• LAST_ACCEPT_DATE, NEED_BY_DATE, START_DATE, END_DATE — validity and required-by dates.
• LEAD_TIME, LEAD_TIME_UNIT — supplier lead-time information.
• TERMS_ID, NAME (APT) — payment terms.
• FREIGHT_TERMS_LOOKUP_CODE, FOB_LOOKUP_CODE, SHIP_VIA_LOOKUP_CODE, ATC.NAME — freight, FOB, ship-via, and tax code descriptors.
• TAXABLE_FLAG, INSPECTION_REQUIRED_FLAG, RECEIPT_REQUIRED_FLAG, RECEIVE_CLOSE_TOLERANCE, QTY_RCV_EXCEPTION_CODE — control flags.
• FROM_HEADER_ID, FROM_LINE_ID, FROM_LINE_LOCATION_ID — reference back to the originating document.
• Audit columns (LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE, PROGRAM_ID, etc.) and the fifteen ATTRIBUTE columns with ATTRIBUTE_CATEGORY.

Common Use Cases and Queries

In legacy customizations this view was queried for RFQ shipment pricing and discount data. Because it is obsolete and not implemented, equivalent logic should now be sourced directly from PO_LINE_LOCATIONS joined to PO_HEADERS, HR_LOCATIONS, ORG_ORGANIZATION_DEFINITIONS, AP_TERMS, and AP_TAX_CODES. A typical historical query pattern was:

SELECT h.segment1, pll.price_discount, pll.quantity
FROM   po_headers h, po_line_locations pll
WHERE  h.po_header_id = pll.po_header_id
AND    h.type_lookup_code = 'RFQ';

Such queries should be redirected to the base tables for supported behavior. Any existing report or interface referencing ICX_PO_RFQ_LINE_LOC_V should be reviewed during upgrade or assessment to remove the obsolete dependency.