Search Results supplier_part_number




Overview
Explore in AI Chat

Overview

ICX_POR_REQ_ASLS is an Oracle E-Business Suite view owned by the APPS schema and defined in the ICX (Oracle iProcurement) product. It presents a consolidated, denormalized perspective of the Approved Supplier List (ASL) as it is consumed by the iProcurement requisitioning flow. Its principal purpose is to expose supplier, supplier site, and sourcing attributes—including the value commonly searched as supplier_part_number—in a form that iProcurement can query when building requisitions, sourcing rules, and punchout or catalog pricing lookups.

The view is delivered in a VALID state in both 12.1.1 and 12.2.2 and is designed primarily for internal consumption by iProcurement application logic rather than as an end-user reporting object. Nevertheless, technical consultants frequently query it to reconcile ASL sourcing data with requisition lines and to validate supplier part number maintenance.

Underlying Base Objects

ICX_POR_REQ_ASLS is defined over several base objects, joined to produce a single sourcing row per ASL entry:

The join to FND_GLOBAL is also documented in the referenced-object list, reflecting that the view operates within the session context (org/operating unit) established by EBS security.

Key Columns

Common Use Cases and Queries

Typical scenarios include validating which supplier part numbers are approved for an item, reconciling iProcurement requisitions back to ASL entries, and auditing vendor-site sourcing by operating unit. A representative query retrieving supplier part numbers for an item is:

  • SELECT asl_id, supplier, supplier_site_code, unit_of_measure, currency, supplier_part_number FROM apps.icx_por_req_asls WHERE item_id = :p_item_id AND inventory_organization_id = :p_org_id;
  • Filtering by supplier_part_number supports troubleshooting where users search using a manufacturer or vendor part number within iProcurement.
  • Joining to PO_REQUISITION_LINES_ALL via ITEM_ID and SUPPLIER_ID helps confirm that a requisitioned line traced to a valid approved ASL source.

Because the view is not indexed directly, queries should be constrained by the driving keys (ITEM_ID, SUPPLIER_ID, INVENTORY_ORGANIZATION_ID) and rely on the underlying PO_APPROVED_SUPPLIER_LIST indexes for performance.