SAP Working Capital Analytics - Overview

SAP Working Capital Analytics
Overview
SAP Business Suite – Application Innovation
January 2014
SAP Working Capital Analytics
Overview
SAP Business Suite – Application Innovation
SAP Working Capital Analytics – Introduction
SAP Working Capital Analytics – Why Using HANA?
SAP Working Capital Analytics – HANA Model Overview
Additional Information – SAP HANA Live
SAP Working Capital Analytics
Overview
SAP Business Suite – Application Innovation
SAP Working Capital Analytics – Introduction
SAP Working Capital Analytics – Why Using HANA?
SAP Working Capital Analytics – HANA Model Overview
Additional Information – SAP HANA Live
= Current Assets – Current Liabilities
Other Liquid
Assets
Current Assets
Represents the value of all assets that are
reasonably expected to be converted into cash
within one year in the normal course of
business.
Current Assets
A measure of both a company's efficiency and
its short-term financial health.
Accounts
Receivable
Other Short
Term
Liabilities
Current Liabilities
A company's debts or obligations that are due
within one year.
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Inventory
Accounts
Payable
Current Liabilities
Cash
Working Capital
Working Capital
SAP Working Capital Analytics
Definition of Working Capital
4
SAP Working Capital Analytics
Performance Indicator Relations and Influencing Factors
Influencing Factors
Performance Indicators
Days Sales
Outstanding
(DSO)
Operating
Cycle (OC)
Cash
Conversion
Cycle (CCC)
Days Payables
Outstanding
(DPO)
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Accounts
Receivable (AR)
+
Days
Inventory Held
(DIH)
-
Net Sales
Inventory
Cost of Goods
Sold (COGS)
Accounts
Payable (AP)
5
SAP Working Capital Analytics
Performance Indicator Relations and Influencing Factors
SAP WorkingPerformance
Capital Analytics
1.0 features Web applications
and content
Influencing
Factors
Indicators
to analyze aspects relevant for
•
•
Days Sales
Outstanding
(DSO)
Days Sales Outstanding
(DSO)
Operating
Cycle (OC)
Days Payables Outstanding
(DPO)
Cash
Conversion
Cycle (CCC)
Days Payables
Outstanding
(DPO)
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Net Sales
Accounts
Receivable (AR)
+
Days
Inventory Held
(DIH)
Inventory
Cost of Goods
Sold (COGS)
Accounts
Payable (AP)
6
SAP Working Capital Analytics
Business Context
Business Context / Use Case
• In today's volatile financial markets a company’s
efficiency and financial health is more important than
ever.
• Influencing working capital is of high significance in
this context, especially in a global environment with
major regional differences, e.g. with regards to payment
terms.
• SAP Working Capital Analytics provides a new, intuitive
and easy to use way to analyze Days Sales
Outstanding (DSO), Days Payables Outstanding
(DPO) and related KPIs.
• SAP Working Capital Analytics allows users to
interactively build up flexible drill-down analysis paths
to analyze complex data on a detailed level.
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
7
SAP Working Capital Analytics
Product Overview
What’s this all about?
An analytics application that helps companies
•
analyze all aspects of days sales outstanding
and days payables outstanding
•
•
explore root causes of working capital changes
optimize strategies to improve the company’s
liquidity, efficiency and overall financial health
Key Product Features
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
•
Analytics for receivables and payables based on
real-time ERP data powered by SAP HANA
•
•
Analysis paths can be saved and reused
•
Drill-down to line item level to fine-tune tactics
regarding receivables and payables
Multidimensional drill-down opportunities to
interactively explore data
8
SAP Working Capital Analytics
Customer Value
Limitations of Competing Solutions
•
•
Key-date-dependent views on data only
•
Limited drill-down capabilities only
Loss of detail, information and precision, due
to calculations on aggregated data
Value of SAP Working Capital Analytics
Improvements in DSO-related and DPO-related
KPIs
• increase the efficiency of receivables
collections
• support better payment term negotiations with
customers and suppliers
• improve the payment behavior towards
suppliers
• increase liquidity
• give CFOs more flexibility regarding
investments, using own cash instead of loans
• improve credit ratings
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
9
SAP Working Capital Analytics
Technical Overview
Technology
• Powered by SAP HANA
• SAP HANA Live two-tier architecture
• SAP HANA views ready to use for DSO and DPO
•
•
Analytics
HTML 5 Web applications for desktop for
• DSO Analysis
• DPO Analysis
Analysis Path Framework
• Provides reusable UI elements such as
• Analysis step gallery
• Analysis path / drill-down logic
• Uses OData service requests to expose data
• Allows application adaptations by configuration
Technical Prerequisites
•
•
•
•
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
SAP Working Capital Analytics 1.0
SAP HANA Live for SAP ERP
SAP HANA 1.0 Appliance Software SPS07
SAP ERP Financials
10
SAP Working Capital Analytics
DSO Analysis
Target Roles
Analysis Area
 Corporate / regional controller
 Regional CFOs
 Country manager
 Days Sales Outstanding (DSO) /
