Implement LOG on few tables

[Former Member]

We will put auditory control on some few tables, transaction SE13 -> LOG

The problem is to find a procedure to do this massively.

SAP standard has about 3.000 table with this check ON and we need the log on 20 tables.

I red an article that is possible to do this changing the field PROTOKOLL on DD09L, we are analizing to do this change developing a program.

The question is:

Do you know this procedure?

Is safety?

We need to change another table?

There is any Note or procedure that SAP recomend?

Regards

Marcelo Bagattí

[Former Member]

And I think you don't understand what you are doing and are about to create a big mess...

[Former Member]

20 tables should not be a hassle....

No, it is not safe to update single fields of SAP tables directly. In this case there is at least one other table which also plays a part. Generally, change documents are not created either, and there will be no record in the system when you upgrade to let you know that you have changed something with a dependency.

Get yourself a coffee and click 20 times...

Cheers,

Julius

[Former Member]

You don't understood the question

I need turn off the log for 3.000 tables, so i need select each table by the name and put off .... after that transport the changes to QAS and PRD, if same table is diferent, etc.

The job and the risk is high ....

[Former Member]

Updating DD09L-PROTOKOLL will not remove the log for the 3000 tables.

I am not aware of a standard utility for this, and the requirement is a bit suspect.

What is your concern?

If there are performance problems, investigate then individually, as you have individually identified the 20 tables you do want to log.

Perhaps you are confusing table change logging with application change documents? Those are 2 different things.

Try to locate the problem and fix only that one, instead of globally turning logging off.

Cheers,

Julius

[Former Member]

This procedure have a high impact on the SAP perfomance, the recomendation is to set only a few tables.

For security reason i need the LOG in 20 tables and not in 15,000 as is now (this is the correct number).

My problem is setup only that i need (20 tables)

[Former Member]

What will you do when folks have made customizing changes and never released the transports?

How will you find out who did what and when for any further maintenance on such objects?

Sorry, I think your requirement is invalid...

Cheers,

Julius

[Former Member]

Julius i think that you don't understood the question and the solution.

If i made a program to do this, assign for unique time this transaction a one special user, run and test, in development, quality and production.

All the changes and testing are maded and registered.

[Former Member]

And I think you don't understand what you are doing and are about to create a big mess...

[sdipanjan]

> We will put auditory control on some few tables, transaction SE13 -> LOG

>

> The problem is to find a procedure to do this massively.

>

20 tables Not at all Massive work. What will you do if you get change to update any Master Data thousands in number?

> SAP standard has about 3.000 table with this check ON and we need the log on 20 tables.

>

> I red an article that is possible to do this changing the field PROTOKOLL on DD09L, we are analizing to do this change developing a program.

>

> The question is:

> Do you know this procedure?

> Is safety?

Not at all. If you need to create a new client what you used to do? Do you use SCC4 or just make entry directly in T000 by using Table maintenance functions. Similarly here also, you should use SE13.

> We need to change another table?

No. Don't update any Table directly. Use the Dialog transactions as SAP provided.

> There is any Note or procedure that SAP recomend?

>

SAP Doesn't recommend direct table maintenance of it's own name space.

Regards,

Dipanjan

[Former Member]

Standard SAP come with the flag LOG = ON for 13,000 tables

I need to turn OFF this FLAG for 12,980 tables.

If this FLAG represents only one value in the field DD09L->PROTOKOLL, change it represents few time, anyone do this work in this mode?

Regards

Marcelo

[sdipanjan]

>

> Standard SAP come with the flag LOG = ON for 13,000 tables

>

> I need to turn OFF this FLAG for 12,980 tables.

>

> If this FLAG represents only one value in the field DD09L->PROTOKOLL, change it represents few time, anyone do this work in this mode?

First of all, you should not make any changes to SAP Proposals... so don't deactivate Table logs for the Tables as SAP Proposed to be active. If you want to know the reason: Suppose some day you need to raise a support message to OSS and need help from SAP. They want to analyze logs of few tables which are logged as per proposal from SAP and they couldn't find.....

In this scenario, you may lose the opportunity of any support from SAP.

For you assistance please check the following SAP Notes:

[ SAP Note 112388 Tables are subject to logging|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_sec/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d313132333838%7d]

[SAP Note 15184 Error in table logging|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_db/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d3135313834%7d]

Regards,

Dipanjan

[Former Member]

The proposal of SAP is to be very carefull to active this process, look the note 1916

