Introduction:
This article with cover the Idoc to file scenario with an acknowledgement back
to the sender ECC system using the Sender IDoc Adapter (AAE).
Requirement: In this scenario, when the idoc is triggered
from SAP and posted in the target SFTP/FTP server, the acknowledgment of the
successful arrival of the message needs to be sent back to SAP without actually
designing another asynchronous scenario. This can be achieved by using the ALEAUD
Idoc which in turn updates the original idoc status. The objective is to
provide the configuration needed to receive the acknowledgment back to ECC.
Basically, in the sender Idoc Adapter
(AAE), we have the following acknowledgements;
System acknowledgment: sent back when the request arrives at the
final receiver.
System error acknowledgment: sent back when a system error occurs
during message processing within SAP XI.
Application acknowledgment: sent back when the message is
successfully processed within the receiver application.
Application error acknowledgment: sent back when an error occurs
during message processing within the receiver application.
ALEAUD Special Handling Needed
Choose this option to enable the sender Java IDoc adapter to apply special handling to the incoming ALEAUD
message. The adapter replaces the IDoc number of the ALEAUD message with the
original IDoc number.
If the target system is a non ECC system, we may get only System acknowledgments. If the target system is an ECC system, we can get System acknowledgments as well as Application acknowledgments & we can select all the five options above, although the target ECC system will have to run the program ‘RBDSTAT’ to send the pplication acknowledgments.
Steps:
- We have the idoc to file scenario working to trigger the idoc and place the XML in
the SFTP server working as expected. - To receive the acknowledgment back into SAP, ALEAUD idoc needs to be configured in
SAP in WE20 to receive the acknowledgement in the form of ALEAUD idoc which in
turn updates the original idoc status.
In PI,
3. Configuration of IDoc sender channel: In the IDoc sender channel,
we need to provide the acknowledgment destination as an RFC destination which
points from PI to ECC.
4. In the tab ‘Ack Settings’, we need to select the acknowledgment parameters:
5. Persistence parameter in NWA: The persistence parameter is to be set as ‘true’ in NWA in
order to receive IDoc acknowledgments. The path of this parameter is NWA->
Configuration-> Infrastructure->Application Resource->Java IDoc
Adapter->Properties:
Note for Persistence:
If you want the IDoc information to be persisted in the DB, set the value to true, else set the
value to false.
- By setting the value to false, monitoring and acknowledgments cannot be monitored.
- When the value is set to false there is no database operation and hence the IDocs
are processed faster. - Message persistence is only done at the Messaging System for Adapter Engine. The
persistence here refers to correlation information which is required for
monitoring and acknowledgments handling. Hence setting the parameter is
necessary to get acknowledgements.
6. Test by triggering the idoc from SAP and receive the updated idoc status with ALEAUD
idoc.
In SAP– We find an inbound ALEAUD idoc triggered to update the
original ORDERS idoc (status was 03) status to 41.
In PI, there would be one message for the original outbound message and one for the inbound ALEAUD acknowledgment message.