One of the most striking differences between BW and BW/4HANA is data modeling. On one hand, there is less but more versatile objects to choose from (see figure 1). On the other hand, there is a new, more intuitive alternative to BW's long standing admin workbench (RSA1), namely the Data Flow Modeler (see figure 2). It shows physical and virtual containers (like DSOs or composite providers) as boxes. Data transformations, combinations, transitions etc. are indicated as directed lines between those boxes. From those boxes and lines it is possible to access the respective editor for those objects. In that way, a DW architect can navigate along the paths that the data take from entering the system towards the multidimensional views that serve as source to pivot tables, charts and other suitable visualisations. This is not only great for the mentioned DW architect but also allows for rapid prototyping scenarios, e.g. when a DW architect sits down with a business user to quickly create a new or modify a given model. Figure 3 shows an example.

Figure 1: Less and more logical objects when architecting a DW with BW/4HANA.

Figure 2: The new Data Flow Modeler in BW/4HANA.

Figure 3: The same scenario, once in the traditional admin workbench (left) and BW/4HANA's Data Flow Modeler (right).

This blog has also been published here. You can follow me on Twitter via @tfxz.

SAP has recently launched BW4/HANA for running a real-time digital enterprise, you can see the replay of the event here . I was privileged to witness the event live in person. Thanks to SAP blogger team for the invite. In this blog , I would like to share the experiences and the information I have learnt about SAP BW4HANA during the event.

     In Today’s digitally competitive world, SAP launches BW4HANA new product (not a legal successor of any existing SAP Business Warehouse solution) to address the needs of data explosion and to effectively manage & use the data to transform your business in a simple and modern fashion. You can see the evolution of SAP's data Warehouse over the years shared by SAP below:

General Availability of the product is from September 7,2016. For more information have a look at here

What are the design principles?

     We have data everywhere coming in different source systems like Social Media, Sensors, Legacy systems etc.., and with the increase of new demands like real-time, flexible analytics there was always a need of modern data warehouse. BW4/HANA is natively written on HANA (and runs only on SAP HANA ) with driving goals of Simplicity, Openness, Modern Interface and High Performance. Below diagram shared by SAP depicts the same.

(a) Simplicity:

There is a drastic reduction in the number of different object types in BW4HANA as depicted in the image shared by SAP below:

Due to the decrease of persistence layer it will solve many consistency issues, which further result in reduction of layers, total memory used, total lines of code and ultimately reduction in TCO.

In addition it also supports advanced multi-temperature management option with which BW4HANA knows the usage of data in the tables and categorises them accordingly i.e. hot store (active data ) and warm store ( not so active data) to effectively utilise the memory as shown by SAP below:

(b) Openness:

To give the user the option to manage both SAP and non-SAP source systems and access the models via SQL interface.

BW4/HANA Models can be exposed as HANA views in HANA system and also vice-versa is possible. With these capabilities, it means there is no need to replicate the data between the systems and supports any native SQL data warehousing approach which is very important considering customers comprising users and engineers from different SQL backgrounds to ease the usage of BW4/HANA.

(c) Modern UX:

They have further simplified the access for every user by giving new intuitive UI’s for all the users as shown by SAP below:

As shown in a live demo during the launch of an example business which sells the bikes and the business wanted to launch a new marketing campaign. To select the targeted audience the topologic & demographic data which resides in HADOOP. The Demo showed the ease of connecting with HADOOP and flexibly changing the data model to gain additional insights of data to have a better marketing campaign to make business better.

(d) High Performance:

     With HANA being the driver of the product strategy, High Performance in BW4/HANA is always given priority with unified data load management approach and supporting high frequent data loads in real-time. The Algorithm pushdown to HANA and also to minimize unnecessary overheads to the performance while trying to connect with data on Hadoop to HANA were taken care in BW4/HANA

AWS Collobaration with BW4HANA:

