Services Integration Framework Guide

10.4 HotFix 1
- 10.5
- 10.4 HotFix 3
- 10.4 HotFix 2
- 10.4
- 10.3 HotFix 3
- 10.3 HotFix 2
- 10.3 HotFix 1
- 10.3

Back Next

Unmerge

unmerges two rows in a base object.

Unmerge

provides the same unmerge functionality as the Data Manager tool in the Data Steward workbench. This request restores all foreign keys updated in the merge.

Unmerging can take a long time to complete, so you may want to run the unmerge asynchronously. You cannot use unmerge within a transaction. For more information about unmerging and merging, see the

Multidomain MDM Configuration Guide

If the request is unsuccessful, the program throws an Informatica request exception. If the request is successful, then the response also indicates that the unmerge succeeded.

You can configure Unmerge requests according to a specific system when using the Hub Console Audit Manager to audit requests made by external applications. Once auditing for a particular SIF API request is enabled, Informatica MDM Hub captures each SIF request invocation and response in the audit log. For more information, see the

Multidomain MDM Configuration Guide

Cross-reference Added Directly to a Base Object

Typically when a new cross-reference is inserted, a new base object record is created for it. But Put or CleansePut APIs and the “Load By ROWID” batch job can also add a cross-reference record directly to a base object. This means that the cross-reference record was never the only cross-reference for a base object record. When such a cross-reference record is identified to be unmerged, it is deleted from the system and there is no independent base object record to reinstate for it.

Linear Unmerge

During a linear unmerge, no attention is paid to the process by which the records were originally merged.

Consider a scenario where initially there are three base object records with ROWID_OBJECT values of 1, 2, and 3. Each of these base objects has a single cross-reference record with corresponding source keys 1, 2, and 3, and SALES as the SystemName value. If you merge ROWID_OBJECT 3 into 2, and then merge ROWID_OBJECT 2 into 1, then as a result of the merge a single base object record with ROWID_OBJECT 1, and three cross-reference records remain.

Now, if sourceKey 2 of the SALES system is targeted for a linear unmerge, then the base object of sourceKey 2 is reinstated and the cross-reference of sourceKey 2 is associated with the reinstated base object. The resulting base object records are as follows:

ROWID_OBJECT=1 has two cross-reference records with sourceKeys 1 and 3.

ROWID_OBJECT=2 has one cross-reference records with sourceKey 2.

Tree Unmerge

During a tree unmerge, the process by which the records were originally merged determines the outcome.

Consider a scenario where initially there are three base object records with ROWID_OBJECT values of 1, 2, and 3. Each of these base objects has a single cross-reference record with corresponding source keys 1, 2, and 3, and SALES as the SystemName value. If you merge ROWID_OBJECT 3 into 2, and then merge ROWID_OBJECT 2 into 1, then at the time record 2 was merged into record 1, record 3 had already been merged into 2. So the cross-references for sourceKeys 2 and 3 are removed from the base object and the base object record for sourceKey 2 is reinstated. The resulting base object records are as follows:

ROWID_OBJECT=1 has one cross-reference record with sourceKey 1.

ROWID_OBJECT=2 has two cross-reference records with sourceKeys 2 and 3.

In both cases, the consolidated field values in the base object record are recalculated after the unmerge.

Cascade Unmerge

Unmerge performs a cascade unmerge if this feature is enabled for this base object in the Schema Manager in the Hub Console. With cascade unmerge, when records in the parent object are unmerged, Informatica MDM Hub also unmerges affected records in the child base object.

Required Parameters

The following table lists and describes the parameters that are required by the Unmerge API:

Parameter	Description
SiperianObjectUid	Name and type of the package or base object containing the record to be unmerged.
SystemName	Name of the system for which the record must be unmerged.
SourceKey	Source key of the record that must be unmerged.
TreeUnmerge	Set to true for a tree unmerge operation or false for a linear unmerge operation.

Use Case

This is the common scenario for using the Unmerge request:

In a custom UI, use unmerge to allow a data steward to manually unmerge records. A data steward might unmerge records when, for example, a merge of two records was done in error.