“”

Q1. SAP HANA utilizes which new Technology?

 Wireless networking
 Solid State drives
 Multi Core CPUs
 Large read only Memory

Databases that support SAP S/4HANA can handle both OLTP and OLAP processing from a single data model
and therefore, we do not need to move transactional data to a separate system. This means transactional
and analytical applications run off the same tables, and data is available in real-time at every level of
detail.

******SAP S4/HANA System conversion

Customers who want to change their current system into a SAP S/4HANA system (Database, NetWeaver
and Application transition) in one step can benefit from the following:

 Migration without re-implementation

 No disruption for existing business processes
 Re-evaluation of customization and existing process flows

There are tools available to help complete these activities. Software Update Manager (SUM) and
Database Migration Option (DMO) are used for rapid database migration.
Key deliverables per Phase
The authorization object FINS_MIG is required to execute SAP S/4HANA migration activities.

New SAP customers starting with SAP S/4HANA take over their legacy data using other tools. SAP S/4HANA
migration tools only work for existing customers and systems. Depending on the active applications in the
source system, different preparation steps are relevant. The Greenfield approach (new implementation)
is always an option and should be considered.

You can migrate either directly from classic G/L to SAP S/4HANA or first migrate from classic G/L to
new G/L and from there to SAP S/4HANA. The second option is only advisable if you need to implement
document splitting and/or parallel ledgers immediately. SAP will offer services to add additional ledgers
and document splitting in the future.
Q1. You can implement additional standard ledgers in a system during a migration project

 True
 False

High Level System prerequisites for Migration

 Uses a Unicode system

 Uses SAP NetWeaver 7.51
 Uses SAP Business Suite
 Uses SAP HANA DB
 Uses SAP ERP ECC 6.0 atleast Ehp 8

Only one fiscal year can be open in asset accounting during migration and the last year cannot be
reopened after migration.

2304418 - FI-AA Year end closing reset is not allowed for migrated years .

A certified Financial statement for the previous fiscal year is a pre-requisite for the conversion.

Q2. Only one Fiscal year can be opened in Asset accounting during migration, the previous year can be
reopened after migration is completed.

 True
 False
Q3. Which factors can greatly affect the required length of a migration Project ?

 The size of the system

 The system starting point new or classic G/L
 The data quality in the system
 The use of the NZDT (Near zero down time)

Preparation for Migration’

 Analysis and Prepa?’ration

 Installation
 Customizing
 Data Migration
 Post Processing
Before migration, all sub ledgers must be fully reconciled. Any inconsistencies found in test migrations
must be cleaned up in the productive system.
Postings are not permitted in the system after installing SAP S/4HANA until the end of migration.
Use the switch business partner framework browser for activating: CA_BP_SOA,
VENDOR_SFWS_SC1 and VENDOR_SFWS_SC2 have to be active for the vendor contact
person data to be synchronized with BP contact person data (SAP Note 1454441–Development
of contact person for vendors).

To allow the customer/vendor numeric numbers to be taken over to the business partner, the
numeric intervals of the business partner number ranges must be set to external. Switch back
after the successful data synchronization. The numeric intervals of the business partner must be
changed to internal.
For every customer/vendor account group, a BP grouping must be available. You can only use
the same business partner grouping if the customer number is equal to the vendor number in SAP
ERP.

Run check report mapping (SAP Note 2216176) to ensure all the necessary CVI mappings
are done.

The following mappings are checked:

 BP roles are assigned to account groups

 Every account group BP grouping must be available
 Customer value mapping
 Vendor value mapping
 Customer and vendor value mapping (BP → customer/vendor)
 CVI mapping (check CVI_CUST_LINK/CVI_VEND_LINK vs. KNA1/LFA1) - post-
conversion check
 Contact person mapping - post-conversion check
Customizing

Software Update Manager (SUM) is the technical tool for system conversion to SAP S/4HANA.
Migration starts after the SUM ABAP process and the follow-up activities.

It is important not to activate the new G/L manually. The flag for the new GL will be automatically
activated later.