It has been a long partnership of AWS with SAP which helps to increase speed by using quick start guides to quickly install SAP HANA or to Scale up the systems in matter of minutes or hours. Which will help them customers to innovate faster and also thereby reduce the costs. And if by any chance the intended POC’s do not work as expected they can easily scale down as well. The recent launch of X1 system for HANA has an improved scale up and scale out w.r.t memory as shown by SAP below:

What does customers say?

     As quoted by Berndt during the launch event, SAP already has close to 4000 customers using BW on HANA , As I was present during the launch I also witnessed 3 customers Fairfax Media, ConAgra & Colgate customers views on how BW4/HANA benefitted them.

     Diego Lombardino, Head of Finance from Fairfax Media, describes the importance of real-time availability of the reports for their business users to be more self-serve and quotes an example of how it is important for their business users to not only know how many users read a web article but also what advertisements they have found interested and clicked up on. He also mentions about the benefits of using cloud like easy to setup, scalability (from 244 GB to 2 TB) and agility are the reasons to use AWS instead of on premise system

     Andy Xydakis, VP of Business Applications from ConAgra Foods mentions the ease of moving 4 TB of production data to AWS in 10 hours. He focusses on simplification of the analytics environment being the major benefit of implementing BW4/HANA on AWS

     Declan Roche, Director of IT Analytics from Colgate Palmolive speaks about flipping 80/20 rule & spend more time with customers on opportunities than building plans along with speed being the major benefit of implementing BW4/HANA.

How to migrate to SAP BW4/HANA and further Road Map?

For Customers on BW 7.5 Powered by HANA,must have already benefited from performance improvements, reduced data layers and simplifications based on the consolidation of modeling objects.Though BW 7.5 will be supported , BW4HANA may receive more upcoming innovations and developments.

It is fairly a simple conversion to SAP BW4HANA via transfer tool,  which will enable them to receive further innovations like simplified Big data access or more modern UX.

For Customers on BW 7.3 or 7.4 , SAP recommends to upgrade to BW 7.5 and then apply the add-on for further moving to BW4HANA..

For Customers on older versions of BW on other Db have an option for fresh green field implementation depending on the use case or can choose to upgrade to BW 7.5 and further move to BW4HANA

The same is illustrated by SAP  which suggested 3 Paths for migration to SAP BW4/HANA depending on your existing landscape as shown by SAP below :

From the launch on September 7,2016 customers can expect continuous innovations and incremental for the product and its maintenance ( like new choices for cloud. Modern UX, Performance etc.,) . Details on further Road map can be found here:

SAP BW/4HANA Roadmap

SAP BW/4 HANA - Technical Overview

Addons support: Have a look on this SAP Note 2189708 to check what add-on's are supported on SAP BW4HANA

What is the overall impact S/4HANA+ BW4/HANA impact on landscape? :

With the launch of S/4 HANA, BW/4HANA the new possible landscape shared by SAP looks like below:

With the power of HANA operational reporting can be handled via S/4 HANA but if you want to have the historical analysis or connecting multiple data sources coming in different formats BW4HANA will be very helpful. Which was depicted by SAP as shown below:

     It has been a wonderful event and it was a pleasure to see the special shutouts to all the delivery partners and especially the company I work for i.e., Infosys which has already proven its implementation experience by serving different customers globally

Some Important links & References:

BW/4HANA Website

Data Warehousing

SAP BW4/HANA FAQ

SAP AND AMAZON WEB SERVICES SPECIAL EVENT SAP AND September 7th 2016 | sap-amazon-web-services</title></head&…

Hoping that my blog helps you to understand about BW4/HANA and brings you a 1 step closer in your journey towards next generation data warehouse i.e. BW4HANA.

Yours

Krishna Tangudu

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. You can follow me on Twitter via @tfxz.

Greetings,

We are all aware of the rapid and disruptive changes in the BW world due to the new wave...called SAP HANA Platform...and the latest edition to the HANA stack is BW/4HANA...which is claimed to be the vanguard datawarehousing solution bridging the gap between Enterprise data and Big Data and enabling real-time analytics on top of this data...you can read more about BW/4HANA..here(bw/4hana).

