The SAP Fiori Apps Reference Library is a comprehensive online library of all available SAP Fiori apps. It provides information about the app features, technical data, configuration, and implementation. You can use the SAP Fiori Apps Reference Library to look up the business catalog(s) that grant access to an app by following these steps:

Go to the SAP Fiori Apps Reference Library website and log in with your SAP credentials.

In the search bar, enter the name or ID of the app you want to restrict access to, and click the search icon.

In the search results, click on the app tile to open the app details page.

On the app details page, scroll down to the Implementation Information section and expand the Configuration tab.

Under the Configuration tab, you will see the Business Catalog field, which lists the business catalog(s) that contain the app. You can click on the business catalog ID to view more details about it, such as the business roles, business groups, and other apps that are assigned to it.

References = SAP Fiori Apps Reference Library, Cloud Creating a Business Catalog

 Fiscal year variant and group currency are activities that are applied to the entire system and cannot be changed after confirmation in SAP Central Business Configuration. These activities are part of the system provisioning step, which is the first step in the implementation process. Once the system provisioning is completed and confirmed, the system is locked for these activities and any changes would require a new system provisioning. Scoping and configuration activities, on the other hand, are not applied to the entire system and can be changed later on in the project experience step, which is thesecond step in the implementation process. Scoping and configuration activities allow the user to adapt the preconfiguration content to their company’s needs and extend the configuration for areas not equipped with preconfiguration content. References = SAP Central Business Configuration – Overview, page 6; Configuring with SAP Central Business Configuration

 SAP Business Application Studio and SAP Build are two tools that enable customers to develop their own custom applications and integrate them with SAP S/4HANA Cloud Public Edition. SAP Business Application Studio is a cloud-based development environment that offers both low-code and full-stack development capabilities. It supports various SAP technologies and frameworks, such as SAP Fiori, SAPUI5, SAP Cloud Application Programming Model, and SAP Cloud SDK. SAP Build is a cloud-based prototyping and user research tool that helps customers to design and test user interfaces for their applications. It provides a drag-and-drop interface, a library of UI components, and integration with SAP Web IDE and SAP Fiori Launchpad. Both tools are part of the SAP Extension Suite, which provides a range of services and capabilities to extend SAP applications and processes. References = Create a SAP Fiori App and Deploy it to SAP S/4HANA Cloud > Create a SAP Fiori App and Deploy it to SAP S/4HANA Cloud. Create a SAP Fiori App and Deploy it to SAP S/4HANA Cloud > Create a SAP Fiori App and Deploy it to SAP S/4HANA Cloud. Low-code/No-code | SAP Developers.

Regression tests are a type of testing that should be done after a release upgrade has occurred. Regression tests are performed to ensure that the existing functionality of the system is not affected by the changes introduced by the new release. Regression tests help to identify any defects or errors that may have been introduced or uncovered by the release upgrade. Regression tests are part of the quality assurance process and are essential for ensuring the stability and reliability of the system. References = SAP S/4HANA Cloud, Public Edition - All Learning Journeys | SAP Learning -> Implementing SAP S/4HANA Cloud Public Edition -> Unit 5: Quality Assurance -> Lesson: Performing Regression Tests

You can rename or assign a different deployment target in SAP Central Business Configuration before completing the Confirm Scoping milestone. This allows you to change the system tenant that will be used for the initial deployment of the content. However, you cannot define the group currency or create a company code beforeconfirming the scoping, as these are configuration activities that require a deployed system. References = Deployment Targets, Assigning a Deployment Target

When you build an integration scenario using the SAP Fiori Communication Management apps in SAP S/4HANA Cloud Public Edition, you must create a communication system and a communication arrangement. A communication system represents the communication partner within a communication, such as the system that calls or provides services. A communication arrangement defines the settings for a specific communication scenario, such as the authentication method, the communication user, and the service URL. You can use the Communication Systems app and the Communication Arrangements app to create and manage these objects in the SAP Fiori launchpad. References = Setting up Communication Management - SAP Learning, Setting up SAP Best Practices Integrations - SAP Learning, Setting Up Integrations in SAP S/4HANA Cloud Public Edition

The SAP Activate methodology outlines the phases for implementing SAP S/4HANA Cloud Public Edition. One crucial phase is the 'Explore' phase. During this phase, consultants workclosely with the business to understand its processes and requirements through Fit-to-Standard workshops. These workshops are designed to identify the best fit of the standard SAP S/4HANA processes with the business's needs. It's a collaborative effort to explore the capabilities of SAP S/4HANA Cloud and configure the business processes accordingly. This phase is fundamental in ensuring that the solution is tailored to meet the specific needs of the business, setting the foundation for a successful implementation.

 Before the first Fit-to-Standard workshop, the consultant should do the following activities:

Deactivate scope items that are NOT part of the Statement of Work/Digital Discovery Assessment. This is to ensure that the Starter system reflects the agreed scope of the project and does not include any unnecessary or out-of-scope items. The consultant can use the Scope Item Management app to deactivate scope items1.

Review the integration requirements collected from the Digital Discovery Assessment. This is to understand the customer’s integration needs and prepare for the integration topics that will be discussed in the Fit-to-Standard workshop. The consultant can use the Integration Solution Advisor tool to review the integration requirements and the recommended integration scenarios2.

The consultant should NOT do the following activities before the first Fit-to-Standard workshop:

Upload customer master data in the Starter system using migration templates. This is not required before the first Fit-to-Standard workshop, as the customer master data is not relevant for the process validation. The consultant should upload the customer master data in the Quality system after the Fit-to-Standard workshop, using the SAP S/4HANA Migration Cockpit3.

