Error: Screen output without connection to user in Android device/WPF client

[former_member286937]

Hello Experts,

Below is the screenshot of the error Screen output without connection to user which we are getting while delta synchronization in Android device/WPF Client. However this issue only occurs when we add components to a work order and then transmits in Agentry Work Manager 6.2 application.

Following are the details:

Application:               Agentry Work manager 6.2 (Standard solution with minor screen set customization)

Platform:                   SAP Mobile Platform 3.0

Device/Virtual Device: Android/WPF Client

Steps to reproduce an issue:

1. Creating Work Order and successful synchronization

2. Getting work order id at the device end.

3. Adding component to the work order

4. Transmitting after adding component and getting error  Screen output without connection to user

Please assist regarding this issue.

Thanks,

Abhilasha Gupta

[sravanthi_polu]

Hi Abhilasha,

Please let us know the customization's in front end.Does there is any custom code in java.

Have you verified the required roles/authorizations are in place for the user performing sync.

Let us know if there are any errors in slg1, event logs,server logs.

Thanks & Regards,

Sravanthi Polu

[bill_froelich]

You will need to work with you SAP team to address this.  It appears you have a customization in your backend that is attempting to output to the screen.  There was probably an assumption made that the user is always coming in through SAP GUI. Chances are you will need to have the BASIS team review the modifications and make a change to support the Work Manager transactions.

--Bill

[former_member286937]

Hi Bill,

We have not done any customization at the back end. It is a standard 'out of box, solution of Agentry Work Manager 6.2 application.

Thanks & regards,

Abhilasha

[stephen_kringas]

Hi Abhilasha,

Your Work Manager maybe "standard" but there will be a UserExit in the Work Order trying to display a dypnro screen.

In your ABAP system, go to TCode ST22 and you'll see the dump. You'll be able to see the call stack and find out which user exit is throwing the error.

We have experienced the same issue where an existing Work Order User Exit (built before Work Manager was implemented) was trying to display a GUI screen. Since Work Manager is updating Work Orders via an RFC, if an exit tries to display a dynpro screen you'll get the dump "Screen output without connection to user"

More information can be found here -

http://help.sap.com/abapdocu_70/en/ABENRFC_SYS_FAIL.htm

Cheers,

Stephen

[Former Member]

Hello Everybody,

Hope you 're doing a brilliant job...!!

Just want to share few information on this incident. I am working with Abhilasha on this issue.

When user add the components to work order and then transmit in Agentry this issue comes and in the backend system, a dump get generated. I refer the blog http://help.sap.com/abapdocu_70/en/ABENRFC_SYS_FAIL.htm and come to know that we need to run the calling program in a background process and user type should be dialog. The user type is dialog and having profile SAP_ALL access.

In the backend system dump file, the error points to - " Attempt made to send an image to a user during background processing." Also the RFC call type used is synchronous.

As per sapnote 49730, its mentioned to use asynchronous RFC instead of synchronous RFC when executing the function module that leads to the screen output.

I 'd like to know how could we find whether the asynchronous or synchronous rfc is being used in our scenario. Also want to know how could we execute the process in dialog processing mode. Please give your suggestion on this.

Attached is the backend system dump trace file for the reference. Appreciate your support.
 

Regards,

Arjun

ST22 dump trace file.txt.zip

[stephen_kringas]

Hi Arjun,

Your issue is caused by  custom exit (Include - ZPM_WORKORDER_INFO3) trying to display a popup with the function module -  REUSE_ALV_POPUP_TO_SELECT.

Since the Work Order Create RFC (/SMERP/PM_DOWORKORDER_CRT) can't output dynpro screens it causes the dump.

You'll need to update you're enhancement cater for being called via RFC so it doesn't try to display a popup.

Stephen