See Explanation below for all solution
Explanation:
Task 1: Assign the Administrator Business Role to Your User
Objective
The purpose of this task is to assign the standard SAP business role Administrator to your own business user so you can perform the required configuration and administration activities in SAP S/4HANA Cloud.
The required business role is:
Business Role ID: BR_ADMINISTRATOR
Business Role Description: Administrator
For your exercise, you must always replace ###### with the last 6 digits of your group number. In your case, this was done with your own group suffix during execution.

Why this task is required
In SAP S/4HANA Cloud, access to apps and functions is controlled through business roles.
Without the Administrator role, your user may not be able to:
open administration apps,
maintain configuration-related master data,
assign other roles,
proceed with later project tasks.
So this task is the first access-enablement step.
Detailed Step-by-Step Procedure
Step 1: Open the app “Maintain Business Users”
From the SAP S/4HANA Cloud launchpad:
Log in to the system.
Use the search bar or app finder.
Search for:
Maintain Business Users
Open the app.
This app is used to maintain business users and assign or remove business roles.
Step 2: Search for your own user
Inside Maintain Business Users:
In the search/filter area, locate the field for User Name or search criteria.
Enter your own user ID.
Click Go.
For example, in your exercise you used your own SAP Learning user.
You must open your own business user because the Administrator role needs to be assigned to your personal user record.
Step 3: Open your user record
After the search results appear:
Click your user entry in the list.
Open the user details screen.
This takes you to the detailed maintenance page where business roles can be reviewed and assigned.
Step 4: Switch to Edit mode
In the business user detail screen:
Click Edit.
Without entering edit mode, the role assignment list is display-only and cannot be changed.
Step 5: Go to Assigned Business Roles
Inside your business user:
Open the tab:
Assigned Business Roles
Review the currently assigned roles.
This tab shows all business roles already assigned to your user and is the correct place to add new ones.
Step 6: Click Add
In the Assigned Business Roles section:
Click Add.
This opens the dialog:
Add Business Roles
The Add dialog is used to search and select standard SAP-delivered business roles.
Step 7: Search for the Administrator role
In the Add Business Roles popup:
In the field Business Role ID, enter:
BR_ADMINISTRATOR
Click Go.
Select the role:
Administrator
Business Role ID: BR_ADMINISTRATOR
This is the standard Administrator role required by the task.
You must select the exact standard role, not a custom role.
Step 8: Add the role
After selecting BR_ADMINISTRATOR:
Click OK or Apply, depending on the popup behavior.
Confirm that the role is added to the list of assigned business roles.
At this point the role is added to your draft changes, but not yet finally saved.
Step 9: Save the user
Back in the business user detail screen:
Click Save.
This is the final and mandatory step.
If you do not save, the Administrator role remains only in draft and is not actually assigned.
Step 10: Verify the assignment
After saving:
Check the Assigned Business Roles list.
Confirm that the Administrator role appears in the list:
BR_ADMINISTRATOR
Expected Result:
Your user now has the Administrator business role assigned successfully.
What to verify after completion
You should verify the following:
Your user record is saved successfully.
The role Administrator is visible in the assigned roles list.
No draft remains unsaved.
Later administration apps are available to your user.

See Explanation below for all solution
Explanation:
Objective
The purpose of this task is to assign the required business catalogs to the custom all-employee business role created in the previous task. These catalogs provide the applications that will later be shown in the launchpad space and page for all employees.
The catalogs that must be assigned are:
HCM – Employee Self Service
SAP_HCM_BC_EMP_PC
Concur – Employee Self-Service
SAP_CON_BC_CTE_ESS_PC
Business Scenario Explanation
In the previous task, you created a new custom all-employee business role, for example:
Z_EMPLOYEES_ALL_######
That role exists, but on its own it does not yet provide app access.
In SAP S/4HANA Cloud, app access is granted through business catalogs.
This means the role must now be connected to the catalogs that contain the apps employees need.
Later, these catalogs will feed the launchpad page content so end users can easily find the relevant applications.
Important Notes
Always replace ###### with the last 6 digits of your group number.
Use the exact catalog names and IDs.
Assign both required catalogs.
Save the role after assignment.
Do not assign the wrong catalog variant.
Required Catalogs
Assign exactly these two business catalogs:
Business Catalog
Business Catalog ID
HCM – Employee Self Service
SAP_HCM_BC_EMP_PC
Concur – Employee Self-Service
SAP_CON_BC_CTE_ESS_PC
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.
Use the app search.
Search for:
Maintain Business Roles
Open the app.
Explanation:
This app is used to maintain business roles, assign catalogs, assign launchpad spaces, and maintain restrictions.
Step 2: Search for your custom all-employee business role
Inside Maintain Business Roles:
Search for your business role ID:
Z_EMPLOYEES_ALL_######
Example
If your suffix is 000013, search for:
Z_EMPLOYEES_ALL_000013
Open the role.
Explanation:
You must open the custom all-employee role created in the previous task, not a template role and not a standard SAP role.

