SAP HANA SPS 11 Modeling Enhancements Overview

1© 2014 SAP AG or an SAP affiliate company. All rights reserved.
SAP HANA SPS 11 – What’s New?
SAP HANA View Modeling
SAP HANA Product Management December, 2015
(Delta from SPS 10 to SPS 11)

© 2015 SAP SE or an SAP affiliate company. All rights reserved. 2
Disclaimer
This presentation outlines our general product direction and should not be relied on in making a
purchase decision. This presentation is not subject to your license agreement or any other agreement
with SAP.
SAP has no obligation to pursue any course of business outlined in this presentation or to develop or
release any functionality mentioned in this presentation. This presentation and SAP’s strategy and
possible future developments are subject to change and may be changed by SAP at any time for any
reason without notice.
This document is provided without a warranty of any kind, either express or implied, including but not
limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-
infringement. SAP assumes no responsibility for errors or omissions in this document, except if such
damages were caused by SAP intentionally or grossly negligent.

Agenda
Topics
 Overview What’s New in SAP HANA Modeling SPS11
 Calculation View Modeling Enhancements
 SAP HANA Studio Modeling Environment Enhancements
 Conversion SAP HANA Views to Calculation Views

SAP HANA SPS 11 – What’s New in SAP HANA Modeling
SAP HANA Studio Model Editor – Enhancements Overview
Enhanced and new capabilities in SAP HANA Modeler
 Calculation View Editor Enhancements
– Multitenant database remote Calculation Views
support as data sources
– Enhanced support for Right Outer-/Full Outer-Joins
– Implicit Union-node pruning enhancement
using union pruning metadata tables
– Support for AGG / DEV / VAR as aggregation functions
– SQL Expressions for filters, restricted measures and
default values for Variables
– Attribute value internal-/external conversion metadata
support
– Hierarchies enhanced properties
for member-cycle handling
 SAP HANA Modeling Environment
– Enhanced query caching (support transactional invalidation)
– Switch off "Import BW Models“ for B4HANA Systems
 Analytic Privilege Editor
– Hierarchy-based value help dialogs
– Support for Core Data Services artefacts
 Calculation View Migration support
– Attribute-/Analytic-View and Scripted Calculation View
conversion
– Classic Analytic Privileges conversion

SAP HANA Studio View Editor
New capabilities and enhancements in the SAP HANA Studio View Editor

SAP HANA SPS11 - Modeling Enhancements
Calculation View Enhancements – Multitenant data sources
Enhanced Multitenant data sources support
 Multitenant database container tables as data sources for
Calculation Views introduced with SAP HANA SPS10
 New support for remote Calculation Views
as data sources within Calculation Views
– Re-use of Calculation Views across multitenant database
containers, providing fastest cross-tenant database
connectivity using SAP HANA Views
 Note, present constraints to be considered
– Remote Script-based calculation Views or remote
Table Function are not directly supported as
– Remote Calculation Views as Dimensions within
StarJoin-Calculation Views, cannot directly be
referenced.
Search for View in remote tenant
Note, the database schema mapping is also applied to remote
calculation view data sources.

Calculation View Enhancements – Join Enhancements
Join Enhancements in Calculation Views
 Referential Join
– Now supported in standard joins nodes
(no longer restricted to star join nodes anymore)
 Full Outer Joins
– Now supported in standard joins nodes
– Restricted support with StarJoin nodes,
constrained to one dimension view only.

Calculation View Enhancements – Join Enhancements
Join Enhancements in Calculation Views
 Special join-types usage within StarJoin
– Full Outer-/Right Outer-Join are supported within StarJoin-
nodes, but constrained to one dimension view only.
– The Shared Dimension-View in the StarJoin-node related
with a full outer- or right outer-condition has to be the “last”
View in the StarJoin-node
o The respective DIM-View can be moved down to the last position
– A Calculation View validation rule will validate
the scenario.
The last / lowest
Dimension-View in the
Start Join node.
Here CVDIM_Products
Example scenario
For the products dimension,
you want to ensure also
dimension values unassociated
with facts shall be included in
queries results.

Union-Node Enhancements in Calculation Views
 Enhanced implicit Union-Node pruning support
– The database optimizer will prune the Union-data sources
based on the query and meta information provided in a
pruning configuration table
– The pruning configuration table contains value patterns,
which provide column value-based pruning information
related to the input sources
– Debug and trace tools, e.g. explain plan will show the
pruned data source access pattern
Union node to be
pruned
Union pruning configuration tableExplain plan shows only table SO_CurrentYear has been accessed
Calculation View Enhancements – Union (Pruning) Enhancements

