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

Similar Messages

How to get Idoc acknowledgment in File to Idoc scenario

Hi All,
Please give suggestions about the below mentioned scenario:
Scenario: FileXI- ECC - Data from File is converted to various IDocs and posted in SAP. (No BPM used)
Problem: Exception Handling > > We want a message back from SAP system telling us that out of 100 IDocs that were sent, n were posted successfully and rest failed along with the error description. How can this be achieved?
Regards,
XIer

Pls go thruough these links also
Please see the below links
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
/people/ravikumar.allampallam/blog/2005/06/24/convert-any-flat-file-to-any-idoc-java-mapping
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
/people/stefan.grube/blog/2006/09/18/collecting-idocs-without-using-bpm
unable to import from SLD
/people/sravya.talanki2/blog/2005/08/17/outbound-idocs--work-around-using-party
/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping
/people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
idoc erros - http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
IDOC Acknowledgements
R/3 IDOC ->XI-> ORACLE Error Handling
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb
/people/kannan.kailas/blog/2005/12/07/posting-multiple-idocs-with-acknowledgement
/people/udo.martens/blog/2005/09/30/one-logical-system-name-for-serveral-bpm-acknowledgements
Regards
Abhishek Agrahari

IDOC:inbound scenario for posting Message type ORDRSP

Hi All,
I am doing a inbound scenraio to post message type ORDRSP.
Acknowledgement gets created in Purchase order successfully but texts at header level and item level are not getting updated in the purchase order
I am using the segment E1EDKT1 and E1EDKT2 for header texts . For item texts I am using the segments E1EDPT1 and E1EDPT2.
Any pointers to this is appreciable.
Thanks in advance.

Hi,
Depending on whether the Order is a third party order are not, the texts are picked up from either SO or PO.
Put a break point on line 842 in the Include LEINMF11 and debug, this should help you get to the root cause of the issue.
Regards,
Chen

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

Idoc Acknowledgement in File

Hi All,
I came through some threads in SDN regarding Idoc acknowledgement and followed handling Idoc acknowledgement document. I am able to get back acknowledgement(ALEAUD) in Xi.
I configured a scenario to receive this acknowledgement in File.
But i am not able get the acknowledgement in the File.
In SXMB_MONI ,in the pipeleine step Technical Routing of Response i am getting Acknowledgement Message Stopped.
How to rectify the above error..I need to get the acknowledgement back in File..?
Is it possible to do without BPM..?
Hoping for good solution..
Thank You
Regards
Prakash

Hi,
If you are lokinf for IDOC acknowledgements means check these
setting up Audit Response.
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
ALEAUD need at least following fields to be filled:
E1ADHDR/MESTYP: original message type
E1ADHDR/E1STATE/DOCNUM: original IDoc number
E1ADHDR/E1STATE/STATUS: 68 in case of error, 53 in case of success
E1ADHDR/E1STATE/STATXT: Short description for R/3 user what has happend
If you are using XI 3.0 SP12 then there is some bug See : 828277
Just have a look into this blog-/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
http://help.sap.com/saphelp_nw04/helpdata/en/42/c8f66bc7a56bb0e10000000a1553f6/frameset.htm
ALEAUD not coming to SAP from XI & u0093Acknowledgment not possible" in idx5
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb
Or else if you are looking to receive the File Acknowledgements means have a look at this
/people/michal.krawczyk2/blog/2006/06/22/xi-playing-with-the-file-adapters-acknowledgments
Regards
Seshagiri

IDoc Acknowledgment Clarification

Hi,
I have a doubt in IDoc Acknowledgment Scenario
My doubt is:
My XI server date is a week prior to the date of R/3 server.
Is it possible to get Acknowledgment for IDoc if the date of the R/3 server and XI server doesn't match.
Thanks in advance
Krish