Step 3: Verify the correct role is open
Confirm that the role details show:
Business Role ID = Z_EMPLOYEES_ALL_######
Business Role Description = All Employee Role ######
Explanation:
This ensures you are assigning catalogs to the correct business role.
Step 4: Go to the “Business Catalogs” tab
Inside the role:
Click the tab:
Business Catalogs
Explanation:
This tab is used to assign the business catalogs that define which apps and app authorizations the role provides.
Step 5: Click Add
In the Assigned Business Catalogs section:
Click Add
This opens the dialog:
Add Business Catalogs
Explanation:
The Add popup is used to search for and assign SAP-delivered business catalogs to the custom role.
Step 6: Search for the first catalog
In the Add Business Catalogs popup:
Search for:
SAP_HCM_BC_EMP_PC
or
HCM – Employee Self Service
Select:
HCM – Employee Self Service
Business Catalog ID: SAP_HCM_BC_EMP_PC
Explanation:
This catalog provides employee self-service apps and is required by the task.

Step 7: Search for the second catalog
Still in the Add Business Catalogs popup:
Search for:
SAP_CON_BC_CTE_ESS_PC
or
Concur – Employee Self-Service
Select:
Concur – Employee Self-Service
Business Catalog ID: SAP_CON_BC_CTE_ESS_PC
Explanation:
This catalog provides the Concur employee self-service content and is also explicitly required by the task.
Step 8: Add the selected catalogs
After selecting both catalogs:
Click OK or Apply
Explanation:
This adds the selected catalogs to the custom role in draft mode.
Step 9: Verify both catalogs are listed
Back in the Business Role screen, verify that both assigned catalogs are visible:
SAP_HCM_BC_EMP_PC
SAP_CON_BC_CTE_ESS_PC
Explanation:
This confirms that the required app authorizations have now been attached to the role.
Step 10: Save the role
Click:
Save
Explanation:
This finalizes the catalog assignment.
Without saving, the catalogs remain only in draft and the role will not provide the required app content.
Step 11: Verify the result after save
After saving, check again that the role still shows both business catalogs in the assigned list.
Explanation:
This confirms the task was completed successfully and the role is ready for the next step, which is launchpad space/page content.
Expected Result
After this task is completed successfully:
the custom all-employee role has both required business catalogs assigned, the role is saved successfully, the role now provides the app authorizations required for employee self-service content, the launchpad page can later use these catalogs to add the required tiles.

See Explanation below for all solution
Explanation:
Purpose: Identify your own six-digit suffix and use it consistently in every task.
Open the user menu at the top-right of SAP S/4HANA Cloud.
Read your user name and note the last six digits.
Use those last six digits in every place the task PDF shows ######.
Example used in this guide: 000013

See Explanation below for all solution
Explanation:
Task 7: Restrict the Custom Business Role for US / 1710 and Mark All Other Fields as Not Maintained Objective The purpose of this task is to maintain the restriction values of the custom business role created in the previous task so that project managers only have the minimum access required for their work in the United States.
This task is performed on the custom business role created from the template:
Template Role: SAP_BR_PROJECT_MANAGER_PROF
Custom Role Example Pattern: BR_PROJECT_MANAGER_PROF_US_######
The task requires you to:
maintain only the listed restriction fields,
enter the exact required values for US and 1710,
set all other restriction fields to Not Maintained,
and save the role.
Business Scenario Explanation
This restriction setup is what makes the new custom role safe and fit for purpose.
The business requirement says that end users:
are project managers based in the United States,
should only access relevant US project data,
should not be able to staff or work outside the intended scope,
should only see and maintain data for the allowed organizational scope.
This is achieved by limiting the role to:
US for country-related fields
1710 for company / organizational fields
Everything else must be Not Maintained so that unnecessary access is not left open.
Important Notes
Replace ###### with the last 6 digits of your group number.
Use the values exactly as shown.
Maintain only the fields listed in the table.
Set all other restriction fields to Not Maintained.
Do not leave unrelated fields blank while still restricted.
Restricted + blank is usually wrong.
Not Maintained is the correct setting for all unrelated fields.
Required Restriction Values
Use the following values exactly as shown in your task screenshot.

