1610_Finance Intro Hana 1610

Intro Session to S/4HANA Finance Purnima Prithvipathy & Ajeet Agarwal | RIG APJ November 2016

External

Disclaimer The information in this presentation is confidential and proprietary to SAP and may not be disclosed without the permission of SAP. Except for your obligation to protect confidential information, this presentation is not subject to your license agreement or any other service or subscription agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or any related document, or to develop or release any functionality mentioned therein. This presentation, or any related document and SAP's strategy and possible future developments, products and or platforms directions and functionality are all subject to change and may be changed by SAP at any time for any reason without notice. The information in this presentation is not a commitment, promise or legal obligation to deliver any material, code or functionality. This presentation is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. This presentation is for informational purposes and may not be incorporated into a contract. SAP assumes no responsibility for errors or omissions in this presentation, except if such damages were caused by SAP’s intentional or gross negligence. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

© 2016 © 2016 SAP SAP SESEororan anSAP SAP affiliate affiliatecompany. company. All rights All rights reserved. reserved.

External

2

SAP S/4HANA Finance: foundation of the digital core

Instant insight Single source of truth

Intuitive user experience insight for business users

Flexible and nondisruptive Easier to deploy and extend

Real-time accounting

End-to-end process automation

Business Networks

Instant financial analysis

Customer Experience

Digital Core

SAP HANA

Real-time treasury and cash management

Financial planning and analysis

Workforce Engagement

Real-time and predictive planning

Accounting and financial close

© 2016 SAP SE or an SAP affiliate company. All rights reserved.

SAP HANA Platform

Security

Treasury and financial risk

Finance operations

Internet of Things and Big Data

Enterprise risk and compliance

External

3

SAP S/4HANA Finance: Business Case elements for the business department

Modern User interfaces

Full transparency

10-50%

Better

Better productivity

Business Partner

Dynamic Planning and Simulation

30% shorter planning cycles

Faster Close

Improved Cashmanagement

Operational Excellence

Compliance und Risk management

2-5 Days

10%

15%

20%

Decrease of DSO

Less FTE

Less fraud

faster close


External

4

SAP S/4HANA Finance

SAP Accounting powered by SAP HANA Alternative in-memory functionality for ERP customers

SAP Cash Management powered by SAP HANA

Integrated Business Planning for Finance

New product for Group Cash Management

New capabilities and enhanced integration for ERP and BPC

Business Suite on HANA SAP HANA Platform


Aligned

Agile

Predictive

Single Source of Truth

Real time processes

Dynamic Planning and Analysis

External

5

SAP ERP, SAP S/4HANA Finance, SAP S/4HANA: different products

Finance Innovations as an Add-on to classical Logistics

FI/CO ECC 6.0, EhP 0-8

SAP S/4HANA SAP S/4HANA Finance

1503


SAP ERP

1511

1610

1605

SAP S/4HANA FINANCE

SAP ERP

Finance Innovations packaged with innovations for Logistics

SAP S/4HANA Enterprise Management

External

6

SAP S/4HANA Finance, SAP S/4HANA: minor structural differences in Finance process setup e.g.: mandatory implementation of Ÿ SAP Business Partner instead of Customer/Vendor Ÿ SAP Creditmanagement intead of Customer Credit Control (no separate license) Ÿ Material Ledger for Material valuation Ÿ Material number with 40 digits Automatically, technically converted

SAP S/4HANA SAP S/4HANA Finance

1503

SAP S/4HANA FINANCE

SAP ERP


1511

1610

1605


External

7

The way to SAP S/4HANA: via SAP S/4HANA Finance or directly

SAP S/4HANA FINANCE

SAP ERP


SAP ERP


External

8

Accounting and Financial Close New Innovation for S/4HANA Finance Add-On

> 20 3 Laggards

Universal Journal

Best-in-class

<1 Target

Accelerated Financial Close

Ÿ Ultimate single source of truth for instant insight and easy customer extensions

Ÿ Improved soft close and hard close

Ÿ ONE line item table with full detail for all applications

Ÿ Correct asset acquisition values at any time - now also for valuation areas with “special items”

