Check Real SAP C_S4CPB_2602 Exam Question for Free (2026) [Q10-Q25]

See Explanation below for all solution
Explanation:
Objective
The purpose of this task is to create a test user in SAP S/4HANA Cloud for demonstrating professional services business processes to project managers during a Fit-to-Standard workshop.
This task is completed by importing:
worker data
work agreement data
The import must use the exact values provided in the task.
Business Scenario Explanation
In this scenario, you need a test user that represents a Project Manager.
This user is needed so that project-management-related professional services processes can later be demonstrated in the system.
Instead of creating every record manually, SAP asks you to use the import process.
This is faster and also ensures the worker and agreement data are loaded in the correct structure.

Important Notes
Always replace ###### with the last 6 digits of your group number.
Use the values exactly as provided.
Do not change spaces, punctuation, or capitalization unless the task explicitly tells you to.
A wrong value, extra space, or missing number can cause task validation failure.

If your suffix is 000013, then the values become:
Worker ID = 1000013
User Name = PM000013
First Name = Project
Last Name = Manager 000013
Email = [email protected]
Step 1: Open the app used for importing users/workers
From the SAP S/4HANA Cloud launchpad:
Log in to the system.
Open the relevant import app used in your simulation for importing worker and work agreement data.
Start creation of a new import.
Explanation:
This task is not done by manual user creation only.
The scenario specifically says to create the new business user by importing the new user’s data.
The import will load the basic worker and work agreement records that are required before the business user is fully usable.
Step 2: Enter the import name
When creating the import:
In the field Import Name, enter:
Project Manager Test User ######
Replace ###### with your own 6-digit group suffix.
Example
For suffix 000013, enter:
Project Manager Test User 000013
Explanation:
The import name identifies your import package and should be entered exactly as required by the task.
Step 3: Prepare the worker data
In the worker import structure, enter these values:
Worker ID = 1######
User Name = PM######
Worker Type = BUP003
First Name = Project
Last Name = Manager ######
Email = PM######@dummy.sap.com
Language = EN
Company Code = 1010
Cost Center = 10101501
Example for 000013
Worker ID = 1000013
User Name = PM000013
Last Name = Manager 000013
Email = [email protected]
Explanation:
These values define the person as a project manager test worker and connect the worker to:
the company code,
the cost center,
the default language,
and the worker type required by the scenario.
Step 4: Prepare the work agreement data
In the work agreement import structure, enter:
Start Date = today’s date in YYYYMMDD format
End Date = 99991231
Example
If today’s date is March 30, 2026:
Start Date = 20260330
End Date = 99991231
Explanation:
The end date 99991231 is used to indicate an open-ended validity.
This is common in SAP for a record that should remain valid indefinitely.
Step 5: Upload or enter the import data
Depending on the app behavior in your exercise:
Upload the prepared import file or
Enter the values into the import structure manually if the system provides inline entry.
Explanation:
The business scenario says the business user must be created by importing worker and work agreement data.
This means the relevant master data must be loaded into the system first before the user is fully available.
Step 6: Start the import
After all values are entered:
Validate the data if the system provides a validation option.
Start the import.
Explanation:
Validation checks whether:
required fields are filled,
date formats are correct,
codes like BUP003, 1010, and 10101501 are valid,
and the import structure is complete.
Step 7: Wait for the import to complete
Monitor the import process.
Wait until the import shows success or completed status.
Explanation:
Only after the import is complete will the worker and work agreement records exist in the system and be usable for further user setup and role assignment.
Step 8: Verify the imported worker/business user
After the import finishes:
Open the relevant business user / worker maintenance app.
Search using:
Worker ID
or User Name
Confirm that the imported user exists.
Explanation:
This step ensures the imported data was actually created and is available for later process demonstrations.
Expected Result
After the import is completed successfully:
a new test worker/user exists in the system,
the worker has the required professional-services identity,
the work agreement is valid,
the user can be used in later project manager demonstrations.

See Explanation below for all solution
Explanation:
Objective
The purpose of this task is to migrate two bank master records into SAP S/4HANA Cloud Public Edition using the Migrate Data Using Staging Tables approach.
This task is performed inside the migration project created earlier:
Migration Project Name: Bank Data ######
Migration Object: Bank
The bank master data must be entered exactly as provided in the task tables.
Business Scenario Explanation
In this scenario, you are responsible for loading a small number of bank records into the system. Because there are only two banks to migrate, the selected migration method is:
Migrate Data Using Staging Tables
This method requires you to:
open the existing migration project,
download the Bank templates,
populate the required CSV file with the bank data,
upload the files,
validate the data,
transfer the data to staging tables,
complete any required mapping tasks,
migrate the bank instances,
verify the migrated banks in the target app.
Important Notes
Always replace ###### with the last 6 digits of your group number.
Use the values exactly as shown in the task.
Keep names, spaces, and numbers exactly correct.
During your execution, mappings may be required for:
Country/Region Key
Language Key (ISO)
Regional Code
Bank Key
If regional text values like Pennsylvania or Georgia are rejected, mapping may be needed to:
PA
GA
Example
If the suffix is 000013, the values become:
Bank 1
Bank Country/Region = US
Bank Key = A000013
Bank Name = Bank of A000013
Street = West Chester Pike
House Number = 3999
City = Newtown Square
Postal Code = 19073
Country/Region = US
Language = EN
Location = Pennsylvania
Bank 2
Bank Country/Region = US
Bank Key = Z000013
Bank Name = Bank of Z000013
Street = Lenox Road
House Number = 3580
City = Atlanta
Postal Code = 30326
Country/Region = US
Language = EN
Location = Georgia
Detailed Step-by-Step Procedure
Step 1: Open the app “Migrate Your Data”
From the SAP S/4HANA Cloud launchpad:
Log in to SAP S/4HANA Cloud.
Search for:
Migrate Your Data
or
Migration Projects
Open the app.
Explanation:
This app is the migration cockpit where the project and Bank migration object are maintained.
Step 2: Open the migration project
In the migration projects list:
Search for your project:
Bank Data ######
Open the project.
Example
If your suffix is 000013, open:
Bank Data 000013
Explanation:
This is the migration project created in the previous task and it contains the migration object Bank.

