System Conversion to S/4HANA FINANCE


For detailed information on the conversion process, please follow the below mentioned SAP SNotes.

S Notes  
2390881 Consistency checks before the installation during the migration to Asset Accounting (new)
2332030 Conversion of accounting to SAP S/4HANA
2333236 Composite SAP Notes: Enhancements and message texts for the program RASFIN_MIGR_PRECHECK
1939592 SFIN: Pre-Check Report for migrating to New Asset Accouting
2180591 Currencies in FI-GL and FI-AA are inconsistent
2147666 Assigned ledgers in FI-GL and FI-AA are inconsistent
2105948 Check report for Financials add-on
1968568 Release Scope Information: SAP Simple Finance add-on 1.0 for SAP Business Suite powered by SAP HANA
2220152 Ledger approach and Asset Accounting (new): Non-calendar fiscal year variant for parallel valuation
2023763 SFIN: check old dc engine and parallel currency in precheck report RASFIN_MIGR_PRECHECK
2246638 Check parallel areas in ANLB is mssing in Precheck
2226973 sFIN: Period scaling does not correspond to the definition AFASL
2353504 ACC_AA 173 not issued in case of incorrect configuration
2359854 Precheck: No message handling when checking periodic APC posting
1976487 Information about adjusting customer-specific programs to the simplified data model in SAP Simple Finance
2186803 SAP Simple Finance, OP: Treatment of NewGL tables and customer enhancements
2160045 S/4HANA Finance: Fields of Appends to COEP and BSEG missing in table ACDOCA
2076652 SAP Simple Finance: SAP Note for adjustment of customer-specific programs for aging
2105948 Check report for Financials add-on
2408083 FAQ: Data Model of S/4HANA Finance Data Migration
2431747 General Ledger: Incompatible changes in S/4HANA compared to classic ERP releases

Steps to remember for the Conversion:

Preparation of Data

Before starting system conversion, get system ready by performing the following activities:

⇒ Check the consistency of your financial data and perform reconciliation between your accounting components, so the data can be merged correctly in the universal journal entry. In SAP S/4HANA all line item documents are stored in the universal ACDOCA data table.

⇒ Perform period-end closing including the storage of reporting key figures and closing the posting periods.

  • Lock the current and previous periods in Materials Management using program RMMMPERI.
  • Perform closing for periodic asset postings using program RAPERB2000.
  • Execute the periodic depreciation posting run using program RAPOST2000.
  • Make sure that all held documents have either been posted or deleted.
  • If you are already using account-based profitability analysis, perform a delta upload to SAP BW for all account-based CO-PA DataSources for which you use the delta method.

⇒ Document the posting data. Make sure that all carry forward balances are complete and consistent. To ensure this, carry forward the balances for all currencies and all ledgers.

⇒ Archive any data that you no longer need in every day business processes before the migration.

⇒ If you have not been using the new depreciation calculation from the Enterprise Extension Financials Extension (EA-FIN) you must implement it as part of a separate project.

Prepare Asset Accounting

Activate the new depreciation calculation in your source system. To do so you must activate the EA-FIN business function.

Perform Pre-Checks

 ⇒ Pre-Checks help you identify the steps you need to take to ensure your system is compatible with the conversion process.

⇒ The Controlling and General Ledger pre-checks provided analyze whether your ledger, company code and controlling area settings are consistent and can be migrated to SAP S/4HANA. These Controlling and General Ledger pre-checks are automatically executed when you run the report R_S4_PRE_TRANSITION_CHECKS.

⇒ To run pre-checks for Asset Accounting (FI-AA), please implement the SAP Notes listed in the collective SAP Note 2333236. The pre-check program for Asset Accounting (FI-AA) is not included in the central pre-check report R_S4_PRE_TRANSITION_CHECKS. To execute the appropriate pre-checks for Asset Accounting, please run the report RASFIN_MIGR_PRECHECK.

⇒ Whereas you run the report R_S4_PRE_TRANSITION_CHECKS in client 000 to perform the checks across all clients, then run the report RASFIN_MIGR_PRECHECK in each productive client.

