orkungedik/SAP-basis-dataset huggingface dataset:
## 5.6.2.8 Troubleshooting for SAP S/4HANA Cloud Extensibility Service
Information about troubleshooting issues you might experience when extending SAP S/4HANA Cloud on SAP BTP using the SAP S/4HANA Cloud Extensibility service.
## Cloud Foundry Environment
These are some issues you might experience when extending SAP S/4HANA Cloud on SAP BTP, Cloud Foundry environment:
- Cannot create an SAP S/4HANA Cloud Extensibility Service Instance of the Messaging Plan [page 2171]
- My SAP S/4HANA Cloud Extensibility Service Instance Failed to Create and It Didn't Say Why [page 2172]
## 5.6.2.8.1 Cannot create an SAP S/4HANA Cloud Extensibility Service Instance of the Messaging Plan
Cannot create an SAP S/4HANA Cloud Extensibility service instance of the messaging plan.
## Issue/Symptom
You are trying to create an SAP S/4HANA Cloud Extensibility service instance of the messaging plan and you get the following error message:"Creation Failed."
## Reason
You are probably providing in the JSON file the same emClientId that was already used in the subaccount.
## Solution
Make the value of the emClientId parameter unique within the subaccount.
## Related Information
Set Up the Connectivity Between Event Mesh and the SAP S/4HANA Cloud Tenant [page 2140]
## 5.6.2.8.2 My SAP S/4HANA Cloud Extensibility Service Instance Failed to Create and It Didn't Say Why
My SAP S/4HANA Cloud Extensibility service instance failed to create and it didn't say why.
## Issue/Symptom
You are trying to create an SAP S/4HANA Cloud Extensibility service instance but the creation fails with no error message.
## Solution
This is what you can do:
- You can use the Cloud Foundry command line interface to get the error message by executing the command:
- cf service &lt;service\_instance\_name&gt; Check for any error messages there.
- Can you reach the SAP S/4HANA Cloud tenant? Check that the tenant is not in maintenance or being updated.
If this didn't help, you can try some more specific actions. What service plan are you using?
## I am using the messaging service plan
Issue/Symptom
Your SAP S/4HANA Cloud Extensibility service instance of the messaging plan failed to create and it didn't say why.
## Solution
Try to do the following:
- Is the Enterprise Messaging Integration scenario (SAP\_COM\_0092) enabled on your SAP S/4HANA Cloud tenant? Check whether you see it in the Display Communication Scenarios application in your SAP S/ 4HANA Cloud tenant.
- The clients for SAP Event Mesh require unique values (within your subaccount in SAP BTP) for the emname and namespace properties. In the messaging plan, you have either provided these manually, or you have only set the emClientId property and let it generate them. If the latter, then these values would be emClientId&gt; for emname and sap/S4HANAOD/emClientId&gt; for namespace . Check whether your subaccount already has existing clients with such emname or namespace values. You can do this by using the Enterprise Messaging Business Application from the SAP Event Mesh subscription of your subaccount. See View Event Catalog for a Subaccount.
## I am using the api-access service plan
## Issue/Symptom
Your SAP S/4HANA Cloud Extensibility service instance of the api-access plan failed to create and it didn't say why.
## Solution
Try to do the following:
- Is the communication scenario with the scenarioId that you provided enabled on that tenant? Check whether you see it in the Display Communication Scenarios application in your SAP S/4HANA Cloud tenant.
- Are you using supported authentication types? In the scenario definition, you can see which authentication types are supported for both outbound and inbound connectivity. Verify that the types you are providing in the descriptor are supported by the scenario.
## 5.6.4.1 Configure the Entitlements for the SAP SuccessFactors Extensibility Service
Configure the required entitlements to make the SAP SuccessFactors HXM Suite OData APIs of the registered SAP SuccessFactors system accessible in your subaccount in which your extension applications will reside.
## Prerequisites
- You are an administrator of the global account in SAP BTP.
- The subaccount is in the SAP BTP, Cloud Foundry environment with enabled Cloud Foundry, or Kyma, or both capabilities.
- You have registered an SAP SuccessFactors system. See Register an SAP SuccessFactors System in a Global Account in SAP BTP [page 2061].
## Context
An entitlement is your right to provision and consume a resource. In other words, the entitlement is the api-access service plan that you're entitled to use, and the sso-configuration service plan that allows you to register an assertion consumer service in SAP SuccessFactors automatically.
## Procedure
1. In the SAP BTP cockpit, navigate to your global account.
2. In the navigation area, choose Entitlements Entity Assignments .
3. On the Entity Assignments screen, select your subaccount in the Subaccounts/Directories field.
4. Choose Edit , and then choose Add Service Plans .
5. Select the SAP SuccessFactors Extensibility service.
##  Note
To have the SAP SuccessFactors Extensibility service in the list, you need to have registered at least one SAP SuccessFactors system.
6. In the Service Details area, select the system you have registered. In the Available Plans area, select the api-access and sso-configuration service plans, and then choose Add 2 Service Plans .
## Related Information
Configure Entitlements and Quotas for Subaccounts [page 2269]
## 5.6.4.2 Create a Service Instance to Consume the SAP SuccessFactors HXM Suite OData API
To enable the integration of your extension applications with the SAP SuccessFactors system you have registered in the global account in SAP BTP, you first need to create a service instance of the corresponding service.
## Context
In both Cloud Foundry and Kyma environment, you consume services by creating a service instance. Service instances are created using a specific service plan.
To allow applications running on SAP BTP to consume SAP SuccessFactors HXM Suite OData APIs, you need to create a service instance of the SAP SuccessFactors Extensibility service using the api-access service plan.
You create the service instance in your subaccount with the respective environment enabled. When creating the service instance, you configure the authentication type for the communication by specifying the required configurations in a JSON format. SAP BTP supports the following authentication scenarios for SAP SuccessFactors:
- OData access with OAuth 2.0 SAML bearer assertion To use this authentication type, you must protect your application. See Adding Authentication and
Authorization [page 530].
- OData access with OAuth 2.0 SAML bearer assertion with technical user
The process for creating a service instance depends on the environment you are using:
- For Cloud Foundry environment, see Create an SAP SuccessFactors Extensibility Service Instance in the Cloud Foundry Environment [page 2181].
- For Kyma environment, see Create an SAP SuccessFactors Extensibility Service Instance in the Kyma Environment [page 2183].
## 5.6.4.2.2 Create an SAP SuccessFactors Extensibility Service Instance in the Kyma Environment
## Prerequisites
- Before creating an SAP SuccessFactors Extensibility service instance in the Kyma environment, see Create a Service Instance to Consume the SAP SuccessFactors HXM Suite OData API [page 2180].
- Have the Kyma environment enabled for the subaccount you are using. See Creating a Kyma Instance [page 3125].
- Configure the roles in the Kyma environment. See Assign Roles in the Kyma Environment [page 3301].
- The SAP BTP Operator module is enabled. See Adding and Deleting a Kyma Module [page 3157]
- Have the entitlements of the SAP SuccessFactors Extensibility service configured. See Configure the Entitlements for the SAP S/4HANA Cloud Extensibility Service [page 2114].
## Context
During the creation of the service instance, a destination on the subaccount level with the same name as the service instance name is automatically created in this subaccount. It contains all instance binding properties which are sufficient to establish connection to the SAP SuccessFactors system.
##  Note
Make sure that you don't already have a destination with the same name as the service instance. If you do, you will not be able to create the service instance.
## Procedure
1. Navigate to the subaccount for which you want to create an SAP SuccessFactors Extensibility service instance.
2. On the subaccount Overview page, in the Kyma Environment section, open the Kyma dashboard.
3. Choose Namespaces from the left-hand side navigation and open the namespace in which you want to create a service instance.
4. Choose Service Management Service Instances from the left-hand side navigation.
5. In the Service Instances page, choose Create Service Instance in the upper right-hand corner. A new dialog opens.
6. Choose the Advanced tab and fill in the following fields:
- Give a meaningful name of the new SAP SuccessFactors Extensibility service instance.
- In the Offering Name field, enter sap-successfactors-extensibility , which is the technical name of the SAP SuccessFactors Extensibility service.
- In the Plan Name field, enter api-access .
- Expand Instance Parameters . To define the authentication type for the API access, specify the parameters listed in this JSON file: API Access Configuration JSON File [page 2185].
7. Choose Create .
## Next Steps
After creating the SAP SuccessFactors Extensibility service instance, you have to bind the instance to an application, and it will be assigned an access URL and credentials to the corresponding API. See Using SAP BTP Services in the Kyma Environment [page 2019].
## 5.6.4.2.3 API Access Configuration JSON File
Use the authentication type JSON descriptor to define the authentication type for the inbound connectivity to the SAP SuccessFactors HXM Suite OData API.
<!-- image -->
| Parameter   | Description                                                                                                                   |
|-------------|-------------------------------------------------------------------------------------------------------------------------------|
| systemName  | The name of the system you have registered in a global ac- count in SAP BTP.  Note The system must be in status Registered . |
|             | Rules/Guidelines • Required: Yes                                                                                              |
## Parameter
technicalUser
## Example
```
{ "systemName":"MY_SYSTEM", "technicalUser":"technicalonboarder" }
```
## Description
The name of the technical user for consuming the SAP SuccessFactors HXM Suite OData API without a logged-in user.
##  Caution
This property specifies the systemUser property in the destination that is created as a result of creating the SAP SuccessFactors Extensibility service instance.
The systemUser is deprecated and will be removed soon. We recommend that you work on behalf of specific (named) users instead of working with a technical user.
##  Note
The technical user can be any user with the respective permissions. These permissions depend on the use case and the API you want to access. To find out which permission you need to assign to the technical user, go to SAP Business Accelerator Hub , find the SAP SuccessFactors API you want to access and from the Overview tab go to the Documentation section and open the help.sap.com link. There you find the right information for each API.
## Rules/Guidelines
- Required: No
- Allowed characters: [a-zA-Z0-9\_-]
- Max length: 100
## 5.6.4.3 Configure Single Sign-On Between a Subaccount in SAP BTP and SAP SuccessFactors
Use this procedure to configure the single sign-on (SSO) between SAP BTP and the SAP SuccessFactors system.
## Prerequisites
You have the UI and Role Administrator role assigned to your user. See Security Administration: Managing Authentication and Authorization [page 2278].
## Context
The authentication to SAP SuccessFactors applications is restricted to the authorized users. The identification of a user is verified by the identity provider, as specified by SAML 2.0. The Identity Authentication service stores a list of all users that are allowed to access the SAP SuccessFactors system along with their credentials. The integration between the SAP SuccessFactors and the identity provider is based on a trust configuration. When a user attempts to access SAP SuccessFactors for the first time, the system redirects the user to the identity provider for identification. From then on, the user session is kept active, and the user is no longer prompted for credentials when trying to use the SAP SuccessFactors application. This is called single sign-on (SSO).
To ensure the required security for accessing the applications, you need to configure the single sign-on between the subaccount in SAP BTP and the SAP SuccessFactors system using a SAML identity provider. The single sign-on requires both solutions to be configured as trusted SAML service providers for the identity provider, and at the same time, the identity provider to be configured as trusted identity provider for the two solutions.
If you have an account in the Cloud Foundry environment, you need to set up the single sign-on (SSO) according to this environment.
## Procedure
1. Configure SAP SuccessFactors as a Trusted Identity Provider in SAP BTP [page 2188].
2. Configure the Subaccount as a Trusted Service Provider in SAP SuccessFactors [page 2188].
## 5.6.4.3.1 Configure SAP SuccessFactors as a Trusted Identity Provider in SAP BTP
Use this procedure to set up the trust configuration of the subaccount in SAP BTP and add SAP SuccessFactors as an identity provider.
## Procedure
1. Download SAML metadata from the SAP SuccessFactors system.
- a. Go to https://&lt;sap\_successfactors\_system&gt;/idp/samlmetadata? company=&lt;company\_id&gt;&amp;cert=sha2 where:
- &lt;sap\_successfactors\_system&gt; is the hostname of your SAP SuccessFactors system
- &lt;company\_id&gt; is the ID of your SAP SuccessFactors company
- b. When you are prompted, save the file on your local file system and change its extension to .xml .
2. Register the SAP SuccessFactors identity provider in the SAP BTP cockpit.
- a. Open the cockpit and navigate to your subaccount.
- b. Choose Security Trust Configuration .
- c. Choose New SAML Trust Configuration .
- d. To upload the SAML metadata you downloaded in step 1, choose Upload . Browse to the XML file you saved and select it. Some of the fields are automatically filled in.
- e. In the Name field, enter a meaningful name for the trust configuration.
- f. Save the changes.
3. Make the trust configuration to the SAP SuccessFactors identity provider the only configuration that is active.
## 5.6.4.3.3 Single Sign-On Configuration JSON File
Use the single sign-on (SSO) configuration JSON file to define the assertion consumer services in SAP SuccessFactors for the subaccount in SAP BTP and for each extension application you have deployed in SAP BTP that is extending the SAP SuccessFactors system functionality.
##  Note
The content of the JSON file must be up to 5120 characters without spaces.
systemName
logoutURLs
## 
```
"systemName": "MY_SYSTEM", site.com/logout"] }
```
The name of the system you have registered in the global account in SAP BTP
## Rules/Guidelines
The name must be the same as the one defined during the system registration in the global account. See Register an SAP SuccessFactors System in a Global Account in SAP BTP [page 2061].
##  Note
The system must be in status Registered .
(Optional) This is a list of the logout URLs. A logout URL is the absolute URL that corresponds to the URL of the application router with the appended value of the logoutEndpoint property. See logout [page 468].
##  Note
Make sure that the value of the logoutMethod property is set to GET in the xs-app.json file.
##  Note
The SameSite attribute of the Set-Cookie HTTP response header needs to be set to None so that the cookies are sent in all responses to both first-party and cross-origin requests. You also need to set the cookie Secure attribute, because it requires a secure context/ HTTPS. See Environment Variables [page 494].
##  Note
If you don't specify the logoutURLs parameter, only an assertion consumer service for the subaccount in SAP BTP will be created.
```
Sample Code { "logoutURLs": ["https://my-first-site.com/logout", "https://my-second-
```
## 5.6.4.4 Restore Configuration Settings After an Instance Refresh
After an instance refresh, you must restore some of your extension integration artifacts and configuration settings for the SAP SuccessFactors target company.
## Prerequisites
- You have a dedicated SAP SuccessFactors company instance.
- You have a registered SAP SuccessFactors system in your global account in SAP BTP.
- You have performed the instance refresh with the Instance Refresh tool or your cloud operators have performed an instance refresh manually.
## Context
In SAP SuccessFactors, instance refresh is a procedure in which the data and the settings of a source company instance are copied into another company instance. During the instance refresh the data of the target company instance is deleted and replaced by the data of the source company instance. Therefore, after an instance refresh, if the target company has been integrated with a global account in SAP BTP, the extension integration configuration settings and artifacts in the target company are overwritten by the configuration settings and data coming from the source company.
You can trigger the instance refresh automatically with the Instance Refresh tool or your cloud operators can trigger it manually.
If you have performed an instance refresh with the Instance Refresh tool, the OAuth clients, and the Assertion Consumer Services (ACS) created by the cloud platform are recreated. In Provisioning , the Extension Management Configuration page displays the integration details for the target system.
##  Note
The OAuth clients are assigned new IDs. This does not affect the configuration settings.
However, if you have the following artifacts, you must reconfigure them in the SAP SuccessFactors target company instance:
- Custom home page tiles
- Permission roles
- Permission groups
##  Note
After a manual instance refreshed, no artifacts are reconfigured. If you want to restore the integration settings for the target company instance, you need to recreate the SAP SuccessFactors Extensibility service instance.
## Procedure
To restore the configuration settings after an instance refresh, proceed as follows:
- After an automated instance refresh:
1. If you have configured custom home page tiles in the target company instance, reconfigure them. See Custom Home Page Tiles.
2. If you have configured permission roles and permission groups, you need to reconfigure them. See What Are Role-Based Permissions?.
- After a manual instance refresh:
1. For SAP SuccessFactors, Second Half 2021 Release or later, proceed as follows:
1. Recreate the SAP SuccessFactors Extensibility service instance. See Create a Service Instance to Consume the SAP SuccessFactors HXM Suite OData API [page 2180].
2. If you have configured permission roles and permission groups, you need to reconfigure them. See Custom Home Page Tiles.
3. Reconfigure the permission roles and permission groups. See What Are Role-Based Permissions?.
## Results
You have restored the extension integration artifacts and configuration setting of the target company instance.
## 5.6.4.6 Configuring Backup
You can back up and restore the destination and the trust configuration settings for the integration between the SAP SuccessFactors system and the global account in SAP BTP.
You can back up the following configuration settings:
- The HTTP destination configured during the creation of the SAP SuccessFactors Extensibility service instance. For more, see Export Destinations.
- Your subaccount X.509 certificates. For more information, see Set up Trust Between Systems
- Your SAP SuccessFactors IdP SAML 2.0 metadata. To download your SAP SuccessFactors IdP SAML 2.0 metadata, in the SAP BTP cockpit, navigate to Connectivity Destinations Download IdP Metadata .
- Your identity provider configurations. You can back up identity provider configurations with the Identity Provider Management API. For more information see: Identity Provider Management API.
## 5.6.4.7 Accessibility Features in SAP SuccessFactors Extensibility Service
To optimize your experience of SAP SuccessFactors Extensibility service, SAP Business Technology Platform (SAP BTP) provides features and settings that help you use the software efficiently.
##  Note
SAP SuccessFactors Extensibility service runs on the SAP BTP cockpit. For this reason, accessibility features for SAP BTP cockpit also apply. See the accessibility documentation for SAP BTP cockpit on SAP Help Portal at Accessibility Features in SAP BTP cockpit [page 2206].
For more information on screen reader support and keyboard shortcuts, see Accessibility for End Users.
## 5.6.4.8 Troubleshooting for SAP SuccessFactors Extensibility Service
Information about troubleshooting issues you might experience when extending SAP SuccessFactors on SAP BTP using the SAP SuccessFactors Extensibility service.
## Cloud Foundry Environment
These are some issues you might experience when extending SAP SuccessFactors on SAP BTP, Cloud Foundry environment:
- My SAP SuccessFactors OData Destination Does Not Work [page 2199]
- My SAP SuccessFactors Extensibility Service Instance Failed to Create and It Didn't Say Why [page 2200]
## 5.6.4.8.1 My SAP SuccessFactors OData Destination Does Not Work
SAP SuccessFactors OData destination does not work.
## Issue/Symptom
You are extending SAP SuccessFactors on SAP BTP, Cloud Foundry environment using the SAP SuccessFactors Extensibility service. Y ou are trying to configure the integration between SAP SuccessFactors and SAP Business Technology Platform (SAP BTP) and your SAP SuccessFactors OData destination does not work.
## Solution
To fix your SAP SuccessFactors OData destination, you can try the following:
- Make sure that the names of the destination properties, and their values match the names described in Create an HTTP Destination in SAP BTP.
- Make sure that the values of the Client Key and apiKey properties match the API Key value specified in the SAP SuccessFactors OAuth client.
- Make sure that the X509 certificate specified in the SAP SuccessFactors OAuth client is the same as the one you have in the Cloud Foundry environment. See Configuring the Extension Application's Connectivity to SAP SuccessFactors.
- Make sure that you have the uaa.user authorization scope defined in the xs-security.json file. See:
- Update a Service Instance
- UAA Scopes
- Make sure that the uaa.user authorization scope is defined in the role template in the xs-security.json file. See Accessing Business Service Data.
- Make sure you consume the destination correctly, as described in Consumе the Destination.
- Make sure that you use the user\_token OAuth grant for retrieving the destination. See OAuth User Token Exchange Authentication.
- Make sure that the name of the destination that you use in your application matches the name of the one created in the SAP BTP cockpit.
- Note that if you have a destination defined as an environment variable, it will overrule the one created in the cockpit.
- Check the logs in Kibana. If you do not have the application logging service, you can add it. See Access and Analyze Application Logs and Container Metrics.
- Make sure that the name of the destination is the same as the name of the SAP SuccessFactors Extensibility service instance you have created. See Access and Analyze Application Logs, Container Metrics and Custom Metrics.
## 5.6.4.8.2 My SAP SuccessFactors Extensibility Service Instance Failed to Create and It Didn't Say Why
My SAP SAP SuccessFactors extensibility service instance failed to create and it didn't say why.
## Issue/Symptom
You are trying to create an SAP SuccessFactors Extensibility service instance but the creation fails without an error message.
## Solution
This is what you can do:
- You can use the Cloud Foundry command line interface to get the error message by executing the command:
cf service &lt;service\_instance\_name&gt;
Check for any error messages there. See Managing Service Instances .
- Can you reach the SAP SuccessFactors company? Check that the tenant is not in maintenance or being updated.
- Check that there is not an already existing destination with the same name as the SAP SuccessFactors Extensibility service instance you are creating. When creating this service instance, a destination with the same name will be automatically created. See Create an SAP SuccessFactors Extensibility Service Instance in the Cloud Foundry Environment.
## 6 Administration and Operations
Administration and operation tasks for SAP BTP include management and configuration of global accounts and subaccounts as well as the operation of applications.
<!-- image -->
- Account Administration Using the SAP BTP Command Line Interface (btp CLI) [page 2401]
- Account Administration in the Cockpit [page 2205]
- Administration and Operations in the Cloud Foundry Environment [page 2501]
- Administration and Operations in the ABAP Environment [page 2631]
- Administration and Operations in the Kyma Environment [page 3124]
- Account Administration Using APIs [page 2457]
## Administration of Global Accounts, Directories, and Subaccounts
Some of the typical responsibilities of SAP BTP administrators include maintenance of global accounts, management of directories and subaccounts, and configuration of entitlements. To do this, you can use either the SAP BTP cockpit, the SAP BTP command line interface, or APIs.
- Account Administration in the Cockpit [page 2205]
- Account Administration Using the SAP BTP Command Line Interface (btp CLI) [page 2401]
- Account Administration Using APIs [page 2457]
## Administration and Operations in Different Environments
Environments constitute the actual platform-as-a-service offering of SAP BTP that allows for the development and administration of business applications. Each environment offers different approaches to manage administration and operations. For more information, see Environments [page 56].
## Administration and Operations in the Cloud Foundry Environment
In the Cloud Foundry environment, you can manage orgs, spaces, and space quota plans using the SAP BTP cockpit or the SAP BTP command line interface.
Learn more about the different application operations that you can perform in the Cloud Foundry environment.
- Org Administration Using the Cockpit [page 2512]
- Org Administration Using the Cloud Foundry CLI [page 2532]
- Application Operations in the Cloud Foundry Environment [page 2578]
- Audit Logging in the Cloud Foundry Environment [page 2595]
## Administration and Operations in the ABAP Environment
When using the ABAP environment, the account administration tasks are performed in the Cloud Foundry environment.
The application operations are specific to the ABAP environment. For more information, see SAP Fiori Apps in the ABAP Environment [page 2633].
## Administration and Operations in the Kyma Environment
The administrators of the Kyma environment take care of setting it up and make sure it's ready for developers to work with.
- Assign Roles in the Kyma Environment [page 3301]
- Creating a Kyma Instance [page 3125]
- Kyma Environment Backup [page 3162]
## Related Information
Account Model [page 111]
## 6.1 Account Administration
Learn how to manage global accounts, directories, and subaccounts on SAP BTP using different tools.
- Account Administration in the Cockpit [page 2205]
- Account Administration Using the SAP BTP Command Line Interface (btp CLI) [page 2401]
- Account Administration Using Joule in the Cockpit [page 2396]
- Account Administration Using APIs [page 2457]
- Account Administration Using Infrastructure as Code [page 2499]
Once your account model is set up, you can move on to managing the different environments you plan to use:
- Administration and Operations in the Cloud Foundry Environment [page 2501]
- Administration and Operations in the ABAP Environment [page 2631]
- Administration and Operations in the Kyma Environment [page 3124]
## Related Information
## Account Model [page 111]
Entitlements and Quotas [page 117] User and Member Management [page 121] Environments [page 56]
## 6.1.1  Account Administration in the Cockpit
Learn about frequent administrative tasks you can perform using the SAP BTP cockpit, such as managing global accounts, directories, subaccounts, entitlements, and members.
## Access the Cockpit [page 2206]
Learn how to access the SAP BTP cockpit.
## Navigate in the Cockpit [page 2207]
Learn how to navigate to your global accounts, directories, and subaccounts in the SAP BTP cockpit.
## Managing Global Accounts Using the Cockpit [page 2208]
Your SAP BTP global account is the entry point for managing the resources, landscape, and entitlements for your departments and projects in a self-service manner.
## Managing Directories Using the Cockpit [page 2241]
Learn how to organize and manage your subaccounts according to your technical and business needs by using directories in the SAP BTP cockpit.
## Managing Subaccounts Using the Cockpit [page 2249]
Learn how to structure a global account according to your organization's and project's requirements with regard to members, authorizations, and entitlements by managing subaccounts.
## Managing Entitlements and Quotas Using the Cockpit [page 2261]
When you purchase an enterprise account, you are entitled to use a specific set of resources, such as the amount of memory that can be allocated to your applications.
## Subscribe to Multitenant Applications Using the Cockpit [page 2274]
Subscribe to multitenant applications from the Subscriptions page in the SAP BTP cockpit.
## Security Administration: Managing Authentication and Authorization [page 2278]
This section describes the tasks of administrators of SAP BTP. Administrators ensure user authentication and assign authorization information to users and user groups.
## Related Information
Account Model [page 111]
## 6.1.1.1 Access the Cockpit
Learn how to access the SAP BTP cockpit.
## Context
Navigate to https:/ /cockpit.btp.cloud.sap to access the cockpit. Depending on your geographic location, this URL redirects you to the closest regional cockpit URL.
##  Tip
Use the idp URL parameter to choose which identity provider with which you want to log on.
For example: https://cockpit.btp.cloud.sap?idp=mytenant.accounts.ondemand.com
For more information, see Log On with a Custom Identity Provider to the SAP BTP Cockpit [page 2332].
## 6.1.1.1.1 Accessibility Features in SAP BTP cockpit
To optimize your experience of the SAP Business Technology Platform (SAP BTP), SAP BTP cockpit provides features and settings that help you use the software efficiently. Learn more about these features and settings and find out how to use them.
##  Note
SAP BTP cockpit is based on SAPUI5. For this reason, accessibility features for SAPUI5 also apply. See the accessibility documentation for SAPUI5 on SAP Help Portal at Accessibility for End Users.
For more information on screen reader support and keyboard shortcuts, see Screen-Reader Support for SAPUI5 Controls and Keyboard Handling for SAPUI5 Elements.
Additionally, SAP BTP cockpit offers a high contrast black theme. See Use High Contrast Black Theme [page 2206].
## Use High Contrast Black Theme
## Context
This feature is recommended for users with need for high contrast themes.
## Steps
1. In the header toolbar choose Your Name Settings .
2. Select the High Contrast Black theme and click Apply .
3. Once you've saved your changes, the cockpit starts with the theme of your choice.
## 6.1.1.3 Managing Global Accounts Using the Cockpit
Your SAP BTP global account is the entry point for managing the resources, landscape, and entitlements for your departments and projects in a self-service manner.
## Global Account Settings
As a global account administrator, you can access the global account settings by clicking  (Global Account Settings) in the SAP BTP cockpit.
In the General tab of the global account settings, you can obtain general information about your global account, including your global account ID, global account name, account type, payment models, contract status, global account subdomain, geographic access restrictions, and when your account was created.
##  Note
In this tab, you cannot change any of the values. The only value that you can edit is the global account name, and you can do this in the Account Explorer page (see Change the Display Name of Your Global Account [page 2210]).
In the Subaccounts tab in the global account settings, you can
- Define default settings that are used when creating a new subaccount in this global account. You can set the supported providers, the default provider, and the default region.
- Set the option to enable the force deletion of subaccounts. If this option is selected, all global account admins can force delete subaccounts that are not marked as "used for production". The force deletion of a subaccount permanently deletes all its data, including applications, service instances, spaces, active subscriptions, and members. The force deletion is permanent and irreversible. This option also enables the force deletion of subaccounts using the btp CLI or the SAP Cloud Management APIs. Subaccounts that are marked as "used for production" cannot be force deleted.
## Related Information
Setting Up Your Account Model
Managing Directories Using the Cockpit [page 2241] Managing Subaccounts Using the Cockpit [page 2249]
## 6.1.1.3.1 Log On to Your Global Account
Use the SAP BTP cockpit to log on to your global account and start working in SAP BTP.
## Prerequisites
You have received a welcome e-mail from SAP for your global account. If you don't have a global account administrator or one isn't available, there is a workaround using SAP for Me.
For more information, see 2669325 - How to add a user as a Global Account administrator for SAP Business Technology Platform .
## Procedure
1. Use the link in your Welcome e-mail.
Choose https://cockpit.btp.cloud.sap to access the cockpit. Depending on your own geo location this URL will redirect you to the closest regional cockpit URL.
<!-- image -->
If single sign-on has not been configured for you, you will have to enter your credentials. You'll find your logon ID in your Welcome e-mail.
2. Choose a global account.
## Results
The Account Explorer page for that global account opens.
## Next Steps
- Track and monitor usage of services in your global account:
- Use the filters to specify which usage information to display in the tables and monthly usage charts. The Period filter is applied to the chart display.
- Some rounding or shortening is applied to large values. Mouse over values in the table to view the exact values in the tooltips.
- Choose a row in the table to view its historic information in the Monthly Usage chart. To display a larger view of a chart, choose the  (Zoom) button.
- To download the information in the Overview page to a Microsoft Excel file, choose the Export button.
- Access your subaccounts and create new subaccounts. See Create a Subaccount [page 2249].
## Related Information
Account Model [page 111]
Global Accounts [page 111] Create a Subaccount [page 2249]
## 6.1.1.3.2 Change the Display Name of Your Global Account
Change the display name for the global account using the SAP BTP cockpit.
## Prerequisites
You are an admin of the global account that you'd like to edit.
## Context
 Tip
