Application Help for Logging of SAP NetWeaver BW Access

Application Help PUBLIC

Document Version: 1.0 – 2017-12-18

Application Help for Logging of SAP NetWeaver BW Access

Content

1 What's New in UI Logging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Logging of SAP NetWeaver BW Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

3 Logging of Data in SAP NetWeaver BW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

4 Logging of BEx Analyzer and BEx Web Applications in SAP NetWeaver BW. . . . . . . . . . . . . . . . .8

5 Logging of BEx Analyzer and BEx Web Applications in Business Warehouse Integrated Planning (BI-IP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

6 Logging of Data Accessed Through MDX Statements or BICS. . . . . . . . . . . . . . . . . . . . . . . . . . 11

7 Adjustments to Data Records for Transfer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

8 Simulation of Data Record Transfer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

9 Transfer Data to External Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

10 User Interface Logging - Common Part. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1710.1 Logging of Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1810.2 Transfer of Log Records to the External Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2010.3 Maintaining User Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2310.4 Adjustments to the Logging Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2410.5 Simulation of Data Record Transfer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2510.6 Setting Filtering and Mapping of Data Transfer from Temporary Log to Log Repository. . . . . . . . . . . 2610.7 Archiving Log Repository Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2710.8 Alerting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2810.9 Remote Log Facility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

2 P U B L I CApplication Help for Logging of SAP NetWeaver BW Access

Content

1 What's New in UI Logging

The following table shows you what is new and what has changed for UI logging.

Table 1:

Topic Type of Change Required Support Package (SP)

More Information

Data Protection and Privacy: define legal reasons and retention periods for UI logging and assign them to the logged application

New SP04 for the Common Part of Logging (SWC LOGCOM 200), SP01 for Logging of SAP Gateway (SWC LOGGW 200), and SP03 for all other technologies

The Security Information of each of the UI Logging configuration guides discusses Data Protection and Privacy in detail. Visit https://help.sap.com/viewer/p/UI_LOGGING and select the relevant technology, then open the configuration guide

and see User Interface

Logging - Common PartConfiguring the Common

Part Security

Information . Note that the content of the common part in the configuration guide for each technology covers the Data Protection and Privacy topic in full.

Application Help for Logging of SAP NetWeaver BW AccessWhat's New in UI Logging P U B L I C 3

https://help.sap.com/viewer/p/UI_LOGGING



2 Logging of SAP NetWeaver BW Access

Product Information

Table 2:

Product Logging of SAP NetWeaver BW Access

Release Logging of SAP NetWeaver BW Access 2.0 (SP02)

Based On SAP NetWeaver 7.0 (including EHP1, EHP2 and EHP3), 7.3 (including EHP1), 7.4, and 7.5

Documentation published January 2017

Purpose

The violation of data privacy and industrial espionage are severe threats in today’s business world. This is especially true for companies or organizations in need of protecting highly sensitive information that cannot be safeguarded by setting authorization restrictions.

With logging of SAP NetWeaver BW access 2.0, SAP provides software for improving data security and compliance by logging data that is accessed by users in an SAP NetWeaver Business Warehouse (BW) system.

The logged data is stored in a temporary log and can subsequently be transferred to an external repository for the purpose of data evaluation and analysis.

Prerequisites

You have installed the platform-independent logging software (LOGCOM 200).

NoteFor more information about common, platform-independent features, see section User Interface Logging - Common Part [page 17], which is available as a part of the platform-specific documentation on SAP Service Marketplace athttps://support.sap.com/swdc Software Downloads Installations and Upgrades A–Z Index L LOGGING SAP NW BW ACCESS .


Logging of SAP NetWeaver BW Access

http://help.sap.com/disclaimer?site=https%3A%2F%2Fsupport.sap.com%2Fswdc

Prerequisites

The logging of SAP NetWeaver BW access 2.0 software allows you to establish which users had access to which data at which point in time in a SAP NetWeaver Business Warehouse (BW) and SAP NetWeaver Business Warehouse Integrated Planning (BI-IP) environment.

You analyze the data from the SAP NetWeaver BW system by defining queries in BEx query designer. The software allows you to log all data that is accessed through analyzing queries in one of the following SAP Business Explorer (BEx) tools:

● Business Explorer (BEx) Analyzer● Business Explorer (BEx) Web Application Designer

For more information, see Logging of BEx Analyzer and BEx Web Applications in SAP NetWeaver BW [page 8].

In addition, data that is accessed using MDX statements or Business Intelligence Consumer Services is logged. For more information, see Logging of Data Accessed Through MDX Statements or BICS [page 11]

In order to minimize the amount of logged data, you can do the following:

● Restrict logging to certain users● Enable logging on InfoObject, InfoProvider, and query level

Application Help for Logging of SAP NetWeaver BW AccessLogging of SAP NetWeaver BW Access P U B L I C 5

3 Logging of Data in SAP NetWeaver BW

You can log data accessed in an SAP NetWeaver Business Warehouse system using various SAP Business Explorer (BEx) front-end tools.

In addition to queries requested using BEx Analyzer and BEx Web applications, you can log MDX statements in SAP NetWeaver BW, as well as data accessed through BICS in BEx Analyzer and BEx Web applications.

After the system has processed the user input, the data displayed to and edited by the user is recorded and stored in a temporary log.

Prerequisites

You have made the following Customizing settings:

● You have activated logging on client level in Customizing for SAP NetWeaver UI Logging Common Settings Define General Logging Parameters .

● You have activated logging according to your requirements in Customizing for SAP NetWeaver Logging of SAP NetWeaver BW Access .

Features

NoteThe Customizing for logging is client-independent.

Process

1. The system checks the following:○ Whether logging is active on client level○ Whether logging is active for the current user○ Whether logging is active for the InfoObject, InfoProvider, or query in question

2. The system determines which data is to be logged.3. The system logs the data.

Each server roundtrip (request/response) is logged separately. Processing that happens entirely on client side is not logged.


Logging of Data in SAP NetWeaver BW

NoteYou can filter and adjust the data to be logged by implementing the appropriate Business Add-In. For more information, see the BAdI documentation in Customizing for Logging of SAP NetWeaver BW Access Business Add-Ins .

4. The system stores the data in a temporary log. In addition, a log identifying already logged data is created.

Result

A log record is created.

You can display the temporary log data by executing the Display of Temporary Log Data report (transaction code /LOGWIN/SHOW_LOG). For more information, see the report documentation in the system.

NoteIf you want to delete test data from the temporary log, you can do so by executing the Clear All Data from Temporary Log report (transaction code /LOGWIN/CLEAR_LOG).

If you want to clear the log that contains the “metadata” identifying which data has already been logged, you can do so by executing the Deletion of Log Identifying Already Logged Data report (transaction code /LOGWIN/DEL_AL_TABLE).

For more information, see the report documentation in the system.

You can subsequently transfer the logged data to the External Repository. You can also simulate this process before triggering the actual data transfer. For more information, see section User Interface Logging – Common Part.

Related Information

User Interface Logging - Common Part [page 17]

Application Help for Logging of SAP NetWeaver BW AccessLogging of Data in SAP NetWeaver BW P U B L I C 7

4 Logging of BEx Analyzer and BEx Web Applications in SAP NetWeaver BW

You can log result sets for queries requested via BEx Analyzer and BEx Web applications.

Features

Both tools offer two ways to request data, all of which are covered by the logging of SAP NetWeaver BW access 2.0 software. Logging is triggered by the following user activities:

● Business Explorer (BEx) Analyzer○ Opening a query○ Opening a workbook and refreshing the data

NoteIf the workbook is opened offline (that is, without connection to an SAP NetWeaver BW system) or without refreshing the data, no data is logged.

● Business Explorer (BEx) Web applications○ Starting a Web template ad-hoc from BEx Web Application Designer○ Starting a Web template via a URL or an iView in SAP NetWeaver Portal

Restrictions

Note that the order in which the data is logged does not necessarily correspond to the order in which the data is displayed in SAP Business Explorer.

When running a hierarchy query in SAP Business Explorer, the following applies:

● Business Explorer (BEx) Analyzer○ When the user runs a hierarchy query, the system logs the data that are displayed to the user.○ When the user drills down on the hierarchy query, both the expanded data and the original data are

logged.○ When the user collapses the expanded query items again, the system logs the data that is displayed to

the user.● Running a query in Business Explorer (BEx) Web:

○ When the user runs a hierarchy query, the system logs the data that is displayed to the user.○ When the user drills down on the hierarchy query, both the expanded data and the original data are

logged.○ When the user collapses the expanded query items again, the system does not log any data.


Logging of BEx Analyzer and BEx Web Applications in SAP NetWeaver BW

5 Logging of BEx Analyzer and BEx Web Applications in Business Warehouse Integrated Planning (BI-IP)

Similar to queries logged in SAP NetWeaver BW, you can log result sets for queries requested via BEx Web applications in Business Warehouse Integrated Planning.

Fetaures

Both tools offer two ways to request data, all of which are covered by the logging of SAP NetWeaver BW access 2.0 software. Logging is triggered by the following user activities:

● Business Explorer (BEx) Analyzer○ Opening a query○ Opening a workbook and refreshing the data

NoteIf the workbook is opened offline (that is, without connection to an SAP NetWeaver BW system) or without refreshing the data, no data is logged.

● Business Explorer (BEx) Web applications○ Starting a Web template ad-hoc from BEx Web Application Designer○ Starting a Web template via a URL or an iView in SAP NetWeaver Portal

The results displayed in Web applications or BEx Analyzer can be edited. Therefore, the system logs not only the results displayed to the user but also the delta information, that is, the changes made by the user.

Restrictions

Note that the order in which the data is logged does not necessarily correspond to the order in which the data is displayed in SAP Business Explorer.

When running a hierarchy query in SAP Business Explorer, the following applies:

● Business Explorer (BEx) Analyzer○ When the user runs a hierarchy query, the system logs the data that are displayed to the user.○ When the user drills down on the hierarchy query, both the expanded data and the original data are

logged.○ When the user collapses the expanded query items again, the system logs the data that is displayed to

the user.● Running a query in Business Explorer (BEx) Web

Application Help for Logging of SAP NetWeaver BW AccessLogging of BEx Analyzer and BEx Web Applications in Business Warehouse Integrated Planning (BI-IP) P U B L I C 9

○ When the user runs a hierarchy query, the system logs the data that is displayed to the user.○ When the user drills down on the hierarchy query, both the expanded data and the original data are

logged.○ When the user collapses the expanded query items again, the system does not log any data.

10 P U B L I C

Application Help for Logging of SAP NetWeaver BW AccessLogging of BEx Analyzer and BEx Web Applications in Business Warehouse Integrated

Planning (BI-IP)

6 Logging of Data Accessed Through MDX Statements or BICS

The logging of SAP NetWeaver BW access 2.0 software allows you to log MDX statements.

In addition, data accessed through Business Intelligence Consumer Services (BICS) using BEx Analyzer and BEx Web Application Designer is logged. The data is stored in a temporary log in its original format. In the case of MDX statements, the log contains the statement, which can be executed in transaction MDXTEST.

Features

If your system landscape is based on SAP_BW 700, access to the following interfaces is logged:

● BAPI_MDDATASET_GET_STREAMDATA● BAPI_MDDATASET_GET_CELL_DATA● BAPI_MDDATASET_GET_DATA_XMLA● BAPI_MDDATASET_GET_FLAT_DATA● BAPI_MDDATASET_GET_FS_DATA

If your system landscape is based on SAP_BW 701/702/710/711/720, access to the following interfaces is logged:

● BAPI_MDDATASET_GET_STREAMDATA● BAPI_MDDATASET_GET_CELL_DATA● BAPI_MDDATASET_GET_DATA_XMLA● BAPI_MDDATASET_GET_FLAT_DATA● BAPI_MDDATASET_GET_FS_DATA● RSR_MDX_BXML_GET_DATA● RSR_MDX_BXML_GET_GZIP_DATA

If your system landscape is based on SAP_BW 730, access to the following interfaces can be logged:

● BAPI_MDDATASET_GET_STREAMDATA● BAPI_MDDATASET_GET_CELL_DATA● BAPI_MDDATASET_GET_DATA_XMLA● BAPI_MDDATASET_GET_FLAT_DATA● BAPI_MDDATASET_GET_FS_DATA● RSR_MDX_GET_CELL_DATA● RSR_MDX_GET_FLAT_DATA● RSR_MDX_GET_FS_DATA● RSR_MDX_BXML_GET_DATA● RSR_MDX_BXML_GET_GZIP_DATA

Application Help for Logging of SAP NetWeaver BW AccessLogging of Data Accessed Through MDX Statements or BICS P U B L I C 11

The data is stored in the temporary log in its original format. You can use one of the following reports to display the data in a structured output format:

● Display of Temporary Log Data (transaction code /LOGWIN/SHOW_LOG)● Simulation of Data Transfer to an External System (transaction code /LOGWIN/SHOW_TSF_RST)● Simulation of Data Transfer to External Repository (Mem.-Efficient) (transaction code /LOGWIN/

SHOW_TSF_R_2)


Logging of Data Accessed Through MDX Statements or BICS

7 Adjustments to Data Records for Transfer

Before transferring the Temporary Log records to the External Repository, you can make adjustments to the logged data according to your requirements.

Prerequisites

● You have implemented the External Repository.

● You have defined the mapping for views and fields in Customizing for SAP NetWeaver Logging of SAP NetWeaver BW Access Configure Field Mapping for Data Transfer .

Features

● You can specify that certain data be excluded from the log transfer.● You can change or enhance the data while transferring it to the External Repository.

NoteThe Customizing for filtering and mapping for data transfer is client-dependent.

Activities

● If you want to exclude specific queries from being transferred to the External Repository, in Customizing for SAP NetWeaver Logging of SAP NetWeaver BW Access , choose Configure Field Mapping for Data Transfer Filtering InfoObjects . Select the Exclude checkbox for the InfoObjects that are not to be transferred.

NoteYou can automatically create entries for the views and fields of the logged transactions by executing the Generation of Mapping Entries report using transaction /LOGWIN/MAP_ENTRY. For more information, see the corresponding report documentation in the system.

● If you want to create descriptive short texts for the technical names of the logged InfoObjects that are to be transferred to the External Repository, in Customizing for SAP NetWeaver Logging of SAP NetWeaver BW Access , choose Configure Field Mapping for Data Transfer Filtering InfoObjects . Define descriptive short texts in the corresponding field.

Application Help for Logging of SAP NetWeaver BW AccessAdjustments to Data Records for Transfer P U B L I C 13

● If you want to change or enhance the data that is to be included in the Temporary Log records, you implement Business Add-Ins (BAdI) in Customizing for SAP NetWeaver Logging of SAP NetWeaver BW Access Business Add-Ins . For more information, see the BAdI documentation in the system.

● If you want to determine the format in the External Repository (new versus old data model), in Customizing for SAP NetWeaver Logging of SAP NetWeaver BW Access , choose Make Client-Dependent Settings.


Adjustments to Data Records for Transfer

8 Simulation of Data Record Transfer

You can simulate the transfer of logged data before you actually transfer the data records to the External Repository.

This allows you to test the mapping entries, which are used to map Temporary Log data to the format required by the implementation of the External Repository to which the data is sent.

Prerequisites

● You have implemented the Business Add-In /LOGWIN/GET_TRANSFER_HDL_BADI in Customizing for SAP NetWeaver UI Logging Common Settings Business Add-Ins BAdI: Retrieval of Transfer Handler

Implementation. .

● You have defined the mapping for InfoObjects in Customizing for SAP NetWeaver Logging of SAP NetWeaver BW Access Configure Field Mapping for Data Transfer .

Activities

To simulate the transfer of data to an External Repository, you execute the Simulation of Data Transfer to an External System report by using transaction /LOGWIN/SHOW_TSF_RST or /LOGWIN/SHOW_TSF_R_2.

After you have triggered the data transfer simulation, the system displays the data in the Temporary Log as it would be transferred to the External Repository. However, all data is kept and no changes to the database are made.

For more information, see the report documentation in the system as well as section User Interface Logging - Common Part [page 17] of the application help .

Application Help for Logging of SAP NetWeaver BW AccessSimulation of Data Record Transfer P U B L I C 15

9 Transfer Data to External Repository

After the data has been logged and stored in the Temporary Log, you can transfer it to the External Repository for the purpose of evaluation and analysis.

Prerequisites

● You have implemented the External Repository.

● You have defined the mapping of GUI views and fields in Customizing for SAP NetWeaver Logging of SAP NetWeaver BW Access Configure Field Mapping for Data Transfer

Activities

To display the data in the External Repository execute Display of External Repository Data report using transaction /LOGWIN/SHOW_EXT_L_2 and /LOGWIN/LOGANALYZER.

For more information, see the report documentation in the system as well as section User Interface Logging – Common Part.

Related Information

User Interface Logging - Common Part [page 17]


Transfer Data to External Repository

10 User Interface Logging - Common Part

Product Information

Table 3:

Product User Interface Logging – Common Part

Release User Interface Logging – Common Part 2.0 SP03

Based On SAP NetWeaver 7.0 (including EHP1, EHP2 and EHP3), 7.3 (including EHP1), 7.4 and 7.5

Documentation published December 2016

Purpose

The violation of data privacy and industrial espionage are severe threats in today’s business world. This is especially true for companies or organizations in need of protecting highly sensitive information that cannot be safeguarded by setting authorizations restrictions.

With user interface logging, SAP provides software for improving data security and compliance by logging all data that is displayed to and entered by users. The logged data is stored in a Temporary Log and can subsequently be transferred to the External Repository for the purpose of auditing and analysis.

Prerequisites

You have installed the platform-specific logging software components according to your requirements.

NoteWe recommend that you read the platform-specific section together with this section to gain an overview of all logging-specific functions and processes.

Features

User interface logging allows you to determine which users had access to which data at which point in time. You can log data that is entered by and displayed to users in various platform-specific environments. For more information, see the platform-specific section.

Application Help for Logging of SAP NetWeaver BW AccessUser Interface Logging - Common Part P U B L I C 17

In order to minimize the amount of logged data, you can do the following:

● Restrict UI logging to certain users● Disable or limit logging on client level

More Information

For more information about platform-specific features, read the appropriate sections for the respective technologies.

10.1 Logging of Data

You use this process to log data in your chosen platform.

All entries made by a user are captured. After the system has processed the user input, the data displayed to the user is recorded and stored in a Temporary Log.

Prerequisites

You have activated logging on client level in Customizing for SAP NetWeaver Common Settings for Logging Define General Logging Parameters . In addition, you have activated logging according to your requirements

in the appropriate, platform-specific Customizing activity.

Process

1. The system checks the following:1. Whether logging is active in general2. Whether logging is active for the current user3. Whether logging is active for the current platform-specific entities (for example, SAP GUI transaction,

BW InfoObject)2. The system determines which data is to be logged.3. The system logs the data.

Each server roundtrip (request/response) is logged separately. Processing that happens entirely on client side is not logged.

NoteYou can enhance the data to be logged according to your requirements by implementing the appropriate, platform-specific Business Add-In in your client system. For more information, see the BAdI documentation in your client system.


User Interface Logging - Common Part

4. The system stores the data in a Temporary Log.

The following figure provides an overview of the logging process:

Figure 1: Logging Process

Result

A log record is created. You can display the data in the Temporary Log by executing the Display of Temporary Log Data report (transaction code /LOGWIN/SHOW_LOG). For more information, see the report documentation in the system.

NoteIf you want to delete test data from the Temporary Log, you can do so by executing the Deletion of Data from External Log report using transaction /LOGWIN/DEL_EXTLOG. For more information, see the report documentation in the system.

The logged data can subsequently be transferred to the External Repository. For more information about this process, see Transfer of Log Records to the External Repository [page 20].


10.2 Transfer of Log Records to the External Repository

This process allows you to transfer the Temporary Log data to the External Repository, for example, for the purpose of data evaluation and analysis.

You have the following options:

● You can transfer the data without specifying size restrictions. We recommend this option if you do frequent transports of smaller amounts of data.

● You can transfer the data in a memory-efficient way by specifying size restrictions. We recommend this option if you want to transfer large amounts of data.

Prerequisites

● You have implemented the Business Add-In /LOGWIN/GET_TRANSFER_HDL_BADI in Customizing for SAP NetWeaver Common Settings for Logging Business Add-Ins BAdI: Retrieval of Transfer

Handler Implementation .● You have defined the appropriate mapping in the appropriate platform-specific Customizing (if applicable).

Process

1. To start the transfer of data records to an external system, you have the following options:○ You can access the Transfer of Data Records to an External System report by using transaction code /

LOGWIN/TSF_TO_EXT.○ If you want to transfer data in a memory-efficient way, you can access the Transfer of Data Records to

an External System (Mem.-Efficient) report by using transaction code /LOGWIN/TSF_TO_EXT_M.You can either schedule these reports as a background job or execute them manually. For more information, see the report documentation in the system.

NoteYou can also simulate the transfer of data records to an external system. For more information, see Simulation of Data Record Transfer [page 25].

2. The system loads the implementation for the transfer of data from the Temporary Log to the External Repository.

3. The data is selected from the Temporary Log according to the selection criteria specified in the transfer report.

4. The system filters and maps the selected data to the format required by the implementation of the External Repository.

5. The system sends the data to the External Repository.6. If the data transfer is successful, the data is by default deleted from the Temporary Log. If the data transfer

is not successful, the data is kept and set to status Failed to Transfer.



If the data transfer process was started but terminated due to unknown reasons, the data is kept in status Selected for Transfer.

NoteYou can reset the status of the data records from 10 (Selected for Transfer) to 00 (Logged During User Processing)) by executing the Reset Processing Status of Data Records report using transaction /LOGWIN/RESET_STATUS.


