Skip to Content

The migration mode in migration template determines what operation would be performed on the data entered in the migration template. Depending on the migration mode we can either create new records or modify existing records. By default the migration mode is set to “Add new records”. This can be changed by clicking on the “Properties” button in the migration template screen.

/wp-content/uploads/2015/12/1_847784.png

/wp-content/uploads/2015/12/2_847785.png

1) Add new records: This mode is used if we are creating new installed base/installation points in the system

2) Enhance already existing records: This mode is used if we want to add new data to already existing installed base/installation points. This means that the data which is entered in the template should not exist in the installed base/installation point except for the installed base ID or installation point ID. If we try to enter data which already exists then we will get an error. Example scenarios where this mode can/cannot be used is explained below:

a) Create installed base ( using migration mode “Add new records” ) with customer ( role code = 60 ) in installed base parties tab

/wp-content/uploads/2015/12/3_847830.jpg

/wp-content/uploads/2015/12/4_847836.jpg

/wp-content/uploads/2015/12/5_847837.jpg

b) Update installed base ( using migration mode “Enhance already existing records” ) with new parties like employee responsible or service technician ( role code = 39 or 43 ).This will execute successfully and the installed base will be updated with the new parties.

/wp-content/uploads/2015/12/6_847774.jpg

/wp-content/uploads/2015/12/7_847841.jpg

/wp-content/uploads/2015/12/8_847842.jpg

c) Update installed base ( using migration mode “Enhance already existing records” ) changing the customer. This will result in an error as the customer for the installed base already exists ( created in step 1)

/wp-content/uploads/2015/12/9_847850.jpg

/wp-content/uploads/2015/12/10_847852.jpg

/wp-content/uploads/2015/12/11_847857.jpg

Some scenarios where this mode should be used are as follows:

  1. You want to add new parties to existing installed base/installation points
  2. You want to add description in different languages to existing installed base/installation points
  3. You want to add notes data in different languages to existing installed base.
  4. You want to add detailed description in different languages to existing installation points.
  5. You want to add an existing registered product to an existing installed base.

3) Modify already existing records: This mode is used to modify already existing data of installed base/installation points. This means that the referenced data to be modified in the template should already exist in the installed base/installation point. If we try to enter data which does not exist then we will get an error. Example scenarios where this mode can/cannot be used is explained below:

a) Create installed base ( using migration mode “Add new records” ) with customer ( role code = 60 ) in installed base parties tab.

/wp-content/uploads/2015/12/12_847869.jpg

/wp-content/uploads/2015/12/13_847870.jpg

/wp-content/uploads/2015/12/14_847880.jpg

b) Update installed base ( using migration mode “Modify already existing records” ) changing the customer. This will execute successfully.

/wp-content/uploads/2015/12/15_847898.jpg

/wp-content/uploads/2015/12/16_847899.jpg

/wp-content/uploads/2015/12/17_847900.jpg

c) Update installed base ( using migration mode “Modify already existing records” ) adding new parties like service technician/employee responsible. This will result in an error ( as shown below ) as these parties don’t exist for the installed base.

/wp-content/uploads/2015/12/18_847919.jpg

/wp-content/uploads/2015/12/19_847920.jpg

/wp-content/uploads/2015/12/20_847921.jpg

4) Replace already existing records: This migration mode is used to create/modify installed base/installation points with the data as it is entered in the migration template.

  1. If the installed base/installation point does not exist it will be created with the data in the template.
  2. If the installed base/installation point exists then it will be updated based on the rules below
    1. Any previously existing data which is not present in the template will be deleted
    2. Any new data in the template which is not existing in the installed base/installation point will be created.
    3. Any data which is present in the installed base/installation point as well as in the template will be updated based on the data in the template

Choosing the correct migration mode is important while running migration template in order to avoid errors during upload or loss of data. Hope this information is useful in this regard.

Other important links related to installed base and installation points are mentioned below:

Registered Product BO information:

http://scn.sap.com/docs/DOC-68151

How to create installation point hierarchies using migration template:

http://scn.sap.com/community/cloud-for-customer/blog/2015/11/12/how-to-create-installation-point-hierarchy-using-migration-template

To report this post you need to login first.

3 Comments

You must be Logged on to comment or reply to a post.

Leave a Reply