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: 

Error occur while trying to save a program in SE38

biswajit_das6
Participant
0 Kudos

Hi,

I'm facing a problem while trying to save a program in se38.

It is directly taking me to debug mode.

By ST22 this "ROLLBACK_IN_POSTING" error is recognized.

And from SM21I got following details :

Time Type Nr Clt User Code Priority Grp N Text

10:25:13 DIA 001 010 BISWAJIT R6 8 Perform rollback

10:25:13 DIA 001 010 BISWAJIT R6 8 Perform rollback

10:25:14 DIA 001 010 BISWAJIT AB 0 Run-time error

ROLLBACK_IN_POSTING" occurred

and from SM13 the following details I have found.

Function Module RS_NEW_PROGRAM_INDEX

Status Update was terminated

Report LSEUAXU01

Error details Class: 00 Number: 671

00 671: ABAP/4 processor: ROLLBACK_IN_POSTING

If any one kindly help me to solve this problem it will be very very

helpful for me.

Thanks in Advance.

with regards,

Biswajit Das

6 REPLIES 6

Former Member
0 Kudos

Hi

Check whethere there may be OSS note implemented which is impacting the t code

check the version of include LSEUAXU01

Regards

Shiva

venkat_o
Active Contributor
0 Kudos

Hi, Are you getting the problem for only one report or others as well ? Regards, Venkat.O

0 Kudos

Thanks again for your reply.

Yest it is occurring only for SE38.

Thanks & Regards,

Biswajit Das

matt
Active Contributor
0 Kudos

What Venkat means by

Are you getting the problem for only one report or others as well ?

is, does this happen with just one program you save in SE38, or does it happen for all programs you save in SE38?

Now, SE38 is a standard SAP tx. So, if there is a problem with it - go to OSS first.

matt

0 Kudos

Ohh sorry..

it is occurring for all the reports. still I'm trying to solve it but not finding any clue.

Even I'm trying to do the same from SE80. but it is in vain.

Thanks ,

Biswajit Das

matt
Active Contributor
0 Kudos

You must contact SAP about this problem, through OSS.

m@t