[2026年09月20日] 合格させるC_S4CPB_2602レビューガイド、信頼され続けるC_S4CPB_2602テストエンジン
C_S4CPB_2602テストエンジン練習テスト問題、試験問題集
質問 # 12
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.
質問 # 13
SIMULATION
Business Scenario You are working on an implementation project and need to create a test user in the system for demonstrating the professional services business processes to project managers during your upcoming Fit-to-Standard workshop. Follow the instructions below to create a new test user with a basic import of worker and work agreement data.
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:
Assign the Project Manager - Professional Services (BR_PROJECT_MANAGER_PROF) business role to the new user and save.
正解：
解説：
See Explanation below for all solution
Explanation:
Objective
The purpose of this task is to assign the Project Manager - Professional Services business role to the newly created test user so that the user can perform the professional-services processes required during the Fit-to-Standard workshop.
The required business role is:
Business Role ID: BR_PROJECT_MANAGER_PROF
Business Role Description: Project Manager - Professional Services
Business Scenario Explanation
In the previous task, a new test user was created for demonstrating professional services processes.
That new user now needs the correct project-manager authorization.
Without this business role, the test user will not have access to the project-manager apps, pages, and processes needed for the workshop demonstration.
This task connects the newly created user to the standard professional-services project manager role.
Important Notes
Always replace ###### with the last 6 digits of your group number.
Use the exact values as required.
The business role ID must be:
BR_PROJECT_MANAGER_PROF
Do not use a similar role or partial match.
Save at the end, otherwise the assignment remains incomplete.
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 app search.
Search for:
Maintain Business Users
Open the app.
Explanation:
This app is used to maintain business users and assign business roles.
Since the new user was created in the previous task, this is the correct app to assign the new role.
Step 2: Search for the newly created Project Manager test user
In Maintain Business Users:
In the filter/search area, enter the user name of the new test user.
The required user name format is:
PM######
Example
If your group number suffix is 0000457, then search for:
PM0000457
Click Go.
Explanation:
You must open the newly created project manager test user, not your own user.
The role assignment in this task belongs to the imported test user created in Task 4.
Step 3: Open the new business user record
From the search results:
Click the user entry with:
User Name = PM######
Open the detail page.
Explanation:
This opens the worker/business user record where the Project Manager role will be assigned.
Step 4: Verify that you are on the correct user
Before editing, confirm the business user details are correct.
Typical expected values are:
User Name = PM######
First Name = Project
Last Name = Manager ######
E-Mail = PM######@dummy.sap.com
Explanation:
This check is important because assigning the role to the wrong user would cause the simulation validation to fail.
Step 5: Switch to Edit mode
On the business user detail page:
Click Edit
Explanation:
Edit mode is required so the role list can be changed.
Step 6: Open the "Assigned Business Roles" tab
Inside the business user record:
Click the tab:
Assigned Business Roles
Explanation:
This tab shows all roles currently assigned to the new test user and is the correct place to add the project manager role.
Step 7: Click Add
In the Assigned Business Roles section:
Click Add
The system opens the popup:
Add Business Roles
Explanation:
This popup is used to search and add standard SAP-delivered business roles to the user.
Step 8: Search for the Project Manager role
In the Add Business Roles popup:
In the filter field for business role ID, enter:
BR_PROJECT_MANAGER_PROF
Click Go
Select:
Project Manager - Professional Services
Business Role ID: BR_PROJECT_MANAGER_PROF
Explanation:
This is the exact standard business role required by the task.
It provides the professional-services project manager access for the test user.
Step 9: Add the role
After selecting the role:
Click OK or Apply
Explanation:
At this point, the role is added to the user in draft mode, but the change is not yet final until saved.
Step 10: Save the business user
Back on the user detail page:
Click Save
Explanation:
This is the final required step.
If you do not save, the role assignment will not be stored and the task will not be completed successfully.
Step 11: Verify the assignment
After saving, confirm that the user now has the role:
Project Manager - Professional Services
BR_PROJECT_MANAGER_PROF
Explanation:
This confirms that the new test user is now properly prepared for later professional-services process demonstrations.
Expected Result
After the task is completed:
the new test user PM###### exists,
the role BR_PROJECT_MANAGER_PROF is assigned,
the user is saved successfully,
the user can later be used as a professional-services project manager in the workshop scenario.
質問 # 14
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.
質問 # 15
SIMULATION
Create a Custom Launchpad Space and Page
Business Scenario
You are building a custom business role that will be assigned to all employees in the organization. The business role and its corresponding Launchpad Space and Page need to include the apps that have been granted through the business catalogs assigned to the business role to ensure employees have an easy time finding the relevant applications.
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:
Create a Launchpad Space and Page with the information below.
正解：
解説：
See Explanation below for all solution
Explanation:
Objective
The purpose of this task is to create a custom launchpad space and page for the all-employee business role so employees can easily find the apps granted through the assigned business catalogs.
This task belongs to the all-employee role created in the previous tasks, for example:
Business Role ID: Z_EMPLOYEES_ALL_######
The page values shown in the task are:
Page Title: General
Page Description: General
Business Scenario Explanation
In SAP S/4HANA Cloud, business catalogs grant the app authorizations, but users still need a clean launchpad structure so they can actually find those apps easily.
That is why this task requires creating:
a Launchpad Space
a Launchpad Page
for the all-employee role.
The space acts like a container in the launchpad navigation, and the page acts like the content area where app tiles will later be displayed.
Important Notes
Always replace ###### with the last 6 digits of your group number.
Use the exact text values shown in the task.
The task image explicitly shows:
Page Title = General
Page Description = General
Save each object after creation.
Required Values
From the task image, use:
Parameter
Value
Page Title
General
Page Description
General
Additional execution values used in your run
During your actual execution, the custom launchpad space/page used this pattern:
Space ID: Z_ALL_EMP_######
Space Description: General
Space Title: General
Page ID: Z_ALL_EMP_######
Page Title: General
Page Description: General
Objective
The purpose of this task is to create a custom launchpad space and page for the all-employee business role so employees can easily find the apps granted through the assigned business catalogs.
This task belongs to the all-employee role created in the previous tasks, for example:
Business Role ID: Z_EMPLOYEES_ALL_######
The page values shown in the task are:
Page Title: General
Page Description: General
Business Scenario Explanation
In SAP S/4HANA Cloud, business catalogs grant the app authorizations, but users still need a clean launchpad structure so they can actually find those apps easily.
That is why this task requires creating:
a Launchpad Space
a Launchpad Page
for the all-employee role.
The space acts like a container in the launchpad navigation, and the page acts like the content area where app tiles will later be displayed.
Important Notes
Always replace ###### with the last 6 digits of your group number.
Use the exact text values shown in the task.
The task image explicitly shows:
Page Title = General
Page Description = General
Save each object after creation.
Required Values
From the task image, use:
Parameter
Value
Page Title
General
Page Description
General
Additional execution values used in your run
During your actual execution, the custom launchpad space/page used this pattern:
Space ID: Z_ALL_EMP_######
Space Description: General
Space Title: General
Page ID: Z_ALL_EMP_######
Page Title: General
Page Description: General
質問 # 16
SIMULATION
Create a Custom Launchpad Space and Page
Business Scenario
You are building a custom business role that will be assigned to all employees in the organization. The business role and its corresponding Launchpad Space and Page need to include the apps that have been granted through the business catalogs assigned to the business role to ensure employees have an easy time finding the relevant applications.
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
Create a new business role (not from a template) with the information below.
正解：
解説：
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.
質問 # 17
SIMULATION
Business Scenario
You are working on an implementation project and need to assign yourself the Administrator business role to complete your job tasks. Follow the instructions below to assign the Administrator business role to your user.
Prerequisites Note:
In the task below, always replace ###### with the last 6 digits of your group number.
Your Task 1.
Assign the Administrator (BR_ADMINISTRATOR) business role to your user and save.
正解：
解説：
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.
質問 # 18
SIMULATION
Note: In this practical certification exam, you will only be given high-level instructions. The step descriptions are complete and tested to work. They are not detailed, as this is a test of your knowledge of navigating the system on your own.
Caution: Please make sure you are always using your assigned group number. The last 6 digits are denoted as ###### in the following tasks. Your results will not be recorded if you are not using your own group number. To find your group number: Select your user in the top right corner. You will see your user name with a series of numbers. Use the last 6 digits as your group number Caution: To keep the system running smoothly and avoid unnecessary costs, please follow the assigned exercises carefully when using the SAP Landscape. Avoid going beyond the exercise scope and only use your group number to help maintain a stable and efficient environment for everyone.
正解：
解説：
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
質問 # 19
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:
Migrate the bank data listed below.
Table 1: Bank 1
正解：
解説：
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.
質問 # 20
......
100%無料C_S4CPB_2602日常練習試験には20問があります：https://www.goshiken.com/SAP/C_S4CPB_2602-mondaishu.html