IDOC sender: Error in Logical system name?

Hi,
In my current project, the IDOC sender system logical name is P2PCLNT100 but the SLD system name is P2P.
Its an IDOC to proxy scenario. At the receiver system side, the schemeAgencyID is getting populated at P2P and not P2PCLNT100, due to which there is an error on the receiver's side.
Following is already checked:
1. SLD has maintained the proper logical system name for the P2P system
2. The IDOC xml on the XI system has the sender port properly populated as P2PCLNT100
3. I have also debugged the program on the receiver side and fails at a point where it checks the logical system name from the database BBP_BACKEND_DEST.
On the receiver system, the followed error is shown as follows:
- <STANDARD>
<CONTROLLER />
<FAULT_TEXT>An error occured within an XI interface: SLD system P2P is not known Programm: SAPLBBP_BD_MAPPING_SAPXML1; Include: LBBP_BD_MAPPING_SAPXML1F1Y; Line: 96</FAULT_TEXT>
<FAULT_URL />
<FAULT_DETAIL />
</STANDARD>
Thanks in advance for the useful answers.
Sowkhya

Hi,
1. R/3 system's logical system name and SLD business system's logical system name has the same.
Is there a need to have the business system name in SLD to have the same name as R/3 system logical name?? As far as my knowledge goes, business system and logical system need not have the same name. Correct me if in the case IDOC sender scenario is different..
2. SLDCHECK shows following message:
Summary: Connection to SLD does not work
The issue still persists. Will SLDCHECK correct solve the issue?
Regards,
Sowkhya

Similar Messages

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

Logical System Name of an Idoc Sender

Hi,
I have seen that For Idoc senders the the Logical System name associated with the sending Client has to be SAP+System Id(For example SAPE05 where System Id = E05).
Is it mandatory? If so how can I have multiple clients in a sender Idoc systems sending data?
Regards.

The logical system nameing convention is:
<System ID>CLNT<Client>.
If your system is ADM, client 070, the name would be:
ADMCLNT070.
Regards,
Jason

BI Error Logical system name has been changed for this system

Hello All,
I have installed the BI system and did a client copy from 000 to 200 client with profile SAP_ALL.
Now I have loged into the system with client 200 and wen I run RSA1, I am getting the following error
message: "Logical system name has been changed for this system"
Thanks
Sekhar..

Hi,
Goto tcode SCC4.
Switch to change mode. (System will prompt that this table is cross client. Continue)
Select your client (in this case 200). Click on details button (next to change mode button)
Enter the proper logical system name in Logical system field.
Click on Save button.
Then try RSA1.
Hope it helps
regards,
Pruthvi R

Problem with logical system name

Hi All
We are facing problem when connecting Ecc 6.0 and BW
When i execute the RSA 1 transaction, i am getting the following error:
Logical system name has been changed for this system
I raised this issue to SAP.
I got the following reply:
Please see if the RSADMIN table has the correct logical system in BW.
If the logical system name here is incorrect, use report
sap_rsadmin_maintain to change the logical system name.
We reffered the Table RSADMIN, but couldnt identify which field has got logical system name.
Then we executed sap_rsadmin_maintain program in se38, but dont know what to enter in value and object field.
Can anyone help in this regard
Thanks in advance
Regards
Rak

Hi Lars,
I would start RSA1 in debugging mode. Try to establish which check is giving you this message by e.g. trying to set breakpoint at message.
Like this you can at least check which entry must be converted in order to be able to proceed.
Best regards,
Olav

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

Filt to IDoc: cannot convert sender to ALE logical system

