You've heard about SAP HANA, but how does it impact you? This presentation will introduce the technology and describe the new accelerators recently built allow for exciting new possibilities in SAP Controlling. This presentation covers:
1. Basic SAP HANA architecture and its relevance for Controlling users
2. The impact of SAP HANA on drill-down reporting in CO-PA and CO-PC
3. Tips for leveraging SAP HANA top-down distribution and assessment in CO-PA and on the costing run in the material ledger to reduce time-to-close
4. Options for using new Business Objects user interfaces to visualize data for different user groups
3. Topics
• Introduction
• SAP HANA – The Basics
• Profitability Analysis
• Overhead Management
• Production Cost Analysis
• Material Ledger
• SAP HANA – Next Steps
• Summary
4. SAP HANA: Breakthrough Innovation with In-Memory Computing
In-memory computing is a technology that analyzes massive quantities of data in
local memory so that the results of complex analyses and transactions are
available at your fingertips and business decisions can be executed without delay.
Benefits
• Gain Real-Time – know it when it happens
• Go Deeper – ask any question on any data
• Act Broadly – manage large volumes of data
• Run Faster – analyze at the speed of thought
• Get Flexibility – eliminate pre-fabrication requirements
5. Your Controlling Data…
• Large data volumes
• Reports require tens of thousands of
records to be read and aggregated
• Process performance
• Reports take several hours to
complete impacting close times
• Speed of analysis and reporting
• Difficult to make relevant finance
available to managers within
adequate time frame
• Poor productivity
• Laborious and time consuming
reconciliation processes at period
close
6. Big Data : What the Experts Say...
VELOCITY
Worldwide digital content will double in 18
months, and every 18 months thereafter.
IDC
Mobile
ERP Data Reports
Costs
Emails
Planning Profitability
Period-end closing
Opportunities
Speed
VOLUME VARIETY
Velocity
In 2005, mankind created 80% of enterprise data will
150 Exabyte of information. be unstructured spanning
In 2011, 1,200 Exabyte’s traditional and non--traditional
will be created. Analysis sources.
The Economist Gartner
Transactions Revenues
7. Topics
• Introduction
• SAP HANA – The Basics
• Profitability Analysis
• Overhead Management
• Production Cost Analysis
• Material Ledger
• SAP HANA – Next Steps
• Summary
8. SAP HANA – The Basics
SAP HANA is used as second
SAP UI
database to accelerate existing
applications
• SAP HANA serves as secondary
database for SAP ERP or SAP CRM
Data Modeling • Data is replicated / written into In-
Memory in real time for secondary
SAP Computing Engine storage
Business Read • User interface remains unchanged to
Suite ensure non disruptive acceleration
• Application is accelerated by reading
the data directly from the In-Memory
database
Traditional DB
Replicate
SAP HANA
9. SAP HANA – The Landscape
HANA DB is maintained as secondary DB in ERP and connected as RFC connection
ERP System HANA DB
ABAP-
Accelerated read
Program
Copy of
read
Database Table
write
Database Table
Table replication
or line-wise inserts
10. Reading from SAP HANA – An Example Data Selection
HANA DB Tables
ERP DB Tables
11. Configuration for ERP Accelerators in SAP ERP
Monitoring of and configuration for
ERP accelerators (transaction HDBC):
• Overview of available accelerators
• Central configuration of secondary DB
connection
• Activation of secondary DB for individual
applications
• By user
• By report / transaction
• Availability and status of secondary DB
• Overview of replicated tables by
accelerator scenario
12. Topics
• Introduction
• SAP HANA – The Basics
• Profitability Analysis
• Overhead Management
• Production Cost Analysis
• Material Ledger
• SAP HANA – Next Steps
• Summary
14. CO-PA Accelerator – Allocations via Reference Data
• Assessments of cost
center expenses into
CO-PA are accelerated
if receiver tracing
factor for reference
data is variable.
• In this example the
Sales Quantities per
Receiver will be read
from SAP HANA to
determine how the Transactions:
cost center expenses KEU1 (definition)
are to be allocated. KEU5 (execution)
15. CO-PA Accelerator – Top-Down Distribution
• Example: allocate overhead marketing cost to Allocate to product
products according to billing quantity per product
For any customer,
company code …
Value field as reference
base for allocation
Value field to be
allocated
Transaction KE28
16. Profitability Analysis: Customer Data
ERP w/o HANA ERP with HANA Acceleration
(production (test installation) factor vs. ERP
Hardware)
EBIT with commodity sales 280 sec 7 sec 40
– initial report (DB 2,8 sec)
EBIT with commodity sales 620 sec 5 sec 124
– drilldown by alphacode (DB 2,9 sec)
Cost allocation 45 sec 5 sec 9
– initial report (DB 3,4 sec)
Cost allocation 260 sec 7 sec 37
– drilldown by sending cost (DB 3,3 sec)
center
17. CO-PA Accelerator - How it Works
In-memory database is used as secondary database to accelerate data selection in all CO-PA processes.
Segment Level
CE3
CO-PA Interface
CE4 ERP-Reporting &
SD „Best Choice BW -Upload
FI of Source“
CE2
OM
CO-PA Read-interface
CE1
PC Line Items
Add Delta
OBJ
CRM Top-Down-
Initial Build distribution
…
Periodic
Update
K81 K81 Customer-defined
K81.1 K81.3 Aggregation
Classic DB Levels
Costcenter-
allocation
In Memory DB K81
CO-PA
Line Items
18. Topics
• Introduction
• SAP HANA – The Basics
• Profitability Analysis
• Overhead Management
• Production Cost Analysis
• Material Ledger
• SAP HANA – Next Steps
• Summary
19. Controlling Accelerator
Accelerated ERP Reporting and In-
Memory Based Partner Object
Reporting
SAP BO BI 4.0 Display Actual Cost Line Items for Cost Centers
ERP System HANA DB and Orders
Display Plan Cost Line Items for Cost Centers and
Cost Center Accounting Orders
Overhead Orders Accelerated read Accelerated overhead and accrual
calculation
Investment Programs
Line items Active Availability Control Monitor
read
write
Table replication
DB Table
20. New Line Item Browser
To leverage the speed of
HANA accelerated CO Line
Item Browsers are provided:
Cost center actual line
items KSB1N (replacing
KSB1)
Cost center plan line items
KSBPN (replacing KSBP)
Order actual line items
KOB1N (replacing KOB1)
Order plan line items
KOBPN (replacing KOBP)
21. Functions of New Line Item Report
Values are
aggregated by
shown
characteristics.
Here: Cost
Element
Direct navigation
Display single
between cost center
document
groups and cost
centers
One-click access to
predefined Layouts
22. Extended Selection Options
• The speed of HANA allows more freedom in
selection of data
• Any field in the line item can be selected, where
the old transactions would finish with a timeout
for non key fields
• New Feature: Postings by partner and source
object
• Examples:
• Show me the aggregated value of the debits my
cost centers received from the IT department
• Show me the postings to my project that were
initiated by payroll in Brazil.
23. Accelerated Overhead Calculation & Accrual Calculation
Actual Overhead Calculation: Project/WBS Element/Network CJ44
Financial Statement Plan/Actual Comparison CJ45
Runtime improvement:
Plan Overhead Calculation: Project/WBS CJ46 Programs will typically only need
Plan Overhead Calculation: Projects/WBS Elements (collectively) CJ47
half the time
Actual Overhead Calculation: Product Cost Collector CO42
Actual Overhead Calculation: Production/Process Orders CO43
Actual Overhead Calculation: Business Process CPZI
Plan Overhead Calculation: Business Process CPZP
Actual Overhead Calculation: Order KGI2 Actual Accrual Calculation for Cost Centers KSA3
Actual Overhead Calculation: Internal/maintenance orders KGI4 Calculate Cost Center Actual Accrual Costs: Initial KSA4
Plan Overhead Calculation: Internal/maintenance orders KGP4 Screen
Plan Accrual Calculation for Cost Centers KSA8
Plan Overhead Calculation: Order KGP2
Actual Overhead Calculation: Cost Object (individually) KKPZ
Actual Overhead Calculation: Cost Object (collectively) KKPJ
Runtime improvement:
Actual Overhead Calculation: Cost Centers/Activity Types KSI4
The runtime may typically
Plan Overhead Calculation: Cost Centers/Activity Types KSP4
decrease by a factor 2
Actual Overhead Calculation: Sales Orders VA44
24. Investment Programs Monitor
With this new function the speed of
HANA enables comparison of
relevant budget values and
assigned values of all orders or
WBS elements for an investment
program (or to a sub-tree of an
investment program) in real time.
25. Topics
• Introduction
• SAP HANA – The Basics
• Profitability Analysis
• Overhead Management
• Production Cost Analysis
• Material Ledger
• SAP HANA – Next Steps
• Summary
26. Production Cost Analysis
Accelerated ERP Reporting
• Accelerates all CO-PC drill-down reports
(SAP and customer specific)
SAP BO BI 4.0
ERP System HANA DB • Accelerates POWER Lists and Crystal
Reports
Production Cost Reports Accelerated read
Responsibility Reporting Responsibility Reporting on HANA
Transactional data
Master data • Cost center and activity reporting as
(for HANA-based
write
read
reporting)
additional dimension for responsibility
DB Table
Transactional reporting
data replicated via
datasource
table replication for
master data
30. Production Cost Analysis – ERP Reports
• Acceleration of drill-down reports
by reading from SAP HANA
• On-the-fly summarization means
that data collection run
(Transaction KKRV) is no longer
needed during period close
• On-the-fly summarization means
that there are no aggregate
records in the database
• Transaction KKBC_HOE will be
migrated to SAP HANA later
31. Production Cost Analysis – New Reports (1)
Product based view
• Use Business Object
Explorer for Responsibility
Reporting
• Responsibility reporting
determines the cost center
Product Ad hoc drill Cost center Sub second
based view down based view access
at which variances
occurred
• New analysis of variances
by activity type
32. Production Cost Analysis – New Reports (2)
Product based view
• Use SAP
Business
Objects
Analysis Client
for
Management
Reporting
• Drill-Down
Using Familiar
Pivot Table
33. Topics
• Introduction
• SAP HANA – The Basics
• Profitability Analysis
• Overhead Management
• Production Cost Analysis
• Material Ledger
• SAP HANA – Next Steps
• Summary
34. Material Ledger Accelerator
• Material Ledger Reporting
• Drill down Reporting for ML
• Virtual Info Provider for ML Reporting
with SAP BO BI 4.0 tools
SAP BO BI 4.0 • Accelerated Material Price Analysis
ERP System HANA DB
• Material Ledger Period End
Accelerated read
Closing
Material Ledger /
Actual Costing • Accelerated costing runs
Monthly aggregated • Accelerated BW extraction
reporting data
write
read
Closing Documents
DB Table Table replication
36. Reporting Using Virtual InfoProvider
SAP BO BI 4.0
ERP System HANA DB
Virtual InfoProvider
(incl. Authority Accelerated read
Check)
HANA DB Tables
write
read
ERP DB Tables Table replication
37. Performance Measurements for Costing Run
Selection Step:
Select CKMLPP
Select CKMLPP 54,7%
Post Closing:
Join MLHD x MLIT
x MLPP
Select MLIT
50,9%
38. Resulting Code Changes
• Replicate content of relevant tables to HANA
• Change program to read data from HANA
HANA
39. Improvements in Costing Run
Costing Run ERP w/o HANA ERP with Acceleration
(production HANA factor vs. ERP
Hardware) (test
installation)
Selection 45 minutes 10 minutes 4,5
Post Closing 75 minutes 27 minutes 2,7
40. Relevant Database Tables
Material Data:
Table Content # Fields # Keys Typical Count To be
replicated
CKMLHD Header data by material / plant 18 1 2.5 Mio -
CKMLPP Collected quantity data and status by 39 5 60 Mio yes
material and period
CKMLCR currency-dependent data by material, 56 6 120 Mio -
period and currency
ML Document Data:
Table Content # Fields # Keys Typical Count To be
replicated
MLHD Header data by material ledger document 21 1 45 Mio yes
MLIT Control data by document item 43 3 250 Mio yes
MLPP Additional Info per item 23 5 270 Mio yes
MLCR Values and quantities by Item
41. Acceleration of Selection Step
• Materials have to selected by plant and by status in CKMLPP from
millions of entries. It is difficult to achieve good performance with
the CKMLPP keys.
• When CKMLPP can be read from HANA the step can be
accelerated by a factor of 3 in a typical customer case
• There are 2 variants
• Asynchronous replication: CKMLPP will be replicated / HANA by a
designated program
• Ongoing replication via the LT replicator
• The first variant will be used as a start. In the long run he
synchronous replication makes much more sense, because
otherwise the replication step will add a new step in the period
end closing process.
To be replicated: CKMLPP
42. Acceleration of Posting Step
• Performance tests showed that the post closing step spends a
large amount of the runtime reading ML documents that were
written in the previous steps of the settlement. Join on MLIT x
MLPP x MLHD (> 50% of Runtime)
• Reading from HANA accelerated the step by a factor of 2 to 3.
To be replicated: MLHD, MLPP, MLIT
43. Topics
• Introduction
• SAP HANA – The Basics
• Profitability Analysis
• Overhead Management
• Production Cost Analysis
• Material Ledger
• SAP HANA – Next Steps
• Summary
44. Bring Side-by-Side to Suite on HANA
Side by Side SAP UI On HANA SAP UI
SAP SAP
Business Business
Read
Suite Suite
Replication
Traditional DB
DB Migration
45. In-Memory Computing for SAP Business Suite
In-Memory Benefits for SAP Business
Suite:
Productivity
Improved business processes
Performance
Reduced complexity:
OLAP and OLTP in one system
Agility:
Less code, less customizing, better
Flexibility supportability, …
46. Topics
• Introduction
• SAP HANA – The Basics
• Profitability Analysis
• Overhead Management
• Production Cost Analysis
• Material Ledger
• SAP HANA – Next Steps
• Summary
47. Resources
• Janet Salmon, Controlling with SAP – Practical Guide
• ISBN: 978-1-59229-392-6
• http://www.sap-press.com/products/Controlling-with-SAP-
%E2%80%94-Practical-Guide.html
• Vanda Reis, Actual Costing with the SAP Material Ledger
• ISBN: 978-1-59229-378-0
• http://www.sap-press.com/products/Actual-Costing-with-the-
SAP-Material-Ledger.html
• Rapid Deployment Solutions for SAP HANA
• http://www.sap.com/solutions/rapid-deployment/hana-erp-
profitability-analyis/index.epx
• http://www.sap.com/solutions/rapid-deployment/hana-erp-
financial-reporting/index.epx
47
48. Five Key Ideas
• SAP HANA provides innovation through in-memory computing
• Data is replicated from SAP ERP to SAP HANA in near real-time
• SAP ERP transactions read data from SAP HANA
• Alternatively you can use SAP Business Objects reporting
tools to display the data
• Accelerators are available for Profitability Analysis, Overhead
Management, Production Cost Analysis and the Material Ledger
• SAP plans to extend the approach to cover SAP ERP, bringing
OLAP and OLTP into a single system and optimizing where
possible
48
49. Questions
• Now:
• Ask questions now for immediate answers
• Later:
• Janet.dorothy.salmon@sap.com
Q&A
49
50. Disclaimer
SAP®, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver®, Duet®, PartnerEdge, and other SAP® products and
services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in
Germany and in several other countries all over the world. All other product and service names mentioned are the
trademarks of their respective companies. ERP Corp is neither owned nor controlled by SAP.
Notas do Editor
[Talk track:]Organizations are dealing with a “Big Data” trend characterized by increasing volumes of data from enterprise systems, mobile phones, web and social platforms, the variety of data, especially the growth of unstructured data and the velocity by which it needs to be processed and presented for business decision making on the most appropriate device. It is estimated that 4 Exabytes of unique information will be generated this year; that is more than the previous 5,000 years. Social platforms like Facebook, Google and Twitter have over 600 million users, many interacting with products and services. The total number of people, especially consumers, with access to mobile devices exceeds the number of people with access to clean drinking water. The value to an organization in addressing these business trends is enormous considering that data is a company’s most strategic asset. At the same time, the speed at which business must make relevant decisions is shrinking. What if you could take a process that takes a week and shrink it so that it only takes an hour?What if you could take an activity which takes an hour and shrink it so it only takes a second?What if every employee can plan and work with instant answers to complex questions?What if you could explore data and make decisions on data that reflects the current state of your business? (no more delays between recording and availability of data for analysis)What if you could analyze information about your each and every customers, products, suppliers, partners to gain insight into key indicators such as profitability, spend and quality?Imagine how you could use this insight to steer and guide your business processes for e.g. for new products or service offeringsToday we are going to talk about a technology that does exactly that – SAP in Memory Computing Technology(IMCT) and how IMCT will change your business.Time is …? Money, that is correct. Business today can be painfully slow. Decisions take too long AND is usually based on outdated, aggregated dataIt takes too long to get present and possible future state of information to the people who need Hence business seems to be increasingly dealing with emergencies and rationalizing outcomes rather than making confident fact-based decisionsIT is spending increasingly more of its time and budget maintaining and replicating and aggregating data into data warehouses which are designed for yesterdays questions. Hence IT realizes that in order to deal with the increased complexity and volume of data analysis it needs to figure out how it can provide fast, flexible and detail data to answer any question-SAP offers in-memory computing that delivers groundbreaking innovations in hardware and software so that massive volumes of data can be instantly and cost-effectively managed and analyzed. It enables IT to combine rapid database transactions with real-time data analytics to dramatically improve existing business processes and enable a new breed of innovative solutions.
SE16H Access tables in ERP DB and HANA DBPerform Adhoc queriesUse aggregation functionsUse JOINsCompare runtimes between ERP DB and HANA DB15 Mio items from 3 different databasetables in 2 different DBs in 2 seconds !
No change to the existing report definitionsAdditional drilldowns are now possible e.g. by customer and article (not feasible before)Drilldown performance not dependent on availability of suitable aggregation level, selection always on line item level from In-Memory DatabaseExisting ERP reports are accelerated with no changes to report definitions
EBIT: initial selection 280 seconds (or 4,5 minutes) > 7 secondsDrill down by customer and article 620 seconds (10 minutes) > 5 secondsGet rid of pre-prepared aggregation levels (less data in the data base, no work for administrator)Go deeper than could technically go before.Cost allocation by reference data (nearly a minute)Drill down (4 minute to 7 seconds)
Line items. SAP has 300 millon. In current system, select via key fields such as cost center and order, ok. Select via vendor or personnel number a disaster. SAP reconciling COEP with FI-GL via functional area – high level classification for cost of goods sold reporting.
Drill-down. KKML0 – no solution. Accelerated material price analysis - buying peanuts using them to make peanut butter.BOBJ reporting – use of virtual info provider to read data from HANA but give interface to consume in Crystal, Dashboards etcCosting run. SLA -> 8 hours to load to BW.
CKM3Reporting only possible on a single materialDrilldown to document level very slowKKML0Reporting possible for multiple materialsDrilldown to detail level is fast
What is a Virtual InfoProvider?Virtual infoproviders are BW objects which are defined in ERP via transaction RSA1 (embedded BW). The InfoProvider consists of:- InfoObjects which describe the characteristics and key figures (like data elements)- An ABAP function module which is called in ERP to read the dataInfoObjects and InfoProviders are generated via an ABAP program based on the structures of the reporting tables FCML_MATFCML_REPFCML_CCS_REPFCML_ALTFCML_PROC
CKMLHD, MLHD, MLIT and MLPP to HANA via LT Replicator (or replication program)Only (relatively) small changes in ABAP programs were needed.Only a small amount of tables need to be replicated into HANA.