sap q&a - short presentation title...methodology for bw 7.3 upgrade, os/db migration sap nw bw...

Project ApproachesSAP NetWeaver BW powered by SAP HANAParallel (heterogeneous) System LandscapeGabor Kovacs - Customer Solution Adoption (CSA), SAP LabsMay 15th, 2013

© 2013 SAP AG. All rights reserved. 2Public

Disclaimer

This presentation outlines our general product direction and should not be relied on inmaking a purchase decision. This presentation is not subject to your license agreementor any other agreement with SAP. SAP has no obligation to pursue any course ofbusiness outlined in this presentation or to develop or release any functionalitymentioned in this presentation. This presentation and SAP's strategy and possible futuredevelopments are subject to change and may be changed by SAP at any time for anyreason without notice. This document is provided without a warranty of any kind, eitherexpress or implied, including but not limited to, the implied warranties ofmerchantability, fitness for a particular purpose, or non-infringement. SAP assumes noresponsibility for errors or omissions in this document, except if such damages werecaused by SAP intentionally or grossly negligent.


Agenda

Project Approaches to BW on HANAMigration vs. New InstallationDecision drivers, comparison

Parallel System Landscape (Managing Heterogeneous System Landscapes)General Considerations, RecommendationsDevelopment and transport considerations

Transport Management between BW on HANA and BW on xDB (RDBMS)HANA-optimized InfoProvidersOther InfoProvidersOther BW ObjectsBW on HANA ‘Mixed’ Scenarios


Agenda





SAP NWBW 7.x

X database

Project Approaches to BW on HANATwo Options to Consider: Migration vs. New Installation

Full transport and loadinto New Instance

Partial transport andload into New Instance

PrimaryApproaches

to BW onHANA Move to BW powered by HANA by functional subject

areas or all subject areas depending on requirements.

Upgrade &Migrate ExistingBW Landscape

Deploy ParallelBW 7.3

Landscape

Subject Areas

Methodology for BW 7.3 Upgrade, OS/DB MigrationSAP NWBW 7.3

SAP HANA 1.0 SP3*

SAP NWBW 7.3

SAP HANA 1.0 SP3*

Production Go-Live possible without loading all subjectareas

Subject Areas

In-MemoryProduction Solution

In-MemoryProduction Solution

Potential LegacyProduction Solution

* SAP HANA 1.0 SP3 minimum – current release SPS5Parallel Landscape for Long Term?


Project Approaches to BW on HANANew Installation and Migration Options

New installationIn-place migration Copy, upgrade + migrate

Migration Tools, Technical details for SAP NetWeaver BW:Upgrade and Migration - BW on HANAUpgrade/Migration/ImplementationSWPM (Software Provisioning Manager)Post Copy Automation toolDatabase Migration Option (DMO) for SUM

Migration Options

http://www.saphana.com/docs/DOC-3294

http://scn.sap.com/docs/DOC-7856

http://service.sap.com/sltoolset


http://scn.sap.com/community/it-management/alm/software-logistics/blog/2013/01/15/dmo-upgrade-and-migrate-sap-systems-to-sap-hana


DMO at a GlanceDatabase Migration Option for Software Update Manager

Scenario - for ‘in-place’ migration optionDMO stands for “database migration option of Software Update Manager (SUM)”DMO combines the upgrade and the migration to SAP HANA in one tool: SUMDMO for SUM is not yet general available, but we started piloting with customersDMO will be available for BW and Suite systems (later this year)DMO is part of SUM, so no new product, and no additional license fees

BenefitsOne downtime instead of two: combination of upgrade and migrationLess requirements for the DB software version of the existing DBWell known tool SUM is used, with improved UICombination of procedures is possible – DMO + PCA (further automation, less TCO)Original DB continues to run, but is no longer used to store data – can be reactivated asfallback


Comparison of Standard and New Migration ProcessesNew option also reduces time by eliminating prep/post activities

Prepact.

Postact.

UpdateBW 7.xto 7.31