Ÿ This replaces the “logical document” of release 1.0. Ÿ Secondary cost elements are now G/L accounts. Ÿ Data stored only once: no reconciliation needed by design Ÿ Reduction of memory footprint through elimination of redundancy. © 2016 SAP SE or an SAP affiliate company. All rights reserved.

Ÿ Real-time profitability by earlier derivation of market segment

Ÿ Elimination of multiple reconciliation tasks due to the universal journal Ÿ Significant speed-up of asset depreciation run

Central Finance Ÿ Real-time replication of secondary CO postings from several source systems into a central system Ÿ Document drill back to the original FI document in the source system Ÿ Replication of cost objects (production orders, product cost collectors, and internal orders) Ÿ Mapping functionality for harmonization of master data (optionally via MDG solution) Ÿ Centralized error handling with the error correction and suspense tool External

9

Challenges of the Current Architecture Multiple Sources of Truth

Challenges Ø The combined content of several tables represents “the truth” in SAP ERP. Reconciliation efforts are required by design. Ø Need “to move” data to the appropriate table for reporting (e.g. “settlement”) Ø Different level of detail stored in the respective components/tables Ø Components are structured differently (e.g. fields/entities differ) Ø Different capabilities in the components (customer fields, currencies, multi-GAAP etc.)

Reconciliation

Ø Performance often required the usage of a data warehouse introducing another redundant repository. Ø Multiple BW extractors needed to cover the complete truth in data warehouse.

Business Warehouse


External

10

List of Tables Replaced by Compatibility Views


External

11

Universal Journal Single Source of Truth

New Architecture ØConcept: “Take the best of all worlds” (e.g. ledger, market segment, coding block, etc.) ØOne line item table with full detail for all applications - for instant insight & easy extensibility ØThis replaces the “logical document” of SAP Accounting 1.0. ØData stored only once: no more reconciliation needed - by design ØReduction of memory footprint through elimination of redundancy. ØFast multi-dimensional reporting possible without replicating data to business warehouse (BW).

A universal journal entry can have (technically) up to 999,999 line items à less or no need for summarization (depending on data volume)


ØIf BW is in place anyway, only one single extractor needed. ØSecondary cost elements are now G/L accounts. External

12

SAP S/4HANA: Universal Journal

All Value flows in one single source Ÿ Multi-dimensional GL

SAP S/4HANA

1511

1610

SAP S/4HANA Finance

1503

1605

Ÿ Parallel Ledger

SAP S/4HANA

1511

1610

SAP S/4HANA Finance

1503

1605

Ÿ Custom defined fields

SAP S/4HANA

1511

1610

SAP S/4HANA Finance

1503

1605

SAP S/4HANA

1511

1610

SAP S/4HANA Finance

1503

1605

SAP S/4HANA

1511

1610

SAP S/4HANA Finance

1503

1605

Ÿ Unified, extensible currencies

SAP S/4HANA

1511

1610

SAP S/4HANA Finance

1503

1605

Ÿ Consistent parallel valuation (Transfer Prices)

SAP S/4HANA

1511

1610

SAP S/4HANA Finance

1503

1605

Ÿ Soft Close and Prediction

SAP S/4HANA

1511

1610

SAP S/4HANA Finance

1503

1605

Ÿ Extension Ledger Ÿ 999.999 line items


External

13

SAP S/4HANA: Universal Journal

Classic GL in SAP ERP

Migrate to New GL

Universal Journal

Parallel Ledgers Document Split

Parallel Ledgers Document Split

Classic GL in SAP ERP

Subsequent Introduction

Universal Journal

Parallel Ledgers* Document Split**

*

SAP S/4HANA

1511

1610

SAP S/4HANA Finance

1503

1605

planned for SP5

** planned for 1709 © 2016 SAP SE or an SAP affiliate company. All rights reserved.

Document Split = Online Document Split External

14

SAP S/4HANA

1511

1610

SAP S/4HANA Finance

1503

1605

LoB Finance Subsequent Implementation of Non-leading Ledger for add. accounting principles •

Guided Implementation of new accounting principles via further ledgers and depreciation areas

