Skip to Content

Agentry Transaction Error Handling

Dear Community,

Recently we have implemented the Transaction Error Handling for some of the deployed Agentry apps.

Reference is made to the following links:

Transaction Error Handling Steps in SAP Help documentation for SDK 3.0 SP12

Agentry - Transaction Error Handling

SMP 3.0: Agentry Transaction Failure Handling


My understanding is that standard Agentry does not support error handling that elegantly, it will stop the user from continuing his/her daily work activities when an error occurs during the transmit process, expecting to resolve the error first.


Under certain circumstances this behaviour might be acceptable, however, there will be instances where the error is of such nature that it cannot be resolved instantly, for example due to changed configuration in the ERP system (which should not happen, but certainly is not an unlikely scenario).


This is where Transaction Error Handling can play a role, where the failing transaction is stored on the SMP server, and allowing the user to continue his/her work.


But now, there is a (number of) failed transaction(s) living on the SMP server, what is the follow up from there?

There are no tools - at least not that I am aware of - to monitor the failed transactions, let alone be able to reprocess these xml files at a later stage (of course with minimal user interaction).


It raises a number of questions:

1. What is SAP's recommendation here?

2. What tools has SAP made (or will make) available to allow monitoring and reprocessing (especially considering the failed transactions are stored on SMP, and they need to be (re)processed in ERP) ?

3. How do other customers deal with this, or what processes and procedures were put in place to close this gap?

4. In one of the above links I read about inbound transaction management. What exactly does this entail, and when will this be part of the Agentry framework (not just for a specific Agentry app)?


Best regards,

Edwin

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Best Answer
    May 27, 2016 at 02:20 PM

    Edwin,

    Hi. Based on your question:

    "My understanding is that standard Agentry does not support error handling that elegantly, it will stop the user from continuing his/her daily work activities when an error occurs during the transmit process, expecting to resolve the error first."

    Answer:

    • Agentry error handling can be done different ways. There are Agentry error handling steps (uses Agentry libraries) wherein the user will see a warning but allow them to continue but if configured properly an IT admin will get an email that an error occured to do the necessary. This will help the user not to get stuck during his work day.
    • This libraries are called if you use the Agentry Eclipse Editor Error Handling.
    • Another technique for Error handling if you are not using the Agentry feature of Error handling is to do all the error handling in JAVA. Both of these techniques are not trivial and may need SAP consultants experts in Agentry error handling process. Most of the out of the box SAP Work Manager and Inventory Manager may only use error exception handling in Java but they do not use the Agentry feature of Error Handling as shown in the picture below.





    • From the picture above, you can select Fatal with message (make the user know it is really an error for them not to continue) or Fatal without message or No Change or Retry with change (the user will need to modify their selection/answers) or Retry without change.
    • This is not trivial because a business unit needs to know what to do if an error occurs.
    • In SAP we only gave a few examples as this is purely configurable or customizable based on user requirements and the type of action that needs to be done is different per business flow.
    • This is an advance feature of Agentry and it will need experts in Agentry customization to do the work and we suggest you to either subcontract the work with SAP consulting or partners who worked in this space (this is the answer to most of your questions above)

    Best Regards,

    SAP Mobile Support Team


    a.png (68.3 kB)
    B.png (40.7 kB)
    Add comment
    10|10000 characters needed characters exceeded