Results for “hz_account_num_s”

34 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IBE_PARTY_V2PVT is the package body of a private PL/SQL API within the Oracle E-Business Suite iStore (IBE) module. Its principal business function is to encapsulate the creation and maintenance of TCA (Trading Community Architecture) party, customer, and contact data on behalf of the iStore self-service application. The package acts as a wrapper layer over the public HZ_*_V2PUB APIs, allowing iStore flows — user registration, business account setup, and contact management — to insert and update records in the HZ schema without exposing the caller directly to the HZ public API surface. The object resides in the APPS schema, holds a VALID status in ETRM 12.2.2, and is classified as an OTHER API.

Key Procedures and Functions

The documented package exposes twelve procedures. Each is described by purpose only; parameter lists are not published here.

Tables Accessed

The package reads and writes the core TCA tables through APPS synonyms. HZ_PARTIES stores party-level records, while HZ_PERSON_LANGUAGE retains language preferences. HZ_CUST_ACCOUNTS and HZ_CUST_ACCOUNT_ROLES hold customer accounts and account role assignments, with account numbers drawn from the HZ_ACCOUNT_NUM_S sequence. HZ_PARTY_SITES and HZ_CONTACT_POINTS store addresses and communication points, and HZ_CONTACT_PREFERENCES records contact preference settings. HZ_ORG_CONTACTS links contacts to organizations, and HZ_RELATIONSHIPS maintains party relationships. DUAL provides single-row selection scaffolding. The package also references the HZ_MO_GLOBAL_CACHE and HZ_*_V2PUB public APIs, the IBE_ADDRESS_V2PVT and IBE_USER_PVT helper packages, FND_API, FND_MESSAGE, FND_MSG_PUB for error handling, and MDSYS.SDO_GEOMETRY for spatial data types.

Usage Notes

IBE_PARTY_V2PVT is a private package body invoked only from within the iStore application layer, not directly by end users. It is called by two other packages during registration and account-update flows, and it coordinates rather than duplicates work performed by the HZ_*_V2PUB public APIs. It is not referenced by any database object other than its two calling packages. Customizations that require party or account creation on behalf of iStore should invoke the public HZ APIs directly; the private signature of IBE_PARTY_V2PVT may change between releases and is not a supported extension point. The dependency on HZ_ACCOUNT_NUM_S is significant for implementations that customize account numbering, since account numbers for iStore-generated customers are obtained through this sequence.