The following figure provides an overview of the transfer process:

Figure 2: Transfer Process



Result

The data records are transferred to the External Repository according to your requirements.

NoteIf you have transferred the data to the sample repository delivered by SAP, you can do the following:

You can display the data records in the sample repository by executing the Display of External Repository Datareport using transaction /LOGWIN/SHOW_EXT_L_2 and /LOGWIN/LOGANALYZER.

For /LOGWIN/LOGANALYZER, the graphic function is enabled. You can use it to review the log in chart, which provide a more visible mode. If you want to use the graphic, do not hide the Count column.

You can delete all data in the sample repository by executing the Deletion of Data from External Log report using transaction /LOGWIN/DEL_EXTLOG. For more information, see the report documentation in the system.

10.3 Maintaining User Manager

You use this function to include or exclude users from UI logging based on user name, user role, profiles, and group memberships. You can also check the results of the settings that you have made.

Prerequisites

You have activated or deactivated logging on client level in Customizing for SAP NetWeaver Common Settings for Logging Define General Logging Parameters .

Features

● Current Customizing○ Shows whether roles, profiles, groups, and users are currently included or excluded from UI logging. If

they are included in UI logging, the system logs the users who are maintained on the Users tab, users with roles that are maintained on the Roles tab, users with profiles that are maintained on the Profiles tab, users with groups that are maintained on the Groups tab. All other users are excluded. If they are excluded from UI logging, the system excludes the users, roles, profiles, groups, from UI logging.

