How t Build Orchestration to send data to SAP using MySAP Business Suite v2.0 RRS feed

  • Question

  • Hi All,

    I want to optimise my solution where i have scenario where i need to pick xml's from 60 different folders specified for 60 different RFC's.

    So the folders are remote share folders, i used file adapter to pick the xml's and send xml's to SAP in reposnse SAP gives back xml which i further send to reponse folders.

    As number of files will be more in a day i can expect 2000 files. And requirment is to intimate some admin about the failure in communication with SAP or any other error after retrying for some time. And later admin can resume the transactions after checking for error.

    I am stuck at point, i had set retry interval to say 6 hours, and then how can i notify the admin after retry attempts have been exhausted.. about this so that he can restart the transactions.

    Also pls advise would there be any solution suppose if there is some error or issue biztalk dumps files to some folder and we can notify admin about this and admin can reinitiate the transactions.

    My only concern is no data in xml's should be lost and with minimum delay action can be taken.

    Pls advise..


    -- Kind Regards Sandeep
    Saturday, January 7, 2012 11:59 AM

All replies

  • You need to build some exception handling framework to acheive your requirements.

    For example to meet the above scenario you can capture the delivery failure and route the messages to a folder and have some other biztalk process read the folder and sent out notification.

    If not retries are required then u can have that built in same orchestration which will get the acknowledgement from the send port and on receipt of NACK u can have a process to send out notifications.

    Some good explanation can be found on below link




    Monday, January 9, 2012 4:09 AM
  • The best and recommended solution for supporting IT team is monitoring tools. See this article by Steef to know about different monitoring tools available for BizTalk.

    Though not a good approach but for the time being you can use the Delivery Notification to report failures to Administrator.

    Please mark the post answered your question as answer, and mark other helpful posts as helpful, it'll help other users who are visiting your thread for the similar problem, Regards -Rohit Sharma (
    Monday, January 9, 2012 9:20 AM
  • Hi All,

    Pls advise when the retries to a port gets exhausted, can i able to re initiate the transactions. Because doing so i do get xml from SAP but i see message gets suspended and i see Response XML from SAP with error NACK xml along with it..

    Also if suppose i do not use retry and catch exception in orchestration then sending xml to admins means filling up his mail box.

    Pls advise how to handle this...

    -- Kind Regards Sandeep
    Tuesday, January 10, 2012 6:46 AM
  • Did you check on the SAP end what was the error for whcih it had sent a NACK.

    As far as exception handling is concerned yes you will be filling the mailbox if number of failures are high :-)



    Tuesday, January 10, 2012 10:43 AM
  • Hi,

    Yes, at one instance the login id i configured in SAP Adapter to call RFC is blocked after 31st Dec 2011. So all transactions on 1st January 2012 went for retry and afte retry exhausted message got suspended and then when i resumed the transactions ..i did get xml in return but again i see message got suspended along with NACK message..

    And in some of the cases suppose if GLCODE is blocked from SAP port i get exception and it went under retry on SAP port.

    So i want to avoid this so that admin can be intimated or else when i resume the messages it should be processed.

    -- Kind Regards Sandeep
    Tuesday, January 10, 2012 11:36 AM
  • When you resubmit you get a NACK. You need to find why this is happening at SAP end.

    in case of getting an exception were glcode is blocked you cna have retry as 0 and send and notification back to orchestration and hve your further proecc defined there.


    Tuesday, January 10, 2012 11:42 AM
  • Hi All,

    When i set retry on Send port(Send-receive port)  the orchestration retires for set retry count and then i see error in event viewer as mentioned below:

    Uncaught exception (see the 'inner exception' below) has suspended an instance of service 'BizTalk_Project_DCS_DOMESTIC.Orchestration_C_VEH_SRN(054dfc2f-ef48-cd36-1e82-7f345c6da0fe)'.

    The service instance will remain suspended until administratively resumed or terminated.

    If resumed the instance will continue from its last persisted state and may re-throw the same unexpected exception.

    InstanceId: 5cffb45b-120a-4e9b-bde8-12a93811f40a

    Shape name:


    Exception thrown from: segment -1, progress -1

    Inner exception: An error occurred while processing the message, refer to the details section for more information

    Message ID: {FA8D3FBD-3247-4578-8653-8C47400C5E99}

    Instance ID: {9CBD5963-6FCF-4220-87ED-235004DC140F}

    Error Description: User account not in validity date


    But in Admin view of BizTalk i see these messages as when i resume the orchestrattions i get messages back from SAP but along with actual message i get NACK message also.

    Pls advise why NACK is also coming with actual message.

    -- Kind Regards Sandeep
    Friday, January 13, 2012 4:27 AM
  • Whats the error description the NACK received ?
    Friday, January 13, 2012 6:57 AM
  • not remember exactly but it is same as mentioned above


    Error Description: User account not in validity date

    But i do get response from SAP along with above Xlang error.



    -- Kind Regards Sandeep
    Friday, January 13, 2012 7:21 AM
  • The error indicates issue with the user you are using to connect to SAP.

    Even for the other suspended messages you would have received similar NACK's


    Friday, January 13, 2012 11:04 AM
  • Yes i do received same erro for other messages also.

    Pls advise if i see message suspended with Xlang Error , how can i resume messages successfully.

    -- Kind Regards Sandeep
    Saturday, January 14, 2012 4:27 PM

    This looks like an issue with the credentials you are using to connect to SAP.

    Check with your SAP team for the validity of credentials used.



    Friday, January 20, 2012 8:52 AM
  • Hi Sandeep,

    Why you are not going for "Failed Message Routing"?. Enable the "Failed Message Routing" at the send port. And create a SMTP send port subscribed to the failed message to notify the admin people.

    Take a look at these links:



    Abhijit Mahato - Microsoft Community Contributor 2011 - MCTS BizTalk Server blog: Please "Mark as Answer" if Post has Answered the Question
    Monday, January 23, 2012 6:39 AM
  • Hi Abhijit,

    Thanks for your advise..

    Will i able to send original message also when sending mail to admin with reason.

    That beacuse of certian reason message cannot be able to deliver to SAP.

    -- Kind Regards Sandeep
    Monday, January 23, 2012 5:25 PM
  • Hi Sandeep,

    Yes!! You can send the original message as an attachment with the mail. So i think failed message routing wud be suitable in your case.

    Another alternative is there, you can use the Exception management capability of ESB Toolkit 2.0/2.1. With this you can play around with the original message and fault message as well. Apart from that you will also get some tools to repair and resubmit of the message.

    Take a look at this link:



    Abhijit Mahato - Microsoft Community Contributor 2011 - MCTS BizTalk Server blog: Please "Mark as Answer" if Post has Answered the Question
    Tuesday, January 24, 2012 6:24 AM
  • Hi Abhijit,

    Thanks for your reply..

    Pls advise if suppose i set retry on send-receive port and as number of message processed are high about 500 to 800 daily, so with time number of messages retrying on port will get increase.

    Can i able to get any notification when retry gets exhausted so that i can check and reinitiate the transactions when message gets suspended after retry attempts.


    -- Kind Regards Sandeep
    Tuesday, January 31, 2012 5:07 PM