ALEAUD back to ccBPM

Hello,
I have a scenario like this
WebService -> XI -> ccBPM (Sync-Async Bridge) -> async IDOC to R/3 -> ALEAUD -> XI -> close Bridge -> WebService Response
R/3 sends ALEAUD back to the ccBPM.
I'm sending an IDOC from a ccBPM to R/3 and in R/3 I'm sending the status of the posting via ALEAUD back to XI.
XI takes the the ALEAUD IDOC which is sent via the SM59 to XI and treats it like an acknowlegement for the send step even so my BPM send step has no acknowledgment requested.
My question is: Can I make XI not treat the ALEAUD for the BPM, e.g. configure an outbound async ALEAUD interface to XI? Or if XI treats the acknowledgement how can I get the ALEAUD IDOC data used in my ccBPM, e.g I want to map the stautus back to my web service call.
Cheers
Stefan

Before I ask my questions, please note I do have a copy of the "How To Handle Acknowledgements for IDoc" How To Guide. I just need some clarification from the group.
Here are my questions:
1. XI will not send a positve acknowledgement/status to let the sender system know it made it to XI ok, correct?
2. The only status that XI itself will initiate will be if there is a techncial issue with XI, correct? (Granted the Receiver system could send a positive or negative status back to Sender System) I just want to make sure that XI will not send a status back to Sender System that equates to "Triggering EDI subsystem OK" (or something like that)
3. How does the status of an idoc get set to 12 from 03? Does that mean that I always have the program RBDMOIND configured when I am interfacing to XI in order to force the status from 03 to 12?
4. As a norm, are those who are using XI seeing a 12 status on the Sender System IDoc Status?
5. If a techical issue error occurs in XI, what specific error status will be sent back to the Sender System?(if at all) I am looking for an example status number of what to expect.
6. If we are doing SAP R/3 to a partners XI system directly and that partner does not have RBDSTATE configured on their SAP R/3 environment and there is nothing else on their XI system for ALEAUD processing, I am out of luck in determining if the IDoc actually made it to their XI system, correct?
7. The Configure Scenario 2 in the document How To Handle Acknowledgements for IDoc" How To Guide should allow us to determine "did the Idoc get to that Server" correct?
Thanks for any feedback on this,
Ian

Similar Messages

ALEAUD back to ECC when we have an error in the receiver adapter engine

Hello friends,
My scenario is ECC (async) to SOAP (sync) and back to ECC (async = ALEAUD). I'm using aync/sync bridge is receiver SOAP adapter.
Is it possible to send back an ALEAUD automatically when I have an error in my receiver SOAP adapter? If so can you please explain how to achieve that?
Your help is greatly appreciated,
Thank you in advance,
Kind regards,
John

Hi,
The below reports will helps you to get alerts when any error in target end..
IDX_NOALE - you can configure what kind of acknowledgement you want to request for the send message type. for example you can configure for only error acknowledgements.
IDX_ALEREQUEST - you can configure to send back an acknowledgement as PI message, so that you can control the ALEAUD content by mapping.
Thanks & Regards,
A.Neelima.

ACK_ channel for handling ALEAUD back to ECC system

Hi,
I have created a channel called ACK_Receiver_XI_TO_ECC for sending ALEAUD for all IDOC's that are received from ECC to XI. I also have another receiver IDOC channel for all IDOCs that are sent from XI to ECC. I read in one of the pdf's that when there are multiple receiver IDOC communcation channels, the one starting with Ack_ is chosen to send the ALEAUD. But in my case, in Development and QA system it is correctly picking the Ack_.. channel but in production it is picking the other receiver IDOC communication channel. Any ideas why and how this can be rectified? I have the "Restore original parties.." option checked on the Ack_.. one and not on the other so the selection of the other in production is giving me the "Unable to convert sender service to ALE logical system" error.
Thanks
ram

Hi Ram,
>I also have another receiver IDOC channel for all IDOCs that are sent from XI to ECC. I read in one of the pdf's that when there are multiple receiver IDOC communcation channels, the one starting with Ack_ is chosen to send the ALEAUD
I dont think so, the channel will be determined by the Receiver Agreement. If you have more than one what are valid for a message, that is take which is less generic. For example, if you have 2 Receiver Determinations and you type in the first at Receiver Interface a joker (*) and in the second for Receiver Interface a certain value the second Receiver Determination will determine the channel. This is a general rule for IB objects and allows to create generic rules but having exceptions.
Please compare the Receiver Determinations in the different transport layers.
"Unable to convert sender service to ALE logical system" means, that your sending system has no value for logical system. Control that at Business Component, Adapter Specific Identifier. If the sender is Business System, correct that at SLD and reimport the system.
Regards,
Udo

