Same busines system having different Logical system name--- is it possible

Hi Experts,
Can I create same business system connected to to a specific Technical system? Here I am creating more than one business system having same business sytem name but different logical system name?
What are the outcomes can I expect?
Thanks
Sugata B

One technical system could have multiple business system and each business system should have a unique logical system name. However, if you provide some similar name, then I guess while configuring there would be no error. At runtime, you may face some error when business system is checked during SLD lookup.
Regards,
Prateek

Similar Messages

Internal order - Error - Different logical system for order

Hello all,
I try to send IDoc (INTERNAL_ORDER) from system A to system B.
I have done:
- BD64 / WE20 / WE21
But after having customizing I have got following error:
Different logical system for order xxxxxx
Message no. 2075ALE001
Diagnosis
Internal order xxxxxxx already exists in system B. Its master system B is different from the master system A of the new internal order to be distributed with the same order number xxxxxxx.
System Response
Internal order xxxxxxx with master system A cannot be distributed in system B.
Procedure
Check customizing for ALE for internal orders.
How to solve this?
My aim is to maintain internal order master data in test system.
Thanks for your help.
David

I have found something.
If I change in table AUFK, logical from empty to A (master) and I run IDOC then IDOC has been correctly integrated.
Then: how to define "master"?

The central system has no logical system name

I am encountering one error message during configuring the Chnage Request Management in solution manager. As follows.
The central system has no logical system name
Message no. SCDT_DIST034
How do i define it?

Hello,
You may define logical system name via Tcode SCC4. Select your client and there is dropbox for Logical System. Click on the dropbox and you may received message "No value.." and ask you if you want to define the new logical system.
Please ensure the rec. logical scheme is : <SID>CLNT<CLNTNO.>
Hope this could help you.
Regards,
AZLY

Connect to R/3 systems with different XI systems

Hi all,
I have the next scenario:
R/3 system A --> XI system A --> Other systems
R/3 system B --> XI system B --> Other systems
Both systems have different SLD system.
And I need create an IDOC interface between both R/3 systems.
Could somebody help me?
Can I send and IDOC to a XI system with only configure a RFC connection (SM59) or I need configure it in SLD?
Regards, Raú

Hey
are u suppose to do an IDOC(R/3 system A)-Xi-IDOC(R/3 system B) scenario,of u have to collect IDOC's from both the R/3 systems and send it to a single file?
in any case u have to maintain separate Business system and logical system name for both R/3 systems
thanx
ahmad
Message was edited by:
Ahmad

Can one physical system have multiple logical systems? if yes why?

can one physical system have multiple logical systems? if yes why?
Regards
sriman

Logical system is an ALIAS name for a physical LOCATION. so we may have more than 1 logical system name for a physical location.
eventhough its allowed,but normally we dont do that.
you can do this in FILE transaction.
Regards
srikanth

Unable to convert send system to ALE logical system

Hi Expters,
I am doing FILE 2 IDoc Scenario as follows...
Created 1 BS for sender as Third Party...
Created 1 BS for receiver as WebAs ABAP...
I did everything perfect in IR and ID. But I am getting error in end to end testing. I am placing file in my local drive and the file has been picked up correctly.
And also I can see my Logical System name in ID(Adapter Specific Identifiers) towards my receiver BS. But There is no logical system is displaying for the sender BS in ID.
Still I am getting Error: Unable to Convert Sender System to ALE Logical System...
I have followed blogs and wikis but not successfull...
Do needful in this regard...
Regards,
Basha.

Hi,
Refer this link
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
Problem Unable to convert the sender service to an ALE logical system
http://wiki.sdn.sap.com/wiki/display/XI/UnabletoconvertSendersystemtoALElogicalsystem
Regards,
Nithiyanandam

Regarding Error: Unable to Convert Sender System to ALE Logical System

Hi friends,
in File to IDoc scenario, i created a sender business system called bs_filetoidoc_send based on Standalone technical system and a receiver business system based on ABAP r/3 system. in my SAP IDES system which is dual stack (abap+java), XI client is 001 (LS: devclnt001) and r/3 client is 800 (LS: t90clnt090) i.e i'm posting idoc to t90clnt090.
I tried to send a text file. but while processing xml message in XI, i got an error saying "Unable to Convert Sender System to ALE Logical System".
then i searched the blogs and forum and found the solution. it was saying LS name was not assigned to BS bs_filetoidoc_send. so i went to SLD and tried to assign LS devclnt001 to my sender BS bs_filetoidoc_send, but got an error saying that "A business system with LS devclnt001 already exists". when i checked which is that BS, it is supposed to be the INTEGRATION SERVER itself with BS name INTEGRATION_SERVER_DEV.
then i configured my sender BS as INTEGRATION_SERVER_DEV itself which picked up the text file successfully and also receiver abap server received the IDOC with correct data and format with status 51. so scenario worked fine when i used my sender BS as INTEGRATION SERVER itself.
please clear my following doubts which arose after this scenario.
1) why the scenario didn't work when I used only standalone sender business system?
2) why should we assign a LS name of XI server to sender business system only in this scenario?
scenario worked according to my requirement, but using integration server itself as a sender BS confused though.
Many Thanks.