One of the striking features of the new BW world is the new form of Request ID, called tsn (Transaction Sequence Number). The Baton has now been passed on from our well-known REQUEST to REQTSN...

Here's a glimpse of the new shape and form:

New Manage screen :

Grouping by Calendar or Request List:

Here we can see that new Req TSN has format: <YYYYMMDD HH:MM:SS> <Number>  <Timezone>

We can filter by either time or Status:

We also have Historical View:

Much more to come. It feels like learning a whole new product !

Happy Learning !

Greetings,

With the release of BW/4HANA, there has been a lot of fuss and confusion w.r.t the differences between:

BW on HANA

BW, Edition for HANA

BW/4HANA

and a lot of people are still not sure and needs a clear-cut, lucid answer without any verbose mumbo-jumbo, and I, personally, belong to this group.

Therefore, in this Blog, I have attempted to put things in perspective and to provide a clear and crisp answer.

I realize that in a technical world, things change at a rapid pace and if you find a fallacy in any of the facts I have provided here, I would request you to

correct me right away and I will have no issues standing corrected. I also have few things to get confirmation on and I invite others to fill in that gap..after all, this is how we all learn.

Here we go..

Modeling Differences:

SAP Notes referred:

Happy Learning !

This blog is the second in a series of three. Part 1 can be found here:"BW on HANA … Now What?" (Part 1 of 3).

As promised in the previous blog, in this blog I will present a stepwise approach to move towards the better SAP BI world described before.

Step 0: Migrate to HANA database

You already took this step, otherwise you wouldn’t have been attracted by the title of this blog. Am I right? (If not, contact me. I can arrange a discount ;-) .) As I said earlier, you will gain a factor 3 performance increase on average just by taking this step alone. You may be disappointed in the performance increase after migration for queries you already put a lot of effort in with “old school” methods such as aggregates and hot caching. Why is that? Because the old tricks also worked. But they took a lot more effort and maintenance.

Step 1: Use new (virtual) BW objects

Now that you have a high version of SAP BW software available, you can make use of the new BW objects: Advanced DataStore Objects (ADSOs), Open ODS Views and Composite Providers. Open ODS Views and Composite Providers are virtual, ADSOs are persistent. ADSOs and Composite Providers are combinations and simplifications of “old school” BW objects. With Open ODS views and Composite Providers you can build 100% virtual “data flows” in BW.

After migration, you will probably introduce the new objects in newly built data flows and data flows to be redesigned for some reason. You may even launch an optimization project aimed at replacing old objects by new ones in existing data flows …

Step 2: Pilot for Native HANA

… but in parallel you can explore the possibilities of Native HANA by starting a pilot project. To demonstrate potential business value, choose a reporting area that benefits strongly from real-time reporting functionality, and that does not require broad and complex data-integration. The pilot will get your organization acquainted with all the new backend and frontend technology and will demonstrate the added value that Native HANA may have for your organization.

Step 3: Mixed architecture BW/ Native HANA with BW in the lead

Once your Native HANA pilot project is finished, you basically obtained a mixed architecture of BW and Native HANA data flows in your data-integration platform. Nothing wrong with that. However, you should not confront your reporting users with different frontend tools for the different backend

scenarios. With BW still being dominant, it makes sense to have BW in the lead for frontend tooling. The Composite Provider objects makes it possible to combine persistent and virtual objects with Native HANA Views in one report. Below, this is displayed graphically. If the Native HANA data flow ends with one final step to a BW Composite Provider, users can still apply the frontend tools they are accustomed with to disclose the Native HANA data.

Step 4: Mixed architecture BW/ Native HANA with Native HANA in the lead

At a certain point in these developments, BW may cease to be dominant in your data-integration platform. This is the time to consider moving to frontend tools better suited or even specifically designed for Native HANA. In the SAP portfolio Lumira and Business Objects (BO) Cloud currently fall into this category. The integrating backend object for this scenario is the “Generated HANA View”. See picture below.