You can also change the account's display name using the SAP BTP command line interface (btp CLI) with the btp update accounts/global-account command. See Account Administration Using the SAP BTP Command Line Interface (btp CLI) [page 2401].
## Procedure
1. Open your global account in the SAP BTP cockpit.
2. Navigate to the Account Explorer page.
3. In the Directories &amp; Subaccounts view, locate the first entry in your account structure, which is your global account, and click  (Actions) . Then select Edit .
4. In the Edit Global Account dialog box, enter the new human-readable name for the global account.
5. Save your changes.
## Related Information
Account Model [page 111]
## 6.1.1.3.3 Add Members to Your Global Account
Add users as global account members using the SAP BTP cockpit.
## Prerequisites
- You must be a global account administrator to add other global account members. If you don't have a global account administrator or one isn't available, there is a workaround using SAP for
Me.
For more information, see 2669325 - How to add a user as a Global Account administrator for SAP Business Technology Platform .
- The users exist in a trusted platform identity provider. All users of SAP BTP are stored in identity providers, either in the default or in a custom identity provider. SAP BTP needs a copy of the user, sometimes called a shadow user. You assign the shadow user authorizations to access resources in SAP BTP. When a user authenticates, SAP BTP forwards the request to the identity provider. For more information, see Trust and Federation with Identity Providers [page 2280].
## Context
Assign predefined or custom role collections to users who need to manage or view the global account in SAP BTP cockpit. Examples of predefined role collections include the following:
- Global Account Administrator
- Global Account Viewer
For more information about these role collections, see Role Collections and Roles in Global Accounts, Directories, and Subaccounts [page 125].
## Procedure
1. Navigate to your global account.
2. Add a user to your global account.
For more information, see Create Users [page 2347].
##  Note
If the user is already a user in a subaccount and has logged on to SAP BTP cockpit, SAP BTP adds the user at the global account level automatically, but without any role collections.
3. Assign a role collection to the user. For more information, see Assign Users to Role Collections [page 2355].
## Results
The next time this user logs on to the SAP BTP cockpit, the user can access this global account.
## Related Information
User and Member Management [page 121]
## 6.1.1.3.6 Managing Budgets in Your Global Account
Budgets allow you to better control your global account spending and plan for future consumption by setting up budget limits for your global account in SAP BTP.
Automatic email alerts notify global account administrators when spending exceeds defined thresholds, allowing for timely intervention. You can also leverage the SAP Alert Notification service for SAP BTP to create custom alerts according to your specific monitoring needs.
##  Note
This is a beta feature. Beta features aren't part of the officially delivered scope that SAP guarantees for future releases. For more information, see Important Disclaimers and Legal Information.
##  Tip
Remember to periodically review your budget settings and thresholds to ensure proactive financial management.
## Important Information
When you use budgets in your global account, please note the following important details:
- Costs and usage values between the last balance statement and the current date are estimates and may change at the end of the month when the actual overall global account usage is aggregated for billing purposes. SAP does not guarantee the accuracy or reliability of real-time alerts based on these estimates. It is your responsibility to review and validate alerts before you make any decisions based on them.
- The system doesn't suspend costs and service usage when a budget amount or threshold is exceeded. It's your responsibility to take the appropriate action within the global account to prevent overages.
- There may be a delay between the time a budget threshold was exceeded and the time that you receive a notification. This may be due to delays in the update cycles of costs and service usage, as well as the periodic evaluations of budgets against your global account costs and usage.
- If your global account combines both subscription and consumption-based commercial models, then any usage that falls within your prepaid quota, as defined by your subscription-based commercial agreement, is not evaluated by your budget.
## 6.1.1.3.6.1  Accessing Your Global Account's Budgets
Access and manage your global account's budgets in SAP BTP cockpit. Monitor spending, view active and expired budgets, and configure table columns.
## Prerequisites
- Your global account uses the SAP BTP Enterprise Agreement (SAP BTPEA), Cloud Platform Enterprise Agreement (CPEA), or Pay-As-You-Go for SAP BTP flavor of the consumption-based commercial model, or it combines one of these consumption-based flavors with the subscription-based commercial model. Note that the use of the consumption-based commercial model is subject to its availability in your country or region.
- You must also be a global account administrator or global account viewer.
## Procedure
1. Open SAP BTP cockpit.
2. From the global account level, go to the Costs and Usage page.
3. Click on the Budgets tab.
The Budgets tab shows your global account's budgets in two separate tables:
- Active Budgets : All budgets that are currently active and monitoring spending in your global account.
 Tip
