Results for “number_po_headers_changed”

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

Overview

The APPS.AP_DUPLICATE_VENDORS_V view is a Payables (AP) reporting object that presents duplicate supplier and supplier site information collected by the Oracle Payables duplicate supplier identification process. The view is defined over the AP_DUPLICATE_VENDORS table and joined to the supplier and supplier site definitions held in the Purchasing schema, exposing both the surviving ("kept") supplier and the duplicate supplier side by side. Although the object remains VALID in the APPS schema at 12.1.1 and 12.2.2, the ETRM documentation explicitly annotates the description as "(Release 10SC Only)", indicating that the underlying duplicate-supplier functionality is a legacy feature that has been superseded by the Oracle Supplier Network and later supplier merge and duplicate-prevention capabilities. The view is nevertheless retained in the data dictionary for backward compatibility, and its VENDOR_SITE_CODE and DUP_VENDOR_SITE_CODE columns make it a useful reference point when resolving supplier site identifiers during duplicate analysis, reconciliation, and migration projects.

Underlying Base Objects

The documented base objects are:

• AP_DUPLICATE_VENDORS (SYNONYM) — The primary driver object. It stores one row per detected duplicate pairing, including entry identifiers, processing flags, and calculated invoice counts and amounts.
• PO_VENDORS (VIEW) — Joined twice, as PV (duplicate side, using VENDOR_ID) and PV1 (kept side, using VENDOR_ID), supplying the VENDOR_NAME and DUP_VENDOR_NAME values.
• PO_VENDOR_SITES (VIEW) — Also joined twice, as PVS and PVS1, supplying VENDOR_SITE_CODE and DUP_VENDOR_SITE_CODE.
• FND_GLOBAL (PACKAGE) — Referenced for session context such as ORG_ID, which is exposed as a column to support multi-org filtering.

All supplier and site joins are outer joins ((+) notation), so a duplicate record is returned even if the corresponding supplier or site definition cannot be resolved.

Key Columns

• ENTRY_ID — Identifier of the duplicate detection entry.
• VENDOR_ID / VENDOR_SITE_ID — The retained supplier and supplier site.
• DUPLICATE_VENDOR_ID / DUPLICATE_VENDOR_SITE_ID — The supplier and site flagged as duplicates.
• VENDOR_SITE_CODE / DUP_VENDOR_SITE_CODE — Supplier site codes for the retained and duplicate sides respectively; these are the columns users identify by the search term vendor_site_code.
• VENDOR_NAME / DUP_VENDOR_NAME — Supplier names for each side of the pairing.
• NUMBER_PAID_INVOICES, AMOUNT_PAID_INVOICES, NUMBER_UNPAID_INVOICES, AMOUNT_UNPAID_INVOICES — Invoice activity statistics used to judge the financial impact of merging or removing the duplicate.
• PAID_INVOICES_FLAG, KEEP_SITE_FLAG, PROCESS, PROCESS_FLAG — Control flags governing merge behavior.
• PROCESS_INVOICE — DECODE-derived helper: P when process is paid, otherwise B or I.
• PO_CHECK_BOX — DECODE-derived flag yielding N for process I, otherwise Y.
• ORG_ID — Operating unit identifier.

Common Use Cases and Queries

Because the view exposes both a retained and a duplicate site code, it is commonly queried when validating supplier site references prior to merge or purge activity. A typical query resolves the site codes for a given entry:

• SELECT entry_id, vendor_id, vendor_name, vendor_site_code, duplicate_vendor_id, dup_vendor_name, dup_vendor_site_code FROM ap_duplicate_vendors_v WHERE org_id = :p_org_id;
• SELECT vendor_site_code, dup_vendor_site_code, number_unpaid_invoices, amount_unpaid_invoices FROM ap_duplicate_vendors_v WHERE process_flag IS NULL ORDER BY vendor_site_code;

These queries assist in identifying which duplicates still require processing, sizing open invoice exposure, and confirming that the correct VENDOR_SITE_CODE is preserved before the duplicate supplier site is removed or merged.