It is tempting not to take this step too early, as the before mentioned frontend tools are still under construction. Currently, the BW-based frontend tools offer more functionality and stability.

Step 5: Fully Virtualized Native HANA data-integration platform

A final step could be … abandoning BW altogether. A sad step this could be for a lot of people, for example … me. Sob. However, remember the “horror of data loading” as described in the previous blog, straighten your back, and just go for it!

Seriously, you may not get to this final step. But at least there is a clear roadmap of “next steps” following successful “previous steps”. You may need to slow down every once in a while to wait for SAP’s technology to become more mature. But I have confidence in SAP’s proven innovative power. Fully virtualized data integration is not a theoretical concept. It is doable, and sooner than we think.

Follow-up

Abandon the classical data warehouse. Or not? As noted previously, in certain situations data persistency in the data-integration platform is still required: historic data, “snapshots” and data from systems without direct access coupling. I will address this in more detail in the next blog, along with topics like the new BW objects, frontend tools, programming in Native HANA and any topics that you would like to propose. Just post your suggestions in the comments below.

The author works as Principal Consultant SAP Business Intelligence for Experis Ciber NL: http://www.ciber.nl/

With the introduction of the BW Modeling Tools, a new development environment for BW metadata objects was provided. The first editors which were shipped for the HANA CompositeProvider and the Open ODS view were released for SAP NetWeaver BW 7.4 SP5 in 2013. With BW/4HANA, the BW Modeling Tools become the major set of tools for the maintenance of BW objects.

This blog provides some hints and tips regarding the installation and configuration of the BW Modeling Tools. Please find detailed information about installation in the corresponding guide http://service.sap.com/~sapidb/011000358700001144122013E.
A short description of the required installation steps can be found in the following note: http://service.sap.com/sap/support/notes/1954169

The BW Modeling Tools represent a state-of-the-art development environment based on Eclipse. In general, the BW Modeling Tools can be installed in two ways:

• SAP Support Portal   (https://support.sap.com/software.html)
  Please note that you need   a user account to access this web site.
  To display a list of the available   versions, go the SAP download center and search for “BW MODELING TOOLS”. To   make sure you get the latest version, please pay special attention to how the   version numbers are handled, where Release 1.8 is older than 1.15 for   example.
  Important: In general we recommend using the latest   available version.
  As mentioned in the installation guide, you also need to   download the SAP HANA Studio and the ABAP Development Tools for this kind of   installation.
  
  
• SAP Update Site   (https://tools.hana.ondemand.com/)
  Using the update site allows   you to install the BW Modeling Tools directly on a plain Eclipse. All required   dependencies will be resolved automatically.
  Please note that you do not   require a user account to access this web site. The software will be provided   under the terms of the SAP Developer License.
  From the functional   perspective, there is no difference in comparison to the version on the SAP   Support Portal. It’s important however to know that there might be a delay in   the shipment of new versions. A new version will always be provided on the   support portal first. The version will generally then be available on the   update site two to three weeks later.

Target folder for installation

Before starting the installation, consider which location to install it to on your computer. In Microsoft Windows, you should not use standard folders, such as C:\Program Files. Due to the authorization handling of Microsoft Windows, using these folders can cause negative side effects and can prevent you from using the BW Modeling Tools.
If you install the BW Modeling Tools into a non-standard folder like c:\tools\BWMT, you also have the advantage that all installed components are directly available in this one folder. You can therefore copy the content of this folder to another computer and use it without installing. This is also a great option for distributing the BW Modeling Tools within a company.

Installation steps

As mentioned before, the installation process is described in detail in the installation guide. There are also some very helpful installation tutorials available on YouTube.

For installation using the download package from the SAP support portal, please see the following two tutorials on YouTube:
Part 1: https://www.youtube.com/watch?v=8d-v57ttxcM
Part 2: https://www.youtube.com/watch?v=Jfo-kKOy6ow

For installations using the SAP update site, please see the following tutorial:
https://www.youtube.com/watch?v=z0Gfgqflxmg

Multi-user environment

Eclipse can also be installed in multi-user environments. In this case however, you need to adjust the configuration handling. The configuration details, the used workspace for example, will be stored by default in the “configuration” subfolder of the installation folder. In a multi-user environment, this would cause file access collisions. To solve this problem, you need to add the osgi.configuration.area parameter to the “configuration\config.ini” Eclipse configuration file. By adding osgi.configuration.area=@user.home/hdbstudio.config for example, Eclipse creates a local configuration file called hdbstudio.config for each user in the corresponding home directory.

Further details and possible scenarios can be found on the Eclipse Help site (help.eclipse.org) by searching for "Eclipse Multi User Installs". Note http://service.sap.com/sap/support/notes/2252199 also provides information about installation into multi-user environments.

Default workspace

To work with Eclipse, a workspace has to be selected. This folder will contain details about metadata information, projects and so on. Especially in the case of distribution to multiple users within a company, it can be important to adapt the default workspace to meet company requirements.

This setting can be found in the “configuration\config.ini” configuration file in the installation folder. By changing the existing entry osgi.instance.area.default, you can change the location of the default workspace.

Language-dependent UI texts

The BW Modeling Tools generally only supports English UI texts. A set of German texts is also shipped with the product however. By default, Eclipse takes the locale settings from the operating system. If you are using a German locale on the operation system, the BW Modeling Tools will therefore automatically switch to German texts.
This default handling can be changed by setting a parameter in the Eclipse INI file. The UI texts can be fixed as English by adding the following line to the “eclipse.ini” file at the end:
-Duser.language=EN
This line can actually be added at any position after “-vmargs”.

If you are using a HANA Studio installation (already includes Eclipse), please note that the INI file name is not “eclipse.ini”, but “hdbstudio.ini”.

Updating the BW Modeling Tools

The steps for updating the BW Modeling Tools are straightforward. Adjust the available update sites in Eclipse or HANA Studio and run “Check for Updates”. The configuration details for this step can be found in the installation guide.

Please note however that performing an update will not remove older versions from the file system. If you perform multiple updates, this results in multiple versions of the corresponding feature on the file system and an increase in the disk space required. At runtime however, only the latest version is used.

Bearing in mind that updates of the HANA Studio and the ABAP Development Tools are not required that often, a good strategy might be to prepare a basis installation with HANA Studio and ABAP Development Tools and the required Eclipse features.
Before the BW Modeling Tools are installed, now create a copy of the current installation folder and keep this one as a backup. As soon as a new version of the BW Modeling Tools is available, just install this new version on top of the backup version. This way, the installation directory will not grow over the time.

With this in mind, please note that the update will not install any new features. If a new version of the BW Modeling Tools provides a new feature, it is still necessary therefore to use the menu entry Help -> Install New Software….
Please check the release schedule note for an overview of the released versions: http://service.sap.com/sap/support/notes/1944835

For anyone out there, wishing to install and explore the EPM Demo on B4/HANA, take a quick look below

This pertains to the SAP B4/HANA 1.0 [Developer Edition] in the SAP CAL

I have not had a chance yet to test on other versions

FYI: This story does not have a happy ending

In short, I found 4 missing InfoObjects that will fail the complete activation, and give errors

If you get to the end in your efforts, and can find a way around, do let me know

What's in the box

Eclipse

Neon with BW Tools v1.15.2

Active InfoAreas

Active DataSources

BW

no BWDEVELOPER user, have to use user DEVELOPER

In eclipse use the Project "BW_A4H_001_developer_en_1"

no RSA1 - Modelling option, have to use Eclipse

SYSTEM->STATUS

License will run out after three months, and can be extended through the usual way

Example of transaction no longer support - RSD1

INSTALL BI CONTENT 0EPM_CONT_DELV

RSOR - BI Content

Choose Source System, and continue to find 0EPM_CONT_DELV - currently installed (not activated)

When collected for installing you may see the following immediate errors

This is due to the following InfoObjects not existing anywhere in the system

0D_NW_PCURR

0D_NW_PUNI

0D_NW_PRCUR

0D_NW_STUNI

They are required for some other 0EPM_CONT_DELV InfoObjects

"install", without need to change any further options

4 minutes later

Errors have occurred

New InfoAreas, i.e. 0EPM_CONT_DELV, under 0BWTCT, now visible in Eclipse

Under Key Figures, see the outcome of the missing InfoObjects

Amongst the objects which erred is Key Figures 0EPM_GAMT. It depends upon one of the missing InfoObjects, 0D_NW_PCURR, and is why the error occurred

The next task is to create new custom InfoObjects, for substitution the missing ones.

ZDNWPCURR will replace 0D_NW_PCURR Order Currency

ZDNWPUNI will replace 0D_NW_PUNI Order Unit

ZDNWPCUR will replace 0D_NW_PRCUR Product Currency

ZDNWSTUNI will replace 0D_NW_STUNI Standard Unit of Measure

In Eclipse, create a new InfoArea to organize custom objects

r/click over the BW Repository InfoArea area, and choose, New -> InfoArea, and create

r/click over the new InfoArea, and choose New -> InfoObject… and create

Create InfoObject Unit ZDNWPCURR and Activate

IMPORTANT, due to a bug, try this

In BW, navigate to RSOSM– “Use BW Search on SAP HANA”, enter the InfoObject name, and execute the search.

If nothing is found, perform these steps.

In Eclipse, under the InfoObjects Dictionary area, change the Unit Type from the existing “Currency” to “Unit”, Activate, and back to “Currency”, and Activate.

In BW, perform the search again, and it should be found.

Continue on with the remaining InfoObjects

Create InfoObject Unit ZDNWPUNI and Activate

Create InfoObject Unit ZDNWPCUR and Activate

Create InfoObject Unit ZDNWSTUNI and Activate

Refresh the InfoArea, and all should be visible

Adjust Key Figures

Now substitute the missing InfoObjects with our custom InfoObjects for all the following Key Figures

0EPM_GAMT

Change  InfoObject 0D_NW_PCURR

To InfoObject ZDNWPCURR, and Activate

Do this for the remaining InfoObjects, taking care of the correct substitution

0EPM_NAMT use currency ZDNWPCURR

0EPM_PQTY use unit ZDNWPUNI

0EPM_PRICE use currency ZDNWPCUR

0EPM_TAMT use currency ZDNWPCURR

Adjust Characteristic

Also, the InfoObject Characteristic 0EPM_PRID requires adjusting

Attribute 0D_NW_PRCUR requires substituting for ZDNWPRCUR

Attribute 0D_NW_STUNI requires substituting for ZDNWSTUNI

Activation should resulting in the following

INSTALL TAKE 2 - BI CONTENT 0EPM_CONT_DELV

RSOR - BI Content

Collect the 0EPM_CONT_DELV once again, do not change, tick, or check anything, and "Install"

Fewer error messages, but an observation identifies the same missing objects are still getting in the way

A quick check will reveal the previously erred Key Figures are still ok, as you would expect, and have not been overwritten

In RSOR, I tried to activate, just the advanced DSO InfoArea 0EPM_ADSOS

Same errors occured

Then I tried to install an individual ADSO 0EPM_ADSO1

I did not receive the previous InfoObject errors, which I thought was promising

However, I was not able to see the objects in eclipse, to fix up or otherwise, so that pretty much leaves me out of options.

Previously, RSA1 -> Modelling, would be used to inspect the Object in error, for a possible fix or cause analysis. However, with eclipse, I cannot see the object, so it’s the end of my story, for now.

If you have had the same experience, do share, as I am sure there would be many out there, just like me, keen to see this working, so we can explore further.

Thanks

Glen

Steps to load 0IC_C03 - Material Stocks/Movements InfoCube in BW on HANA

1. In a small down time interval lock/stop all users/postings in ECC at that time.

         Eg: The day is 09-23-2016 @ 11:00:00 AM).

2. STOP V3 JOB’s for 2LIS_03_* DataSources in ECC.

3. Clear Setup tables, RSA7, SMQ1 in ECC and InfoCube data in BW.

4. Execute Tcode MCNB in ECC, under Data destination Info tab, select 2LIS_03_BX DataSource.

5. Under Data source Info select All Stock Including - non valuated stocks).

