About assigning logical system name to client

Hi:
    the SAP landscape is:
    CRM DEV CR0 (CLIENT 200)        -
>    CRM PRD CR1 (CLIENT 800)
                  \|/                                                                        \|/
      ERP DEV MZ0 (CLIENT 200)      -
>   ERP PRD MZ1 (CLIENT 800)
   the crm dev is connected the erp dev and the crm prd is connected the erp prd.
   the CRM version is CRM2007 and the ERP version is ECC 6.
    My question is :
   Can the logical system name of the prd client 800 be same with the dev 200?
   Could you give me any advice?
THANKS.
Edited by: Xiaofeng Qiu on Jun 5, 2009 11:27 AM

Hi,
The logical system must be unique company-wide. In a production system, the logical system must not be changed.
Goto SCC4-->Double click on any client number. You will see logical system text. Select it & press f1 you will below information about logical system.
"The distribution of data between systems requires that each system in the network has a unique identification. The logical system is used for this purpose.
In the SAP System the client corresponds to a logical system.
When you maintain the logical system, note the following:
The logical system must be unique company-wide. It must not be used by any other system in the ALE integrated group. In a production system, the logical system must not be changed."
Thanks
Sushil

Similar Messages

How to Assign Logical System to a Client in SALE Transaction

Hi ABAP/EDI Specialists,
1How to Assign Logical System to a Client. In the SALE transaction window.
I didn't see any Receiving and Sending Systems(Tree). But I can see Logical Systems. In the Definition and Assign Subtree are there. I created two Logical Systems STUD_S and STUD_R. When I executed Assign Logical Systems. I got a window, Where I can see a list of Clients. I got confused, how to Assign those Two Logical Systems to Client 800 and 810. Finally I double Clicked on each client and in the next window. I changed the Logical System to STUD_S for Client 800 and Logical System STUD_R for client 810. and saved them.
Is this procedure correct???
Why I need this is, While generating partner profiles in ALE Model (BD64), I am getting no list at all. When I executed I got no list.
"No messages have been defined for the selection conditions in the Model"
I got struck at this point.
Please help me to come out of it.
Thanks,
Chinna

Hi Chinna,
Thanks for such a valuable information. I am able to move further. But i got struck while generating parntner profiles from ALE distribution model.
Log For Partner Profile Generation:
Partner:
Partner ZVK_SS_800 as partner has been Created ( Sending System)
Partner ZVK_SS_820 as partner has been Created (Receiving System)
Port:
Port Cloud not be Created
RFC destination ZVK_SS_820 not specified for system ZVK_SS_820
Enter the RFC destination and Restart the generation
It is not recognizing the RFC port, even though i followed all the steps correctly.
While creating RFC destination, can someone tell me How to fix the above error and what is the Client No, Username and Pasword i have to give.
Thanks
Chinna
Edited by: Chinna on Jun 6, 2008 7:43 PM

Assigning logical system to a client in CUA

Hi All,
I have got a doubt in the basic configuration in the setup of CUA.
I have performed all the steps that is given in the CUA cook book.
In, assiging the logical system to a client, whether this step shoud be done only in the central system alone.
Or the assignment should be done in the child system also.
When i created the all the steps in central system, logical system is created automatically in child system. but in the client assignment i didn't find information. in cookbook also they have do it in all the SAP system.
kindly advice.
Thanks and Regards,
Subhashini.

>
> So creating clients in Central system is enough for the child system.
The term you used "Creating Client" is technically wrong in this regard. You already have a client which is in use as Central system - right? You need to maintain the details of Logical system names of all the Child system in Central system to keep the central system updated with the knowledge of type and name of the Child systems it has. This definition can be done by using TCode BD54 which is table maintenance view ( V_TBDLS ) of the table TBDLS.
There is nothing to do or even can be done like Creating Client within a client (here your central system).
> Since there is noe transfer of user master from child to central system no need to create a client for the logical system.
>
Its true that there will no transfer of user master from child to central system. But of course the similarly here you are not creating any client within the child system. You are just creating the logical system name (tcode BD54) for this client (child system) and mapping it with the client in tcode SCC4.
Let us know your question. Also as suggested by Barnherd, please go through the SAP Help documentation on CUA. Also try to get an overview of Client in SAP (from SAP Help or SAP course ADM100) and Logical Systems.
Regards,
Dipanjan

Logical system name

