IDoc Adapter Logical System Empty

Hello All,
For one of our scenarios for Reciver IDoc adapters we are getting the error "Receiver service cannot be converted into an ALE logical system ". On further investigation it seems the logical system stays on editing the Adapter Specific Message attributes option & even after clicking the Compare with SLD Option. Can you please assist us with this issue ? Also sldcheck runs fine but sldapicust gives an error CIM_ERR_FAILED. We recently upgraded our sld and we believe this might be the issue.
Thanks,
Kiran

Hi Debashish & Veera,
The issue has been resolved. When our SLD was migrated to a newer version 1 month ago back our logical system names got cleared. We did not face this issue until yesturday since the logical system names were still cached with the business system. Yesturday a newer IDoc scenario was imported in production and which caused the business system cache to be refeshed and it started pulling the new empty logical system name causing the scenarios to fail.
Thanks,
Kiran

Similar Messages

IDoc Adapter - Logical System - File to IDOC configuration

I have a scenario reading a File ->XI->IDoc in R/3. I'm looking to have the control record parameter for SNDPRN reflect the Environment dealt with. I unchecked the 'Apply Control Record Values from Payload' & 'Take Sender from Payload' boxes but the problem I'm getting is that the system is reading from the business service (IDoc Adapter - Logical System) and feed it in the Partner Profile in the IDOC. This means that I should all the time redefine 3 this Logical System in config before transporting my scenario from DEV/QA/PRD. Any idea how I can avoid this kind of 'hardcode' ?
Thanks

Hi,
Why u r using three different LS can't u use only one LS and send all the IDOCs to same LS. That will ease ur task.
Do let me know why u r going for three different LS.
In the file r u getting any data which will help u to identify that this file is for which LS. IF that is the scenario then u can use the value mapping and based on the value which is coming in file u can map it to the IDOc filed which u have mentioned and in the configuration it will take the respective configuration.
Thnx
Chirag

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

IDOC to Logical System

Hi all,
Can I send an idoc from development(301 client) system to the LOGICAL SYSTEM of the same development(301 client) system?
If I do so, i see the status as '29' i.e 'Receiver of idoc is its own logical system'..
Is there any solution to avoid the above message?
Thanks,
Faraz

Hi,
To avoid this message 'Receiver of idoc is its own logical system', you have to use a other client which is not in the DEV box.
Better use some quality Box client.
But it should work even if you use two different clients of the same box.
create separate Logical systems in two clients and do other settings also in both the clients and do.
reward if useful
regards,
Anji

Hiow to download idoc to logical system

Hi ,
How to download idoc (invoic02 ) to a logical system , when a sale order is created .
after downloading how to convert to xml message.
can any one help me out how to do this .since i dont have any prer knowledge on idocs little bit elobrate will be helpfull.
Thanks ,
Vinay .

Hi
Go thru the bellow links.
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400365
Idoc's
http://www.thespot4sap.com/Articles/SAP_ALE_IDOCS.asp
Thanks
Sunil

How to download idoc to logical system

Hi ,
How to download idoc (invoic02 ) to a logical system , when a sale order is created .
after downloading how to convert to xml message.
can any one help me out how to do this .since i dont have any prer knowledge on idocs little bit elobrate will be helpfull.
Thanks ,
Vinay .

Hi
Go thru the bellow links.
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400365
Idoc's
http://www.thespot4sap.com/Articles/SAP_ALE_IDOCS.asp
Thanks
Sunil

One Idoc -- One Logical System ?

Hi everyone,
Right now i'm developed 6 interface using idoc (6 different business process). Do we need create logical system for each interface? Or just only one logical system? If we have success create this interfaces, how to transport this setting (logical system,rfc destination) to production system ? Thank you.
Regards,
Satria

