AckRequestNotSupported

Hi,
I have a scenario which sends an acknowledgment back to XI(from here to external application) from ECC as an iDoc, here I've extended the standard iDoc: ALEAUD01. I configured the whole scenario, when i run the report RDBSTATE it creates the outbound iDoc successfully, and i could see the success message on XI through SXMB_MONI, but i always get the message " <SAP:Status>AckRequestNotSupported</SAP:Status>" on response,and it wont creates a payload for response and no acknowledge been passed to receiver.
I am using SOAP receiver for the external application, connection and user authentication is fine to the external application.
*SOAP Body: Manifest*
<?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" />
*SOAP Header: Ack*
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!--  Response
  -->
- <SAP:Ack xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1" applicationAckNotSupported="true" applicationErrorAckNotSupported="true">
  <SAP:Status>AckRequestNotSupported</SAP:Status>
  <SAP:Category>permanent</SAP:Category>
  </SAP:Ack>
Please help.
Thank you.

Hi,
Check if these links can help u
JDBC Adapter / Acknowledgements
ALEAUD not coming to SAP from XI & u0093Acknowledgment not possible" in idx5
Thanks
Vikranth

Similar Messages

  • AckRequestNotSupported error in IDoc to file scenario

    Hi,
    I have a scenario from IDoc to file adatper, when i try to run this scenario, every thing is ok except there is a error in message monitor.
    This error is regarding the Acknowledgment("Acknowledgment not possible"), But the ALEAUD IDoc have been sent to the orignal sender (IDoc side) with the empty content except the Header segment such as sender name, receiver name etc.
    And when i tracted the detail information in message monitor, i got the following error information.
      *<SAP:Status>AckRequestNotSupported</SAP:Status>*
      *<SAP:Category>permanent</SAP:Category>*
    I also went through some weblog and artical, i didn't got the solution.
    If some body also have this error?
    thanks & Best regards
    Rocky
    Following is My acknowledgment error information: FYI
      *<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>*
    *- <!--  Response*
      -->
    - <SAP:Ack xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1" applicationAckNotSupported="true" applicationErrorAckNotSupported="true">
      <SAP:Status>AckRequestNotSupported</SAP:Status>
      <SAP:Category>permanent</SAP:Category>
      </SAP:Ack>
    Outbound Acknowledgment content:
    - <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <SAP:TABNAM>EDI_DC40</SAP:TABNAM>
      <SAP:MANDT>030</SAP:MANDT>
      <SAP:DOCREL>700</SAP:DOCREL>
      <SAP:DOCNUM>0000000000036022</SAP:DOCNUM>
      <SAP:DIRECT>2</SAP:DIRECT>
      <SAP:IDOCTYP>ALEAUD01</SAP:IDOCTYP>
      <SAP:CIMTYP />
      <SAP:MESTYP>ALEAUD</SAP:MESTYP>
      <SAP:MESCOD />
      <SAP:MESFCT />
      <SAP:SNDPOR>SAPO01</SAP:SNDPOR>
      <SAP:SNDPRN>A01CLNT030</SAP:SNDPRN>
      <SAP:SNDPRT>LS</SAP:SNDPRT>
      <SAP:SNDPFC />
      <SAP:RCVPOR>SAPO05</SAP:RCVPOR>
      <SAP:RCVPRN>A05CLNT231</SAP:RCVPRN>
      <SAP:RCVPRT>LS</SAP:RCVPRT>
      <SAP:RCVPFC />
      <SAP:TEST />
      <SAP:SERIAL />
      <SAP:EXPRSS />
      <SAP:STD />
      <SAP:STDVRS />
      <SAP:STATUS>03</SAP:STATUS>
      <SAP:OUTMOD />
      <SAP:SNDSAD />
      <SAP:SNDLAD />
      <SAP:RCVSAD />
      <SAP:RCVLAD />
      <SAP:STDMES />
      <SAP:REFINT />
      <SAP:REFGRP />
      <SAP:REFMES />
      <SAP:CREDAT>0000-00-00</SAP:CREDAT>
      <SAP:CRETIM>00:00:00</SAP:CRETIM>
      <SAP:ARCKEY />
      </SAP:IDocOutbound>

    Hi Rocky,
    Check the below links of setting up of ALEAUDUT RESPONSE:
    /people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
    Check this document on handling IDOC acknowledgements. This might give you some idea.
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
    Please check the above two links if u have missed anything in setting up the acknowledgement.Let me know if u need furthur information
    Thanks,
    Bhargav.
    Note:Award points if found useful.

  • Problems with acknowlegment of soap

    Hi,
    I have the scenario idoc - xi - soap
    I sent the idoc to webservice but  the acknowledgment have a mistake:
    In the rwb
    Message processing failed. Cause: com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.
    For idocs I run the program IDX_NOALE for dont have acknowledgment but in the message in the moni I have AckRequestNotSupported and the channel communication have a mistake but the message is correct
    some have idea to eliminate this mistake
    Message processing failed. Cause: com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.

    Cvetaev,
    It appears that in the past few days you have not received a response to your
    posting. That concerns us, and has triggered this automated reply.
    Has your problem been resolved? If not, you might try one of the following options:
    - Visit http://support.novell.com and search the knowledgebase and/or check all
    the other self support options and support programs available.
    - You could also try posting your message again. Make sure it is posted in the
    correct newsgroup. (http://forums.novell.com)
    Be sure to read the forum FAQ about what to expect in the way of responses:
    http://forums.novell.com/faq.php
    If this is a reply to a duplicate posting, please ignore and accept our apologies
    and rest assured we will issue a stern reprimand to our posting bot.
    Good luck!
    Your Novell Product Support Forums Team
    http://support.novell.com/forums/

  • How to send application acknowledgement from R/3 system

    Hi guys,
          How to send application acknowledgement from R/3 system. Ex. we have post one IDoc and check user validations. Suppose date is wrong that means indicate earlier or wrong date but date format is correct. In this situation we need send one acknowledment to sender.
    How to find the solution? pls tell anyone.
    Regards
    Vijay

    Hi Vijay,
    Plz do perform the following steps:
    1) In the Integration Server, call transaction SE38
    2) Run program IDX_ALEREQUEST to process IDocs with message type ALEAUD as XI request
    message.
    3) Now Enter Sender Port, Sender Client,Partner Number, Partner Type, and Partner Rol
    4) In Integration Directory, configure the routing of interface
    5) Call transaction SXMB_MONI to display the XI message.
    Also,
    Further in IDX5 as well you will find entry for IDoc ALEAUD.ALEAUD01
    Please go through the link
    1)Succesful IDOC acknowledgements from ECC
    2)https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb
    3)https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
    After you triggered the IDoc by e.g. tcode: WPMA and IDoc reached FILE system, FILE receiver CC actually is only able to send acknowledgment types SystemErrorAck and AckNotSupported.
    This is because:
    - IDoc sender adapter requests the following acknowledgments:
    SystemAckRequested="false"
    SystemErrorAckRequested="true"
    ApplicationAckRequested="true"
    ApplicationErrorAckRequested="true"
    - File receiver adapter “that run on the Adapter Engine support system acknowledgments and system error acknowledgments if they are requested by the sender. These acknowledgments are triggered when a message is successfully processed by the adapter or if an error occurs while it is being processed.”
    If you haven’t suppressed acknowledgments for IDocs WP_PLU in IDX_NOALE in XI then you will get:
    SystemErrorAck – when message has not reached the FILE system
    AckNotSupported – for all others acknowledgement types
    QQ) Will this IDOC Ack applicable for this scenario???
    Rather not, since FILE adapter does not support any other acknowledgements then system and IDoc adapter does not request other acknowledgements then application + SystemErrorAckRequested.
    In sender system your IDoc will be always in status 39 (instead of 03), when acknowledgement is turned on.
    This is because:
    For SystemErrorAck the corresponding ALEAUD status is 56
    For AckNotSupported the corresponding ALEAUD status is 50
    Both inbound 56 and 50 statuses end up in 39 for your outbound IDoc in sender system.
    Q1) Will this ALEAUD Idoc contains any Message from File System????
    In both cases, it will result in status 39 - IDoc is in the target system. So it does not matter.
    Q2) Basically what Information will contain this IDOC Ack.
    Idoc number from sender system and status 56 or 50 depends on acknowledgement type.
    Q3) Do we receive any Info from the Target File System , if we implement this Ack concept??
    Nothing useful.
    Remember that “File Receiver has no way to determine if the written file has been correctly processed by the back-end application”. However, if your “FILE” application can read your WP_PLU message and after successful processing is able to generate any kind of message then you can acknowledge the communications but you will not be able to link original message with the acknowledgement request message.
    To do that you need to configure just normal scenario (that will be your new acknowledgement scenario) FILE -> XI -> R/3. Your FILE service will send ALEUAUD Idoc to R/3 system. Your FILE application must take care to generate proper ALEAUD XML message. In order to treat ALEAUD as a request message (not standard acknowledgement) you need to run IDX_ALEREQUEST in SE38 on XI.
    Q1) It means if the Idoc not reached to Target File system means we can able to get the System Error Ack to Sender SAP R/3 System. Am i Right????
    Supposed you have turned off acks on XI (tcode: se38, IDX_NOALE) for your sender port/client:
    You have sent the IDoc and the last status is "03 - Data passed to port OK"
    You don't know whether it was even delivered to XI ...
    Supposed you have turned on acks on XI (tcode: se38, IDX_NOALE) for your sender port/client.
    1)
    You send and IDoc and it has been delivered successfully to FILE system.
    Adapter Engine creates acknowledgement type: AckNotSupported
    In XI you can see Ack Status: AckRequestNotSupported (Acknowledgement not possible). Category: permanent.
    XI will send ALEAUD IDoc to R/3 system: status "50 - IDoc is added"
    The IDoc status in sender will be "39 - IDoc is in receiving system (ALE service)".
    2)
    You send and IDoc and it has not been delivered successfully to FILE system. e.g. FILE server is down.
    Adapter Engine creates acknowledgement type: SystemErrorAck
    In XI you can see Ack Status: Error (Acknowledgement contains system errors). Category: transient.
    XI will send ALEAUD IDoc to R/3 system: status "56 - IDoc with errors is added"
    The IDoc status in sender will be "39 - IDoc is in receiving system (ALE service)".
    So status 39 means only that IDoc reached XI, but you don't know whether it was delivered to FILE system or not.
    Q2) And one more thing is Even though we are dealing with the IDOCFile OR FileIDOC we can able to get the ACk of Type System Error Ack only. Am I Right?????
    No, "Sender adapters of the Adapter Engine do not request any acknowledgements."
    Q3) So the same case( Which we disscused for IDOCFile) is Applicable for FileIDOC also????
    No.
    Can we able to get the System Error Ack, if the File is not reached to SAP R/3( Target here)
    No.
    Q4) If Yes to Q3 means,Where this System Error Ack will be seen in File System side???
    Do we need to do any extra settings to receive these System Error Ack at File system side??
    Not relevant.
    Regards,
    Vinod.

  • SOAP Receiver Acknowledgements (File XI SOAP)

    Hello Friends,
    can some one help me on this issue? I want to suppress all Aknowledgements on the receiver SOAP Adapter.  Is there any How to guide for SOAP Acknowledgement?
    By the way; I have have been configured;
    SXMB_ADM > Runtime > ACK_SYSTEM_FAILURE > 0
    but nothing is changed and i get the same error (see below)
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Technical Routing of Response
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="OUTBINDING">CO_TXT_ROUTING_BACK_ERROR</SAP:Code>
      <SAP:P1>,XXXXXXX</SAP:P1>
      <SAP:P2>XXXXXXX,XXXXXX,,</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Es ist ein Fehler beim Zurück-Routing aufgetreten Fehler beim Kommunikationskanal aufgetreten.</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
        <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Technical Routing of Response
      -->
    - <SAP:Ack xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Status>AckRequestNotSupported</SAP:Status>
      <SAP:Category>permanent</SAP:Category>
      </SAP:Ack>
    Thanks,
    Fth

    Hi Fatih,
    Check if these links can help u
    JDBC Adapter / Acknowledgements
    ALEAUD not coming to SAP from XI & u0093Acknowledgment not possible" in idx5
    **Reward if helpfull**

  • Acknowledge problem

    Hi
    I am trying to implement acknowledgement in ABAP client proxy, intend to get acknowledgement from receiver.
    but when I am writing abap code, I found there is no if _ wsprotocol _ async _ messaging in our SAP system,our SAP system version is WAS 620 with SAP_BASIS patch 0043 SAPKB62043, and APPINT 200_620 0006 SAPK-20006INAPPINT
    If I want to use acknowledgement, do I need to upgrade, which level I need?
    thank you very much

    > No , I do want to get an IDoc acknowledgment in system level, and I know it is not possible to get an application level acknowledgment due to receiver is an file adapter
    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)
    Regards,
    Jakub

  • Error in the Acknowledgment

    Hi,
    Can anyone help me?
    I have a scenario of ABAP Proxy - PI - Web Service.  This is an asynchronous interface and the message is being sent from sender to receiver system.  The problem is, I'm receiving an error in the acknowledgment with status AckRequestNotSupported.
    I want to turn this thing off or make it work for my interface.  Could anyone suggest something?
    Thank you so much.

    Turn off acknowledgements by running report IDX_NOALE.
    Read more about acknowledgements [here|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe] or [here|http://wiki.sdn.sap.com/wiki/display/ABAP/HandlingIdocAcknowledgements]

  • Acks and Adapter metadata ?

    How many types of acknowledgements are there and how to create it ?
    What is adapter metadata ?

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

Maybe you are looking for