MultiProviders views in HANA

Hello Experts,
I'd like to ask something about the MultiProvider of BW in HANA.
I have created a multiprovider in BW. then I switch to HANA which is the DB of the BW app. In the BW schema, column views, I found there are two similar column views. I checked the content and the structure. Both are the same. So I wonder what is the difference of the two view? If I can use anyone of them for my reporting?(I use IDT to connect to the view).
See the screen shot below. Many thanks.

Hi Vaithi,
This categorization of views is in SAP HANA Live, and functionalities are as below.
Private views are abstraction layer for SAP tables. These views are used in Re-use views. Private views cannot be modified.
Re-use views are built on top of Private views and we can use Re-use views to build Query views.
Query views are created on top of Re-use views and we use Query views for reporting in reporting tools.
In general when we create models, we don't categorize this way because we use Attribute views, Analytic views and Calculation views according to our requirement. But in HANA Live, all models are calculation views and hence they are divided into separate categories.
Are you planning to categorize models created by you or copying the HANA Live views and want to classify them?
Regards,
Chandu.

Similar Messages

Call a PAL function within a view in HANA?

Hi community!
Does anyone know how you can integrate the call of a PAL function (e.g tripple exponential smoothing) into a HANA view? I guess this must be achievable in a CE Script?
Business scenario: we would like to show a time series based prediction on a Design Studio dashboard. Because the datasource is near-realtime and rapidly changing, we would like to calculate the PAL function on applications request. how can this be achieved?
Furthermore I was not able to integrate ordinary db views in an analytical-view (it seems to only support tables? does anyone know the reason why?)
thanks a lot!
matthias

Hi Mohler,
PAL is ultimately some set of database procedures . If you want to use it as HANA View, you may need to right scripted views and consume the same.
Analytic views are typically defined on at least one fact table that contains transactional data. Using analytic views you can create a selection of measures—sometimes referred to as key figures—, add attributes and join attribute views. Analytic views leverage the computing power of SAP HANA to calculate aggregate data, e. g., the number of cars sold per country, or the maximum power consumed per day.
Ref : https://cookbook.experiencesaphana.com/bw/modeling-data/modeling-concepts/views/
Sreehari

Grant privileges on DB View in HANA Trial

Hello!
I created DB View on my scheme. View uses table SNWD_BPA of EPMSAMPLEDATA schema. I created OData service with this View. I can browse content of metadata OData service without no issue.
https://s3hanaxs.hanatrial.ondemand.com/.../BusinessPartners.xsodata/$metadata
However, if I try to get to the element level like this:
https://s3hanaxs.hanatrial.ondemand.com/.../BusinessPartners.xsodata/BusinessPartners
I receive: exception 1: no.71000258 (ptime/query/checker/check_clause.cc:579)
Not authorized NO exception throw location recorded. Stack generation suppressed.
I executed successfully
call "HCP"."HCP_GRANT_SELECT_ON_ACTIVATED_OBJECTS"
But this doesn't help.
Does anyone know what privileges should be assigned to user and how can this be done?

I changed main idea of my OData service.
First, I created service with direct access to SNWD_BPA of EPMSAMPLEDATA. I created role with select access to SNWD_BPA of EPMSAMPLEDATA. But I used the wrong order of parameters with procedure call HCP_GRANT_ROLE_TO_USER.
Second time, I created view for access to SNWD_BPA of EPMSAMPLEDATA and changed Odata service. But view cannot be granted on trial hana cloud platform.
Current solution is: Odata service is same as first time and correct granted role.

External views with HANA as secundary database

Hi,
internally we have since some time a discussion on whether one can make external views in ABAP when HANA is your secondary database. According to the documentation it is not possible, but apparently the HANA-versions of Financial transactions do use them. These transactions are SAP standard transactions. It is difficult to convince our users/developers that this is not possible, when they see it is used in SAP standard ...
We do not get any clear answer to this problem. Also not from our consultants. The only remaining possibility seems to sketch a possible solution and ask you all some questions and make some statements to see if I am right.
I think this little sketch shows the landscape you need to make all this possible:
One cannot create an external view in Ecipse (ABAP in …) when you have HANA as a secondary database.
External views can only be created using AIE, not in SE11 in the GUI.
When these external views are created – using the described process – these views cannot even be displayed in the AIE when having HANA as a secondary database.
This is the message we get:
If you want to create an external view, you need a ‘landscape’ where HANA is you primary database. This means a supplementary R/3-ABAP and a supplementary HANA database, where all necessary tables do exist.
You have to develop you HANA artefacts (attribute views, analytical views, calculation views, …) in this separate landscape.
If you want to call them using external views, you have to do your developments here!
Based on these views you create external views in the AIE on this separate landscape. This way they exist in the ABAP dictionary in this system.
The name of the HANA-artefact and the external view in the ABAP dictionary have to be identical.
You copy the HANA artefacts to you first HANA (where you use it as secondary database). Copy, transport, … whatever.
You copy/transport your external view to your first ABAP dictionary.
Now you can use it in a SELECT with CONNECTION(“to_2ndary_hana”).
Is this correct? Or do I still miss something?
Thanks for any reaction.
Regard.
Kris
Message was edited by: Jens Weiler