Prepact.

Postact.

MigrateanyDB to

HANA

ProductiveUse

Possible

Current migration to SAP HANA

DatabaseUpgrade

OSUpgrade

Prepact.

Postact.

DMO:BW 7.xto 7.31

DualStackSplit

DMO: Integrated update and migration to SAP HANA

SAP BW„on HANA“

UnicodeConversion

DatabaseUpgrade

UnicodeConversion

OSUpgrade

DualStackSplit

not needed

* - may be a necessary step –depends on customer situation, start release

LegendInformation sourcesSCN Blog: DMO - Upgrade and Migrate SAPSystems to HANA (software logistics)SAP Note 1799545 on DMO:https://service.sap.com/sap/support/notes/1799545

http://scn.sap.com/community/it-management/alm/software-logistics/blog/2013/01/15/dmo-upgrade-and-migrate-sap-systems-to-sap-hana

https://service.sap.com/sap/support/notes/1799545


BW 3.x / 7.x(xDB/HW)

Current State

BW 7.3 / 7.31*(xDB/HW)

BW 7.3 BW7.3 on HANA

Project Approaches to BW on HANAMigration option – Relevant Project Activities

BW 7.3 / 7.31*powered by

SAP HANA

BW on HANA Migration Planning

BW on HANADesign

Use Case Identification

Unicode Planning

BW Technical Upgrade

BW Authorizations

BW Data Volumes

BW In-MemoryConversion Analysis

HANA Readiness

BW RDBMS RDS

BW on HANAMigrate

Housekeeping:Note 1829728 - BW Housekeeping Task List

Migration to BW on HANA RDS:https://service.sap.com/rds-hana-bwmig

Does notrepresentseparateinstallations

Upgrade to latest SP

Unicode Upgrade


BW Housekeeping

BW Data Volumes

BW on HANAPrepare

Functional Upgrade(e.g. data flows)

* current SP9 / SP7


https://service.sap.com/rds-hana-bwmig



SAP HANA

Install NewEnvironment

TransportConfiguration to New

Environment

Project Approaches to BW on HANANew Installation – Relevant Project Activities


SAP HANA

BW on HANA Solution Planning

BW 3.x / 7.x(xDB/HW)

CurrentEnvironment

SAP HANA Install andConfigure

SAP NW BW 7.3 Installand Configure

BW on HANAInstall

Transport systemconfiguration

BW on HANATransport

Initial load of databased on transported

content

BW In-MemoryConversion

Functional upgrade(data flows)

BW Authorizationmigration

Use Case Identification

BW Authorizations


Data Load Planning

BW on HANADesign

* current SP9 / SP7


Agenda





What to Consider When Deciding on Options?Where Do We Go from Here?

Business Considerations Functional Considerations Technical Considerations

Key Drivers

Cost considerations

Use case scenarios

Project duration

Subject Areas

System Consolidation

HANA Impact

Redesign

Data Latency / Loadwindow

BW Footprint

BW Versions

BW 7.x deployment

Data Volume

Archiving

BW Landscape –system support

Reporting Tools

Migration options, tools

HM1

HM1 Design should be optimizedHartz, Marc, 3/20/2013


What to Consider When Deciding on Options?Business Considerations

Drivers

Do you have a sense of how many subject areas cantake advantage of in-memory?

Do you have multiple BW landscapes you would liketo consolidate?

Is the current inclination toward a big bang deploymentor an iterative roll-out of new, improved functionality?

What are the drivers for the HANA migration? Whatare the KPIs and desired outcomes?

How much the different alternatives cost? Hardware,project, etc.

HANA Impact

System Consolidation

Cost

Project Duration vs.Live Use Case

Subject Areas

Do you have any use cases requiring immediate HANAacceleration? Would immediate acceleration of thoseuse cases offset a potentially longer overall project?


What to Consider When Deciding on Options?Functional Considerations

Data Latency / LoadWindows

Opportunity to Re-Architect

