A Greenfield S/4HANA Implementation Makes You Fit For The Future
A Greenfield S/4HANA Implementation Makes You Fit For The Future
A Greenfield S/4HANA Implementation Makes You Fit For The Future
1. SAP S/4HANA Finance is a combination of SAP Accounting powered by SAP HANA, SAP Cash
Management and SAP Integrated Business Planning (IP, BPC and embedded BW) for Finance and
also includes additional innovations in the areas of Treasury and Financial Risk Management,
Collaborative Finance Operations and more
2. SAP Finance comply both local and global requirements of finance department and hold solutions
specifically built for 25 industries in more than 50 countries
3. With SAP Finance, the life of the finance folks are simplified and mandates the use of Account -
based COPA providing the detailed information for cost of sold goods, production variance and invoice
quantities. The costing-based COPA avoids reconciliation issues between COPA and GL
4. SAP HANA will be deployed on the cloud (public and private), on-premise and via hybrid options.
Eighty-one percent of all organizations have made a move to the cloud for half of their future
transactions
In this article, you will learn why and how we implemented SAP S/4HANA with the
Greenfield Approach at one of our customers in the machinery industry. These lessons-
learned and best-practices will help you when you decide to adopt the S/4HANA
Greenfield Approach at your organisation as well.
The Management faced a major challenge in 2015: the company had been strategically
reorganised with new business units that would each be answerable for their results. At
that time, the organisation was processed in SAP ERP through different systems and
clients, each with its own solutions, each of which was segregated from the others. To
depict the new structures, a central SAP-ERP system was essential in order to facilitate
the creation of centralised solutions covering all the different legal entities, and to drive
the harmonisation of processes and routines.
Some of the critical factors in the success of any implementation project are
hardly affected by technology but by the people at work. This is no different
during the implementation of SAP S/4HANA.
Right from the start of the project, slot-leads and key users who would be
involved at the blueprint phase, and who would help define the requirements
of the new system, were designated for each subsidiary. This method of
working ensured a high level of acceptance right from the beginning of the
project. We informed the slot-leads and key users on a regular basis about
the project progress. Moreover, we created a communication template, in
which all the items for project communications were included. This also set
out communication guidelines, to ensure that the lines of communication
would function in a co-ordinated manner throughout the company.
1. First and foremost, have database reading operations been optimised, or are
further improvements still required here?
2. Are there any errors in the current code, such as implicit classifications that
emerge only after the migration?
3. Are there any structures, objects or modules used that will no longer exist in this
form after the implementation of S/4HANA?
If performance does not play a vital role, will custom developments still run
on S/4HANA? Therefore, a review relating to points 2 and 3 should be carried
out. The ability to run programs that are a legacy from “old” structures could
if necessary be achieved using compatibility views. These will continue for
example to make “old” tables available.
Conclusion
The implementation of SAP S/4HANA with a Greenfield Approach offers many
opportunities to optimise your historically-evolved processes and to get more
standardised processes, thereby making your organisation higher-performing
and fit for the future. Don’t waste this opportunity. Before you start your own
SAP S/4HANA implementation, we recommend you allow time for a reflective
phase in order to put the spotlight on these matters.
THE GREENFIELD APPROACH