S4 Financials Powered By HANA-Purna

S/4 Finance Powered By HANA 2.0
Purna Chandar Pokala
Dec 10, 2015

© 2014 SAP SE or an SAP affiliate company. All rights reserved. 2Public
Purpose of the Presentation
 Give a High Level Overview on the technical component of Smart Financials (sFIN2.0) and how it relates
to other products
 Give a High level overview on the upgrade paths on Smart Financial (sFIN2.0)
 Give a High level overview on the required installation & Migration steps from a Functional point of view
S/4 Finance Topics
1. New General Ledger
2. Universal Journal Set ups
3. New Asset Accounting
4. New Controlling area
5. New House Bank & Cash Management
6. Fiori tiles Configuration
7. HANA live quarry views
8. Central Finance Setup
9. IBP – Changes on planning
10. Migration Steps from ECC to sFIN

Facts to start with…
S/4 HANA Financials Package 2.0
 Includes Simplified Accounting – New General Ledger, New Asset Accounting, Account Based CO PA
 Based on in – Memory Database Technology SAP HANA
 Delivered as on Add on Product to Enhancement Package 7 for SAP ERP 6.0 & also S/4 HANA system
 Replacing the Classic ERP Financials applications, but still Highly Integrated with other ERP applications
like Logistics ., Now in to Simple Logistics
 Deploy on premise & also Cloud solution – SAP supporting both along with Hybrid support service
 Key Innovation - Fiori as User interface with UI5 technology
 Role Based authorization
 Enables real-time reporting due to HANA in-memory database technology
 Accelerated processing and reporting, with reduced time to close and more timely availability of data for
analysis
 Document Level Drill down reporting

S/4 HANA Finance Capabilities - Improve SAP Performance
S/4 Finance
One Logical Document
One accounting document across
Finance, Controlling, and CO-PA
simplifies reporting and display of
accounting document information
Elimination of Aggregates
Elimination of totals tables, fixed
hierarchies, and database indices
allows for flexible reporting and
dynamic hierarchies pulling from
line item detail in real-time
Real-time Close
Reduction in batch close
processes, processes designed for
real-time operations, and
availability of reporting on demand
enables transition to a continuous
(soft) close
Next-Gen User Experience
New web and mobile transactions,
role-based dashboards, and
flexible reporting powered by SAP
Fiori
Integrated Business Planning
Embedded Business Planning &
Consolidations sits within the same
HANA database as SFin, updates the
same financial tables, and can utilize
line item detail
Central Journal
Pre-built SLT libraries and data
transformation capabilities enable
rapid deployment of SFin as a
central financial platform

Architecture of SAP Accounting powered by SAP HANA
Logistics
Document
CO
Document
FI
Document
Totals & Indices
Financial Accounting
Totals & Indices
Management Account.
From … Stability
Processing
Analytics
CO Document
FI Document
Flexibility
Aggregation on the fly
via HANA views
Pre-Defined Aggregates
Flexibility
Stability
Processing
Analytics
Logical document
Logistics
Document
… To
Customer
Benefits
• Harmonized internal
and external
reporting
• Higher flexibility in
reporting and
analysis
• Significantly reduced
reconciliation effort
• Significantly reduced
memory
consumption
• Central journal for
heterogeneous
system landscapes

Simple Finance Removes Redundancy

How Simple Finance Saves the Data Base Size
Table sizes of customer system
Table Description
ERP Financials in
Suite on HANA
Simple Finance on
HANA
BKPF Accounting documents 1.2 GB 1.2 GB
BSEG Accounting document line items 4.5 GB ** 5.0 GB
BSID Open items Accounts Receivable 0.1 GB
BSIK Open items Accounts Payable 0.0 GB
BSIS Open items General Ledger * 23.2 GB
BSAD Cleared items Accounts Receivable 3.3 GB
BSAK Cleared items Accounts Payable 2.1 GB
BSAS Cleared items General Ledger * 5.5 GB
KNC1 Totals Accounts Receivable 0.1 GB
LFC1 Totals Accounts Payable 0.0 GB
GLT0 Totals General Ledger 0.0 GB
Total (of above tables) 40.0 GB 6.2 GB
* Includes partially archived items (not considered here)
** Includes additional fields for New G/L

Simplifying User Experience

SAP Fiori UX

Fiori Apps

Universal Journal
 Creating backup tables for the totals