BW Footprint

BW versions

How much of the 7.xcontent is deployed?

Is the current BW configuration meeting the businessneeds, or is there a desire for redesign?

Are your currently challenged to meet load windowsand / or is current data latency impacting the business?

How much BW configuration do you currently havedeployed to users? What is your growth plan?

What version of BW do you have deployed currently?

Are you currently utilizing the 7.x dataflows and/or7.x security?


What to Consider When Deciding on Options?Technical Considerations

ArchivingConsiderations

Data Considerations

SupportConsiderations

Reporting Tools

Internal Capabilities

How much data are you managing in your currentBW landscape?

Are you currently archiving in ECC? Does ECCcontain all the relevant history you require in BW?

What is your current system support plan? What isyour ability to support multiple BW landscapes?

What reporting tools are currently deployed? Howdo users access data in the BW system?

What is your internal team’s capabilities andbandwidth to support the project activities?

Migration options,Tools

What are the technical options, requirements? Whattools are available?


How Have Other Companies Decided What To Do?Example #1 – Full Upgrade and Migrate – hidden


Provided an opportunity to remove layers (e.g.reporting) and flatten the architecture, whichprovided support and cost benefits

Phased parallel landscape approach would delayrealization of full benefits

Data Considerations

Current BW system contained large amounts ofdata

Phase parallel landscape approach would havetaken too long to meet business needs

How did they decide which option?Why did they choose BW on HANA?

Which option did they choose?

Faster reporting

Faster data loading

Lower TCO

Reduced maintenance costs

Reduced development costs

Upgrade & migrate existingBW landscape

Support Considerations

Challenges with supporting data feeds fromnumerous systems into two BW landscapes

Cost of additional hardware and supportrequirements for two BW landscapes


How Have Other Companies Decided What To Do?Example #2 – Parallel Landscape – hidden


Not content with their current BW design

How did they decide which option?Why did they choose BW on HANA?

Which option did they choose?

Faster reporting

Faster data loading

Lower TCO

Reduced maintenance costs

Reduced development costs

Deploy Parallel BW 7.3 onHANA landscape

Increased end-user self-sufficiency

Subject Areas

Recognized that certain subject areas were mostimportant to in-memory capabilities

BW Footprint

Current BW system still young

Completed prioritization analysis to determinetop subject areas

Wanted to take advantage of some re-designopportunities with in-memory capabilities

Saw opportunity to adjust based on user input


How Have Other Companies Decided What To Do?Two examples – How did they decide which option?


Provided an opportunity to remove layers (e.g.reporting) and flatten the architecture, whichprovided support and cost benefits

Phased parallel landscape approach would delayrealization of full benefits

Data Considerations

Current BW system contained large amounts ofdata

Phase parallel landscape approach would havetaken too long to meet business needs

Upgrade and migrate existing BW

Support Considerations

Challenges with supporting data feeds fromnumerous systems into two BW landscapes

Cost of additional hardware and supportrequirements for two BW landscapes


Not content with their current BW design

Deploy parallel BW on HANA

Subject Areas

Recognized that certain subject areas were mostimportant to in-memory capabilities

BW Footprint

Current BW system still young

Completed prioritization analysis to determinetop subject areas

Wanted to take advantage of some re-designopportunities with in-memory capabilities

Saw opportunity to adjust based on user input


SAP BW to BW on HANA Implementation ApproachesHow do they compare?

New installation In-place migration Copy, upgrade + migrate

Simplifies IT effort

Provides opportunity to re-engineer andleave unnecessary data behind

Requires significant impact analysis andprioritization effort of existing scenarios

Requires operating 2 Data Warehouses inparallel for an extended period of time

Extends time to delivery of business readycontent (transports, testing, reloading ofbusiness data)

Leverage Existing Landscape

Improves time to delivery – all contentand data is available post migration

Scope Defined - No RequirementsGathering

Increases IT effort

Downtime Requirement

No real Fallback option (only via restore)

Minimized Downtime

