Skip to main content

S/4HANA Simple Finance: Questions and Considerations

Here are some things to consider when assessing a move to S/4 HANA Simple Finance:
HANA & S/4HANA:
HANA is the superfast powerful “in-memory” database. It organizes data differently to reduce complexity, it is faster to access, indexing, aggregating not required etc. Instead of holding totals in tables, totals are calculated on the fly (a phrase you will hear a lot – meaning recalculated as you go). SAP Trainings Online is best SAP HANA training platform by professionals.  
Considerations/Questions: 
  • Some customizing will still work as there will be “views” with the same name as the obsolete tables (recreated from the new table for this purpose). Your bespoke program can read from these views but if your bespoke programs were writing to tables, you cannot write to the views.
  • You should be told about various tools to check your bespoke customizing well before any migration. In any case, it is a good idea to review as you may now be able to replace some programs with standard functionality.
  • You may find a separate charge for the database, in addition to the S/4 HANA and the landscape.
S/4 HANA is the SAP Business Suite that is built and optimized to run (only) on the HANA database.
You will see two different types or editions of S/4 HANA (Learn SAP S/4HANA by certified experts i.e. the business suite “software”) but the combination with different landscape options can be confusing.
The names of the two different S/4 HANA editions are:
  • SAP S/4 HANA Cloud (although a number of different versions exist) with quarterly releases.
  • SAP S/4 HANA on-premise – each release is named after the year and month – we have had 1503 (Simple Finance only), 1511 and 1610 releases (1610 the current one was released on Oct 2016 next will be 1709 i.e. Sept 2017).
The first is sold as a service and is available on a multi-tenanted public cloud (i.e. your data is secure, but you share the programs with other customers - simplified, standardized, almost no custom programming) whereas the on-premise version is available how you want it, on third party or your servers/cloud, with custom programming allowed (and when we did it more complex to license and buy/hire the different pieces)  
Considerations/Questions
  • If you are using an Industry solution check whether it is compatible specifically with edition that you are going with.
  • Check any restrictions - e.g. AFS with 1511 edition did not use BP (Business Partners) although BP was mandatory for the standard solution
  • Free trials are available but careful that you understand which edition you are trialing
  • Check paths (if on e.g. 4.6 you may have to migrate first to higher version, then convert to S/4 HANA if not a new implementation)
Landscape: Public cloud
Multi-tenant, scalable, operated by service provider and not customer, and lot of simplification, pre-configuration and Fiori front end. Different versions such Enterprise Management Cloud (the main Business programs), Finance Cloud, Professional Services Cloud, Hybris Marketing Cloud and Manufacturing Cloud.
Effectively the Public Cloud has one set of programs that you are sharing with other customers. It should be very secure but it does mean that very little, if any bespoke work can be carried out.
Very different concept to standard SAP. You have access to a reduced version of the SPRO/IMG (the configuration menu) and you cannot write your own ABAP programs. You have quarterly updates and you do not have a choice about implementing them. In the past, you may have had a Development system for configuring and unit testing, a Quality/Testing system and perhaps a Training system as well as the final Production client, the public cloud structure is very different (you usually have production and one other)
Generally sold as Opex rather than Capex (operating rather than capital costs) or subscription based for the combination of software and hardware. Self-service configuration allows business users more access to set up e.g. of organizational structure, house banks
Considerations/ Questions:
  • Security
  • Check into different versions (mentioned above) there seem to be a lot more available now
  • Licensing (subscription – user/revenue based)
  • Backups
  • Upgrades
  • OSS notes
  • If system crashes – time to reboot and get data back into memory – how the data is backed up while you work and how much time you might lose (should be minimal but they should be able to explain this) 
  • Service level agreements, incident support, monitoring, what is included
  • Check how many systems involved (usually production plus one other). 
  • Check – but I think it uses only Fiori will you have enough Fiori transactions that you need as not all GUI transactions may be available in Fiori
