Free SAP C-S4CPB-2602 Practice Test & Real Exam Questions
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.
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.
Correct Answer:
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.
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.
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.
Your Task
Assign the Configuration Expert - Data Migration (BR_CONFIG_EXPERT_DATA_MIG) business role to your user and save.
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.
Your Task
Assign the Configuration Expert - Data Migration (BR_CONFIG_EXPERT_DATA_MIG) business role to your user and save.
Correct Answer:
See Explanation below for all solution
Explanation:
Objective
The purpose of this task is to assign the Configuration Expert - Data Migration business role to your own user so that you can use the migration cockpit and perform the bank data migration scenario using staging tables.
The required business role is:
Business Role ID: BR_CONFIG_EXPERT_DATA_MIG
Business Role Description: Configuration Expert - Data Migration
Business Scenario Explanation
In this scenario, you are responsible for migrating bank data into SAP S/4HANA Cloud Public Edition.
Because only a few banks need to be loaded, the chosen migration method is:
Migrate Data Using Staging Tables
Before you can use migration apps such as Migrate Your Data, your user must have the correct migration authorization.
That is why this task requires assigning the business role:
Configuration Expert - Data Migration
BR_CONFIG_EXPERT_DATA_MIG
Without this role, you may not be able to:
create migration projects,
open migration objects,
upload staging-table files,
validate and transfer data,
execute mapping tasks,
or run the migration itself.
Important Notes
Always replace ###### with the last 6 digits of your group number in later migration tasks.
Use the exact role ID required by the task:
BR_CONFIG_EXPERT_DATA_MIG
Save the user after role assignment.
Make sure the user is not left only in draft status.
Required Role
Field
Value
Business Role ID
BR_CONFIG_EXPERT_DATA_MIG
Business Role Description
Configuration Expert - Data Migration
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.
Use the app search.
Search for:
Maintain Business Users
Open the app.
Explanation:
This app is used to assign business roles to business users.
Since the task asks to assign a role to your own user, this is the correct starting point.
Step 2: Search for your own user
Inside Maintain Business Users:
In the search/filter area, enter your own user ID.
Click Go.
Explanation:
You must assign the migration role to your own user because you are the one who will execute the migration tasks.
Step 3: Open your user record
From the search results:
Click your user entry.
Open the business user details page.
Explanation:
This opens the screen where assigned roles can be reviewed and maintained.
Step 4: Switch to Edit mode
On the business user page:
Click Edit
Explanation:
Edit mode is necessary before the Assigned Business Roles list can be changed.
Step 5: Open the "Assigned Business Roles" tab
Inside the business user record:
Click:
Assigned Business Roles
Explanation:
This is the section where the new business role will be assigned.
Step 6: Click Add
In the Assigned Business Roles area:
Click Add
This opens the popup:
Add Business Roles
Explanation:
This popup allows you to search for and assign standard SAP business roles.
Step 7: Search for the migration role
In the Add Business Roles popup:
In the role search field, enter:
BR_CONFIG_EXPERT_DATA_MIG
Click Go
Select:
Configuration Expert - Data Migration
BR_CONFIG_EXPERT_DATA_MIG
Explanation:
This is the exact role required for the bank migration scenario.
Step 8: Add the role
After selecting the role:
Click OK or Apply
Explanation:
This adds the migration role to your user in draft mode.
Step 9: Save the user
Back on the business user page:
Click Save
Explanation:
This finalizes the assignment.
Without saving, the role will not be available for use in the migration tasks.
Step 10: Verify the role assignment
After saving, confirm that your assigned roles list includes:
Configuration Expert - Data Migration
BR_CONFIG_EXPERT_DATA_MIG
Explanation:
This verifies that your user is now authorized to work with migration projects and staging-table migration.
Expected Result
After this task is completed successfully:
your user has the role BR_CONFIG_EXPERT_DATA_MIG,
the role assignment is saved,
your user can proceed with the bank migration project tasks,
migration-related apps are available to your user.
Explanation:
Objective
The purpose of this task is to assign the Configuration Expert - Data Migration business role to your own user so that you can use the migration cockpit and perform the bank data migration scenario using staging tables.
The required business role is:
Business Role ID: BR_CONFIG_EXPERT_DATA_MIG
Business Role Description: Configuration Expert - Data Migration
Business Scenario Explanation
In this scenario, you are responsible for migrating bank data into SAP S/4HANA Cloud Public Edition.
Because only a few banks need to be loaded, the chosen migration method is:
Migrate Data Using Staging Tables
Before you can use migration apps such as Migrate Your Data, your user must have the correct migration authorization.
That is why this task requires assigning the business role:
Configuration Expert - Data Migration
BR_CONFIG_EXPERT_DATA_MIG
Without this role, you may not be able to:
create migration projects,
open migration objects,
upload staging-table files,
validate and transfer data,
execute mapping tasks,
or run the migration itself.
Important Notes
Always replace ###### with the last 6 digits of your group number in later migration tasks.
Use the exact role ID required by the task:
BR_CONFIG_EXPERT_DATA_MIG
Save the user after role assignment.
Make sure the user is not left only in draft status.
Required Role
Field
Value
Business Role ID
BR_CONFIG_EXPERT_DATA_MIG
Business Role Description
Configuration Expert - Data Migration
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.
Use the app search.
Search for:
Maintain Business Users
Open the app.
Explanation:
This app is used to assign business roles to business users.
Since the task asks to assign a role to your own user, this is the correct starting point.
Step 2: Search for your own user
Inside Maintain Business Users:
In the search/filter area, enter your own user ID.
Click Go.
Explanation:
You must assign the migration role to your own user because you are the one who will execute the migration tasks.
Step 3: Open your user record
From the search results:
Click your user entry.
Open the business user details page.
Explanation:
This opens the screen where assigned roles can be reviewed and maintained.
Step 4: Switch to Edit mode
On the business user page:
Click Edit
Explanation:
Edit mode is necessary before the Assigned Business Roles list can be changed.
Step 5: Open the "Assigned Business Roles" tab
Inside the business user record:
Click:
Assigned Business Roles
Explanation:
This is the section where the new business role will be assigned.
Step 6: Click Add
In the Assigned Business Roles area:
Click Add
This opens the popup:
Add Business Roles
Explanation:
This popup allows you to search for and assign standard SAP business roles.
Step 7: Search for the migration role
In the Add Business Roles popup:
In the role search field, enter:
BR_CONFIG_EXPERT_DATA_MIG
Click Go
Select:
Configuration Expert - Data Migration
BR_CONFIG_EXPERT_DATA_MIG
Explanation:
This is the exact role required for the bank migration scenario.
Step 8: Add the role
After selecting the role:
Click OK or Apply
Explanation:
This adds the migration role to your user in draft mode.
Step 9: Save the user
Back on the business user page:
Click Save
Explanation:
This finalizes the assignment.
Without saving, the role will not be available for use in the migration tasks.
Step 10: Verify the role assignment
After saving, confirm that your assigned roles list includes:
Configuration Expert - Data Migration
BR_CONFIG_EXPERT_DATA_MIG
Explanation:
This verifies that your user is now authorized to work with migration projects and staging-table migration.
Expected Result
After this task is completed successfully:
your user has the role BR_CONFIG_EXPERT_DATA_MIG,
the role assignment is saved,
your user can proceed with the bank migration project tasks,
migration-related apps are available to your user.
