embedded business warehouse
DESCRIPTION
Embedded Business WarehouseTRANSCRIPT
Embedded BWDefinition and PositioningMarch 2015
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 2
Embedded BWDefinition
Suite
onH
ANA
Clie
nt00
1
SAP
BW
Clie
nt00
2
VirtualAccess
Extractor
SAP HANA / any DB
User Interfaces (BI, Mobile)
(1) (2)
BWQuery
What is Embedded BW:SAP BW is automatically included in SAP ERP systemssince SAP NetWeaver 7.0, The SAP BW technology thatexists inside such an ERP system is called ‘Embedded BW’.The Embedded BW is used to support:
certain business processes in the SAPBusiness Suite (1) e.g. integrated businessplanning in the Financials Add-On, SAP BusinessPlanning & Consolidation (BPC)or analytics in the SAP Business Suite (2) e.g.use of SAP BW for OLAP scenarios
From an outside perspective, the product that is sold to andinstalled at a customer is the SAP Business Suite
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 3
Embedded BWRecommendation
Suite
onH
ANA
Clie
nt00
1
SAP
BW
Clie
nt00
2
VirtualAccess
Extractor
SAP HANA / any DB
Other SAPand Non SAP
apps
In general, SAP recommends to useEmbedded BW only in scenariosdescribed in the previous slide
When using Embedded BW beyond this,i.e. loading external data, please reviewSAP Note 1661202, and check with youraccount executive regarding your licensemodel
For building an Enterprise DataWarehouse with SAP BW, SAPrecommends to use a separate SAPBW system. For more information,please refer to SAP’s EDW Positioningas well as SAP HANA Live / BWPositioning.
BWQuery
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 4
Embedded BWRecommendation
Please also consider:• Loading of external data should be avoided and only done to support the local business process,
number of external sources should be limited. Percentage of external data should not be more than20% of the overall DB volume!
• Sizing for BW has to follow the common rules and recommendations. It has to be done cumulative tothe ERP sizing itself.
• Resource Allocation and Capacity Planning, System and Workload Management and Monitoring• Backup and Recovery, Lifecycle Management, Security
Client Distribution:• If an ERP system has one client, there is the option to run BW in the same client or a separate client• When multiple clients are deployed in one ERP system, for organizational reasons, SAP recommends
to have a dedicated SAP BW client (for development and administration purposes)
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 5
Embedded BW in SAP Simple Finance: Sizing Options
Simple Finance System
HANA
BW
CharacteristicsHeavy transactional processingExternal data load via BW-ETL restricted– Data volume < 20%
ScenariosSimple FinanceCentral Finance with major transactional processing
SizingERP based sizingScale-out not supportedScale – up supported
FIN
Simple Finance System
HANA
BW
FIN
CharacteristicsLittle transactional processingMainly external data load
ScenariosCentral Finance with restricted transactionalprocessing
SizingBW based sizingScale-out supportedFixed core to memory ratio
ERP based sizing“Simple Finance with Embedded BW”
BW based sizing“EDW with Embedded Finance”
Both systems contain exactlythe same software componentsThey only differ with respectto sizing
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 6
Embedded BWRelated Information
EDW Positioning• http://scn.sap.com/docs/DOC-41326
Positioning of SAP Business Warehouse Powered by SAP HANA and SAP HANA Live for SAPBusiness Suite• https://scn.sap.com/docs/DOC-35584
System Landscape Recommendations for SAP NetWeaver 7.3 – Information Centric Capabilities• http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/50b765af-91a5-2e10-9692-
d4764d024cb3?QuickLink=index&overridelayout=trueSupport for Multiple Applications on SAP HANA• Presentation: like http://scn.sap.com/docs/DOC-59771• http://service.sap.com/sap/support/notes/1661202
Additions BW Deployment Recommendations (multi-client ops)• http://service.sap.com/sap/support/notes/1358744Considerations with SAP HANA Multi-tenant Database Containers and SAP BW• http://service.sap.com/sap/support/notes/2121768
THANK YOU
Questions?EMEA: [email protected]: [email protected]/BPC: [email protected]: [email protected]
Appendix
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 9
Deployment Options for BW Systems (1)
Multi-Components One Database
Suite
onH
ANA
Syst
emID
‘AB
C‘
VirtualAccess
Extractor
SAP HANA
SAP
BW
Syst
emID
,‘D
EF‘
BWQuery MCOD
• From a system landscape perspective,Embedded BW (same installation) isdifferent from MCOD (= two SAPNetWeaver stacks (one for Business Suite+ one for BW) running on the sameinstance of SAP HANA).
• MCOD setup on one SAP HANA system isnot supported for SAP Business Suiteand SAP BW (SAP Note 1661202“Support for multiple applications on SAPHANA”).
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 10
Deployment Options for BW Systems (2)
• Instead of MCOD, SAP BW can bedeployed as an additional databasecontainer beside a Suite on HANAsystem on a multi-tenant database.Please refer to SAP Notes 2096000 &2104291 for more information aboutMulti-tenant Database Container(MDC) concept of SAP HANA
• Other scenarios and options regardingQuality Assurance (QA)- andDevelopment systems, please seehttp://scn.sap.com/docs/DOC-59771for more information
SAP HANA
TenantABW
Host 1
TenantABW
Host 2
TenantABW
Host 3
TenantABW
Host 4
TenantBBW
Host 5
SAP BW SAP ERP
TenantA
TenantB
SAP HANA
SAP BW SAP ERP
MDC
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 11
© 2015 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 anSAP 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 additionaltrademark 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 orSAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products andservices, 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 relatedpresentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliatedcompanies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may bechanged 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 uncertaintiesthat could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-lookingstatements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.