orkungedik/SAP-basis-dataset huggingface dataset:
## 4.2.12.1.1.2  Creating a Business Configuration Maintenance Object in ADT
Find out how to create a business configuration maintenance object using the ABAP Development Tools (ADT).
## Procedure
1. In the Project Explorer , select the relevant package node.
2. Open the context menu and choose New&gt;Other ABAP Repository Object&gt;Business Configuration Management&gt;Business Configuration Maintenance Object&gt;Next to launch the creation wizard.
3. Enter a name and a description and choose Next .
## Related Information
Working with Business Configuration Maintenance Objects
## 4.2.12.1.2  Develop Common Capabilities
The guides in this section focus on specific development tasks common to a business configuration application. Whether or not you want to follow these guidelines depends on your initial situation and the desired result of your development.
##  Note
The Business Configuration Maintenance Object wizard [page 941] takes these concepts into account. You can therefore use the wizard to generate an executable example which illustrates the implementation of these concepts.
- Authorization Control [page 948]
- Transport Handling [page 949]
## 4.2.12.1.2.1  Authorization Control
## Context
Authorization control in RAP protects your business configuration object against unauthorized access to customizing data.
It's recommend to use the authorization S\_TABU\_NAM together with the CDS root entity name of the business object as table name to perform the read and modify operation. However, you can also check against the physical table names or use a different authorization object instead.
## Procedure
The advantage of using the CDS root entity name is that if the business object is extended by a new table you don't need to adjust the authorization check.
See also Provide Authorization on how to create the IAM app and add the authorization object.
## Example
The business configuration CDS root entity name is /ITAPC1/I\_Status .
The data control language (DCL) can be dfined as follows:
```
 Sample Code @MappingRole: true define role /ITAPC1/I_Status { grant select on /ITAPC1/I_Status where ( ) = ASPECT pfcg_auth ( 'S_TABU_NAM', ACTVT = '03', TABLE = '/ITAPC1/ I_STATUS' ); }
```
The global authorization check in the behavior implementation can be defined as follows:
```
 Sample Code METHOD GET_GLOBAL_AUTHORIZATIONS. AUTHORITY-CHECK OBJECT 'S_TABU_NAM' ID 'TABLE' FIELD '/ITAPC1/I_STATUS' ID 'ACTVT' FIELD '02'. DATA(is_authorized) = COND #( WHEN sy-subrc = 0 THEN if_abap_behv=>authallowed ELSE if_abap_behv=>auth-unauthorized ). result-%UPDATE      = is_authorized. result-%ACTION-Edit = is_authorized. ENDMETHOD.
```
The authorization instance of S\_TABU\_NAM in the IAM app can be defined as follows. Whether or not the user has write or read authorization is finally defined in the General Role Details section of the Business Role the Business Catalog with this IAM app is assigned to.
```
 Sample Code ACTVT = Change, Display TABLE = /ITAPC1/I_STATUS
```
## 4.2.12.1.2.2  Transport Handling
## Context
Business configuration content is usually not directly maintained in a productive system, but created in a development system, and then transported to the test system and productive system. As the developer of a business configuration app, you need to ensure that changes to the business configuration content is recorded onto a transport request of type Customizing and the user has the option to select the correct transport request.
## Recording Changes on Transport Request
With the factory class MBC\_CP\_API you can instantiate a transport API to validate and record entity keys of a RAP business object on a transport request.
```
 Sample Code DATA(api) = mbc_cp_api=>rap_table_cts( table_entity_relations = VALUE #( ( entity = '/ITAPC1/I_Status'table = '/ITAPC1/STATUS' ) ( entity = '/ITAPC1/I_StatusText' table = '/ITAPC1/STATUST' ) ) ).
```
In the behavior implementation define an Additional Save Implementation in the header directly after the keyword managed. In the save\_modified method you can record the changes on the transport request with the method record\_changes of this API. Check the ABAP Doc of record\_changes for more information and example implementation.
For each entity of the RAP BO define a Validation on save for create, update and delete. In the validation implementation call the method validate\_changes of the API. Check the ABAP Doc of validate\_changes for more information and example implementation.
## Transport Selection
The before mentioned API methods require a transport request to be passed. For the transport selection define an action with Abstract CDS Entity D\_SelectCustomizingTransptReqP as the parameter. This CDS Entity returns all modifiable transport request of type Customizing where the user either owns the request or owns at least one open task.
Save the result of the action in a virtual field of the draft entity. When recording or validating the changes the previously selected transport request can then be retrieved from the draft entity.
##  Note
When developing custom business configuration objects, you can decide if you want to provide a transport selection screen for change recording. If you are using this transport pattern, we recommend autofilling the transport request based on the software component of the business configuration object.
## 4.2.12.1.3  Develop UI-Specifics
The UI layout of a Business Configuration Maintenance Object in the Custom Business Configurations app depends on the following layers.
- CDS Annotations
You can use CDS annotations to define, among other things, the field labels and description, value helps, facets and actions.
- Fiori Elements Settings in the Business Configuration Maintenance Object definition
You can configure the list report, object pages and table settings of the Fiori Elements List Report Floor Plan rendered by the Custom Business Configurations app.
- Generic UI functions of the Custom Business Configurations App [page 2687].
Grouping of business configuration maintenance objects, intent navigation, display change logs and show documentation are generic UI functions of the Custom Business Configurations app.
## 4.2.12.1.3.1  Grouping
The standard variant of the Custom Business Configurations app shows you the list of business configuration maintenance objects.
If the list needs to be structured in a simple hierarchical manner, you have the option to group the business configuration maintenance objects semantically.
<!-- image -->
As the developer of the business configuration maintenance object, you specify a data element of the same software component as configuration group.
<!-- image -->
The name of the data element can then be used by the custom business configurations app user as the Group By element in the table settings.
By clicking on settings you can navigate to the View Settings window.
The description of the configuration group data element is shown as the group label. Other attributes of the data element are not relevant. If the configuration group of a business configuration maintenance object is not maintained, the object is assigned to the generic group Not Assigned .
The Custom Business Configurations app user can save and share the variant with grouping in the My Views Dialog.
## 4.2.12.1.3.2  Table Creation Mode
If a new entry is added to a table, the Custom Business Configurations navigates to the object page of the new entry by default. This can be changed so that a navigation is not triggered .
This configuration is done with the Table Creation Mode attribute in the Table Settings section of the definition.
In the following example the business object consists of five entities:
```
[XI1] /ITAPC 1/UI_STATUSCLASS X 1 define service IITAPCI/UI_STATUSCLASS 2 expose JITAPCI/C_StatusClass_ as StatusClassAll; 3 expose IITAPC1/C_StatusClass as StatusClass; 4 expose IITAPCI/C_StatusClassText as StatusClassText; 5 expose IITAPCI/C_StatusCodeText as StatusCodeText; 6 expose IITAPCI/C_StatusCode as StatusCode; 7 1
```
For entity StatusClass the app shall navigate to the object page when creating a new table entry because the entity has many attributes which the user must maintain. Therefore Table Creation Mode is set to New Page .
The app shall not navigate to the object page when creating a new table entry for the entity StatusClassText because the user only needs to specify language key and text. Therefore Table Creation Mode is set to Creation Row and Table Type to Grid Table .
<!-- image -->
## 4.2.13  Integration and Connectivity
The ABAP environment enables you to connect to other systems using different protocols. It is possible to consume services from other systems and provide services for consumption in other systems.
## Integration and Connectivity Development Guide [page 954]
Get an overview of the ABAP integration and connectivity development guide.
## SAP-Provided APIs [page 957]
## Integrating On-Premise Systems [page 1099]
Set up the Cloud Connector to enable communication from the ABAP environment to your on-premise systems using Remote Function Calls (RFC) and HTTP calls.
## Managing the SAP BTP ABAP environment Service Instance [page 1103]
## Integrating the ABAP Environment with SAP S/4HANA Cloud [page 1107]
You can integrate the SAP BTP ABAP environment with an SAP S/4HANA Cloud Public Edition system. This allows ABAP developers to implement outbound service calls from the ABAP environment to the SAP S/4HANA Cloud Public Edition system.
## Developing Metrics for Health Monitoring [page 1108]
Learn how you can add your own metrics to Health Monitoring in SAP Cloud ALM or SAP Focused Run.
Accessing ABAP-Managed Data Using SQL Services for Data Integration Scenarios [page 1117]
As a developer in the ABAP environment, you can expose CDS view entities in an ABAP system for external consumption using SQL services.
Integrating Enterprise Event Enablement [page 1119]
## 4.2.13.2  SAP-Provided APIs
## Integrating Business Users from an External Identity Management System [page 958]
You can use this communication scenario for the business user.
## Integrating Business Role Change Documents [page 998]
You can use this scenario to read the change documents of business roles.
## Integrating Business User Change Documents [page 1001]
You can use this scenario to read the change documents of business users.
## Integrating Business Role Data (Read) [page 1003]
You can use this communication scenario to read business role data.
## Integrating Business User Logon Details (Read) [page 1011]
You can use this communication scenario to read business user logon details.
## Integrating Support User Data (Read) [page 1016]
You can use this communication scenario to read support user data.
## Integrating Communication Arrangement Data (Read) [page 1019]
You can use this communication scenario to read communication arrangement data.
## Integrating Communication Management Data (Read and Write) [page 1026]
You can use this communication scenario to read and write communication arrangement, communication system and communication user data.
## Integrating Communication System Data (Read) [page 1034]
You can use this communication scenario to read communication system data.
## Integrating Communication User Data (Read) [page 1040]
You can use this communication scenario to read communication user data.
## Integrating Content Security Policy Data (Read) [page 1045]
You can use this communication scenario to read Content Security Policy (CSP) data.
## Integrating Protection Allowlist Data (Read) [page 1049]
You can use this communication scenario to read protection allowlist data.
Integrating Certificate Data (Read) [page 1055]
## Integrating Cross-domain Identity Management [page 1066]
You can use this communication scenario to maintain data via SCIM.
## Manage Git Repository [page 1071]
The Manage Git Repository API allows you to manage software components (Git repositories) on an SAP BTP ABAP Environment system.
## 4.2.13.2.1  Integrating Business Users from an External Identity Management System
You can use this communication scenario for the business user.
The communication scenario SAP\_COM\_0093 allows you to use and provision business users from an external data source, for example an identity management system, in SAP Integrated Business Planning.
The communication scenario gives you access to two SOAP services:
- MANAGEBUSINESSUSERIN lets you create business users in your system
- QUERYBUSINESSUSERIN lets you read existing business users from your external data source into your own identity management system.
- QueryBusinessUserMetadaIn lets you read metadata information for the service MANAGEBUSINESSUSERIN from an external data source such as an identity management system. The service provides the search parameter RoleCategory , which restricts the result set of the metadata information of the service. The response includes the metadata information based on the given criteria. If errors occur, the log contains information about the severity code, the message number, and message texts.
##  Note
This scenario processes personal data. For more information on how to handle data protection and privacy, see Data Protection and Privacy.
For more information, see the service documentation on the SAP Business Accelerator Hub and search for SAP IBP - Identity Management .
## Related Information
Inbound Service: Business User [page 959]
Inbound Service: Business User - Read [page 976]
Business User - Read Metadata [page 991]
## 4.2.13.2.1.3.2  CodeList
## Nodes and Fields
##  Note
In the following table, field attributes are marked in blue.
## CodeList
| Node or Field                                        | Description                                                                             | Cardinality   |
|------------------------------------------------------|-----------------------------------------------------------------------------------------|---------------|
| FieldName                                            | Nameof the field.                                                                       | 1..1          |
| FieldCodeList Cardinality: 0..un- bounded FieldValue | This node provides the available code lists for SAP specific co- des. For example coun- | 1..1          |
| Node or Field   |                  | Description                        | Cardinality   |
|-----------------|------------------|------------------------------------|---------------|
|                 | FieldDescription | try/region code, aca- demic title. | 0..unbounded  |
<!-- image -->
To display more information about the service node on the SAP Business Accelerator Hub, select the operation.
## 4.2.13.2.1.3.3  Log
## Nodes and Fields
##  Note
In the following table, field attributes are marked in blue.
## Log
| Node or Field                          | Description                                                                                                                         | Cardinality   |
|----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|---------------|
| BusinessDocumentProcessingResultCode   |                                                                                                                                     | 0..1          |
| MaximumLogItemSeverityCode             | If several messages are stored for a business user, the most severe level is shown from the maximum of all received severity codes. | 0..1          |
| Item TypeID                            | Message number.                                                                                                                     | 0..1          |
| Cardinality: 0..unbounded CategoryCode | Not in use.                                                                                                                         | 0..1          |
| SeverityCode                           | Severity code definition: • 1 - Information                                                                                         | 0..1          |
| Note                                   | Contains the message texts.                                                                                                         | 1..1          |
|                                        | WebURI Not in use.                                                                                                                  | 0..1          |
<!-- image -->
To display more information about the service node on the SAP Business Accelerator Hub, select the operation.
## 4.2.13.2.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] How to Create Communication Users [page 2710]
## 4.2.13.2.2.1.1  Operation for Business Role Changes - Read
The Business Role Changes - Read inbound service offers this operation:
| Operation                  | HTTP Method   | Sample URL                                                                |
|----------------------------|---------------|---------------------------------------------------------------------------|
| BusinessRoleChangeDocument | GET           | GET<host>/sap/opu/odata/sap/ APS_IAM_API_BROLE_CDOC/Busi- nessRoleChanges |
## 4.2.13.2.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.
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]
## 4.2.13.2.3.1.1  Operation for Business User Changes - Read
The Business User Changes - Read inbound service offers the following operation:
| Operation                  | HTTP Method   | Sample URL                                                                |
|----------------------------|---------------|---------------------------------------------------------------------------|
| BusinessUserChangeDocument | GET           | GET<host>/sap/opu/odata/sap/ APS_IAM_API_BUSER_CDOC/Busines- sUserChanges |
## 4.2.13.2.4  Integrating Business Role Data (Read)
You can use this communication scenario to read business role data.
## Context
The communication scenario SAP\_COM\_0A04 allows you to read business role data, such as business role ID or description, read business roles, read assigned business users, launchpad spaces and business catalogs, or filter for specific combinations.
## Authentication Methods
This communication scenario can be configured with the following inbound authentication methods:
- Basic Authentication (user and password)
- X.509 (certificates)
## 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 Read Integration scenario (SAP\_COM\_0A04) in the Communication Arrangements app.
For more information, see the Related information section.
## Related Information
Communication Management [page 2707]
## 4.2.13.2.4.1  Business Role - Read Integration
This service enables you to to do the following:
- Read business roles
- Read assigned business users, launchpad spaces and business catalogs
- Filter for specific combinations
This service is published on the SAP Business Accelerator Hub. For more information about APIs, see the Related Information section.
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
| Service Group (incl. Name- space if It Exists)   | Repository   | Service Name (incl. Name- space if It Exists)   |   Version |
|--------------------------------------------------|--------------|-------------------------------------------------|-----------|
| aps_iam_api_brole_read                           | srvd_a2x     | BusinessRole                                    |      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                                  |
|---------------|--------------------------|-------------|--------------------------------------------------|
| BusinessRoles | Contains business roles. | Mandatory   | Please refer to the Related Information section. |
## Additional Information
##  Note
For more information about Communication Management, see the Related Information section.
## Related Information
## APIs on SAP Business Accelerator Hub
Communication Management [page 2707]
## 4.2.13.2.4.1.1.1  Business Role - Business User Entity
Technical name: BusinessRoleBusinessUsers
## Properties
| Property       | Description      | Necessity       |
|----------------|------------------|-----------------|
| BusinessRoleID | Business role ID | Mandatory (Key) |
| UserID         | Business user ID | Mandatory (Key) |
To display more information about the properties on the SAP Business Accelerator Hub, choose Schema View .
## 4.2.13.2.4.1.1.2  Business Role - Launchpad Space Entity
Technical name: BusinessRoleLaunchpadSpaces
## Properties
| Property       | Description      | Necessity       |
|----------------|------------------|-----------------|
| BusinessRoleID | Business role ID | Mandatory (Key) |
| SpaceID        | Space ID         | Mandatory (Key) |
To display more information about the properties on the SAP Business Accelerator Hub, choose Schema View .
## 4.2.13.2.4.1.1.3  Business Role - Business Catalog Entity
Technical name: BusinessRoleBusinessCatalogs
## Properties
| Property          | Description         | Necessity       |
|-------------------|---------------------|-----------------|
| BusinessRoleID    | Business role ID    | Mandatory (Key) |
| BusinessCatalogID | Business catalog ID | Mandatory (Key) |
To display more information about the properties on the SAP Business Accelerator Hub, choose Schema View .
## 4.2.13.2.4.1.1.4  Business Role - Derived Business Role Entity
Technical name: BusinessRoleDerivedRoles
## Properties
| Property              | Description              | Necessity       |
|-----------------------|--------------------------|-----------------|
| BusinessRoleID        | Business role ID         | Mandatory (Key) |
| DerivedBusinessRoleID | Derived business role ID | Mandatory (Key) |
##  Note
To display more information about the properties on the SAP Business Accelerator Hub, choose Schema View .
## 4.2.13.2.4.1.1.5  Business Role - Restriction Entity
Technical name: BusinessRoleRestrictions
## Properties
| Property                      | Description                      | Necessity       |
|-------------------------------|----------------------------------|-----------------|
| BusinessRoleID                | Business role ID                 | Mandatory (Key) |
| RestrictionTypeAssignmentUUID | Restriction type assignment UUID | Mandatory (Key) |
| AccessCategory                | W: Write R: Read F: Value Help   | Optional        |
| RestrictionType               | Restriction type                 | Optional        |
To display more information about the properties on the SAP Business Accelerator Hub, choose Schema View .
## 4.2.13.2.4.1.1.6  Business Role - Restriction Field Entity
Technical name: BusinessRoleRestrictionFields
## Properties
| Property                      | Description                      | Necessity       |
|-------------------------------|----------------------------------|-----------------|
| BusinessRoleID                | Business role ID                 | Mandatory (Key) |
| RestrictionTypeAssignmentUUID | Restriction type assignment UUID | Mandatory (Key) |
| Property       | Description                                                                                                                                                     | Necessity       |
|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|
| FieldName      | Field name                                                                                                                                                      | Mandatory (Key) |
| MaintainStatus | <empty>: No maintenance status set. not_maint: Maintenance status set to Not Maintained . maint_derived: Maintenance Status set to Maintained in Derived Role . | Optional        |
| IsLeading      | Leading                                                                                                                                                         | Optional        |
To display more information about the properties on the SAP Business Accelerator Hub, choose Schema View .
## 4.2.13.2.4.1.1.7  Business Role - Restriction Value Entity
Technical name: BusinessRoleRestrictionValues
## Properties
| Property                       | Description                       | Necessity       |
|--------------------------------|-----------------------------------|-----------------|
| BusinessRoleID                 | Business role ID                  | Mandatory (Key) |
| RestrictionTypeAssignmentUUID  | Restriction type assignment UUID  | Mandatory (Key) |
| FieldName                      | Field name                        | Mandatory (Key) |
| RestrictionValueAssignmentUUID | Restriction value assignment UUID | Mandatory (Key) |
| LowValue                       | Low value                         | Optional        |
| HighValue                      | High value                        | Optional        |
To display more information about the properties on the SAP Business Accelerator Hub, choose Schema View .
## 4.2.13.2.5  Integrating Business User Logon Details (Read)
You can use this communication scenario to read business user logon details.
## Context
The communication scenario SAP\_COM\_0889 allows you to read business user logon details, such as user name, validity, assigned business roles, read business users, read assigned business catalogs, business roles and application jobs, or filter for specific combinations.
## Authentication Methods
This communication scenario can be configured with the following inbound authentication methods:
- Basic Authentication (user and password)
- X.509 (certificates)
## 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 User Logon Details Read Integration scenario (SAP\_COM\_0889) in the Communication Arrangements app.
For more information, see the Related information section.
## Related Information
Communication Management [page 2707]
## 4.2.13.2.5.1  Business User Logon Details - Read Integration
This service enables you to
- Read business users
- Read assigned business catalogs, business roles and application jobs
- Filter for specific combinations
This service is published on the SAP Business Accelerator Hub. For more information about APIs, see the Related Information section.
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
| Service Group (incl. Name- space if It Exists)   | Repository ID   | Service Name (incl. Name- space if It Exists)   |   Version |
|--------------------------------------------------|-----------------|-------------------------------------------------|-----------|
| aps_iam_api_buser_read                           | srvd_a2x        | BusinessUser                                    |      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                                              |
|---------------|-------------------------|-------------|--------------------------------------------------------------|
| BusinessUsers | Contains Business Users | Mandatory   | For more information, see the Related Information sec- tion. |
## Additional Information
##  Note
For more details about Communication Management, see Communication Management [page 2707].
## Related Information
Business User Entity [page 1013]
## 4.2.13.2.5.1.1  Business User Entity
Technical name:
## Properties
| Property                     | Description                        | Necessity       |
|------------------------------|------------------------------------|-----------------|
| UserID                       | User ID                            | Mandatory (Key) |
| UserName                     | User name                          | Optional        |
| Description                  | Description                        | Optional        |
| FirstName                    | First name                         | Optional        |
| LastName                     | Last name                          | Optional        |
| EMailAddress                 | Email address                      | Optional        |
| GlobalUserID                 | Global user ID                     | Optional        |
| BusinessUserGroup            | Business user group                | Optional        |
| PriceCategoryCode            | Price category code                | Optional        |
| PriceCategory                | Price category                     | Optional        |
| LockStatus                   | Lock status                        | Optional        |
| Validity                     | Validity                           | Optional        |
| IsLoggedOn                   | Is logged on                       | Optional        |
| NeverLoggedOn                | Never logged on                    | Optional        |
| ValidFromDate                | Valid From date                    | Optional        |
| ValidToDate                  | Valid To date                      | Optional        |
| LastLogonDateTime            | Date and time of last logon        | Optional        |
| LastChangedDateTime          | Date and time of last change       | Optional        |
| LastChangedByUserID          | Last Changed By <user ID>          | Optional        |
| LastChangedByUserName        | Last Changed By <user name>        | Optional        |
| LastChangedByUserDescription | Last Changed By <user description> | Optional        |
| LastChangedByEMailAddress    | Last Changed By <email address>    | Optional        |
| LastChangedByGlobalUserID    | Last Changed By <global user ID>   | Optional        |
BusinessUsers
##  Note
To display more information about the properties on the SAP Business Accelerator Hub, choose Schema View .
## Expandables
This entity is expandable with the following:
- Business Catalogs
- Business Roles
- Application Jobs
## Related Information
Business User - Business Catalog Entity [page 1014]
Business User - Business Role Entity [page 1015]
Business User - Application Job Entity [page 1015]
## 4.2.13.2.5.1.1.1  Business User - Business Catalog Entity
Technical name: BusinessUserBusinessCatalogs
## Properties
| Property          | Description         | Necessity       |
|-------------------|---------------------|-----------------|
| UserID            | User ID             | Mandatory (Key) |
| BusinessCatalogID | Business catalog ID | Mandatory (Key) |
<!-- image -->
To display more information about the properties on the SAP Business Accelerator Hub, choose Schema View .
## 4.2.13.2.5.1.1.2  Business User - Business Role Entity
Technical name: BusinessUserBusinessRoles
## Properties
| Property       | Description      | Necessity       |
|----------------|------------------|-----------------|
| UserID         | User ID          | Mandatory (Key) |
| BusinessRoleID | Business role ID | Mandatory (Key) |
##  Note
To display more information about the properties on the SAP Business Accelerator Hub, choose Schema View .
## 4.2.13.2.5.1.1.3  Business User - Application Job Entity
Technical name: BusinessUserApplicationJobs
## Properties
| Property       | Description     | Necessity       |
|----------------|-----------------|-----------------|
| UserID         | User ID         | Mandatory (Key) |
| ApplicationJob | Application job | Mandatory (Key) |
##  Note
To display more information about the properties on the SAP Business Accelerator Hub, choose Schema View .
## 4.2.13.2.6  Integrating Support User Data (Read)
You can use this communication scenario to read support user data.
## Context
The communication scenario SAP\_COM\_0347 allows you to read support user request logs.
## Authentication Methods
This communication scenario can be configured with the following inbound authentication methods:
- Basic Authentication (user and password)
- X.509 (certificates)
## 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 Support User Request Log Integration scenario (SAP\_COM\_0347) in the Communication Arrangements app.
For more information, see the Related information section.
## 4.2.13.2.6.1  Support User - Read Integration
This service enables you to to do the following:
- Read support users
- Read associated user information
This service is published on the SAP Business Accelerator Hub. For more information about APIs, see the Related Information section.
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
| Service Group (incl. Name- space if It Exists)   | Repository ID   | Service Name (incl. Name- space if It Exists)   |   Version |
|--------------------------------------------------|-----------------|-------------------------------------------------|-----------|
| api_iam_susr_read                                | srvd_a2x        | SupportUser                                     |      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                                  |
|--------------|-------------------------|-------------|--------------------------------------------------|
| SupportUsers | Contains support users. | Mandatory   | Please refer to the Related Information section. |
## Related Information
## APIs on SAP Business Accelerator Hub
Communication Management [page 2707]
## 4.2.13.2.6.1.1  Support User Entity
Technical name:
SupportUsers
## Properties
| Property                  | Description                                             | Necessity       |
|---------------------------|---------------------------------------------------------|-----------------|
| CAMSupportUserRequestUUID | Support user request UUID for SAP Cloud Access Manager. | Mandatory (Key) |
| Property                       | Description                                                           | Necessity   |
|--------------------------------|-----------------------------------------------------------------------|-------------|
| CAMSuppUserValdtyStartDateTime | Support user validity start datetime for SAP Cloud Access Manager.    | Optional    |
| CAMSupportUser                 | Support user for SAP Cloud Access Manager.                            | Optional    |
| CAMSupportAccessLevel          | Support access level for SAP Cloud Ac- cess Manager.                  | Optional    |
| CAMSupportAccessCategory       | Support access category for SAP Cloud Access Manager.                 | Optional    |
| CAMSupportAccessCategoryText   | Support access category text for SAP Cloud Access Manager.            | Optional    |
| CAMSuppAddedAuthorizationMode  | Support added authorization mode for SAP Cloud Access Manager.        | Optional    |
| CAMSuppAddedAuthznModeText     | Support added authorization mode text for SAP Cloud Access Manager.   | Optional    |
| CAMSuppAddedAuthorizationUser  | Support added authorization user for SAP Cloud Access Manager.        | Optional    |
| CAMSupportIncident             | Support incident for SAP Cloud Access Manager.                        | Optional    |
| CAMSupportIncidentSystem       | Support incident system for SAP Cloud Access Manager.                 | Optional    |
| CAMSupportIncidentSystemText   | Support incident system text for SAP Cloud Access Manager.            | Optional    |
| CAMSupportIncidentSystemNumber | Support incident system number for SAP Cloud Access Manager.          | Optional    |
| CAMSupportIncidentTicketNumber | Support incident ticket number for SAP Cloud Access Manager.          | Optional    |
| CAMSupportIncidentTicketYear   | Support incident ticket year for SAP Cloud Access Manager.            | Optional    |
| CAMSuppUserValdtyEndDateTime   | Support user validity end date and time for SAP Cloud Access Manager. | Optional    |
To display more information about the properties on the SAP Business Accelerator Hub, choose Schema View .
## Expandables
This entity is expandable with the following:
- SupportUser
## Related Information
Support User - User Entity [page 1019]
## 4.2.13.2.6.1.1.1  Support User - User Entity
Technical name: SupportUserUsers
## Properties
| Property        | Description                    | Necessity       |
|-----------------|--------------------------------|-----------------|
| UserID          | Contains the user ID.          | Mandatory (Key) |
| UserDescription | Contains the user description. | Optional        |
| IsTechnicalUser | Technical user.                | Optional        |
| AddressPersonID | Contains the person ID.        | Optional        |
| AddressID       | Contains the address ID.       | Optional        |
## 4.2.13.2.7  Integrating Communication Arrangement Data (Read)
You can use this communication scenario to read communication arrangement data.
## Context
This communication scenario allows you to read communication arrangements, read assigned inbound users, outbound users, inbound services and outbound services.
## Authentication Methods
This communication scenario can be configured with the following inbound authentication methods:
- Basic Authentication (user and password)
- X.509 (certificates)
## 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 Communication Arrangement Read Integration scenario (SAP\_COM\_0A07) in the Communication Arrangements app.
For more information, see the Related information section.
## Related Information
Communication Management [page 2707]
## 4.2.13.2.7.1  Communication Arrangement - Read Integration
This service enables you to:
- Read communication arrangements
- Read assigned inbound users, outbound users, inbound services and outbound services
This service is published on the SAP Business Accelerator Hub. For more information about APIs, see the Related Information section.
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
| Service Group (incl. Name- space if It Exists)   | Repository ID   | Service Name (incl. Name- space if It Exists)   |   Version |
|--------------------------------------------------|-----------------|-------------------------------------------------|-----------|
| aps_com_api_ca_read                              | srvd_a2x        | CommunicationArrangeme nt                       |      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                                              |
|-----------------------------|---------------------------------------|-------------|--------------------------------------------------------------|
| CommunicationArrange- ments | Contains communication ar- rangements | Mandatory   | For more information, see the Related Information sec- tion. |
## Additional Information
##  Note
For more information about Communication Management, see the Related Information section.
## Related Information
Communication Arrangements - Entity [page 1021]
APIs on SAP Business Accelerator Hub
Communication Management [page 2707]
## 4.2.13.2.7.1.1  Communication Arrangements - Entity
Technical name: CommunicationArrangements
## Properties
| Property                     | Description                    | Necessity       |
|------------------------------|--------------------------------|-----------------|
| CommunicationArrangementUUID | Communication arrangement UUID | Mandatory (Key) |
| Property                     | Description                        | Necessity   |
|------------------------------|------------------------------------|-------------|
| CommunicationArrangementName | Communicaton arrangement name      | Optional    |
| CommunicationSystemID        | Communication system ID            | Optional    |
| CommunicationSystemName      | Communication system name          | Optional    |
| CommunicationScenarioID      | Communication scenario ID          | Optional    |
| CommunicationScenarioName    | Communication scenario name        | Optional    |
| LastChangedDateTime          | Date and time of last change       | Optional    |
| LastChangedByUserID          | Last changed by <user ID>          | Optional    |
| LastChangedByUserName        | Last changed by <user name>        | Optional    |
| LastChangedByUserDescription | Last changed by <user description> | Optional    |
| LastChangedByEMailAddress    | Last changed by <email address>    | Optional    |
| LastChangedByGlobalUserID    | Last changed by <global user ID>   | Optional    |
##  Note
To display more information about the properties on the SAP Business Accelerator Hub, choose Schema View .
## Expandables
This entity is expandable with the following:
- Inbound User
- Outbound User
- Inbound Services
- Outbound Services
## Related Information
Communication Arrangement - Inbound User Entity [page 1023]
Communication Arrangement - Outbound User Entity [page 1023]
Communication Arrangement - Inbound Service Entity [page 1024]
Communication Arrangement - Outbound Service Entity [page 1025]
## 4.2.13.2.7.1.1.1  Communication Arrangement - Inbound User Entity
Technical name: CommArrangementsInboundUsers
## Properties
| Property                     | Description                                                                                                                                                                  | Necessity       |
|------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|
| CommunicationArrangementUUID | Communication arrangement UUID                                                                                                                                               | Mandatory (Key) |
| UserID                       | User ID                                                                                                                                                                      | Mandatory (Key) |
| UserName                     | User name                                                                                                                                                                    | Optional        |
| OAuth2ClientID               | OAuth 2.0 client ID                                                                                                                                                          | Optional        |
| OAuth2GrantType              | OAuth 2.0 grant type                                                                                                                                                         | Optional        |
| AuthMethod                   | x509 : SSL Client Certificate basic : User ID and Password none : None oauth2 : OAuth 2.0 oauth1 : OAuth 1.0 princ_prop: Principal Propagation oauth2_mtls: OAuth 2.0 (mTLS) | Optional        |
##  Note
To display more information about the properties on the SAP Business Accelerator Hub, choose Schema View .