Logical system names after system copy for SAP ECC 6.0

Hi!
We successfully installed SAP ECC 6.0 system as system copy.
All the logical system names of old system have been copied to new system.
Question
What is the approach to change the logical system names for new SAP system?
a) just via tcode SCC4
b) via BDLS
c) other tcodes, reports
Thank you very much!
regards
Jürgen

I think you can do it through BDLS

Similar Messages

Logical System Name after System Copy

Hello,
I have three questions about the logical system name after system copy.
Q1) When I change SID D22 to S11 during system copy,
do I have to change the logical system name of all clients in the target system? The target system is used for test, and the landscape has S11 and Virtial system. The target system S11 does not communicate with the source system D22.
Q2) If the answer for Q1 is YES, is it correct that the following procedure for changing logical system name?
1.Tr-CD:BD54
Add new logical system name for all clients in the target system.
2.Tr-CD:SCC4
As for all clients, select new logical system name with F4 help.
Q3) If the answer for Q1 is YES, do I have to add new RFC connection entries with SM59 for all clients in the target system?
I refer to the guide "Homogeneous and Heterogeneous
System Copy for SAP Systems Based
on SAP Web Application Server
ABAP 6.40 SR1".
thanks,
Keishi

Hi Keishi,
As a good and ideal practice the answer to your first question Q1 is yes. Infact I would say that in case you are using ALE then it is must
For Q2 there has to be an additional step which is most important one. Running BDLS transaction which would allow you to change logical systems in relevant tables from the one of source system to target system.
For Q3 the answer is agaain yes and you can have two approaches>
1. manually recreate all the RFC destinations after sys. copy.
2. Export all the RFC destination data relevant tables before system copy and then reimport them after sys. copy.
Regards.
Ruchit.

Logical system names after system copy

Hi!
I installed a new SAP system via System Copy (SAPINST) approach.
As a consequence the old logical system names have been copied.
Question:
What is the appropriate approach (tcode, report) to change the logical system names of each clients of SAP system?
Thank you very much!
regards
Jürgen

Logical System Names
When data is distributed between different systems, each system within a network has to be clearly identifiable. The u201Clogical systemu201D deals with this issue.
A logical system is an application system in which the applications work together on a common data basis. In SAP terms, the logical system is a client.
Since the logical system name is used to identify a system uniquely within the network, two systems cannot have the same name if they are connected to each other as BW systems or as source systems, or if there are plans to connect them in any way.
Although SAP does not recommend that you connect test systems to production systems, a test system can have the same name as a production system. This makes copying production systems to test systems a lot simpler.
You are only allowed to change the logical system name of a system if the system is not connected to any other systems, because changing the logical system name would render all the connections to other systems useless.
In BW, you make the settings for the logical system names in the BW Customizing Implementation Guide under Business Information Warehouse ® Connections to other Systems ® General Connection Settings. In the source system, you make the settings for the logical system in the Implementation Guide under Cross Application Components ® Distribution (ALE) ® Basic Settings.
Note SR047 lists names that cannot be given to BW systems, because they are reserved for internal use.
Logical system names must contain capital letters and numbers only. SAP recommends the following naming convention for logical system names: .

Change logical system names after system copy

Hi!
We successfully installed SAP ECC 6.0 system as system copy.
All the logical system names of old system have been copied to new system.
Question
What is the approach to change the logical system names for new SAP system?
a) just via tcode SCC4
b) via BDLS
c) other tcodes, reports
Thank you very much!
regards
Jürgen

Hi,
Go though the system copy guide.
http://service.sap.com/instguides
After system copy,
If you need to change logical system names in the system that results from the copy, change the logical system names as described in SAP Notes 103228 and 544509.
https://service.sap.com/sap/support/notes/103228
https://service.sap.com/sap/support/notes/544509
Before running BDLS to change the logical system name, you have to define the correct logical system name in the new copied system. in tcode BD54.
- while running BDLS, execute in background.
Regards,
Debasis.

