## 12.3.2.2  Read-Access Logging
## Prerequisites
Before you can use the delivered RAL configurations, the following prerequisites must be met:
- The RAL configurations have been activated.
- RAL is enabled in each system client.
## Description
Read-access to personal data is partially based on legislation, and it is subject to logging functionality. The Read Access Logging (RAL) component can be used to monitor, and log read-access to data and provide information, such as which business users accessed personal data and when they did so. In RAL, you can specify which read-access information is to be logged and under which conditions.
## Read-Access Logging for Behavioral Insights CDS Views Created for SAP Analytics Cloud
You can display the configurations in the system by performing the following steps:
1. In the SRALMANAGER transaction, on the Administration tab page, choose Configuration .
2. Choose ANALYTICS channel.
3. Choose Search . The system displays the available configurations for the selected BW Analytics channel.
4. Verify that the configuration listed is active.
5. Choose Display Configuration to display the detailed information about the configuration. Related recordings can also be displayed for specific channels.
##  Note
Note: You can also ensure that the BW Analytics configuration is available and is active using the SRALMANAGER transaction, by performing the steps detailed above.
In Behavioral Insights, the C\_BHVRLINSGTSCUSTEVTHISTQ, C\_BHVRLINSGTSPRDTNHISTQ and C\_BHVRLINSGTSPRDTNRSLTRSNQ CDS views are enabled for read-access logging. Customers can configure
the fields that are to be logged. The customers can configure the fields that are to be logged by creating the metadata extensions for these CDS views.
In read-access logging, you can configure which read-access information is to be logged and under which conditions. SAP delivers sample configurations for applications.
## Read-Access Logging for Fields Created Using the OData Gateway Service
You can configure read-access logging for the fields created using the OData Gateway Service to the Explore At-Risk Customers application using the SAP OData Gateway channel.
The UI\_ATRISKCUSTOMER\_ANA is the OData service for Behavioral Insights that logs data to protect and restrict access to sensitive business partner data.
You can configure any of the fields that are part of the entity types of the OData service for read-access logging. The following fields that are accessed by the Explore At-Risk application can be configured for read-access logging:
- Customer ID
- Customer Name
- Customer Status
- Customer Type
- Account ID
- Account Name
- Account Type
- Subaccount ID
- Risk Score
- Risk Score Range
- Risk Score Trend
- Debt
- Debt Range
•
Credit
- Actual Amount
- Scenario
- Event Name
- Event Category
- Event Start Date
- Event Value
- Period Key
##  Note
The fields in the Explore At-Risk application belong to different entities and the customer can configure the fields in all entities for read-access logging.
For more information about the standard roles that can be assigned to the user based on the required privileges, see the User Administration and Authentication section in the Security Guide for SAP S/4HANA.