SLD - Logical System Management

Hi,
We are implementing XI and we have the problem with SLD logical system management. The problem is that we use the same Logical system name (Ex. PRDclnt350) for all the systems to avoid running lengthy BDLS process when we hook our R3 systems to their respective BW systems.
Can you please suggest how we take care of this in XI -SLD landscape as it requires unique logical system names for each Business System when maintaining in SLD.
Can we have multiple SLDs and will it take care of the issue. If so can we take one of them as the master SLD and the rest as slave SLDs. What would be the best practices for synchronizing them. Any help in this regard is greatly appreciated.
Thanks and regards..
Haritha

Hi All,
We opened an OSS note with SAP regarding this. Please see the question we asked and the response we got from them regarding the SLD maintenance:
Hi,
We are on BW 3.5 and SAP ERP 5.0. We are implementing XI now. So we
need to configure SLD and register our Business systems. The problem is
we have the concept of using the same logical system for all our SAP
systems, say WRPCLNT750, when we are hooking our systems to their
respective BW systems. And in SLD, we have problem becuase of this, as
it recommends to have unique logical system name for each Business
System being registered.
We want to mention some points in here about our landscape and some of
the recommendations we got from SAP regarding this. Ours is a very big
warehouse system and in order to avoid the lengthy "BDLS" runs, SAP
recommended using the same Logical System name for all the SAP systems.
Hence we are using the same logical system name for our systems.
So now coming to our problem, can you please tell us what would be the
best practice that needs to be followed now for SLD Business System
registration. How can we overcome the hurdle of NOT having a unique
logical system name for our systems in central System Landscape
Directory.
Please let us know the solution as early as possible.
Thanks and regards..
Haritha.
The Response:
Hello Haritha
I have found some pass cases with the same question that you have,
however, the replies from developer are as below.
Logical systems cannot be duplicated within the SLD, that means one
Business System per Logical System name, both need to be unique, the SLDis working a designed here.
I would suggest you rename one of the copies of the productive system
to solve this.
My apology that I couldn't provide you a better answer for this.
Thanks & Best Regards
Andy Lam
Active Global Support - SolMan & Technology
Kindly, please let me know your suggestions.
Thanks and regards..
Haritha.

Similar Messages

SLD Logical System Name Changes not taking effect in IDOC

All -
I've had to change a logical system name in the SLD, everything appears to be okay but new Idocs are still posting with the old LS name - any suggestions as to where to look for the old name would be most appreciated.
Thanks!

Hi Dennis,
After changing the logical system name in SLD have you done "Compare with SLD" from Service --> "Adapter-Specific Identifiers" for Business system in Integration Directory?
- Pinkle

ATTRIBUTE_INV_SND_SERV (partner number different of SLD logical system)

Hi,
I'm implementing an interface with XI 3.0. In my scenario, I've created one IDOC communication channel. and i try to send some data from file (File --> XI --> IDOC R/3)
I am using a XSL mapping to build an Idoc-XML from this input file and I'm filling the sender and receiver partner name (different of the default logical system of SLD)
In a first test, the Idoc adapter changed the partners name by the default ALE name of SLD, then when Idoc couldn't be processed in R/3 system because EDI partner was not customized. We would like to use the logical system of our mapping instead of the logical system froM SLD.
Then, I've applied next changes:
- I've checked "Apply Control Record Value from Payload"
- I've changed the Header mapping, indicating:
        Sender service as XPath = ..../SNDPRN
     receiver service as XPath = .... /RCVPRN
- The schema as ALE#LS
But althought these modifications, we are having this error in the monitoring (SXMB_MONI)
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert sender service to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please, i would really appreciate if anybody of you can help me to fix this problem.
Thanks in advance,
Gerardo

Hi michal,
    I've reviewed your weblog and it's very helpful as verifications guide.
    We've imported the Business system from the SLD, but we don't want to use its logical name. We would like to use the logical name of our XSL mappings.
    We've also checked the receiver agreements in SXI_CACHE, and both seems to be ok:
ReceiverService     /.../IDOC/EDI_DC40/RCVPRN
SenderService     /.../IDOC/EDI_DC40/SNDPRN
    And as last step, we've applied oss note 791181, but i have still the same error message ATTRIBUTE_INV_SND_SERV.
   Anyway, thanks a lot for you help. Please, if you have any more idea, please, i would really appreciate your help.
Regards,
Ger

Logical system missing in PI SLD

Hi,
The problem I facing currently during transport of SAP business system from Dev to Quality system, logical system is missing in the Adapter Specific parameters.
The actual problem I have seen in the SLD, the logical system is a blank and even after I pushed from RZ70.
Can you please suggest me how could i retrieve the Logical system in the SLD by automatically.
Thanks in advance.
Best Regards,
Sateesh