Incorrect Source System name after System Copy

Hello Friends,
When we copied Source system from Production to our Qulaity system, the DTP s are still displaying Production Source system.
We are in BI7.0 SP13 . I have run TC BDLS to convert Old Source system to new Source system.
But still displaying Old source system .
Please help me with this Issue .
Any advice appreciated .
Thanks

Hi,
Take a look at OSS notes below.
o 184447 Building a BW-system landscape
o 121163 BDLS: Converting logical system names
o 369758 BDLS: New functions and better performance
o 524554 Storing destinations in the BW environment
o 325470 Activities after client copy in BW source systems
o 538052 Maintenance of Myself destination in BW
o 305527 Details for correct BW Source System Connection
o 325525 Copying and renaming systems in a BW environment
o 184971 Notes on BW source system connections
o 184754 Procedure after BW database copy
o 305527 Details for correct BW Source System Connection
o 547314 FAQ: System Copy procedure
o 140276 Error in source system assignment
Regards.

BI:Logical system name has been changed for This System

Hi, Gurus,
I want to Use my IDES SAP ERP 7.0 as my BI system for training purposes,when iam executing the transaction RSA1 in the system it is giving message
"Logical system name has been changed for
system"
I Have changed the entries in table "RSADMINA" and maintained the Client no as 100 (My base client for BI) which i have copied from 001.
When iam executing the Transaction RSA1 in 100 it is giving above mentioned error ,whereas in 001 it is working fine.
Please Help . ..
I tried to change the system logical name by "bdls" but it doesnt worked........

Hi Deepak,
Check the entries in table RSLOGSYSMAP (this is meant for correct conversion of logical system names for tansports).
You can easily maintain the entries using tcode RSLGMP.
Hope it helps.
Grtx
Marco
PS I'm not a basis guy but do you have a correct BI installation yet?

BI Error Logical system name has been changed for this system

Hello All,
I have installed the BI system and did a client copy from 000 to 200 client with profile SAP_ALL.
Now I have loged into the system with client 200 and wen I run RSA1, I am getting the following error
message: "Logical system name has been changed for this system"
Thanks
Sekhar..

Hi,
Goto tcode SCC4.
Switch to change mode. (System will prompt that this table is cross client. Continue)
Select your client (in this case 200). Click on details button (next to change mode button)
Enter the proper logical system name in Logical system field.
Click on Save button.
Then try RSA1.
Hope it helps
regards,
Pruthvi R

RSA1 error Logical system name has been changed for this system

Hello All,
Earlier the RSA1 was activated for client 300 on our crm 5.2. after that we changed the client to 500 using SE16 -> Type table RSADMINA / Check Colum BWMANDT -> 500.
But now when we login to client 500 and execute RSA1 it is showing
Logical system name has been changed for this system"
In scc4 we have not made any changes. Can you tell what should be done ? in the pop up it is showing following steps
Change the name of the logical system (table T000) for client back to SIDCLNT300. 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 SIDCLNT300,
delete all existing connections between this system and other systems,
delete all transfer structures that still exist, and
do not use ALE or Workflow.
Guys do you know how to fix this ? .
Also do you know Assignment of Source System to Source System ID (table RSSOURSYSTEM) using RSA1 ?
Edited by: Sahad K on Mar 17, 2008 10:55 AM

Hello Hari,
Both the options you said cannot be used
since the logical system SIDCLNT300 is used by client 300 and it cannot be given to client 500. Also there already exist a logical system SIDCLNT500 which is assigned to client 500.
I found out the issue. In the table RSBASIDOC the logical system name that can use rsa1( bw client )is set as SIDCLNT300). Only if we delete that entry and set it to SIDCLNT500 ( 500) we can use it on client 500.
The solution is specified in /message/3284842#3284842 [original link is broken]
Let me try the solution 2 and inform you.
Solution 2:
You cannot delete the source system. Two cases have to be distinguished:
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'.
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'.
Incase you have any idea other than this please let me know how to edit the RSBASIDOC table and change the entry to client 500.
Edited by: Sahad K on Mar 18, 2008 5:07 AM

