orkungedik/SAP-basis-dataset huggingface dataset:
## 6.3.1.3.4.3  Schedule Custom Code Analysis
Learn more about the Schedule Custom Code Analysis app.
## Purpose
The Schedule Custom Code Analysis app enables you to schedule projects created in the Custom Code Migration app as application jobs. With this functionality, the analyses can be performed once or periodically. The Schedule Custom Code Analysis app is available to all users that have access to the Custom Code Migration app and have been assigned the Project Manager - IT business role.
## Key Features
With this app you can schedule ABAP Test Cockpit (ATC) mass runs for your custom code migration project in a SAP BTP ABAP environment system through a predefined custom code analysis application job template.
## Access Information
For more information how to provide access to users and how to implement this app, see Enable Usage of the Analyze Custom Code App [page 2661].
## Component for Customer Incidents
BC-DWB-TOO-ATF
## Supported Device Types
- Desktop
## 6.3.1.4 Additional Software
Install Additional Software [page 2673]
## 6.3.1.4.1 Install Additional Software
With this app you can only display the list of the apps that are available for download. This helps you to better integrate your apps with other programs you need for your daily business.
## Key Features
You can use this app to:
- Download the current version of the SAP Cloud Print Manager

Tip
For more information, see the SAP Cloud Print Manager Quick Guide that you can call up directly in the application by clicking Help . This document is only available if you have installed SAP Cloud Print Manager.
- Download the current version of ABAP Development Tools
## Supported Device Types
- Desktop
## Component for Customer Incidents
If you need support or experience issues, please report an incident under component BC-CCM-PRN-OM .
## 6.3.1.5 Application Jobs
Find out more about application jobs in SAP and how they can be helpful.
Many business activities have to be run periodically. To avoid starting these activities manually each time, you can create application job templates and schedule them as application jobs in the Application Jobs app.
An application job template can be scheduled as an application job. In the scheduling dialog, you as a business user can determine a periodic start condition (such as every first Monday of the month at 1:00), and you can set appropriate parameter values for the application job execution. The application job will then be run automatically without further manual interaction, whenever the start condition is fulfilled.
SAP also offers the Application Job Templates app. In this app, you can create new templates by saving an existing template with new parameter values. You can also connect existing templates to multistep templates. Running a multistep template means running all steps sequentially.
Application Jobs [page 2674]
Application Job Templates [page 2679]
Maintain Job Users [page 2682]
## 6.3.1.5.1 Application Jobs
You can use this app to monitor all application jobs from all specialized application jobs apps (example: Schedule Overhead Accounting Jobs,...) that business users have scheduled. You can also cancel application jobs.
## Key Features
##  Note
You can use the scheduling, copying and restarting features in the Application Jobs app only if you have been granted the necessary authorization via a business role. For more information on how to get the necessary authorizations for this app, see Maintaining Authorizations [page 2678].
You can use this app to:
- Schedule jobs based on a job template: Select a job template, define the description, start date, start time and recurrence of the job, and enter job-specific selection criteria and parameters
- Work with personalized job templates: Create and personalize a job template, save personalized job template for later use, and share personalized template
##  Note
The parameters under Scheduling Information can't be saved as a part of a template.
- Schedule jobs with a custom factory calendar: In the Application Jobs app, define the scheduling information, change an existing calendar, create a new one, and define execution days
- Arrange job series that take different time zones into account
- Monitor jobs
- Display logs and results: You can navigate to application job logs and application job results by clicking on the icon in the Log or the Results column. The icon can be either an error icon, a success icon, or an info icon. Selecting the icon, you'll navigate to the specific logs or the specific results of the selected job.
- Copy a job
- Cancel a job
- Restart Job Chains
## Supported Device Types
- Desktop
- Tablet
## Component for Customer Incidents
If you need support or experience issues, please report an incident under component BC-SRV-APS-APJ .
## 6.3.1.5.1.1  Creating an Application Job
Find out how to create your own application jobs in the Application Jobs app.
## Context
You can use the Application Jobs app to schedule and monitor application-related jobs. If you have manual activities that you often need to do at a specific time, the app can reduce your workload by running these tasks smoothly in the background. You can plan regular jobs which allows you to concentrate on other tasks.
## Procedure
1. Open the Application Jobs app.
2. Choose Create to create a new application job.
3. Select a job template and enter a job name.
4. Specify your preferred scheduling options. You can define the recurrence of your job by selecting Define Recurrence Pattern .
5. In the next step, you can adjust the parameters of your application job.
6. You can choose to let the system check if your entries are consistent. If possible, the system fills in default values for the parameters. To choose this option, click Check .
7. You can choose to save the application job as a template, or manage your templates. To do so, select Template .
8. Finally, to schedule your application job, select Schedule .
## 6.3.1.5.1.2  Job Cancellation
Job cancellation details
A job can be canceled either by the system or by a user. If a job is canceled by the system, it gets the status Failed . If you want to cancel a job, please keep in mind that the system behavior depends on what exactly you want to cancel:
- If you cancel a single job with the status Scheduled , this job will be canceled and removed from the job list.
- If you cancel a single job with the status In Process , this job will be canceled, will get the status Canceled and will remain in the job list.
- If you cancel a job that has the status Scheduled and is a part of a job series, all jobs with the status Scheduled will be canceled and removed from the job list. All jobs with other statuses will remain in the list and won't be canceled.
- If you cancel a job that has the status In Process and is a part of a job series, a job with the status In Process will be canceled and will get the status Canceled . All other jobs of the series with other statuses will remain in the list.
To cancel a job, please select the job to be removed and choose Cancel from the main toolbar.
##  Note
Please note that the jobs with the status Finished cannot be canceled because they have already been run.
##  Note
You can choose to skip a single execution of a periodic job chain. To do so, select Skip . A skipped job can be restored by clicking Restore .
## Related Information
Application Jobs [page 2674]
## 6.3.1.5.1.3  Regular Job Deletion
Get an overview of the regular job deletion
All jobs that are not removed by a user remain in the system until a technical cleaning job runs. The time when this job is run by the system depends on the periodic granularity of the jobs that should be deleted. Currently, the following timeframes apply:
Regular Job Deletion
| Periodic Granularity of the Job to Be Deleted   | Job is Automatically Deleted After   |
|-------------------------------------------------|--------------------------------------|
| Not periodic                                    | 14 days                              |
| Minutes                                         | 7 days                               |
| Hours                                           | 14 days                              |
| Days                                            | Periodic value*24 days               |
| Weeks                                           | Periodic value*7*24 days             |
| Months                                          | Periodic value*31*24 days            |
| Every X week in every Y month                   | Periodic value*31*24 days            |
## Example
You have scheduled a job that runs every two weeks and ends after 20 runs. The first run starts in the calendar week 2 and ends in the calendar week 40. Each job run stays in the system for the certain retention time. Retention period is always set to 24 runs. Retention time=periodic value * retention periods * weekdays [days] = 2 * 24 *7 [days] = 336 [days] = 48 [weeks]. The first job run will be deleted a day after 48 weeks since this job run took place.
##  Note
This is the default behaviour. If the application chooses to have different schemes, this is documented in the application-specific documentation.
## 6.3.1.5.1.4  Restart Job Chains
Find out how to restart job chains.
When an application job or a chain of application jobs consisting of one or more steps has the status Failed , Canceled or User Error , you can restart it. T o do so, select the job and choose one of the following options from the drop-down menu:
- From Error Step: All steps before the error step will be skipped and all other steps (including the error step) will be executed.
- After Error Step. All steps before the error step including the error step will be skipped and all other steps after the error step will be executed. This option is not available for single step jobs.
The new job will be executed immediately with the original job user.
##  Note
You can't change the starting or application parameters.
## Related Information
Application Jobs [page 2674]
## 6.3.1.5.1.5  Maintaining Authorizations
Find out which authorizations you need to maintain in order to use the Application Jobs app.
## Context
To change access to the objects of other users used in the Application Jobs app, create a new business role assigning the business catalog SAP\_CORE\_BC\_APJ\_JCE to it. Y ou can modify the provided restriction types according to your needs.
## Procedure
1. Create a new business role assigning the business catalog SAP\_CORE\_BC\_APJ\_JCE to it. The restriction type Job Catalog Entry/Application Job Part contains the two fields Application Job Catalog Entry and Application Job Part . For more information, see Maintain Business Roles [page 2769].
##  Note
With this restriction type, you'll be able to provide the necessary authorizations for certain actions on the application jobs of other users that are based on a specified job catalog entry. You can display the result lists of these application jobs.
Alternatively, you can also create a display only-role using this restriction type.
2. Next, define your business role with the restriction fields Application Job Catalog Entry and Application Job Part mentioned above. To do so, select Maintain Restrictions . In the Application
Job Catalog Entry field, you can choose the job catalog entries, and in the Application Job Part field, you can choose for which job part access should be granted. You can choose the values JOB (Job Details), SPOOL (Result List), and APPLOG (Log) by clicking the Edit icon next to the fields.
3. If you want to have different business users for the job owner and the job user, the job owner needs the authorization to schedule the application job for the job user. In this case, the job owner needs the restriction type Create Application Jobs for Other Users .
4. Go back and select Save . Now, you've maintained your business role, and you can assign the role to a business user. For more information on authorizations, see 3028505 .
##  Note
The private templates of other users aren't shown in the Application Jobs app, even if the authorization to view these private templates was granted via SAP\_CORE\_BC\_APJ\_TPL . Y ou can view the private templates of other users only in the Application Job Templates app. For more information, see Application Job Templates [page 2679].
## Related Information
Maintain Business Users [page 2758] Maintain Business Roles [page 2769]
## 6.3.1.5.2 Application Job Templates
You can use this app to create your own application job templates. The application job templates consist of a set of parameters that you can set for the assigned job catalog entry. This app is mandatory to create multi-step templates which can then be submitted via the Application Jobs app. A multi-step template consists of several other templates that run in a series, one after the other. Each step could be a single-step template, or another multi-step template that was created with the Application Job Templates app before.
## Key Features
You can use this app to:
- Create and customize a job template
- Create multi-step templates
- Change the template parameters
- Transport job templates, if supported: For more information, see 2999966
- Display a list of templates you have read access to
- Display the layer code of the template:
- Global: a template with this layer code is predelivered by SAP and therefore can't be edited or deleted
- Private: a template with this layer code is visible for all users within the Application Job Templates and the Application Jobs apps, but only the author can edit or delete the template
##  Note
With the new restriction type, you can define a full authorization for job templates, such that a system administrator can display, change or delete private templates of other users
- Shared: a template with this layer code is visible to all users that have the required authorizations to use the Application Job Templates and the Application Jobs apps
- Reference: a template with this layer code is visible for all users within the Application Job Templates and the Application Jobs apps, but only the author can edit or delete the template. It can't be scheduled in the Application Jobs app. It can be used as a copy pattern to create other templates.
- Delete a job template
## Supported Device Types
- Desktop
- Tablet
## Component for Customer Incidents
If you need support or experience issues, please report an incident under component BC-SRV-APS-APJ .
## Related Information
Creating an Application Job Template [page 2680]
## 6.3.1.5.2.1  Creating an Application Job Template
Find out how to create your own application job templates in the Application Job Templates app.
## Context
You can use the Application Job Templates app to create a job template for a specific business purpose so that you can schedule concrete jobs by reusing the job template.
## Procedure
1. Open the Application Job Templates app.
2. Choose Create to create a new job template.
3. Enter a name and specify your preferred scheduling options.
4. Tick the Shared Template checkbox if you want other users to be able to view or edit the job template. If you share the template, all users who have access to the Application Job Templates app, and who have the appropriate authorizations, can make the same changes as you.
5. Select Maintain Steps and choose Add to add an existing template as step. This step can be repeated many times to create a multi-step template.
6. Click Save Job Template . Now, you can view each parameter of your selected templates in the Parameter Section and edit the values according to your needs.
7. If you are done editing, you can now choose whether to check your parameters, or display, save, or cancel your job template. When clicking Save to save your job template, you can choose to save and reload the page to be able to view the values you've entered previously by selecting Save and Reload . Mind that this may trigger a longer reload of new values. If you want to get back to the main page and continue working, choose Save and Back .
##  Note
If you want to schedule multistep templates with the Application Jobs app, you'll need the appropriate authorizations for all steps.
## 6.3.1.5.2.2  Maintaining Authorizations
Find out which authorizations you need to maintain in order to use the Application Job Templates app.
## Context
In order to grant access and authorizations to the Application Job Templates app, create a new business role assigning the business catalog SAP\_CORE\_BC\_APJ\_TPL to it.
## Procedure
1. Create a new business role assigning the business catalog SAP\_CORE\_BC\_APJ\_TPL to it. For more information, see Maintain Business Roles linked below.
2. (Optional) If you want to grant read or write access to templates of other users, select Maintain Restrictions to provide Write , Read , or No Access using the restriction type APPLICATION JOB TEMPLATE LAYER .
3. Go back to Save your template.
##  Note
You will always be able to see your own templates and the templates delivered by your software provider without having to maintain further authorizations.
##  Note
The possible values for the layer field are Global , Shared , and Private . These are described in Application Job Templates linked below. The restriction type Global is predelivered by SAP and therefore can't be edited or deleted, but you can modify the restriction types Shared and Private to your needs.
##  Note
If you want to schedule multistep templates with the Application Jobs app, you'll need the appropriate authorizations for all steps.
## Related Information
Maintain Business Users [page 2758]
Maintain Business Roles [page 2769] Application Job Templates [page 2679]
## 6.3.1.5.3 Maintain Job Users
With this app, you can change the owner and the user of application jobs that you've created from a job template. This can be helpful if, for example, a person changes the department within a company or leaves the company, and the corresponding business user has to be deleted.
## Key Features
You can use this app to:
- Change either the job owner or the job user of an application job, or change both
- Delete an application job
## Supported Device Types
- Desktop
- Tablet
## Component for Customer Incidents
If you need support or experience issues, please report an incident under component BC-SRV-APS-APJ .
## 6.3.1.5.3.1  Editing Job Users
Find out how to change the user of your application job, or delete your job.
## Prerequisite
Before changing the user of a job, ensure that the target user has the correct authorizations to run the job. Otherwise, the job will fail.
To be able to see the app, make sure that the target user is assigned to a business role that has the business catalog SAP\_CORE\_BC\_APJ\_USR\_PC included.
## Procedure
1. Open the Maintain Job Users app.
2. Select the scheduled jobs that you want to work with, and choose one of the following actions:
- Change Job Owner to change the owner of your application job
- Change Job User to change the user of your application job
- Change Job Owner and User to change both the owner and the user of your application job
- Delete to delete your application job
When clicking on an application job, you'll be navigated to the Details page of the Application Jobs app.
3. If you've decided to change the owner or the user of your application job, or if you want to change both, a dialog opens. Enter the new job owner and user by selecting them from the value help. Mind that in case of a job user change, you can only select users that have the appropriate start authorization for a job. Job owners don't need this authorization, but they need the restriction type Create Application Jobs for Other Users instead. For more information, see Maintaining Authorizations of the Application Jobs documentation. App-specific authorizations are not checked. You can choose to only display these users by filtering for Only Valid .
<!-- image -->
If a job owner is a communication user, the owner can't be changed, since the connection to the corresponding communication arrangement of the type SAP\_COM\_0064 would be broken.
4. You can change multiple application job owners and users at the same time. To do this, select all users you want to change and choose Change Job Owner and User . If the job owner differs from the job user, the job owner must have the appropriate authorization given by the restriction type Create Application Jobs for Other Users of business catalog SAP\_CORE\_BC\_APJ\_JCE .
5. You can choose to display the change history of your application job by selecting Change History . All changes that were made to the owner and user in the past are shown in the change history. The change history shows the user type, and the new and old user IDs. You can view who changed the user, and when it was changed. The type of change is shown, too.
6. You can delete multiple application jobs at the same time. To do this, select all jobs you want to delete and choose Delete .
You've now maintained your job user.
## Related Information
Application Jobs [page 2674]
Maintaining Authorizations [page 2678]
## 6.3.1.6.1 Business Configuration Change Logs
With this app, business process configuration experts can keep track of content changes in your business configuration tables. Table data change logs can be used to check when data was changed, which kind of data was changed, or by whom. This is made visible in a table.
## Access Information
To access the app, you need to have the following business catalog assigned to your user: SAP\_CORE\_BC\_BCT\_LOG\_PC - Business Configuration - Change Logs.
This business catalog is available in the business role template: SAP\_BR\_BPC\_EXPERT .
To display the change logs for tables, users must have the authorization for the object S\_TABU\_NAM with Display Change Documents for ACTVT and the name of the table for TABLE .
## Key Features
You can use this app to:
- Display which changes were made to the records of your business configuration tables.
- Display when changes were made to the records of your business configuration tables.
- Display who made changes to the records of your business configurations tables.
## Component for Customer Incidents
If you need support or experience issues, please report an incident under component BC-CUS-TOL-ALO .
## 6.3.1.6.1.1  Working in the Business Configuration Change Logs App
## Prerequisites
The Log Changes checkbox has to be enabled in the technical settings for the table:
- For tables delivered by SAP: SAP defines whether change logging is enabled.
- For tables you have created: You need to enable change logging.
##  Note
Log Changes checkbox can be enabled or disabled in the Technical Table Settings ADT editor by expanding the entry of your table in the project explorer.
## Displaying a Change Log
Find out how to display the change log of your business configuration tables.
## Procedure
1. Open the Business Configuration Change Logs app.
2. Use the search bar to find a configuration table. You can search based on the table name or a specified date range.
3. Select a configuration table to see its change log details.
4. You can filter the change log details based on criteria such as field name, changed date, changed by, and more.
## Download Change Logs
Find out how to display the change log of your business configuration tables.
## Procedure
1. Open the Business Configuration Change Logs app.
2. Select the button Download Change Logs . Once selected you will be navigated to the Business Configuration Change Logs Overview app.
3. Select Create to schedule a job.
4. Select a Job Template and a Job Name , then select Step 2 .
5. You can either start the job immediately by selecting it or select a specific start date and time. Select Step 3 to continue
6. In the Parameters section select an Evaluation Begin Date , Evaluation Begin Time , Evaluation End Date and an Evaluation End Time . All the change logs given in this time window will be downloaded.
7. To download the change logs for a specific user, provide their Username . When no username is provided, all change logs from every user will be downloaded
8. The Exclude Text Tables option allows to filter out the change logs for the text tables.
9. Once all the Parameters are entered, select Schedule to start the job immediately or at the provided time given at Step 5 .
## Result
In the Business Configuration Change Logs Overview app, you can see the scheduled jobs. Once the job is finished you can preview the change logs or download the change logs.
If you need support or experience issues, please report an incident under component BC-CUS-TOL-ALO .
## 6.3.1.6.3 Manage Number Range Intervals
You can use this app to get an overview of number range objects and maintain number range intervals.
## Key Features
You can use this app to:
- Display properties of number range objects
- Display, create, change and delete number range intervals
- Change the number range status of a number range interval
- Display the change history
## Supported Device Type
- Desktop
## Prerequisites
To access the Manage Number Range Intervals app, assign the SAP\_CA\_BC\_IC\_LND\_NUM\_PC (Number Range Management - Configuration) business catalog to a proper business role and - if required - restrict it to specific number range objects.
To maintain number range intervals and to create transport requests, assign business role BR\_BPC\_EXPERT .
For more information, see:
- Maintaining Number Range Intervals [page 2691]
- Changing the Number Range Status [page 2692]
- Checking Properties of a Number Range Object [page 2690]
## 6.3.1.6.3.1  Checking Properties of a Number Range Object
To check the properties of a number range object, proceed as follows:
1. Start the Manage Number Range Intervals app from the Business Configuration app group on thr fiori launchpad.
2. Choose a number range object from the list and click the arrow-button on the right-hand side of the entry. The Properties section is displayed.
##  Note
You can only display properties. You don't have the option of changing them.
The following parameters are displayed:
- Subobject exists: The number range object distinguishes between further subobjects.
- Year-Dependent: This parameter is set to Yes if the number range intervals are distinguished according to to-fiscals.
- Subobject as Prefix: This parameter is set to Yes if determined numbers consist of the prefix (name of subobject) and the numbers.
- Number of Digits: This parameter determines the length of an interval.
- Rolling: This parameter is set to No to prevent the number range object intervals from starting from the upper limit automatically.
- Buffering Type: This parameter shows whether main memory, parallel, or no buffering is supported.
- Number: In case of parallel and main memory, this parameter determines how many numbers are reserved in the buffer for the intervals.
- Warning at Remaining: This parameter displays the percentage of numbers remaining in a number range. When reaching the percentage in number assignment, a warning is given. Assuming an interval from 1 to 1000 and a percentage of 10 (%) is used, a notification will be triggered if number 900 has been reached.
You can maintain number range objects using the ABAP Development Tool (ADT) or APIs. For more information, see
- ADT:
Working with Number Range Objects
- API: Maintaining Number Range Objects
## 6.3.1.6.3.2  Maintaining Number Range Intervals
You can structure the defined character set of a number range object in intervals. For more information on intervals, see Intervals.
To maintain a number range interval, proceed as follows:
1. Start the Manage Number Range Intervals app from the Business Configuration app group on the fiori launchpad.
2. Choose a number range object from the list and click the arrow-button on the right-hand side of the entry. The Properties section is displayed.
3. In the Number Ranges section, press Create to create a new interval. Assign a two-character ID as interval number and a lower and upper limit. If the current number range object supports subtypes or is yeardependent, assign a subtype and a year accordingly.
##  Note
Don't set the External Interval flag if you want to use an internal number assignment. That means that during number determination within an application program using that interval, the number range framework automatically assigns a number from the associated number range object to the data record created by the user. Only digits are assigned from internal intervals of the number range object.
For an external number assignment, an application selects a number for a new data record by their own. This can be useful if you want more information to be included in the structure of the number. The number range framework then checks whether the selected number is in an interval of the number range object that is defined as external. However, it does not check whether this number has already been used. Digits and also letters and special characters are assigned from external intervals of a number range object.
4. Press Save to save the new interval.
If you want to delete an interval mark it by using the radio button and press Delete .
If you want to change an interval, open it by clicking the arrow-button on the right-hand side of the entry. Then press Edit if you want to change the limits or the external flag.
## 6.3.1.6.3.3  Changing the Number Range Status
The Number Range Status or Number Range Level is the last number used by an interval.
##  Note
Only change this number in case of inconsistencies.
To change the number range status, proceed as follows:
1. Start the Manage Number Range Intervals app from the Business Configuration app group on thr fiori launchpad.
2. Choose a number range object from the list and click the arrow-button on the right-hand side of the entry. The Properties section is displayed.
3. Choose a number range interval from the list and click the arrow-button on the right-hand side of the entry.
4. Click the Change Number Range Status button. In the pop-up, enter a new interval level an press Change Number Range Status .
## 6.3.1.6.5 Export Customizing Transports
With this app, business process configuration experts can manage business configuration changes recorded in requests.
Business configuration changes are recorded in requests, depending on the category to which the customizing objects belong. Unlike ABAP repository objects, customizing objects recorded in a request are accessible to other business users.
## Access Information
The following business catalogs are available to manage the customizing requests:
- Display/Edit/Delete: SAP\_CORE\_BC\_BCT\_TRN\_MNG\_PC - Business Configuration - Transport Management
- Display/Edit/Delete/Release: SAP\_CORE\_BC\_BCT\_TRN\_REL\_PC - Business Configuration - Transport Release Management
These business catalogs are contained in the business role template: SAP\_BR\_BPC\_EXPERT .
## Key Features
You can use this app to:
- Display a list of customizing requests
- Create new customizing transport requests
- Display the customizing tasks, objects, attributes, notes and logs of a customizing transport request
- Display the objects recorded in a customizing task
- Display the table keys recorded for an object
- Add notes to a customizing request
- Check customizing transport requests
- Release customizing transport requests
- Assign a transport request to your user
- Create tasks for other users
- Change the transport category
- Take over tasks and transports from other users and assign them to your user
- Check the consistency of all open requests
- Release all open requests
## Default Customizing Request
Since configuration changes recorded in requests of the type Customizing Request are not lockable, it might happen that several business users record their configuration changes in different requests.
Recording the configuration changes in different requests might create dependencies between these requests, however to avoid such dependencies, a new transport category is introduced.
Any new request created from this app is categorized as Default : In a client, there can be only one open default request of the type Customizing Request .
Business users can record their configuration changes to this default request to avoid any dependencies.
If you need to perform an emergency fix, record the configuration changes in a request which is not categorized as Default . Default requests are listed in the column Transport Category .
## Component for Customer Incidents
If you need support or experience issues, please report an incident under component BC-CUS-TOL-CTO .
## 2. Consistency check of all open requests.
- Consistency check is performed for all the open requests.
- If any error occurs in this phase, the message Error occurred in Check phase is displayed. This message appears when you select Release All &gt; Show Progress after the run is completed. Additionally the individual requests with error in the consistency check are also displayed. You can navigate to those requests to see the logs of the error messages.
## 3. Check for changes to open requests during the consistency check phase
- The open requests are checked for any modifications made during the consistency check phase. Ensure that no modifications are made to the open requests and no changes are recorded to them during the process.
- Changes to open requests, such as adding or deleting tasks under these requests or deleting any open requests, are not allowed during this process. This is because the dependency check errors have been suppressed with the assumption that the dependent requests are also released together. Therefore, changes to open requests could result in an inconsistent state.
- If any error occurs due to any open request being modified or changed during the consistency check phase, the message Error occurred in suppression of request dependency check errors is displayed. This message appears when you select Release All &gt; Show Progress after the run is completed. The message also contains a detailed description, which you can refer to.
## 4. Assign ownership of all open requests to your user (Assign To Me)
- All open requests that are not already owned by you will be assigned to your user.
- If any error occurs in this phase, the message Error occurred in Assign To Me phase is displayed. This message appears when you select Release All &gt; Show Progress after the run is completed. Additionally the individual requests with errors in assigning the ownership are also displayed. You can navigate to those requests to see the logs of the error messages.
## 5. Determining the sequence for releasing open requests
- The sequence for releasing open requests is determined.
- If any error occurs in this phase, the message Error occured in determination of release sequence for open requests is displayed. This message appears when you select Release All &gt; Show Progress after the run is completed. The message also contains a detailed description, which you can refer to.
## 6. Release of all open requests.
- In the final phase, all the open requests are released in the order determined in the previous phase.
- If any error occurs in this phase, the message Error occured in Release phase is displayed. This message appears when you select Release All &gt; Show Progress after the run is completed. Additionally the individual requests with an error during the release are also displayed. You can navigate to those requests to see the logs of the error messages.
##  Note
Consistency check gets triggered in thebackground and the UI shows the latest transport request status as soon as Release All is triggered. The UI gets refreshed everytime after certain interval showing the latest status. The transport with status Checking shows the request currently being processed.
As soon as the consistency check is complete, a momentarily message gets displayed at the bottom.
If the Release all is already running, you can't trigger another and it will give you an error message
## Release Request
1. Release any tasks belonging to your transport request. A request can't be released until all its tasks have been released.
2. Check the consistency of your request by triggering a release simulation: Select the request and click Release &gt; Check .
3. You can also release your request directly without triggering a simulation: Select the request and click Release &gt; Execute .
4. To refresh the status of a released or simulated request: Select the request with the status Checking or Release Started and click Refresh .
5. View the results of the simulation or direct release in the Logs tab.
<!-- image -->
## Merge Request
If there are dependencies between different requests or several business users have recorded their configuration changes in different requests, you can choose to merge these different requests into one.
1. Select the request you want to merge.
2. Select Merge .
3. In the selection dialog, enter the target request number to which the selected request should be merged, and click Merge .
<!-- image -->
##  Note
The configuration changes recorded in the request you selected to merge are copied to the target request. After merging, the previously selected request will be deleted.
## Create Copy
It can happen that for technical reasons, it's necessary for you to create a copy of an exported request. This can be the case if, for example, your exported request containing the business configurations didn't synchronize to the Git Repository. In order to synchronize these business configurations with the Git Repository again, a copy is needed.
1. Select the request you want to copy.
2. Click on Create Copy .
## Repository Id
You can export the business configuration recorded in a request to a specific software component by assigning the Repository Id when creating a request.
1. Select Create to create a new request.
2. Using the value help, check the allowed repository ids which can be assignet to the request.
3. Select the suitable repository id and save the changes.
## 6.3.1.6.5.2  Semantic Business Configuration Lock Token
When critical business configuration changes are made in a customizing tenant of the development system, a check is triggered in the test and production systems to ensure that the configurations can be changed consistently. To count as a consistent change, the new configuration must meet the following critera:
- It doesn't violate existing configurations or business processes in the production system.
- It can be imported into the test and production systems, offering the new or changed business processes.
If the new business configuration matches the existing configuration or application data, it generally returns either a SUCCESS or a ERROR messages. The SUCCESS status allows to save the business configuration in the customizing tenant of the development system. This business configuration can then be sent to the targeted test and production systems with a transport request to make the changes active. A Semantic Business Configuration Lock Token safeguards this verified configuration until the transport reaches the test and production systems.
This generic mechanism is defines into three phases:
1. Setting the Semantic Business and Configuration Locks After the checks are successful in the test and production systems, a lock is saved with the status Preliminary | On hold . Once the configuration changes are recorded to a transport and saved in the customizing tenant of the development system, the locks will be finalized and changed from Preliminary | On hold to Active in the test and production systems.
2. Checking the Business Processes for existing Locks
When a lock is set in the test and production system, all related business processes are checked for active locks. If a business process is blocked due to an existing lock, the user receives detailed information explaining why the process could not be completed as usual.
3. Release of Semantic Business &amp; Configuration Locks When an active lock exists, the business processes are blocked. To release this lock, import the transport
containing the critical configuration changes into the test and production systems. This import will successfully release the locks.
##  Note
Critical business configuration changes create a lock in the test and production systems, so these changes should no longer be imported into these environments. To resolve this, revert the configuration changes
in the customizing tenant of the development system, and then import the transport into the test and production systems to release the locks.
## 6.3.1.6.6 Maintain Customizing Translations
The Maintain Customizing Translations app provides an easy way to translate customizing extensions into other languages.
## Context
You've built a customizing extension and would now like to translate it into other languages. The Maintain Customizing 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 Customizing Translations app to upload it and publish the translated texts into your system.
## 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.
<!-- image -->
##  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.6.6.1  Create a Translation Project
## Context
You want to translate your customizing 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\_CORE\_BC\_BCT\_TRN\_MNG\_PC to ensure that changes can be recorded on transport requests.
## Procedure
1. Open the Maintain Customizing Translations app.
2. Click + (Create) to create a new translation project. Choose a project type from the dropdown.
3. Fill in an identifier for your project, a name, and a description.
4. Click Create at the bottom right of your screen.
5. You now need to add your translation project to a transport. You can create a customizing transport request by using the Export Customizing Transports app. For more information, see Export Customizing Transports [page 2695] .
## Results
Your project has now been created and added to the overview list.
## Related Information
Select Your Text Sources [page 2704]
## 6.3.1.6.6.2  Select Your Text Sources
## Context
Select the text sources that you want to have translated.
## Procedure
1. In the Maintain Customizing Translations app, open the project you want to add text sources to.
2. Scroll down to Text Sources and click Add .
3. Here you can select which text source types to add. The following text source types are supported:
- UI runtime adaptations
##  Note
Mind that only the translation of those UI runtime adaptations which have been recorded on a Customizing transport request are supported. UI runtime adaptations which have not been recorded at all or have been recorded on a workbench request will not be considered
For more information on how to work with UI runtime adaptations, see Adapting SAP Fiori UIs at Runtime - Key User Adaptation
- SAP Fiori launchpad Pages
- SAP Fiori launchpad Spaces
##  Note
For more information on how to manage launchpad pages and spaces, see Manage Launchpad Pages and Manage Launchpad Spaces.
- Text tables
##  Note
A database table needs to fulfill the following requirements to be considered a text table by the app:
- The delivery class of the text table has to be C
- There must be exactly one language key field
- Every character-like, non key field with a length greater than one will be treated as a text attribute
- The translation of text tables that contain key fields of type p (packed number), i (integer) or x (byte field) is not supported. That includes any kind of UUID and raw types, such as SYSUUID\_X16 .
4. Select Add to open the Add Text Source dialog which displays all text sources that can be added to the translation project. By filtering the type and name, you can choose the text sources you want to add. Select Add to add the text sources you selected to your translation project.
##  Note
The total amount of texts in a translation project must not exceed 1000. Be aware that a text source might contain more than one text.
## Related Information
Select Your Source and Target Language [page 2705]
## 6.3.1.6.6.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 Customizing Translations app, open the project for which you want to create a translation from a source language to a 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. For a given text source, 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.6.6.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 Customizing 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 for the given source and target language, choose All T exts .
4. 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 2707]
## 6.3.1.6.6.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 Customizing 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 and click Select .
Your translations have now been published.