Skip to Content

Greetings,

On August 31st , a new BW Avatar is born:

BW4HANA.gif

This is not BW on HANA….rather, this is BW especially and exclusively 4 HANA.

A great deal of ink has already been spilled enumerating its might and bright..but I still feel that there are lot of questions people are asking which warrants for a perusal over multiple sets of documents to kind of have an overall picture and although there are umpteen resources available in terms of great documents such as SCN FAQs, SAP Guides etc, a one-stop-shop kind of a document might help provide a consolidated reference point.

All I have tried to do, in my humble effort here, is to go through the myriad sites and documents (BIG DATA..for me) related to BW/4HANA, and have given a consolidated picture…similar to what a Datawarehousing tool, such as BW/4HANA, intends to do..

So, here we go…

Discussion Points Insights | Comments
What is it Just like S/4HANA, it’s a new DataWarehousing product, created only to work with SAP HANA
What it’s not It’s not the next version of BW on HANA
Launch Date

31 August’ 2016

https://news.sap.com/sap-modernizes-data-warehousing-with-the-launch-of-sap-bw4hana

General Availability

7th September’ 2016

Keynote:
http://events.sap.com/sap-amazon-web-services/en/home

https://influence.sap.com/BW4HANA10

Central SAP note

SAP Note: 2347382

https://launchpad.support.sap.com/#/notes/2347382

Minimum HANA Version required

SAP HANA SPS12
Revision 122 or higher

SAP Note: 2347382

https://launchpad.support.sap.com/#/notes/2347382

Is this separate from NetWeaver Stack Yes, SAP BW/4HANA is a separate product which is not part of and does not depend on a NetWeaver delivery. The underlying platform consists of the ABAP application server and SAP HANA.
Old Versioning

BW 3.x, 7.x.

Latest being 7.5, Edition for SAP HANA (BW 7.5, SP04)

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

New versioning

BW/4HANA 1.x

Latest being BW/4HANA 1.0

The Journey so far

1 - Journey so far.png

Software Components

BW/4HANA is built on Application Server for ABAP and comprises only the following software components:


SAP_BASIS
SAP_ABA

SAP_GWFND

SAP_UI

DW4CORE

What happened to the BI Content

Traditional BI Content will not be supported (software components BI_CONT and BI_CONT_XT).

New SAP BW/4HANA business content on top of the Business Content DataSources will be delivered in Q4 2016.

Also, all Business Content Datasources (extractors) that are released for Operational Data Provisioning (ODP) will be supported (the ODP Source System is replacing the SAP Source System in SAP BW/4HANA).

SAP Note: 2232584

https://launchpad.support.sap.com/#/notes/0002232584

FAQ

http://go.sap.com/documents/2016/08/c4458a08-877c-0010-82c7-eda71af511fa.html

Clients required

SAP GUI

SAP NetWeaver Business Client

ABAP Development Tools for SAP NetWeaver (ADT) – for HANA Studio

Modeling Tools for SAP BW∕4HANA (BW Modeling Tools) – for HANA Studio

SAP BusinessObjects Analysis, Edition for Microsoft Office (Sep License)

SAP BusinessObjects Design Studio(Sep License)

Any pictorial depiction of the landscape Product Landcape - Clients and Instances.png
Is it only on-premise or Cloud-based

Both.

Cloud Providers: HEC | AWS (as of now).

Any change in Modeling

A big change.

No more RSA1 !

The new modeling paradigm is…Data Flow Modeler
2 - DataFlowModeler.png

Do I still need to have SAP GUI installed and use Datawarehouse workbench

Yes. SAP GUI is still required.

Datawarehouse Workbench will be used for the following activities

  1. DataSource still maintained in DataWarehousing Workbench.
  2. Administrative tasks are still performed in the DataWarehousing Workbench such as:
    1. Defining Process chains
    2. Authorization Maintenance
    3. Transports
    4. Workspace Administration
    5. DBA Cockpit based monitoring
    6. NLS-IQ administration
    7. Tracing the query execution via RSRT

