SIMULATION
Migrate Bank Data
Business Scenario
You are responsible for migrating bank data into the SAP S/4HANA Cloud Public Edition system. You have determined the best method is Migrate Data Using Staging Tables, as you only have a couple banks to migrate.
Prerequisites:
Note:
In the task below, always replace ###### with the last 6 digits of your group number.
Note:
Make sure to use the EXACT names/values/spaces as they are listed in the task. Even forgetting a space or a number will cause the validation of the task to fail and be marked as incorrect.
Task:
Use the correct app to verify your data has been migrated successfully (see the documentation for the Bank migration object).

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.

SIMULATION
Create a Custom Business Role with Restrictions
Business Scenario:
You are building a custom business role with restrictions to ensure the end users assigned the role have only the minimum level of access necessary to complete their core job tasks. The end users are project managers based in the United States. They should only be able to create projects, edit projects, and access projects that are occurring in the United States. They should not be able to staff any resources outside of the United States. Write, Read, and Value Help access should be restricted to only the United States for all relevant fields.
Prerequisites:
Note: In the task below, always replace ###### with the last 6 digits of your group number.
Note: Make sure to use the EXACT names/values/spaces as they are listed in the task. Even forgetting a space or a number will cause the validation of the task to fail and be marked as incorrect.
Task:
Restrict the fields listed below for the US / 1710. All other fields should be marked as Not Maintained. Save the role when finished.

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.