Results for “ar_correspondences”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

ARP_CMERGE_ARDUN is an Oracle Receivables PL/SQL package owned by the APPS schema that participates in the customer merge (party/customer de-duplication) process within Oracle E-Business Suite. Its name reflects its functional anchoring: "CMERGE" denotes customer merge, "AR" denotes the Receivables module, and "DUN" denotes dun (the D-U-N-S number, or Data Universal Numbering System identifier). The package therefore serves as the Receivables-side component responsible for reconciling and consolidating dun-related data — most notably correspondences and dun history — when two customer records are merged into one.

In Oracle EBS 12.1.1 and 12.2.2, the customer merge framework is orchestrated across Trading Community Architecture (TCA) and the Receivables subledger. When a merge request is submitted, the driving merger program invokes a chain of module-specific packages to move or re-point transactional and reference data from the "from" (duplicate) customer to the "to" (surviving) customer. ARP_CMERGE_ARDUN is the entry point that Receivables exposes to that framework for dun-and-correspondence processing. It is classified as a non-API "OTHER" object in the ETRM repository, meaning it is a supporting internal routine rather than a published extension interface, and it is exposed to the merge driver rather than intended for direct customer invocation. The header record indicates a long-lived component, last shipped under revision 120.2.

Key Procedures and Functions

ETRM documents a single callable program unit in this package:

• MERGE — The sole documented procedure. It accepts a request identifier, a set number, and a process mode, and performs the dun-related customer merge for the request/set combination it is passed. The signature accepts req_id (NUMBER), set_num (NUMBER), and process_mode (VARCHAR2). The request identifier ties execution to the parent merge submission; the set number identifies the specific merge set being processed; and the process mode governs the operational behaviour of the call within the merge run. All consolidation of dun data from the duplicate to the surviving customer is driven from this single entry point.

Tables Accessed

The package reads and writes a defined set of Receivables and TCA merge tables through APPS synonyms:

• RA_CUSTOMER_MERGES and RA_CUSTOMER_MERGE_HEADERS — the Receivables customer merge tables recording the merge request, the source and target customers, and the merge header/line detail. The MERGE procedure uses these to resolve the merge participants and record progress.
• AR_CORRESPONDENCES — stores dunning and other customer correspondence. The package re-points or consolidates correspondence history so that the surviving customer inherits the dun records of the duplicate.
• HZ_CUSTOMER_MERGE_LOG and HZ_CUSTOMER_MERGE_LOG_S — the TCA customer merge audit/log table and its sequence, used to record merge activity for the entities touched during dun processing.
• PLITBLM — a PL/SQL index-by or interim table conventionally used for in-process collections within this code family, supporting the set-oriented assembly of records prior to update.

Usage Notes

ARP_CMERGE_ARDUN is not intended for direct customer or partner invocation. It is invoked by the Oracle Receivables customer merge driver as part of a concurrent merge run; the caller supplies the merge request identifier, the set number, and the processing mode. ETRM records the package as referenced by one other package, consistent with its role as a subordinate module in a larger merge orchestration. Because its classification is "OTHER" and no public API contract is documented, customizations should not call MERGE directly; any extension to dun handling during customer merge should be implemented through supported TCA or Receivables merge hooks. During troubleshooting of merge failures involving dunning letters or correspondence, the HZ_CUSTOMER_MERGE_LOG and RA_CUSTOMER_MERGES records, together with the req_id and set_num passed to this procedure, are the primary diagnostic breadcrumbs.