sfin-training series migrationdocshare01.docshare.tips/files/30041/300413062.pdf · sap simple...

SFIN-Training SeriesMigration

18th June, 2015

Objectives

• Simple Finance overview• How to Migrate to Simple Finance?• Summary

3

SFIN-Overview – Functional Changes

Copyright © 2015 Accenture All rights reserved.

•Technical Changes in tables•Compatibility Views for total Tables•Unified Master Data•Appendix Ledger•Ledger & Currency Settings

General Ledger

• CO Actual Items in ACDOCA• Non Actual items stored in COEP• Faster Period close Controlling

• New Asset Accounting Mandatory• Asset Accounting Based on Universal Journal entry – No Redundant Data• Depreciation Postings happen with all details (individual assets)• Faster Depreciation postings due to new structure• Changes in Asset Data Conversion

Asset Accounting

• Account based Profitability Analysis is default solution • Account Based profitability analysis is based on Universal Journal Entry• No Changes in costing based COPA• Cost of Goods sold component wise and Price variance category wise available from 1.0

Profitability Analysis

• Usage of Material ledger for parallel currencies and parallel valuation purpose based on ACDOCA• No change in usage of Material Ledger for Actual Costing Purpose Material Ledger

4

SFIN-Overview – Technical Changes


•Removal of indices / total / and line item based linkage•Single Line Item Table - ACDOCA•Compatibility ViewsArchitecture

•One line Item table with all dimensions• Immediate profitability Character tics derivations•Reduction of memory footprint – no redundancy•Fast Multi-dimensional Reporting•One Single Extractor

Unified Journal Entry

• Compatibility Views to safeguard custom ABAP• Via this views the select is redirected to the new persistency in HANA• Customer ABAP programs that read directly “COEP” via select statements continue to run as before• Central Journal Approach

Non Disruptiveness

•Real Time BI like operational Reporting •Hanalive using Lumira & Office Analysis as front end•Fiori based transactions•Embedded BW – No Replication

Reporting & UX

5

The New Architecture


Custom specific

Universal Journal Entry in SAP Accounting

• Single repository of journal entries across multiple applications without redundancy

Universal Journal

This enables deeper, instant insight across all dimensions, easier extensibility, and process optimizations for an accelerated financial close.

PublicSector

Joint Venture

ProfitabilityAnalysis

FixedAssets

MaterialLedger

AccountsReceivable

Mgmt.Accounting

AccountsPayable

General Ledger

7

Simplified Data Model


8

Non Disruptiveness


Safeguarding customer investments: • From the perspective of an ABAP program nothing

changed (read access) • We provide so called “compatibility views”. • Via this views the select is redirected to the new

persistency in HANA • In the example given, an access to table

FAGLFLEXA is redirected via the view V_FAGLFLEXA to the new Universal Journal Entry

• Consequence: Customer ABAP programs that read directly “FAGLFLEXA” via select statements continue to run as before

Objectives

• Simple Finance overview• How to Migrate to Simple Finance?• Summary

From where can I move into Simple Finance?

11

Migration from Classic G/L to G/L in SAP Accounting


Classic G/L

in ERP

New G/Lin ERP

S4HANA

At year end only

At anyperiod end

Subsequent Optimization * Introduction of additional ledgers Introduction of document split Change from parallel accounts to parallel

ledgers

Recommendedapproach

Alternateapproach

(if New G/L migrationproject already started)

Migration is fast and easy

New G/Lin ERP

S4 HANA

At anyperiod end

At anyperiod end

Migration Steps

Migration Steps - Preparation

Preparation

1. Pre-checks, if Simple Finance can be installed on current system setup2. Reconcile GL with sub ledgers (Data consistency checks)3. Check Customer-Defined Coding4. Period End Close and Financial Reporting5. Documentation Before Installation


Preparation

OSS note – 1939592 – It checks for prerequisite to implement new asset accounting. Smart Financials require new GL accounting. If New GL is not active then you can install simple Finance first and then Migrate to New GL accounting.New GL is activeJoint Venture accounting must not be active.Lease accounting Engine must not be activeClassic Real Estate Must not be activeIn component PSM-FM, IS-PS: The request with reference to Asset must not existPeriodic depreciation Must be completeDepreciation area for parallel currency must exist.Execute program : RASFIN_MIGR_PRECHECK

