4.bw4hana Documentation.docx

  • Uploaded by: Anonymous aCeye79n
  • 0
  • 0
  • November 2019
  • PDF

This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA


Overview

Download & View 4.bw4hana Documentation.docx as PDF for free.

More details

  • Words: 5,100
  • Pages: 124
SAP BW/4HANA is the next generation of SAP Business Warehouse powered by SAP HANA. BW / 4 HANA is specially designed to run on SAP HANA only. It delivers new levels of simplicity for building and operating data warehouse solutions with flexible data management capabilities in a modernized user experience. Another central aspect for customers running SAP BW powered by SAP HANA is the migration path to SAP BW/4HANA. Finally, we will have a look at the future development roadmap for SAP BW/4HANA. Simplicity, Openness, Modern UI, High Performance Simplicity: The number of data objects will be reduced-Eliminates data redundancies, increases consistency, and results in a smaller foot print Administration efforts to maintain data objects -and error prone data flows will be reduced BW/4 HANA will leverage HANA’s data life cycle features by automatically distributing the data to hot and warm storage areas. Openness: Customers see great benefit in possibility to expose BW/ 4 HANA Models and Native HANA Views. These automatically generated HANA views can be consumed in visualization tools like Business Objects Lumira or cloud or they can used by customers to build their own data models on top of BW /4 HANA data models. Modern UI: Business Objects cloud (instead of BEX) will provide a modern UX for visualization storytelling and exploration. BW /4 HANA Data can also be accessed by Digital Boardroom. UX will improve for administrators, as modern HANA studios and front ends will be used instead of SAP GUIS front end. High Performance: Operations and calculations on details level can be pushed down to HANA resulting in a superior performance. HANA Specific libraries can be utilized running in the HANA platform. As with BW on HANA scale-out will be a de facto standard for customer implementations.

SAP has launched the next generation data warehouse application i.e. BW/4 HANA to leverage in-memory computing capability of SAP HANA. New deployment options like AWS (Amazon Web Services) and SAP HANA Enterprise Cloud are included for BW/4 HANA along with the traditional on-premise deployment feature. It would help customers to perform data analysis in real time on the cloud.

Gradually, SAP is redesigning its enterprise business applications for SAP HANA, thus customers could fully leverage the in-memory platform. For example, last year, SAP introduced S/4 HANA as next generation business suite which is the successor of SAP ERP known as ECC6.0. In the same way, to accelerate data warehousing processes, BW/4 HANA is offered by SAP to make business processes simpler with real time analytics powered by SAP HANA. BW/4 HANA is designed simple and powered by enhanced modeling technique coupled with unified streamlined data warehouse object model. Moreover, it's far more integrated, efficient with faster data loading along with faster query analysis using SAP HANA Vora engine and a complete end-to-end data management platform which would help customers to meet today's complex business challenges. This data warehousing tool would be able to process big data by using SAP HANA Vora; as a result processing IoT data would be possible by business organizations. It has expanded the scope of data warehousing and made business more connected to the outside world. Moreover, an easy migration process is offered by SAP to move business from SAP BW to BW/4 HANA.

Design principles of SAP BW/4HANA: Simplification: This might be an over-used buzzword, but SAP has removed huge amounts of functionality that was only required to support the complexities of traditional RDBMS. Removing all this code really simplifies the codebase and allows the development team to focus on HANA optimization. User Experience: User experience both for developers and end users is a focus. The modeling tools will be in Eclipse and the Web. It will no longer be necessary in the future for developers to use SAP Gui for modeling. Openness: SAP BW/4HANA is open from a data perspective (consumption from any source, and data tiering to Hadoop) and from an end-user perspective (models can be consumed from any major BI tool).

Features of SAP BW/4HANA: One thing to bear in mind is that SAP took a deliberate strategy with SAP BW/4HANA: announce the product and the vision, and deliver product immediately. ·

The code simplification is complete, so the product is leaner and meaner

·

The new modeling tools are in the initial release