Logical System Conversion after system refresh failed

Hello,
Logical System Conversion after system refresh couldn't complete as the printer was locked. This job was run in the background. In SM37, the job log of RBDLSMAP shows as job finished, but it took only 40 seconds. Now I see that the logical system got changed(Converted) in the client settings scc4 but I know that this client being a production client and would run for couple of hours. Here is the job log information.
02/18/2009 16:09:33 Job started                                                                     00           516          S
02/18/2009 16:09:33 Step 001 started (program RBDLSMAP, variant &0000000000000, user ID ABCD)      00           550          S
02/18/2009 16:09:33 Output device PRN1 is locked in the SAP system                                  PO           349          I
02/18/2009 16:10:19 Job finished                                                                    00           517          S
When try to rerun bdls again, it shows that it is already available and it says "The new logical system name is already assigned to the current client".
Any suggestions on this?
Thanks,
Mahesh

Hi ,
Rerun the BDLS again as this took very little time.
When you try to run again it popsup message saying it already exists just delete that and again put the Logical system name and run it will run that time.
May be while scheduling the job you gave for spool I am not sure why is it looking for Printer which is locked.
Thanks.

Conversion of source system names after transport

Hi gurus,
Please someone can tell me how to configure the "conversion of source system names after transport" in the BI system as my transport is not working on a new BI System ?
Thx in advance

