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
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
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.
Note: Based on your deployment plan whatever the system groups assigned to the deployment plan will be listed under system groups.
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.
Note: Deployment Plan can be set at only in Project Level.
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.