Doublet cleansing

Basics

The tool Doublet cleansing offers administrators the option to merge duplicate contact persons, business partners and employees.

In the following, we will only detail the consolidation of contact partner and business partner duplicates. The procedure can also be applied for consolidating employee duplicates.

We distinguish between 4 types of doublet cleansing:

• Distribution of datasets (Processing type A)

• Deleting a dataset (Processing type L)

• Transfer of a dataset (Processing type X, Person ID = Primary keys differ)

• Consolidation of datasets (Processing type Z, Person ID = Primary keys are identical)

Overview of the processing types

Case 1: Distribution of business partner roles (Doublet cleansing: Processing type A, Role handling: Processing Type A)

Problem description

Person datasets with multiple roles exist in a system, which are to be distributed.

Note

The primary key (PK) of the business partner changes!

All Pk references (to datasets, link tables, etc.) are also changed to the new Pk.

Procedure for the separation of a business partner role

In the following example, the business partner role Sample AG₂ is to be separated from its original person Sample AG₁ and given its own new person.

1. Creation of a doublet cleansing

2. Select the processing type A "Distribute"

3. The person of the business partner role Sample AG₂ to be handled is to be entered as a person doublet

4. Create a new doublet handling via "create new and assign" /Role Handling

5. Select the processing type A "Distribute"

6. enter "Business partner" in the field 'Role name'

7. Enter the business partner (in older versions the primary key of the business partner role) Sample AG₂ in the field "PK slave role"

Case 2: Deleting the business partner duplicate (Doublet cleansing: Processing type L)

Problem description

A person dataset with a role that is to be deleted exists in a system.

Procedure for deleting a business partner doublet

In the following example, the business partner role Sample AG₂ including the person dataset is to be deleted.

All dependent data will remain intact (activities, documents, etc.).

1. Creation of a doublet cleansing

2. Select the processing type L "Delete"

3. The person of the business partner doublet Sample AG₂ to be handled is to be entered as a person doublet

All dependent data will remain intact. Person and role will be deleted (physical removal from the database).

A role handling will not be necessary in this case.

Case 3: Transferring the business partner (Doublet cleansing: Processing type X, Role handling: Processing type Z)

Problem description

2 person datasets with individual roles exist in a system. Both roles should be assigned to one person, so that one person will be deleted and one role is reassigned.

2 role handling procedures are initiated. One role handling for the role 'Business partner' and one for the role 'Default contact person', because not only the business partners as such must be consolidated - that also has to be done for the default contact persons.

Background

When the two business partners were originally created, the system created a default contact person for each business partner. When the two business partners are now consolidated via doublet cleansing, then you must also include the default contact persons in the relevant role handling.

Use case

• Sample AG1 with own person (and an own default contact person).

• Sample AG2 with own person (and an own default contact person).

In this case study, Sample AG₂ is to be merged with Sample AG₁, so that only one person Sample AG1 remains with one role.

Procedure for business partner transfer

In the following example, the person of the business partner role Sample AG₂ is to be deleted and the business partner role Sample AG₂ is to be transferred to the person of Sample AG₁.

The Sample AG₂ business partner is merged with the Sample AG₁ business partner.

A person dataset Sample AG₁ with a business partner Sample AG₁is created.

All dependent data will remain intact (activities, documents, etc.).

1. Creation of a doublet cleansing

2. Select the processing type X "Transfer"

3. The person of the business partner doublet Sample AG₂ to be handled is to be entered as a person doublet

4. The person _{Sample AG1} to whom the business partner is to be attached, must be entered in Original Person

5. Create a new doublet handling via "create new and assign" /Role Handling

6. Select the processing type Z "Merge"

7. enter "Business partner" in the field 'Role name'

8. The business partner Sample AG₂ must be entered into the "PK slave role" field

9. The business partner Sample AG₁ must be entered into the "PK master role" field

The two contact persons are also to be merged in the same duplicate run.
The default contact person Sample AG2 will be merged with the default contact person Sample AG1.
A person set Sample AG1 with a default contact person Sample AG1 is created.

