Source system server migration (new ip address)

Hi Experts
We are moving our servers (source systems) to new boxes. The source systems will be copied to the new ones and the only thing changing will be the IP addresses. BW server will not be touched.
Do I need to create new source systems? I am hoping not to do this and, Are the deltas will be ok? Or do I need to reinitialize all the delta loads?
Thanks!
Daniel

Hi Daniel
No need to create new source system...In fact without deleting the existing one, you wont be able to create same source again.
And do not delete , because that means you will lose all the DataSource.
Need to adjust RFC to point to different hostname /IP address.
In case any inconsistency happens , need to restore the source system connection from BW side.
RSA1-->Source System--->Resotre ...this will automatically adjust RFC connection. Search Forum to know the process of restore in detail if needed.
Delta might need to be re-initialized. Are you planning to clear all the queue before ( LBWQ) server migration? Else you might end in some problems during migration if you are doing it by database restore method.
Regards
Anindya
Edited by: Anindya Bose on Feb 10, 2012 6:38 AM

Similar Messages

We would like to test old deltas from the source system( copied to new)

Hi Gurus,
The scenario is
They will make a DB copy of the Prod system onto a QA system, the Copied system will have
its system ID changed(SID) to a new one.
There will be deltas available in the RSA7, as this is a copy of the 3 weeks old prod
system. Now the delta's will be available on the Copied system pointing to the BW Prod system.
We would like to test these delta's to BW Dev. why we would like to do the delta's to the
BW dev system is to check whether we can do system copies without clearing the delta's on
the source system.
After the system copy we will do all the activities necessary to reflect the system changes
a. Like BDLS, We20, we21,ALE checks, RFCDES, RSLOGSYSDEST, RSBASIDOC, etc on the source system to
reflect the changes of the BW Prod system to BW Dev system.
b. Likewise, we will perform all the above activities on the BW dev system by changing the
existing source system to the new source system( performing BDLS,we0, we21, etc)to reflect
the new Source system with the new (SID).
c. We will check the source system connection
d. Replicate the datasources on the new source system
e. Activate the Transfer rules for the new source system.
Now for us to do delta's from the new source system to the Bw dev system we need to change
underlying tables in source system to point the delta's, arfc TID's etc to the BW dev system.
We can change the entries in the TRFCQOUT, ARFCCSTATE, ARFCDATA tables to point the LUW's and
destination to the BW dev system.
What I presume is if we run the BDLS on the Copied system to change the BW prod system to BW
and also the underlying Tables for the LUW's and etc will still be pointing to BW Dev. I would
like to know if this is the case .
Lastly, appreciate if anyone can say if this is possible to do without having to clear the
BW delta queue on the source system.

Hi Ramesh,
Appreciate a lot for your response, but i would like to know if we can reflect the entries in table RSSDLINIT(Last Valid Initializations to an OLTP Source) and RSSDLINITSEL(Last Valid Initializations to an OLTP Source) in the BW system on the copied source system
tables ROOSPRMSC(Control Parameter Per DataSource Channel), ROOSPRMSF(Control Parameter Per DataSource Channel) by executing the ABAP program RSSM_OLTP_INIT_DELTA_UPDATE after we do the BDLS conversion on the new copied source system.
After the BDLS conversion I reckon the entries in the RSA7 queue, ARFCCSTATE, TRFCQOUT tables willl reflect the BW Development system instead of the BW Production system isnt it.
response much appreciated.
Kalyan

Problem BW : DTP lost source system mapping and new one created?

I had a little question concerning the BI content activation, when you have to activate objects and there are two source systems, one of them already with a flow working. Do you have to check both source systems in your screen of source system selection, if there are shared objects? I was afraid if I only checked the one I wanted the existing one would dissappear? I donu2019t want to touch the existing one as it was a 3.5 flow which has been migrated to 7.0.
I have also another question, which is a worse scenario of what has happened recentlyu2026!! Imagine you have originally one source system in your BW DEV environment (towards QA) with a certain amount of Datasources connected to it as well as some DTPu2019s. A new source system was added to this BW DEV (towards PROD). Do you think adding this new source system could have an impact in the mapping of the DTP towards the Datasources? In fact, some of our DTP have been modified and they are pointing to the incorrect Datasource/Source system. These DTP were created manually as well as the Transformations as it was a former 3.5 flow. Do you know a way to bring it back to itu2019s previous connection. Maybe a table that points to the correct source system or a function module? RSBKDTP and RSBK* tables do not store this info (only descriptions) and RSRV doesnu2019t do it.
Please let me know if you have had a similar case! Points are waiting and the gratitude of my boss...lol

