cancel
Showing results for 
Search instead for 
Did you mean: 

Activation of change log in OB52

Former Member
0 Kudos

Hi Experts,

Currently change log is not activated for t-code OB52in our client to see the changes made to open and close posting periods.

Please help me to know how to activate, for us to see what changes were made and by whom. 

Regards,

vivek

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos
Former Member
0 Kudos

Can i set the rec/client parameter for one or 2 tables.

Regards,

vivek

Former Member
0 Kudos

rec/client is the parameter .. you need to set for the client ( Production client)..

table logging you can check it from below,

http://help.sap.com/saphelp_470/helpdata/pt/7e/c81ebb52c511d182c50000e829fbfe/content.htm

JPReyes
Active Contributor
0 Kudos

The paremeter rec/client only enables and disables table recording.

In order to start recording changes you need to enable the feature in SE11.

Read,

http://help.sap.com/saphelp_nw04/helpdata/en/7e/c81ebb52c511d182c50000e829fbfe/content.htm

Regards, Juan

Former Member
0 Kudos

thanks for the ans.

i want to enable this  only 2-3 tables in a client not to all.

if i set rec/client=<client no> its enable to all tables. which cause performance issue.

Former Member
0 Kudos

Hi Vivek,

Once you activated the parameter. For those 2/3 tables you can do it from SE11.. as per the above help guide.

Thanks,

Jagadish.

Former Member
0 Kudos

i checked in DD09L table i see 28,664 table Logging is enable.

so how to mass Logging off all theses tables.

Former Member
0 Kudos

Hi Vivek,

The below discussion can help you out,

http://scn.sap.com/thread/1333255

THanks,

Jagadish.

Former Member
0 Kudos

Hi

SAP delivers lot of packages with table logging active in technical settings (SE13). So once you activate rec/client for all such tables logging gets activated.But this is just one aspect of change logs. Not everything is stored in DBTABLOGS (which need rec/client). A lot of change logs get stored in CDHDR and CDPOS. That works even without rec/client if I remember correctly. But of course tables for which logging gets stored in either set of tables is different.

Now coming to OB52 (which if I recall correctly is T001B) if table logging is active (which I feel probably is)rec/client will record changes but will do so for all such tables. Having said it is not a massive performance issue just that DBTABLOGS keeps on expanding but for production systems it shouldn't be an issue honestly.

Regards.

Ruchit.

Answers (0)