cancel
Showing results for 
Search instead for 
Did you mean: 

RABAX_STATE Dynpro not found

Former Member
0 Kudos

Hello there

I've a problem with my ITS. After modify my ITS Programm and my Dynpro programms it doesn't work.

I've the problem, when I call the transaction from the web, which i've modified, than it works. But when I will forward to an other page from the same programm (other transaction), the site could'nt be viewed.

The error is "Dynpro doesn't found" . The error was in the applikationsserver XY and in the workprozess 0 .

The abbort is "RABAX_STATE".

The abap was SYSTEM-EXIT of program SAPMZP00.

I hope you can help me.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

Try to republish your ITS service, using SIAC_PUBLISH_ALL_INTERNAL transaction.

Hope this helps,

Iván.

Former Member
0 Kudos

Hi Ivan

Thanks for your answer. Unfortunatly it doesn't help. I run the transaction SIAC_PUBLISH_ALL_INTERNAL, everthing were OK" published, but my problem isn't solved. It's the same error, which cames.

Hope you have other solutions.

Thanks

Answers (1)

Answers (1)

Former Member
0 Kudos

Here I've more information about the error, I've here the runtime Error (ST22):

*******************************

"DYNPRO_NOT_FOUND" " "

"SAPMZP00" or " "

"SYSTEM-EXIT"

Internal notes

The termination was triggered in function "dyrdyp.c"

of the SAP kernel, in line 545 of the module

"//bas/700_REL/src/krn/dynp/dybas.c#8".

The internal operation just processed is "----".

Internal mode was started at 20100906092718.

A dynpro with number 0000 does not exist.

Dynpro name.............. "SAPMZP00"

Dynpro number............ 0000

Error text .............. "Cannot read dynpro source."

*******************************

The error is always, Dynpro 000 can't be found. But in my programm (SAPMZP00) I don't have the dynpro 000.

Former Member
0 Kudos

Hello there

I found the problem. While I modified my dynpro I make a mistake. I renamed the dynpro pbo-status from status_0100 to Dstatus_0100. So the problem was, the Pbo status_0100 couldn't find, because of the new name.

I'm sorry it was my false.