Hi Firmin,
You can do this in RSA1 in tools under conversion of logical source system names.
Here you maintain the development system or the system used for development as the source system.
You will have to mention the logical name of the development system.
In the target system column mention the system in which the transports would be imported. This could be the quality system or the production system.Again you would have to mention the logical system name
Check the folllowing link for more informationn on this.
[Conversion of logical names|http://help.sap.com/saphelp_nw70/helpdata/en/46/94b1fc87bd13eae10000000a155369/content.htm]
Hope it helps you ,
Best regards,
Sunmit.

"Conversion of Source System names after the transport" : O

Experts:
Environment : BI 7.0 and SP 12
<b>Tranports related to transformation rules are failing with inactive status...</b>
Further investigation on this, I have noticed that in our QA system, where "Conversion of Source System names after the transport" : O screen, we have columns
Original Source System, Target Source System, 7.0, Description(I guess, since no name is found)
Everything looks fine to me with reference to actual techinical names of source/target system...
My question there is a check box on column "7.0", which is UNCHECKED. Is this correct?
My understanding is that, this check box needs to be CHECKED, since this is related " Only Valid for RSDS, TRFN and DTPA Objects ". Is this correct?
If yes, Can I check this box in QA system, save and retransport my requests. If so, what happens to standard BW objects i.e., transfer ruels, update rules etc...
OR do i need to create another entry with same source/target system and check the 7.0 box.
OR do i need to create 3 entries with same source/target system and check 7.0 box for each entry i.e., RSDS, TRFN, DTPA.
Finally, please advise the exact steps that need to be taken here...pros and cons
Your inputs will be of great help....
Thanks,
BI
Message was edited by:
B I

Hi,
Yes you need to check the checkbox as it is related to Data sources and transformation and DTPs. you can mark the check box if your client is modifiable, if not you need to transport the setting from DEV. Go to
SPRO > Business Intelligence>Transport Settings--> Change Source system name after transport.
you also need to maintain the Source system IDs .
Hope it helps.

File system for SAP ECC, EP , BI and CRM installation on Solaris/DB2

Hello,
We are going to implement SAP ECC 6.0 with EP 7, BI and CRM on Solaris operating system with IBM DB2 database.
All these applications are going to be installed on single server, as being a basis person, I know this is not all recommended.
But due to client's requirement and keeping cost factor in mind I need to install all these application on single box.
Now here I need your help. as I basis person, I know the required Solaris file system for SAP ECC 6.0 but not having any Idea about other application like EP/ CRM and BI .
If anyone able to help me with required Solaris file system. it will be great help.
Please let me know if there is any query.
Thanks.

> All these applications are going to be installed on single server, as being a basis person, I know this is not all recommended.
> But due to client's requirement and keeping cost factor in mind I need to install all these application on single box.
Why not using Solaris zones/container? This decreases the administrative amount tremendeously since you will deal as with "single machines" but they all run together on one box.
> Now here I need your help. as I basis person, I know the required Solaris file system for SAP ECC 6.0 but not having any Idea about other application like EP/ CRM and BI .
So you'd need to read the installation guides
Markus

Source System Problem after system refresh in RSA1 trx

Hi,
We have R/3 4.7 Test source system created in our SCM 2007 Test System. The source system check was OK.
The R3 Test system was refreshed with Production data few days back and now my source system is not working. When i perform Source System check it says:
BI unknown in source system
BI IDoc type ZSSB006 is not the same as source system IDoc type
I performed following steps in R3 Test system after its system refresh:
1. Created logcal system and created RFC.
2. Created port in trx we21.
3. Created partner profile in trx we20.
4. For the outbound parameter RSSEND, I had to create idoc type that should be same as in my SCM system i.e. ZSSB006.
5. Created idoc type using trx we30 as a copy of RSSEND and added entry in table EDIMSG. Now, i could also create outbound parameter RSSEND with idoc type ZSSB006.
After performing the above steps i also replicated the datasources for the R3 Test source system, but its still showing above error.
I also checked the RSBASIDOC table in SCM test system. It has correct entry for my source system. But there is no such entry in RSBASIDOC table in the R3 test system.
Someone pls help me.
Regards,
Chintan

Hi
Need to restore the All Dalaload connection settings after refresh the system which either R/3 or SCM.
RSA1 -> select the Source system -> Right click -> Restore , It'll ask the connecon paramters like RFC , method of activations. Then check the connection test of the Source system .
Check the the note for further info...
Note 886102 - System Landscape Copy for SAP BW and NW BI
Hope halp you...
Regards,
Sureshram

Disaster Recovery For SAP ECC 6.0 On Oracle

Hi All,
This is our infrastructure
Windows 2003 Server
SAP ECC 6.0
Oracle 10
Legato Networker Client / Library
Actually our Backup Strategy is to do an Online Backup Every Night from monday to saturday. We want to test our backup by doing a Restore. We are assuming a complete loss of the system including hardware.
What we do:
1. Install the SAP System on a new host with the same hardware characteristic of the source system.
2. Install & Configure the legato utility.
3. Copy the E:\oracle\MIS\sapbackup\ directory from the source system to the test system.
4. Them we put the database in mount mode.
5. Execute the command: brrestore -b bdyxwoqv.fnf -m full (bdyxwoqv.fnf-> Full Online Backup that was executed without problems).
It gives the following errors:
BR0386E File 'F:\ORACLE\MIS\SAPDATA2\SR3_10\SR3.DATA10' reported as not found by
backup utility
BR0386E File 'F:\ORACLE\MIS\SAPDATA3\SR3700_9\SR3700.DATA9' reported as not foun
d by backup utility
BR0280I BRRESTORE time stamp: 2008-10-01 17.45.19
BR0279E Return code from 'backint -u MIS -f restore -i E:\oracle\MIS\sapbackup\.
rdyybrzp.lst -t file -p E:\oracle\MIS\102\database\initMIS.utl': 2
BR0374E 0 of 63 files restored by backup utility
BR0280I BRRESTORE time stamp: 2008-10-01 17.45.19
BR0231E Backup utility call failed
BR0406I End of file restore: rdyybrzp.rsb 2008-10-01 17.45.19
BR0280I BRRESTORE time stamp: 2008-10-01 17.45.19
BR0404I BRRESTORE terminated with errors
Since this is a new SAP system it never will find the SAPDATA files because they where on the source system and this is a new test system.
We found the following note:
96848 Disaster recovery for SAP R/3 on Oracle
But this note is for SAP R/3 no for SAP ECC!
It explain that you have to install your SAP system with the System Copy Method (is this the only way??).
2.) Installation of the R/3 System
The installation of SAP software contains the software installation of the database. The initial SAP database should be created again but the SAP data should not be loaded.
Install the SAP system with the Oracle-specific system copy method, which is based on backup/restore. This method is described in the system copy guide for your Product/Release. Refer to Note 659509 for products that are based on Web AS.
3.) Modification of the installation
Above all, you must take into account the mounted file systems at the time of the loss. If necessary create new SAPDATA directories (mount points). These generally identify a disk or a logical storage area (logical volume).
Are we working in the right way? maybe there is a formal procedure to do a Restore from an Online backup when you complete loss your system.
Please some tips.
Best Regards,
Erick Ilarraza

