Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

DYNPRO_WRITE_FAILED abap dump exists when generating objects in tcode SGEN

Former Member
0 Likes
935

Hello Colleagues,

Good day to you all!

I am experiencing many abap dumps in st22. these are DYNPRO_WRITE_FAILED when generating objectes in tcode SGEN. I have successfully installed an ST-A/PI release 01Q_700 and i am now generating objects via SGEN. Can you kindly help what are these dumps? Looking forward to hear from you. Thank you!!!!  (i have also attached the text file of the dump)

Runtime Errors         DYNPRO_WRITE_FAILED

Date and Time          06.09.2013 21:49:23

What happened?

    Error in the SAP kernel.

    The current ABAP "ROIB1M02" program had to be terminated because th

    ABAP processor detected an internal system error.

What can you do?

    Note which actions and input led to the error.

    For further help in handling the problem, contact your SAP administ

    .

    You can use the ABAP dump analysis transaction ST22 to view and man

    termination messages, in particular for long term reference.

Error analysis

    The database interface reports an error at write access:

    Error no. 1 was reported.

    1:   SQL error

    2:   Invalid value in call

    3:   Screen number in the header (field DNUM) and in the ID are

         different

What happened?

     Error in the SAP kernel.

     The current ABAP "ROIB1M02" program had to be terminated because the

     ABAP processor detected an internal system error.

What can you do?

     Note which actions and input led to the error.

     For further help in handling the problem, contact your SAP administrator

     .

     You can use the ABAP dump analysis transaction ST22 to view and manage

     termination messages, in particular for long term reference

Error analysis

     The database interface reports an error at write access:

     Error no. 1 was reported.

     1:   SQL error

     2:   Invalid value in call

     3:   Screen number in the header (field DNUM) and in the ID are

          different

4 REPLIES 4
Read only

anilkumar_kalkivai
Active Participant
0 Likes
643

Hi,

Try steps in How to correct the error:

  Report the error to SAP if it is an SAP screen.                                              

    Otherwise:                                                                                   

    Check whether the screen header contains valid values for the screen                         

    version at EXPORT DYNPRO.                                                                    

    You have to retrieve a screen from the database with exactly the version                     

      as you saved it. This is guaranteed as long as the screen header D020S                     

    was not changed.     

As it is mentioned, if it is a screen related issue you have to raise an OSS to SAP.

Regards,

Anil.

Read only

0 Likes
643

HI Anila,

Thanks. But would you know if there is a consequence when I ran the install of ST-A/PI via foreground and NOT in background? but according to the logs, my install was successful for st-a/pi.

Thanks in advanced!

Regards,

Meinard

Read only

Former Member
0 Likes
643

Hi,

DYNPRO_WRITE_FAILED may be a lock issue from parallel processing.

Please retry SGEN.

Regards,

Klaus

Read only

0 Likes
643

Hello Klaus,

I have already retried SGEN and generated the remaining objects using the option "regenerate  the objects  of the last run". But i noticed that every time I regenereate objects from SGEN, I am experiencing the dumps in ST22. Should I now pick "GEnereate all objects of selected software components"? (note that the generation is now 100% complete)    

Alos, Previously, in ST-A/PI upgrade, I chose the upgrade to be done in FOREGROUND in saint. Would that have an effect in sgen? Thanking you in advanced.

Regards,

Meinard