Logical System is missing

When I click on RSA1, I get a message " System RBA client 150 has no logical name!
Naming takes place through assignment to a logical system." And gave me an option to create or assign.
I select Assign and get 4 options SAP AG Konzern
Auslieferungsmandant R11
Test EarlyWatch Profiles
Unit Test
I select Unit Testing > Details> I get my client name , city, logical system (BLANK) , std currency and client role set to 'Customizing'.
What should i put in the logical system which is set to BLANK. should i put in there BIDEV150 ?
Please advise,
Thanks,
Krrish

Hi Diego,
I did put in my logical name provided by the company. And i get Entry BIDEV150 does not exist in TBDLS (check entry). So i went to tcode SALE and Define Logical System> entered BIDEV150 for Log System and name BI development for name. Is this correct. Should I now save it?..its creating a transport..should I go for it? Can i undo it if needed and delete the transport.
Once this is done can i then assign it the client?
Thanks

Similar Messages

LOGICAL SYSTEM IS MISSING CREATE ?

Hai All
I installed the BW in the system.but i cont login the BW system.Its shows error message'system ecc client 001 as no logical name.Naming takes place through assaignment to a logical system you must have to create another logical system before you can do this to continue,now assaign the logical system to this system and client'.Please tell me the answer asap.
Thanks

Hi Ram,
Take help of basis team to create logical system and assigning also you can check in sm59 your system is working or not.
Thanks & Regards,
Venkat.

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

BS- Adapter Specific Identifies - Logical System: value is missing

Hi,
I've created a simple scenario in which idoc is being received in ECC (by idoc receiver). my communication channel (i.e., soapSender) is part of my INTEGRATION_SERVER business system. i checked, for the relevant business system the Adapter Specific Identifies -> Logical System values and it was missing. therefore, i had to update the correlated technical system definition (at SLD) and updated required value (i.e., logical system). somehow the value is still missing when i re-check the business system (at Integration Builder).
i took the following actions:
1. delete and re-import BS from SLD.
2. re-start xI
and nothing was changed.
What can be done?
Regards,
Uri

Hi Uri,
>Indeed, the LS was not exits
I do not 100% understand your statement. Plz check AGAIN (in SLD) if the logical system name is still there.
My suspect was that a ABAP job (you can look to it in RZ70) is overwriting the technical system.
Regards,
Udo

An RFC destination could not be specified for the logical system

Hello Experts,
I am trying post goods receipt in EWM system in a simple inbound delivery process. It is not getting posted back in ECC. I have my RFC connection setup properly(I assume since I was able to transfer inbound delivery to EWM in first place).It seems some setting related to Outbound queue in EWM is missing.Can anyone tell me in detail what settings are required?Is it something to do with WE20 transaction?I am not sure what settings should be done there.The error log is as below-
An RFC destination could not be specified for the logical system
SB3CLNT011
Message No. B1550
Diagnosis
An RFC destination should be specified for the logical system SB3CLNT011.
This could not be done in this case. SB3CLNT011 is not your local logical system
and this system is not included in the relevant Customizing tables.
Procedure
Check:
RFC
destination
Port
definitions
oubound partner profile of
message type SYNCH for this logical system
Regards,
Khushboo

Hi Oritra and Suraj,
I have checked remote connection in SM59 for both the logical system.It works fine.I understand this is more of a technical issue,but I don't have A local basis team to help me so reaching out to experts here.Can you guide me what technical settings could be checked for EWM-->ECC connection?When I execute BD82 for SB3CLNT011 it shows me green status with message "No messages have been defined for the selection conditions in the model".
Although when I do this for EWM logical system SB3CLNT012 it shows me this with all green status-
System SB3CLNT011 as a partner type already exists
System SB3CLNT012 as a partner type already exists
Port A000000018 with RFC destination SB3CLNT011 already exists
Outbound parameters for message type SHP_IBDLV_CHANGE SHP_IBDLV_CHANGE01 already
Outbound parameters for message type SHP_IBDLV_SAVE_REPLICA SHP_IBDLV_SAVE_REPLI
Outbound parameters for message type SYNCH SYNCHRON already exist
Am I missing something in WE20?
Regards,
Khushboo