Hi Eric,
Thanks a lot for your reply, I will follow the Note 96848 Disaster recovery for SAP R/3 on ORACLE point 5.
5.) Restore profile and log files, as you sayed in case of disaster we will lost our "source" system.
On the other hand to configure the legato client we take care of the name of the server, we configured the .sap, .cfg and .utl files so in theory the restore will be done on the new test system since we run the brrestore command from that system.
Officially there is not a documentation from SAP to do a Restore from a Online Backup with SAP ECC, SAP Netweaver (ABAP / ABAP + Java). You only have the 96848 note??? I found the following information:
http://help.sap.com/saphelp_nw70/helpdata/en/65/cade3bd0c8545ee10000000a114084/frameset.htm
But there is not a official procedure like a System Copy Guide or Installation Guide.
Best Regards,
Erick Ilarraza

Sql Server configuration requirements for SAP ECC 6.0

Dear All,
I am using Sql server 2005 Enterprise as data store for Sap ecc 6.0.There are certain configuration requirements to be done while installing it so that sapinst.exe (sap installer) is able to use it to create its own DB's.
For eg it requires a collation of SQL_Latin1_General_CP850_BIN2 whereas the default that gets installed is SQL_Latin1_General_CP1_CI_AS.
Like this there are other requirements which I am not aware of.Most of the docs available on the Internet are talking of ecc 6.0 with Oracle 10.2G which is the most common combination.I am having docs for this combination.
I am installing ecc for the first time.
*I am unable to download docs from sap. marketplace as it requires a login given to certified users or sap purchasers.I am neither.*
Can anyone help me with this.If anyone has ECC 6.0 installation guide with sql server it will be serve my purpose.
Thanks for your efforts.

"Excuse me?
What he is doing is illegal , you know what that means, right? If you don't believe me, read the license that comes on the first installation DVD.
Actually, I even think it's kind of barefaced to ask in the forum of the software vendor for help! I mean, it's like asking in a bank forum how to rob and fraud the bank! You - and many others - may think that it's right and ok to do that. I tell you: it is not. Not for "home use", not for personal use, not at all.
You can use the software available here in the SDN to lean and study, that's why it's there.
If you deal at all with copied software, then just be smart enough to make other people not notice. He can be happy if he's not prosecuted (which would legally be possible)."
Do u understand what is legal or illegal? Have u read the license in full?
The license does not put any limit on the number of users.So if I am using it means that one more user has been added by the license holder.
Therefore there is nothing illegal about it.
It would have unethical (not illegal) if the software is being used for a business purpose other than for which it has been purchased.
Since it being used for training purpose the above does not hold good.
In fact it is SAP who is benefited in the long run bec' after a person learns it technology because he is going to implement it somewhere, for which the concerned user will have to purchase a license.Therefore I am helping SAP to increase its business.
But there are some stupid people who don't understand these things but are ready to shout at the top of their voice thinking themselves to be intelligent.
Edited by: coolmind26 on Jun 5, 2011 10:57 AM

Logical system names after system copy for SAP ECC 6.0

Similar Messages

Maybe you are looking for