To avoid manual work in transporting Scripted Calculation views

To avoid manual work in transporting Scripted Calculation views

Disclaimer: This article is completely based on my learning experience and your suggestions are most welcome. I hope, this article will be useful for those consultants who are new to SAP HANA.

Overview

In transport scenario if the physical schema in the target system is not the same as the physical schema in the source system we will make use of schema mapping. The schema mapping works well with graphical models. In case of scripted calculation views if the schema names are mentioned along with the table name in the SQL script then we need to do the change manually in the target system. This manual work can be avoided by making use of default schema option in the Scripted Calculation views.

Note

                This works well when all the catalog objects used in the Scripted Calculation views are of from same schema.

Description

                In source system we have a table named CUSTOMER_DATA in schema ABCD. We  create a simple Scripted Calculation view using this table.

Instead of mentioning the schema name in the SQL script we will mention it in the default schema option in the semantics section.

In the target system we will create a Schema mapping between ABCD schema and physical schema (DEVARAJJ) of the target system. The Schema mapping option will be available in quick view of the Modeler perspective.

Once the Scripted Calculation view has been transported to the target system it will automatically take data from the table in physical schema (DEVARAJJ) of the target system without any manual change in the SQL Script because of the schema mapping.