IDoc application ack

hi all;
i am sending an IDoc from BPM to SAP with application ack.
i am not getting an ack back.
do i need to do some setting in SAP
do i have to use a seperate adapter to get an ack back

Hi Mudit,
There is a guide to handle idoc acknowledgements, in sap xi. please refer,"how to handel acknowledgements for idoc" at,
https://websmp202.sap-ag.de/nw-howtoguides
Have look at "How To Handle Acknowledgments for IDoc" .
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
Also go through these links...
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
unwanted ack idocs
Re: ACK send back but which Idoc Adapter
IDoc Ack
Idoc Ack in SP 17
I hope it helps.....
Regards,
Abhy

Similar Messages

Why Application ack not supported in Reciever adapters?

Hi All,
a.What is difference between Application and System acknowledgements ?
b. Why Application ack not supported in Reciever adapters (except for CIDX and RNIF)?
(as mentioned in http://help.sap.com/saphelp_nw70/helpdata/en/0d/5ab43b274a960de10000000a114084/content.htm)
c:http://help.sap.com/saphelp_nw70/helpdata/en/e1/091640a991c742e10000000a1550b0/content.htm
says If messages are sent from the PCK to the Integration Server, you must create a receiver XI adapter in the PCK.!!
Should not this be either way?
Regards
Guru

a. System acknowledgments used by the runtime environment to confirm that an asynchronous message has reached the receiver.
Application acknowledgments used to confirm that the asynchronous message has been successfully processed at the receiver.
http://help.sap.com/saphelp_nw2004s/helpdata/en/f4/8620c6b58c422c960c53f3ed71b432/content.htm
c. No
Message was edited by:
Prabhu S

IDoc Packaging + Ack ALEAUD = bad behavior ?

Hi,
I'm in version PI 7.11 and I'm studying the IDoc packaging of EhP1 with Acknowledgment (ALEAUD).
My scenario is a basic one: File -> PI --> ECC (100 idocs). And then ECC returns Ack.
So for the returned Acknowledgment, I have that:
- on ECC, I did ALE config, and I run programs RBDSTATE / RSEOUT00 to create one IDoc ALEAUD (Ack).
- In PI, I use a sender CC (Idoc adapter) by using option "Idoc Packaging".
- In PI, I use a Sender Agreement with Idoc ECC's ALEAUD and this sender CC.
- In PI, I use program IDX_ALEREQUEST on ECC's ALEAUD idoc.
My problem is:
ECC send me ONE idoc ALEAUD which contains 100 segments corresponding to 100 Idocs received at the first step. BUT even if I used the "Idoc Packaging"... in IDX5 of PI, I have not one idoc ALEAUD, but I have 100 Idocs ALEAUD !
And so after that my mapping is run 100 times instead of one ! Image if I need to return an email... with this PI behaviour, I will send 100 "Ack" emails.
So does somebody know why IDoc Packaging does not work with ALEAUD whereas program IDX_ALEREQUEST is correctly used ?
Thanks
Mickael
Note: I don't want to have to create a BPM to collect my ALEAUD Idocs. That's too heavy...
And (for the moment), I don't want to create a specific ZALEAUD idoc...

Hi Prashant,
yes, I did not precise it, but of course IDXNOALE is used, else PI will generate an Ack of this ECC's ALEAUD... so a ack of a ack... but it's not really my problem.
what I say is:
- Request : PI -> 100 idocs MATMAS (for instance)
- Ack : ECC return to PI only one idoc ALEAUD with 100 segments "E1STATE" corresponding to the 100 idocs MATMAS.
- Ack : PI receive this only one ALEAUD... but in IDX5 and in SXI_MONITOR, we see in fact 100 IDocs ALEAUD with 1 segment E1STATE, instead of having only one idoc ALEAUD (like in ECC side) !
So I'm searching a way to keep in PI the only one Idoc ALEAUD sent by ECC, in order to be able (for instance) to send only one email (and not 100 emails like it's the case for the moment).
Regards
Mickael

Application Ack by ABAP server Proxy

In a XI (with BPM)----> ABAP Proxy (ECC) scenario,
can we have application acknowledgemnt from the ECC hosting the ABAP proxy to XI.
We have tried using Transport acknowledgemtn (by settings in BPM), and it works, but please tell if application acknowledgemtn can be sent from ABAPA proxy back to XI.

> We have tried using Transport acknowledgemtn (by settings in BPM), and it works, but please tell if application acknowledgemtn can be sent from ABAPA proxy back to XI.
Yes. But you have to define a fault message type and apply this to the interface which is used for ABAP proxy.
In the ABAP proxy, you need to use "raise exception" statement to send a negative application ack message.
A postive application ack is sent automatically, when no exception is raised.

Request IDoc : Application document not posted

I am loading master data in the development system for the first time after the basline config. I am getting the following error.
Request IDoc : Application document not posted

