Disabling application log created by standard transaction

[ankit_munshi2]

hello - We want to disable creation of application logs created by a standard transaction (EA58/EA29). Does anyone know about any config by which we can do it ?

Thanks!

AM

[rubin_luke3]

Hi AM,

I am unaware of a transaction to disable the standard application log, but using SLG2 you can delete the expired logs in the system. Even you can schedule a job to do that for you using SLG2.

regards,

[kiran_k8]

Ankit,

Let the logs get created through those transactions.May be someday you will find the need for such logs.

If needed you can explore creating a background job for SLG2 to delete the existings logs based on your requirement,at regular intervals.

Btw,why do you want to disable the creation of logs ?

K.Kiran.

[ChristinaHo]

It is not possible to deactivate the application log of a mass activity.

You can just reduce the problem class. With problem class 1 VERY HIGH you get less information.

In EA29 and EA58 you can unmark the flag Extended Log.

[ankit_munshi2]

hello - there's no problem class option on screen in EA29. Also, extended log flag is already un-checked.

Thanks!

AM

[matt]

Why do you want to disable the logs? They do no harm if they're created and slg2 will allow cleanup.

[AmlanBanerjee]

Hi Ankit,

There is a way to disable Application log for mass jobs.

For EA29, the mass activity is BIPR

For EA58, the mass activity is CBPR.

Go to the following SPRO Config- IMG--->Financial Accounting--->Contract Accounts Receivable and Payable--->Technical Settings---->Prepare Mass Activities

Search for the mass activity BIPR and CBPR and untick the log level3 tick as shown below

Hope it helps

Thanks

Amlan

[ankit_munshi2]

Hi Amlan,

I tried to deselect the checkbox and re-run EA29. Application logs were still created.

Thanks!

AM

[william_eastman]

disabling the logs is not a good idea - and is very unusual. It sounds like you have a problem in your print form design that is generating too many messages, which is not in the standard logic but in your custom logic. I would look into that!

[ankit_munshi2]

It was indeed a piece of custom code which was triggering too many logs. The log entries were coming frm a standard function module. We wrote a piece of code right before and after the standard function module to turn off logging.

Thanks!

AM