Step 3: Open the Bank migration object
Inside the migration project:
Locate the migration object:
Bank
Open it.
Explanation:
The Bank migration object is where the templates, uploads, mapping tasks, and migration instances are handled.


Step 4: Download the template files
On the Bank migration object screen:
Click:
Download Template
This provides the CSV template files needed for migration.
Explanation:
For the Bank migration object, the main files typically include:
S_BNKA#FreeText_Mandatory.csv
S_SCRIPT_ADRC#FreeText.csv
The mandatory file contains the bank master structure; the second file is optional for international address versions.
Step 5: Populate the mandatory Bank CSV file
Open the mandatory CSV file:
S_BNKA#FreeText_Mandatory.csv
Enter the two bank records exactly as required from the task tables.
Explanation:
This file must contain the bank master data that will be loaded into the staging tables.
The data must match the required values exactly.

Step 6: Use the correct values in the Bank CSV
Populate the mandatory file with the two records.
Bank 1
Bank Country/Region = US
Bank Key = A######
Bank Name = Bank of A######
Street = West Chester Pike
House Number = 3999
City = Newtown Square
Postal Code = 19073
Country/Region = US
Language = EN
Location = Pennsylvania
Bank 2
Bank Country/Region = US
Bank Key = Z######
Bank Name = Bank of Z######
Street = Lenox Road
House Number = 3580
City = Atlanta
Postal Code = 30326
Country/Region = US
Language = EN
Location = Georgia
Explanation:
These values create two bank master records, one beginning with key A###### and the other with key Z######.
Step 7: Keep the optional international address file empty if not needed For the file:
S_SCRIPT_ADRC#FreeText.csv
leave it with header only if no separate international address version data is required.
Explanation:
During your execution, the optional file was not required and the Bank migration still proceeded because only the mandatory Bank Master structure had to be populated.
Step 8: Open Upload Files
In the Bank migration object:
Go to:
Upload Files
Explanation:
This is where the CSV folder is created and the files are uploaded to the migration cockpit.

Step 9: Create a CSV Folder
Click:
Create CSV Folder
Explanation:
When using CSV with staging tables, SAP groups the upload into a CSV folder structure.
Step 10: Upload the CSV files
Upload:
S_BNKA#FreeText_Mandatory.csv
S_SCRIPT_ADRC#FreeText.csv (optional / empty if not used)
Explanation:
The mandatory file is required.
The optional file may remain empty or not provided depending on the migration object’s structure.
Step 11: Validate the data
After upload:
Click:
Validate Data
Explanation:
This checks:
file readability,
required columns,
correct structure,
duplicate keys,
and data consistency.
Step 12: Correct any file or format errors if needed
During execution, common issues included:
wrong file mapping,
UTF-8 / CSV reading problems,
missing mandatory fields,
duplicate key values,
region value mismatches.
Explanation:
You must resolve validation errors before continuing to staging tables.
Examples from your run:
duplicate key values had to be corrected,
file structure mapping had to be adjusted,
CSV encoding had to be corrected.
Step 13: Transfer data to staging tables
After validation is successful, click:
Transfer Data to Staging Tables
Explanation:
This moves the validated CSV data into SAP’s staging tables so the Bank migration object can create migration instances.
Step 14: Go to Mapping Tasks if required
If the system shows mapping tasks, open:
Mapping Tasks
Explanation:
For your run, the following mappings had to be confirmed:
Country/Region Key
Language Key (ISO)
Regional Code
Bank Key
Step 15: Maintain mapping values
If mappings appear, confirm or maintain them as follows:
Country/Region Key
source US → target US
Language Key (ISO)
source EN → target EN
Regional Code
If text values are shown:
source Pennsylvania → target PA
source Georgia → target GA
Bank Key
Confirm the system-generated source values to the correct target values for:
A######
Z######
Explanation:
These mappings are required when the migration object needs target-system value confirmation before posting the records.
Step 16: Confirm the mapping tasks
After maintaining the mappings:
Click:
Confirm
Explanation:
All mapping task statuses should change to Confirmed before running migration again.
Step 17: Open the Bank instances
Return to the Bank migration object and open:
Instances
Explanation:
This screen shows the individual bank records created from the staging-table data.
Step 18: Select the bank instances
Select both bank records.
Expected rows:
US / A######
US / Z######
Explanation:
Both bank records must be selected so they can be migrated into the target system.
Step 19: Click Migrate
Click:
Migrate
Explanation:
This starts the actual creation of bank master records in the target SAP S/4HANA Cloud system.
Step 20: Resolve authorization issue if it appears
During your execution, migration initially failed with:
You are not authorized to create bank data for country/region US
The fix was to assign the additional business role:
Master Data Specialist – Bank Data
SAP_BR_MD_SPECIALIST_BNK
Explanation:
The migration cockpit role alone is not always enough.
Bank creation also requires bank master data authorization.
Step 21: Refresh and check migration status
After migration:
Refresh the screen.
Check the status of both bank instances.
Expected final result:
Success
Success
Explanation:
Both bank rows must finish successfully for the task to be considered complete.
Step 22: Verify in “Manage Banks – Master Data”
Open:
Manage Banks – Master Data
Search for:
US / A######
US / Z######
Explanation:
This is the final business verification step that proves the bank master records were created successfully in the system.
Expected Result
After this task is completed successfully:
both bank records are loaded through staging tables,
all mapping tasks are confirmed,
both migration instances complete successfully,
the two banks are visible in Manage Banks – Master Data.

