Initiating the Project in the Prepare Phase

Configuring the Project Environment

Objective

After completing this lesson, you will be able to set up the SAP SuccessFactors HCM environment during the Prepare phase by requesting an SAP Cloud ALM tenant, provisioning system instances, managing access and security, and activating end-user guidance tools.

Request SAP Cloud ALM Tenant

Purpose

The purpose of this task is to request an SAP Cloud ALM tenant. SAP Cloud ALM is an essential how-to solution for managing all aspects of any SAP cloud solution. It assists customers through the initial implementation, going live, monitoring integrations, to running and continuously optimizing your instance.

Customers are entitled to use SAP Cloud ALM if they subscribe to an SAP Cloud Service that includes SAP Enterprise Support and cloud editions.

Procedure

  1. Follow the Help - Requesting SAP Cloud ALM accelerator to request access to SAP Cloud ALM.

  2. Refer to Help - SAP Cloud ALM for additional support.

Procedure Note(s)

  • For further questions or feedback, please send an email to cloudalm@sap.com.
  • Learn about SAP Cloud ALM by reviewing the SAP Cloud ALM - Functional Overview.pdf accelerator or the Self-Enable on SAP Cloud ALM.

Accelerator(s)

SAP SuccessFactors HCM Environment Set Up

Setting up the SAP SuccessFactors HCM environment involves following activities:

  1. Provisioning the required instances
  2. Managing Security Access
  3. Setting up System Architecture

Let’s go through each in detail, beginning with how to get the systems ready for the project team.

1. Provisioning the Required Instances

Before any configuration can begin, you must ensure the correct system instances are available and that both the client and consultant teams can access them.

Where to check which instances the client has?

  • Review the Statement of Work (SOW): Check if it mentions anything about a pre-defined instance strategy from the sales cycle.

  • Identify instances for use: Search for your client and you will be able to see the instances that have been provisioned for this client.
    1. Navigate to the system using the following link: Login
    2. Go to the Cloud Provisioning section and open the Details view.
    3. Scroll down to locate BIZX. This is the identifier used for the SAP SuccessFactors tenant.
    4. If Learning (LMS) is in scope, ensure the LMS tenant is identified and connected to the BizX tenant before proceeding.
    5. Click the Tenant ID link on the BIZX row to continue.
Terminology
  • SAP SuccessFactors often uses the term instances instead of environments.
  • BizX is the technical name for the SAP SuccessFactors tenant. There are always at a minimum 2 BizX tenants provisioned:
    • Preview
    • Production
  • LMS is the tenant for SAP Learning, which is part of the SAP SuccessFactors suite.

How does the client get access?

  1. The primary Client contact listed on the SAP SuccessFactors contract will receive an email from SAP with access details for the SAP SuccessFactors tenants. This includes username and password (in a separate email).

  2. This email is often sent immediately after the contract is signed and processed, so it may have arrived several weeks before you start your implementation. Advise your client contact to check their inbox and junk mail folder thoroughly.

  3. If the client already has a SAP SuccessFactors product and therefore a system admin, that system admin should get hold of any new instances that may have been provisioned and that email will help achieve that.

  4. If the client doesn't have a System Admin, they should forward you that email so you can temporarily act as the client admin and help provision the access to the consultants.

How does the consultant get access?

Typically, the Client’s System Administrator will log into the SAP SuccessFactors Admin Center and grant Provisioning Access to all consultants by adding their name and email.

Once access is provisioned, the next step is to configure security permissions to ensure team members have the appropriate level of access.

2. Managing Security Access

After the consultant(s) have access to Provisioning, they will:

  1. Create a user account for themselves that will have admin permissions.

  2. Adjust role-based permissions and either create or adjust the SAP SuccessFactors admin user role.

Until the project enters the Realize phase, the number of users should be kept to a minimum:

  • Client Admins - Typically one to three people.
  • SAP Consultants - Lead, Nearshore and Offshore consultants will need administrator roles for Explore workshops and pre-configuration.

3. Set Up System Architecture

The final task is to formalize the high-level governance for the system architecture.

To define architecture for the SAP SuccessFactors environment:

  1. Work with your SAP SuccessFactors Solutions Architect to define the environment strategy.

  2. Ensure this is aligned with any other project happening in parallel. For example, if customer is also reviewing SAP S/4HANA while SAP SuccessFactors Employee Central is being implemented, you will want to ensure both the SAP S/4HANA and SAP SuccessFactors environment strategies are aligned.

The SAP SuccessFactors landscape is provisioned as a set of independent tenants — typically a Preview Instance and a Production Instance. Additional instances (e.g., Test, Sales Demo, or Training) may be provisioned when specifically scoped in the SOW.

Note