Any ideas?

Migrate Dataservices source system to new source system type in BW 7.3

Hi All,
We have upgraded our BW system to 7.3. In our old 7.0 environment we have linked Data Services 4.0 as an external source system. Now in BW7.3 we would like to migrate the developments on the old source system to the new source system type.
Does anyone know if there is any migration tool which we can use for this?
Best regards,
F. Geldof

Hi Valerie,
Unfortunately i didn't find the answer yet. For the moment we have kept the old connection types to our DS environment.
Good luck!
Best regards,
F. Geldof

How to transfer all the transfer structure to new source system ?

Hello
I have created a new source system on my BW system with new RFC connection .
I want to replace all my old transfer structure with old source system to this new system .
can u plz let me know how can i do this ?
Regards,

can u plz many help in this ?

Weblogic server not working on new Ip address

Hi,
I tried to change the listen Ip address for the weblogic server.
i am able to start the server on new Ip address but the console is not opening.
Please help.
I need to do this to make my weblogic server available in case of high availability.
thanks in advance.

Can you provide some more information on what was working, what you changed and what is working now?
What are you starting with the new IP? Admin Server? Managed Servers? If you goto to the Admin Server URL in a browser what do you see?
Thanks,
Mark

G/L account picked for the "wrong" source system entry

Dear Experts,
in SRM 7.0, Classic Scenario, i am facing the following issue with respect to G/L account determination in the SC:
We have three R/3 systems connected to SRM. All these R/3 systems use the same Material Groups, but the G/L accounts are different in each R/3 system.
In the Table "Determination of G/L Account using product categories", i have maintained the repsective combinations. For each combination of product category and account assignment category, the respective G/L account is defaultet for the respective source system.
But in the shopping cart, the determination of the correct G/L does not always work. When a user enters the shopping cart initially with a line item that is accounted to his default account assignment category, than the correct G/L account for his source system is derived. But if he changes the account assignment category of the line item, than a G/L account from a "wrong" source system is getting picked up from the table.
I have checked the GUIDs of the product categories between "Comm_category" and "bbp_det_account" and they are correct.
What can be the reason for the picking of the G/L account from the wrong source system?
Can the note 1357871 bring the correction?
Thank you very much!

Hello Dima,
I think your problem comes from your source system for product category management.
Could you clarify one point: if you change account assignment category, does new G/L account have to be determined for same backend system too or not ?
If yes, correct new G/L account will be determined using your customizing (IMG: SAP Implementation Guide > SAP Supplier Relationship Management > SRM Server > Cross-Application Basic Settings > Account Assignment > Define G/L Account for Product Category and Account Assignment Category ).
If it does not work, log an OSS message.
If no, you need to switch value for each SC item field BBP_PDIGP-LOGSYS_FI from old backend source system to the new one. For this, use BBP_DOC_CHANGE_BADI.
Then, your customized G/L account definition for product category and account assignment category should be OK.
Regards.
Laurent.

Reconnect R/3 source system after BW systemcopy ?

We want to copy our BW 3.0b development system as a BW sandbox system in order to try out the BW 3.5 migration.
Therefore, we performed a system copy of our BW DEV system to a new machine. On the BW-side we ran BDLS to get a new logical name for the system and defined a RFC connection to our R/3 Dev Source System (incl. appropriate RFC users).
On the R/3 side we also defined an additional RFC connection to the "new - just copied" BW-system.
While trying to reconnect our R/3 Devopment source system within the new BW we encountered the problem that the R/3 system recognized that there already exists a connection to a BW (the old BW dev). If we take this option, the old connection is deleted and a new one is defined. However, from the R/3 perspective we want two BWs connected. It seems the problem has to do with the IDOCs and TRFC port definitions, because the IDOC type ZRSBW010 seems to point to the wrong system.
Unfortunately, we are stuck at the moment.
Any kind of help or hints to relevant SAP documents would be much appreciated.
In the OSS we found some notes on this topic (325525 etc.) but we still not sure how to proceed.
However, in general, we think it shouldn't be a problem to have one R/3 connected to several BW's or is it?
Frank Schülke, E.ON Ruhrgas IT, Germany

