Results for “cs_audit_merge_ship_to_cont”

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

Overview

CS_SR_PARTY_MERGE_PKG is an Oracle E-Business Suite service (TeleService / Customer Care) package whose primary responsibility is to propagate Oracle Trading Community Architecture (TCA) party merge activity into Oracle Service service request data. When two HZ_PARTIES records are merged (for example through the Customer Merge or Supplier Merge concurrent programs), references to the surviving party must be re-pointed from the merged ("from") party to the surviving ("to") party across every dependent application schema. CS_SR_PARTY_MERGE_PKG fulfills that responsibility for the Service module.

The package body carries header version cssrpmgb.pls 120.1 (2005/12/22), indicating it is a long-standing component of the party merge infrastructure shipped with release 11.5.9 and later, and still present in 12.1.1 and 12.2.2. It participates in the standard TCA party merge callout architecture, in which application-owned "party merge handler" packages are invoked by the merge driver (HZ_MERGE_BATCH processing) to update or logically delete rows that reference the merged party.

Key Procedures and Functions

The package exposes seventeen documented procedures, organized into three functional groups.

• Incident (service request) reference updates: CS_INC_ALL_MERGE_PARTY, CS_INC_ALL_MERGE_BILL_TO_CONT, CS_INC_ALL_MERGE_SHIP_TO_CONT, CS_INC_ALL_MERGE_SITE_USES, CS_INC_ALL_MERGE_SHIP_SITE_USE, CS_INC_ALL_MERGE_SITE_ID, CS_INC_ALL_MERGE_CT_SITE_ID, CS_INC_ALL_MERGE_INST_SITE_USE, and CS_INC_ALL_MERGE_CONT_POINTS. These procedures update the corresponding foreign-key columns on service request header, contact, and site-use records (customer_id, bill_to_contact_id, ship_to_contact_id, bill_to_party_id, ship_to_party_id, and site/contact-point references) so they point to the surviving party or contact.
• Audit trail updates: CS_AUDIT_MERGE_PARTY, CS_AUDIT_MERGE_OLD_BILL_CONT, CS_AUDIT_MERGE_SHIP_TO_CONT, CS_AUDIT_MERGE_OLD_SHIP_CONT, CS_AUDIT_MERGE_SITE_ID, and CS_AUDIT_MERGE_OLD_SITE_ID. These procedures maintain the Service audit table (CS_INCIDENTS_AUDIT_B), correcting historical references to the merged party or contact so the audit history remains internally consistent. The user search term "cs_audit_merge_party" corresponds directly to CS_AUDIT_MERGE_PARTY, which is the primary audit-handling entry point.
• Contact and contact-point updates: CS_CONTACTS_MERGE_PARTY and CS_CONTACTS_MERGE_CONT_POINTS, which re-point contact and contact-point records (CS_HZ_SR_CONTACT_POINTS) to the surviving party/contact.

Internally, CS_INC_ALL_MERGE_PARTY uses a cursor (C1) against CS_INCIDENTS_ALL_B filtered by p_from_fk_id across the five party/contact columns, then bulk-updates those columns while capturing audit information via CS_ServiceRequest_PVT.SR_AUDIT_REC_TYPE. Standard parameters include p_entity_name, p_from_id, p_from_fk_id, p_to_fk_id, p_parent_entity_name, p_batch_id, p_batch_party_id, x_to_id, and x_return_status.

Tables Accessed

• CS_INCIDENTS_ALL_B — the base service request table; the package updates customer, bill-to/ship-to contact, and bill-to/ship-to party columns.
• CS_INCIDENTS_AUDIT_B — the audit table for service requests; updated by the CS_AUDIT_* procedures to keep historical references valid.
• CS_HZ_SR_CONTACT_POINTS — service request contact points; updated by CS_CONTACTS_MERGE_CONT_POINTS.
• HZ_MERGE_BATCH — the TCA merge batch table that records the merge transaction and is used by the handlers to obtain merge context.
• PLITBLM — a PL/SQL table synonym used for bulk processing / rowid collection.

Usage Notes

The package is not intended for direct end-user invocation. It is called by the TCA party merge framework during execution of the Customer Merge (and equivalent) concurrent programs, where each registered "merge handler" package is invoked once per affected entity. Callers must be operating within the merge batch context so that p_batch_id, p_batch_party_id, and the from/to identifiers are populated.

Because it manipulates the service request base and audit tables, the package is also referenced by at least one other service package. Customizations that add new party-referencing columns to CS_INCIDENTS_ALL_B or CS_HZ_SR_CONTACT_POINTS generally require corresponding extension of the merge handlers, and these procedures should be re-validated after any upgrade between 12.1.1 and 12.2.2, since merge-handler registration and audit structures are sensitive to patch level. Direct calls from custom forms or concurrent programs are possible but require the same parameter contract used by the TCA merge driver.