Unable to Convet IntegrationProcess in to ALE Logical System
Hi,
I am working on a BPM where i am using the two synchronous steps the process is working fine but iam not getting the Outbound messages and when i cheak in the Acknowledgement xml message its saying that unable to convert integration process in to ALE Logical system is this any thing to do with the IDOC Configuaration
Amaresh
Hi,
If Integration Process/Business Service is used as a sender whilepostng IDocs to SAP System, it will identified by its Logical system name... which can be set in the adapter specific identifiers.
So go to your Integration Process
Menu path : Integration Process>service>Adapter specifc identifiers. Specify the Logical system name.
Check this blog
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
Regards,
Prakash
Similar Messages
-
Unable to Convert Sender Service to an ALE Logical system
Hi,
I am doing a simple SOAP -> PI 7.11 -> IDOC scenario. All objects are created and activated. In testing I get an error
Unable to convert the sender service TemporaryDisconnection_Sender to an ALE logical system
Sender is a Business Service.
I search SDN and found this blog /people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
I did the Compare with SLD for the Business System. But still the error comes.
In mapping I Disable EDI_DC40 segment.
Also find one suggestion which tells to change the Header Mapping in Receiver Agreement, what exactly should I put in Sender Communication Component of the Header mapping?
Thank you,
Pankaj.Hi,
In this thread I could find a solution by Michal: Unable to convert the sender service to an ALE logical system
3. click on sender service (header mapping section) and select your business system that represents XI business system
Will try if it works for me also.
If there are any suggestions, then please do post.
Thank you,
Pankaj. -
Unable to convert the sender service to an ALE logical system
Hello,
file adapter > XI 3.0 > Idoc adapter > r/3 system
In sxmb_moni I receive "Unable to convert the sender service to an ALE logical system".
In we05 in r/3 system no Idocs are arrving. I have no problem with idoc > XI > idoc scenario to this same r/3 system (using same sld business system)
I read other topics on this error but it seems they all talk about an IDOC outbound interface.
What should I check?
Thanks
BoazI do have the same problem as Boaz Paz
When I try :
file adapter > XI 3.0 > Idoc adapter > r/3 system
> This is a B2B scenario where "AVTItalia" is the external party trying to send via its "AwayOrders" business service (a file pickup) an idoc to business system "UPG" (non party service)
I get an error while XI tries to call its IDoc Adapter:
<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>AwayOrders</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert sender service AwayOrders to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
With the following trace logs :
<Trace level="1" type="T">Party normalization: sender</Trace>
<Trace level="1" type="T">Sender scheme external = XIParty</Trace>
<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
<Trace level="1" type="T">Sender party external = AVTItalie</Trace>
<Trace level="1" type="T">Sender party normalized = AVTItalie</Trace>
I ve tried to (cf. /people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc ):
1. add a logical system name "ACYAVTFBC1" in "Adapter specifier Id" of "AwayOrders"
In the runtime cache > services an entry appears for " ... Logical System | AVTItalia | ACYAVTFBC1...".
2. declare "AVTItalia" as a business partner in SLD with the logical system name
Plz help! -
Hi All,
File to IDoc scenario.
1. Business system is correct because its working for other scenarios.
2. I checked Adapter Specific attributes in Business service and given Partner number which in maintained in WE20 for the partner in R/3.
3. Refreshed cache.
But still... its showing the below error.
<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>BS_PARTNER</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert the sender service BS_PARTNER to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Any idea what might be wrong?
Regards
Deepthi.Hi Experts,
Could you please help me to fix this.
SCENARIO: SAP - IDOC -
> XI -
> SOAP Adapter (Webservice)
Workaround:
1. Verified Adapter Specific configurations and its fine with same Logical system in SLD and ALE service.
2. Header mapping in Receiver com channel : Sender service and Receiver Service is assigned
3. Identifier Tab in comm channel details: Its empty - no values.
SXMB_MONI :
Error Details:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
<SAP:P1>CAPTOR3_PRU</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert sender service X12345X to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks in Advance,
Sunil. -
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. -
Unable to convert the sender service PPG to an ALE logical system
Hello all,
maybe anybody can help or give me further information.
I have set up a scenario to send IDOC from a business system ( ERP ) to a business service ( EXT ).
Receiver is a linux system so I use the FTP-FILE adapter as communication channel.
The send-process is so far ok.
Here my tests:
1) exclude the specific IDOC in IDXNOALE table ( means no technical acknowledgment for this IDOC )
result :
a) message in SXMB_MONI: status-flag: processed, acknowledgment-flag: not in use
b) message in RWB-Monitor: Sender ERP --> Receiver EXT ok
2) But I would like to have a system status..... here now the problem
add specific IDOC into IDXNOALE table ( for request acknowledgments )
result:
a) message in SXMB_MONI: status-flag: processed, acknowledgment-flag: acknowledgment not possible
--> error message: unable to convert the sender service EXT to an ALE logical system
b) message in RWB-Monitor: there are now two message,
first: Sender ERP --> Receiver EXT = ok
second: Sender EXT ---> Receiver ERP = system error
Receiver-Interface is : http/ww.ahlstrom.com/EXT/ MI_IN
3) furhter tests:
a) change FTP apdapter channel ( put some wrong settings )
message in SXMB_MONI: status-flag: processed, acknowledgment-flag: contains system errors
message in RWB-Monitor 3 messages ( one ok, and two error messages )
b) changed only the receiver communication channel to HTTP ( other extisting scenario )
then the acknowledgment works fine wihout errors.
I'm wondering, but here Receiver-Interface is: http://sap.com/xi/xI/Message/30/Acknowledgment
Summary: The process works, but strange:
message in SXMB_MONI: unable to convert the sender service EXT to an ALE logical system
message in RWB: system error
No problems with HTTP adapter
Regards,
Reinhard DoekerHi,
Addition to the above said by Udo...
for routing the ack back to the sender system you need to create communication channel of type idoc with name as Ack.....
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe?quicklink=index&overridelayout=true
Check the above link section 3.2
HTH
Rajesh -
Unable to convert sender service(BPM) to an ALE logical system
Hi All,
I am working on simple File to File Scenario where XI picks the File and process thru BPM and sends the file to R/3 Application server and wait for SYSTAT STATUS IDoc for the acknowledgement from R/3 System.
My scenario is working fine by receiving the STATUS IDoc and closing the BPM instance.
But later I am getting System error message as below:
Unable to convert sender service (BPM) to an ALE logical system
Any clues in this case?
Thanks in Advance.
Regards
Sudha.Hi Rajesh,
1. I am receiving the file into BPM and after validation Iu2019m splitting the file into multiple files.
2. Each split file sent to R/3 Application Server(by activating the correlation with the filename)
3. BPM will wait for SYSTAT STATUS IDoc (by using correlation with the filename) from R/3 System
for acknowledgement purpose. After receiving the respective STATUS IDoc (with the filename) then
BPM will close the instance.
4. If the STATUS IDoc not received with in specified duration an alert will raise and close the BPM
instance.
So we are not sending the STATUS IDoc data to Sender system.
Regards
Sudha. -
Unable to convert the sender service ABC_Service to an ALE logical system
Hi,
I have a JMS (Party) --> PI --> IDOC scenario.
Party: ABC_Party
Service: ABC_Service
I am getting the error Unable to convert the sender service ABC_Service to an ALE logical system when I test the scenario using RWB -> Component Monitoring -> Integration Engine -> Test Message.
I have already done the below settings:
1) Defined Header Mapping in Receiver Agreement for IDOC (Sender Party, Sender Service and even Receiver Service are specified)
2) Business Component (ABC_Service) -> Adapter Specific Identifiers -> mentioned details for SAP (IDOC) system.
The scenario works perfectly fine for a party-less communication JMS -> PI -> IDOC
Have already seen:
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/rajeshkumar.pasupula/blog/2009/03/16/unable-to-convert-the-sender-service-to-an-ale-logical-system
Thank you,
Pankaj.You need to create party if its a B2B scenario
Under Identifiers
under agency select any standard agency , scheme name will automatical;ly get populated and name you can give manually as sender name
Please refer this for more details
http://help.sap.com/saphelp_nwpi71/helpdata/en/b9/64663c7a6c2545ae292fb26d8c33c4/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/81/104bb1fbab254c8644877c7f856bbf/content.htm
Re: Party Configuration
In case of cross company process it is required
Regards
Ninad
Edited by: Ninad Sane on Nov 18, 2010 11:17 AM -
Once again: Unable to convert sender service to an ALE logical system
Hi,
I know there's a lot of threads regarding that error but I didn't find one that fits to our current scenario:
IDoc -> XI -> File
We have checked if the logical system name in SALE (of sending system) fits to the one in the business system and it does now.
It didn't fit at first but we've changed it in the SLD and reimported the business system.
We still get the same message:
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
<SAP:Stack>Unable to convert sender service to an ALE logical system</SAP:Stack>
There is no logical system entered in the receiver business system. Do we need that? But of which logical system?
Thanks for any advice
KarstenHi,
Acknowledgments
Receiver adapters that run on the Adapter Engine support system acknowledgments if they are requested by the sender.( Ex : Idoc----File). Here by default Idoc has the inbuilt feature of requesting the Ack.
Acknowledgments are triggered when a message is successfully processed by the adapter or if an error occurs while it is being processed. Receiver adapters do not support application acknowledgments.
Sender adapters of the Adapter Engine do not request any acknowledgments
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb
Regards
Seshagiri -
Unable to convert the service as an ALE logical system
nHi to All..
I'm facing a problem in one scenario IDOC to RNIF. I got this problem "Unable to convert the sender service to an ALE logical system. In that Interface is working properly but the thing is Acknowledgement is showing error and when I was triggring the IDOC from ECC at the time message Data Receiving successfully but coming to Acknowledgement Am getting ERROR. Any one can please do the needful for this.
Note:- Sender is Business system and Receiver is Business Service
Thanks and Regards
SrinivasHi srini
Receiver System is SEND the acknowledge to ECC here only we are facing the problem
help me uderstand correctly ...
your asyn interface is ECC(sender)-to- Bservice receiver .(works fine)
now Bservice (sends an ACK)- to -ECC (receiver) - do u have other asyn interface for this .. must be.
if not this means you are trying out sync scenario in which you are expecting the ack to go back to ECC syn (which i think not possible or u need to use BPM as the idoc interface will be always asyn).
try giving the LS name in the Bservice , not in the Bsystem as you mentioned.or
open your receiver agreement and select header mapping - Sender service
choose your PI's business system
Regards,
Srinivas -
Unable to convert sender service BPM_Name to an ALE logical System
Hello ,
While sending from BPM to R/3 ( IDOC) i am getting the following error :
"Unable to convert sender service <BPM_Name> to an ALE logical system"
Please kindly advice,
ReddyHi Bujji,
I just remembered that you have to maintain your adapter specific parameters for your business process. The side effect however is that you have to define the business process name as logical system in your receiving SAP system and that you have to maintain partner profile settings.
The answer to your question is there in this Blog:
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
If the above solution doesnot work.....
You can also try this, don't enter the "adapter specific settings" on the Integration Process. Instead enter a "Header Mapping" Sender Service in the Receiver Agreement. this should be the real sending system.
When you enter "adapter specific settings" in a BPM, the receiving SAP systems ALE layer thinks the sending system is your BPM - using the method discussed here we are overriding that so that ALE see's that its communicating with the real sending system.
I hope it helps....
Regards,
Abhy
Message was edited by: Abhy Thomas -
Unable to convert sender service IP_testScenario to an ALE logical system
i have a IDOC -> BPM--->File scenario,
the BPM is named as IP_testScenario
when IDOC is sent from R3 to BPM, in the MONI i can also see a Acknowledgement message saying
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
<SAP:P1>IP_MMWIS016_01</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert sender service IP_testScenario to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
why this happens...........pls helpHi..
For Sender you have to create the TS of Type Web AS ABAP right..
While assigning your Bs in ID...Double click on your BS , Goto Service--> Adapter Specific Identifiers..
Hope it helps...
Kumar.S -
Problem Unable to convert the sender service to an ALE logical system
Hi to All..
I'm facing a problem in one scenario File to Idoc .. I got this problem
"Unable to convert the sender service to an ALE logical system" in pipeline Call Adapter.
I check this blog but the problem persist . /people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
Also I have another scenario in other Software Component Version SCW and the Idoc works correctly..
I wonder if I miss something
this the trace
<Trace level="1" type="T">----
</Trace>
- <Trace level="1" type="B" name="CL_IDX_IDOC_SERVICE-ENTER_PLSRV">
<Trace level="1" type="T">Pipeline Service ID: PLSRV_CALL_ADAPTER</Trace>
<Trace level="1" type="T">Get Information from IS-Header Objekt</Trace>
<Trace level="1" type="T">Get Information from SD-IDoc-Endpoint</Trace>
<Trace level="1" type="T">Sender and Receiver after Header-Mapping</Trace>
<Trace level="1" type="T">Sender service Sys_XXX</Trace>
<Trace level="1" type="T">Receiver service Sys_EDV_XXX</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
Edited by: Luis Ortiz on Jan 25, 2010 3:37 PMHi,
in order to use only one logical system (PI's) in we20 in ECC and not as many as you have sender systems
Regards,
Michal Krawczyk -
ERROR"Unable to convert sender service to an ALE logical system,(Urgent)
Hi All when i am not giving the sender service address in the Receiver Aggrement i am getting this perticular error .
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <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_IDOC_METADATA</SAP:Code>
<SAP:P1>Transaction IDX1: Port SAPRP1, client , RFC destination contain errors</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: Transaction IDX1: Port SAPRP1, client , RFC destination contain errors</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
==========================================
And if i am giving this one then i am not getting any such error rather i am getting another error "Unable to convert sender service to an ALE logical system" for this also i have checked the LS system name in the Adapter specific Identifier and the logical name are exactly same. But still i am getting this error
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <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>
=============================================
Still i am getting this error can anyone please let me know what to do now..??
Please treat this as urgentHi,
This error is caused when Sender System name does not match the logical system name of partner. As you mentioned you have done all the steps to ensure that, here's a checklist that could be helpful:
1. Check adapter specific parameters for sender system.
2. Maintain header mapping in receiver agreement and ensure that sender service name provided is same as business partner name required in R3 and business partner type is LS.
3. This may sound very basic, but ensure that checkbox for 'Apply control record from payload' is not checked and if it is then the values passed through payload are appropriate.
Hope this would be helpful.
Thanks,
Bhavish -
Error "Unable to convert the sender service to an ALE logical system"
Hi,
I send I message from XI to R3 and I get the error "Unable to convert the sender service to an ALE logical system" in transaction "sxmb_moni". I've configured the idoc-adapter, as following:
-I have created a business system "r3sys_bs" with a logical system "r3system". This business system is the idoc-adapter. This logical system is also created in transaction "bd54". In the ID I have assigned the business system the logical system (adapterspecific identification).
So, this error still appears.
Can anybody help me please?
Regards
StefanHi,
our scenario is JMS --> XI --> IDoc
so, I have created a business system "jms_bs" without a logical system in sld, that I use for the jms-connection to another software. so, the business system is a "third party".
Then I have created a business system with assigned logical system for the IDoc-Receiver as I in my first posting mentioned.
Which of both business systems need a logical system?
Thanks
Regards
Stefan
Maybe you are looking for
-
I use Microsoft Word 2010 with Windows 7 and IE8. Yesterday I updated my Adobe Reader to 10.1.5. I have numerous Word documents that have hyperlinks to pdf documents in them. Now when I use Word to convert these Word documents to pdf, the links in th
-
Deleting Lightroom 1.4 after loading 2.2
I have loaded Lightroom 2.2 into my computer and still have 1.4 on the harddrive. Should 1.4 be deleted?
-
Unidentified error connecting to MySql
I'm almost embarrassed to post this question because there seems to be plenty of the same issue already here. On the other hand I'm not as embarrassed as the developer who created such a useless message as "unidentified error" .... but that's another
-
Documentation generator for Forms 6i
Does a tool exists to document the code on triggers and procedures in Forms 6i files? For every single form , a program unit called p_documents is created, with no code to write the documentation in comments .. something like this .. Procedure p_docu
-
Is it possible to set what is determined as whitespace by a JTextArea
I have the code: JTextArea doc = new JTextArea(text); doc.setLineWrap(true); doc.setWrapStyleWord(true);now doc.setWrapStyleWord wraps the text if the word is too long to fit on the current line, it uses whitespace as word seperators. now i want to s