opensap hana1 week 02 database tasks loading modeling

Week 2 Unit 1: Database Schemasand Database Tables

© 2013 SAP AG. All rights reserved. 2Public

Database Schemas and Database TablesThe SAP HANA Repository

Object management, versioning,and transport

Software component deliveryand patching

Built-in support for translatabletexts

Support for server-baseddevelopment


Database Schemas and Database TablesThe SAP HANA Repository

Presentation logic

Control flow logic

Calculation logic

Client

Data Data artifacts

Control flow artifacts

Presentation artifacts

HANA

Manage all artifacts in onerepository

Presentation (UI)

Control flow (Application)

Data persistence:TablesViewsSchemas…


Database Schemas and Database TablesData Persistence in SAP HANA

Data persistence objects

Schemas

Tables

SQL views

Sequences

Procedures

…


Database Schemas and Database TablesDatabase Schemas for SAP HANA

Database object

Mandatory

Contains logical groups:TablesViewsProceduresSequences…


Database Schemas and Database TablesDesign-time Schemas for SAP HANA

Design-time object

Transportable

Plain text file

Mandatory file suffix(.hdbschema)

Repository activationcreates runtime object inthe catalog


Database Schemas and Database TablesDesign-time Schemas: Configuration Syntax (.hdbschema)

Mandatory syntax(.hdbschema)

Schema name keyword

Schema name

Authorizations


Database Schemas and Database TablesDatabase Tables for SAP HANA

Database object<package.path>::<TableName>

A set of data elements

Type:ColumnRow

Metadata:Constraints on tableConstraints on values in particularcolumns…


Database Schemas and Database TablesDesign-time Tables for SAP HANA

Design-time object

Transportable

Plain text file

Mandatory file suffix(.hdbtable)



Database Schemas and Database TablesDesign-time Tables: Configuration Syntax (.hdbtable)

Mandatory syntax(.hdbtable)

Schema name

Table typeColumn/Row…

Table columnsName, SQL type, length…

Data typesNVARCHAR, DATE, DECIMAL…

Primary key

Week 2 Unit 2: Sequences andSQL Views


Sequences and SQL ViewsDatabase Sequences for SAP HANA

Database object<package.path>::<SequenceName>

Generates an incremented list ofnumeric values

Ascending/descending order

Used by applications to:Reference sequence objectsGenerate primary key valuesIdentify table columns/rowsCoordinate keys across rows/tables


Sequences and SQL ViewsDesign-Time Sequences for SAP HANA

Design-time object

Transportable

Plain text file

Mandatory file suffix(.hdbsequence)



Sequences and SQL ViewsDesign-Time Sequences: Configuration Syntax (.hdbsequence)

Mandatory syntax.hdbsequence

Keywords:schemastart_withnomaxvaluenominvaluecyclesdepends_on_tabledepends_on_view

Usage:SQL Insert (NEXTVAL)


Sequences and SQL ViewsSQL Views for SAP HANA

Database object<package.path>::<ViewName>

SQL statements/queries

Join data from different tables


Sequences and SQL ViewsDesign-Time SQL Views for SAP HANA

Design-time object

Transportable

Plain text file

Mandatory file suffix(.hdbview)



Sequences and SQL ViewsDesign-Time SQL Views: Configuration Syntax (.hdbview)

Mandatory syntax

Schema name

SQL query:JSON notation (\”Name\”)Select fromleft outer join onorder bydepends_on_table/view

Joined table names:<package.path>::header<package.path>::item

Week 2 Unit 3: Authorizations


AuthorizationsAvailable Active Roles: Overview

Default Roles:CONTENT_ADMINMODELINGPUBLIC

Imported Roles:<PackagePath>::<RoleName>sap.hana.xs.admin::administratorsap.hana.xs.admin::viewersap.hana.ui5.db::SITE_DESIGNERsap.hana.ui5.db::SITE_USER


AuthorizationsBuilding Repository Roles: Create

Design-time object

Transportable

Plain text file

Mandatory file suffix (.hdbrole)

Repository activation creates runtimeobject in the catalog


AuthorizationsBuilding Repository Roles: Define

Role name

Extends another role

Privileges:SchemaSELECT, INSERT, UPDATE,DELETE, DROP…Application:ADMIN (EXECUTE, SAVE…)– System– SQL objects– Packages– Analytic

Commit/Activate


AuthorizationsBuilding Repository Roles: Grant Activated Role to a User

Grant role with_SYS_REPO procedure:

GRANT_ACTIVATED_ROLE

Grant parameters’ROLENAME’’USERNAME’

SQL procedure call

Week 2 Unit 4: EPM Demo Schema


