monitor direct table changes

[Former Member]

hi,

it is possible to change table entries via se11 > debug

is there a way to monitor the changes made?

SE16N_CD_KEY, SE16N_CD_DATA  is not available in 4.6C

REgards,

[Former Member]

Hi,

I'm curious, are you trying to find out who has changed entries on a table or are you trying to find out if you can change a table without anyone knowing?!

Also, this would probably be better posted into one of the ABAP forums, as it isn't really related to BPM or Composition.

And finally, changing table entries using the SE11 or SE16 debug trick is a serious no-no so whoever is doing it should be given a talking to about how not to meddle with an SAP system...

Gareth.

[former_member181931]

Thanks Gareth. Moved to ABAP Development space. @Ramesh let me know if another ABAP space is more appropriate.

Laure

[Former Member]

hi gareth, thanks,

i am wanting to find out who has changed the entries in the table...

i know it is possible to change entries using the debug method and i want to know if there is a way to trace if people are doing it... i was hoping sap should have something like non-repudiation..

[Former Member]

You can take away the rights of the users to modify the values in debugging. I dont think you can do anything to do stop them from doing this unless you maintain roles for the users.

[Clemenss]

if table is not flagged for log data changes in DDIC, you can do what you want. If you use SE16N with &SAP_EDIT, changing user, date/time ad result of the change (not previous state!) is recorded. But this can be deleted 🙂

Regards,

Clemens

[former_member213851]

Hi Ramesh,

In order to monitor the changes made  to the  Table entries in debug mode, you may add piece of code in the existing functionality such that while saving the New value, a mail will be triggered to the desired email id with new value of the field as well as Old value.  

Regards

Sachin.

[yogendra_bhaskar]

Hi Ramesh,

What u want can be implemented in many ways :

1 > storing the changes in z table

2 > restrict authorization for debugger

3 > recording or restricting the value change of "code" variable in include LSETBF01 , form set_status_val.

But the main problem is your monitoring can also be altered...

[raymond_giuseppi]

- Debug actions like changing values of variables are stored in system log (SM21) but this log is often periodically cleared and not easy to use for tracking.

- If table is lagged for log data in SE11, Basis should also set profile parameter rec/client to adequate value. (off, all, list of clients)

Regards,

Raymond