Hi Kris,
except for "The name of the HANA-artefact and the external view in the ABAP dictionary have to be identical" all you points above are valid.
Let me say a couple of words about the external views, especially those delivered by SAP.
Assume you have a development system landscape like DEH (development system with HANA as primary DB), DEO (development system with another DB), QCS (quality system, doesn't matter which DB but receiving the consolidated transports of DEH and DEO), PDS (productive system with non-HANA as primary DB and a secondary DB connection to HANA).
In this heterogeneous landscape you can create HANA content in DEH (respectively in the HANA underlying DEH) and external views via the ABAP Development Tools. You can transport the HANA content (e.g. via the HANA Transport Container) as well as the external views (and database procedure proxies) to the QCS system. The dictionary content, i.e. external views and database procedure proxies are active - otherwise the import/activation will fail - but you cannot consume them. Consumption of external views in the QCS system will lead to runtime exceptions as the underlying HANA artefacts are not accessible. However, since all the dictionary content exists, i.e. external views, database procedures, and the HANA transport container and all of them are active, you can further transport them to the productive system PDS. Once the external view is available in PDS and the HANA artefacts are available in the "side-car HANA" (assuming for simplicity you just use the connection to the DEH HANA), you can consume the external view respectively the underlying HANA view via OpenSQL in conjunction with the CONNECTION statement.
The described procedure explains how SAP has been able to deliver external views. In our system landscape, we have development systems on HANA as well as systems using non-HANA as primary database - how exactly depends on the product etc. So once the colleagues developed their HANA views and created the external views on such a development system on HANA, we can deliver external views. You can consume these external views:
in a system using HANA as primary database (assuming of course you have also received the correct HANA content and everything has been activated properly)
in a system using HANA as secondary database and using the CONNECTION statement in Open SQL
In scenario 1. you are able to create external views yourself via the ABAP Development Tools, while in the second scenario you can neither view nor maintain the external view.
For database procedure proxies, there is a method to create the DB procedure proxies programatically (see http://scn.sap.com/thread/3498161).
Hope this clarifies your questions,
Cheers,
Jasmin

Private Reuse and Query views in HANA

When you create custom views (models) how would you classify as private, reuse and Query views?
In SAP provided views they classified the views into Private, reuse and query views.. we would like to categorize our views in the same way. Take a look at the attachment for how SAP provided views are classified.
thanks

Hi Vaithi,
This categorization of views is in SAP HANA Live, and functionalities are as below.
Private views are abstraction layer for SAP tables. These views are used in Re-use views. Private views cannot be modified.
Re-use views are built on top of Private views and we can use Re-use views to build Query views.
Query views are created on top of Re-use views and we use Query views for reporting in reporting tools.
In general when we create models, we don't categorize this way because we use Attribute views, Analytic views and Calculation views according to our requirement. But in HANA Live, all models are calculation views and hence they are divided into separate categories.
Are you planning to categorize models created by you or copying the HANA Live views and want to classify them?
Regards,
Chandu.

Call procedure while creating view in hana.

Can we call procedure while creating a attribute view like
CREATE VIEW "PAYROLLDBTEST"."@HourTransactionView"
"DocEntry",
"DocNum",
"EmpID",
"EmpCode",
"FullName",
"TableName",
"TranName",
"U_FromDate",
"U_ToDate",
"NoOfDays",
"U_FromTime",
"U_ToTime",
"NoOfHours",
"OvertimeHours",
"UnpaidDays",
"Weekends",
"Holidays",
"U_Remarks",
"U_BatchNo",
"ProjectCode"
) AS SELECT
T0."DocEntry" AS DocEntry,
    T0."DocNum" AS DocNum,
   T0."U_EmpCode" AS EmpID,
CALL PAYROLLDBTEST.GetEmpCodeFromEmployeeID('EmpID') ,              (getting syntax error here).
    GetEmployeeFullName("@TRANSACTION_HOURS".U_EmpCode) AS FullName,
      T0."U_TransactionType" AS TranCode,
    GetHourTableName("U_TransactionType") AS TableName,
     GetHourTransactionName("U_TransactionType") AS TranName,
    T0."U_FromDate",
    T0. "U_ToDate",
      DAYS_BETWEEN("U_FromDate", "U_ToDate") + 1 AS NoOfDays,
      T0."U_FromTime" AS U_FromTime,
       T0."U_ToTime" AS U_ToTime,
    IFNULL("U_WorkHours", 0) AS NoOfHours,
     IFNULL("U_OvertimeHours", 0) AS OvertimeHours,
    IFNULL("U_PaidDays", 0) AS PaidDays,
     IFNULL("U_UnpaidDays", 0) AS UnpaidDays,
    IFNULL("U_WeekendsCount", 0) AS Weekends,
     IFNULL("U_HolidaysCount", 0) AS Holidays,
      T0."U_Remarks",
       T0."U_BatchNo",
    T0."U_ProjectCode" AS "ProjectCode"
    FROM
    "@TRANSACTION_HOURS" T0
    INNER JOIN
    "OHEM" T1
    ON
     T1."empID" = T0."U_EmpCode";

Hello,
The problem could be a SAPGUI related problem... Whats the current sapgui patch level ? Does it work when you try on another wokstation with the same user ?
Could you please use SAPGUI 720 and update your patch level to 7 ? Then check the behaviour again.
Best regards
Rene

What is the best practice to replicate the change of an object name in HANA AT/AN view where there are dependent views in it?

Dear All HANA Studio Experts,
I'm using SAP HANA Studio Version: 1.0.68 in our current landscape and looking for a expert and intelligent solution for a problem that we have encountered recently.
We have created multiple AT views, AN views and created CA views on top of these AN views to cater different LOB related to our organization. We have also designed BO universe on top of the CA views from HANA and finally created webi reports out of these universes.
In a particular scenario, we have one AT view which is been used by 10 different AN views.
Now we had 3 Requirements like below:
1. To add a new field in this AT view,
2. To update an existing field in this AT view and
3. To remove a field from this AT view which is not required anymore.
Problems Encountered:
Req 1. When we added a new field (e.g. XX_ADD) in the AT view and activate it, its throwing warning that there are dependent objects on this AT view. However no error thrown and it leads to re-work to check if this new field is available in all those dependent views and re-deployed those all.
Question: How to ensure if this addition of object will not impact the rest of the dependent views?
Req 2. When we updated an existing field (e.g. XX_UPDATE_NEW) in the AT view and activate it, its throwing warning that there are dependent objects on this AT view. However the BO reports built on top of these different dependent AN views became inoperative.
Question: How to ensure if we need to update the name of an existing object it will not impact the rest of the dependent AN views?
Req 3. Finally we have removed one object from the existing fields as it is not required. Again we faced warnings that there are dependent AN views on this AT view.
Question: How to ensure if we need to delete an existing object, it will automatically reflect in all dependent AN views?
Please suggest, if it is a good practice to create separate AT,AN and CA views for each of the LOB's and avoiding any dependent views (hence gradually the total no. of logical objects will be increase) or to reuse the AT/AN views whenever possible and in case of any updation/deletion we need to do a huge rework to check and redeploy the dependent objects again and again?
Thanks for reading this detailed explanation and please let me know in case you need any other inputs....don't hesitate to share your expert thoughts on this.

Hi Avishek,
Are you using Development or Modeller Prespective?
Avishek Chakraborty wrote:
Now we had 3 Requirements like below:
1. To add a new field in this AT view,
2. To update an existing field in this AT view and
3. To remove a field from this AT view which is not required anymore.
1) Adding a new Field in the AT View and after activating the view. Then you have to Refresh/Check out the dependent views to see if it is reflecting.
2) We cannot update the existing field in the AT view i.e like name change if it is being already used in joins in any of the dependent views. It will not allow you to activate
3) To remove the field which is not being used any where, we can make the changes in AT View and Refresh/Check out to see if the dependent views are reflecting the change
Regards,
Krishna Tangudu