Hi there,
i have used forum search for my issue, but could not figure out the issue by myself so far.
I tried to read a file into PI 7.0, map to and IDoc and send IDoc to SAP system. I have the following configuration:
Sender: SYSTEM_A
---Logical System <none>
Receiver: SYSTEM_B
---Logical System: EIECLNT300
the IDoc i'm sending looks like this (most of them dummy values):
<?xml version="1.0" encoding="UTF-8"?>
<ORDERS05>
<IDOC BEGIN="value2">
---<EDI_DC40 SEGMENT="value2">
<TABNAM>value2</TABNAM>
<DIRECT>value2</DIRECT>
<IDOCTYP>value2</IDOCTYP>
<MESTYP>value2</MESTYP>
<SNDPOR>EIECLNT300</SNDPOR>
<SNDPRT>value2</SNDPRT>
<SNDPRN>PITCLNT001</SNDPRN>
<RCVPOR>value2</RCVPOR>
<RCVPRN>EIECLNT300</RCVPRN>
---</EDI_DC40>
---<E1EDK01 SEGMENT="value2">
---</E1EDK01>
</IDOC>
</ORDERS05>
PITCLNT001 is the logical System name of PI. Do i need to configure "PITCLNT001" as logical system at SYSTEM_A (besides, thats not possile)?
regards,
MS
Edited by: Manuel Schlestein on Jan 28, 2009 10:39 AM
Edited by: Manuel Schlestein on Jan 28, 2009 10:40 AM

Hi
Create a logical system for SYSTEM_A in SLD (you can give some string) and create that same logical
system in IDOC side (SALE).
Thanks
Prasad Nemalikanti

Stuck with logical system name for JDBC Sender system!!!!!!!!!!!!!

Hi All,
I'm doing a scenario as JDBC2FILE.
I tried to add my jdbc sender system to SLD. So i created the technical system
now i'm creating business system...what should i give at logical system name tab? I've created tech system and business system as third party.
do we need logical system name in this scenario where we are not interacting with any R/3???
can anyone suggest the way to achieve this scenario?
Thanks in advance.....
Santhosh.

Hi Santhosh,
I just want to add ons..few more information which it might help you.
You no need to give logical system when you are using Thirdpaty.
Please check the below blog you will get more idea how to proceed to achieve the JDBC Scenario.
/people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30
If you have any doubts while proceeding with your scenario plesae let me know..I will try my level best.
Thanks and Regards,
Chandu

Where to define third party logical system name in file to idoc scenario

Hi Friends,
I am shalini shah.
I have one doubt, where I can define the logical system name in File to Idoc scenario.
I created Logical system for R/3 system in SALE t.code, but where to define the Third party logical system ,
In SALE or any where.
Please give me solution.
Warm Regards,
Shalini Shah

Hi Shalini,
You need to create Business system in SLD and import the business system in ID.Then u will start with the configuration.
Just refer the below link for configurations with step by step solution.
File To IDOC - Part1 (SLD and Design):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
File To IDOC - Part2 (Configuration):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
File To IDOC - Part3 (Steps required in XI and R3):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
Thnx
Chirag

IDOC error - Receiver of IDoc is its own logical system

hi,
i have a requiremnt to generate the IDOC for the same and same client. actually i have to get the data from application server and i have to generate the IDOC.
for this i have created a Zreport and passed the data from application server to segment and i called the
FM "MASTER_IDOC_DISTRIBUTE". after executing the Zreport, IDOC is generated and show the error
status as 29.i.e. Receiver of IDoc is its own logical system.
my logic is as follows.
MOVE 'LS' TO w_edidc-rcvprt.
MOVE 'SBECLNT130' TO w_edidc-rcvprn.
MOVE 'ISU_MR_UPLOAD' TO w_edidc-mestyp.
MOVE 'ISU_MR_UPLOAD01' TO w_edidc-idoctp.
pls let me know the solution for this problem.
Regards,
Balu

Hi Reddy,
please let me know how did u solve this issue, even i have the same requirement and am gettign status 29.
Thanks
Rakesh

ERROR B191 - IDoc has its own logical system as receiver

I everybody, i'm tryng to execute a package to charge a ODS from another ODS (Datamart) but the process ends with the error "IDoc has its own logical system as receiver", can you help me with is?
What should be the reason for this error? What can i make to solve it?
Thanks to all