Thanks a lot...
I have tried this scenario using the pdf which you have mentioned.
But i didn't get acknowledgment in response....
While configuring the background job - the date of the job start date has a conflict with XI server date. Here comes my doubt......
Please provide suggestions.
Krish
Edited by: Krish Krish on Oct 10, 2008 5:27 AM

File to idoc bypass scenario

hi all
I am doing file to idoc bypass scenario....i have to send file containing
EDIDC segment to respective idoc.I have used the idoc name as interface and its also successfully picking the file but while receiving the idoc receiver is showing some error.in sxmb_moni its showing error as obligatory field eiedk01 is missing while its persent in the pay roll of the messege...........please guide me in bypaas
can i check my message expect sxmb_moni .
my receiver adapter is IDOC
sender adapter is XI........
regards
saurabh sharma

Look into the replies by Bhavesh in this thread.
https://forums.sdn.sap.com/click.jspa?searchID=3098859&messageID=3484218
Regards,
Jai Shankar

File -- IDOC scenario using XI 3.0

Hi
I tried out a simple flat file to IDOC scenario using XI as the middleware and tried to post documents of type CREMAS03 on the backend R/3 system.
Now, I see that there is an IDOC number generated in the XI layer by the IDOC adapter. This IDOC number is seen under <SAP:DOCNUM>XXXXXXXXXX</SAP:DOCNUM>in the
Response-->IDOCOUTBOUND section of the pipeline in SXMB_MONI
According to SAP documentation :
To enable you to select IDocs in the target system later on, the system transfers the message GUID and the IDoc number in the ARCKEY field of the IDoc control record.
Now, I do find the XI msgid given as arckey in the control record of the Inbound in the target R/3 backend system. But I cannot find the XI IDOC number being cross referenced in the control record of the IDOC in the R/3 backend.
1.Is there a way to cross reference the IDOC number in XI with the IDOC number in the R/3 backend ( we have two different IDOC numbers, right ) i.e a IDOC number to IDOC number cross referencing in this File-->IDOC inbound into the R/3 system scenario involving XI
2. In the XI box, do we get as a part of async.reponse from the R3 system, the IDOC number that is created within the R3 system ? This would serve directly as a cross reference. Or do we have to indirectly query EDIDC table in the R/3 backend with the arckey value = msgid in XI - to retrieve the IDOC number created in the R3 backend ?
Thank you in advance for your time.

Hi,
Pls look into following link about Acknowledgement.
http://help.sap.com/saphelp_nw04/helpdata/en/f4/8620c6b58c422c960c53f3ed71b432/content.htm
Pls note that , you can't get/receive the Acknowledgement for Sender File Adapter. Because File System acts as an Async system. But you can get the Idoc response and you can write it into another file. For this you need to use BPM.
Hope this helps..
Regards,
Moorthy

System Level Acknowledgement in File to IDOC Scenario

Hi All,
I have the File-> IDOC Scenario. Once the IDOC is successfully sent to R/3, PI should send a acknowlement file back to the sender system.
Could someone suggest how to design this scenario?
Should I use IDOC Acknowledgement. As it is a existing scenario, I dont want much change in r/3 side.

Dear All,
For file to idoc scenario is there any possibility to get line items details or xml details i.e the segments and its related field details using reference id, transaction id or interface name or message id in SAP PI 7.0. I know we need to click each and every message in sxi_monitor and look for details.
For SAP(R3 System) I can create a report and set the job for specific time period so automatically it throws the details(like reference no, document date, invoice no from) in ftp path as .csv file. The same ftp path is maintained in program.
I wanted to check FTP--->PI postings and I have set the job at r3 system it is working fine and Im monitoring it too.
Now the end to end scenario is FTP--->PI--->ECC(R3 system). Please help.Many Thanks.

Output type not created for outbound delivery while using SHMNT05 idoc type

