Prototyping Your Scenarios with SAP BW7.4-on-HANA in the Cloud  – Piece of Cake with SDATA

You  heard about the exciting new functionality that is offered by BW-on-HANA especially with the latest feature package SAP BW 7.4 SP08(SCN or openSAP course).! And of course, you know of the easy way to get a free trial version of SAP BW7.4 SP08 on HANA! Now the big question is: how can you test your reporting scenarios with your data in such an environment? With the SDATA tool we have made exactly this extremely easy and comfortable!Read More...

New Query Designer in Eclipse with SAP BW 7.4 powered by SAP HANA
SAP BW 7.4 SP9 powered by SAP HANA comes with a first version of a query designer integrated in the BW-Modelling Tools (BWMT) in eclipse. With this feature it is now possible to define not only the InfoProviders of SAP BW 7.4 (Advanced DataStore Object, CompositeProvider, OpenODS View), but also queries with specific functionality in eclipse. Read the details in this blog from Marc Hartz.

Open Online Courses Delivered by SAP
How can you balance your busy work schedule, while learning how SAP innovations could potentially transform your business? With openSAP, of course! Whether you’re an SAP professional, developer, consultant, entrepreneur, professor or student you can keep up to date with the latest innovations from SAP.

Extended Storage and Dynamic Tiering

In his blog Thomas Zurek resolves the confusion around the terminology of extended storage and dynamic tiering within HANA. Further details can be found in a presentation attached to SAP Note 1983178.(SMP Login required)

See the recently featured content.

This is steps to create a SDA connection To Teradata with HANA Studio .

First you have to install Teradata Driver.

You have to download driver from Teradata Site :

http://downloads.teradata.com/download/connectivity/odbc-driver/linux

I already Tried with version 13, 14 and 15 of Teradata Driver.

The Doc here will talk about version 15 of Teradata Driver as it's supported now by SAP but it will be the same for Older Drivers.

to install the driver and all its dependencies please follow this steps :

1 Download :

tdodbc__linux_indep.15.00.00.03-1.tar.gz    (ODBC Terada Driver)

Teradata CLIv2 for Linux

(containing tdicu and TeraGSS required for Teradata to work properly)

2 login as root :

tar -xvf tdodbc__linux_indep.15.00.00.03-1.tar.gz

cd tdodbc

rpm -ivh tdodbc-15.00.00.03-1.noarch.rpm --nodeps

this will install Teradata Driver into /opt/teradata (without dependencies )

tar -xvf cliv2_LINUX_indep.15.00.00.04.tar.gz

cd TeraGSS/

rpm -ivh TeraGSS_linux_x64-15.00.02.01-1.noarch.rpm

cd tdicu/

rpm -ivh tdicu-15.00.00.00-1.noarch.rpm

now it's done with the Teradata drivers and dependencies

