Party merge

Oracle Trading Community Architecture
Party Merge

User Guide

Release 11i

April, 2002

Oracle Trading Community Architecture Party Merge User Guide, Release 11i

Copyright © 2002, Oracle Corporation. All rights reserved.

Contributors: Charlie Ahern, Ajay Singh

The Programs (which include both the software and documentation) contain proprietary information of
Oracle Corporation; they are provided under a license agreement containing restrictions on use and
disclosure and are also protected by copyright, patent and other intellectual and industrial property
laws. Reverse engineering, disassembly or decompilation of the Programs, except to the extent required
to obtain interoperability with other independently created software or as specified by law, is prohibited.

Program Documentation is licensed for use solely to support the deployment of the Programs and not for
any other purpose.

The information contained in this document is subject to change without notice. If you find any problems
in the documentation, please report them to us in writing. Oracle Corporation does not warrant that this
document is error-free. Except as may be expressly permitted in your license agreement for these
Programs, no part of these Programs may be reproduced or transmitted in any form or by any means,
electronic or mechanical, for any purpose, without the express written permission of Oracle Corporation.

If the Programs are delivered to the U.S. Government or anyone licensing or using the programs on
behalf of the U.S. Government, the following notice is applicable:

Restricted Rights Notice Programs delivered subject to the DOD FAR Supplement are commercial
computer software and use, duplication and disclosure of the Programs including documentation, shall
be subject to the licensing restrictions set forth in the applicable Oracle license agreement. Otherwise,
Programs delivered subject to the Federal Acquisition Regulations are restricted computer software and
use, duplication and disclosure of the Programs shall be subject to the restrictions in FAR 52.227-19,
Commercial Computer Software - Restricted Rights (June, 1987). Oracle Corporation, 500 Oracle
Parkway, Redwood City, CA 94065.

The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently
dangerous applications. It shall be licensee's responsibility to take all appropriate fail-safe, back up,
redundancy and other measures to ensure the safe use of such applications if the Programs are used for
such purposes, and Oracle disclaims liability for any damages caused by such use of the Programs.

Oracle is a registered trademark, Oracle8i, Oracle9i, Oracle MetaLink, Oracle Store, PL/SQL, Pro*C,
SQL*Net, and SQL*Plus are trademarks or registered trademarks of Oracle Corporation. Other names
may be trademarks of their respective owners.

Contents

Send Us Your Comments .................................................................................................................... v

Preface........................................................................................................................................................... vii
Documentation Accessibility ................................................................................................. ix
Online Documentation ............................................................................................................ x
Related Guides .......................................................................................................................... x
Guides Related to All Products ............................................................................................. xi
Guides Related to This Product ............................................................................................. xi
Other Implementation Documentation ............................................................................... xiii

1 Party Merge
Introduction ......................................................................................................................................... 1-2
Party Merge Example ......................................................................................................................... 1-4
Before the Merge ................................................................................................................... 1-4
After the Merge ..................................................................................................................... 1-4
Overview of the Party Merge Process............................................................................................. 1-6
Registering Applications for Party Merge ........................................................................ 1-6
Merging Parties or Party Sites ............................................................................................ 1-7
Merging Individuals, Organizations, or Relationships .................................................. 1-7
Merging Entities from Other Applications ....................................................................... 1-8
Setting Up Party Merge ..................................................................................................................... 1-9
Registering the Necessary Entities and Merge Procedures ............................................ 1-9
Party Merge Process ......................................................................................................................... 1-13
1. Creating the Merge Batch .............................................................................................. 1-13

iii

2. Processing the Merge Batch .......................................................................................... 1-19
3. Reviewing the Party Merge Requests Log File .......................................................... 1-20
4. Identifying Types of Errors ........................................................................................... 1-22

A Party Entities
Party Entities ........................................................................................................................................ A-2

B Impact on D&B Information
Impact on Dun & Bradstreet Data ................................................................................................... B-2
DUNS Numbers Are Different ........................................................................................... B-2
DUNS Numbers Are the Same ........................................................................................... B-2
No D&B Data Exists for the Merge-to Party ..................................................................... B-2
Merge-from Party is a Branch of Merge-to Party ............................................................. B-2
Merge-from Party is the Headquarters of Merge-to Party ............................................. B-2

C Duplicate Checking
Duplicate Checking ............................................................................................................................ C-2
Contact Points and Restrictions .......................................................................................... C-2
Customer Accounts and Related Information .................................................................. C-3
Roles in a Customer Account .............................................................................................. C-4
When the Party is an Organization .................................................................................... C-4
When the Party is a Person ................................................................................................. C-6
When the Party is Either an Organization or a Person ................................................... C-8

iv

Send Us Your Comments
Oracle Trading Community Architecture Party Merge User Guide, Release 11ii
Oracle Corporation welcomes your comments and suggestions on the quality and usefulness of this
document. Your input is an important part of the information used for revision.
■ Did you find any errors?
■ Is the information clearly presented?
■ Do you need more information? If so, where?
■ Are the examples correct? Do you need more examples?
■ What features did you like most?

If you find any errors or have any other suggestions for improvement, please indicate the document
title and part number, and the chapter, section, and page number (if available). You can send
comments to us in the following ways:
■ Electronic mail: appsdoc_us@oracle.com
■ FAX: (801) 659-7164 Attn: Oracle Applications Documentation Manager
■ Postal service:
Oracle Corporation
Oracle Applications Documentation Manager
500 Oracle Parkway
Redwood Shores, CA 94065
USA
If you would like a reply, please give your name, address, telephone number, and (optionally)
electronic mail address.

If you have problems with the software, please contact your local Oracle Support Services.

v

Preface

Welcome to Release 11i of the Oracle® Trading Community Architecture Party Merge
User Guide.
This guide assumes you have a working knowledge of the following:
■ The principles and customary practices of your business area.
■ Oracle Trading Community Architecture Party Merge
If you have never used Oracle Trading Community Architecture Party Merge,
Oracle suggests you attend one or more of the Oracle Applications training
classes available through Oracle University.
■ The Oracle Applications graphical user interface.
To learn more about the Oracle Applications graphical user interface, read the
Oracle Applications User’s Guide.
See Other Information Sources for more information about Oracle Applications
product information.

vii

How To Use This Guide
The Oracle Trading Community Architecture Data Quality Management User
Guide contains the information you need to understand and use Oracle Trading
Community Architecture Party Merge. This user guide includes:
■ Chapter 1 provides information on how to set up and use the party merge
features.
■ Appendix A describes the entities and procedures that must be processed to
merge the entities from any Oracle Application.
■ Appendix B describes how to resolve and merge Dun & Bradstreet information
for the merge-from and merge-to parties. This helps you retain as much of your
D&B data about the parties as possible.
■ Appendix C lists how child entities that belong to a party are merged or
transferred. These entities can include party sites, contacts, relationships, and
profile information.

viii

Documentation Accessibility
Our goal is to make Oracle products, services, and supporting documentation
accessible, with good usability, to the disabled community. To that end, our
documentation includes features that make information available to users of
assistive technology. This documentation is available in HTML format, and contains
markup to facilitate access by the disabled community. Standards will continue to
evolve over time, and Oracle Corporation is actively engaged with other
market-leading technology vendors to address technical obstacles so that our
documentation can be accessible to all of our customers. For additional information,
visit the Oracle Accessibility Program Web site at
http://www.oracle.com/accessibility/.