○ Shows whether UI logging is switched on or off. If it is switched on, you can make changes in the user manager, but you cannot test them using the Check User option.

● Users tabYou can maintain the users who should be included / excluded from UI logging for a specified date range.

● Roles tab


You can assign the roles that should be included / excluded from UI logging for a specified date range. You can define the roles for the users in transaction SU01. The system includes / excludes all users who are assigned to the role from UI logging for the specified date range.

● Profiles tabYou can assign the profiles that should be included / excluded from UI logging for a specified date range. You can define the profiles for the users in transaction SU01. The system includes / excludes all users who are assigned to the profile from UI logging for the specified date range.

● Groups tabYou can assign the groups that should be included / excluded from UI logging for a specified date range. You can define the groups for the users in transaction SU01. The system includes / excludes all users who are assigned to the groups from UI logging for the specified date range.

● Exception UsersYou can assign the users for whom the rules for UI logging are reversed as per your settings, that is, the rules that apply to the other users are reversed for these users.

● Check User optionYou can enter or select a user to check whether the user is currently logged based on the current settings. The system also displays the reasons for the user being logged or not being logged. You must save your settings before using the Check User option.

Activities

To maintain the user manager, go to Customizing for SAP NetWeaver Common Settings for Logging User Management Maintain User Manager .