AC 5.3 Logical systems and multiple Physical systems

HI all:
We have set up a Logical System, and then have hooked up 2 Physical systems to it. Based on the documentation from SAP, the rule set (and the way we set it up) is at the Logical system level.
Physical system #1 is reporting the correct results, however, Physical system #2 results are not complete. My understanding is that both Physical systems should be drawing from the rule set based in the Logical system.
Results: Physical system #1 - correctly identifies 10 risks
Physical system #2 - incorrectly only identifies 5 of the expected 10 risks.
Role assignment to user is exactly same, authorizations are exactly the same. The User/Role/Profile Full Sync has been repeated as part of troubleshooting.
Has anyone experienced this? I'm looking for ideas/options on where to investigate why the results are different.
Thanks
Margaret

HI:
Thanks for answering!! I'm having trouble understanding the answers, sorry.
When you have a logical system...you upload the rules once to that system, and generate them. Then when you set up a physical system and hook it up to the logical system...the 1st, 2nd or 3rd physical system....they all use the same ruleset. The whole concept (as I understand) is that the use of Logical and Physical systems...and putting the rule set on the Logical system so you don't have to worry about one rule set taking precedence over another, is an advantage, if this is possible (ie: we don't have multiple rule sets).
Where should I be checking that the risks are defined properly? The rule set is the delivered one from SAP. The functions and risks match what we had (plus more) in the CC 4.0 system.
The first physical system we set up (example: Development) works fine, and all regular SoD risks are coming up as expected. When we added another system (example: Test)...the results of SoD analysis were incomplete.
Does that help clarify? Perhaps I'm just missing something?
Margaret
Edited by: Margaret Sokolov on Apr 28, 2009 4:34 PM

No logical system group can be determined for administrative unit &1

Dear GTS gurus,
In Risk Management module when we execute the report "Analyze LTVD Request Relevance of Products" (/SAPSLL/PRE_VD_OPT_ANL_PROD) we sometimes get the error message:
No logical system group can be determined for administrative unit *******
Now I did some googling and found the following website: consolut - /SAPSLL/PRE_VDEC139 - No logical system group can be determined for administrative unit &amp;1 - /SAPSLL/…
It says that in customizing item "Define Administrative Unit Attributes" some assignment is missing but I was not able to figure out what exactly. I compared it with Administrative Units which did not not issue any error messages and customizing looks good to me.
Can you share your insights on this topic?
Best Regards
Greg

Hello Gregor,
Under the Admin Unit attributes, you must have a Plant Group defined.
Is that Plant Group assigned to a logical system ?
(IMG: General Settings -> Organizational Structure -> Define Cross-Plant evaluation (or Define Plant-based BOM evaluation)
By the way, the site you have found is one of the many sites out there that lists the messages available in a SAP system. The same information is available within GTS (Transaction SE91).
Regards.
Mouaz BEN REDJEB

Logical system name vs. destination name - CUA -

Hey experts,
at the moment I´m thinking about using the CUA in our SAP environment for role distribution.
In this scenario I need destinations to the child systems (of course!). In all manuals I found it say, that i HAVE to create destinations which have the same name as the logical system. However, this is not possible cause this is against corporate name conventions.
So I tried to use different destination names, but when I use the function "text comparison" (SU01->Roles) it always fails and says that the destination to the child system is missing.
So here my question: How can I tell the CUA not to search for destinations named like the logical system????
Thx in advance, nice weekend
Oliver

Hey John,
piece of cake ;).. that's what I thought at first. Unfortunately it´s not that easy. This is because of partially really strict restrictions within the SAP-Software.
At the one Module, you can choose the destination, is used for a particular group of functions. At the next, you simply can´t. SAP says "you need to have a destination, named as the logical system name". And there is no way around.
Maybe I´am the first guy being disturbed by this "feature"....
Of cause, I already placed several posts within the basis section... but still.. no way around. In one case I even opened a ticket at SAP... (I already posted the answer above) ....
Thx anyways!
Oliver

