Search Results hz_message_obj_tbl




Overview
Explore in AI Chat

Overview

APPS.HZ_AIA_CUSTOM_PKG is a customer-model integration package within the Oracle E-Business Suite Trading Community Architecture (TCA). The $Header artifact (ARHAIACS.pls 120.0, dated 2007/12/06) identifies it as a no-ship, customer-specific extension seeded under the AR product family. Its declared purpose is to support Account Information Architecture (AIA) synchronization and customer merge processing for the Oracle Customer Model, providing programmatic hooks that allow external or downstream applications to propagate customer account changes and to assemble the business-object collections required when parties, accounts, or related organizations are merged.

The package operates on TCA public business objects, principally HZ_ORG_CUST_BO and its table type HZ_ORG_CUST_BO_TBL, together with the merge object structures CRMINTEG_HZ_MERGE_OBJ and CRMINTEG_HZ_MERGE_OBJ_TBL. It follows the standard Oracle API conventions: a validation flag (p_validate_bo_flag) initialized to FND_API.G_TRUE, a FND_API-style message list, and paired x_return_status and x_messages OUT parameters.

Key Procedures and Functions

  • SYNC_ACCT_UPDATE — Synchronizes an account update event for a supplied organization/customer business object, accepting the caller module and object source and returning status, messages, and the processed object.
  • SYNC_ACCT_ORDER — Parallel routine that synchronizes account order information, using the same validation-flag, message-list, and return-object pattern as SYNC_ACCT_UPDATE.
  • GET_ACCT_MERGE_OBJ — Retrieves the account merge business object for a given customer merge header identifier, used to stage account-level merge data.
  • GET_RELATED_ORG_CUST_OBJS — Returns the collection of organization/customer objects related to a merge batch and a specified merge-to party.
  • GET_PARTY_MERGE_OBJS — Returns the party merge objects associated with a merge batch and merge-to party.
  • GET_MERGE_ORG_CUSTS — Given from/to organization and account identifiers, assembles the organization/customer objects participating in the merge, honoring the p_init_msg_list flag and returning status and messages.

Tables Accessed

The package reads and writes core TCA and merge entities. Customer and account structures include HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNTS_M, HZ_CUST_ACCOUNT_ROLES, HZ_CUST_ACCOUNT_ROLES_M, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_ACCT_SITES_ALL_M, and HZ_CUST_SITE_USES_ALL. Party and contact data is drawn from HZ_ORG_CONTACTS and HZ_CONTACT_POINTS. Merge processing relies on HZ_MERGE_BATCH, HZ_MERGE_DICTIONARY, HZ_MERGE_PARTIES, and HZ_MERGE_PARTY_HISTORY. Business-object definitions are resolved through HZ_BUS_OBJ_DEFINITIONS, and environment defaults are read from AR_SYSTEM_PARAMETERS.

Usage Notes

HZ_AIA_CUSTOM_PKG is not referenced by any other documented package, indicating it is invoked directly rather than called internally by the TCA API stack. It is typically exercised through account merge concurrent programs, customer-model integration flows, or custom PL/SQL wrappers that must synchronize account updates and orders across systems. Because the package is classified OTHER and marked noship in the source header, it must be treated as a customization: release upgrades may overwrite or remove it. Any dependent code should be registered against the customer's own change-control baseline, and callers should always inspect x_return_status and x_messages before committing, since the message list is the sole channel for validation and processing errors.