Results for “primary_vendor_item”

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

Overview

The PO_APPROVED_SUPPLIER_LIST table, owned by the PO schema within the Purchasing module, stores the Approved Supplier List (ASL) for an Oracle E-Business Suite implementation. An ASL entry defines which supplier, supplier site, or manufacturer is authorized to supply a specific item or item category to a given organization. It is the authoritative source that sourcing rules, requisitions, purchase orders, and receiving logic consult to determine approved sources of supply. The table is valid in both 12.1.1 and 12.2.2, and for 12.2.2 it is documented with 40 columns.

Under the heuristic Data Vault classification mined from its foreign key structure, the table is a link. This is a natural modeling suggestion: each row associates a vendor, a vendor site, a manufacturer, and an item or category within an owning and using organization, acting as a many-to-many resolver. The surrogate primary key is ASL_ID via constraint PO_APPROVED_SUPPLIER_LIST_PK.

Key Information Stored

The table carries 40 documented columns. The most operationally significant include:

• ASL_ID — surrogate primary key; also the unique-index candidate PO_APPROVED_SUPPLIER_LIST_U1. It is the join key leveraged by all dependent child tables.
• VENDOR_ID and VENDOR_SITE_ID — foreign keys to PO_VENDORS and PO_VENDOR_SITES_ALL, identifying the approved supplier and site.
• MANUFACTURER_ID — foreign key to MTL_MANUFACTURERS, used when the ASL is defined at the manufacturer level.
• ITEM_ID and CATEGORY_ID — define the scope of approval, either by inventory item or by purchasing category.
• OWNING_ORGANIZATION_ID and USING_ORGANIZATION_ID — establish organizational context for the approval.
• ASL_STATUS_ID — the lifecycle status of the ASL record (e.g., approved, pending, inactive).
• DISABLE_FLAG — indicates whether the ASL record is disabled.
• PRIMARY_VENDOR_ITEM — flag identifying the preferred vendor item relationship.
• MANUFACTURER_ASL_ID — self-referencing link to a manufacturer-level ASL.
• REVIEW_BY_DATE — date by which the approved source should be reviewed.
• COMMENTS and the ATTRIBUTE_CATEGORY / ATTRIBUTE1–15 descriptive flexfield columns for user-defined data.
• Standard Who/audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, plus REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, and PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical scenarios include reporting on which vendors are approved for a given item, validating that a requisition or PO line references an approved source, and auditing ASL records that are approaching or past their review date. A common query joins the ASL to vendor and item master data:

• List active approved suppliers for an item: SELECT a.asl_id, a.vendor_id, a.vendor_site_id, a.item_id FROM po_approved_supplier_list a WHERE a.item_id = :item_id AND NVL(a.disable_flag,'N') = 'N'.
• Join to PO_VENDORS and PO_VENDOR_SITES_ALL for supplier names and site details.
• Identify ASLs due for review using REVIEW_BY_DATE relative to SYSDATE.
• Trace downstream activity by joining dependent tables such as PO_ASL_ATTRIBUTES and PO_ASL_DOCUMENTS on ASL_ID.

Related Objects

The table sits at the center of an ASL sub-model. It references PO_VENDORS (VENDOR_ID), PO_VENDOR_SITES_ALL (VENDOR_SITE_ID), and MTL_MANUFACTURERS (MANUFACTURER_ID). Numerous child tables reference ASL_ID, including PO_ASL_DOCUMENTS, PO_ASL_ATTRIBUTES, PO_SUPPLIER_ITEM_CAPACITY, POR_FAVORITE_LIST_LINES, ICX_CAT_PRICE_HISTORY, ICX_CAT_ITEM_PRICES, MSC_ST_ITEM_SUPPLIERS, MRP_AD_SI_CAPA, and MTL_CONSUMPTION_TXN_TEMP. These relationships make PO_APPROVED_SUPPLIER_LIST the pivotal link for sourcing, procurement, and planning integrations.