Skip to Content

With NetWeaver Process Orchestration 7.31 SP10 and 7.40 SP5, we are now able to detect and handle technical errors.  Some examples of technical errors are invalid password, unauthorized access, network failures, etc.  The technical errors include those occur in PI.  This capability has been missing in previous releases of BPM.

Why do we want this?  During the runtime of an integration scenario, when we receive a technical error, the integration will terminate with an error message, which we can view in the monitor.  We can also be alerted of the error.  But, what if we want to automate the process so that we can react to the error?  Maybe we want to update a status database or send the message to an alternate receiver or “rollback” a previously updated application/system.

This capability is also needed when we convert ccBPM to BPM, as ccBPM can detect such error event.

To configure this in BPM is quite easy.  I am assuming that the reader is already familiar with BPM.  The steps are as follow:

  1. Create or using an existing “Automated Activity”.

/wp-content/uploads/2014/02/pic1_392190.png

   2.  Select the “Automated Activity” and click on the “Property” tab.

   3.  In the “Property” tab, select “Boundary Events”:

/wp-content/uploads/2014/02/pic2_392191.png

   4.  Click “Add…”. This will bring up the events that can be selected.  Go ahead and select “Technical Error” and click “OK”:

/wp-content/uploads/2014/02/pic3_392195.png

  5.   A new object on the upper left corner will be create in the “Automated Activity”:

/wp-content/uploads/2014/02/pic4_392204.png

  6.   When you hover the mouse over this object, you will be able to select the action you want to perform when technical error occurs:

/wp-content/uploads/2014/02/pic5_392206.png

Below is a sample BPM which uses this feature:

/wp-content/uploads/2014/02/pic6_392207.png

To report this post you need to login first.

18 Comments

You must be Logged on to comment or reply to a post.

  1. Suseelan Hari

    Hi William,

    Good Day!

    Very nice explanation about configuring BPM. Updating SAP PO and this information is very useful. Whenever required I will refer this blog. Thank you so much for sharing this information. All the best!

    Regards,

    Hari Suseelan

    (0) 
  2. Chris Mills

    Thanks Bill, good article. I was trying this out the other day and couldn’t select technical error within boundary events even though we are on the latest release of PO and NWDS. Turns out a simple re-sync of the DC’s made technical errors visible in NWDS.

    If anyone else has this issue refer to the following: http://scn.sap.com/thread/3487670

    Cheers

    Chris

    (0) 
  3. Gareth Ryan

    Good to know this feature is now available – actually hard to believe it wasn’t there from the start.  Few of my customers just couldn’t understand why their processes would fail in such a simple way!

    Cheers,

    Gareth.

    (0) 
  4. chetan mittal

    nice feature…

    I have one question, is it possible to cancel the process using java bpm api’s in SAP PO. means till now i can perform human activities and intermediate task using BPM API’s.

    thanks,

    chetan

    (0) 
  5. divyesh vasani

    As usual, nice one and always informative blog 🙂 .

    TechnicalError can catch mapping error too ?

    I was thinking if automated activity of type service reference “XI” includes mapping and can we catch mapping error and send mail with as above?

    —Divyesh    

    (0) 
  6. Thorsten Stork

    Hello,

    thank you for the blog.

    I tried to implement this in an BPM on an PO 7.40 SP7, the asynchronous message I send from the BPM to PI will stuck in status “waiting” because of an unknown host in the FTP Adapter and firewall.

    But the BPM go on the “success” way -not the “Exception way – and ends before an definitive status “sucess or error”.

    Is the Boundary Events “technical Error” working with asynchronous Interfaces? I think it should.

    Any Ideas ?

    Regards

      Thorsten

    (0) 
    1. Christian Loos

      Hi Thorsten,

      This only works for synchronous messages. In the asynchronous case, the error has to be handled within PI. BPM has successfully delivered the message to PI and hence it is considered successfull.

      Regards,

      Christian

      (0) 
      1. Thorsten Stork

        Hi Christian,

        it is planned to implement such feature, because in ccBPM there was a possibillity to react to asynchronous interfaces, if the transport ack wasmissing?

        So in the past it would be possible to build a sync –  async bridge, so we could confirm to the synchr caller that all asynchr receiver had got the message.

        Regards

          Thorsten

        (0) 
          1. Thorsten Stork

            Hi Christin,

            sorry, the word synch <-> Async may be a little bit incorrect.

            We want to to give a responce to a synchronous caller, if we are sure, alls (multiple) asynchronous receiver hat received teh message. How we  do that, without techn acks for asynchronous Services in BPM ?

            Regards

              Thorsten

            (0) 
  7. Sandeep Maurya

    HI William,

    in ccBPM, there is option “Create New Transaction” in transform or send node, where is similar option in NW BPM?

    in PI 7.1, I am using this option for reprocessing(if ccBPM is failed), this will start reprocessing from the same point where it failed.

    Thanks

    Sandeep Maurya.

    ccBPM prop.jpg

    (0) 
  8. Jayasuryaavthi Tadikonda

    Hi William,

    Thank you for nice blog.

    As  mentioned in the blog with the latest SP of BPM we can handle the time out exceptions. Could you please let me know how can we capture those in bpm through web service.

    Exceptions related to the service can be hold by fault structure in the service. But in case of time out and password expiry how can we capture them in bpm.

    Regards,

    Jaya

    (0) 

Leave a Reply