1. Create a new Role handling via "create new and assign" /Role Handling

2. Select the processing type Z "Merge"

3. Enter "Contact person" in the field 'Role name'

4. The default contact person Sample AG₂ must be entered into the "PK slave role" field

5. The default contact person Sample AG₁ is to be entered into the "PK master role" field

Tip

You should extend your search to include the fields 'ID person', 'Primary key', 'Creator', and 'Creation date' if the match code for the entries in the fields 'Original person' and the doublet person are the same.

Case 4: Consolidation of business partner roles (Doublet cleansing: Processing type Z, Role handling: Processing type Z)

Problem description

Two roles exist for one person dataset in a system. Only one role should be attached to the person dataset, which means the roles must be merged.

Use case

• Sample AG1 with person dataset Sample AG1

• Sample AG2 based on the person dataset Sample AG1 (second business partner role)

Procedure for the consolidation of business partner roles

In the following example, the business partner role Sample AG₂ is to be merged with the business partner role Sample AG₁.

1. Creation of a doublet cleansing

2. Select the processing type Z "Merge"

3. The person of the business partner roles Sample AG₁ and Sample AG₂ to be handled is to be entered as a person doublet

4. The field 'Original person' will be automatically populated with the same value

5. Create a new doublet handling via "create new and assign" /Role Handling

6. Select the processing type Z "Merge"

7. enter "Business partner" in the field 'Role name'

8. The business partner Sample AG₂ must be entered into the "PK slave role" field

9. The business partner Sample AG₁ must be entered into the "PK master role" field

Case 5: Transferring contact person roles (Doublet cleansing: Processing type X, Role handling: Processing type X)

Problem description

Two roles with an own person dataset exist in a system. Both roles should be attached to the person dataset, so that one role must be transferred to the other person dataset and the original person dataset will be deleted.

Use case

• Hans Mustermann 1 with the person dataset Hans Mustermann 1

• Hans Mustermann 2 with the person dataset Hans Mustermann 2

Procedure for the transfer of contact person roles

In the following example, the contact person role Max Mustermann₂ is to be transferred to the person of the contact person role Max Mustermann₁ .

1. Creation of a doublet cleansing

2. Select the processing type X "Transfer"

3. The person of the contact person roles Max Mustermann₂ to be handled is to be entered as a person doublet

4. The field 'Original person' is populated with the person to which the contact person role is to be transferred (Max Mustermann₁).

5. Create a new doublet handling via "create new and assign" /Role Handling

6. Select the processing type X "Transfer"

7. Enter "Contact person" in the field 'Role name'

8. The primary key of Max Mustermann₂ is to be entered into the "Slave Role Primary Key" field

Initializing the doublet script

The consolidation of the individual doublets as per the entry into the tool Doublet cleansing is started by initializing the doublet script.

The doublet script is initialized via special start parameters of the client. These can be modified via the desktop link:

> client\jboss\bin\run.bat doublet <BENUTZERNAME> <PASSWORT>

The doublet script should be initialized at night (e.g. via a Windows server schedule) - and not during business hours. There should be no other users in the system.

That can be verified by the administrator via the menu item Extras / Active Users..

Background

• Performance
  The greater the volume of data to be moved, the more resources will be needed. This may take some time for large databases. The doublet run should therefore be done at night, so as to not impact on running operations.

• Conflicts
  A conflict may occur if a user is working on a dataset that is currently being edited in the doublet run.

  

  Hinweis

  Doublet cleansing starts without a prompt. Any changes made cannot be recovered without a backup.

  
  Background

• Transaction
  All database changes will be rolled back if an error occurs during processing.

• Logging
  The current status and all SQL statements can be viewed in the server log. The following settings are required. Example in jboss-log4j.xml:

 <category name="de.cursor.jevi.server.util.doublet.Doublet">
<priority value="DEBUG"/>
</category>
<category name="de.cursor.jevi.server.util.doublet.dao.DefaultDoubletDAO">
<priority value="DEBUG"/>
</category>