Frank,
It is possible to connect a copy of your BW dev. system to the same R/3 system. The problem you are experiencing is related to the connection ID from table RSABASIDOC. This is a unique ID in your system (normally the first two characters of your source system name). Tis ID is in RSBASIDOC in yuor BW and R/3 system. When you copy your BW and try to connect it to your R/3 system again, you will get the conflict you already noticed.
The solution is to run SE37 --> RSAP_BIW_DISCONNECT in your new BW system (make a screen shot first of the RSBASIDOC entry!). This will be cleared by the function module. You will notice that the source system is not visible anymore is RSA1. However all the transfer rules etc. are still there (invisible). This would not be the case when you are doing a remove source system in RSA1 as suggested. Now you can create the source system again via the normal way. Use exactly the same name for the source system mas you made it via the BDLS. During this process the BW and R/3 systems are "negociating" a new unique connection ID for this BW-R/3 connection. This creation of the source system will also make all the related info visible again (like transfer rules).
Note in general: If you get a screen saying the connection ID is already used, ALWAYS choose DO NOT DELETE. After chosing DELETE there is no way of solving the issue other then restoring the system from backup! In this case you would delete everything in your R/3 system regarding the original BW system! When you get the message, check RSBASIDOC in both systems as there will be a conflict.
Regards,
Sander.

BI Source system (critical issue)

Hi Friends,
I am working as a basis consultant.
we have a ECC6 Development server and in the same server we hav installed BI-Cont and using as a BI Dev sever too.
Client - 400 is R/3 Develop server
Client - 300 is BI Develop server
we cofigured 400 client as a source system for bi(300) and lot of develpments are made.
Now we are planning to make this ECC6 DEV as a Production server for BI. (simultaniously R/3 developments also will happen in the same server).
Now i have Created a new client-500 for BI(Production) in the same server and i want to add our R/3 Production server client-900(different server) as a Source system.
1 I maintained RS_MANDT_UNIQUE_SET and set to client 500.
2 I maintained table RSADMINA and set client 500
and BW_user
3 Created RFC between client 500 to PRD server client 900
now when i tried RSA1 Transaction in BI PRD client 500, it says "Logical system name has been changed for this system" "Message no. R3206"
when i see the long text it says
"The logical system name of this system is PRDCLNT500. However, this system was originally created with the logical system name DEVCLNT300. It is not permitted to change the logical system name, as connections to other systems will be damaged beyond repair.
System Response
The transaction is canceled.
Procedure
Change the name of the logical system (table T000) for client back to DEVCLNT300. This enables you to continue working with the system.
If you really want to change the logical name, than you can, if and when you:
change the system name back to DEVCLNT300,
delete all existing connections between this system and other systems,
delete all transfer structures that still exist, and
do not use ALE or Workflow."
1 I tried to remove the source system from 300, but it is prompting to delete lot of packages and it is going for a while. so i stopped it.
2 I removed all the RFC Connections between 300-400
3 I deleted the logical system "DEVCLNT300".
Still the same Issue "Logical system name has been changed for this system".
Please help me Resolving this issue, since this issue became so critical.
Thanks in advance
Prakash

Thank you for Replying
I know the landscape we are having will confuse.
In ECC6 DEV Server a new client 500 is created for BI Producion server (not exactly prod but assume like that).
There is seperate R/3 Production server (client-900) and that shud be configured as a source system for the new BI PRD Client 500.
I dont want any data from 300, infact i would delete the 300client (BIdevclt) after i configure everything in client 500.
I did all the BI post installation steps for client 500.( including RS_MANDT_UNIQUE_SET)
but since the 300 client was configured as BW dev in the same server, i am getting an error if i access RSA1 in client 500 "Logical system name has been changed for this system" "Message no. R3206"
I went through the BDLSS transaction, but it talks about converting logical system and i dont want to do that.
Client400 is configured as source system for bi dev 300. I want to delete all the configuration made in 300.
I want to know deleting the souce client manually from BI dev 300 client is the only way to fix this or anything else we could do it for this ERROR.