Calculation View Enhancements – Union (Pruning) Enhancements
Union-Node enhanced implicit pruning
 Union pruning configuration table
– All columns must be of type VARCHAR or NVARCHAR only.
SCHEMA: Name of the schema that contains the calculation view
CALC_SCENARIO: Name of the calculation view in the format package/view-name
INPUT: Name of the data source in the union node.
COLUMN: Target column name, where the filter condition shall apply
OPTION: Operator. The following operations are allowed. (=, <, >, <=, >=, BETWEEN)
LOW_VALUE contains the comparison value for =, <, >, <=, >= or the low value for
BETWEEN
HIGH_VALUE: contains the high value for BETWEEN
– Note: The following rules apply for complex filter conditions
Different entries of the same column will be combined by OR.
The resulting entries of the different columns will be combined by AND.
The BETWEEN operator is a closed interval
Union pruning configuration table
The above example is an equivalent to the pruning
pattern for input source “u” as
('2000' <= C1 <= '2005' OR C1 = '2008')
AND
(C2 < '1998' OR C2 > '2005')

Calculation View Enhancements – New Aggregation Functions
New Aggregation Functions
 Support for new aggregation functions average,
standard deviation, variance in calculation view
aggregation-types nodes
– Is not recommended to use in stacked scenarios
– A default validation rule is issuing a Warning message
if used in stacked scenarios

Calculation View Enhancements – Transparent Filter Flag
Transparent Filter Flag incl. in column propagation
 The Transparent Filter will omit columns from unnecessarily
being used as part of aggregations (group by)
 This Flag is required when using …
– Queries on multi-node Calculation Views, where the queries contain
filters on columns that shall not be projected into lower aggregation
nodes or stacked views scenarios where the lower views have
count distinct measures
– Was required to explicitly specify on
each node
 Now Transparent Filter Flag is propagated
to semantics along with column itself

Calculation View Enhancements – Hierarchies
Hierarchy Enhancements
 Cycle handling in user-defined hierarchies
– User defined parent-child hierarchies may have to handle
cyclic relationship, depending on the processed hierarchy
input data
– Therefore a new property has been introduced providing
3 options, how cycle should be handled and processed:
Cycle Option Description
Break up at load time
[breakup]
Default behavior.
Cycles are broken up at load time. They might be traversed
incompletely if starting from within a cycle and not from the root node.
Which node is marked with IS_CYCLE = 1 depends on the initial
traversal during the hierarchy instantiation.
Error [false] Error in case the hierarchy navigation traverses a cycle
Traverse completely,
then break up [true]
Cycles are completely traversed once and then broken up.
The duplicate node is marked with IS_CYCLE = 1 in the result.

Calculation View Enhancements – SQL Expression Support
General SQL support within Expression Editors
 Explicit expression language selection
– Explicit distinction between Column Engine expression
and SQL Expression was introduced for Calculation
Columns with SAP HANA SPS10
 Now SQL expression are additionally supported in
–Filter expressions
–Restricted measure expressions
–Default values expressions for
Variables/Input Parameters

Calculation View Enhancements – SQL Expression Conversion
Expression conversion behavior
 Harmonized execution modes between Column
Engine- and SQL expression language
– Calculation View execution will try to optimize and unfold
any view operation into a SQL expression
Similarly if a SQL expression was used, but execution
optimization determine conversion into a column store
expression
– No result differences between use of a SQL vs Column
Store expression due to respective semantic functions
conversion
SAP NOTE: 1857202 - SQL Execution of calculation views
Example – Add sematic using a NULL-value
Within a column store expression, you want to use the
column store semantic addition behavior
1 + NULL = 1
This may implicitly get converted into a SQL expression
ADD_NAZ(1,NULL) = 1
Within a column store expression, you want to use the SQL
semantic addition behavior
SQLADD(1,NULL) = NULL
This may implicitly get converted into a SQL Function
1 + NULL = NULL

Calculation View Enhancements – Attribute Value Conversion
Attribute value conversion support with Calculation Views
 Default conversion functions for attribute columns
