Planning and Deleting Runtime Measurements 

Using the For User/Service pushbutton on the initial screen of the transaction, you branch to a follow-on screen where you can plan runtime measurements and can also display or delete measurements already planned.

Displaying and Editing Planned Runtime Measurements

The screen displays a list of all currently planned runtime measurements. Using the Update function, you can refresh the display to check whether the status of a planned measurement has changed. To delete planned measurements, you simply select the line and choose the Delete function.

Planning Runtime Measurements

You use the function Create to plan a new measurement. In the following dialog box, the system displays the parameters for the measurement:

·        User

·        External Session

·        Process Type

·        Object Type

·        Object Name

·        Number of Measurements

·        End of Validity

Notes on Filling the Input Fields

In the User field, you must enter the user under whose name the event to be measured will run. The name specification is optional. If no user is entered, the user is not taken into consideration for the planned measurement – that is, actions of any arbitrary user can be measured.

The specification of the client is also optional and serves to uniquely identify the user. (users MAIER/000 and MAIER/100 may possibly be assigned to different persons).  

If the measurement is to be activated for a particular external session, a corresponding value can be entered for this.

In addition to the option “arbitrary”, the following types of processes can be specified:

·        Dialog

·        Update

·        Background Processing (batch)

·        RFC

·        HTTP

·        SMTP

·        ITS

·        Shared Objects Area Constructor

The object to be measured can also be arbitrary, or one of the following types. Remember, however, that only certain combinations make sense.

·        Transaction (starting a transaction) – suits dialog, background processing

·        Report (calling a program) – suits dialog, update, background processing

·        Function module (calling a function module / RFC) – suits dialog, update, background processing, RFC

·        Shared Objects Area Constructor (setting up a shared objects area) - suits shared objects area constructor

·        URL (calling a URL through ITS or HTTP) – suits http, SMTP, ITS

The object name is also optional and specifies the name of an object of the selected type. Here you need only enter a prefix – that is, the specification “F1” for a report would mean that each execution of a report whose name begins with “F1” can be measured.

The maximum number of planned measurements specifies how many measurements are to be created. The expiry date and time serve to limit the validity of the planned measurement.  As soon as the maximum number of measurements of the expiry time has been reached, the status for planning is set to “finished”.