JDBC to Idoc scenario - change of logical system name

Hi,
I have a JDBC to idoc scenario that worked. Now i had to change the logical system name from my sender system from ABC_123 into ABC123 in the SLD (Business System - Integration - Logical System name). I did so and also refreshed my Cache.
Afterwards I started the process, but it failed in the Receiver system. The idoc is correct expect of the partner name. My receiver system expect ABC123 - as I changed in the SLD - but PI send ABC_123.
If io look in SXI_CACHE - Services my Business System still got the "old" name (ABC_123).
Did i miss something resp. how can i load the current configuration from SLD?
Thanks in advance
Michael

Hi Michael,
Again Import the changed logical system in the Integration directory of you PI system.
And check the scenario (Sender Agreement, Receiver agreement ) what system they are reflecting.
If they are showing old system then you have to replace the business system in all the scenario.
Edited by: Rajhans Abhay on Jan 7, 2010 3:14 PM

ATP Check Issue - No business system could be determined for logical system

Dear all
Got an issue while executing ATP check on a planned order in product view,
with a message: "No business system could be determined for logical system"
CIF setting wise:
regular business system group maintained and assigned in place,
master data wise:
business system group info fine in product master,
Is there anywhere suggested to check under ATP setting:
category, check mode, business event, check control/check instruction?
Your kindest enlighting is appreciated,
Thank you,
mandy

Dear Mandy,
usually this error is caused by a missing customizing entry:
spro:
Integration with SAP Components
   Integration via APO Core Interface (CIF)
     Basic Settings for Creating the System Landscape
       - Maintain Business System Group
       - Assign Logical System and Queue Type :
Please read the documentation for these two transactions and create the systems.
You need to specifiy there all systems that are in your BSG. The documentation for the customizing of 'name logical system' in APO says:
To enable the transfer of data between SAP R/3 and SAP APO, you need to name both the SAP APO system in which you are working and the SAP R/3 system to which you want to transfer data as logical systems.
I hope this helps.
Regards,
Tibor

Logical System Error

Hi AlL
I am working on the JDBC TO IDOC Scenario and when testing I get error:
Unable to convert the sender service ABC_Service to an ALE logical system
I check on the SLD under the Business System and what I find is that there is no LOGICAL SYSTEM NAME.
How to make the PI System to keep up the LS, on the TCode BD54 I created it
Role:
Pipeline URL:
Group:
Technical System: PI1 on saptrain1 Change...
Client: 001 of PI1
Logical System Name: #######
Thanks
Yonela

Hi Guys
On my JDBC TO IDOC Scenario when testing on the MONI I get the below 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>XIServer</SAP:Category>
<SAP:Code area="XICACHE">BUSINESS_SYSTEM</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>NO INTEGRATION SERVER</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while refreshing the XI runtime cache</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
but on the SLD my Business System looks like this:
Role: Integration Server
Pipeline URL:   http://saptrain1:8000/sap/xi/engine?type=entry
Group:    No group assigned
Technical System: PI1 on saptrain1 Change...
Client: 001 of PI1
Logical System Name: LSJDBC
I have done
with this user : PIDIRUSER i have done the full cache
http://saptrain1:8000/CPACache/refresh?mode=full
CPA cache refresh (mode=full) successfully executed in 30937 milliseconds.
but when running
http://saptrain1:8000/sap/xi/engine?type=entry on the browser i get :
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Header />
- <SOAP:Body>
- <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<faultcode>SOAP:Client</faultcode>
<faultstring>Empty HTTP request received</faultstring>
<faultactor>http://sap.com/xi/XI/Message/30</faultactor>
- <detail>
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIProtocol</SAP:Category>
<SAP:Code area="MESSAGE">EMPTY_HTTP_REQUEST_RECEIVED</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Empty HTTP query received; message processing not possible</SAP:Stack>
</SAP:Error>
</detail>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope
What I am I missing out
Thanks,
Yonela

