Skip to Content
0

Work Manager Application crashes on cancelling transcation

Feb 03, 2017 at 10:01 AM

100

avatar image

Hi,

I am using the below product versions:

SMP 3.0 SP09 , SDK SP 12 android client 70.12.3.40, Work Manager 8.0

I have an add transaction that contains an external data property. When I cancel the transaction by clicking on cancel shown on the transaction screen or back button on the android device, the app crashes every time. Surprisingly, when I remove the external data property from that transaction application workis fine without crashing.

Please suggest any work around for this.

Regards.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

5 Answers

Mark Pe
Feb 03, 2017 at 03:20 PM
0

Shankar,

Hi. We can have some theories on why it may be crashing. Let us take your comment above of "When I cancel the transaction by clicking on cancel shown on the transaction screen or back button on the android, device, the app crashes every time".

Now from what we know internally in SAP, "A detail screen contains a field to display an External Data Property (EDP). From that screen, an edit transaction is launched. The transaction is applied, and the EDP changes. When the detail screen wizard closes, the original detail screen is displayed."

Now let us have a theory that when you click on the cancel shown or the back button and we merged this on what we stated above that the field needs to "DISPLAY" a value upon applying the transaction by clicking the back button or cancel forces no value in it and thus creating the crash.

So some value or data should be present before you click Cancel or Back due to the Apply transaction step.

This may be theoretical but this is what we can share for now.

Hope this helps.

Mark Pe
SAP Product Support

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Hi Mark,

I went through your suggestion post which I tried removing the apply step from the action containing the discussed transaction. However, still cancelling the transaction leads to application crash.

Additionally, the screen from which the transaction is launched doesn't contain any external data property but a list of string proprties. So, the assumptions made by you doesn't hold true in my case. Please comment.

Regards,

Shankar

0
Mark Pe
Feb 06, 2017 at 08:36 PM
0

Shankar,

Thanks for sharing and for doing some additional check. With your last statement above, then the apply is not the culprit. That theory was based on other older incidents in SAP.

Here is another idea: From older issues that was reported before in product support, crashing with external data property may be tied to the pop up that gets shown by the OS of the device when the user has an opportunity to use the external data property. If your external data property is tied to attach documents or some special coding or some other items, pay attention to what the Android device is doing during that time frame. What I mean is sometimes, calling an external property may require you to add a user input or to click on something on the device or something else. When this is done sometimes the OS of the Android may show you a popup for entering data (like a keyboard) and so forth. What if your situation was tied to a pop-up (i.e Android popup for user entry)? So my guess is that if this pop up is shown, is for your user to click on the minimize function of the Android OS instead of using the Agentry client arrow button to be used right away.

So here is the theory:

  1. You have a transaction with an external data property.
  2. You are force by the Android OS to enter data (picture, or string keys - keyboard or others).
  3. You clicked on the Agentry device icons (Cancel or Back) to continue then crash.
  4. What if instead of clicking the Agentry device icons to continue, you minimize the Android OS keyboard or external data input first before clicking on the Agentry client icon buttons (Cancel or Back).

This is my next theory of the issue. But again thanks for checking if the first theory works or not.

Please provide the version of your Android OS and Model of the device so we may know if it is the newest or an older version.

Best Regards,

Mark Pe
SAP Platinum Support Engineer

Share
10 |10000 characters needed characters left characters exceeded
Shankar Kandaswamy Feb 07, 2017 at 01:28 PM
0

Hi Mark,

I went through your comments. As per your suggestion, I closed all the active input windows(file explorer in my case) and clicked on cancel/back. However, it didn't help. The app still crashes.

Regards,

Shankar

Share
10 |10000 characters needed characters left characters exceeded
Bill Froelich
Feb 07, 2017 at 02:57 PM
0

Please be sure to check the latest client available. As of right now SMP3 SDK SP14 is the current Android client (70.14.0).

Also it is helpful if you include details about the device and OS version it is running as well.

--Bill

Share
10 |10000 characters needed characters left characters exceeded
Shankar Kandaswamy Feb 08, 2017 at 07:59 AM
0

Device: Samsung Galaxy S5

OS Version: Android 6.0.1

Are you saying that the crash will not happen with the latest client available.

-- Shankar

Show 1 Share
10 |10000 characters needed characters left characters exceeded

I don't know one way or the other if it will happen with the latest client. I do know that if a fix is needed it will be made to the current version and not the older version you are currently running so the best first step is to test with the latest client and see if the behavior is the same. If it still crashes and you have consistent reproduction steps, I would log a ticket with support so it can be investigated further.

--Bill

0