•

Flexible data transfer from a source ledger into new ledgers including opening balances, open items and documents of current fiscal year

•

Correct and consistent accounting data ensured with every data transfer step

•

Automatically enhance asset master data towards new valuation

•

Easy handling using Migration Cockpit

This is the current state of planning and may be changed by SAP at any time. © 2016 SAP SE or an SAP affiliate company. All rights reserved.

External

15

Multi-Currency in the Universal Journal Up to 10 Parallel Currencies per Ledger SAP ERP Ÿ 3 local currencies in FI (including NewGL) Ÿ 2 currencies in CO Ÿ 3 currencies in Material Ledger

Universal Journal (ACDOCA)

FI (BSEG)

local Crcy

2nd local Crcy

CO (COEP)

local (Obj) Crcy

CO Area Crcy

ML

local Crcy

2nd ML Crcy

Local Crcy

Global Crcy

1st free Crcy

2nd free Crcy

SAP S/4HANA Finance

3rd free Crcy

SAP S/4HANA

1511

1610

SAP S/4HANA Finance

1503

1605

3rd local Crcy

3rd ML Crcy

4th free Crcy

5th free Crcy

6th free Crcy

7th free Crcy

8th free Crcy

ledger-dependent

Ÿ Local currency: ACDOCA field name = HSL, currency type 10 Ÿ Global currency: ACDOCA field name = KSL, currency type of controlling area Ÿ Freely Defined Currencies 1 – 8 – You can configure any currency type. – There is no dependency on the currency types of the leading ledger. – ACDOCA fieldnames OSL, VSL, BSL, CSL, DSL, ESL, FSL, GSL Ÿ If you activate parallel valuations with transfer prices, then additional rules / constraints apply.


External

16

Unified Master Data Maintenance for GL Account and Cost Element – Account Type


External

17

Convergence of G/L Accounts and Cost Elements

Master Data Ÿ Ÿ Ÿ Ÿ Ÿ

All cost elements are now G/L accounts. Differentiation by attribute “account type” in the G/L account master. Secondary cost elements are blocked against manual postings. Maintenance of cost elements is done via G/L account maintenance. The old cost element table is updated in the background.

Hierarchies Ÿ Secondary cost elements need to be added to the account hierarchy (FS stmt. version) Ÿ Management accounting continues to work with cost element groups, currently. Ÿ As a consequence, hierarchies need to be also maintained in CO for the moment.

Multiple account assignments Ÿ These are possible (e.g. cost element by internal order and cost center). Ÿ There is one primary account assignment per cost element which is relevant for subsequent processes.


External

18

Extension Ledger – Use Cases

Universal Journal

Extension Ledger A

Extension Ledger B

“Post into closed periods for restatement purposes”

“Distribute revenues differently on org units than in legal view”

Extension Ledger C “Adjustments for consolidation purposes”

Ledger IFRS Ledger Local GAAP


§ An extension ledger stores delta values and points to another ledger – thus providing a flexible mechanism for adjustments and reporting. § An important use case is for management views on top of legal data. § Besides creating a master record, extension ledgers need no additional configuration. § Reporting on the extension ledger always includes the data of the base ledger (in the figure: IFRS ledger). § Multiple extension ledgers can point to the same base ledger. § Benefit of reduced data footprint and zero reconciliation effort as only delta values are kept. § Extension ledgers are stored in the universal journal – same as “normal” ledgers. nThe concept was introduced wit sFin 1.0 as appendix ledgers. Currently only manual postings to extension ledgers are supported. Further enhancements are expected

External

19

Ledgers in SAP Accounting

Basic Principles – Changes

n

One Ledger (0L) assigned to all Company Codes delivered as Leading Ledger

n

Contains full set of line items in ACDOCA.

n

Basis for Actual CO data

n

Create management view on top of a legal ledger, especially caused by the posting period restrictions related to FI and CO union

n

extension ledger contains only adjustment postings. In reporting extension ledger inherits postings of base ledger.

n

Additional Non Leading Standard Ledgers can be assigned to selected Company Codes, contain full set of line items in ACDOCA,inherits currency configuration of Leading Ledger