Thank You

Jayanth Maydipalle


New GL with document splitting: Legacy data transfer

You plan to use the new general ledger in mySAP ERP with active document splitting. Beforehand, you need to determine the best way to transfer legacy data from operational systems with the minimum amount of effort?

Reason and Prerequisites

You want to create a new system, and copy the posting data from financial accounting from an old system or an external system.

This note gives you a rough guide of the options you have when you transfer legacy data. However, it is not a complete guide and there are also be other scenarios. Therefore, you should always set up a legacy data transfer as a project and carry it out with your SAP consultant on site. This note can only provide limited help in the process.

The following two scenarios are possible:
1. Legacy data transfer from an SAP system.
2. Legacy data transfer from an external system.

Scenario 1: Legacy data transfer from an SAP system.
Create a copy of your existing SAP R/3 system and then carry out the technical upgrade to mySAP ERP.
You can then carry out the migration from the classic G/L accounting to the new G/L accounting within the framework of a project.

To ensure maximum security, SAP supports each migration project with a migration service.
Scenario 2: Legacy data transfer from an external system.
This scenario can in turn be spilt up into the following subsections.
These influence how the documents should be transferred:

2.1.   G/L accounts, not managed on an open item basis
2.2.   Accounts that are managed on an open item basis (in particular customers/vendors)
2.2.1. Singular account assignment
– Substitution
– Constant
– Inheritance
2.2.2. Distributed account assignments
– Documents with offsetting lines
– Migration with migration customizing (Enter splitting)

In principle, it is always best if you prepare the data in the operational system with corresponding quality, and if the corresponding items are delivered with the account assignments required for the document splitting.

2.1. Normal G/L accounts not managed on an open item basis:
In the new system for G/L accounts, you should post to period 12 of the old fiscal year (and the posting date should be the last day of the fiscal year) (you can use report RFBIBL00 to do this, for example). As a result of the normal balance carryforward, you receive a start financial statement in period 0 of the new fiscal year.

2.2. Accounts that are managed on an open item basis:
The open items must be posted to the legacy system in the same way, for example with original posting date, due date, term of payment and so on.

2.2.1. Singular account assignment.
Within the FI substitution (Callup point 2 – Document level), you assign a unique account assignment to the receivables/payables or to accounts that are managed on an open item basis. The document splitting should not carry out splitting anymore and should copy the account assignment from the open item directly. The subsequent processes then refer to the substituted account assignment.
Alternatively, you can post the open items individually, where the offsetting line has a unique account assignment. If the inheritance is active in the document splitting, the account assignment is transferred to the open items. During this procedure, the account assignment is only set in the general ledger view.

If no complete opening balance sheet has to be created on additional account assignments, a standard constant can be set in the document splitting. The account assignments of this constant are set on all rows that are not assigned to accounts. After the transfer, this function of the standard account assignment can be deactivated again.
Alternatively, a separate splitting rule can also be defined, which assigns a constant to the items that are not assigned to accounts. This splitting rule can be assigned to a document type that is only used within the framework of the data transfer.

2.2.2. Distributed account assignments.
In the general ledger view, the open items should be distributed to the general ledger characteristics.
– During the posting of the documents with the open items, the document splitting should distribute the open items on the basis of the offsetting lines that are assigned to accounts. The expected relationship of the account assignments to the open items is displayed in the offsetting lines. Where necessary, a separate document splitting rule must be defined, which is assigned to a document type created especially for the legacy data transfer.

– The legacy data transfer occurs in the classic G/L accounting (the new G/L accounting is not active). Within the framework of the following migration from the classic G/L accounting to the new G/L accounting, there are tools which can enter a distribution for document items for documents of the current fiscal year. In this case, using a migration scenario with document splitting is absolutely necessary. Note that this process, that is, first transferring legacy to the classic G/L accounting, and then carrying out the migration usually means more work in the project.

Important: Up to the last point, the document splitting must always already be activated and set completely during the transfer! Otherwise, you will have more work to do when you use the document splitting at a later stage.