SAP HANA Basics For Developers: Part 5.8 Cross Container From Outside Our Project

This series is based upon SAP HANA on premise and SAP HANA, express edition - HANA 2.0 with XSA and SAP Web IDE for SAP HANA. Originally recorded in January 2019.

SAP HANA embraces the concepts of a micro-service architecture. This means that different parts of the same overall application might be separated into separate services. This is true also of the database services. So far we have purchase order data in our db module and access to the non-container schema, SFLIGHT and user data from the user_db HDI container within our project. However, we also want master data that already exists in a completely separate HDI container that has been installed from another MTA (Multi-Target Application).

In this video, we will configure access and synonyms between our local project container and an already existing container deployed on this system.

In order to perform this exercise in your own system, you will have to first download and deploy (with the –use-namespaces option) this MTA into your development space from:

[mandardukhande]

Hi, in this video at 10:30 mins you have executed build at correct level (DB module) only but still it got failed and at 13:10 min again you did build on same thing (DB module) . Could you please explain why build failed first time and it got successful in second time.

[rajkrishna]

How to make column case insensitive. For example I am creating a view using synonym select distinct { xyz }. But while deploying SAP is looking for column XYZ which is not there in the table/view. Column name is xyz not XYZ. How do i make the column insensitive column query? I want to do this in my .cds file.

[rajkrishna]

Does the db artifacts, synonym and the entity have to have the same name? Suppose my db atrifact in container 1 is abc and the synonym is xyz and the entity in the synonym container is def. will this scenario work where all three are named differently. I feel synonym and the entity ( with @cds.persistence.skip) has to have the same name or the entity name has to be same as the DB artifact for which we are creating synonym.