Choose the View in Billing Tab action in the  (Actions) context menu of a budget to quickly open the Billing tab. This tab is then automatically filtered by the subaccounts and service plans defined in the budget's scope.
- Expired Budgets : All budgets whose end date surpasses the current date. Expired budgets are no longer active in your global account and don't send alerts or events.
 Tip
Click

(Configure Table Columns) to set the columns you want to view in each table.
4. Click on a budget to view its configuration and History chart.
## 6.1.1.3.6.3  Creating a Budget
Creating a budget allows you to monitor and manage spending in your global account. You can create a budget from scratch or from an existing budget that is active or has expired.
Each global account is allowed up to 10 active budgets. Active budgets have an end date in the future or no end date. Budgets expire automatically when the current date surpasses the end date of the budget.
## Procedure
1. In the Budgets tab, click Create .
<!-- image -->
To duplicate a previous budget configuration, choose Create as New Budget in the budget's  (Actions) context menu. Note that when you use this option to create a new budget, you cannot change the budget type.
2. Configure the budget's settings.
For detailed information about each of the budget settings, see Understanding Budget Settings [page 2234].
- a. Enter the budget name and an optional description.
- b. Choose the budget type: Cost or Charged Usage .
- c. (Optional) Define the budget's scope by selecting the applicable subaccounts and service plans.
- d. Specify the budget amount.
- e. Set the time period by entering the start date and optionally the end date. You cannot enter a start date that is in the past.
- f. (Optional) Set up to three budget thresholds.
3. View the budget amount and threshold in the History Preview chart below the Scopes section.
4. Review your configuration and then click Create .
## 6.1.1.3.6.4  Viewing a Budget's Details
Viewing a budget provides detailed information about the budget's configuration and status.
## Procedure
- In the Budgets tab, click on a budget to display more details.
For detailed information about each of the budget settings, see Understanding Budget Settings [page 2234].
Use the History chart below the Scopes section to view the costs or charged usage in your global account over the past 12 months. The budget amount and threshold values are overlaid on the chart data, including budget exceedance information, if relevant.
## 6.1.1.3.6.5  Editing a Budget
Editing a budget allows you to make changes to the budget's settings.
##  Note
When you make changes to an existing budget, previously sent alerts may not accurately reflect the new budget settings.
Any changes you make to budget amount will trigger alerts from the current month onward, not retroactively.
## Procedure
1. In the Budgets tab, go to the Active Budgets table.
2. Choose Edit in the budget's  (Actions) context menu.
3. Make changes to the budget's editable settings.
Note that you cannot change the start date and budget type of an existing budget.
For detailed information about each of the budget settings, see Understanding Budget Settings [page 2234].
4. Review your configuration and then click Update .
<!-- image -->
Whenever you change a budget's settings, we recommend you review and update your threshold values carefully to ensure they align with the new budget settings.
## 6.1.1.3.6.6  Deleting a Budget
Deleting a budget removes it permanently from your global account. Deleted budgets cannot be retrieved.
Before deleting a budget, we recommended that you first check with the user that created the budget. Open the budget's details to view this information.
## Procedure
1. Go to the Budgets tab.
2. Choose Delete in the budget's  (Actions) context menu.
3. Confirm the delete action.
## 6.1.1.3.7 Configure Legal Information
Administrators can define legal links per enterprise global account in the SAP BTP cockpit.
## Prerequisites
You have the Administrator role for the global account for which you'd like to define legal links.
## Context
You can define the privacy link relevant for a global account so the members of this global account can view this information.
## Procedure
1. Choose the global account for which you'd like to make changes.
2. In the left-hand navigation, choose Legal Information Configure Privacy Link .
3. Enter the relevant URL.
4. Save your changes.
The links you configured are available in the Legal Information menu.
## Related Information
Navigate in the Cockpit [page 2207] Global Accounts
## 6.1.1.3.8 Enable Analytics in the Cockpit
Learn about how to enable analytics in the SAP BTP Cockpit to improve the overall user experience.
## Prerequisites
You have the Administrator role for the global account for which you'd like to enable analytics.
 Note
