Customer tailored release master plan generation for hybrid networked solutions

1. A computer program product comprising a non-transitory machine-readable medium storing instructions that, when executed by at least one programmable processor, cause the at least one programmable processor to perform operations comprising:

accessing common release master plan information for a cloud-based application purchased by a business software customer from a service provider cockpit of a service provider of the cloud-based application;

reading, from a customer-specific system landscape directory, information characterizing an on-premises application of the business software customer;

generating, by combining data pulled from the common release master plan, the information characterizing the on-premises application of the business software customer, and a release master plan management object model, a customer-tailored release master plan for a hybrid networked business solution for the business software customer, the customer-tailored release master plan comprising an overview of new features to be added to an upcoming change to a specific application of a customer-specific system landscape and, based on the upcoming change, one or more impacts on other applications deployed in the customer-specific system landscape; and

providing, for use by a user at the business software customer, the customer-tailored release master plan as an interactive document comprising preparation steps to be performed to enable a new feature of the hybrid networked business solution.

2. A computer program product as in claim 1 , wherein the hybrid networked business solution comprises an interdependency between the cloud-based application and the on-premises application.

3. A computer program product as in claim 1 , wherein the common release master plan information comprises at least one of a planned release date for an upcoming release of the cloud-based application, a feature to be included in the upcoming release, a business scope extension provided in the upcoming release, a system prerequisite for use of a feature of the upcoming release, a preparation and/or action needed by the business software customer to enable the feature.

4. A computer program product as in claim 1 , wherein the accessing further comprises obtaining a customer-specific upgrade or update date indicating when the cloud-based application will be updated or upgraded for the business software customer.

5. A computer program product as in claim 1 , wherein the customer-specific system landscape directory further comprises information about a second cloud-based application supplied by a different service provider and also available to the business software customer.

6. A computer program product as in claim 1 , wherein the generating comprises processing and merging the common release master plan and the information characterizing the one or more on-premises applications of the business software customer with the release master plan management object model.

7. A system comprising computer hardware configured to perform operations comprising:

accessing common release master plan information for a cloud-based application purchased by a business software customer from a service provider cockpit of a service provider of the cloud-based application;

reading, from a customer-specific system landscape directory, information characterizing an on-premises application of the business software customer;

generating, by combining data pulled from the common release master plan, the information characterizing the on-premises application of the business software customer, and a release master plan management object model, a customer-tailored release master plan for a hybrid networked business solution for the business software customer, the customer-tailored release master plan comprising an overview of new features to be added to an upcoming change to a specific application of a customer specific system landscape and, based on the upcoming change, one or more impacts on other applications deployed in the customer-specific system landscape; and

providing, for use by a user at the business software customer, the customer-tailored release master plan as an interactive document comprising preparation steps to be performed to enable a new feature of the hybrid networked business solution.

8. A system as in claim 7 , wherein the hybrid networked business solution comprises an interdependency between the cloud-based application and the on-premises application.

9. A system as in claim 7 , wherein the common release master plan information comprises at least one of a planned release date for an upcoming release of the cloud-based application, a feature to be included in the upcoming release, a business scope extension provided in the upcoming release, a system prerequisite for use of a feature of the upcoming release, a preparation and/or action needed by the business software customer to enable the feature.

10. A system as in claim 7 , wherein the accessing further comprises obtaining a customer-specific upgrade or update date indicating when the cloud-based application will be updated or upgraded for the business software customer.

11. A system as in claim 7 , wherein the customer-specific system landscape directory further comprises information about a second cloud-based application supplied by a different service provider and also available to the business software customer.

12. A system as in claim 7 , wherein the generating comprises processing and merging the common release master plan and the information characterizing the one or more on-premises applications of the business software customer with the release master plan management object model.

13. A computer-implemented method comprising:

accessing common release master plan information for a cloud-based application purchased by a business software customer from a service provider cockpit of a service provider of the cloud-based application;

reading, from a customer-specific system landscape directory, information characterizing an on-premises application of the business software customer;

generating, by combining data pulled from the common release master plan, the information characterizing the on-premises application of the business software customer, and a release master plan management object model, a customer-tailored release master plan for a hybrid networked business solution for the business software customer, the customer-tailored release master plan comprising an overview of new features to be added to an upcoming change to a specific application of a customer-specific system landscape and, based on the upcoming change, one or more impacts on other applications deployed in the customer-specific system landscape; and providing, for use by a user at the business software customer, the customer-tailored release master plan as an interactive document comprising preparation steps to be performed to enable a new feature of the hybrid networked business solution.

14. A computer-implemented method as in claim 13 , wherein the hybrid networked business solution comprises an interdependency between the cloud-based application and the on-premises application.

15. A computer-implemented method as in claim 13 , wherein the common release master plan information comprises at least one of a planned release date for an upcoming release of the cloud-based application, a feature to be included in the upcoming release, a business scope extension provided in the upcoming release, a system prerequisite for use of a feature of the upcoming release, a preparation and/or action needed by the business software customer to enable the feature.

16. A computer-implemented method as in claim 13 , wherein the accessing further comprises obtaining a customer-specific upgrade or update date indicating when the cloud-based application will be updated or upgraded for the business software customer.

17. A computer-implemented method as in claim 13 , wherein the customer-specific system landscape directory further comprises information about a second cloud-based application supplied by a different service provider and also available to the business software customer.

18. A computer-implemented method as in claim 13 , wherein the generating comprises processing and merging the common release master plan and the information characterizing the one or more on-premises applications of the business software customer with the release master plan management object model.

19. A computer-implemented method as in claim 13 , wherein the accessing, the reading, the generating, and the providing are performed by at least one system comprising computing hardware.