Search Results create_vendor_site

Overview

The APPS.POS_AP_SUPPLIER_SITE_BO_PKG package body is a business-object (BO) layer component within the Oracle E-Business Suite Payables and Payments architecture that encapsulates the logic required to create and retrieve supplier site information. Its primary purpose is to serve as a programmatic gateway for the creation of vendor sites, including the associated disbursement and external payee setup required for payment processing. The package is classified under the ETRM with an API classification of OTHER and is owned by the APPS schema. It forms part of the broader supplier management surface, sitting above the base AP_VENDOR_PUB_PKG interfaces and coordinating with the Payments (IBY) modules to ensure that a newly created supplier site is properly registered as an external payee for disbursement purposes. The package is particularly relevant to integrations and extensions that need to automate supplier site creation without invoking the standard supplier entry forms. The source header indicates a last revision in the 12.2 code line (120.2.12020000.4), confirming its applicability to Oracle EBS 12.2.2, with behavior consistent with the 12.1.1 release family.

Key Procedures and Functions

The ETRM metadata documents two procedures hosted by this package:

• CREATE_POS_SUPPLIER_SITE_BO — The core business-object routine responsible for creating a supplier site. Based on the package body excerpt, the public entry point create_vendor_site accepts a supplier site record (p_site_rec) of type ap_vendor_pub_pkg.r_vendor_site_rec_type along with an external payee record (ext_payee_rec) and the standard API return parameters (x_return_status, x_msg_count, x_msg_data). The routine orchestrates the creation of the vendor site, deriving identifiers such as the vendor site ID, party site ID, and location ID, and additionally manages the creation of the external payee and associated bank account records through the IBY APIs. This procedure is the target of the user search term "create_vendor_site."
• GET_POS_SUPPLIER_SITES_BO_TBL — A retrieval routine that returns a table of supplier site business objects. It is used to query existing supplier site definitions in bulk, supporting consumers that need to display or process multiple sites for a given supplier.

Tables Accessed

The package reads and writes several base tables through APPS synonyms, as documented in the ETRM metadata:

• AP_SUPPLIERS — The supplier header table, accessed to validate and associate the site with its parent supplier.
• AP_SUPPLIER_SITES_ALL — The supplier site table, which is the principal write target where the new site row is inserted.
• AP_TERMS — The payment terms table, referenced to resolve and validate payment term assignments for the site.
• HZ_ORIG_SYS_REFERENCES — The TCA origin system reference table, used to maintain cross-references between the supplier site entity and its originating system identifiers.
• IBY_TEMP_EXT_BANK_ACCTS — The temporary external bank account table used by the Payments module during disbursement setup and external payee creation.
• PLITBLM — A PL/SQL index-by table used internally for bulk processing and message handling.

Usage Notes

This package is typically invoked programmatically rather than interactively. It is called by custom concurrent programs, integration scripts, and extension code that automate supplier site creation, particularly where external payee and disbursement setup must be performed in the same transaction. Standard Oracle forms for supplier entry call lower-level public APIs, but the business-object layer represented here is suited to bulk or service-oriented processing. Callers must supply a valid API version and initialize the message list in accordance with the standard EBS API calling convention, and must inspect x_return_status and the message stack upon completion. Because the package participates in the external payee creation flow, errors in the IBY setup can affect the overall result and should be handled by the calling application. The reference to FND_GLOBAL.CONC_REQUEST_ID indicates the package records the concurrent request context, reinforcing its use from concurrent processing. The ETRM notes that this object is referenced by one other package, confirming its role as a subordinate component in a larger supplier business-object hierarchy.