That means:
Country restriction = US
Org/company restrictions = 1710
Detailed Step-by-Step Procedure
Step 1: Open the app “Maintain Business Roles”
From the SAP S/4HANA Cloud launchpad:
Log in to the system.
Search for:
Maintain Business Roles
Open the app.
Explanation:
This app is where the custom role was created in the previous task and where its restrictions are maintained.
Step 2: Open your custom Project Manager US role
In Maintain Business Roles:
Search for your custom role.
Open the role with ID pattern:
BR_PROJECT_MANAGER_PROF_US_######
Example
If the suffix is 000457, then the role is:
BR_PROJECT_MANAGER_PROF_US_000457
Explanation:
You must open the custom role, not the standard SAP template role.
The restrictions belong to the derived custom role only.
Step 3: Confirm the correct custom role is open
Check the role details and confirm:
the business role ID matches your custom role,
the description matches the US-specific project manager role,
the role is based on template SAP_BR_PROJECT_MANAGER_PROF.
Explanation:
This avoids accidentally changing the wrong role.
Step 4: Click “Maintain Restrictions”
On the custom role page:
Click:
Maintain Restrictions
Explanation:
This opens the detailed restriction maintenance area where access categories and field-level values are controlled.
Step 5: Set the access categories for restriction maintenance
On the restriction page, ensure the access categories are maintained as required for the role.
During your run, these categories were maintained as restricted so values could be entered for the listed fields.
Explanation:
Restriction values can only be maintained correctly when the role is in the right restriction mode.
This step prepares the role so the listed fields can be populated with US / 1710 values.
Step 6: Understand the rule before entering values
This task uses a strict rule:
Keep maintained
Only the fields explicitly listed in the table should be maintained with values.
Set to Not Maintained
Every other restriction field not listed in the table must be marked:
Not Maintained
Explanation:
This is the most important logic in the whole task.
If a field is unrelated and still left as restricted or blank, it can cause validation problems or give more access than intended.
Part A: Maintain the required restriction fields
Step 7: Maintain Bank Country/Region Key
Search for:
Bank Country/Region Key
Then maintain:
Read, Value Help = US
Value Help = US
Explanation:
This ensures the user can only read and search bank-related values for the United States.


Step 8: Maintain Company Code
Search for:
Company Code
Then maintain:
Write, Read, Value Help = 1710
Read, Value Help = 1710
Do not maintain an extra standalone Value Help entry for Company Code unless the task explicitly requires it.
Explanation:
The task table does not include a standalone Company Code Value Help line.
So only the listed two Company Code restriction types should contain 1710.


Step 9: Maintain Purchasing Organization
Search for:
Purchasing Organization
Then maintain:
Write, Read, Value Help = 1710
Read, Value Help = 1710
Value Help = 1710
Explanation:
This ensures all purchasing-organization-related access for the role is limited to organizational value 1710.
Step 10: Maintain Valuation Area
Search for:
Valuation Area
Then maintain:
Read, Value Help = 1710
Value Help = 1710
Explanation:
This limits valuation-related access to the intended organizational scope.
Part B: Set all other fields to Not Maintained
Step 11: Search through the other restriction fields
After entering the required fields, review the remaining restriction objects.
Examples from your run included fields such as:
Accounting Principle
Authorization Group for Business Partners
Billing Type
and many other unrelated restriction fields
Explanation:
These fields were not listed in the task table, so they must not stay restricted.
Step 12: Mark unrelated fields as Not Maintained
For each field not listed in the required table:
Open the field setting / restriction dialog.
Choose:
Not Maintained
Important examples
From your run:
Accounting Principle → Not Maintained
Authorization Group for Business Partners → Not Maintained
Billing Type → Not Maintained
Explanation:
These fields are outside the required US / 1710 restriction list.
If you leave them restricted without a required value, the setup is incorrect.
Step 13: Do not mark the listed fields as Not Maintained
The following must stay maintained with values because they are in the required table:
Bank Country/Region Key
Company Code
Purchasing Organization
Valuation Area
Explanation:
Only the unrelated fields become Not Maintained.
The listed fields must remain restricted with the required values.
Step 14: Save the role
After all required fields are maintained and all other fields are marked Not Maintained:
Click Save
Explanation:
This finalizes the role restrictions.
Without saving, the restriction changes remain incomplete.
Step 15: Verify the restriction result
After saving, verify that:
required fields contain US and 1710 exactly as defined,
unrelated fields are no longer restricted,
the role saves without error.
Explanation:
This is your final proof that the restricted custom role has been completed correctly.
Expected Result
After the task is completed successfully:
the custom role remains based on SAP_BR_PROJECT_MANAGER_PROF,
required US / 1710 restriction fields are maintained,
all unrelated restriction fields are marked Not Maintained,
the role is saved successfully,
the role now reflects minimum necessary access for US-based project managers.