If you are an Administrator for multiple global accounts, you must enable analytics for each global account.
## Context
To help improve user experience in the SAP BTP Cockpit, global account administrators can allow global account users to send anonymized usage data to SAP. By enabling analytics in the cockpit, we'll identify and fix issues more quickly, making for an improved cockpit experience. We use analytics to understand how users interact with the platform. With this information, we can make improvements, such as adapting navigation patterns, enhancing customer support, and prioritizing features.
What kind of data do we collect?
- Cockpit usage data: How often a page is opened or which functionality (buttons, links) is used or not used
- Click paths: The navigational paths a user takes to navigate through the cockpit
What data don't we collect?
- Personal, user-specific, or company identifying data
- User input
Your data is used to improve the overall user experience and cannot be used for marketing or advertising purposes.
## Procedure
1. Open the global account for which you'd like to enable analytics. If you are the Global Account Owner and analytics has not yet been enabled, a dialog box will automatically appear when you access the global account. Here you can enable analytics by clicking "Allow for this Global
Account." You can also choose to no longer see this information or decide later following the steps below.
2. Navigate to the global account settings by clicking  (Global Account Settings) .
3. Select Consent Management .
4. Toggle the button for Help improve the BTP cockpit experience .
5. Save your changes.
## Results
After you have enabled analytics in the global account, each global account user must also provide their consent before anonymized usage data is sent to SAP. All users of a global account can change their consent choice at any time by accessing Cookie Preferences in the Legal Information menu located in the lower left. Global account administrators can also update or withdraw global account consent at any time in the global account settings.
## Related Information
SAP BTP Cookie Statement
<!-- image -->
SAP BTP Cockpit Privacy Statement