Reconnect of a R/3 source system afer a BW system copy

We want to copy our BW 3.0b development system as a BW sandbox system in order to try out the BW 3.5 migration.
Therefore, we performed a system copy of our BW DEV system to a new machine. On the BW-side we ran BDLS to get a new logical name for the system and defined a RFC connection to our R/3 Dev Source System (incl. appropriate RFC users).
On the R/3 side we also defined an additional RFC connection to the "new - just copied" BW-system.
While trying to reconnect our R/3 Devopment source system within the new BW we encountered the problem that the R/3 system recognized that there already exists a connection to a BW (the old BW dev). If we take this option, the old connection is deleted and a new one is defined. However, from the R/3 perspective we want two BWs connected. It seems the problem has to do with the IDOCs and TRFC port definitions, because the IDOC type ZRSBW010 seems to point to the wrong system.
Unfortunately, we are stuck at the moment.
Any kind of help or hints to relevant SAP documents would be much appreciated.
In the OSS we found some notes on this topic (325525 etc.) but we still not sure how to proceed.
However, in general, we think it shouldn't be a problem to have one R/3 connected to several BW's or is it?
Frank Schülke, E.ON Ruhrgas IT, Germany

We worked out this scenario. Our solution came with an interpretaion of SAP documentation including SAP Note 886102, obsolete (but informative) SAP Note 184754, and the document How to... System Copy in SAP Business Intelligence System Landscapes - May 2005.
Basically the steps are...
-Using the BW transport collector in the source BW system, collect, release, and export all objects related to the R/3 source system.
-Perform the system copy of the source BW system to the target BW system.
-Change SM59 destinations in the target BW system to the R/3 source systems to invalid hostnames.
-Delete the R/3 source system definitions from the target BW system (the nonsensical hostnames in SM59 ensure you will not make any changes in the actual R/3 source systems).
-Use BDLS to change the logical system in your target BW system.
-Recreate the R/3 source system definitions in the target BW system, this step will make corresponding config for the target BW system in the R/3 source system. It is important here to activate and replicate.
-Ensure that table RSLOGSYSMAP has the correct entries for your R/3 source systems
-Import the objects you collected in the first step into your target BW system.

How to delete source system in BI system

Dear Experts ,
recently we finished client copy in BI production system to quality system,
now we are facing problem with source system connections in bI system
in RSA1 APO production system's source system is comes to BI quality system now i need to delete that APO source system in BI quality system ..please let me the process how can i delete source in BI quality
can i delete it as below
log in into BI quality system --> RSA1 --> select source system which i need to deletse --> right click & delete
or we have any other process to delete it.
Regards

Hi Swathimatta,
Apart from the two ways to delete the source system:
1.- log in into BI quality system --> RSA1 --> select source system which i need to deletse --> right click & delete
2.- Execcuting the FM 'RSAP_BIW_DISCONNECT.
If you cannot delete the source system:
Use fuction module RSAR_LOGICAL_SYSTEM_DELETE to delete
the source system:
1 - Go to SE37.
2 - Run fuction module RSAR_LOGICAL_SYSTEM_DELETE.
3 - Fill with the parameters as mentioned below:
      I_LOGSYS          = FUENTE
      I_FORCE_DELETE    = X
      I_NO_TRANSPORT    =
      I_NO_AUTHORITY    =
