Search Results sync_vendorsite

Overview

ITG_SYNCSUPPLIERINBOUND_PVT is an Oracle E-Business Suite private (PVT) PL/SQL package owned by APPS. It implements the inbound supplier synchronization logic used by Oracle's supplier integration framework, allowing external or upstream systems to create, update, and delete supplier header, supplier site, and supplier contact records in the EBS Procurement schema. In the Oracle EBS 12.1.1 and 12.2.2 releases, the package belongs to the "ITG" (Integration/Internet Technology Group) namespace and forms part of the supplier data hub architecture through which vendor master data is propagated into the trading community model.

The package accepts inbound supplier synchronization requests distinguished by a sync indication flag (values such as 'A' for add, 'C' for change, and 'D' for delete), maps the external payload into the internal supplier structures, invokes the relevant Trading Community Architecture (TCA) and Payables APIs, and returns status information to the caller. Because it is classified as a private package, it is not part of the published, supported public API surface; it is intended to be called only by higher-level supplier synchronization programs within the same integration stack, and one other package in the environment is documented as referencing it.

Key Procedures and Functions

• SYNC_VENDOR — Synchronizes the supplier header record. It processes the sync indicator, supplier name, one-time flag, partner identifier, active status, currency, DUNS number, parent identifier, payment method, tax identifier, payment terms, and US-flag control attributes, along with the control date and the operating unit (MOAC) organization. It returns a standard API return status and message count/data, plus a supplier information record type containing the resolved vendor identifier, currency, payment method, terms, VAT number, control date, and address style.
• SYNC_VENDORSITE — Synchronizes supplier site/address information for an existing supplier. It accepts address line components (up to four lines), city, country, county, site code, and related address attributes, and creates or updates the corresponding supplier site in the Payables model.
• SYNC_VENDORCONTACT — Synchronizes supplier contact records. It creates, updates, or removes the contact persons associated with a supplier and its sites.

Each procedure follows the standard EBS API convention of returning x_return_status (typically 'S', 'E', or 'U'), x_msg_count, and x_msg_data, allowing the caller to retrieve diagnostics through FND_MSG_PUB.

Tables Accessed

The package reads and writes a set of TCA and Payables tables through APPS synonyms. AP_SUPPLIERS stores the supplier header (vendor name, tax identifier, parent relationship, one-time flag, active status). AP_SUPPLIER_SITES holds the site-level addresses and payment attributes. AP_SUPPLIER_CONTACTS stores contact person records. AP_TERMS resolves payment terms identifiers. FINANCIALS_SYSTEM_PARAMS_ALL supplies the financials system parameters, including functional currency and MOAC context. FND_CURRENCIES validates currencies, and FND_TERRITORIES validates country codes. HR_ALL_ORGANIZATION_UNITS provides the operating unit organization context for multi-org security. HZ_LOCATIONS and HZ_PARTIES underpin the TCA party and location records to which suppliers are linked. Read and write patterns differ by procedure: header synchronization predominantly touches AP_SUPPLIERS and HZ_PARTIES, site synchronization touches AP_SUPPLIER_SITES and HZ_LOCATIONS, and contact synchronization touches AP_SUPPLIER_CONTACTS.

Usage Notes

ITG_SYNCSUPPLIERINBOUND_PVT is not invoked directly from standard EBS forms. It is typically called from the inbound supplier synchronization concurrent programs and integration flows that ingest vendor data from external systems such as supplier portals, legacy ERP instances, or third-party procurement networks. Custom code should not call this private package directly; the recommended integration path is through the public supplier APIs (for example, AP_VENDOR_PUB_PKG) or the supported supplier integration interfaces. Because the package performs validation against FND_CURRENCIES, FND_TERRITORIES, and financials system parameters, callers must ensure the correct operating unit context is initialized through MOAC before invocation. In release 12.2.2, the package operates alongside the TCA party model, so changes made through this package must be consistent with party-level supplier records to avoid data inconsistencies between Procurement and the Trading Community Architecture.