orkungedik/SAP-basis-dataset huggingface dataset:
## 6.3.1.19.11.1  Partitioning a Large HANA Table
Break down large columnar tables into partitions before the SAP HANA database threshold of two billion records per table is reached.
## Procedure
1. On the SAP Fiori launchpad of your ABAP environment, search for the Partition HANA Tables app.
2. To search for tables that contain a large number of records, enter your search criteria.
By default, the search criteria include the table name, the number of records, the total memory in MB and the number of partitions. If you want to include other search criteria, choose the Adapt Filters button.
3. Choose the Go button.
A list of tables that match the search criteria and that are eligible for partitioning is displayed, such as your own tables or tables released for partitioning by SAP . You can identify large tables in this list by checking the number of records and the total memory of the individual tables.
##  Note
You can add or remove columns in the list by choosing the Settings button.
4. Choose the table that you want to partition and choose the Partition Table button.
5. In the Change Partitioning Schema dialog box, select the partitioning key and enter the number of partitions that you want to create. Then choose Partition Table .
6. In the Confirm Table Partitioning dialog box, choose OK .
A background job is scheduled on the backend system that carries out the table partitioning.
7. To check whether the job has finished and your table was partitioned successfully, refresh the list of tables by choosing the Go button.
##  Note
You can always undo the partitioning of a table by choosing a partitioned table in the list and then choosing the Merge Partitions button. All partitions of this table will then be merged back into one partition.
## 6.3.1.19.12  ABAP Runtime Errors
## App ID: F7770
With this app, you can display and analyze the ABAP runtime errors that have occurred in your current tenant.
## Key Features
This app provides the following key features:
- List of all ABAP runtime errors that have occurred in your current tenant, which you can personalize
- Display of summary information, the source code, and the call stack for each ABAP runtime error that has occurred
- Option to navigate to ABAP development tools for Eclipse (ADT) to fix the error or to display the error in the Web browser (HTML)
## Supported Device Types
- Desktop
- Tablet
## Component for Customer Incidents
If you need support or experience issues, please report an incident under component BC-OP-MON .
## 6.3.1.19.13  HANA Memory Analysis
App ID: F8727
With this app, you can get an overview of the memory consumption of the HANA memory components over time. This helps you to understand how the SAP HANA database requests, uses and manages memory, which is crucial to understand how the system workload is processed.
## Key Features
This app provides the following key features:
- Identification of the components in your HANA memory that approach the critical memory limit that leads to botthenecks in your HANA memory
- Overview of the total memory consumption of column store and row store tables
- Overview of the content of the SQL plan cache
## Supported Device Types
- Desktop
- Tablet
## Component for Customer Incidents
If you need support or experience issues, please report an incident under component BC-OP-MON .
## 6.3.1.19.14  SQL Statement Analysis
App ID: F8784
With this app, you can analyze the performance and resource consumption of SQL statements within a selectable time range.
## Key Features
This app provides the following key features:
- List of the most expensive SQL statements in the SQL plan cache
- Display of the application/execution sources of the SQL statement with navigation links to the source code location
- Historical overview of performance metrics such as execution time and CPU time
- Download of PlanViz (PLV) files for analysis with the SAP HANA SQL Analyzer for Visual Studio Code
## Supported Device Types
- Desktop
- Tablet
## Component for Customer Incidents
If you need support or experience issues, please report an incident under component BC-OP-MON .
## 6.3.1.20  Manage Banks - Master Data
App ID: F6437
With this app, you can display and create master data for the banks your company, your business partners, customers, and your suppliers use to conduct business.
## Key Features
You can use this app to:
- Display banks and view their basic information, such as bank name, SWIFT/BIC code, bank number and address information.
- Create and edit both standard banks and internal banks. For more information about the bank categories the app supports, see Banks and Bank Categories.
- Create and edit international address versions. For more information, see International Address Versions.
##  Note
Additional features relating to Cash Management can be accessed in app Manage Banks - Cash Management . For more information, see Manage Banks - Cash Mangement under Feature Comparison for Bank Management Apps .
##  Note
This app contains in-app help for key fields and concepts. To display the help while working in the app, press F1 or choose the question mark displayed in the app header.
In addition, following technical features and options are supported:
- Banks can be replicated to other systems using SAP Master Data Integration. For more information, see Master Data Replication Using SAP Master Data Integration (Related Links).
- Banks can be imported from external files with other app Import Bank Directories . For more information, see Uploading Bank Data (Related Links).
## Access Information
For information on what business role and business catalog need to be assigned to your user to access the app, see the overview table in the chapter Applications for General Functions for Key Users.
## Supported Device Types
- Desktop
- Tablet
## Component for Customer Incidents
If you need support or experience issues, please report an incident under component CA-BK-BNK ( Bank Master Data ).
## Related Information
Master Data Replication Using SAP Master Data Integration
## 6.3.1.21  Translation
Maintain Translations [page 2901]
## 6.3.1.21.1  Maintain Translations
The Maintain Translations app provides an easy way to translate developer extensions into other languages.
## Context
You've built a developer extension and would now like to translate it into other languages. The Maintain Translations app allows you to select your text sources and generate an XLIFF (1.2) file containing the translatable texts as well as useful notes on them. XLIFF (XML Localization Interchange File Format) is a standard used in localization. The XLIFF file can then be forwarded to a dedicated translator or translation agency. Once the XLIFF file has been translated, you can use the Maintain Translations app to upload it and publish the translated texts into your system.
## Prerequisites
The following business catalogs are required:
Business Catalogs
| Primary                             | Secondary                                |
|-------------------------------------|------------------------------------------|
| SAP_A4C_BC_DEV_TRA_PC               | SAP_A4C_BC_TRN_MNG_PC                    |
| (for the Maintain Translations app) | (required to create transport requests)  |
|                                     | SAP_A4C_BC_TRN_REL_PC                    |
|                                     | (required to release transport requests) |
<!-- image -->
- Create a Translation Project [page 2903]
- Select Your Text Sources [page 2904]
- Select Your Source and Target Language [page 2906]
- Generate and Download the XLIFF File [page 2906]
- Upload and Publish the Translated XLIFF File to the System [page 2907]
## Key Features
You can use this app to:
- generate an XLIFF file of the texts that need to be translated.
- publish the translated texts to the system.
##  Note
If you want to have your texts translated by SAP , you can use the SAP Translation Hub. For more information, see SAP Translation Hub.
## Supported Device Types
- Desktop
## Component for Customer Incidents
If you need support or experience issues, please report an incident under component BC-DOC-TTL-MTR .
## 6.3.1.21.1.1  Create a Translation Project
## Context
You want to translate your developer extension. Before you can select your text sources and target languages, you need to create a translation project.
##  Note
Please assign the business catalog SAP\_A4C\_BC\_TRN\_MNG\_PC to ensure that changes can be recorded on transport requests.
## Procedure
1. Open the Maintain Translations app.
2. Click + (Create) to create a new translation project.
3. Fill in an identifier for your project, a name and description, and the name of the package that should contain your translation project.
4. Click Create at the bottom right of your screen.
5. You now need to add your translation project to a transport. You can either use an existing transport request that matches the transport target of the package you have selected for the translation project, or create a new one by clicking Create . Save your changes by clicking Select .
## Results
Your project has now been created and added to the overview list.
## Related Information
Select Your Text Sources [page 2904]
## 6.3.1.21.1.3  Select Your Source and Target Language
## Context
Select your source language as well as the languages you want to translate your texts into.
## Procedure
1. In the Maintain Translations app, open the project for which you want to select the source language and target language. You can choose to select either a single language or more than one language.
2. Scroll down to Translations and click Create .
3. Select a Source Language and Target Language from the dropdown menus and confirm with Create .
##  Note
You can select from all of the languages that are installed in the system. In case of ABAP repository objects and text pools, it's only possible to maintain translations for languages other than the original language.
Note that deleting a previously created translation entry for a given source and target language pair will only delete the corresponding entry in the translation project. Already published texts for the target language of the translation will not be deleted from the system.
4. A new entry has now been added to the list.
5. Repeat these steps for all source and target languages.
## 6.3.1.21.1.4  Generate and Download the XLIFF File
## Context
You can generate an XLIFF file for your source and target language(s) that you can download and send to your dedicated translator or translation agency.
## Procedure
1. In the Maintain Translations app, open the project you want to have translated and scroll down to Translations .
2. Select the entry for the source and target language for which you want to generate the XLIFF file.
3. Navigate to Download . Here you can select whether the XLIFF file should contain all texts ( All T exts ) or only those texts that were changed since you last published a translated XLIFF file in these languages ( Changed Texts ). If this is the first time you are generating an XLIFF file for the project in this target language, choose All T exts .
The XLIFF file will now be downloaded to your computer. You can send it to your dedicated translator or translation agency to be translated.
## Related Information
Upload and Publish the Translated XLIFF File to the System [page 2907]
## 6.3.1.21.1.5  Upload and Publish the Translated XLIFF File to the System
## Context
Your texts have been translated and a new XLIFF file has been sent back to you. You can now upload and publish the translated texts into the system. Here's how:
## Procedure
1. In the Maintain Translations app, open your project and scroll down to Translations .
2. Select the entry for the source and target language for which you want to upload and publish the translated XLIFF file.
3. Click Upload .
4. Search for the translated file and confirm with Upload .
5. Now the translations have been uploaded to the system. They still need to be published, however. Select the entry and click Publish .
6. Select a transport to which you want to add the corresponding language (LANG) transport entries or R3TR TABU entries (in case of text tables) and click Select .
7. Your translations have now been published.
## 6.3.1.22  Software Component Lifecycle Management
The software component lifecycle management allows you to manage the lifecycle of software components that are available in your ABAP environment landscape.
## Purpose
For the lifecycle management of software components you can use the app Manage Software Components in your launchpad that displays available software components, and imports them to service instances in your ABAP environment landscape. With the app, you can create new software components and delete them. Due to similarity to the Git protocol and its workflows, the following documentation uses the term pull as synonym for import .
One software component is comparable to a repository in Git. These "repositories" are centrally stored in separate units and cannot be referenced by other software components, which means the transport of development objects between the components is not possible. All software components are managed by SAP.
Once you have pulled a new software component to a service instance, a new structure package is created. The structure package name corresponds to the software component name. A software component itself is developed in ABAP packages in ABAP Developments Tools (ADT). The development objects are then uploaded to the structure package, and the software component is made available for the import to other service instances.
##  Note
In your system you will see all software components linked to the same global account that is the relevant layer for software component access control. Furthermore, only the global account is relevant for the visibility of the software components. Region or infrastructure provider do not matter. You only need to ensure that all systems are created within the same global account.
This is contrary to the overall SAP approach, where you can use the subaccount level inside a global account as a relevant access control layer (entity separation).
##  Caution
It is strongly discouraged to perform ABAP cloud development on a software component across multiple development systems. The reason for this is the potential for critical merge conflicts. When multiple developers work on the same software component simultaneously, edit it in different development systems, and release the transport requests afterward, inconsistencies and conflicts can arise in the target system.
This can lead to significant problems in the further development and maintenance of the software. It can even result in data loss. To avoid these issues, performing ABAP development on a software component in only one development system is highly recommended.
## Related Information
Manage Software Components [page 2914]
## 6.3.1.22.2  Manage Software Components
You can use this app to create, display, clone, delete and configurate software components in your ABAP environment landscape. Moreover, you can pull (import) changes from the central software component into other instances.
## Purpose
This app allows you to create a software component on a service instance and make with a 'Clone' and import changes (=commits = transport requests) on other instances after an initial clone using a 'Pull'.
## Key Features
You can use this app to:
- display available software components
- create new software components
- pull software components and display pulls
- delete software components
- display logs for performed actions like Clone, Pull, and other
- create and delete branches
- display pushed commits (= released transport request)
- create and delete tags on commits
- configure the repository role (Source or Target)
- enable or disable a rollback mechanism for failed pull operations
In addition, the app supports the integration with Git.
## Supported Device Types
- Desktop
- Tablet
- Smartphone
## Related Information
Display Software Components [page 2915] Create Software Components [page 2916] Pull Software Components [page 2918] Delete Software Components [page 2921]
## 6.3.1.22.2.1  Software Components
## 6.3.1.22.2.1.1  Display Software Components
## Context
You want to see which software components exist in the global account and which are already available locally, meaning in a Cloned state. T o display available software components, perform the following steps:
## Procedure
1. Open the Manage Software Components Fiori app to view all created software components in the global account.
2. Click on a software component to display more detailed information.
## Table Explanation
| Column                 | Description                                                                                                                                                    |
|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Name                   | Nameof the software component that has to be unique per service instance. The maximum length of the name is restricted to 18 characters including a namespace. |
| Description            | Description of the software component, which can only con- tain 60 characters.                                                                                 |
| Type                   | Type of the software component. The software component must either be Development or Business Configuration .                                                  |
| Checked Out Branch     | The name of the branch that is currently checked out (ac- tive). Empty if not cloned yet.                                                                      |
| Git Repository URL     | If a customer-managed Git repository is used with the Bring- your-own-Git feature, the repository URL will be displayed.                                       |
| Cloned                 | Shows whether or not the software component has been cloned on the current system instance.                                                                    |
| Relative Creation Date | Date and time when the software component was created, relative to the current date and time, e.g., '10 days ago'.                                             |
| Column          | Description                                                                                                 |
|-----------------|-------------------------------------------------------------------------------------------------------------|
| Created On      | Date and time when the software component was created.                                                      |
| Created By      | Email address of the business user who created the software component.                                      |
| Changed On      | Date and time when last changes were made to the software component.                                        |
| Changed By      | Email address of the business user who performed the last changes on the software component.                |
| Repository Role | Shows the selected role of the software component in the current system instance. Either Source or Target . |
## 6.3.1.22.2.1.3  Clone Software Components
## Context
If a software component is not locally in your system yet, you will first need to clone it once to import it into your system.
You can now deactivate the rollback mechanism for clone actions in the Manage Software Components Fiori App. The clone rollback should only be deactivated in exceptional cases.
Example of a use case: If you have a faulty remote repository (software component) but no development system on which the repository (software component) is still available locally. Then you need a way to clone the faulty software component and fix the errors.
##  Note
Cloning a software component is only necessary once per system instance.
## Procedure
1. Go to the details page of the software component you would like to clone.
2. Click Clone .
3. A pop-up opens. You can now select which branch you would like to import. If the software component does not have branches yet, the master or main branch (dependent on when the repository was created) is automatically selected. Select By Tag if you want to clone a specific git tag, which has been assigned to a commit. Select By Commit if you want to clone a software component with a specific commit ID. Confirm by clicking Clone .
##  Note
There is no input validation for the entered values for the options By Tag and By Commit . If the entered values are not valid the cloning process will start, but will be shown as failed in the end of the cloning process. In this case, the clone Latest option is automatically called as a fallback. With this, the repository is still useable, but not in the orginally requested version.
##  Note
If the initial clone of a software component runs into errors, the partly imported objects will be removed again from the system instance and the system will be kept clean. The clone rollback is now available for all system types.
4. The software component with the selected branch is now imported into your current system instance. The Clone button turns into a Pull button. From now on, you can use it to pull (remotely available) changes of your software component to your system.
##  Note
It is recommended to clone multiple software components one by one. Please clone software components with objects that are reused by other components first.
## Related Information
Pull Software Components [page 2918]
## 6.3.1.22.2.1.6  Display the Action History
## Context
You want to see which actions were already executed for a specific software component. To display the action history, perform the following steps.
## Procedure
1. Open the Manage Software Components Fiori app.
2. Select the software component you are interested in.
3. Scroll down to the section History to display the table.
## Table Explanation
| Column          | Description                                                                                                                      |
|-----------------|----------------------------------------------------------------------------------------------------------------------------------|
| Action          | Type of action that was executed. This could be a Create Repository , Delete Repository , Checkout , Pull , Create Tag and more. |
| BranchName      | Nameof the branch that was used for this action, e.g., the branch that was check out (switched to).                              |
| Status          | This attribute indicates whether the action is currently run- ning, was successfully completed, or encountered errors (stopped). |
| Started By      | Nameof the user who executed the action.                                                                                         |
| Short Commit ID | ID of the Commit that was used for this action, e.g., the commit that was pulled.                                                |
| Tag             | Nameof the tag that was used for this action.                                                                                    |
| Start Time      | Date and time when the action was started.                                                                                       |
| Change Time     | Date and time when the status (or executed step) of the action was changed.                                                      |
| Column             | Description                                                                                                                              |
|--------------------|------------------------------------------------------------------------------------------------------------------------------------------|
| Last Status Change | Date and time when the status (or executed step) of the action was changed in relation to thecurrent date and time, e.g., '10 days ago'. |
## 6.3.1.22.2.1.7  Display Open Transport Requests
Displaying Open Transport Requests: Use this to easily view all open transport requests for a specific software component. It provides the unique identifier, description, owner, and last update of each request.
## Context
To view all open transport requests for the selected software component on the current system instance, follow these steps. Please note that open transport requests from other system instances will not be displayed.
## Procedure
1. Open the Manage Software Components Fiori app.
2. Select the software component you are interested in.
3. Scroll down to the section Open Transports to display the table.
## Table Explanation
| Column            | Description                                                           |
|-------------------|-----------------------------------------------------------------------|
| Transport Request | ID of the ABAP transport request.                                     |
| Description       | Description of the ABAP transport request.                            |
| Owned By          | The name of the ABAP user who currently owns the trans- port request. |
| Updated At        | Date and time of the most recent change to the transport request.     |
## Navigate from Transport Request to ABAP Development Tools for Eclipse
You can navigate to the open transport request in ABAP development tools for Eclipse by clicking on the transport request in the software components application table. This link opens up a popup.
Here, you can click on the TransportRequest button to diyplay the respective tansport request in ABAP development tools for Eclipse.
In case nothing opens up when clicking on TransportRequest , the following must be activated in ABAP development tools for Eclipse:
ABAPDevelopmentTools &gt; Settings &gt; General &gt; Link Handlers &gt; enable ADT Scheme entry . The link can then be opened.
## 6.3.1.22.2.1.8  Configure Software Components
## Context
You can configurate software components in the Repository Settings , which can be opened by clicking on the Settings button.
## Key Features
You can do the following adjustments to the selected software component:
- Repository Role: Use the repository role to configure how transport requests behave when they're released. If the option Target is selected, the transport requests will not be pushed to the remote repository. However, if the Source option is selected, the transport request can be pushed to the remote repository.
- Rollback Mechanism: This rollback mechanism can be enabled and disabled. If enabled, only valid commits can be imported in the repository. If disabled, all commits can be imported even if they are invalid. For more information about
- this mechanism, see: Pull Software Components [page 2918].
- Update Credentials (BYOG software components only):
- Use this option to update your Git user credentials that were saved when the software component was cloned. This option is enabled only for Bring Your Own Git components that have already been linked to a Git repository. For more information on that, see Bring Your Own Git [page 2936].
## 6.3.1.22.2.2  Branches
## 6.3.1.22.2.2.2  Create a Branch
## Context
You want to create a new branch for your software component.
## Procedure
1. Open the Manage Software Components Fiori app.
2. Choose the software component you want to work on.
3. Navigate to the section Branching and click on Create .
4. Choose a name for your new branch and select the parent branch from the drop down menu.
5. Confirm with Create . You can also create a branch based on a specific commit state. This referenced commit must be available commit IDs should only be used if the software component has already been pulled. Otherwise, the long ID
in the current system, i.e. included in the currently selected branch. To do this, simply fill in the Commit ID in the Create New Branch popup. The commit ID can be provided in short or long format. Note that short needs to be used.
##  Note
When you delete a branch and recreate it with the same name, the creation will be denied with an error popup saying "Branch cannot be recreated". As a consequence, a branch name has to be unique once it has been used. Please choose another name in that case.
6. Refresh the page. Your new branch has now been created and added to the table.
## 6.3.1.22.2.2.3  Switch a Branch (Checkout)
## Context
You previously created a new branch and added it to the table. To learn how to create a new branch, please navigate to the previous page. Now you want to work on the new branch by checking it out. Please be aware that a new checkout is not possible while a checkout or pull is already in progress.
##  Note
All objects in the target branch will overwrite existing objects in the system without further notice. It is important to ensure that all open transport requests in the current branch are released before switching to a new branch.
## Procedure
1. After you created a new branch and refreshed the page, you navigate to it.
2. Choose the Checkout button to switch to this new branch.
## 6.3.1.22.2.2.5  Delete a Branch
##  Caution
## Branch Deletion :
While it is possible to delete branches, please consider the possible negative effects of branch deletion, like losing the commit history.
Please make sure that the branch you are deleting is no longer in use on other systems. If you delete the branch while it's in use in other systems, this code can no longer be released there, even if there are open transport requests.
The branch will be deleted locally as well as on the remote repository. After the branch deletion, a pull of this branch is no longer possible on all system instances.
## 6.3.1.22.2.3  Commits
## 6.3.1.22.2.3.1  Display Commits
## Context
You want to view all commits of a branch. To display the list of commits, follow these steps:
## Procedure
1. Open the Manage Software Components Fiori app.
2. Select the software component you are interested in.
3. Scroll down to the section Branching to display the table.
4. Select the branch you are interested in.
5. Scroll down to the section List of Commits to display the table.
## Table Explanation
| Column              | Description                                                                                                                                    |
|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------|
| Pulled              | Shows if the changes of a commit are in the current system instance. Either Yes or No .                                                        |
|                     |  Note If a branch is not active, all commits are indicated as No , despite the commit may also be in the commit history of the active branch. |
| Short Commit ID     | ID of the commit in short form.                                                                                                                |
| Message             | Commit message that begins with the transport request ID followed by the transport request descirption.                                        |
| Author              | Commit author, meaning the e-mail address of the ABAP business user (CB-user) that owned and released the trans- port request.                 |
| Pushed to Remote    | Relative date and time when the transport request was re- leased from the source system and therefore pushed to the remote repository.         |
| Pushed to Remote On | Date and time when the transport request was released from the source system and therefore pushed to the remote repo- sitory.                  |
| Tag                 | Shows the last tag name if assigned.                                                                                                           |
| Tag Description     | Shows the last tag description if assigned.                                                                                                    |
| Tagged By           | Shows the last tag creator if assigned.                                                                                                        |
## 6.3.1.22.2.3.2  Display Commit Objects
## Context
You want to view all objects that were changed with a specific commit. To display the list of objects, follow these steps:
## Procedure
1. Open the Manage Software Components Fiori app.
2. Select the software component you are interested in.
3. Scroll down to the section Branching to display the table.
4. Select the branch you are interested in.
5. Scroll down to the section List of Commits to display the table.
6. Select the commit you are interested in.
7. Scroll down to the section Committed Objects to display the table.
## Table Explanation
| Column      | Decsription                                                                                               |
|-------------|-----------------------------------------------------------------------------------------------------------|
| Object Type | ABAP object types like CLAS , INTF , APIS and many oth- ers. For more information, see ABAP Object Types. |
| ObjectName  | Nameof the ABAP object that was touched.                                                                  |
| Action Type | Shows what kind of action was performed on the object. Can be either Created , Modified or Deleted .      |
## 6.3.1.22.2.4  Tags
## 6.3.1.22.2.4.1  Create a Tag
## Context
You can assign a tag name and tag description to individual commits.
## Procedure
1. In the Manage Software Components app, open your software component.
2. Navigate to a branch. Commits on this branch are displayed in the List of Commits .
3. Select a commit and click Add Tag to add a tag name and a tag description.
4. (Optional) Navigate to the Tagging tab of your software component to see a table listing all the tags on the branch that is currently checked out/active. Log entries for the creation and deletion of tags are also displayed in the Recent Actions table in the History tab.
##  Note
Note that a commit can have multiple tags assigned to it. There is no restriction on how many tags a commit can contain.
## 6.3.1.22.2.4.2  Display Tags
## Context
You want to view all tags that are assigned to commits of all branches, independently of what branch is active. To display the list of tags, follow these steps:
## Procedure
1. Open the Manage Software Components Fiori app.
2. Select the software component you are interested in.
3. Scroll down to the section Tagging to display the table.
## Table Explanation
| Column      | Description                                             |
|-------------|---------------------------------------------------------|
| Tag         | Nameof the tag assigned to a commit                     |
| Description | Description of the tag assigned to a commit.            |
| Commit ID   | ID of the commit the tag is assigned to.                |
| Created On  | Date and time when the tag was created.                 |
| Created By  | Email address of the business user who created the tag. |
| Column     | Description                                                                                  |
|------------|----------------------------------------------------------------------------------------------|
| Changed On | Date and time when last changes were made to the software component.                         |
| Changed By | Email address of the business user who performed the last changes on the software component. |
## 6.3.1.22.2.4.3  Delete Tags
## Procedure
1. Open the Manage Software Components app.
2. Choose the software component where you want to delete the tag.
3. Scroll down to the section Tagging to display the table.
4. Here, you can select the tag you want to remove and click the delete button.
## 6.3.1.22.3  API for Managing Software Components
You can use the MANAGE\_SOFTWARE\_COMPONENTS API to work with software components on SAP BTP ABAP environment systems. The MANAGE\_SOFTWARE\_COMPONENTS API belongs to the communication scenario SAP\_COM\_0948 and is an integral part of the partner add-on build pipeline.
## 6.3.1.22.3.1  Cloning Software Components to an ABAP Environment System
- You have an ABAP environment system.
- You have created a communication user as described in How to Create Communication Users.
- You've created a communication system as described in How to Create Communication Systems.
- You've created a communication arrangement as described in How to Create a Communication Arrangement.
- You have selected the communication scenario SAP\_COM\_0948 for your communication arrangement and have mapped it to your communication system.
If a software component is not in your system yet, you will first need to clone it once to import it into your system. Please note that you can clone a software component only once into your system.
## 1. Authentication on the server
The first step serves the authentication on the server. The response header contains an x-csrf-token , which is used as authentication for the POST request following in step 2.
GET /sap/opu/odata4/sap/a4c\_mswc\_api/srvd\_a2x/sap/
manage\_software\_components/0001 HTTP/1.1
Accept: application/json
X-Csrf-Token: fetch
Host: host.sap
Response
HTTP/1.1 200 OK
<!-- image -->
```
X-csrf-token: xCsrfToken that was retrieved in the first request in the header parameters. The software component is passed in the path of the request URL. The branch you want to clone is passed in the body of the request. If you don't enter a branch name, the main branch is automatically selected. Alternatively, you can clone a specific tag or commit ID by entering the tag name or commit ID. Make sure that the tag or commit ID exists on the branch. If that's not the case, no clone action will be executed.
```
## 3. Tracking the Status of the Action
To track the status of the action, you can do a GET request using the UUID contained in the response.
```
 Sample Code Request GET /sap/opu/odata4/sap/a4c_mswc_api/ srvd_a2x/sap/manage_software_components/0001/Actions/96bbf3e1-5202-1edead8e-b46db5437410 HTTP/1.1 Accept: application/json Host: host.abapcp.int.sap
```
The response contains the same entity as the second request. The action is successful, when the status in the response body has the value S . The status description status\_descr will then return Successful . In case of an error status will have the value E and status\_descr the value Error .
## 6.3.1.22.3.2  Pulling Software Components to an ABAP Environment System
- You have an ABAP environment system.
- You've created a communication user as described in How to Create Communication Users.
- You've created a communication system as described in How to Create Communication Systems.
- You've created a communication arrangement as described in How to Create a Communication Arrangement.
- You have selected the communication scenario SAP\_COM\_0948 for your communication arrangement and have mapped it to your communication system.
- You have cloned the software component to the ABAP Environment system. See Cloning Software Components to an ABAP Environment System.
You can use the communication scenario SAP\_COM\_0948 to pull software components to an ABAP environment system.
## 1. Authentication to the server
The first step serves the authentication on the server. The response header contains an x-csrf-token , which is used as authentication for the POST request following in step 2.
```
 Sample Code Request GET /sap/opu/odata4/sap/a4c_mswc_api/srvd_a2x/sap/ manage_software_components/0001 HTTP/1.1 Accept: application/json X-Csrf-Token: fetch Host: host.sap Response HTTP/1.1 200 OK X-csrf-token: xCsrfToken
```
## 2. Pull a Software Component
To trigger the pull of a software component, you need to insert the x-csrf-token that was retrieved in the first request in the header parameters. The software component you want to pull is passed in path of the request URL.
```
 Sample Code Request POST /sap/opu/odata4/sap/a4c_mswc_api/srvd_a2x/sap/ manage_software_components/0001/SoftwareComponents/%2FDMO%2FCOMPONENT/ SAP__self.pull HTTP/1.1 Accept: application/json X-Csrf-Token: {{xcsrfToken}} Host: host.abapcp.int.sap Content-Length: 39 { "commit_id": "", "tag_name": "" } Response HTTP/1.1 200 OK Content-Type: application/json { "@odata.context": "../$metadata#Actions/$entity", "@odata.metadataEtag": "W/\"20240111143934\"", "uuid": "763eca2a-340b-1eee-ad8e-c864d7a77c38", "sc_name": "/DMO/COMPONENT", "import_type": "Pull", "branch_name": "master", "namespace": "", "status": "Q", "status_descr": "Scheduled", "criticality": 0, "user_name": "WebAPI - CC0000000009", "commit_id": "", "tag_name": "", "relative_date_change_time": "", "change_time": "2024-01-16T13:50:54Z",
```
```
"start_time": "2024-01-16T13:50:54Z", "execution_mode": "", "import_mode": "", "SAP__Messages": [] }
```
## 6.3.1.22.3.3  Working with Branches on a Software Component
- You have an ABAP environment system.
- You've created a communication user as described in How to Create Communication Users.
- You've created a communication system as described in How to Create Communication Systems.
- You've created a communication arrangement as described in How to Create a Communication Arrangement.
- You have selected the communication scenario SAP\_COM\_0948 for your communication arrangement and have mapped it to your communication system.
- You have cloned the software component to the ABAP environment system. See Cloning Software Components to an ABAP Environment System [page 2939].
You can use the communication scenario SAP\_COM\_0948 to work with software components on a SAP BTP ABAP environment system.
## 1. Authentification on the server
The first step serves the authentication on the server. The response header contains an x-csrf-token , which is used as authentication for the POST request following in step 2 and 3.
```
 Sample Code Request GET /sap/opu/odata4/sap/a4c_mswc_api/srvd_a2x/sap/ manage_software_components/0001 HTTP/1.1 Accept: application/json X-Csrf-Token: fetch Host: host.sap
```
```
Response HTTP/1.1 200 OK X-csrf-token: xCsrfToken
```
## 2. Create a Branch
To create a branch, you perform a POST request on the Branches entity. In the header parameters, you should include the x-csrf-token that was retrieved in the first request. Fill in the following data in your request body:
1. sc\_name : the name of your software component
2. branch\_name : the name of your new branch
3. derived\_from : the branch that your new branch should derive from
## 
```
Sample Code Request POST /sap/opu/odata4/sap/a4c_mswc_api/srvd_a2x/sap/ manage_software_components/0001/Branches HTTP/1.1 Accept: application/json X-Csrf-Token: {{xcsrfToken}} Host: host.abapcp.int.sap Content-Length: 103 { "sc_name" : "/DMO/COMPONENT", "branch_name" : "feature", "derived_from" : "main" } Response HTTP/1.1 201 Created Content-Type: application/json { "@odata.context": "$metadata#Branches/$entity", "@odata.metadataEtag": "W/\"20240111143934\"", "sc_name": "/DMO/COMPONENT", "branch_name": "feature", "is_active": false, "criticality": 0, "delta": "Please checkout first", "delta_criticality": 0, "derived_from": "main", "name_of_new_branch": "", "commit_id": "", "commit_message": "", "last_commit_by": "", "relative_date_last_rem_commit": "", "last_commit_on": null, "commit_id_on_system": "-", "created_by": "CC0000000009", "created_on": "2024-01-16T14:00:00Z", "execution_mode": "", "import_mode": "", "SAP__Messages": [] }
```
## 3. Check Out a Branch
Simply creating a branch did not change the state of the system. In order to work with the newly created branch, you need to import the branch to the system. This action is called checkout branch . Y ou need to include the software component and the name of the branch in the path of the request URL.
## 
```
Sample Code Request
```
```
POST /sap/opu/odata4/sap/a4c_mswc_api/ srvd_a2x/sap/manage_software_components/0001/Branches/%2FDMO%2FCOMPONENT/ main/SAP__self.checkout_branch HTTP/1.1 Accept: application/json X-Csrf-Token: {{xcsrfToken}} Host: host.abapcp.int.sap Content-Length: 44 { "import_mode" : "", "execution_mode": "" } Response HTTP/1.1 200 OK Content-Type: application/json { "@odata.context": "../ $metadata#com.sap.gateway.srvd_a2x.a4c_a2g_mswc_api.v0001.ActionsType", "@odata.metadataEtag": "W/\"20240111143934\"", "uuid": "96bbf3e1-5202-1ede-ad8f-001e560df4e6", "sc_name": "/DMO/FCOMPONENT", "import_type": "Checkout", "branch_name": "main", "namespace": "", "status": "Q", "status_descr": "Scheduled", "criticality": 0, "user_name": "WebAPI - CC0000000009", "commit_id": "", "tag_name": "", "relative_date_change_time": "", "change_time": "2024-01-16T14:03:22Z", "start_time": "2024-01-16T14:03:21Z", "execution_mode": "", "import_mode": "", "SAP__Messages": [] }
```
## 4. Tracking the Status of the Action
To track the status of the action, you can do a GET request using the UUID contained in the response.
```
 Sample Code Request GET /sap/opu/odata4/sap/a4c_mswc_api/ srvd_a2x/sap/manage_software_components/0001/Actions/96bbf3e1-5202-1edead8e-b46db5437410 HTTP/1.1 Accept: application/json Host: host.abapcp.int.sap
```
The response contains the same entity as the second request. The action is successful, when the status in the response body has the value S . The status description status\_descr will then return Successful . In case of an error status will have the value E and status\_descr the value Error .
## 6.3.1.23  User Interface Monitoring
Display Launchpad Content Exposure Logs [page 2947]
## 6.3.1.23.1  Display Launchpad Content Exposure Logs
With this app, you can check the application log created when publishing launchpad content to SAP BTP. You can check, for example, when the publishing run started, if the publishing was successful or if there were any issues.
##  Note
Log entries about apps that are not exposed and have a severity level of Information do not indicate an error. Applications may not be exposed for various reasons. For example, inactive applications may not be exposed in either version of exposure, or apps without a tile may not be displayed in exposure version 2.
## Implementation Information
To use the app, you need the following:
- Business catalog: SAP\_CORE\_BC\_UI\_MON
- Business role: SAP\_BR\_ADMINISTRATOR
To get the key information, including all the technical data you need for the installation and configuration, go to the SAP Fiori apps reference library.
## Related Information
Create Communication Arrangement
## 6.3.1.24  Manage Security Audit Log
With this app, you can manage Security Audit Log related parameters.
## Key Features
You can use this app to:
- Each parameter can be active or inactive, so that changing the parameter value is possible without having the change immediately active
- Maintain parameter DELETE :
- Maintain the default audit log retention time in days. After the number of days the Security Audit Log Events will be removed from database to reduce the consumption of the SAP HANA DB storage. The
default retention period is 45 days. Confirm the default by activating the parameter DELETE , or define a custom retention period.
Mark the parameter you want to change and switch to Edit mode. Select the option for Parameter Status (active or inactive) and for Parameter Value . Save your settings.
## Access Information
For information on what business role and business catalog need to be assigned to your user to access the app, see the overview table in the chapter Applications for General Functions for Key Users .
## Supported Device Types
- Desktop
- Tablet
- Smartphone
## Component for Customer Incidents
If you need support or experience issues, please report an incident under component BC-SEC-SAL .
## Related Information
Manage Security Audit Log (Deprecated) [page 2948]