· The Simplified Object Model is delivered, so BW and HANA native schemas are interchangeable · The Advanced Multi-Temperature Management delivered is complete, so older data can be aged out to less expensive storage and still be updated · Pushdown of complex EDW algorithms into the HANA database, instead of running in an application tier The benefits of this approach are the customers have a clear view of strategy and roadmap. They can immediately start the work to prepare for BW/4HANA and get on the initial release.

Basic scenarios: BW4HANA Hana system is attached to BW4 because we can share objects, each of SAPABAP2, S4HANA and native HANA complement each other, this is called transformation modeling or mixed modeling. We can mix and match according to business requirements, BW4HANA contain INFOAREA just as like HANA contain PACKAGES INFOAREA contains INFO OBJECTS just as like package contain information views in HANA INFO OBJECTS contain “Characteristics” and “Key figures” just as like information views contain Attribute views, Analytic views and Calculation views

In order to create a project: window<-perspective<-

Click on Reset perspective

Select yes

Click on open perspective icon

Select BW Modeling<-click on ok

Right click on free space: click on new<-click on project

Select BW Project<-click on next

Select BW4HANA<-click on next

We can view system ID, application server and instance number<-click on next

Provide user name and password<-click on finish

Click on SAP Logon

Right click on BW4HANA<-click on properties

We can view application server details, instance number and system ID<-cancel

Click on finish

Now, we can see that the project has been created

Right click on project<-select “Attach SAP HANA System”

Select “BEST” system and click on finish

Go to SAP Logon

Right click on BW4HANA<-click on logon

Provide user name and password<-click enter

Select system<-click on status

Now, we can view the details about product version, database system, host name and owner name

Get back to the project: right click on BW Repository<-new<-click on infoarea

Provide the name and click on finish

Right click on BW Repository<-now, we can see that info area (COPAPROJECT_1) has been created

Right click on info area (COPAPROJECT_1)<-new<-select info Objects

Provide the name for info Object (ZCUST_1) and click on finish

View the general characteristics of the info Object (ZCUST_1)

If we click on Texts checkbox in properties, that going to enable “External SAP HANA view for master data and Master data/Texts tab appears at the bottom of the page

Click on checkboxes of short text, medium text, long text and extra long text

Click on checkbox of Master Data <-Attributes tab appears at the bottom of the page<-click on attributes

Click new

Provide info Object name (NAME5) and click on finish

Click new

Provide info Object name (LAND5) and click on finish

Click new

Provide info Object name (REGIO5) and click on finish

Enable texts checkbox for info Object “LAND5”

Enable Texts checkbox for info Object “NAME5”

Enable Texts checkbox for info Object “REGIO5”

Go to general tab<-enable “External SAP HANA View for Master Data” checkbox

If we click on “Usable as Info provider” checkbox, that’s gonna automatically enable the “External SAP HANA View for Reporting” Text box

Click on check (check BW object)

Go to hana modeler by clicking on hana modeler icon

Click on activate (check BW object) as shown below

Right click on content<-find<-

Search for object ZCUST_1 and click on ok

Now we can see that the object does get activated: content<-system_local<-BW<-BW2HANA
Click on auto layout

Click on semantics

Click on data preview

Click on raw data<-now, we see no data

In order to get the data: go back to customer info object

Click on miscellaneous<-click on Master Data Maintenance

We entered two records

Click on Texts

Now, give short description, medium description and long description of the data

Click on save

Now, we can see that the data has been saved successfully

Go to data preview<-click on Analytics List UIBB

Click on Navigation panel and we can view the data with two records that we created

If we want to save the data in excel sheet: click on the icon as shown below

If we want to save the data in excel sheet, we can save it by clicking in save