Receivables
Business Questions
Metrics and KPIs
 How is the DSO performance of my countries ,
customers or sales organizations?
 What is the DSO / overdue DSO trend over time?
 How is the payment discipline of customers ?
 Which business partners do not pay on time?
 Which receivables are overdue and have significant
business volume?
 What is the aging structure of receivables?








DSO
Best possible DSO
Overdue DSO
Revenue
Receivables
Overdue receivables
Open receivables
Cleared receivables
Categories and Drill-Down Options
Mandatory Analysis Settings
 Company code
 Analysis time frame
 Currency
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
 Time
 Company code
 Country of company
Code
 Customer
 Country of customer
 Customer group








Sales organization
Distribution channel
Division
Sales district
Aging
Net due days
Days in arrears
Receivables
11
SAP Working Capital Analytics
DPO Analysis
Target Roles
Analysis Area
 Corporate / regional controller
 Regional CFOs / purchasers
 Country manager
 Days Payables Outstanding (DPO) /
Payables
Business Questions
Metrics and KPIs












How is the DPO performance of my countries ?
What is the DPO / overdue DPO trend over time?
How is the payment discipline towards my suppliers?
What are the countries with high expenses / a high
impact on DPO?
 Which payables are not paid on time?
 What is the aging structure of payables?
 How do payments terms (net due days) change over
time?
Mandatory Analysis Settings
 Company code
 Analysis time frame
 Currency
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
DPO
Best possible DPO
Overdue DPO
Expenses
Payables
Overdue payables
Open payables
Cleared payables
Categories and Drill-down options
 Time
 Company code
 Country of company
Code
 Vendor
 Country of vendor




Aging
Net due days
Days in arrears
Payables
12
SAP Working Capital Analytics
Overview
SAP Business Suite – Application Innovation
SAP Working Capital Analytics – Introduction
SAP Working Capital Analytics – Why Using HANA?
SAP Working Capital Analytics – HANA Model Overview
Additional Information – SAP HANA Live
SAP Working Capital Analytics
Example: Calculation Methods for DSO
Calculation: Introduction
SAP Working Capital Analytics allows analysts to calculate relevant measures based on
financial line items (referred to as direct method).
The following slides provide details about typical calculation methods in comparison to the
direct calculation based on financial line items.
The calculation methods are explained by looking at a calculation example for DSO.
The example is based on a simulation as outlined on the next slide.
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
14
SAP Working Capital Analytics
Example: Calculation Methods for DSO
Simulation Example
•
Each day a certain amount of revenue is generated.
•
Revenue always results in a corresponding accounts receivable position.
•
Customers always pay after 15 days.
 Obviously, the DSO is 15 days!
