Audit Log - Table Log

[Former Member]

Hi everyone,

Can anyone tell me if i activate table logging on a table (not customizing table) like MARC table, what information is saved in the system?.

Can I check or know, previous the audit log activation over this table, what fields or what information is recorded?

thanks,

HEPC

[Former Member]

Provided the table log is active( One way is by using t-code SE13 to look if data changes are logged), you can make use of t-code SCU3 to look at the logs. Per my understanding any changes in the table should be logged if table loggin is active for that table.

because data changes are logged it is not wise to activate table logging for transactional tables because of the performance issue that it will build up by logging all those changes. Customizing tables are not changed frequently so logging them do not bottle up performance.

[Former Member]

Hi,

Yes, I agree with you, for that reason we want to know, previos the log activation over that tables, what the system will save into the log file and with that information, we'll take a decission about.

Best Regards,

HEPC

[Former Member]

This SAP help document might help.[http://help.sap.com/SAPHelp_46c/helpdata/EN/cf/21eaf9446011d189700000e8322d00/frameset.htm] - per this document If logging is switched on, each change to an existing data record (with UPDATE, DELETE) by the user or application program is recorded in the database in a log table (DBTABPRT)

[Former Member]

After clicking on your 46C link, there is a search window in the top right corner right of "Help on Help".

If you type the term "native SQL" in there and hit enter, then a different scenario develops for table logging....

So, you also need to review code. ABAP is very powerfull!

Cheers,

Julius

[Former Member]

Hi Julius,

Could you explain me more, what transaction or what are the steps?

Thanks,

HEPC

[Former Member]

This is table logging for customizing type entries in not necessarily what you are looking for.

For master data you need to use the application change documents (table CDHDR etc) which is a different concept (I would use that route and protect the object S_ARCHIVE).

What you are actually looking for (and waiting for) is [the package concept at runtime|http://forums.sdn.sap.com/click.jspa?searchID=58483939&messageID=4675719] which developers can already see as warnings. It also means that the package which the table is assigned to must have a complete set of APIs.

I would personally not look for workarounds with performance impacts, but rather clean up the code to make it package concept conform, and then use the application change documents and not the table change records.

This is a better design - more sustainable, less hassles and auditable (via where-used-lists).

My 2 cents,

Julius

[Former Member]

Hello,

I need to know what the system would save if I active the table loggin on the table MARC for example, I don't need that for create or modify programs or reports.

Thanks

HEPC

[sdipanjan]

Hi,

Can you please check the following links? It has the information to considerable extent I hope.

[Logging Customizing Objects|http://help.sap.com/saphelp_nw70ehp1/helpdata/en/7e/c81ed552c511d182c50000e829fbfe/frameset.htm]

[Logging Changes to Table Data|http://help.sap.com/saphelp_nw70ehp1/helpdata/en/c7/69bcd2f36611d3a6510000e835363f/frameset.htm]

Regards,

Dipanjan

[sdipanjan]

Hi,

Can you please do a search with string Table Logging / SCU3 etc. in [Security Forum|;. As much as I can remember, there are many discussions happened earlier also on Table Logging and how it works.

Regards,

Dipanjan