See Explanation below for all solution
Explanation:
Objective
The purpose of this task is to check the Bank migration object documentation and assign the additional business role needed so you can successfully migrate bank data into SAP S/4HANA Cloud Public Edition.
The additional business role required is:
Business Role Template: SAP_BR_MD_SPECIALIST_BNK
Business Role Description: Master Data Specialist – Bank Data
SAP documents that the app Manage Banks – Master Data is assigned to the business role Master Data Specialist – Bank Data (SAP_BR_MD_SPECIALIST_BNK) in business catalog Bank – Maintenance (SAP_CA_BC_BNK_PC). That is the role needed for bank master data maintenance and is the missing authorization when the migration cockpit can load data but cannot create banks in the target system.
Business Scenario Explanation
In the previous migration steps, you already assigned the role:
Configuration Expert – Data Migration
BR_CONFIG_EXPERT_DATA_MIG
That role gives access to the migration cockpit itself, meaning you can:
create migration projects,
select migration objects,
upload CSV files,
validate data,
transfer data to staging tables,
and execute migration runs.
However, for the Bank migration object, SAP also requires the authorization to create bank master data in the target system. If that authorization is missing, the migration can still reach the execution stage, but then fail with an authorization message such as:
You are not authorized to create bank data for country/region US
That is why the additional role Master Data Specialist – Bank Data (SAP_BR_MD_SPECIALIST_BNK) must be assigned.
Important Notes
Always replace ###### with the last 6 digits of your group number in later migration steps.
The role to add here is in addition to the migration cockpit role.
Save the user after assigning the role.
Refresh the session after assignment so the new authorization is loaded.
Required Additional Role