Partner type -only logical system?

Hi!
I have a scenario where I want to send an idoc to SAP using XI idoc adapter. It works fine using a partner type "logical system" (LS). But now i would like a scenario where the partner i a type "customer" (KU). I have defined a new business system in the SLD as a sender (just in case) and the partner of course exist in SAP under customers). I have also mapped the korrekt values to the IDOC (sndprt, sndpor and so on) -but these are of course overwritten using the values from the SLD (which only operates using logical system). Is there a way to integrate using a partner of type customer? I have made a similar scenario work using the Business Connector -what is the missing link to make it work in XI?
best regards

Hi Martin,
> I have a scenario where I want to send an idoc to SAP
> using XI idoc adapter. It works fine using a partner
> type "logical system" (LS). But now i would like a
> scenario where the partner i a type "customer" (KU).
This is not foreseen in XI 2.0. You need to wait for XI 3.0, there it will be possible.
Regards
Stefan

Receiver service ??? cannot be converted into an ALE logical system

Hi,
I am hoping for some help with an Idoc issue in XI version 3.0. The scenario is like this:
Flat file->File adapter->XI->Idoc adapter->R/3
I have configured a scenario in one system like this that works fine. But in the current system I am getting the error message "Receiver service ??? cannot be converted into an ALE logical system" from the Idoc adapter.
As it is XI 3.0, I have set the Agency and Scheme in the destination communication channel to <Service>, ALE#LS and in the destination party, I have created a alternative identifier <Service>, ALE#LS, SYSCLNT200.
I have configured an ALE logical system name in the SLD.
I have cleared the SLD cache in the integration builder.
The ALE logical system name was not in the SLD when the message first appeared, but I thought clearing the cache would fix that. I have not tried deleting the service and re creating it. That is my next step....if all else fails.
Not sure what else I haven't tried.
Can anyone offer any advice?

Thanks Sam Raju for the reply.
On your questions:
1. I checked IDX1 - port for the receiving R/3 is defined as SAPIR1_300 (port: SAPIR1 and Client: 300) and it is mapped to RFC destination of IR1300.
2. Checked RFC destination IR1300 - it is setup as R/3 connection and checked test connection and remote login and both are working fine
3. Checked IDX5 - did find one message (status is successful) corresponding to the file I am sending into R/3 and this entry is an Outbound entry.
Question: Should there be two entries here in IDX5 - one for inbound and the other for outbound?
May be I am doing something wrong here in setting up the interface mapping and endpoints. Anyway when I check the IDOCOutbound in the Soap Header, I see the following:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:IDocOutbound xmlns:SAP="http://sap.com/exchange/MessageFormat/">
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>100</SAP:MANDT>
<SAP:DOCNUM>0000000000008002</SAP:DOCNUM>
<SAP:DIRECT>2</SAP:DIRECT>
<SAP:IDOCTYP>FLIGHT_SAVEREPLICA01</SAP:IDOCTYP>
<SAP:MESTYP>FLIGHT_SAVEREPLICA</SAP:MESTYP>
<SAP:SNDPOR>SAPBXI</SAP:SNDPOR>
<SAP:SNDPRN>PRISM</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
<SAP:RCVPOR>SAPIR1</SAP:RCVPOR>
<SAP:RCVPRN>IR1CLNT300</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
</SAP:IDocOutbound>
Do you see anything wrong or missing here. SNDPOR is XI port, SNDPRN is the source partner (file) and RCV... information is all the receiving R/3.
I am suspecting that something is missing either here or in the endpoint setup.
Also, in the TechnicalRouting I have this:
- <SAP:address version="20">
<SAP:systemKey>IR1CLNT300</SAP:systemKey>
<SAP:endpointType>IDOC</SAP:endpointType>
<SAP:url>IDOC://SAPIR1?RFCDEST=IR1300&DOCREL=&VERSION=3&SAPREL=46C</SAP:url>
</SAP:address>
Any issues you see here in url?
Also, when I look on the XI server, I do not see these files deposited anywhere- so they are going somewhere (as the status in IDX5 is successful)!
Do I need to activate any queues or triggers anywhere.
Can you please offer advice and help us out.
Thanks again.
Srini
[email protected]