Accessibility of Code Examples in Documentation
JAWS, a Windows screen reader, may not always correctly read the code examples
in this document. The conventions for writing code require that closing braces
should appear on an otherwise empty line; however, JAWS may not always read a
line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation
This documentation may contain links to Web sites of other companies or
organizations that Oracle Corporation does not own or control. Oracle Corporation
neither evaluates nor makes any representations regarding the accessibility of these
Web sites.

ix

Other Information Sources
You can choose from many sources of information, including online documentation,
training, and support services, to increase your knowledge and understanding of
Oracle Trading Community Architecture Party Merge.
If this guide refers you to other Oracle Applications documentation, use only the
Release 11i versions of those guides.

Online Documentation
All Oracle Applications documentation is available online (HTML or PDF).
■ Online Help - The new features section in the HTML help describes new
features in 11i. This information is updated for each new release of Oracle
Trading Community Architecture Party Merge. The new features section also
includes information about any features that were not yet available when this
guide was printed. For example, if your administrator has installed software
from a mini-packs an upgrade, this document describes the new features.
Online help patches are available on MetaLink.
■ 11i Features Matrix - This document lists new features available by patch and
identifies any associated new documentation. The new features matrix
document is available on MetaLink.
■ Readme File - Refer to the readme file for patches that you have installed to
learn about new documentation or documentation patches that you can
download.

Related Guides
Oracle Trading Community Architecture Party Merge shares business and setup
information with other Oracle Applications products. Therefore, you may want to
refer to other guides when you set up and use Oracle Trading Community
Architecture Party Merge.
You can read the guides online by choosing Library from the expandable menu on
your HTML help window, by reading from the Oracle Applications Document
Library CD included in your media pack, or by using a Web browser with a URL
that your system administrator provides.
If you require printed guides, you can purchase them from the Oracle Store at
http://oraclestore.oracle.com.

x

Guides Related to All Products

Oracle Applications User’s Guide
This guide explains how to enter data, query, run reports, and navigate using the
graphical user interface (GUI) available with this release of Oracle Trading
Community Architecture Party Merge (and any other Oracle Applications
products). This guide also includes information on setting user profiles, as well as
running and reviewing reports and concurrent processes.

Guides Related to This Product

Oracle Trading Community Architecture Data Quality Management User
Guide
Use this user guide to learn how to maintian the quality of your party and customer
account information. This user guide describes how to set up and process
transformation functions and match rules to identify possible duplicate records.

Oracle Trading Community Architecture D&B for Oracle Applications
User Guide
Use this user guide to learn how to obtain fianacial and credit information about
parties from Dun & Bradstreet’s global database of company information.

Oracle interMedia User’s Guide and Reference
This user guide and reference provides information about Oracle interMedia. This
product enables Oracle9i to store, manage, and retrieve geographic location
information, images, audio, video, or other heterogeneous media data in an
integrated fashion with other enterprise information. Oracle Trading Community
Architecture Data Quality Management uses interMedia indexes to facilitate search
and matching.

Oracle Receivables User Guide
Use this user guide to learn how to implement flexible address formats for different
countries. You can use flexible address formats in the suppliers, customers, banks,
invoices, and payments windows in both Oracle Payables and Oracle Receivables.
This user guide also explains how to set up your system, create transactions, and
run reports in Oracle Receivables.

xi

Oracle Receivables Tax Manual
This manual provides information about calculating tax within Oracle Receivables,
Oracle Order Management, Oracle Sales and Marketing, and Oracle Web
Customers. It includes information about implementation procedures, setup forms
and windows, the Oracle Receivables tax calculation process, tax reports and
listings, and tax-specific open interfaces.

xii

Installation and System Administration
Oracle Applications Concepts
This guide provides an introduction to the concepts, features, technology stack,
architecture, and terminology for Oracle Applications Release 11i. It provides a
useful first book to read before an installation of Oracle Applications. This guide
also introduces the concepts behind Applications-wide features such as Business
Intelligence (BIS), languages and character sets, and Self-Service Web Applications.

Installing Oracle Applications
This guide provides instructions for managing the installation of Oracle
Applications products. In Release 11i, much of the installation process is handled
using Oracle Rapid Install, which minimizes the time to install Oracle Applications,
the Oracle8 technology stack, and the Oracle8i Server technology stack by
automating many of the required steps. This guide contains instructions for using
Oracle Rapid Install and lists the tasks you need to perform to finish your
installation. You should use this guide in conjunction with individual product user
guides and implementation guides.

Oracle Applications Implementation Wizard User Guide
If you are implementing more than one Oracle product, you can use the Oracle
Applications Implementation Wizard to coordinate your setup activities. This guide
describes how to use the wizard.

Upgrading Oracle Applications
Refer to this guide if you are upgrading your Oracle Applications Release 10.7 or
Release 11.0 products to Release 11i. This guide describes the upgrade process and
lists database and product-specific upgrade tasks. You must be either at Release 10.7
(NCA, SmartClient, or character mode) or Release 11.0, to upgrade to Release 11i.
You cannot upgrade to Release 11i directly from releases prior to 10.7.

Maintaining Oracle Applications
Use this guide to help you run the various AD utilities, such as AutoUpgrade,
AutoPatch, AD Administration, AD Controller, AD Relink, License Manager, and
others. It contains how-to steps, screenshots, and other information that you need to
run the AD utilities. This guide also provides information on maintaining the
Oracle applications file system and database.

xiii

Oracle Applications System Administrator’s Guide
This guide provides planning and reference information for the Oracle Applications
System Administrator. It contains information on how to define security, customize
menus and online help, and manage concurrent processing.

Oracle Alert User’s Guide
This guide explains how to define periodic and event alerts to monitor the status of
your Oracle Applications data.

Oracle Applications Developer’s Guide
This guide contains the coding standards followed by the Oracle Applications
development staff. It describes the Oracle Application Object Library components
needed to implement the Oracle Applications user interface described in the Oracle
Applications User Interface Standards for Forms-Based Products. It also provides
information to help you build your custom Oracle Forms Developer 6i forms so that
they integrate with Oracle Applications.

Oracle Applications User Interface Standards for Forms-Based Products
This guide contains the user interface (UI) standards followed by the Oracle
Applications development staff. It describes the UI for the Oracle Applications
products and how to apply this UI to the design of an application built by using
Oracle Forms.

Other Implementation Documentation

Oracle Applications Product Update Notes
Use this guide as a reference for upgrading an installation of Oracle Applications. It
provides a history of the changes to individual Oracle Applications products
between Release 11.0 and Release 11i. It includes new features, enhancements, and
changes made to database objects, profile options, and seed data for this interval.

Oracle Workflow Guide
This guide explains how to define new workflow business processes as well as
customize existing Oracle Applications-embedded workflow processes. You also
use this guide to complete the setup steps necessary for any Oracle Applications
product that includes workflow-enabled processes.

xiv

Oracle Applications Flexfields Guide
This guide provides flexfields planning, setup and reference information for the
Oracle Trading Community Architecture Party Merge implementation team, as well
as for users responsible for the ongoing maintenance of Oracle Applications
product data. This guide also provides information on creating custom reports on
flexfields data.

Oracle eTechnical Reference Manuals
Each eTechnical Reference Manual (eTRM) contains database diagrams and a
detailed description of database tables, forms, reports, and programs for a specific
Oracle Applications product. This information helps you convert data from your
existing applications, integrate Oracle Applications data with non-Oracle
applications, and write custom reports for Oracle Applications products. Oracle
eTRM is available on Metalink

Oracle Applications Message Manual
This manual describes all Oracle Applications messages. This manual is available in
HTML format on the documentation CD-ROM for Release 11i.

xv

