Setting Up the Implementation Project in SAP Cloud ALM

Once a project team member has been created in SAP Cloud Identity Services, they can be added to SAP Cloud ALM. The IT Contact needs to eventually provide all project team members access to SAP Cloud ALM, but it's most important the partner project manager is given access first, because they are responsible for setting up the implementation project and assign tasks to the other project team members.

Watch this video to learn how the IT Contact can set up users in SAP Cloud ALM.

First, the partner project manager should review the existing standard roles that are already available to use. The existing roles can be edited or deleted and new roles can be created. For example, it would make sense to create a role for the line of business (LoB) experts in each area.

One role can be assigned to more than one person, so this makes sure tasks for specific LoBs get assigned to the team of configuration experts responsible for that LoB.

Next, the partner project manager creates the project and selects the appropriate roadmap:

• RISE with SAP Methodology - Clean Core Success Plan
  • Maintainable System Environment: Reducing custom code for an easily maintainable system.
  • Standardized Best Practices: Aligning with SAP best practices and processes.
  • Ease of Future Upgrades: Simplifying future upgrades, minimizing rework.
  • Cloud-readiness: Optimizing for cloud deployment with continuous updates.
  • Sustainable Operations: Focusing on long-term sustainability and operational efficiency.
  Note

  This roadmap was created to support the use case where customers want to run the clean core initiative as a separate project that could run in parallel and beyond the actual implementation project. The "Clean Core" tasks and Quality Gates in this project are present in all other SAP S/4HANA Cloud Private Edition roadmaps. This means if you choose any of the roadmaps listed below, you will still be getting the "Clean Core" tasks and Quality Gates.

• RISE with SAP S/4HANA Cloud Private Edition - Implementation
  • New SAP Customers: For organizations new to SAP implementing SAP S/4HANA from scratch.
  • Legacy System Replacement: For companies migrating from non-SAP ERP systems.
  • Standardization: Adopting SAP's best practices without legacy customizations.
  • Comprehensive Implementation: Ideal for greenfield projects needing a modern ERP solution.
• RISE with SAP S/4HANA Cloud Private Edition - System Conversion
  • Existing SAP ECC Users: For those transitioning from SAP ECC to SAP S/4HANA Cloud Private Edition.
  • Protect Existing Investments: Retaining customizations, configurations, and historical data.
  • Minimize Disruption: Leveraging a brownfield approach for minimal business disruption.
  • Technical Conversion: Suitable for technical upgrades to the new SAP environment.
• RISE with SAP S/4HANA Cloud Private Edition - Selective Data Transition
  • Fast and Flexible Migration: Efficiently migrate all or selective historical data to SAP S/4HANA.
  • Source and Target: Transfer data from SAP ERP to SAP S/4HANA, whether it's an empty system, newly implemented, or already in use.
  • Minimal Downtime: Migrate data with minimal business disruption.
  • Flexible Execution: Perform migration in one go or in stages, fitting various project needs.
  • Balanced Approach: Combine New Implementation and System Conversion benefits for flexible data transfer and harmonization.
• RISE with SAP S/4HANA Cloud Private Edition - Upgrade
  • Routine Upgrades: Keeping current with SAP’s latest releases.
  • Feature Enhancement: Leveraging new functionalities and performance improvements.
  • Security and Compliance: Meeting new regulatory and security requirements.

After entering a project name, move to the Timeboxes tab and enter the general dates for each phase. Start with the customer's planned go-live date an work backwards from there to fill in the timeboxes. Typically the Fit-to-Standard workshops in the Explore phase take the longest, so this should be given the most time of any phase. The timeboxes are used to visually show how many days are remaining in a phase and how many tasks have been completed or are yet to complete in the Overview app.

After the project has been created, it's time to match the actual project team members with their relevant roles and turn off any roles you don't need for this project.

You can also create a team by including a collection of several different roles or users into one group, which is called a team in Cloud ALM.

For new implementations, you'll need to select the SAP Best Practices scope. Navigate to the Scopes tab, then click the Manage Scopes link. This brings you to the Manage Scopes app, where you will set the scope to match with what the customer already selected on the Digital Discovery Assessment (DDA). The customer executive sponsor(s) completed the DDA in the Discover phase. If you do not have the DDA, ask the customer project manager to follow up with the customer executive sponsor(s), because it's important for this activity. Once the partner project manager has the DDA, they can select the same business processes chosen on the DDA in the Cloud ALM scoping either manually, or by importing the scope from a file that you export from the Digital Discovery Assessment. First, we will cover selecting the scope manually.

Keep in mind the DDA is just a starting point - the final scope will likely change after all Fit-to-Standard workshops have been completed.

For system conversion projects, you can ignore this step as the analysis of the customer's existing scope can be done with SAP Signavio Process Manager, which is then used as the documentation tool moving forward. Access to SAP Signavio Process Manager is included in the customer's RISE with SAP bundle.

Select the latest SAP Best Practices package for SAP S/4HANA Cloud Private Edition OR the Enterprise Management Layer for SAP S/4HANA and select the Save button.

The Enterprise Management Layer (EML) is a better fit for larger companies that have many different intercompany business processes. This would be indicated on the customer's Digital Discovery Assessment that was completed by the executive sponsor(s) in the Discover phase. Select the Process Scoping button to choose the specific business processes and their local versions that should be added to the project.

Begin by filtering by the local versions (country/region) the customer needs for their system. Next, filter by the line of business (Business Process Group filter) and scroll to the very end of the page to load all solution processes in the list.

Then start working through the Digital Discovery Assessment results and in the "Scope" column in Cloud ALM, click the "slider" button to add each individual process to the scope. You can use the business process ID in the search field to identify exactly which processes you're looking for. Every process selected on the Digital Discovery Assessment should also be added to the scope in Cloud ALM. When finished, select the End Scoping button.

A faster alternative to manually selecting the scope is to export an Excel file from the customer’s original Digital Discovery Assessment (DDA) and import that file to SAP Cloud ALM. Members of the partner implementation team likely wouldn’t have access to the customer’s DDA, and if the customer executive sponsor who completed the DDA hasn’t already exported and saved this file, the partner project manager can instruct them to navigate to the Supply Chain of Selling app to open their DDA.

Within their personal DDA, select the More drop-down menu and choose Import & Export. Select the Export Excel button to download the version that can be imported in SAP Cloud ALM through the Manage Scopes > Scope from file option. ​

The system group is used to group together the SAP S/4HANA Cloud development, quality, and production systems and attach them to the project. In the Projects and Setup app, select the System Groups tab, then Create.

The partner project manager likely does not know the system names for all provisioned systems, so they should ask the IT Contact for this information. After saving the system group, it can be assigned to a deployment plan.

The deployment plan is to help you keep track of upcoming releases for your systems. For SAP S/4HANA Cloud Private Edition, we moved to a two-year release cycle after the release in October 2023.

This means one release every other year. Customers are required to keep their systems within mainstream maintenance, which means installing at least one upgrade every 7 years. SAP handles the technical upgrade, so the customer just needs to work with their contact from SAP Support to let them know when they're ready to prepare for an upgrade installation. In the Projects and Setup app, navigate to the Deployment Plans tab, select create, then enter the upcoming release(s) that fall within the timeboxes of your implementation. After saving the deployment plan, you can assign the previously created system group and save again.

In the Projects and Setup app, select the Projects tab and search for your project. Select the Deployment Landscape tab within your project, then the keyword search to find your Deployment Plan and save it to the project.