Hi Reddy,
please let me know how did u solve this issue, even i have the same requirement and am gettign status 29.
Thanks
Rakesh

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

RSA1 error Logical system name has been changed for this system

Hello All,
Earlier the RSA1 was activated for client 300 on our crm 5.2. after that we changed the client to 500 using SE16 -> Type table RSADMINA / Check Colum BWMANDT -> 500.
But now when we login to client 500 and execute RSA1 it is showing
Logical system name has been changed for this system"
In scc4 we have not made any changes. Can you tell what should be done ? in the pop up it is showing following steps
Change the name of the logical system (table T000) for client back to SIDCLNT300. This enables you to continue working with the system.
If you really want to change the logical name, than you can, if and when you:
change the system name back to SIDCLNT300,
delete all existing connections between this system and other systems,
delete all transfer structures that still exist, and
do not use ALE or Workflow.
Guys do you know how to fix this ? .
Also do you know Assignment of Source System to Source System ID (table RSSOURSYSTEM) using RSA1 ?
Edited by: Sahad K on Mar 17, 2008 10:55 AM

Hello Hari,
Both the options you said cannot be used
since the logical system SIDCLNT300 is used by client 300 and it cannot be given to client 500. Also there already exist a logical system SIDCLNT500 which is assigned to client 500.
I found out the issue. In the table RSBASIDOC the logical system name that can use rsa1( bw client )is set as SIDCLNT300). Only if we delete that entry and set it to SIDCLNT500 ( 500) we can use it on client 500.
The solution is specified in /message/3284842#3284842 [original link is broken]
Let me try the solution 2 and inform you.
Solution 2:
You cannot delete the source system. Two cases have to be distinguished:
The source system still exists.
Switch to Transaction SM59. Find the destination which has the same name as the logical system of the source system from field SLOGSYS in table RSBASIDOC (see above).
Such a destination does not exist in Transaction SM59. In this case, you have to create the destination to the source system. Name the destination equal the entry in SLOGSYS from above. Then return to the Administrator Workbench and repeat the deletion.
The entry exists but a remote login is not possible. Correct the communication parameters.
Everything works. Change to Transaction SE37, function module RSAR_LOGICAL_SYSTEM_DELETE, Sngl. test. Parameter I_LOGSYS = <log. name of the source system>, I_FORCE_DELETE = 'X'.
The source system no longer exists or was replaced with another source system with the same IP address.
Proceed as described in the first case but make sure, that the field 'Target host' contains a not existing server in the maintenance screen of the destination (Transaction SM59). If necessary, change an existing entry. Later when you delete, the system asks you whether you want to delete, although the source system is not available. Select 'Ignore'.
Incase you have any idea other than this please let me know how to edit the RSBASIDOC table and change the entry to client 500.
Edited by: Sahad K on Mar 18, 2008 5:07 AM

Logical system name for acknowledgement in BPM

Hi,
I have a szenario:
IDOC --> BPM --> MAIL
Inside BPM I check the message and depending on an xml-element I stop the process or I send the message by mail.
When I stop the process the BPM sends back an acknowledgement and in SXMB_MONI I can see an error of the acknowledgement:
"Sender Test_BPM_IDOC_TO_MAIL kann nicht in ein ALE Logisches System umgeschlüsselt werden" (Sender can not convert in a ALE logical system)
What can I do?
Possible Solution 1:
I can define my BPM "Test_BPM_IDOC_TO_MAIL" as a logical system (including WE20 for ALEAUD).
Possible Solution 2:
I can enter an existing logical system name in the "adapter specific attributes".
BUT it is not use the same logical system name twice (BAD ... or is there a workaround?
Is Solution 1) a common way?
Thanx
Regards
Wolfgang Hummel

Hi,
there are many ways:
some for aleaud are described in my book:
<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>
>>>>Is Solution 1) a common way?
no this is not good a good idea
BTW
you can also supress aleaud raport IDX_NOALE
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

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

IDOC sender: Error in Logical system name?

Similar Messages

Maybe you are looking for