External

20

Significantly Reduced Reconciliation Effort What § Obsolete – Reconciliation of multiple ledgers ** § Obsolete – Reconciliation Ledger ** § Obsolete – Reconciliation of totals vs. line items § Obsolete – Reconciliation of OLTP and OLAP § Drastically simplified – FI versus CO § Drastically simplified – FI versus CO-PA * * for account-based CO-PA and primary cost elements ** already available with New GL in SAP ERP


Why § because redundancy has been eliminated § due to real-time integration from CO to FI § because totals are dropped § due to real-time analytics on OLTP § due to 1:1 link on line item level § due to link to CO-PA characteristics table

è Faster financial close and lower costs

External

21

SAP Accounting powered by SAP HANA Fixed Asset Accounting integrated in Universal Journal Entry

Fixed Asset Accounting based on Universal Journal. n No

redundancy in data storage

n Reconciliation

o o

between G/L and AA is ensured by design

Local GAAP US GAAP xxx xxx xxx IFRS

No reconciliation-step in financial close needed anymore. All non-statistical items are updated as Universal Journal Entries.

n Even

after migration, reporting for previous fiscal years is possible due to compatibility views.

n Transparent n Depreciation

assignment of depreciation area to accounting principle posted with all details: Accumulated depreciation and depreciation cost by asset


External

22

New architecture in FI-AA - Overview From Operational Entry to multiple accounting-principle-specific Parallel Documents (Integrated Asset Acquisition)

Rules: §

Operational Entry Document posts to technical clearing account.

§

Operational Entry Document never updates the asset, asset is used for checks only

§

The entry document triggers the creation of (1 to n) accounting principle specific documents.

§

The accounting principle specific documents § §

clear the technical clearing account in each view (balance zero) post to the asset reconciliation account and update the asset subledger


External

23

Integrated Acquisition with ledger approach to parallel valuation (different amounts to be capitalized due to accounting principle) (1) Document Entry: 31 K Vendor

160000 (Payable)

70 A Asset

FIAA-1000-0

Financial Accountant

10.200 PRCTR1

KOSTL1

LGAAP

Freight costs are not capitalized in the local GAAP (New Transaction: Post only to

40 S GL

4xxxxxx (freight expense)

200

accounting principle LGAAP)

75 A Asset

13000 (Machines)

PRCTR1

KOSTL1

Generated documents:


External

24

Fiori Applications – Asset Master List Asset Master List Cockpit § Define a list of fixed Asset you are responsible for and save as a tile to your launch pad § Monitor all incomplete, in process, capitalised or retired assets as needed § Display the number of incomplete Assets already in the launch pad § Download selected lists or items, share them via e-mail list or e-mail link


External

26

Key innovations

BEL NR

DOC LN

G/L Account

Amount

ACCASTY (Cost Collector Type)

OBJ.NR.

WBSElement

Sales Order

PAOBJNR (Profitability Segment)

Customer

Product (MATNR_PA)

Prod. group

Customer specific field

1

1

Expenses

4000 €

WBS element

PR1

WBS1

1

E1

customer1

P-100

PG1

21

General ledger part

CO with definition of real account assignment

Profitability characteristics - a fixed set is provided by SAP and can be enhanced with customer specific fields

Reporting The Universal Journal allows you to explore organizational, customer, or product profitability in the same report used for financial reporting, based on any available dimension that has been posted to. In financial reports such as the income statement, it is possible to analyze revenue as well as costs by different profitability characteristics. In addition, manufacturing enterprises can review multilevel cross-margin analyses in their income statement.

Account-based profitability analysis Account-based CO-PA lays the foundation for Profitability Analysis in the Universal Journal. We have reused the profitability master data definition: the operating concern and the definition of the characteristics, the posting logic on the profitability segment, and the powerful derivation tool. These functionalities remain unchanged so that customers can keep their logic as before.

June 2016 - S/4HANA Finance Pre-Study:


27

External

27

Enhancements of Profitability Analysis