Date
01.06.2011
02.06.2011
03.06.2011
04.06.2011
05.06.2011
06.06.2011
07.06.2011
08.06.2011
09.06.2011
10.06.2011
11.06.2011
12.06.2011
13.06.2011
14.06.2011
15.06.2011
16.06.2011
17.06.2011
18.06.2011
19.06.2011
20.06.2011
21.06.2011
22.06.2011
23.06.2011
24.06.2011
25.06.2011
26.06.2011
27.06.2011
28.06.2011
29.06.2011
30.06.2011
Revenue
999,41 €
992,26 €
977,11 €
954,28 €
924,23 €
887,58 €
845,07 €
797,56 €
746,03 €
691,53 €
635,16 €
578,07 €
521,43 €
466,39 €
414,07 €
365,54 €
321,79 €
283,71 €
252,07 €
227,52 €
210,55 €
201,53 €
200,62 €
207,84 €
223,06 €
245,95 €
276,06 €
312,77 €
355,33 €
402,88 €
DSO
Clearing Date
15
15
15
15
15
15
15
15
15
15
15
15
15
15
15
15
15
15
15
15
15
15
15
15
15
15
15
15
15
15
16.06.2011
17.06.2011
18.06.2011
19.06.2011
20.06.2011
21.06.2011
22.06.2011
23.06.2011
24.06.2011
25.06.2011
26.06.2011
27.06.2011
28.06.2011
29.06.2011
30.06.2011
01.07.2011
02.07.2011
03.07.2011
04.07.2011
05.07.2011
06.07.2011
07.07.2011
08.07.2011
09.07.2011
10.07.2011
11.07.2011
12.07.2011
13.07.2011
14.07.2011
15.07.2011
Receivables
11.878,96 €
12.417,71 €
12.886,84 €
13.276,78 €
13.579,59 €
13.789,09 €
13.901,03 €
13.913,11 €
13.825,10 €
13.638,78 €
13.357,95 €
12.988,34 €
12.537,47 €
12.014,53 €
11.430,17 €
10.796,31 €
10.125,84 €
9.432,44 €
8.730,23 €
8.033,51 €
7.356,49 €
6.712,95 €
6.116,00 €
5.577,81 €
5.109,35 €
4.720,14 €
4.418,14 €
4.209,48 €
4.098,43 €
4.087,23 €
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
The graphic above illustrates how revenue and receivables are
distributed over time, assuming that positions are cleared after
15 days. .
The table shows revenue and receivables for June 2011.
15
SAP Working Capital Analytics
Indirect Calculation Method for DSO (classical)
In a first step, the “classical” DSO calculation (indirect method) is explained in more detail.
DSO Formula
Indirect Method “classical”
DSOt =
Receivablest
Revenue of last 30 days*
x 30*
* Could also be any other number of days
DSO Calculation Example
Indirect Method “classical”
Receivables as of June 30, 2011: 4.087,23 €
Revenue June 1 – June 30, 2011: 15.517,40 €
DSOt =
4.087,23 €
15.517,40 €
days
x 30
DSOt = 7,9 days
DSO variations resulting
from calculation method
Result
Although the DSO should be 15 days, we see that the ‚classical‘ approach to calculate DSO results in
considerable variations of DSO values (e.g. DSO June 03: 19,3 days/ DSO June 30: 7,9 days), depending
on when the calculation is performed. This effect even increases in case of seasonal fluctuations.
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
16
SAP Working Capital Analytics
Indirect Calculation Method for DSO (rolling avg. receivables)
The following example shows how DSO is calculated using rolling averages.
DSO Formula Indirect Method
‚Rolling avg. Receivables‘
DSOt =
Rol. Av. Receivables 12 days**
x 30*
Revenue of last 30 days*
* Could also be any other number of days
** Could also be a rolling average over other perdiod
DSO Calculation Example Indir.
Method ‚Rolling avg. Receiv.‘
Avg. Receivables June 19 – June 30, 2011: 5.764,15 €
days
Revenue June 1 – June 30, 2011: 15.517,40 €
DSOt =
5.764,15 €
15.517,40 €
x 30
DSOt = 11,1 days
DSO variations slightly decreased
Result
Using rolling averages to calculate DSO decreases variations to some degree. However, DSO values are
only approximations that are subject to certain assumptions.
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
17
SAP Working Capital Analytics
Direct Calculation Method for DSO
This slide outlines how DSO is calculated based on original documents (direct method).
DSO Formula Direct Method
Σ (CD – PD) * AR
DSOt =
Σ AR
AR = Accounts Receivable Amount
CD = Clearing Date
PD = Posting Date
DSO Calculation Example
Direct Method
Doc.1: posted June 1, cleared June 16, 2011: 999,41 €
Doc. 2: posted June 2, cleared June 17, 2011: 992,26 €
DSOt =
days
((06/16/11 – 06/01/11) * 999,41) + ((06/17/11 – 06/02/11) * 992,26)
1.991,67
DSOt = 15,0 days
True DSO, no variation
Result
A DSO calculation based on document details allows you to derive DSO values that reflect real movements
and developments without making any assumptions.
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
18
SAP Working Capital Analytics
Formulas for DSO / DPO Calculation
Formulas Provided with the Application
The following slides depict the formulas provided with SAP Working Capital
Analytics to calculate the KPIs DSO and DPO.
Important note:
By default, SAP Working Capital Analytics uses the direct calculation method
based on financial line items for DSO and DPO.
You can change the configuration so that calculations are performed using the
indirect method instead.
For more information how to switch the calculation method see the SAP
Working Capital Analytics documentation, chapter Enhancing SAP Working
Capital Analytics, available at http://help.sap.com/hba.
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
19
SAP Working Capital Analytics
DSO Definitions
DSO
Indicates the average number of days that it takes a
company to collect its outstanding accounts receivable.
Overdue DSO
Indicates the average number of days that an invoice has
been overdue.
Best Possible DSO
The DSO that can be reached if payment is always made
on the due date.
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
20
SAP Working Capital Analytics
Direct Calculation of DSO
DSO =
Overdue
=
DSO
Σ (Line Item Clearing Date – Line Item Posting Date) * Line Item Amount
Σ Line Item Amount
Σ (Line Item Clearing Date – Line Item Net Due Date) * Line Item Amount
Σ Line Item Amount
Σ (Line Item Net due Date – Line Item Posting Date) * Line Item Amount
Best Possible
=
DSO
Σ Line Item Amount
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
21
SAP Working Capital Analytics
Indirect Calculation of DSO – Calculation per Month
DSO =
Overdue
=
DSO
Best Possible
=
DSO
Average Accounts Receivable Balance of last X Months*
x 30
Average Monthly Revenues of last Y Months**
Average Overdue AR Balance of last X Months*
Average Monthly Revenues of last Y Months**
x 30
DSO – Overdue DSO
* Parameter X: can be any positive number of months (Default parameter = 1)
** Parameter Y: can be any positive number of months (Default parameter = 1)
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
22
SAP Working Capital Analytics
Indirect Calculation of DSO – Overall Calculation
Average Accounts Receivable Balance of Analysis Time Frame
DSO =
Overdue
=
DSO
Average Monthly Revenues of Analysis Time Frame
x 30
Average Overdue AR Balance of Analysis Time Frame
Average Monthly Revenues of Analysis Time Frame
x 30
Best Possible DSO = DSO – Overdue DSO
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
23
SAP Working Capital Analytics
DPO Definitions
DPO
Indicates the average number of days that it takes a
company to pay its suppliers.
Overdue DPO
Indicates the average number of days that an invoice
from a supplier has been overdue.
Best Possible DPO
The DPO that can be reached if payment is always made
on the due date.
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
24
SAP Working Capital Analytics
Direct Calculation of DPO
DPO =
Overdue
=
DPO
Σ (Line Item Clearing Date – Line Item Posting Date) * Line Item Amount
Σ Line Item Amount
Σ (Line Item Clearing Date – Line Item Net Due Date) * Line Item Amount
Best Possible
=
DPO
Σ Line Item Amount
Σ (Line Item Net due Date – Line Item Posting Date) * Line Item Amount
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Σ Line Item Amount
25
SAP Working Capital Analytics
Indirect Calculation of DPO – Calculation per Month
DPO =
Overdue
=
DPO
Average Accounts Payable Balance of last X Months*
x 30
Average Monthly Expenses of last Y Months**
Average Overdue AP Balance of last X Months*
Average Monthly Expenses of last Y Months**
x 30
Best Possible DPO = DPO – Overdue DPO
* Parameter X: can be any positive number of months (Default parameter = 1)
** Parameter Y: can be any positive number of months (Default parameter = 1)
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
26
SAP Working Capital Analytics
Indirect Calculation of DPO – Overall Calculation
Average Accounts Payable Balance of Analysis Time Frame
DPO =
Overdue =
DPO
Average Monthly Expenses of Analysis Time Frame
Average Overdue AP Balance of Analysis Time Frame
Average Monthly Expenses of Analysis Time Frame
x 30
x 30
Best Possible DPO = DPO – Overdue DPO
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
27
SAP Working Capital Analytics
Characteristics of Calculation Methods for DSO / DPO
Direct Calculation
Indirect Calculation
Calculation
Approach
Direct calculation of time span between posting
date and clearing date (true DSO / DPO) per line
item
Indirect calculation by deriving DSO/ DPO
from influencing factors
(receivables balance and revenue for DSO;
payables balance and expenses for DPO)
Calculation
Level
granular per line item
aggregated
Relevant
Documents
cleared line items
(cleared receivables/ cleared payables)
receivables/ payables:
line items posted before end of analysis time
frame and open at end of analysis time
frame
revenue/ expenses:
posted within analysis time frame
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
28
SAP Working Capital Analytics
Pros and Cons of Calculation Methods for DSO / DPO
Direct Calculation
Indirect Calculation
Pros
• More precise
• Independent from calculation effects
caused by seasonal business or big scale
transactions.
• Less affected by a high proportion of special
business transactions such as credit memos,
invoice pooling, partial payments.
Cons
Effects in case of special business
transactions:
• Unexpected effects in case of a high
proportion of credit memos.
• Lower values in case of invoice pooling or
partial payments.
• Highly key date dependent, that is, KPI
calculations are more affected by influences
and assumptions causing considerable KPI
variations with limited informative value.
• Effects can be reduced to some degree using
rolling averages.
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
29
SAP Working Capital Analytics
Overview
SAP Business Suite – Application Innovation
SAP Working Capital Analytics – Introduction
SAP Working Capital Analytics – Why Using HANA?
SAP Working Capital Analytics – HANA Model Overview
Additional Information – SAP HANA Live
SAP Working Capital Analytics
HANA Model Architecture, DSO Analysis
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
31
SAP Working Capital Analytics
HANA Model Architecture, DSO Analysis
Query Views
Reuse and Private Views
ECC Database Tables
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
32
SAP Working Capital Analytics
HANA Model Architecture, DPO Analysis
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
33
SAP Working Capital Analytics
HANA Model Architecture, DPO Analysis
Query Views
Reuse and Private Views
ECC Database Tables
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
34
SAP Working Capital Analytics
Overview
SAP Business Suite – Application Innovation
SAP Working Capital Analytics – Introduction
SAP Working Capital Analytics – Why Using HANA?
SAP Working Capital Analytics – HANA Model Overview
Additional Information – SAP HANA Live
SAP HANA Live
Unified View of Business Processes Across Organizational Functions
SAPdelivered
Query
Views
Partner Apps
New SAP Apps
SAP Business Suite
SAP
NetWeaver
BW
Multi-channel Unified User Experience
Personalized
Views
Personalized
Views
Personalized
Views
Custom-built
Open Interface
Customer Extensions
SAP NetWeaver
Reuse Views
SAP HANA PLATFORM
Application Services
Database Services
Synchronizations Services
Operational
Reporting
Private Views
Out-of-the-Box
Physical Tables
SAP HANA Live (VDM)
Instantaneous
transactions results-toactions
Unified view of
operations
without delay
Empowerment
for front-line
employees
* SAP HANA Live is a separate package for SAP Business Suite
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
36
SAP HANA Live Architecture
Foundation for new Class of Applications
HTML5-based (web & Mobile)
Other SAP Solutions
Open Interfaces: https | oData | SQL | MDX
Web
Resource
oData
Service
XS Engine
Application Services
SAPdelivered
Query
Views
Personalized
Views
Personalized
Views
Personalized
Views
Customer Extensions
Reuse Views
SAP HANA PLATFORM
Private Views
Virtual Data Model
HTTP(S),
HTML, CSS, JS, …
3rd Party
SAP BusinessObjects BI
SAP HANA Live
Physical Tables
Database Layer
Atomic data
set for detailed
drill-down
information
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Operational data
available
instantaneously
Pre-defined
models across
entire suite
37
SAP HANA Live for SAP Business Suite
Differentiation Through Real-time Business Intelligence
Open
 Access via standard interfaces, especially SQL
