ALEAUDIT IDOC FROM R/3 AS ACKNOWLEDGEMENT TO XI IDOC

Hi,
I am working on one XI scenario in which XI is sending one CREMAS Idoc to R/3.In R/3 this is an inbound Idoc which has process code CRE1.
Now In XI I want that whenever this IDOC get posted successfully in R/3,it should send one ALEAUDIT idoc to XI as an acknowledgment for sent idoc immediately.
   How should I configure all these things in XI and in R/3?
   I read that I will have to schedule a job in R/3,but how should i schedule job which will send immediate ALEAUDIT idoc to XI after successfull posting of CREMAS idoc?
    Please guide me.

Hi ,
Check these docs...
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
https://websmp210.sap-ag.de/~sapdownload/011000358700003477212005E/HowTo_IDOC_Ack_20040817RR.pdf
sekhar

Similar Messages

Problem with ALEAUD IDOC

Helo everybody
We have this scenario:
JDBC>PI-(IDOC)---->SAP
SAP(ALEAUD IDOC)>PI----->JDBC
But we cant recive the Aleaud Idoc in PI. We get this 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="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_NO_REQUEST</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>ALEAUDIT IDoc cannot find request IDoc in Integration Server</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Anybodoy knows what´s happenning and how to solve it????
Thanks a lot

Christian Abad Chico wrote:
> Helo everybody
>
> We have this scenario:
> JDBC>PI-(IDOC)---->SAP
> SAP(ALEAUD IDOC)>PI----->JDBC
>
> But we cant recive the Aleaud Idoc in PI. We get this 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="1">
> <SAP:Category>XIAdapter</SAP:Category>
> <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_NO_REQUEST</SAP:Code>
> <SAP:P1 />
> <SAP:P2 />
> <SAP:P3 />
> <SAP:P4 />
> <SAP:AdditionalText />
> <SAP:ApplicationFaultMessage namespace="" />
> <SAP:Stack>ALEAUDIT IDoc cannot find request IDoc in Integration Server</SAP:Stack>
This IDoc is received by PI as acknowledgement. Hence it tries to correlate this to the request IDoc and is not able to find the request IDoc. The correlation used is the idoc number DOCNUM under E1STATE
So, If you are manually generating the ALEAUD Idoc through we19 make sure that you fill in proper Idoc number in the above field to get rid of this error.
> <SAP:Retry>N</SAP:Retry>
> </SAP:Error>
>
> Anybodoy knows what´s happenning and how to solve it????
>
> Thanks a lot
From the description of your scenario, You need to get the ALEAUD message as a request message as against acknowledgement. For that you need to use the program IDX_ALEREQUEST program in PI as suggested by others in your other threads. If this issue is already solved, Please close the same.
Best Regards,
Nageshwar

ALEAUDIT IDoc cannot find request IDoc in Integration Server

Hi,
i m working with a scenario SAP ECC 7.0 -> IDoc -> PI -> IDoc -> R/3 4.6c
I m sending a purchase order (ORDERS.ORDERS05) from SAP ECC and i want to receive an acknowledgment from R/3. Unfortunately there are only zeros in the field E1ADHDR / E1STATE / DOCNUM, this leads to the error "ALEAUDIT IDoc cannot find request IDoc in Integration Server" on PI.
Does anybody know what to do in the R/3 system to send the original IDoc number in E1STATE / DOCNUM?
XML Source of the ALEAUD received at PI:
<?xml version="1.0" encoding="UTF-8" ?>
<ALEAUD01>
<IDOC BEGIN="1">
<EDI_DC40 SEGMENT="1">
<TABNAM>EDI_DC40</TABNAM>
<MANDT>100</MANDT>
<DOCNUM>0000000004307392</DOCNUM>
<DOCREL>46C</DOCREL>
<STATUS>30</STATUS>
<DIRECT>1</DIRECT>
<OUTMOD>2</OUTMOD>
<IDOCTYP>ALEAUD01</IDOCTYP>
<MESTYP>ALEAUD</MESTYP>
<SNDPOR>SAPQV1</SNDPOR>
<SNDPRT>LS</SNDPRT>
<SNDPRN>QV1CLT100</SNDPRN>
<RCVPOR>A000000022</RCVPOR>
<RCVPRT>LS</RCVPRT>
<RCVPRN>QXC100</RCVPRN>
<CREDAT>20090605</CREDAT>
<CRETIM>111523</CRETIM>
<SERIAL>20090605111521</SERIAL>
</EDI_DC40>
<E1ADHDR SEGMENT="1">
<MESTYP>ORDERS</MESTYP>
<MESTYP_LNG>ORDERS</MESTYP_LNG>
<E1STATE SEGMENT="1">
<DOCNUM>0000000000000000</DOCNUM>
<STATUS>53</STATUS>
<STACOD>SAPV1311</STACOD>
<STATXT>&1 &2 wurde gesichert</STATXT>
<STAPA1>Terminauftrag EX</STAPA1>
<STAPA2>2510016042</STAPA2>
<STATYP>I</STATYP>
<STAMQU>SAP</STAMQU>
<STAMID>V1</STAMID>
<STAMNO>311</STAMNO>
<STAPA1_LNG>Terminauftrag EX</STAPA1_LNG>
<STAPA2_LNG>2510016042</STAPA2_LNG>
<E1PRTOB SEGMENT="1">
<DOCNUM>0000000004307353</DOCNUM>
<OBJTYPE>BUS2032</OBJTYPE>
<OBJKEY>2510016042</OBJKEY>
</E1PRTOB>
</E1STATE>
</E1ADHDR>
</IDOC>
</ALEAUD01>
Regards,
Udo