Account-Based CO-PA Ÿ Split of cost-of-goods-sold posting on multiple accounts (by cost component) Ÿ Split of production variance posting on multiple accounts (differentiation of price / quantity effects) Ÿ Three new quantity fields in CO line items + BAdI for conversion of logistic quantities to common quantities (e.g. products sold in different box sizes – but KPI in Finance is calculated on tons/KG of products) Ÿ It is planned to further enhance account-based CO-PA.

Costing-Based CO-PA Ÿ Product continues to exist and be supported, but no enhancements with SAP Accounting. Ÿ Customers can run account-based and costing-based CO-PA in parallel. Ÿ Customers should assess their valuation in FI versus valuation in costing-based CO-PA – If different, continue using costing-based CO-PA – If the same, customer may consider switching to account-based CO-PA.


External

28

Account-based vs Costing-based CO-PA Account-based Report line

Costing-based

Account

Value

Revenue

800000

€ 1.250.850

Rebates

880000

€ 175.258

Net revenue Material consumption Purchased Goods

€ 1.075.592 450001 Material

450000

€ 524.023

450002 Activities. var. € 127.668

Value field

Revenue

VV001

€ 1.250.850

Pomotion rebate

VV020

€ 58.668

Customer rebate

VV021

€ 36.558

Material rebate

VV022

€ 80.032

Provision (calculatory)

VV030

€ 52.326

€ 675.269

Net revenue

€ 1.023.266

450003 Activities. Fix € 23.578

451000

Gross profit % of net revenue Overhead Costs

Report line

650000

Net profit

€ 88.964 € 311.359 28,95% € 124.687 € 186.672

Profitability analysis in SAPanalysis ERP (EHP7) Account-based profitability with SAP S/4HANA Finance © 2016 SAP SE or an SAP affiliate company. All rights reserved.

Raw materials

VV100

€ 524.023

Production activities (variable)

VV110

€ 127.668

Production activities (fix)

VV111

€ 23.578

Purchased goods

VV112

€ 88.964

Gross profit

€ 259.033

% of net revenue

25,31%

Sales cost

VV201

€ 42.487

R&D cost

VV202

€ 59.674

Finance & admin cost

VV203

€ 22.526

Net profit

•

Account-based CO-PA and Costing-based CO-PA share the definition of characteristics (e.g. customer group, product group, region etc.)

•

Account-based only uses values per account as it is posted into P&L

•

Costing-based collects, derives and calculates values per value field

•

Costing-base uses also events and sources that doesn‘t post into P&L

€ 134.346 External

29

Account-Based CO-PA – A Reminder (2) Account-based CO-PA involves extending the primary cost element for revenue and sales deductions by the relevant profitability segment. Any allocation will also update the relevant profitability segments. It is up to you how deep you go – either remaining e.g. at distribution channel or division or going down to the product or customer.


External

30

Where Customers still need Costing-based CO-PA Costing-based Use Cases that still call for the use of costing based profitability analysis: Ÿ Adding estimated costs to specific sales transactions, e.g. freight, commissions (which are not yet posted in GL) Ÿ Assigning multiple cost estimates (e.g. a group view or sales view) Ÿ Statistical conditions shall be taken into account Ÿ Having defined own record types (record types in account based are only B, F, C, D) Ÿ Fields are contained which are normally foreign to accounting (parallel quantity recording only per BADI) Ÿ Building a parallel valuation in CO-PA

Report line

Value field

Revenue

VV001

€ 1.250.850

Pomotion rebate

VV020

€ 58.668

Customer rebate

VV021

€ 36.558

Material rebate

VV022

€ 80.032

Provision (calculatory)

VV030

€ 52.326

Net revenue

€ 1.023.266

Raw materials

VV100

€ 524.023

Production activities (variable)

VV110

€ 127.668

Production activities (fix)

VV111

€ 23.578

Purchased goods

VV112

€ 88.964

Gross profit

€ 259.033

% of net revenue

25,31%

Sales cost

VV201

€ 42.487

R&D cost

VV202

€ 59.674

Finance & admin cost

VV203

€ 22.526

Net profit


€ 134.346

External

31

New Material Valuation in Detail

Material Ledger (ML) is the standard tool used for material valuation in S/4HANA §

