Task 1: Create Directories

You need to create these directories:

Americas

Eurasia

Partner under Americas with label access=external

Human Resources under Eurasia with label access=internal

Before You Start

Log in to the SAP BTP Cockpit .

Make sure you are inside the correct Global Account .

Open the left-side navigation menu.

Why this is important:

All directories in this task must be created inside the correct global account hierarchy. If you create them in the wrong location, the simulation result will be incorrect.

Step 1 — Create Directory Americas

What to do

In the SAP BTP Cockpit, select your Global Account .

In the left navigation menu, click Directories .

Click Create or Create Directory .

Fill the fields as follows:

Name: Americas

Description: Americas Accounts

Parent: your Global Account

Click Create .

Explanation

This creates a top-level directory directly under the global account.

It will later be used as the parent for the Partner directory.

What to verify

After creation, you should see:

Americas

listed under the directories of the global account.

Step 2 — Create Directory Eurasia

What to do

Stay in Directories .

Click Create Directory again.

Fill the fields:

Name: Eurasia

Description: Eurasia Accounts

Parent: your Global Account

Click Create .

Explanation

This creates another top-level directory, parallel to Americas .

What to verify

You should now see both:

Americas

Eurasia

under the global account.

Step 3 — Create Directory Partner under Americas

What to do

In the Directories area, select Americas .

Click Create Directory .

Enter:

Name: Partner

Description: Partner Accounts

Parent: Americas

Locate the Labels section.

Add a new label:

Key: access

Value: external

Click Create .

Explanation

This creates Partner as a child directory under Americas .

The label is required and must be entered exactly:

access = external

This label helps classify the directory.

What to verify

Under Americas , you should now see:

Partner

and the directory should contain the label:

access=external

Step 4 — Create Directory Human Resources under Eurasia

What to do

Go back to the Directories list.

Select Eurasia .

Click Create Directory .

Enter:

Name: Human Resources

Description: Human Resources Accounts

Parent: Eurasia

In the Labels section, add:

Key: access

Value: internal

Click Create .

Explanation

This creates Human Resources as a child directory under Eurasia .

The required label is:

access = internal

What to verify

Under Eurasia , you should now see:

Human Resources

and the label should be:

access=internal

Final Expected Directory Structure

After completing Task 1, your structure must be exactly like this:

Global Account

Americas

Partner

Label: access=external

Eurasia

Human Resources

Label: access=internal

Important Checks Before Moving On

Verify all of the following:

Americas exists

Eurasia exists

Partner is under Americas

Human Resources is under Eurasia

Partner has label access=external

Human Resources has label access=internal

All names and descriptions are entered exactly as required

Common Mistakes to Avoid

1. Wrong parent

Partner must be created under Americas

Human Resources must be created under Eurasia

2. Wrong label key or value

Use exactly:

access → external

access → internal

3. Spelling errors

Be careful with:

Americas

Eurasia

Partner

Human Resources

4. Creating all directories directly under the global account

Only Americas and Eurasia are direct children of the global account.

Partner and Human Resources must be child directories.

Before you start

Log in to SAP BTP Cockpit .

Open the correct Global Account .

Go to Directories .

Open Human Resources .

Open the EU HCM Dev subaccount.

This matters because the task must be completed specifically in EU HCM Dev . SAP documents that Cloud Foundry is enabled at subaccount level, and the system creates a Cloud Foundry org linked to that subaccount.

Part 1 — Enable the Cloud Foundry environment

Step 1 — Open the subaccount overview

In EU HCM Dev , go to Overview .

Explanation

SAP Help describes the cockpit flow for enabling Cloud Foundry from the subaccount Overview page.

What to verify

You should see a Cloud Foundry section on the overview page.

Step 2 — Start enabling Cloud Foundry

In the Cloud Foundry section, click Enable Cloud Foundry .

Explanation

This starts creation of the Cloud Foundry organization for the subaccount. SAP notes that when you enable Cloud Foundry in a subaccount, the system automatically creates a Cloud Foundry org for it.

