FD02 - dynpro does not exist [closed]

Question

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.

Closed 8 years ago.

I am running transaction FD02, and when I put a specific client number it triggers a dump (DYNPRO_NOT_FOUND, see image).

I tried to search for notes using the terms given below but I could not get any relevant info.

"DYNPRO_NOT_FOUND" " "
"SAPLSZA1" or " "
"SYSTEM-EXIT"

What needs to be done to avoid the dump? The other clients works fine, only one does not. Thanks.

Answer 1

If you say that the other clients work but one in particular does not, then the problem might be in a customizing table. I assume that the screen number is read from some kind of a configuration table and for the client you are testing on, those entries have not been provided.

Answer 2

This problem has to be investigated in your system. If you don't have the knowledge for yourself, you should report this via SAPnet. SYSTEM-EXIT suggests that it's a problem with some kind of additional programming, but from the info you give it's impossible to determine exactly what is going wrong.