Hi,
I have done the system copy from production system to quality system yesterday.After that i am unable to change the logical system name in Quality syste in scc4.The logical system field disabled.Why?
Regards,
Mani

Hi,
What we do after system copy is run BDLS in target system & this changes logical system name.
Check below link for more details
Re: about assigning logical system name to client
Thanks
Sushil

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.

Regarding problem while assigning logical system

Hi Friends,
I had a problem while assigning logical system to the client where in both of my systems are having same client number which belong to 2 different systems.
while assigning the sender and receiver logical system to the same client i am facing problem stating that an entry has already been made for the same key.
could any one plz give me a clear idea...while assigning logical systems (cross clients) for 2 different systems having same client number.
Regards,
Madhu

Hello Madhusree,
I'm running with same problem. I've created two logical systems and assigned them to two different clients. But here pops up the issue while generating partner profiles, throwing error "No active plan version exists". Later when I researched about the issue, I came to know that T77S0 table doesn't have any entries regarding plan versions. Basically, I created two clients by doing "client copy" from source client (800 & 100). And I could see plan version entries in the T77S0 of client 800. So, I thought of assigning just defined logical system to the source client 800 itself. But it throws error saying "entry already exists"; as client (800) is already assigned with other logical system.
By coming across your post, gives me leap of hope that two logical systems can be assigned to same client. Could you please share me those troubleshooting steps concerning this issue. Points will be awarded.
Regards, Anil.

Assign a Logical System Name of a production client

Hi everybody,
We have an ERP system (now upgraded to ECC 6.0) that is in productive use since 7 years. Until now, no Logical System Name have been assigned to the production client - the field in transaction SCC4 is empty/blank.
Now we plan to implement a BW, so a test and a productive BW systems have been installed. According to the attached file and content of note 184447 we choose to use "Option 1: Uniform Logical System names clients by system type" for naming convention for LSN's.
All the systems/clients (BW test and productive, ERP test only) now are assigned with corresponding LSN's, except the production ERP client. It is still without LSN and the client is not defined as Source System for productive BW system.
So, my question is:
Should I expect any problems if the LSN of the production client is set up now, after long time, effective productive use?
I would mention that this is infact initial setup, not a change of LSN. Therefore transaction BDLS is not relevant, I think.
Thanks in advance

Hi DB49,
I already did an initial setup of LSN in the test ERP client (that client is copy of the productive ERP client, i.e. the LSN has not been set). And everything seems to be OK.
But the documentation says that ".... In a production system, the logical system must not be changed ...".
"Changed" is not "ïnitial setup" of course, so there will not be any problems I hope, but ...
SCC4 --> LSN field --> F1 -->
"System in which applications run integrated on a shared data basis.
The distribution of data between systems requires that each system in the network has a unique identification. The logical system is used for this purpose.
In the SAP System the client corresponds to a logical system. You can assign a logical system to a client in the client maintenance (choose Goto -> Detail).
The logical system is relevant in the following SAP areas:
ALE general: two or more logical systems communicate with one another.
ALE - ALE business processes (for example, cost center accounting): definition of a system where a specific application runs. Changes to master data can only be made in this system, for example.
Workflow objects: the logical system in which the object is located is always included in an object's key.
When maintaining the logical system, note the following:
The logical system must be unique company-wide. It must not be used by any other system in the ALE integrated group. In a production system, the logical system must not be changed. If the logical system of a document reference is not set to initial and does not match your own, the system assumes the document is located in a different system."

Logical system name to be updated while client copy--URGENT HELP REQUIRED

Hello All,
I have a query regarding the "Logical System name" updation during Client copy.
When we make a client copy(SRM Masters) for the Production system(SRM),the Old Logical system name for backend(which is attached to the SRM masters) gets copied to the new Client (Copy) which needs to be updated.
There is a std transaction BDLS through whcih w e can change the current Logical system name to a new one but this seems to work fine for System copy but not for Client copy.
So when i make a client copy of SRM masters for Production system,is there any other std way wherein i can change the "Logical system name " for the backend or do i have to write a CUSTOM program wherein entries for the Backend Logical system name in tables like CRMMLSGUID will be updated with the new Logical system name?
Any help on this is appreciated.
Thanks & Regards,
Disha.