Real-Time Business Intelligence
 Access with any client
Uniform
 One approach for all Business Suite applications
 Analyze cross application boundaries
Intuitive
 Data models are made simple
SAP Business Suite
 Customizing dependencies are hidden
Fast
 Reporting performance powered by SAP HANA
SAP NetWeaver
 Rapid implementation times
Real-Time
SAP HANA Live
 Cycle time from recording to reporting is zero
 Built on replication or embedded
Extensible
 Adjust to industry or customer language
SAP HANA PLATFORM
 Easily enrich with non-SAP data
 Easily include customer modifications
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
38
SAP HANA Live Deployment Options
Existing Stack
Sidecar Approach
Integrated Stack
SAP Frontend
SAP Frontend
BOBJ
HTML 5
Any
frontend
SAP Business
Suite
SAP Business
Suite
HTML 5
(ERP, CRM, SCM,…)
Any
frontend
(ERP, CRM, SCM,…)
AnyDB
BOBJ
SAP HANA
Live
SAP HANA
Live
SAP HANA
SAP HANA
Replication
Customers can add new analytics capabilities immediately without disruption to their existing
landscape. Any investment today will be valid for SAP Business Suite powered by SAP HANA.
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
39
© 2014 SAP AG 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 AG 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 AG
(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 AG and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP AG or an SAP affiliate company for informational purposes only, without representation or warranty of any kind,
and SAP AG or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP AG 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 AG 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 AG’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 AG 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.
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
40