1) I can create any no of LS names using SALE
Yes you can create.
> 2) But I can assign a client to any one of those LS names (or 1 client will have only one LS name associated with it)
One Client will have one LS associated to it...and that can be any one of the LS..created.. use SCC4 to find the associated Ls for all the clients of a system
3) So anyways INTEGRATION_SERVER_DEV has to associated with the client 001 only, so finally I have to use INTEGRATION_SERVER_DEV only as my sender BS. Probleum is that I can't remove the LS name DEVCLNT001 from INTEGRATION_SERVER_DEV and assign it to bs_filetoidoc_send BS right. If I do so, I think I would get an error saying that INTEGRATION_SERVER_DEV is not associated with the LS name of client 001.
As the logical system defined in Partner profile is expected to arrive in Control record of IDoc..it should be passed in that...
Did u checked this blog../people/rajeshkumar.pasupula/blog/2009/03/16/unable-to-convert-the-sender-service-to-an-ale-logical-system so as per you need the explaination in the blog need to associate the logical system name .
HTH
Rajesh

How to find out the systems under a logical system?

Hi,
Is their any table in SAP so that we can see the the systems under a Logical System, I need to check it in production where i dint have the access for SCC4 ,SM59 and SPRO.
I also checked in all *Log*Sys* Tables but find nothing.

Hi Pranjal,
I don't think if there is such a table to give you mapping of the logical groups and the connectors associated with the same. Would like to know if there is any as such
As Alessandro suggested, GRACCONNSTAT is the only table on this context.
Ameet

System Copy and Logical system name conversion

Hello All,
Can any one let me know some inputs over these few queries.
1. How much time would a 500+GB clients take for Export and reimport after the system copy.
2. What would be run time of the BDLSS report ( Converting the logical system names) for a typical 1500 GB QTY system
The requirement is my QTY has 3 clients, and i would like to refresh it with my PRD data. How do i safely perform thia activity with the least downtine possible and please note, the clients are around 500+ GB huge..
Thanks in advance for your inputs.
Rgds,
Sri

Hi Frank,
the parameters of my installation are as folows.
Appl Serv : OS - AIX (5.2 Version) and CPU's - 4 (Mem 20480) ::: DB serv : OS - AIX(5.2 Version) and CPU - 6 (Mem 22528)
The DB version is Oracle 9.2
We are on 4.7 enterprise version of SAP with SAPKA62055 patrch level.
br
Sri

Different Logical Systems ?

HI,
is it possible to use another Logical Systemname (Sender Service) ?
i know 2 possibilities.
1) Change the LS in the SLD but i can´t do that because a lot of companies using this LS.
2) Check "Using sender from payload" but this is already changed to "using controlinformation from payload" and might not be changed.
Is there another way to change the SenderService ID in the configuration and no other companies (business systems) are involved ?
Thank YOu,
Gordon

Hi,
are you talking about IDOCs?
>>>>2) Check "Using sender from payload" but this is already changed to "using controlinformation from payload" and might not be changed.
you can set it for even IDOC channel ...
so it can be changed in this way
for more info on IDOC processing check out:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Reg Logical System Name

Hi,
We have ECC 6.0 PROD and ECC 6.0 QAS System.
WE have different logical system names for both the systems
But when we refreshed the PROD to QAS , we have to run the BDLS transcation to change the logical System name(since we are having different logical System name)
But BDLs is taking more than 40 hours.
Please let me know , whether logical system name can be the same throughtout the landscape or not
In other words , is there any side effects if i have same logical system name for QAS and PROD

I've been researching the same issue. I found the following
"Is it necessary to change the logical system names?
Because of the two reasons mentioned above (long runtime of transaction BDLS and possible inconsistencies), it may be desirable, to avoid the renaming of logical systems during system copy.
Whether logical systems names need to be changed at all after a system copy depends on the type of the target system: "
This is from SAP System Landscape Copy for SAP Net Weaver and my SAP Solutions
Best Practice for Solution Management
I found it searching for sap bdls alternative
Hope this helps. I'm continuing my search.

