Results for “vendor_number”

50+ results




Overview
Explore in AI Chat

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

Overview

AP_SRS_PAYEE_V is a Payables (AP) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its purpose is to expose a consolidated list of payees that can be referenced by payment-related reports and integrations, particularly those associated with supplier reimbursement and external payee processing. The view derives its name from the Supplier Reimbursement System (SRS) payee context and returns one row per distinct payee party, along with an optional supplier number.

The view plays a bridging role between the supplier master, the payments party model, and the Trading Community Architecture (TCA) party registry. Because it presents both registered suppliers and non-supplier payees in a single result set, it is useful wherever a caller must enumerate payees without knowing in advance whether a payee is a full supplier or only an external payee. This is directly relevant to user searches for "vendor_number," since the VENDOR_NUMBER column carries the supplier's SEGMENT1 value for supplier-backed payees.

Underlying Base Objects

Per the documented ETRM metadata, AP_SRS_PAYEE_V is defined over three base objects, all referenced through synonyms in the APPS schema:

The view is a UNION of two branches. The first branch joins AP_SUPPLIERS, IBY_EXTERNAL_PAYEES_ALL, and HZ_PARTIES on PARTY_ID, returning supplier-backed payees with a populated VENDOR_NUMBER. The second branch returns parties registered as external payees in IBY_EXTERNAL_PAYEES_ALL that have no matching AP_SUPPLIERS row, using a NOT EXISTS subquery and emitting NULL for VENDOR_NUMBER. Both branches GROUP BY the selected party attributes and the whole result is ordered by the first column (PAYEE_NAME).

Key Columns

  • PAYEE_NAME — the party name from HZ_PARTIES.PARTY_NAME. This is the display name of the payee and is the ordering key.
  • VENDOR_NUMBER — the supplier number, drawn from AP_SUPPLIERS.SEGMENT1. It is NULL for payees that exist only as external payees and are not registered suppliers.
  • PAYEE_PARTY_ID — the TCA party identifier (HZ_PARTIES.PARTY_ID / AP_SUPPLIERS.PARTY_ID), which uniquely ties each row back to the party model and to IBY_EXTERNAL_PAYEES_ALL.

The NULL capability of VENDOR_NUMBER is significant: it distinguishes supplier records from pure external payees, and any consumer of the view should expect and handle NULLs when matching or filtering on vendor_number.

Common Use Cases and Queries

The view supports reconciliation, lookup, and integration scenarios in which a caller needs to resolve a payee to a supplier number or enumerate payees by name. Typical uses include populating payment or reimbursement report pick lists, validating that a party has an external payee registration, and locating the vendor number associated with a payee party.

To find the vendor number for a given payee name:

SELECT payee_name, vendor_number, payee_party_id
FROM   apps.ap_srs_payee_v
WHERE  payee_name = :p_payee_name;

To list only those payees that are registered suppliers (non-NULL vendor numbers):

SELECT payee_name, vendor_number
FROM   apps.ap_srs_payee_v
WHERE  vendor_number IS NOT NULL
ORDER  BY vendor_number;

To identify external payees that are not suppliers:

SELECT payee_name, payee_party_id
FROM   apps.ap_srs_payee_v
WHERE  vendor_number IS NULL;

To resolve a party identifier to its payee details:

SELECT payee_name, vendor_number
FROM   apps.ap_srs_payee_v
WHERE  payee_party_id = :p_party_id;

Because the view already performs the grouping and union internally, callers should treat it as a read-only reporting interface and avoid assuming a one-to-one mapping between payee name and vendor number.