Satria,
In R/3:
1. Logical System are careated only once. If there is a requirement then only they will be created by using tcode SALE (it's not so frequent).
2. You can see all logical system by using Tcode "BD54".
Note: In DEV, QA or PROD system, you will not be having authorization to create any logical system.
So, while doing outbound processing you can reuse the same logical system.
If still you have any doubt, kindly let me know.
Kindly set the thread to "Answered", once you get your final ans.
Regards,
Sarvesh
*****Reward points, if found helpfull.
Message was edited by:
Sarvesh Singh

Sending IDoc to Logical System

Hi All,
Foremost thing before i post my query is that am an ABAP Developer.
Now the Query is, we have scenario where in we need to send the Sales order/Delivery when it is created to a logical system( an external sytem ). I have created a new message condition type which has the transmission medium as 6 ( EDI ) and the partner to be of type LS (Logical Sytem). I have also defined the partner profile of the logical system with this message condition type. But the problem is when am issuing an output am not able to see my logical system as on of the options as a partner, the options what i have are the Ship to Party, Sold to Party and so on from the sales document.
I need to know how can issue and idoc to a logical system instead of a ship to party or a sold to party. Is there anything that am missing while creating the message condition type ?
Regards,
Chaitanya.

Hi,
Have a look at this, it may help
http://help.sap.com/saphelp_47x200/helpdata/en/2d/b12d3b1daca008e10000000a114084/frameset.htm
http://help.sap.com/saphelp_47x200/helpdata/en/4c/df7e98f0dd11d2b74b0000e8160175/frameset.htm
http://help.sap.com/saphelp_47x200/helpdata/en/dc/6b7cac43d711d1893e0000e8323c4f/frameset.htm
If you just want to send delivery information use output type LAVA. This will need including in the shipping output determination.

ALE logical system - File -- XI -- R/3 scenario

Hi
I have the following scenario which I'm trying to run.
File --> XI --> R/3 scenario.
I have created a sender agreement XID|ASN_out|NBD where XID is my XI 3.0 system and NBD is my R/3 system. I have also created an interface determination and receiver determination.
The following error is in transaction SXMB_MONI in my XID system:
"Unable to convert the sender service to an ALE logical system"
Both XID and NBD are business systems defined in SLD and they have both a logical system assigned.
Why do I get this error and how can I fix it?
Best regards
Göran
Message was edited by: Göran Westin
Message was edited by: Göran Westin

Ok. I fixed the problem.
In the Integration Builder - Configuration > Select business system of choice > Menu > Service > Adapter specific identifiers > IDOC Adapter > Logical system - got a value after reading/refreshing it from the SLD.

Problem converting Integration Process to ALE logical system(acknowledgmen)

Hello,
I have a scenario where a sender SAP system sends an IDoc via an Interface Mapping to an Integration Process.
This worked perfectly fine on our development environment, but after transporting the scenario to our quality systems I got the following acknowledgement error:
Unable to convert the sender service name of integration process to an ALE logical system.
What could be the reason for this? We have a logical system on the sender SAP system set up for the XI system itself but not for the Integration Process.
We also use SYSTAT IDocs and there we set the the logical sender system name to the logical system for SAP XI and not for the integration process.
Is this also necessary for acknowledgements? Where could this be done. Strange thing is that it works perfectly fine on our development environment.

I raised the same question a few months back.Answer to this question is in the same thread.
Idoc Acknowledgements - Logical System Name
You will have to select option "Restore Original Parties for Idoc Acknowledgments " in the Acknowledgment Idoc adapter.
Regards
Bhavesh

Logical System in IDOC-XI scenario

Hi,
I need help to understand few things in IDOC-XI scenario, could any one help me in this regard.
we use Adapter specific identifiers to map services, we have following type of identifiers 1) Sys.ID & Client No. 2) Logical System.
my questions are
a) Are we use Logical System in B to B scenario ?
b) Are we use LS in reference to the SAP system or Non SAP system ? if a non SAP system....how a non SAP system send an IDOC and why a non SAP system receive an IDOC ( conversion is possible in XI ) ?
Thanks and Regards
Mahesh.

Hay Kumar,
Logical systems can also be used for SAp sytems wich are not installed yet as a virtuall placeholder.
a) yes. if on of your business is a non sap system or a propritery system that you developed yuo'll ue LS.
b) non SAP system can send and recieve IDOCs. so it's possiable to get an IDOC from a system and turn it into an RFC for SAP or get an IDOC from an SAP system and then turn it into something else for another system.
Have a Good One,
Uri Lifshitz.

Logical System in file 2 idoc

Hi
I am developing an scenario of file to idoc.
My problem is, when it is generating the idoc in target system, the Parner Number in control record is filling with the logical system name given when creating the business system.
I tried changing the logical system name with actual partner number which I want but giving an error ' The selected integration server already has a business system with logical name "pidclnt001". Select a different integration server or change the logical name. '
Can anybody advice me, is it not possible to create two scenarios to send same Idoc to same system ?
Regards,
Shylesh

Hi Shylesh !
You need to enable the header mapping option in your receiver agreement to overwrite the Logical System name that is sent to the R/3 destination system...which now is the Logical System name linked to your sender system (info is in SLD if is a business SYSTEM or in the Adapter Specific identifier attributes if it is a business SERVICE)
You cannot have more than 1 business service/system with the same Logical System name...but you can overwrite the sender logical system name that arrives to the destination R/3 system using the header mapping section of the receiver agreement as noted above.
Regards,
Matias.

SOAP to IDOC: Unable to convert sender service BS to an ALE logical system

Hello everyone,
I have this scenario where i receive web services calls and have to integrate the received xml messages (idocs) into SAP R3 system.
I allready reveive the message in my XI engine, but i'm getting this error (being BS the name of my Business Service included in my external party):
"Unable to convert sender service BS to an ALE logical system"
I allready tried everything that is specified in this blog:
The specified item was not found.
Probably it doesn' fit my requirements. I'm not sure...
Can anyone help ?
Thank you in advance for any help
Nuno

- do u have the same logical name defined in the BS and in the Adapter specific attributes.
also check if u have defined the logical system (SALE ) with the same name.

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

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

IDoc Adapter Logical System Empty

Similar Messages

Maybe you are looking for