Search Results lines_all

Overview

IBE_CUSTOMER_ACCT_PVT is a private (PVT-classified) PL/SQL API package owned by the APPS schema in Oracle E-Business Suite. It belongs to the iStore (IBE) application family and is defined with AUTHID CURRENT_USER, meaning its SQL executes under the privileges of the calling session rather than the package owner. The package's core business purpose, as stated in its header comments, is to retrieve a valid InvoiceTo (BillTo) or ShipTo party site identifier for the currently logged-in user, applying a defined precedence of address selection rules. Beyond simple retrieval, the package also exposes procedures for creating customer account roles, customer account sites, and customer account site uses, making it a consolidation layer for common party and customer-account operations required by iStore self-service flows. Its original header indicates an early revision (115.1, dated 2003), and it remains a documented object in the ETRM repository for 12.2.2.

Key Procedures and Functions

The ETRM metadata documents eight procedures in the package. Documented behaviours are as follows:

• GETPARTYSITEID — Returns a valid party site identifier for a given party and site-use type. The selection logic is explicitly documented: it first checks whether the user has a Primary BillTo address and returns that identifier; if no primary BillTo exists, it returns the first non-primary BillTo address; if no valid BillTo address is found, it falls back to the first valid address of any other site-use type (for example ShipTo).
• CREATE_PARTY_SITE_USE — Creates a party site use record and returns the resulting site use identifier. Note that this procedure appears commented out in the header excerpt.
• CREATE_CUST_ACCOUNT_ROLE — Creates a customer account role and returns the generated role identifier, associating a party, customer account, and account site with a role type.
• CREATE_CUST_ACCT_SITE — Creates a customer account site record for a party or account identifier.
• CREATE_CUST_ACCT_SITE_USE — Creates a customer account site use record.
• GET_CUST_ACCOUNT_SITE_USE — Retrieves customer account site use information.
• GET_CUST_ACCT_ROLE — Retrieves customer account role information.
• GETCUSTOMERACCTDATA — Retrieves consolidated customer account data for the calling context.

All procedures follow the standard EBS API convention of accepting p_api_version_number, p_init_msg_list, and p_commit arguments and returning x_return_status, x_msg_count, and x_msg_data for error handling.

Tables Accessed

The package operates almost entirely within the Oracle Trading Community Architecture (TCA) and Receivables customer model. It references the following objects through APPS synonyms:

• HZ_PARTIES, HZ_PARTY_SITES, HZ_PARTY_SITE_USES — party and party-site foundation data used by GETPARTYSITEID and site-use creation.
• HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES, HZ_CUST_SITE_USES_ALL — the customer account, account site, and site-use tables that the creation and retrieval procedures read and write, including the _ALL variants that expose multi-org records.
• HZ_CUST_ACCOUNT_ROLES — target table for CREATE_CUST_ACCOUNT_ROLE and source for GET_CUST_ACCT_ROLE.
• HZ_CONTACT_POINTS, HZ_LOCATIONS — contact and address detail supporting site resolution.
• HZ_RELATIONSHIPS, HZ_ROLE_RESPONSIBILITY — relationship and role/responsibility context used to determine the current user's applicable customer role.
• HR_ORGANIZATION_INFORMATION — organization-level information used to resolve the operating context of the party.

Usage Notes

Because this is a private package, it is not intended for direct invocation by external applications or customer extensions; it is called internally by other iStore packages. The ETRM metadata records that IBE_CUSTOMER_ACCT_PVT is referenced by one other package, which supplies the calling context. In practice the package is invoked from iStore self-service user interfaces (checkout, address selection, and account administration) and from concurrent programs that need to resolve or provision a user's default BillTo or ShipTo site. Developers working on customizations should treat the public IBE APIs and the standard TCA/HZ public APIs (such as HZ_CUST_ACCOUNT_V2PUB and HZ_PARTY_SITE_V2PUB) as the supported integration points, reserving direct calls to this package for internal extension only when the private signature is fully understood and version stability has been verified.