Enables fast deployment of 2 consistentlandscapes for stability and data accuracychecks

Improves time to delivery – all content anddata is available post migration

Increases IT effort

Requires additional migration preparationstep Post Copy Automation (PCA) supportfor all BW interfaces


SAP BW on HANA migration and project approachesTechnical Evaluation - summary

1. NewInstallation

2. In-PlaceMigration

3. Copy &Migrate

EDW Redesign planned +++ - ++Redundancy in Staging + +++ --EDW Model Consistency - +++ ++Transport Restrictions +++ -- +Implementation Effort Medium Low MediumSystem Availability Impact Low High LowOperation Cost High Low Medium





SAP BW on HANA migration and project approachesTechnical Evaluation - considerations

How to get toBW on HANA

Reasons you would choose Things to consider

NewInstallation

• Minimize downtime for production• Parallel production systems (side-by-side

operation)• Ongoing benchmark• Redesign, clean up• No need to split dual-stack• Functional upgrade (authorizations, dataflow)

w/o changing current system

• Transports – complex dependencies, restrictions• Reload data, request history lost• Delta queue management (PCA tool), extractor specifics

for one source to two BW (SAP notes: 844222, 775568)• Additional hardware cost (app servers)• Not suited for replacement of current prod system• Change of System-ID and Logical System• Longest duration (redesign/rebuild) – complex landscape

to maintain

In-placemigration

• Minimum overall project duration• No additional hardware cost (reuse

application servers)• No change of SID and Logical System• No SAP ECC extractor limitations• Multiple change events combined (e.g.

Oracle/BW upgrade, OS/DB migration)

• Production downtime!!• Migration preparation tasks, split dual-stack (Dual-Stack

Split)• No Parallel production systems (fallback = restore)For BW < 7.3 SP9• Analysis authorization• BW Technical upgrade to 7.3• Unicode conversion• Apply latest Support Package

Copy +Migrate

• No risk for current production system• Downtime only for DB Export• Parallel production systems (validation prior

cutover)

• Migration procedure, preparation tasks, delta queuehandling, split dual-stack

• Change of System-ID and Logical System• Parallel production systems• PCA support to be validated for all source systems


SAP BW on HANA migration and project approachesTechnical Evaluation – considerations 1/2

Technology Switch vs. EDW RedesignIs an EDW Redesign planned in the context of the BW on HANA project or is thefocus on a technology switch for improved performance, TCO and flexibility onexisting models only?BW on HANA offers much more flexibility and the possibility to implement scenariosstreamlined

Redundancy in Data StagingWill the BW on HANA project result in two separate production systems that have tobe supplied both with latest delta data (if redundant data: realignment challenges)

EDW Model ConsistencyRisk of diverging corporate meta data (especially master data) - Corporate masterdata across multiple systems has to be synchronized

Landscape ComplexityLandscape complexity (multiple production systems) – system administration


SAP BW on HANA migration and project approachesTechnical Evaluation – considerations 2/2

Transport Restrictions (more details follow)Consistency of the productive BW systems has to be ensuredTransporting between BW / RDBMS and BW / HANA systems includes certaintechnical restrictions

Implementation Costs (TCD)Additional effort to reload data to new systems or to transport modelsAdditional effort to redesign and (re)implement, new scenarios

System Availability ImpactMinimize downtimes for end users during migration project

Operation Costs (TCO)Total cost of ownership will increase as results of a new and additional productivesystem landscape

HM2

HM2 I like the points we have so far!

Should we also add "landscape complexity" in general?Hartz, Marc, 3/20/2013



Agenda






Parallel BW LandscapeBW on HANA and BW on xDB (non-HANA)

SAP strongly recommends to have the same DB platforms across all BWsystems of a transport landscape (Development/ Sandbox/ Quality/Production).

SAP Note 1808450 - Homogenous system landscape for on BW-HANA

When Productive BW on xDB and BW on HANA coexist:Parallel independent System-Landscapes (BW on HANA and BW on xDB)