6. At the same time (parallel) use Tcode OLI1BW in ECC and give the Posting date range from 01-09-2016 to 23-09-2016. This is

   for 2LIS_03_BF Load.

7. And also you can perform another activity, use Tcode OLIZBW in ECC and give the Company code and Posting date range from

   01-09-2016 to 23-09-2016. This is for 2LIS_03_UM Load.

   If you have multiple company code, repeat the step 6 for all company codes using the same Posting date range selection.

   Note:

   Step 5 and Step 6 can also perform once the 2LIS_03_BX data load is completed, but to save and utilize ECC down time, we can

   do in parallel. It depends on person to person and project to project and also the length of ECC down time.

8. Once Step 3 job is completed in ECC then load the data to BW till PSA using InfoPackage using “Generate Initial Status”

   under Update Tab. This is for 2LIS_03_BX Load.

9. Once the PSA load is success then load data to 0IC_C03 Cube using DTP, before loading data, check the “Extraction” tab in

   DTP, under Extraction tab Extraction Mode = “Initial Non-Cumulative for non-Cumulative values”.

    Set this option in DTP and load the data into InfoCube.

10. No compression is required because it’s HANA, you can’t find “Marker update” option in 0IC_C03 InfoCube.

11. Quickly you can validate the data by comparing data using Tcodes in ECC MB52 or MB5B and simple BEx report.