Hi Sateesh,
Please check the following links for similar issue , if it helps:
Logical system of PI in SLD
Logical system name in SLD for the R3 buss. system is not open for input.??
Logical System Name Not appearing in the Business System
Also, you can enter the Logical Name in the SLD, for the related TS / BS.
Regards,
Azhar

Clarification Regarding Logical System Names

HI all,
I read the blogs regarding Logical System Name, even I am having the some problems in my system.
For PI system client is 100.
R/3 System Client is 100 is created.
IN PI when I checked the sale->basic setting-> LOgical Settings-> Assign Logical Systems
I found there is only one client 100, and it is having the same logical system name as 'PICLNT100'.
In SLD one Business System is created for Client 100 and having the Logical System Name is 'PICLNT100'.
When I checking in the R/3 system that logical system Name ('PICLNT100') is not there and for r/3 client 100 having the different logical system name.
IN ID when I found the Goto ID->File Buinsess system and Menu ->Services->Adapter Specific Identifiers->Logical Ssytem,
It is different from the SLD logical System Name.
How Can I know in PI, that Logical System is belongs to r/3 or PI client 100,
when I running the sceanrio it is giving error as ATTRIBUTE_INV_SND_SERV while doing the file to Idoc scenario.
How I have to maintain the logical system names in this case?
please help me in this.
Regards,
Sree

hi.
each r3 system has his own SLN (PI,BI,ECC,etc). this name identify each R3 sytem.
http://help.sap.com/saphelp_nw04/helpdata/en/78/217dc151ce11d189570000e829fbbd/frameset.htm
IN ID when I found the Goto ID->File Buinsess system and Menu ->Services->Adapter Specific Identifiers->Logical Ssytem,
to export data of your R3 system to SLD, just do it from TCODE RZ70 in your r3 system, not PI.
once you configure it all data from r3 system is exported to SLD.
if the SLN does not match in Adapter Specific Identifiers->Logical Ssytem, edit the Bussines System (press in the little pencil) go to Adapter Specific Identifiers->Logical Ssytem and prees in the little hand icon. in the SLN in not refresh, go to menu enviroment--> CLEAR SLD DELTA CACHE. and repeat the steps before.
each time you send data to an R3 system and the sender system is a legacy. in your receiver communication channel>header mapping>sender system--> select the PI Bussines system and try again.
hope its helps
Rodrigo
PD: rewards points if useful

Regarding "Error An SLD system has not been assigned to logical system "

Hi all,
I am trying to connect SRM system to an XI system. All the settings are done (or I thought so). When I try to send a PO via XML/XI to the XI system in SRM Web UI, it gives me the following error:
nformation Processing BBP_PO_SEND_XML Is Started
Error An SLD system has not been assigned to logical system
Error Action could not be successfully executed
The backend systems are defined in spro. When I debugged the coding, I find that the right Logical system itself is not picked up - is there any thing missed out?
Thanks,
Vijay

Hi,
You should assign this here:
Supplier Relationship Management -> SRM Server -> Technical Basic Settings -> Define Backend Systems.
Here you should fill the "System Landscape Directory Name" for the systems you have defined.
Regards
Kathirvel

Logical systems while implementing charm in solution manager

Hello Everybody,
I just wanted to know how many logical systems we need while implementing charm in solution manager 7.0. I have 3 clients in development , 3 clients in Quality and 1 client in production.
Thank you,
vikram.

Hi Vikram,
Yes, i1n ChaRM we always work with logical systems, I mean clients.
The standard is:
DEV -> QAS -> PRD
However, you can also use:
- Minimum
DEV -> PRD
- Target groups
DEV -> QAS -> PRD
- > TST
DEV -> QA1 -> QA2 -> PRD
DEV -> QA1 -> PR1
-> QA2 -> PR2
There are a lot of combination possible.
BR
Fernando

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

An SLD system has not been assigned to logical system TEC101

Hello all
We are trying to send an message RFC or IDOC from our SRM (5.0) system to the XI (7.0). But we allways get the error
"An SLD system has not been assigned to logical system TEC101". In the SLD the system is visible, sldcheck works.
Does anyone know this problem and can give me a hint how to fix this problem?
Thanks a lot
Stefan

Hi Stefan,
Is there a technical & Business System for SRM5.0 in SLD? If entry exists then confirm if the logical system name mentioned in Business System is TEC101.
If entry does not exist in SLD for SRM, then in SRM run t-code
1) SLDAPICUST .. Enter relevant details
2) RZ70 : Give XI Server details , activate and then Execute.
Once you do that you can see entry for SRM in SLD.
After that try running the schenario again.
Regards,
Sumit

Logical System not appearing in SLD

