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: 

update was terminated vl02n transacton

Former Member
0 Kudos

Hi All

i was running vl02n for specific output type.I am getting error update was terminated.I have check in sm13 and shows like

For output delivery 8000003526 is working fine,but with 8000003558 is not working.

Please help on this.

Thanks

Vamsi

19 REPLIES 19

FredericGirod
Active Contributor
0 Kudos

Hi,

try to change the output : instead of print after save, put print with external transaction.

after this, go in VL71 and ask for print your transaction. You will have a dump, and you will be able to activate debug to see where you are, and what appends exactly.

in VL02n --> print in background, so update process error --> SM13

in VL71 --> print in foreground, so just error .. you could debug (more easily)

regards

Fred

Former Member
0 Kudos

Hi,

Probably System is trying to print Some Script/layout . Check whether any layout is attached for this delivery and see how the printing is handled (i.e. via custom code, routine, etc.. ) . From the error message it seems that the FM END_FORM is called before OPEN_FORM.

Regards

Arulmani

Former Member
0 Kudos

Hi

I have tried to add same output type for delivery 8000003526 second time,now it is throwing update error

Thanks

Vamsi

0 Kudos

what is the error?

0 Kudos

update was terminated

0 Kudos

The actual error you can find with SM13, update terminated is a generic message. Look with SM13 for the FM(s) in error and actual error message/dumps.

Also check your Cutomizing for Output Determination for Outbound Deliveries.

Regards,

Raymond

0 Kudos

Hi Raymond,

I have given an error screenshot in posting question.

Thanks

Vamsi

0 Kudos

So are you saying the same error you are getting again which is attached in your screen shot in that case it looks to be a script error which is attached to the output type.

0 Kudos

Hello Mohan,

The problem may be with the language of the message output.

Check in which message type is being triggered and check if the sap script is created in

the same language.

To avoid update terminations, change the processing mode of message type to periodic schedule job

by using vv31 tcode.

Thanks

0 Kudos

So your Customizing seems to contain a wrong/undefined/not translated message/form/driver program, check Customizing thru NACE.

Regards,

Raymond

Former Member
0 Kudos

Hi Vamsi

You can the check the script name and print program name using the table TNAPR based on the output type. .

Regards

Anbu

Lakshmipathi
Active Contributor
0 Kudos

Check the following note

  • Note 1055717 - Update termination for EK00 at send time 4

If this is not solving your issue, then share the Error analysis and "How to correct the error" from ST22

G. Lakshmipathi

Former Member
0 Kudos

Hi All

In foreground , working fine, but when i am executing it in the background i am getting an error "END_FORM is invalid, OPEN_FORM is missing".


Thanks

Vamsi

0 Kudos

Check if the printer setup is LOCL for you in the output options as you are executing the job in background...

Regards

0 Kudos

Hi,

If LOCL printer option is not available check with printer option as secured-local.

BR, Manu

Former Member
0 Kudos

Hi All

I have checked in su3 and assigned lp01 and also while assigning ouput type to document number .i have assigned same printer name.Still facing the same issue.

Thanks

Vamsi

0 Kudos

Can you set a break point in the program LSTXCU01 before line 33 and check for values in structure RSTXC. It is form name and other relevant information. May be that will give you some clue.

0 Kudos

Hi Abhijit

I have checked  rstxc-tdstarted is not setting in endform,if i comment end_form,same  rstxc-tdstarted error is close form.

Thanks

Vamsi

0 Kudos

There are other fields as well in RSTXC like TDFORM which is form name...

other option is can you debug sapscript and find out which part is throwing an error?