SAP C_S4CPB Dumps Questions Answers

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.

Objective

The purpose of this task is to create a new Communication User for the integration scenario Bank Integration with File Interface (1EG) .

This communication user will later be used in the integration setup, especially when defining the communication system and communication arrangement.

Business Scenario Explanation

In this scenario, you are setting up the integration for:

Bank Integration with File Interface (1EG)

In SAP S/4HANA Cloud, technical communication between systems is usually handled through:

a Communication User

a Communication System

a Communication Arrangement

This task is the first step in that chain.

The communication user acts as the technical user that the system uses for integration-related authentication.

Important Notes

Always replace ###### with the last 6 digits of your group number.

Use the exact values shown in the task.

Do not change spaces, underscores, or capitalization.

The password should not be typed manually if the task says:

Have the system propose a password

Required Values

Use the following values exactly as shown in the task image.

Example

If your suffix is 000013, then the values become:

User Name = 1EG_COMM_USER_000013

Description = 1EG Communication User

Step 1: Open the app “Communication Users”

From the SAP S/4HANA Cloud launchpad:

Log in to SAP S/4HANA Cloud.

Use the search bar or app finder.

Search for:

Communication Users or

Maintain Communication Users

Open the app.

Explanation

This app is used to create and maintain technical communication users for integration scenarios.

This is the correct starting point because the task explicitly says to create a Communication User .

Step 2: Start creating a new communication user

Inside the Communication Users app:

Click:

New

Explanation

This starts the creation of a new communication user record.

Step 3: Enter the User Name

In the new communication user screen, enter:

User Name = 1EG_COMM_USER_######

Example

If your suffix is 000013, enter:

1EG_COMM_USER_000013

Explanation

This is the technical identifier for the communication user.

It must match the task exactly.

Step 4: Enter the Description

In the Description field, enter exactly:

1EG Communication User

Explanation

This is the functional description of the technical integration user.

It should be entered exactly as written in the task to avoid validation issues.

Step 5: Let the system propose the password

In the password section:

Do not manually type a password.

Click:

Propose Password

Explanation

The task explicitly says:

Password = Have the system propose a password

So the correct action is to use the SAP-generated password instead of entering your own value manually.

Step 6: Review the generated password

After clicking Propose Password :

The system generates a password automatically.

If the system displays the password, note it down if needed for later integration steps.

Explanation

In some cases, the proposed password may later be needed during communication setup or documentation.

Even if not needed later in the simulation, this confirms the correct procedure was followed.

Step 7: Save the Communication User

Click:

Save

Explanation

This finalizes the creation of the communication user.

Without saving, the technical user will not exist and the later integration steps will fail.

Step 8: Verify the Communication User

After saving, confirm that the communication user exists in the list and displays the correct values:

User Name = 1EG_COMM_USER_######

Description = 1EG Communication User

Explanation

This confirms the task is complete and the user is ready to be used in the next integration setup tasks.

Expected Result

After this task is completed successfully:

the communication user exists,

the user name matches the required naming convention,

the description is correct,

the password was proposed by the system,

the user is saved successfully.

Objective

The purpose of this task is to create a Communication System for the integration scenario Bank Integration with File Interface (1EG) .

This communication system will later be used in the communication arrangement and will reference the communication user created in the previous task.

Business Scenario Explanation

In this scenario, you are setting up:

Bank Integration with File Interface (1EG)

In SAP S/4HANA Cloud, the technical setup typically requires:

a Communication User

a Communication System

a Communication Arrangement

In Task 13 , you created the communication user.

In Task 14 , you now create the communication system and link that previously created communication user for inbound communication.

The communication system represents the external or technical integration partner definition used in the scenario.

Important Notes

Always replace ###### with the last 6 digits of your group number.

Use the exact values shown in the task.

Do not change capitalization, underscores, or spacing.

The communication user assigned in this task must be the one created in the previous step:

1EG_COMM_USER_######

Required Values

Use the following values exactly as shown in the task image.

Example

If your suffix is 000013, then the values become:

System ID = 1EG_SYSTEM_000013

System Name = Bank Integration with File Interface

Host Name = DUMMY

Inbound Communication User = 1EG_COMM_USER_000013

Step 1: Open the app “Communication Systems”

From the SAP S/4HANA Cloud launchpad:

Log in to SAP S/4HANA Cloud.

Use the search bar or app finder.

Search for:

Communication Systems

Open the app.

Explanation

This app is used to create and maintain technical communication systems for integration scenarios.

Because the task explicitly asks to create a Communication System , this is the correct app.

Step 2: Start creating a new Communication System

Inside the Communication Systems app:

Click:

New

Explanation

This starts the creation of a new communication system record.

Step 3: Enter the System ID

In the communication system creation screen, enter:

System ID = 1EG_SYSTEM_######

Example

If your suffix is 000013, enter:

1EG_SYSTEM_000013

Explanation

This is the technical ID of the communication system.

It must exactly match the task requirement.

Step 4: Enter the System Name

In the System Name field, enter exactly:

Bank Integration with File Interface

Explanation

This is the descriptive name of the communication system and must be entered exactly as provided.

Step 5: Enter the Host Name

In the Host Name field, enter exactly:

DUMMY

Explanation

For this simulation, the host is not a real productive endpoint.

The task explicitly requires the placeholder value DUMMY.

Step 6: Maintain the inbound communication user

Locate the section for:

Users for Inbound Communication

Then:

Click Add or select the entry field/value help

Choose the communication user created in the previous task:

1EG_COMM_USER_######

Example

If your suffix is 000013, select:

1EG_COMM_USER_000013

Explanation

This is a critical link between the communication user and the communication system.

Without assigning the previously created communication user, the communication system setup is incomplete.

Step 7: Verify the inbound user assignment

After adding the inbound communication user, confirm that the selected user is:

1EG_COMM_USER_######

Explanation

This confirms that the system will use the correct technical user for inbound communication in the later communication arrangement.

Step 8: Review all entered values

Before saving, check the following:

System ID = 1EG_SYSTEM_######

System Name = Bank Integration with File Interface

Host Name = DUMMY

Users for Inbound Communication = 1EG_COMM_USER_######

Explanation

This review helps avoid validation issues caused by incorrect naming, missing underscores, or selecting the wrong communication user.

Step 9: Save the Communication System

Click:

Save

Explanation

This finalizes the creation of the communication system.

Without saving, the communication system will not exist for the next task.

Step 10: Verify the saved Communication System

After saving, confirm that the communication system exists and displays the correct values:

1EG_SYSTEM_######

Bank Integration with File Interface

Host = DUMMY

inbound user = 1EG_COMM_USER_######

Explanation

This confirms the system is successfully created and ready for the communication arrangement setup in the next step.

Expected Result

After this task is completed successfully:

the communication system exists,

the system ID matches the required naming pattern,

the system name is correct,

the host name is DUMMY,

the previously created communication user is assigned for inbound communication,

the system is saved successfully.