Step 1: Review the migration object documentation
Open the Bank migration object in the migration project and review the documentation or role requirement note.
Explanation:
The task explicitly asks you to check the documentation for the Bank migration object and assign the additional role required for migration. SAP’s official documentation for bank maintenance shows that bank master maintenance is tied to the role Master Data Specialist – Bank Data (SAP_BR_MD_SPECIALIST_BNK).
Step 2: Open the app “Maintain Business Users”
From the SAP S/4HANA Cloud launchpad:
Log in to SAP S/4HANA Cloud.
Search for:
Maintain Business Users
Open the app.
Explanation:
This app is used to assign business roles to your user.
Step 3: Search for your own user
In Maintain Business Users:
Enter your own user ID in the search field.
Click Go.
Explanation:
You must assign the additional role to your own user because you are the one executing the migration.
Step 4: Open your user record
From the search results:
Click your user entry.
Open the business user detail page.
Explanation:
This opens the maintenance screen where assigned business roles can be changed.
Step 5: Switch to Edit mode
On the user detail page:
Click Edit
Explanation:
Edit mode is required before the assigned business roles list can be updated.
Step 6: Open the “Assigned Business Roles” tab
Inside the business user record:
Click:
Assigned Business Roles
Explanation:
This is where you assign the additional bank master data role.
Step 7: Click Add
In the assigned business roles section:
Click Add
This opens the popup:
Add Business Roles
Explanation:
This popup is used to search for standard SAP business roles.
Step 8: Search for the additional bank role
In the Add Business Roles popup, search for either:
SAP_BR_MD_SPECIALIST_BNK
or
Master Data Specialist – Bank Data
Then select the matching role.
Explanation:
SAP documents that the app Manage Banks – Master Data belongs to the role Master Data Specialist – Bank Data (SAP_BR_MD_SPECIALIST_BNK). That is the role needed for bank creation/maintenance authorization.
Step 9: Add the role
After selecting the role:
Click OK or Apply
Explanation:
This adds the role to your user in draft mode.
Step 10: Save the business user
Back on the business user page:
Click Save
Explanation:
This finalizes the new role assignment.
Step 11: Confirm both migration-related roles are assigned
After saving, verify that your user now has both:
BR_CONFIG_EXPERT_DATA_MIG
SAP_BR_MD_SPECIALIST_BNK
Explanation:
These two roles cover different parts of the scenario:
BR_CONFIG_EXPERT_DATA_MIG → migration cockpit access
SAP_BR_MD_SPECIALIST_BNK → bank master data creation/maintenance authorization Step 12: Refresh your session After saving:
Refresh the browser completely, or
Sign out and sign in again
Explanation:
SAP role assignments may not become active in the current session immediately. A refresh or new login ensures the authorization is reloaded.
Step 13: Return to the migration project
Go back to:
Migrate Your Data
open your project:
Bank Data ######
open migration object:
Bank
Explanation:
Now that the additional bank role is assigned, the system should allow you to migrate bank master data successfully.
Expected Result
After this task is completed successfully:
your user still has the migration role BR_CONFIG_EXPERT_DATA_MIG,
your user also has the additional bank role SAP_BR_MD_SPECIALIST_BNK,
the authorization error for creating bank data should no longer occur,
the Bank migration can proceed successfully.
Screenshots for This Task
Screenshot 1: Assigned Business Roles list including the migration role Use the screenshot from your run where the business user already shows:
Configuration Expert – Data Migration
This screenshot can be used to explain the starting point before the additional role is assigned.
What this screenshot proves
It shows that the migration role alone was not enough for the bank creation authorization.
Screenshot 2: Migration error message
Use the screenshot from your run that shows the message:
You are not authorized to create bank data for country/region US
This is the key evidence that an additional bank master data role was required.
What this screenshot proves
It proves the migration cockpit role was present, but bank maintenance authorization was still missing.
Official SAP Documentation Basis
SAP’s official documentation states that the Manage Banks – Master Data app is assigned to:
Master Data Specialist – Bank Data
SAP_BR_MD_SPECIALIST_BNK
within catalog:
Bank – Maintenance
SAP_CA_BC_BNK_PC
This is the basis for the additional role assignment required in this task.

See Explanation below for all solution
Explanation:
Objective
The purpose of this task is to create a new Communication User for the integration scenario Bank Integration with File Interface (1EG).
This communication user will later be used in the integration setup, especially when defining the communication system and communication arrangement.
Business Scenario Explanation
In this scenario, you are setting up the integration for:
Bank Integration with File Interface (1EG)
In SAP S/4HANA Cloud, technical communication between systems is usually handled through:
a Communication User
a Communication System
a Communication Arrangement
This task is the first step in that chain.
The communication user acts as the technical user that the system uses for integration-related authentication.
Important Notes
Always replace ###### with the last 6 digits of your group number.
Use the exact values shown in the task.
Do not change spaces, underscores, or capitalization.
The password should not be typed manually if the task says:
Have the system propose a password
Required Values
Use the following values exactly as shown in the task image.

Example
If your suffix is 000013, then the values become:
User Name = 1EG_COMM_USER_000013
Description = 1EG Communication User
Step 1: Open the app “Communication Users”
From the SAP S/4HANA Cloud launchpad:
Log in to SAP S/4HANA Cloud.
Use the search bar or app finder.
Search for:
Communication Users
or
Maintain Communication Users
Open the app.
Explanation:
This app is used to create and maintain technical communication users for integration scenarios.
This is the correct starting point because the task explicitly says to create a Communication User.
Step 2: Start creating a new communication user
Inside the Communication Users app:
Click:
New
Explanation:
This starts the creation of a new communication user record.
Step 3: Enter the User Name
In the new communication user screen, enter:
User Name = 1EG_COMM_USER_######
Example
If your suffix is 000013, enter:
1EG_COMM_USER_000013
Explanation:
This is the technical identifier for the communication user.
It must match the task exactly.
Step 4: Enter the Description
In the Description field, enter exactly:
1EG Communication User
Explanation:
This is the functional description of the technical integration user.
It should be entered exactly as written in the task to avoid validation issues.
Step 5: Let the system propose the password
In the password section:
Do not manually type a password.
Click:
Propose Password
Explanation:
The task explicitly says:
Password = Have the system propose a password
So the correct action is to use the SAP-generated password instead of entering your own value manually.
Step 6: Review the generated password
After clicking Propose Password:
The system generates a password automatically.
If the system displays the password, note it down if needed for later integration steps.
Explanation:
In some cases, the proposed password may later be needed during communication setup or documentation.
Even if not needed later in the simulation, this confirms the correct procedure was followed.
Step 7: Save the Communication User
Click:
Save
Explanation:
This finalizes the creation of the communication user.
Without saving, the technical user will not exist and the later integration steps will fail.
Step 8: Verify the Communication User
After saving, confirm that the communication user exists in the list and displays the correct values:
User Name = 1EG_COMM_USER_######
Description = 1EG Communication User
Explanation:
This confirms the task is complete and the user is ready to be used in the next integration setup tasks.
Expected Result
After this task is completed successfully:
the communication user exists,
the user name matches the required naming convention,
the description is correct,
the password was proposed by the system,
the user is saved successfully.

