Results for “suggested_vendor_phone”

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

Overview

ICX_REQ_DIST_HEADER_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the ICX (Oracle iProcurement) product family. Its documented description is "Account Distribution Header View." In practice, the view presents a denormalized, join-ready projection of requisition header, line, and distribution information, oriented toward iProcurement shopping and requisition display flows rather than toward the raw normalized transactional model. It combines header-level attributes from PO_REQUISITION_HEADERS with line-level attributes from PO_REQUISITION_LINES and distribution-level attributes from PO_REQ_DISTRIBUTIONS, exposing them under user-friendly column aliases such as CART_ID, CART_LINE_ID, and CART_LINE_NUMBER. These aliases reflect the iProcurement shopping cart metaphor, in which a requisition is presented as a cart and each requisition line as a cart line. The view is therefore best understood as a presentation and integration layer: it shields callers from the underlying primary key and foreign key structure, applies currency formatting through the FND_CURRENCY package, and makes the requisition data consumable by iProcurement pages, concurrent programs, and custom extensions.

Underlying Base Objects

The ETRM metadata for 12.2.2 records the following referenced base objects: PO_REQUISITION_HEADERS, PO_REQUISITION_LINES, and PO_REQ_DISTRIBUTIONS, all accessed as synonyms; GL_SETS_OF_BOOKS and ORG_ORGANIZATION_DEFINITIONS, accessed as views; and the packages FND_CURRENCY, HR_GENERAL, HR_SECURITY, and ICX_UTIL. The core relational relationship is the standard requisition hierarchy: PO_REQUISITION_HEADERS is joined to PO_REQUISITION_LINES on REQUISITION_HEADER_ID, and PO_REQUISITION_LINES is joined to PO_REQ_DISTRIBUTIONS on REQUISITION_LINE_ID. GL_SETS_OF_BOOKS supplies CURRENCY_CODE, which is passed to FND_CURRENCY.SAFE_GET_FORMAT_MASK to format unit price into a display mask. ORG_ORGANIZATION_DEFINITIONS supports destination and expenditure organization lookups, while HR_GENERAL and HR_SECURITY participate in resolving personnel and applying security restrictions appropriate to the iProcurement session. ICX_UTIL is used for iProcurement-specific utility logic. Because the view is described as VALID in the APPS schema, it is safe to query directly from custom reports and integrations subject to the same security expectations as other APPS-owned iProcurement views.

Key Columns

The view exposes a mixture of identifiers, descriptive attributes, financial values, and descriptive flexfield columns. Cart and line identity columns include CART_ID, REQUISITION_NUMBER, SHOPPER_ID, CART_LINE_ID, CART_LINE_NUMBER, and LINE_ID. Descriptive columns include ITEM_DESCRIPTION, ITEM_ID, ITEM_REV, UNIT_OF_MEASURE, QUANTITY, CATEGORY_ID, and LINE_TYPE_ID. Financial columns include UNIT_PRICE, formatted via FND_CURRENCY.SAFE_GET_FORMAT_MASK using the set of books currency, and EXT_PRICE, computed as QUANTITY multiplied by UNIT_PRICE. The view also carries supplier suggestion columns: SUGGESTED_BUYER_ID, SUGGESTED_VENDOR_NAME, SUGGESTED_VENDOR_SITE, SUGGESTED_VENDOR_CONTACT, SUGGESTED_VENDOR_PHONE, and SUGGESTED_VENDOR_ITEM_NUM, the last mapping from SUGGESTED_VENDOR_PRODUCT_CODE. Distribution and delivery columns include EXPENDITURE_TYPE, DESTINATION_ORGANIZATION_ID, DELIVER_TO_LOCATION_ID, NEED_BY_DATE, EXPENDITURE_ORGANIZATION_ID, PROJECT_ID, TASK_ID, and EXPENDITURE_ITEM_DATE. Line-level descriptive flexfield columns ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 are exposed as LINE_ATTRIBUTE_CATEGORY and LINE_ATTRIBUTE1 through LINE_ATTRIBUTE15.

Common Use Cases and Queries

Typical uses include custom requisition reports, iProcurement-style cart extracts, supplier suggestion analysis, and integration feeds to external purchasing or analytics systems. A representative query retrieving supplier contact details for open requisitions follows:

• SELECT requisition_number, cart_line_number, item_description, quantity, unit_price, ext_price, suggested_vendor_name, suggested_vendor_site, suggested_vendor_contact, suggested_vendor_phone FROM apps.icx_req_dist_header_v WHERE suggested_vendor_contact IS NOT NULL AND need_by_date >= SYSDATE ORDER BY requisition_number, cart_line_number;

• Aggregating spend by vendor: SELECT suggested_vendor_name, SUM(ext_price) FROM apps.icx_req_dist_header_v WHERE suggested_vendor_name IS NOT NULL GROUP BY suggested_vendor_name;

• Extracting distribution detail for a specific cart: SELECT cart_id, cart_line_id, expenditure_organization_id, project_id, task_id, expenditure_item_date FROM apps.icx_req_dist_header_v WHERE cart_id = :p_cart_id;

The presence of HR_SECURITY and HR_GENERAL in the view definition indicates that results may be subject to row-level security based on the querying user; consumers should not assume unrestricted visibility across all preparers. Because UNIT_PRICE is returned as a formatted character string rather than a numeric value, arithmetic should generally rely on EXT_PRICE or on the underlying PO_REQUISITION_LINES.UNIT_PRICE column directly.