Training and Support
Training
Oracle offers a complete set of training courses to help you and your staff master
Oracle Trading Community Architecture Party Merge and reach full productivity
quickly. These courses are organized into functional learning paths, so you take
only those courses appropriate to your job or area of responsibility.
You have a choice of educational environments. You can attend courses offered by
Oracle University at any one of our many education centers, you can arrange for
our trainers to teach at your facility, or you can use Oracle Learning Network
(OLN), Oracle University’s online education utility. In addition, Oracle training
professionals can tailor standard courses or develop custom courses to meet your
needs. For example, you may want to use your organization structure, terminology,
and data as examples in a customized training session delivered at your own
facility.

Support
From on-site support to central support, our team of experienced professionals
provides the help and information you need to keep Oracle Trading Community
Architecture Party Merge working for you. This team includes your technical
representative, account manager, and Oracle’s large staff of consultants and support
specialists with expertise in your business area, managing an Oracle8i server, and
your hardware and software environment.

xvi

Do Not Use Database Tools to Modify Oracle Applications Data
Oracle STRONGLY RECOMMENDS that you never use SQL*Plus, Oracle Data
Browser, database triggers, or any other tool to modify Oracle Applications data
unless otherwise instructed.
Oracle provides powerful tools you can use to create, store, change, retrieve, and
maintain information in an Oracle database. But if you use Oracle tools such as
SQL*Plus to modify Oracle Applications data, you risk destroying the integrity of
your data and you lose the ability to audit changes to your data.
Because Oracle Applications tables are interrelated, any change you make using
Oracle Applications can update many tables at once. But when you modify Oracle
Applications data using anything other than Oracle Applications, you may change a
row in one table without making corresponding changes in related tables. If your
tables get out of synchronization with each other, you risk retrieving erroneous
information and you risk unpredictable results throughout Oracle Applications.
When you use Oracle Applications to modify your data, Oracle Applications
automatically checks that your changes are valid. Oracle Applications also keeps
track of who changes information. If you enter information into database tables
using database tools, you may store invalid information. You also lose the ability to
track who has changed your information because SQL*Plus and other database
tools do not keep a record of changes.

About Oracle
Oracle Corporation develops and markets an integrated line of software products
for database management, applications development, decision support, and office
automation, as well as Oracle Applications, an integrated suite of more than 160
software modules for financial management, supply chain management,
manufacturing, project systems, human resources and customer relationship
management.
Oracle products are available for mainframes, minicomputers, personal computers,
network computers and personal digital assistants, allowing organizations to
integrate different computers, different operating systems, different networks, and
even different database management systems, into a single, unified computing and
information resource.
Oracle is the world’s leading supplier of software for information management, and
the world’s second largest software company. Oracle offers its database, tools, and
applications products, along with related consulting, education, and support
services, in over 145 countries around the world.

xvii

Your Feedback
Thank you for using Oracle Trading Community Architecture Party Merge and this
user guide.
Oracle values your comments and feedback. In this guide is a reader’s comment
form that you can use to explain what you like or dislike about Oracle Trading
Community Architecture Party Merge or this user guide. Mail your comments to
the following address or call us directly at (650) 506-7000.
Oracle Applications Documentation Manager
Oracle Corporation
500 Oracle Parkway
Redwood Shores, CA 94065
U.S.A.
Or, send electronic mail to appsdoc_us@oracle.com.

xviii

1
Party Merge

This chapter describes how to set up and use the party merge features.

Party Merge 1-1

Introduction

Introduction

The party merge feature of the Trading Community Architecture provides the
capability to merge parties and their related entities.
The Oracle Trading Community Architecture (TCA) customer model separates the
attributes of a party that has entered into a trading partner relationship from the
attributes of that relationship. For example, a customer account relationship
contains the attributes of that transactional relationship between the party and you.
Different types of parties include Organization, Person, and Relationship. With this
customer model you can represent each party in your trading community with a
single view across multiple Oracle Applications. Although Customer Relationship
Management (CRM) and Enterprise Resource Planning (ERP) applications in the
Oracle E-Business Suite share the same model, each application uses the model
differently depending on the context and need for particular party information.
The party information that you enter in Oracle Applications with on-line forms and
batch data entry includes the party’s name, address, contact information, and so on.
This information is stored in the TCA party registry and can be shared among the
customer accounts of a party.
Because the TCA party registry shares information across the Oracle Applications
E-Business suite, you must maintain the quality of the data in the party registry.
Duplicate data in a party registry can reduce the efficiency and accuracy of your
party processing and reports. You can use the Party Merge feature to eliminate
duplicate data in the party registry.
The Party Merge feature provides you the functionality to:
■ Consolidate duplicated parties or party sites.
For example, you can merge Vision Corp. into Vision Corporation
■ Integrate an acquired party into the acquiring party.
For example, you can merge Blue Company into White Corporation
■ Merge duplicate party sites for a party.
To maintain an efficient and accurate party registry, use the Party Merge feature
with other data quality management tools. You can use fuzzy search methods, such
as data transformations and match rules, to identify parties as candidates to be
merged. In addition, Oracle Applications support a Customer Account Merge
functionality that you can use to merge transactions from a source customer account

1-2 Oracle Trading Community Architecture Party Merge User Guide

Introduction

to a target customer account. After the merge-from account is merged into the
merge-to account you can either inactivate or delete the source customer account.

Party Merge 1-3

Party Merge Example

Party Merge Example

This example provides an example of a party merge, showing both the before and
after conditions.
ABC Company has implemented the Oracle Applications E-Business Suite. While
checking the quality of its data, ABC Company determines that duplicate records
exist for a party, Vision Corporation. Data for this party were entered into the
database under the names Vision Corp. and Vision Inc. Using the Party Merge
utility, ABC Company plans to merge the two Vision parties.

Before the Merge
From party name: Vision Corp.
From party sites:
■ 500 Vision Parkway, with three uses: bill-to, ship-to, and marketing.
■ 600 Vision Parkway, with two uses: bill-to and ship-to.
To party name: Vision Inc.
To party sites:
■ 100 Vision Parkway, with one party site use: bill-to.
■ 600 Vision Parkway, with one party site use: ship-to.
The 600 Vision Parkway party sites exists for both Vision Corp. and Vision Inc. and
is considered to be duplicated.

Merging Party Vision Corp. with Vision Inc.
The party site 500 Vision Pkwy is transferred to Vision Inc. The details of 500 Vision
Pkwy, for example the bill-to, ship-to, and marketing party site uses stay with the
party site.
The party site 600 Vision Parkway is merged with 600 Vision Pkwy on Vision Inc.
The bill-to site use is transferred because it does not exist for Vision Inc. The ship-to
site use is merged because it already exists for Vision Inc.

After the Merge
■ Vision Corp. is set to a status of Merged.
■ The party site 600 Vision Pkwy is set to a status of Merged.


Party Merge Example

■ The ship-to party site use is set to a status of Merged.
■ Vision Inc. has three party sites:
– 100 Vision Parkway with a bill-to site use
– 500 Vision Parkway with a bill-to, ship-to, and marketing site use
– 600 Vision Parkway, with a bill-to and ship-to site use

Party Merge 1-5

Overview of the Party Merge Process


With the Party Merge feature you can consolidate duplicate parties, integrate an
acquired party into another party, or consolidate duplicate party sites of a party in
the TCA party registry. The related child entities that get merged or transferred
include party relationships, contact information, party profiles, customer accounts,
and information obtained from third-party sources.
The merging parties are referred to as the merge-from party and the merge-to party,
or the source and the target respectively. After the merge-from party is merged into
the merge-to party you can delete the merge-from, or source, party. By default the
merge-from party is set to a Merged status.

