Tips, Experience and Lessons Learned from multiple HANA projects(TELL @ HANA – PART 1)
Its been some time that I have been working in HANA and related areas like SLT, Lumira, Fiori and so on.
So thought of sharing some topics here, which would be handy.
1) This series is exclusively for Beginners in HANA and all those HANA experts here, please excuse me 😎
2) These are some Solutions/Observations that we have found handy in our projects and am quite sure there would be multiple ways to derive the same result.
3) These series of documents are collaborative in nature. So please feel free to edit the documents,wherever required!
4) All the points mentioned here were observed in HANA system with revisions >= 82.
Part 2 of this series can be found here –> Tips, Experience and Lessons Learned from multiple HANA projects(TELL @ HANA – PART 2)
Part 3 of this series can be found here –> Tips, Experience and Lessons Learned from multiple HANA projects(TELL @ HANA – PART 3)
Part 4 of this series can be found here –> http://scn.sap.com/docs/DOC-65343
1) Related to HANA:
Use Case: We have a table in a HANA schema and we were asked if there is any option to find a where used list where the table has been used.
Table Name: STKO.
Solution: Go to schema SYS.
There you will find a view named OBJECT_DEPENDENCIES.
You will get the dependent information in that view.
In SQL Terms: SELECT * FROM “SYS”.”OBJECT_DEPENDENCIES” where BASE_OBJECT_NAME = ‘STKO’
–> Following is another way to see the ‘Where-Used List’:
In HANA Studio Left Navigator Pane > Catalog > Any Schema > Tables folder > Context Menu (Right click on the table), select option ‘ Open Defenition’
Then in the right hand side, below the editor pane along side properties tab you see the tab ‘ Where-Used List ‘
2) Related to HANA/SLT:
Use Case: We have a new SLT configuration enabled for a source system.
Which all tables would be created automatically under the target schema defined in the configuration?
Observation: We have created a Non-SAP configuration in SLT and MII_SQl was the configuration name provided in SLT.
Now in HANA side, you will see that the schema MII_SQL has the following tables by default.
3) Related to HANA:
Use Case: We have a HANA Information View. We want to know the Number of records available in the output.
Solution: HANA Information View –> Semantics –> Data preview –> Show Log –> Generated SQL.
Copy the “SYS_BIC”.sap.hba.ZDBR44364/CV_FMIFIIT (My calculation view for this documement purpose)
Now write a SQl command.
4) Related to HANA:
Use Case: We need to connect to a HANA cloud system. How to do that.
Solution: Initially when we see the HANA studio, we will see the following:
Now Click, Install New Software
Once it is installed, you will now see the option to add the Cloud System in HANA Studio.
While connecting to the cloud system, you might encounter the following error:
Access the following path(Preferences) and make the required changes in the HTTP and HTTPS line items.
Some times, you might get a following error message.
This happens when the service is temporary down and you should be able to connect to the HANA cloud system after some time. So please try back after some time.
Sometimes, you might get the following error:
The work around that we had done to overcome this issue was to Reinstall the Kepler components again into the Eclipse/ HANA Studio.
5) Related to HANA:
Use Case: We have created a Information View, but it failed to activate with the following error message:
Solution: Execute the SQL command
GRANT Select on Schema <Schema_Name> to _SYS_REPO with GRANT option.
Once this SQL is executed, the model validation would be successful.
6) Related to Lumira:
Use Case: Lumira hangs during loading at the following screen.
Solution: This happens sometimes due to issue in user profiles.
Go to C Drive: Users –> Find User –> Delete the .sapvi file and try loading Lumira again.
7) Related to HANA:
Use Case: Using the option ‘SAVE AS DELIMITED TEXT FILE'(Comma Delimiter), I had to export a table which had columns containing values like the following,
Disclaimer: In Real time, this should not have happened as the ID with comma separation doesn’t look that good. 😛
If you observe closely, the ‘CMPLID’ column values itself is comma separated and when the same was exported, it was creating a new column after the comma separation in CSV file (the alignment of the columns were going wrong)
Solution: During the Export of the table from HANA, I had used the option ‘SAVE AS HTML FILE’.
Now once we got that HTML File, it was fed into a Third Party Solution ‘http://www.convertcsv.com/html-table-to-csv.htm‘
The HTML file was converted to CSV using that.
This can further be loaded back to HANA without any issues.
8) Related to HANA/SLT
Use Case: Some tables were missing in the Data Provisioning Option in HANA studio, in case of a Non-SAP source system scenario where the SLT configuration is already up and running since a long time.
Solution: This needs a little more explanation and the same has been published here in SDN few days ago. Please find the link below:
9) Related to HANA:
Use Case: You were performing lot of steps in HANA studio and in between you want to perform an activity whose link is available only in ‘Quick Launch Screen’, but it is not seen in UI.
Solution: You Can go to the following option to ‘Reset Perspective’
Or else, the following option can be used to get only the ‘QUICK VIEW’ screen.
10) Related to HANA
Use Case: SAP has delivered new DU’s (Say for Manufacturing OEE) and you have been asked to import the latest DU content to your HANA system.
Solution: Log into service.sap.com.
Click on SAP Support Portal.
Click on Software Downloads
Click on Support Packages and Patches
Click on A-Z Alphabetical List and select H
It will take you to a screen like below:
Download the MANUFACTURING CONTENT to your desktop. It will a ZIP File.
There will be a .TGZ file (Not LANG_.TGZ File) inside that and it needs to be imported into your system using the following option.
Once the Delivery Unit is successfully imported, you can check for the same in the ‘DELIVERY UNITS’ link in Quick Launch in HANA Studio.
11) Related to HANA:
Use Case : While trying to connect Join_1 and Projection, I was getting the following warning(Comapartment Changes). We tried all options to connect both the nodes, but system was not allowing us to do so.
Solution: Finally, we had to close the Whole View and relaunch it again. After doing that, we were able to join the nodes.
12) Related to HANA:
Use Case: For a POC/DEMO, We had to Generate huge number of Test Data/records(at the order of more than 1 Billion) into HANA Schema Tables.
Main catch here was that the whole activity was not just generating junk data but some meaningful data with some conditions.
2 Tools were available to fulfil our requirement.
1) DEXTOR –> You can get more details in this video:
2) HANA Data Generator:
Eventually we used the 2nd option, but there are some limitations and at times you find not get the expected results,but yes it is indeed a very nice tool
Sample screen where we had given some conditions:
NOTE: Please note that it was not working in JAVA 8 version and I had to uninstall 8 and install 6 for making the tool work
Hope this document would be handy! 😉
1929953 – SAP HANA Studio’s Content Folder missing from Modeler Perspective