Sending back Acknowledgement back -Aleaud

Hi All,
I need help on the approach for the Aleaud .Currently the idoc document flows from Sys A to XI to SysB . I need to send back the Aleaud back to Sys B without going through XI( bypass the XI).
Can I use the RBDSTATE program to do it with the variant set to the System to be sent. The problem is the sender information on the Inbound Idoc to SysB will be that of the XI System.Do I need to use a User exit to change this information and populate in the Aleaud. Secondly,one more system will be added to the XI system the path will be the same for the inbound process i.e Sys C to XI to Sys B but in this case the Aleaud will be sent to Sys C.How to differentiate the Idoc's and determine which system to send the aleaud.
Thanks
Alok

This seems to be a standard requirement to send acknowledgement back to the external system which send messages to the web service. How do I listen to JMS topic which persists the messages. On saving I need to initiate a acknowledge message back. Anybody out there with suggestions. Thanks in advance.

CcBPM Correlation - Conversion Id

Hello,
so far, e.g. before SP12 I used the field "conversionid" in my ccBPM to connect two messages together. My scenario is that I receive data for an IDOC from a web service which I send via the IDOC adapter to R/3 and then I send an ALEAUD back to my ccBPM which answers the SOAP call. I use the S/A Bridge for that. ws -> xi -> idoc -> r/3 -> idoc -> xi -> ws.
I used the conversionid which was the same on the sending the idoc and the receiving of the ALEAUD. Now after SP12 it is empty.
What have other people used to correlate two message other then payload information as the ALEAUD does not have a great payload.
I sure could extend the ALEAUD to send the right fields back but I like that the ccBPM has its own connection fields you could use (At least you can select them in the correlation editor).
Thanks
Stefan

Hi Stefan.,
Which of the following is the conversatino id?
versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">
- <SAP:Payload xlink:href="cid:[email protected]">
these are the only id's i can see in header apart from message id. so can you please tell me where and how can i get conversation id??
Thank you
Indrasena

Another BPM question... SOAP-XI-IDOC with ALEAUD Idoc