Registering Applications for Party Merge
You must register party entities, for example accounts, organization contacts, and
party sites in the Party Merge dictionary. The registration specifies the names of the
procedures required to merge the entities that interact with the party entities. The
Party Merge program uses the information in the Party Merge dictionary to
recognize which entities to merge.
Some Oracle Applications, along with their party entities, are automatically
registered at installation. If you have installed any of these applications, when you
use the Party Merge feature, the entities associated with the parties in these
applications are merged as well. The applications include:
Enterprise Resource Planning (ERP) applications:
■ Activity Based Management
■ Accounts Receivables
■ Spares Management
■ XML Gateway
■ Application Object Library
■ Project Contracts
Customer Relationship Management (CRM) applications:
■ Advanced Service Online
■ Hosting Manager
■ Marketing



■ Sales
■ CRM Gateway for Mobile Services
■ Order Capture
■ Service
■ Customer Care
■ Install Base
■ Support
■ iStore
■ Collections
■ CRM Foundation
■ Contracts Core
■ Contracts for Rights
■ Contracts Service Module
■ Partner Relationship Management

Merging Parties or Party Sites
You can merge parties or party sites that belong to a party. You cannot merge party
sites between parties. However, until you merge the parties that they belong to.
Before the Party Merge process begins, you can choose to delete the merge-from
party when the process ends. If you merge party sites for the same party, you
cannot choose to delete the merge-from party because the merge-from and merge-to
parties are the same party.
Deleting a party changes its status to Deleted. You cannot retrieve a deleted party in
any search or transaction window unless the application is specifically designed to
include deleted parties in any query results.

Merging Individuals, Organizations, or Relationships
You can merge Person, Organization, or Relationship party types. You can,
however, only merge parties with the same party type. This implies that an
organization can only be merged with another organization, a person with a person,
and so on.

Party Merge 1-7


Merging Entities from Other Applications
You must process and merge or appropriately transfer other Oracle Applications
information of the duplicate party, such as transactions and attributes, into the
merge-to party. Before using the Party Merge feature, you must, register all
applications and entities that interact with the Trading Community Architecture to
ensure that all transaction and attributes are merged when the party is merged.


Setting Up Party Merge


You can use the Merge Dictionary window to set up and control the merge process.
The Party Merge dictionary stores the entities and procedures that must be
processed to merge party entities for any Oracle Application. During the merge
process, each procedure sequentially executes for the entities in the Merge
Dictionary window. You register the entities and procedures for a specific Oracle
Application in the Party Merge dictionary.
You can set up the Party Merge process for all Oracle Applications that you use to
interact with parties.
For example, if your company enters into a service contract with one of the parties
in your registry, you would use Oracle Receivables to send invoices and statements
to that party and Oracle Service to administer that service contract. If that party is
acquired by another party, is identified as a duplicate of another party, or has sites
that must be consolidated, you must merge those parties or party sites. This party
merge affects customer accounts and attributes of the parties in Oracle Receivables,
Oracle Service, and other Oracle Applications.

Registering the Necessary Entities and Merge Procedures
Each of the Oracle Applications maintains its own tables to store the information
required to complete its business functions. During a party merge process, all
registered applications must be able to access the data for the appropriate entity that
is related to the party registry. If a party merge procedure attempts to access a
deleted party, the transaction, attributes, and other information for the party cannot
be merged.
The Merge Dictionary window lets you maintain how Oracle Applications are
affected by the merge process. In the Merge Dictionary window you, or an
application developer, can register the foreign keys and procedures to the party
registry. The merge program would recognize these foreign keys and procedures
without the need to recompile or regenerate the application code.
For the list of party entities, see Appendix A - Party Entities on page 27.
In the Merge Dictionary window you can customize the merge process. You would
customize the merge process if you want to:
■ Merge your own custom entities as part of the merge process that affects the
standard TCA entities, so that custom entities can be merged using standard
merge rules.

Party Merge 1-9


■ Use a different implementation of the merge process for the standard TCA
entities, so that standard entities can be merged using custom rules.
You can override the procedures that Oracle Development defined for merging TCA
entities with the custom procedures.
You, or your Oracle applications developer, must develop the code to customize the
Merge procedures used by your custom applications and entities.
Your custom merge procedure should:
■ Perform any required validations before you run the merge process.
■ Meet the processing requirements of your range of business activities.

Prerequisites
Before you add any Oracle Application to the Party Merge dictionary you must:
■ Identify any entities that have foreign keys in the party registry.
■ Create merge procedures by identifying the foreign keys for those entities.

To set up entities for Party Merge in the Party Merge dictionary:
1. Navigate to the Merge Dictionary window.



2. Enter the name of the Oracle Application affected by the merge process in the
Application field.
3. In the Entity field, enter the name of the table that has a foreign key to the HZ_
PARTIES table or a related table such as HZ_PARTY_SITES or HZ_CONTACT_
POINTS.
4. In the Parent Entity field, enter the name of the table that the foreign key of the
table in the Entity field refers to.
5. The Procedure Type field defaults to PL/SQL.
6. In the Description Column(s) field, enter the name of the columns used to
generate a description for the record, for example, PARTY_NAME for the HZ_
PARTIES table. You can alternatively enter a complex concatenation or decode
expression. The information in the Description Column field is used in reports
and logs.
7. In the Additional Query Clause field, enter a SQL clause that is used to specify
additional filtering conditions for joining the table to the related parent entity.
8. In the Primary Key field enter the name of the primary key column for the
entity.
9. In the Foreign Key field, enter the name of the foreign key column which links
the entity to its parent entity.
10. In the Procedure Name field, enter the name of the merge procedure, which
must conform to the standard merge procedure signature.
11. In the Child Entities region, for each child entity, enter the foreign key that
relates the child to the parent entity in the Foreign Key field.
If the relationship between the parent and child entities involve more than one
foreign key or is complex, you can enter an additional join condition in the
Merge Procedure Name Field.
For example, the HZ_CONTACT_POINTS table can be associated with either a
party or party sites based on the value of the owner_table_name. To associate HZ_
CONTACT_POINTS with:
■ The HZ_PARTIES table
– Enter the join condition as hz_contact_points.owner_table_name = HZ_
PARTIES.
– Define the foreign key as owner_table_id.
■ The HZ_PARTY_SITE table

Party Merge 1-11


– Enter the join condition as hz_contact_points.owner_table_name = HZ_
PARTY_SITE.
– Define the foreign key as owner_table_id.


Party Merge Process

Party Merge Process

The Party Merge process involves four procedures:
1. Creating the merge batch.
2. Processing the merge batch.
3. Reviewing the Party Merge Requests log file.
4. Identifying types of errors.

1. Creating the Merge Batch
Merging Parties and Party Sites
You can use the Merge Batch window to set up a merge batch for the parties or
party sites that you are merging. You can only merge parties of the same party type.
You can merge or transfer party sites, organization contacts, party relationships, and
profiles related to a party. All other entities related to a party are either always
merged or always transferred based on the merge procedures defined for that
entity.
When you select a party as the merge-to party in a batch, the records for that party
are locked and cannot be selected as a merge candidate for this or any other batch
until after this batch is submitted and processed. When you select a party as the
merge-from party in a batch, the records for that party are locked until after the
merge process completes, when the party is deleted or deactivated.
In the Merge Batch window, you can specify if you want to delete the merge-from
party after the merge process completes. You can, however, set up any merge
procedure, registered with the Party Merge dictionary to prevent the deletion of
records, if your company’s business rules require that parties cannot be deleted. To
prevent deletion, a merge procedure must call the HZ_PARTY_MERGE. veto_delete
procedure. At the end of the merge process, if none of the merge procedures has
vetoed the deletion of the merge-from parties, then those party records are deleted.

