ALEAUD01 idoc

Hi,
I am receiving a 850 from edi translator via PI into ECC. Can I use ALEAUD message to send the idoc status back to translator via PI. Since the incoming order will have sending partner type as 'KU' and it seems ALEAUD works only for logical systems. Please let me know the options?
Thanks,
Jassi

Hi,
http://help.sap.com/saphelp_bw/helpdata/en/0b/2a65df507d11d18ee90000e8366fc2/content.htm
Try the above link, Stil u having the same prb let me know.
Regards,
S.Saravana

Similar Messages

ALEAUD01 IDOC problem with Senderpartner Number

Hi,
I have scenario like R3 -XI-File NFS.so we have created a third party Receiving system(TEST_XYZ)as a business system maintain in SLD.
when the IDOCs sent from sender R3 system acknowledgments been sent back to R3 system from XI,but XI system generate acknowledgment populating wrong sender SNDPRN(TEST_XYZ 's Logical system maintained(TESTPRN) in SLD for Business system TEST_XYZ) and the ALEAUD01 IDOCS are failing in R3 system as there is no partner profile set up in R3.I changes the Logical System name for Thirdparty Business System in SLD,but still XI ack populating with wrong SNDPRN.
R3 sending IDOCs with a RCVPRN like TEST123 and type LS to XI,if XI can send back ALEAUD01 with SNDPRN same as RCVPRN TEST123 ,then all ALEAUD01 will be posted correctly.
I have tried putting receiving Business system (TEST_XYZ) Adapter specific identifiers Logical system name as TEST123,but no luck.
how can resolve the issue please?
thank you,
Sathish
Edited by: Sathish on Feb 3, 2009 2:57 PM

Hello Sathish,
I was having two scenarios and you are right that was R/3 -XI-R/3 .
I tried for idoc to file scenario with configuring RCVPRN as logical system of File. When i tested the scenario it worked as expected i mean ack with SNDPRN as Logical system of File and RCVPRN as logical system of R/3.
In your case after changing the logical system of file in SLD. In ID clear SLD Cache and try to sync logical system in the adapter specific properties and you will be configured log in that .
Rerun the scenario now you will see the ALEAUD01 with expected control record
HTH
Rajesh

IDoc acknowledgement scenario using ALEAUD01 IDoc type

Hi All,
I have a query, regarding IDoc acknowledgement scenario using ALEAUD01 IDoc type as mentioned below.
In a scenario where we configure and send ALEAUD01 to sender as acknowledgement of the IDoc’s received, is there any way how do we make sure that IDoc’s received by target SAP system has sent the acknowledgement successfully. Would there be any key information in the ALEAUD01 IDoc, which refers to the IDoc/data sent?
Thanks
Rajendra

I needed 24 seconds to know the answer
I took the word ALEAUD01 into Google and added site:help.sap.com in the search field
Among the first 10 results was one with the subject
Acknowledgment Messages
one click to open and skimming through the text ....
And opening one of the other hits in Google told me even which field is having this info

Problem with ALEAUD01 IDOC

Hi I got one different senario in ALAUD01 idoc.
If the back ground job is scheduled to process idoc then it is generating the idocs perfectly.But user is asking in between if they find any config issue they are going to change in BD87 and they will process IDOCS manuvally.so at that time there is chance of duplication.
so i need a help in this regard.How to find previously generated IDOC with contentes and how to compare that with present one and if there is any duplicate i need to delete that IDOC .So please guide me in this record.
Thanks,

If the user changes the data in the idoc reprocess the existing idoc will have all the changes and the old data will copied into a different idoc number and that will have different status and that can never processed, so there is no question of duplication.
Thanks,
MAhesh.

ALEAUD01 idoc for acknowledgement

Hi,
I am receiving a 850 from edi translator via PI into ECC. Can I use ALEAUD message to send the idoc status back to translator via PI. Since the incoming order will have sending partner type as 'KU' and it seems ALEAUD works only for logical systems. Please let me know the options?
Thanks,
Jassi

ALE audit is only possible for IDocs of type logical system (LS).
Refer the 2.Introduction part in this document-
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe?quicklink=index&overridelayout=true

IDOC Acknowledgement with ALEAUD01 does not work

Hi,
since my last thread Changing IDOC status after succesful processing i learned much about IDoc's and ALE.
But my problem is still alive! I have the scenario IDOC (HRMD_A06) --> XI --> file. I noticed that the file adapter creates an acknowledge message and transfers it to the IDoc Adapter as an ALEAUD01 IDoc.
Unfortunately XI does not fill the ALEAUD01 IDoc in the right way. The field DOCNUM in segment E1STATE (which should reference the original IDoc) is always empty but the STATUS Field is set in the right way to 50.
The SAP 4.7 Application Server processes these ALEAUD01 IDoc without an failure and set the ALEAUD01 IDoc to Status 53, but the original HRMD_A06 keeps in STATUS 03. (Of cource, the application server can't determine the referenced IDoc without the DOCNUM!)
When i am editing these ALEAUD01 with transaction WE19 by filling DOCNUM in segment E1STATE manually and sending it to the Input Queue, everything works fine. The STATUS of the referenced HRMD_A06 changed to 39 (IDoc received target System) That's what i expected.
But why does not XI set the DOCNUM in segment E1STATE empty, when it generates the ALEAUD01? This makes no sense to me. Is this a bug of the XI IDoc adapter? Or is there any other trick?
Greetings

Hi Erik,
Pls go through the below links and my answers, that may help you to fix your problem.
Re: Acknowledgements ever switch to Status 39
Re: ALEAUD issue
Re: Steps For Updating the IDOC Status using ALEAUD
Re: Asyncronous acknowledge from file adapter
Regards
Vishnu

Error while testing Inbound Idoc

The error message "Interface for function Z***** is incorrect*." is shown while trying to test an incoming IDOC in we19.
PL HELP!!!!!!!
The procedure followed by me was,
WE31 created custom segments,
WE30 Created custom basic type,
we81 Custom message type,
se37 function module,
we82,
we57,
bd51,
we42,
bd67,
we20,
Am not able to figure out why exactly is the error message being shown.
please tell me if a step was missed or what the possible error is, I think the parameters of function module are correct....

Hi friend,
if it is help full please give max reward point.
Standard program, RBDMOIND is scheduled or executed online to determine whether the communication was successful. If IDoc is Dispatched to destination system, RBDMOIND updates the status of the IDoc to 12 (Dispatched OK), Otherwise remains in status 03.
Two programs enable cross-system reporting:
     RBDSTATE: It reports the status of the incoming IDocs to sending system, using ALEAUD message and ALEAUD01 IDoc
     RBDAUD01: It executed on sending system to analysis the audit log and display the output as a report
IDoc Status in Receiving System          IDoc status in Sending System via ALEAUD
53 Application docu posted     =>     41 Application docu created in receiving sys
51 Error: Application docu      =>     39 IDoc in receiving sys. Status repeated
     not posted                         each time RBDSTATE runs.
68 Error: No further processing     =>     40 Application docu not created
ALE Auditing
BDM7          =>     ALE Audit: Statistical Analysis
BDM8          =>     ALE Audit: Sending the Confirmations
RBDSTATE     =>     Run on Receiving System to return Audit Message

IDoc Acknowledgement to JDBC status update

Hi,
JDBC --> XI --> SAP R/3 (IDoc ACC_DOCUMENT02)
JDBC <-- XI <-- SAP R/3 (IDoc ALEAUD01)
I have the following scenario... I am reading data from a database using the JDBC Adapter. The data is in the following format at source. Using the JDBC adapter I read the database for rows for which the status is blank, this is multiple documents.
Invoice 1 Status 53
Invoice 1 Status 53
Invoice 1 Status 53
Invoice 1 Status 53
Invoice 2 Status <blank>
Invoice 2 Status <blank>
Invoice 2 Status <blank>
Invoice 2 Status <blank>
Invoice 3 Status <blank>
Invoice 3 Status <blank>
Using a BPM process I split the source data into multiple messages and map them to the IDoc structure. In the above example Invoice 2 & 3 would be read from the database and split into 2 individual IDocs to be posted separately into SAP.
IDoc 1
Invoice 2 Status <blank>
Invoice 2 Status <blank>
Invoice 2 Status <blank>
Invoice 2 Status <blank>
IDoc 2
Invoice 3 Status <blank>
Invoice 3 Status <blank>
I now want to extend this scenario to include acknowledgement messages which I can use to update the status in the source system.
I have configured the ALEAUD01 message in the destination system and scheduled the RBDSTATE program to run periodically. I can see in the XI message monitor that my messages now have aknowledgement status.
What I would now like to do and hopefully someone can help is to use the status information being fed back from SAP in the ALEAUD01 message to update the status field for individual lines in the source table. Can anyone help with this step???
Regards,
Pete

I can see the limitation of ALEAUDIT as it is handled internally in XI. Using the bespoke route I can create a copy of ALEAUDIT and a bespoke IDoc ZALEAUD01 for example, which will send the status idoc to XI.
In BPM I can configure a receive step to receive the IDoc... But, how do I then relate the IDoc I created to the particular segment in my ALEAUD01 IDoc.
Regards,
Pete

IDOC: Status (Error/Success/information)report to Sender system

How would one send a message(error/success/information) to the sending(external) system to inform them of the statuses of the messages they've sent to our SAP system?

Hi Baumann,
you have an option called Audit reporting in which you can have the status of idoc at sender side.read the following.
Setting Up Audit Reporting
In the default behavior, after an IDoc is dispatched to a destination system, the sender does not know the state of the process on the destination system. You can configure the system, however, for cross-system reporting. You must model the ALEAUD message between the systems.
Two programs enable cross-system reporting.
1)RBDSTATE. This program is scheduled to run periodically on the destination system. It reports the status of incoming IDocs to the sending system, using the ALEAUD message and ALEAUD01 IDoc. This status information is recorded separately from IDoc status information in the audit logs.
2)RBDAUD01. This program is executed on the sending system. It analyzes the audit log and displays the output as a report.
The RBDSTATE program returns the following statuses, from the receiving to the sending system.
RBDSTATE Is Run on the Receiving System
Status of IDoc in receiving system     Status reported to sending system via ALEAUD
53 (Application document posted.)     41 (Application document created in receiving system.)
51 (Error: Application document not posted.)     Status 39 (IDoc is in the receiving system.) This status is repeated each time RBDSTATE is run, as long as the IDoc remains in status 51.
68 (Error: No further processing.)     40 (Application document not created in receiving system.)
reward points if helpful,

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