ML enables the support of parallel valuations (multiple currencies)

§

ML is base for optional available improved valuation methods (actual costing)

§

Following material valuation methods are supported: standard price, moving average price, actual price based on actual costing

The new material valuation ensures improved throughput scalability §

for standard price valuation shared SAP enqueue locks are used instead of exclusive ones à enables the application to process goods movements in parallel

Redundancies in data model for inventory valuation are eliminated §

material inventory values are only stored in Material Ledger tables à classic business suite stores inventory values in local currency twice: in ML and material master tables

§

valuated material postings (FIN postings) are only stored in the unified journal entry (ACDOCA)

§

compatibility views ensure that read access still works (for the classical tables of ML and material master)


External

32

Material Ledger in S/4HANA Details Material Ledger (ML) in classic ERP §

Option 1: parallel currencies

§

Option 2: actual costing

Material Ledger (ML) in S/4HANA §

parallel currencies will always be active (Option 1) à the material master can show up to 3 parallel material prices and the according inventory values

§

the material ledger tables are used to store material prices and inventory values

§

actual costing can be activated if actual material costs shall be calculated (Option 2)


External

33

Material Valuation Methods S/4HANA Supports All Valuation Methods Standard Price (S-Price) • With S/4HANA standard price valuation for materials will work as before • The throughput for standard price materials will be improved as there will be no application locks any longer (parallel updates are supported)

Moving Average Price (V-Price) • With S/4HANA there will be no changes for the calculation of the moving average price • For materials with price control “moving average” application locks are still required to ensure continuous consistency of inventory valuation, therefore there will be no throughput improvements for moving average materials

Actual Costing, Periodic Unit Price (PU-Price) • To enable inventory valuation at actual costs and improved throughputs, customers can use Actual Costing (based on Material Ledger) instead of using a moving average price


External

34

Material Ledger Manages Material Valuation

Inventory valuation is done in the material ledger application, and no longer in materials management Principle of One •

Valuation data storage in ML tables instead of material master accounting view

•

Historic data (in MBEW, MBEWH etc.) are read via compatibility views.

•

Multi-currency

•

Main valuation methods: Standard price and Moving Average price. Will be preserved and moved to ML storage by migration program.

•

The statistical moving average price for standard-price materials will no longer be calculated

•

Material Ledger periodic unit price with multi-level price determination as additional offering. To be activated separately

•

Valuation methods per different accounting principles like GAAP achieved by Alternative Valuation Run


External

35

Material Inventory Reports (S4/HANA) Balance Summary, Line Items

The new material valuation provides improved reporting capabilities §

Reporting is no longer based on material ledger tables which only know material relevant data and cannot provide insights into financial dimensions (e.g. no information like profit center, functional area)

§

The new reporting based on the unified journal entry combines material and financial data (see below)


External

36

Types of Material Ledger

Multiple Valuations – Price Determination 2 Prices and values shown in material master are selected from universal journal (ACDOCA) Multilevel Actual Costing – Price Determinaton 3 No change – Costing run needed to update inventory values at period close


External

37

Material Price Analysis Material Price Analysis (CKM3) is widely used to analyze all factors contributing to the cost of a material. Material Price Analysis initially displays data from aggregated data sets (MLCD) and then drills down to the document level (MLIT, MLPP) You can switch between valuations and currencies and navigate between periods in this view. In S/4HANA Data are read from the universal journal.


External

38

SAP S/4HANA

1511

1610

SAP S/4HANA Finance

1503

1605

LoB Finance Parallel Valuation: Transfer Pricing: Legal, Group and Profit-Center Valuation

Multi-national groups need to report profitability for the group in total and for the individual units based on the operational flows. Up to three parallel valuation methods for legal, group and profit center valuation provide different perspectives on the value chain within a group. Ÿ Legal perspective looks at the transactions from the point of view of the affiliated companies including markups Ÿ Group valuation looks at the whole group eliminating markups (i.e. intercompany profits) Ÿ Profit center valuation treats profit centers as if they were independent companies, using negotiated prices SAP ERP provided those 3 perspectives, but the solution had significant short-comings Ÿ Heterogeneous approaches across applications, high complexity, difficult to understand Ÿ No clear separation of management valuations, insufficient currency flexibility

