Antwort:

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

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

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

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

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

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

Antwort:

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.