Search Results ota_tea

Overview

OTAP_CMERGE is a private PL/SQL package body owned by APPS that participates in the Oracle Trading Community Architecture (TCA) customer account merge process. Its specific responsibility is to propagate the surviving customer identifier across Oracle Order Management and Oracle Service contracts booking data whenever two customer records are merged in Oracle Receivables. In the Oracle E-Business Suite 12.1.1 and 12.2.2 environments, account merges are orchestrated by the Customer Merge concurrent program, which drives a series of table-specific merge routines registered with the merge engine. OTAP_CMERGE is one such registered routine, handling the OTA schema's booking and finance tables that would otherwise retain references to the duplicate (obsolete) customer.

The package is classified as OTHER in the ETRM 12.2.2 repository, meaning it is not part of a public API surface and is intended for internal invocation only. The body header reflects a legacy 120.0 revision dated 2005, consistent with the long-standing stability of the TCA merge framework.

Key Procedures and Functions

• MERGE — The single documented entry point. It is the public driver invoked by the customer merge engine for each request and set number. Internally the body defines private helper procedures, such as OTA_TBD (account merge routine for OTA_BOOKING_DEALS), which perform the row-level update of duplicate customer IDs to the surviving party. The MERGE routine honours a process mode parameter (for example a LOCK mode that short-circuits processing) and otherwise opens a cursor over RA_CUSTOMER_MERGES joined to the affected OTA tables, bulk collects the affected keys, and calls HZ_ACCT_MERGE_UTIL to load the merge set before applying updates.

The documented procedure set is limited to MERGE; all other routines in the body are private and not part of the callable interface.

Tables Accessed

• OTA_BOOKING_DEALS — the principal booking transaction table; duplicate customer IDs are replaced with the surviving ID.
• OTA_DELEGATE_BOOKINGS, OTA_EVENT_ASSOCIATIONS, OTA_FINANCE_HEADERS, OTA_NOTRNG_HISTORIES — related booking, event, finance, and notification history rows that carry the customer reference and must be re-pointed.
• RA_CUSTOMER_MERGES and RA_CUSTOMER_MERGE_HEADERS — Oracle Receivables merge staging tables supplying the request ID, set number, DUPLICATE_ID and process flag used to drive the merge.
• HZ_CUSTOMER_MERGE_LOG and HZ_CUSTOMER_MERGE_LOG_S — TCA merge audit log structures updated to record the affected entities.
• HZ_CUST_ACCT_SITES_ALL, HZ_LOCATIONS, HZ_PARTY_SITES — location and site data consulted to resolve surviving account site information.
• PLITBLM — a generic PL/SQL index-by table used by the EBS merge framework for bulk collection work areas.

Usage Notes

OTAP_CMERGE is not called directly by end users or custom forms. It is registered with the TCA Customer Merge framework, which invokes the package's MERGE procedure as part of the Account Merge concurrent request (RAXTRX or equivalent). In Oracle EBS 12.1.1 and 12.2.2, the package is executed in the context of the APPS schema and depends on HZ_ACCT_MERGE_UTIL, FND_PROFILE (specifically the HZ_AUDIT_ACCT_MERGE profile option), and ARP_MESSAGE for message substitution. Because the ETRM metadata records zero referencing packages, no other PL/SQL unit depends on it symbolically, and there is no supported path for custom code to invoke it outside the standard merge program. Administrators troubleshooting merge failures involving booking deals should examine the HZ_CUSTOMER_MERGE_LOG entries produced by this package and confirm that the Customer Merge request completed without error.