Logical system not seen in ID (7.0)

Dear XI experts,
i defined in SLD a logical system as application system (SAP BACKEND)to send and receive IDOCS.
I am trying to assign a Business system in the ID which I defined in the SLD and cant seem to find this in the ID.
What must have I missed while defining the Business system or Technical sysetm?
Perhaps some step information could help for PI 7.0.
Thanks

hi,
have a look at my blog:
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
Regards,
Michal Krawczyk
http://mypigenie.com XI/PI FAQ

BW / SolMan Logical System Change

Hello all, I am having a BW related issue and would really appreciate some advice. I realize some of this is for the solMan forums and will cross post (I normally dont)
ENVIRONMENT
New installation of Solution Manager EhP1 (19). System name is ED0. We are running Windows / MS SQL
System is only for Solution Manager ops (client 001), and CUA master (client 950).
BACKGROUND
We want to use full SolMan capabilities. This seems to include some limited BW interaction. We do not use BW in the landscape, so will rely on the "internal" BW in SolMan.
During installation, our person made a new client (000 > 400), set it as default (login/system_client), then ran tc:RSA1 and activated the content. (This sets the client)
Client 400 HAS NOT BEEN USED FOR ANYTHING other than the initial installation, and subsequent activation of BW. It has no connections to other systems, no data, cubes, or anything
PROBLEM
We were NOT AWARE that he had ran RSA1 and activated content, and began using client ED0_001 as our PRODUCTION SolMan client.
We are now unable to run RSA1 in anything but client 400.
We are unable to change the client 001 logical system name because Solution Manager has been built around it.
TROUBLESHOOTING
We changed table RSADMINA / field BWMANDT to 001 from 400. This changed the error from "You can only run in client 400" to "The logical system name has changed" (exit only)
In sandbox I duplicated this problem, then deleted the 400 client (with T000 entry). Changed the login/system_client to 001, RSDAMINA to 001, and ran function module RS_MANDT_UNIQUE_SET (set i_mandt to 001). After restart, RSA1 gives same error, logical system name changed"
On same sandbox after #2 above I attempted tc: BDLS to see if it would let me assign an exisiting logical system. It did not
QUESTIONS
Will it have any impact on Solution Manager operations to have the "BW Client" on ED0_400 while Solution Manager production is on ED0_001?
Is it possible to change the BW operating client to 001 from 400? (said another way, can I change the current logical systems BW is keyed with to a different, but existing, logical system)
Assuming the answer to Q1 is yes, and the answer to Q2 is no, what steps need to be performed to make BW fulfill the SolMan requirements?

Updated Information - Answer to Question #1.
I am embarrased I missed this section in the master guide the first time around. I will leave the question unanswered in case someone has an easy rememdy to changing the BI client logical system, as I would like to have it in my productive client if possible. However I am relieved I have the option of running it separately in case that can't be done.
There are three major options to consider when planning your system landscape in regards to BI.
BI in the Productive SAP Solution Manager Client
In this scenario, BI is used in the same productive client as SAP Solution Manager. This option allowsfor simpler configuration, and isolates the BI activities conducted for solution life cycle management from the data on a production BI instance. This is SAPu2019s recommendation.
BI in a Separate Client on SAP Solution Manager
In this scenario, BI activities are conducted in a separate client on the SAP Solution Manager system. This scenario provides increased security, as user access is more restricted. However, you must maintain users separately and this increased your administration effort. There is no technical benefit.
BI in a Separate, Non-Productive BI System
In this scenario, the BI activities are conducted in a separate, nonproductive BI system in the landscape. Data is sent to this system from the SAP Solution Manager system via RFC. This is only needed in rare cases for sizing purposes.

Logical System is missing

Similar Messages

Maybe you are looking for