See Explanation below for all solution
Explanation:
Objective
The purpose of this task is to use the correct SAP app to verify that the bank master data migrated in the previous task was created successfully in the target system.
The correct verification app is:
Manage Banks – Master Data
SAP’s documentation for bank maintenance assigns this app to the bank master data role and uses it for maintaining and checking bank records, which matches the verification step after migration.
Business Scenario Explanation
In the previous migration tasks, you:
created the migration project,
selected the Bank migration object,
prepared and uploaded the bank data,
validated and transferred it to staging tables,
completed mapping tasks,
migrated the two bank records.
However, a migration is not considered complete until the data is verified in the target application used for ongoing business maintenance.
For the Bank migration object, that target verification app is:
Manage Banks – Master Data
This app allows you to search for the migrated banks and confirm that the data now exists in SAP S/4HANA Cloud Public Edition.
Important Notes
Always replace ###### with the last 6 digits of your group number.
Use the exact bank values that were migrated.
Verification must be done in the correct app, not only in the migration cockpit.
The expected bank records are the two banks from the previous task.
Correct Verification App
Purpose
App
Verify migrated bank master data
Manage Banks – Master Data
SAP documents that bank master maintenance is handled through the bank master data application and the associated bank maintenance role/catalog, which is why this is the correct end-user verification app after bank migration.
Data to Verify
You should verify the two migrated banks:
Bank 1
Bank Country/Region = US
Bank Key = A######
Bank Name = Bank of A######
Bank 2
Bank Country/Region = US
Bank Key = Z######
Bank Name = Bank of Z######
Example
If your suffix is 000013, verify:
US / A000013 / Bank of A000013
US / Z000013 / Bank of Z000013
Detailed Step-by-Step Procedure
Step 1: Return to the SAP Fiori launchpad
After finishing the migration:
Go back to the SAP S/4HANA Cloud homepage.
Explanation:
The verification must be performed in the target business app, not only from the migration results screen.
Step 2: Open the app “Manage Banks – Master Data”
From the launchpad search:
Search for:
Manage Banks – Master Data
Open the app.
Explanation:
This is the correct app for checking whether the migrated bank master records now exist in the target system.
Step 3: Search for the first migrated bank
In Manage Banks – Master Data:
In Bank Country/Region, enter:
US
In Bank Key, enter:
A######
Click Go
Example
If your suffix is 000013, search for:
Bank Country/Region = US
Bank Key = A000013
Explanation:
This checks whether the first migrated bank was created successfully.
Step 4: Verify the first bank details
Confirm that the search result shows the correct bank record:
Bank Country/Region = US
Bank Key = A######
Bank Name = Bank of A######
You can also verify address data if visible, such as:
Street = West Chester Pike
City = Newtown Square
Explanation:
This confirms that the first bank master record exists in the target system after migration.
Step 5: Search for the second migrated bank
Clear or update the search criteria and enter:
Bank Country/Region = US
Bank Key = Z######
Click Go
Example
If your suffix is 000013, search for:
Bank Country/Region = US
Bank Key = Z000013
Explanation:
This checks whether the second migrated bank was created successfully.
Step 6: Verify the second bank details
Confirm that the second search result shows:
Bank Country/Region = US
Bank Key = Z######
Bank Name = Bank of Z######
You can also verify address data if visible, such as:
Street = Lenox Road
City = Atlanta
Explanation:
This confirms that the second bank master record exists in the target system after migration.
Step 7: Confirm successful verification
If both banks are visible in Manage Banks – Master Data, the migration verification is successful.
Explanation:
This is the final proof that the migration did not only complete technically in the cockpit, but also posted the expected business data into the target application.
Expected Result
After this task is completed successfully:
the app Manage Banks – Master Data is used for verification,
Bank 1 is visible:
US / A###### / Bank of A######
Bank 2 is visible:
US / Z###### / Bank of Z######
the migrated bank data is confirmed as successfully created in the target system.

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:
Task 3: Assign the HR Administrator Business Role to Your User
Objective
The purpose of this task is to assign the HR Administrator business role to your own business user so you can continue the worker, work agreement, and business user setup activities required for the professional services scenario.
The required business role is:
Business Role ID: BR_ADMINISTRATOR_HRINFO
Business Role Description: Administrator – HR Info
Task 3: Assign the HR Administrator Business Role to Your User
Objective
The purpose of this task is to assign the HR Administrator business role to your own business user so you can continue the worker, work agreement, and business user setup activities required for the professional services scenario.
The required business role is:
Business Role ID: BR_ADMINISTRATOR_HRINFO
Business Role Description: Administrator – HR Info
Step 1: Open the app “Maintain Business Users”
From the SAP S/4HANA Cloud launchpad:
Log in to SAP S/4HANA Cloud.
Use the app search or launchpad search.
Search for:
Maintain Business Users
Open the app.
Explanation:
This app is used to maintain user master data and assign business roles.
All business role assignments for your own user are done here.
Step 2: Search for your own user
In Maintain Business Users:
In the filter/search area, enter your own user name or user ID.
Click Go.
Explanation:
You need to open your own user because the HR Administrator role must be assigned to your own account before continuing the simulation.
Step 3: Open your user record
After the search results appear:
Click your own user in the result list.
Open the detail page.
Explanation:
This opens the business user detail screen where all assigned roles can be reviewed and maintained.
Step 4: Switch to Edit mode
On the user detail page:
Click Edit.
Explanation:
Edit mode is required before you can add or remove business roles.
Without edit mode, the Assigned Business Roles tab is display-only.