Unlike traditional on-premise landscapes, SuccessFactors configuration is not "copied" wholesale between tenants via transports. Instead, configuration is re-applied or synchronized between instances using SAP SuccessFactors-provided tools (e.g., Instance Sync, Instance Refresh) and manual re-configuration, each with specific rules, limitations, and dependencies.

The specific instance landscape for each project (e.g., 2-tier vs. 3-tier, additional training or demo instances) is defined in the customer’s SOW. Always confirm the agreed-upon landscape with the customer and SAP SuccessFactors Architecture team before provisioning.

Watch the video to explore an example of a SAP SuccessFactors instance strategy and understand how each environment connects across the implementation lifecycle, from development to go-live.

Key Points from Video
  • Preview Instance as the Starting Point — All configuration work begins in the preview instance, which serves as the development sandbox where the team builds, unit tests, approves configurations, and validates upcoming SAP release features before they reach any other environment.

  • Configuration Migration Ensures Consistency — Rather than rebuilding approved configurations from scratch, a structured migration path is used to move validated work from the preview instance to the production stack, saving significant time and maintaining consistency across environments.

  • QA/Test Instance as the Primary Testing Environment — The QA/Test instance is the central hub for all major testing activities, including User Acceptance Testing (UAT) and System Integration Testing (SIT), and uses refreshed, anonymized production data to ensure testing is as realistic as possible.

  • Specialized Instances for Specific Needs — The production stack includes purpose-built instances beyond QA, such as a parallel payroll testing instance for side-by-side calculation validation and a data migration instance dedicated to practicing large-scale employee data loads.

  • Final Migration as the Gateway to Go-Live — Only after stakeholder sign-off in the QA instance is a final configuration migration performed, moving fully approved and validated configurations into the live production environment in preparation for Go-Live.

  • Production Instance as the Live Destination — The production instance is the ultimate environment used daily by employees, managers, and HR teams, housing all live transactions and real employee data, with a strict standard that only perfected configurations reach it.

  • Optional Instances for Special Scenarios — Additional instances may be introduced on an as-needed basis to support complex activities such as advanced data migration, user training, or isolated testing of new modules without disrupting the main project flow.

The following tables describe the purpose and key characteristics of each instance in the recommended landscape architecture during implementation.

Preview InstanceQA / Test InstanceProduction Instance
  • Used for development, unit testing, and approving configuration.
  • Used to validate Preview release content before it moves forward.
  • May be connected to third-party applications for end-to-end testing.
  • Approved configuration is moved from Preview to Quality Assurance.
  • Data can be loaded and/or refreshed from Production.
  • Used for testing and support of Production escalations.
  • Used for User Acceptance Testing (UAT) and System Integration Testing (SIT).
  • Connected to all third-party applications for end-to-end testing.
  • Data should be refreshed from Production (PRD) and anonymized.
  • Configurations are migrated from Preview (DEV) upon approvals.
  • Used for testing and support of Production (PRD) escalations.
  • Environment for all live transactions and data management.
  • Connected and integrated to all third-party applications.
Parallel Payroll Testing InstanceData Migration InstanceAdditional Instances
  • Used for parallel payroll testing.
  • Requires production-grade data.

Used for iterative data loads

  • Payroll Parallel Testing
  • Data Migration and/or Training
  • Testing of a new module or specific functionality
  • Processes that have unique integration or data requirements

Note

During implementation, pay close attention to project timelines and release dates overlapping. Evaluation and migration of new features to Production may affect implementation project timelines.

Leveraging Pre-Configured Leading Practices

Where project timelines allow, customers can accelerate the Prepare phase by leveraging pre-configured SAP SuccessFactors leading-practice content:

  • Request access to a pre-configured Demo Environment as part of Embedded Launch Activities to experience leading practices firsthand.
  • Apply leading-practice baseline configuration to the Preview instance so that Fit-to-Standard workshops in the Explore phase begin from a working example rather than an empty tenant.
  • Reference SAP SuccessFactors Architecture Leading Practices (SAP Customer) for guidance on recommended starting configurations.

This approach reduces the volume of net-new decisions required during Explore and helps ground stakeholder conversations in a tangible, working example of the solution.

Initial System Access for SAP Cloud ALM

Purpose

To access SAP Cloud ALM and complete the necessary setup before using the solution.

If the SAP Cloud ALM tenant is already established and fully configured, ensure that all required integrations are properly set up. In SAP Cloud ALM, SAP Activate content is integrated, providing enhanced project and task management functionality. Once this task is completed, it should be the primary source for following SAP Activate.

Prerequisite

Received email with access information to SAP Cloud ALM tenant.

