What you cannot do with an S/4HANA conversion project
Most of the blogs and vast amount of documentation existing in the SAP community focuses on prerequisites, steps to follow, recommendations and advices for a successful transition to S/4HANA.
But what about the things we cannot achieve during a conversion project? Or the things which cannot be done in a specific phase of the conversion project or afterwards, in the converted and live S/4HANA system?
In this blog, lets analyze those aspects which cannot be achieved during or post a conversion project.
Please note that not all the items from this blog can be found in the Simplification List or in the Readiness Check.
1. You cannot identify all the data inconsistencies in the source system.
There are standard reports available in the ECC system for consistencies checks, which have been available for a while and most of them focus on generic checks and not checks specific for the S/4HANA conversion. In order to identify all the data inconsistencies relevant for the S/4HANA conversion, a full conversion cycle must be executed, using as recent copy of Production. This is also one of the reasons the conversion project follows an iterative approach.
One of the consistency checks reports specifically targeting S/4HANA conversion projects is provided via note 2755360. However, this report is not capturing all the data inconsistencies as the programs executed during the data migration.
- with note 2887318 an additional program for GL errors correction is provided. This program can be used along with note 2714344 to support pre-conversion error resolution
- note 2896400 provides a series of consistency checks in the area of Asset Accounting, targeting specific S/4HANA conversion related errors and which can be executed in ECC environments. Note 2714344 can also be consulted for asset related errors and support the resolution.
These additional programs/ notes, increase considerably the % of data inconsistencies which can be addressed before the conversion cycle.
2. You cannot implement document splitting or a further accounting principle/ledger during the conversion project.
The conversion to S/4HANA from classic GL, is similar to the New GL migration scenario 1 – Merge of Classic GL and parts of Scenario 2 (Scenario 1 and additional merging of PCA and SPL). The implementation of document splitting and of a further accounting principle are available after the conversion to S/4HANA, as subsequent implementation projects, starting with release 1610 – for the additional accounting principle and release 1709 for the subsequent document splitting. For additional information, including limitations, please see Implementation of a Further Accounting Principle and Subsequent Implementation of Document Splitting.
3. You cannot switch from the accounts approach for parallel valuation to the ledger approach for parallel valuation.
This transition scenario is currently not available – not during the conversion project, nor as a subsequent project in S/4HANA.
The transition scenario is available in ECC at the moment, so it can be done before the conversion project, as part of the NEW GL Migrations scenarios. For a complete list of scenarios available in ECC as part of New GL Migration, please see Migration to New General Ledger Accounting.
4.You cannot change the relationship/assignment between existing company codes and controlling areas.
This does not include creation of a new controlling area for new legal entities or the assignment of a new Controlling Area to a company code which was not using the Controlling component before. Such project can be executed only in the ECC system, before the conversion project, with the support of the team previously called SLO and currently called DM<.
5. You cannot introduce an additional currency.
As part of the S/4HANA conversion, only the existing currencies are taken over in the environment. It is possible to introduce a new currency, after the conversion, starting with release 1809. The new currency will be available only in the General Ledger component as it will be introduced only in the Universal Journal (only table ACDOCA). All the documents will be enhanced with this additional currency and all the documents pertaining to the current fiscal year will have balance zero ensured.
As this new currency will not be available in table BSEG, it will also not be reconciled for components like Asset Accounting, Material Ledger and Controlling.
During conversion or after – as part of the separate project, it is also not possible to:
- Introduce a company code currency or a controlling area currency
- Introduce a currency type for Transfer Pricing
- Convert an existing currency type
For these specific requirements, it is still possible to execute a project in the ECC system with the support of the team previously called SLO and currently called DM<. For additional information, please check SAP Help or note 2334583.
6. You cannot use a combination of accounts approach and ledger approach for parallel valuation.
In ECC, it was possible to use such set up. In order to be able to use New Asset Accounting, which is a pre-requisite for S/4HANA, you must map the parallel valuation in New Asset Accounting with either ledger approach or accounts approach in the General Ledger application.
7. You cannot use alternative fiscal year variants with different “beginning/end dates” when using the ledger approach for parallel valuation, for the representative ledgers in a ledger group.
8. You cannot share the same chart of depreciation for company codes with different ledgers assignment or different currencies assignment.
This was possible in Classic Asset Accounting but not possible in New Asset Accounting, as GL and Asset sub-ledger will be completely reconciled and in sync. As a solution, you can create a new Chart of Depreciation and change the assignment of the company code to the new chart of depreciation. In order to achieve this, please raise an OSS incident with SAP Support. There is a pilot available for such requests.
9. You cannot use the same chart of depreciation, for new company codes created after conversion, where a Parallel Ledger in source system has different currencies than the Leading Ledger.
In ECC, it was possible to have a Parallel Ledger with a different currency assignment than the Leading Ledger. In S/4HANA, the non-leading ledgers inherits the parallel currencies from the Leading Ledger. This might require an additional chart of depreciation, as the migrated ones cannot be used (it will not have the depreciation area required for the additional parallel currency in the non-leading ledger).
10. You cannot do a partial Finance data migration – migrate selected company codes, ledgers or partial transactional data.
In case certain company codes are not required from business point of view, in order to disable some configuration checks during conversion, you can mark them as ‘‘template‘‘, as per the note 2159452.You can also consider deleting a non-leading ledger, in specific business contexts. You will have to open an OSS incident with SAP Support to get access to a pilot note. For selective data migration from ECC to an already LIVE S/4HANA OP system, please see the scenario Company Code Specific Conversion to S/4HANA with details in the note 2522155. This scenario can be executed only with the involvement of the team previously called SLO and currently called DM<.
For a smooth transition to S/4HANA, carefully consider what is the level of transformation you want to achieve, what is your current set up in the source ECC system and what are the current conversion tools and programs designed to do. A conversion project could be a great experience and bring lot of simplifications for your business and customers, given the right expectations are set.
Let me know what you think in the comments below!