Disha,
Yes, I did it twice and it worked fine.
The R/3 GUID is sent by the OLTP system (R/3) in R/3 message header.
SRM checks this GUID in CRMMLSGUID table.
If is not the same one, then replication process fails.
The only solution I found was to delete this entry. It is automatically recreated with the new GUID with the next replication, with FM CRMT_OLTP_LOGSYS1, called in BAPI_CRM_SAVE.
Look at OSS note 588701 & 765018 for deletion of CRMMLSGUID.
The issue is exactly ours: around system/client copy.
In an CRM environment, this is more critical, because we make a huge use of the middleware. But in our case, and especially after system/client copies, we can go, even if SAP does not guaranty anything, because we don't care about "old" replicated data (I don't care about old BDOCs, that should even be deleted after processing).
We have to take some risks sometimes...
Rgds
Christophe

Assign logical system to client

I understand that we assingn a logical system to a client in tcode SALE.
However my Q is if say i have one receiver system YXD/800 and another receiver system RXD/800 ....
when i try to assign client 800 to these 2 receiver systems it allows me to enter only one receiver system..
Cannot I assign same client ( say 800 ) to two different receiver systems

hi ,
according to my understand about your post,
you transfer the data across the three users of 800 client.
you have to create three logical systems for three clients.
then you can maintain RFC destination across two systems by using SALE.
Regards,
karunakar

Re: Assign Logical System to Client

Hi Guys,
Currently our BI client 100 is connected to ECC client 140. Now I want to connect BI client 100 to e-recruiting client 180.
How to do this? How to assign same client to different logical systems?
Regards,
Anand

first i created logical sytem for erecruiting.
for BI the logical system already defined as it is already conected to SAP ecc.
Second step using tcode SCC4, now how to assign the logical system of e recruiting to BI client 100.
Already BI client 100 is assigned to SAP ecc logical system.
Its not allowing me to define another logical system for same client.
Am i doing the right step?
Regards,
Anand.

Assign Logical System to client 000

I need to install Bw at SAP ECC 6.0, in doing so on the client 000 with the transaction RSA1, present the message that should be assigned System logical customer 000, it does not bring inconvenience to any future activity,
Thanks

Hi Victor,
If you're installing BW you shouldn't use cleint 000, create a new client...
Once you create the client go to transaction SALE and You'll see Create logical system ans assign logical system in the list.
First create a new logical system for the client to use... then assign the logical system to the client.
Regards
Juan
Please reward with points if helpful

Logical system name has not been assigned to

Hi, Expert
I m trying to transferr DATA from ECC to APO . when I configured my ECC and APO systems according the SCM 210, but I still meet the error like this
logical system name has not been assigned to
syste: user:
Function/Q/SAPAPO/CIF_PRODUCT_INBOUND
text: logical system name has not been assigned to
my ECC is ECC6.0,and APO 7.0
Can u help me,Thank u. I m waiting the solution on desk
Rockey
Edited by: Xinyou Dong on Jun 2, 2011 9:11 AM

Hi,
I think you dont have partner profile created.
Try to create one with the RFC which is connecting ECC and APO.
Thanks,
Deepthi

Logical System and Logical System Name

Hi,
I would like to create the following and please tell me how do I go about doing this. I am doing this because I am trying to implement both RFC/Idoc to File and File to Idoc/RFC. The basis admin guys are unavailble at the moment so I am on my own at this moment.
Creating a port(I suppose I need to do this on the R3. What are the steps involved)
Create a Partner Profile

Hi Sonia,
For XI communicating with SAP R/3 through Idocs ALE settings need to be done,
just go through the following steps and Configure ALE :-
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2) a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.
Regards,
Ashwin M
Reward If helpful

Logical system name in business system (SLD)

Hi,
While creating business system in SLD what should give for the logical system name?
Should the logical system name exists in ABAP stack or the new one?
Thanks.

Hi,
If you are creating the BS for SAP R/3 in SLD means we have to give the LS name which we had in SAP R/3( goto SALE and take the LS from there)
Goto Assign LS-----take the client which you are using for SAP R/3 and take the LS name assigned to that Client
Regards
Seshagiri

System alias does not work if not the same as logical system name?

In most of the situations, we define the portal system alias same as the connected R/3 client logical system name.
I also saw some exceptions that system aliases were defined differently from the connected R/3 client logical systems, and they were tested fine.
However I forget the way to make that working.
Could you help me recall how is that achieved?
Thanks!

Hi,
There is nothing tricky here. Just assign more System Aliases to the system connector !

About assigning logical system name to client

Similar Messages

Maybe you are looking for