By default, after the installation of SAP S/4HANA and before finalizing the migration, an error
occurs in the case of an attempted posting: FINS_FI_MIG 150 Data migration is not yet finished:
Posting of documents is not possible. The message can be switched from error to
warning/information in the test environment but should never be changed in a productive system
as this will lead to data inconsistencies. Start with 10 jobs to define the optimal number of jobs.
Increase or decrease this number and check the effect on the system performance in the data
migration monitor in the later steps.

The fiscal year variants of productive controlling areas and all their assigned company codes
must be the same.
All entries in the universal journal need all required currency types and amounts according to the
customizing. This includes the currency types which were only used in controlling.

Define exchange rate types:

This is relevant for statistical CO objects with object currency not equal to company currency.
The corresponding line item with the real account assignment is already archived and no
company currency is available.

Amounts in local currency need be calculated by using this currency type (M or EURX) and
posting date.

Calculate amounts for previous CO specific currencies:

Amounts for currency types that were formerly used only in CO are calculated and form existing
FI amounts based by FI customizing or by using the CO approach (note 678180).

Calculate amounts for previous CO specific transaction currencies (this is only needed in
case of using transfer prices):

For a migration from ERP, use value 2 – Calculate Transaction Currency for each Parallel
Valuation (1 – Take Document Currency for all Valuation is used for a new S/4HANA
installation).
The new G/L is an active flag set automatically in the background after this step.

The technical migration involves the following settings for the journal entry ledger:

 Company code assignments

 Currency settings
 Fiscal year variant
 Open period variant
 Settings from real-time integration of CO-FI

This activity should not be repeated if it has run error-free, since it overwrites the values.

It is possible to define eight additional currency types besides the local currency (HSL, the
currency type 10) and the global currency type (KSL, the currency type of the controlling area).
There is no more dependency on the currency types of the leading ledger. Table
FINSC_VERSN_LD defines the mapping controlling area and version to ledger.

The new currencies have the following characteristics:

 Real-time currency conversion for all currency types is possible

 Balance zero per document is guaranteed for each currency
 Controlling area currency (KSL) is now calculated for all accounts, even for non cost
elements.
 This requires that the amounts are selected from historical data. This is not yet supported
for all processes. Therefore, amounts are converted with the current exchange rate
(program FINS_ACDOC_UTIL_SET_KSL from note 2357161).

The new clearing logic is available for open items on general ledger accounts, customers,
vendors, CO allocations and GL allocations, but not for material ledger process, CO settlements
and fixed asset processes like depreciation.

You configure the settings for the Account Approach as for Ledger Approach but of course
all accounting principles refer to the leading ledger. There is a new indicator Parallel GL
Accounts in the company code settings for the ledger. this is to increase transparency when
assigning more than one accounting principles to a ledger for the company code.

The leading ledger (usually 0L), maintained in Define Settings for Journal Entry Ledger, must be
always assigned to CO version 0. The leading ledger is representative for controlling. This is
currently a restriction.

Use IMG activity, Review the Assignment of Ledger and Company Code to Acc.-Principles, to
get an overview about the assignment of ledgers, company codes, and accounting principles.
The document types can be specified on the following levels:

 Company code via different document type mapping variants.

 Controlling business transactions (for example KAZI - Actual cost center accrual) which
can have a separate document type.
 Normal postings and cross-company postings which can have separate types per business
transaction as well.

Check and define default values for posting in Controlling

Default settings are necessary for postings where there is no possibility to manually define the
document type and leger group in the Controlling business transaction.

The major question here is which ledger(s) should Controlling update?

This is the same critical setting as in new G/L where the ledger group assigned in the real-time
integration variant determined the ledger posted to in Financial Accounting. When no ledger group
is entered in controlling transactions, all ledgers are updated in table ACDOCA (exactly as for FI
transactions).

The decision is simple here when using the accounts approach.

The business functions include (amongst others) the following helpful functions:

 Posting and Clearing for Specific Ledger Groups

 Drilldown Reports for Profit Centers and Segments
 Switch to Open Item Management for G/L Accounts
 Check Posting Period for Non-Representative Ledgers

The business functions will be activated with the transport requests in follow on systems (very
important: activation of all activated business functions should be transported, a quick manual
check in the target system is necessary)