(even if the Driver's official documentation suppose that you don't have to add the driver path to $LD_LIBRARAY_PATH, it's recommended to add it manually to avoid any error message)

now we have to configure the .odbci.ini file in the <SID>adm /home :

Here how to the .odbci.ini file has to look like :

[ODBC]

InstallDir=/opt/teradata/client/15.00/odbc_64

Trace=0

TraceDll=/opt/teradata/client/15.00/odbc_64/lib/odbctrac.so

TraceFile=/usr/joe/odbcusr/trace.log

TraceAutoStop=0

[ODBC Data Sources]

testdsn=tdata.so

[testdsn]

Driver=/opt/teradata/client/15.00/odbc_64/lib/tdata.so

Description=Teradata database

DBCName=Teradata_server_ip

LastUser=Username

Username=Username

Password=password

Database=Teradata_database

DefaultDatabase=teradata_database

(Of course you have to change info with your own credentials ( teradata_server_ip, username, password, Teradata_database)

Now it's time to make test our configuration from Console Command  line

connecto to SSH with <SID>adm user

hdbsdautil -t tdodbc -S "dsn=testdsn" -U username -P password -info

if everything is working well so we just have to restart Hana (even if it's not mentioned in the Hana Official Documentation )

HDB stop

HDB start

Now we have to create the SDA rempte connection in HANA Studio :

Open Hana Studio and login in the System with user <SID>adm

Go to ' Provisionning" > Remote Source > New Remote Source

Done

Thank you

Purpose of documet:

This document provides details on tables to be referred and procedure to collect information related to Non BW objects (like includes, tables, methods, class etc) for transporting across different landscapes in BW (Dev to Quality to Production in a typical business scenario)

1.  Webdynpro

   To collect information related to webdynpro objects, go to Table WDY_COMPONENT to get the list of the Webdynpro Components

Go to Table WDY_APPLICATION to get the list of the Webdynpro application, Component, view names in detail

To refer any other details - Webdynpro tables starts with WDY* in SE11.

2. Transaction Codes

    To collect information related to transaction codes, go to Table TSTC & get the list of Transaction Codes.

3. BPS Objects:

Step 1:   Get the list of planning areas from UPC_AREAT

Step 2:  Run the program UPC_TRANSPORT_BPS_ALL

               Specify the option as “Full Transport” and provide planning areas we got from step 1.

Note:

It is always advisable to go for Full transport as BPS contains lot of dependent objects (Planning Levels, Packages, Formula Extensions (FOX), Variables, and Planning Sequences) and by choosing the option selective transport would result in non-collection of dependent objects under request. The objects will be collected as table entries under customization request

Drawbacks / Pain points / Suggestions for improvement:

The standard program accepts only one planning area and we can enhance this program (Create a custom program) to accept multiple planning areas to expedite the transport of BPS applications.

Normal programs:

To collect information on Normal Programs, Go to TADIR Table and mention Object Type = PROG

4. Customer exit

   To collect information on Customer Exits, refer table TADIR and mention Object Type = CMOD to collect custom exits that starts with Z.

5. BADIs:

To collect information on BADIs, go to TADIR Table & mention Object Type = ENHO (for implementation) & ENHS ( for Enhancement spot)

ENHO (for implementation):

ENHS (for Enhancement spot):

      6. Classes & Interfaces:

To collect information on classes and interfaces, Go to Table SEOCLASS and mention the Class Name (CLSNAME) & Class types (CLSTYPE) as 0 for Class & 1 for Interfaces

    7. Methods:

To collect information on Methods, go to Table TMDIR and Mention the Class Name in Object Type Name – for class and retrieve its respective methods

8. Tables/Structures/Views:

  To transport Tables Go to table DD02L& get the list of tables/Structures/views based on the entries maintained in field ‘TABCLAS’

9. BSP applications:

   To collect information related to BSP applications, go to Table SSCOOKIE to get the list of BSP Application

10. Function Module / Function Group:

   To collect information on function modules go to Table TFDIR to get the list of Function Modules

To collect information on function groups, go to Table TLIBG to get the list of Function Group

11. Includes:

    To collect information related to Includes, go to Table TRDIR à Mention Program Type as ‘I’ to get the list of Includes

Dear All,

I would like to share some of our finding during the BW on HANA Implementation project.

If you are planning for such project either Implementation or Migration you can refer this piece of information during your project.

We have come across below list of sap notes which was helpful during our project.

Project Technical environment

SAP BW 7.40 SP08

HANA SPS09 Rev 94

Please find the list of SAP Note :

I will keep updated this list with some more information.

Best Regards,

Atul Kumar Jain

Advanced DataStore Object or Advance DSO is introduced in SAP BW 7.4 SP8.It is introduced to simplify the SAP BW landscape.It is only available to use if you have HANA Database. It replaces all persistence infoprovider PSA, DSO, InfoCube and Hybridprovider.

The Advanced DSO,

• Supports InfoObject and Field based Modeling
• Support huge data as Data activation step at DB level instead of Application server as traditional method
• Can contains 120 Key fields (compared to 16 in standard DSO)
• Data Activation Step is speedup by 5 to 10 factor
• As column store data base, can be used directly in reporting and query performance is up to 100x.
• Can be modeled in the Eclipse-based SAP BW modeler

As we have done testing of data loading time and db size. We have seen tremendous query and data loading performance and reduction in size to store the data.

There are some new features are available into the SAP BW 7.4 on HANA like Composite InfoProvide, Planning application execution as DB level, query performance improvement and data loading performance.

Today we had an interactive Q&A webcast with SAP's Storm Archer and Brian Woods.  Special thanks to ASUG Volunteer Allison Levine for moderating.

ASUG Webcast: Migrating to BW on HANA: Interactive Q&A Session

Date:  Wednesday, April 08, 2015

________________________________________________________________

Q: if we have already archived on older technology (ADK and Open Text), how do we get the data back after upgrade from 7.0 to 7.4 BoH

A: Data that has been archived does not need to be restored unless there is some business reason, in which case if it is restored prior to the upgrade and migration, it will be available in the new 7.40 on HANA system. This can also be done in the case where you want to upgrade but are not yet ready to migrate to HANA. Note number 1652907 (next slide)

Source: SAP

________________________________________________________________

Q: We are planning to upgrade in next 2 months and stuck on archiving question. SO WHAT’S THE QUESTION?

A: We often recommend a NLS project along with a general “clean up” project prior to the Upgrade and Migration. Cleaning up any nonproductive objects, and moving static “Cold” data to NLS will reduce the RAM requirements for the HANA Appliance, and reduce the time for the upgrade and migration.

________________________________________________________________

Q: Can we migrate multiprovider to composite provider without loosing queries and query elements?

A: No, not currently.

________________________________________________________________

Q: As in the current stage, can the eclipse based UI do everything what can be done from the conventional modeling experience in app layer ? Anything which has been discontinued ?

A: The Eclipse based modeling tools do not provide All of the functionality of the traditional UI at this time. All new modeling objects and capabilities are being addressed by these tools, but we have not made an effort to migrate all existing functionality to Eclipse. Nothing has been discontinued at this point, and there are no immediate plans to do so.

________________________________________________________________

Q: If we upgrade to BW 7.4 SP8 (or later), but not yet move to HANA, what benefits will we receive -- or not receive?

A: Slide 38 in the Roadmap Session shows the new functionality added to SP8-SP9 and indicates which features are for HANA only, and which release the functionality was made available in. This is only the newest functionality, there are also slides like this for the SP05 features and functions which I can share during the Q&A session.

________________________________________________________________

Q: In the current Infocube/DSO world, the size of a DSO is about 4 times the size of a cube containing the same data (due to the sid's vs the native characteristics being stored). For ADSO's which are cube like is the size more like a DSO or a cube?

A: There are a number of considerations that go into the size. Depending on the type of data will affect the overall compression. The overall goal is to compress data where we can and improve overall performance.

________________________________________________________________

Q: If you create Bex query in BWMT can you change in Current Query designer?

A: The BWMT tools are used to create BW objects and elements stored in the BW system. When you create the Bex query, it is stored in the BW Schema and should be accessible for update inside the SAP GUI.

________________________________________________________________

Q: How these HANA / BW modeling are affected when it goes onto S/4 on HANA?

A: All BW Info sources should continue to function. It is not yet clear if the extractors will be modified, or if they will be replaced with Core Data Services (CDS), but while the mechanism may change somewhat, the result will be the same. As many of you know, this is not yet determined since the Suite/S4 HANA team will have to make the necessary modifications to ensure consistent data and harmonized data models between S4 and traditional Suite.

________________________________________________________________

Q: Does the cost of NLS comparable to HADOOP?

A: NLS sits on top of a data persistence technology. We believe that SAP IQ is the best technology for this, and accordingly our solution is based on this. We do have Partner solutions that are based on HADOOP, and I Would be happy to have a call to discuss the fully loaded costs of each if you like, but the summary is “Use the right persistence technology for the job”

________________________________________________________________

Q: where do we define which data goes to warm storage? is there any T Code?

A: For BW objects, the only objects that are available for this Warm Storage (based on Extended Storage/ Dynamic Tiering) are PSA and WO/DSO (Corporate Memory). The option is set when the InfoProvider is Activated. It is a check box on the modeling screen.

________________________________________________________________

Q:  Can you discuss how the ODP removes the need for the PSA?  Since the ODP is on the source system - what version/release is required in your ECC system to support the ODP?

A:  Not stopping at PSA layer to do transformation; PSA is a staging area not a corporate memory; ODP/ODQ structure can reside on source system or target or separate

________________________________________________________________

Q: Where can we find a list of NLS restrictions besides cannot being updated

A: There is an FAQ for SAP IQ based NLS http://scn.sap.com/docs/DOC-54468

________________________________________________________________

Q: Does SAP BW on HANA 7.4 support 3rd Party NLS Storage like Informatica NL Solution and will it have all the same capabilities that

will be available to SAP IQ?

A: Yes, we still support our partner solutions for NLS, it is up to the partner to decide if they want to be certified for any given release of

BW.

________________________________________________________________

Q: Note 2063449:Push down of BW OLAP functionalities to SAP HANA referenced in the presentation is not released to customers?

A: Note is released and available. Details of OLAP functionality and availability is listed some are available and other are planned or

under discussion.

________________________________________________________________

Q: What is required to transition a mature SAP BW installation on Oracle to SAP BW 7.4 HANA?

A: The upgrade and migration process is described in great detail (http://scn.sap.com/docs/DOC-46824)

and you will have a choice to either migrate the existing models as is, or conduct a project to rearchitect

the solution based on the current and planned BW on HANA capabilities (remove InfoCubes, reduce

layers, leverage new CompositeProvider, Open ODS View), and more generally the logical EDW concept

and federation based on SDA.

________________________________________________________________

Q: Once the data has been archived in HANA, how does the memory get freed up? In the past with

traditional databases, it is done through database reorg, how is it handled in HANA

A: To actually purge the data marked deleted (like after a NLS run), a delta-merge completes the process

in removing the data from the HANA Data log files.

________________________________________________________________

Q: Looks like SAP Note 2063449 not released, perhaps being updated

A: See above

________________________________________________________________

Q:  We are currently using the 3.x archiving method to archive our non cumulative Infocubes.

Will we run into issues with the archived non cumulative infocubes when we migrate to hana

A:  Expanded capability to handle non cumulative cubes.  Should not be a problem with new functionality.

________________________________________________________________

Q:  What is the Utility to convert from Multiprovider to Composite provider and can I download somewhere on marketplace

A:  No, Not currently. We have plans, but no ETA at this point. (updated 5/27/2015)

________________________________________________________________

Q:  When we are talking about Role based roll out of GUI, is this SAP Fiori ?

A:  Fiori is not a development GUI

________________________________________________________________

Q:  Do we have any NLS Project case studies? Where can I get it .

A:  The FAQ link is in the slides for NLS.  There should be some stories located there. http://scn.sap.com/docs/DOC-54468  

________________________________________________________________

Q:  What would be the benefits of utilizing dynamic data tiering and NLS vs. using something like a Hapoop for a cold data storage?

A:  Dynamic tiering is a capability of HANA, not Hadoop.  This dynamic tiering is using disk based tables in HANA.  That is the same technology used in Sybase IQ.  You can use it but you will need to write the application do make this happen.

________________________________________________________________

Q:  does the SAP NLS solution have any advantages over the partner solutions?

A:  Yes.  SAP can take advantage of new featuers in HANA and BW much more quickly than partners. For example, able to use proxy tables to speed up processing of NLS queries by a factor of 3 times.

________________________________________________________________

Q:  Is there a longterm advantage of using SAP IQ vs a 3rd Party NLS solution?

A:  Having one vendor for all of your system is an advantage.  Also see above response on SAP NLS advantages.

________________________________________________________________

Q:  how will SAP be able to help if we want to migrate data from an existing 3rd Party NLS system to SAP IQ?

A:  All the data will have to come back into BW and be re-archived.

________________________________________________________________

Q:  Do you see any real viable use case for using smart data access with Hadoop and BWoH?

A:  Yes.  SAP is rated as a leader in advanced analytics (predictive modeling).  For the predictive modeling you don't always know what the data will look like.

________________________________________________________________

Q:  IS the preferred NLS solution  is to use Dynamic tiering instead of Sybase IQ?

A:  No.  SAP NLS solution still runs on a standalone IQ system.

________________________________________________________________

Q:  Whats the advantage of NLS solution like Sybase IQ if we implement Dynamic tiering? I thought we culd use Dynamic tiering for Warm data and use IQ for archiving(COLD Data)

A:  NLS is not the persistence technology.  You still need something that maintains the data and insures query integrity.

________________________________________________________________

Q:  So NLS is integrated for historic reporting.?.so it holds mainly the reporting layer data..and not the PSA data..

A:  Yes correct

Meet Storm and Brian next month at ASUG Annual Conference - see Find ASUG BW HANA Content and more - at ASUG Annual Conference

_____________________________________________________________

Join us May 4th

BI pre-conference session at ASUG Annual conference

Monday, May 4. (extra registration fees apply).

Featuring Hands-on SAP BusinessObjects BI 4.1 w/ SAP NetWeaver BW Powered by SAP HANA – Deep Dive

More details

REGISTERLimited to 30 people.

Check out the ASUG Education Sessions at Conference: ASUG BI Schedule 2015.xlsx

Several upcoming ASUG BI Webcasts includes BI, BW, HANA, EIM & more - register

The end-2-end Guide is especially designed for the technical oriented people in a BW on HANA project to ensure that all relevant Information also find their was to the most neuralgic group of people: the technical Administrators.

The e2e Guide should be the first document on everybody's desk, before reading a countless amount of notes and documents.

For the detailed steps of the Installation/Migration we created a "SAP First Guidance" Document to answer´s  questions, issues and shows workarounds,  in addition to  the standard guides and SAP notes.This Guidance document has no claim of completeness and it is the most complete starting point for a successfull implementation.

The Software Provisioning Manger 1.0 (SWPM) should be used to install NetWeaver based System from 7.30 onwards (despite system exports or fresh installs)

It is now possible to install also the ABAP CI of the BW system on the HANA appliance

Note 1953429 - SAP HANA and SAP NetWeaver AS ABAP on one Server

You have now also a new option to install the HANA client as described here
Note 1943235 - SAP HANA client installation

SAP First Guidance - Business Warehouse on SAP HANA Installation
(also valid for installation of an export provided by a hom/het systemcopy)

Automated Initial Setup of ABAP-Based Systems

The power of Smart Data Access (SDA) with SAP HANA SP08

Note 1964644 - HANA data backup via DB13 fails with SQLCode -10108
dbs/hdb/connect_property = CONNECTTIMEOUT=0

Note 2000003 - FAQ: SAP HANA

Note 2056106 - InfoObject 0IOBJNM not active after installation of NW 7.40 SR2 or BW 7.40 SP08

Note 1944352 - UNCAUGHT_EXCEPTION CX_RSR_X_MESSAGE

Note 2140419 - P14; BATCH: Max. 293 WPs, no BTC jobs started

The BW Basis customizing tasks which can be found here: BW Basis Customizing 7.x

and in the online Help - Performing Wizard-Based Basic Configuration for BW ABAP

For the BI-JAVA configuration follow the Blog here - BI-JAVA, BEx Web and EP: the real connection ...

You can get a list of new transactions in BW 7.3 here:

http://wiki.sdn.sap.com/wiki/display/BOBJ/New+Transaction+codes+in+SAP+BW+7.3

The "one stop ALM page" - SAP BW Application Lifecycle Management (ALM)

Roland Kramer, PM SAP BW/In-Memory

SAP First Guidance

The First Guidance documents are the beginning of a series of documents that should help to better understand the various concepts of SAP BW powered by SAP HANA.The documents are still “work in progress”, so these guides are not intended to be exhaustive.. The purpose of these documents is to deliver additional information besides SAP Help and blogs to get a better understanding of the concepts of SAP BW on SAP HANA.

This Content replaces the existing "SAP HANA Cookbook"

See also the Customer Adoption Journey Map

SAP First Guidance - Business Warehouse on SAP HANA Installation
(Updated version: reflects now the 7.31/7.40 releases as well, the usage of the SL toolset (SWPM, SUM, etc.) and the current SAP HANA 1.0 SP08 release and there actual revisions.)

After BW on HANA is already available since mid April 2012 this document was enhanched a few times since the first version.
On base of this information this "SAP First Guidance" document is released to support Basis administrators in running and  and configuring a Business Warehouse on a SAP HANA system. SAP First Guidance - Business Warehouse on SAP HANA installation provides answers to major questions and issues as well as workarounds and additional details to complement standard SAP Guides and SAP notes. This SAP First Guidance document has no claim of completeness, but it is the most complete starting point for an successfull implementation.

For more information please contact roland.kramer@sap.com

SAP First Guidance - Migration BW on HANA using the DMO option in SUM

the database migration option (DMO) is an option inside of the software update manager (SUM) for combined update and migration: update an existing SAP system to a higher software release and migrate to SAP HANA database in one technical step. As the technical SUM steps are the same, this “SAP First Guidance” document should make all customer-specific documentation obsolete. It is the complementary documentation to the existing Notes and SUM/DMO Upgrade Guides.

DMO can be used with every BW Release starting from 7.0x and onwards. It makes the two step approach (upgrade/migration) and the usage of the BW post copy automation (BW-PCA) obsolete. It can also be used within a Release, e.g. to go from 7.40 SP06 on anyDB to migrate to 7.40 SP07 on HANA.

For more information please contact roland.kramer@sap.com

SAP First Guidance - Implementing BW-MT for BW-aDSO

SAP BW 7.4 SP08 powered by SAP HANA is the next milestone for enterprise data warehousing with BW on HANA and provides the next level of simplification for BW .In addition, SAP BW on HANA Virtual Data Warehouse capabilities have been enhanced for even more flexibility. In midterm the advanced DSO shall replace the main BW InfoProviders with persistency (InfoCube, DSO, PSA). The classic InfoProviders are of course still supported and do co-exist with the advanced DSOs.

For more information, please contact roland.kramer@sap.com

SAP First Guidance - SAP NLS Solution with Sybase IQ

This “SAP First Guidance” document provides all the necessary information to help quickly implement this newly released option: Store historical BW data on an external IQ server to optimize the  system size  when preparing  to migrate to SAP BW powered by SAP HANA. The SAP NLS solution with Sybase IQ also helps to keep down the TCO for investing in the SAP In-Memory when historical (“frozen”) data is stored on a less sophisticated device, which acts like a “BW Accelerator on Disk”. SAP Sybase IQ is therefore the perfect smart store for this kind of data. Please note that the SAP NLS solution can be used with all database versions supported by SAP BW 7.3x. SAP HANA is not necessary. The document is a “work in progress” and is not intended to be exhaustive.  It does however contain all information required for successful implementation of the SAP-NLS solution with Sybase IQ. SAP-NLS can be used with every SAP supported database, where SAP IQ will be the seconday database for data reallocation.

For more information, please contact roland.kramer@sap.com

SAP First Guidance - SEM/BW Modelling in SolMan 7.1 with MOPZ

Due to constant Questions about the Upgrade to NetWeaver 7.3x and 7.40 including SEM Add-On Components, we created a SAP First Guidance Document which describes the successfull Definition of a SAP BW 7.0/7.01 System with the SEM Add-On Installed on top.  With this Information you will be able to integrate the stack.xml in the SUM (software update manager) process and the DMO (database migration option) DMO process included in SUM as the first input is the location of the stack.xml which defines the download directory for SUM. Furthermore the interaction of the stack.xml in the upgrade process enables you a smooth Integration into the Upgrade Process included in DMO.

For more information please contact roland.kramer@sap.com

SAP First Guidance - BW Housekeeping and BW-PCA

The system copy procedure of SAP BW systems and landscapes is complex for a number of reasons. There is a large number of configuration settings (such as connections and delta queue handling for data loading) and system copy scenarios of SAP BW (each with different landscape aspects).  These have to be handled as part of every system copy, regardless of whether the system copy is part of the migration to SAP HANA or if you want to perform regular system copies of your SAP BW landscape. BW-PCA can be used from SAP BW 7.0 onwards depending on the SPS level.

Additionally see the usage and implementation of the BW Houskeeping Task List and the Pre/Post Task Lists for Upgrade/Migration. These are Included in the database migration option (DMO) as part of the software update manager (SUM). Additional Details also can be found on the BW ALM Page.

For more information please contact roland.kramer@sap.com

------------------------------------------------------------------------------------------------------------

SAP First Guidance SAP BW 7.40 on HANA - HANA Analysis Processes

Starting with SAP BW 7.4 SP5 on HANA a new feature to analyze data from certain perspectives, for example to calculate ABC classes or to calculate scoring classes, is introduced. This new feature is called SAP HANA Analysis Process and enables the data warehouse modeler to analyze the data using different predefined or own written functions or scripts. HANA provides the integration numerous specialized libraries like PAL, AFL, R to understand the correlation of the data in the existing EDW.

SAP First Guidance - SAP BW 7.40 on HANA - View Generation

The focus of this document is the exposure of BW data natively in HANA as HANA views that point directly to the data and tables managed by BW. This enables HANA-native consumption of BW data.

SAP First Guidance - SAP BW 7.30 on HANA - Inventory InfoCubes

This SAP first guidance document describes the handling of non-cumulative InfoCubes on SAP HANA. As the handling of Inventory InfoCubes changed within SAP BW 7.30 based on SAP HANA, this document wants to briefly describe the differences. for better understanding it is recommended to read How to Guide based on previous release How to Handle Inventory Management Scenarios in BW.

SAP First Guidance - SAP BW 7.40 SP05 on HANA - OpenODSView

In SAP BW 7.4 SP05 on HANA the new metadata object Open ODS View is introduced, which provides the data warehouse modeler with a flexible, easy to use tool to integrate external data in the EDW Core Data Warehouse.

SAP First Guidance - SAP BW 7.40 SP05 powered by SAP HANA - CompositeProvider

A CompositeProvider is an InfoProvider in which you can combine data from BW InfoProviders such as InfoObjects, DataStore Objects, SPOs and InfoCubes, or SAP HANA views such as Analytical or Calculation Views using join or union operations to make the data available for reporting. This paper explains how to create a CompositeProvider in SAP BW 7.4 SP5 using the BW modeling tools in SAP HANA Studio.

Hi All,

When we reach a certain level of experience, we are expected to deliver the solution from scratch.

Have you ever faced any situation where you are given a very fresh BW system and asked to start with the initial configuration? At that point, this document would be handy in understanding those basic steps.

These days we have 2 broad landscapes available:

a) BW on Traditional data base

b) BW on HANA.

In this document, I will try to cover the concepts in General (Application layer) and some topics exclusively for BW on HANA systems will be added to this document at a later stage.The values mentioned in this series of documents must be considered for reference purpose only and should be finalized after having a detailed discussion with the client team.

Before starting the document, I would recommend you to go through the following wonderful documents written by our colleagues. I will try to cover only those points which are not mentioned in the below reference documents.

1)  SAP BW 7.3 Configuration after installation of BW Part 1  --> http://scn.sap.com/docs/DOC-55967

2)  SAP BW 7.3 Configuration after installation of BW Part 2  --> http://scn.sap.com/docs/DOC-55956

3)  SAP BW Configuration – Basic System Settings  --> http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/30422873-8369-2d10-ddb5-e516359259f1?QuickLink=index&overridelayout=true&48438641495213

