SAP Activate

  • SAP Activate Methodology consists of one simple, modular and agile methodology and is the successor of Accelerated SAP and SAP Launch methodologies. SAP Activate Methodology provides full support for initial deployment and continuous business innovation with a harmonized implementation approach for cloudon-premise and hybrid deployments.
  • SAP Activate Methodology is designed  to support a broad coverage of SAP solutions starting with SAP S/4HANA. The methodology also enables co-innovation with customers and is accessible for partners.
  • The third component/pillar of the SAP Activate framework is the SAP Activate Methodology. ​
  • The SAP Activate Methodology provides one simple, modular and agile methodology and is the successor of ASAP and SAP Launch methodologies. ​
  • SAP Activate methodology provides full support for initial deployment and continuous business innovation with a harmonized implementation approach for cloud, on-premise, and hybrid deployments. 
  • SAP Activate methodology is designed to support a broad coverage of SAP​​.

Madiba Inc. possesses a formidable knowledge , set of best practices, market standards, early bird lessons learnt and access to utilize content available on roadmap viewer of the SAP methodologies applicable to all transition scenarios to SAP S/4HANA and coverage for on-premise and cloud solutions, such as SAP Business Suite, SAP Ariba, SAP SuccessFactors and others. 

For the New Implementation, there are two versions of the methodology guidance, one for cloud and one for on-premise

These two new implementation methodologies succeed the previous guidance SAP offered in ASAP methodology for on-premise and in the SAP Launch methodology for cloud solutions. SAP now supports implementation projects with these different flavors of SAP Activate. 

The on-premise version supports SAP S/4HANA and SAP Business Suite, and other on-premise solutions. 

The Cloud Methodology supports the cloud editions of SAP S/4HANA, as well as SAP SuccessFactors, SAP Hybris Cloud for Customer, and Ariba solutions. 

System conversion is designed only for an on-premise deployment model. 

Landscape transformation is a scenario that supports both on-premise and cloud editions because the customers may decide to use certain capabilities in the cloud and certain capabilities in on-premise and integrate those solutions.