Named-User Counts in the CCMS Monitoring Architecture
The Named Users monitoring tree in the System Configuration contextreports on the numbers of users defined in the main SAP ABAP userrepository, table USR02.
USR02 classifies users according to these types:

• A: normal dialog users


• B: System users for internal RFC and background processing


• C: Communication users for external RFC


• L: Reference users


• S: Service users.

By default, the data collection method reports only on type A users byclient.
If you wish, you can customize the behaviour of the data collectionmethod in two ways, by setting parameters in the method definitionCCMS_Named_Users_Collect. The parameters and their effects are asfollows:

• ALERT_ON_USER_COUNTS: By default, no alerts are generated for user
counts. They are reported into text attribute MTEs. By setting thisparameter to X, you can have the counts reported into performance MTEs,which can generate alerts.

• REPORT_ALL_USERTYPES: By default, the data supplier reports only on
dialog users (type A) by client. By setting this parameter to X, youcan have the data supplier report counts of all five USR02 user types.

• TRACE: Setting this parameter to 'X' tells the data supplier to write
progress messages to the MoniInfra_Server->Datasupplier->Log message logMTE in CCMS_Selfmonitoring, monitor collection SAP CCMS Technical ExpertMonitors.
A word of caution: The USR02 user counts are the basis of thenamed-user counts that determine customers costs under typical SAPcontracts. However, the USR02 numbers of themselves are not adquate fordetermining any user counts for purposes of contract pricing. Suchcounts can only be derived by classifying users according to thecategories stored in table USR06 and presented in transaction USMM -System Measurement.
As an example, cost-free Web users of an SAP System have normal type Adialog user master records in USR02, and a large customer may addthousands of these users a month, without incurring any costs under itsSAP contract.
The classification of users is a customer task. At large customers, theclassification is often kept up-to-date, but at smaller customers, theclassification is often a once-a-year job when SAP requests a SystemMeasurement. For this reason, the Monitoring Architecture does notattempt to evaluate USR06 classifications, since the results may bemisleading.
For your convenience, the usmm transaction for user classification andthe system survey is the analysis method for the user counts monitor.