tables and index tables in the Data
Dictionary that are being done away
with (*_BCK in FI and *_BAK in CO)
 Saving the totals tables and index
tables in backup tables
 Deleting the original totals tables and
index tables
 Creating SAP HANA views (with the
same names) for the totals, index,
and line item tables
 Creating the new table for the
universal journal entry

New General Ledger
Two type of Ledgers
 Standard Ledger - standard ledger contains a full set of journal entries for all business transactions
 Appendix Ledger/ Extension ledger - An appendix ledger is assigned to a standard ledger and inherits
all journal entries of the standard ledger for reporting. Postings made explicitly to an appendix ledger
are visible in that appendix ledger but not in the underlying standard ledger. This concept can be used
to avoid duplication of journal entries if many business transactions are valid for both ledgers and
only a few adjustments are required in the appendix ledger

Open/Close Periods Ledger wise in Fiori

New Asset Accounting
Approach;
 Accounting Approach - The values of all types of valuation are then managed in one single ledger
 Ledger Approach- The values of each valuation are managed separately in separate ledgers.

New Asset Account
 Independent Dep Areas
 Delta Dep Area not required
 Independent Transaction types
 Different FYV for each valuation
 Dep area for quantity update
 Technical Clearing ac for Acquisition
 Separate document for each valuation
 Document Migration to Universal Journal

New Cost accounting
 Account Based COPA & Cost Based COPA - Costing-based profitability analysis is still available and you can use
both types of profitability analysis in parallel. However, account-based profitability analysis is the default
solution. With account-based profitability analysis, any revenue posting or cost of goods sold posting is updated
under the relevant account and assigned to the correct market segment characteristics
 Assignment of split to cost component structure
 COBK & COEP remains the key tables for CO, -COBK storing header and COEP storing line item., & They are linked
to FI tables ( BSEG, BKPF) with the POSNR field.
 COSS & COSP Removed

New Cost Accounting
New Transaction Codes:
 Settlement-Order & Project – VA88 to VA88H., & CJ8G to CJ8GH
 Result Analysis – KKAK to KKAKH
 WIP Calculation – KKAO to KKAOH
 Variance Calculation for Cost Centre – KSS1 to KSS1H
Changes in Configuration in Controlling
 Document type for posting in Controlling
 Document type Mapping for CO Business Transaction
 Default Variant assigned CO document to FI doc type
 Default Ledger assignment
 Ledger for CO version
COPA Reporting in Fiori
 Net Margin Analysis
 Margin Analysis – Analyse Margin Based on Customer, Segment, product & period –Controlling area
 Profit Margin

New Cost Accounting – Architectural Changes
 COEP table will still exist and be written with entries
except for Value type 04 and 11.
 ACDOCA will get updated with 04 and 11 value type.
 Compatibility views for tables are available on all
traditional tables. E.g.: V_COEP., - Custom programs on
this traditional tables can still use them. Via the view
select is redirected to the new table ACDOCA.
 Access to old table data is still possible with
V_tablename_ORI e.g. : V_COEP_ORI,
 COBK still will be written as before. & COSP and COSS
will all be written directly to ACDOCA.
 New tables COPS_BAK: Primary cost: Planned cost&
commitments
 COSS_BAK : Secondary cost : Planned cost &
commitments will be updated with entries other than
value types 04 and 11

New House Banks
 Bank Master Record
 House Banks
 Bank Accounts
 Connectivity Path

New House Bank

New Cash Management powered by SAP HANA
Cash Management Changes

SAP Cash Management powered by SAP HANA
Daily Cash Operations
– Cash Positions and Short-Term Cash
Forecasting
– Bank Transfer, and Payment Approval
– Analyse Payment Details, and Payment
Statistics.
Bank Account Management
Liquidity Management
– Mid-term Liquidity Forecast
– Actual Cash Flow Analysis
– Embedded Liquidity Plan and Variance
Analysis
New Fiori (UI5) user interface, and
KPI cockpit – SAP Smart Business for
Cash Management.
Integrated with FI, TRM, BCM (Bank
Communication Management), and IHC
(In-House Cash).

Central Finance
 Business Function Activation
 FINS_CFIN
 FIN_GL_ERR_CORR
 FIN_GL_ERR_CORP_SUSP
 Install SAP LT Replication Server
 Install sNote in source System
 2111634
 2108225
 2115885
 Central Finance Interface
 Master data either through Manual or
MDG
 Mapping Required for Master data &