Hi Volker,
yes, that was the right hint
I needed to change the RCVPRT field to LS to force the receiving system to send the ALEAUD with original number at the right place. Strange reaction, but it is SAP software, he, he.
Regards,
Udo

Missing ALEAUD idocs

Dear Experts,
For one of our existing interfaces for Delivery Idocs from R3>PI>third party; we have an issue with the ALEAUD messages. This configuration is in place since a long time. Some of the Delivery Idocs are in status 12 in R3 system and they do not have the corresponding ALEAUD Idocs- hence the staus remains 12 and does not get changed to 39. The third party application has been receiving these delivery Idocs; hence I am not sure why we do not have ALEAUD messages getting created for these. I have checked the below:
In R3 WE09 I have searched ALEAUD messages for the Idocs in status 12 with filter: Segment:E1STATE and Field DOCNUM and heValue <Original Delivery Idoc Number>. For the 39 status idocs I do find ALEAUD Idocs corresponding to th original delivery Idoc. But for the Idocs in status 12; as suspected; I do not find ALEAUD messages.
In PI SXI_Monitor; I do not know how to corelate/find the ALEAUD message for a specific Delivery Idoc message. But I checked with approximate timestamp randomly and could not find the ALEAUD message for my delivery. Is there any other way to find if an ALEAUD message is created for an Original message?Checked in Trace and reliable messaging in SOAP header, response header; but no luck. For 1 hr I could find 2000 messages and going through each of them individually is not an option. I do not have time/aprovals to implement content based search on my production box within a short duration to apply any filter to find these messages.
Can you please help and tell me
1. How can I find/correlate ALEAUD messages for an original message in PI?
2. What could be the reason that ALEAUD messages are not getting generated; only for some messages; eventhough the same has been received at the Destination?

My issue was solved.
After further analysis it was found that the ALEAUD messages are created from the response messages sent by the receiving 3rd part system. Eventhough the 3rd party system was receiving all our outgoing messages; they failed to process the acknowledgement or confirmation for some of the messages. Inturn we received no confirmation responses from the third party and hence the ALEAUD messages were not created for the same. After finding this, the same was informed to the thrid party system and they are fixing the message confirmation/acknowldgement processing from their side. So the issue was closed.
I had also raised an OSS message for this where the analyst had asked me to check the below.. Please go through the same for your issue. Maybe it will help you...
"I looked at the example IDoc messages and i found no request message
created by the external system. Please give us the message id that
for the request message id that should create and ALEAUD-IDoc
for IDoc xxxxxx. If this is missing in the system please contact
the administrator of the external system why this request messages
was not created.
I found 126890 messages in the system with system error, possible
one of these messages contain the information for your idocs.
transaction SM58 i found many errors with function module
IDOC_INBOUND_ASYNCHRONOUS, this function module transports IDocs
and these IDocs are possible missing in the receiving system ?
Please check the errors and try to correct them."
Thank you

ALEAUD idoc

Hi all.
I am following the How ToHandle Acknowledgments for IDoc guide.
I have posted 3 idocs into a BW system. The three idocs are similar but errors are produced in the system.
I made use of the program RBDSTATE and the variant SAP_AUDIT_SEND to send acknowledgements back to the XI server. However there is only one ALEAUD idoc sent back to the XI server and the ALEAUD only corresponds to the first idoc received in the BW system.
How can i send three separate ALEAUD for the three similiar idocs received in the BW system?
Appreciate any advice.