Step 5: Open the “Assigned Business Roles” tab
Inside your user record:
Click the tab:
Assigned Business Roles
Explanation:
This tab lists all current roles assigned to your user and is the correct place to add BR_ADMINISTRATOR_HRINFO.

Step 6: Click “Add”
In the Assigned Business Roles section:
Click Add
This opens the dialog:
Add Business Roles
Explanation:
This popup allows you to search for standard SAP business roles by ID or description.
Step 7: Search for the HR Administrator role
In the Add Business Roles popup:
In Business Role ID, enter:
BR_ADMINISTRATOR_HRINFO
Click Go
Select the role:
Administrator – HR Info
Business Role ID: BR_ADMINISTRATOR_HRINFO
Explanation:
This is the exact role required by the task.
It gives you the workforce / HR information administration permissions needed for the later simulation steps.
Step 8: Add the role to the user
After selecting the role:
Click OK or Apply
The role should now appear in your assigned roles list.
Explanation:
At this stage, the role is added to the user in draft mode, but it is not yet permanently stored until you save.

Step 9: Save the business user
Back on the business user detail page:
Click Save
Explanation:
Saving is mandatory.
If you do not save, the role assignment remains incomplete and later tasks may fail because your user will not actually have the HR Administrator authorization.
Step 10: Verify the role assignment
After saving, verify that the role appears in the assigned roles list:
BR_ADMINISTRATOR_HRINFO
Administrator – HR Info
Explanation:
This is your proof that the task is complete.
You should see the HR role together with your other assigned roles.
Expected Result
After completing this task successfully:
your user has the HR Administrator role assigned,
the role appears in Assigned Business Roles,
the user is saved successfully,
later worker/business-user creation steps can be performed.
Why this role matters
The role BR_ADMINISTRATOR_HRINFO is required because the scenario involves:
worker information,
work agreement information,
user creation for workshop demonstration,
HR-related administration steps.
In SAP S/4HANA Cloud, access is always role-based, so assigning this role is an authorization prerequisite for later tasks.

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.