EPM Demo SchemaAvailable EPM Demo Data

The EPM demo data includes thefollowing catalog objects:

Tables

Views

Sequences

Synonyms


EPM Demo SchemaEPM Demo Data: Tables

A table is a set of data elements thatare organized using columns androws.

EPM Tables:AddressesBusiness partnersEmployeesProductsSales orders…


EPM Demo SchemaEPM Demo Data: Views

A view is a virtual table based on thedynamic results returned in responseto an SQL statement.

EPM ViewsPurchaseOrderHeaderExt


EPM Demo SchemaEPM Demo Data: Sequences

A sequence is a database object thatgenerates an automaticallyincremented list of numeric values toidentify tables, columns, or rows.

EPM Sequences:Address IDEmployee IDPartner IDPurchase Order IDSales Order IDText ID


EPM Demo SchemaEPM Demo Data: Synonyms

A synonym is an alternative name fora database table.

EPM Synonyms:TCURCTCURFTCURNTCURRTCURTTCURVTCURW…

Week 2 Unit 5: Single File DataLoad of CSVs


Single File Data Load of CSVsAutomatic Table Data Load: Required Files

CSV fileHolds data, separated bycommas, to load into target table

Table Import ModelDefines target DB table for loadMandatory file suffix (.hdbtim)

Table Import DataConnects CSV file to data loadmodel file (.hdbtim )Mandatory file suffix (.hdbtid)


Single File Data Load of CSVsAutomatic Table Data Load: Source File

Data source file

Transportable, design-timeobject

Contains the values to loadinto the database table

Values separated by commas

Number of columns in CSVfile/ target table must match

Data types in target table/CSVcolumns must match


Single File Data Load of CSVsAutomatic Table Data Load: Import Model

Table import model file

Design-time object

Transportable

Mandatory file suffix(.hdbtim)

Specifies source file type

Defines the target table inthe database (“item”)


Single File Data Load of CSVsAutomatic Table Data Load: Import Data

Table import data file

Design-time object

Transportable

Mandatory file suffix (.hdbtid)

Connects the CSV source file tothe data load model file

Specifies the source CSV file


Single File Data Load of CSVsAutomatic Table Data Load: SQL Query to View Results

SELECTTOP 1000 *

FROMSchema nameWORKSHOPX_00Namespaceworkshop.sessionx.00.dataObject delimiterdouble colon (::)Table nameitem

Week 2 Unit 6: Attribute Views


Attribute ViewsOverview

Attribute views:Model an entity based uponrelationships of multiple sourcetables

Can contain:ColumnsCalculated columnsHierarchies


Attribute ViewsDefining Sources and Relationships

Define an attribute view:

SourcesThe main components of anattribute view are tables.

RelationshipsJoin fields in tables to get aconsistent definition of theoverall entity.


Attribute ViewsDefining the Output Structure

Example:Tables often contain alarge number ofcolumns.Add only the columnsyou really need in theoutput structure.

Output structureField selection


Attribute ViewsDefining Field and Column Properties

The properties of a view columnaffect the overall usage:

Key AttributeDrilldown-EnabledHidden


Attribute ViewsDefining Calculated Output Fields 1

To define a new calculatedoutput field that is based onexisting fields in the view,you can use:

Other output fields

Formulas

Conversion (unit of measureand currency)


Attribute ViewsDefining Calculated Output Fields 2

To define a new calculatedoutput field, you must specify:

The data type

The field width

The scale

The rule definition


Attribute ViewsData Preview

Preview the datadisplayed by the view


Attribute ViewsData Preview with Analysis

Week 2 Unit 7: Analytic Views

© 2013 SAP AG. All rights reserved. 2

Analytic ViewsOverview

Analytic Views:Leverage the computing power ofSAP HANA to calculate aggregatedataContain two types of columns– Attributes– Measures


Analytic ViewsSet Parameters

Assign a unique name forthe technical name of theanalytic view

Change the view type toAnalytic View


Analytic ViewsDefinition of Data Foundation and Logical Joins

Explanation of terms:

Data Foundation:Represents the tables used for defining thefact table of the view

Logical Join:Represents the relationship between theselected table fields (fact table) andattribute views


Analytic ViewsData Foundation View

The Data Foundation viewshows all the fields that canbe incorporated into thefinal model.

These fields are marked asoutput fields


Analytic ViewsLogical Join

The Logical Join viewdisplays only thosefields you have chosento include in this model,as well as the restrictedand calculatedmeasures that havebeen defined.


Analytic ViewsSemantics View

In the Semantics view,you can classify thecolumns andcalculated columns asattributes andmeasures.