IDOC MESS ..URGENT..!!

pls help me with this scenario ,
The idocs are coming from an external system called x in flat file .
i have scjeduled the program rseinb00 to create the idocs .
i have done the settings to process these idocs via idoc_input_orders.
Now , if i have made this setting , it means that whenever an idoc of type orders01 will come this FM will be triggered. Does it mean that for inbound it doesnt matter if it comes from system x y or z , once the settings are done in one partner profile it will always use this function module to process any idocs that come on that system .
For eg : I have one partner profile ABC type LS
Inbound parameter : orders , process code ORDE.
Now , if orders01 idoc comes from supoose system A , System B to ABC Logical system , it will process all the orders01 in the same way ??
The issue with me is that :
Once the RSEINB00 creates Idocs , the idoc_input_orders is triggered as per the settings in Partner profile.
My first question is :
What is the standard way of reporting the errors produced during idoc processing to the external system (Non SAP) ?
If i copy the standard FM idoc_input_orders , and try to read the status table , How can I ensure that i read the status of only those idocs that came from System A ?
If I try to set up the ALEAUD01 idoc to produce an audit idoc , how can i ensure that it contains only status of idocs from system A??
I m in a mess , pls help ASAP.

I suspect whether there is a standard way available!
However, there can be a work-around which would call for some development.
Approach could be:
1. Create a ZReport which will fetch all status records for the specified conditions (such as IDoc No., IDoc Create Start/End time etc), format & download the status info (flat file format) to a specified location.
2. Subsystem can pick up the downloaded file by running scheduled job.
3. This report can either be executed manually or scheduled to run at some speficied time intervals.
This approach can be extended to a Z_BAPI function module & this BAPI can be called by the subsystem directly to get the status info of say previously sent IDocs.
Thanks,
Puru

