Many questions in IT service management can only be answered if there is comprehensive information about your IT system usage (reports, RFC, FIORI services etc.). The corresponding information is only available in SAP systems for a short period of time and must be stored in an appropriate format for permanent use. SUIM's Application Tracer offers a powerful, time-saving solution to monitor, analyze and report on activities and systems, as and when you need.
Efficiency
Flexibility
Simplicity
Authorizations related entitites
Identity related entitites
Integration with 3rd parties products
Integration in other SUIM products
Following IT-system usage data can be analyzed:
- Transactions or FIORI services used per user, organizational unit, or system
- RFC function usage and the original system
- Table usage: which table was read and by whom
- Report usage: which report was executed with SE38/SA38
- Role usage/business roles (AM/AMSO)
- http services and use of mime objects
- Execution type: dialogue, batch, http etc.
Unlike SAP standard workload monitoring (ST03N) that deletes the data after certain time, AT allows you to store the traced data unlimited. Therefore it is important to optimize your storage space by storing only the relevant attributes and reducing the amount of data to the necessary minimum. The tracing activities of AT can be customized according to your needs.
Flexible collectors that can collect and centrally store the relevant data in all SAP ABAP stack systems ???
Addtitionally an open gateway is delivered to extend AT in order to integrate also your non-SAP ABAP stack systems.
A customizing workspace is included for configuring the application tracer. The Launchpad Designer tool allows you to create different launchpads depending on your AT end-user roles (AT as a tool for your development team, authorization team, controller, reviewer etc.). By separating different end-user launchpads with different monitoring levels that ensures compliance with data protection guidelines.
Organizational view: The organizational view allows you to have statistics to know which applications are used by which organizational unit (or user/user group).
Technical view: The technical view gathers results to see the degree of use of in-house developed programs, services used etc. The data give you relevant information about e.g. what ICF services should be enabled/disabled, what transactions should be removed from roles etc.
Authorization view: The authorization view allows you to have statistics on the use of roles / parts of roles, to do research for auditors, to optimize the indirect use of functions, to set licenses on only executed actions, optimize security on table access and RFC calls.