Create project team members 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 and customer project managers are given access first, because they are responsible for setting up the implementation project and assigning tasks to the other project team members.
Watch a video
Watch this video to learn how the IT Contact can set up users in SAP Cloud ALM.
Define project roles
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.
Create project with SAP Activate Roadmap and Timeboxes
Next, the partner project manager creates the project and selects the SAP Activate Roadmap: SAP S/4HANA Cloud Public Edition (3-system landscape) - Implementation. 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 and 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.
Add team members to roles
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.
Assign the 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 exact same business processes chosen on the DDA in the Cloud ALM scoping. While you do have the ability to export the DDA in a format that can be imported into Cloud ALM through the Scope from File option, we do NOT recommend this. Even though it's a little more work up front, creating the scope by selecting each business process and it's necessary local versions (countries) is more efficient in the long run because it enables you to easily filter and add/remove processes from the master scope list as the Fit-to-Standard workshops are conducted and the partner LoB configuration experts realize perhaps too many, or not enough business processes were selected on the original DDA. The DDA is just a starting point - the final scope will likely change after all workshops have been completed.
Select the latest SAP Best Practices package for SAP S/4HANA Cloud Public Edition and select the Save button. Select the Process Scoping button to choose the specific business processes and their local versions that should be added to the project.
Filter scope by the processes selected in the Digital Discovery Assessment
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.
Create a system group
The system group is used to group together the SAP S/4HANA Cloud starter, development, test, 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; ask the IT Contact for this information. After saving the system group,
Create a Deployment Plan and assign System Group
The deployment plan is to help you keep track of upcoming releases for your systems. For SAP S/4HANA Cloud Public Edition, it takes approximately one month to finish all the upgrade activities and have all systems on the latest release. This means the implementation project needs to pause for this period of time to learn about the new features, how they will affect your current scope and customizations, and if any newly released business processes should be activated. 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.
Assign Deployment Plan to Project
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 Edit button to find your Deployment Plan and save it to the project.
Learn more about how to use SAP Cloud ALM with the video playlists in the SAP Help Portal and in this SAP Blog: End to End Story for Implementation in SAP Cloud ALM.