ConsiderationsConsistent Metadata (transport)Platform (DB) specific scenarios (HANA-specific scenarios, xDB-specific objects)Restrictions: cross-DB, cross-release transports



Parallel BW LandscapeDevelopment Landscape Considerations

Co-existing BW on RDBMS and BW on HANA systemsComplex Global Landscapes – not all systems migrated to HANAOriginal BW and BW on HANA for different use case scenarios

Parallel Landscape (minimize time of co-existence Landscape)

Development

Original BW

BW on HANA

QA Production

xDB

SAPHANASAP

HANA

xDB

SAPHANASAP

HANA

xDB

SAPHANASAP

HANA

Transport

Transport

Transport

Transport

Leading BWDevelopment

System?

Transport

Tran

spor

t? Note 1808450 - Homogenous system landscape for on BW-HANA


Parallel BW Landscape – Production onlyDevelopment Landscape Considerations

Transport

OriginalBWDevelopment

BWD

ProductionBWP

ConsolidationBWQ

ProductionBHP

BW onHANA

Transports

Feeding two productive BW systems with transports:• Technically possible but not recommended

(Consider Note 1808450 - Homogenous system landscape for on BW-HANA )• However this should be avoided as long-term solution as transport/

landscape complexity increase and HANA advantages cannot be fullyleveraged (cannot test and develop HANA specific scenarios)


http://help.sap.com/saphelp_nw73/helpdata/en/c1/7a2cbfe391428e9f9df7b093f42a93/frameset.htm


Agenda






Transport Management in Parallel BW LandscapeGeneral Considerations

Transports between ReleasesNote 1090842 - Composite note: Transports across several releases

… consider custom ABAP enhancements as wellNote 1847431 - SAP NetWeaver BW ABAP Routine Analyzer

Transports between HANA and non-HANA databasesUsing non-HANA-based development system for a HANA-based production system doesnot allow you to develop and test HANA-specific objects and processesUsing a HANA-based development system for a non-HANA-based production system willlead to several problems due to– Obsolete objects (e.g. aggregates, DB indexes, obsolete Process types (process chains) )– New development paradigms and architecture changes (e.g. reporting on DSO, simplified data flows,

new HANA-optimized InfoProviders, ‘mixed’ scenarios based on native HANA models, InfoCubecompression, Inventory handling, CompositeProvider, type of partitioning and pruning, archivingstrategy, transformation ABAP code)

Mixed-platform landscape will cause overhead (TCO) and potential forsuboptimal implementation.


Transport Management in Parallel BW LandscapeDevelopment / Design considerations

Scenarios available only in BW on HANAHANA optimized objects, procedures, Planning Applications KitStreamlined LSA++ architecture– Fast Reporting on DataStore Objects will lead to slimmer layer designActivate Master Data via DTP‘Mixed scenarios’Planning Applications Kit (Note 1637199 - Using the planning applications KIT )

Additional developments for BW on xDB (after transport from BW on HANA)Aggregates management (Change-Runs, Roll-Up Processes)Secondary DB IndexesEnhance process chains – obsolete process types in HANAAuthorization: BW Analysis Authorization is mandatory in BW 7.3; if the target system is onlyBW 7.0 (w/ old concept) or BW 3.x transport is not possible – recreate authorizationNon-cumulative key-figure handling, like Inventory InfoCubesPerformance optimization (DSO and InfoCube Partitioning) and Database OperationsWorkspaces



Agenda



Transport Management between BW on HANA and BW on xDB (RDBMS)HANA-optimized InfoProvidersOther InfoProvidersOther BW ObjectsNon-cumulative handlingBW on HANA ‘Mixed’ Scenarios





Transport Management in Parallel BW LandscapeTransporting InfoProviders between BW on HANA and BW on RDBMS

Consider structural differences and DB-specific featuresNote 1691096 - Transport of InfoCubes from and to SAP HANA database

Database of thedevelopment

system

Object Type inthe development