Mixed Modeling in BW4HANA Using Composite Provider A Composite Provider is an Info Provider, which combines data from several analytic indexes or from other Info Providers (by Join or Union), and makes this data available for reporting and analysis. UNION and JOIN operations are executed in HANA and not the application server. The main advantage of Composite providers is that: BW Info Providers can be combined using the JOIN operation allowing us to create new scenarios not possible or very expensive with standard techniques When we hear the word Union, what strikes our mind immediately is a Multi provider. SAP still suggests the usage of Multi provider in case your requirement is just to use Unions. This is because the OLAP engine is well suited for this operation. Composite providers however can be used on top of Multi providers to execute Join operations with Multi provider as one of the data providers. This gives us additional flexibility and even one additional level of modeling thus allowing us to create new scenarios that were not possible before.

Login to SAP HANA studio (main car)

Click on window<-perspective<-reset perspective

Click on yes

Click on open perspective icon

Click on BW Modeling and click on ok

Right click on free space<-new<-project

<-select BW Project and click next

Double click on BW4HANA

Click on next

Provide user name and password<-click on finish

We can see that the project has been created

Right click on project<-select SAP HANA System

Select BEST and click on finish

Now, we have SAP HANA System library hana studio

Expand BW Repository and we can see different info areas

Right click on repository<-new<-infoarea<-

Provide name and description and click on finish to create an infoarea

Expand data sources

