Skip to Content
avatar image
Former Member

Agentry Error Handling - Occurs in all transaction issue

Hi All,

Im facing an issue with error handling in Agentry. Though i have error handling steps in only some of the transactions, the error handling pop up is coming up for other transactions that has no error handling step added to it. This would allow the users to click "Continue" and skip that transaction which is causing an issue.

We are using the latest SMP server. Do we have any specfic configuration to restrict the error handling to come up only on the transactions that has error handling steps?

Please help as this is affecting many scenarios

Thanks in advance

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • avatar image
    Former Member
    Mar 03, 2017 at 03:57 PM

    Thanks all for the replies..

    I have figured a way to do skip the error handling pop up.

    Whenever there is an exception captured in the update step, in the respective java steplet i have added

    this._useNewErrorHandlingMethod = false;

    before the "throwExceptionToClient" method.. This would ensure that the error handling pop up is not triggered and just stops the sync in the transmit screen. So user is forced to discard the object or clear user data to avoid that pending transaction

    Since "_useNewErrorHandlingMethod" static variable, if you need the error pop up for certain transactions then set

    this._useNewErrorHandlingMethod = true;

    along with Error handling step in the agentry to throw the pop up with user having the option to abort or continue.

    -Karthik

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Mar 03, 2017 at 09:33 AM

    Hi

    I did not use error handling step for transaction but i would like to ask about 'apply step' after transaction. Do you use one apply step for those two transaction as you mentined?

    Add comment
    10|10000 characters needed characters exceeded

  • Mar 03, 2017 at 03:15 PM

    Karthik,

    Can you provide more information about how you setup your Error handling? There are two or three different techniques (General) that one can use and we wanted to know if you are using strictly the following:

    a) Agentry.ini - Error handling setup.

    b) Java based Error handling + Editor Transaction Error handling steps.

    c) Work Manager Inbound Queue Management.

    I am guessing b but just in case you are using a, that may be the issue as it applies to all and you need to focus on b.

    If you are using B. please provide a snapshot of your Error handling step in the editor so we can in SAP can review.

    Best Regards,

    Mark Pe

    SAP Product Support

    Add comment
    10|10000 characters needed characters exceeded

    • To Karthik and all,

      As a follow up to this and based on the internal review of the code with the development team + the statement of the workaround above, the decision made by the SAP development team is not to further optimize or enhanced the older feature Fatal with message error type. With this stated, the documented workaround by Karthik will be the official workaround by SAP and any of the SAP user/customers regarding this issue. So kudos to you Karthik, for getting the workaround that we may have to follow. Expect users from different areas to reach out to you for your expertise.

      Best Regards,

      Mark Pe
      SAP Platinum Support Engineer