later for Transaction data – Mapping in
Central Finance & Cost Object
Mapping ( Long Live/Short Live
data)
 Document Relationship Browser
 Central Finance Offer Badis
 Harmonized Financial Reporting

Central Finance – Posting Example

IBP – Integrated Business Planning

Planning in Excel
SAP delivers example workbooks
as content. Customers may use
this or use it as template for their
own workbook definition.
Planning XLS for:
 Cost centre
 Internal order
 Project
 Market segment
 Profit centre
 Profit & loss

SAP Analysis for Office via Excel - Example

HANA View

Migration Road Map

Migration Customization & Execution

Changes in new version 1503 Vs 1511

Steps before you install the add-on
 Making a preliminary check that ascertains whether the add-on can be installed with the current system
settings, or whether additional activities are required
 Making consistency checks that check the correctness of the accounting data from a technical point of view,
and list any inconsistencies
 Performing reconciliation between the accounting applications, to enable the data to be merged correctly in
the universal journal entry
 Carrying out period-end closing including the storage of reporting key figures and closing the posting periods
 Once you have carried out the preparatory steps, and have met the prerequisites for implementing the SAP
Simple Finance add-on, you can proceed to install it.
 while installing the add-on, the following steps to prepare the migration to make system automatically
executed it
 Creating backup tables for the totals tables and index tables in the Data Dictionary that are being done away
with (*_BCK in FI and *_BAK in CO)
 Saving the totals tables and index tables in backup tables
 Deleting the original totals tables and index tables
 Creating SAP HANA views (with the same names) for the totals, index, and line item tables
 Creating the new table for the universal journal entry as ACDOCA
 Migrate the accounting and Controlling data immediately following the installation
 After the migration, you have to reconcile the data and perform tests manually

Prior to Installing
 Make sure that you have either posted or deleted all held documents.
 Implement report RASFIN_MIGR_PRECHECK from SAP Note 1939592 , and test whether the necessary
prerequisites for new Asset Accounting have been fulfilled using this report
 If you discover when executing report RASFIN_MIGR_PRECHECK that currency areas are missing, you have to
create these first in separately and have the system determine the values.
 If necessary, implement the new depreciation calculation as part of a separate project as per SAP Note 965032
 Make sure that you have carried forward all of the balances in all applications to the current fiscal year. This
also applies to the sub ledgers as well., Use the following transactions:-
I. FAGLGVTR, if you are using new General Ledger Accounting
II. F.16, if you are using classic General Ledger Accounting
III. AJRW, if you are using Asset Accounting
IV. F.07, if you are using Accounts Receivable and Accounts Payable
 Check whether the currency settings and the CO configuration in your system allow you to upgrade to the SAP
Simple Finance add-on. Execute the report FINS_MIG_PRECHECK_CUST_SETTNGS asper SAP Note 2129306
 Consistency Checks Before Installation and Migration
 Check Customer-Defined Coding as per SAP note 1976487
 Handling Customer-Defined Fields and Interfaces
 Period-End Closing Activities
 check the consistency of your FI data
 Perform Reconciliation for General Ledger & all AP, AR, AA sub ledgers

Customer-Defined Fields & Coding
 SAP HANA generates new data structures in Accounting and replaces existing tables with same-named views
 Check if you have write accesses to the tables in your own customer objects in your customer namespace. You
have to replace these accesses, since the views with same names allow only read access.
 Check if you have your own customer-specific views in your own objects in your customer namespace for the
tables that no longer exist. 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.
 If a customer field exists in both BSEG and in the indexes, then it will automatically generated into the view with
the same name. if the customer field only exists in the index., - then It is not transferred into a view with the same
name In this case the field must first be included in the BSEG and filled using a customer program.
 If you transferred data from your Z tables to new General Ledger Accounting during the migration to the Financial
Accounting add-on 1.0, you have to delete the data of these Z tables before the migration to SAP Simple Finance
If you do not delete the data, the data of the Z tables is migrated again and transferred to the new table structure.
The values would then be duplicated.
 If you have used interfaces to connect your system to external systems that make postings to General Ledger
Accounting (in real time or subsequently), check whether adjustments need to be made to the interfaces
 ALE scenarios are only partially supported., Simple Finance add-on 2.0 system cannot serve as an ALE receiver for
CO line items., .because FI and CO line items use the same persistence table

Documentation before Installation & Migration
 Make sure that all balance carry forwards are complete and consistent
 Create the documentation for the closing to compare the data with data after the migration as per SAP