– 2 scalar functions can be specified per columns to maintain
conversion from internal to external format
conversion from external to internal format
– External formatted value is always a string (VARCHAR)
– “Preserve Order” can be additionally specified
– Client require to make of the BIMC metadata generated
in order to leverage the conversion capabilities
Stored
Data Type Format
Stored Data
Value
Formatted Value
Order
Preserving
ABAP Date 20150305 05.03.2015 No
ABAP Date
(order preserving)
20150305 2015.03.05 Yes
ABAP Time 221012 22:10:12 Yes
ALPHA (8 digits)
ABCDE ABCDE Yes
12345 000012345
Conversion example

Calculation View Enhancements – Attribute Value Conversion
Attribute value conversion support with Calculation Views
 Conversion with Variables and Parameters
– Variables and Parameters of type column implicitly inherit the
conversion properties (not displayed for variables)
– Parameters of type direct, static list, derived also allow explicit
assignment of conversion functions
 Usage scenario with BI Clients and custom applications
– Users will be prompted for formatted values,
– Those shall be converted using the specified
conversion scaler function
– Query uses value conversion expression in
variable filter where clause or
parameter clause

Calculation View Enhancements – Enhancing Query Result Cache
Enhancing Query Result Cache Controls
 Using query cache with HANA Views (introduced with SPS09)
– Query cache is only used for complex queries (group by …)
– Suitable to use read-mostly workload, same set of queries is executed
repeatedly, rather non-changing data, rather expensive queries
e.g. Smart Data Access queries
 Enhanced query result cache control properties
– Enabling/disabling the query result cache per view (may behave then
as referred in global / system result cache settings)
– View-specific invalidation control additionally supports “transactional”,
which will invalidate cache, once the underlying data is changed
Reviewing cache use.

Additional SQL Optimization
SAP HANA View Modeling – Recent Enhancements
Optimized Calculation View Execution
 Since SAP HANA Rev 62 the SQL optimization
can explicitly be determined setting
the “Execute In:” property to “SQL Engine”
 Since SAP HANA SPS9 the optimized execution
behavior implicitly evaluates to leverage
additional SQL optimization
 SAP HANA SPS10 optimization enhancements
include implicit optimized Star Join processing
Optimized execution for SQL-queries against Calculation Views
 The initial Calculation Engine optimization generates a single SQL statement across a stacked model,
which is then passed to the SQL optimizer
 The SQL optimizer adds additional optimizations and delegates operations to the best database execution
operator, e.g. delegate star join-nodes to the OLAP processing engine where possible
Calculation Engine Optimization
Calculation Views
SQL Optimization
includes
• Stacked Views /
SQL unfolding
• Cost-based
Optimization
• Delegate
processing to
best operator
* Implicit SQL optimization details are documented in SAP Note 2223597.

Visualize PlanCalculation View Debugger
SAP HANA View Modeling – Recent Enhancements
Performance Analysis & Query Insight Tools
Timeline – root cause analysis
Operator list
Explain Plan

SAP HANA Studio Modeling
Environment
New capabilities and enhancements in the Modeler- and Development perspectives
in SAP HANA Studio

Analytic Privileges Editor – SQL-based Analytic Privileges
SQL-based Analytic Privileges with CDS
 Now additionally support to apply SQL based analytic
privileges to Core Data Services artefacts (*.hdbdd)
– The CDS object must have enabled the
structureprivlegecheck propery

Analytic Privileges Editor – SQL-based Analytic Privileges
Hierarchy support with Analytic Privileges
 Modeled privilege restrictions support Hierarchy-use
(reference to Hierarchy-node column) and
Hierarchy-based value help dialog
for restriction value selection.
 Usage with
– SQL-based analytic privileges
– StarJoin-Calculation Views
secured by SQL-based analytic privileges
& Hierachy SQL access enabled
– Supported with Parent-Child Hierarchies

General Modeler – Miscellaneous Enhancements
General SAP HANA Studio Modeler Enhancements
 Export / Import of Delivery Units show progress bar
– UI shows progress and errors (e.g. connection errors)
– Cancellation of Export / Import-Job offered
 Multi-Select support e.g. for data sources in find / add
dialogs in model editor
– Executed in parallel as background jobs
for enhanced development agility
Cancel Job

General SAP HANA Studio Modeler Enhancements
 Switch off "Import BW Models“ for SAP BW 7.5, edition for SAP HANA
– Prohibiting the import of BW models in B4H system from SAP HANA Studio.

SAP HANA Studio Modeler Quick View new dialogs
 Delete Inactive Objects