See Explanation below for all solution
Explanation:
Objective
The purpose of this task is to create a custom business role for project managers in the United States by using the standard SAP template role Project Manager – Professional Services and then restricting the role so users only have the minimum access needed for their job.
The template role used is:
Template Business Role ID: SAP_BR_PROJECT_MANAGER_PROF
Template Business Role Description: Project Manager – Professional Services The new custom role must be created with exact values defined in the task.
Business Scenario Explanation
In this simulation, you are building a restricted custom role for project managers who work only in the United States.
The goal is to ensure that these end users:
can create and edit projects,
can access only projects occurring in the United States,
cannot work with projects or staffing outside the US,
have only the minimum level of authorization needed.
This is done in two major parts:
Create a new custom business role from the standard SAP template
Restrict the role values so only US-related data is allowed
Important Notes
Always replace ###### with the last 6 digits of your group number.
Every value must be entered exactly as shown.
Even one missing space or incorrect character can cause the simulation validation to fail.
You must also create and assign a launchpad space as part of the custom role creation.
Required Values for Role Creation
Use the following values exactly as shown in the task image.
Parameter
Value
New Business Role ID
BR_PROJECT_MANAGER_PROF_US_######
New Business Role Description
Project Manager – Professional Services – US – ######
Option for Launchpad Spaces
Create and Assign Spaces Based on Space Templates
New Space ID
ZBR_PROJECT_MANAGER_PROF_US_######
Activate IAM Apps
Yes (check the box)
Example
If your suffix is 000457, the values become:
BR_PROJECT_MANAGER_PROF_US_000457
Project Manager – Professional Services – US – 000457
ZBR_PROJECT_MANAGER_PROF_US_000457
Detailed Step-by-Step Procedure
Part 1: Open the standard template role
Step 1: Open the app “Maintain Business Roles”
From the SAP S/4HANA Cloud launchpad:
Log in to SAP S/4HANA Cloud.
Use the app search.
Search for:
Maintain Business Roles
Open the app.
Explanation:
This app is used to maintain standard and custom business roles.
Because this task requires creating a custom role from an existing template, this is the correct starting app.

Step 2: Search for the template role
Inside Maintain Business Roles:
In the search/filter area, search for:
SAP_BR_PROJECT_MANAGER_PROF
or
Project Manager – Professional Services
Open the standard SAP template role.
Explanation:
You must start from the standard template role because the task explicitly says to use the template for:
Project Manager – Professional Services
SAP_BR_PROJECT_MANAGER_PROF

Part 2: Create the custom role from the template
Step 3: Click “Create Derived Business Role”
On the template role page:
Click:
Create Derived Business Role
Explanation:
This function creates a customer-specific copy based on the standard SAP business role template.
It preserves the delivered role content but allows you to define your own role ID, description, restrictions, and launchpad space.
Step 4: Enter the custom role information
In the creation popup, enter the values exactly as follows:
Template = SAP_BR_PROJECT_MANAGER_PROF
New Business Role ID = BR_PROJECT_MANAGER_PROF_US_######
New Business Role Description = Project Manager – Professional Services – US – ###### Option for Launchpad Spaces = Create and Assign Spaces Based on Space Templates New Space ID = ZBR_PROJECT_MANAGER_PROF_US_###### Activate IAM Apps = checked Explanation:
These values define the new custom project manager role that will later be restricted to US-only access.
The space option is important because the task expects the role to include its own launchpad space.

Step 5: Confirm creation
Click OK
Explanation:
SAP now creates the custom role derived from the template and assigns the new launchpad space at the same time.
Part 3: Verify the newly created custom role
Step 6: Review the new custom role
After creation, SAP opens the new custom role.
Verify:
Business Role ID = BR_PROJECT_MANAGER_PROF_US_######
Business Role Description = Project Manager – Professional Services – US – ###### Business Role Template ID = SAP_BR_PROJECT_MANAGER_PROF Explanation:
This confirms the derived role was created correctly from the right SAP template.
Part 4: Maintain role restrictions
Step 7: Open “Maintain Restrictions”
On the custom role page:
Click:
Maintain Restrictions
Explanation:
This is the most important part of the task.
You are not only creating a role – you are also limiting the role so it only allows US-related values.
Step 8: Understand the rule for restriction maintenance
The PDF/task logic is:
Fields explicitly listed in the restriction table → keep them Restricted and enter the required values All other fields not listed in the task table → set them to Not Maintained Explanation:
This is essential.
If extra fields remain restricted or blank, the role may not validate correctly.
The safest approach is:
only maintain the required fields,
mark all unrelated fields as Not Maintained.