system

Object alreadyexists in

production

Database of theproduction system

Resulting objectType in the

production system

Classic Database Standard InfoCube No SAP-HANA Database SAP HANA-OptimizedInfoCube

Classic Database InfoCube with DataPersistency in the BWA No SAP-HANA Database SAP HANA-Optimized

InfoCube

Classic Database Standard InfoCube Yes SAP-HANA Database Standard InfoCube

SAP-HANA Database SAP HANA-OptimizedInfoCube No Classic Database Standard InfoCube

SAP-HANA Database SAP HANA-OptimizedInfoCube Yes Classic Database Standard InfoCube *

SAP-HANA Database SAP HANA-OptimizedInfoCube Yes Classic Database InfoCube with Data

Persistency in the BWA **

Classic Database Standard DataStoreObject Yes / No (both cases) SAP-HANA Database Standard DataStore

Object

SAP-HANA Database SAP HANA-OptimizedDataStore Object Yes / No (both cases) Classic Database Standard DataStore

Object

* InfoCube is already available in the target system as standard InfoCube** InfoCube is already available in the target system as InfoCube with Persistency only in BWA



DataStore Objects:Note 1715129 - Transport of DataStore objects in SAP HANA environmentSource system: Classic DBMS, target system: SAP HANAIf the SAP-HANA-optimized DataStore object in the target system contains data, the transport terminateswith an error message. In this case, you either have to set the property "Optimized for SAP HANA" in thetarget system and activate the object again, or you have to import a new transport.Do you need HANA-optimized DSO? http://scn.sap.com/docs/DOC-41327,http://www.saphana.com/docs/DOC-3129

MultiProviderNo specific considerations – assuming the part-providers transported successfully

Semantically Partitioned ObjectNo specific considerations – assuming the part-providers transported successfully

HybridProviderThe HybridProvider is a transport object in its own right. The metadata of a HybridProvider comprises theproperties of the InfoCube and the properties of the DataStore object/VirtualProvider– InfoCube in the HybridProvider follows the above rules (BWA only InfoCube!)– HANA-optimized DSO (with RDA) in HybridProvider is not available (always standard DSO)

http://help.sap.com/saphelp_nw73/helpdata/en/c1/7a2cbfe391428e9f9df7b093f42a93/frameset.htm



CompositeProviderCannot be transported between xDB (w/ BWA) and BW on HANAClassic DB: only available with BWA (limited scenario) – not transportableBW on HANA: can only be transported if it consists solely of transportable InfoProviders

TransientProviderCannot be transported (no matter what the DB is)

Analytic IndexSupported with BWA and BW on HANA, but cannot be transported between – need to be re-created in thetarget system

Query Snapshot IndexSupported with BWA and BW on HANA, but cannot be transported between – need to be re-created in thetarget system

VirtualProviderNo specific considerations, except VirtualProvider on HANA-models (see below)


Transport Management in Parallel BW LandscapeTransporting BW Objects between BW on HANA and BW on RDBMS

Process ChainsConsider obsolete process types (Obsolete Process Types for SAP HANA Database)– Transport from xDB to HANA: fails (????) if PC includes obsolete process types -> manual adjustment– Transport from HANA to xDB: manual adjustment required if xDB specific process types neededSpecial process types only for BW on HANA– Trigger Delta Merge only available and necessary in SAP HANA

BW WorkspaceCannot be transported (no matter what the DB is)

InfoObjectsNo specific considerations

Open Hub DestinationOpen Hub with specific HANA table destination cannot be transported to xDB (functionality not available)Otherwise no specific considerations (except BW release-specific functionalities)

TransformationsConsider ABAP coding and HANA specific optimizations

http://help.sap.com/hana/hana_dev_en.pdf




Transport Management in Parallel BW LandscapeDevelopment / Design considerations – Non-cumulative handling

HANA-optimized non-cumulative InfoCube:Flag ’No Marker update‘ removed for HANA-optimized InfoCubesFunctionality is replaced by DTP Flag ‘Historic values‘

