Changing the Source System Assignments in SAP BW Objects without Affecting the Data Modeling

Transcription

1 Changing the Source System Assignments in SAP BW Objects without Affecting the Data Modeling Applies to: SAP ECC 6.00 and SAP BW 7.0 releases. For more information, visit the Business Intelligence homepage. Summary This document gives you the idea about how to change the source system assignment details in the mapping of all the data sources, transfer rules etc. without affecting any rules. Author: Company: Nitesh Verma Capgemini Consulting India private limited. Created on: 5 April 2010 Author Bio Nitesh Verma is currently, working in Capgemini Consulting as a SAP BI Consultant, he has more than 3 years of work experience in SAP BI Implementation, upgrade as well as support projects SAP AG 1

2 Table of Content Introduction... 3 Scenario... 3 Pre-requisites:... 3 Step by step process... 4 Step 1: Back Up for DBQ Step 2: Delete the RFC... 4 Step 3: Create the RFC... 5 Step 4: BDLS job test run... 6 Step 5: BDLS original run... 7 Step 6: After the Original run... 8 Step 7: Checking the source system Related Content Disclaimer and Liability Notice SAP AG 2

3 Introduction Most of the time in SAP BW projects the source system changes. This may be happen for many reasons like for testing the data in the BW with different systems or may be basis people migrates the old one with the new one or system copy etc. At this stage in SAP BW, we require to change the source system assignment in all the rules without doing all the mappings of data again with new one. Scenario Let s take an example that previously, the R3 source system (DBQ600) was having a client 600 and the BW development (BWD) is connected to the DBQ600. Now let s say system copy was happened in the R3 quality and the DBQ600 is changed to DBQ500. Means the client no. gets changed from 600 to 500. Now in this case, we need to move all the assignments of Datasources, Transfer rules, Transformation, Infopackages etc to new DBQ500 from DBQ600 and start load from DBQ500 without doing any manual intervention in recreation of the data flows. Pre-requisites: 1. Do not create the source system in the BWD for DBQ500 in any case. It will create the entries in the BWD system tables which will create the problem in the Source System assignment change. 2. The BWD should be in modifiable stage and also the source system which can achieve with the help of Basis people. 3. No one should login in the BWD or no RSA1 activity is going on in the BWD. 4. Stop all the Background jobs, scheduling etc. 5. Have a look in the SAP note SAP AG 3

4 Step by step process Step 1: Back Up for DBQ600 Take the back up of all the transfer rules and Datasources related to the DBQ600. This activity is for safety purpose. 1) Go to RSA1 Transport connection in BWD 2) Select the grouping method Save for system copy. 3) Drag and drop the source system DBQ600 in the collection area. 4) Create the transport request for the collected objects. 5) Go to Tcode SE09. 6) Release that transport request. Step 2: Delete the RFC Delete the RFC for the old source system. 1) Go to the Tcode SM59 in BWD 2) Select the RFC which is currently using in the DBQ600 source system. 3) Click on the delete button SAP AG 4

5 4) This is an example for 400, in my case I have deleted the 600 one both the dialog and the normal one. Step 3: Create the RFC Create the RFC for new client DBQ500 for remote connection. 1) Go to tcode SM59 in BWD. 2) Give the IP details in the Technical settings tab. 3) Give the correct logon details of background user to remote login in the DBQ500. 4) Do the connection test and authorization test for RFC SAP AG 5

6 Step 4: BDLS job test run BDLS is Tcode which is used for Logical system name conversion. First we need to do the test run to check and remove the errors and warnings if any. 1) Go to the Tcode BDLS in BWD 2) Enter the source system details in the old and new logical system names as I have entered. 3) The old name is the current one DBQ600 Source system logical name. 4) The new one is the name which is present in the DBQ500. For this: a. Go to the Tcode BD54. b. See the source system logical name. c. Take that name and copied to the new name blank in BWD. 1) Tick the first one like above. 2) Tick the test run and Tick check existence. 3) Click on the execute button. This will take nearly 5-10 minutes depending upon the objects present in the BWD. 4) The logs will come in the different window. The Logs is generally contains the details about where the entries for DBQ600 is maintained. Analyze the logs. If any error is there then try to remove that error with the help of Basis guy. If any warning is come then see the warnings details like Table names etc. Table names are generally related to the system tables. Check that details also with the basis guy that the tables which are giving warnings is critical tables or not. If yes then try to remove those warnings also otherwise it will give errors in the Original run SAP AG 6

7 5) After removing the errors and warnings. Execute the test run again and check the logs. Step 5: BDLS original run After doing the test run go for the original run. 1) After doing the whole analysis with the test run. Execute the original run like following. 2) In the original run be sure enough that no activities are going on in the RSA1. 3) The original run will take double time as compared to the test run. 4) In the original run, the places/tables where the entry is maintained with the DBQ600 is changed or replace with new one DBQ500. 5) This will not create the new source system for DBQ500 instead this will change the logical name of the source system from DBQ600 to DBQ500 and the Description remains the same which you can change after completion of the run. 6) This will also change the Flow details assignment SAP AG 7

8 Step 6: After the Original run. After the original run, we need to carry out some more steps to do the future activities i.e. Data loads etc. 1) Logoff from the BWD and re-login. 2) This will adjust the RFC to the source system. 3) Go to the connection parameter of the DBQ500 and check that it directing to the DBQ500 only not DBQ600. 4) Check the source system mappings also. 5) Replicate the source system i.e. Datasources. 6) After replication completion do the manual check of the data flows that it opens and working fine without any dumps. Step 7: Checking the source system. Check the source system that it is working fine for data loads or not. 1) Check the source system by right click on source system SAP AG 8

9 2) If ok then activate the source system and restore it. 3) But if the error comes like Idoc is not same as maintained in BW or Partner profile error or anything then do the following. a) Go to the R3 side. b) Go to SE16 Table RSBASIDOC and display the entries. c) In this table, mapping of BW to R3 system is maintained in my case the entries were 3, which is ideally should be 1. d) Just check that which mapping you require, in my case I requires only DBQ600 BWD150. e) So delete the remaining entries from the table. f) Go to the BW side and Restore the source system by giving the correct credentials. g) It will ask you to login in DBQ500 with administrator rights. h) After logging, the system will automatically do the Idoc and partner profiles settings. i) After that it will redirect to BWD and give you 2 options source system i.e. delete and do not delete for restoring the source system. So click on the delete button. This will create the source system again after deletion. 4) Do the source system check again in the BWD. 5) Try the data loading with any data source SAP AG 9

10 Related Content Note BDLS: Converting logical system names Note Logical system name conversion in T000 For more information, visit the Business Intelligence homepage SAP AG 10

11 Disclaimer and Liability Notice This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this do cument, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document SAP AG 11