Search Results import_vendors

Overview

APPS.POS_BATCH_IMPORT_PKG is the core PL/SQL package body that drives the Oracle Payables supplier batch import process in Oracle E-Business Suite 12.1.1 and 12.2.2. It orchestrates the loading of supplier records from the open interface tables into the production supplier tables, performing validation, rejection handling, and the transfer of vendor, vendor site, and vendor contact information. The package is the engine behind the "Import Suppliers" concurrent program, which is the standard mechanism used to bring external vendor data—received through the Supplier Open Interface—into Oracle Payables.

The source header identifies the file as POSSUPIMPB.pls at version 120.10, indicating a long-maintained component of the supplier import subsystem. The package carries module-level constants for the FND logging framework and derives environment context from fnd_global.user_id and fnd_global.login_id, reflecting the standard Oracle API conventions of audit stamping and debug logging.

Key Procedures and Functions

The ETRM metadata documents three procedures or functions in this package. Each serves a distinct role in the batch import lifecycle.

• IMPORT_BATCH — The main driver procedure. It processes a batch of supplier interface records, coordinates the movement of data from the interface tables into the base supplier tables, and invokes the appropriate validation and rejection logic when records fail. This is the entry point typically called by the concurrent program.
• CHK_VENDOR_NUM_NMBERING_METHOD — A validation routine that checks the vendor numbering method configuration. It verifies whether supplier numbers are system-generated or manually entered, and enforces the corresponding numbering rules against incoming interface records.
• GET_PARTY_ID — A lookup function that retrieves the party identifier associated with a supplier. In Release 12, the TCA (Trading Community Architecture) model ties suppliers to HZ party records, so this function resolves the party relationship needed to correctly create or match supplier and party records during import.

Additional internal functions such as INSERT_REJECTIONS support the rejection-handling mechanism, writing failed records to POS_SUPPLIER_INT_REJECTIONS with an associated reject code so that users can review and correct them before reprocessing.

Tables Accessed

The package reads and writes an extensive set of interface and base tables. On the interface side, it works with AP_SUPPLIERS_INT, AP_SUPPLIER_SITES_INT, and AP_SUP_SITE_CONTACT_INT, which hold staged supplier, site, and contact data. It writes rejected rows to AP_SUPPLIER_INT_REJECTIONS. On the base side, it inserts or updates AP_SUPPLIERS, AP_SUPPLIER_SITES_ALL, and AP_SUPPLIER_CONTACTS.

Because R12 uses TCA, the package also references HZ_CLASS_CODE_DENORM and HZ_CODE_ASSIGNMENTS to resolve party classification and code assignment data. Configuration and setup tables consulted include AP_PRODUCT_SETUP, FINANCIALS_SYSTEM_PARAMETERS, FND_LOOKUP_VALUES, FND_LANGUAGES, and FND_PROFILE_OPTION_VALUES. Concurrent request context is captured from FND_CONCURRENT_REQUESTS.

Usage Notes

POS_BATCH_IMPORT_PKG is invoked principally through the "Import Suppliers" concurrent program in Oracle Payables, which submits the batch import on behalf of the user. It is not intended for direct interactive use, although custom code may call it to programmatically load vendor data. Because it manipulates core supplier tables and relies on profile options and setups, it should be run only by users with appropriate Payables responsibility and after interface data has been populated and validated. Common search terms such as import_vendors refer to this same import functionality, since "vendor" and "supplier" are synonymous in R12. The package is referenced by one other package, indicating it is also called internally within the supplier import framework rather than exclusively from the concurrent program.