Skip to Content
Technical Articles

How To Disable Table Logging For Several Objects

How To Disable Table Logging For Several Objects

This blog provides detailed explanation on disabling of table logging for all tables in Sap system with standard procedure as below.

This procedure is applicable as of SAP_BASIS 740 and following releases for SAP Products based on NetWeaver and S4Hana .

If we decide to deactivate logging of all tables, it takes too much effort to handle the task manually.

First need to implement note 2341818, so that the reports ZSLA_CREATE_DATAFILE_LOGGING_1, ZSLA_SE13_06_AS_OF_740 are in place.

After implementation of above note, need to proceed with below procedure.

1.Run report ZSLA_CREATE_DATAFILE_LOGGING_1 in transaction SE38


If you want to process all rows at once, do not change the default value 60.000.
In case you want to split the processing into several parts, enter PACKSIZE 10.000 or 5.000 for example.

Reducing the PACKSIZE can be necessary, if time frame for batch input processing is too small. Batch Input Processing of all rows at once, takes about 3 hours.

F8-execute

2. Run report ZSLA_SE13_06_AS_OF_740 in transaction SE38

  • Tick radio-button Generate Session
  • Enter any session name in field Session name, here for example I gave as name- Disable Log

  • Enter TABLES_WITH_PROTOKOL_x in field DATASET (x represents the sequential number of the file: 1,2,n)
    Execute the report with icon Execute
    If the list of transactions is displayed proceed with next step.

F8-execute

3. Start transaction SM35
Select the session with the Session name you entered above.
Press button Process
In screen Process Session choose radio-button Background in frame Processing Mode
Press button Process
Now you can monitor the process in transaction SM37.

Once the job has status Finished, this task is done.

Repeat step 1 and 2 one after the other for all files TABLES_WITH_PROTOKOL_1, TABLES_WITH_PROTOKOL_2, TABLES_WITH_PROTOKOL_n,

Select session and Click process

Click Process button and you can monitor the process in transaction SM37

Now go back to tcode – SM35 and check the session log

From above screenshot, it shows 11,562 table entries disabled, 146 entries need to be updated either manually or by repeating above procedure of step 1 and 2 .

If we want to perform changes manually , follow below procedure

  • Start transaction SE13
  • Enter the object within field Table/view name
  • Press button Change
  • Confirm the information Make repairs in foreign namespaces only if they are urgent
    Untag flag Log data changes
  • Press icon Activate

In order to find the list of these 146 tables, go to SE38 and give program name – RSTBHIST and click List Of Logged Tables button as shown below.

Troubleshoot:

While changing the table manually ,sometimes you may face issues like it gives a popup -Objects are locked in particular transport , in that case need to release the transport and again try to change it manually it works.

Note: Always make sure for the table T000, table logging should not be disabled.

(T000 is fundamental table and maintain SAP system clients in SAP system, so it should always be protected in productive system)

For reference:

2341818 – Disable Logging for several objects as of SAP_BASIS 740 and following releases

 

Thanks.

2 Comments
You must be Logged on to comment or reply to a post.
  • Hi Sumit,

     

    what are the benefits of deactivating logging, in which scenario we find that there is need of deactivation logging for all tables?

     

     

    Thanks & Regards,

    Murtaza

    • Hi ,

      System generates a log entry in the log table DBTABLOG for every change to logged tables, performance bottlenecks and memory problems may occur when you log tables that are subject to mass changes.

      First, test the effects of changing the below parameters and of changes to the number of logged tables in the quality system.,It will start recording table changes (into table DBTABLOG).

      rec/client =Activate/Deactivate table auditing

      rsau/enable=Enable Security Audit

      auth/object_disabling_active=Value ‘N’ prohibits disabling of authorization objects

      In order to meet the requirements for audit safety, all configuration tables for which this appears required by law and for which no other change logging takes place are delivered with activated logging.SAP standard tables for master data and transaction data are delivered without a logging indicator. Many of these tables are subject to mass changes that would result in performance problems if logging were to take place.

       

      Regards,

      Sumit