10.4 Adjustments to the Logging Process

You can define the settings for what is logged by excluding certain types of data from the log records or by excluding users from the log records.

Features

To adjust the data you want to include in the Temporary Log records, you can do the following:

● Exclude users from being logged● Change or enhance the data to be logged



Activities

● If you want to exclude a specific user from the Temporary Log records, you execute the Maintain Exclusion Entry for Specific User report by using transaction /LOGWIN/CREATE_USER. For more information, see the report documentation in the system.

NoteThis is an alternate transaction to exclude a specific user from the Temporary Log records. Typically, you should use the User Manager.

● If you want to exclude several users from the Temporary Log records, you execute the Create Exclusion Entry for Users report by using transaction /LOGWIN/DEF_USERS.

NoteThis is an alternate transaction to exclude several users from the Temporary Log records. Typically, you should use the User Manager.

● If you want to include/exclude an entry for users and reports, use transaction /LOGWIN/MAINTAINUSER Create and Maintain Incl./Excl. Entry for User and define the corresponding settings in Customizing for SAP NetWeaver under Define General Logging Parameters.

● If you want to change or enhance the data that is to be included in the Temporary Log records, you implement the appropriate Business Add-In (BAdI) in Customizing for SAP NetWeaver Common Settings for Logging Business Add-Ins BAdI: Retrieval of Transfer Handler Implementation . In addition, you must implement the appropriate BAdI in your chosen client platform.

