Contact Us
×
How you can contact us:

Deployment & Release Planning

Keeping your production systems stable and reliable is crucial in a fast-paced world. Deployment and Release planning within SAP Cloud ALM for Implementation helps you to make software and configuration changes a non-event by giving you the opportunity to stay on top of your go-live activities.

You can learn more about SAP Cloud ALM's assistance with Deployment and Release planning on this page. 

The Tenants used for a Product line are called Systems and the Systems are maintained under Landscape Management

  • Products are referred as Service Types
  • Systems are referred as Tenant ID

A system group is a collection of systems belonging to one product line for example: SAP S/4HANA Cloud, SAP Integration Suite, SAP SuccessFactors workforce Analytics, SAP Ariba Procurement and other SAP Products as listed below

The steps to create a System group are,

  • Select the Project and Set Up Tile under Implementation section, once it's selected as a user, you can navigate and find easily where do you need to create systems and where do you do your deployment planning

  • You can create a System Group  and choose your required product to pair up with SAP Cloud ALM (Example: Here I have chosen SAP S/4Hana Cloud for System Group Demo SG1010, SAP Integration Suite [Cloud Integration] for the System Group Demo SG1011 and SAP SuccessFactors workforce Analytics for the System Group Demo SG1012)

 

System Group 1: Demo SG1010

System Group 2: Demo SG1011

System Group 3: Demo SG1012

  • The required Tenants/Systems needs to assign under the Systems such as Starter/Preview, Development, Quality Assurance and Production. Click on Assign System to choose your desired system. (The same list of Systems is picked from the same role as maintained under Landscape Management)
  • Each Tenant/System comes up with a unique Id, if one Tenant/System with Unique Id is assigned under Production environment, it can not be assigned under any environment
  • Click on Save to save your changes and repeat the same steps to create a multiple System Groups

Deployment Plan is a collection of Systems Groups and Release Timelines, and the same Deployment Plan can be applicable for multiple Projects. 

Release is a Timeline which helps the Project Leads to manage their Deployments. Same Release can be used across the multiple Projects. Also, you can assign Requirements and Features to the Release and test them together. 

  • Click on Deployment Plan from the header under your Project and Set Up Tile and select create to create a new Deployment Plan
  • Fill up the Title blank to name your Deployment Plan. For Example: Here I have named it as Demo DP1010
  •  Assign release dates for your deployment plan also you can model them overlapping. At the end of every release, you will do the Productive delivery
  • Click on Edit and select Assign to choose the System Groups you are going to use with the help of simple text search

  • Similarly, assign the System groups and Click on Save. To put it simply, we have combined multiple System Groups into a Deployment Plan as well as each system group can have a different delivery plan too

  • You can assign your Deployment Plan with your existing Project or by creating a new project
  • Choose the Deployment Landscape Tab below your Project and select the required Deployment Plan you want to assign to the Project
  • Once deployment plan is assigned, the system groups will automatically be assigned

Note: Based on your deployment plan whatever the system groups assigned to the deployment plan will be listed under system groups.

  • You can not add new system manually in project Page
  • To create a new Deployment Plan, you have to go back to the Deployment Plan Tab to add a new one and it will appear in project page automatically. Similarly, to create a new System Group you have to go back to the System Group to create a new one

Advantage: Even multiple projects can use a same deployment plan rather than every project setting the landscape manually. It is much simpler way to use a deployment plan

Requirements are expectations from Business that need to be fulfilled. 

  • Choose Requirement Tile and Click on create to create a Requirement.
  • The main Advantage here is, once you selected the Deployment Plan then you not only get the Landscape information you also get the Release information after the requirement creation

Note: Deployment Plan can be set at only in Project Level.

  • Requirement does not need to know the Deployment Plan. A requirement just needs to know the Requested Release

This completes the concept. That means your planning follows a Release Schedule. The Release Schedule comes from a Deployment Plan and Deployment Plan comes from the project. Because we assigned a Deployment Plan to the Project. Please visit Deployment Confirmation link to know more.

 

Assigning a deployment plan to a project in SAP Cloud ALM for Implementation provides you with an option to assign releases to requirements. Based on the assigned releases you are able to bundle requirements which should go live together. The release on requirement level indicates a planned release to production.

The actual release to production is planned on feature level. The end date of a release can be seen as the go-live date. 

Simply assign the suitable release to the appropriate feature(s).

Note: Plan your releases in alignment to your sprint planning, in order to enable deployment to production in a timely manner.

Based on the status and the release of features you can easily figure out several ones for the deployment to production. As soon as all features related to a requirement are deployed to production it can be confirmed. 

Note: This means the feature with the latest release and thus with the latest planned go-live date is decisive for the actual go-live date of the requirement it is assigned to.