Error creating External view on HANA Live model in CRM

[former_member187673]

Hi, I'm getting the following error when trying to create an External View on HANA Live models in CRM e.g. sap.hba.crm.BusinessTransactionType:

Generation of external view ZCRM_BUSTRXTYPE from DB view sap.hba.crm/BUSINESSTRANSACTIONTYPE

View sap.hba.crm/BUSINESSTRANSACTIONTYPE (schema _SYS_BIC) does not contain any columns in the database

We are on ABAP 740 and HANA Rev 73.

The tables referenced in the view are all in the Column Store.

Is there a restriction on creating external views on HANA Live models?

I made a copy of of the HANA Live model and was able to successfully create the External view on the copy.

Please advise.

Thanks

Peter

[JensWeiler]

Hi Peter,

problem could be, that the view is not working correctly:

Can you please check, if the sap.hba.crm/BUSINESSTRANSACTIONTYPE view is returning data if you wirte a SELECt in HANA (_SYS_BIC).

And also take a look if the view is present in the respective content folder ?

Cheers

Jens

[former_member187673]

Hi Jens, view exists in content folder and is working fine when I select from it in Studio SQL editor:

Could this be an authorization issue on sap packaged content as I can create external view fine on a copy of the view in non-sap package?

Thanks

Peter

[padmashree_b]

Hi Peter,

I suspect the name of the View. It is case sensitive and from the error also, it mentions as "sap.hba.crm/BUSINESSTRANSACTIONTYPE" while the artifact is "sap.hba.crm/BusinessTransactionType".

Quick question, did you browse for the View in the wizard or did you type the name of the View?

With the HANA Studio you can only create Views with upper case.

Kind Regards,

Padma

[JensWeiler]

Hi Peter,

thanks to Padma - I totally forgot about this problem. There is already a Note available for this:

1837708

Hope this helps

Jens

[former_member187673]

Hi Guys, you're on the right track here alright. I've checked the note and the correction is already implemented in the system however it seems there is still a bug there:

METHOD convert_nhi_dbviewname.

     DATA splittable TYPE STANDARD TABLE OF dbviewname.

     DATA wa_splittable LIKE LINE OF splittable.

     DATA no_lines TYPE i.

     DATA level_dbpackage_hierarchy TYPE i.

     " A typical name could be: packHier_1.Pack_hier2.Pack_hier3.VIEWNAME_A

     " This is to be converted to: packHier_1.Pack_hier2.Pack_hier3/VIEWNAME_A

     " Substitute the last '.' by '/'

     SPLIT nhi_dbviewname AT '.' INTO TABLE splittable.

     DESCRIBE TABLE splittable LINES no_lines.

     level_dbpackage_hierarchy = no_lines - 1.

     DO level_dbpackage_hierarchy TIMES.

       READ TABLE splittable INTO wa_splittable INDEX sy-index.

       IF sy-index < level_dbpackage_hierarchy.

         CONCATENATE dbviewname wa_splittable '.' INTO dbviewname.

       ELSE.

         CONCATENATE dbviewname wa_splittable INTO dbviewname.

       ENDIF.

     ENDDO.

     READ TABLE splittable INTO wa_splittable INDEX no_lines.

     TRANSLATE wa_splittable TO UPPER CASE. "To be sure...

     CONCATENATE dbviewname '/' wa_splittable INTO dbviewname.

   ENDMETHOD.                    "convert_nhi_dbviewname

The line I have highlighted is basically converting BusinessTransactionType to BUSINESSTRANSACTIONTYPE and therefore when it tries to look for the view in HANA it can't find it.

I confirmed that it will create the External View if there is no translation by converting the value back to BusinessTransactionType via the debugger.

Jens, do you know if there are any subsequent notes that address this line of code? I was unable to find any.

If not I will go ahead and log an incident to get this addressed.

Thanks

Peter

[JensWeiler]

Hi Peter,

we are still analysing the problem - could you just help us a little more and tell us the SAP BASIS SP Level of your system ?

Thanks a lot

Jens

[former_member187673]

Thanks Jens. We are on Release 740 SP 5.

[JensWeiler]

Hi Peter,

as I have just seen, you have already opened a ticket. This is in process and will most probably fix the issue.

Cheers

Jens

[former_member187673]

Hi Jens, yeah created a ticket there earlier so will see how it goes, thanks.

[Former Member]

Please check SAP note 1932922, it will help to solve the issue.

[former_member187673]

Thanks Tim, just got same advice in my ticket. This has solved the problem. Thanks All.