orkungedik/SAP-basis-dataset huggingface dataset:
## 6.3.1.13.11.5  How to Manage Deprecated Business Catalogs After an Upgrade
## Context
If you want to view all deprecated business catalogs after an upgrade, you want to assign the successor business catalogs and adopt the relevant changes in your business roles, proceed as follows:
## Procedure
1. Select the Manage Business Role Changes After Upgrade tile on the SAP Fiori Launchpad to open the app. On the initial screen, view the Deprecated Business Catalogs area to get an overview of what has changed with the last upgrade.
2. Download a csv file containing all recently deprecated business catalogs if required.
3. Click on the required business catalog to check how the deprecation affects your business roles. The business roles affected by the deprecated business catalog are displayed in a list. By clicking on the business catalog Name above the list, you can view a description of the deprecated business catalog and the successor business catalog.
4. Select the required business role and click Adopt Changes if you want to take over the changes to your business roles. Please note that you might lose your maintained restrictions by doing this. We recommend that you validate the business role after the automatic adoption. By adopting the changes, you add all the successors business catalogs to the selected roles. The deprecated catalog will be removed.
##  Note
If the deprecated business catalogs contain extensions and you click Adopt Changes , the included extensions will be removed. If you want to keep these extensions, you need to re-assign them.
5. Select the Add the dependent business catalogs of the successor business catalogs checkbox if required.
6. Click OK . The system displays a progress bar and a list of change results when it is done.
7. Click Close to return to the Deprecated Business Catalogs area.
## 6.3.1.13.11.6  How to Manage Business Role Template Changes After an Upgrade
## Context
To get an overview of changes in the business role template area since the last upgrade, you can display any differences between business role and business role template in the How to Manage Business Role Changes After an Upgrade app. Either the template or the role that was based on the template might have changed. For example, business catalogs might have been added or removed. To apply these changes in a detailed maintenance screen, you can cross-navigate to the Business Role Templates app.
## Procedure
1. Select the Manage Business Role Changes After Upgrade tile on the SAP Fiori Launchpad to open the app. On the initial screen, the Business Role Templates area provides an overview of what has changed with the latest upgrade.
2. Download a csv file containing all recently changed business templates if required.
3. Click on the required business role template for details of the changes. The type of change (for example Different from Business Roles ) is already displayed on the initial screen.
4. To display a detailed comparison, select one or more affected business roles and click Compare with Business Role Template . This takes you to the Business Role Templates app.
5. All deviations of the business roles from the business role templates are displayed in a table. You can click Apply All if you want to take over all of the changes. Alternatively, you can go through the list and select deviations you would like to apply.
6. You can define one role as leading and all changes you make to this role will be automatically transferred to the roles you selected in the Deviations table.
6. Click Save when you're done.
Please note that you can also adjust your business roles directly in the Business Role Templates app.
## Related Information
Business Role Templates [page 2805]
## 6.3.1.13.11.7  Phase-In / Phase-Out Status
If a restriction is in status Phase-In , the values have no effect in the system at the moment. Therefore, you can prepare your system for new restrictions that will be active in the next release.
The Phase-Out status denotes that the restriction will be removed in the next release.
## 6.3.1.13.12.1  SAP Support User Request Log
In the Display Technical Users app, you can display more information about when and why SAP support users accessed your customer system in the past 12 months. For each support user, the relevant incident ID, access
level, access category, customer user, request date and validity date is displayed when you click on the required entry in the Users list. SAP support user IDs are pseudomized to respect the data subject rights of SAP employees according to GDPR.
## Related Information
Access Levels [page 2797] Access Categories [page 2799]
## 6.3.1.13.13  Business Catalogs
You use this app to display all available business catalogs.
With this app you can get an overview of the business catalogs, their status (for example Deprecated ), and their usage within business roles. You use this application to see which applications and business catalogs delivered by SAP have changed, for example after an upgrade. They may also be deprecated. As a key user, you need to have an overview of these changes to adapt the affected business roles accordingly.
## Key Features
You can use this app to:
- Display business catalogs, their usage in roles, and general description
- Display business catalog changes: Check if the business catalogs or apps in your area have changed (for example, a transaction has been replaced with an SAP Fiori app), and which business roles are affected by these changes.
- Display assigned apps: You can display apps that have their own tile access (classified as Standard Application ) as well as ones that can be started indirectly via app-to-app navigation (classified as Standard Navigation Target ).
- Display deprecations: Check if any of the business catalogs in your area are deprecated and which successors they will be replaced with. Select the affected business role and transfer the changes.
- Display dependencies: Check if a business catalog depends on other business catalogs or if other business catalogs depend on a business catalog in order to be fully operational.
- Display scope items: check which scope items the business catalogs depend on. Business catalogs that do not depend on any scope items are always visible in the system. For these business catalogs, Scope Items (0) is displayed on the relevant tab and the following message appears in the table: The business catalog is not scope-dependent .
- Display component: check under which component you can create an incident if required.
## 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-IAM .
## 6.3.1.13.13.1  How to Handle Deprecated Business Catalogs
If you want to check how many deprecated business catalogs you still have in use, or you want to change assignments from the old, deprecated business catalogs to the new, active catalogs quickly and easily, proceed as follows:
## Context
Due to ongoing development of new features and new apps, we need to periodically revise existing business catalogs. This means that some business catalogs are deprecated and replaced by new ones, and you need to assign business roles and business users to these new catalogs.
Rather than disappearing, deprecated business catalogs are identified as being obsolete, which allows you to identify them at a glance. You can also check how many deprecated business catalogs you still have in use with the Business Catalogs app. This app lets you change assignments from the old, deprecated business catalogs to the new, active catalogs quickly and easily.
##  Note
Some business catalogs might be redesigned in each release. Please check the assignments for your business roles and business users and make the necessary changes to the assignments as soon as possible.
## Procedure
1. In the Business Catalogs app, check how many deprecated business catalogs you still have in use.
You can filter the list of catalogs for the deprecated ones but the deprecated business catalogs are also marked with the appendix (deprecated) in the list of all catalogs in use.
2. Change assignments from the old, deprecated business catalogs to the new, active catalogs.
Once the deprecation of a business catalog is announced via the Business Catalogs app, the catalog will remain in the system for six months before being deleted. During this period you can use the old or the new business catalog. Within this timeframe you can do the replacement when it suits you best. In the Business Catalogs app, you can see the release in which the deprecation of a business catalog was announced.
Example: A business catalog is deprecated with a Cloud 2202 release. The business catalog will then be deleted with the Cloud 2208 release.
3. Ensure that also the assignments of custom catalog extensions are changed.
## 6.3.1.13.14  IAM Information System
With this app you can get an overview of business users in your system and what roles and restrictions are assigned to them.
With this app you can display information about the usage of business roles, business catalogs, business users and restrictions, and how they are related.
If you want to look up more information about a business role, derived business role, business user, business catalog, business role template or restriction, you can jump directly to the respective app by clicking the entity.
You can use this app for administrative tasks as part of your daily work.
## Key Features
You can use this app to:
- Check the usage of the following entities and how they are related: Business role, derived business role, business role template, application, business user, business catalog, restriction, launchpad space, launchpad page.
- Check, for example, which business roles are assigned to a business user, which business catalogs and restrictions are therefore assigned to the business user and to which applications a user has access. You can also download a list of business users and business catalogs.
- Check, for example, which business roles and business catalogs are required to make a certain app visible for a business user on the SAP Fiori Launchpad.
##  Note
You can also display the scope items the business catalogs depend on. Business catalogs that do not depend on any scope items are always visible in the system. For these business catalogs, Scope Items (0) is displayed on the relevant tab and following message appears in the table: The business catalog is not scope-dependent .
- Display assigned apps: You can display apps that have their own tile access (classified as Standard Application ) as well as ones that can be started indirectly via app-to-app navigation (classified as Standard Navigation Target ).
## 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-IAM .
## 6.3.1.13.15  Display IAM Apps
With this app you can display IAM apps of all supported IAM app types. This helps you to keep an overview of the assigned business roles.
## Key Features
You can use this app to:
- View general information, such as the app ID or the transaction
- View the app description
- Display the assigned business catalogs
- Display the assigned business roles
- For external apps: View the related authorizations including authorization objects, authorization instances and authorization fields.
## 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-IAM .
## 6.3.1.13.15.1  IAM App Types
The following IAM app types are available:
| IAM App Type Description   | IAM App Type   | Explanation                                                                                                                                                                                                                       |
|----------------------------|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| External App               | EXT            | An external app represents an app ex- tension. It defines what is included in a tile (this is determined by the services). You can use the external app to bundle services, define authorizations and as- sign business catalogs. |
| Business Configuration App | MBC            | A business configuration app serves as an entry point to the configuration ob- jects provided by the different applica- tion areas or partners. The configura- tion objects can be adjusted to change the system behaviour.       |
| Custom Inbound Service App | IBS            | This application type is only created in the development system and is only re- quired for authorization purposes to al- low the developers to test the inbound services locally.                                                 |
| UI5 Adaptation App         | UI5A           | An IAM app for a developer adaptation project. It is similar to an external app but release state checks for services in- herited from the base app are disabled.                                                                 |
## 6.3.1.13.16  Business Role Templates
You can use this app to you get an overview of the business role templates delivered by SAP .
With this app you can get an overview of the delivered business role templates, any changes included in upgrade, and whether you need to adapt your business roles to these changes. For example, after an upgrade, you can check if the business role templates have changed and are therefore different from the existing business role - a new business catalog might have been added or an existing catalog replaced by another. You can see which business roles were affected by the changes and adapt them if required.
## Key Features
You can use this app to:
- Display business role templates
- Display usage of business role templates in business roles
- Display differences between business role templates and business roles
- Check which business roles are affected by these changes
- Adapt business role to changes
- Create a business role
- Display scope items: check which scope items the business role templates depend on. Business role templates that do not depend on any scope items are always visible in the system. For these business role templates, Scope Items (0) is displayed on the relevant tab and the following message appears in the table: The business role template is not scope-dependent .
- Display component: check under which component you can create an incident if required.
## 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-IAM .
## Related Information
How to Create a New Business Role [page 2770] How to Create a Business Role from a Template [page 2771]
## 6.3.1.13.17  IAM Key Figures
You can use this app to display the following information:
- Number of business users assigned to business roles
- Month of the business user's last log-on
- Number of locked and unlocked business users
- Validity of business users
- Number of business roles with unmaintained restrictions
- Number of business roles with unrestricted access
<!-- image -->
##  Note
You can filter for the productive business roles in your area, for example by adding a certain namespace followed by an asterisk (*) in the Filter by Business Role ID field in the tile configuration.
- Business user price categories
- •
- Business roles with default values from business catalogs The default values are delivered automatically and can't be overwritten. This means either that an asterisk
(*) overwrites all defined values or that fixed values are added to the restrictions you have defined. Business roles affected by these non-changeable values are displayed in red in the overview chart.
## 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-IAM .
## 6.3.1.13.17.1  IAM Key Figures - Background
The charts in the IAM Key Figures app support you to increase the security in your area and to reduce costs by displaying which business users are inactive and can be removed.
They also provide a helpful overview that can be useful before go-live. For example, it helps you to evaluate whether the business user and role distribution in your area is ready for use.
To define threshold values, you can use color codes for the bars in your charts. The following colors are available:
- Green: Accepted
- Yellow: Warning
- Red: Critical
##  Example
You can define the colors based on certain time frames. If a user has not logged on to the system for 6 months and you want to use this point in time as a threshold value, you can determine that the corresponding bar in the chart is red.
You can also jump directly to the Maintain Business Users app or Maintain Business Roles app if you need more information about the business users or business roles that are shown in the overview charts.
## Related Information
Maintain Business Roles [page 2769] Maintain Business Users [page 2758]
## 6.3.1.14  Message Monitoring
Message Dashboard [page 2812]
Message Monitoring Overview [page 2813]
Message Monitoring for Integration Experts [page 2814]
Assign Recipients to Users [page 2815]
Message Monitoring (Emergency Correction) [page 2816]
SOAP Error Log, OData Error Log, and Event Error Log [page 2817]
Assigning the Business Catalog for SOAP Error Log, OData Error Log, and Event Error Log to Your Business Role [page 2818]
Automatic Reprocessing [page 2818]
## 6.3.1.14.1  Message Dashboard
With this app, you can get an overview of the interfaces you're responsible for and their current status. You can analyze the root causes of errors, restart or cancel data messages.
## Key Features
You can use this app to:
- See all interfaces you've been assigned to using recipients.
- See the general status of your interfaces over time and restrict the time range.
- Check for active alerts and confirm them in the column Alert .
- Configure what notifications you want to receive for a specific interface in the column Notification . Y ou can choose between E-Mail for the Next Alert (default), E-Mail for Every Single Error , and No Mail .
- See the message numbers and statuses (error, warning, success) by namespace and interface.
- Navigate to the message summary for an overview of how often a certain log message was written to the application log and how many data messages used a certain log message.
- Navigate to the monitoring and error handling to analyze the log messages in detail.
- Display the contents of the data messages.
- Create custom hints, message texts, and functions for certain log messages.
- Cancel data messages with issues that don't require you to take action (this functionality is only available for selected message formats).
- Solve errors by correcting the underlying data content of the messages.
- Restart corrected data messages or messages that had a temporary issue (this functionality is only available for selected message formats).
- Download payload for SOAP, IDoc, and XML messages.
## Supported Device Types
- Desktop
- Tablet
## Component for Customer Incidents
If you need support or experience issues, please report an incident under component BC-SRV-AIF .
## 6.3.1.14.2  Message Monitoring Overview
With this app, you can see an overview of all the interfaces that you're responsible for monitoring. The intuitive card-based view provides a holistic overview of your message interfaces and also provides additional details like the number of messages in different statuses for each interface. When you click on the specific status for a specific interface, you're redirected to Message Monitoring . Here, you can see a filtered view of the messages in the status that you selected for the specific interface containing the log information and key field information. For example, in the Message Monitoring Overview app, if you're monitoring an interface AIF\_XXX\_MMO and in the card specific to AIF\_XXX\_MMO , you click on the status Error , you're redirected to the Message Monitoring where you can see all the messages in status Error for the interface AIF\_XXX\_MMO . Y ou also see the log information and key field information for the messages in the Error status. This improves the efficiency of you finding the list of messages in a specific status for a given interface.
##  Tip
If you don't see the interface you're assigned to, verify that your user is assigned to the corresponding recipient using the Assign Recipients to Users app.
## Key Features
This app provides the following key features:
- Monitoring overview of all the responsible interfaces
- Quick overview of key parameters of the selected messages
- Filter or search for messages with key content as the search parameters
- Navigate to Message Monitoring with appropriate filter conditions for specific interfaces and message status, significantly improving the user experience
- Order the cards to keep an eye on mission-critical interfaces using drag-and-drop mechanism
- Identify interfaces with an active alert
## Supported Device Types
- Desktop
- Tablet
## Component for Customer Incidents
If you need support or experience issues, please report an incident under component BC-SRV-AIF .
## Related Information
Assign Recipients to Users [page 2815]
## 6.3.1.14.3  Message Monitoring for Integration Experts
With this app, you can display an overview of your interfaces and get details on all messages processed through them.
##  Tip
If you don't see the interface you're assigned to, verify that your user is assigned to the corresponding recipient using the Assign Recipients to Users app.
## Key Features
You can use this app to:
- Get a tabular overview of your interfaces and all messages (with specific status) processed through them.
- Filter your overview by time and/or interface, and restrict it to show only interfaces with messages or errors.
- Drill down on the messages of a specific interface and filter them by time, status, and key fields (if defined).
- Get more information on an individual message (such as log messages, message details, and data structure).
- Download the payload of a specific message.
- Edit, restart, or cancel a message (if in status Error or In Process ) (this functionality is only available for selected message formats).
- Perform mass error handling for multiple messages of an interface at once.
- Set process information for a message (such as defining a process status).
- Identify interfaces with an active alert and confirm the alert.
- Define data links and dynamic data links for log messages without a predefined link.
- Display the original payload of a message in the message's data content.
## Supported Device Types
- Desktop
- Tablet
## Component for Customer Incidents
If you need support or experience issues, please report an incident under component BC-SRV-AIF .
## Related Information
Assign Recipients to Users [page 2815]
## 6.3.1.14.4  Assign Recipients to Users
With this app you can assign your business users to the recipients that were defined for the communication scenarios. Once the users are assigned they can use the Message Monitoring Overview and Message Dashboard to monitor the interfaces and data messages they are responsible for.
## Key Features
You can use this app to:
- Find and add users.
- Find and assign pre-defined recipients to these users.
- Define which types of log messages the user can see in the Message Dashboard, for example, warnings only.
- Define if the messages are displayed or hidden on the Message Dashboard.
- Define if the user can see messages that are in process or that had a technical error using Advanced Error Handling .
- Unassign recipients from users.
## Supported Device Types
- Desktop
- Tablet
## Component for Customer Incidents
If you need support or experience issues, please report an incident under component BC-SRV-AIF .
## 6.3.1.14.5  Message Monitoring (Emergency Correction)
With this app, you can edit non-customized fields of a message payload in an emergency.
## Key Features
You can use this app to:
- Get a tabular overview of your interfaces and all messages (with specific status) processed through them.
- Filter your overview by time and/or interface, and restrict it to show only interfaces with messages or errors.
- Drill down on the messages of a specific interface and filter them by time, status, and key fields (if any are defined).
- Get more information on an individual message, such as log messages, message details, and data structure.
- Download the payload of a specific message.
- Edit, restart, or cancel a message (if in status Error or In Process ) (this functionality is only available for selected message formats).
- Set process information for a message (such as defining a process status).
- Identify interfaces with an active alert and confirm the alert.
- Edit the payload of messages, even if the messages aren't customized to be changeable.
Despite having similar functionalities as Message Monitoring for Integration Experts , Message Monitoring (Emergency Correction) doesn't support navigating to the Message Monitoring app or performing mass error handling.
## Supported Device Types
- Desktop
- Tablet
## Component for Customer Incidents
If you need support or experience issues, please report an incident under component BC-SRV-AIF .
## 6.3.1.14.6  SOAP Error Log, OData Error Log, and Event Error Log
With these apps, you can view and filter error logs related to SOAP web services, OData services, and events using SAP Application Interface Framework.
## Key Features
You can use these apps to:
- Get a comprehensive overview of failed communications relating to SOAP web services , OData services , and events
- Filter the SOAP Error Log, OData Error Log, and Event Error Log for various capabilities, such as Message ID, User Name, or Processing Date
## Supported Device Types
- Desktop
- Tablet
## Component for Customer Incidents
If you need support or experience issues, please report an incident under component BC-SRV-AIF .
## 6.3.1.14.7  Assigning the Business Catalog for SOAP Error Log, OData Error Log, and Event Error Log to Your Business Role
## Context
If you want to display the technical monitoring apps SOAP Error Log, OData Error Log, and Event Error Log in SAP Fiori launchpad, your user needs business roles that are authorized for the relevant business catalog.
## Procedure
1. In SAP Fiori launchpad, go to Identity and Access Management Maintain Business Roles .
2. Select Business Role , then click Edit .
3. In the tab Assigned Business Catalogs , select Add .
4. In the pop-up Assigned Business Catalogs , select the following business catalog: Communication Management - Technical Message Monitoring SAP\_CA\_BC\_COM\_TECH\_ERR\_PC .
5. Click OK , then select Save . The tiles SOAP Error Log , OData Error Log , and Event Error Log are now visible in SAP Fiori launchpad.
## 6.3.1.14.8  Automatic Reprocessing
With this app you can configure the automatic reprocessing that is executed when a data message fails with a specific log message.
## Key Features
You can use this app to:
- Create, edit, and delete automatic reprocessing settings for a specific combination of log message and interface. Whenever a data message fails with the selected log message, the configuration you defined is executed.
- Define a maximum number of reprocessing attempts that can be executed for a failed data message.
- Define a minimum waiting time that must pass before the application can trigger a reprocessing attempt. The waiting time can take longer depending on the interval of the background job that executes the reprocessing.
- Define the intermediate status (In Process or Error) the failed data message displays while it's waiting to be reprocessed.
## Supported Device Types
- Desktop
- Tablet
## Component for Customer Incidents
If you need support or experience issues, please report an incident under component BC-SRV-AIF .
## 6.3.1.15  Output Management
Maintain Print Queues [page 2819]
Monitor Email Transmissions [page 2831]
## 6.3.1.15.1  Maintain Print Queues
## Purpose
Using this app, you can set up print queues to manage the printing of documents and monitor the print jobs in each queue.
This helps you to identify and analyze errors and gives you a sense of direction for doing troubleshooting to solve them.
## Key Features
With this app you can:
- Create a new print queue
- Delete a print queue
- Pause a print queue This allows you to stop print items from being collected by the printing process while you are carrying out
repairs.
- Restart a print queue
- Check the status (such as New , Failed , Transmitted , Successful , Warning ) of queues or individual print items in the queue and display detailed information regarding the status
- Reassign a print item to another print queue
## Component for Customer Incidents
If you need support or experience issues, please report an incident under component BC-CCM-PRN-OM-PQ or BC-CCM-PRN-OM-PM .
## Related Information
Install Additional Software (SAP BTP ABAP Environment) Install Additional Software (SAP S/4HANA Cloud) Integrating SAP BTP ABAP Environment and Local Printers Integrating SAP S/4HANA and Local Printers Printing (SAP BTP ABAP Environment) Printing (SAP S/4HANA Cloud)
## 6.3.1.15.1.1  Before Getting Started
## Background Information for Print Queues
In a Cloud environment, the back-end system does not have a connection to local printers in your network (no virtual private network access is available, for example). To establish this connection, you need to create a print queue in the Cloud system representing an output channel to a local printer. To do so, open the Install Additional Software app and install the SAP Cloud Print Manager for Pull Integration (hereafter abbreviated as CPM) in your network. The CPM can then regularly check whether new print items are in the print queue. If this is the case, the CPM retrieves these items and sends them to the locally configured printer. In addition to that, you need to define communication scenario SAP\_COM\_0466 . For more information on the CPM, see 3048273 or Working with the SAP Cloud Print Manager for Pull Integration [page 2822].
Watch the following video to learn how to get started with printing:
## Related Information
SAP\_COM\_0466 (SAP S/4HANA Cloud) SAP\_COM\_0466 (SAP BTP ABAP Environment)
## 6.3.1.15.1.2  Creating Print Queues
You want to set up print queues to manage the printing of documents.
## Procedure
1. Open the Maintain Print Queues app.
2. Click New to create a new print queue.
3. Select a print manager.
4. Enter the required information:
- Queue : Print queue name
- Description : Print queue desciption
- Format : The format is the printer language type of the queue. The following language types are available: PDF, CAB 203 dpi, CAB 300 dpi, Datamax 203dpi, Datamax 300 dpi, Datamax 406 dpi, Datamax 600 dpi, HP Laserjet 4350 PCL 5e, HP LaserJet 4350 PS, PCL 5c (Color), PCL 5e (Monochrome), Intermec 203 dpi, Intermec 300 dpi, Intermec 400 dpi, Lexmark T644 PCL 5e, Lexmark T644 PS, PostScript 2, Postscript 3, Toshiba 203 dpi, Toshiba 305 dpi, XMLDATA, Zebra 203 dpi, Zebra 300 dpi, Zebra 600 dpi.
- Communication User : T echnical user with which the SAP Cloud Print Manager for Pull Integration logs on to the system. You have to define a communication user in the communication scenario SAP\_COM\_0466 first. Y ou can connect several queues to the same SAP Cloud Print Manager for Pull Integration - in this case all queues must use the same communication user.
- Retention : Spool Retention Period. The retention period is the number of days after which the print queue items that are in final state ( successful or failed ) will be deleted automatically.
5. Click Create to create a new print queue.
## Results
You have created a print queue you can use in the SAP Cloud Print Manager for Pull Integration .
##  Note
The Maintain Print Queues app always includes a print queue called DEFAULT . It's the only print queue provided by SAP and serves as a sample queue that can't be used for productive output as it can't be connected to the SAP Cloud Print Manager for Pull Integration .
To connect to your physical printers, you therefore need to create one or more custom print queues.
Keep in mind that you can't define custom retention time for items in the DEFAULT queue and that SAP might adapt the standard retention time at any time to avoid misuse. The DEFAULT print queue should also not be used as storage for all documents that are printed from the system, as SAP might restrict the given quota at any time to avoid misuse. A cleanup job will delete all items in the DEFAULT print queue after eight days, regardless of their status. This will not affect the behavior of other print queues.
## Related Information
SAP\_COM\_0466 (SAP S/4HANA Cloud) SAP\_COM\_0466 (SAP BTP ABAP Environment)
## 6.3.1.15.2  Monitor Email Transmissions
## Use
You can use this app to display successful and failed email transmissions and to provide background information. This app is read-only and doesn't allow any data changes.
## Key Features
With this app, you can:
- Search for a specific email by adapting filters
- Sort, add, or remove columns
- Display all outgoing email requests
- Export a results list as a spreadsheet
- Get the header data and information about the sending status on a specific email request
- Send a test email to check if the email outbound in a system is working
## Supported Device Types
- Desktop
- Tablet
## Component for Customer Incidents
If you need support or experience issues, please report an incident under component BC-SRV-COM .
## Related Information
Monitoring Email Transmissions [page 2832]
## 6.3.1.15.2.1  Monitoring Email Transmissions
Find out how to monitor your email transmissions.
## Procedure
Start the Monitor Email Transmissions app. On the starting page, you can search for a specific email by adapting the following filters:
- Subject
- Status
- Sender
- Created at
- Recipient Address
In addition, you can
- Sort columns
- Add or remove columns
Click Go to display the search results. In the results list, all email requests are displayed according to the filters you've set. You can export the results list as a spreadsheet.
To get more information on a specific email request, click a request in the results list. On the Details page, the following information is displayed:
- Status
- Sender
- Status Code
- Subject
- Created at
- Response
You can also get information about the recipients, such as:
- Latest status
- Recipient address
- Copy (BCC or TO)
- Latest status changed at
You can get additional information about the present and former recipient's status by selecting a recipient.
## Email Reorganization
Due to data protection reasons, all displayed emails will be deleted from the table view after 30 days.
## Testmail Functionality
You can send out a test email to any recipient chosen by you. The subject and the text are fixed values that are set by the app. The mail sender will automatically be set as the email address of the user currently logged on, or, if that user has no email address, as the default email address. After the successful creation of the send requests, the email can be viewed in the main table of the Monitor Email Transmissions app.
Sending test emails can help administrators to check if the email outbound of their system is working. If the email outbound is not working, you'll either directly receive an error message, or you can see the error message in the main view of the Monitor Email Transmissions app.
## Related Information
Monitor Email Transmissions [page 2831]
Configuration of the System Email Outbound
## 6.3.1.16.2  Read Access Logging Configuration
With this app you can configure Read Access Logging to determine which read access to data is logged and under which conditions.
<!-- image -->
##  Restriction
RAL items can not be created in the P system, only in the Q system. If you try to create configurations, log domains, purposes or recordings in the P system, you will get an error message saying Items of type SRAL\_&lt;RAL Item&gt; must not be edited in this system . Y ou can still activate and deactivate RAL items in the P system.
## Key Features
You can use this app to:
- Define purposes of Read Access Logging
- Define semantic grouping of fields to be logged
- Manage recordings of application user interfaces
- Change predelivered configurations of what to log
- Enable Read Access Logging in current client
- Check runtime errors and see changes to configurations
## Prerequisites
To access the app, you need to have the SAP\_CORE\_BC\_RAL\_CONF business catalog assigned to your user. This business catalog is contained in the SAP\_BR\_ADMINISTRATOR business role template.
## 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-RAL .
## 6.3.1.16.2.1  How to Define Purposes of Read Access Logging
Read Access Logging is always based on a logging purpose that is freely defined according to the requirements of an organization. It describes why specific data is logged.
## Context
In the configuration, you specify the logging purpose and each log entry in the log is assigned its purpose as an attribute. This configuration enables you to organize the log data by the logging purpose. For example, various archiving rules or reportings can be created based on logging purposes.
In each Read Access Logging configuration, assign a logging purpose. When you define archiving rules, use the logging purpose as the basis.
## Procedure
1. In the Read Access Logging Configuration app, choose Logging Purposes .
2. Decide whether to create a purpose or modify one of the templates delivered by SAP.
SAP delivers default purposes you can copy and modify to your needs or you can create your own.
- To create your own purpose, choose Create under Search Results .
- To copy a purpose from SAP, do the following.
- a. Under Search Criteria , choose Search .
- b. From the search results, select a template from SAP.
Templates from SAP use the  (SAP Template) icon under Owner or list SAP under Created By or Changed By .
- c. Under Actions , choose  (Copy) .
3. Enter the required data.
The ID is limited to ten characters. We recommend that you use an abbreviation of the purpose name as ID. The purpose name appears on all UIs.
4. Save your entries.
## Results
Assign logging purposes during the creation of Read Access Logging configurations. Logging purposes help you with the definition of archiving rules.
## 6.3.1.16.2.2  How to Define Semantic Grouping of Fields to Be Logged
Within an application, the data to be logged must be defined on a semantic level, before the actual fields and rules are defined. Log domains are semantic descriptions of semantically identical or related fields that have different technical representations.
## Context
In Read Access Logging, you define a log domain. When changing Read Access Logging configurations, assign a log domain to each field to be logged.
For a log domain, specify a name and a business area that the data element is related to. This definition is necessary because different applications might use the same log domain. For example, a log domain account can be something different in the Human Resources application than it is in the Banking application.
## Procedure
1. In the Read Access Logging Configuration app, choose Log Domains .
2. Decide whether to create a log domain or modify one of the templates delivered by SAP.
SAP delivers default log domains you can copy and modify to your needs or you can create your own.
- To create your own log domain, choose Create under Search Results .
- To copy a log domain from SAP, do the following.
- a. Under Search Criteria , choose Search .
- b. From the search results, select a template from SAP.
Templates from SAP use the  (SAP) icon under Owner or list SAP under Created By or Changed By .
- c. Under Actions , choose  (Copy) .
3. Enter the required data.
You can freely define the business area. The business area functions as a namespace for the data element.
The description appears in the detailed view of the read access log and can be helpful for the person evaluating the log to identify the log domain.
4. Save your entries.
## Results
When you change a configuration, you can assign a log domain to each field to be logged. The log domain is displayed in the read access log and helps the log evaluator to understand the semantics of the field. It enables the evaluator to search for a given semantic field regardless of the technical representation or ID of this field.
## 6.3.1.16.2.4  How to Define What to Log
To define what to log, use a read access logging configuration.
## Context
There are pre-existing configurations delivered by SAP that you can use immediately. If you need a configuration that is more customized to your needs, you can either create a configuration from scratch or change an existing one.
The configuration can then be activated and used for different applications.
## Related Information
How to Create a New Configuration [page 2842]
How to Activate or Deactivate the Correct Read Access Logging Configuration [page 2844]
## 6.3.1.16.2.4.1  How to Create a New Configuration
You can define what to log by creating your own read access logging configuration or modifying a template delivered by SAP.
## Procedure
1. In the Read Access Logging Configuration app, choose Configuration .
2. Select a channel.
3. Decide whether to create a configuration or modify one of the templates delivered by SAP.
SAP delivers default configurations you can copy and modify to your needs or you can create your own.
- To create your own configuration, select a channel and choose Create under Search Results . For channels that use recordings, choose a recording.
- To copy a configuration from SAP, do the following.
- a. Under Search Criteria , filter with Owner is SAP Template .
- a. From the search results, select a template from SAP.
Templates from SAP use the  (SAP) icon under Owner .
- b. Under Actions , choose  (Copy) .
For channels that use recordings, copy the recording that comes with the template under the same name or enter a new name.
- c. Find the channel you just copied and choose  (Edit Configuration) .
4. Depending on the channel, select the object you want to create a configuration for.
For example, an operation for a Web Service, a function module for an RFC, or an application for a Web Dynpro. If you are editing an existing channel, the object is already selected for you.
For more information, see Channel-Specific Information [page 2846].
5. Enter the required data.
- For Dynpro, choose Application / Software Component .
- For Dynpro and Web Dynpro, specify a Log Context .
6. Create log groups.
##  Note
For a logging purpose, only create one logging group.
- a. Under Log Groups , choose  (Create Log Group) .
- b. Specify a logging purpose and a description for the log group.
- c. Specify the fields that you want to log together in the log group.
Move fields in the Field list to the log group.
- d. In the Fields list, define how each field should be logged.
- The Logging Type determines if only the field name is logged when accessed or if the value of that field is also logged.
- To save space in the database, set Exclude if Initial to have Read Access Logging ignore a field if its value is initial.
##  Note
The initial value is not the default value, but the technical initial value. For example, the empty value for string or character-based fields or the number zero for integers. The default value is logged in any case.
If this option is set and all fields within a Web service, RFC, or Web Dynpro UI are initial, no log entry is created for any of the fields.
- For Dynpro and Web Dynpro, specify the Field Type , which is whether an input field, an output (display) field, or both.
##  Note
Values for password fields cannot be included in logs. The Logging Type is Without Value and cannot be changed.
## 7. Create conditions.
- a. Under Conditions choose  (Create Condition) .
If you do not assign any conditions, select the Without Condition checkbox in the log group attributes and continue with the next step.
- b. Specify a name and a description for the condition.
- c. Create one or more expressions for the condition.
Expressions are joined using logical AND .
- d. Specify the fields that you want to define rules for.
Move fields in the Field list to the expression.
- e. For each field, specify the select option (the selection criteria).
For example, Username Inclusive Equals John Smith .
Select options are joined using logical OR .
- f. Assign conditions to a log group or set the Without Condition option.
To assign a condition, select the Log Group, choose Assign Condition and select a condition. Activate the assignment if you want to apply the condition to the log group. The log groups and conditions do not need to be activated, however.
8. To check the configuration for consistency and function: choose  (Check Configuration) Check .
9. Save your entries.
## 6.3.1.16.2.4.2  How to Activate or Deactivate the Correct Read Access Logging Configuration
## Context
To activate or deactivate Read Access Logging for certain apps, follow the steps described below.
## Procedure
1. Go to the app for which you want to activate or deactivate Read Access Logging.
2. Open the app and navigate to your user area ( User Actions Menu ).
3. Click the About icon.
- If the app has an app ID such as F1492 , please proceed with the steps in the section Activating and Deactivating Read Access Logging for Apps with App ID .
## Activating and Deactivating Read Access Logging for Apps with App ID:
4. Copy the app ID.
5. Go to the SAP Fiori apps reference library and select All Apps .
6. In the Search bar, paste the app ID you have just copied.
7. Click the app entry in the results list.
8. On the App Details screen, select SAP S/4HANA Cloud from the dropdown list.
9. In the section Implementation Information , select your current SAP S/4HANA Cloud release.
10. Open the subsection Configuration and copy the OData service name/s and the OData service version of the app.
11. Go back to the SAP Fiori launchpad and open the app Read Access Logging Configuration.
12. Go to Configuration .
13. Select the channel SAP Gateway .
14. Paste the OData service name that you have just copied in the field Service ID . If you have copied more than one OData service name, you can add further Service ID fields to your search criteria.
15. Paste the OData service version that you have just copied in the field Service Version .
16. Click Search .
In the search results list, you can see if Read Access Logging configurations exist for the service/s and, thus, for the app, and if the Read Access Logging is active or inactive.
17. To activate or deactive Read Access Logging, select the service/s, and click either Activate or Deactivate . Read Access Logging is now activated or deactivated for the respective app.
## Related Information
How to Define What to Log [page 2842]
## 6.3.1.16.2.4.3  How to Compare an Existing Configuration With an SAP Template
You can compare an existing configuration that has been created based on an SAP template with the current SAP template to see if there are any deviations.
## Context
Because SAP templates are updated from time to time, it can be useful to compare existing configurations that are based on an SAP template. To check for templates with deviations and to see what has changed, follow these steps:
## Procedure
1. Under Administration open Configuration .
2. Choose the channel that you want to search through.
3. Under Search Criteria select Deviations from SAP Template is True .
4. Choose Search .
5. Choose one of the search results.
6. Choose More and select  Compare with SAP Template .
##  Note
If you want to rebuild a configuration based on an updated version of the SAP Template, close the pop-up window, choose the configuration, then choose More and select  Rebuild from SAP Template .
## Results
A pop-up window opens where you can check which values are different between the SAP Template (left) and the existing configuration (right).