Search Results hz_cust_accounts_pkg




Overview
Explore in AI Chat

Overview

HZ_CUST_ACCOUNTS_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It is classified in the ETRM repository as an "OTHER" API and holds a VALID status, indicating that it is a compiled, active database object within the Oracle Trading Community Architecture (TCA) data model. The package provides the low-level row maintenance logic for the HZ_CUST_ACCOUNTS entity, the central table that stores customer account records in TCA. Every customer account created through Oracle Receivables, Order Management, or any TCA-enabled application ultimately resolves to a row in HZ_CUST_ACCOUNTS, and this package encapsulates the insert, update, delete, locking, and retrieval operations against that table and its related sequence and intersection tables.

The package depends on the SYS.STANDARD package, confirming that it relies only on core PL/SQL built-in functionality rather than other custom APIs. Its restricted dependency footprint is characteristic of a table-handler package that performs direct DML rather than a full public business API.

Key Procedures and Functions

The ETRM metadata documents five procedures within HZ_CUST_ACCOUNTS_PKG. Parameter lists are intentionally not reproduced here; the descriptions below summarise each program unit's purpose.

  • INSERT_ROW — Creates a new customer account row in the base table. It is the entry point for persisting a newly constructed account record, including the assignment of the account number and the writing of the corresponding primary-key and secure columns.
  • UPDATE_ROW — Modifies an existing customer account record. It applies changed attribute values to the base table row and is typically paired with the audit columns used throughout TCA.
  • LOCK_ROW — Acquires a row-level lock on a specified customer account, providing pessimistic concurrency control so that subsequent updates within the same transaction cannot be overwritten by a competing session.
  • SELECT_ROW — Retrieves a single customer account row into the calling program's variables, serving as the standard read accessor for the package.
  • DELETE_ROW — Removes a customer account row from the base table, supporting cleanup and correction scenarios.

The absence of documented public business-layer functions (such as account-creation wrappers) confirms that this package operates at the persistence layer rather than exposing business validation rules.

Tables Accessed

The package references four objects through APPS synonyms:

  • HZ_CUST_ACCOUNTS — the primary base table holding customer account records; the target of INSERT_ROW, UPDATE_ROW, and DELETE_ROW, and the source for SELECT_ROW and LOCK_ROW.
  • HZ_CUST_ACCOUNTS_S — the TCA secure/translation table that stores the descriptive, language-dependent attributes of the account alongside a reference to the base row.
  • HZ_ACCOUNT_NUM_S — the sequence-backed object used to generate unique customer account numbers when new accounts are inserted.
  • DUAL — the standard Oracle utility table, used for single-row expression evaluation and sequence access.

Usage Notes

HZ_CUST_ACCOUNTS_PKG is referenced by one other package, HZ_CUST_ACCOUNT_V2PUB, which is the documented public TCA API for customer account maintenance. This relationship establishes the intended call path: applications and custom code should invoke the V2PUB API, which performs business validation and then delegates persistence to HZ_CUST_ACCOUNTS_PKG. Direct invocation from Oracle Forms is not part of the documented design, since TCA forms communicate through the public APIs. The package is therefore encountered primarily in the context of API-driven integrations, concurrent programs that import or migrate customer data, and custom PL/SQL that requires controlled record-level access to HZ_CUST_ACCOUNTS. Because DELETE_ROW and UPDATE_ROW perform unguarded DML, callers must supply their own validation and should use LOCK_ROW to serialise concurrent modification. In releases 12.1.1 and 12.2.2 the package remains schema-resident in APPS and is compiled against the synonyms described above.