on 02-11-2009 10:15 AM
Hi all,
Is it possible to receive a system aknowledgement from the fileadapter when a message (IDoc) has passed trough the adapter engine, without using BPM.
Not a application aknowledgement! but a system aknowledgement!
When I try I get the following message in the IDoc monitor: "aknowledgement not possible".
And guys, please do not post one billion links. I have gone through them all, and they don't give me the answer.
Thanks
System ack is received only when it is requested at sender. For idoc as sender, it requests for application ack and not system ack. This is the reason you are getting "acknowledgement not possible". File adapter won't support applicatin ack. For system ack, you will have to configure BPM.
Regards,
Prateek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
But AFAIK confirmation of the idoc can be possible from XI by default all you need to do is confiure recei ver CC for the business system of R/3. (idoc type is ALEAUD01)
i have worked for this scenario and even in XI it is showing ackNotPossible but i am able to see this in R/3
Are you expecting SYIDOC01 type then it will not be send by default.
I hope i am in correct context .correct me if not
BR
Rajesh
No need of receiver determinations etc.,,
but SNDPRN will be taken from Business system of File/thirdpartys adapter specific identifier and RCVPRN will be R/3 Business systems Adapter Specific identifier (ASI)in ALEAUD idoc
so make sure the partner is there in R/3 for processing ALEAUD01 .
File Business system ASI should be there in R/3 and it should have inbound parameters for ALEAUD to process
Hope this is clear any doubt do post
Regards
Rajesh
IDOC outbound from R/3
SNDPRN - R3SNDR
RCVPRN - FILERCVR (assume with these parameters idoc is coming to PI)
IDOC Business system should have adapter specific identifier as - R3SNDR
File Business system should have - FILERCVR
While generating ALEAUDO1 it will have from PI
SNDPRN - FILERCVR
RCVPRN - R3SNDR
SO in R/3 you should have partner profile FILERCVR with inbound processing for ALEAUD
Hope its clear
Rajesh
I get the following error for the return message in adapter engine:
Error Category: IDOC_ADAPTER
Error Code: ATTRIBUTE_INV_SND_SERV
Message: Unable to convert sender service THN_TEST to an ALE logical system.
So it seams that a message is being sent back to the R/3 system, but is stopped in the Receiver IDoc Adapter.
Any ideas?
Thanks!
Thanks Rajesh, my ALEAUD01 has now status 53.
One last question before i close this:
Is it normal that my we05 IDoc monitor shows first the outbound (MATMAS) IDoc with status 39 and the on the next line the ALEAUD01 with status 53. (shouldn't the outbound IDoc somehow be connected with the acknowledgement?)
Thanks
Hi ,
I doc Does not support Synchronous Communication And In case if you want any system acknowledgment it is Very difficult because There Are "N" Number of messages Been processed in XI so how Would you figure out the Acknowledgment is for which Message......
You can Create alert Configuration to send an email if the error Occurs.
Regards,
Sainath Chutke
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Did you check in sender system is there any idoc ALEAUD01 received or is there any error in SXMB_MONI.
It is possible to send idoc ack (sys) back to sender system .
Do let us know the exact error you are facing will help to identify the problem area.
Rajesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
80 | |
9 | |
9 | |
7 | |
7 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.