So here we go....

1)  Maintain and CHECK SOURCE SYSTEM CONNECTION:

      Check RFC connection between BW-ECC/CRM/or any other systems in your landscape.

      TCODE: RSA1 -->   Source System --> Check.

      Rectify the errors(if any). This step anyway might need your Basis help.

2)    CHECK BICS CONNECTION BETWEEN BW AND BO USING A SERVICE USER

This Step is important if you have a BW-BO integration(BICS) in place.

Try using a service user here as it will avoid the confusions related to Passwords.

3) TRANSFER APPLICATION COMPONENT HIERARCHY(IN BW)

YES

TCODE: SPRO. Do the same steps in Source Sytems and BW.

In this step, we transfer and activate the application component hierarchy delivered by SAP. This is a one-time activity and only needs to be done once at the beginning. Do this is BW system also, as sometimes BW will act as a source system.

This will help the system to arrange all objects application components accordingly. Otherwise, replicated objects will go and collect under NODESCONNECTED

4)  UNICODE:

Ensure that system is Unicode, else languages like Arabic will not work.

5) ARABIC LANGUAGE PACKS:(For Middle East Customers)

Ensure that Arabic language packs are installed.

TCODE: SMLT

6)  TRANSPORT SETTINGS:

Set the Transport to Switch OFF Standard. So that the system does not prompt for package/req, every time a new object is created or edited.