– Deletes all inactive objects in a user’s
workspace or reverts to the last active version
of an object.
 Migrate
– Converting Attribute-, Analytic- and Scripted
Calculation Views
to new Graphical Calculation Views

Conversion approach to
Calculation Views
Attribute-, Analytic- and Scripted Calculation View conversion
to graphical Calculation View

Converting all SAP HANA Views to Calculation Views
Going forward with Graphical Calculation Views
 Graphically modeled Calculation Views target to unify all SAP HANA View capabilities,
with respect to functionality as well as performance
– Dimension-Type graphical Calculation Views replacing Attribute-Views
– Cube-/StarJoin-Type graphical Calculation Views replacing Analytic-Views
– Table Functions as Data Sources in graphical Calculation Views replacing Scripted-Calculation Views
– SQL-based Analytic Privileges replacing classic modeled Analytic Privileges
 Graphical Calculation Views in the new SAP HANA “environments”
– The web-based development workbenches/IDE for SAP HANA will only support modeling graphical Calculation Views
– The new SAP HANA Deployment Infrastructure will only support graphical Calculation Views
Converting your SAP HANA Views
 With SPS11 a migration utility is initially provided to support the conversion into Calculation Views
Note: As of SAP HANA SPS11 Calculation Views are not yet functional feature equivalent to Attribute- and Analytic Views (i.e. Temporal Join & Fuzzy search).
However for most scenarios equivalent performance can already be achieved since SAP HANA SPS10 and the introduced execution optimizations.

Going forward with Graphical Calculation Views
 Converting your SAP HANA Views
– Dimension-Type graphical Calculation Views replacing Attribute-Views
– Cube-/StarJoin-Type graphical Calculation Views replacing Analytic-Views
– Table Functions as Data Sources in graphical Calculation Views
replacing Scripted-Calculation Views
– SQL-based Analytic Privileges replacing classic modeled Analytic Privileges
 With SPS11 a migration utility is initially provided
to support the conversion process

Using the Migrate Objects Utility
 Converting Attribute- and Analytic Views
– In Step1, select the object types to convert,
additionally a migration Log can be enabled
– In Step 2 either choose individual views to be migrated or
by select complete packages
The default is that the views are replaced by calculation views
in the same package with the same name.
References in calculation views and analytic privileges
using the migrated views are adjusted.
Alternatively by selecting the checkbox “Copy and migrate“
the migration can be simulated by, then the calculation views
are stored as copies allowing to test and validate the
converted objects*.
1
2
*However references of the impacted objects are not automatically adjusted.

– Step 3 provides an overview what will happen during the migration
with respect to adjusting impacted objects.
– Step 4, the migration runs as a background job afterwards.
Once finished the log can be checked in the Job Log View
or in the folder specified under migration log path.
Note: The migration just saves the new objects.
You have to activate all the objects (including the deletions)
manually in one step by choosing Activate from the Quick View
3
4
When objects get „copied and migrated“ („Simulation
mode“), the utility does not display the list of impacted
objects.

– Step 5 Activate converted objects (incl. activate deletions)
using activate from the QuickView
– Note: If “in-place” conversion is chosen, during activation the
Attribute- and Analytics Views first need to be deleted.
Then in a second step, the Calculation Views can get activated.
.
5
5

 Converting Script-based Calculation Views
– Step1-3, migrate objects using the utility and review joblog
– Step 4, activate new objects
Graphical Calculation Views and
Table Functions
1
2
34

Converting Analytic Privileges to SQL-based Analytic Priv.
 SQL-based Analytic Privileges replacing classic modeled Analytic Privileges
– Step 1, select privilege conversion in the migration utility
– Step 2, select package
– Step 3, review impacted objects and
adjusted references
– Step 4 Review Joblog and migration-log
2
4
3
1

 A migration log records critical changes the utility performs during the migration
activity and provides information on the status
of the migration activity.
 Migration Log records the following details
– The total number of objects that you have selected for migration.
– The total number of objects successfully converted to new object types.
– The objects that require user actions before you can successfully activate those objects.
– The list of impacted objects whose references modeler could automatically adjust.
These impacted objects are also converted to the new object type.
– The list of impacted objects whose references modeler could not automatically adjust.
You have to manually select such impacted objects and
convert it to the new object types in a new migration step.
– For converting classical XML-based analytical privileges,
the log records the roles and users associated with the
analytic privileges.

General notes and recommendations
 Migration Rollback