IDoc Acknowledgements w/ XI 2.0

Hi All,
We are attempting to utilize the IDoc Acknowledgment functionality that is built into XI IDoc Adapter. The documentation mentions this functionality briefly and says that all you have to do is add the ALEAUD.ALEAUD01 IDoc to the endpoint that is equal to the sending business system. I've done this, but nothing seems to happen. Does anybody have any experience with this functionality? Are there any detailed examples or documentation? Any help is greatly appreciated!
Thank you,
Jeff Kocur

Hi All,
I have now resolved this problem and thought I should spend some time sharing this with you.
I decided to look at the code that was issuing the error which was calling a function module called SAI_LOGICAL_SYSTEM_GET to return the logical system for my business system. When I ran the function module in test mode it returned a blank logical system. The logical system is stores in table sailcrbsc. I re-ran the function module with the bypass buffer field set to 'X' - now when the function module is called it returns the correct logical system.
Anyone out there have any more info on this? How should I have re-built this table?
Regards
Ian

IDOC Acknowledgement Error

Hi All,
I am getting "Receiver exists , No filters , No conversion , No version change" message in IDOC Status of ALEAUD. And IDOC has not been sent to XI System.
I have done the settign for Idoc acknowledgement.
What is the reason of this message.?

this is inbound message that i am getting..
<?xml version="1.0" encoding="UTF-8" ?>
- <ALEAUD01>
- <IDOC BEGIN="1">
- <EDI_DC40 SEGMENT="1">
<TABNAM>EDI_DC40</TABNAM>
<MANDT>900</MANDT>
<DOCNUM>0000000002416250</DOCNUM>
<DOCREL>620</DOCREL>
<STATUS>30</STATUS>
<DIRECT>1</DIRECT>
<OUTMOD>2</OUTMOD>
<IDOCTYP>ALEAUD01</IDOCTYP>
<MESTYP>ALEAUD</MESTYP>
<STDMES>ALEAUD</STDMES>
<SNDPOR>SAPEIT</SNDPOR>
<SNDPRT>LS</SNDPRT>
<SNDPRN>EITCLNT900</SNDPRN>
<RCVPOR>SAPXID</RCVPOR>
<RCVPRT>LS</RCVPRT>
<RCVPRN>XIDCLNT300</RCVPRN>
<CREDAT>20071105</CREDAT>
<CRETIM>190225</CRETIM>
<ARCKEY>A05D0C308BBB11DC8598001A4BA967D2 0000000000573053</ARCKEY>
<SERIAL>20071105171956</SERIAL>
</EDI_DC40>
- <E1ADHDR SEGMENT="1">
<MESTYP_LNG>Z_MLS_INBOUND_RECEIPT</MESTYP_LNG>
- <E1STATE SEGMENT="1">
<DOCNUM>0000000000573053</DOCNUM>
<STATUS>64</STATUS>
<STACOD>SAPB1999</STACOD>
<STATXT>& & & &</STATXT>
<STAPA1>Immediately processi</STAPA1>
<STAPA2>Unable to interpret</STAPA2>
<STAMQU>SAP</STAMQU>
<STAMID>B1</STAMID>
<STAMNO>999</STAMNO>
<STAPA1_LNG>Immediately processing not possible:</STAPA1_LNG>
<b><STAPA2_LNG>Unable to interpret EGOD3 as a number.</STAPA2_LNG></b> - <E1PRTOB SEGMENT="1">
<DOCNUM>0000000002416235</DOCNUM>
</E1PRTOB>
</E1STATE>
</E1ADHDR>
</IDOC>
</ALEAUD01>
In 'Ack' i am getting this message.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Ack xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Status>Error</SAP:Status>
<SAP:Category>transient</SAP:Category>
</SAP:Ack>