10.5 Simulation of Data Record Transfer

You can simulate the transfer of logged data before you actually transfer the data records to the External Repository.

This allows you to test the mapping entries, which are used to map Temporary Log data to the format required by the implementation of the External Repository to which the data is sent.

Prerequisites

● (Optional) You have implemented the Business Add-In /LOGWIN/GET_TRANSFER_HDL_BADI in Customizing for SAP NetWeaver Common Settings for Logging Business Add-Ins BAdI: Retrieval of Transfer Handler Implementation . In addition, you have activated logging according to your requirements in the appropriate, platform-specific Customizing activity.

● You have defined filtering and mapping configurations in the appropriate platform-specific Customizing (if applicable).


NoteYou can automatically create mapping entries for the logged entities by executing the Generation of Mapping Entries report using transaction /LOGWIN/MAP_ENTRY. For more information, see the report documentation in the system.

Activities

To simulate the transfer of data to the External Repository, you have the following options:

● You can simulate the data transfer without specifying size restrictions. We recommend this option if you do frequent transports of smaller amounts of data.To simulate the data transfer, you use transaction /LOGWIN/SHOW_TSF_RST. For more information, see the report documentation in the system.

● You can simulate a memory-efficient data transfer by specifying size restrictions. We recommend this option if you want to simulate the transfer of large amounts of data.To simulate the memory-efficient data transfer, you use transaction /LOGWIN/SHOW_TSF_R_2. For more information, see the report documentation in the system.