HANA Enterprise Cloud
Be careful when people mention Cloud as they usually mean public cloud. HEC is often referred to as on-premise rather than cloud as this is the edition of S/4 HANA that is used with it.
HEC is owned by customer or Third Party, but still scalable. One upgrade/release per year. Here you are the only one on the system (regardless of whether it is Cloud or not) so you are free to choose when the upgrades happen, what bespoke programming/customizing you want to carry out etc. Upgrade is an IT project (as opposed to private cloud upgrades which are done automatically by SAP)
Considerations/Questions:
Licensing – It is a quite complicated, perpetual license and recurring hosting fee but a lot of licensing is based on revenue, number of objects etc.
Hybrid
Mix of two, you may have some systems in the cloud and some not.
Implementation
3 Options:
System Conversion On premise edition only
Data is directly converted with history in the existing system (but not necessarily all history–e.g. you could take last 5 years’ open items).  Figures have been quoted to me of downtime of one weekend for the physical conversion itself, but obviously depends how much data and the complexity and what other changes are taking place and you would.
You would still need many months testing and full project team in place, especially if you have many interfaces. It also assumes that you make copy your productive system to a sandbox to do the first test run, which will give you an indication. Bear in mind you will also have to convert all your development, quality, training etc. Systems. Can’t use with public Cloud.
Considerations/Questions:
  • Are you migrating to New GL or already on it? This has major effect on timing as New GL has to be at yearend
  • Are you introducing Parallel ledgers with new GL. Discuss with SAP whether better to migrate to new GL and parallel ledgers before implementation (only since the 1610 release can you add parallel ledgers after migration but not sure if you can add them during
  • Document splitting – this cannot be added (in 1610) after migration so you may have to go to new GL before the migration to S/4 HANA
  • Integration to other systems - depending what you have been using in the past there may now be more efficient ways of interfacing to other systems – this should be looked into
  • Have to convert whole system at once – cannot move in stages (e.g. once company code at a time)
  • Check steps – usually install HANA database before conversion, some configuration tasks
  • Maintenance planner to run through tasks and timing
Greenfield Implementation
Worth considering if on SAP for years. you can use the move to S/4 HANA to move to Best Practices, re-engineer business processes and get rid of a lot of obsolete or no longer necessary bespoke work. 
Considerations/Questions:
See migrations considerations/questions about uploading data
Central finance/landscape transformation
To consolidate a lot of diverse systems very quickly, you basically map your finance data from all your SAP and non-SAP data to a Central Finance S/4 HANA system. The data is reposted, but if coming from an SAP system you can drilldown to the original data and you get all the advantages of the speed and consolidation upfront and can migrate the individual systems when you are ready.
Considerations/Questions:
This is not a migration of historic data
Still a great deal of mapping to do if individual companies on different systems chart of accounts etc.
Was not a separate cost for the Central Finance itself – just the way it is configured but you may need tools for the mapping.
Storage
Data aging strategies (i.e. which data is held in memory, which “nearby” and any archived on different system etc. – data used more frequently should in “hot storage” and “warm storage”.
FIORI
Described as “user experience”, consists of Apps or Tiles (rather like a smartphone than menu path/transaction codes). Includes interactive apps (see figure below) where key information is available on tile itself. Uses Launchpad for home page. (Know about FIORI launchpad indetail from SAP FORI training) Available for multiple devices, desktops, tablets/phones. Based on user roles, so smaller transactions tailored for specific role (not necessarily every field available for every user) 
Worth considering and mandatory for Public Cloud version. 
Considerations/Questions:
  • Check in-house knowledge required for Fiori and UI5 stuff (Learn from SAPUI5 training by SAP Trainings Online)
  • Check whether Fiori is mandatory (generally shouldn’t be for on-premise), but SAP will try to sell it
  • Are the transactions you need covered by Fiori (most standard ones should be)
  • Worth looking at what is available on Fiori that is not on the SAP GUI
  • Check what transactions are available for mobile devise (I presume e.g. approving a PO might be but not sure if everything is)
  • Should be trial versions available
  • If using personas – check how fits in with Fiori (should be seamless but you will need to know how)
  • I believe the GR/IR cockpit is neither a GUI transaction nor a Fiori App as it is not in my 1610 S/4 HANA version nor the Fiori Apps I have access to, nor the Fiori catalogue 
  • If the GR/IR cockpit is indeed separate functionality/program; check whether separate licensing/cost is involved and what other functionality is included.  
  • Not all of the thousands of SAP ECC transaction codes were available on Fiori – check whether you still need GUI access.
SAP Trainings Online is an interactive global training podium started by proven industry experts with an aim to provide quality SAP training in all SAP technical and SAP functional training courses. Our trainers are highly talented and have Excellent Teaching skills. They are well experienced trainers in their relative field. This training is your one stop & Best solution to learn SAP Simple Finance at your home with flexible Timings. We offer SAP module trainings conducted on normal training and fast track training online classes.
Register Here for SAP simple finance free demo
For more details visit:www.saptrainingsonline.com
Email:contact@saptrainingsonline.com
Contact:India +91 9052775398 USA +13152825809

Comments

Popular posts from this blog

SAP S/4HANA Simple Finance Simplified Way to Finance | SAP Simple Finance Online Tutorials

SAP S/4HANA Simple Finance SAP’s Financial & Controlling module (one of the core modules from SAP, since its R/2 days) is a pretty mature offering with awesome breadth and depth. But over the years, the world has changed a lot. New financial regulations across the globe are necessitating change. There is also a need for lightning fast financials reporting.  The world of data is changing swiftly and financial operations must deal with enormous amounts of data processed at higher speeds and make sense of it. Considering this and to leverage its high-performance HANA platform, SAP has taken its Financial & Controlling module to the next level by launching “Simple Finance” (short form- SFIN) with SAP Business suite 4 HANA (i.e. S/4 HANA) ). And while doing it, SAP not only overcame some of the short-comings (of traditional FICO module) but also packed it with some powerful new features. Single Source of Truth In Simple Finance, SAP has introduced a new table named ‘

Introducing profitability analysis in SAP S/4HANA with 1709 Version

Understanding the importance of profitability analysis, key differences between costing- and account-based CO-PA, and discuss the improvements in account-based CO-PA with SAP S/4HANA Finance . Evaluate your business requirements and plan your SAP S/4HANA Finance integration, including important configuration steps for account-based CO-PA. When we talk about profitability analysis, you should keep in mind the different ways that profitability of a business is measured. There is an external view and internal view of profit for any business organization. The external view of profit is mostly driven and influenced by a number of statutory, tax, and regulatory requirements, whereas the internal view is driven by the management requirements of how business units, products, customer segments, and so on are performing. Traditional data models in enterprise resource planning (ERP) systems focused on data collection, aggregation, and reporting primarily to meet the external view o

SAP Simple Finance New Options in Profitability Analysis | SAP Simple Finance Tutorials

Even though Simple Finance sounds at the outset like a contradiction in semantics alone, SAP claims otherwise. SAP has built its product with a lot of well-thought out feature frameworks that brings about simple-to-use features along with real-time SAP HANA-powered (know HANA offerings from SAP HANA training ) and Cloud-based functionalities which are all pervasive in the IT domain today. Discover what changes in profitability analysis (CO-PA) when you use SAP HANA as a database. Learn how to link the general ledger and CO-PA and see what functional enhancements have been made to account-based CO-PA to provide greater transparency. Ensure that you get the best of both worlds: figures in the income statement that match the lines in CO-PA, but with sufficient detail to explore your manufacturing costs properly Learning objectives By reading this article, you’ll learn how: The use of SAP HANA as a database impacts profitability analysis (CO-PA) The data structure