Hi
Recheck the Connectivity RFC & IDOC too. you may ask basis for help.
verify the IDoc things no problem, connection and authorization between bw and r/3 established well.
try check in monitoring - menu environment
-> 'ale management' - in datawarehouse and in source system.
take a look oss note 520012.
Symptom
RSINFO Idocs with status 51 are repeatedly sent to the top. IDOCs with status 51 (document not posted) queue for ALE inbound processing. This may slow down the system.
Other terms
IDoc RSINFO, status 51, bd87, we05, RSRQST, R3 013
Reason and Prerequisites
The requests are started periodically and cause a R3 013 error message; the message is sent to the BW system but the requests retain a status 51. You can display the IDOCs via transaction we05. Enter RS* in the 'Logical message type' field and execute the process. You can also display the IDOCs with transaction bd87.
Solution
IDOCs with status 51 can be selected for deletion by running the 'RBDMANIN' report; do not use the 'Import in the background' indicator (you must manually remove the indicator).
Each relevant IDOC is then processed separately in the foreground and you can decide for each IDOC if you want to select it for deletion.
Hope it helps

Request IDoc : Application document not posted ERROR

Hi All,
When I am executing Info Package in BW PROD the system is showing error
Transfer (IDocs and TRFC): Errors occurred
Request IDoc : Application document not posted
I searched the forums but no such kind of error regarding this senario.This problem is for all IP in BW PROD.
Can anyone help in this issue.
Thanks,
Mayur

In SCC4 the following
in we21
Please do not make any changes to these parameters by urself ,ask ur basis team to check it and change it accordingly ....

BPM SEND step with Acknowledgemnt.Process logic depends on Application Ack.

Hi,
I am designing one BPM process in which I want to send IDOC to R/3.This IDOC will be processed by the R/3 system using process code.
Now I have sent this IDOC to R/3 through send step with application acknowledgment and only if acknowledgment comes then only next processing logic of the BPM process should be executed.
How should I design SEND step because the communication is asynchronous but I want the processing depending on acknowledgement only?
Please guide me.

Hi,
Take a look at this doc,
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe">How to handle Idoc Acks'</a>
Regards,
Bhavesh

Urgent: Error in idoc(Application document not posted)

Hi experts,
i am getting the error in R/3 side when i am extracting data from it.
i checked with WE07 it's shows the error as follows
"Application document not posted".
it's been urgent how to resolve this issue. please through a light on it.
Regards
Harikrishna N

Hi Hari,
You start error processing by executing the corresponding work items in your Business Workplace. If a file read error could be corrected, for example, the IDocs which have not yet been read can be read and stored in the database manually, by starting report program RSEINB00.
This could be the reason for ur error..
IDoc could not be generated under MC
EDIN: Evaluates the partner data from the MC record
TS70008037
No process code in the additional partner profile MC parameters; Error when writing the application data in the IDoc.
this link givs u the req info
[http://help.sap.com/saphelp_nw70/helpdata/EN/dc/6b7f1543d711d1893e0000e8323c4f/frameset.htm]
Hope it helps U
Regards,
NR

Inbound idoc application document not posted

Hi,
idoc status is 51 i.e. application document not posted.. when im tyring to send the cm data to other system it is successfull and doing some modifications in that and the same is sent from the other non-sap system to sap system.
During the sending from non-sap to sap system, the inbound idoc is getting the error as 51. and also providing some field name as kna1-cassd is not an input field.
This field is not being provided with any value but still the idoc is getting error with this field.
"Even i tried in the sap system itself, taking some sample data tested in we19 and executing with inbound idoc f.m:IDOC_INPUT_DEBITOR.. still the idoc is getting error message as 51 (with the same field).
Please provide your valuable suggestions to solve this problem.
I had created one cm and tried but still the same message is comming.
Awaiting your help.
thanks
rohith

Thanks for all your suggestions..
The problem is that im using the standard function module:IDOC_INPUT_DEBITOR..
So, this function module cannot be modified which is not my requirement.
My requirement is that i will send an outbound idoc to some non-sap system and now the non-sap system will make some modifications and resent to sap system (here in sap it is an inbound processing).
So, during inbound processing the status is showing as 51 due to the field kna1-cassd..
So i cannot make any customization but the inbound processing should be done and it should be saved into the db...
Hope you have got a clear requirement.
Waiting for your response.
Thanks
rohith

IDOC - Application object type not planned

Hi all,
I am doing an inbound idoc.... in TCODE we42, i trying to put function module which i created, attached to the process code.
However, when i put my function module ZIDOC_INBOUND to the process code... it comes out error, 'Application Object Type not planned.'
Why is this so?
Please advice...
Thanks and regards...
William Wilstroth

Sorry... i think this should be in Data Transfer section

Receiving ASN -- IDoc application error

Hi experts,
I am working on Auto-ID integration Scenario.
when i am sending ASN (DESADV.DELVRY03 IDoc) to receiving R3 system using XI, i am getting the following error,
POSEX field empty --> Application document not posted
I gone thru the IDoc documentation in we60 and found that POSEX field comes under E1EDL24 : Delivery Item segment and E1EDL41 : Reference data ordering party
I dont know which segment should get populated while generating ASN (DESADV.DELVRY03 IDoc). also there was no error generated in the sender R3 system while generating ASN.
If anyone knows about these IDocs please help me

Hi Amit,
The problem is behind the IDoc field POSEX which is mandatory to create Inbound delivery in the receiver R3 system.
When we send the ASN to receiver R3, the Inbound function module expects the data from POSEX field to send the datas to the Application.
Here i did some customization in the XI mapping program in order to get the item reference number(POSEX).
Solution:
POSNR field also refers to item number so you just map this field with POSEX.

Configure idocs for User management ack settings?

1. IDOC config idoc says acknowledgments should not be requested, and run idx_noale ? why should we turn off and how to do this ?
2. IDOCs sent to IS should not be processed by IDoc adapter, advises insert the relevant idoc types into exception table, execute report idx_select_idoctyp_without_is
why we need to configure explicitly for each relavant ido types?
thanks

Hi Kumar,
Receiver adapters that run on the Adapter Engine support system acknowledgments if they are requested by the sender. Acknowledgements 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. The RNIF and CIDX adapters are exceptions to this rule, since they also support scenario-dependent application acknowledgments. Sender adapters of the Adapter Engine do not request any acknowledgments.
This means, JDBC adapter does only send system acks, however IDoc adapter is requesting application acks. Therefore as mentioned by the previous poster, you have to disable acks for this scenario using report IDX_NOALE.
Also go through these documents for any further help:
http://sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how to handle acknowledgments for idoc.pdf
http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
I hope this clears all your doubts.
Regards,
abhy
PS: AWARD POINTS FOR HELPFUL ANSWERS.

Confirmation on Using IDOC Ack

Hi,
Suppose We have FileIDOC and IDOCFile scenarios
Q1) Wil these IDOC Ack ALEAUD is Applicable in case of IDOC is the Sender Only Or in case of the Receiver also??
Q2) This Ack is for SAP R/3 Sys Or Fo Xi Sys???
Regards
Suman