After you have triggered the data transfer simulation, the system displays the data in the Temporary Log as it would be transferred to the External Repository. However, all data is kept and no changes to the database are made.

10.6 Setting Filtering and Mapping of Data Transfer from Temporary Log to Log Repository

You use this function to make technology-dependent Customizing entries for the Temporary Log.

It is also used to generate mapping entries, which are used to map Temporary Log data to the format required by the implementation of the External Repository to which the data is sent.

Activities

Execute the following steps to set up the filtering and mapping of data transfer from Temporary Log to Log Repository:

1. Clear the Temporary Log using transaction /LOGWIN/DEL_EXTLOG.

2. In Customizing activity Define General Parameters under SAP NetWeaver Common Settings for Logging , deactivate the filter for Temporary Log.

3. Call the transaction, web service, function, gateway service to be logged.4. Execute report Generation of Mapping Entries (transaction /LOGWIN/MAP_ENTRY).



5. Depending on your settings, this report creates the Customizing entries for the Temporary Log and/or the field mapping for data transfer. For example, in the case of OData filtering, the report creates Customizing entries for Configure Temporary Log Creation and in the case of OData transfer, the report creates Customizing entries for Configure Filtering and Mapping for Data Transfer.

6. Go to the list of fields in Customizing; delete the unwanted entries and save it.7. Activate the filter for Temporary Log.8. Call the transaction to be logged again and check the Temporary Log.9. In an iteration, adapt the field list and check the Temporary Log until you get the desired Temporary Log.