Data sources<-ODP-SAP<-EHP7<-SAP<-SAP application components<-sales and distibution<sales master data<-double click on sales organisation (0SALESORG_ATTR (EHP7)

Click on fields

Fields tab opens up

Right click on sales organisation

Click on explore data flow

Drag and drop open ODS view onto workspace

Join a link between sales organisation and newnode1

Rearrange the rows as shown below

Name of the newnode1 can be renamed

Give the name, select master data at semantics, select data source (BW) as source type and click on next

Select the object shown and click on finish

Click on master data

We can view the source fields and characteristics and key figures

Click on check BW objects

Click on activate BW objects

Now, we can see that the object has been created

Right click on SALESORG1 and click on explore data flow

Right click on SALESORG1 and click open

Click on data preview<-analytics list UIBB

Now, query panel opens up

Now, we can view the output data using query panel

Right click on infoarea (IA_MAY5)<-select composite provider

Provide the name and description for composite provider and click on finish

Click on checkbox of External SAP HANA View<-click on scenario

The following scenario appears

Right click on table<select join with

Search for SALESORG1 object

Drag and drop the object at the union

We can see the source table

Data sources<-ODP-SAP<-EHP7<-SAP<-SAP Application distribution<-sales master data<-sales document header data

components<-sales

and

Right click on sales document header<-click on explore data flow

Drag and drop open ODS View onto the workspace

Link join between sales documentation and new node

Arrange the nodes in a proper manner

Provide details and click on next

Select the object that is shown below and click on finish

Click on facts

Now, we can view fields like characteristics and key figures

Go back to composite provider

Right click on BW Repository and click refresh

Now, drag and drop salesheader1 onto the union

On drag and drop of salesheader1onto union, we see that it adds to the source

Click on union

Right click on salesorg1 and click on create assignments

Right click on the object as shown and click on create assignments

Right click on the object as shown and click on create assignments

Right click on the object as shown and click on create assignments

Right click on the object as shown and click on create assignments

Right click on the object as shown and click on create assignments

Right click on the object as shown and click on create assignments

Right click on the object as shown and click on create assignments

Apply filter in order to find out VKORG

VKORG mapped with target object

Click on check for BW Objects

Click on activate BW Object

Double click on the composite provider and do the data preview

Do the data preview: click on Analytics List UIBB

We don’t find data in the output because data is not present in the tables which we have taken

Let us check for the data in salesheader table, click on data preview<- click on Analytics List UIBB

It is confirmed that there is no data present in the tables which we have taken

We removed all the links, unions and the nodes

Right click on salesheader1<-click on Explore data flow

Open DBS access data directly from source system. This is one open DBS

Right click on salesorg1 and click on Explore Data flow

The following scenario is another open DBS

Open composite provider<-right click on the object<-click on explore data flow

COMPOSITE JOIN CAN JOIN UNIONS FOR BW4HANA AND ALSO HANA In the following scenario, it joins the two unions (SALESORG1 AND SALESHEADER1). This is also called as mixed modeling in BW4HANA.

Certification Questions: 1. Which of the following are characteristics of SAP NetWeaver Business Warehouse (SAP BW) when migrating it to run on SAP HANA? (Choose three) A. The sizing of your current SAP BW application servers remains valid. B. It allows co-deployment of the SAP BW application server on the SAP HANA database hardware. C. It allows re-use of your available SAP BW application servers. D. It eliminates the need to upgrade to the latest SAP BW application version. E. The system usage is the same as an equivalent SAP BW on non-SAP databases. Answer: A, C, E 2. You are using SAP NetWeaver Business Warehouse (SAP NetWeaver BW) in your company as the enterprise data warehouse. You want to use SAP NetWeaver BW as a data provisioning tool for SAP HANA without disturbing your BW reporting. Which of the following are SAP recommended actions? (Choose two) A. Automate the ETL processes in SAP NetWeaver using process chains. B. Write data back from SAP HANA into the replicated SAP NetWeaver BW tables. C. Create new InfoObjects for the SAP HANA InfoProviders. D. Schedule the real-time data loads into SAP HANA. Answer: A, C 3. How can you improve the performance of a scripted calculation view? A. Read data from column tables using nested SELECT statements B. Convert SQL code to equivalent CE functions C. Combine analytic views using a CE_JOIN function D. Combine data from the row store and column store Answer: B 4. You are using SAP Landscape Transformation to replicate data into SAP HANA.Which of the following can you use to define the schema that the replicated data populates? A. Advanced replication settings (transaction iuuc_repl_content) B. Change Authoring Schema in the Quick Launch view C. Data Provisioning in the Quick Launch view D. Configuration & Monitoring Dashboard (transaction LTR) Answer: D

5. You have an SAP NetWeaver Business Warehouse (SAP NetWeaver BW) on SAP HANA system installed on multiple nodes. Which of the following information objects are stored on the master node? A. SAP NetWeaver BW master data tables B. DataStore Objects (DSOs) C. ABAP system tables D. Persistent Staging Area (PSA) table Answer: C 6. Which of the following are characteristics of SAP NetWeaver Business Warehouse (SAP NetWeaver BW) when it is migrated to run on the SAP HANA database? There are 2 correct answers to this question. A. The current SAP NetWeaver BW application server hardware can be re-used. B. The SAP NetWeaver BW application server can be installed on the SAP HANA hardware. C. All SAP NetWeaver BW 7.x application versions can be used. D. The sizing of the current SAP NetWeaver BW application server remains valid. Answer: A, D 7. You have to size an SAP HANA system for SAP NetWeaver BW. The SAP NetWeaver BW system is currently running on a non-SAP RDBMS.Which of the following factors influences the size of the SAP HANA system? A. The partitioning of tables B. The number of tables in the row store C. The number of indexes D. The size of aggregates Answer: B 8. Which tasks do you have to perform if you want to use SAP BW with SAP HANA as the Underlying database? Please choose the correct answer. Choose one: A. Do a heterogeneous system copy from your current DB to SAP HANA DB B. Ensure that you have at least SAP NetWeaver Business Warehouse 7.02 installed C. Recreate SAP BW indexes after SAP HANA database migration. D. Do a homogeneous system copy from your current DB to SAP HANA DB Answer: A

9. In which engines is an analytic view executed that contains a calculated column? (Choose two) A. Calculation engine B. Row store engine C. OLAP engine D. Join engine Answer: A, C

Interview Questions: 1. What is SAP BW/4HANA? SAP BW/4HANA, affectionately known as BW4 or B4, is SAP's next generation logical data warehouse (LDW). It is designed to be a simplified, high-performance, open platform for historic and legacy enterprise data. It is a logical successor both for SAP BW customers, and for traditional EDW customers running Teradata, Netezza, Oracle and IBM DB2. 2. Why did SAP create SAP BW/4HANA? The SAP HANA platform on its own is an amazing database but it doesn't contain the rich functionality of data warehouses for data harmonization, batch loading of legacy data, and long term storage. That's where SAP BW/4HANA comes in. 3. What are the design principles of SAP BW/4HANA? Simplification: This might be an over-used buzzword, but SAP has removed huge amounts of functionality that was only required to support the complexities of traditional RDBMS. Removing all this code really simplifies the codebase and allows the development team to focus on HANA optimization. User Experience: User experience both for developers and end users is a focus. The modeling tools will be in Eclipse and the Web. It will no longer be necessary in the future for developers to use SAP Gui for modeling. Openness: SAP BW/4HANA is open from a data perspective (consumption from any source, and data tiering to Hadoop) and from an end-user perspective (models can be consumed from any major BI tool). 4. What are the killer features of SAP BW/4HANA? One thing to bear in mind is that SAP took a deliberate strategy with SAP BW/4HANA: announce the product and the vision, and deliver product immediately.     

The code simplification is complete, so the product is leaner and meaner The new modeling tools are in the initial release The Simplified Object Model is delivered, so BW and HANA native schemas are interchangeable The Advanced Multi-Temperature Management delivered is complete, so older data can be aged out to less expensive storage and still be updated Pushdown of complex EDW algorithms into the HANA database, instead of running in an application tier.

The benefits of this approach are the customers have a clear view of strategy and roadmap. They can immediately start the work to prepare for BW/4HANA and get on the initial release. 5. Do you need SAP BW/4HANA if you have SAP S/4HANA? SAP BW was originally designed due to deficiencies in the Oracle database that meant it was not well suited to reporting on transactional data. SAP customers implemented BW so they could take load off the transactional system and harmonize data. It later grew into an EDW, where data from many other systems was consolidated into one place. SAP S/4HANA pushes operational reporting back into the transactional system where it belongs and integrates it with the Fiori User Experience so customers have aggregated data available on demand. However, SAP S/4HANA is not designed to be a Logical Data Warehouse for data from many systems, or as the location to store long-term historic data. 6. Do you need SAP BW/4HANA if you have HANA Enterprise? Many customers have used HANA as a platform for data marts or data warehouses and have built their own workflow. This will remain an option for those that don't want BW. The neat thing about SAP BW/4HANA is you can have your cake and eat it: it can operate in a mixed mode with HANA Enterprise. 7. What is the strategy for BW on Any DB? SAP BW 7.5 is available on IBM DB2, MaxDB, Microsoft SQL Server, Oracle, SAP ASE and SAP HANA. If you are on a current database version and Operating System, like Oracle 12.1 on RedHat Linux 7, then the end of support at the time of writing is June 2024. SAP BW/4HANA is a code fork and is the primary development platform. It is understood that BW 7.5 won't be developed at the same pace going forwards and there is unlikely to be a BW 7.6. That said, SAP will no doubt backport some functionality to BW 7.5 and will definitely continue to fix bugs and security patches through the supported timeline. There are mentions of NetWeaver 7.5 EhP1 on SAP's website, but it's not clear at this time whether that will be a S/4 HANA-only release.

8. When will SAP BW/4HANA be available? The great thing is that version 1.0 is planned to be released to Customer on September 7th 2016. 9. What is the upgrade path for SAP BW customers? One way is to create a new SAP BW/4HANA system and selectively move the objects you use to this. This is advantageous for customers with a very old BW system with a large number of legacy objects BW 3.x, especially when there are a large amount of objects which are no longer used. The upgrade approach is a three step process: 1. Upgrade to SAP BW 7.5 SP04 on HANA. This is a straightforward upgrade/migration and will leave all the objects intact. 2. Object Conversion. Unused objects can be deleted, and legacy objects (InfoProviders, DSOs etc.) can be migrated to BW/4HANA objects via a set of semi-automated tools. This can be done in a Big Bang approach, or gradually. 3. Enable SAP BW/4HANA mode. This is a mini-upgrade which locks in the BW/4HANA mode, and deletes all the legacy code, and enables BW/4HANA-specific functionality. 10.

Is SAP BW/4HANA based on the NetWeaver platform? Yes! Just like SAP S/4HANA, SAP BW/4HANA is based on the NetWeaver 7.5 code base. This means that the administration and tooling will be familiar for SAP customers.

11. What legacy objects are no longer supported in BW/4HANA? As BW grew in size and scope, the number of different ways of achieving the same goal increased. This left a large amount of different object types, some of which didn't take advantage of the SAP HANA database. SAP BW/4HANA takes an approach of minimizing the number of supported objects by design, and allowing for an object conversion to move to these. Here's a list of what's gone:    

All support for BW 3.x objects DSOs, InfoProviders, MultiProviders, VirtualProviders, InfoSets, PSAs, InfoPackages All support for BEx (Query Designer, BEx Analyzer, Report Designer, Web Templates, BEx Web, Broadcasting) UDConnect, DBConnect.

12. What about SAP Business Planning & Consolidation (BPC)? BPC will continue to be supported in embedded mode. The older classic BPC will not be available on SAP BW/4HANA and customers will need to move their models to embedded models. It's worth noting that the desktop software "EPM Add-In" is supported on both embedded and classic mode. 13. What about BW add-ins like SEM? SAP has had to continue to support add-ins like BCS and SEM through the lifecycle of BW on HANA which has been great for customers looking to transition to BPC and SAP Strategy Manager. Since the whole purpose of BW/4HANA is to simplify the code base, some add-ins will be converted for BW/4HANA and others will be disabled during the upgrade process. 14. What is the approach for NLS and Data Temperature Management? SAP BW/4HANA does not support third party NLS solutions and instead offers Hadoopbased automated data temperature management that moves cold data into Hadoop. This can be based on time, or some other predefined setting. 15. Is SAP BW/4HANA Cloud-only? The collaboration for the SAP BW/4HANA launch was with Amazon Web Services. SAP has worked with AWS to get BW/4HANA templates and demo systems working from the day one. AWS have announced its X1 public cloud system for HANA, which is a 2TB system that can be provisioned in minutes. AWS has also announced two additional systems: a 1TB system, which sits between the 244GB and 2TB system from a price point perspective, and scale-up support for 2TB - up to 7 nodes, or a massive 14TB. So whilst BW/4HANA is "cloud-first", it is available today in the AWS cloud and also for download as an on-premises or managed cloud (HEC, Virtustream, IBM Softlayer etc.) edition. From a software delivery perspective there is only one code-line for cloud and on-premises. 16. How is SAP BW/4HANA licensed? Full details aren't available yet (they will be available at launch) but it is understood to be a similar deal for SAP customers with the full runtime database as SAP S/4HANA and there will no doubt be a Q3/Q4 promotion to stimulate the customer base. It also seems that customers who are on a BW on HANA runtime license will be able to upgrade to SAP BW/4HANA by moving to a full S/4HANA runtime license.

Error 1: Error in BW project creation in HANA I faced an issue with creation the BW project in HANA I have already installed SAP HANA Studio, established connection to my server with HANA. Also I installed all necessary plugins: - Add-ons of ABAP development tools for SAP HANA (Developer Edition) v.2.24 - BW Modeling Tool for SAP HANA v.1.1 I performed all steps from this guide: Configuring the ABAP Back-end for ABAP Development Tools My user in the system has two ABAP roles: SAP_BC_DWB_ABAPDEVELOPER and SAP_BC_DWB_WBDISPLAY. They are activated and correct, authorization profiles are assigned. The error is the following: When I try to create BW project in HANA system, I'm able to choose my connection. The connection is insecure without SNC. On the next screen I enter my login and password and get the error message:

User XXXXXXXX is not authorized to access system ZZZ using ABAP in Eclipse (No authorization to access the resource /sap/bc /adt/compatibility/graph.) I have the trace for this error: null Info Thu May 15 11:37:35 FET 2014 [ERROR] ====> GET /sap/bc/adt/compatibility/graph HTTP/1.1 [adt.tmp_1400143048305, stateless] --- REQUEST: GET /sap/bc/adt/compatibility/graph HTTP/1.1 X-sap-adt-profiling: server-time --- RESPONSE: HTTP/1.1 403 Forbidden

Content-Type: application/xml ~server_protocol: HTTP/1.1 X-sap-adt-profiling: server-time=1921 <exc:exception xmlns:exc="http://www.sap.com/abapxml/types/communicationframework"><message lang="EN">No authorization to access the resource /sap/bc/adt/compatibility/graph.No authorization to access the resource /sap/bc/adt/compatibility/graph.<properties/> [ERROR] ====> GET /sap/bc/adt/core/discovery HTTP/1.1 [adt.tmp_1400143048305, stateless] --- REQUEST: GET /sap/bc/adt/core/discovery HTTP/1.1 X-sap-adt-profiling: server-time --- RESPONSE: HTTP/1.1 403 Forbidden Content-Type: application/xml ~server_protocol: HTTP/1.1 X-sap-adt-profiling: server-time=1991 <exc:exception xmlns:exc="http://www.sap.com/abapxml/types/communicationframework"><message lang="EN">No authorization to access the resource /sap/bc/adt/core/discovery.No authorization to access the resource /sap/bc/adt/core/discovery.<properties/> Solution: Two mentioned roles were added, but none of them didn't contain needful authorization object S_ADT_RES with URI value = /sap/bw/modeling/* (mentioned in SAP Note # 1969032 Missing authority for resources related to BW Modeling Tools ) URI value was manually added (NON-capital letters!!!) and everything finally worked!

Error 2: Issues Importing BW Model in HANA Studio Currently we are on BW on HANA (BW 7.3 SP9) and we are trying import BW model into HANA and later expose them in Explorer. In the HANA Studio I am doing File>Import> Import SAP NetWeaver BW Models>New Connection>Lists all the infoproviders> Selected one of the infoproviders (HANA Optimized DSO) > Finish It runs for some time and gives out an error message "Completed with errors", In the error log I find lot line with message "Table could not be found or the user does not access privileges". Does anyone anyone know what user is missing access privileges? is it the BW side or the HANA side? Solution: Finally got our issue of importing BW models fixed by granting content activation role to the Modeler user.

I

Error 3: import BW model to HANA failed We have BW 7.4 installed on Sy base database. I have created DSO and uploaded the data. Now In SAP HANA studio, I imported connection-->SAP netweaver BW with all user credientials and test connection successfully. Now i could see all the info areas with DSOs and Info object. Now I tried to import one of the DSO. I get error message. So you need to grant access to this schema to _SYS_REPO user as well. GRANT SELECT ON SCHEMA "EFASHION_TUTORIAL" TO _SYS_REPO WITH GRANT OPTION; Solution: "We have to do BW 7.4 installed on Sy base database" If this is the case, we cannot import BW models in HANA. The use case for BW models in HANA is to generate HANA views for BW artifacts in BW on HANA system. So now let us consider a scenario where the end user wants to generate HANA model for BW Infocube. For this infocube, there would be several tables generated while creating the infocube. Once when the user tries to import the models, same tables would be used to generate HANA artifacts. ie., /BIC/* tables would be used to generate Analytic views or Calculation Views. So if BW is not running on HANA, then this feature is not available. Also if BW is 7.4 SP05 and above, we can generate HANA models for BW providers from BW system itself. We need not follow the wizard to import the models.

Error 4: Error while creating advanced DSO While creating ADSO in hana studio getting below error. Could anyone help to resolve the issue ASAP.

Solution: Use latest Modelling Tools Version 1.14 to solve the issue.

More Documents from "Anonymous aCeye79n"

Temporal Join.docx
November 2019 24
Fsc020.pdf
November 2019 17
1. Attribute View.docx
November 2019 17
4.bw4hana Documentation.docx
November 2019 17
Security Questions.docx
November 2019 8