Search Results find_duplicate_parties

Overview

POS_SEARCH_DUP_PARTY_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports supplier and party duplicate-detection and registration workflows within the Procurement/Supplier lifecycle (Oracle iSupplier Portal and Supplier Registration). The package is declared with AUTHID CURRENT_USER, meaning its SQL executes under the privileges of the calling user rather than the defining schema, which allows it to be safely exposed to self-service supplier-facing flows. It provides the programmatic foundation behind the "find duplicate parties" requirement: given a set of supplier attributes such as supplier name, alternate name, tax payer identifier, tax registration number, D-U-N-S number, and SIC code, the package determines whether a matching party already exists before a new supplier record is created. When duplication checks complete, it can create or update the underlying TCA organization, record supplier registration mappings, and enable an existing party for use as a supplier. The package is classified as OTHER (not a public, committed API), indicating it is intended primarily for internal consumption by Oracle's supplier registration and duplicate-management screens rather than as a formally supported integration interface.

Key Procedures and Functions

The documented procedures cover the full duplicate-detection and registration lifecycle:

• FIND_DUPLICATE_PARTIES — The primary entry point that accepts supplier identification attributes (supplier name, alternate name, tax payer ID, tax registration number, D-U-N-S number, SIC code, and supplier registration ID) and returns a search context identifier along with standard FND API return status, message count, and message data. This is the procedure associated with the user's search term and is the core duplicate-matching routine.
• POS_CREATE_ORGANIZATION — Creates a new TCA organization party and its associated profile, returning the new party ID, party number, and organization profile ID.
• UPDATE_SUPP_PARTY_ID — Associates a supplier registration record with a resolved party ID, linking the registration to its TCA party.
• POS_UPDATE_ORGANIZATION — Updates the attributes of an existing TCA organization party, returning the resulting profile ID and message information.
• SEARCH_DUPLICATE_PARTIES — An alternate search routine that matches on party name, party number, status, SIC code, and postal address attributes (address, city, state, country), returning a search context identifier.
• ENABLE_PARTY_AS_SUPPLIER — Enables an existing party for use as a supplier.
• ASSIGN_PARTY_USAGE — Assigns party usage to a party, supporting the supplier registration flow.

Tables Accessed

The package reads and writes the following tables through APPS synonyms:

• HZ_PARTIES — The TCA party master, written during organization creation and update and queried during duplicate matching.
• HZ_PARTY_NUMBER_S — The sequence used to generate unique party numbers.
• POS_ADDRESS_REQUESTS and POS_CONTACT_REQUESTS — Supplier registration requests for address and contact data.
• POS_SUPPLIER_REGISTRATIONS — The supplier registration record updated with a resolved party ID.
• POS_SUPPLIER_MAPPINGS — Maps registration data to supplier entities.
• DUAL — Used for single-row query operations.

Usage Notes

POS_SEARCH_DUP_PARTY_PKG is typically invoked indirectly through the Oracle Supplier Registration and iSupplier Portal duplicate-search screens, where a prospective supplier's details are entered and checked against existing parties before registration proceeds. Custom code should note that the package is not designated as a public API; the official interface is the Oracle Supplier Registration UI. When invoking it directly, callers must honor the p_init_msg_list convention and inspect x_return_status, x_msg_count, and x_msg_data using the standard FND API message-handling pattern. The search context identifier returned by FIND_DUPLICATE_PARTIES and SEARCH_DUPLICATE_PARTIES is subsequently consumed by the related create/update routines. The package is referenced by zero other packages per the documented metadata, confirming it is a leaf-level implementation package rather than a shared library.