12. Once Step 5 job is completed in ECC then load the data to BW till PSA using InfoPackage using “Initialize Delta Process, with       Data Transfer” under Update Tab. This is for 2LIS_03_BF Load.

13. Once the PSA load is success then load data to 0IC_C03 Cube using DTP, before loading data, check the “Update” tab in DTP, under     Parameters of the InfoCube tab, CHECK “Historical Transactions” for history loads, because we are loading history data from         1^st September 2016 to 23^rd September 2016 to set the DELTA pointer in ECC.

    No compression is required because it’s HANA.

    Note:

    Once you load all history data, then UN-CHECK this option for delta loads.

    Once Step 6 job is completed in ECC then load the data to BW till PSA using InfoPackage using “Initialize Delta Process, with       Data Transfer” under Update Tab. This is for 2LIS_03_UM Load.

14. Once the PSA load is success then load data to 0IC_C03 Cube using DTP, before loading data, check the “Update” tab in DTP, under     Parameters of the InfoCube tab, CHECK “Historical Transactions” for history loads, because we are loading history data from         1^st September 2016 to 23^rd September 2016 to set the DELTA pointer in ECC.

    No compression is required because it’s HANA.

    Note:

    Once you load all history data, then UN-CHECK this option for delta loads. 

15. Once data loads are completed then check the BW Data with MB5B/MB51/MB52 Tcodes in ECC, it will match.

16. To perform all the above steps in small ECC down time period, you must practice these steps in Quality/Test system prior

    to implement in Production system to avoid confusion and get confidence. And also validate the data in Quality/test system

    using different BEx report in BW and MB5B/MB51/MB52 Tcodes in ECC.

17. Once Delta Pointer is set in ECC then load all history data using the above steps or you can start delta loads,

    I prefer first load all history data in weekends and then continue DELTA loads.

18. After all history loads are done then schedule V3 jobs for 2LIS_03_* DataSources using LBWE Tcode in ECC and continue

    DELTA Loads in BW.

    Note:

    UN-CHECK “Historical Transactions” option in DTP for BF and UM DataSource delta loads.

Hi All,

Have a Good Day !!!!!!!!

ABAP CDS Views, which is S/4 HANA New and Advanced Modeling Object.

So many SAP documents and SCN links are available about