OSS note :2129306 – ZFINS_MIG_PRECHECK_CUST_SETTING program checks consistency for ledger, company code, controlling area to determine if Migration to SFIN2.0 is possible. This report checks if settings can be automatically Migrated to new customizing tables• Currency settings• Compatibility of User exits and BADI• Are there scenario like transfer pricing, ABC ?

• Pre-checks, if Simple Finance can be installed on current system setup


Preparation • Pre-checks, if Simple Finance can be installed on current system setup

OSS note – 2153644 - Country Release Information for SAP Simple Finance – There are 62 country version notes

OSS note - 2127080 – Current Limitation of simple Finance

OSS note : 2119188 – Industry solution released with Simple Finance

http://service.sap.com/sap/support/notes/2153644


Preparation • Reconcile GL with sub ledgers (Data consistency checks)

• Indices and documents (report RFINDEX_NACC) - You use this program to check the consistency of the document views (BSIS, BSAS, BSID, BSAD, BSIK, and BSAK) with the line items in table BSEG.

• FI documents with FI balances for all fiscal years without archived data (F.03 or FAGLF03)

• Reconcile asset accounting with GL (transactions ABST and ABST2)

• Reconcile AP / AR sub ledgers with GL (report SAPF190 or FAGLF03)

• Reconcile Materials Management. with GL (reports RM07MBST, RM07MMFI)

• Ledger comparison within New GL (transaction GCAC)

• Take snapshot of all FI CO tables. Note down number of entries in each tables


Preparation • Check Customer-Defined Coding

• Check if you have write accesses in your own customer objects to the tables becoming obsolete. You have to replace these accesses, since the views with same names allow only read access. If we have added a custom field which is getting updated by custom program or a standard field which is getting updated by custom program in a table which is becoming obsolete

• Check if you have your own customer-specific views in your own objects to the tables becoming obsolete. You have to replace these views with an open- SQL SELECT or the call of a read module, since the Data Dictionary does not support database views that are based on other views. This needs to be changed as that table it self-become a “view” or getting data via a view on ACDOCA. “View” on a “View” is not supported


Preparation • Period End Close and Financial Reporting

• Close previous years in asset accounting (only current year open)

• Run pre-check for asset accounting again

• Process or delete all held documents

• General Ledger and Sub ledgers – ensure all balances carried forward


Preparation • Documentation Before Installation

• Financial Statement

• Asset History Sheet

• Customer and Vendor sales list and open item lists • Totals for cost centers

• Further SAP standard and custom specific reports

20

Migration Step- Installation -Technical Components


Installation

1. Lock all users

2. Installation of Simple Finance Add On- Back up table created, Index tables are converted to views

3. Create the back up table

4. Perform reconciliation and checks on data values after install.

21



Installation • Installation of Simple Finance Add On- Back up table created, Index tables are converted to views

SAP enhancement package 7 for SAP ERP 6.0

exchange innovation add-on ► the installation of the SAP Simple Finance add-on exchanges the classic Financials applications of SAP ERP 6.0

SAP Simple Finance Add-On 2.0

SAP NetWeaver 7.4

SAP HANA 1.0

Backend

SAP HANA Live 1.0for SAP ERP

VDM: Virtual Data Model

SAP HANA Live 2.0 for SAP Simple Finance

VDM: Virtual Data Model

SAP Smart Business 2.0 for SAP Simple Finance

related HANA content

SAP Smart Business foundation component 1.0

related HANA content

SAP NW Gateway 2.0* or SAP NetWeaver 7.4

any DB

SAP Fiori 2.0for SAP Simple Finance

Frontend Serveroptional

SAP Simple Finance comprises 4 software products:

1. SAP Simple Finance add-on 2.0 based on EhP 7 for SAP ERP 6.0, SAP NetWeaver 7.4 and SAP HANA 1.0

2. SAP HANA Live 2.0 for SAP Simple Finance based on SAP HANA Live 1.0 for SAP ERP and SAP HANA 1.0

3. SAP Fiori 2.0 for SAP Simple Finance based on SAP NetWeaver Gateway 2.0 or SAP NetWeaver 7.4