Unwanted ack idocs

Hi,
i changed this:
IDOC -> XI -> external adapter engine -> JMS queue
to that:
IDOC -> XI -> jms adapter -> JMS queue
Both variants work well so far. But with the newer version (without external adapter engine) i observe in SXMB_MONI in the ack.column a red icon, which says something like ack. cannot be handled.
There is indeed no configuration in the sending r/3 system to handle acks.
The strange thing is, that with the older variant in same column in SXMB_MONI was an icon with a green question mark (something like waiting for ack.)
It looks for me, as if the jms adapter generates an ack on its own, which is sent back via idoc to r/3.
The check box in the jms adapters configuration, about generation delivery acks is not set.
Can someone confirm this behaviour ?
Does this affect the r/3 system (error messages etc.) ?
What would be the best approach to solve this ?
btw. XI is on SP13
Thanks and Regards,
Peter

Hi Peter,
Seems we can become good friends after this trouble shooting
Anyways,
Use message type as ORDRSP And you need to use the message type of the idoc you want to send to xi.The pdf used Aleaud as it was sending ALEAUD01 idoc, but in your case use Message type for the idoc you want to send so use ORDRSP and reconfigure and cross check ALL the steps one by one slowly.
Again most importantly Your patner profile in we20 do not have the entry for ORDRSP so need to make an entry on the outbound side as well and also the parner type as LS. To add use the " + " icon and define clearly.Actually SAP needs to know if the data is coming from a server which is of a trading patner, if thats the case it refers to the patner profile.
This should get you going, but donot confuse between the idoc used in the pdf and the idoc you need to send.
All the best!
Anirban.
Ps: Its almost end of day here in India, so if still it does not work after these steps please refer:
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
And
http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
other then the acknowlegement pdf.