What is ABAP CDS  View?, How to create it?, It's Features and Benefits.

I have listed few links below for reference which will be useful to understand above things.

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

https://help.sap.com/abapdocu_750/en/abenddic_cds_views.htm

http://scn.sap.com/community/abap/eclipse/blog/2014/02/04/new-data-modeling-features-in-abap-for-hana

https://wiki.scn.sap.com/wiki/display/ABAP/CDS+-+Core+Data+Services

In S/4 HANA, We have Embedded BW also and We can use it Operational Reporting.

But We need one complete analytical suite in the following scenarios

i.       Multiple ECC Systems

         (Example: Separate ECC Systems for America, Europe and Asia Pacific)

ii.      If we have Data from Non-SAP Applications and Multiple Source Systems

          (BODS, 3rd Party Databases - Oracle, DB2, Teradata, MSSQL, ....)

iii.     To Maintain Historical Data

iv.     Extensive Analytical Reporting Usage

v.      Implement Planning Functions

For this above scenarios,

S/4 HANA System and BW on HANA - Both system needed in Enterprise Landscape.

(Ref: Open SAP - BW 7.5 Powered by HANA Course)

CDS views are Integration between S/4 HANA system and BW system.

There are two options available for BW and S/4 HANA Integration.

i.     Virtual data integration:  

          Create Open ODS Views (BW) directly on top of CDS views (S/4 HANA)

ii.    ETL load:

          Extract data from SAP S/4HANA to SAP BW using CDS Views via ODP source system type.

In this blog,

I am going to explain about how to integrate BW and S/4 HANA systems by "ETL load" method.

In S/4 HANA Source System, In-built ABAP CDS View are there for almost all the functionalities.

I have taken Simple ABAP CDS View Model - IMATTYPE (Material Type), Which have 7 records.

In this Integration exercise, This CDS View Output has to be extracted to BW on HANA system.

Steps Involved in ETL Load - Extraction Process:

1.      Data Flow diagram,

          which is explaining Extraction process between S/4 HANA system and BW on HANA System:

2.           Create New Source System (Source S/4 HANA) Under "ODP-ABAP CDS Views".

               In Connection Parameter, In Target Host Field,

               Enter S/4 HANA Application Server Host Name and Instance Number.

               In Log on Security - Enter S/4 HANA User Name and Password and Check the Connection.

               After Successful Connection, Save it.

               New Connection will be created and will be displayed under ODP - ABAP CDS Views.      

3.          In Data Sources Node, Create New Data Source on top of S/4 HANA CDS View – IMATTYPE

             Enter "IMATTYPE" in Operation Data Provider field and select the Type as Master Data Attr.

             Provide Data Source Name as "ZABAP_CDS_EXTRACT_01" and create and Activate it.

                 Data Source "Material Type ABAP CDS View Extraction (ZABAP_CDS_EXTRACT_01)":

4.           Load the data to this data source using Usual Info package execution.

              Verify the data in Data source against S/4 HANA CDS View output.

Source S/4 HANA - CDS View Output	Target BW - Data Source Output

.              

My Observations:

Few of My Observations from this Exercise,

i.            We can customize Existing ABAP CDS Views and create New CDS Views in S/4 HANA.

              This CDS Views also could be extracted same as above method.

ii.           In Source System, ABAP CDS views can be exposed to Bex Query and

              Operation Reporting will be created on top of BEx.

              Reference:http://scn.sap.com/community/bw-hana/blog/2016/02/10/expose-cds-views-to-sap-bw-bex-query-designer#comment-699890

iii.           In Virtual Data Integration (BW - S/4 HANA) Method,

               Two Systems are connected via HANA-HANA Smart Data Access (SDA) Connectivity.

               This ODP - ABAP CDS View Extraction is based on NetWeaver RFC Connectivity.

iv.          In this ETL Load BW-S/4 HANA Integration (ODP - ABAP CDS View Extraction),  

              In Info Package, Only "Full Load" Option is available. "Delta Load" Option is not available.

Thanks & Regards,

Muthuram