cancel
Showing results for 
Search instead for 
Did you mean: 

Screen output without connection to user.

former_member761924
Participant
0 Kudos

Hi Experts,

I'm getting below error from and it seems to have triggered from FORM_PRINT_AFTER_POSTING. Here's the details of dump from ST22.

Can someone please help figure out this error, searched forums and SAP notes nothing useful found.

Any help is appreciated

FredericGirod
Active Contributor
0 Kudos

What are you doing when the dump occurs ?

former_member761924
Participant
0 Kudos

Hello Frederic,

A call is made to POSTING_INTERFACE_CLEARING FM to post and clear documents, post that FORM_PRINT_AFTER_POSTING is being called to print the posted payment document. This is when the error occurs, it's used for a customized Adobe form and below is the error.

Accepted Solutions (0)

Answers (3)

Answers (3)

FredericGirod
Active Contributor

Already asked, and the answer was to read this note :

49730 - Error message: Screen output without connection to user

Sandra_Rossi
Active Contributor
0 Kudos

Based on your short dump, impossible to say what is the culprit except that it happens when a conversion exit is called implicitly (SAPCNVE, CONVERSION_EXIT, e.g. called write WRITE or whatever).

We see that it happens within context of Web Dynpro for ABAP.

As you say that you call POSTING_INTERFACE_CLEARING, FORM_PRINT_AFTER_POSTING..., maybe you call it incorrectly.

Either try to do a SAT during the execution to see when it happens, or try to analyze without Web Dynpro context (create a classic Execution Program) to see whether you get a better short dump or log...

0 Kudos

Check if there is a WRITE or similar list processing statement in the form.

former_member761924
Participant
0 Kudos

There's no list processing statements as such, the termination is happening inside the standard FM FORM_PRINT_AFTER_POSTING that's being called in the custom code.

0 Kudos

I see there's a "CALL SCREEN" statement on line 472 - can you put a breakpoint there and see if it is calling that line?
If not, can you attach or link to the raw analysis (st22 > runtime errors> unformatted display)

former_member761924
Participant
0 Kudos

Steffen, the breakpoint wasn't triggered at CALL SCREEN, attaching the ST22 unformatted display log.

Sandra_Rossi
Active Contributor
0 Kudos
liki999

Better attach the formatted short dump, not the unformatted one!

former_member761924
Participant
0 Kudos

Attaching the formatted dump as well

formatted-dump.txt