Search Results init_hz_party_rec_v2




Overview

AST_API_RECORDS_V2PKG is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, classified under the "OTHER" API category. Its primary design objective is to serve as a record initialization utility layer for the Oracle TCA (Trading Community Architecture) public APIs, particularly the HZ_PARTY_V2PUB, HZ_PARTY_SITE_V2PUB, HZ_LOCATION_V2PUB, and HZ_CONTACT_POINT_V2PUB packages. Rather than performing direct business logic or DML operations, this package provides a standardized mechanism for constructing and returning empty (null-initialized) record structures that correspond to the complex nested record types defined within the TCA public API layer.

The package follows a consistent pattern: each function declares a local variable of a specific record type, leaves it uninitialized (thus all fields default to NULL), and returns it to the caller. This approach provides custom developers and internal Oracle code with a predictable, reusable way to obtain a "clean slate" record before populating individual fields for a TCA API call such as creating or updating a party, location, or contact point.

Key Procedures and Functions

The package exposes 28 documented functions, grouped by the TCA entity they support:

No parameter lists are documented for these functions; each takes no arguments and simply returns a freshly declared record.

Tables Accessed

The ETRM metadata does not document any direct table references accessed via APPS synonyms. This is consistent with the package's design: it operates entirely on PL/SQL record types and does not execute SQL against base tables. Any persistence to HZ_ and other TCA tables occurs in the calling public API packages (such as HZ_PARTY_V2PUB), not within AST_API_RECORDS_V2PKG itself.

Usage Notes

This package is typically invoked as a preparatory step before calling TCA public APIs, allowing developers to obtain a properly typed, null-initialized record rather than declaring the record manually. It is referenced by two other packages within the E-Business Suite, indicating internal Oracle dependency. Custom integrations, concurrent programs, and forms-based extensions that create or update TCA parties, locations, or contact points commonly use these initializer functions to reduce boilerplate and ensure compatibility with the evolving TCA record definitions. In 12.1.1 and 12.2.2, the package remains an APPS-owned utility and should be called only from within the database tier, never modified directly.