Check if the first ALEAUD idoc has the information of the remaining idocs too. And make sure that the packect size in partner profile is 1.
Regards,
Prateek

Aleaud idoc in status 56

hi i work in production support and new to idocs this is the problem given to me i have to solve it asap. when i check the idocs in we02 transaction it shows idocs in status 56 with a message ipartner profile inbound not available.
DETAILED DESCRIPTION OF PROBLEM.
inbound ALEAUD idocs that error with status 56.   These clog up & slow down
workflow- as we are getting over 10,000 of these per month.     For example:
when we work on inbound invoices that error, it's slower. (using transaction
SBWP)    I'm NOT saying ALEAUD idocs are related to inbound invoices, just
saying that SBWP gives us access to variety of idocs and it's been running
slower due to large amount of ALEAUD idocs erroring into workflow every day.
Best I can tell- looks like for every PO & PO Change idoc we send to
SupplySync, we get ALEAUD in response a few seconds/or a minute later.
**See examples on attached Word document, for date of 9/27/05.
Also I checked several different dates and the count/total number of:
PO documents sent    VS   the inbound ALEAUD idocs recvd- always matches
within a count of 1 or 2.
Ex: on 9/27/05     PO docs sent = 663       ALEAUD recvd = 664
Would like to have:
A) ALEAUD idoc creation stopped- if not serving a purpose
B) OR?- have them post successfully instead of erroring in workflow
Or- have workflow purged periodically, if can't do A or B above.
Regardless of how this is resolved- need backlog of ALEAUD purged from
workflow.
any kind of help in solving this problem would be great
thanks
noor.

Hi thanks for reply its very helpful if possible could you plz give more details about the oss notes 153205 it had a look at it talks about report RSWWCIDE to delete type c work items i also saw its selection screen
The selection parameters of the report have the following meaning:
id - ID of the work item -> please always restrict here !!!
cd - creation date of the work item
ct - creation time of the work item
commitc - number of the ContainerItems to be deleted for each LUW
del_log - also delete the history of the ContainerItems
disp - only list selected ContainerItems
does this report deletes the idocs does mean on id of work item i have to enter the idoc numbers which i want to delete and then all idocs nos i enter gets deleted is it so? can youplease give more details.
thanks

Multiple ALEAUD Idocs are being generated per original Idoc

We have the following scenario in PI:
ERP (IDOC)> PI (JDBC)> 3rd Party
PI sends ALEAUD idocs back to ERP when the process is successful. Program RBDAPP01 is then ran on a schedule to update the ALEAUD idoc status, which in turn, updates the idoc status of the orignal idoc sent from ERP (03 to 12).
We just upgraded our PI from 7.0 to 7.1. Now, it seems multiple ALEAUD idocs are being created for each ERP outbound idoc. It used to be 1-to-1. From what I can tell, it look like an ALEAUD it created for every receiver. For example, if we sent one idoc and the data goes to 3 receivers, 3 ALEAUD idocs are created. This causes an issue because the first ALEAUD idoc will update the original outbound idoc to status 12, but any other ones will take it from status 12 to status 09. We want it to stay in status 12.
Any ideas why 7.1 would be any different?

This seems to be the standard behavior. I will explain it.
If an idoc comes and message is sent to say three receivers, all the three message should generate the ack unless they are not disabled. And in this case you will find multiple ALEAUD message at sender. In case the receiver adapters are like File, JDBC which do not support application ack, then ALEAUD won't be sent and you will receiver "Applicaition Ack Not Supported". With this error, if multiple ack are seen in sender then I guess they won't actually perform any update.
Regards,
Prateek

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

User Exit for Aleaud Idoc

Hi everybody!!!
Does anybody knows if exist any user-exit or badi for aleaud idoc???
We receive an Idoc from PI and we sent an Aleaud Idoc to Pi as Ack and we need populatel some fields.
Thanks a lot

try an implementation of BADI IDOC_DATA_INSERT
we have successfully added an ALEAUD extension and populated fields within the extended segment the IDoc then gets sent to PI, however we have not managed to get PI to see those extended fields yet.
Colin

"ALEAUDIT IDoc cannot find request IDoc in Integration Server" error in PI

Hi Experts,
i am getting error "ALEAUDIT IDoc cannot find request IDoc in Integration Server" and
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_NO_REQUEST</SAP:Code> in PI .
i am using ALEAUD.ALEAUD01 IDoc in my scenario.
i found two threads in SCN (scn.sap.com/thread/1370194,scn.sap.com/thread/1132815)but still i did not understand clearly for this issue .
Please clearly expline the solution for this issue in this thread ,i will give you points who post the correct solution.
Please send me solution for this issue clearly.
see the below payload also.
Thanks,
Aadi