10.7 Archiving Log Repository Data

With data archiving, you can keep the size of the database under control and ensure long-term access to your External Log data.

Data no longer required for daily operations or accessed less frequently is moved from the database to archive files.

Process

1. Preprocessing ProgramActivities○ To select the Log Repository data to be archived, use transaction /LOGWIN/ARCHIVE_PRE.○ If you run the preprocessing program in Test Mode in Processing Options, the program shows the

number of the database entries to be archived in the result list, but it will not change anything in database.

○ If you run the preprocessing program in Production Mode in Processing Options, the preprocessing program carries out the archivablility check. In addition, it sets a status for all archivable External Log data. The archive status will be set to Selected for Archiving.

2. Write ProgramActivities○ You can archive the External Log by using transaction /LOGWIN/ARCHIVE_WRT.○ Enter the number of records to be archived in the selection screen.○ If you run the write program in Test Mode in Processing Options, the program selects External Log data

whose archive status has been set to Selected for Archiving and shows the result if the selected data has been archived successfully.

○ If you run the write program in Production Mode in Processing Options, the program selects External Log data whose archive status has been set to Selected for Archiving. It shows the result if the selected data has been archived successfully and the archive status will be set to Archived.

3. Reset ProgramActivities○ If the write program terminates abnormally during processing, the status of part of the selected

External Log data is set to Selected for Write. If you want to reset the status of the External Log, run report /LOGWIN/EXT_LOG_ARCHIVE_RESET.


○ If you choose Selected for Archiving, the status of the External Log data whose archive status is Selected for Write is set to Selected for Archiving.