4. SAP Smart Business 2.0 for SAP Simple Finance based on the SAP Smart Business foundation component 1.0

22


Installation • Create the back up table

After successful installation system would create back up tables for tables which are getting obsolete

23


Installation • Perform reconciliation and checks on data values after install.

After successful installation system would create back up tables for tables which are getting obsolete. Perform reconciliation between original tables and backup tables

24

Migration Step- Data Transfer


Data Transfer

1. Define Message Types for Posting Before and During Migration

2. Preparations and Migration of Customizing for the General Ledger

3. Preparations and Migration of Customizing for Asset Accounting

4. Preparations and Migration of Customizing for Controlling

25

Migration Step- Customization- General Ledger


Data Transfer

• Define Message Types for Posting Before and During Migration

In this Customizing acitvity you define that users are informed by a message so that no posting can be allowed during posting.

Postings are not allowed until Migration is completed! Postings before finishing migration will lead to inconsistencies! In a test environment you can maintain the message type!

26



Data Transfer

Preparations and Migration of Customizing for the General Ledger

• Activate SAP Reference IMG for Financial Accounting (New)

1. Select transaction se38. Enter the program RFAGL_SWAP_IMG_NEW.2. Select transaction se38. Enter the program RFAGL_SWAP_MNEU_NEW.

•. Check and Adopt Fiscal Year Variants

The migration to the unified journal entry requires an unique fiscal year variant in controlling and financial. The report reconciles the fiscal year variant of the controlling areas and their assigned company codes. It creates a proposal for the configuration change.

27



Data Transfer


Migrate General Ledger Customizing :

• Migrate all new General ledger to new customizing (Company code assignment, currency setting, fiscal year variant, open period variant, setting for real time integration between CO-FI)

28



Data Transfer


Define Settings for Journal Entry Ledger

• In this Customizing activity, you define the ledgers that you use in Accounting.

29



Data Transfer


Define ledger for CO version : Assignment of version to ledger

• In this activity, you define a ledger that represents Controlling. That is, a ledger that contains all postings of actual data that is relevant to Controlling. This is done by assigning the version 000 to a ledger. You do this on a company code level, but you have to use the same ledger for all company codes.

The current restriction is that the version 000 must be assigned to the leading ledger.You have to assign the version 000 to the leading ledger for all company codes that are assigned to a Controlling area.

30



Data Transfer


Define Document Types for Postings in Controlling

• In this activity, you can create new document types for postings in Controlling

31



Data Transfer


Define Document Type Mapping Variants for CO Business Transactions

• In this activity, you define a mapping variant that maps CO business transactions to document types

32



Data Transfer


Check and Define Default Values for Postings in Controlling

• In this activity, you define default values for use in CO business transactions whose user interfaces do not allow you to enter a document type or a ledger group for posting purposes.

33



Data Transfer


Define Offsetting Account Determination Type

• In this customizing activity you define how the system calculates the offsetting account in all applications

SAP recommends to choose the option "As case 2, but including lime items generated automatically".

34



Data Transfer


Define Source Ledger for Migration of Balances

• In this customizing activity you define the source ledger (and by doing so the source database table) of the balances for general ledger accounting using the following:

• Target Ledger

• Company Code (you can specify * to apply the settings to all company codes)

• Starting Fiscal Year (by specifying year 0001 you apply the settings for all fiscal years)

35



Data Transfer


Execute Consistency Check of General Ledger Settings

• In this activity, the Customizing settings for the ledgers are checked. This check must run without error messages before migration of transaction data.

36



Data Transfer


Activate Business Functions

• In this customizing activity you activate the business functions that are necessary for migrating to the SAP Simple Finance add-on for SAP Business Suite powered by SAP HANA

Business functions need to be activated:FIN_GL_CI_1FIN_GL_CI_2FIN_GL_CI_3

37

Migration Step- Customization –Asset accounting


Data Transfer

• Preparations and Migration of Customizing for Asset Accounting

• Check if enterprise extension EA-FIN is active• Before activating this Component make sure that all period end closing activities have been performed• Reconcile all ledger and sub ledgers for leading and non leading valuation

1. Check Prerequisites for Activating Asset Accounting (New),