Prerequisites
Before you create a merge batch, you must:
■ Define any custom entities and merge procedures in the Merge Dictionary
window.
■ Decide if you want to delete all of the records of the merge-from party.

Party Merge 1-13

Party Merge Process

To create a merge batch for parties:
1. Navigate to the Merge Batch window.
2. Enter a name for the batch in the Batch Name field. The batch name should be
unique and related to the parties that you are merging.
3. Enter a reason for the merge in the Merge Reason field. You can either use a
predefined reason, such as Merger or De-duplication Merge, or enter your own
reason.
4. Check the Commit at Batch Level check box if you want to save the batch after
the complete batch has been merged. Do not check the check box if you want to
save records after each pair of parties has merged.
5. Check the Delete Merged Records check box to delete the merge-from party
records after the batch merge completes. Do not check this box if you do not
want to delete the merged records. These records are instead assigned a Merge
status.
6. In the Party Details region, enter one or more parties that you want to merge.
7. Enter the party type for each party that you are merging in the Party Type field:.
■ Organization
■ Person
■ Relationship


Party Merge Process

8. In the From Party fields, enter the party name or party number of the
merge-from party.
9. In the To Party fields, enter the party name or party number of the merge-to
party.
10. Enter the reason for merging these two parties in the Merge Reason field.

11. Save your work before moving on to the tabbed regions.

To merge party sites:
1. Navigate to the Party Sites tabbed region.
2. Enter the from site’s address in the Address field and the appropriate merge
operation in the Operation field, Merge or Transfer Party Merge operation.
3. If you enter the Merge operation, you must enter an address for the merge-to
party site.
If you are merging US party sites, you can only merge addresses that reflect the
same Sales Tax Structure. For example, of you use the State.County.City Sales
Tax Location Flexfield Structure, you can only merge party sites that have the
same state, county, and city.
Oracle Receivables calculates sales taxes in the United States based on the
address components of the Sales Tax Structure that you define in the System
Options window. Because sales tax rates can change, modifying these
components can invalidate the tax calculated for transactions previously
assigned to an address. To ensure that you do not violate US sales tax audit
requirements, you must merge party sites with addresses of same Sales Tax
Structure.

See also: Setup Steps for US Sales Tax, Oracle Receivables Tax
Manual

Merging Party Relationships
Party relationships and organization contacts are a binary relationship between two
parties, such as a partnership. A party relationship can be a party itself, so that
certain party relationships could themselves enter into relationships.
For example, if Joe is your contact at Vision Corporation, you can record this as a
relationship between the person Joe and the organization Vision Corporation. That
relationship, Joe as a contact for Vision Corporation, is itself a party that can enter
into its own relationships.
This table shows details of this sample relationship:

Party Merge 1-15

Party Merge Process

Party ID Subject ID Object ID Type of Relationship
789 (Joe, contact for Vision 456 (Joe) 123 (Vision Contact Of
Corp.) Corp.)

After reviewing your database, you might determine that Vision Corporation and
Vision Inc., another party in your database, are duplicates that should be merged.
After the merge process, the contact information would be changed as shown in this
table:
Type of
Party ID Subject ID Object ID Relationship
789 (Joe, contact for Vision Inc.) 456 (Joe) 123 (Vision Corp.) Contact Of

To merge party relationships:
1. Navigate to the Party Relationships tabbed region.
2. For each relationship to be transferred or merged for a party, enter that
relationship’s subject, object, and type in the From Relationships region.
For example, if a type of relationship exists called Subsidiary of and Vision
Manufacturing is a subsidiary of Vision Corporation, then Vision
Manufacturing would be the subsidiary of Vision Corporation. Vision


Party Merge Process

Manufacturing would be the subject of the relationship and Vision Corporation
would be the object of the relationship.
Party relationships do not require a hierarchical relationship like a parent-child
relationship. For example, party relationships defined as Partner of, Colleague of,
Competitor of, and so on do not imply a hierarchical relationship, but you have
to identify a subject and object of the relationship before you can merge
relationships.
In the Operation field, enter either Merge or Transfer.
You can merge only if the same party relationship exists for the merge-from and
merge-to parties.
3. Enter a relationship for the merge-to party in the To Relationships region.
If the same party relationship exists for the merge-from and merge-to parties,
the relationships are automatically selected to be merged and cannot be
transferred.
If parties of the type Relationship represent both relationships, the relationship
parties are automatically added to the batch.
If you manually select two party relationships to be merged and relationship
parties represent both relationships, you must first manually merge the
relationship parties in another batch before running this batch.

Merging Organization Contacts and Viewing Profile Information

To merge organization contacts:
1. Navigate to the From Org Contact region.
2. For each organization contact for the merge-from party, enter that contact’s
name and title. You can enter the type, department, and party site to identify a
group of organization contacts.
3. In the Operations field, enter either Merge or Transfer.
You can merge only if a similar organization contact exists for the merge-to
party.
4. If you enter Merge as the operation, enter an organization contact for the
merge-to party that the party in the From Org Contact region is to be merged
into.
If the same organization contact exists for the merge-from and merge-to parties,
that contact is automatically selected to be merged. You must add the

Party Merge 1-17

Party Merge Process

relationship parties for these contacts to the batch before entering the
organization contacts for merging.

To view person profiles for the merging parties of Person type:
1. Navigate to the Person Profiles tabbed region.
2. For each person in the merge-from and merge-to parties, you can view the
taxpayer ID, tax registration number, and date of birth.
If a person is selected, the from-person profile is merged with the to-person
profile.

To view organization profiles for merging parties of Organization type:
1. Navigate to the Org Profiles tabbed region.
2. For each organization in the merge-from and merge-to parties, you can view the
taxpayer ID, tax registration number, and DUNS number.
If an organization is selected, the from-organization profile is merged with the
to-organization profile.

Merging the Party Sites of a Party
You can use the Merge Batch window to merge duplicate party sites for a party.
After the merge process all entities associated with the merge-from party site,
including customer account sites, refer to the merge-to party site.
To submit a merge for two sites of the same party, you cannot check the Delete
Merged Records check box. Checking that check box implies deleting both the
merge-from and merge-to parties.

To merge party sites for the same party:
1. Navigate to the Merge Batch window.
2. Enter a name for the batch in the Batch Name field. The batch name should be
unique and related to the party for which you are merging the party sites.
3. Enter a reason for the merge in the Merge Reason field. You can either use a
predefined reason, such as Merger or De-duplication Merge, or enter your own
reason.
4. Check the Commit at Batch Level check box if you want to save the batch after
the complete batch has been merged. Uncheck the check box if you want to save
records after each pair of parties has merged. Make sure that the Delete Merged
Records check box is not checked.


Party Merge Process

5. In the Party Details region, enter one or more from-parties for which you want
to merge the party sites.
6. Enter the party type for each party that you are merging in the Party Type field:
■ Organization
■ Person
■ Relationship
7. Check the Site Merge check box. The To Party fields are automatically
populated with information from the From Party fields.
Alternatively, you can just enter the party name or party number of your
from-party in the To Party fields.
8. Enter the reason for merging these party sites in the Merge Reason field.
9. Save your work.
10. Enter all party sites to be merged in the Party Sites tabbed region. Follow the
steps for merging party sites on page 15.
The other tabbed regions are disabled.