Note: Web-based administration & monitoring is already work-in-progress and will soon be delivered in next few quarters.

What happens to BW on HANA versions (7.x on HANA)

SAP BW 7.5 powered by and edition for SAP HANA will still be supported release options and will move into maintenance, receiving little development or new functionality moving forward.

SAP BW/4HANA will receive the majority of the new innovation being developed moving forward.

Difference between 7.5, edition for HANA and BW/4HANA
  1. No more RSA1 in BW/4HANA. The new Data Flow Modeler takes over.
  2. The future innovations will be for BW/4HANA.
  3. The integration with Hadoop offered with BW/4HANA via HANA Vora.
  4. Out-of-the-box deployment to HANA Enterprise Cloud and Amazon Web Services (AWS)
How long will BW 7.3, 7.4 and 7.5 on HANA be supported

It follows the NW 7.x release timelines. Therefore:

BW 7.0 -> Maintenance ends on 31.12.2017

BW 7.3 -> Maintenance ends on 31.12.2020

BW 7.4 -> Maintenance ends on 31.12.2020

BW 7.5 -> Maintenance ends on 31.12.2022

PAM:

https://apps.support.sap.com/sap(bD1lbiZjPTAwMQ==)/support/pam/pam.html?smpsrv=https%3A%2F%2Fwebsmp203.sap-ag.de#s=sap%20netweaver%20&o=most_viewed%7Cdesc&ts=8&st=l&rpp=20&page=1

What happens to Bex The SAP Business Explorer (BEx) are not supported any more.
How will I create my Query now Queries are now defined in BW/4HANA in the BW Modeling tools (HANA Studio) via the perspective – ‘BW Modeling’.
What about front-end

Here’s the mapping:

  1. BEx Web – > SAP BusinessObjects Design Studio
  2. Enterprise Reporting -> Crystal report via BOE
  3. BEx Analyzer/Workbook -> SAP BusinessObjects Analysis, Edition for Microsoft Office
  4. BEx Information Broadcasting -> BOE Broadcasting
  5. Dashboards (previously Xcelsius) -> SAP BusinessObjects Design Studio
  6. Crystal Report -> Crystal report via BOE
  7. WebI -> WebI
  8. Explorer -> Lumira
  9. Mobile -> RoamBI
What are new objects corresponding to old ones

Here’s the mapping:

  1. DataStore object (classic) – > DataStore object (advanced)
  2. InfoCube (all types) -> DataStore object (advanced)
  3. MultiProvider -> CompositeProvider
  4. Infosets -> CompositeProvider
  5. VirtualProvider based on the data transfer process -> Open ODS View
  6. VirtualProvider based on a SAP HANA Model -> Open ODS View or CompositeProvider
  7. VirtualProviders with Function Modules -> SAP HANA View (in Open ODS View or CompositeProvider)
  8. Transient Provider -> Open ODS View
  9. SPO -> SPO based on Advanced DSO
  10. Infoobjects – > Infoobjects (enhanced)
  11. InfoObject with master data access via SAP HANA View -> Open ODS View
  12. CompositeProvider (object type COPR) – > CompositeProviders(Note: 2080851)
  13. HybridProvider (InfoCube + DataStore object (classic)) – > DataStore object (advanced)
  14. Analysis process ->  SAP HANA analysis process and transformation
  15. PSA -> DataStore object (advanced)

3 - Old Vs New Objects.png

Any changes in process chain monitoring

Process chains can be monitored via the traditional ABAP Workbench.

However, now the new UI5 based monitoring capabilities can be leveraged:
4 - Process chain monitoring.png

What about Openhubs

They are still relevant and will be supported in BW/4HANA.

No separate license required.

How to migrate

For greenfield:

  1. Implement from scratch
  2. Implement from scratch and transport objects (only new ones such as aDSO, Composite provider) from your existing BW on HANA to BW/4HANA.

For brownfield:

The process goes something like this:

  1. First, upgrade to BW 7.5, edition for HANA. This is done by installing an Add-on using SUM tool.
  2. Then, convert your stnd objects to new HANA-optimized objects.That means, for example, no more InfoCubes and MultiProviders but Advanced DataStore Objects for persistency and CompositeProviders for modeling joins and unions of your persisted or maybe even remote data. 
    To make this conversion as easy as possible, a transfer tool is provided.
    This transfer tool is only available after you upgrade to BW 7.5, edition for HANA.
    The transfer tool will automate the conversion from old to new object types.
    A “Conversion Guide” documenting the complete end-to-end process for transitioning to SAP BW/4HANA is in the works.
  3. Then, switch to BW/4HANA (by executing report RS_B4HANA_CHECK_ENABLE with B4H as the new mode and choosing “Save New Mode”.

For consolidation brownfield:

This is a scenario wherein, several local BW datawarehouses and legacy warehousing systems needed to be consolidated to BW/4HANA.
For this, we can contact SAP to design a tailor-made migration path.


3 Migration Paths.png

https://blogs.saphana.com/2016/09/07/the-road-to-sap-bw4hana-part-1/

Which option is best for my case, any recommendations from SAP

Which Path is right for my case.png

https://blogs.saphana.com/2016/09/18/the-road-to-sap-bw4hana-part-2/

How about going from BW on xDB (Oracle, DB2 etc) directly to BW/4HANA Not supported
Transfer tool

SAP Note: 2238220

Tcode: RSB4HTRF

https://launchpad.support.sap.com/#/notes/0002238220

https://launchpad.support.sap.com/#/notes/0002080851

I hear terms like compatibility mode and B4H mode..what’s the deal

To move to BW/4HANA, first BW has to be upgraded to

BW 7.5, edition for SAP HANA (7.50 SP04 or higher) –
This is called Compatibility mode.
This mode still supports old object types (InfoCubes, Multiprovider etc.)

Then you need to use the “Transfer tool” to convert all your old object types to new objects types (aDSO, Composite Provider etc.)

Then you move to BW/4HANA using SUM
This is called B4H mode.
This mode doesn’t support the old object types anymore.

https://launchpad.support.sap.com/#/notes/2246699

Still confused between BW on HANA, BW, Edition for HANA and BW/4HANA

Answers here:

Difference between BW on HANA, BW, Edition for HANA and BW/4HANA

How will virtual access be designed now

Using EIM – SDI (Smart Data Integration) framework

Using Open ODS Views

http://scn.sap.com/community/developer-center/hana/blog/2014/11/27/hana-sp9-data-provisioning–overview

How will LSA++ look like in BW4HANA

Report at any layer of the Data Warehouse with speed and flexibility

5 - LSA++ in BW4HANA.png

What about 3.x flow No more supported and must be migrated.
Any new sizing exercise introduced

No, the same sizing process used for SAP BW powered by SAP HANA applies to SAP BW/4HANA.

SAP Note 2363248
https://launchpad.support.sap.com/#/notes/0002363248

SAP Note 2296290

https://launchpad.support.sap.com/#/notes/0002296290

What are the changes in Archiving and hot, warm and cold data

With BW/4HANA, relocate cold data, based on extended time slice partitions per persistence object, either

to SAP IQ Near-line Storage (near-online)

OR

to SAP Hadoop NLS (near-offline) – using tool called DLM (DataLifecycleManagement)
6 - NLS in IQ or Hadoop.png

What about automatic HANA view generation 7 - Automatic View Generation.png
Any changes in SAP source systems Vs non-sap source system integration

Number of Source System Types reduced from 7 to 3.

  1. ODP Source System (For SAP sources such as ECC, SRM , CRM etc, including SLT)
  2. HANA Source System (For non-SAP sources, including Hadoop data lakes | using EIM – SDI)
  3. Flat File

8 - SAP and non-SAP source system integration.png

Change in Load Administration

BW/4HANA will have a new request ID concept: tsn

Manage loads by a unique ID, called request TSN (transaction sequence number)

/wp-content/uploads/2016/09/3_1037437.png


More details here…#TSN – The new face of BW Request ID

What about BPC

BPC 10.1 is supported with BW/4HANA.

However, only Embedded model is supported. Standard model not supported.

SAP Note: 2189708: List of supported and

Not supported Add-Ons

https://launchpad.support.sap.com/#/notes/0002189708

Any customer tried this

3 of them so far:

  1. Fairfax Media Interview: https://www.facebook.com/HANAbySAP/videos/1263550880335403/
  2. ConAgra
  3. Colgate customers


Faifax early adoption of BW/4HANA:

http://www.asugnews.com/article/early-adopter-fairfax-media-on-running-sap-bw-4hana-on-aws

What’s the Licensing framework for BW/4HANA

Licensing will be driven by the factor that how is BW/4HANA deployed.

We have 2 options:

  1. Cloud-based: Licensing will be based on subscription and Instance type selected (AWS/CAL)

  2. On-premise: Licensing will remain as the existing stnd process for SAP Applications.

Excerpt from BW/4HANA Master Guide:

License.png

BW/4HANA Master Guide:

http://help.sap.com/download/bw4hana10/SAP_BW4HANA_Master_Guide_en.pdf

Can I get a look and feel

Couple of “Try Now” versions are available on AWS:

  1. BW/4HANA XL edition
  2. BW/4HANA 1.0 Developer Edition


XL Edition:
https://cal.sap.com/subscription?sguid=0ebabe2b-6da4-40cb-905b-00a4d5ba281a

Developer Edition
https://cal.sap.com/subscription?sguid=217bd04e-53c2-453c-80a9-40fefe0137f8

Any online demo I can see this product in action

SAP BW/4HANA Demo

by Ian Kimbell and Ulrich Christ

http://events.sap.com/sap-amazon-web-services/en/home

  -> Video Highlights

       -> SAP BW/4HANA Demo by Ian Kimbell and Ulrich Christ

Does it have Early Adopter Pgm to help transition to this brand new product?

Yes.

SAP provides an Early Adopter Pgm. Salient features of this pgm:

  1. Early Adoption expiry: March 7, 2017
  2. Direct access and interaction with Development Team.
  3. A dedicated Project Coach will also be assigned at no additional cost

  How to register: 

  1. Go to https://influence.sap.com/BW4HANA10
  2. Register



http://scn.sap.com/blogs/BW4HANA_EAC/2016/09/14/early-adopter-care-program-for-sap-bw4hana-nomination-period-open

Planned features
  • Q3/2016:
    Multi-temperature data management.
    Cloud deployment on either HEC or AWS.
    Copy complete data flows
    Automatic generation of HANA optimized BW objects
    Conversion of DB Connect Source Systems to HANA Source Systems

9 - planned features - Q3-2016.png


  • Q4/2016:
    New HANA optimized business content.
    New ODP DataSources.
    Interoperability with Big Data (such as Hadoop)

10 - planned features - Q4-2016.png


  • Q2/2017:
    Transformation modelingWeb-based process chain monitoring
    HANA Vora integration with HAP
    “1-Step” conversion based on tool support and AGS service

11 - planned features - Q2-2017.png

  • Future:
    Tighter integration with Big Data
    Power Designer Integration
    Further Cloud Integration

12 - planned features - Future.png

How is Big Data &

IoT supported

IoT is supported in BW/4HANA via Smart Data Streaming (part of EIM)

Big data is supported in BW/4HANA via Smart Data Integration (part of EIM)

Certification for BW/4HANA Not yet available
Pictorial Summary 13 - Pictorial Summary.png
How does it fit together with S4HANA

Firstly, SAP BW/4HANA is completely independent of and not a prerequisite for SAP S/4HANA and vice versa.

S4HANA – Primary use case is operational reporting on current data from single SAP system.

BW/4HANA – Primary use case is Datawarehousing which provides consolidation (SAP + non-SAP + Big Data) and historical analysis

What about Stnd extractors from S/4HANA flowing into BW/4HANA

The following will apply :

  1. All new planned SAP standard content extraction from SAP S/4HANA to SAP BW/4HANA or SAP BW , powered by SAP HANA will be based on CDS delta extraction technology
  2. New Business content in SAP BW/4HANA and SAP BW , powered by SAP HANA will be aligned with SAP S/4HANA embedded analytics virtual data model structures (VDM)
  3. All extractors not blacklisted (SAP Note 2333141 -SAP S/4HANA 1610: Restriction Note) are enabled for SAP BW, powered by SAP HANA and SAP BW/4HANA (restrictions applicable)
  4. All custom developed objects for extraction have to be verified and adapted to the new SAP S/4HANA relevant structures

14 - S4HANA Extractors in BW4HANA.png

The future

Behold !

15 - The Future.png

It would be a good idea to follow the BW/4HANA SCN Space for all the future updates and Information:

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

Happy Learning !

————————————-

Source|Referenced Links:

Context | Topic Link
What is BW4HANA http://scn.sap.com/community/bw-hana/blog/2016/08/31/what-is-bw4hana
Technical overview http://go.sap.com/documents/2016/08/62147c09-877c-0010-82c7-eda71af511fa.html
Help.SAP Link http://help.sap.com/bw4hana10
Master Guide http://help.sap.com/download/bw4hana10/SAP_BW4HANA_Master_Guide_en.pdf
SCN BW/4HANA Space http://scn.sap.com/docs/DOC-74554
Application Developer Guide http://help.sap.com/saphelp_bw4hana10/helpdata/en/31/d619bba62d4519a1b54f6b290132d3/frameset.htm
BW/4HANA FAQ http://go.sap.com/documents/2016/08/c4458a08-877c-0010-82c7-eda71af511fa.html
BW/4HANA FAQ – John Appleby http://www.bluefinsolutions.com/blogs/john-appleby/august-2016/the-sap-bw-4hana-faq
SAP BW/4HANA Roadmap http://go.sap.com/documents/2016/08/740d6709-877c-0010-82c7-eda71af511fa.html
Road to BW/4HANA http://go.sap.com/documents/2016/08/5ccf0908-877c-0010-82c7-eda71af511fa.html
Marc Bernard’s Blog

https://blogs.saphana.com/2016/09/07/the-road-to-sap-bw4hana-part-1/

https://blogs.saphana.com/2016/09/18/the-road-to-sap-bw4hana-part-2/

Product Launch http://events.sap.com/sap-amazon-web-services/en/home
Early Adopters Pgm Early Adopter Care program for SAP BW/4HANA: Nomination period open
Data Modeling with BW/4HANA http://scn.sap.com/community/bw-hana/blog/2016/09/07/data-modeling-with-bw4hana
TSN – The new face of BW Req ID #TSN – The new face of BW Request ID
Facebook Post Video https://www.facebook.com/HANAbySAP/videos/1263518537005304/
SCN Blogs http://scn.sap.com/community/bw-hana/blog/2016/09/11/launch-of-sap-s-next-generation-data-warehouse-bw4hana
S4/4HANA and BW/4HANA positioning: http://go.sap.com/documents/2016/08/04aa9909-877c-0010-82c7-eda71af511fa.html
To report this post you need to login first.

47 Comments

You must be Logged on to comment or reply to a post.

  1. Franziskus Heep

    Hi,

    ist that mapping of new objects corresponding to old ones and the mapping of the frontends concerning the differnce between an old version of BW and BW 7.5 or the difference between BW 7.5 and BW/4 HANA

    (0) 
    1. Debanshu Mukherjee Post author

      Hi,

      Good question.

      Actually, it’s the mapping between the old way of designing Vs new way of designing.

      Until the BW on HANA versions, both old and new objects are supported (including creation)

      On compatibility mode version (formerly known as BW, edition for HANA), both old and new objects are supported, with an exception that old objects can no longer be created. Only existing old ones are tolerated to be there and continue functioning.

      BW/4HANA version – Existing old objects not tolerated at all. You have to first transfer old object to new ones and then switch to BW/4HANA.

      Hope that answers your question.

      (0) 
  2. Nikhil Anand

    Great Stuff Debanshu. I think BPC is currently not supported on BW4HANA neither Standard nor Embedded but there might be plans for it. There is no NW footprint in BW4HANA so if ever BPC is supported it will be a new product.Also BW4HANA is a new product and hence it has no predecessors.

    Cheers

    Nikhil

    (0) 
  3. DEVJEET HENSH

    Very detailed and Informative Article Debanshu. This is very exiting time for us SAP Folks, with so many new products like S/4, BW on HANA and now BW4/HANA being launched.

    So It’s always helpful to get such detailed overview articles. Please keep up the good work by updating it whenever you can.

    Thanks,

    Devjeet Hensh

    (0) 
  4. Trinath Kotapati

    Very fist statement:

    Just like S/4HANA, it’s a new DataWarehousing product, created only to work with SAP HANA

    What does this created only to work with SAP HANA means? It could be read as BW/4 HANA created only to work with S/4HANA. I understand it can have both sources: SAP ECC Netweaver and S/4HANA, but more aligned to work with S/4HANA.

    (0) 
    1. Garnet Umali

      Hi Trinath,

      Good point. It can definitely be read from umpteeen point of views.

      However, by – created only to work with SAP HANA – what I meant was that BW/4HANA software can only sit on top of HANA Database. It doesn’t support other databases, such as Oracle, DB2 etc, to be it’s primary persistence layer.

      W.r.t the source systems, I already mentioned that it can talk to both SAP and non-SAP sources.

      Hope that answers your question.

      Reg

      Deb

      (0) 
  5. Aswini Kumar Kalujualapati

    Hi Debanshu,

    Really helpful document. Can you throw some light on the following:
    –> Is there a need for a customer in SAP BW 7.5 on HANA to move to SAP BW/4HANA (What are the key factors why he should move)
    –> What are enhanced Infoobjects ?

     

    (0) 
    1. Debashu Mukherje

      Hi Ashwin,

      Firstly, apologies for such a late response…actually, I haven’t been able to attend to my blogs recently due to travel and other committments.
      So let’s tackle your questions:

      –> Is there a need for a customer in SAP BW 7.5 on HANA to move to SAP BW/4HANA (What are the key factors why he should move)
      Key Factors:
      1. Integration with Big Data (Hadoop) natively. Trust me, in coming years, everyone will need to handle big data..so sooner the better.
      2. Plugged in for all latest innovations in BW world. The old world will be supported but till certain time and will very minimal innovations.
      3. Integration with Fiori and Mobile applications natively.
      4. Integration with IoT.
      5. Automated data lifecycle management
      6. Web enabled administration and monitoring user interface.

      –> What are enhanced Infoobjects ?
      By enhanced means that now Infoobjects will have additional properties such as XXL. These can store additional information for a characteristic as data type STRING or XSTRING.

      Hope that helps.

      Reg
      Deb

      (1) 
  6. Mahadev Prasad Hulikul

    very useful debanshu..all in one place.

    -> if a customer is using EP for accessing reports , what would be the possible migration approach when they move from 7.x to BW4HANA as the B4H has no JAVA stack?

     

    (0) 
    1. Debashu Mukherje

      Hi Prasad,

      This is a great question and to tackle this one, let’s break it down;

      If a customer uses EP, then they must have enabled iViews or similar templates to show reports in EP. Now, these reports must be created as Bex Queries in the backend.

      If the above statement is true, then, unfortunately, Bex is no longer supported. However, migration might be supported. The replacement for Bex Web is Business Objects Cloud or Design Studio / Lumira 2.x and replacement for Information Broadcasting is Crystal reports.

      Here’s the clear-cut direction from SAP:

      https://blogs.sap.com/2016/10/13/sap-business-explorer-maintenance-support-policy/

      Hope that answers the question.

      Reg
      Deb

      (0) 
  7. Marcus Preis

    Excellent work.

    Very curious how the customer base will take it, since it is still (maybe more than ever) confusing to draw a clear SAP BI analytics roadmap. Especially if you are more an SME and are not ready for experiments.

    But following with greatest interesst 🙂

    Best + Thx,

    Marcus

     

    (0) 

Leave a Reply