Hello Friends,
Logical System of SAP R/3 system is not appearing in SLD. The logical system is available in backend ABAP System. I have even run the RZ70 data collection programs as well. However, I am not able to populate the logical system names in SLD.
I have put the same logical system names in the client tab of the technical system but in vain. The logical system field is non-editable and I believe it is always non-editable unless some technical system is not assigned to it.
The logical system name is also not available in ID (if it is not in SLD then it won't be in ID as well).
[The SLDCHECK is throwing exception 4. what to do for this? May be the data is not transfered because of this? Even though I have maintained proper password in SLDAPICUST!!!]
Request your kind adivse on what can be done. Where can I lookout for possible errors.
Thanks & Regards,
Anand Patil

Hi
On SLD - > Technical System -> Client -> Logical System Name , generally It is Editable entity .
If in Your Case , You can not change it, chech with ut basis Guy , for roles and authorisation against your Username ,
Check the Same SLD Roles with some PI Service User.
Regards
Prabhat Sharma.

Logical System Name in SLD

Hi All,
I was going through the guide
https://websmp105.sap-ag.de/~sapdownload/011000358700001410142005E/Configure.pdf
for the configuration of IDOCS. In this document, they have asked to verify the name of Logical System in SLD. In SLD I cant find an entry for the field Logical SYSTEM(for my client xxx in R/3). Now I do not want to delete the existing bussiness system but edit it to contain the Logical System Name in it.
Pls help me out.
Thanks & Regards,
Jai Shankar.

Hi
- Go to Technical System in the SLD.
- Select the system you want to check
- Select the client number you want to check
Here you will find the Logical System Name

Logical system name in SLD for the R3 buss. system is not open for input.??

Dear all,
We are upgrading to PI 7.1 and have a problem in a scenarie where PI is sending IDOC to R3.
The problem is probably related to the fact that it is not possible to write a logical system name in SLD for the R3 system. I can not read the logical system name for the R3 system into the Directory (adapter specific identifier), *because the logical system for the R3 bussines system is not an input file??*. How can i enter the logcal system name so i avoid following error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_RCV_SERV</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Receiver service cannot be converted into an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Regards Ugur

There are two ways....
Option 1 : Go to the BS of ur R3 system in Integration Direction. Go to edit mode mode and select Properties -> Adapter Specific attributes - > enter the LS name and save...
Option2 : You can use it from the mapping.... U either hard code/use from source the EDIDC40 section of ur mapping and the in ur IDOC receiver config select the option user
Option ! is the best soln...All the IDOC to that R3 system will go the specified LS...
regards,
Arvind R

SLD: Adjust / Add logical system name for Business System [XI 3.0]

Hi,
In the <b>System Landscape Directory</b>, is it possible to adjust the logical system name of an already created business system?
I found in the content maintenance in Subset="All Classes", Class=SAP_BCClient" --> <MY_BUSINESSSYSTEM_ENTRY> the only possibility to add information on the logical system name of a business system.
Unfortunately, the information provided in the BCClient Entry is not forwarded to the Business System Entry for my Business System in the Business Landscape View of the SLD...
Is there another possibility to add the logical system name to an exisiting business system?
Regards
Kristian

In a third party business system, it is not possible to add a logical system, but you can delete the business system and recreate it with the same name without problems.
After assigning a new logical system to a business system, you have to go to the integration directory and reload the logical system for the business system. Therefore open the Business System in change mode and maintain the Logical System with menu service -> Adapterspecific Identifiers.
Regards
Stefan

Is Logical System required for Solution Manager to work?

Hi all
We will be upgrading to SAP ERP in the near future and will have to use Solution Manager.
We only have one company code and no business areas in our configuration. So that, we do not need ALE, consequently, we have not defined/used a logical system.
Do we now need to define a logical system and assign our client to it, in order to use Solution Manager?
tia
Manuel

Hi Manuel,
in logical components the term "Logical System" is used to discribe the combination of system and client in an ABAP system. This does not mean you have to define logical systems in ALE customizing. That is not required as far as I know.
Regards
Andreas

SLD Business System with or with out Logical System If so, which Log system

Hi
I'm in confuse with the Logical System when creating a Business System in SLD.
Our requirement is LEGACY -- PI/XI -- ECC.
When I create Business sytem in SLD, I need to give a Logical System. Which system (Is it xi/pi or ECC ) Logical System to be provided?
Thanks.

>
Pothana Yadav wrote:
> Hi
>
> I'm in confuse with the Logical System when creating a Business System in SLD.
> Our requirement is LEGACY -- PI/XI -- ECC.
>
> When I create Business sytem in SLD, I need to give a Logical System. Which system (Is it xi/pi or ECC ) Logical System to be provided?
>
> Thanks.
if you are using File to IDoc scenario then need to define logical systems for both business systems you are going to create for
i.e they will be used as sender and receiver partners in case of logical systems
if need more details check the below blog
/people/rajeshkumar.pasupula/blog/2009/03/16/unable-to-convert-the-sender-service-to-an-ale-logical-system
check the same for how logical system are used in this case...
note above will be helpful in case of only idoc scenario..else no need of creating logical systems even though target sysstem is ECC
HTH
Rajesh

SLD - Logical System Management

Similar Messages

Maybe you are looking for