7)  POSTING MODE FOR MASTER DATA

TCODE: RSCUSTV9  -->  Posting Mode for Master Data

By making this setting, if master data does not exist in the system, the corresponding entries are created.

For example – We have the InfoObject MATERIAL, which has the navigation attribute COLOR. We want to create a new entry in the master data maintenance MATERIAL 4711 with the color RED. The value RED is not yet available in the master data table of the navigation attribute COLOR. With this setting on Data records are updated. Navigation attribute values that do not exist are created. This ensures that master data attribute load does not stop because there are new attributes and the attribute load has not been completed yet.

8)  Tcode: SNRO

Maintain Proper Number Ranges.

9)  THRESHOLD VALUE FOR DATA LOAD

TCODE: RSCUSTV6  -->  Threshold Value for Data load

NOTE: The Values mentioned above is just some dummy values. Actual Values should be entered after discussing with the client team.

• The Frequency Status value controls after how many data IDocs an info IDoc is to be sent to the BI system. This enables a user to monitor the status of data loads online.

• The Package size contains the number of data records within a package that are delivered when you load data from the source system.

• Since we would be doing data loads using process chain mostly in background, the parameters can been set on a relatively higher side.

10)  PROJECT SPECIFIC PACKAGES

Create Development package with project specific naming convention:

