Changes and Challenges with S/4HANA (Part 2): Transformation
Note: This blog article only covers S/4HANA on-premise edition 1511.
As we’ve learned in Part I, there is a lot of work associated with migrating your system to S/4HANA. The question is, where do you start?
First, you need to make sure, that your SAP system is UNICODE-enabled. If you have not enabled UNICODE for your SAP system, you must do that first because S/4HANA requires UNICODE. Second, it is recommended that you check and clean up your custom code and data. HANA retains a lot of data in its memory, including unused code and data, unlike in the old world, where data was stored on disk. That can quickly get expensive. A migration to S/4HANA is the perfect time to get rid of unnecessary data.
S/4HANA on-premise 1511 Roadmap
SAP issued the following roadmap, as an overview of the implementation of S/4HANA on-premise 1511. You can learn more the Road to SAP S/4HANA here.
If you have read the Simplification List we have referenced in Part 1, you can imagine how much effort it is to verify for every transaction if it has been replaced or consolidated.
Xiting Authorization Management Suite (XAMS)
Fortunately, you can automate this time-consuming task using the Xiting Authorization Management Suite (XAMS). XAMS analyses your existing roles and compares them with the new data model in S/4HANA. Our solution then marks transactions that don’t exist anymore in S/4HANA or that have been consolidated into new transactions. Thus, you can significantly expedite your migration project while lowering the risk or costly mistakes.
Furthermore, you can quickly adjust affected roles in your development environment by appending new transactions and by removing old ones. You can do all that directly in XAMS instead of manually updated each role individually. In combination with our Role Designer, you can virtually build roles via drag & drop and immediately see if the affected role has all the transactions it needs. When the new role fits the requirements of the assigned users, you can automatically build the role with all TCODES as menu items already included.
If you need additional support, Xiting is going to offer this as a “S/4HANA Migration Service”. In addition to the mentioned capabilities, the service will also cover Fiori apps, which will replace transactions.
Related services
- Testing of new roles via Productive Test Simulation
- Checking for SoD conflicts, critical authorizations, and combinations
- SU24 optimization regarding S/4HANA
- Changes and Challenges with S/4HANA Part III - 18. July 2017
- Changes and Challenges with S/4HANA (Part 2): Transformation - 14. November 2016
- Changes and Challenges with S/4HANA (Part 1) - 20. October 2016
