orkungedik/SAP-basis-dataset huggingface dataset:
## 6.3.1.25  Manage Security Audit Log (Deprecated)
With this app, you can manage Security Audit Log related parameters.
## Key Features
You can use this app to:
- Each parameter can be active or inactive, so that changing the parameter value is possible without having the change immediately active
- Maintain parameter DELETE :
- Maintain the default audit log retention time in days. After the number of days the Security Audit Log Events will be removed from database to reduce the consumption of the SAP HANA DB storage. The default retention period is 45 days. Confirm the default by activating the parameter DELETE , or define a custom retention period.
Mark the parameter you want to change and switch to Edit mode. Select the option for Parameter Status (active or inactive) and for Parameter Value (Keep, Replace, or Clear Value) and save your settings.
## Access Information
For information on what business role and business catalog need to be assigned to your user to access the app, see the overview table in the chapter Applications for General Functions for Key Users.
## Supported Device Types
- Desktop
- Tablet
- Smartphone
## Component for Customer Incidents
If you need support or experience issues, please report an incident under component BC-SEC-SAL .
## 6.3.1.26  Business Event Logging
Business Event Logging enables you to log business events that are raised by activities of SAP S/4HANA applications or business users. Business events are messages that are sent to notify a consumer that an object has changed.
The events triggered during the execution of business activities can be:
- Business events for remote consumption: C2-released events (external)
- Business events for local consumption: C1-released events (internal)
For example, you can find events such as created , changed , and deleted for Sales Order. The RAP-based events are listed in the SAP Business Accelerator Hub.
You can activate Business Event Logging using configuration activities for each object, such as Sales Order, Outbound Delivery, and so on.
The business event logs give you insights into the way processes run in the local system and how objects change. You can get an overview of all the logged business events, the number of events triggered, the types of
events triggered, and information on changes to fields. Events of the same type occurring in the same session are grouped into activities.
This graphic displays the components of Business Event Logging:
<!-- image -->
## Benefits
With Business Event Logging, you can collect records of these business events, irrespective of whether the consumer has subscribed to the event, to get insights into the way business processes run in the local system. You can either store the default information or the complete business event data, depending on your configuration settings.
Essential properties of an event are stored by default. These properties are:
- Objects
- Object components
- Business object key
- Date of event
- Event type (corresponding to performed action)
- User who performed the action
- Relevant field changes
- Qualifiers (for generic events)
Field changes are also recorded as long as they are defined in the business events.
## 6.3.1.26.1  Business Event Logging Configuration
## Prerequisites
To configure business event logging, create a business role and assign the catalog SAP\_CA\_BC\_IC\_LND\_BEL\_BCO\_PC to the role. For instructions, refer to How to Create a New Business Role [page 2770]. You can also create a business role using the template SAP\_BR\_BPC\_EXPERT . For instructions, refer to How to Create a Business Role from a Template [page 2771] .
## Configure the Application
## Activate Business Event Logging
To activate logging for your objects:
1. Open the Custom Business Configurations app. You'll see a list of all business configurations that can be adapted.
2. Search for Activate Business Event Logging using the search bar.
3. Select the custom business configuration from the list and choose Edit .
4. To create a new entry, choose New Entries .
5. Enter the Object and select the Activate Logging checkbox to activate logging for the object.
##  Note
When you activate logging for an object, the keys and metadata such as event type, performed by, performed at, and other details of the object are logged and displayed in the business event logging apps. When you enable logging for all business event data, all changes made to the object is logged by the system. The fields captured by the system depend on how the event has been defined. For more information on the fields that get logged, refer to the SAP Business Accelerator Hub.
6. Choose Save .
For documentation about this item, refer to Show Documentation .
## 6.3.1.26.2  Business Event Logging Applications
With these apps, you can view business event logs and business events by object instances in your local system.
## Key Features
Business Event Logging contains these features:
- Displaying Business Event Logs
- Displaying Business Events by Objects
- Display Changes to Objects
## Components
All users can use the following applications in the ABAP environment for Business Event Logging:
- Display Business Event Logs app to view all the events logged in the SAP S/4HANA system.
- Display Business Events by Objects app to view all the sequences of business events in the context of the instances of object components.
- Display Changes to Objects app to view all changes for an Object.
## Prerequisites
To access applications, create a business role and assign business catalog SAP\_CA\_BC\_BEL\_PC to the role. For instructions, refer here.
To create a business role using a template, select the SAP\_BR\_BUSINESS\_PROCESS\_SPEC template. For instructions, refer here.
## 6.3.1.26.2.1  Display Business Event Logs
App ID: F6021
With this app, you can display logged business events. The events can be filtered by business event type for each object.
## Key Features
You can use this app to:
- Get an overview of logged business events
- View details of logged business events
- Go to business event sequence for an instance
## Supported Device Types
- Desktop
- Tablet
- Smartphone
## 6.3.1.26.2.2  Display Business Events by Objects
App ID: F6035
With this app, you can display object instances with their events grouped by activities. You can filter objects by processing variants. The detailed view provides information about the sequences of activities for instances of object components.
## Key Features
You can use this app to view:
- Instances of object components containing business events
- Sequence of business events logged for an instance of object component
- Processing variants, number of events for each instance of object component, and the processing cycle time
## Supported Device Types
- Desktop
- Tablet
- Smartphone
## 6.3.1.26.2.3  Display Changes to Objects
## App ID: F8211
With this app, you can view the recorded field changes for an object.
## Key Features
You can use this app to view:
- The field changes that are recorded for an object
- Old and new values for a changed field
## Supported Device Types
- Desktop
- Tablet
- Smartphone
## 6.3.1.26.3  Monitoring for Business Event Logging
You can monitor the problems that occur in business event logging using:
- Message Monitoring: You can use Message Monitoring Overview app to view runtime errors, to monitor processing of events, and to view missing events.
- Application Log: You can use Application Log to view additional information such as database errors, deletions, and other information related to business event logs.
## 6.3.1.26.3.1  Message Monitoring
You monitor the problems that occur in business event logging by using Application Interface Framework (AIF) . You can check the error status to identify failures. If there are failures in the queue, the business events aren't logged. However, the events aren't lost.
## Prerequisites
To access Message Monitoring, create a business role and assign the role to a catalog. For more information about catalogs and other settings, refer to Message Monitoring [page 2812]. Use the BEL\_IBD\_QUEUE\_MONITOR recipient to view Business Event Logging messages.
## Message Monitoring
1. Log on to SAP Fiori launchpad.
2. Open the Message Monitoring Overview app. For more information, refer to Message Monitoring Overview.
3. Select From (Date/Time) and To (Date/Time) values to limit the time range for the monitoring records.
##  Note
The default time range is "last 2 weeks". If you want a custom time range, you can also select the values in the From and To fields.
4. Choose Go to view the messages in this time range.
5. Select the following cards to monitor the processing of business events for the business event log:
- Namespace: /BEL
- Interface:
- BEL\_IBD
- BEL\_LG\_MGR
If you want to view only the error or success messages, choose Error or Success .
6. On the Message Monitoring screen, in the Log Messages column, you can see all business event logging messages for your selected time range. All types of messages, such as success, error, warning, canceled, and in process are included.
7. You can filter by Status .
8. Choose Message Details to see all the message logs.
If a queue fails, the user can restart the queue manually with the AIF user interface. If errors occur during restart, create an incident under component CA-GTF-BEL .
## 6.3.1.26.3.2  Application Log
You can use the Application Logs app to display application logs for Business Event Logging. If you need to see at a glance errors or information that ocured during Business Event Logging execution, this apps gives you a structured overview. To go to the Application Logs app, select the corresponding icon in the Log on the initial screen of the Application Jobs app. For more information, see Application Logs [page 1417]. To display the logs specific to Business Event Logging, filter based on the BEL\_LOG category.
| Log Object   | Log Subobject   | Description                                                                  |
|--------------|-----------------|------------------------------------------------------------------------------|
| BEL_LOG      | BUFFER          | Displays information about metadata buffer updates.                          |
| BEL_LOG      | DELETION        | Displays when and what business event log entries have been deleted.         |
| BEL_LOG      | ERROR           | Displays information about errors oc- curring during business event logging. |
## 6.3.1.26.4  CDS Views for Business Event Logging
## 6.3.1.26.4.4  Business Event Data
| CDS ViewName             | C_BuEvLgEvtFullPayloadJSONDEX                                                 |
|--------------------------|-------------------------------------------------------------------------------|
| Analytical Data Category | @Analytics.dataCategory: #FACT                                                |
| Represented Objects      | This view represents the following object: • BusEvtLogEvent (TechnicalObject) |
## Purpose
This CDS view provides full business event data (payload) in JSON format.
This CDS view provides the data to answer the following business questions:
- What is the full business data contained in the event?
To help you decide which CDS view to use for your purposes, SAP has introduced the annotation ObjectModel.supportedCapabilities that indicates the most appropriate use cases for each CDS view. To find out what use cases are best supported by this CDS view, access the entry of the CDS view in the View Browser app and find the values for this annotation under the Annotation tab.
## Structure
## Important Fields
Important fields in this view include the following:
| Field Name                   | Description                                                                                                                                                             |
|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| SAPObjectType                | The object type, a business object, or a technical object cor- responding to the specified object component. For example: Outbound Delivery for Outbound Delivery Item. |
| BusEvtLogPayloadJSONString   | Event Payload details in JSON format.                                                                                                                                   |
| BusEvtLogLastChangedDateTime | Timestamp of when the event was changed.                                                                                                                                |
## 6.3.1.26.4.5  Business Event Data v2
| CDS ViewName             | C_BuEvLgEvtFullPyldJSONDEX_2   |
|--------------------------|--------------------------------|
| Analytical Data Category | Fact                           |
## Purpose
This CDS view provides full business event data (payload) in JSON format.
This CDS view provides the data to answer the following business questions:
- What is the full business data contained in the event?
To help you decide which CDS view to use for your purposes, SAP has introduced the annotation ObjectModel.supportedCapabilities that indicates the most appropriate use cases for each CDS view. To find out what use cases are best supported by this CDS view, access the entry of the CDS view in the View Browser app and find the values for this annotation under the Annotation tab. For more information, see Supported Capabilities for CDS Views.
## Structure
## Important Fields
Important fields in this view include the following:
| Field Name                   | Description                                                                                                                                                               |
|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| SAPObjectType                | The object type, a business object, or a technical object corresponding to the specified SAP object node type. For example: Outbound Delivery for Outbound Delivery Item. |
| BusEvtLogPayloadJSONString   | Event Payload details in JSON format                                                                                                                                      |
| BusEvtLogLastChangedDateTime | Timestamp of when the event was changed                                                                                                                                   |
## Data Extraction
## Data Extraction Type
- Full
- Delta (change data capture)
##  Note
Data conversion using the Cloud Data Integration (CDI) channel can be different from that of the other channels (ODATA, ABAP SQL Service, and so on). For example:
- The timestamps could appear in a different format
- The IDs might not contain leading zeros
There could be formatting changes for other data as well.
## Related Information
Virtual Data Model and CDS Views in SAP S/4HANA Cloud Public Edition
## 6.3.1.26.4.6  Business Event Activity
| CDS ViewName             | C_BUSEVTLOGACTIVITYDEX   |
|--------------------------|--------------------------|
| Analytical Data Category | Fact                     |
## Purpose
This CDS view retrieves activities.
This CDS view provides the data to answer the following business questions:
- What are the logged activities?
To help you decide which CDS view to use for your purposes, SAP has introduced the annotation ObjectModel.supportedCapabilities that indicates the most appropriate use cases for each CDS view. To find out what use cases are best supported by this CDS view, access the entry of the CDS view in the View Browser app and find the values for this annotation under the Annotation tab. For more information, see Supported Capabilities for CDS Views.
## Structure
## Important Fields
Important fields in this view include the following:
| Field Name                          | Description                                                  |
|-------------------------------------|--------------------------------------------------------------|
| BusEvtLogBusinessActivity           | Activity ID                                                  |
| SAPObjectType                       | RAP SOT: SAP Object Type                                     |
| SAPObjectNodeType                   | RAP SOT: SAP Object Node Type                                |
| EventOperation                      | Business Event Operation                                     |
| SAPBusinessObjectNodeKey1 (1-8)     | Object Key Part (1-8)                                        |
| CreatedByUser                       | Users WhoExecuted the Action                                 |
| BusEvtLogCreationDateTime           | Action Execution Time Stamp                                  |
| BusinessEventLogLogicalSystem       | Logical system                                               |
| BusEvtLogTransactionID              | Identifies the session in which a business event was created |
| IsTechnicalUser                     | Is a Technical User                                          |
| BusEvtLogUserInteractionType        | Application Type                                             |
| BusEvtLgUsrIntactnTypeValue         | Application ID                                               |
| SAPBusinessObjectNodeKey1Name (1-8) | Key Names                                                    |
## Data Extraction
This CDS view is enabled for data extraction in full mode as well as in delta mode. Deltas are determined automatically by change data capture.
## Related Information
Virtual Data Model and CDS Views in SAP S/4HANA Cloud Public Edition
## 6.3.2  Communication Operations
## Communication Management [page 2965]
Learn more about the basic principles of communication management when integrating your system or solution with other systems to enable data exchange in your ABAP environment.
## Integration in BTP Apps via SAP Destination Service [page 2969]
In this topic you learn how to configure destinations in the SAP Destination service that shall be used by applications to consume services provided by the ABAP environment, and how to maintain corresponding communication arrangements in the ABAP environment. For instance, how to configure a destination that is used by an SAP Fiori application from the HTML5 repository that accesses an OData service of the ABAP environment.
## Overview of Communication Scenarios Managed by SAP [page 2983]
Find a quick overview of all the communication scenarios in the ABAP environment.
## Integration Scenarios [page 2984]
You can integrate the ABAP environment with the following services.
## 6.3.2.1 Communication Management
Learn more about the basic principles of communication management when integrating your system or solution with other systems to enable data exchange in your ABAP environment.
<!-- image -->
## 6.3.2.1.1 Communication Scenario
A communication scenario, which is created in the development system using ABAP Development Tools and transported to other systems, is a design time description of how two communication partners communicate with each other. It consists of inbound and/or outbound services as well as supported authentication methods.
It provides technical information, such as the used inbound and outbound services and their service type, for example OData or SOAP, and the number of allowed communication arrangement instances. If the scenario exposes inbound services, it specifies the authorizations that are required to run the services.
The following types of communication scenarios are available:
- Managed by SAP , where SAP provides a ready-to-use communication scenario and you create and maintain a communication arrangement.
- Managed by the customer , where you develop a communication scenario and create and maintain a communication arrangement.
## Related Information
Display Communication Scenarios [page 2711] Overview of Communication Scenarios Managed by SAP Outbound Communication
## 6.3.2.1.2 Communication System
A communication system is a specification of a system that represents a communication partner and the technical information required for the communication, such as the host name, port, users for inbound or outbound communication, certificates, etc.
If the communication system represents an on-premise system that is protected by a firewall, the system can be connected by assigning a cloud connector.
Instead of maintaining the credentials for outbound communication in the communication system itself, the communication system can also refer to a destination from the destination service. This can be a destination on subaccount level, or a destination from a destination service instance.
An administrator user in the ABAP environment has to create the communication system in the Communication Systems [page 2714] app in SAP Fiori launchpad. Note that the communication system is not transported between ABAP systems but created locally. The communication partner can vary for each system.
## 6.3.2.1.3 Communication User
A communication user is a specific type of technical user that is assigned to a communication system. The user can be assigned a password or X.509 certificate.
A communication user is added as a user for inbound communication to communication systems.
An administrator user in the ABAP environment creates the communication user in the Maintain Communication Users [page 2708] app in SAP Fiori launchpad. Note that the communication user is not transported between systems but created locally. The technical users and their credentials can vary for each system.
## 6.3.2.1.4 Communication Arrangement
A communication arrangement is a runtime description of a specific communication scenario. It describes which communication partners communicate with each other in the scenario, and how they communicate.
To describe this runtime behavior, you have to create an arrangement for a scenario, assign the communication system and communication users, and select the authentication method that shall be used.
If the communication scenario exposes inbound services, the communication user is granted the authorizations that have been specified for the communication scenario.
An administrator user in the ABAP environment creates the communication arrangement in the Communication Arrangements [page 2711] app in SAP Fiori launchpad. Note that it is not transported between systems but created locally. For certain SAP-managed scenarios that integrate an SAP BTP service, you can also create a communication arrangement from a service key of the service instance that you would like to connect.
For inbound-only scenarios, you can create a communication arrangement by creating a corresponding service key for the ABAP environment service instance.
## Related Information
Maintain a Communication Arrangement for Inbound Communication
## 6.3.2.1.5 Destination Service
Using the SAP destination service, you can retrieve and store technical information about the target resource (destination) that you want to connect with your application to a remote service or a system.
The destination service allows you to read and manage the address of a remote service and the user authentication information for the connection on subaccount and service instance level.
<!-- image -->
## Related Information
Destination Service Create a Destination [page 1104]
## 6.3.2.1.6 Destination
A destination is stored in the SAP destinations service and contains the connection details for the communication partner.
You can use a destination to:
- Connect your application to the Internet (via HTTP, RFC, or WebSocket RFC) or to an on-premise system (via HTTP or RFC)
- Send and retrieve emails by configuring a mail destination
##  Note
You can create a destination for a destination service on instance level or subaccount level.
A destination can be referenced in a communication system. To refer a destination from a destination service instance, a communication arrangement for SAP-managed scenario SAP\_COM\_0276 needs to be maintained to enable communication with the destination service instance. In this case, the destination name and the service instance name need to be maintained in the communication system.
## Related Information
Managing Destinations
## 6.3.2.1.7 Cloud Connector
The Cloud Connector serves as a link between cloud applications and on-premise systems.
In the Cloud Connector, the subaccount of the ABAP system is connected so that the Cloud Connector can be used within a communication system or destination in the subaccount.
It provides an easy setup with a clear configuration of the systems that are exposed to SAP BTP .
## Related Information
Cloud Connector
## 6.3.2.2.1 Inbound Communication via Communication User
## Configuring Basic Authentication [page 2972]
When using the basic authentication method, the client application provides the name of a communication user and its password to authenticate against the ABAP environment.
## Configuring Client Certificate Authentication [page 2974]
When using the client certificate authentication method, the client application uses a client certificate to authenticate against the ABAP environment as corresponding communication user.
## 6.3.2.2.2 Inbound Communication via Business User (Principal Propagation)
## Configuring SAML Assertion Authentication [page 2976]
When using the SAML assertion authentication method, the client application sends a signed SAML bearer assertion containing information about the business user to authenticate against the ABAP environment.
## Configure OAuth 2.0 SAML Bearer Assertion Grant [page 2979]
When using the OAuth 2.0 SAML Bearer Assertion Grant authentication method, the SAP Destination service sends a signed SAML Bearer Assertion containing information about the business user to the token endpoint of the ABAP environment to obtain an access token.
## 6.3.2.2.2.2  Configure OAuth 2.0 SAML Bearer Assertion Grant
When using the OAuth 2.0 SAML Bearer Assertion Grant authentication method, the SAP Destination service sends a signed SAML Bearer Assertion containing information about the business user to the token endpoint of the ABAP environment to obtain an access token.
## Context
You can provide your own certificate to sign the SAML assertion or use the standard subaccount-wide signing certificate. The ABAP environment needs to trust the issuer of the SAML Bearer Assertion.
To authenticate the OAuth client as communication user at the token endpoint, a client secret (password of the communication user) or client certificate can be used. In the latter case, the client certificate needs to be provided by the SAP Destination service and the ABAP environment needs to trust the signing root certificate authority (CA). The list of trusted root certificate authorities can be found in SAP Note 2801396 .
Finally, the client application uses the access token to authenticate as a business user at the ABAP environment to access the actual resource.
## Procedure
1. Maintain the key store for the signing certificate.
If the SAML assertion shall not be signed by the standard subaccount-wide signing key, then either upload a key store including the signing certificate, the private key, or generate one, for instance my-signingkeystore.p12 . For more information, see Use Destination Certificates.
2. Download the signing certificate.
If you use the standard subaccount-wide signing key, then download the signing certificate by choosing Download Trust in the SAP Destination service.
## 3. Maintain the key store for the client certificate.
If the OAuth client shall authenticate via client ID and client certificate, then either upload a key store including the client certificate, the private key, and the certificate chain to the SAP Destination service, or generate one, for instance my-keystore.p12 . For more information, see Use Destination Certificates.
## 4. Create a communication user.
Create a communication user using the Maintain Communication Users app in your ABAP environment system. In this context the communication user represents the OAuth client. Enter the following data:
| Field       | Input                                                                                                                                                                                                                                  |
|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| UserName    | Provide a user name, for example, MY_OAUTH_CLIENT .                                                                                                                                                                                    |
| Description | Provide a description.                                                                                                                                                                                                                 |
| Password    | If the OAuth client shall authenticate via client secret, pro- vide a password.                                                                                                                                                        |
| Certificate | If the OAuth client shall authenticate via client certificate, then upload the client certificate to the communication user. During runtime, the service is processed by the com- munication user that is assigned to the certificate. |
## 6. Create a communication arrangement.
Create a communication arrangement using the Communication Arrangements app in your ABAP environment system. Enter the following data:
| Field                                         | Input                                                                    |
|-----------------------------------------------|--------------------------------------------------------------------------|
| Scenario ID                                   | Select the scenario, for example, Z_MY_SCENARIO .                        |
| ArrangementName                               | Provide a name, for example, MY_ARRANGEMENT .                            |
| Communication System                          | Select the communication system, for example, MY_COMMUNICATION_PARTNER . |
| Inbound Communication - UserName              | Select the communication user, for example, MY_OAUTH_CLIENT .            |
| Inbound Communication - Authentication Method | OAuth 2.0                                                                |
## 7. Get technical data of the own communication system.
Open the own communication system in the Communication Systems app in your ABAP environment system. To open your own communication system, choose Own SAP Cloud System .
## Denote the following values:
- Host name, for example, 1a354373-d200-46f6-9d5cdaab9a65d9b6.abap.eu10.hana.ondemand.com
- OAuth 2.0 confidential client token service URL, for example, https://1a354373-d200-46f6-9d5cdaab9a65d9b6.abap.eu10.hana.ondemand.com/sap/bc/sec/oauth2/token
- SAML2 audience, for example, https://1a354373-d200-46f6-9d5c-daab9a65d9b6.abapweb.eu10.hana.ondemand.com
## 6.3.2.4 Integration Scenarios
You can integrate the ABAP environment with the following services.
Integrating Security Audit Logs [page 2985]
Integrating Business Role Change Documents [page 2989]
You can use this scenario to read the change documents of business roles.
Integrating Business User Change Documents [page 2990]
You can use this scenario to read the change documents of business users.
Integrating Content with SAP Build Work Zone, standard edition [page 2991]
Get an overview of the process for integrating content to the SAP Build Work Zone, standard edition. This process is composed of a content exposure flow and a content consumption flow.
Integrating SAP Analytics Cloud [page 2993]
SAP Analytics Cloud is used as analytics client consuming ABAP environment data exposed via ABAP environment analytical queries.
## Integrating SQL Services Using SAP Datasphere [page 2996]
You need the integration scenario SAP\_COM\_0532 if you want to create a replication flow in SAP Datasphere to subscribe to CDS view entities from an ABAP system and consume data from these views. With a communication arrangement based on SAP\_COM\_0532 combined with a communication arrangement for exposing the SQL service, you can consume data from custom CDS view entities that are exposed using the SQL service.
## Integrating SAP Document Management Service [page 2998]
You can integrate the SAP BTP ABAP environment with SAP Document Management Service to establish a communication scenario.
## Integrating SAP BTP ABAP environment and Local Printers [page 2999]
To set up the integration between SAP BTP ABAP environment and local printers, you can use two communication scenarios, SAP\_COM\_0466 and SAP\_COM\_0467 .
## Integrating External Scheduler [page 3009]
This inbound OData service enables external systems to schedule an application job based on an application job template.
## Integrating Factory Calendar [page 3030]
Learn how to integrate an ABAP Platform system with the factory calendar.
## Integrating Outbound Emails Using SMTP [page 3031]
Learn how to integrate outbound emails using the Simple Message Transfer Protocol (SMTP).
## Integrating SAP Enable Now Manager [page 3032]
The ABAP environment supports the extended content scenario of SAP Enable Now that allows you to add an additional source for help content to the SAP Companion plugin. You can edit the contextsensitive in-app help delivered by SAP and adapt it to your needs or include your own content.
## Integrating UI Theme Designer [page 3033]
To set up the integration between SAP BTP ABAP Environment and UI theme designer, you can use the communication scenario SAP\_COM\_0623 .
## Integrating SAP Build Process Automation [page 3037]
You can integrate your ABAP environment with SAP Build Process Automation.
## Integrating SAP Workflow Management [page 3047]
You can enable the communication between the ABAP environment and the workflow capability within the SAP Workflow Management service.
Integrating Business Event Logging [page 3053]
## 6.3.2.4.1 Integrating Security Audit Logs
Service name: RSAU\_LOG\_API
This service enables you to retrieve the security audit log data. You can use the audit log data to integrate them into your Security and Event Management solution (SIEM) to detect security relevant event situations.
This is an OData version 4 service. This version aims to improve processing time and resource consumption of clients and servers. This includes a lightweight JSON format that reduces the size of every response.
## Technical Details
A service group contains services belonging to the same business object model and so it shares similar environment conditions. This means the configuration and administration of a service group apply to all services in a service group, that is, routing, authorization, and so on, so you only have to do them once.
In the OData version 4 (V4) runtime implementation of the SAP Gateway Foundation, framework services originate from repositories.
| Service Group (incl. Name- space if Existent)   | Repository ID   | Service Name (incl. Name- space if Existent)   |   Version |
|-------------------------------------------------|-----------------|------------------------------------------------|-----------|
| RSAU_LOG_API                                    | SRVD_A2X        | RSAU_LOG_API_SERVICE                           |      0001 |
## Service Structure
## Service Header (optional)
The service header contains information about the service.
## Entities
The entities contain the business data of the service.
| Entity             | Description        | Necessity   | Link to Details                           |
|--------------------|--------------------|-------------|-------------------------------------------|
| Security Audit Log | Security Audit Log |             | Retrieving Security Audit Log [page 2885] |
## Service Response
The details included in the response vary according to the type of operation. For more information, see Operation for Security Audit Log Integration.
## Integration with SIEM Solution
Service name: RSAU\_LOG\_API
Communication scenario: SAP\_COM\_0750
This service enables you to retrieve the security audit log data. You can use the audit log data to integrate them into your Security and Event Management solution (SIEM) to detect security relevant event situations.
## Additional Information
##  Note
For more details about Communication Management, see Communication Management [page 2707].
## 6.3.2.4.1.1  Operations for Security Audit Log Integration Read
The Security Audit Log Integration - Read offers the following operations:
| Operation                                 | HTTP Method   | Sample URL                                                                                                                                                 |
|-------------------------------------------|---------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Retrieving Security Audit Log [page 2885] | GET           | Example getting the first 1000 audit log entries: GET <host>/sap/opu/ odata4/sap/rsau_log_api/srvd_a2x/ sap/rsau_log_api/0001/SecurityAudi- tLog?$top=1000 |
## 6.3.2.4.1.1.1  Retrieving Security Audit Log
With SecurityAuditLog you can retrieve the Security Audit Log by using the HTTP method GET .
## Request
You have to include the following properties in the URL of the request:
| Property   | Necessity   | Comment                                                                                      |
|------------|-------------|----------------------------------------------------------------------------------------------|
| eventID    | Optional    | Security Audit Log Event • String <= 3 characters Example: AU1, AU2                          |
| log_tstmp  | Optional    | Timestamp of the security audit log event • String($date-time) Example: 2017-04-13T15:51:04Z |
| Property   | Necessity   | Comment                                                           |
|------------|-------------|-------------------------------------------------------------------|
| slgmand    | Optional    | Client within the SAP System • String <=3 characters Example: 100 |
| sid        | Optional    | System ID • String <=3 characters • Example: YI3                  |
| counter    | Optional    | Message counter • integer($int16)                                 |
| slgtc      | Optional    | Transaction Code • String <= 20 characters Example: VA01          |
| slgrepna   | Optional    | ProgramName • String <= 40 characters Example: SAPMSSY8           |
## Response
The operation returns the Security Audit Log.
## Examples
## Get events within a specific timeframe:
GET &lt;host&gt;/sap/opu/odata4/sap/rsau\_log\_api/srvd\_a2x/sap/rsau\_log\_api/0001/
```
SecurityAuditLog? $filter=(log_tstmp%20ge%202021-05-08T10%3A25%3A09Z%20and%20log_tstmp%20le%20202105-09T10%3A25%3A09Z)
```
## Response
```
{ "eventID": "AU1", "log_tstmp": "2021-05-08T10:26:22.740611Z", "slgmand": "100", "sid": "ABC", "counter": 0, "terminal_name": "", "user_fullname": "Example Administrator", "slgtc": "S000", "slgrepna": "RSBTCRTE",
```
```
"rsau_text": "Logon successful (type=B, method=A)", "UserDescription": "Example Administrator" }, { "eventID": "AU1", "log_tstmp": "2021-05-08T10:28:22.924215Z", "slgmand": "100", "sid": "ABC", "counter": 0, "terminal_name": "", "user_fullname": "Example Administrator", "slgtc": "S000", "slgrepna": "RSBTCRTE", "rsau_text": "Logon successful (type=B, method=A)", "UserDescription": "Example Administrator" },
```
## 6.3.2.4.2 Integrating Business Role Change Documents
You can use this scenario to read the change documents of business roles.
## Context
This scenario allows you to read the change documents of business roles. We recommend that you limit the number of change documents according to the Changed On and the Business Role ID fields to avoid a high volume of data.
## Procedure
1. Check if a communication user already exists for this scenario. If not, create a communication user in the Maintain Communication Users app.
For more information, see the Related information section.
2. Check if a communication system already exists for this scenario. If not, create a communication system in the Communication Systems app.
3. Check if a communication arrangement already exists for this scenario. If not, create a communication arrangement for the Business Role Change Document Integration scenario (SAP\_COM\_0366) in the Communication Arrangements app.
For more information, see the Related information section.
## Related Information
How to Create a Communication Arrangement [page 2712]
## 6.3.2.4.3 Integrating Business User Change Documents
You can use this scenario to read the change documents of business users.
## Context
This scenario allows you to read the change documents of business users. We recommend that you limit the number of change documents according to the Changed On and the Business User ID fields to avoid a high volume of data.
## Procedure
1. Check if a communication user already exists for this scenario. If not, create a communication user in the Maintain Communication Users app.
For more information, see the Related information section.
2. Check if a communication system already exists for this scenario. If not, create a communication system in the Communication Systems app.
2. For more information, see the Related information section.
3. Check if a communication arrangement already exists for this scenario. If not, create a communication arrangement for the Business User Change Document Integration scenario (SAP\_COM\_0327) in the Communication Arrangements app.
For more information, see the Related information section.
## Related Information
How to Create a Communication Arrangement [page 2712] How to Create Communication Users [page 2710]
## 6.3.2.4.4 Integrating Content with SAP Build Work Zone, standard edition
Get an overview of the process for integrating content to the SAP Build Work Zone, standard edition. This process is composed of a content exposure flow and a content consumption flow.
## Exposing Content to SAP Build Work Zone, standard edition
Communication scenario SAP\_COM\_0647 - SAP Fiori Launchpad Content Exposure Integration is needed to supply the SAP Build Work Zone, standard edition with content from the connected system.
For a description of the steps required to set up the communication scenario SAP\_COM\_0647 , see Expose Launchpad Content to Launchpads on SAP BTP.
## Consuming Content in SAP Build Work Zone, standard edition
## Prerequisite
Launchpad content from the same system/client has been transferred to SAP Build Work Zone, standard edition using SAP\_COM\_0647 - SAP Fiori Launchpad Content Exposure Integration.
Content Consumption - Cloud Solutions
Content Consumption - Portal Service
Content Consumption - SAP Work Zone
## Related Information
Set SAP BTP ABAP Environment as a Content Provider for SAP Build Work Zone, standard edition
## 6.3.2.4.4.1  Enabling Notifications on SAP BTP ABAP environment in Launchpads Running on SAP BTP
Get an overview of the communication scenario SAP\_COM\_0683 - Enabling Notifications from SAP BTP ABAP environment in launchpads running on SAP BTP. The launchpads running on SAP BTP include the SAP Build Work Zone, standard edition and SAP Cloud Portal service.
## Prerequisites
- To receive notifications, every user must have the same email configured in the SAP BTP system user management section and in the Identity Provider (IdP) used by the launchpad running on SAP BTP, Cloud Foundry environment.
- If you want to deliver push notifications to mobile devices, the target user is identified using the email ID they provided. Currently, it is not possible to use other types of identifiers.
- You've generated and noted the following parameters from the launchpad running on SAP BTP:
- Host
- OAuth 2.0 Client ID
- Client Secret
- Authorization Endpoint
- Token Endpoint
## Procedure
1. Log on to the SAP Fiori launchpad in your SAP BTP ABAP environment system.
2. Open the Communication Arrangements app.
3. Create a communication arrangement. Choose scenario SAP\_COM\_0683 .
4. Enter a name for the communication arrangement.
5. Create a new communication system by choosing New next to the communication system.
6. Provide values for System ID and System Name and then choose Create .
7. In the Technical Data section, enter the value for Host obtained from the launchpad running on SAP BTP.
8. In the OAuth 2.0 Settings section, enter values for Auth. Endpoint and Token Endpoint obtained from the launchpad running on SAP BTP.
9. Create a new user for Outbound Communication by entering the following details:
- Authentication Method: OAuth 2.0
- Client Authentication: Basic
- OAuth 2.0 Client ID: Client ID obtained from the launchpad running on SAP BTP
- Client Secret: Client Secret obtained from the launchpad running on SAP BTP
10. Save the Communication System and Communication Arrangement.
## Related Information
Working with Notifications
## 6.3.2.4.5 Integrating SAP Analytics Cloud
SAP Analytics Cloud is used as analytics client consuming ABAP environment data exposed via ABAP environment analytical queries.
## Prerequisites
- You have the BI Admin role in the SAP Analytics Cloud system. For more information, see Requesting Roles.
- You have the Administrator role (role template ID SAP\_BR\_ADMINISTRATOR ). For more information, see Maintain Business Roles.
- Your end users' web browsers must be configured to:
- Allow pop-up windows from the SAP Analytics Cloud domain: [*.]sapbusinessobjects.cloud , if you'll be choosing the single sign-on (SSO) authentication method in step 2.
- Allow 3rd party cookies from the Tomcat server's domain. For example, in Internet Explorer 11, go to Internet Options Security Trusted Sites , add your domain name, then select Enable Protected Mode .
## Context
You can configure a live data connection in SAP Analytics Cloud and create an SAP Analytics Cloud model based on an ABAP environment analytical query to consume the result set in an SAP Analytics Cloud Story. The analytical query is delivered as CDS content and is exposed via the analytical engine and the InA protocol via the REST services under /sap/bw/ina/... to SAP Analytics Cloud.
SAP BTP destinations are created by the SAP Analytics Cloud app when you define an SAP Analytics Cloud connection of the type ABAP environment.
You set up the scenario using the following tasks:
1. Configure Identity Authentication [page 2994]
2. Create a Communication System [page 2994]
3. Create a Communication Arrangement [page 2995]
4. Configure Live Data Connection [page 2996]
## 6.3.2.4.5.1  Configure Identity Authentication
Configure your Identity Authentication tenant as the identity provider.
## Prerequisites
You have the System Owner role.
## Procedure
1. Log on to the SAP Analytics Cloud system via the default identity provider tenant.
The identity provider is the Identity Authentication tenant that you get with the ABAP environment tenant.
2. Go to System Administration Security and change the Authentication Method from SAP Cloud Identity (Default) to SAML Single Sign-On (SSO) , then follow the steps for SAML Single Sign-On (SSO) Configuration .
3. Under Step 2: Upload Identity Provider metadata , deselect Identity Provider will also be used... if this checkbox is visible.
4. Under Step 3 , set the SAML User Mapping to Custom SAML User Mapping . Under Security Users , the value in the Custom SAML User Mapping column must equal the User Data User Name of the corresponding business user in the ABAP environment.