The Accounting Exit allows the allocation of system resources used by the application systems to accounting units. The system resources are the number of screen changes made, the used CPU time on the R/3 application systems, and other common time values from the workload statistics. In principle it is then possible to assign system loads to user groups (also client-specifically if necessary). Database resources are also taken into account.
The accounting analysis is based on the Workload Monitor statistics. No action is taken during the analysis which could lead to data being changed.
The workload statistics of the application systems must be active for a functional accounting to take place. SAP delivers the R/3 System preset with active statistics; this can be recognized by the profile parameter "stat/level = 1" for the application systems in question. A further requirement for meaningful accounting is the maintenance of the user master records, that is, the allocation of users to accounting units in the user master data maintenance. If the account is not maintained, it is managed under the account "No account".
No special measures are necessary for installation.
Maintenance of the user master records, field "Account number". This corresponds to the ACCNT field in the USR02 table.
The accounting information is available for several past periods. Data is available stored on a daily, weekly or monthly basis. At least the last 2 periods are available in the standard system. A user-defined residence time can be set in the Workload Monitor. Use the menu path "Administration -> Monitor -> Performance -> Workload -> Analysis" and choose "Goto -> Parameters -> Performance database". The corresponding values can be changed there under "Standard statistics residence time".
Report RSSTAT10 can be started in the background. Use the start parameter "Accounting report only" and, if required, choose client-dependent reporting with "Accounting profile by client".
There are two ways of doing an analysis of accounting. Firstly, there is a report for displayed the data gathered. Secondly, there are two function modules which can be used for reading the underlying data and passing it to custom-coded accounting software.
The display program is called RSSTAT10 and is contained in the Workload Monitor transaction (Administration -> Monitor -> Performance -> Workload -> Analysis). The required application server or the total of all the application servers can be selected using the function key "Performance database", the same way as for the corresponding period under review. The result can then be displayed in the interactive list via "Goto -> Accounting profile". Note: The list can also be generated by report RSSTAT10.
The function modules for accessing the accounting data are contained in the function group STUW. This contains the function modules SAPWL_ACCNT_GET_DIRECTORY and SAPWL_ACCNT_GET_SYSTEM_USAGE. The first of these is for obtaining an overview of the available accounting data, whilst the second is used for reading the data itself.
Since in the RSSTAT10 program the account is derived from the user master at the time of analysis, deleted user master data cannot be taken into account. Users who only work in the R/3 System at certain times are therefore, when using the RSSTAT10 program, to be administered by specifying the validity interval and not by deleting the user master record. Since the data is only calculated at the time of analysis, you can also redefine accounts later.
Function modules can also be used to simulate a previous status of the user master data, if required, since a specific assignment of users to accounts can be passed to the function modules where necessary. If the current status of the user master is to be used, then a user-account assignment must also be specified.