Error while validating/activating views in SAP HANA

Hi,
I are getting below error while activating/activating view in HANA
"exception 40109:nrepository/base/activation/activator.cpp:176nRepository: Encountered an internal error in the repository code, this is most likely a bug in the implementation;Activator failed to retrieve/lock NRIV entry for domain activation_idnexception 71000139:nptime/query/plan_executor/trex_wrapper/trex_wrapper_body/trex_update.cc:2123n[2458] current operation cancelled by request and transaction rolled backn "
Please suggest why this error is coming & how can we rectify it.
Regards
Divyank Mehta

Hi Krishna,
I am getting same error while activating the View.HANA Studio version is 85.
Thanks

Connecting Hana view to SAP Lumira

Hi ,
I created a view in Hana system and used the Connect to SAP HANA One source option in SAP Lumira for the Dataset.
On the next screen i am able to see all views under different packages from HANA, but i am not able to see the new view created by me.
My questions -
1) Do i need to have certain privileges in order to see the newly created view in the view list at lumira level?
2) Any Steps which i am missing in addition to creating an anayltic view, adding a data foundation to the view ?
Regards
Chaitanya Sharma

Hi Chaitanya,
Check if the Schema and the package containing the AN view you have created is assigned to your USERNAME under Object & Package privilege respectively.
And while connecting to HANA System in Lumira login with the USER which has these assigned objects. Check if this helps
Regards,
Avinash Raju

