Application Development 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: 

Updatre terminated error for transaction ME21N while saving PO

Former Member
0 Kudos

Hi All,

I am getting update was terminated error while creating and printing PO in ME21N.

System ID.... D48

Client....... 010

User..... OS1014

Transaction.. ME21N

Update key... 4A76F463D0DB0179E100800097A2993E

Generated.... 03.08.2009, 12:53:47

Completed.... 03.08.2009, 12:53:52

Error info... TD 030: Spool request 788 contains no SAPscript data

I have checked it in SM13 . The FM which is causing error is RV_MESSAGE_UPDATE. Throwing short dump at the Message line in the following code.

CALL FUNCTION 'TH_IN_UPDATE_TASK'

IMPORTING

in_update_task = lin_update_task.

IF lin_update_task = 0.

MESSAGE x002 WITH 'CSLI_DLG2UPD_BEGINWORK'.

ENDIF.

I could know where is the error. But I dont know how to solve it further.

Can anybody help me out on this.

Thanks in advance.

Rraajzni.

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Hi,

Try to debug script.

Thanks and Regards

4 REPLIES 4

Former Member
0 Kudos

Hi,

Try to debug script.

Thanks and Regards

Former Member
0 Kudos

Hi,

Try debugging using update debugging.You may get a clearer picture.

Also try saving the PO without printing because it might be a problem with sapscript data.

If its saving correctly then check sapscript and try again.

Regards,

Subhashini

former_member555112
Active Contributor
0 Kudos

Hi,

There is probably some error with your sapscript or smart form.

Go to SM13. Check the update termination.

Put a breakpoint at the statement where the dump occurs.

Start PO creation process once again and before saving go to debugging.

Turn update debugging on and system debugging on.

Then do F8.

The process will stop at your break-point. Then debug the dump.

Regards,

Ankur Parab

Former Member
0 Kudos

Solved...The problem is in printing sapscript