Tracking Table value changes

Former Member — Tue, 28 Jul 2009 06:36:53 GMT

Hi all,

currently we are in the process of tracking the data changes in the following table

/sapsll/adrcon (GTS specific) but it has been checked for the log data changes in its technical settings

but still we are unable to track the changes in

cdpos table

please provide your valuable inputs

so that we can track the changes

cheers

balu

Re: Tracking Table value changes

Former Member — Tue, 28 Jul 2009 09:24:41 GMT

Hi,

The place where we find Transaction Table history is SCU3.

===================================================================================================

The logging flag defines whether changes to the data records of a table should be logged. If logging is activated, every change (with UPDATE, DELETE) to an existing data record by a user or an application program is recorded in a log table in the database.

Note: Activating logging slows down accesses that change the table. First of all, a record must be written in the log table for each change. Secondly, many users access this log table in parallel. This could cause lock situations even though the users are working with different application tables.

Dependencies

Logging only takes place if parameter rec/client in the system profile is set correctly. Setting the flag on its own does not cause the table changes to be logged.

The existing logs can be displayed with Transaction Table history (SCU3).

Regards,

Bhargava

topic Tracking Table value changes in Application Development and Automation Discussions

Tracking Table value changes

Re: Tracking Table value changes