transporting organizational structure from one system to another

10
Transporting Organizational Structure from one system to another By Ribhu Ahuja, Tata Consultancy Services Scenario: We have two systems – DEV (Development) and QA (Quality) – These are CRM 2007 systems or they can be SAP R/3 systems as well. We have an org structure created on the DEV system and we want to replicate it in the QA system. Steps and reports used: First of all, let us see the organizational structure in the dev server. Use T code PPOMA_CRM to see the same. In R/3 systems, the TCode would be PPOME. We need three standard reports to completely transfer the HR data from one system to the other. These reports are – RHMOVE00, RHMOVE30 and RHALTD00. First, we execute the report RHMOVE00 on the DEV server.

Upload: muhammad-javeed

Post on 03-Jan-2016

25 views

Category:

Documents


1 download

DESCRIPTION

Transporting Organizational Structure From One System to Another

TRANSCRIPT

Page 1: Transporting Organizational Structure From One System to Another

Transporting Organizational Structure from one system to another

By Ribhu Ahuja, Tata Consultancy Services

Scenario:

We have two systems – DEV (Development) and QA (Quality) – These are CRM 2007 systems or they can be SAP R/3 systems as well. We have an org structure created on the DEV system and we want to replicate it in the QA system.

Steps and reports used:

First of all, let us see the organizational structure in the dev server. Use T code PPOMA_CRM to see the same. In R/3 systems, the TCode would be PPOME.

We need three standard reports to completely transfer the HR data from one system to the other. These reports are – RHMOVE00, RHMOVE30 and RHALTD00.

First, we execute the report RHMOVE00 on the DEV server.  

Page 2: Transporting Organizational Structure From One System to Another

In the Plan version, choose 01 – current plan version.

In Sequential file box, in file type choose P – for physical file and PRESS ENTER.

Page 3: Transporting Organizational Structure From One System to Another

In the field File name, press F4 and it shows the directory to choose the file from.

Notice the directory name here - /usr/sap/dev/work - this is the default directory of the dev server on which we need to create a file (BASIS consultants would be helpful here). Give this directory name to the basis person and ask him to create a file there named ‘hrdata’ and grant you the write permission to this file. We will use this file hrdata to export our records from dev server. This file would be Unix or Windows NT based file depending on the server type. The basis person will create this file hrdata on the specified server path. Once the file is created, it will show on the list of file name:

Now choose this file and return to the previous screen.  

Page 4: Transporting Organizational Structure From One System to Another

Now execute the transaction. It shows the list of entries exported:

Now, our file ‘hrdata’ contains all the data, which needs to be imported to the QA server. With the help of BASIS consultant, copy the file ‘hrdata’ from DEV server to QA server i.e. from path /usr/sap/dev/work to /usr/sap/qua/work with the same rights and permissions provided on the dev server.

Note: If our requirement is to transport the HR data from one client to another, we can do the same by

clicking on button and specifying the client to which we want to transfer the

Page 5: Transporting Organizational Structure From One System to Another

data.

In the other scenario, where we are copying data from one server to another, this

task won’t solve our purpose. In QA server, run the report RHMOVE00 and choose P for physical file. This time, our working directory would be /usr/sap/qua/work/hrdata. Once you execute the report in the quality server, the following screen appears:

Click on the button. We get the following screen:

Execute the report and we see the following screen:

Page 6: Transporting Organizational Structure From One System to Another

Press the button and we are on the batch input session screen (SM35) 

Choose our entry – PD and click on the button. If we choose foreground update, we can see the data being updated in the screens as shown:

Page 7: Transporting Organizational Structure From One System to Another

 

This way all the master data will get uploaded to the quality system. This will transport all the master data, but if we compare the TCode PPOMA_CRM of DEV and QA servers, it will show that the organizations have been created, positions beneath them are created but the persons attached to the positions are not showed up. For doing that, we need to execute the report RHMOVE30 on the dev system and we see the following screen: 

Page 8: Transporting Organizational Structure From One System to Another

Make the entries as shown in the figure and hit F8. We see the following screen:

Page 9: Transporting Organizational Structure From One System to Another

Click select all - and then click . It asks for the transport request number: 

Page 10: Transporting Organizational Structure From One System to Another

Give the same or create a new request. Once done, release the request and transport the same. After the request is transported, execute the transaction PPOMA_CRM in QA server. Thus we see that the entire org structure is transported to the QA server from the DEV server. Now we see the persons attached to the positions too.