the same problem
"ALEAUDIT IDoc cannot find request IDoc in Integration Server"
Could someone help with it?

Receiving idoc from R/3 and receiving aleaudit idoc back to senderr

Hi,
I'm trying to post a idoc from R/3 to a FTP server using file adapter. I have configured a RFC destination, port on R/3 to the XI server and a partner profile on R/3. Also created a RFC destination and port on the XI to the R/3 system.
When I try to test the idoc using TA we19, mention the sender and reciever port , the idoc is sent with a msg 'IDoc sent to R/3 System or external program'. In TA we05 the idoc is shown with status 3.
But when monitoring the idoc in XI it doesn't appear in the moni
Would appreciate ur replies.

HI,
Please try to run program RBDMOIND with ta code se38.
Also see the below links for ALE AUDIT.
Check these docs...
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
https://websmp210.sap-ag.de/~sapdownload/011000358700003477212005E/HowTo_IDOC_Ack_20040817RR.pdf
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
Regards
Chilla..

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

How to get Original Message ID from the MDN of Acknowledgment?

Hi,
Here is the usecase...
Host Trading Partner: ABCHost (Host)
Trading Partner: XYZPartner
Transport Protocol: HTTP1.1
Exchange Protocol: AS2
Business Protocol: Custom Document over Internet
There are 1000s of messages sent via B2B to the Trading partner and the Acknowledgement is received. Now that the Trading Partner system receives a lot of messages per day, they are asking us to give them the MDN Ids from the Acknowledgment they sent in order to find the transaction.
Is there a way to generate a report to do that using the Timestamp, Business Action, Sending/Host Trading Partner, AS2 Identifiers etc.?
If not thru' the B2B Console, is there a way to write a query to run on the backend to generate the report?
Thanks
Bala

Hi Bala,
You can see the details of MDN in the B2B repository in the view "b2b_instancemessage" or in the table "tip_businessmessage_rt".
You can refer InstanceMessageUtil (http://download.oracle.com/docs/cd/B14099_19/integrate.1012/b19324/oracle/tip/adapter/b2b/utility/InstanceMessageUtil.html).
Rgds,
Nitesh Jain
[email protected]

Succesful IDOC acknowledgements from ECC

Dear MDM gurus,
What is the best way to handle acknowledgements from ECC (INTO MDM) for inbound IDOCS from MDM (MDM->XI->ECC).
We want it such that when an IDOC gets posted into ECC succesfully,it should send an acknowledgement signal back to MDM saying that IDOC was received properly.
Thanks.

HI Mugdha,
I have a concern on the Acknowledgement (ALEAUD) Idoc. I have implemented this scenario wherein DEBMAS IDoc is posted from MDM -PI - ECC and ECC sends back the acknowldgement using ALEAUD Idoc.
However, in PI (SXMB_MONI) there is no separate message entry created for this acknowledgment. The ALEAUD acknowldgement message details is attached to the original DEBMAS message which was triggered from MDM - PI - ECC. Due to this, PI interface created is not able to read the acknowledgement message and process it to post/dump the target file onto the MDM Port.
I tried triggering and ALEAUD Idoc manually using PI - RWB which generated a separate message for ALEAUD Idoc in sxmb_moni and then my target file was created in MDM (But this is just a manual way of testing the PI interface).
Can you advice on how this concern can be dealt with?
Thanks in advance,
Elizabeth.

IDoc Acknowledgement Issue in SAP PI 7.3

We have configured IDoc to IDoc scenario between two ECC system using IDOC_AAE adapter. When we run the RBDSTATE program to trigger ALEAUD IDoc it is getting failed in SM58 in ECC system. But when we configure a separate scenario to transfer ALEAUD IDoc from one ECC to other ECC system usin IDOC_AAE adapter then the ALEAUD IDoc reached in target ECC system. In this case there is no error in SM58 of ECC system.
SM58 Error: Commit fault: ASJ.ejb.005043 (Failed in component: sap.com/com.sap.aii.ad
Regards,
Anurag

Hi Anurag, Hasan,
Check the following OSS Notes, they are both addressed to the error you mentioned (appearing under different circumstances, so you might have to choose the right one):
1719180 Handling of multiple acknowledgements in one ALEAUD IDoc
1729575 Sending IDoc acknowledgements fails because of long text
Regards,
Greg

ALEAUDIT IDOC FROM R/3 AS ACKNOWLEDGEMENT TO XI IDOC

Similar Messages

Maybe you are looking for