BPC Embedded model is based on Business Warehouse-Integrated Planning (BW-IP) in which it uses BW objects directly. This model is different from Standard model and includes data access to all community users.

1. 1
Monday, March 14, 2022
A Presentation by George Kordosis
info@sapbpcanalytics.eu
https://www.sapbpcanalytics.eu/

2. Key capabilities
2

3. Simplification - BW Modeling Tools in Eclipse
Delivered and planned Eclipse Editors in SAP BW
3
Composite
Provider
advanced
DataStore Object
Open ODS View
Query Designer
(simple queries)
SAP BW 7.4 SP9 / SP10
InfoObject
Query Designer
(complex queries)
SAP BW 7.5 SP1
Semantic Groups
Aggregation Level
OpenHub
SAP BW 7.5 SP4
Transformations
&
Data Flows
Planned
Innovations

4. Platform Integration - HANA Smart Data Integration for
SAP BW
4
SAP BW
HANA Source System
Smart Data Access
EIM: Smart Data Integration
SAP HANA
tREAL-TIME
REPLICATION
DIRECT
ACCESS

5. 5
Following templates are
available for supporting
• Cost center planning
• Functional Areas / Work Analysis
• Internal Order Planning
• Project systems Planning
• Profit Centre Planning
• Cost of Sales Planning
• P&L Planning
• Market Segment
• WIP Analysis
• Balance sheet
Following BW/ HANA
Content available as part of
offering:
• Info-Providers
• Queries
• Planning Functions
• Filters
• Sequences
• HANA Information Models

6. What is Embedded BW:
6

7. What is Embedded BW:
7

8. In general, SAP recommends to use Embedded BW only for the SAP
standard scenarios. Beyond those cases particular rules and limitations apply,
i.e.:
SAP strongly recommends not to use Embedded BW for data
warehousing (EDW) use cases!
The amount of data persisted in the Embedded BW should not exceed
20% of the overall data volume of the system. This applies to
Extraction from own Suite / S/4HANA system
Integration of data from external applications Data from
planning applications License implications
Use of BPC requires a separate license
Security / Authorizations
Embedded BW relies on a separate authorization concept. Authorizations
from Suite / S/4HANA do not apply but need to be mapped if required.
Client Distribution
SAP recommends a separate client for Embedded BW
for organizational reasons (development, administration)
whenever data is physically replicated from another SAP application (on
the same system) to the Embedded BW
For certain scenarios the Embedded BW can be installed on the same
client (for additional details see slides 8, 9 in the appendix).
3

9. 9

10. SOFTWARE MATRIX
!

11. THE PATH TO SAP CLOUD
FOR PLANNING
& CONSOLIDATION

12. THE PATH TO SAP CLOUD
FOR PLANNING
& CONSOLIDATION

13. Key capabilities
13

14. 14

15. The path to BPC Optimized for S4HANA
15

16. The Evolution for SAP BPC
16

17. 17
“overall main
objectives”
• Iimprovement in the
budgeting and
consolidation business
processes.
• Integration of data in a
centrally accessible
repository storing silo.
“overall main objectives”
• Make the monthly
reporting preparation
more transparent and
efficiently for the users.
• Improve business
information and enable
business visibility and
analysis for the
management reporting
outputs.
.
“Key capabilities”
• It eliminates data
replication and have real time
access to master and
transactional data maintained
in SAP ERP.
• It enables flexible
drill-down on dimensions
including customer, segment,
product category, product
geography and channel.

18. 18
Thank You