SAP S/4HANA Finance, OP 1605 now delivers these capabilities, but with a much more streamlined, consistent approach in the universal journal. In earlier releases of SAP S/4HANA and SAP S/4HANA Finance only legal valuation was supported.

This is the current state of planning and may be changed by SAP at any time. © 2016 SAP SE or an SAP affiliate company. All rights reserved.

External

39

End-to-End Treasury and Risk Management Treasury Solution Map

Payments and Bank Communications

Payment Operations

Cash and Liquidity Management

Electronic Bank Statements

Front Office Deal capture

Debt and Investment Management

Financial Risk Management

Suite Capabilities

Workflow and Signatures

Cloud

Foundation

Cash Position

Mid Office Risk Controlling

Risk Identification Type and Origin of Risk

Shared Service Center

Monitoring and Status Payment Factory Tracking

HANA Platform

Bank Account Management*

Back Office Correspondence & Settlement

Risk Quantification Exposure Mgmt

Working Capital Management

Liquidity Management

Risk Analysis

Governance Risk and Compliance

Analytics

Bank and SWIFT Connectivity

Accounting

Risk Management Hedge with Financial Instruments

Commodity Risk Management

Mobile

Rapid Deployment Solutions (RDS)

SAP Cash Management powered by SAP HANA © 2016 SAP SE or an SAP affiliate company. All rights reserved.

External

40

SAP Cash Management Enhanced Functionality

SAP S/4HANA

1511

1610

SAP S/4HANA Finance

1503

1605

Cash Position Details § Multiple day view in one page § More dimensions (planning level, G/L account, summarization term, planning group) § Allow end user to personalize the layout for analysis § Simplify the backend for better performance

Bank Account Management § Improved usability for countries only using IBAN § Configuration to split mass change signatory request per country/per account type § Easier configuration of field status group

Liquidity Management § Pre-configured app “Liquidity Forecast Detail”

One Exposure § Integration to MM and SD © 2016 SAP SE or an SAP affiliate company. All rights reserved.

External

41

SAP S/4HANA: Planning SAP Business Objects Planning and Consolidation for S/4HANA

SAP S/4HANA

1511

1610

SAP S/4HANA Finance

1503

1605

Planning, Budgeting, Forecasting entirely integrated, while remaining flexible: Ÿ Direct access to all data (actuals, master data)

ACDOCP

Ÿ Flexible planning Level, Periods, preliminary master data, Workflow, comments, Excel-Frontend

ACDOCA

Ÿ Simulation, Scenarios

“Planning is coming home”


External

42

SAP S/4HANA: Consolidation SAP Business Objects Planning and Consolidation for S/4HANA

SAP S/4HANA

1511

1610

SAP S/4HANA Finance

1503

1605

Legal and statutory Consolidation: Ÿ Direct access to all data (actuals and master data) Ÿ Real-time Consolidation: facilitate process steps (data acquisition, validation, intercompany)

ACDOCC

Ÿ Simulation, Scenarios = heading for „Continuous Accounting“ from entity to group close


ACDOCA

External

43


External

44

Roadmap and Information Roadmap Adoption SAP Market Introduction HCP Apps for Finance Transition paths Central Finance Conversion Simplification List

Roadmap and links

www.sap.com/roadmaps à Line of Business à Finance à Solutions/Products à Cross topics à SAP Fiori

http://help.sap.com

à Financial Management à SAP S/4HANA Finance

http://help.sap.com

à Enterprise Management à SAP S/4HANA (z.B. Simplification List, Compatibility Packs)


External

46

Strong customer adoption of SAP S/4HANA (Finance) (as of October 24th., 2016)

1.433 309

Active customer projects Live customers 25 industries All regions New implementations and conversions


External

47

Thank you

Purnima Prithvipathy & Ajeet Agarwal Regional Implementation Group | APJ E: [email protected] / [email protected]


© 2016 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.


External

49

1610_Finance Intro Hana 1610

Recommend Documents