Search Results po_autosource_vendors




Overview
Explore in AI Chat

Overview

PO_AUTOSOURCE_VENDORS is a table in the PO schema of Oracle E-Business Suite, belonging to the Purchasing (PO) product family. Per the ETRM documentation, its description is recorded simply as "No longer used." This designation indicates that the table is a legacy or deprecated object retained in the schema for backward compatibility, historical data retention, or to satisfy referential integrity expectations from earlier releases, rather than an actively maintained transactional entity.

Historically, the table supported the Oracle Purchasing automatic sourcing feature, which allowed buyers to define rules by which the system would suggest or assign approved suppliers to requisition lines or purchase order lines. The columns AUTOSOURCE_RULE_ID, VENDOR_ID, VENDOR_RANK, and SPLIT together suggest that the table originally held a ranked list of candidate vendors associated with a sourcing rule, including the ability to split sourcing across multiple suppliers based on rank.

From a Data Vault modeling perspective, the metadata's heuristic classification identifies this object as a link. This is consistent with its composite primary key (AUTOSOURCE_RULE_ID, VENDOR_ID), which resolves a many-to-many relationship between sourcing rules and vendors. In a Data Vault design, this would model as a link table connecting a sourcing-rule hub and a vendor hub.

Key Information Stored

The table contains 30 documented columns. The most significant are:

  • AUTOSOURCE_RULE_ID — Part of the composite primary key; foreign key to PO_AUTOSOURCE_RULES. Identifies the sourcing rule to which the vendor association applies.
  • VENDOR_ID — Part of the composite primary key; foreign key to PO_VENDORS. Identifies the supplier candidate.
  • VENDOR_RANK — Ordinal priority of the vendor within the rule, used to sequence supplier suggestions.
  • SPLIT — A distribution or allocation indicator, likely used to control how sourcing is divided among ranked vendors.
  • ORG_ID — Operating unit identifier, supporting multi-org partitioning of sourcing rule data.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns capturing who last modified the row and when.
  • CREATION_DATE, CREATED_BY — Audit columns capturing initial row creation.
  • REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program context columns indicating the request that inserted or updated the row.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The standard Oracle EBS descriptive flexfield (DFF) columns.

The surrogate primary key is defined by PO_AUTOSOURCE_VENDORS_PK on (AUTOSOURCE_RULE_ID, VENDOR_ID). The unique index PO_AUTOSOURCE_VENDORS_U1 on the same column pair represents the business-key candidate, reinforcing that rule-vendor combination is the natural uniqueness constraint.

Common Use Cases and Queries

Because the table is documented as no longer used, primary use cases center on historical reporting, data migration, and impact analysis rather than operational purchasing flows.

  • Historical sourcing analysis — Retrieving the ranked vendor lists previously configured per sourcing rule:

    SELECT v.VENDOR_NAME, av.VENDOR_RANK, av.SPLIT FROM PO.PO_AUTOSOURCE_VENDORS av JOIN PO.PO_VENDORS v ON av.VENDOR_ID = v.VENDOR_ID WHERE av.AUTOSOURCE_RULE_ID = :rule_id ORDER BY av.VENDOR_RANK;

  • Rule-level aggregation — Counting vendors per sourcing rule to understand former sourcing breadth:

    SELECT AUTOSOURCE_RULE_ID, COUNT(*) FROM PO.PO_AUTOSOURCE_VENDORS GROUP BY AUTOSOURCE_RULE_ID;

  • Migration and archival assessment — Identifying whether legacy rows exist before decommissioning or archiving, typically filtered by ORG_ID for a given operating unit.
  • Audit tracing — Using LAST_UPDATE_DATE, CREATED_BY, and REQUEST_ID to trace who loaded or changed vendor sourcing assignments.

Related Objects

The following objects are referenced or closely associated with PO_AUTOSOURCE_VENDORS based on the documented foreign keys and known Purchasing schema relationships:

  • PO_AUTOSOURCE_RULES — Parent table of the sourcing rule; joined via PO_AUTOSOURCE_VENDORS.AUTOSOURCE_RULE_ID = PO_AUTOSOURCE_RULES.AUTOSOURCE_RULE_ID.
  • PO_VENDORS — Supplier master; joined via PO_AUTOSOURCE_VENDORS.VENDOR_ID = PO_VENDORS.VENDOR_ID.
  • PO_VENDOR_SITES_ALL — Vendor site detail, typically joined through VENDOR_ID to enrich supplier reporting.
  • PO_REQUISITION_HEADERS_ALL and PO_REQUISITION_LINES_ALL — Requisition entities formerly populated through sourcing rules.
  • PO_HEADERS_ALL and PO_LINES_ALL — Purchase order entities that may have consumed autosource suggestions.
  • PO_AGENTS — Buyers associated with sourcing rules, useful for contextual reporting.