Part 5: Enter the required US restrictions
From your exercise run, the maintained values included restrictions such as:
Keep these kinds of fields restricted with US/1710 values where required Examples from your run:
Bank Country/Region Key
Read, Value Help = US
Value Help = US
Company Code
use 1710 only where the task table explicitly requires it
Purchasing Organization
use 1710 where required
Valuation Area
use 1710 where required
Explanation:
These are the exact business restrictions that make the role usable only for the intended geography and business scope.
Step 9: Set unrelated restriction fields to “Not Maintained”
For every field not included in the task’s restriction list, choose:
Not Maintained
Examples from your screenshots included fields like:
Accounting Principle
Authorization Group for Business Partners
Billing Type
These should be Not Maintained unless they are explicitly listed in the task’s required restriction table.
Explanation:
This removes unnecessary access and matches the task wording that all other fields should be set to Not Maintained.

Step 10: Save the restrictions
After all required values are entered and unrelated fields are marked Not Maintained:
Click Save
Explanation:
This saves the restriction profile of the role.
If you do not save here, the role will remain incomplete or in draft.
Part 6: Verify launchpad space and page creation
Step 11: Go to Launchpad Spaces
In the custom role:
Open the tab:
Launchpad Spaces
Verify that the assigned space exists:
ZBR_PROJECT_MANAGER_PROF_US_######
Explanation:
Because you selected Create and Assign Spaces Based on Space Templates, SAP should have created and assigned the launchpad space automatically.
Step 12: Verify the created space
Open the assigned space and confirm:
the custom space exists,
it is customer-managed,
the pages are assigned correctly.
Explanation:
This proves that the new business role has its own launchpad structure as required by the task.
Expected Result
After this task is completed successfully:
a new custom role exists based on SAP_BR_PROJECT_MANAGER_PROF,
the role uses the exact required ID and description,
the role has a custom launchpad space,
IAM apps are activated,
restrictions are maintained for US-only access,
all irrelevant fields are set to Not Maintained,
the role is saved successfully.

See Explanation below for all solution
Explanation:
Objective
The purpose of this task is to complete the launchpad setup for the custom all-employee role by:
assigning the custom Launchpad Space to the business role,
editing the Launchpad Page,
creating a section titled Self-Services,
adding the required applications as standard preferred square tiles:
Manage My Timesheet
Concur Travel Expense
Business Scenario Explanation
In the earlier tasks, you created:
a custom all-employee business role,
the required business catalog assignments,
a custom launchpad space and page.
This task completes that setup by adding the actual application tiles that end users will see on the launchpad.
The goal is to make it easy for employees to find the relevant self-service applications without searching manually.
Important Notes
Always replace ###### with the last 6 digits of your group number.
Use the exact values listed in the task.
The section title must be exactly:
Self-Services
The two tiles must be:
Manage My Timesheet
Concur Travel Expense
Save after editing the page.
Prerequisites
Before doing this task, the following should already exist:
custom business role:
Z_EMPLOYEES_ALL_######
assigned business catalogs:
SAP_HCM_BC_EMP_PC
SAP_CON_BC_CTE_ESS_PC
custom launchpad space and page created for the role
page title and description:
General
Detailed Step-by-Step Procedure
Step 1: Open the app “Maintain Business Roles”
From the SAP S/4HANA Cloud launchpad:
Log in to SAP S/4HANA Cloud.
Search for:
Maintain Business Roles
Open the app.
Explanation:
This is the app where the custom all-employee role is maintained. The launchpad space assignment and page navigation are controlled from here.
Step 2: Open the custom all-employee business role
In Maintain Business Roles:
Search for your custom business role:
Z_EMPLOYEES_ALL_######
Open the role.
Example
If your suffix is 000013, the role is:
Z_EMPLOYEES_ALL_000013
Explanation:
You must work in the custom all-employee role because the launchpad space and page belong to this role.
Step 3: Open the Launchpad Spaces tab
Inside the role:
Click:
Launchpad Spaces
Explanation:
This tab shows which launchpad space is assigned to the role.
Step 4: Verify the Launchpad Space is assigned
Check that the assigned space exists.
In your execution, the assigned space followed this pattern:
Z_ALL_EMP_######
Explanation:
The task says to assign the launchpad space to the custom business role.
If the space already appears in the assigned list, then this part is already complete.
If the space is not listed:
Click Add
Create or assign the required custom space
Save the role
Step 5: Open the assigned Launchpad Space
In the assigned launchpad spaces list:
Click the arrow > at the far right of the space row.
Explanation:
This opens Space Details, where the page linked to the space can be accessed.
Step 6: Open the Pages tab
In Space Details:
Click:
Pages
Explanation:
A space can contain one or more pages.
This task requires you to edit the page content.
Step 7: Open the Launchpad Page
In the Pages list:
Open the page row by clicking the arrow > at the far right.
In your run, the page followed this pattern:
Z_ALL_EMP_######
Explanation:
This opens Page Details, where the page content can be edited.
Step 8: Open Page Content
Inside Page Details:
Click the tab:
Page Content
Explanation:
This is the area where sections and application tiles are maintained.
Step 9: Click Edit
On the Page Content screen:
Click Edit
Explanation:
The page must be in edit mode before you can create sections or add app tiles.
Step 10: Enter the section title
In the section title field, enter exactly:
Self-Services
Explanation:
This creates the section in which the required employee self-service app tiles will be placed.
The title must match the task exactly.
Step 11: Add the tile “Concur Travel Expense”
On the right side of the page content screen, in the list of apps derived from the assigned catalogs:
Find:
Concur Travel Expense
Click:
Add
Explanation:
This adds the Concur employee self-service app tile into the Self-Services section.
Step 12: Add the tile “Manage My Timesheet”
Still on the right side app list:
Find:
Manage My Timesheet
Click:
Add
Explanation:
This adds the timesheet app tile into the same Self-Services section.
Step 13: Verify both tiles are visible in the section
After adding both apps, confirm that the page content now shows:
Concur Travel Expense
Manage My Timesheet
under the section:
Self-Services
Explanation:
This confirms the tiles were placed correctly on the page.
Step 14: Save the page
Click:
Save
Explanation:
This finalizes the page changes.
If you do not save, the tiles and section will not be retained.
Step 15: Verify the role is assigned to your business user
To verify the page and tiles from the home screen, make sure the custom all-employee role is assigned to your own business user.
Open:
Maintain Business Users
Then:
Open your own user
Open Assigned Business Roles
Confirm the role is assigned:
Z_EMPLOYEES_ALL_######
Save if needed
Explanation:
Without role assignment, the launchpad space and page may not appear on the homepage for your user.
Step 16: Refresh the homepage
Go back to Home.
Then:
Refresh the browser or reload the session
Open the page/tab:
General
Explanation:
This ensures the launchpad updates and shows the newly added content.
Step 17: Verify the result on the homepage
On the General page, verify that you can see:
section title:
Self-Services
tile:
Concur Travel Expense
tile:
Manage My Timesheet
Explanation:
This is the final proof that the task was completed successfully.
Expected Result
After this task is completed successfully:
the custom launchpad space is assigned to the business role,
the page contains a section named Self-Services,
the page shows the tiles:
Concur Travel Expense
Manage My Timesheet
the tiles are visible on the launchpad homepage under the General page.

