Search Results ap_duplicate_vendors_pk




Overview

AP_DUPLICATE_VENDORS_ALL is a Payables (AP) module table in the AP schema that stores supplier information used by the Supplier Merge process. Its Row Source documentation identifies it as "Supplier information used by Supplier Merge," and it is classified as VALID within the E-Business Suite 12.1.1 and 12.2.2 data model. The table acts as a repository of candidate duplicate supplier and supplier site pairings that the Supplier Merge concurrent program evaluates and processes, capturing both the duplicate record and the surviving record along with supporting statistical measures (such as invoice counts and amounts) that help the application determine the impact of merging one supplier into another.

From a heuristic Data Vault modeling perspective, mined from its foreign key structure, this object is best classified as a link table. It resolves a relationship between suppliers and supplier sites (the duplicate and the retained entity), rather than representing a standalone business entity (hub) or purely descriptive attributes (satellite). The relationship-centric nature of the primary key, ENTRY_ID, and the presence of two foreign key references into PO_VENDOR_SITES_ALL support this interpretation. The documented physical schema contains 20 columns under owner AP.

Key Information Stored

The table's primary key is AP_DUPLICATE_VENDORS_PK, defined on the ENTRY_ID column, which serves as the surrogate identifier for each duplicate processing record.

Common Use Cases and Queries

The primary use case is driving and auditing the Supplier Merge process. Payables administrators and technical consultants query this table to preview, verify, and reconcile duplicate supplier consolidations. Typical SQL patterns include identifying pending duplicate records and linking them to site details:

  • Listing duplicates awaiting processing: SELECT ENTRY_ID, VENDOR_ID, DUPLICATE_VENDOR_ID, PROCESS_FLAG FROM AP_DUPLICATE_VENDORS_ALL WHERE PROCESS_FLAG IS NULL OR PROCESS_FLAG = 'N';
  • Quantifying merge impact: SELECT VENDOR_ID, SUM(NUMBER_UNPAID_INVOICES), SUM(AMOUNT_UNPAID_INVOICES) FROM AP_DUPLICATE_VENDORS_ALL GROUP BY VENDOR_ID;
  • Joining to sites: SELECT d.ENTRY_ID, s.VENDOR_SITE_CODE FROM AP_DUPLICATE_VENDORS_ALL d, PO_VENDOR_SITES_ALL s WHERE d.VENDOR_SITE_ID = s.VENDOR_SITE_ID;

Reporting use cases include pre-merge impact assessment reports, post-merge reconciliation, and detection of suppliers with paid invoices that require special handling.

Related Objects

The documented foreign keys tie AP_DUPLICATE_VENDORS_ALL to the supplier site master, and the wider Supplier Merge process engages additional Payables and Purchasing objects.

  • PO_VENDOR_SITES_ALL — Referenced twice via VENDOR_SITE_ID and DUPLICATE_VENDOR_SITE_ID.
  • PO_VENDORS — Supplier master referenced through VENDOR_ID and DUPLICATE_VENDOR_ID.
  • AP_SUPPLIERS — Payables supplier layer corresponding to vendor records.
  • AP_SUPPLIER_SITES_ALL — Payables site layer aligned with the site identifiers.
  • AP_INVOICES_ALL — Invoice data underlying the count and amount columns.
  • PO_HEADERS_ALL — Purchase order headers affected by merge, linked to NUMBER_PO_HEADERS_CHANGED.
  • AP_SUPPLIER_MERGE — The Supplier Merge concurrent program and associated logic.