Is it possible to use 0FI_AR_03 with 2 different BW Systems in parallel?

Hi
The 0FI_AR_03 DataSource is already in use from another BW system and we would like to this DataSource with our BW system, too.
Is it possible to use the DataSource 0FI_AR_03 with 2 BW systems in parallel?
Thx for your help in advance, Michael

hi Michael,
welcome to SDN ...
it should possible, the delta is maintained separately for different bw system, as we can see there is 'bw system' in RSA7. make sure your new bw system has different logical system name from the existing one.
hope this helps.

Same Logical System Name, different Business System

Hi all,
I have a problem regarding SLD and Integration Directory. The client is requiring me to use the same logical system name for two different business systems. It seems that this is not possible in XI. When I tried activating the business system in ID, I'm getting the error, 'Logical system XXX already exists in communication component YYY'. Please help. Thanks!
IX

Hi,
You cannot have same logical name for two business systems....
Why you need it?? How will the SAP system understand which which system the message was sent for?? Some workaround like
1. Create a business system with this logical system
2. Overwrite sender/receiver business system in the receiver agreement for messages sent to 2nd business system..
This may lead to discrepancies....
Regards
Suraj

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

Idoc Acknowledgements - Logical System Name

All,
Stuck with a few issues with Idoc Acknowledgments which I hope SDN can help me with. For ease of understanding the problem, am splitting this into 2 Scenarios ,
Scenario 1
SAP R3 (Idoc ) - XI - File ( Business Service)
R3 Triggers Idoc to XI and XI sends this as a File to the target Application. AleAdudits can be sent back to the R3 system as shown in <a href="/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc">this</a> blog by Saravana by adding the Logical System Name to the Business Service.
Issue :
R3 has configured Partner Profile with respect to XI and this cannot be changed. To send the Idoc Ack's back to R3 we need to add the Corresponding Logical System Name to the Business Service.
The problem is - what if the Idoc is to be sent to 2 Different Business Service / Systems. The R3 expects an Acknowledgment with XI as the sender partner but we cannot share the same logical system across different Business Systems / services . The easiest solution seems to be to create different partner profiles in R3, one for each Business System / Service. But this is not possible currently.
Scenario 2: 
R3 - XI - BPM - Target
Idoc triggered from R3, are sent to a BPM and then from the BPM to a file. Everything works fine.
But, the problem lies that when the Ack needs to be sent back to R3, The ack errors out because no Logical System Name is associated with the BPM.
We do not want to add another logical system name to the BPM and thereby create another partner profile and the problem is similar to Scenario 1.
Solutions Explored
1. In the ACK_IDOCAdapter , I tried to select option Take Sender From Payload and Take Receiver from Payload.
But this does not seem to help. I can see the trace in MONI saying the ACK_IDOC adapter is choosen to send the ack back to R3 , but it does not take the Partner Names from the payload of the AleAdudit and errors out with error Unable to convert..
2. As this AleAduit is sent from XI back to R3 and is not a R3 (AleAduit) - XI - R3 (aleaduit) case, adding a entry as shown in Section 6 in
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb">this</a> document will not help.
Has anyone tried something of this sort. Any known solutions?
I hope the description of the problem made sense, if no, do let me know.
Regards
Bhavesh

Bhavesh,
Your problem as i understand -> The problem is - what if the Idoc is to be sent to 2 Different Business Service / Systems. The R3 expects an Acknowledgment with XI as the sender partner but we cannot share the same logical system across different Business Systems / services . The easiest solution seems to be to create different partner profiles in R3, one for each Business System / Service. But this is not possible currently.

If the IDOC is sent to 2 different business services/systems/Integration Processes, then it is very logical that an ALEAUDIT be sent for each of these business systems/services. Ideally, you SHOULD NOT look at sending a common ALEAUDIT for different recievers in XI, the reason being, failures could happen only for one receiver and NOT for others. Failure could be in the mapping/content conversion. I am assuming here that you are configuring XI to send back "ALEAUDITs" only for System Error Acks(hoping it is possible, since i see 3 XXXs in the IDXNOALE table).
So, it is logical that you configure a different LS in R/3 for each reciever system/service/IP, all these LS's will have one entry for ALEAUDIT in the Inbound params entered in WE20.
If your intention is to send ALEAUDITs back only in case of errors, it makes sense to create an entry for each receiver in R/3. If not, then it is a limitation.
Regards
Saravana

Same busines system having different Logical system name--- is it possible

Similar Messages

Maybe you are looking for