Step 3 — Enter the required Cloud Foundry values

In the enablement dialog, enter:

Landscape: cf-eu10-004

Instance Name: cf-eu-hcm-dev

Org Name: btpops####-eu-hcm-dev

Then confirm by clicking Create or Enable .

Explanation

The task gives you the exact landscape and naming values to use. SAP documentation shows that enabling Cloud Foundry in the cockpit requires naming the Cloud Foundry instance and org.

What to verify

After the process completes, the subaccount should show Cloud Foundry as enabled, with the org created for EU HCM Dev .

Part 2 — Create the space

Step 4 — Open Spaces

In EU HCM Dev , after Cloud Foundry is enabled, open:

Cloud Foundry

Spaces

Explanation

SAP Help shows that spaces are created from the Spaces area after Cloud Foundry is enabled in the subaccount.

Step 5 — Create the space

Click Create Space .

Enter:

Space Name: activity-recording

Confirm by clicking Create .

Explanation

This creates the required Cloud Foundry space inside the org for EU HCM Dev . SAP’s cockpit documentation and setup guides show this as the standard next step after enabling the environment.

What to verify

You should now see:

activity-recording

in the list of Cloud Foundry spaces.

Part 3 — Create the space quota

Step 6 — Open Cloud Foundry Space Quotas

In EU HCM Dev , open:

Cloud Foundry

Space Quotas

Explanation

SAP Help states that, in the Cloud Foundry environment, the quotas allocated to a subaccount can be further distributed by creating space quota plans , and these are managed from the Cloud Foundry Space Quotas area.

Step 7 — Create a new space quota

Click Create Space Quota or New Space Quota .

Enter the quota name:

half-org-quota

Explanation

This creates a quota plan that you will assign to the required space. SAP Help describes creating space quota plans in the subaccount and then assigning them to spaces.

Step 8 — Set quota values to half of the org quota

In the quota form, set the values to half of the available org quota for:

Memory

Routes

Services

Instance Memory

For App Instances , set:

Unlimited

Then save the quota.

Explanation

The simulation asks you to halve the available org quota for those four dimensions. SAP Help confirms that space quotas are used to limit resource consumption inside the org by defining values such as memory, routes, and service instances, and that these plans can then be assigned to spaces.

How to calculate “half”

Use the current org quota values shown in the Cloud Foundry quota screens and divide each by 2 before entering it.

Examples:

If org memory = 2 GB , enter 1 GB

If routes = 20 , enter 10

If services = 200 , enter 100

If instance memory = 2 GB , enter 1 GB

What to verify

The new quota plan should exist as:

half-org-quota

with the reduced values saved.

Part 4 — Assign the quota to the space

Step 9 — Assign the quota to activity-recording

Open the newly created quota:

half-org-quota

Choose Assign Spaces or Assign to Spaces

Select:

activity-recording

Save the assignment

Explanation

SAP Help states that after creating a space quota, you assign it to one or more spaces from the space quota management flow.

What to verify

The quota half-org-quota should now be assigned to:

activity-recording

Final expected result

Inside EU HCM Dev :

Cloud Foundry is enabled

landscape is cf-eu10-004

instance name is cf-eu-hcm-dev

org name is btpops####-eu-hcm-dev

space activity-recording exists

space quota half-org-quota exists

memory, routes, services, and instance memory are each set to half of the available org quota

app instances are unlimited

quota half-org-quota is assigned to activity-recording

Common mistakes to avoid

Enabling Cloud Foundry in the wrong subaccount; it must be EU HCM Dev .

Using the wrong landscape; the task explicitly requires cf-eu10-004 .

Typing the wrong org name; use exactly btpops####-eu-hcm-dev.

Forgetting to create the space before assigning the quota.

Entering full org quota instead of half .

Limiting app instances to a number instead of leaving them unlimited .

Creating the quota but not assigning it to activity-recording.

Task 2 — Create Subaccounts in a Directory

You must create these two subaccounts inside the Partner directory:

AM PA Dev Test

AM PA Prod

Important:

Replace #### with your global account number

Enter all names and subdomains exactly

Be careful with hyphens and spaces

AM PA Prod must be marked as used in production

Before You Start

Log in to SAP BTP Cockpit .

Open your correct Global Account .

Go to Directories .

Open the Partner directory.

Why this matters:

Both subaccounts in this task must be created inside the Partner directory. If you create them under the global account or another directory, the task will be wrong.

Step 1 — Open the Partner Directory

What to do

In the left menu, click Directories .

In the directory list, select Partner .

Explanation

The Partner directory is the container where both required subaccounts must be created.

What to verify

You should now be inside the Partner directory page.

Step 2 — Start Creating the First Subaccount

What to do

Inside the Partner directory, go to Subaccounts .

Click Create → Subaccount .

Explanation

This opens the subaccount creation screen.

What to verify

You should now see the form for creating a new subaccount.

Step 3 — Enter Data for AM PA Dev Test

What to do

Enter the following values:

Display Name / Name: AM PA Dev Test

Description: Partner Development and Testing

Subdomain: btpops####-am-pa-dev-test

Then choose the region:

Cloud Provider: Microsoft Azure

Region: US West (WA)

Environment / Technical Region: cf-us20

After checking all values, click Create .

Explanation

This creates the development and testing subaccount for the Partner directory.

The important points are:

the subaccount name must match exactly

the subdomain must include your account number in place of ####

the region must be Microsoft Azure → US West (WA) cf-us20

What to verify

After creation, you should see the new subaccount:

AM PA Dev Test

inside the Partner directory.

Step 4 — Confirm the First Subaccount Exists

What to do

Check the subaccounts list under Partner .

Explanation

Before creating the production subaccount, confirm that AM PA Dev Test was created successfully, because it will be used as the source subaccount for the next step.

What to verify

You should see:

AM PA Dev Test

If it is not there, do not continue until it is created correctly.

Step 5 — Start Creating the Second Subaccount

What to do

Still inside the Partner directory, click Create → Subaccount again.

Explanation

This opens a new subaccount creation form for the production subaccount.

Step 6 — Enter Data for AM PA Prod

What to do

Enter the following values:

Display Name / Name: AM PA Prod

Description: Partner Production

Subdomain: btpops####-am-pa-prod

Then set:

Source Subaccount: AM PA Dev Test

Enable the production setting:

Used in Production: Yes

Then click Create .

Explanation

This creates the production subaccount by using AM PA Dev Test as the source subaccount.

Using a source subaccount means SAP BTP copies base settings from the selected source, which helps keep configuration aligned.

The production indicator is mandatory here because this is the production subaccount.

What to verify

After creation, you should see:

AM PA Prod

inside the Partner directory, and it should be marked as a production subaccount.

Final Expected Result for Task 2

Inside the Partner directory, you must have these two subaccounts:

1. AM PA Dev Test

Description: Partner Development and Testing

Subdomain: btpops####-am-pa-dev-test

Region: Microsoft Azure → US West (WA) cf-us20

2. AM PA Prod

Description: Partner Production

Subdomain: btpops####-am-pa-prod

Source Subaccount: AM PA Dev Test

Used in Production: Yes

Common Mistakes to Avoid

1. Creating the subaccounts in the wrong place

Both subaccounts must be created in:

Partner directory

Not in:

Global Account

Americas

Eurasia

Human Resources

2. Wrong subdomain format

Use exactly:

btpops####-am-pa-dev-test

btpops####-am-pa-prod

Replace only #### with your global account number.

Do not:

remove hyphens

add spaces

misspell dev-test or pa-prod

3. Wrong region for AM PA Dev Test

It must be:

Microsoft Azure

US West (WA)

cf-us20

4. Forgetting the source subaccount for AM PA Prod

You must select:

AM PA Dev Test

as the source subaccount.

5. Forgetting the production flag

For AM PA Prod , make sure:

Used in Production is enabled