2. Migrate Charts of Depreciation,

3. Display Migration Log,

4. Activate Asset Accounting (New)

•. If you are already using classic Asset Accounting and want to migrate to new Asset Accounting, you have to migrate the charts of depreciation from classic Asset Accounting.

•. During the migration, the system makes the following changes

• Assign accounting principle and ledger group

• Adjust Post to General Ledger option

• Specify transfer of APC values

• Specify transfer of depreciation terms

• The system determines, if you are using the accounts approach or the ledger approach

38

Migration Step- Customization –COPA


Data Transfer

• Preparations and Migration of Customizing for Controlling

1. Delete Settings for the Change of Profitability Segment Characteristics

•. In this activity, you delete the settings for profitability segment characteristics (segment level) made in transaction KEQ3 because in SAP Accounting powered by SAP HANA each profitability segment contains all available characteristics. A summarization of specific characteristics is no longer possible. This includes the settings for distributed profitability analysis characteristics (segment level) made in transaction KEQ4.

2. Maintain Operating Concern

•. In this activity, you activate your operating concerns for account-based Profitability Analysis, if not yet done.

3. Activate Account-Based Profitability Analysis

•. In this activity, you activate account-based Profitability Analysis for your operating concerns, if not already active.

4. Transport Operating Concern

•. In this activity, you transport the definition of your operating concerns.

39

Migration Step- Data Transfer


Migration

1. Regenerate CDS views- For Custom fields2. Migration of Cost Elements and Customizing3. Technical Check of Transaction Data4. Enrich Transactional Data (BSEG, COEP)5. Migration of Line Items into New Data Structure (ACDOCA)6. Migrate Balances7. Set Migration to completed.

40

Migration Step- Data Migration (Generate CDS views)


• Regenerate CDS views- For Custom fieldsData Migration

Regenerate the compatibility and data migration views so as to adapt them to the configuration of customer-specific entities. The following applications are considered during generation:

• General Ledger

• Controlling

• Material Ledger

• Cash Management

• Asset Accounting

• Regenerate the compatibility and data migration views to adapt them to customer-specific entities

• Regenerate the mapping of customer-specific fields in the data migration procedure

• Generate the redirection of SELECT-statements to corresponding compatibility views (see below)

41

Migration Step- Data Migration –Migration of Cost element


• Migration of Cost Elements and CustomizingData Migration

1. Check Consistency of G/L Accounts and Cost Elements

•. In this Customizing activity you check whether the G/L accounts and cost elements are consistent with each other.

2. Migrate Secondary Cost Elements to Chart of Accounts, Display Status of Migration of Cost Elements

•. In sFIN 2.0 the master data of G/L accounts and cost elements were merged. Cost elements are now special G/L accounts and must be maintained in the same transaction as for maintaining G/L accounts: Edit G/L Account Centrally (FS00).

3. Migrate Default Account Assignments, Display Status of Migration of Default Account Assignments•. The fields of the cost element master have undergone a review and not all fields have been retained. In

particular, the fields for default assignment on cost center or internal order were omitted from the joint master data record.

•. Starting from existing cost element master data, the migration process transfers the default assignments from the master data table CSKB to the Customizing table TKA3A.

4. Adopt Authorizations

•. The merge of cost elements and G/L accounts requires adjustments to authorizations for creating cost elements.

42

Migration Step- Data Migration –Technical check


• Technical Check of Transaction DataData Migration

1. Analyze Transactional Data, Display Status of Analysis of Transaction Data

•. In this Customizing acitivity you analyze in a test system if all transactional data is complete and correct.

For example:check whether all FI documents are complete and correct •. Balance zero •. all line items have corresponding document headers •. corresponding entries in document lines table (BSEG) and in line items table of New G/L

(FAGLFLEXA) have same amount •. consistency of New G/L index tables (FAGLBSIS, FAGLBSAS) with table BSEG_ADD •. use the result of this check to correct inconsistent documents in productive environment before