You can also createvariables/inputparameters andhierarchies andassign variables to thecolumns.


Analytic ViewsCalculated Columns

There are many options for defining acalculated measure:

Aggregation, such as sum, minimum,maximum, and countData types, such as decimals, numbers,and so onExpressions or operatorsString, date math, conversion, and so on


Analytic ViewsRestricted Columns

The restriction for a measure is basedon an attribute value.

In the example, the measureRC_PRODUCT_CAT_NOTEBOOKSshows only Gross Amount valuesfrom the Product Category‘Notebooks’.


Analytic ViewsData Preview

The same options existhere as exist for theattributes view:

Raw dataDistinct valuesAnalysis

Week 2 Unit 8: Calculation Views


Analytic View

View or Table

Join

Calculation ViewsTwo Types


Calculation ViewsView Creation Wizard

Assign a unique name must bealphanumeric (A-Z; 0-9; _)

Select Graphic or SQLScript


Calculation ViewsSelecting Components

Select any tables, attributeviews, or analytic views toadd to the Calculationview.


You can add projection nodes to addextra fields. For example, adding thecurrency converted amount field

Calculation ViewsSelecting Components


Choose the fieldsthat should beavailable for thenext level

Calculation ViewsOutput Definition


Calculation ViewsCalculated Column


Calculation ViewsDefine Union


Calculation ViewsScripted Views Overview

DB Layer

Code

Traditional:“Data to Code”

New Model:“Code to Data”

Massive datacopies create

bottleneck

Transferminimumresult set

Application LayerApplication Layer

DB LayerCode


Calculation ViewsDefine Output Structure, Define Function and SQLScript


Calculation ViewsDefine Which Columns are Attributes or Measures

You need to selectthe attributes andmeasures for theoutput node.

Week 2 Unit 9: Analytic Privileges


SQLprivilege

SYSTEMprivilege

Packageprivilege

Analyticprivilege

Analytic PrivilegesTypes of Privileges

When you access the SAP HANA database, ensure that any access to data isbacked by corresponding privileges. Different schemas are implemented.

AuthorizationConcept

SQL PrivilegePrivilege SQL statementtype (for example,SELECT, UPDATE, andCALL ...)

Analytic PrivilegeAnalytic Privileges areused to provide row-level authorizationViews.

System PrivilegeUsed for administrativetasks.Sytem Privileges areassigned to users androles.


Analytic PrivilegesConcept

Analytic privileges control access to SAP HANA data models.

You can implement row-level security with analytic privileges. However, youcan restrict access in a given data container to selected attribute values,such as:

Field from Attribute viewField from Attribute view used in Analytic viewPrivate dimension of Analytic viewAttribute field in Calculation viewCombinations of the aboveSingle value, range, IN-list


Analytic PrivilegesCreation

Define Name and Description

Choose the package


Analytic PrivilegesSelect Information Models

Select applicable InformationModels

Views have two functions inAnalytic Privileges– Views to which you want to grant

access

– View from which you want to selectfields for restrictions

You can add further views tothe privilege later


Analytic PrivilegesSelect Views

Restrictions apply to all views inlist of “Reference Models”

Choose “Add” in “Reference Models”section– Pick any appropriate view from any

package

Do not use the “Applicable to AllContent Models” option

Reason:– Can have surprising side effects– You give away control over model access


Analytic PrivilegesDefine Concrete Restrictions

You may implementvalue restrictions for allselected fields

If no value restrictionimplemented norestrictions (wildcard)Otherwise: user will onlybe allowed to see listedvalues


Analytic PrivilegesDynamic Analytic Privileges

Dynamic analytic privileges provide a more flexible approach. The actual filterconditions are obtained at runtime from a stored procedure, which cancontain complex logic.

This enables you to:Reuse the same analytic privilege for several usersChange the filter condition in the underlying tables and views without having to change theanalytic privilege itself

Example:The stored procedure in theanalytic privilege queriesthe user‘s businessdepartment from an orgtable, and checks inanother table whether theuser has manager status.

Attribute Views

Analytic Views

Calculation Views

User3 restrictions

User2 restrictions

User1 restrictionsDynamicAnalyticPrivilege


Analytic PrivilegesIn a Role

The last step is toassign the differentprivileges to anauthorization role

Thank you

Contact information:

[email protected]

© 2013 SAP AG. All rights reserved. Public

© 2013 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation orwarranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Groupproducts and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothingherein should be construed as constituting an additional warranty.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and other countries.Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

© 2013 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation orwarranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Groupproducts and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothingherein should be construed as constituting an additional warranty.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and other countries.Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

opensap hana1 week 02 database tasks loading modeling

Documents