Hi,
Have a few problems with this BPM.
1- I'm testing my scenario with XMPSpy and when I look at my message in SXMB_MONI, I see the inbound message with the SOAP envelop in one long string. Usually I don't see it and I think this is why my mapping is not working? Do I need to do something special to not see the message with the SOAP envelop? For this, I didn't setup the SOAP as a sender, I only created a web service.
2- The IDoc is being sent to R/3 (not mapped properly because of #1 I think) but the ALEAUD is not sent back to XI. I don't see it as an outbound in R/3 (we05). I did look at the (How to handle Ack for Idoc) but no help. What are the steps that I need to do in R/3 to get the ALEAUD to be sent back to XI? Is the problem with XI or R/3?
What I did so far:
1- Did the setting in my BPM to get an ACK back after sending the Idoc to R/3 (acknowledgement = application)
2- ALE settings in R/3 for outbound ALEAUD
3- I guess my next challenge will be to within the same BPM to link back the ALEAUD back form R/3 to the response of my SOAP call. Right now i get Pipeline timeout condition satisfied. There are a few messages on this subject but i don't think this was ever done successfully? Any help you be appreciated for this.
Rgds,
Yves

> 1- I'm testing my scenario with XMPSpy and when I look at my message in SXMB_MONI, I see the inbound message with the SOAP envelop in one long string. Usually I don't see it and I think this is why my mapping is not working? Do I need to do something special to not see the message with the SOAP envelop? For this, I didn't setup the SOAP as a sender, I only created a web service.
Very foggy description Do you send request directly to PIPLINE ... ?
You should generate the SOAP request based on webservice deifintion (WSDL) e.g. via XMLSpy and you should send it to SOAP sender channel in AE.The payload of your inbound message should be exactly like the one you send from XMLSpy.
Regards,
Jakub

Receiver determination for ALEAUD??

Hi,
I have configured my ALEAUD for a (B2B partner) R3 -> PI (B2b) - > PI (local) - > R3 (local) scenario... I have requested the partner PI system to map their systems to my business systems in their Receiver determination step - header mapping.... But the reverse step of sending back AleAUD is falling in our partners system because of the changed business system names...
I am not able map the ALEAUD back to the original Business sytems used by the partners....Although I have created a receiver aggrement the std Aleaud does not pick it up.
I would like to avoid using the ALEAUD as a seperate message approach.
Regards,
Arvind R

Hi Arvind,
Refer this links. Hope it will help you.
Custom processing for ALEAUD01 messages ??
Re: XML Incoming Invoices - Send response to Vendor for Failed Messages in XI
Thanks.

How to make ALEAUD trigger XI scenario

I've been reading a lot of messages on this but not found good answers to this requirements.
I would like to trigger a XI non BPM scenario when I receive an ALEAUD back from R/3 on FI message type. The idea behind is to read certain fields from ALEAUD segment and to report on them (to remote system).
I configured ALEAUDIT XI IDoc scenario incl map and all but my scenario is not being called or shown in SXMB_MONI or RWB message display.
However I do see Acks being posted for the reference message in question.
Any idea?
THanks,
Pam

Ravi,
ALEAUD IDocs are being triggered in R/3 and they do make it to XI. I see them in IDX5 and also in the ref XI message where it does get posted as Ack. In addition, I have a separate XI interface which takes this ALEAUD, maps certain fields of it and send an email notificaiton to remote system. This scenario IDoc - XI - Mail/fail (tried both) is not happening. The scenario just does not get triggered. Don't see it in RWB message display or sxmb_moni.
Thanks,
Pam

Field E1STATE/DOCNUM is missing! (ALEAUD)

Hello,
I have the following async scenario:
SAP => IDOC-SenderAdapter => FileReceiverAdapter
I receive an Acknowledgment (ALEAUDIT) back from XI to SAP, when the fileadapter has written the file, but field in E1STATE/DOCNUM is missing! In others words, I don't now exactly to which idoc i receive a ALEAUD idoc.
What could it be?
Thanks!

Hi Alexander did you get to solve the problem with the empty DOCNUM field in ALEAUD?
In your first post you stated that you were dealing with an IDoc-to-File scenario but then you mention that JDBC adapter doesn't support acknowledgements. I found that a bit confusing.
I managed to get system acknowledgements from File adapter but the ALEAUD idoc received by R3 is missing some fields (like DOCNUM and STATXT) in E1STATE segment.
Can somebody enlight me with this problem without posting any link (i have already visited all of them without an answer to my question).
Thanks in advance,
Nicolá

Error in ALEAUD Idoc

Hi All,
When i send the MATMAS Idoc from ECC to XI, it is giving success and iam expecting the ALEAUD back to SAP.
If the ALEAUD idoc is posted successfully to ECC means ,the outbound idoc status will be turned into 39 status.Else it is in 03 only
when i check the status of ALEAUD, few of the Status is in 51 and saying the error as
Error when locking the audit statistics for DR2CLNT200 DWMS ZATEMATMAS
Please let me know the solution for this.
Regards

HI Vamshi,
This is a lock issue. When one idoc is trying to update a table and at the same time another idocs come to update it, then it will be locked.
In your case i believe the first ALEAUD got updated with success but when the second ALEAUD is upadting ECC, the third might have also reached thus locking it. If you can add some time delay in getting the response back then it might help with the lock issue.
Hope this helps.
Thanks,
Sudhir

ALEAUDIT with wrong SNDPRN/RECPRN

Hello,
I have setup an IDoc scenario R/3-XI-R/3 which works correctly for sending IDocs and receiving answer IDoc.
The sendinf R/3 system creates the IDoc with
controlrecord:
ReceiverInformation: LI#LF#VEND1
SenderInfo: KU#AG#CUST1
In XI this information is converted correctly on the IDOCRECEIVER to SYSTEM2.
Also the conversion back on the answer messages works correctly and the IDocs are received with the correct values.
Answer IDo (correct converted in IDOCRECEIVER to SYSTEM1):
SenderInfo: LI#LF#VEND1
ReceiverInfo: KU#AG#CUST1
The problem now comes with the ALEAUDIT IDoc.
SYSTEM2 send an ALEAUDIT back, but this header record is not converted, it is received with:
SenderInfo: LS#SYSTEM2
ReceiverInfo: LS#SYSTEM1
I can setup an additional receiver in WE20, but I want to use the existing partner profile for VEND1.
How can I convert the control record of the ALEAUDIT IDoc like other IDocs from SYSTEM2.
Or is this a missing functionality in XI?
best regards
Werner Magerl

Hi Rumi Singh,
The design should be The communication component ( Your file system) should be assigned with a logical system name in the adapter specific parameters. This is because, the logical sender for the data is not XI, but the file system.
Then you have to create the partner profile from this system in your SAP system. This should not be environment specific.
Steps: Create a logical system using SALE transaction
Create a logical system entry in partner profile WE20.
Best Regards,
Ravikanth Talagana

IDOC IDX_NOALE do not sent aleaud for all Busisness sytems/components

Hello,
Does anyone knows if it is standard possible to switch off the ALEAUD acknowledgment for a Business system/component
We have several idocs which are going to 2 business systems, we only want 1 ALEAUD back.
is this possible.
regards Meinhart

hi.
NOALE :
ReliableMessaging SystemAckRequested="false" SystemErrorAckRequested="true" ApplicationAckRequested="true" ApplicationErrorAckRequested="true" SOAP:mustUnderstand="1"
Standerd SAP ALEAUD triggering, logical systems in the 2 business systems.
regards

BPM - IDoc to SOAP problem (Unable to convert sender service)

Hi,
I have a BPM scenario where I'm sending an Idoc from r/3 to XI to SOAP. As part of my scenario I'm sending an acknowledgment (ALEAUD) back to R/3.
I'm getting Unable to convert sender service IP_BPEL_INBOUND_ORDER to an ALE logical system on the Ack back.
So I usually know what to do when I get this, I do the SLD settings on the r/3 service and I'm OK. But in this case, it's asking for those ALE settings on the Integration Process?
I tried adding a logical system on it but now I'm getting the error that this is already used by the r/3 service. So I'm not to sure what to do next???
Rgds,
Yves

Ok do one thing, in you mapping take one field at target side (may be u can create one or use which is not been used yet) just map the standard function called Sender to this field in target.
Now in Intergration Directory when you do the header mapping by using F4 do not map the business systems this time, just press the button "Etended Path" (m not sure abt the exact name of this button) not use the X-Path here and select that target field which you mapped with Sender function in mapping.
How To Handle Acknowledgments for IDoc
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb
I hope this will solve your problem.
Regards,
Sarvesh

BPM IDoc-XI-SOAP

Hi BMP Gurus,
I have a BMP scenario that look like this: IDoc(ORDER05)-XI-SOAP.
Within my BPM, I'm returning a confirmation (ALEAUD) back to R/3 to confirm the SOAP Call. In my ALEAUD Idoc back, I'm mapping some of the original Idoc info (ORDER05).
Now, in addition, I would like to do map some of the Web Service result information back as part of the same ALEAUD Idoc. How can I do that if my Interface Mapping back is defined for the original ORDER05 Idoc to ALEAUD?
Is there a way to link different struc messages in BPM before sending the IDoc back to R/3?
I was looking at correlations but I think this will work for messages of the same structure only.
Rgds,
Yves

Hi,
Hope the below link will give you the answer...
Forum post in Exchange Infrastructure: Idoc Acknowledgements and BPM.
Idoc Acknowledgements and BPM.
Reg,
Srini

Acknowledgments for IDoc

Hi,
In an IDoc-PI/XI-External System scenario, are system error acknowledgments sent back to the SAP sender system when system errors occurred during message processing in PI/XI?
If so, in what forms are the system error acknowledgments?
Thanks in advance,
Francis

Ohhh.. i think lot of confusion
I answered earlier also in terms of non SAP systems. Lets talk only in terms of Idoc
In case of idocs, only receiver system decides whether an acknowledgment IDoc should be sent back to the sender based on the ALE configuration (for ALEAUD). So this would only be possible in Idoc - XI - Idoc scenario. In any of the other scenario u will not get ALEAUD back.
In case of External Sys - XI - Idoc, even if Idoc receiver sends back the ALEAUD, BPM would be required to send back the ALEAUD to external system.
In case of Idoc - XI - External Sys, the system ack sent by the External Sys is converted to an ALEAUD message and is sent back to Sender R3 system
Regards,
Prateek

ALEAUD back to ccBPM

Similar Messages

Maybe you are looking for