"Changes to control and customizing tables, for example, can be logged (refer to SAP Note 1916). The logs are

stored in table DBTABLOG.

Recorded are always "Before images" before the change u2013 which means the complete set of entries.

Changes to master data tables, however, are stored in the corresponding business areas using change

documents (tables CDHDR, CDCLS). An overview of FI and MM tables that are subject to logging is provided in

the audit guides for R/3 FI and R/3 MM (SAP Note 112388 u2018Tables are subject to loggingu2019).

Basically, all customizing tables are delivered with activated logging because the requirements of external

auditors are inconsistent as regards the logging of tables. Tables for master and transaction data, on the other

+hand, are delivered by SAP without logging indicators. A large number of these tables are subject to mass+

changes, which would cause performance problems if they were logged. You should use great caution if you want

+to log any of these tables. "+

[Former Member]

No. You are misinterpreting the note.

It is saying that transaction and master data tables are generally not logged using the table logging mechanism, so you should be carefull if you additionally turn these tables on for table logging. They have their own application change documents.

=> SAP delivers the customizing tables with a default flag, not the BSEG.

Your requirement is not valid.

Cheers,

Julius

[Former Member]

You know any implementation of LOG with the SAP Table proposal?

Put LOG on 15,000 tables for me is a high risk when the company need 20.

Why not put log only that we need?

Today the LOG is not active, so we don't have nothing.

Edited by: Seguridad Sap TEIC on Jul 9, 2009 3:05 PM

Edited by: Seguridad Sap TEIC on Jul 9, 2009 3:06 PM

[Former Member]

> You know any implementation of LOG with the SAP Table proposal?

Yes, most of them. Including the transport tool logging. No problems...

> Put LOG on 15,000 tables for me is a high risk when the company need 20.

If they are generally customizing tables, and you are not making mass customzing changes (e.g. adding 1 million company codes to T001?) to those projects which you do use in the system (which is unlikely) then where is the risk?

Of course some table might be incorrectly logged (also in the Z* and Y* range.

> Why not put log only that we need?

SAP gives you defaults. If you don't use the customizing, there is no log, even although it is active.

> Today the LOG is not active, so we don't have nothing.

Exactly. So turn it on in PROD and DEV, and optionally in QAS clients.

I still don't see your requirement. Only an urban legend..

Please read the note again carefully, differentiating between customizing objects (rec/client) and master data tables (CDHDR).

Cheers,

Julius

[sdipanjan]

>

> Basically, all customizing tables are delivered with activated logging because the requirements of external

>

> auditors are inconsistent as regards the logging of tables. Tables for master and transaction data, on the other

>

> +hand, are delivered by SAP without logging indicators. A large number of these tables are subject to mass+

>

> changes, which would cause performance problems if they were logged. You should use great caution if you want

>

> +to log any of these tables. "+

Customizing Table contents doesn't go for massive changes throughout it's life cycle (pre archive). So system performance for frequent changes are not evident and thus can be logged. Also maximum Business critical data are stored here including your company structure. So it's a great idea to monitor any change made on these tables from structural as well as contents point of view and thus SAP provides them with Logging active.

Transactional and Master data records go though severe changes, append and enhancement on daily basis almost and to monitor each of any such changes requires enormous system resource which will affect dialog response time (one e.g. of impact on system) during business hrs. So SAP doesn't though about logging them to monitor the changes. Instead they have come up with New Transactions to review change history of Master and Transactional data by using ALV to get our desired layout with sort and filter (etc. ..) facilities.

I have tried to make it clear in layman language ..... your requirement is to activate logging 20 Tables as per your company policy. So please go ahead with that (keeping in mind that you are not putting On any Master/Trnx table) if they are not proposed by SAP. But please do not play with SAP Proposals. There should not be any excuse to Create any such SOP to alter SAP Defaults in this case.

Regards,

Dipanjan

[Former Member]

> But please do not play with SAP Proposals. There should not be any excuse to Create any such SOP to alter SAP Defaults in this case.

Actually I have often tweaked SAP proposals, typically by adding some additional standard tables. In higher releases, this is less necessary as SAP have added most of them to the standard.

But I still add a few.

Cheers,

Julius

[Former Member]

People, I find several notes where SAP recommended changing this flag for some tables. For example KONP table.

This table has 1 million records in my systemu2026u2026

Note 672503

https://websmp230.sap-ag.de/sap(bD1lcyZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=672503

[Former Member]

Moved from Security to ABAP Data Dictionary forum...