– If migrated objects are not yet activated
– “Delete inactive objects” will delete the inactive calculation views and revert
the attribute and analytic views to the last active status before the migration.

General considerations and recommendation on how to approach a migration
 Object dependencies and package structures
– Dependencies between Attribute and Analytic Views
o When analytic views using attribute views as shared dimensions are migrated, any other used attribute views had to
be migrated as well before the actual migrated analytic view can be activated.
o Furthermore if such an attribute view is referenced in other analytic views, those have to get migrated as well.
Otherwise errors with reference to impacted objects will occur during activation of the dimension calculation view.
Therefore if this attribute views is referenced in analytic views in other packages, those have to be included in the
migration step as well.
– References to migrated objects in Calculation Views are automatically updated during activation, even if the packages
containing the Calculation Views have not been selected for migration.
 Migration procedure recommendation
– Several migration steps can be executed in order to reach a consistent state of all migrated objects.
– Then all migrated objects can get activated at once.
– This also allows to cancel the migration and to revert to the status before,
by choosing “Delete inactive objects” from the Quick View.

Considerations for converting Attribute- and Analytic Views
 Features and capabilities with different behavior in Graphical
Calculation Views
– Hidden columns have to be made visible during migration
or stay as missing in the resulting Calculation View
– Analytic views internally used row.count columns, will be made
visible during migration calculation view header property
“Count Star column" with row.count.
– Derived Attribute Views are migrated as multiple copies into new
calculation Views with no derive dependency anymore.
– All column filters in the attribute-/analytic views are converted to an
equivalent filter expressions in the new graphical calculation views
– Data Foundation with Input Parameter filter expression will be migrated
as extra projection nodes with filters.
– “Relational optimization”-Analytic View option will be dropped during
migration as the general Calculation View optimization are applied.
– Calculation views filter with an empty string,
thus more rigidly, if the HANA user property
“Session Client” is not set.
Capabilities not yet supported with
Graphical Calculation Views
– Temporal Join in Analytic Views
– Search Attributes in Attribute Views

Converting Analytic Privileges to SQL-based Analytic Priv.
Specific consideration for migrating Analytic Privileges
 Privilege differences for Dimensions in Calculation Views
– In order to access data from an Analytic View, it was sufficient to grant an analytic privilege, that
had the analytic view as the secured object.
– After the migration to a calculation view, all dimension views need to be added as secured objects
as well.*
 Dynamic Analytic Privileges referencing a procedure
– Requires manual adjustment and migration effort.
 Re-assign roles, users and SELECT privileges to the new SQL analytic privileges
– The migration log or job log will provide information on SQL analytic privileges which do not have
users or roles assigned to them.
 A single classic modeled analytic privilege maybe converted to multiple SQL-based
analytic privileges, which altogether provide the restricted access to the views.
– In such cases the new SQL analytic privileges have to be re-assigned to the users or roles.
– The migration log or the job log will provide information on SQL-based analytic privileges which do
not have any roles or users assigned to it.
*This migration behavior is targeted to be improved in a future release.

General migration procedure recommendations
 Take a back-up of all objects
– Before performing a migration activity, it is recommended to take a back-up of all modeler objects
 Start migration with a clean workspace
– Before you perform the migration activity it is recommended to have only models that are in the active state. After a
migration is complete, the new object types are in this inactive state. Starting with a clean workspace helps you identify
those objects that are impacted by the migration activity and also to undo the changes of the migration activity.
 Simulate the migration activity before migrating
– If you want to convert attribute views and analytic views to graphical calculation views, then it is recommended to first
simulate the migration activity and understand the impact of the migration. You can proceed with the migration after
analyzing the impact. For more information on simulating a migration activity
 Migrate information views before migrating analytic privileges
– If you want to convert information views and classical privileges to graphical calculation views and SQL analytic
privileges respectively, then in the first migration activity convert the analytic views or attribute views or script-based
calculation views to graphical calculation views and in the next migration activity convert the classically-modeled
analytic privileges to SQL analytic privileges.
 Undo migration changes can only be done before activating the objects using “Delete Inactive Objects”.

© 2015 SAP SE or an SAP affiliate company. All rights reserved. 43Public
SAP HANA SPS11 - Modeling Capabilities
Web-based SAP HANA View Editor – Status
Graphical View Editor for Calculation Views
 Editor for Graphical Calculation Views*