See Explanation below for all solution
Explanation:
Objective
The purpose of this task is to assign the newly created custom all-employee business role to your own business user, save the assignment, refresh the browser, and then verify that the new Launchpad Space and its tiles are visible on the homepage.
This is the final verification step for the all-employee role and launchpad setup.
Business Scenario Explanation
In the previous tasks, you created and configured:
a new custom business role for all employees,
the required business catalogs,
a custom launchpad space,
a custom launchpad page,
and the employee self-service tiles:
Manage My Timesheet
Concur Travel Expense
However, even if all of that is configured correctly, you still will not see the new page and tiles on your homepage until the custom role is assigned to your own business user.
This task connects the configuration to your user and verifies the final end-user result.
Important Notes
Always replace ###### with the last 6 digits of your group number.
Use the exact business role ID.
Save the user after adding the role.
Refresh the browser after saving.
Then navigate back to Home and confirm the space/page/tiles are visible.
Required Business Role
Assign the custom all-employee role created earlier:
Business Role ID: Z_EMPLOYEES_ALL_######
Business Role Description: All Employee Role ######
Example
If your suffix is 000013, the role is:
Z_EMPLOYEES_ALL_000013
Detailed Step-by-Step Procedure
Step 1: Open the app “Maintain Business Users”
From the SAP S/4HANA Cloud launchpad:
Log in to SAP S/4HANA Cloud.
Search for:
Maintain Business Users
Open the app.
Explanation:
This app is used to assign business roles to users.
The launchpad space and tiles will only become visible after the custom role is assigned to your own user.
Step 2: Search for your own business user
In Maintain Business Users:
Enter your own user name or business user ID in the search field.
Click Go.
Explanation:
You must assign the role to your own user because you are the one who will verify the launchpad result on the homepage.
Step 3: Open your user record
From the search results:
Click your user entry.
Open the user details page.
Explanation:
This opens the maintenance page where assigned business roles can be reviewed and changed.
Step 4: Switch to Edit mode
On the business user page:
Click Edit
Explanation:
Without edit mode, the role assignment list is display-only.
Step 5: Open the “Assigned Business Roles” tab
Inside the user record:
Click:
Assigned Business Roles
Explanation:
This tab contains the list of all business roles currently assigned to your user and is the correct place to add the all-employee role.
Step 6: Click Add
In the Assigned Business Roles section:
Click Add
This opens the popup:
Add Business Roles
Explanation:
This popup allows you to search for and assign the custom all-employee role.
Step 7: Search for the custom all-employee role
In the Add Business Roles popup:
In the business role search field, enter:
Z_EMPLOYEES_ALL_######
Click Go
Select the role:
Z_EMPLOYEES_ALL_######
All Employee Role ######
Example
If your suffix is 000013, search for:
Z_EMPLOYEES_ALL_000013
Explanation:
This is the custom role created in the earlier launchpad/employee-role tasks.
It contains the launchpad space, catalogs, and page content that must now become visible to your user.
Step 8: Add the role
After selecting the role:
Click OK or Apply
Explanation:
This adds the role to your user in draft mode.
Step 9: Save the business user
Back on the business user page:
Click Save
Explanation:
This is a mandatory step.
Without saving, the role assignment is not finalized, and the new launchpad content will not appear for your user.
Step 10: Confirm the role assignment
After saving, verify that your assigned roles list includes:
Z_EMPLOYEES_ALL_######
All Employee Role ######
Explanation:
This confirms that the role is now officially assigned to your user.
Step 11: Refresh the browser
After saving:
Refresh the browser completely
Explanation:
SAP launchpad content is often cached in the current session.
A browser refresh ensures the newly assigned role content is loaded.
Step 12: Navigate back to Home
After refreshing:
Return to Home
Explanation:
The role’s launchpad space and page must be verified from the end-user homepage, not only from configuration apps.
Step 13: Open the page / launchpad tab
On the homepage, look for the custom page/tab that contains the employee content.
In your run, the visible page was:
General
Explanation:
The launchpad page created earlier was titled General, so that is the page you should open to verify the result.
Step 14: Verify the section title
On the page, confirm that you can see the section:
Self-Services
Explanation:
This was the section title created in the earlier page-content maintenance task.
Step 15: Verify the tiles
Under the Self-Services section, confirm that both tiles are visible:
Concur Travel Expense
Manage My Timesheet
Explanation:
These are the two required employee self-service tiles added to the page in the previous task.
Seeing both of them confirms that:
the catalogs were assigned correctly,
the launchpad page was maintained correctly,
the business role was assigned correctly,
and the browser refresh loaded the new content successfully.
Expected Result
After completing this task successfully:
your own user has the custom business role assigned,
the role is saved successfully,
after browser refresh the launchpad updates,
the homepage shows the new launchpad page,
the Self-Services section is visible,
and the tiles Concur Travel Expense and Manage My Timesheet are visible.