Or follow the recommendations from note 140276, Solution 2:
"You cannot delete the source system. Two cases have to be distinguished:
    o The source system still exists.
       Switch to Transaction SM59. Find the destination which has the
       same name as the logical system of the source system from field
       SLOGSYS in table RSBASIDOC (see above).
       - Such a destination does not exist in Transaction SM59. In this
          case, you have to create the destination to the source system.
          Name the destination equal the entry in SLOGSYS from above.
          Then return to the Administrator Workbench and repeat the
          deletion.
       - The entry exists but a remote login is not possible. Correct
          the communication parameters.
       - Everything works. Change to Transaction SE37, function module
          RSAR_LOGICAL_SYSTEM_DELETE, Sngl. test. Parameter I_LOGSYS =
          <log. name of the source system>, I_FORCE_DELETE = 'X'.
    o The source system no longer exists or was replaced with another
       source system with the same IP address.
       Proceed as described in the first case but make sure, that the
       field 'Target host' contains a not existing server in the
       maintenance screen of the destination (Transaction SM59). If
       necessary, change an existing entry. Later when you delete, the
       system asks you whether you want to delete, although the source
       system is not available. Select 'Ignore'. "
I hope it can help you.
Regards,
Fran.

How to replace a source system with another in BW

Hello experts,
I've read many topics dealing with my customer's need, but I still can't find the solution.
My landscape is the following one :
ECC6 with DEV, QUAL and PROD
BW with DEV and PROD
BW DEV source system is ECC6 DEV, I need to change it to ECC6 QUAL
A lot of work has already been done, and I'd like not to lose it changing the source system.
Datasources are the same in ECC6 DEV and QUAL.
This is not a system or a client copy, it is really a source system switch.
The new source system is already created (both DEV and QUAL ECC6 are available in "source systems" in RSA1), and I tried to use BDLS tcode
In the "old logical system name" I choose my current source system and in "new logical system name" I choose the one I now need to use.
System answer is : "The logical system name ECC6 QUAL already exists"
Obviously I did something wrong, but can't figure what.
Is there any action to perform before BDLS ?
Any help is appreciated, and points will be given.
Guillaume P.

Thanks for your answer,
"relevant object" means for you datasources, transfer rules and transformations ?
With the grouping option "Save for system copy" I can't take easily all datasources, and others objects
Will I have to pick all object one by one ?
What would be the adjustement in table RSLOGSYSMAP ? For the moment it's empty.
Regards
Guillaume P.

Change the source system

Hello
In our Quality Box , I need to change the source system connection (from QR1 to QR2). I created the new connection successfully. Now the issue is all the Transfer structure still using OLD connection ( i.e QR1) . I run BDLS and it did not word. How can I re-assign the new source system (QR1) to all of my Transfer structures in one go. Is there any report ?
Farooq

Hello,
You cant directly convert the existing objects for a source system to the new source system.
For that you need to do a transport of the objects to the QA box while maintaining the entry in BDLS to convert to the new source system.
Regards,
Shashank

Not able to change source system connection

Hi, I have problems changing a source system connection from BW. BW is already connected to source system A, which is closed down, and I'd like to connect BW to source system B, which excists and can be accessed. I have tried to use BDLS, but get the message that System B already excists (new one). I try to delete it (Change view logical System), but am not allowed to do this. I get the message "must not be deleted, first delete from distribution model." And thats where I am stuck. Can anyone guide me on my way?
Regards E!

Comment to the last answer:
When I try to delete in SALE I am told that the source system also excists in the Distribution Model (CUA) and can therefore not be deleted. It must be deleted in the distribution model first. I find CUA at BD64. Looks like this is the connection to Solution Manager. What are the consequences for deleting the Source System here? And will it hlep me to solve my problem, which is that I can't change my connection from Source System A to new Source System B?
Regards E

New Document Address Number

Hi All-
We are on SRM 5.0, SP6 Ext classic scenario. Every time we create a Shopping cart with an existing Ship to Address number, the system generates a new document address number in SRM even though the address number and the address already exist in SRM.
I am not sure if this happens standard in SRM 5.0 or is it due to some custom development on our system. I am aware that this was an old Issue and there were OSS notes related to it:
Note 570543 - Creation of document addresses
Note 718206 - Copy template: New address number for delivery address
Can somebody confirm if they are seeing the same behaviour on their SRM 5.0 system? If yes, i can go ahead and create an OSS message and keep you guys updated.
Thanks,
Sundeep

Hi Sundeep,
We are using SRM 5.0 , SP7 and it is not creating new address number whenever we create new shopping cart.
But it is creating new address numbers whenever some changes were made to the business partners.
Rgds,
Teja

Source system server migration (new ip address)

Similar Messages

Maybe you are looking for