Search Results ast_api_records_v2pkg




Overview
Explore in AI Chat

Overview

APPS.AST_API_RECORDS_V2PKG is a PL/SQL package in the Oracle E-Business Suite 12.1.1 / 12.2.2 environment that serves as a record-initialization utility layer for the Oracle TCA (Trading Community Architecture) public APIs used by the Oracle Sales and Marketing / customer data model. The package is classified under the generic "OTHER" API classification and carries a VALID status in the ETRM (E-Business Suite Technical Reference Manual) metadata. Its central role is to normalize and pre-populate the complex record structures (PL/SQL record types) that are required by the Version 2 (V2) public APIs of the HZ schema. Before a caller can invoke a TCA public API such as HZ_PARTY_V2PUB.CREATE_PARTY, it must populate a large, position-sensitive record with default values and mandatory placeholders. AST_API_RECORDS_V2PKG encapsulates that preparation logic so that upstream callers do not have to construct each record field-by-field. The package depends on FND_API, the standard EBS API framework, and on the full family of TCA V2 public APIs, indicating that it is tightly coupled to the customer/party data model.

Key Procedures and Functions

ETRM documents 28 procedures and functions. All of the listed entry points are initialization routines, each responsible for establishing a clean, defaulted record structure for a specific TCA entity:

The consistent naming convention ("INIT_" prefix and "_V2" suffix) confirms that each routine is a parameter/defaulting helper tied to the corresponding TCA V2 API.

Tables Accessed

The metadata does not enumerate specific base tables accessed directly; instead, the package's dependency list shows it calls through to the HZ V2 public APIs, which in turn read and write the underlying TCA tables (such as HZ_PARTIES, HZ_PERSON_PROFILES, HZ_ORGANIZATION_PROFILES, HZ_LOCATIONS, HZ_CONTACT_POINTS, HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, and HZ_PARTY_SITES). Because AST_API_RECORDS_V2PKG is an initialization layer, it primarily manipulates in-memory record structures and only causes physical table access indirectly when the caller subsequently invokes the corresponding HZ public API. Any direct table reference would be through APPS synonyms, but the documented dependency set is limited to packaged API calls rather than standalone DML.

Usage Notes

AST_API_RECORDS_V2PKG is referenced by two other packages, AST_PARTY_LOCATIONS_V2PUB and IEX_CUST_OVERVIEW_PVT, which confirms its role as a shared initialization utility within the Sales (AST) and Interaction Center (IEX) modules. Typical invocation is from custom PL/SQL that must create or update party, location, contact, or customer account data programmatically. The standard pattern is: call the relevant INIT_ routine to obtain a defaulted record, overlay the caller's business values, and then pass that record to the corresponding HZ_*_V2PUB procedure. Because record structures in the TCA V2 APIs are large and change between releases, using these initialization routines is the supported method to insulate custom code from structural changes. The package is not intended for end-user invocation through forms or concurrent programs directly; it is a technical building block for developers extending Oracle EBS customer and party functionality.