WHY HANA VIEW ARE GIVING BAD PERFORMANCE IN DASHBOARD THEN TABLE

Dear Experts ,
I have created a dashboard on top of HANA view.
Scenario 1
HANA view is taking 3 seconds to fetch data in HANA studio .
When we create dashboard on that view, the dashboard is taking around 50sec.
Report has around 10 queries.
Scenario 2
Then we insert data into a table from same above view .
HANA table is taking 10 ms to fetch data in HANA studio .
When we create the same dashboard on that table, the report is taking
around 4 Seconds.
Report has around 10 query.
You may raise finger on dashboard tool. But by only converting view to table dashboard is giving good performance .
Please suggest what should we use Table or View for reporting tool ????
Only performance matter to Users and that's why we have taken HANA.
Thanks
Anupam.

"When you use attribute view in calculation view, hana will first build the attribute view first it will process all the data from memory in attribute view and then only will proceed with the calculation view."
That's actually completely false.
Attribute views are not materialized in full every time an Analytic View is queried. On the contrary, only the joins/materialization required to fulfill the query are performed. I have rolled out Analytic views with 50+ attribute views joined to them, if every one was built every time the AV was used, that would be a disaster.
An attribute view is fully executed if you query it directly with SQL, but the behavior changes when used in an AV.
Quick observation in good faith of my statement.
Query an analytic view with one column from a joined attribute view (Material - MARA)
SELECT "PAPH1", SUM("VVREV")
FROM "_SYS_BIC"."Main.Analytics.CO/AN_COPA"
WHERE "PERIO_T" = '2013010'
GROUP BY "PAPH1"
Only one join is executed to the fact table
Query an analytic view with one column from a joined attribute view (Material - MARA), plus another column from a joined table (T179T) inside the attribute view (snowflaked dimension).
SELECT "PAPH1", "VTEXT_1", SUM("VVREV")
FROM "_SYS_BIC"."Main.Analytics.CO/AN_COPA"
WHERE "PERIO_T" = '2013010'
GROUP BY "PAPH1", "VTEXT_1"
Only two joins are executed; one to the snowflaked dimension and one to the fact table
So even though I am issuing a query against an AV with a very large number of dimensions, only what is needed is actually executed.
Happy HANA,
Justin

HANA views call in ABAP ECC 6.0 via secondary connection

Dear Folks,
We have created views in HANA, same views we need to call it in ABAP ECC 6.0(Netweaver 7.3) i.e. via secondary database connection.
So,
1.Is it possible to call HANA vies in ABAP ECC 6.0?
2.Is there any version limitations? or will work fine on ECC 6.0
3. If yes can you give me sample code of abap to access hana as secondary database
Note : I have gone through Mr. Thomas Jung thread.
Regards,
Amol

