cancel
Showing results for 
Search instead for 
Did you mean: 

How define infoprovider based on Calculation view in query

0 Kudos

I have 2 CV in composite , how to define which one by code name? (0infoprovider ch)

Abhishek_Hazra
Active Contributor
0 Kudos
rolo_tomasi

Is your question about how to identify the calculation views by the GUID? Or ...?

0 Kudos
abhishek.hazra

Yes, maybe there is a table like for query guid

Accepted Solutions (1)

Accepted Solutions (1)

Abhishek_Hazra
Active Contributor

Hi rolo_tomasi,

I am not sure if there is a table to directly look through & get the calculation view name from the technical GUID,
But you can use the class method : CL_RODPS_HANA_MODEL=>HASH_ODPNAME to get the GUID & prefix it with '2H' to get the link.
For example : You see the calculation views' name & package from hana studio, which are used in your HCPR.

in SE24 tcode, execute the method mentioned above.

with the package & calculation view names as shown below.

After execution you get the result in r_odpname as below. Disregard the '$T' part at the end & the rest part should be concatenated with '2H' at the beginning. That will give you the GUID you see in the query designer screen in your question's screenshot. For my example, in below, it should be 2HQ2M9WL97ZJ7ZZ6OYMIBMPKTSA.


Alternatively you can create a program to have that information handy for future passing the desired composite provider name as parameter. You can follow the answer : https://answers.sap.com/answers/353912/view.html.

Hope this helps 🙂

Best Regards,
Abhi

0 Kudos

Thank U , got it . In the end of name some trash symbols

HCSJ1B7VG7QS4K5I62FJWPPX5$T

Abhishek_Hazra
Active Contributor
0 Kudos

Good 🙂 And yes, that's what I mentioned to disregard in my earlier answer 🙂

0 Kudos

sorry missed it

Abhishek_Hazra
Active Contributor
0 Kudos

Hi Again,

Found out that you can get rid of those extra trash characters at the end if you pass value -1 to the parameter I_TYPEID, while executing the method 🙂


This is basically generating a hash value of 25, so you can directly use the following class method as well : CL_RSMDS_HASH_UTILITIES => TO_GUID_C25. Under I_DATA parameter pass the concatenated value of package & calculation view together with an underscore in between (no space), it will generate the same hash ID for you.



Best Regards,
Abhi

Answers (1)

Answers (1)

MKreitlein
Active Contributor

Hello Maxim,

can you check table: RODPS_HANA_ADMIN

Select your CV technical name without the 2H upfront.

I thought in this table you would find it...

BR, Martin

Abhishek_Hazra
Active Contributor

Hi Matrin,
Thanks for the nice info. But I have noticed that the table always does not contain entries for all the calculation views in the system, whereas the class can correctly generate a GUID for given package & calculation view combination anyway. Do you know the reason?

Best Regards,
Abhi

MKreitlein
Active Contributor
0 Kudos

Hi Abhi,

unfortunately I don't know... I just had the table name in an old documentation.

Sorry, Martin

Abhishek_Hazra
Active Contributor
0 Kudos

Just figured out, it generates an entry in the table when we consume the calculation view within a BW component like composite provider. But it was a nice info, thanks 🙂

Best Regards,
Abhi