InterviewSolution
| 1. |
What Happens To Existing Modifications When A Customer Moves To Sap S4/hana? |
|
Answer» In any scenario, the move to SAP S/4HANA is a great opportunity to validate the existing modifications and simplify your solution. It has not been unusual for customers to realize that 50% of the modifications that hamper fast release cycles and require long test cycles were no longer necessary to run the business, but were leftovers from older projects while the remaining modifications could have been built in a less INTRUSIVE manner. When moving to SAP S/4HANA, public cloud edition, customers will move their modifications to SAP HANA Cloud Platform as an extension. ALSO, customers that MAKE the choice of the SAP S/4HANA, managed cloud edition, the recommended approach is to use SAP HANA Cloud Platform extensions to provision enhancements. In fact, standard field extensions can directly be done within the SAP Fiori UX while SAP HANA Cloud Platform can be leveraged for more significant developments. SAP S/4HANA, on-premise edition, provides maximum customization opportunities: on premise as traditionally done in the past or through SAP HANA Cloud Platform. SAP has several references of SAP Business Suite customers using SAP HANA Cloud Platform extensions for on-premise systems. In general, the SAP HANA extension framework of SAP HANA Cloud Platform uses SAP HANA as the common platform for SAP S/4HANA and offers additional CHOICES such as the integration of open source solutions. The extension framework has the advantage to isolate modifications from the core and drive agility for the on-premise deployment and SAFEGUARD agility for cloud deployments. This means that rather than modifying the core code, enhancements are put in a “safe” environment so that innovation packages can be easily applied. The core SAP S/4HANA system remains “clean” and can be quickly and easily updated when new innovations are added – in just the same way that consumer mobile apps are updated on a regular basis. In any scenario, the move to SAP S/4HANA is a great opportunity to validate the existing modifications and simplify your solution. It has not been unusual for customers to realize that 50% of the modifications that hamper fast release cycles and require long test cycles were no longer necessary to run the business, but were leftovers from older projects while the remaining modifications could have been built in a less intrusive manner. When moving to SAP S/4HANA, public cloud edition, customers will move their modifications to SAP HANA Cloud Platform as an extension. Also, customers that make the choice of the SAP S/4HANA, managed cloud edition, the recommended approach is to use SAP HANA Cloud Platform extensions to provision enhancements. In fact, standard field extensions can directly be done within the SAP Fiori UX while SAP HANA Cloud Platform can be leveraged for more significant developments. SAP S/4HANA, on-premise edition, provides maximum customization opportunities: on premise as traditionally done in the past or through SAP HANA Cloud Platform. SAP has several references of SAP Business Suite customers using SAP HANA Cloud Platform extensions for on-premise systems. In general, the SAP HANA extension framework of SAP HANA Cloud Platform uses SAP HANA as the common platform for SAP S/4HANA and offers additional choices such as the integration of open source solutions. The extension framework has the advantage to isolate modifications from the core and drive agility for the on-premise deployment and safeguard agility for cloud deployments. This means that rather than modifying the core code, enhancements are put in a “safe” environment so that innovation packages can be easily applied. The core SAP S/4HANA system remains “clean” and can be quickly and easily updated when new innovations are added – in just the same way that consumer mobile apps are updated on a regular basis. |
|