Search Results chk_vendor_num_nmbering_method




Overview
Explore in AI Chat

Overview

POS_BATCH_IMPORT_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the batch import of supplier (vendor) records in Oracle Payables. It forms part of the supplier interface framework that allows large volumes of supplier, supplier site, and supplier contact data to be loaded into the EBS base tables from external or legacy source systems. The package operates against the open interface tables (AP_SUPPLIERS_INT, AP_SUPPLIER_SITES_INT, AP_SUP_SITE_CONTACT_INT) and the corresponding production tables (AP_SUPPLIERS, AP_SUPPLIER_SITES_ALL, AP_SUPPLIER_CONTACTS), validating and transforming staged rows before they are merged into the live supplier records. In the context of EBS 12.1.1 and 12.2.2, it is a supporting component of the Supplier Interface concurrent process, and it is referenced by POS_MERGE_SUPPLIER_PKG, indicating its use during supplier merge and data consolidation scenarios as well. The package is classified as an API of type OTHER within the ETRM repository, and its status is VALID.

Key Procedures and Functions

  • IMPORT_BATCH — The primary driver procedure, responsible for processing a set of supplier interface records as a batch. It reads staged rows, applies validation rules, and coordinates the movement of supplier, site, and contact information into the base tables, recording rejections where validation fails.
  • CHK_VENDOR_NUM_NMBERING_METHOD — Determines and validates the vendor numbering method in effect, ensuring that the supplier number being imported conforms to the configured numbering scheme (for example, automatic versus manual numbering as defined in Payables system setup).
  • GET_PARTY_ID — Returns the party identifier associated with a supplier, supporting the association of supplier records with the correct TCA (Trading Community Architecture) party in the HZ registry, which is essential for correct supplier-party linkage.

Tables Accessed

The package references a range of tables through APPS synonyms. Interface and base supplier tables include AP_SUPPLIERS_INT, AP_SUPPLIERS, AP_SUPPLIER_SITES_INT, AP_SUPPLIER_SITES_ALL, AP_SUP_SITE_CONTACT_INT, and AP_SUPPLIER_CONTACTS, which hold the staged and final supplier, site, and contact data. AP_SUPPLIER_INT_REJECTIONS stores rows that fail validation. AP_PRODUCT_SETUP and FINANCIALS_SYSTEM_PARAMETERS provide Payables control settings, including supplier numbering options. FND_LANGUAGES, FND_LOOKUP_VALUES, and FND_PROFILE_OPTION_VALUES supply language, lookup, and profile option data used during validation. FND_CONCURRENT_REQUESTS links the import activity to its concurrent program request. HZ_CLASS_CODE_DENORM and HZ_CODE_ASSIGNMENTS support the TCA party and code assignment logic, while AP_SUPPLIERS and the party-related tables are used together to resolve the supplier-to-party relationship via GET_PARTY_ID.

Usage Notes

POS_BATCH_IMPORT_PKG is typically invoked indirectly by the Oracle Payables Supplier Open Interface concurrent program (often run as part of supplier batch import), rather than being called directly by end users. It may also be called from custom PL/SQL scripts that load supplier data into the interface tables and then trigger the import. Because it is referenced by POS_MERGE_SUPPLIER_PKG, it participates in supplier merge processing, where supplier records are consolidated. Developers integrating with EBS should treat it as an internal supporting package rather than a formally published API; where a public interface is required, Oracle recommends using the supported Supplier Open Interface or corresponding TCA APIs. As with all APPS schema objects, callers must ensure correct initialization of the FND session context and appropriate privileges before invocation.