See Explanation below for all solution
Explanation:
Task 8: Create a New Business Role (Not from a Template)
Objective
The purpose of this task is to create a new custom business role for all employees in the organization. This role is intended to become the base role that will later be connected to the required business catalogs, launchpad space, and page so that employees can easily access the relevant apps.
This task explicitly says:
create a new business role
not from a template
use the exact values provided in the task
Business Scenario Explanation
You are building a role for all employees in the organization.
Unlike the earlier project-manager role, this one is not derived from a standard SAP template.
The purpose of this role is to provide a shared employee-level launchpad structure.
Later, the role will be used to:
assign business catalogs,
create a launchpad space,
create a launchpad page,
place apps on the page for employee self-service access.
In this step, the focus is only on creating the new business role with the correct identification and access category settings.
Important Notes
Always replace ###### with the last 6 digits of your group number.
Use the values exactly as shown.
Do not create this role from a template.
The access categories must be set exactly as required:
Unrestricted for all categories
Save the role at the end.
Required Values
Use the following values exactly as shown in the task screenshot

Step 1: Open the app “Maintain Business Roles”
From the SAP S/4HANA Cloud launchpad:
Log in to SAP S/4HANA Cloud.
Use the app search.
Search for:
Maintain Business Roles
Open the app.
Explanation:
This app is used to create, maintain, copy, derive, and restrict business roles.
Since this task requires creating a brand new custom role, this is the correct place to start.
Step 2: Start creating a new business role
Inside Maintain Business Roles:
Click New
Explanation:
This task explicitly says to create a role not from a template.
So you must use New, not:
Create From Template
Create Derived Business Role
Copy
Using New creates a completely customer-defined business role.
Step 3: Enter the business role ID
In the new business role creation screen:
In Business Role ID, enter:
Z_EMPLOYEES_ALL_######
Example
For suffix 000013:
Z_EMPLOYEES_ALL_000013
Explanation:
This is the technical identifier of the new business role.
It must match the task exactly for validation to succeed.
Step 4: Enter the business role description
In Business Role Description, enter:
All Employee Role ######
Example
For suffix 000013:
All Employee Role 000013
Explanation:
This is the readable description shown in SAP and should exactly match the exercise requirement.
Step 5: Set access categories
In the Access Categories section, set all categories to:
Write, Read, Value Help = Unrestricted
Read, Value Help = Unrestricted
Value Help = Unrestricted
Explanation:
The task explicitly says:
Access Categories: Unrestricted for all categories
So all three category dropdowns must be left or set to Unrestricted.
This means:
the role is not restricted by country, company code, or other field-level limitation in this step, this role is intended to be broadly reusable for all employees.
Step 6: Review the role before saving
Before saving, verify:
Business Role ID is correct
Business Role Description is correct
all 3 access category values are Unrestricted
Explanation:
This avoids common mistakes such as:
wrong suffix,
extra spaces,
restricted instead of unrestricted values,
creating from template accidentally.
Step 7: Save the role
Click:
Save
Explanation:
This finalizes the new business role.
Without saving, the role remains only in draft and is not actually created.
Step 8: Verify the role after save
After saving, confirm that the role is displayed with:
Business Role ID = Z_EMPLOYEES_ALL_######
Business Role Description = All Employee Role ######
Write Access / Read Access / Value Help Access = Unrestricted
Explanation:
This is the confirmation that the role was created successfully and matches the task requirement.
Expected Result
After the task is completed successfully:
a new custom business role exists,
it was created not from a template,
the role ID and description match the required values,
all access categories are Unrestricted,
the role is saved and available for the next steps.