Working and Modeling Content of Project Flashcards
Dependencies in Information Models
- Other Action->Data lineage
2. Other Action->Impact Analysis.
Show lineage
will not work on Shared Objects from Dim view in the STAR Cal View
Outline view
Jump to relavant col
Workspace-> Project-.> Module
Workspace can contain as many project as required with different name.
Project Creation will ask for Project template
MTA- Multi Target Application
Another project Template is SAP HANA Database Application Template.
Types of Modules which can be created.
SAP HANA Database (HDB) Module,
JAVA module
Node. JS module
HDB Module contains Design time files
- Tables.
- Tabes Data
- CV
- CDS views.
- Table functions
- Procedures.
- Analytical privileges
- Synonyms.
Persistence layer : Inside or External
- Standalone Application(Tables and data stored inside application as CDS)
- Pure Data Analytics application where data can be stored outside.
Namespace of Design time and Run Time objects
- Namespace are optional.
- Namespace for all design time object in same folder should be optional.
- Definition can be added at . HDINamespace.
CV, TF, PROC, AP
- Each Design time object defines only 1 Runtime Object.
2. Runtime Object name is defined inside the object content and should match design time file name.
Synon, CDS tables,CDS views, Roles.
One or Several runtime objects.
HDI container
If you delete a run time object via SQL , after you build it , you can again see the Runtime object
True
HDI container
If you create a run time object via SQL , after you deploy the container , you will not see this Table.
True.
Datasources for Calculation view
- It should be available inside HDI and corresponding Design time file available.
- Synonyms ref DB objects located in other schema.
If CV is ref by using the Database table created in Plain SQL in your container ,
Build of the CV will fail.
Key properties of HDI container.
- Container = Schema.
- DB objects are deployed into the Schema.
- Schema free.
- Direct ref not allowed , Synonyms must be used.
HDI container Configuration file
- .HDICONFIG - Binds design time objects with corresponding Build plugin.
- Without plugin , it is not possible to build the design time files.
- By default hidden.
- .HDICONFIG is always unnamed file, if you try to add any name, build will fail.
Database explorer
Technical user is SBSS.
Service Support Security Support.
Building Modelling Content
- Building modelling content means
a)Creating Runtime Objects from Design time
objects. HDB Module build
b) Project build and create the MTAR file.
b) Deploy them to the container( Schema) or to
target systems.
Build errors.
- Dependency checks is done end to end for whatever you are building.
- Project exported but not assigned to SPACE.Space in which you deploy the container service must be specified and Develeloper access on the user id in that space.
- Definition of Object on which this object is dependent is not yet provided or it is not yet build.
- Name Space inconsistency between Content of design time file and the name space property.
- Service to external schemas not defined and running in target space.
- Synonyms of external schemas are not build.
- Object specific error( e.g no measure in the cube).
- Object you build and ref object. ( col name between objects with dependency).
Rename the column
First we need to refactor the consuming view , then only build of the source View will be successful.
Synonynm
.hdbsynonymn and .hdbsynonymconfig
XSADVANCED Migration tool
All the steps are now taken care by the tool related to migration and once MTA file is generated , we need to deploy it.
