Table Logging

[Former Member]

What is the best way to capture material determination changes? The DBTABLOG table is 180GB in size so another way needs to be investigated other than setting on table logging for the material determination tables.

There is no built-in SAP change record functionality in VB11-VB13 like there is in (for example) VK11-VK13, price records.

Tables: KOTD*

Thank you,

[Former Member]

hi lp,

Logging Customizing Objects

Use

The analysis of logged customizing objects allows you to answer the following questions about customizing setting changes:

· who made a change?

· what was changed?

· when was the change made?

Logs are analyzed by object, i.e. the changes can be shown in their customizing context, not just technically at table level.

Change logs can be deleted or archived. If you archive logs, you must ensure that the analysis includes the archived logs.

The analysis only applies to the logon client. If you want to see change logs for another client, you must logon in that client. Logs of cross-client objects are shown in every logon client.

Productive data changes should not be logged, for performance reasons.

Prerequisites

The analysis can only be used when:

· the Log Data Changes checkbox is set in the technical settings of the table, or the tables in the view, in the ABAP Dictionary

The Dictionary setting is predefined by SAP for the objects to be logged. You should not deactivate logging for these objects, as analysis inconsistencies can occur if customizing settings are sometimes maintained without logging.

See Activate Table Change Logging.

...

Call transaction SE13.

Enter the table name.

Choose Change.

Set the checkbox Log data changes.

Save your entries.

· the profile parameter rec/client is maintained.

The logging profile parameter should always be set in the customizing system and client. Logging in the productive system or client can impair performance.

Save your entries.

Process flow

You can start the analysis of logged customizing objects from the IMG, the customizing menu, or the view (cluster) maintenance.

Analysis from the IMG

1. Go to the IMG and choose the activity whose change history you want to see.

2. Enter the period you want to analyze, and start the analysis.

3. The changes are displayed as a list. The following information is provided for each change:

Date and time

Key field(s)

Comparison of the old and new function field values, or message that the record is new or has been deleted.

You can call detail and technical information for each entry.

Analysis from the customizing menu

You can call the analysis in the customizing menu via Tools ® IMG Logging instead of from the IMG. Enter the name of the object or table in the next screen.

Analysis from the view (cluster) maintenance

The analysis can also be called from view or view cluster maintenance via Utilities ® Change Logs.

Activate/Deactivate Table Change Logging

Prerequisites

You have activated the system profile parameter Rec/Client, to be able to log the table changes in a client.

To be able to use the logging in transports, you must make the entry r3transoptions = recclient="XXX"in the transport control profile. You can enter the same value for XXX as for the profile parameter rec/client.

Activate/Deactivate Table Change Logging

...

1. Choose Tools ® ABAP Workbench ® Development ® Dictionary (SE11) in the initial screen.

2. Enter the name of the table whose log settings you want to check.

3. Choose Change.

The table is displayed. The system may ask you for a change key, because a change to a Dictionary object is a modification in a customer system. Enter the appropriate data.

4. Choose Goto ® Technical Settings.

5. Select/Deselect the Log Data Changes checkbox.

All customizing tables are automatically recorded by default.

6. Choose Activate.

If you only save the change, it is not effective.

Deactivate table change logging in the technical settings

To avoid generating too many log entries, you can deactivate the logging for specified tables when making bulk changes.

Deactivating the logging in the technical settings of the table in the Dictionary is not a modification. You do not need to specify a change key.

...

1. Choose the transaction Dictionary: Technical Settings (SE13).

2. Enter the table name.

3. Choose Change.

4. Deselect Log Data Changes.

5. Choose Activate.

You should not deactivate logging for customizing objects.

thanks

karthik

reward me points if usefull

[Former Member]

Hello karthik,

Thank you for the details but I've done this already. I've set table logging via SE11 / table details / technical settings and then can view the changes using SCU3. This is actually the only way I know how to do it. Unfortunately my Basis team is concerned that the top logging table DBTABLOG is very, very large so I wanted to see if there was another way to log activity / changes to tables that do not have built in change logs in their functional side.

Thanks again for your efforts. Most appreciated.

LP

[Former Member]

Hi,

Since you are already familiar with the DBTABLOG, let me get straight to the point.

Have you tried the option of Archiving the DBTABLOG data? You may like to check this - Link: [http://help.sap.com/saphelp_47x200/helpdata/en/8d/3e7006462a11d189000000e8323d3a/frameset.htm]

There is also an option of reading the archived logs via the SCU3 back again, so no worries.

In general, if the DBTABLOG size is really huge, maybe you can see the list of logged tables, and switch OFF logging for tables where logging is really not necessary. Helps the situation.

Regards,

Rekha

[Former Member]

Hi

i have requirement to use change pointers

But the changes are not getting saved in CDHDR/CDPOS tables

My table : FAGL_011pc

FAGL_011Zc

FAGL_011qt

I changed the Technical settings to "Log Data Changes"

The log is not creating in table "DBTABLOG" also.

What might be the reason

Pls urgent requirement.

[Former Member]

Hi Preeti,

change Documents (CDHDR/CDPOS) is a different thing from Activity Logs (DBTABLOG).

For Change documents (CDHDR/CDPOS), the logging has to be enabled at the Data Element level. Moreover, you need what is called a Change Document object defined via txn SCDO, for your application. You should maintain tables/structures for which you require change information, and generate automatic coding. In turn, you must call this generated module inside your application for the different actions.

(Your tables are FAGL_*, which are probably SAP Standard tables, so Change documents is not what you need. Such coding, if required must have already been implemented within the application).

For DBTABLOG, Activity Logs, please also read through the SAP note 1916. You can then take a call on whether the tables should be logged, and how you can get that done.

Regards

Rekha