2. Processing the Merge Batch
After you create the merge batch to merge either different parties or party sites of
the same party, you have three options to process your merge batch:
■ Preview your merge batch and the outcome of the merge process before
submitting the Party Merge process.
■ Submit the Party Merge process immediately after entering your merge details.
■ Save your work and submit the Party Merge process at a later time.
After a merge batch is successfully processed, you cannot reverse the results.

To preview the merge batch results:
1. Create the merge batch in the Merge Batch window. For more information, see
Creating the Merge Batch on page 13.
2. Press the Preview Batch button.
3. The Party Merge process runs and merges the appropriate parties and other
entities, but does not commit the merged records to the database. The request
number is displayed in the Last Request ID field.

Party Merge 1-19

Party Merge Process

4. Navigate to the Find Requests window, select the Specific Requests option,
enter the request number in the Request ID field, and press the Find button.
5. In the Requests window, preview the expected effect of the merge process on
the merging parties and their entities. For more information, see Reviewing the
Party Merge Requests Log File on page 20.
If you query for the merge batch at this point in the Merge Batch window, the
Merge Done check boxes are not checked. Even if you checked the Delete Merged
Records check box, no records are deleted because the merge process is submitted in
the preview mode.

To submit the Party Merge process:
1. Create the merge batch in the Merge Batch window. For more information, see
Creating the Merge Batch on page 13.
2. Press the Run Batch button.
The Party Merge process runs and merges the appropriate parties and other
entities. If you checked the Commit at Batch Level check box, the entire batch
must be successfully processed before the merged records are committed to the
database. If the Commit at Batch Level check box is not checked, each merged
record is committed as it is processed.
The request number is displayed in the Last Request ID field.
3. Navigate to the Find Requests window, select the Specific Requests option,
enter the request number in the Request ID field, and press the Find button.
4. In the Requests window, view the status and results of the merge process. For
more information, see the Reviewing the Party Merge Requests Log File section on
page 20.
If you query for the merge batch at this point in the Merge Batch window, the
Merge Done check box is checked. If you checked the Delete Merged Records check
box, the merge-from parties are set to the Deleted status.

3. Reviewing the Party Merge Requests Log File
You can use the Party Merge Requests log file to review the parties and related
entities affected by the merge process. Oracle Receivables automatically generates
this output file after you run the Party Merge process. The report body displays
Merged or Deleted for each merge-from party to indicate the status of the merge-from
party or party site. The report displays an error message if the Party Merge process
fails.


Party Merge Process

This table shows the report headings.

In this heading... Party Merge prints...
Request ID The request ID for your concurrent process.
Log Message The sequence of processes that run to execute the merge
batch. This includes:
■ Start time of the merge
■ Batch ID
■ Batch name
■ Rule set name
■ Merge process
■ Entities merged or transferred
Execution status The execution status (see below).

The Merge Process log message displays the details of the entities that have been
merged or transferred. The entities that are merged or transferred are based on the
merge procedures that were registered with the Party Merge dictionary.
The entities include, but are not restricted to, parties, party sites, relationships,
contacts, profiles, contact points, customer accounts, customer account sites, and so
on. For a complete list of preregistered TCA entities, see Appendix A - Party Entities
on page 27. In addition to these standard TCA entities, other Oracle Applications
and legacy system entities can be registered with the Party Merge dictionary. These
entities are also merged during the party merge process. You can also view the
details about these entities in the Party Merge Request log file.

Execution Status
The possible execution status combinations are:

Merge batch successfully executed / Batch rollback complete
This status occurs after you click the Preview Batch button and the merge batch
successfully runs without committing any merged records.
This status indicates that the merge procedures registered with the Party Merge
dictionary ran, the merge process completed, but the merged records were not
committed to the database.

Party Merge 1-21

Party Merge Process

Merge batch successfully executed / Batch commit complete
This status occurs after you click the Run Batch button and the merge batch
successfully runs.
dictionary ran, the merge process completed, and the merged records were
committed to the database.

Merge batch failed / Batch rollback complete
dictionary did not run successfully, and no merged records were committed to the
database. Along with this status information, the log file provides details of the
error and identifies the merge procedure that the error occurred in.

4. Identifying Types of Errors
The Party Merge process encounters two types of errors – data errors and procedure
errors.

Data Errors
The Party Merge process might fail at the batch or party level if any record contains
corrupt data. If the Commit at Batch Level check box is checked and the Party
Merge process encounters corrupt data, the entire batch fails, and none of the
parties are merged. If the Commit at Batch Level check box is unchecked and the
Party Merge process encounters corrupt data, only the party or parties that have
corrupted data are not merged. All other parties successfully merge. Users should
be able to correct most data errors.

Procedure Errors
The Party Merge process can fail if any procedures were not correctly coded,
registered, and tested. The Party Merge Requests log file identifies the procedure
that caused the Party Merge process to fail. Procedure errors must be corrected by
an application developer.

Merge Order of Parties and Customer Accounts
If you find duplicate parties, you should determine if duplicate customer accounts
exist between the merge-from and merge-to parties. If you find duplicate customer
accounts, duplicate parties might exist for these customer accounts. You should
verify that duplicate parties exist and merge those duplicate parties.
■ When two customer accounts are merged and the corresponding parties are
verified as duplicates, the parties can be merged.


Party Merge Process

■ When two parties are merged and the corresponding customer accounts are
verified as duplicates, the customer accounts can be merged.

Party Merge Followed by Customer Merge Example
checking the quality of its customer data, ABC Company determines that duplicate
records exist for a party, Vision Corporation. Data for this party were entered into
the database under the names of Vision Corp. and Vision Inc. Using the Party
Merge utility, ABC Company plans to merge the two Vision parties.

Before Party Merge
Customer account number: 765432
From customer account party sites:
Customer site ID: 1CUSTIDVISIONCORP
Customer account number: 234567
To party sites:
■ 100 Vision Parkway, with one use: bill-to.
Customer site ID: 1CUSTIDVISIONINC
■ 600 Vision Parkway, with one use: ship-to.
The 600 Vision Parkway party sites exist for both Vision Corp. and Vision Inc. and
are deemed to be duplicates.

Merging Party Vision Corp. with Vision Inc.
The 500 Vision Pkwy party site is transferred to Vision Inc. The details for 500
Vision Pkwy, such as the bill-to, ship-to, and marketing party site uses stay with the
party site.

Party Merge 1-23

Party Merge Process

The 600 Vision Pkwy party site is merged with 600 Vision Pkwy for Vision Inc. The
bill-to site use is transferred because it does not exist for Vision Inc. The ship-to is
merged because it already exists for Vision Inc.

After Party Merge and Before Customer Account Merge
■ Vision Corp. is set to a status of Merged.
■ The 600 Vision Pkwy party site is set to a status of Merged.
■ The ship-to party site use is set to a status of Merged.
■ Vision Inc. has two customer accounts:
– Customer account number: 1CUSTVISIONCORP
– Customer account number: 1CUSTVISIONINC
■ Vision Inc. has three party sites:
– 100 Oracle Parkway with a bill-to site use
– 500 Oracle Parkway with a bill-to, ship-to, and marketing site use
– 600 Oracle Parkway with a bill-to and ship-to site use.

Merging the Customer Accounts
The customer account with the customer number of 1CUSTVISIONCORP is merged
with the customer account with the customer number of 1CUSTVISIONINC.
The customer account site with the customer site ID of 2CUSTIDVISIONCORP is
merged with the customer account site with the customer site ID of
2CUSTIDVISIONINC.

