Search Results destination_customer_id




Overview
Explore in AI Chat

Overview

APPS.ICX_PO_REQUISITION_LINES_INQ_V is an Oracle E-Business Suite internal inquiry view owned by the APPS schema. It exposes requisition line information in a denormalized, display-ready form designed for the Oracle iProcurement and iSupplier style self-service inquiry flows maintained by the ICX (Oracle iProcurement) product. The view carries FND Design Data reference ICX.ICX_PO_REQUISITION_LINES_INQ_V and is documented with the Oracle Internal Use Only warning, meaning Oracle Corporation does not support direct customer access to the underlying data except through standard Oracle Applications programs. Its companion inquiry packages are PO_INQ_SV and PO_REQS_INQ_SV, which the view depends on for derived and translated values.

The view is read-only by construction. It presents one row per requisition line, keyed by ROW_ID (ROWID), REQUISITION_HEADER_ID, and REQUISITION_LINE_ID, and augments core purchasing columns with human-readable descriptions such as DEST_ORGANIZATION, DELIVER_TO_LOCATION, ITEM_DESCRIPTION, and DISPLAY_UNIT_PRICE. This makes it well suited to line-level inquiry, approval notification rendering, and lightweight reporting that must not traverse the transactional tables directly.

Underlying Base Objects

The documented base objects are broad and span purchasing, inventory, HR, and financials:

The view joins PO_REQUISITION_LINES to its header, resolves item, category, and vendor key flexfields through the _KFV synonyms, converts currency via the GL and FND packages, and applies HR_SECURITY so users see only authorized organizations and locations.

Key Columns

Identity and classification columns include ROW_ID, REQUISITION_HEADER_ID, REQUISITION_LINE_ID, LINE_NUM, LINE_TYPE, LINE_TYPE_ID, ITEM_ID, ITEM_REVISION, CATEGORY_ID, and ITEM_DESCRIPTION. Quantity and price columns include QUANTITY, QUANTITY_RECEIVED, QUANTITY_DELIVERED, QUANTITY_CANCELLED, UNIT_PRICE, and DISPLAY_UNIT_PRICE. Status and workflow indicators include CANCEL_FLAG, ON_RFQ_FLAG, RFQ_REQUIRED_FLAG, MODIFIED_BY_AGENT_FLAG, ENCUMBERED_FLAG, and URGENT.

Destination and sourcing columns include DESTINATION_TYPE_CODE, SOURCE_TYPE_CODE, DEST_ORGANIZATION, DELIVER_TO_LOCATION, DEST_SUBINVENTORY, SOURCE_ORGANIZATION, and SOURCE_SUBINVENTORY. Procurement detail columns include SUGGESTED_VENDOR_NAME, SUGGESTED_VENDOR_LOCATION, SUGGESTED_VENDOR_CONTACT, SUGGESTED_VENDOR_PHONE, NEED_BY_DATE, REFERENCE_NUM, UN_NUMBER, HAZARD_CLASS, and TRANSACTION_REASON. Note columns include NOTE_TO_AGENT, NOTE_TO_RECEIVER, and JUSTIFICATION. Forty-plus ATTRIBUTEn columns carry descriptive flexfield content.

On the searched term destination_customer_id: the documented column list for this view does not include a DESTINATION_CUSTOMER_ID column. Customer destination context in requisition lines is typically carried through the destination type code, the ATTRIBUTEn descriptive flexfield segments, or the underlying PO_REQUISITION_LINES row rather than a named view column. Users who need customer-level destination identification should inspect the DFF attributes exposed here or query the base table or a customer-specific view.

Common Use Cases and Queries

Typical uses are line-detail inquiry screens, approval notification content, and read-only extracts for downstream reporting. A basic line listing filtered by header:

SELECT requisition_line_id, line_num, item_description, quantity, unit_price, need_by_date
FROM apps.icx_po_requisition_lines_inq_v
WHERE requisition_header_id = :p_header_id
ORDER BY line_num;

Destination and sourcing review:

SELECT requisition_line_id, destination_type_code, dest_organization, deliver_to_location, dest_subinventory
FROM apps.icx_po_requisition_lines_inq_v
WHERE destination_type_code IS NOT NULL;

Because the view performs HR security and lookup resolution, it is preferable to the base synonym for user-facing queries, while bulk batch interfaces should use PO_REQUISITION_LINES directly to avoid the additional join cost.