Initialization of non-cumulative and Historical data -> compression not required!

Historical TransactionsTurn off for regular delta

Initialization record stored withSID_0RECORDTP = ‘1’ – ‘NCUMInitialization’ partition of/BI0/F0IC_C03 table

Historical transactions stored withSID_0RECORDTP = ‘2’ – ‘NCUMHistory’ partition of /BI0/F0IC_C03table

Delta transactions stored withSID_0RECORDTP = ‘0’ –‘uncompressed’ partition of/BI0/F0IC_C03 table

DTP for History and Delta

DTP for Initialization

http://help.sap.com/saphelp_nw73/helpdata/en/AF/81F38183CF46B9B919F82D7BB7EC47/frameset.htm

https://www.experiencesaphana.com/docs/DOC-1363

https://www.experiencesaphana.com/docs/DOC-1463














http://scn.sap.com/community/netweaver-bw-hana

http://www.saphana.com/


https://www.saphana.com/community/resources

http://www.saphana.com/community/solutions/net-weaver-bw/bwonhanafaq


https://training.sap.com/course/bw362--098-g-en/


Transport Management in Parallel BW Landscape‘Mixed’ Scenarios with BW on HANA

Consuming HANA-models in BW on HANALeverage HANA Datamart scenarios in BW via:– TransientProvider accessing HANA-model– Virtual Provider accessing HANA-model– InfoObjects accessing HANA Attribute view– HANA-model accessing BW InfoProvider

Not available in BW on xDB, therefore cannot be transportedTransport of InfoProviders on HANA-models in the BW on HANA landscape– TransientProviders cannot be transported – need to be redeployed in every BW on HANA systems– VirtualProviders: can be transported, even if the underlying HANA-model does not exist in the target

HANA database– InfoObjects: can be transported, even if the underlying HANA Attribute view does not exist in the target

HANA database

Deploy HANA-models– Export/Import (http://help.sap.com/hana/hana_dev_en.pdf)– CTS+ (http://scn.sap.com/docs/DOC-35874)

Mixed scenarios: BW on HANA and HANA Datamart

http://scn.sap.com/community/webinars/technology-rig-know-how


AppendixFurther References

Using the SAP HANA Database (Specific functions, system behavior, obsolete functions and tools)Aspects of the HANA-optimized InfoCubeReporting on HANA models in BW-on-HANAInfoProviders in SAP NetWeaver BW powered by SAP HANA (webinar replay, presentation)How To - Delta Merge for SAP HANA and SAP NetWeaver BW powered by SAP HANASAP First Guidance – SAP NetWeaver BW 7.30 on HANA Inventory InfoCubesWhat's New with SAP NetWeaver BW 7.30 and BW Accelerator 7.20Modeling SAP NetWeaver BW and SAP HANA Mixed Scenarios (webinar replay, presentation)SAP HANA as Driver of EDW Evolution - LSA++ for BW on SAP HANA (webinar replay, presentation )How to SELECT in SAP BW TransformationsCompositeProvider

Follow SCN BW on HANA and SAP HANA

SAP How-to Guides for SAP NetWeaver Business Warehouse 7.3 powered by SAP HANA

https://www.saphana.com/community/resources -> HANA Solutions -> BW powered by HANA

FAQ BW on HANA http://www.saphana.com/community/solutions/net-weaver-bw/bwonhanafaqSAP Education:

SAP HANA Education: Course & Certification Program 2013BW362

mailto:[email protected]


AppendixSAP Customer Solution Adoption Know-How Webinars

http://scn.sap.com/community/webinars/technology-rig-know-how

Thank you

Contact information:

Gabor [email protected]

We value your opinion. Let us know how you like this CSA presentation and how wecan make adopting SAP innovations a more beautiful experience. Please sendquestions and comments to [email protected].

sap q&a - short presentation title...methodology for bw 7.3 upgrade, os/db migration sap nw bw...

Documents