Evaluate the L2 Business-Driven Configuration Questionnaire responses. This is not required before the first Fit-to-Standard workshop, as the L2 Business-Driven Configuration Questionnaire is not available at this stage. The consultant should evaluate the L2 Business-Driven Configuration Questionnaire responses after the Fit-to-Standard workshop, using the SAP Activate Methodology.

References =

1: Scope Item Management App

2: Integration Solution Advisor Tool

3: SAP S/4HANA Migration Cockpit

: [SAP Activate Methodology]

In different deployment models, the responsibility for application management varies, with the customer typically taking on more responsibility in certain models:

Platform as a Service (PaaS):In this model, the customer is responsible for managing the applications they develop or deploy on the platform, even though the provider manages the underlying infrastructure, operating systems, and middleware.

On premise:In an on-premise deployment, the customer has full responsibility for managing both the applications and the infrastructure they run on. This includes maintenance, updates, security, and compliance for both the applications and the hardware/software infrastructure.

Private Cloud:Similar to on-premise deployments, customers in a private cloud model are typically responsible for managing their applications, including SAP S/4HANA Cloud Public Edition. The cloud provider may manage the cloud infrastructure and virtualization layer, but the customer often handles application-level management tasks, including updates, customization, and user management.

These deployment models contrast with Software as a Service (SaaS), where the service provider is generally responsible for managing the application, including its maintenance, updates, and availability.

The IT Contact is the person who is responsible for setting up the initial system access, provisioning users, and managing authentication for the SAP S/4HANA Cloud Public Edition project. The IT Contact should be identified and assigned immediately when the implementation begins, as they will receive all the SAP communications and notifications related to the system setup and configuration. The IT Contact should also be available and accessible throughout the project, and collaborate with the project team and the business stakeholders1.

The IT Contact should be someone who is a hands-on system administrator, not an executive. They should have the skills and experience to perform the system administration tasks, such as creating users, assigning roles, configuring identity providers, and troubleshooting issues. They should also be committed and engaged with the project, and provide feedback and participate in testing and training activities1.

Therefore, the correct answer is C, as the customer system admin is the most suitable person to be the IT Contact for the SAP S/4HANA Cloud Public Edition project. References = 1 How to Choose the Right IT Contact for Your SAP S/4HANA Cloud Public Edition Project - SAP Community

 You can complete the following activities in the Maintain Business Roles SAP Fiori app:

Assign business catalogs to a business role. Business catalogs are collections of SAP Fiori apps that are relevant for a specific business area or task. You can add one or more business catalogs to a business role to grant access to the corresponding apps1.

Maintain restrictions. Restrictions are rules that limit the access of a business role to certain data or functions based on predefined criteria, such as company code, plant, or sales organization. You can maintain restrictions for a business role in a new UI that provides an overview of the restriction types and values2.

You cannot complete the following activities in the Maintain Business Roles SAP Fiori app:

Maintain technical catalogs. Technical catalogs are collections of SAP Fiori apps that are grouped by technical criteria, such as application component or OData service. Technical catalogs are not assigned to business roles, but rather to business catalogs as dependencies3.

Assign PFCG profiles to a business role. PFCG profiles are authorization profiles that are created and maintained in the Profile Generator (PFCG) transaction in the SAP GUI. PFCG profiles are not assigned to business roles, but rather to business users as part of the user role assignment4. References = Maintain Business Roles; Maintain Business Roles and Business Users; Maintain Business Roles - New (Preview); Maintain Business Catalogs

When using the Local SAP S/4HANA Database Schema migration approach, you can upload multiple XML files at once by using a ZIP file. The total maximum permitted size for the XML files in the ZIP file is 160 MB. The limit for the ZIP file is also 160 MB. Therefore, the maximum file size is 160 MB per ZIP file and 160 MB per file. References = SAP Help Portal - SAP Online Help, SAP Help Portal - SAP Online Help

You specify the data retention period in the SAP S/4HANA Migration Cockpit when the project status is “Finished”. The data retention period is the length of time (in days) that the project and all associated data is kept in the system after you have set the status of the project to Finished. To do this, set the option Data Retention Period to On. The data will be deleted from the SAP S/4HANA system when the data retention time expires. If you set the option Data Retention Period to Off, then the project and all associated data will be kept in the system indefinitely. You can also change the retention time for finished projects on the Technical Information tab of the project settings. References = The Migration Project Screen, Migrating Data to the SAP S/4HANA System

 In the Realize phase of the SAP Activate Methodology, the project team uses a series of iterations to build and test a complete business and system environment based on the inputs from the previous steps. The activities in this phase include1:

Receiving the systems from SAP

Performing configuration in the Q-System using SAP Central Business Configuration

Setting up manual test cases in SAP Cloud ALM

Performing data loads and data migration

Delivering key-user training

Preparing for cutover and go-live Therefore, the correct answers are C and D, as they are part of the Realize phase activities. References = 1 SAP Activate – Explore Phase: Use Fit-to-Standard to Confirm Business Process Requirements - SAP Community

 Tools that enable non-developers to create low/no-code extensions are designed to be user-friendly, requiring minimal to no programming knowledge, allowing business users to tailor applications to their specific needs. Among these tools, SAP Fiori extensibility apps and SAP Build stand out:

SAP Fiori extensibility apps:These apps allow users to adapt the user interface and behavior of standard SAP Fiori apps without writing code. Users can personalize forms, fields, and workflows directly within the SAP Fiori environment, making it possible to adjust applications to meet specific business requirements.

SAP Build:SAP Build is a suite of tools designed to enable users to create and enhance applications, automate processes, and design business sites with low-code or no-code approaches. It provides a user-friendly interface where users can drag and drop components, set up workflows, and integrate data without needing deep technical expertise.