SLD question: When is Logical system mandatory?

Hi Experts,
When we create a business system we get a dialog for entering logical system. My question is, for what business system, logical system in mandatory? Is it for ABAP? or third party? or Java?
What is the real significance of a logical system?
Thanks
Gopal

Hi,
When your Business System you create is going to be a Web AS ABAP and you are going to use this with the IDOC adapter , then the Assignment of the Logical System Name with the Client is mandatory.
Otherwise, when you are adding a clinet to a technical system, the Logical System Name is optional.
Regards,
Bhavesh

Similar Messages

New outputs generated when changing logical system in output master record

Hi!
We are sending documents from ECC 5 to a legacy system via XI/PI. We are about to move from an old XI installation to a new PI installation. The output record used (for example in a billing document) is set up based on logical system. When moving from the old to the new platform, we need to change the output records from the old logical syste to the new logical system. However this leads to generation of new outputs in all billing docs when opened in change mode. This goes also for billing docs where we already generated outputs via lthe old logical system in the past. Is there any solution to prevent the automatic generation of outputs for documents where the condition type already was successfully processed (as it works when the logical system is not changed)?
Best regards
/Björn

Normally the same output is not supposed to be generated, unless 'Multiple issuing' checkbox is checked in the output type configuration.
Also you can probably add a requirement in the output determination procedure and check if output record already exists. Take a look at the standard 'Reprint' routine, kind of the opposite is needed in this case.

SLD doesnu00B4t refresh de Logical System

Hi All,
I work on enviroment that had never had an IDOC scenario, because this the Technical System in SLD doesn´t have a Logical System.
So, now the company needs a IDOC scenario, and I created one correct logical system in the BD54 (R3 Receiver), after this I updated the Logical system of the Client in Technical System (SLD).
However, When I check the Business system linked with this Technical System as I said above, the logical system name isn´t updated as I did.
I tried to create other clients in TS to see if the BS refresh, but the Logical system still not showing up in BS.
Am I missing something ?
The BS needs to have a Logical system name and thus I can update the BS in Integration Builder (configuration)
Thanks in Advance.
Diego Crespo
Edited by: Consultores Procwork on May 13, 2009 4:42 PM

Hi
-->While creating technical system as WEB AS ABAP in your SLD you need to maintain the details of your R/3 system like DB Host name,Installation number,Client etc.....While creating TS you no need to maintain any LS.
-->While creating the Business System as WEB AS ABAP along with your name to BS it will ask the LS name and you ned to select your required TS(ie WEB AS ABAP TS).
-->The LS name which you maintained in your SLD must and should created in your R/3 system in BD54 and that LS name should be assigned to client using t-code SCC4.
-->If the LS name which you assigned to your BS is not reflecting in your ID means,
FROM->MENU->Clear SLD.
-->Select your BS and click on button compare with SLD
Thanks

"Logical System" & "Assign Logical System to Client"

Hi Experts,
I'm new to Basis, I have the following systems installed:
1. EBP and SUS are installed in same server with different client:
    EBP: E01 with client 100
    SUS: E01 with client 200
2. ECC system is installed at a separate setver
    ECC: D01 with client 100
My question is, in EBP client which logical systems and client assigments need to be done?
What I confused is, for the EBP and ECC they have same client number 100, in EBP client , the client number 100
should be assigned to EBP or to ECC?
Kindly please guide.
Thanks and best regards
Jack

Hello Jacky,
                   You can assign the client number 100 to EBP and ECC systems, it doesn't create any problem. Because when you logical system in EBP, you need to create two logical systems one for EBP and ECC, but you need to assign client 100 to EBP only, same goes to the other side also.
Regards,
Prasanna

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.

Clarification on Logical System naming

I have a Web AS ABAP Technical system ES1 with a client 100 assigned as a Logical system ES1CLNT100.
I also have a Business system BS_ES1 running on this with a Logical System name ES1CLNT100 i.e. the same as the technical system (this is a test system and no I did not set this up myself).
I assume that I need to change the logical system ID of the business system to something different, say BSES1. Is that correct?
If I use that BS_ES1 business system as the receiving system for IDocs, do I need to enter the logical system name in SALE for the receiving system that receives the IDocs?
Kind Regards,
Tony.

Were you allowed to create 2 Business Systems in the SLD with the same logical System Name? That is strange?
Even though maybe you can do this at the SLD, when you try to import it into the ID, you will be unable to activate the Business System in ID.
There can be one and only one business system in the ID that uses one Logical System Name.
Regards
Bhavesh

XI 3 File to IDoc scenario - Still referencing Old Logical system

Hi
Dont know if you can help. I have a file to idoc scenario using XI 3 to R/3 4.6c system.
I had the interface working from a third party system XMLHUB to SAP R/3. The Logical system name for the XMLHUB was XMLHUB01 in the SLD which I have set up as a partner profile in R/3. I have recently changed the logical system name to XMLHUBDEV01 in the SLD and created that logical system in R/3 and changed the partner profile to XMLHUBDEV01.
Unfortunately in the sender information of the IDoc the partner number is still XMLHUB01 and not XMLHUBDEV01. I don't understand where this partner is sent from to get into the control record of the IDoc.
I have cleared the SLD cache in both the Repository and the directory. Is there somewhere else I should be looking? Any help would be appreciated.
Regards
Daniel

hi daniel...
this thread wud answer ur query....
Re: IDOC Payload
regards..
vishal

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.

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

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

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

An SLD system has not been assigned to logical system

Hi masters
I trying send PO in XML to SUS through XI ,
but when try to send the SRM/EB system show the next message
Processing BBP_PO_SEND_XML Is Started
An SLD system has not been assigned to logical system
Action could not be successfully executed
in XI system I defined the SLD sistem for SRM/EB and SRM/SUS
that SLD name is settup into define system Landscape into colum System Land Directory Name
in SLDCHECK all is Ok on green light.
what can I do ?

Hi. Nikhil.
In SRM/EB
1.- trying configurates SMXB_ADM
2.- Integratio Engine configration
3.- Role of Business System = Application System
4.- Corresponding Integ. Server = dest://RFC type H for XI system,
problem .
when I push bottom check (F7)
the message is the next
red light No access to system Landscape at present

Logical systems assignment when SRM and ECC are on 2 different servers

Hi SRM guru's,
What is the standard practice for Logical system creation and assignment when ECC and SRM are on 2 different servers.
I could not able to find which i created a logical system in SRM server which i created in ECC
Same for the ECC also.
how do i assign logical system of SRM to ECC
vice versa.
your prompt response is appreciated.
Regards

Hi Sai,
Logical System Naming/Creation procedure is not dependent on the servers but it is just a logical representation of a system.
As you are trying to name logical systems for ECC & SRM, please follow the below procedure which is usually recommeded by SAP and followed.
Logical System : <SID>CLNT<Client Number>
For Example if you have a client 300 in system DE0 (also called SID), the logical system name will be DE0CLNT300. And it will be same for SRM system.
You can refer the below document which eplains the creation of logical system and RFC destinations etc
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
Note: Only while configuring the RFC Destination, the servers will play a crucial role.
Regards
Kathirvel

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

SLD question: When is Logical system mandatory?

Similar Messages

Maybe you are looking for