Hi Experts,
Please help me to solve the below issue.
Problem:- I want to to generate an IDOC(using type SHPMNT06) once the PGI is done for an outbound delivery.
Already it is working fine when used DESADV.DESADV01 or DESADV.DELVRY07. But now the output type is not getting created when used SHMNT.SHPMNT06. I have created a separate output type ZPJ7 just as a mirror copy of the earlier output type(ZPJ6) used for DESADV.DELVRY07.
Question:- Is it possible to use idoc SHPMNT06 instead for DESADV01 or DELVRY07? If yes then what are steps to be followed?
The reason why SHPMNT06 idoc is planned:- We have a scenario to send outbound delivery to 3rd party system via XI. If the outbound delivery is for National(Not for Export) and PGI is completed then send the idoc straight forward to XI otherwise DO NOT generate the idoc, but just create the delivery. Collect all the deliveries in a transport and send it in a shipment. The shipment details can be sent using SHPMNT idoc. Now from XI perspective, if we can utlitze the same SHPMNT idoc for the National delivery(1st case) then perhaps this will require less effort. Hence shipment idoc is required to be generated when the delivery is created and PGI is done.
Also it would be great if you can advice some better way to solve above mentioned scenario.
Many Thanks,
Sanjay

There could be several reasons. Go to the document and in the extras-output check output determination analysis in the processing log.
If the output has been created successfully then you need to see your printer determination. Ask basis to check it up. If the problem is that even the print preview is not coming. Check your communication in the output analysis and ensure LOCL is selected. Any other printer will need to be configured.
If thats done already then check whether you have maintianed the condition record.
If that too is done then check whether your output type has been assigned to the output procedure and that the output type is listed in the procedure.
regds
Jude

Idoc Acknowledgement ALEAUD.ALEAUD01

Experts,
I have scenario like this: File(File system) XI/PIIDOC (R/3 sytem), this scenario works fine as is.
Now, i have to send back an IDOC acknowledgement from R/3 system to XI system. I used the link
[https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb]
and all configuration is in place. some times it works, n some time it wont.. this is beacuse I make some permutation n combination of changes, in some of the steps mentioned in the URL.. so, I dont know where I am going wrong..
Note: I did read related SDN posts..
your answers are highly appriciated.
Thanks!

Hi Prema,
1. Was the IDOC was created successfully?
-> Check whether IDOC was created correctly using transaction WE05/WE02/BD87. The issue could be due to partner profile setting, port setting or conditioning setting of your ALE distribution model.
2. Was the IDOC was sent successfully?
-> Check whether number of created IDOC using transaction WE05/WE02/BD87 match with the number of IDOC going thru PI? If it is, then the IDOC was NOT created, and you might want to check the background job that runs RBDSTATE using transaction SM36/SM37
3. Was the IDOC stuck in the PI?
-> You might want to check using SXI_MONITOR and try to fix the issue
Regards,
Lim...

Using same Idoc type & Message type for 2 Interfaces

Hi all,
we have 2 interfaces which uses same Idoc type, message type & Partner No.Only Process code is going to different according to the posting logic.
How can we differentiate both while posting idocs to not mess up each other .
Regards

Hi all,
Say example:
Interface 1 is invoice coming from legacy system to SAP and i have to use AAA.BBB Idoc
Interfaces 2 is accrual coming from legacy system to SAP and i have to use AAA.BBB Idoc
So i am creating partner No with LS_LEGACY and with 2 inbound entries one for each.
Even though i am using the same Idoc types but inside those the process codes are different because they are different in posting logic.
Issue:
From XI perspective i can't differentiate them saying like Invoice interface should execute the entry in the partner profile with invoice process code and accrual interface with accrual process code.
My Idea is to design like this...
Using the Message Code option, While creating partner profile give the MESCODE and in Mapping provide the same MESCODE.
So that even thought i am using the same partner No with same message type & basis types for 2 scenarios, the right interface will trigger the right process code based on the MESCODE mentioned in mapping by carrying the control record values
Please let me know ur views
Regards

