IDOC acknowledgements

[Former Member]

Hello All,

This is a IDOC - XI - File scenario. The scenario works fine and the file is generated as expected. But the IDOC ack has error status in SXMB_MONI. The error msg is "Acknowledgement not possible". When I open the msg in SXMB_MONI and double click on <b> Acknowledgement Id</b>, the following is displayed in the window

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> 
- <!--  Response 
  --> 
  <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7" />

Do I need to maintain partener profile value for ALEAUDIT under Outbound or Inbound sections? I have not done this. Is this the reason for this error?

Regards,

Jai Shankar

[Former Member · Accepted solution]

You can turn of this message via the report IDXNOALE(select your message type ie IDOC Name).

[Former Member · Accepted solution]

Sekhar,

>>You can turn of this message via the report IDXNOALE(select your message type ie IDOC Name).

Thanks. But I want the acknowledgement back in R/3. I dont need to turn off the acknowledgement.

@Chilla,

My sender IDOC has partner type Logical system only.

Regards,

Jai Shankar

Message was edited by:

Jai Shankar

[Former Member · Accepted solution]

Hi Sekhar,

it is IDX_NOALE.

You use this function to define for a particular sender port and client which acknowledgments are requested from the sender

see below link

http://help.sap.com/saphelp_nw04/helpdata/en/44/932e8896b610bbe10000000a422035/content.htm

Regards

Chilla

[Former Member · Accepted solution]

Hello All,

I tried to add ALEAUDIT under Inbound parameters. Now I tested my scenario again. This time, there was ALEAUDIT IDOC posted successfully back to the R/3, but still I see the symbl "<b>Acknowledgment not possible"</b> icon in SXMB_MONI for my msg.

I opened the msg and copied the msg id of Acknowledgement and saw the status. The status of the msg is successful. But this msg also has the Ack status <b>"Acknowledgement not possible"</b>

What am I missing here? Am I mot supposed to get Ack status successful in monitoring?

Thank You.

Regards,

Jai Shankar

[prateek · Accepted solution]

<i>Am I mot supposed to get Ack status successful in monitoring? </i>

Yes. U ll not get it.

u may ignore this.

Am I mot supposed to get Ack status successful in monitoring?

Regards,

Prateek

[bhavesh_kantilal · Accepted solution]

jai,

Exactly what I was wondering this morning as well.

Another interesting fact which I noted,

1. For the idoc to file, the Check the ACK tab under the SOAP Header. The status will be Ack Not possible and Permanent.

2. The same thing for an idoc to idoc, the AckTab will contain Acknowledgement status and Transient.

Also have a look at the Aleduit in We02 of your R3 ,you will see the difference in the Ale Audit Content.

My undrstanding this, ALEAUDIT is used for Application Acknowledgements, in the case of Idoc to File, you can only send back a Transport Acknowledgement and that is exactly what has happened here. The Ack status says Ack cannot be sent, and also the AleAudit that reaches the Source does not contain much info when compared to a ALEAUDIT sent from a R3 system.!

Regards

Bhavesh

[Former Member · Accepted solution]

Bhavesh,

You are correct. File adapters do not support application acknowledgements.

So, just deleted receiver agreement for the scenario and made system (error) acknowledgement. This is supported by File adapter.

Now, the status of ack node has the following

  <SAP:Status>Error</SAP:Status> 
  <SAP:Category>transient</SAP:Category> 
  </SAP:Ack>

Also, the ALEAUDIT idoc in WE02 displays the error text and some more info.

Final point is ALEAUDIT can be used for System error acknowlegement and application acknowlegement if supported by the target.

Pls correct me if my understanding is incorrect.

Regards,

Jai Shankar

[bhavesh_kantilal · Accepted solution]

Jai,

The AleAduit sent in the case of Idoc to File if the file is posted successfuly is not actually a App Ack, and that is why we get the info Ack not possible.

But, as the R3 might expect this Idoc, XI still sends it back to the Source R3 system.

I guess this is the only logical conclusion.

Regards

Bhavesh

[Former Member]

HI,

ALE audit is only possible for IDocs of type logical system (LS).

So no need to do any configuration for acknolwledgment. Unless if you have the receiver is also R3 receive Idoc.

Regards

Chilla

[former_member529475]

Hi Jai

Find the solution.

This Feature is Available under SP 18 and we are on SP16

http://help.sap.com/saphelp_nw04/helpdata/en/42/c8f66bc7a56bb0e10000000a1553f6/frameset.htm

Check this document on handling IDOC acknowledgements. This might give you some pointers.

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50...

Cheers..

Vasu

<i>** REward points if it helps you **</i>