Procedure

  1. Read the overviews and follow the procedures listed under Help - Required Setup for SAP Cloud ALM to complete the required setup of SAP Cloud ALM. If you need help, refer to our Help - Troubleshooting and FAQ for SAP Cloud ALM or SAP for Me - Schedule an Expert.

  2. Create a project for your implementation using the Projects and Setup app within SAP Cloud ALM. To automatically derive tasks from the SAP Activate methodology, select the relevant product-related roadmap (depending on the transition path, either new implementation, system conversion, or selective data transition) or several combinable roadmaps. This ensures your team is using the right roadmap for implementing your cloud product.

    For guidance, see the in-app help and/or topic ‘Projects and Setup - Creating a Project’ in Help - SAP Cloud ALM for Implementation.

Procedure Note(s)

Additional integration and configuration options help customers leverage the full capabilities of SAP Cloud ALM, including integrations with SAP LeanIX, SAP Signavio, and Tricentis.

For more information, review the Integration and Configuration Options after the section for Help - Required Setup for SAP Cloud ALM.

Accelerators

Request Provisioning Access to SAP SuccessFactors

The purpose of this task is for the customer administrator to request provisioning access for the consultants or partners to SAP SuccessFactors development and test tenants.

Prerequisite

  • The consultant or partner must have achieved Associate Certification and completed the periodic delta assessment for each product module they will implement.
  • The implementation partner must have access to Customer Instance Access Requests (CAR).

Procedure

  1. Add the implementation consultants or partners to the provisioning users following the step-by-step description attached to SAP Note 2519639 - Manage Provisioning Access Tool in SAP SuccessFactors. [Only SAP Customers, SAP Partners, and SAP Employees can access SAP Notes.]

  2. Request the consultants or partners to access the Customer Instance Access Requests (CAR) and follow the instructions on the page. [Only approved SAP Partners can access this accelerator.]
    • You can include multiple people in a single request.
    • Request access for Development and Test together during the Prepare phase.
    • Request Production access separately during the Realize phase.

Accelerators

Add Super Admin Access to Your Account

Purpose

To grant access to users who require Super Admin and/or Role-Based Permission in the SAP SuccessFactors instance.

The updated Manage RBP Admin and Super Admin Access page allows you to efficiently manage both super administrators and Role-Based Permission administrators within the system.

This task is repeated for the Development, Test, and Production tenants.

Procedure

Setup the super admin users by following the procedure in Help - Managing RBP Admin and Super Admin Access

Accelerators

Create Initial User in the Employee Central Payroll Development System

Purpose

To create the initial project users in the SAP SuccessFactors Employee Central Payroll Development system. This is applicable only when SAP SuccessFactors Employee Central Payroll is in scope.

All the three systems are provisioned at the same time.

Prerequisite

  • Access information provisioning email
  • Initial password provisioning email

Procedure

  1. Reset the passwords for the systems, Development, Test and Production, listed in the provisioning email. Initial passwords expire after 10 days after provisioning.

  2. Follow the instruction in SAP Note 2534043 - Getting started with Employee Central Payroll - initial user.[Only SAP Customers, SAP Partners, and SAP Employees can access SAP Notes.]

Accelerators

Activate SAP - Managed WalkMe Content for End Users

Purpose

To understand how the SAP-managed WalkMe content is integrated across various SAP solutions and learn how to enable it.

SAP provides prebuilt WalkMe content for certain products (e.g., SAP Ariba, SAP SuccessFactors, SAP Concur, SAP S/4HANA Cloud). Activating WalkMe makes this content available to your users. This task guides administrators through activating SAP-managed WalkMe content so that end users benefit from the built-in, step-by-step guidance within SAP solutions. Activating WalkMe enables contextual help, accelerates user adoption and training, and provides analytics on how users interact with the software.

Procedure

  1. Review WalkMe Interactive Demo to understand what WalkMe is and its value across SAP solutions.

  2. Identify Your SAP Solution: Determine which SAP solution(s) you are implementing: Ariba, Fieldglass, SuccessFactors, Concur, or SAP S/4HANA Cloud, etc. and follow the solution-specific guidance:

    1. SAP S/4HANA Cloud: The WalkMe-based alternative user experience for in-app help will not automatically be available in your system but requires that you activate the Toggle the SAP-enabled WalkMe integration (APS_UI_WME_INTEGRATION) feature in the Activate Features configuration activity. Follow instructions via Set Up Your SAP S/4HANA Cloud Public Edition - Activate Features

    2. SAP Ariba: Review WalkMe in SAP Ariba to understand SAP WalkMe integration with SAP Ariba and its release schedule.
      1. Enable WalkMe for SAP Ariba Guided Buying, if applicable, by following the Implementation Details in SAP Ariba Guided Buying Integration with SAP WalkMe.

      2. Enable WalkMe for SAP Ariba Guided Sourcing, if applicable, by following the Implementation Details in SAP Ariba Guided Sourcing Integration with SAP WalkMe.

    3. SAP SuccessFactors: Enable WalkMe content by following Help - Showing SAP SuccessFactors-Managed WalkMe Content to Users.

    4. SAP Concur: Follow the WalkMe Enhancements to Concur User Assistance to activate and display the available WalkMe Walkthroughs. For customers with WalkMe or WalkMe Premium for SAP Concur solutions enabled, the User Assistance Settings page will be renamed to WalkMe Settings.

    5. SAP Sales Cloud: Follow SAP Cloud for Customer - Configure WalkMe In-App Help to activate and display the available WalkMe walkthroughs.

    6. SAP Fieldglass: Review WalkMe Walkthroughs Available in SAP Fieldglass to understand the smart walkthroughs using WalkMe in SAP Fieldglass and how to configure it.

