Query on IDOC Ack (STATUS) config in XI for a specific partner comm.

Hi Experts,
Is it possible to configure the IDOC Ack (STATUS.SYSTAT01 message) in XI for a specific partner communication? We want to configure our system like ALEAUD but the message type should be STATUS.SYSTAT01 and the acknowledgment should be send to sender system for a specific partner only if XI receives any IDOC like (Orders) from that specific partner. For other partners (same sender system) we donu2019t want this acknowledgment settings and configuration. If possible please provide the configuration filters steps etc. Thanks for your valuable inputs in advance.
Thanks,
Satish
Edited by: Satish Jaiswal on Jan 8, 2009 2:55 AM

Hi Husain,
I have the document you have mentioned. Please note my requirement is to filter the Ack while creating and sending to R/3 based on Partner and Message type. The document provides info only on Message type filter but not parner specific for same sender system!!! Any help appreciated. Also note: BPM and Alert is out of scope.
Looking for  some ALE configuration tricks to achieve this.
Thanks
satish
Edited by: Satish Jaiswal on Jan 9, 2009 2:40 AM

Similar Messages

  • IDOC Ack status back to XI/BPM ?

    Hi
    i have done File to Idoc scenario, and want to get acknowledgemnents inside XI/BPM.
    i hv proivded port,client,message type and selected 'Request acknowledgement' tab and executed report 'IDX_NOALE'. but im not getting any acknowledgement status in moni. please suggest hw could i get Idoc acknowledgements in XI.
    1.Do i need to import ALEAUD Idoc into XI ? and Is any configuration required in ID for ALEAUD?
    2.Is it possible to map Idoc status back into BPM? if yes, please explain how BPM should design?
    3.once Idoc ack status received inside XI, is it possible to send same status to the back end sender system?
    appreciate your help..
    Regards,
    Rajesh

    hi
    1.Do i need to import ALEAUD Idoc into XI ? and Is any configuration required in ID for ALEAUD?
    By default, audit idocs will come and get tagged to the IDoc. If you want to send it to the file system, all configurations must be done for IDoc to file scenario for the audit IDoc.
    2.Is it possible to map Idoc status back into BPM? if yes, please explain how BPM should design?
    Yes, it can be done. But won't be reqd in ur case.
    3.once Idoc ack status received inside XI, is it possible to send same status to the back end sender system?
    Yes, Q1
    Check this document on handling IDOC acknowledgements.
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
    rgds,
    Arun

  • IDOC Acks not working

    Hi All,
    I have spent hours searching SDN for this specific problem, and can see some similar threads but none with a successful answer, so I will ask again.
    I have the following scenario:
    R/3 system sending an IDOC to XI, then XI mapping that to a custom XML message and sending it via the HTTP Adapter to an external business partner.
    We have no issues with the above and get a chequered flag in SXMB_MONI.
    But we want an Acknowledgement of that transmission to go back to the initiating IDOC in the R/3 system and update the status. e.g. If there was a HTTP comms failure and the message ended up in error in SXMB_MONI then we want that status sent back as an Acknowledgement to the original IDOC so that the R/3 system is aware of the failure.
    We can see that XI tries to send the Ack back, but in SXMB_MONI in the "Ack Status" column there is an error associated with the Ack which says either "Acknowledgement not possible" or "Acknowledgement contains system errors". When we look into the error message contained within the Acknowledgement it says:
    Unable to convert the sender service XXXXX to an ALE logical system
    The Sender Service listed in the error message is the original Receiver Service which passed on the HTTP message to the 3rd party receiver. But in this case it is the sender because it is trying to send an Ack back to the R/3 system that is now the Reveiver. Note that it is a Business Service (not in SLD), it is NOT a Business System.
    My question is - where is XI looking for an ALE Logical System name? My Business Service is not in the SLD (doesn't need to be, it's a 3rd party external system and I can send to it fine). I even tried populating the Adapter Specific Identifers for this Business Service with the IDOC Logical System name and R/3 System ID and Client, but that did nothing becasue this isn't using the IDOC Adapter, it's using the HTTP Adapter.
    And note that we have SXMB_ADM param RUNTIME-ACK_SYSTEM_FAILURE = 1.
    And please dont post a bunch of links, I've looked at every message in SDN that refers to the above. Please only reply if you can type the exact answer and it refers to the Acks only.
    Thanks,
    Brendan.

    Hi,
    Open(Double click) the Receiver Business service in ID and goto Change mode
    goto Adapter Specific Identifiers---just give the LS name as HTTP and click on Apply and save Activate.
    Do SXI_Cache also
    Now try to post the Idoc Again from R/3
    Regards
    Seshagiri

  • IDOC ack

    Hi,
    i have put in a production support team and the project team which implemented the project has moved out. so i cant ask any project team member now
    There are nearly 3 scenarios configured for IDOC -XI-IDOC and they are driving me crazy. All are running fine. But their ack status is driving me crazy. In one scenario it is showing Waiting for ack for all msgs of this scenario.
    In second scenario, there is again a scenario IDOC - XI - IDOC running in XI Prd system like System A - XI prd - System B. It is running fine. The problem is in SXMB_MONI for ack status there is a green tick coming and when i double click the msg to open it, then on double clicking this success ack msg, shows the error CO_TXT_ROUTING_BACK_ERROR saying Error occurred during back-routing Error in communication channel because the path System B to System A http://sap.com/xi/XI/Message, Acknowledgment is not found. This is leading to a lot of error messages in RWB msg monitoring at IE level in System Error status because of these ack msgs.
    The third scenario is again IDOC - XI - IDOC and it is also running fine without anything in ack status column in SXMB_MONI - which is totally fine.
    I have saw the complete XI prd scenarios and no where ALEAUD is configured. So the above ack in scenario 1 and 2 seems to be a transport level ack. I do not want any ack status for any scenario. How to rectify this thing so that it does not see for ack status at all? Please help.

    Hello,
    You can check this link http://help.sap.com/saphelp_nwpi71/helpdata/EN/ab/bdb13b00ae793be10000000a11402f/frameset.htm and then scroll down until you see section 4 and section 5. Section 4 will tell how to disable acknowledgements, but it would be best to consult with business since you are planning to disable it in production.
    Hope this helps,
    Mark

  • Idoc ack in PI

    I am working on IDOC TO FILE scenario where i have the req like dont want to show idoc acknowledments status in PI (sxmb_moni) with question mark symbol which indiactes still waiting for acknowledmantes.
    I dont want messsages waiting for acknowledmantes in PI . Please let me know how to achive this?

    Hi Praveen,
    You will need to run this on PI if you want to turn off ALE Acks.....
    Hope you know what you need to do, if you don't here is what you need to be doing to turn off ALE Audit
    To achieve this add the PORT, CLIENT and MESSAGETYPE of the IDOC to the table IDXNOALE in PI
    1.RUN the report IDX_NOALE
    2. PORT
    3. CLIENT:
    4. Exception List: Add Message Type of IDOC
    5. Click 'Not Request Acknowledgement'
    6. Execute Button.
    Verify the table IDXNOALE
    1. SE16: IDXNOALE
    2. Table should have the change entered.
    Try your way around with this method. you'l get what your looking for
    Cheers!
    Hanish John

  • Idoc reprocess status 03

    hello
    i need to reprocess idocs in status 03 through bd87
    but it is not allowing
    please help

    Hi Manu,
    Looks like you are trying to reprocess the IDOC which is already processed correctly.
    Unfortunately there is no way by which you can do it.
    I can give you a work around though:
    1) Go to WE19 enter your IDOC number which already has status 03 and execute.
    2) On next screen it will display the IDOC, choose approporate button on toolbar (standard Function Module) to process it.
    3) This will generate the new IDOC similar to the one which was posted completely.
    4) Now the new IDOC should have status ready (Unless you have clicked Process Immediately in WE21 for this message type, it shud be execute by Background Job).
    This approch is applicable for testing.
    Let me know if it solves your query.
    Regards
    Shital

  • Ack Status

    I am passing IDocs from SAP 3.1 to 4.7 via XI and in SXMB_MONI the <i><b>Ack Status shows "?"</b></i> this sign and says <u><i><b>Still waiting acknoweledgement</b></i></u>. Can any body tell me what are the settings need to done to fix this .

    HI manish,
    This is because your system acknowledgement is activated but not configured.
    If you do not want to receive ack, Run report IDX_NOALE and deactivate ack for the IDocs you want.
    Regards
    Vijaya

  • Ack Status - Still waiting acknoweledgement

    Hi experts,
    I have this Ack Status (? Still waiting acknoweledgement) in my SXMB_MONI with an IDOC -> XI -> JDBC scenario.
    How can I configure Ack in order to fix this or disable this configuration in case I don't want it?
    Points will be given,
    Regards,
    Daniela

    <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe">Howto- Handle IDoc Ack</a>

  • Reprocessing IDOC with status 52

    Hi,
    I got status 52 for one of the IDOCs, I want to reprocess it . When I use BD87 & BD73, those are not working.
    Please tell me any other way to process it.
    Thanks & Regards
    Vijay

    Hi..Vijay,
    There are already many threads with the same question.
    pls search for your query before posting.
    Eg:
    Re: Idoc status 52 -> How to make it green i.e. 53
    Reprocessing IDOCS with status 52
    regards,
    Padma

  • IP Job in BW finished, but how can I check the IDoc receive status in BW ?

    Hi,experts
    After I execute a Infopackage with loading more than 200000 records data, the infopackage monitor show me yellow light, 186020 from 200000 records. this infomation still show me till now, seaval hours,it looks pause here.
    And I check the request in the R/3, the Job has finished. as you know it means the R/3 push the IDoc already finished.
    and how can I do now ? or how can I check the IDoc receive status in BW side?

    Hi,
    I too had the same problem, i executed the following to solve the proble, may be this will help you:
    1) Go to T-code SM58 and select TRFC and press F6,
    2) For manual push of I-Docs, GO to T-COde BD87 select perticular idoc and see the status if it is not executed properly then do the manual push by pressing Execute option,
    Thanks,

  • How to cancel an idoc in status 64

    How to cancel an idoc in status 64

    Hi Manju,
    If you have table updation access then
    Go to SE16 --> Table EDIDC --> Give your "IDoc number" -->  change the status from 64 to "73 IDoc archived".
    Or you can ask to your ABAPer to do that.
    Hope it helps,
    Regards,
    MT

  • STPPOD Idoc creation status : Error in ALE Service

    Experts,
    I am trying to send GR from MM to SUS in MM-SUS Classic Scenario on ECC 6.0 Server. I have also configured Goods REceipt Notifications Functionality to sending GR from MM to SUS.
    When i am trying to send GR Idoc is generated (STDPOD) but i am getting the Error whose status - 29 in WE02 t-code :
    Status Message for Selected IDoc
    Status Text:   IDoc: 0000000000211243 Status: Error in ALE service
    T100 Text:     Entry in outbound table not found
    While i have properly configured Partner Profile for  Message Type STPPOD :
    Partner Role          Basic Type     Receiver Port           Application     Output Mode
    LS        DELVRY03       A000000018 (XI port)           GRN               Transfer Idoc Immediately
    When i try WE19 t-code for this idoc, i found  the error "Port '' does not exist in the table of port descriptions"
    while  i have already defined port (A000000018)in WE21 t-code  and this port also working fine for other messages.
    Please suggest.
    Thanks.
    Regards,
    Pawan Keshwani

    Nikhil,
    Issue is resolved it was the wiered error. As i removed LS from the field  Partner Role in STPPOD message at  partner profile(WE20) for SUS Client in ECC. Now the message STPPOD outbound message working fine.
    Thanks.
    Regards,
    Pawan Keshwani

  • SAP IDOC shows status 03, but no file is written

    We have SAP configured to generate delivery IDOCs when the SAP Delivery document is posted/saved. The IDOC is initially created with status 30. There is batch job RSEOUT00 every 30 mins that collects the IDOCs in status 30 and converts to status 03. When we review the IDOC processing screen, even though they are in status 03 and successfully written outside of SAP to a folder, there is no file in the folder. We are missing IDOCs. There is no real time external system integration. We are simply trying to write IDOC files to a folder.
    Can you some please share your insights on how to resolve this issue?
    Thanks in advance
    Satish

    RFC destinations, Logical systems, and then Partner profiles needs to be maintained. and You need to create the Distribution model  in sender system.
    Partner profiles maintained in both the systems, soure Outbound properties
    Target Inbound properties.
    if you have two clients in system it will be easily you can check.

  • 5 IDOC with status 29 Error in ALE service

    hi there,
    im looking at this similar problem with less information on me the only info i got is this can anyone help me out pls
    IDOC Status Outbox:
    IDOC failure between 13/07/2008 to 14/07/2009
    1 IDOC with status 02 Error passing data to port
    5 IDOC with status 29 Error in ALE service
    IDOC Status InBox:
    88 IDOC with status 51 Application document not posted
    regards
    raju

    Hi,
    Check this thread.
    DB13-DBCHECK by saving log-throwing DUMP:TSV_TNEW_BLOCKS_NO_ROLL_MEMORY
    Regards.

  • Idoc- can we sent already sended idoc if status is showing error message

    hi
    Idoc- can we sent already sended idoc if status is showing error message
    without making any changes.
    Thanks in advance.

    Hi raja,
    IN BD87.
    give the idoc number,its status,messagetype and partner system and resend it.
    Regards,
    nagaraj

Maybe you are looking for