Each transaction performed by the master index application is assigned a transaction type, indicating the type of action that was performed against the profile. The following table lists and describes each transaction type.
Table 3 Transaction Type Descriptions
Transaction Type |
Description |
---|---|
This transaction type is assigned when a new object profile is added to the database, whether it is through a direct add or through reversing an assumed match. |
|
This transaction type is assigned when a deactivated object profile is reactivated. |
|
This transaction type is assigned when an active object profile is deactivated. |
|
This transaction type is assigned when two object profiles are merged. |
|
This transaction type is assigned when two object profiles are unmerged. |
|
This transaction type is assigned when two source records are merged. |
|
This transaction type is assigned when a source record is transferred from one object profile to another. |
|
This transaction type is assigned when two source records are unmerged. |
|
This transaction type is assigned when an object profile is modified in any way other than those described above. This includes such transactions as modifying an object profile, reversing an assumed match, deactivating or reactivating a source record, and adding or removing a child object (such as an address or telephone number). |