– Introduced with SAP HANA SPS09
– No Analytic- and Attribute-view Modeling support
 Component of the SAP HANA Web-based
Development Workbench
– Supports other database development objects like
table functions, roles, procedures, analytical privileges etc.
– Incl. SQL Editor support, Catalog, Security, Admin, etc.
*Web-based editors are future/mid-term innovation platform for SAP HANA development
tools, however currently not yet feature complete (SAP HANA SPS11).
 *Note, the web-based graphical
Calculation View Editor is planned to be
delivered post SPS11 as a component
of the SAP Web IDE for SAP HANA,
implemented as an XS Advanced
application and building on the HANA
deployment infrastructure.
*See SAP Note: 2233866 - SAP HANA XS Advanced Model SPS11 Release Note

SAP HANA SPS 11 – What’s New in SAP HANA Modeling
SAP HANA Studio Model Editor – Enhancements Overview
Enhanced and new capabilities in SAP HANA Modeler
 Calculation View Editor Enhancements
– Multitenant database remote Calculation Views
support as data sources
– Enhanced support for Right Outer-/Full Outer-Joins
– Implicit Union-node pruning enhancement
using union pruning metadata tables
– Support for AGG / DEV / VAR as aggregation functions
– SQL Expressions for filters, restricted measures and
default values for Variables
– Attribute value internal-/external conversion metadata
support
– Hierarchies enhanced properties
for member-cycle handling
 SAP HANA Modeling Environment
– Enhanced query caching (support transactional invalidation)
– Switch off "Import BW Models“ for B4HANA Systems
 Analytic Privilege Editor
– Hierarchy-based value help dialogs
– Support for Core Data Services artefacts
 Calculation View Migration support
– Attribute-/Analytic-View and Scripted Calculation View
conversion
– Classic Analytic Privileges conversion

How to find SAP HANA documentation on this topic?
SAP HANA Platform documentation
 What’s New – Release Notes
 Modeling
– SAP HANA Modeling Guide
– SAP HANA Modeling Guide for SAP HANA Web Workbench
 Development
– SAP HANA Developer Guide
 References
– SAP HANA SQL Reference
• In addition to this learning material, you find SAP HANA documentation on
SAP Help Portal knowledge center at
http://help.sap.com/hana_platform.
• The knowledge center is structured according to the product lifecycle:
installation > security > administration > modeling > development.
 So you can find e.g. the SAP HANA Modeling Guide
in the modeling section and so forth …

Where to find more information on SAP HANA View Modeling?
• Public Web
 www.sap.com hana.sap.com
 SAP Community Network scn.sap.com
http://scn.sap.com/community/developer-center/hana
http://scn.sap.com/community/hana-in-memory
 SAP HANA Academy https://www.youtube.com/user/saphanaacademy
• What’s new in SAP HANA (incl. SAP HANA View Modeling)
 https://blogs.saphana.com/2014/10/21/what-is-new-in-sap-hana-sps-09/
https://blogs.saphana.com/2015/06/16/new-sap-hana-sps10/
 New Hierarchy capabilities with SPS10 http://scn.sap.com/community/hana-in-
memory/blog/2015/07/09/new-hierarchy-sql-enablement-with-calculation-views-in-sap-hana-10-sps-10
• Watch SAP TechEd Online
 www.sapteched.com/online
Introduction to Data Modeling in SAP HANA (Virtual TechEd Hands-On Workshop)
New and Best Practices for Data Modeling with SAP HANA http://events.sap.com/teched/en/session/26543

Disclaimer
This presentation outlines our general product direction and should not be relied on in making
a purchase decision. This presentation is not subject to your license agreement or any other
agreement with SAP.
SAP has no obligation to pursue any course of business outlined in this presentation or to
develop or release any functionality mentioned in this presentation. This presentation and
SAP’s strategy and possible future developments are subject to change and may be changed
by SAP at any time for any reason without notice.
This document is provided without a warranty of any kind, either express or implied, including
but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or
non-infringement. SAP assumes no responsibility for errors or omissions in this document,
except if such damages were caused by SAP intentionally or grossly negligent.

SAP HANA SPS 11 Modeling Enhancements Overview

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (20)

Ähnlich wie SAP HANA SPS 11 Modeling Enhancements Overview

Ähnlich wie SAP HANA SPS 11 Modeling Enhancements Overview (20)

Mehr von SAP Technology

Mehr von SAP Technology (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

SAP HANA SPS 11 Modeling Enhancements Overview