Recommends below
1. Financial statements (program RFBILA00)
2. Totals report for cost centres (transaction S_ALR_87013611)
3. Sales order selection (program RKKBSELL)
4. G/L account balance list (program RFSSLD00)
5. General ledger line items list (program RFSOPO00)
6. compact document journal (program RFBELJ00)
7. asset history sheet (program RAGITT_ALV01)
8. Depreciation run for planned depreciation (RAHAFA_ALV01)
9. vendor sales (program RFKUML00)
10. vendor open item list (program RFKEPL00)
11. customer sales (program RFKUML00)
12. customer open item list (program RFDEPL00)
13. customer recurring entry original documents (program RFDAUB00)
14. cost centres: actual/plan/variance (transaction GR55 with report group 1SIP for CO totals)
15. Order: Actual/Plan/Variance (Transaction S_ALR_87012993)

Preparing for Migration
 Prepare the data of Financial Accounting, Controlling, and Asset Accounting for migration, immediately after in
stalling the add-on perform the activities in the Preparations and Migration of Customizing step
I. Check Customizing Settings Prior to Migration
II. Define Message Types for Posting Before and During Migration
III. Preparations and Migration of Customizing for the General Ledger
IV. Preparations and Migration of Customizing for Asset Accounting
V. Preparations and Migration of Customizing for Controlling

Migration
 Perform the Customizing activity Regenerate CDS Views and Field Mapping.
 Migration of Cost Elements and Customizing
I. Cost elements are no longer maintained separately in CO but as a special type of G/L account.. As a result of
the merge of CO and FI, you need to do the following:
II. Migrate your secondary cost elements to the chart of accounts
III. Transfer the account assignments of your cost elements to the default account assignment
IV. Adopt the authorizations, since the authorizations for cost element master data maintenance have been
superseded by the authorizations for G/L account master data maintenance
V. Check Consistency of G/L Accounts and Cost Elements -Before starting the actual migration, you need to carry
out this step to check whether the G/L accounts and cost elements are consistent with each other.
VI. Migrate Secondary Cost Elements to Chart of Accounts
VII. Migrate Default Account Assignments
VIII. Adopt Authorizations & Profiles
 Technical Check of Transaction Data
 Migration of Documents and Line Items of the Data
 Migration of Balances
 Completing the Migration
 Migration of House Bank Accounts

Activities to be Executed After the Migration
 Execute the activity Transfer Application Indexes
 Execute the activity Fill Due Dates in FI Documents.
 Execute the activity Fill the Offsetting Account in FI Documents
 Execute the activity Migrate House Bank Accounts
 Make sure that all of the balances carried forward to the current fiscal year are transferred
 Perform closing for periodic asset postings (with program RAPERB2000).
 Execute the periodic depreciation posting run (with program RAPOST2000).
 Check for update terminations in your system and correct any you find.
 Lock the periods in Financial Accounting and Controlling (Plan/Actual).
 For customers who are already using account-based profitability analysis: Perform a delta upload for all of your
account-based CO-PA Data Sources for which you use the delta method.
 Preparation for Productive Start
 Unblock all users in the system
 Open the periods in Financial Accounting and in Controlling (Plan/Actual}

BP is the Big Brother in 1511 onwards.,
 The mandatory target approach in S/4HANA is the Business Partner approach
 Business Partner is now capable of centrally managing master data for business partners, customers, and
vendors. With current development, BP is the single point of entry to create, edit, and display master data for
business partners, customers, and vendors.
 Only SAP Business Suite customer with C/V integration in place can move to SAP S/4HANA, on-premise edition
1511 (Conversion approach). It´s recommended but not mandatory that BuPa ID and Customer-ID /Vendor ID are
the same
 Material Number Field Length Extension
 SAP S/4HANA, on-premise edition 1511 can support a material number with 40 characters. The appropriate
related SAP development entities (domains, structures, table types, and transparent tables, external and internal
interfaces, user interfaces, and so on) have been adapted accordingly. Where required, automated logic is in
place and executed automatically in case a customer converts his current SAP Business Suite system into SAP
S/4HANA, on-premise edition 1511

S4 Financials Powered By HANA-Purna

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (20)

Similar to S4 Financials Powered By HANA-Purna

Similar to S4 Financials Powered By HANA-Purna (20)

More from Chandar Pokala

More from Chandar Pokala (8)

S4 Financials Powered By HANA-Purna

Editor's Notes