After Customer Account Merge
The customer account with the customer number of 1CUSTVISIONCORP is set to a
status of Merged.
set to a status of Merged.
The bill-to and ship-to site uses on customer account site with the customer site ID
of 2CUSTIDVISIONCORP are set to a status of Merged.


Party Merge Process

Vision Inc. has one customer account.
Customer number: 1CUSTVISIONINC
Vision Inc. has three party sites.
■ 100 Oracle Parkway with a bill-to site use
■ 500 Oracle Parkway with a bill-to, ship-to, and marketing site use
■ 600 Oracle Parkway with a bill-to and ship-to site use

Customer Merge Followed by Party Merge Example
checking the quality of its data, ABC Company determines that duplicate records
exist for a party, Vision Corporation. Data for this part were entered into the
database under the names Vision Corp. and Vision Inc. Using the Party Merge
utility, ABC Company plans to merge the two Vision parties.

Before Customer Account Merge
Customer account number: 1CUSTVISIONCORP
From customer account and party sites:
■ 600 Vision Parkway, with two party site uses: bill-to and ship-to.
Customer account number: 1CUSTVISIONINC
To party sites:
■ 100 Vision Parkway, with one party site use: bill-to.
■ 600 Vision Parkway, with one party site use: ship-to.

Party Merge 1-25

Party Merge Process

The 600 Vision Parkway party sites exists for both Vision Corp. and Vision Inc. and
are deemed to be duplicates.

Merging the Two Customer Accounts
The customer account with the customer number of 1CUSTVISIONCORP is merged
with the customer account with the customer number of 1CUSTVISIONINC.
merged with the customer account site with the customer site ID of
2CUSTIDVISIONINC.

After Customer Account Merge and Before Party Merge
The customer account with the customer number of 1CUSTVISIONCORP has the
status of Merged.
The customer account site with the customer site ID of 2CUSTIDVISIONCORP has
the status of Merged.
The bill-to and ship-to site uses for the customer account site with the customer site
ID of 2CUSTIDVISIONCORP have the status of Merged.
Vision Corp has the following party sites:
Vision Corp does not have any customer accounts or customer account sites
belonging to it.
Vision Inc. has two party sites:
■ 100 Vision Parkway, with one use: bill-to.
■ 600 Vision Parkway, with one use: ship-to.


Party Merge Process

After Party Merge
The 500 Vision Pkwy party site is transferred to Vision Inc. The details of the party
site uses for 500 Vision Pkwy, such as bill-to, ship-to and marketing stay with the
party site.
The 600 Vision Pkwy party site is merged with 600 Vision Pkwy to Vision Inc. The
bill-to site use is transferred because it does not exist for Vision Inc. The ship-to is
merged because it already exists for Vision Inc.
Vision Inc. has three party sites.
■ 100 Oracle Parkway with a bill-to site use
Customer Site ID: 1CUSTIDVISIONINC
■ 500 Oracle Parkway with a bill-to, ship-to, and marketing site use
Customer Site ID: 1CUSTIDVISIONCORP
■ 600 Oracle Parkway with a bill-to and ship-to site use

Party Merge 1-27

Party Merge Process


A
Party Entities

This appendix describes the party entities.

Party Entities A-1

Party Entities

Party Entities

The Party Merge dictionary stores the entities and procedures that must be
processed to merge the entities from any Oracle Application. These entities can be
identified using the foreign key attributes that they contain. If any entity contains an
attribute that is a foreign key to any of the TCA entities, these entities should be
part of the merge dictionary and a procedure should be created to handle the
records in this entity during the merge process.
This table lists the foreign keys in Oracle Applications and procedure details for all
the TCA entities processed during the merge process.

Entity Foreign Key Procedure
Party none HZ_MERGE_PKG.PARTY_MERGE
Customer Party ID HZ_MERGE_PKG.CUST_ACCOUNT_MERGE
Account
Contact Points Owner Table ID HZ_MERGE_PKG.CONTACT_POINT_MERGE
Financial Party ID HZ_MERGE_PKG.FINANCIAL_MERGE_MERGE
Profile
References Party ID HZ_MERGE_PKG.REFERNCES_MERGE
Certification Party ID HZ_MERGE_PKG. CERTIFICATION_MERGE
Credit Ratings Party ID HZ_MERGE_PKG.CREDIT_RATINGS_MERGE
Customer Party ID HZ_MERGE_PKG.CUST_ACCOUNT_ROLE_
Account Role MERGE
Code Owner Table ID HZ_MERGE_PKG.CODE_ASSIGNMENTS_
Assignments MERGE
Party Party ID HZ_MERGE_PKG.PARTY_RELATIONSHIP_
Relationship MERGE
Organization Party Site ID HZ_MERGE_PKG.ORG_CONTACT_MERGE
Contacts
Organization ORG_ HZ_MERGE_PKG.ORG_CONTACT_ROLE_
Contact Role CONTACT_ID MERGE

This table provides foreign key and procedure information about sites and their
related entities.

A-2 Oracle Trading Community Architecture Party Merge User Guide

Party Entities

Party Site Party ID HZ_MERGE_PKG.PARTY_SITE_MERGE
Customer Account Party Site ID HZ_MERGE_PKG.CUST _ACCT_SITE_
Party Site MERGE
Organization Party Site ID HZ_MERGE_PKG.ORG_CONTACT_
Contacts MERGE2
Contact Points Owner Table ID HZ_MERGE_PKG.CONTACT_POINT_
MERGE2
Party Site Use Party Site ID HZ_MERGE_PKG.PARTY_SITE_USE_
MERGE
Contact Restriction Owner Table ID HZ_MERGE_PKG.CONTACT_
RESTRICTION_ MERGE
Code Assignments Owner Table ID HZ_MERGE_PKG.CODE_ASSIGNMENTS_
MERGE2

This table provides foreign key and procedure information about
organization-related entities

Organization Party ID HZ_MERGE_PKG.ORG_PROFILE_MERGE
Profiles
Security Issued Party ID HZ_MERGE_PKG.ORG_SECURITY_ISSUED_
MERGE
Industrial Party ID HZ_MERGE_PKG.ORG_IND_CLASSES_MERGE
Classes
Financial Party ID HZ_MERGE_PKG.ORG_FIN_REPORTS_MERGE
Reports
Financial FINANCIAL_ HZ_MERGE_PKG. FINANCIAL_NUMBERS_
Numbers REPORT_ID MERGE
Organization Party ID HZ_MERGE_PKG.ORG_INDICATOR_MERGE
Indicators
Industrial Party ID HZ_MERGE_PKG.ORG_IND_REFERENCE _MERGE
Reference

This table provides foreign key and procedure information about person-related
entities.

Party Entities A-3

Party Entities

Entity Foreign key Procedure
Person Profiles Party ID HZ_MERGE_PKG.PER_PROFILE_MERGE
Person Interest Party ID HZ_MERGE_PKG.PER_INTEREST_MERGE
Citizenship Party ID HZ_MERGE_PKG.PER_CITIZENSHIP_MERGE
Education Party ID HZ_MERGE_PKG.PER_EDUCATION_MERGE
Employment Party ID HZ_MERGE_PKG.PER_EMP_HISTORY_MERGE
History
Work Class Employment_ HZ_MERGE_PKG. WORK _CLASS_MERGE
History_ID
Person Party ID HZ_MERGE_PKG.PER_LANGUAGE_MERGE
Languages

A-4 Oracle Trading Community Architecture Party Merge User Guide