○ If you choose Not Archived, the status of the External Log data whose archive status is Selected for Write is set to Not Archived.

4. Delete ProgramActivities○ You can read the archive file and delete the corresponding External Log data from the database by

using transaction /LOGWIN/ARCHIVE_DEL.○ If you run the delete program in Test Mode in Processing Options, the program selects External Log

data whose archive status has been set as Archived. It also shows the result if the selected data has been deleted successfully.

○ If you run the delete program in Production Mode in Processing Options, the program selects the External Log data whose archive status has been set to Archived. It also shows the result if the selected data has been deleted successfully.

5. Delete ProgramActivities○ You can read the archive file and delete the corresponding External Log data from the database by

using transaction /LOGWIN/ARCHIVE_DEL.○ If you run the delete program in Test Mode in Processing Options, the program selects External Log

data whose archive status has been set as Archived. It also shows the result if the selected data has been deleted successfully.

○ If you run the delete program in Production Mode in Processing Options, the program selects the External Log data whose archive status has been set to Archived. It also shows the result if the selected data has been deleted successfully.

6. Read ProgramActivities○ You can read the archive file and display the data by using transaction /LOGWIN/ARCHIVE_READ.

7. Reload ProgramActivities○ You can reload the archived External Log data from the archive files into the database by using

transaction /LOGWIN/ARCHIVE_RELD.○ If you run the reload program in Test Mode in Processing Options, the program shows the result if the

archive data can be reloaded.○ If you run the reload program in Production Mode in Processing Options, the program shows the result

if the archive data has been reloaded successfully and the archive status is set to reloaded.

10.8 Alerting

You use this function to send alerts to the user’s monitor during the runtime, in the case of any illegal access to sensitive data.

The alerts can be sent in different forms, for example, emails, short message service (SMS), SAP workspace mail, and so on.



Prerequisites

● You have maintained the alert categories, recipients for UI logging in Customizing using transaction ALRTCATDEF under classification ALERTS FOR UI LOGGING.

● You have maintained the following fields in Customizing under SAP NetWeaver Common Settings for Logging Define General Logging Parameters :○ Alerting On/Off ○ Alert Destination

● You have maintained the following activities in Customizing under SAP NetWeaver Common Settings for Logging Alerting :○ Maintain Alerting Conditions○ Edit Alerting Conditions○ Maintain Alerting Parameters

Integration

During the creation of the Temporary Log record, the system reads the Temporary Log according to alerting conditions and triggers the alerts. If the Temporary Log is not activated for certain entries, for example, transaction code, work area, info provider, remote function call, web service, OData service, no alerts are triggered for those entities.

10.9 Remote Log Facility

You use this function to save the External Log data to another server during transfer of Temporary Log data to the External Repository.

You can build up a remote log system to gather all External Log from different systems and hold it for further action, for example, for the purpose of data evaluation and analysis.

The Central Log is required to have a central place for data evaluation and analysis for specified users in a particular system landscape. Besides security reasons, the central log also improves user experience and increases the efficiency of work processes.

Prerequisites

You have maintained the remote log destination (Remote Log Dest. field) in Customizing for SAP NetWeaverCommon Settings for Logging Define General Logging Parameters .


Activities

To start the transfer of data records to a remote system, you have the following options:

● You can access the Transfer of Data Records to an External System report by using transaction code /LOGWIN/TSF_TO_EXT.

● If you want to transfer data in a memory-efficient way, you can access the Transfer of Data Records to an External System (Mem.-Efficient) report by using transaction code /LOGWIN/TSF_TO_EXT_M.

You can either schedule these reports as a background job or execute them manually. For more information, see the report documentation in the system.



Important Disclaimers and Legal Information

Coding SamplesAny software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP intentionally or by SAP's gross negligence.

Gender-Neutral LanguageAs far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.

Internet HyperlinksThe SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency (see: https://help.sap.com/viewer/disclaimer).

Application Help for Logging of SAP NetWeaver BW AccessImportant Disclaimers and Legal Information P U B L I C 31

https://help.sap.com/viewer/disclaimer

go.sap.com/registration/contact.html

© 2018 SAP SE or an SAP affiliate company. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice.Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.Please see https://www.sap.com/corporate/en/legal/copyright.html for additional trademark information and notices.

https://go.sap.com/registration/contact.html

https://go.sap.com/registration/contact.html

https://www.sap.com/corporate/en/legal/copyright.html

Documents

Application Help for Logging of SAP NetWeaver BW Access