Different options to export artifacts across landscape (developer mode , delivery unit and LCM)
Schema mapping
Authoring Schema -> Physical Schema
(The schema mapping defined in the system also applies to the default schema property
of Analytic and Calculation Views)
(This is particularly useful in script based calculation views)
Administrator should normally maintain the Schema Mapping in the target system before
importing the package that contain the information models
When the schema has been created in the target system we should first
import all the relevant tables as first step. After that and before importing the
information models ,define Schema mapping
It is also possible to define Package Specific Authoring Schema
Information Models are stored into package and in order to export or import Packages They
must be included in a Delivery Unit
3.Hierarchies (level and Parent child) when to use level and when to use parent child
A parent-child hierarchy is a hierarchy of members that all have the same type. Consists
of values that define the hierarchy in a parent-child relationship and does not contain named levels.
This contrasts with level-based hierarchies, where members of the same type occur only
at a single level of the hierarchy.
Example:
Employee hierarchy might have no levels, but instead have names of employees who are
managed by other employees.
Employees can have titles, such as Vice President. Vice Presidents might report to other
Vice Presidents and different Vice Presidents can be at different depths in the hierarchy.
https://blogs.sap.com/2015/03/13/implementing-and-displaying-standard-hierarchy-
with-sap-hana/
Standard hierarchy is a tree hierarchy which is used to organize business processes of a controlling area.
The highest node of a standard hierarchy is normally the first business process group. The groups
created thereafter make of the remaining nodes of the standard hierarchy.
There are different standard hierarchies available in SAP ECC like cost center, profit center, cost element
etc.
There are three tables in SAP for groups in standard hierarchy.
SETHEADER
SETNODE
SETLEAF
The vision of SAP HANA smart data integration and SAP HANA smart data quality is to build the
data provisioning tier natively within HANA; to simplify the SAP HANA landscape by removing an
entire tier previously built with heterogeneous non-native tools.
The native integration capability of SAP HANA smart data integration is architected for on premise,
cloud or hybrid deployments, and supports all styles of data delivery including
Federated
Batch
Real Time (not all data sources)
The XSJob file enables you to run a service (for example, an XS JavaScript or a SQLScript)
at a scheduled interval.
Required roles
sap.hana.xs.admin.roles::JobAdministrator and sap.hana.xs.admin.roles::HTT
PDestAdministrator assigned to your use
a. name.xsjob // job schedule definition
b. name.xshttpdest // HTTP destination details
c. name.xsjs // Script to run on schedule
Plan Visualization
PlanViz is a built-in SAP HANA performance tool that provides information about
the runtime of specific queries on data models.
PlanViz offers insight into the data transfer between the join, calculation, OLAP,
and SQL engines, which is a crucial element of performance.
With this information, developers and administrators can pinpoint possible
bottlenecks in the system and identify how to optimize data models to address these
issues.
Provide estimation and actual runtime statistics for memory , CPU time ,parallelism and
total run time.
Can be saved in xml file and viewed latter