starting Simple Finance installation •. database views for indexes return same values as backup tables (backup tables contain data of

secondary index tables in the former release (e.g. BSID_BCK for BSID)

2. Reconcile Transactional Data, Display Status of Technical Reconciliation of Transactional Data

•. The program reconciles the existing transactional data to ensure that the data migration is executed correctly. It checks necessary prerequisites for the programs (like having a document header per line item which is needed for the corresponding join to work properly) and it checks that both parts of a set of redundant data (like documents and application indices) are consistent. You must solve every inconsistency before you start the data migration.

43

Migration Step- Data Migration –Enrichment of Data


• Migration - Enrichment of DataData Migration

1. Enrich Transactional Data, Display Status of Enrichment of Transactional Data

•. In this Customizing activity, you enrich transaction data and documents and migrate them to SAP Accounting powered by SAP HANA..

For Example:•. Filling BSEG-fields from BKPF•. Filling of COEP from COBK and OBJNR•. Filling of profit center fields into CO line items füllen•. Filling of company code data into old CO line items•. Filling of company code data into old CO totals•. Filling of BSEG_ADD from FAGLBSIS/AS•. Filling of COSP_BAK-BUKRS and COSS_BAK-BUKRS

2. Check of Migrated Documents, Display Status of Check of Migrated Documents

•. In this Customizing acitivity you check if all documents are enriched correctly.

44

Migration Step- Data Migration –Migration into New Structure


• Migration of Line Items into New Data Structure (ACDOCA)Data Migration

1. Migrate Accounting Documents to Universal Journal Entry Structure, Display Status of Document Migration to Universal Journal Entry

•. In this Customizing acitivity you migrate accounting documents to the universal journal entry structure.

2. Check Migration of Accounting Documents to Universal Journal Entry, Display Status of Check of Accounting Document Migration

•. In this Customizing acitivity you check if all accounting documents have been migrated correctly.

45




46




47

Migration Step- Data Migration –Migrate Balances


Data Migration

1. Migrate Balances, Display Status of Migration of Balances

•. In this Customizing acitivity you migrate balances.

2. Check Migration of Balances, Monitor Check of Balances

•. In this Customizing acitivity you check if all balances have been migrated correctly.

• Everything what can not get from line items/documents:• Balances carried forward• historic line items may be archived

in this case line items are calculated by comparing the sum of the line items with the old totals (same logic corrects CO internal postings and ML totals)

• Migrate Balances

48

Migration Step- Data Migration –Complete Data Migration


• Set Migration to completedData Migration

1. Calculate Initial Depreciation Values

•. You use this activity to initially build the planned depreciation values for Asset Accounting.

2. Reconcile Depreciation Values and Totals Values in Asset Accounting

•. In this Customizing activity, you once again reconcile the totals values and also the depreciation values.

3. Reconcile and Compare Migrated Data

•. Perform the following comparisons and reconciliations for the migrated data and ledgers to ensure that the migration has been performed successfully and correctly.

4. Set Migration to Completed & Unlock all users•. In this Customizing activity you set the mitgration to completed. If you set the migration to completed,

users are allowed again to make postings in the system.

• Postings are allowed when Migration is completed!

Migration Step- Post Migration

Post Processing

1. Transfer Application Indexes

2. Fill Due Dates in FI Documents

3. Fill the Offsetting Account in FI Documents

50

Migration Step- Data Migration –Complete Data Migration


• Activities After MigrationPost Migration

1. Transfer Application Indexes, Display Status of Transfer of Application Indexes

•. In this Customizing activity, you can transfer application indexes to the database cold area in order to reduce main memory consumption.

2. Fill Due Dates in FI Documents, Display Status of Filling in Due Dates into FI DocumentsYou use this Customizing activity to fill the new due date fields in the FI line items for customers and vendors and for G/L account line items that have a base line date. System stores them in the document tables •. BSEG (document line items) •. BSEG_ADD (New G/L) •. VBSEGD, VBSEGK, VBSEGS (parked documents)

3. Fill the Offsetting Account in FI Documents, Display Status of Filling the Offsetting Account in FI Documents

•. During data migration, you transfer FI documents to SAP Accounting powered by SAP HANA. As part of this process you use this Customizing activity to fill the offsetting account in FI documents.

• Pre-requisite:Business function DAAG_DATA_AGING

Sequence in Test and Productive Environment

Objectives

• Simple Finance overview• How to Migrate to Simple Finance?• Comparison with New General Ledger Migration• Summary