Procedure Note(s)

  • SAP-managed WalkMe content is optional and can be enabled or disabled at any time.
  • Building custom WalkMe content requires a WalkMe Premium license. Consult with your SAP Account Executive to discuss trials, demos, and license entitlement for WalkMe.

Accelerators

Initial System Access to WalkMe

Purpose

To access, install, and prepare WalkMe to ensure the tool is properly installed, configured, and prepared in advance, so that all relevant resources can be enabled and ready to use it as needed.

This task is relevant for customers with WalkMe Premium Digital Adoption Platform.

Prerequisite

Received welcome email to activate WalkMe account

Procedure

  1. Locate the WalkMe provisioning emails sent to the ‘Initial Admin User'.

  2. Follow the steps in the email to activate the initial account.

  3. Review the provisioned WalkMe Systems.

  4. Create additional users and add them to the appropriate systems.

  5. Refer to the WalkMe Help Center for additional guidance on how to get started, Set Up WalkMe and get additional information.

Procedure Note(s)

  • For customer using other Digital Adoption Platforms, the specific steps outlined may not apply. However, if a Digital Adoption tool is available, ensure that it is properly installed, configured, and ready to support adoption activities.

  • For customers with WalkMe or WalkMe Premium for SAP Concur solutions enabled, the User Assistance Settings page will be renamed to WalkMe Settings. Access the WalkMe Enhancements to Concur User Assistance for further information on setup and configuration.

Accelerators

Now that we have covered the key deliverables of the Prepare phase, let’s revisit our case study and look at exactly what Pinnacle Industries did during their Prepare phase to transform its high-level "Future-Ready Workforce" vision into a concrete, executable project.

Case Study: What Pinnacle Industries Did During the Prepare Phase

Recognizing that identity management configuration needed to be completed early, before any user testing could begin, the SAP implementation consulting team worked closely with Pinnacle’s security lead to establish IAS and IPS as the central authentication and provisioning backbone for the SAP SuccessFactors.

Key Activities During the Prepare Phase

  • The implementation team configured SAP IAS as the primary identity provider for all SAP SuccessFactors users across Pinnacle’s three global regions
  • IPS was set up by the consulting team to automate user provisioning from SAP SuccessFactors Employee Central, eliminating the need for manual user account creation
  • The consulting team integrated SAP S/4HANA Cloud with the SuccessFactors environment to enable seamless cross-system user authentication
  • Provisioning jobs were validated against a pilot group of 50 Pinnacle users before rolling out to the full project team
  • Pinnacle’s security lead was kept informed and involved throughout, reviewing outputs and providing formal sign-off at each milestone

Outcome

With the implementation team’s support, Pinnacle Industries had a fully functioning identity management framework in place, enabling:

  • Automated user provisioning for over 15,000 employees across all implementation regions
  • Secure, single sign-on access for all project team members ahead of the first testing cycle
  • A clear governance process for managing user access changes throughout the remainder of the Realize Phase

Identity management tells the system who a user is. Role-Based Permissions tells the system what that user can see and do.

Summary

Configuring the Project Environment

  • Provision System Instances: Identify and access the required SAP SuccessFactors tenants (at a minimum, Preview and Production) by reviewing the Statement of Work and using the SAP One Customer 360 reporting tool.
  • Manage Security and Access: Grant initial access to client administrators and SAP consultants, ensuring "Super Admin" and Role-Based Permissions (RBP) are configured while keeping the user count minimal during the early project stages.
  • Establish SAP Cloud ALM: Request and set up an SAP Cloud ALM tenant to serve as the central hub for project management, task tracking, and following the SAP Activate methodology.
  • Formalize Project Governance: Define a clear environment strategy and system landscape (including specialized instances like QA/Test or Data Migration) to ensure alignment with parallel projects, such as SAP S/4HANA implementations.
  • Enable Adoption Tools: Activate SAP-managed WalkMe content to provide end-users with contextual, step-by-step guidance, accelerating software adoption and training.
  • Prepare for the Explore Phase: By completing provisioning, security setup, and governance—as demonstrated by Pinnacle Industries—the project team transitions from planning to active requirements gathering and solution design.