BMP Correlations (SOAP-XI-IDOC)

Hi,
I have a scenario like this, SOAP-XI-IDOC. I'm using a BMP to:
1- Receive the SOAP request and I'm using a S/A Bridge,
2- Map SAOP request to an Idoc
3- Send the Idoc to SAP
4- Close S/A Bridge
So step 1,2 and 3 are working.
Now, In my SOAP message I get "Pipeline timeout condition satisfied". I did increase the "CHECK_FOR_ASYNC_RESPONSE_TIMEOUT" setting but still getting it.
I think the problem is that the BMP is never ending the process and I'm not to sure why. I'm not using any correlations in my scenario, would this solve my problem? Is it required? What else could be the problem?
How can I debug this to see where is it broken?
My next step, if I can get the first part working, I would like to have my BMP wait for a ALEAUD back from R/3 and mapping this to the SOAP request. ANy idea how to do this part?
Rgds,
Yves

Hi,
I'm sure somebody did this.
Still not able to read the Ack back from R/3 to my BPM. I get the ALEAUD back to XI but I get:
No object type found for this message; check the activation of the corresponding process
When I look at SXMB_MONI_BPE I can see that my workflow is waiting for the response back from R/3.
How can I read the ALEAUD back in my BPM?
I still think I need some correlations but not sure. I did create a correlation between the outbound Idoc from Xi to R/3 (/MBGMCR02/IDOC/EDI_DC40/DOCNUM) to my Inbound Idoc (/ALEAUD01/IDOC/E1ADHDR/E1STATE/DOCNUM) but it's not working. So, is it possible to get back the ALEAUD in a BPM?
And if yes, is it possible to map the ALEAUD to the response back of my SOAP message (response)?
I did look at some forums about looking at table IDXRCVPOR to get the original IDoc number back but I'm not to sure how this would help me. For me, the Idoc number in (/MBGMCR02/IDOC/EDI_DC40/DOCNUM) and (/ALEAUD01/IDOC/E1ADHDR/E1STATE/DOCNUM) should be the same. Right?
Rgds,
Yves

ALEAUD01 idoc

Similar Messages

Maybe you are looking for