session title - sap fico training | sap consulting | sap ... 5 r 150 g 140 b 140 r 213 g 209 b 209 r...
TRANSCRIPT
9/8/2015
1
© 2015 ERP Corp. All rights reserved.
New Options For Implementing
SAP BPC Using Shared Master
Data and Real-Time Transaction
Data
David Dixon
TruQua Enterprises, LLC
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
Introduction
• We are at a historic inflection point impacting fundamental
design principles behind transactional applications (e.g., SAP
ERP), data warehousing (e.g., SAP BW) and analytic
applications (e.g., SAP BPC)
• This session explores those impacts on SAP BPC
3
Thesis
Problem Reaction
Antithesis Synthesis (New Thesis)
Solution
HANA
OLAP
OLTP
OLTP
The Hegelian DialecticSource: TruQua
9/8/2015
2
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
Topics
• Current Integration Challenges with SAP BPC
• New Design Options for Real-Time and Shared Data
• Implementation Considerations
• Summary
4
Start of first section:
List the main points in your presentation and insert this slide at
the start of each new topic. Move the highlighted box down for
each new section. This divides your presentation into easy to
follow sections.
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
SAP BPC Data Integration Example
5
• SAP data travels through multiple layers requiring translation
into different formats and conventions along the way
• The below example is a Financial Planning RDS on BI Content
Source: SAP
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
SAP BPC Within Layered Scalable Architecture (LSA)
6
• LSA is SAP’s
reference
architecture and
design principles
for data
warehousing
• SAP BPC adds
another layer for
data integration
whether in
separate or
shared instances
Source: Modified from SAP
9/8/2015
3
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
LSA Impact to Business Value
7
• Time is Money
• Data Latency
• System
Performance
• Reconciliation
• Effective
models, tools
and analytics
Source: Adapted from Hackathorn, Richard. “Current Practices in
Active Data Warehousing.” Boulder Technology, (Nov. 2002)
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
What SAP ERP Totals Data Looks Like
8
• ERP financial reporting
has intelligence for:
• Four currencies and
one unit of measure
per ledger stored in
columns
• Handling of periodic
and year-to-date views
• Special fiscal variant
intelligence for 17
periods
• Documents store debits and credits in the same columns as a
positive amount with a debit/credit indicator
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
Mapping SAP ERP Data to SAP BW
9
• 0DEBIT and 0CREDIT stores positive periodic totals while
0BALANCE stores cumulative totals as a snapshot amount
• 0CURRENCY stores the transaction currency key and
0CURTYPE represents if an amount is transaction, local, group,
or some other ledger currency
• The time dimension has fiscal year variant intelligence
9/8/2015
4
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
Mapping SAP BW Data to SAP BPC
10
• Generally 2 types of currencies: “LC” for local and reporting
currency (no explicit support for transaction currency)
• Time has no fiscal year variant and can be defined as a
hierarchy (no explicit period 0 and 4 special periods support)
• Measures have account signage and periodic versus year-to-
date intelligence Note: SAP BPC
10.1 “Embedded
Models”
are more consistent
with SAP BW
formats than
“Standard Models”
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
Key Figures in Rows Instead of Columns
11
• Single key figure in model
• Calculations in the
account dimension
• Compare to costing and
account-based CO-PA
• How to data model?
• Key figures?
• Units of measures?
• Aggregation behaviors for
cumulative and non-
cumulatives?
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
0ACCOUNT Period 0 Period 1 Period 2 … Period 12 Period 13 … Period 16 Currency Currency type
Cash 1000 200 -300 … 400 500 … EUR 20
Loans -10000 0 -2000 … 0 0 … 300 EUR 20
Period Headcount Unit
1 200 EA
5 40 EA
9 -20 EA
Account Time Signdata RPTCurrency
Cash 2009.Jan 1200 LCCash 2009.Feb -300 LC… … … …Cash 2009.Dec 900 LCLoans 2009.Jan 10000 LCLoans 2009.Feb 2000 LC… … …Loans 2009.Dec -300 LCHeadcount 2009.Jan 200 EAHeadcount 2009.Feb 200 EA… … …Headcount 2009.May 240 EA… … … …Headcount 2009. Nov 220 EAHeadcount 2009.Dec 220 EA
Note:
Currencies are recognizably
different
Account signage is different
Non-cumulative key figures are
posted differently
Period 0, 13-16 are handled
differently
SAP BW Cumulative Key Figures
SAP BW Non-Cumulative Key Figures
SAP BPC Signed Data
SAP BW and SAP BPC Data Differences In Review
Source: Jens Koerner12
9/8/2015
5
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
Reformatting Master Data
13
• SAP BPC Standard has its
own master data conventions
impacting the chart of
accounts:
• Period accounting versus
cost-of-sales
• Mapping function area
• Mapping statistical key
figures
• Mapping activities or
“drivers”
• Modeling hierarchies instead
of master data attributes
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
SAP Term SAP ERP Field SAP BW InfoObject SAP BPC Dimension
Company Code
(Legal Entity)
BUKRS 0COMP_CODE ENTITY
G/L Account HKONT 0GLACCOUNT ACCOUNT
Transaction Type (B/S
Movements)
BEWAR/RMVCT 0MOVE_TYPE FLOW
(Sub tables)
Trading Partner RASSC 0PCOMPANY INTERCOMPANY
Cost Center KOSTL 0COSTCENTER USER DEFINED
Profit Center PRCTR 0PROFIT_CTR USER DEFINED
Meta Data Mapping SAP ERP, SAP BW and SAP BPC
• Note that semantic modeling and mapping does not entirely go
away with HANA and SAP Simple Finance
14
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
Integrating FI and CO concepts
15
• Different fundamental design principles across Financial
Accounting (FI) and Controlling (CO) and BPC
• Key design decisions need to made with respect to modeling
and mappings
SAP BPC Controlling (CO) Integration (Both) Financial (FI)
Entity Type
Dimension
Cost Objects/Profit Centers
Functional area
Company codes/
Business areas/
SegmentsAccount Type
Dimension
Primary cost elements
GL Account
Account Type
Dimension
Secondary cost elements N/A N/A
Account Type
Dimension
Statistical key figures N/A N/A
User-Defined Activity Types N/A N/A
9/8/2015
6
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
Technical Master Data Conventions
16
• In evaluating the SAP BPC numbering schemes for master data,
it is important to note that in SAP BPC, there is no:
• “Compounding” or “primary key” definition, as there is in
SAP NetWeaver BW and SAP ERP
• Time or version dependencies
• SAP BPC member IDs have up to 32 alphanumeric characters
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
Cost Center Master Data Integration Example
17
• Key considerations – Cost
center master data:
• Is always
“compounded”
(BW term) with a
controlling area
• Has alternate hierarchies
in addition to the
standard one
• Is time-dependent
• Maps to company codes,
business areas,
functional areas, and
profit centers
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
SAP BPC Technical Mapping Conventions
18
1. Map cost center one-to-one with dimension member
• Assumes only one global controlling area
2. Concatenate controlling area with cost center into dimension
member
• Flexibly supports multiple controlling areas
• Other considerations
• Add a prefix (e.g., “CC_”) to keep master data uniqueness
across dimensions
• Strip leading zeros?
• Note that hierarchy nodes have controlling area in the ID
• Considerations and options are the same for cost elements and
activity types
9/8/2015
7
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
Key SAP BPC Data Modeling Questions
19
• How to model internal orders with cost centers?
• Do I take a cost object approach?
• How do I take into account statistical postings?
• Do I model statistical key figures in the account dimension?
• Are activity types in the same model or separate?
• If separate, what are the integration implications?
• How should I model profit center vis-à-vis cost center?
• Should I take into account partner (sender) cost objects?
• How should units of measure and currency keys be modeled?
• Special modeling considerations for allocations?
• Hint: “Yes” for data selections, senders and auditing
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
Topics
• Current Integration Challenges with SAP BPC
• New Design Options for Real-Time and Shared Data
• Implementation Considerations
• Summary
20
Start of second section:
List the main points in your presentation and insert
this slide at the start of each new topic. Move the
highlighted box down for each new section. This
divides your presentation into easy to follow
sections.
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
Bringing Analytics Back Into SAP ERP
21
• The need for shared master data, single source-of-truth and
real-time insight has always been needed but now truly possible
with SAP HANA (first shipped in 2010)
Source: SAP, 2008
9/8/2015
8
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
SAP Simple Finance Single Source of Truth
22
• One physical table for processing and analytics
• Essentially one table for actuals: ACDOCA
• Plan data stored within SAP BW Real-Time InfoCubes
• “Back-to-the-future” with a simplified coding block concept
• “Out-of-the-box” data integration within SAP Financials as part
of SAP Simple Finance reducing reconciliation effort
• The work of financial data integration shifted to migration
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
SAP Simple Finance 1503 Migration Considerations
23
• Data integration via migration to SAP Simple Finance 1503
Controlling
Financial Accounting
Asset Accounting Material Ledger
SAP Simple Finance 1503
Source: Modified from SAP
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
How Profitability Analysis Gets Integrated
24
• Line item linking general ledger line items with account-based
CO-PA (Controlling - Profitability Analysis) becomes the key
part of the Universal Journal integrated design going forward
Source: SAP
9/8/2015
9
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
Technical Prerequisites for SAP Simple Finance 1503
25
• Essentially SAP ECC 6.0 EHP 7 on HANA with HANA Live 2.0
• Not all SAP ERP 6.0 enterprise extensions, industry solutions,
or SAP ERP 6.0 add-ons are supported
• See SAP Notes 2119188 and 2103558
Source: SAP
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
How SAP BPC Was Integrated Into SAP Simple Finance
26
• The new product “Integrated Business Planning for Finance” is
SAP BPC pre-delivered content in SAP Simple Finance
HANA
SEM
BW-BPS
SEM-BCS
BW-IP
Outlooksoft BPC MS
5.1
BPC MS
7.x
BPC NW 7.x
BOBJ
Cartesis
BPC MS 10.0
BPC NW 10.0
(Extended Analytics Analyzer
influence on the EPM Add-
In)
Renovated
Planning
2005 2010 2015
(BPS and
BCS)
10.1 NW Standard
10.1 NW Embedded
IBP for
finance
BOBJ FC
10.1 MS
ERP C4P
© TruQua. All Rights Reserved.
Source: TruQua
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
• HTML5 Web Interface
• Work Status
• Business Process FlowsBPC
• VirtualProviders and Multi-Providers
• Reusable and extensible BI ContentBW
• Extensible HANA views on SAP ERP tables
• HANA-enabled planning and analysisHANA
Three Ways the Solution Integrates With Simple Finance
27
9/8/2015
10
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
• HTML5 Web Interface
• Work Status
• Business Process FlowsBPC
• VirtualProviders and MultiProviders
• Reusable and extensible BI ContentBW
• Extensible HANA views on SAP ERP tables
• HANA-enabled planning and analysisHANA
SAP BPC Integration Within the Solution
28
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
SAP BPC Functionality
• SAP BPC functionality listed under administration:
• Local Providers
• Security
• BPFs
• Work Status
• Audit
• SAPUI5 interface
29
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
SAP BPC Model Integration
• SAP BPC Model is
mapped to an
InfoProvider
• Model is display
only
• Pre-delivered with
Real-Time InfoCube
/ERP/SFIN_R01
• Note that plan data is
stored in an extensible
InfoCube and not in
standard and fixed
SAP planning tables
30
9/8/2015
11
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
• HTML5 Web Interface
• Work Status
• Business Process FlowsBPC
• VirtualProviders and MultiProviders
• Reusable and extensible BI Content
• Analysis for OfficeBW
• Extensible HANA views on SAP ERP tables
• HANA-enabled planning and analysisHANA
SAP BW Integration Within the Solution
31
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
SAP BW Virtualization Options
32
• Leverage existing data
warehouse objects
• Reduce ETL
requirements
• Leverage standard
SAP NetWeaver
functions such as
security, information
broadcasting,
BW Content and more
Real-Time
InfoCube
InfoCube DataStore Object
Aggregation
Level
MultiProvider
DataStore
Planning
Layout
Connects
directly to FI
/ CO tables
Virtual
Provider
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
Real-Time Integrated Actuals Data via Universal Journal
33
• VirtualProvider within a MultiProvider pointing to a HANA View
9/8/2015
12
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
Real-Time Integrated Master Data
34
• Can be enhanced to integrated planning master data by
combining master data tables at the SAP HANA level and
pointing the SAP HANA View to the SAP BW InfoObject
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
OLAP Integration via Excel
35
• Analysis for Office is the Excel-based interface of choice for
IBPf because of its integration with MultiProviders as opposed
to the EPM Add-In which integrates with Real-Time InfoCubes
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
• HTML5 Web Interface
• Work Status
• Business Process FlowsBPC
• VirtualProviders and MultiProviders
• Reusable and extensible BI ContentBW
• Extensible HANA views on SAP ERP tables
• HANA-enabled planning and analysisHANA
SAP HANA Integration Within the Solution
36
9/8/2015
13
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
SAP HANA View on Universal Journal
37
• Simplified SAP HANA calculation views based on a
universalized financial line item table
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
SAP HANA View on Master Data
38
• HANA calculation views on master data tables
• SAP HANA views are extensible and be enhanced to combine
planning master data as well
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
Topics
• Current Integration Challenges with SAP BPC
• New Design Options for Real-Time and Shared Data
• Implementation Considerations
• Summary
39
The name of the last mandatory
section of the agenda is Summary.
Use this slide to summarize your
presentation.
9/8/2015
14
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
Migration to SAP Simple Finance 1503 Considerations
40
• Note that you will be automatically migrated to new GL (General
Ledger) and new AA (Asset Accounting) in addition to ACDOCA
• Can be done at month-end; document splitting considerations
Planning Preparation Installation Migration of Data
Install Add-On
Installation/Upgrade Migration of Application Data
Business uptime Business downtime weekend
Check Prerequisites
Prepare Installation/Upgrade
Prepare Migration of DataTasks Following the Installation
Deploy HANA Content
Migration of DataTasks Following the
Installation
Business uptime
System uptime Down System uptime
SUM uptime phase
Tasks following the migration: Perform during business update
Source: Modified from SAP
On premise edition depicted but
cloud editions also available
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
Central Finance Deployment Option
41
• Central Finance breaks out the Financial Accounting and
Controlling (FI/CO) applications (modules) from the rest of SAP
ERP via Application Link Enabling (ALE)
• Is a way to implement Simple Finance without disrupting your
existing SAP ERP systems as well integrate multiple sources
(both SAP and non-SAP) into one central finance system
• Useful for mergers and acquisitions as well as financial shared
services scenarios
SAP ERP
FI COSD
MM
PP QM QM HR BC CA
S/4HANA
FI COALE
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
Migrating BPC Standard into SAP Simple Finance
42
• Zip up your investment
easily with backup and
restore tool
• After download, upload
the zipped
file into a SAP Simple
Finance system
if the SAP BPC
components are already
installed
• Can be migrated to a
new SAP BPC version
after upload via a
migration program
9/8/2015
15
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
Standard and Embedded In Simple Finance
• BPC Standard can
be installed on a
Simple Finance
system
• Can be used with the
“Embedded”
Integrated Business
Planning for finance
43
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
Loading Data from Embedded to Standard
44
• “Standard” can be loaded from “Embedded” as a data snapshot
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
Embedded Model
Differences
Standard Model
Differences
Similarities
Web Reporting
Microsoft Excel Reporting
BI Integration
Mobile Reporting
SAP HANA support
SAP NetWeaver SSO
BADI Framework for Enhancements
Granular Transports
Process Chains
EPM Office Add-In
EPM Web Client
Business Process Flows
Data Access Profiles
Work Status
Separate
namespace
Analysis for Office Excel
client
Leverage BW content
Full EDW Integration
Aggregation levels
Web Application Designer
Centralized (IT)
Administration
Business-user
Administration
Financial
Consolidation
BEx Analyzer
Navigational attributes
Session-based locking
Matrix Security
FOX scripting
Information Broadcasting
Books
Logic Script
Dimension Member
Formulas
Measures
Business Rules
© TruQua. All Rights Reserved.
Comparing BPC Standard Versus Embedded Options
Source: Derived from SAP45
9/8/2015
16
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
Topics
• Current Integration Challenges with SAP BPC
• New Design Options for Real-Time and Shared Data
• Implementation Considerations
• Summary
46
The name of the last mandatory
section of the agenda is Summary.
Use this slide to summarize your
presentation.
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
Resources
47
• Jens Krüger, SAP Simple Finance: An Introduction (SAP
PRESS, 2015).
• ISBN: 978-1-4932-1215-6
• https://www.sap-press.com/sap-simple-finance_3793/
• http://help.sap.com
• Financial Management SAP Simple Finance SAP Simple
Finance, On-Premise Edition
• http://discover.sap.com/S4HANA
• www.sap.com/solution/lob/finance/software/cloud-erp-finance-
management/index.html
• http://go.sap.com/solution/lob/finance.html
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
Five Key Ideas
1. Past technology limitations produced redundant data
integration layers between transactional and analytical
applications creating reconciliation and data latency issues
2. SAP BPC data formats and application conventions are
different from SAP BW and in turn SAP BW are different to
SAP ERP due to application specific designs and logic
3. SAP HANA enables the virtualization of data layers as well as
the integration of transactional line item tables starting with
SAP Simple Finance and the Universal Journal
4. The SAP BPC Embedded Model takes advantage of
virtualization and the Universal Journal for real-time integrated
financial planning and analysis
5. BPC Standard can work in tandem with BPC Embedded in SAP
Simple Finance to gain “best of both worlds”48
9/8/2015
17
R 150
G 140
B 140
R 213
G 209
B 209
R 0
G 176
B 240
R 292
G 0
B 0
R 255
G 192
B 0
R 234
G 40
B 57
R 123
G 167
B 157
R 146
G 208
B 80
R 60
G 61
B 62
R 7
G 43
B 128
Questions
• Now:
• Ask questions now for immediate answers
• Later:
• E-mail me at [email protected]
49
Q&A
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.