Acks and Adapter metadata ?

[Former Member]

How many types of acknowledgements are there and how to create it ?

What is adapter metadata ?

[Former Member · Accepted solution]

ACKs :

here 2 types of ACKs are there, one is Transport ACK and second one is Application ACK.

Transport ACK : it tells the data reached the target or not.

In SXMB_MONI we can view this status by watching the

ACK status field.

Application ACK : it tells the data reached the target or not and after reached to the target it processed success or not in the target system.

By using some settings in XI and ABAP we can get the Application ACK

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

Adapter metadata : It is a data about the data.

Metadata defines the part of a communication channel that is specific to the adapter.

The functions for creating and editing adapter metadata are intended for parties

developing new adapters. Its used for following the user interface in ID and save

the configuration data in the database. The adapter metadata is an XML document.

[former_member537867]

Hi chandu devina ,

Acknowledgments enable you to confirm that an asynchronous message has been received. You must explicitly request acknowledgments in the application program and can specify what kind of confirmation you want to receive.

Different types of ackmnts are:

System acknowledgement:Positive system acknowledgment.

The receiver was reached successfully. For server proxies, this means that the implementing class for the server proxy was found and that the method for inbound processing could be called.

SystemErrorAckRequested:Negative system acknowledgment.

SAP Exchange Infrastructure runtime reports that an error has occurred during transfer or processing of the message on its way to the receiver. For example, an error in a mapping program or a missing server proxy in the receiver system could trigger this acknowledgment

ApplicationAckRequested:Positive application acknowledgment

The message was processed by the receiver successfully.

ApplicationErrorAckRequested:Negative application acknowledgment

An error occurred during message processing at the receiver.

IDoc sender adapter requests the following acknowledgements:

SystemErrorAckRequested

ApplicationAckRequested

ApplicationErrorAckRequested

File receiver adapter supports only system acknowledgements and system error acknowledgements if they are requested by the sender.

So you will get:

SystemErrorAck – when message has not reached the target system

AckRequestNotSupported – for all others acknowledgement types (your case is here)

For IDOC, you could have ALEAUD as an acknowledgment IDOC.

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...

have a look at the Alert Framework, which can be configured to send mails to specific persons if an interface processing fails.

http://help.sap.com/saphelp_nw04/helpdata/en/80/942f3ffed33d67e10000000a114084/content.htm

There are two types of JDBC acknowledgements Transport level and application level.

IF the JDBC call is asynchronous you can set up for transport level acknowlegement in the send step in ur BPM.

if the JDBC call is synchronous then JDBC adaptor will generate a response message with a tag update count, which gives you the number of rows that were updated.

refer to the following link, which details about reciever jdbc

http://help.sap.com/saphelp_nw04/helpdata/en/2e/96fd3f2d14e869e10000000a155106/content.htm

just check out these links

http://help.sap.com/saphelp_nw04/helpdata/en/29/345d3b7c32a527e10000000a114084/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/7b/94553b4d53273de10000000a114084/content.htm

The following link has entire configuration of Receiver XI Adapter (including acknowledgements)

http://help.sap.com/saphelp_nw04/helpdata/en/f4/0a1640a991c742e10000000a1550b0/content.htm

ADAPTER METADATA:

With adapter metadata you can define configuration data needed for a certain type of adapter at design time. Adapter metadata define the part of a communication channel that is specific to the adapter type.

The functions for creating and editing adapter metadata are intended for parties developing new adapters. They are not intended for general use.

For more information about adapter development, see Adapter and Module Development.

You can export adapter metadata as an XML file and import it into the Integration Directory. In this way you can provide the configuration with new adapter types.

To export adapter metadata, choose Adapter Metadata ® Export XML Description in the object menu bar.

SAP ships adapter metadata for all the adapter types it provides. You can find the adapter metadata shipped by SAP in software component SAP BASIS, software component version SAP BASIS 6.40, in namespace http://sap.com/xi/XI/System.

You can find adapter metadata in the corresponding namespace in the navigation tree of the Integration Builder (Integration Repository) under Adapter Objects ® Adapter Metadata.

For more details see the below link

http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm

Regards,

Vinod.

[Former Member]

there are two types:

system acknowledgements

Application acknowledgements

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."

check the below link for how to handle ack for idocs(sampe)

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b...

Note: reward points if solution found helpfull

Regards

Chandrakanth.k

[Former Member]

With adapter metadata you can define configuration data needed for a certain type of adapter at design time. Adapter metadata define the part of a communication channel that is specific to the adapter type

See the below link

http://help.sap.com/saphelp_nw04/helpdata/en/44/11982eb8da648fe10000000a1553f7/content.htm

about metadata check the below links

http://help.sap.com/saphelp_nw04/helpdata/en/5d/986740eded960ae10000000a155106/frameset.htm

http://help.sap.com/saphelp_nw04/helpdata/en/10/cd6040bc1ccd01e10000000a155106/frameset.htm

Note: reward points if solution found helpfull

Regards

Chandrakanth.k

[Former Member]

Hi,

There are 2 types of Acknowledgements:-

System acknowledgments used by the runtime environment to confirm that an asynchronous message has reached the receiver. for e.g in File Adapter, if ftp server is up and running/or Folder name exists etc

Application acknowledgments used to confirm that the asynchronous message has been successfully processed at the receiver. from SAP help.

http://help.sap.com/saphelp_nw2004s/helpdata/en/f4/8620c6b58c422c960c53f3ed71b432/content.htm

Integration process acknowledgements

Integration Porcess ack:

http://help.sap.com/saphelp_nw04/helpdata/en/43/65c42db39b0398e10000000a1553f6/content.htm

Meta data:

*****Reward points if it is helpful*******

Thanks,

Madhu