Hi,
In that case you can receive technical acknowledgement treating soap adapter as an end point. But it won't be an application ack. For more details you should visit two websites:
http://help.sap.com/saphelp_nw04/helpdata/en/0d/5ab43b274a960de10000000a114084/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
Q2) This Ack is for SAP R/3 Sys Or Fo Xi Sys???
regarding this question there are acknowledgement specific for integration engine, that one must be requested and IDOC acknowledments. that's two different things.
Regarding integration engine you can also read in help:
http://help.sap.com/saphelp_nw04/helpdata/en/f4/8620c6b58c422c960c53f3ed71b432/frameset.htm
Kind regards,
Wojciech

How to suppress the Acknowledgement Error in IDOC to File scenario?

Hi -
I got the status in SXMB_MONI as 'Processed Successfully' for the IDOC to File scenario but the Acknoledgement status throws an error saying 'Acknowledgement not possible'.
I read one of the documents in the forums on how to suppress the acknowledgement using a table on R/3 side using IDXNOALE,
i tried that option but i still get the 'Acknowledgement not possible' error.
Is there any other way to suppress this error?
Thanks,
Tirumal

Hi Tirumal,
Receiver adapters that run on the Adapter Engine support system acknowledgments if they are requested by the sender. Acknowledgements 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. The RNIF and CIDX adapters are exceptions to this rule, since they also support scenario-dependent application acknowledgments. Sender adapters of the Adapter Engine do not request any acknowledgments.
This means, JDBC adapter does only send system acks, however IDoc adapter is requesting application acks. Therefore as mentioned by the previous poster, you have to disable acks for this scenario using report IDX_NOALE.
Also go through these documents for any further help:
http://sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how to handle acknowledgments for idoc.pdf
http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
Regards,
abhy

BPM and IDOCs

I have an scenario where I have to create sequentially several IDOCs. This can be created through BPM but my concern is each IDOC has to get processed before the next IDOC is created, is there a way I can check to see if the IDOC was processed. I was thinking of calling a BAPI to check if the IDOC was processed. Is there any other way to handle the above, if so would appreciate your input.
Thanks in advance for any suggestions.
Sunil Achyut

the standard way to check if an IDoc has been processed is to use the ALEAUD IDoc which serves like an acknowlegment for IDocs. XI will automatically translate the differenet IDoc status values into the corresponding acknowledgment status, so you can use a send step with application ack in the BPM and the BPM will only continue processing when an ALEAUD with a status corresponding to permanent positiv application ack has been received.
Here is some information on the usage of ALEAUD:
http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a6550507d11d18ee90000e8366fc2/content.htm
and here is a how to document for acknowledgments with IDocs using ALEAUD: https://websmp102.sap-ag.de/~sapdownload/011000358700003477212005E/HowTo_IDOC_Ack_20040817RR.pdf
Regards
Christine

IDoc application ack

Similar Messages

Maybe you are looking for