B
Impact on D&B Information

This appendix describes the impact on D&B information of the merge process.

Impact on D&B Information B-1

Impact on Dun & Bradstreet Data


Oracle Trading Community Architecture lets you purchase data from Dun &
Bradstreet’s (D&B) global business databases. Information purchased from Dun &
Bradstreet is stored in the party tables at the party level and must be also merged
with other party information.
You must resolve and merge Dun & Bradstreet data for the merge-from and
merge-to parties. When you merge parties with D&B data, retain as much of the
D&B data about the parties as possible.
When you merge two parties with D&B data, you might encounter these situations:

DUNS Numbers Are Different
If the DUNS numbers for the merge-from and merge-to parties are not the same
number, the data for the merge-to party is retained. The D&B data for the
merge-from party is set to the Merged status.

DUNS Numbers Are the Same
If the DUNS numbers for the merge-from and merge-to parties are the same
number, the latest D&B data, whether for the merge-from or merge-to party, is
retained. If the latest Dun & Bradstreet data is stored for the merge-from party, that
data overwrites the D&B data stored for the merge-to party.

No D&B Data Exists for the Merge-to Party
If D&B data exists for the merge-from party but not the merge-to party, the D&B
data for the merge-from party transfers to the merge-to party as a result of the
merge process.

Merge-from Party is a Branch of Merge-to Party
If the merge-to party is the headquarters for the merge-from party, which is a
branch, and the merge-to party contains the D&B data, this data is retained. The
status of the merge-from party is set to Merged.

Merge-from Party is the Headquarters of Merge-to Party
When the Branch Flag attribute of the merge-from party is N, that party is the
headquarters location. If the merge-from party is the headquarters and the merge-to
party is its branch, the D&B data for the merge-from party is copied to the merge-to

B-2 Oracle Trading Community Architecture Party Merge User Guide


party. The merge-to party becomes the headquarters. All branches associated with
the merge-from party now belong to the merge-to party.

Impact on D&B Information B-3


B-4 Oracle Trading Community Architecture Party Merge User Guide

C
Duplicate Checking

This appendix describes duplicate checking in the context of the party merge
process.

Duplicate Checking C-1

Duplicate Checking

Duplicate Checking

You can either merge or transfer the child entities that belong to a party. These
entities can include party sites, contacts, relationships, and profile information. The
merge procedures automatically handles the merger or transfer of other child
entities.
Below are some of the TCA entities and the rules that are applied to them to
determine whether the entities should be merged or transferred. In general, if the
Party Merge process determines that the entities are exact duplicates based on the
concatenation of table columns, the merge-from record will be merged with the
merge-to record. If the entities are not exact duplicates, the merge-from entity is
transferred to the merge-to entity.

Contact Points and Restrictions
Contact Points
You must transfer contact points unless they are exact duplicates. If the following
columns in the HZ_CONTACT_POINTS table match, the contact points are exact
duplicates. Only exact duplicates are merged.
■ CONTACT_POINT_TYPE
■ STATUS
■ EDI_TRANSACTION_HANDLING
■ EDI_ID_NUMBER
■ EDI_PAYMENT_METHOD
■ EDI_PAYMENT_FORMAT
■ EDI_REMITTANCE_METHOD
■ EDI_REMITTANCE_INSTRUCTION
■ EDI_TP_HEADER_ID
■ EDI_ECE_TP_LOCATION_CODE
■ EMAIL_FORMAT
■ TO_CHAR(BEST_TIME_TO_CONTACT_START, ’DD-MON-YYYY’)
■ TO_CHAR(BEST_TIME_TO_CONTACT_END, ’DD-MON-YYYY’)

C-2 Oracle Trading Community Architecture Party Merge User Guide

Duplicate Checking

■ PHONE_CALLING_CALENDAR
■ DECLARED_BUSINESS_PHONE_FLAG
■ PHONE_PREFERRED_ORDER
■ TELEPHONE_TYPE
■ TIME_ZONE
■ PHONE_TOUCH_TONE_TYPE_FLAG
■ PHONE_AREA_CODE
■ PHONE_COUNTRY_CODE
■ PHONE_NUMBER
■ PHONE_EXTENSION
■ PHONE_LINE_TYPE
■ TELEX_NUMBER
■ CONTENT_SOURCE_TYPE
■ WEB_TYPE
■ EMAIL_ADDRESS
■ URL
Contact points can point to a party site. These contact points are transferred or
merged the way that the contact points are at the party level.

Contact Preferences
Contact preferences are always merged.

Customer Accounts and Related Information
Customer Accounts
Customer accounts are transferred to the merge-to party. After the parties are
merged, you can use the Customer Merge program to merge customer accounts.
This is a separate process that requires a separate concurrent request.

Customer Account Sites
Customer account sites are related to party sites. How customer account sites are
merged depends on how the party site is processed.


Duplicate Checking

■ Party site merge - The customer account site must be modified to point to the
existing merge-to party site.
■ Party site transfer - The customer account site should point to the merge-from
party site, which now points to the merge-to party.

Roles in a Customer Account
Each role in a customer account points to a party. A customer account role can be
processed during the Party Merge process in either of these situations:
■ The role points to the merge-from party
The role must be modified to point to the merge-to party.
■ The role points to an organization contact or other relate-able party relationship.
This relationship is being merged or transferred as the relationship’s subject or
object in a party merge.

Customer Contact Points
Customer contact points point to party-level contact points. The customer contact
point refers to the merge-to contact point on the merge-to party. This contact point
is either a pre-existing contact point for the merge-to party or a contact point that
was been transferred from the merge-from party.

Additional Party Information
If the duplicate check procedure identifies the following as exact duplicates, these
entities are merged, otherwise they are transferred.

When the Party is an Organization
If the duplicate check procedure identifies the following as exact duplicates, they
are merged.

Financial Numbers
If there is a duplicate financial number in the merge-to party’s financial report data,
that financial number is merged with the duplicate.

Financial Reports
The procedure checks for duplicates in these columns:
■ TO_CHAR(DATE_REPORT_ISSUED, 'DD-MON-YYYY')
■ DOCUMENT_REFERENCE
■ ISSUED_PERIOD

C-4 Oracle Trading Community Architecture Party Merge User Guide

Duplicate Checking

■ REQUIRING_AUTHORITY
■ TYPE_OF_FINANCIAL_REPORT
■ TO_CHAR(REPORT_START_DATE, ’DD-MON-YYYY’)
■ TO_CHAR(REPORT_END_DATE, ’DD-MON-YYYY’)
■ AUDIT_IND
■ CONSOLIDATED_IND
■ ESTIMATED_IND
■ FISCAL_IND
■ FINAL_IND
■ FORECAST_IND
■ OPENING_IND
■ PROFORMA_IND
■ QUALIFIED_IND
■ RESTATED_IND
■ SIGNED_BY_PRINCIPALS_IND
■ TRIAL_BALANCE_IND
■ UNBALANCED_IND

Industrial Classification
The procedure checks for duplicates in these columns:
■ INDUSTRIAL_CLASS_ID
■ TO_CHAR(BEGIN_DATE, ’DD-MON-YYYY’)
■ TO_CHAR(END_DATE, ’DD-MON-YYYY’)

Industrial Reference
Checks for duplicates on the following columns:
■ INDUSTRY_REFERENCE
■ ISSUED_BY_AUTHORITY


Party merge

Recommended

Recommended

More Related Content

What's hot

What's hot (19)

Viewers also liked

Viewers also liked (12)

Similar to Party merge

Similar to Party merge (20)

Party merge