Hi Amol,
so, ADBC is available in your system, but you have to make sure that the correct DBSL library for HANA (HDB) is available in your system. You can then just check if you can correctly communicate with the report ADBC_TEST_CONNECTION (using the secondary connection maintained in table DBCON) to your HANA database.
You may have a look at the example on how to select from an external view in report ADBC_QUERY (which selects from a DB table), by using a secondary DB connection to your HANA DB and using the HANA view instead of a DDIC table.
Of course in ADBC you have to take care about the correct type mapping (as you cannot use a DDIC type for definition of your internal table into which you select).
Best,
Jasmin
BTW: One word of precaution, the tasks you try to accomplish is rather cumbersome. We definitively recommend to use a more recent release (e.g. NetWeaver 7.4 SP5 or beyond), however, I think that's not your decision, right?

HANA view as source in Data Services

Hi Gurus,
I have a data flow in Data Services where an attribute view is used as source. That is data flow is running fine as of now.
As per an updated requirement, we have added couple of fields to the view additionally and have to use them in our data flow.
But, when I try to re-import the view into HANA, it is not allowing to do so. It is throwing an error that the table does not exist.
However, if I delete it from my repository and import it as a new one, it is working fine.
Could you please let me know if there is any specific way to re-import views from HANA into Data Services.
Thanks,
Raviteja.

SAP does not provide officially an SAP R3 connector for Data Federator 3.x.
There is a prototype though that you can download and use. Keep in mind though that this is no official SAP product yet..
SAP BusinessObjects Web Intelligence Reporting for SAP ERP [original link is broken]
Regards,
Stratos

"BW BEx - IDT - BO" or "BW export to HANA view - IDT - BO"

Hello Gurus,
The customer I work for is planning on moving to a BW on HANA environment. One of the questions that came up was around usability of BO in the post-hana world. Unfortunately I could not get hold of any customer experience to get to a logical conclusion.
Option 1 ) We continue to use the standard approach. Consume data from BW BEx queries via BICS connection into Business OBjects
Option 2 ) The second option comes with the feature that BW on HANA provider. You could export an Infoprovider into a view inside HANA(it has a setting to be enable during activation). This would mean we the same data could be consumed from a column-view via a normal RDBMS connection.
In terms of better performance and a stable architectural approach, what could be a better suggestion and why ...
Thanks,
Prabhu DC

Hi, Prabhu.
I wish I had an answer, but I just have a similar question. We have a customer considering moving from a BEX environment to HANA, and wants some use cases that would justify the move, and perhaps some customer stories. So far, I have come up dry.
If you should trip over anything that would help us, please let me know, and I will do the same for you.
Thanks, Prabhu.
Steve Phelan (not a guru)

Read ABAP CDS view data in HANA CDS view

Hi experts,
We have created some ABAP CDS views, which we would like to reuse in a HANA CDS view.
When I refer to the ABAP CDS view as "SAP<SYSID>"."Z_ABAP_VIEW_NAME" in the HANA CDS view definition, I get a syntax error: Cannot find artifact...
Is it possible to re-use the ABAP view in my HANA CDS definition?
Is there an alias for the SAP<SYSID> schema? When we apply the developments on a QA or PRD system, the name of the erp content schema will be different...
Kind regards,
Luk

Hi luk,
You can use the ABAP CDS views in HANA CDS. You have to change the schema name while creating the HANA CDS view.
@schema:'$<schema> ' should contain your ABAP CDS view then you can consume it. the artifact cannot be found because you are creating HANA CDS in a different schema.
regards,
Prabuddha

Access database view from JPA to HANA database, JDBC: [258]: insufficient privilege:

My java application is delopyed on neo.ondemand.com and use the hana database on cloud also, we use eclipselink
the jpa persistence configuration:
<property name="eclipselink.target-database" value="com.sap.persistence.platform.database.HDBPlatform"/>
here i do not specify any user or password to access the database, i think hana JDBC somehow hide the user information when java application and hana database both are on the cloud.
for the tables created by JPA itself, access if fine.
now i have created a view via Hana studio, though database tunnel using account dXXXXXXsapdev
i have an JPA entity, and i am trying to access the view from java application, it reports error:
Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.3.2.v20111125-r10461): org.eclipse.persistence.exceptions.DatabaseException Internal Exception: com.sap.db.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: [258]: insufficient privilege:
I do not know which database user is used by JPA to access the view, how can i grant the database rights on the view so that "native java application on cloud" can
access the database schema (or view created though database tunnel )
any comment is welcomed.

Hi,
Please post this issue under SAP HANA Cloud Platform space. The platform experts should be able to help with that.
Regards,
Ifat.

MultiProviders views in HANA

Similar Messages

Maybe you are looking for