ALE IDOC to XML IDOC scenario using XML port

Hi,
I am working on ALE IDOC to XML IDOC scenario using XML port . The requirement is to place a XML IDOC on the application server using ALE IDOC scenario ( output type is created in NACE which is ALE enabled ).
Can anybody help me on the steps.
Regards
Kumar
Moderator message: please search for available information/documentation.
Edited by: Thomas Zloch on Sep 8, 2011 6:01 PM

U can give a try as follows.
In the Partner Profile of Sender R/3 system,
Give the Receiver Party P_Party in the PartnerNo. Give the 'Business Partner' as logical System type.
In XI, Party Definition of P_Party
Give the following Alternative Identifier
Agency -   Sender R/3 Business System
Scheme -   ALE#GP
Value    -    P_Party

Custom - Material Master Update using an IDOC (Message Type - MATMAS_BAPI)

Hello everyone,
I was writing a functional specs. Basically, I want to update the material master MM02 using an IDOC (MATMAS_BAPI01 - Basic Type & MATMAS_BAPI - Message Type). This is currently working.
To my understanding, this currently uses function module - BAPI_IDOC_INPUT1 to update the material master after the IDOC is posted to SAP ECC from XI system.
Now I want to add one small validation logic before it actually updates the material master (MM02).
I looked around and found one exit - EXIT_SAPLMV02_002 in enhancement MGV00001. I was almost sure that this EXIT can be used to write the custom validation code before, actual MM02 updation.
However while trying to establish a link between this EXIT and BAPI_IDOC_INPUT1, I found that EXIT_SAPLMV02_002 is actually a part of another function module - IDOC_INPUT_MATMAS01 and not BAPI_IDOC_INPUT1. I am stuck here if adding the custom logic in the exit really going to work.
a bit of googling and I found from WE30 that the purpose of both these function modules are actually different. While BAPI_IDOC_INPUT1 actually create & updates the material master (also plant specific master data which is my need), IDOC_INPUT_MATMAS01 is just for maintenence of few fields in MM02 (may be custom fields).
Can anyone point out if my thing is in right direction?
Also please offer any solution where shall I put the Custom Logic in the EXIT or the some variants of
BAPI_IDOC_INPUT1.
A less technical explanation would be appreciated as I come from a functional background and invloved in this for writing the func specs. I want to make it sure that what I write is not useless and makes some sense.
Thanks in advance,
Arunesh

Hi Lalit,
Did some head breaking with the function module - BAPI_IDOC_INPUT1 to check whether it is calling the EXIT_SAPLMV02_002 internally. Couldn't get anywhere.
On question of another EXIT in BAPI_IDOC_INPUT1, I don't see any. I am not very proficient in ABAP code, I must say though.
I found the list of exits from google, almost same list everywhere.
http://www.sapfans.com/forums/viewtopic.php?f=21&t=296637
here I got the EXIT, I am talking about.
Any other way to find either the EXIT or link the above?
-- Arunesh

How to generate idoc PODRCH02 using out put type

Hi All,
I need to generate outbound idoc PORDCH02 and message type PORDCH using out put types (messages).But i unable to generated this idoc using message type. System is giving error as *No recipient found for message type PORDCH in the ALE model*
To do this , i have done the following steps.
1. In BD64 i have configure the business object BUS2012, using add bapi. ( In cust.distn model it doesn't allowing the message type. so i have given BAPI )
2. In partner profile (WE20), for sending logical sytems
i have configure the message type in outbound parametes.
3. In NACE for out put type NEU i have given medium as Distribution (ALE), Partner function as LS
Could you please help me out , what are the necessary steps i need to take care and what are the steps i missed out.
Thanks and regards
Praveen

In distribution model, you have to configure both the sending system and receiving system. The Tcode of Distribution model is BD64.

IDoc acknowledgement scenario using ALEAUD01 IDoc type

Similar Messages

Maybe you are looking for