TCODE: SE21, SE80

11)  ACTIVATING/DEACTIVATING PERSONALIZATION IN BEX

TCODE: RS_PERS_ACTIVATE

We use this activity to activate personalisation in BEx. The following have been activated

• BEx history, so that the last report you executed is saved.
• Variables, so that certain variables selected by you are proposed.
• Web applications, so that report drilldowns are saved.

12) INCREASE THE TIME OUT IN BW SERVER FOR DEVELOPMENT ACTIVITIES

During the development Phase, it would be a good idea to increase the timeout in BW system. This will avoid the developer to perform the activities without any timeout issues. Please ensure that it is set to standard/default values post the go live.

TCODE: RZ11 --> parameter name: rdisp/gui_auto_logout

13) CONTROL PARAMETERS FOR THE DATA TRANSFER.(IN SOURCE  SYSTEMS)

The control parameters for data transfer have to be maintained in the source systems.

This is a manual activity and needs to be done manually in DEV, QA and PRD.

Path: Source system  --> TCODE: SPRO -->  IMG

Maintain the following entries:

Save the changes.

14)  VERSIONING OF OBJECTS

TCODE: SPRO

Versioning is set for the required objects and is saved and moved to higher environments.

If you could go through the above mentioned points and reference documents, I believe you would be able to cover most of the important BW configuration steps.

Points exclusive to BW on HANA would be added to this document at a later stage.

Please refer to Roland's document for getting more information on this topic

-->  SAP BW Installation/Configuration (also on HANA) --> http://scn.sap.com/docs/DOC-28504

Hope this document was helpful.

BR

Prabhith