Archiving in Customer/Vendor Integration

Purpose

If you have activated master data synchronization, you should be aware that this affects the archiving and deletion of master data objects. The information about archiving or deletion is also synchronized, as a change to the master data source object, with the corresponding maser data target objects. Setting the archiving or deletion indicator for one of the objects does not restrict the synchronization in any way. Despite these indicators being set, changes to the master data objects continue to be synchronized with one another. The only exception to this is the creation of new objects, as long as the source object is flagged for archiving or deletion.

Both the archiving session of the source object and the archiving session of the target object are triggered for an activated synchronization process of the master data synchronization. Since both archiving sessions can be started independently of each other, it must be defined which one takes precedence. In principle, the archiving was implemented in such a way in the context of the Customer/Vendor Integration that the archiving process of the business partner takes precedence over the archiving process of the customer master or vendor master. In this way, a customer or vendor master can be archived only if the corresponding business partner has already been archived.

When a business partner is archived, the information about key mapping is archived in addition to the business partner data and relationships. The fact that data for the key mapping is now missing in the system allows the archiving process of the customer or vendor master to recognize that the corresponding business partner was archived. The customer or vendor master can now be archived, and deleted in the system.

Process

Below is an overview for Customer/Vendor Integration of the effects on the archiving. Which effect a particular action, performed on the source object, has on the corresponding target object and on the archiving is represented from the point of view of the master data maintenance.

Note Note

For the sake of greater clarity, only the customer master is referred to below. However, the master data object 'customer master’ can be freely replaced with the master data object 'vendor master’.

End of the note.

Synchronization Between Customer Master and Business Partner

Scenario 1: Business Partner Archiving Session Takes Place Before Customer Master Archiving Session

Action	Source Object: Customer Master	Target Object: Business Partner
Initial synchronization	You create a customer master.	The system creates a new business partner.
Delta synchronization	You change the customer master	The system changes the business partner.
Delta synchronization	You set the deletion indicator.	The system sets the indicator Archiving Flag .
The archiving session of the business partner is started.		The system archives the business partner and the relevant key mapping. It deletes the business partner and the key mapping in the database.
The archiving session of the customer master is started.	The system archives the customer master and deletes it in the database.

Scenario 2: Customer Master Archiving Session Takes Place Before Business Partner Archiving Session

Action	Source Object: Customer Master	Target Object: Business Partner
Delta synchronization	You set the deletion indicator.	The system sets the indicator Archiving Flag .
The archiving session of the customer master is started.	The system cannot archive the customer master, since the check shows that the corresponding business partner has not been archived yet.
The archiving session of the business partner is started.		The system archives the business partner and the relevant key mapping. It deletes the business partner and the key mapping in the database.
The archiving session of the customer master is started again.	The system archives the customer master and deletes it in the database.

Scenario 3: Deletion Indicator Reset in Customer Master After Business Partner Already Archived

Action	Source Object: Customer Master	Target Object: Business Partner
Delta synchronization	You set the deletion indicator.	The system sets the indicator Archiving Flag .
The archiving session of the business partner is started.		The system archives the business partner and the relevant key mapping. It deletes the business partner and the key mapping in the database.
Delta synchronization	You change attributes in the customer master	The system does not create any new business partners, as long as the deletion indicator is still set in the customer master.
Delta synchronization	You reset the deletion indicator.	The system creates a new business partner.

Synchronization Between Business Partner and Customer Master

Scenario 1: Business Partner Archiving Session Takes Place Before Customer Master Archiving Session

Action	Source Object: Business Partner	Target Object: Customer Master
Initial synchronization	You create a business partner.	The system creates a new customer master.
Delta synchronization	You change the business partner.	The system changes the customer master.
Delta synchronization	You set the indicator Archiving Flag .	The system sets the deletion indicator.
The archiving session of the business partner is started.	The system archives the business partner and the relevant key mapping. It deletes the business partner and the key mapping in the database.
The archiving session of the customer master is started.		The system archives the customer master and deletes it in the database.

Scenario 2: Customer Master Archiving Session Takes Place Before Business Partner Archiving Session

Action	Source Object: Business Partner	Target Object: Customer Master
Delta synchronization	You set the indicator Archiving Flag .	The system sets the deletion indicator.
The archiving session of the customer master is started.		The system cannot archive the customer master, since the check shows that the relevant business partner has not been archived yet.
The archiving session of the business partner is started.	The system archives the business partner and the relevant key mapping. It deletes the business partner and the key mapping in the database.
The archiving session of the customer master is started again.		The system archives the customer master and deletes it in the database.

Scenario 3: Archiving of Business Partner Data and Customer Data, and Subsequent Restoring of Data from the Archives

Action	Source Object	Target Object
Delta synchronization	You set the indicator Archiving Flag .	The system sets the deletion indicator.
The archiving session of the business partner is started.	The system archives the business partner and the relevant key mapping. It deletes the business partner and the key mapping in the database.
The archiving session of the customer master is started.		The system archives the customer master and deletes it in the database.
The archiving session of the purchasing info record is started.	The system archives the purchasing info record and deletes it in the database.	The system deletes the product relationship and the key mapping in the database.
The customer data is restored from the archive	The system reads the data from the archive and creates the customer record.	The system neither assigns a business partner, nor does it create a new business partner.
The business partner data is restored from the archive	The system reads the data for the business partner and the key mapping from the archive, and creates the business partner.	As long as the corresponding customer master was not assigned to another business partner in the meantime, the system reassigns the originally assigned business partner, according to the key mapping, to the customer master.

Caution Caution

If the customer master is uploaded after the corresponding business partner from the archive, the key mapping can no longer be restored, and is lost.

End of the caution.