#BW4HANA Launch Demo

On 7 Sep 2016, BW/4HANA was launched in San Francisco. Videos from the event can be found on the event’s website. Especially the BW/4HANA launch demo has attracted a lot of attention. For further reuse – like embedding it into PPT – we have uploaded it to Youtube:

The demo is also available as a screencam:

More infos on BW/4HANA can be found here. The blog has been cross-published on SCN. You can follow me on Twitter via @tfxz.

PS: The demo has been shown also at SAP Teched Bangalore (5’33”, Oct 2016).


Real-Time Data with #BWonHANA

SommerblumeHere is a quick summary and a list of some useful pointers for customers requiring real-time data within BW. In general, there is 3 options:

  1. real-time (0 sec*) w/o any replication via transient or virtual infoproviders and / or infoobjects,
  2. real-time (1-5 sec*) via SLT replication,
  3. real-time (1-5 min*) via real-time data acquisition (RDA) enabled extractors.

Marc Hartz’s presentation on the options covers details on all these approaches. Let me add a few comments:

  • Approach 1. allows to report on any SQL-accessible table or view in HANA independent from the fact whether that table or view sits in the same schema as all the other BW tables or in any other schema of the same HANA instance or in any other DB server connected via smart data access (SDA). In that sense, it complements the table replication approach via SLT in 2.
  • Approach 2. has three flavours, namely
    1. replicating into a DB table sitting in the same HANA instance that sits under BW, or
    2. replicating into an ODQ (operational delta queue) which serves as a PSA, or
    3. replicating via a web service; with recent versions of SLT and the availability of approach b. this one should be mostly obsolete.

    Mechanism a. combines with approach 1. while b. and c. combine with RDA, i.e. approach 3., which exists since BW 7.0.

  • Real-time data acquisition (RDA) is supported by a number of standard extractors, e.g. see OSS notes:

Credits go to C. Dressler for compiling most of the details. You can follow me on Twitter via @tfxz. This blog has been cross-published here.

* This is the latency between the data being created and the data being visible in a report or dashboard.