AUD and STAT file

[Former Member]

Hi All,

Please let me know how AUD(Security Audit log) and STATSAP Workload Business Transaction Analysis file is generated. Whether there is any collector job running in background? What is the SAP standard object involved in generating these 2 files.

Thank you.

With Regards,

Gandhi Subramani

[Former Member]

Hi ,

Before you activate the Security audit in SM19, need to do many validations in the system.

Job SAP_COLLECTOR_FOR_NONE_R3_STAT is for Business stats.

The collector is started by the job SAP_COLLECTOR_FOR_NONE_R3_STAT. By default, this job runs hourly and is an SAP standard job; you can schedule it using transaction SM36 (Define Job) by choosing the Standard Jobs button.

PurposeABAP statistics records are generated to measure and analyze the performance of an ABAP system and its components. These statistics records provide information about the workload generated and the resources used in the system by actions. This provides you with a very exact picture of the quality of a system. If performance bottlenecks are detected, you can use this data to determine which component is responsible for them, and can then make the appropriate changes in a targeted way. The Distributed Statistics Records (DSRs) extend this concept for non-ABAP components.

There are two types of statistics records: main records and subrecords:

A main record is always generated when a business action is triggered in the system. An action of this type can be:

In dialog: a dialog step (start of a transaction, triggering of a function code, start of a program)

In background processing: start of a job

A main record forms the logical brackets around a business action. A transaction usually consists of multiple business actions.

A subrecord describes the subactions that are processed within a business action, such as RFC calls or DB accesses. One or more subrecords are always assigned to a main record.

You can use the statistics data to analyze performance problems in great detail. They are the basis of the SAP performance analysis tools, which are mainly used by SAP Support. These analysis tools are:

Business Transaction Analysis (Transaction STAD)

The Business Transactions Analysis calculates the system resource usage of individual transactions for the local ABAP system and provides a detailed analysis of a transaction and its dialog steps. The data is taken directly from the statistics files.

Functional Trace (transaction STATTRACE)

You can use the functional trace to display individual statistics records from ABAP and non-ABAP systems from complex system landscapes. The statistical data of remote ABAP systems is accessed by RFC. For remote non-ABAP systems, the data is read using the SAPCCMSR agent.

Workload Monitor (transaction ST03)

You can use the workload monitor to analyze statistical data for the ABAP kernel. You can display the data for all instances of the local system. The aggregates of the statistics files that are stored in the systemu2019s database are displayed.

Global Workload Monitor (transaction ST03G)

The Global Workload Monitor displays statistical records for entire landscapes and therefore allows you to analyze statistics data for both ABAP and non-ABAP systems. The aggregates of the statistics files are also displayed here.

As of BI Content 7.03 Add-On (Plug-In release 2005.1, OLTP release 7.00), the statistics records are available to you in the Business Warehouse. Both the statistics files themselves and the aggregates are available.

-

---

pre-requisistes for acitviation Audit log

rsau/max_diskspace/local and rsau/max_diskspace/perfile

parameters?

rsau/max_diskspace/local

rslg/max_diskspace/central

rslg/max_diskspace/local

rstr/max_diskspace

rsau/max_diskspace/local

rslg/max_diskspace/central

rslg/max_diskspace/local

rstr/max_diskspace

Activating the audit log

The following instance profiles must be set in order to activate audit logging (use transaction RZ10 to do so).

rsau/enable: Set to 1 to activates audit logging

rsau/local/file: Name and location of the audit log file

rsau/max_diskspace/local: Max. space of the audit file. If maximum size is reached auditing stops.

rsau/selection_slots: Max. number of filters

The settings are activated after the instance has been restarted.

Purpose

The Security Audit Log is a tool designed for auditors who need to take a detailed look at what occurs in the SAP System. By activating the audit log, you keep a record of those activities you consider relevant for auditing. You can then access this information for evaluation in the form of an audit analysis report.

The audit log's main objective is to record:

Security-related changes to the SAP System environment

(for example, changes to user master records)

Information that provides a higher level of transparency

(for example, successful and unsuccessful logon attempts)

Information that enables the reconstruction of a series of events

(for example, successful or unsuccessful transaction starts)

Specifically, you can record the following information in the Security Audit Log:

Successful and unsuccessful dialog logon attempts

Successful and unsuccessful RFC logon attempts

RFC calls to function modules

Successful and unsuccessful transaction starts

Successful and unsuccessful report starts

Changes to user master records

Changes to the audit configuration