SAP Hana Administration
Short Description
SAP HANA Administration Guide...
Description
SAP HANA Live for SAP Business Suite Administrator's Guide PDF download from SAP Help Portal: http://help.sap.com/saphelp_hba/helpdata/en/38/b9ea52e9fbe22de10000000a423f68/frameset.htm Created on May 07, 2015
The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal.
Note This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.
© 2015 SAP SE or an SAP affiliate company. 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 SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein 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 SE in Germany and other countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.
Table of content
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 1 of 44
Table of content 1 SAP HANA Live for SAP Business Suite Administrator's Guide 1.1 Getting Started 1.2 SAP HANA Live for SAP Business Suite - Overview 1.2.1 Virtual Data Models 1.2.2 SAP BusinessObjects Business Intelligence (BI) Solutions 1.2.3 Applications 1.2.4 SAP HANA Live Extension Assistant 1.3 Technical System Landscape 1.4 Installation Steps - General Information 1.5 Pre-Installation Steps 1.5.1 Prerequisites Checklist 1.5.2 Identify Scope of SAP HANA Live Installation 1.5.3 Install Required Version of SAP HANA Database 1.5.4 Installation of SAP Landscape Transformation Replication Server 1.5.5 Configuration of Replication Between Back End and SAP HANA DB 1.6 Installation and Maintenance Process 1.6.1 Create Database Tables (Side-by-Side Only) 1.6.2 Configure Schema Mapping 1.6.3 Download and Deploy Content Package 1.6.4 Installation Information for Virtual Data Models 1.6.5 Installation Information for Applications 1.6.6 Maintenance and Update Process 1.7 Configuration Steps 1.7.1 Generate Time Data 1.7.2 Replicate Data (Side-by-Side Only) 1.8 Post-Installation Activities 1.8.1 SAP HANA Live Browser 1.8.2 Recommended SAP BusinessObjects BI Solutions 1.8.3 SAP Invoice and Goods Receipt Reconciliation 1.8.4 SAP Access Control 1.8.5 SAP Supply Chain Info Center 1.8.6 SAP Working Capital Analytics 1.9 Operation Information 1.9.1 Technical Operations 1.10 Security 1.10.1 User Administration and Authentication 1.10.2 Authorizations 1.10.2.1 Privileges 1.10.2.2 Authorization for SAP HANA Live for SAP SCM 1.10.2.3 Authorization for SAP Invoice and Goods Receipt Reconciliation 1.10.2.4 Authorization for SAP ERP - Production Planning 1.10.2.5 Authorization for SAP Access Control Role Analytics 1.10.2.6 Authorization for SAP HANA Live for Manufacturing 1.10.2.7 Authorization for SAP HANA Live for Global Trade Services 1.10.2.8 Authorization for SAP Working Capital Analytics 1.10.2.9 Authorization for SAP HANA Live for SAP CRM 1.10.2.10 Authorization for SAP HANA Live for SAP CRM and SAP ERP Cross-An 1.10.2.11 Authorization for SAP HANA Live for Risk Management 1.10.2.12 Authorization for SAP HANA Live for Utilities, edition for SAP C 1.10.2.13 Authorization for SAP HANA Live for Product Revenue Accounting 1.10.3 Communication Channel Security 1.10.4 Communication Destinations 1.10.5 Internet Communication Framework Security 1.10.6 Data Storage in SAP Invoice and Goods Receipt Reconciliation 1.10.7 Cross-Site Request Forgery (XSRF) Protection
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 2 of 44
1 SAP HANA Live for SAP Business Suite Administrator's Guide 1.1 Getting Started About this Document This document is the single source of information for the implementation of SAP HANA Live for SAP Business Suite. It contains implementation information as well as security and operation information, and is divided into the following main sections: Introduction with references to related documents and relevant SAP Notes Overview of SAP HANA Live for SAP Business Suite Technical System Landscape Installation and Configuration Information Operation Information Security Information
Note SAP recommends that you read the Release Information Note 1778607 SAP HANA Live for SAP Business Suite.
, which informs you about the highest supported SAP HANA release available for
Related Information For more information about implementation topics not covered in this guide, see the following content on SAP Service Marketplace and on SAP Help Portal: Content SAP HANA Security Guide (including SAP HANA database security)
SAP HANA extended application services
Location on SAP Service Marketplace or SAP Help Portal http://help.sap.com/hana_appliance Guide
Security Information SAP HANA Security
http://help.sap.com/hana_appliance Developer Guide
Development Information SAP HANA
Latest versions of installation and upgrade guides General information about SAP HANA Live for SAP Business Suite General information about trigger-based data replication using SAP Landscape Transformation Replication Server
http://help.sap.com/hana_appliance
Installation and Upgrade Information
http://help.sap.com/hba http://help.sap.com/hana_appliance Installation and Upgrade Information Installation Guide – Trigger-Based Data Replication Using SAP LT Replication Server for SAP HANA Security Information Security Guide – Trigger-Based Data Replication Using SAP LT Replication Server System Administration and Maintenance Information Application Operations Guide – Trigger-Based Data Replication Using SAP LT Replication Server for SAP HANA Information about sizing: http://service.sap.com/sizing Sizing Guidelines Database and Technology SAP In-Memory Computing SAP Landscape Transformation Replication Server, SAP HANA
Released platforms and technology-related topics such as maintenance strategies and language support
http://service.sap.com/platforms To access the Platform Availability Matrix directly, enter http://service.sap.com/pam
Network Security High Availability
Information about Support Package Stacks, latest software versions and patch level requirements Information about Unicode technology at SAP Information about SAP Fiori for SAP Business Suite
http://help.sap.com/hana_appliance
Security Information
http://help.sap.com/hana_appliance System Administration and Maintenance Information SAP HANA Technical Operations Manual (TOM) http://service.sap.com/sp-stacks
http://service.sap.com/unicode http://help.sap.com/fiori
Further Useful Links The following table lists further useful links on SAP Service Marketplace: Content
Location on SAP Service Marketplace
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 3 of 44
Information about creating error messages
http://service.sap.com/message
SAP Notes search
http://service.sap.com/notes
SAP Software Download Center
http://service.sap.com/swdc
Ramp-Up Knowledge Transfer (RKT)
http://service.sap.com/rkt
Important SAP Notes You must read the following SAP Notes before you start the installation. These SAP Notes contain the most recent information on the installation, as well as corrections to the installation documentation. Some of the SAP Notes also contain source code corrections that need to be implemented. Make sure that you have the up-to-date version of each SAP Note, which you can find on SAP Service Marketplace at http://service.sap.com/notes SAP Note Number 1778607
1919137
.
Title
Description
SAP HANA Live for SAP Business Suite
This Release Information Note informs you about the supported SAP HANA releases, that is, it always informs you about the highest available support package stack and revision.
Release Information Note: Frontend Server Content for SAP HANA Live Analytical Applications
This note gives you additional information about the new UI for several products within the SAP HANA Live shipment.
SAP Notes Relevant for APO-Related Analytic Applications SAP Note Number
Title
Description
1784479
Collective Note for APO Planning Data Replication to HANA
This SAP Note is released for Support Package 02 or lower of SAP HANA Live for SAP SCM.
Data Replication from SAP APO to SAP HANA Live
This SAP Note is released for Support Package 03 or higher of SAP HANA Live for SAP SCM.
1863896
1854279
1904500
1945658
1955008
Data replication from SAP APO to SAP HANA Live SP03 This SAP Note describes the corrections delivered with the SP03. Data replication from SAP APO to SAP HANA Live SP04 This SAP Note is released for Support Package 04 or higher of SAP HANA Live for SAP SCM. Data replication from SAP APO to SAP HANA Live SP05 This SAP Note is released for Support Package 05 or higher of SAP HANA Live for SAP SCM. Documentation for data replication activities performed in
This SAP Note contains the documentation about the use
SAP HANA Live
of replicated data in APO-related analytic applications.
SAP Notes Relevant for SAP Supply Chain Info Center You must read the following SAP Notes before you replicate planning data for the analytic application of SAP Supply Chain Info Center: SAP Note Number 1887256
Title
Description
Configuration Required for Navigation to SAP APO
This SAP Note is released for Support Package 03 or lower of SAP Supply Chain Info Center. It describes the configuration steps that are required to enable the navigation from SAP Supply Chain Info Center to SAP APO.
1929737
Role Configuration for Navigation to SAP APO
This SAP Note is released for Support Package 04 or higher of SAP Supply Chain Info Center. It describes the configuration steps that are required to enable the navigation from SAP Supply Chain Info Center to SAP APO.
SAP Notes Relevant for SAP Landscape Transformation Replication Server SAP Note Number 1605140
1882433
1691975
1768805
1733714
Title
Description
Central Note – SAP LT Replication Server
Collective Note for all the relevant SAP Notes for SAP LT Replication Server for SAP HANA.
Installation/Upgrade SLT – DMIS 2011 SP5
Collective SAP Note that includes compatibility information and references to required corrections.
HANA LTR – Clarification on DMIS releases
This SAP Note describes the decision criteria for choosing the correct software version.
SAP LT Replication Server: Collective SAP Note – Non-
This SAP Note describes details about using the SAP LT
SAP Sources
Replication Server for non-SAP source systems.
Guide for Advanced Replication Settings
Provides additional information about transaction IUUC_REPL_CONTENT to specify advanced replication settings.
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 4 of 44
1.2 SAP HANA Live for SAP Business Suite - Overview SAP HANA Live for SAP Business Suite provides enhanced quality for analytics across all Business Suite applications by enabling industry-standard access to SAP data through easily understandable data models. The SAP Business Suite application data models – optimized for data throughput and best performance in transactional scenarios – are optimized for analytic purposes using views in the SAP HANA database. These views form a virtual data model that customers and partners can reuse. The virtual data model is a foundation for future SAP analytic development. Data provided by the virtual data model can be presented through multi-purpose analytical UIs, such as SAP BusinessObjects BI Suite UIs, and domainspecific web applications.
SAP HANA Live Architecture
Features A virtual data model Analytical applications on top with rich client UIs SAP HANA Live for SAP Business Suite provides the following advantages compared to regular reporting solutions: Open Any access to the reporting framework is based on standard mechanisms such as SQL or MDX. No BW modeling or ABAP programming will be required. Uniform One approach is chosen for all SAP Business Suite applications, enabling a common reporting across application boundaries. Intuitive The virtual data model hides the complexity and Customizing dependencies of our SAP Business Suite data model to make data available without requiring a deep understanding of SAP models. Fast SAP HANA Live for SAP Business Suite features SAP HANA as the underlying computing engine, to enable fast analytics on high data volumes. Real-time Since all reporting happens on primary data (or a real-time replication of it), there is no need to wait for data warehousing loading jobs to finish. The cycle time from recording to reporting is dramatically reduced. Virtual data models provide the foundation for operative reporting based on SAP HANA. They allow for the consumption of business data through generic analytical clients such as SAP BusinessObjects Analysis, edition for Microsoft Office and/or scenario-specific analytical applications. The application is the UI on top of a virtual data model, which consumes the data in the underlying views. Applications visualize the data in an understandable way.
1.2.1 Virtual Data Models A virtual data model (VDM) is a structured representation of HANA database views used in SAP HANA Live for SAP Business Suite and follows consistent modeling rules. It provides direct access to SAP business data using standard SQL or OData requests. Business data is exposed through well-defined database views, operating directly on the tables of the SAP Business Suite systems and transforming them into consistent and easily understandable views. These views can be consumed directly by rich client UIs (such as HTML5, SAP BusinessObjects, and Excel) without any additional software layer (an ABAP application system, for
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 5 of 44
example) in between (two-tier architecture).
Structure A virtual data model consists of the following types of views: Query views are designed for direct consumption by an analytical application (based on HTML5, for instance) or a generic analytical tool (for example, BusinessObjects tools). They are always the top view in a hierarchy of views and are not designed for reuse in other views. However, the virtual data model also includes query views to support (showcase) applications based on the virtual data model.
Note The interface of the query views is kept stable. The name of a query view ends with Query and provides output fields in a format consumable by UIs:
Example CostCenterPlanActualCostsQuery Reuse views are the heart of the virtual data model. They expose the business data in a well-structured, consistent and comprehensible way, covering all relevant business data in SAP Business Suite systems. They are designed for reuse by other views and must not be consumed directly by analytical tools. Private views encapsulate certain SQL transformations on one or several database tables or even other views. They are not classified as reuse views, as they might not carry clear business semantics, but are rather intended to be reused in other views. They are comparable to subroutines or (private) methods in programming languages. A private view may be based on database tables, other private views, or on reuse views. Value help views (VHVs) provide the value list for a specific business entity that is used in a value help in a query view. Relevant business entities are specified by an identifier or code. A maximum of one VHV is defined for each business entity per package. A VHV is included either in an underlying package to the business query views that make use of it, or in the same package. In SAP HANA, for each main package a specific VHV exists for a specific business entity. You can find a complete list of views in the SAP HANA Live Browser. For information about classification views, see SAP Note 1892589
.
For information about variant configuration views, see SAP Note 1987669
.
Enhancing SAP HANA Live Note that you cannot extend views delivered by SAP directly; you must make a copy first. For more information about how to enhance SAP HANA Live, see https://scn.sap.com/docs/DOC-44726
.
Note that this link intends to serve as a hint where to find supplementary documentation. SAP does not warrant the availability and correctness of such supplementary documentation or the ability to serve for a particular purpose. SAP shall not be liable for any damages caused by the use of such documentation unless such damages have been caused by SAP's gross negligence or willful misconduct.
1.2.2 SAP BusinessObjects Business Intelligence (BI) Solutions You can, for instance, consume the virtual data models with SAP BusinessObjects BI Solutions. For more information, see Recommended SAP BusinessObjects BI Solutions.
1.2.3 Applications HTML5 applications visualize the data from the virtual data models and allow you to analyze your data in an easy to understand way. Name of Application
Technical Name of Application
Area
SAP HANA Live Browser
HCO_HBA_AF_EXPLORER
All
SAP HANA Live authorization assistant
HCO_HBA_AAA
All
SAP HANA Live extension assistant
HCO_HBA_T_EXTN
All
SAP Invoice and Goods Receipt Reconciliation
HCO_HBA_APPS_GRIRM
SAP ERP
SAP Access Control
HCO_HBA_APPS_GRCA
SAP GRC
SAP Supply Chain Info Center
HCO_HBA_APPS_APOAN
SAP SCM
SAP HANA Live for Manufacturing, option for performance management
HCO_HBA_APPS_OEE
MFG-MPM
SAP Working Capital Analytics
HCO_HBA_A_WCA_DSO_U
SAP ERP
HCO_HBA_A_R_APF HCO_HBA_A_WCA_DSO_S HCO_HBA_A_WCA_DPO_U HCO_HBA_A_R_APF HCO_HBA_A_WCA_DPO_S
SAP HANA Extended Application Services
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 6 of 44
The applications are based on SAP HANA extended application services.
1.2.4 SAP HANA Live Extension Assistant With the SAP HANA Live extension assistant, you can extend query or reuse views delivered by SAP. The tool is an eclipse plug-in for the SAP HANA studio. Extending reuse views You can extend reuse views using this tool. The extended views are created as new reuse views in the package you selected. The tool lists all the underlying columns from all underlying tables of a reuse view. You can select the column that needs to be added as an output of the view and a new extended reuse view is created. The newly added view column can only be of the type Attribute. Extending query views You can extend query views using this tool. The extended views are created as new query views in the package you selected. The tool lists all the underlying reuse views of a selected query view. For each of the reuse views, unused columns are displayed. You can select the required columns to be added to output of the view from the underlying reuse view. To extend query views, you can select underlying reuse views or extended reuse views. Extending existing extensions You can also extend views for which an extension already exists.
Note You can only select packages if you are authorized to create or activate content in these packages. SAP does not recommend that you modify any views created by the tool using the Modeler perspective. Note that, if you do, the tool can no longer be used to modify the views.
For more information, see SAP Help Portal at
http://help.sap.com/hba
Application Help SAP HANA Live Tools SAP HANA Live Extension Assistant .
Prerequisites You have installed the following software: Delivery unit HCO_HBA_T_EXTN.tgz SAP HANA Appliance Software Support Package Stack 08, revision 82 or higher For more information, see Download and Deploy Content Package.
Note You must assign the role sap.hba.tools.extn:roles::ExtensibilityDeveloper to users who would like to extend views using this tool.
Installation To install the SAP HANA Live extension assistant, perform the following steps in sequential order: 1. In the SAP HANA Studio, choose Help and then Install New Software. An installation window opens. 2. Enter the URL of software update site http://:80/sap/hba/tools/extn in the field Work with. The Installation window now lists the SAP HANA Live extension assistant as available software in the list of plug-ins. 3. Click Add to save the URL for easy retrieval. The dialog box Add Repository opens. 4. Select the plug-in for the SAP HANA Live extension assistant from the list of available plug-ins. Retain the remaining default selections and click Next. 5. A review window opens where you can verify the information you entered. Click Next. 6. The License Agreement window opens. Review the licenses and click I accept the terms of the license agreements. Then click Finish. 7. The Installing Software dialog box opens, where you can view the installation progress. 8. A warning message may appear stating that the software contains unsigned content. Click OK. 9. After the installation, a verification box opens asking you to restart SAP HANA Studio. Click Yes. 10. Restart the SAP HANA studio. Right-click query/reuse views and choose Extend View to extend the view.
1.3 Technical System Landscape The following diagrams provide an overview of the technical system landscape for SAP HANA Live for SAP Business Suite. You have two options: Side-by-side scenario Two separate systems where the data is replicated using SAP Landscape Transformation Replication Server.
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 7 of 44
Side-by-Side Scenario
Integrated scenario SAP HANA Live shares an SAP HANA appliance with the Business Suite system, whose data is used for SAP HANA Live. This scenario is recommended for source systems that run on SAP HANA.
Integrated Scenario
1.4 Installation Steps - General Information The SAP HANA appliance software comes pre-installed on a specific appliance hardware system delivered in conjunction with leading SAP hardware partners. This chapter describes the required installation and configuration steps for the SAP HANA Live content packages and applications.
Installation Process The diagram below depicts the required installation steps for both installation scenarios. For the integrated installation, only a few steps are needed. For a side-by-
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 8 of 44
side installation, the steps relevant for handling the table replication from the SAP Business Suite system into the side-by-side SAP HANA database are also necessary.
Overview of Installation Process
Integrated Scenario In the integrated scenario, you do not need to create and replicate the database tables, as they are already available in the SAP HANA database. They are maintained through the data dictionary of the corresponding ABAP Application Server. Therefore, all steps regarding table creation and data replication are not relevant in this scenario. Since the ABAP server creates all tables in one specific database catalog schema (typically ), this needs to be mapped to the authoring schema of the imported content packages. For more information, see Configure Schema Mapping and SAP Note 1800515
.
Side-by-Side Scenario In the side-by-side scenario, the database tables that are used by the SAP HANA Live products need to be replicated from the corresponding SAP Business Suite back-end system into the SAP HANA database. This is done using SAP Landscape Transformation Replication Server. If you want to execute SAP HANA Live views, the data from the corresponding tables must be available. SAP recommends to create all required tables as specified in the SAP Notes corresponding to the SAP HANA Live products, and to replicate the data only for those tables that are used in executed analytical scenarios. This ensures that no unnecessary data is replicated, that no unnecessary SAP Landscape Transformation Replication Server resources are consumed, and that no unnecessary DB memory is consumed. Later on, data for additional tables can be replicated on demand if you want to execute additional scenarios. For more information, see Replicate Data (Side-by-Side Only).
1.5 Pre-Installation Steps Before starting the installation process, it is important to identify the scope and the sequence of the SAP HANA Live products. The Prerequisites Checklist provides you with a quick overview; it is followed by sections that contain detailed information that is required for the installation process.
1.5.1 Prerequisites Checklist This checklist helps you to perform the implementation efficiently. System Details SAP HANA System
Production System
Example
Comment
System
Answer required
ld4711.sap.corp
Server ID
Instance
Answer required
00
system instance
SAP Landscape Transformation Replication Server System
Production System
Example
Comment
System
Answer required
SLT
system ID
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 9 of 44
Instance
Answer required
00
system instance
Client
Answer required
005
client of SLT system
System
Production System
Example
Comment
System
Answer required
ERP
system ID
Instance
Answer required
00
system instance
User for replication
Answer required
010
client of back-end system
Back-End System
Password for replication user
Prepare password to be available during configuration. Do not note it down here for security reasons.
System Prerequisites SAP HANA Version Check that the correct version of SAP HANA is installed
Expected Value
Your Version
SAP HANA Appliance Software
Support Package Stack 08
Answer required
SAP HANA Studio Software
Support Package Stack 08
Answer required
SAP HANA Lifecycle Manager
Latest Version
Answer required
SAP Landscape Transformation Replication Server Installation Install SAP Landscape
Expected Value
Your Version
Comment
Transformation Replication Server Decide on installation option for SAP
Answer required
Landscape Transformation Replication Server (co-deployment in back end or separate server) Co-Deployment: No SAP Landscape Transformation Replication Server deployment needed, since SAP HANA Live VDM views operate directly on the SAP HANA DB Separate server:
SAP Landscape Transformation
a) Provide SAP Landscape
Replication Server is available as add-on
Transformation Replication Server
DMIS
Answer required
DMIS 2011 SP06 or higher recommended
and install it b) install SAP Landscape Transformation Replication Server add-on on back end
Connectivity RFC Destination from SAP Landscape Transformation Replication Server to Back End For communication from SAP Landscape Transformation Replication Server to the back-end system an RFC destination is required Provide the user ID of the user to be used to SLT_REP
Answer required
access the back end for data replication Password for user (data read from back
Prepare password to be available during
end)
configuration of RFC. Do not note it down here for security reasons.
Assign the necessary roles to this user
n/a
Maintain the profile of the role and assign
See chapter 5 of the Security Guide on SAP
the role to the user afterwards.
Help Portal at http://help.sap.com/hana_appliance Security Information Security Guide – Trigger-Based Data Replication Using SAP LT Replication Server
In transaction SM59 in SAP Landscape
Maintain RFC destination
Test RFC destination after it is created.
Transformation Replication Server, create an RFC destination of type “3”
Secondary DB-Connection from SAP Landscape Transformation Replication Server to SAP HANA For communication from SAP Landscape Transformation Replication Server to the SAP HANA DB system, a secondary DB connection is required User for setup of replication (already exists in SAP HANA
Answer required
Input needed in transaction LTR
DB) Password for setup user
Prepare password to be available during configuration. Do not note it down here for security reasons.
Define HANA DB schema name (schema into which data Answer required
Input needed in transaction LTR
get replicated) Define number of jobs to be used for data replication
Input needed in transaction LTR. Observe the additional hints in section Configuration of Replication Between Back
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 10 of 44
End and SAP HANA DB.
SAP HaNA Registration in SAP Solution Manager To download SAP HANA Live content, you can use SAP Solution Manager. If this option is chosen, you must register your SAP HANA DB accordingly Register the SAP HANA DB in the System Landscape Directory (SLD)
Answer required
1.5.2 Identify Scope of SAP HANA Live Installation Consider the following when planning the scope of your installation: the back ends must meet the requirements of the SAP HANA packages you want to install the sequence of packages to be deployed during the installation process You can find the information about the back-end requirements and dependencies either between SAP HANA Live products or to the SAP HANA database in the sections Installation Information for Virtual Data Models and Installation Information for Applications.
1.5.3 Install Required Version of SAP HANA Database To install the SAP HANA Live content, an SAP HANA database installation fulfilling the following prerequisites is necessary: SAP HANA Appliance Software Support Package Stack 08 SAP HANA Studio Software Support Package Stack 08 As of SAP HANA Appliance Software Support Package Stack 08, use the SAP HANA lifecycle manager for the most recent update if you already have the SAP HANA Appliance Software installed.
More Information For information about how to configure the SAP HANA lifecycle manager, see SAP Help Portal at http://help.sap.com/hana_appliance and Upgrade Information SAP HANA Update Guides SAP HANA Update and Configuration Guide .
Installation
For information about how to install SAP HANA Studio, see SAP Help Portal at http://help.sap.com/hana_appliance Installation and Upgrade Information SAP HANA Studio Installation Guide . The SAP Business Suite product for which the SAP HANA Live product is installed needs to fulfill some prerequisites. They are specified in the section Installation Information for Virtual Data Models.
1.5.4 Installation of SAP Landscape Transformation Replication Server (Side-by-Side Only) If you run the side-by-side installation, data must be replicated from the back ends into the SAP HANA database. SAP recommends to use the SAP Landscape Transformation Replication Server for this.
Note This should be completed prior to the installation of SAP HANA Live. Note that you must plan some time for the installation process. Install SAP Landscape Transformation Replication Server Install the SAP Landscape Transformation Replication Server as described in the corresponding installation guide and configure the connection from the SAP Business Suite source system to the target SAP HANA database. If you decide to install SAP Landscape Transformation Replication Server on a separate system, additional hardware is required. For the installation process, see SAP Help Portal at http://help.sap.com/hana_appliance
:
Installation and Upgrade Information Installation Guide – Trigger-Based Data Replication Using SAP LT Replication Server for SAP HANA Security Information Security Guide – Trigger-Based Data Replication Using SAP LT Replication Server Install Data Migration Server (DMIS) Add-On on Back End For the replication, the DMIS add-on is required in the back end for the communication between the back end and SAP Landscape Transformation Replication Server.
Caution Plan the DMIS installation in your back ends carefully. Important SAP Notes SAP Note Number 1605140
1882433
Title
Comment
Central Note – SAP LT Replication Server
Contains all SAP Notes relevant for LT Replication Server for HANA.
Installation/Upgrade SLT – DMIS 2011 SP5
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Collective SAP Note that includes compatibility
Page 11 of 44
1882433
information and references to required corrections. HANA LTR – Clarification on DMIS releases
1691975
Contains decision criteria for choosing the correct software version.
1768805
1824710
SAP LT Replication Server: Collective Note – Non-SAP
This SAP Note describes details about using the SAP LT
Sources
Replication Server for non-SAP source systems.
Installation/Upgrade SLT – DMIS 2011 SP4 / 2010 SP9
Contains information required if you want to install or upgrade the SAP LT Replication Server for SAP HANA using DMIS 2011 SP4 or DMIS 2010 SP9.
Installation/Upgrade SLT – DMIS 2011 SP3 / 2010 SP8
1759156
Contains information required if you want to install or upgrade the SAP LT Replication Server for SAP HANA using DMIS 2011 SP3 or DMIS 2010 SP8.
Installation/Upgrade SLT – DMIS 2010 SP7 / 2011 SP2
1709225
Contains information required if you want to install or upgrade the SAP LT Replication Server for SAP HANA using DMIS 2010 SP7 or DMIS 2011 SP2.
1.5.5 Configuration of Replication Between Back End and SAP HANA DB Once a configuration is created in SAP Landscape Transformation Replication Server, you use SAP HANA studio to initiate and control the table-based replication process of SAP Landscape Transformation Replication Server. For information about the configuration and replication process, follow the instructions given in the Application Operations Guide, available on SAP Help Portal at http://help.sap.com/hana_appliance System Administration and Maintenance Information Application Operations Guide – Trigger-Based Data Replication Using SAP LT Replication Server for SAP HANA :
Create Database Catalog Schema (Side-by-Side Only) During the configuration and replication process, a database schema must be defined in which the database tables are replicated. This replication schema must be mapped to the relevant authoring schema in the next step. This schema is automatically created in your SAP HANA database. For more information, see Configure Schema Mapping.
More Information For more information about how to improve the initial load, see http://scn.sap.com/community/replication-server/blog/2013/09/26/how-to-improve-the-initial-load-byrow-id-approach
. For more information about how to enable parallel replication, see http://scn.sap.com/community/replication-server/blog/2013/10/04/how-to-
enable-parallel-replication . Note that these links are intended to serve as a hint where to find supplementary documentation. SAP does not warrant the availability and correctness of such supplementary documentation or the ability to serve for a particular purpose. SAP shall not be liable for any damages caused by the use of such documentation unless such damages have been caused by SAP’s gross negligence or willful misconduct.
1.6 Installation and Maintenance Process Caution Note the following: For the schema mapping, the information Authoring Schema, given in the tables in section Installation Information for Virtual Data Models, is relevant. For the creation of the database tables, the information Tables for Replication, given in the tables in section Installation Information for Virtual Data Models, is relevant. SAP Notes, if required, are also provided there.
1.6.1 Create Database Tables (Side-by-Side Only) Once the schema and the schema mapping have been prepared, the required tables need to be made available in the schema. Since the tables and their replications consume system resources (depending on their size), SAP recommends to replicate the data only for tables that are actually used, and to merely create all other tables.
Prerequisites Ensure that you have completed all required steps described in Install Required Version of SAP HANA Database and Configuration of Replication Between Back End and SAP HANA DB.
Table Creation The tables that are needed before the deployment of a specific content package are specified in the SAP Notes that you can find in the tables in Installation Information for Virtual Data Models and Installation Information for Applications. Depending on whether you want to create or replicate tables, consider the following:
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 12 of 44
Table Creation If you want to only create the required tables, the list of tables must be added to the corresponding configuration table of SAP Landscape Transformation Replication Server. Note that, with DMIS 2011, SP06, this process has been considerably simplified. For more information, see SAP Note 1799313 Table Replication If you want the tables to be fully replicated, you can do so using the standard data provisioning view of the SAP HANA studio. The list of tables can be imported directly from the CSV file attached to the SAP Note.
.
More Information For more information, see Replicate Data (Side-by-Side Only). For information about the configuration and replication process, see SAP Help Portal at http://help.sap.com/hana_appliance System Administration and Maintenance Information Application Operations Guide – Trigger-Based Data Replication Using SAP LT Replication Server for SAP HANA :
1.6.2 Configure Schema Mapping You must set up a schema mapping to map the authoring schema of a content package to the physical database schema of the relevant tables. The authoring schema is the database schema that is referred to in the content package. In a customer system, the tables are typically stored in another database schema, namely either in the schema configured in SAP Landscape Transformation Replication Server (for the side-by-side scenario) or in the database schema of the ABAP installation (for the integrated scenario). For more information, see Configuration of Replication Between Back End and SAP HANA DB.
Required Steps In the SAP HANA Studio, in the Modeler perspective, on the Quick Launch tab, select the relevant SAP HANA system and choose Setup, then Schema Mapping to add a new schema mapping from the authoring schema to the physical schema.
Example Package sap.hba.ecc refers to the authoring schema SAP_ECC. In your customer landscape the ECC tables are replicated into schema CUSTOMER. Then a schema mapping from SAP_ECC to CUSTOMER needs to be added.
1.6.3 Download and Deploy Content Package Prerequisites Ensure that you have at least created all tables required for the activation, as described in Create Database Tables (Side-by-Side Only).
Downloading and Deploying Content Packages
Recommendation SAP recommends using SAP Solution Manager to install and update SAP HANA Live products and Maintenance Transactions. This allows you to deploy several product versions at once. Alternatively, you can download the required zip files directly from SAP Service Marketplace and deploy them manually. This means only single product versions can be deployed.
Note Your SAP HANA database has to be registered in the System Landscape Directory (SLD). In addition, your SAP HANA database must be created as a product system in the Landscape Management Database. You do this in SAP Solution Manager using transaction lmdb. This is necessary for the steps described under SAP Solution Manager below. For more information about how to register in SLD, see SAP Help Portal at http://help.sap.com/hana_appliance SAP HANA Update Guides SAP HANA Update and Configuration Guide .
Installation and Upgrade Information
SAP Solution Manager: Download product stacks (SAR and XML files) to deploy several product versions at once 1. In SAP Solution Manager, run transaction lmdb. On the Product Systems tab, select your product system and choose Display. 2. 3. 4. 5.
In the navigation tree, click on the top node (Product System). On the Maintenance Transactions tab, under Maintenance Optimizer Transactions, choose Create Transaction. Under Choose File Selection Mode choose Calculate Files Automatically and then choose Continue. On the Operations tab, under Change Options, select change option Support Package Stacks – Implementation of Support Packages and choose Continue. 6. If you are not yet running SPS 08 or higher, set it as your target stack under Select Target and choose Continue.
Note This will update your SAP HANA DB to SPS 08 or higher. 7. Confirm the Major Target by choosing Continue.
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 13 of 44
8. To choose your products, note the following:
Note If you are using Maintenance Optimizer 3.0, the Add-On Product List is created dynamically. You initially see only add-ons that can be installed directly on the SAP HANA database. If you want to install an add-on that requires another add-on to be installed, you must first select the required product version on which the product you want to install is based.
Example You want to install the product version SAP WORK CAPITAL ANALYTICS 1.0. For this product version to be listed, you must first have selected SAP HANA ANALYTICS FOR ERP 1.0.
9. 10. 11. 12. 13. 14.
15.
To find out the required product version of your product, see Installation Information for Virtual Data Models. If you product has several instances, you must select the instances you want to install manually. When your instance is selected, choose Apply. Follow this procedure for all products you want to install. When you are done, choose Continue. Under Select OS/DB-Dependent Files, expand the instance node under File Name. Select SAP HANA database and choose Continue. Under Select Files for Add-on Products, choose Continue. Under Select Stack-Dependent Files, under File Name, new database patches are pre-selected by default. If you do not want to install these patches, de-select them. You must not deselect OS-DB if you are upgrading your SAP HANA databse to HANA SPS 08. Choose Continue. Confirm the download basket by choosing Continue. On the Stack Files tab, download the System-Specific XML for SLM. Save and close the Maintenance Optimizer windows. Then download the calculated files using SAP Download Manager from SAP Service Marketplace. Make the downloaded files and XML files available on your SAP HANA appliance. As the SYSTEM user in the SAP HANA studio, right-click on the server node in the navigation pane, and select Lifecycle Management.
16. Select Apply Support Package Stack under Update SAP HANA System. 17. Choose Manually downloaded content, then browse to find the content you downloaded in step 5 and run the installation and update procedure. For more information about the Maintenance Optimizer, see SAP Help Portal at SAP Solution Manager Maintenance Management Maintenance Optimizer .
http://help.sap.com/solutionmanager71
Application Help SAP Library
SAP Service Marketplace: Download zip files to deploy single product versions manually
Note You must have updated your SAP HANA appliance to SPS 08 or higher. Ensure that you have installed the required product versions. The sequence of the zip-files installation must be done according to their dependencies. For this, the information Required Product Version, given in the tables in section Installation Information for Virtual Data Models, is relevant. Installation of SAP HANA DB SPS08 and lower 1. Go to https://service.sap.com/swdc Installations and Upgrades Browse Our Download Catalog SAP In-Memory (SAP HANA) SAP HANA Add-ons . 2. Download the zip files for the SAP HANA Live installation you require. 3. As the SYSTEM user in the SAP HANA studio, right-click on the server node in the navigation pane, and select Lifecycle Management. 4. Select Deploy HANA Content under Manage SAP HANA Applications Content. 5. On the screen Deploy SAP HANA Content choose the option From an accessible share or From a Personal Computer. 6. Under Path of remote HANA content ZIP archive, browse to the zip files you have downloaded. You can select and deploy only one zip file at a time. Choose Next. Ensure the correct installation sequence. 7. When you are done, choose Run. 8. Repeat steps 5, 6 and 7 for each SAP HANA Live product you want to install. For more information about how to configure the SAP HANA Lifecycle Manager, see SAP Help Portal at http://help.sap.com/hana_appliance Installation and Upgrade Information SAP HANA Update Guides SAP HANA Update and Configuration Guide . Installation as of SAP HANA DB SPS09 1. Go to https://service.sap.com/swdc Installations and Upgrades Browse Our Download Catalog SAP In-Memory (SAP HANA) SAP HANA Add-ons . 2. Download the zip files for the SAP HANA Live installation you require. 3. Ensure that you have configured SAP HANA Application Lifecycle Management as described in the respective section on SAP Help Portal at http://help.sap.com/hana_appliance Development Information SAP HANA Developer Guide . 4. Using hdbalm, install all the SAP HANA Live products you require. Follow the instructions described in the section Installing and Updating Add-On Products and Software Components on SAP Help Portal at http://help.sap.com/hana_appliance Maintenance Information SAP HANA Administration Guides SAP HANA Administration Guide .
System Administration and
1.6.4 Installation Information for Virtual Data Models The virtual data models listed below are available with SAP HANA Live for the different areas of SAP Business Suite.
Installation Information for SAP HANA ANALYTICS FOR ERP 1.0 Instance: HANA Content ECC Server Official Name
SAP HANA Live for SAP ERP
Name
SAP HANA ANALYTICS FOR ERP 1.0
Software Component
HANA CONTENT HBA SAP ECC 100 SP010 (technical name HCO_HBA_ECC)
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 14 of 44
Required Product Version
SAP HANA Platform Edition 1.0 SPS08, revision 82 or higher
Back-End Prerequisites (Minimum Version)
SAP ERP 6.0 SP 12 and all equivalent enhancement packages
Authoring Schema
SAP_ECC
Tables for Replication
See SAP Note 1781992
Installation Information for SAP HANA ANALY. ERP EHP4 1.0 Instance: HANA Content Central Appl. Official Name
SAP HANA Live for EHP 4 for SAP ERP
Name
SAP HANA ANALY. ERP EHP4 1.0
Software Component
HANA CON. HBA BS_FND_701 100 SP06 (technical name HCO_HBA_ECCFND701)
Required Product Version
SAP HANA ANALYTICS FOR ERP 1.0 SPS010, instance HANA Content ECC Server
Back-End Prerequisites (Minimum Version)
EHP4 for SAP ERP 6.0
Authoring Schema
SAP_ECC
Tables for Replication
See SAP Note 1781992
Instance: HANA Content for Insurance (FS-CM and FS-CD) Official Name
SAP HANA Live for EHP 4 for SAP ERP
Name
SAP HANA ANALY. ERP EHP4 1.0
Software Component
HANA CONTENT HBA INSURANCE 100 SP08 (technical name HCO_HBA_FSCX604)
Required Product Version
SAP HANA ANALYTICS FOR ERP 1.0 SPS010, instance HANA Content ECC Server Deploy and activate the ECC views BusinessPartnerName and BusinessPartnerCategoryName required for FS-CM from package HCO_HBA_ECC prior to deploying FS-CM views from package HCO_HBA_FSCX604.
Back-End Prerequisites (Minimum Version)
EHP4 for SAP ERP 6.0 Add-On Insurance
Authoring Schema
SAP_ECC
Tables for Replication
See SAP Note 1847454
Instance: HANA Content HCM Renewal Official Name
SAP HANA Live for EHP 4 for SAP ERP
Name
SAP HANA ANALY. ERP EHP4 1.0
Software Component
HANA CONT. HBA HCM RENEWAL 100 SP06 (technical name HCO_HBA_APPS_HCMR)
Required Product Version
SAP HANA PLATFORM EDIT. 1.0 SPS08, revision 82 or higher
Back-End Prerequisites (Minimum Version)
EHP4 for SAP ERP 6.0 Stack 11 Instance: Human Capital Management
Authoring Schema Tables for Replication
SAP_HCM See SAP Note 1849168
Installation Information for SAP HANA ANALY. ERP EHP7 1.0 Instance: HANA Content Central Appl. VDM Official Name
SAP HANA Live for EHP 7 for SAP ERP
Name
SAP HANA ANALY. ERP EHP7 1.0
Software Component
HANA CONT. HBA SAPAPPL607 100 ISS (technical name HCO_HBA_APPL607)
Required Product Version
SAP HANA ANALY. ERP EHP4 1.0 SPS08, instance HANA Content Central Appl.
Back-End Prerequisites (Minimum Version)
SAP enhancement package 7 (SP 07) for SAP ERP
Authoring Schema
SAP_ECC
Installation Information for SAP HANA ANALYTICS FOR CRM 1.0 Instance: HANA Content CRM Server Official Name
SAP HANA Live for SAP CRM
Name
SAP HANA ANALYTICS FOR CRM 1.0
Software Component
HANA CONTENT HBA SAP CRM 100 SP08 (technical name HCO_HBA_CRM)
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 15 of 44
Required Product Version
SAP HANA PLATFORM EDIT. 1.0 SPS08, revision 82 or higher
Back-End Prerequisites (Minimum Version)
EHP1 for SAP CRM 7.0 SP09
Authoring Schema
SAP_CRM
Tables for Replication
See SAP Note 1782066
Installation Information for SAP HANA ANALYTICS FOR SCM 1.0 Instance: HANA Content for SCM Server Official Name
SAP HANA Live 1.0 for SAP SCM
Name
SAP HANA ANALYTICS FOR SCM 1.0
Software Component
HANA CONTENT HBA SAP SCM 100 SP09 (technical name HCO_HBA_SCM_APO)
Required Product Version
SAP HANA PLATFORM EDIT. 1.0 SPS08, revision 82 or higher
Back-End Prerequisites (Minimum Version)
SAP SCM 7.0 SP14 See SAP Note 1904500
Authoring Schema Tables for Replication
SAP_SCM See SAP Note 1782067
Installation Information for SAP HANA ANALYTICS FOR GRC Instance: HANA Content GRC Official Name
SAP HANA Live for SAP solutions for GRC
Name
SAP HANA ANALYTICS FOR GRC 1.0
Software Component
HANA CONTENT HBA SAP GRC 100 SP09 (technical name HCO_HBA_GRC)
Required Product Version
SAP HANA PLATFORM EDIT. 1.0 SPS08, revision 82 or higher
Back-End Prerequisites (Minimum Version)
SAP Access Control 10.0 SP13
Authoring Schema
SAP_GRC
Tables for Replication
See SAP Note 1782068
Installation Information for SAP HANA ANALY. F. GRC10.1 1.0 Instance: HANA Content GRC 10.1 Official Name
SAP HANA Live for SAP solutions for GRC
Name
SAP HANA ANALY. F. GRC10.1 1.0
Software Component
HANA CONT. HBA SAP GRC101 100 SP02 (technical name HCO_HBA_GRC101)
Required Product Version
SAP HANA ANALYTICS FOR GRC 1.0 SPS09, instance HANA Content GRC
Back-End Prerequisites (Minimum Version)
SAP Risk Management 10.1 SP06
Authoring Schema
SAP_GRC
Tables for Replication
See SAP Note 2027728
Installation Information for SAP HANA ANALYTICS FOR GTS 1.0 Instance: HANA Content for GTS Server Official Name
SAP HANA Live 1.0 for SAP GTS
Name
SAP HANA ANALYTICS FOR GTS 1.0
Software Component
HANA CONTENT HBA SAP GTS 100 SP08 (technical name HCO_HBA_GTS)
Required Product Version
SAP HANA PLATFORM EDIT. 1.0 SPS08, revision 82 or higher
Back-End Prerequisites (Minimum Version)
SAP GTS 10.0 SP06
Authoring Schema
SAP_GTS
Tables for Replication
See SAP Note 1780655
Installation Information for SAP HANA ANALY. FOR FS-PM 1.0 Instance: HANA Content Insurance FS-PM Official Name
SAP HANA Live 1.0 for Policy Management
Name
SAP HANA ANALY. FOR FS-PM 1.0
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 16 of 44
Software Component
HANA CONTENT HBA FS-PM 100 SP06 (technical name HCO_HBA_FSPM510)
Required Product Version
SAP HANA PLATFORM EDIT. 1.0 SPS08, revision 82 or higher
Back-End Prerequisites (Minimum Version)
SAP FS-PM 5.1 (SP08). If you have SP01-07, you need to implement SAP Note 1918954
Authoring Schema Tables for Replication
SAP_FSPM See SAP Note 1918954
Installation Information for SAP HANA ANALYTICS FOR TM 1.0 Instance: HANA Content Transport. Mgmt. Official Name
SAP HANA Live for SAP Transportation Management
Name
SAP HANA ANALYTICS FOR TM 1.0
Software Component
HANA CONTENT HBA SAP TM 100 SP06 (technical name HCO_HBA_TM)
Required Product Version
SAP HANA PLATFORM EDIT. 1.0 SPS08, revision 82 or higher
Back-End Prerequisites (Minimum Version)
SAP Transportation Management 9.0 SP07
Authoring Schema
SAP_TM
Tables for Replication
See SAP Note 1918523
Installation Information for SAP HANA ANALYTICS FOR EM 1.0 Instance: HANA Content Event Mgmt. Official Name
SAP HANA Live for SAP Event Management
Name
SAP HANA ANALYTICS FOR EM 1.0
Software Component
HANA CONTENT HBA SAP EM 100 SP06 (technical name HCO_HBA_EM)
Required Product Version
SAP HANA PLATFORM EDIT. 1.0 SPS08, revision 82 or higher
Back-End Prerequisites (Minimum Version)
SAP Event Management 9.0 SP04
Authoring Schema
SAP_EM
Tables for Replication
See SAP Note 1918524
Installation Information for SAP HANA ANALYTICS F. EMX 1.0 Instance: HANA Content EMX Official Name
SAP HANA Live for Event Management and Transportation Management crossanalytics
Name
SAP HANA ANALYTICS F. EMX 1.0
Software Component
HANA CONTENT HBA EMX 100 SP02 (technical name HCO_HBA_X_EM)
Required Product Version
SAP HANA ANALYTICS FOR EM 1.0 SPS06, instance HANA Content Event Mgmt.
Back-End Prerequisites (Minimum Version)
SAP Event Management 9.0 SPS08
Authoring Schema
SAP_EM
Tables for Replication
See SAP Note 2063157
Installation Information for SAP HANA ANALY. FOR EWM 1.0 Instance: HANA Content EWM Official Name
SAP HANA Live for Extended Warehouse Management
Name
SAP HANA ANALY. FOR EWM 1.0
Software Component
HANA CONTENT HBA EWM 100 SP04 (technical name HCO_HBA_EWM)
Required Product Version
SAP HANA PLATFORM EDIT. 1.0 SPS08, revision 82 or higher
Back-End Prerequisites (Minimum Version)
SAP enhancement package 2 for SAP Extended Warehouse Management 7.0 SP00
Authoring Schema
SAP_EWM
Tables for Replication
See SAP Note 1952597
Installation Information for SAP HANA ANALYTICS FOR PLM 1.0 Instance: HANA Content PLM
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 17 of 44
Official Name
SAP HANA Live for SAP PLM
Name
SAP HANA ANALYTICS FOR PLM 1.0
Software Component
HANA CONTENT HBA SAP PLM 100 SP06 (technical name HCO_HBA_PLM)
Required Product Version
SAP HANA ANALYTICS FOR ERP 1.0 SPS010, instance HANA Content ECC Server
Back-End Prerequisites (Minimum Version)
SAP ERP 6.06 SP 1 and all equivalent enhancement packages Instance: PLM Core
Authoring Schema
SAP_ECC
Tables for Replication
See SAP Notes 1913511
and 1998788
.
Installation Information for SAP HANA ANALYTICS FOR INS 1.0 Instance: HANA Content Insurance Cross Official Name
SAP HANA Live for Insurance
Name
SAP HANA ANALYTICS FOR INS 1.0
Software Component
HANA CONTENT HBA X_INS01 100 SP06 (technical name HCO_HBA_X_INS01)
Required Product Version
SAP HANA ANALY. ERP EHP4 1.0 SPS08, instance HANA Content for Insurance
Back-End Prerequisites (Minimum Version)
EHP4 for SAP ERP 6.0 SAP FS-PM 5.1 (SP08). If you have SP01-07, you need to implement SAP Note 1918954
Authoring Schema
Tables for Replication
SAP_ECC SAP_FSPM See SAP Note 1918716
Note It is not possible to create analytic privileges for the cross-component view sap.hba.x.ins01.InsurancePaidLossRatioAnalysisQuery with the SAP HANA Live authorization assistant, since the required metadata cannot be maintained for different schemas. Instead, you have to maintain analytic privileges manually with attribute restrictions (based on your business requirements) for the following attributes and assign them to the business user (preferably via role): ClaimsLogicalSytem (Logicial system for FS-CM) PolicyLogicalSystem (Logicial system for FS-PM) InsurClmAuthsnGrp (FS-CM specific) InsurClmType (FS-CM specific) InsurPlcyProdnCtrlAuthsnCat (FS-PM specific) InsrrIDByInsrr (FS-PM specific) Limiting the combination of the logical system for FS-CM and the logical system for FS-PM allows for the system and the client-specific data restrictions. It is also required to grant the SELECT object privilege for the cross-component view sap.hba.x.ins01.InsurancePaidLossRatioAnalysisQuery to the business user (preferably via role).
Installation Information for SAP HANA ANALY. FOR MANUF. 1.0 Instance: HANA Content Manufacturing Official Name
SAP HANA Live for Manufacturing
Name
SAP HANA ANALY. FOR MANUF. 1.0
Software Component
HCO HBA OEE 100 SP07 (technical name HCO_HBA_OEE)
Required Product Version
SAP HANA ANALYTICS FOR ERP 1.0 SPS010, instance HANA Content ECC Server
Back-End Prerequisites (Minimum Version)
EHP6 for SAP ERP 6.0 SAP ERP 6.0 SP 19 and all equivalent enhancement packages
Authoring Schema
SAP_ECC SAP_OEE SAP_MII
Tables for Replication
See SAP Note 1803129
Installation Information for SAP HANA ANALYTICS FOR FCC 1.0 Instance: HANA Content Financial Closing Cockpit Official Name
SAP HANA Live for Financial Close
Name
SAP HANA ANALYTICS FOR FCC 1.0
Software Component
HANA CONTENT HBA SAP FCC 100 SP03 (technical name HCO_HBA_FCC)
Required Product Version
SAP HANA PLATFORM EDIT. 1.0 SPS08, revision 82 or higher
Back-End Prerequisites (Minimum Version)
SAP Financial Closing Cockpit 2.0 SP02
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 18 of 44
Authoring Schema Tables for Replication
SAP_FCC See SAP Note 1919584
Installation Information for SAP HANA ANALYTICS FOR ISU 1.0 Instance: HANA Content ISU - ECC Official Name
SAP HANA Live for Utilities, edition for SAP ERP
Name
SAP HANA ANALYTICS FOR ISU 1.0
Software Component
HANA CONTENT HBA ISU ECC 100 SP04 (technical name HCO_HBA_ISUECC)
Required Product Version
SAP HANA ANALYTICS FOR ERP 1.0 SPS010, instance HANA Content ECC Server
Back-End Prerequisites (Minimum Version)
EHP4 for SAP ERP 6.0 (for analytics in the side-by-side scenario) EHP7 SP02 for SAP ERP 6.0 (for analytics in the integrated scenario) Instance: Utilities/Waste&Recycl./Telco
Authoring Schema Tables for Replication
SAP_ECC See SAP Note 1992866
Installation Information for SAP HANA ANALY. F. CRM-IU 1.0 Instance: HANA Content CRM Utilities Official Name
SAP HANA Live for Utilities, edition for SAP CRM
Name
SAP HANA ANALY. F. CRM-IU 1.0
Software Component
HANA CONTENT HBA CRMIU 100 SP02 (technical name HCO_HBA_CRMIU)
Required Product Version
SAP HANA ANALYTICS FOR CRM 1.0 SPS08, instance HANA Content CRM Server
Back-End Prerequisites (Minimum Version)
EHP1 for SAP CRM 7.0 SP09
Authoring Schema
SAP_CRM
Tables for Replication
See SAP Note 2109304
Installation Information for SAP HANA ANALY. F. FND 1.0 Instance: HANA Content Foundation Official Name
SAP HANA Live for SAP Business Suite foundation component
Name
SAP HANA ANALY. F. FND 1.0
Software Component
HANA CONTENT HBA FND 100 SP03 (technical name HCO_HBA_FND)
Required Product Version
SAP HANA PLATFORM EDIT. 1.0 SPS08, revision 82 or higher
Back-End Prerequisites (Minimum Version)
EHP4 for SAP ERP 6.0 SP03
Authoring Schema
SAP_FND
Tables for Replication
See SAP Note 1915289
Installation Information for SAP HANA ANALY. FOR FS-RI 1.0 Instance: HANA Content Reinsurance Man Official Name
SAP HANA Live for Reinsurance Management
Name
SAP HANA ANALY. FOR FS-RI 1.0
Software Component
HANA CONTENT HBA FS-RI 100 SP02 (technical name HCO_HBA_FSRI)
Required Product Version
SAP HANA PLATFORM EDIT. 1.0 SPS08, revision 82 or higher
Back-End Prerequisites (Minimum Version)
FS-RI 6.6
Authoring Schema
SAP_FSRI
Tables for Replication
See SAP Note 2026382
Installation Information for SAP HANA ANALY. F. CMM 1.0 Instance: HANA Content CMM APPL Official Name
SAP HANA Live for Commodity Management
Name
SAP HANA ANALY. F. CMM 1.0
Software Component
HANA CONTENT HBA CM APPL 100 SP01 (technical name HCO_HBA_CM_APPL)
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 19 of 44
Required Product Version
SAP HANA ANALYTICS FOR ERP 1.0 SPS08, instance HANA Content ECC Server
Back-End Prerequisites (Minimum Version)
EHP7 SP05 for SAP ERP 6.0
Authoring Schema
SAP_ECC
Tables for Replication
See SAP Note 2027649
Instance: HANA Content CMM EAFS Official Name
SAP HANA Live for Commodity Management
Name
SAP HANA ANALY. F. CMM 1.0
Software Component
HANA CONTENT HBA CM EAFS 100 SP01 (technical name HCO_HBA_CM_EAFS)
Required Product Version
SAP HANA ANALY. F. CMM 1.0 SPS01, instance HANA Content CMM APPL
Back-End Prerequisites (Minimum Version)
EHP7 SP05 for SAP ERP 6.0
Authoring Schema
SAP_ECC
Tables for Replication
See SAP Note 2027649
Instance: HANA Content CMM GLTD Official Name
SAP HANA Live for Commodity Management
Name
SAP HANA ANALY. F. CMM 1.0
Software Component
HANA CONTENT HBA CM GLTD 100 SP00 (technical name HCO_HBA_CM_GLTD)
Required Product Version
SAP HANA ANALY. F. CMM 1.0 SPS01, instance HANA Content CMM APPL
Back-End Prerequisites (Minimum Version)
EHP7 SP05 for SAP ERP 6.0
Authoring Schema
SAP_ECC
Tables for Replication
See SAP Note 2027649
Installation Information for SAP HANA ANALYTICS F. CRMX 1.0 Instance: HANA Content CRM Cross VDM Official Name
SAP HANA Live for SAP CRM and SAP ERP cross-analytics
Name
SAP HANA ANALYTICS F. CRMX 1.0
Software Component
HANA CONTENT HBA X CRM 100 SP02 (technical name HCO_HBA_X_CRM)
Required Product Version
SAP HANA ANALYTICS FOR CRM 1.0 SPS09, instance HANA Content CRM Server
Back-End Prerequisites (Minimum Version)
EHP1 for SAP CRM 7.0 SP12 EHP4 SP00 for SAP ERP 6.0
Authoring Schema
SAP_CRM, SAP_ECC
Tables for Replication
See SAP Note 2035874
Installation Information for SAP HANA ANALYTICS F. RTL 1.0 Instance: HANA Content Retail Official Name
SAP HANA Live for Retail
Name
SAP HANA ANALYTICS F. RTL 1.0
Software Component
HANA CONTENT HBA RTL 100 SP03 (technical name HCO_HBA_RTL)
Required Product Version
SAP HANA ANALYTICS FOR ERP 1.0 SPS010, instance HANA Content ECC Server
Back-End Prerequisites (Minimum Version)
SAP ERP 6.0 SP12 and all equivalent enhancement packages
Note Due to the additional Customizing fields that are required for this VDM, you must apply SAP Note 2000139 Authoring Schema Tables for Replication
.
SAP_ECC See SAP Note 2063409
.
Installation Information for SAP HANA ANALYTICS F. REFX 1.0 Instance: HANA Content REFX Official Name
SAP HANA Live for Flexible Real Estate Management
Name
SAP HANA ANALYTICS F. REFX 1.0
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 20 of 44
Software Component
HANA CONTENT HBA REFX 100 SP02 (technical name HCO_HBA_REFX)
Required Product Version
SAP HANA ANALYTICS FOR ERP 1.0 SPS010, instance HANA Content ECC Server
Back-End Prerequisites (Minimum Version)
SAP ECC for ERP 6.0 EhP7 SP05
Authoring Schema
SAP_ECC
Tables for Replication
See SAP Note 2028785
Installation Information for SAP HANA ANALYTICS FOR PRA 1.0 Instance:HANA Content PRA VDM Official Name
SAP HANA Live for Production Revenue Accounting
Name
SAP HANA ANALYTICS FOR PRA 1.0
Software Component
HANA CONTENT HBA PRA 100 ISS (technical name HCO_HBA_PRA)
Required Product Version
SAP HANA PLATFORM EDIT. 1.0 SPS08, revision 82 or higher
Back-End Prerequisites (Minimum Version)
IS-PRA-XT 200 SP00 with activation of business function /PRA/OIL_PRA_RMY2
Authoring Schema
SAP_PRA
Tables for Replication
See SAP Note 2141678
Installation Information for SAP HANA ANALYTICS FOR GBT 1.0 Instance: HANA Content GBT VDM Official Name
SAP HANA Live for SAP Global Batch Traceability (SAP GBT)
Name
SAP HANA ANALYTICS FOR GBT 1.0
Software Component
HANA CONTENT HBA GBT 100 ISS (technical name HCO_HBA_GBT)
Required Product Version
SAP HANA PLATFORM EDIT. 1.0 SPS08, revision 82 or higher
Back-End Prerequisites (Minimum Version)
SAP Global Batch Traceability 2.0 SP 1
Authoring Schema
SAP_GBT
Tables for Replication
See SAP Note 2140504
Note To use the SAP HANA Live content for SAP Global Batch Traceability (SAP GBT), table types are needed for the signatures of the corresponding SAP HANA database procedures. During the deployment of the SAP HANA Live content, these table types are created in the SAP_HBA schema globally using the following naming convention: sap.hba.gbt.type::gbt.*. The expression * corresponds to the name of the table type.
1.6.5 Installation Information for Applications The applications listed below are available in addition to the virtual data models of SAP HANA Live for the different areas of SAP Business Suite.
Note To ensure that front-end server cookies are deleted after you have used SAP HANA Live applications, SAP recommends that you close all browser windows after finishing your work. The back-end sessions will then be closed automatically after a timeout period.
Installation Information for SAP GRIR MONITOR 1.0 Instance: GRIR Monitor Official Name
SAP Invoice and Goods Receipt Reconciliation
Name
SAP GRIR MONITOR 1.0
Software Component
GRIR_MONITOR 100 SP08 (technical name HCO_HBA_APPS_GRIRM)
Required Product Version
SAP HANA ANALYTICS FOR ERP 1.0 SPS09, instance HANA Content ECC Server
Note You can only use this application if in Customizing you have not set the summarization of FI data using the purchase order items. You can find the setting in Customizing for Financial Accounting (New) under General Ledger Accounting (New) Periodic Processing Integration Materials Management Perform Document Summarization for Materials Management or in Customizing of Financial Accounting under General Ledger Accounting Business Transactions Integration Materials Management Perform Document Summarization for Materials Management (transaction OBCY). For the reference transactions Material document (MKPF) and Invoice receipt (RMRP), you must not have an entry with Table Name BSEG and Field Name EBELP.
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 21 of 44
Installation Information for SAP GRC ANALYTICS 1.0 Instance: GRC Analytics Official Name
SAP Access Control
Name
SAP GRC ANALYTICS 1.0
Software Component
GRC_ANALYTICS 100 SP09 (technical name HCO_HBA_APPS_GRCA)
Required Product Version
SAP HANA ANALYTICS FOR GRC 1.0 SPS09, instance HANA Content GRC
Installation Information for SAP APO ANALYTICS 1.0 Instance: APO Analytics Official Name
SAP Supply Chain Info Center 1.0
Name
SAP APO ANALYTICS 1.0
Software Component
APO_ANALYTICS 100 SP09 (technical name HCO_HBA_APPS_APOAN)
Required Product Version
SAP HANA ANALYTICS FOR SCM 1.0 SPS09, instance HANA Content for SCM Server
Installation Information for SAP MANUF. ANALYTICS 1.0 Instance: SAP OEE Analysis Report Official Name
SAP HANA Live for Manufacturing, option for performance management
Name
SAP MANUF. ANALYTICS 1.0
Software Component
HCO_HBA_APPS_OEE 1.0 SP07 (technical name HCO_HBA_APPS_OEE)
Required Product Version
SAP HANA ANALY. FOR MANUF. 1.0 SPS07, instance HANA Content Manufacturing
Installation Information for SAP WORK CAPITAL ANALYTICS 1.0 Instance: WCA Days Sales Outstanding Official Name
SAP Working Capital Analytics
Name
SAP WORK CAPITAL ANALYTICS 1.0
Software Component
HANA APP WCA DSO 100 SP04 (technical name HCO_HBA_A_WCA_DSO_S)
Required Product Version
SAP HANA ANALYTICS FOR ERP 1.0 SPS09, instance HANA Content ECC Server
Instance: WCA Days Sales Outstanding UI Official Name
SAP Working Capital Analytics
Name
SAP WORK CAPITAL ANALYTICS 1.0
Software Components
HANA APP WCA DSO UI 100 SP04 (technical name HCO_HBA_A_WCA_DSO_U) ANALYSIS PATH FRAMEWORK 100 SP04 (technical name HCO_HBA_A_R_APF)
Required Product Version
SAP HANA ANALYTICS FOR ERP 1.0 SPS09, instance HANA Content ECC Server
Instance: WCA Days Payables Outstanding Official Name
SAP Working Capital Analytics
Name
SAP WORK CAPITAL ANALYTICS 1.0
Software Component
HANA APP WCA DPO 100 SP04 (technical name HCO_HBA_A_WCA_DPO_S)
Required Product Version
SAP HANA ANALYTICS FOR ERP 1.0 SPS09, instance HANA Content ECC Server
Instance: WCA Days Payables Outstand. UI Official Name
SAP Working Capital Analytics
Name
SAP WORK CAPITAL ANALYTICS 1.0
Software Components
HANA APP WCA DPO UI 100 SP04 (technical name HCO_HBA_A_WCA_DPO_U) ANALYSIS PATH FRAMEWORK 100 SP04 (technical name HCO_HBA_A_R_APF)
Required Product Version
SAP HANA ANALYTICS FOR ERP 1.0 SPS09, instance HANA Content ECC Server
Installation Information for SAP HANA CONTENT TOOLS 1.0 Instance: Analytical Framework Explorer
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 22 of 44
Official Name
SAP HANA Live Browser
Name
SAP HANA CONTENT TOOLS 1.0
Software Component
SAP HANA ANALYT. FWK EXPLORER 100 SP010 (technical name HCO_HBA_AF_EXPLORER)
Required Product Version
SAP HANA PLATFORM EDIT. 1.0 SPS08, revision 82 or higher, instance SAP HANA Database
Instance: SAP HANA Live Authorization Assistant Official Name
SAP HANA Live authorization assistant
Name
SAP HANA CONTENT TOOLS 1.0
Software Component
SAP HANA ANALYT. AUTHASST. 100 SP07 (technical name HCO_HBA_AAA)
Required Product Version
SAP HANA PLATFORM EDIT. 1.0 SPS08, revision 82 or higher, instance SAP HANA Database
Instance: SAP HANA Live Extensibility Plug-in Official Name
SAP HANA Live extension assistant
Name
SAP HANA CONTENT TOOLS 1.0
Software Component
SAP HANA ANALYT. EXTENSIB. 100 SP03 (technical name HCO_HBA_T_EXTN)
Required Product Version
SAP HANA PLATFORM EDIT. 1.0 SPS09, revision 82 or higher, instance SAP HANA Database
1.6.6 Maintenance and Update Process Two methods are available to update your software to a higher SP: You can deploy product stacks. This method automatically considers technical dependencies between selected product versions. You can deploy an update of a single product version. In addition, patches are provided for the latest SP. You can deploy patches of delivery units. The following section describes these methods in detail.
Recommendation SAP recommends that you always update your entire product version and all required product versions to the latest SP when you update or patch your application. To do so, SAP recommends that you use SAP Solution Manager.
Deploy product stacks 1. In SAP Solution Manager, run transaction lmdb. On the Product Systems tab, select your product system and choose Display. 2. 3. 4. 5.
In the navigation tree, click on the top node (Product System). On the Maintenance Transactions tab, under Maintenance Optimizer Transactions, choose Create Transaction. Under Choose File Selection Mode choose Calculate Files Automatically and then choose Continue. On the Operations tab, under Change Options, select change option Support Package Stacks – Implementation of Support Packages and choose Continue. 6. If you are not yet running SPS 08 or higher, set it as your target stack under Select Target and choose Continue.
Note This will update your SAP HANA DB to SPS 08 or higher. 7. Confirm the Major Target by choosing Continue. 8. To choose your products, note the following:
Note If you are using Maintenance Optimizer 3.0, the Add-On Product List is created dynamically. You initially see only add-ons that can be installed directly on the SAP HANA database. If you want to install an add-on that requires another add-on to be installed, you must first select the required product version on which the product you want to install is based.
Example You want to install the product version SAP WORK CAPITAL ANALYTICS 1.0. For this product version to be listed, you must first have selected SAP HANA ANALYTICS FOR ERP 1.0. To find out the required product version of your product, see Installation Information for Virtual Data Models. If you product has several instances, you must select the instances you want to install manually. When your instance is selected, choose Apply. 9. Follow this procedure for all products you want to install. When you are done, choose Continue. 10. Under Select OS/DB-Dependent Files, expand the instance node under File Name. Select SAP HANA database and choose Continue. 11. Under Select Files for Add-on Products, choose Continue.
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 23 of 44
12. Under Select Stack-Dependent Files, under File Name, new database patches are pre-selected by default. If you do not want to install these patches, deselect them. You must not deselect OS-DB if you are upgrading your SAP HANA databse to HANA SPS 08. Choose Continue. 13. Confirm the download basket by choosing Continue. 14. On the Stack Files tab, download the System-Specific XML for SLM. Save and close the Maintenance Optimizer windows. Then download the calculated files using SAP Download Manager from SAP Service Marketplace. Make the downloaded files and XML files available on your SAP HANA appliance. 15. As the SYSTEM user in the SAP HANA studio, right-click on the server node in the navigation pane, and select Lifecycle Management. 16. Select Apply Support Package Stack under Update SAP HANA System. 17. Choose Manually downloaded content, then browse to find the content you downloaded in step 5 and run the installation and update procedure.
Deploy update of a single product version
Note You must have updated your SAP HANA appliance to SPS 08 or higher. Ensure that you have installed the required product versions. The sequence of the zip-files installation must be done according to their dependencies. For this, the information Required Product Version, given in the tables in section Installation Information for Virtual Data Models, is relevant.
1. Go to the Software Download Center at https://service.sap.com/swdc (SAP HANA) SAP HANA Add-ons Installation . 2. Download the ZIP files for the SAP HANA Live installation you require.
Installations and Upgrades Browse Our Download Catalog SAP In-Memory
Note The ZIP file format used in the section Deploy patches of delivery units differs from the ZIP file format used in the section Deploy update of a single product version. 3. As the SYSTEM user in the SAP HANA studio, right-click on the server node in the navigation pane, and select Lifecycle Management. 4. Select Deploy HANA Content under Manage SAP HANA Applications Content. 5. On the screen Deploy SAP HANA Content choose the option From an accessible share or From a Personal Computer. 6. Under Path of remote HANA content ZIP archive, browse to the zip files you have downloaded. You can select and deploy only one zip file at a time. Choose Next. Ensure the correct installation sequence. 7. When you are done, choose Run. 8. Repeat steps 5, 6 and 7 for each SAP HANA Live product you want to install. For more information about how to configure the SAP HANA Lifecycle Manager, see SAP Help Portal at and Upgrade Information SAP HANA Update Guides SAP HANA Update and Configuration Guide .
http://help.sap.com/hana_appliance
Installation
For a detailed description regarding the deployment of SAP HANA content, see the section SAP Service Marketplace in Download and Deploy Content Package.
Deploy patches of delivery units
Note You must have updated your SAP HANA appliance to SPS 08 or higher. Ensure that you have installed the required patches, if they are mentioned in the respective SAP Note. The sequence of the ZIP-file installation must be done according to their dependencies. For this, the information Required Product Version, given in the tables in section Installation Information for Virtual Data Models, is relevant.
1. Go to https://service.sap.com/swdc Installations and Upgrades Browse Our Download Catalog SAP In-Memory (SAP HANA) SAP HANA Addons . Under Related Topics for your add-on choose Support Packages and Patches, then choose Comprised Software Component Versions. Select your component, choose OS independent, then choose SAP HANA database. 2. Download the ZIP files for the SAP HANA Live product. Make the downloaded files available on your SAP HANA appliance.
Note The ZIP file format used in the section Deploy patches of delivery units differs from the ZIP file format used in the section Deploy update of a single product version above. 3. As the SYSTEM user in the SAP HANA studio, right-click on the server node in the navigation pane, and select Lifecycle Management. 4. 5. 6. 7.
In the SAP HANA Lifecycle Manager, choose Apply Single Support Packages. Select the type of the system (either “Normal”, “Primary”, or “Secondary”). Choose Manually downloaded content, then browse to find the content you downloaded earlier. When you are done, choose Run.
For more information about how to configure the SAP HANA Lifecycle Manager, see SAP Help Portal at and Upgrade Information SAP HANA Update Guides SAP HANA Update and Configuration Guide .
http://help.sap.com/hana_appliance
Installation
Ensure that you update all delivery units of the complete stack (delivery units of the product version and of the required product version).
1.7 Configuration Steps 1.7.1 Generate Time Data
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 24 of 44
You need to generate time data and replicate your data. In this step, the date and time tables used by the content packages are filled with the data relevant for your system landscape. Proceed as follows: 1. In the SAP HANA Studio in the Modeler perspective, on the Quick Launch tab, select the relevant SAP HANA system and choose Generate Time Data. 2. In the field Calendar Type, select Gregorian. 3. Enter the period for which you want to generate data. You should generate time data for all years for which data can occur in your application (for example from 1990 to 2030). 4. Select Granularity Day. 5. Choose the day that is the first day of the week in your company. 6. Choose Generate. 7. Repeat steps 1–6 for the granularities Week, Month and Year. For Month and Year, step 5 is not necessary. Result The system populates the generated time data in the following tables, represented in schema _SYS_BI: M_TIME_DIMENSION M_TIME_DIMENSION_WEEK M_TIME_DIMENSION_MONTH M_TIME_DIMENSION_YEAR These tables are used to provide date-related metadata to the virtual data model, such as the reuse view Date in any package of SAP HANA Live for SAP Business Suite.
1.7.2 Replicate Data (Side-by-Side Only) As described above, the relevant database tables are typically only created, but not filled with data by default. In this step the tables relevant for the desired analytical scenarios are filled with data. First, you need to define the set of analytical scenarios (views) that are to be executed later. Then, the list of relevant tables is calculated for these views and the resulting tables are replicated by means of SAP Landscape Transformation Replication Server. There are two ways to calculate the list of relevant tables: SAP HANA Live Browser SAP HANA Live Browser also allows you to generate a list of tables relevant for a view. For more information, see section SAP HANA Live Browser. SQL You can retrieve the list of relevant tables through an SQL statement either per view or per package. See SAP Note 1784483 creating an SQL view that allows you to retrieve this information.
for details about
Once the list of tables has been calculated, the tables are configured for replication through the Data Provisioning screen of the SAP HANA studio.
1.8 Post-Installation Activities In this section you can find information about applications and consumption with SAP BusinessObjects BI Solutions.
1.8.1 SAP HANA Live Browser SAP HANA Live Browser is an SAP UI5 Web-based application that allows you to quickly and easily browse and tag SAP HANA content views, and consume them in SAP Lumira or SAP BusinessObjects Analysis to analyze the data. With this Web application, you can browse SAP HANA content views organized by Application Component Hierarchy (ACH) or browse SAP HANA content views organized by package. SAP HANA Live Browser also allows you to generate SAP Landscape Transformation Replication Server files for a view or a package as a CSV file. The SAP Landscape Transformation Replication Server file contains information about tables that need to be replicated for that view or package to work. You can either download the SAP HANA Live Browser from SAP Solution Manager or directly from SAP Service Marketplace at https://service.sap.com/swdc .
Prerequisites You have installed SAP HANA Content Tools 1.0, Instance Analytical Framework Explorer during the step Download and Deploy Content Package.
SAP HANA Live Browser Configuration 1. Assign roles In the SAP HANA studio, navigate to the Security folder, search for a user and assign the developer or business role. Technical name of developer role: sap.hba.explorer.roles::Developer Technical name of business user role: sap.hba.explorer.roles::Business 2. Access the SAP HANA Live Browser The user with the developer role can access the application using the following URL: http://:80/sap/hba/explorer/index.html The user with the business role can access the application using the URLs:
(with Shell)
http://:80/sap/hba/explorer/index.html
(with Shell)
http://:80/sap/hba/explorer/buser.html
(without Shell)
Note You can log on to SAP HANA Live Browser either as a developer or business user. As a business user you can see all the views in SAP HANA Live
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 25 of 44
Browser to which the user has access. You can open contents of the view, analyze the view using either SAP BusinessObjects Analysis or SAP Lumira (SAP Lumira™), and check the metadata. If you log on to SAP HANA Live Browser as a developer, you can see all views in the SAP HANA system; there are no limitations. In addition to the business user functions, you can also personalize views using tags, search for views, check view cross-references, and generate SAP Landscape Transformation Replication Server files to find out the tables to replicate for a view or group of views.
1.8.2 Recommended SAP BusinessObjects BI Solutions SAP Crystal Reports for Enterprise A reporting tool that allows you to create feature-rich reports and integrate them into Web and Windows applications.
SAP BusinessObjects Dashboards A software product for data visualization, with functions that allow the customer to create dynamic and interactive dashboards.
SAP BusinessObjects Explorer A tool that combines the simplicity and speed of Internet search with the analytical power of business intelligence – for faster, more informed decision making. It allows you to analyze data and relationships in the data in new ways that would not be possible in classic business intelligence tools.
SAP BusinessObjects Analysis, Edition for Microsoft Office A Microsoft Office add-in that allows a multidimensional analysis of OLAP sources. The data is displayed in the workbook in crosstabs. You can insert multiple crosstabs in a workbook with data from different sources and systems.
SAP Lumira SAP Lumira is a data manipulation and visualization tool. You can connect to various data sources, select and clean data, manipulate and visualize data with a diverse offer of graphical charts and tables. SAP Lumira is installed locally and can operate on data either remotely or on locally stored datasets.
SAP BusinessObjects Design Studio SAP BusinessObjects Design Studio enables application designers to create analysis applications and dashboards for browsers and mobile devices (for example for iPads) on top of BW and SAP HANA data sources.
Prerequisites Minimum Level Product
Version
SAP BusinessObjects BI Platform
SAP BusinessObjects BI Platform 4.0 SP07 or higher
SAP Crystal Reports for Enterprise
SAP Crystal Reports for Enterprise 4.0 SP07 or higher
SAP BusinessObjects Dashboards
SAP BusinessObjects Dashboards 4.0 SP07 or higher
SAP BusinessObjects Explorer
SAP BusinessObjects BI Platform 4.0 SP07 or higher
SAP BusinessObjects Analysis, edition for Microsoft Office
SAP BusinessObjects Analysis, edition for Microsoft Office 1.4 SP04 or higher
SAP Lumira
SAP Lumira 1.0 SP13 or higher
SAP BusinessObjects Design Studio
SAP BusinessObjects Design Studio 1.2
Integration Different SAP BusinessObjects BI solutions require different connection types to the SAP HANA database. The graphic shows which SAP BusinessObjects BI solutions allow a direct connection and which solutions need an indirect connection using universe UNX.
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 26 of 44
Virtual Data Models Used by SAP BusinessObjects BI Solutions
More Information For general information about SAP Crystal Reports for Enterprise, see SAP Help Portal at http://help.sap.com/bocr
.
For general information about SAP BusinessObjects Dashboards, see SAP Help Portal at http://help.sap.com/boexpl For general information about SAP BusinessObjects Explorer, see SAP Help Portal at http://help.sap.com/boxcel
. .
For general information about SAP BusinessObjects Analysis, edition for Microsoft Office, see SAP Help Portal at http://help.sap.com/boaa For general information about SAP Lumira, see SAP Help Portal at http://help.sap.com/lumira
.
.
For general information about SAP BusinessObjects Design Studio, see SAP Help Portal at http://help.sap.com/boad
.
1.8.3 SAP Invoice and Goods Receipt Reconciliation Enabling Calls to SAP ERP Back-End Transactions You can call SAP ERP back-end transactions, for example, Maintain GR/IR Clearing Account (MR11), from SAP Invoice and Goods Receipt Reconciliation. The Host Name and the ICM Service Name of the SAP ERP system must be entered into the JavaScript file ExtensionsMain.js, available in folder js/extensions, as follows:
Syntax 01. // Enter here the HOSTNAME and SERVICE NO of your ERP system. 02. ext.hostNameERP = ""; 03. ext.serviceNoERP = ""; You can find both the Host Name and the ICM Service Name in the URL of any Web application.
Example Start the SAP NetWeaver Business Client in your back-end system by running transaction NWBC: https://:/nwbc/~ launch/?sap-client=&sap-language= Note that the low and high value of PurchaseOrderDate is not submitted when you run transaction MR11. You must maintain the Set/Get Parameters MR11_BEDAT_LOW and MR11_BEDAT_HIGH for each user in the custom master data, that is, in transaction SU01 on the tab page Parameter, accordingly. This is to ensure that each receipt falls into the defined time period.
Example MR11_BEDAT_HIGH
20201231
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 27 of 44
20000101
MR11_BEDAT_LOW
For more information about additional functions, see the documentation available on SAP Help Portal at http://help.sap.com/hba Goods Receipt Reconciliation Additional Functions .
under
SAP Invoice and
1.8.4 SAP Access Control Set the client and logical system information for the SAP Access Control Role Analytics package. This allows the application to communicate with SAP Access Control. 1. In the SAP HANA studio, change the perspective to SAP HANA Development and open the Navigator pane. On the SAP HANA Repository tab, expand the relevant SAP HANA system. 2. Open the config.xscfgd file under Content sap hba apps grcra-reuse config 3. Ensure the following lines are present in the config file: Client = ""; Logical system = "";
Example Client = "300"; Logical system = "HS4CLNT300"; Search The application refreshes the data each time you select one of the elements on the screen, such as the filters and dates. Optionally, you can choose to display a Search button and refresh the data when you select the button. To display the Search button, do the following: 1. In the SAP HANA studio, change the perspective to SAP HANA Development and open the Navigator pane. On the SAP HANA Repository tab, expand the relevant SAP HANA system. 2. Open the config.xscfgd file under Content sap hba apps grcra-reuse config . 3. Locate the line show_search = false and change it to show_search = true.
More Information For more information about editing configuration files (for example, checking them in and out), as well as information about editing other files in SAP HANA studio, see the section Working with the Repository in the SAP HANA Developer Guide, available on SAP Help Portal at Development Information SAP HANA Developer Guide .
http://help.sap.com/hana_appliance
1.8.5 SAP Supply Chain Info Center The SAP Supply Chain Info Center is a group of analytical applications that use data in SAP HANA Live to enable you to get a better insight into the planning situation in Demand Planning (DP) and Supply Network Planning (SNP) of the product SAP Advanced Planning and Optimization (SAP APO). You can use the applications to monitor the forecast accuracy, projected stock, and stock coverage situation of the planning objects for which you are responsible. The planning data displayed and processed by the applications is replicated from the SAP APO system to SAP HANA using ABAP reports. For more information about setting up the replication process in SAP APO, see SAP Help Portal at http://help.sap.com/scmserver Application Help SAP Advanced Planning and Optimization (SAP APO) APO Analytics Working with Data Replication . For more information about setting up the replication process in SAP HANA Live, see SAP Help Portal at HANA Live for SAP SCM SAP Supply Chain Info Center Data Replication to SAP HANA . For more information about the applications and how to work with them, see SAP Help Portal at Live for SAP SCM SAP Supply Chain Info Center .
http://help.sap.com/hba
http://help.sap.com/hba
Application Help SAP
Application Help SAP HANA
More Information For more information, see SAP Notes 1784479
, 1863896
, 1904500
, and 1945658
.
1.8.6 SAP Working Capital Analytics Table Replication For SAP Working Capital Analytics, the following tables are required: BKPF BSEG KNA1/LFA1 VBRK/T151T/T171T/TSPAT/TVKOT/TVTWT T001
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 28 of 44
T005 T005T TCURN TCURT TCURX TCURC/TCURF/TCURV/TCURW/TCURR T000 TKA02 DD07L DD07T
Package Structure You can find all packages for SAP Working Capital Analytics in the SAP HANA Studio under sap.hba.apps.wca, and the Framework it is based on under sap.hba.apps.reuse.apf. The package structure contains, for example, all SAP HANA views, the Web content, and the OData files for SAP HANA extended application services.
Configuring SAP Working Capital Analytics Setting Up the URL You must set up the URL used to start the SAP Working Capital Analytics application. The URL, which also contains the client, contains the following constituents: To access the DSO application, enter the following URL in a Web browser: [protocol]://[host]:[port]/sap/hba/apps/wca/dso/WebContent/?SAPClient=[client] To access the DPO application, enter the following URL in a Web browser: [protocol]://[host]:[port]/sap/hba/apps/wca/dpo/WebContent/?SAPClient=[client]
Note The parameter SAPClient determines the client used for your DSO or DPO analysis. The application can access data of only one client at a time. However, you can set up several URLs to perform analyses for different clients.
SAP HANA XS Administration Tool Ensure that, for all packages listed below, only the authentication methods “Form based” and “Basic” are activated: Delivery Unit
Package
HCO_HBA_A_WCA_DSO_U
sap.hba.apps.wca.dso.WebContent
HCO_HBA_A_WCA_DSO_S
sap.hba.apps.wca.dso.s
HCO_HBA_A_WCA_DPO_U
sap.hba.apps.wca.dpo.WebContent
HCO_HBA_A_WCA_DPO_S
sap.hba.apps.wca.dpo.s
HCO_HBA_A_R_APF
sap.hba.apps.reuse.apf
This specific application runtime configuration can be changed using the administration tool for SAP HANA extended application services. For more information, see http://help.sap.com/hana_appliance SAP HANA Administration Guide .
System Administration and Maintenance Information SAP HANA Administration Guides
ISO Codes for Countries The SAP Working Capital Analytics application contains analysis steps that analyze data by country, for example, DSO by Country. To ensure that the country names are displayed in the charts, the three-character ISO codes of all required countries must exist in table T005, column INTCA3, of your SAP ERP system. If the ISO codes are missing in this table, you can copy them from client 000. You can also find the ISO codes in SAP Note 1164216
.
1.9 Operation Information This section gives you an overview of required operational tasks. For more detailed information, see the documentation on SAP Help Portal at http://help.sap.com/hana_appliance Maintenance Information SAP HANA Technical Operations Manual (TOM) .
System Administration and
1.9.1 Technical Operations Operating SAP HANA Live depends heavily on your implementation scenario. If you run SAP HANA Live as an integrated scenario, you will not have any additional requirements regarding the operation. You already take care of all topics for the Business Suite on the SAP HANA system. For the side-by-side scenario, there are two things that you have to consider: SAP Landscape Transformation Replication Server and SAP HANA.
Monitoring, Administration, and Alerting
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 29 of 44
To monitor the SAP HANA database, use the following: SAP SAP SAP SAP
HANA studio Solution Manager Landscape and Virtualization Manager (LVM) Landscape Transformation Replication Server
For more information about monitoring, see SAP Help Portal at SAP HANA Administration Guides .
http://help.sap.com/hana_appliance
System Administration and Maintenance Information
For information about how to monitor your SAP HANA system with SAP Solution Manager, see SAP Note 1747682
.
You administer the SAP HANA database using the administration console perspective of the SAP HANA studio. For more information, see SAP Help Portal at
http://help.sap.com/hana_appliance
System Administration and Maintenance Information :
SAP HANA Technical Operations Manual (TOM) SAP HANA Administration Guides Application Operations Guide – Trigger-Based Data Replication Using SAP LT Replication Server for SAP HANA
Backup & Recovery Backup and recovery of SAP HANA has to be considered within the context of the entire system landscape. Ensure that SAP HANA and the source system can be recovered in a consistent state. For more information about the backup and restore strategy for the landscape consisting of source system, SAP Landscape Transformation Replication Server and an SAP HANA database, see SAP Help Portal at HANA Technical Operations Manual (TOM) .
http://help.sap.com/hana_appliance
System Administration and Maintenance Information SAP
For more information about backup and recovery, see SAP Help Portal at http://help.sap.com/hana_appliance Information SAP HANA Administration Guides SAP HANA Administration Guide .
System Administration and Maintenance
High Availability and Disaster Tolerance SAP HANA supports high availability and disaster tolerance scenarios.
Note Contact your hardware partner of choice for an SAP-certified high availability solution for SAP HANA.
For more information, see the documentation on SAP Help Portal at Information SAP HANA Technical Operations Manual (TOM) .
http://help.sap.com/hana_appliance
System Administration and Maintenance
Starting and Stopping SAP HANA You start and stop the SAP HANA database with the SAP HANA studio. For detailed information about starting and stopping, see the documentation on SAP Help Portal at http://help.sap.com/hana_appliance Administration and Maintenance Information SAP HANA Administration Guides SAP HANA Administration Guide .
System
1.10 Security The applications for SAP HANA Live for SAP Business Suite are a Web-based front-end HTML5 and UI development toolkit for HTML5 (SAPUI5) on top of SAP HANA extended application services. The underlying database is SAP HANA.
1.10.1 User Administration and Authentication SAP HANA Live for SAP Business Suite uses the user management and authentication mechanisms provided with the SAP HANA appliance software SPS 08. Therefore, the security recommendations and guidelines for user administration and authentication as described in the SAP HANA Security Guide apply. For more information, see SAP Help Portal at
http://help.sap.com/hana_appliance
Security Information SAP HANA Security Guide .
User Administration Named User Necessary for other clients such as SAP BusinessObjects BI Suite UIs. User Types All user types that are described in the SAP HANA security guide are necessary. Standard Users No special users are required for SAP HANA Live. Note the following:
Note When using SAP HANA Live for SAP Business Suite, you must ensure that the user’s technical name on SAP HANA is identical with the technical user
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 30 of 44
name on ABAP Application Server. For the side-by-side scenario, with multiple source systems replicating to the same SAP HANA appliance, you must ensure that this is true for all source systems.
User Data Synchronization Synchronization needs to be done manually or automatically, for example by using SAP’s identity management solution.
Integration into Single Sign-On Environments SAP recommends using the SAP logon ticket. SAP HANA Live for SAP Business Suite supports the use of logon tickets for Single Sign-On when using a Web browser as the front-end client. In this case, users receive a logon ticket after they have authenticated themselves with a ticket issued by the SAP system. The ticket is then submitted to other systems (within the same domain) as an authentication token, for example to SAP HANA extended application services. The user does not need to enter a user ID or password for authentication but can access the system directly after the system has checked the logon ticket. For more information, see the chapter SAP HANA Authentication and Single Sign-On of the SAP HANA Security Guide, available on SAP Help Portal at http://help.sap.com/hana_appliance
Security Information , as well as the Security Guide for SAP LT Replication Server at
http://help.sap.com/hana_appliance
Security Information Security Guide – Trigger-Based Data Replication Using SAP LT Replication Server .
1.10.2 Authorizations The user interfaces of SAP HANA Live for SAP Business Suite rely on the access control mechanisms of the underlying SAP HANA database. As a prerequisite, it is assumed that every business user (any user accessing SAP HANA Live content in the SAP HANA database) is created as a named SAP HANA database user. To control the business user’s access to SAP HANA Live application content and displayed data, the relevant authorization settings have to be configured within the SAP HANA database. Authorization settings on the SAP HANA database are achieved through privileges.
1.10.2.1 Privileges SAP HANA Privileges SAP HANA has implemented the regular SQL authorization concept based on privileges. SAP HANA privileges of type “system”, “object”, “analytic”, or “package” are either directly assigned to a user or through roles collecting sets of privileges. For more information, see the SAP HANA Security Guide on SAP Help Portal at Security Guide .
http://help.sap.com/hana_appliance
For more information about authorization in SAP HANA Live for SAP CRM, see SAP Note 1848159
Security Information SAP HANA
.
For more information about authorization in SAP ERP Human Capital Management (SAP ERP HCM) , see SAP Note 1852087
.
Object and Analytic Privileges The read access of a business user to SAP HANA Live application content and the displayed data is controlled by a combination of the following: Object (SELECT) privileges (granting read access to database objects, such as tables or views) Analytic privileges (granting read access to certain rows of data in calculation views by filtering attribute values) if the analytic privilege check is explicitly enabled for the view
Behavior of Privileges on Nested and Dependent Views It is important to understand the interplay of object (SELECT) and analytic privileges, specifically the behavior in nested or dependent views. In particular, as a prerequisite for read access to a calculation view, the user must be granted the following: A SELECT privilege on this view itself (note that no SELECT privilege on the underlying base tables or views of this view is required). An analytic privilege that is applicable to the view if the analytic privilege check is explicitly enabled for the view. It defines an attribute restriction for this view filtering the displayed data. Relevant analytic privileges for all underlying views with enabled analytic privilege check if the calculation view is the top view of a hierarchy of nested calculation views.
Note Result filtering is evaluated for each view individually. An analytic privilege on a higher-level view can only further restrict data access on this view, meaning the output of an underlying view defines the maximum possible output of a higher-level view.
For more information about defining hierarchies on calculation views with parameters, see SAP Note 1892747
.
SAP Standard Delivery SAP does not deliver any predefined privileges or roles for SAP HANA Live for SAP Business Suite business users. Instead, read access privileges for SAP HANA Live business users have to be configured on the customer side in conformity with the customer’s authorization requirements.
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 31 of 44
Query vs. Non-Query Views – Maintenance of Privileges Query Views Calculation views of view category Query (view names with suffix Query) Top level of a view hierarchy Never consumed by other views Intended for direct consumption by an analytical application Analytic privilege check enabled Non-Query Views Calculation views of view category “private” or “reuse” Not directly exposed to business users Analytic privilege check not enabled When configuring business users’ privileges in the SAP HANA studio, SAP recommends to proceed according to the following principles: Do not grant SQL SELECT object privilege for a table directly to a business user. Grant SQL SELECT object privilege on query views only. Never grant SQL SELECT object privilege on any non-query view (reuse view or private view) to a business user. Define row-based access restrictions by analytic privileges on query views according to your data access control requirements.
Note Applications that make use of classification or variant configuration views may deviate from the general recommendation. Also, the underlying classification or variant configuration views are enabled for the analytic privilege check. To enable access restrictions on parts of rows, filter restrictions have to be defined for these underlying non-query views as well. Classification views are generated reuse views that render the characteristic values of classified objects per column. Variant configuration views are generated reuse views that render the characteristic values of configured objects per column. Both types of views are intended to be used together with business object views. To ensure that missing user privileges for the respective data (either classification or variant configuration data) do not filter out any associated business object data, proceed as follows: 1. For classification data and variant configuration data apply the privilege check only at the level of the generated views, not at the level of the joined (query) view. 2. Combine the business object view with the classification or variant configuration view using an outer join. For more information, see SAP Help Portal at
http://help.sap.com/erp
Application Help SAP ERP Central Component Logistics
Product Lifecycle Management (PLM) Classification and http://help.sap.com/erp Application Help SAP ERP Central Component Logistics Product Lifecycle Management (PLM) Variant Configuration (LO-VC) . For more information about generating views, see SAP Note 1892589 configuration views.
for classification views, and SAP Note 1987669
for variant
Note To create an analytic privilege granting full access to a view without any filter restriction for any attribute, add a view as a referenced model without specifying any associated attribute restriction. For reasons of simplicity, reference only one model for a query view in an analytic privilege. For more information about authorization concepts, see SAP Help Portal at Security Guide .
http://help.sap.com/hana_appliance
Security Information SAP HANA
Query vs. Value Help Views – Maintenance of Privileges With respect to authorization, a value help view is completely independent of a query view using the value help view. Therefore, you must explicitly grant SELECT object and analytic privileges for value help views to business users in addition to the privileges granted for query views.
SAP HANA Live Authorization Assistant With the SAP HANA Live authorization assistant, you can provide users authorizations in the SAP HANA system that is required to access business data displayed by the virtual model of SAP HANA Live. For this, the SAP HANA Live authorization assistant takes those permissions into account that the same users already have in ABAP-based SAP Business Suite applications. The SAP HANA Live authorization assistant is used to manage both the analytic privileges that restrict access to specific business data, and the object privileges that control the database views that the user uses to report. For more information, see SAP Help Portal at Assistant .
http://help.sap.com/hba
Application Help SAP HANA Live Tools SAP HANA Live Authorization
Prerequisites You have installed the following software: SAP HANA Appliance Software Support Package Stack 08, revision 82 or higher SAP HANA Live for SAP Business Suite 1.0 Delivery unit HCO_HBA_AAA.tgz For more information, see section Installation Steps (Download and Deploy Content Package). You have assigned SQL EXECUTE privilege REPOSITORY_REST to the user _SYS_REPO and selected the option Grantable to Others. You have replicated the tables USRBF2, UST12 and AGR_1016 from the back-end system.
Installation of SAP HANA Live Authorization Assistant To install the SAP HANA Live authorization assistant, perform the following steps in sequential order: 1. In the SAP HANA studio, choose Help and then Install New Software. An installation window opens.
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 32 of 44
2. Enter the URL of the update software http://:80/sap/hba/tools/auth in the field Work with. The installation window now lists the SAP HANA Live authorization assistant as available software in the list of plug-ins. 3. Click Add to save the URL for easy retrieval. The dialog box Add Repository opens. 4. Select the plug-in for the SAP HANA Live authorization assistant from the list of available plug-ins. Retain the remaining default selections and click Next.
Note The two available plug-ins are Analytic Authorization Assistant and Analytic Authorization Assistant – Metadata. If the user does not want to enter new metadata and only generate analytic privileges with SAP delivered metadata, then you require only the Analytic Authorization Assistant plug-in. 5. 6. 7. 8. 9. 10.
A review window opens where you can verify the information you entered. Click Next. The License Agreement window opens. Review the licenses and click I accept the terms of the license agreements. Then click Finish. The Installing Software dialog box opens, where you can view the installation progress. A warning message may appear stating that the software contains unsigned content. Click OK. After the installation is complete, a verification box opens asking you to restart SAP HANA studio. Click Yes. Restart the SAP HANA Studio to view the SAP HANA Live Authorization menu in the menu bar.
Note The role sap.hba.tools.auth.roles::AnalyticsAuthorizationAdministrator is used to generate analytic privileges. The role sap.hba.tools.auth.roles::AnalyticsAuthorizationDeveloper is used to maintain the metadata enabling you to generate analytic privileges.
For more information about generating analytic privileges, see SAP Help Portal at Authorization Assistant .
http://help.sap.com/hba
Application Help SAP HANA Live
Transformation of User’s ABAP Authorizations into Analytic Privileges for SAP HANA The analytic privileges in SAP HANA are created according to view-specific mapping rules that exist between authorization objects and view attributes, based on the logic below from the users’ authorization data stored in ABAP systems: Multiple values for the same authorization field of the same authorization object are combined with logical OR. Different authorization fields of the same authorization object are combined with logical AND. Different authorization objects are combined with logical OR. Interval values for authorizations maintained using the FROM and TO fields and the asterisk wildcard are taken into account while generating the analytic privileges for users.
1.10.2.2 Authorization for SAP HANA Live for SAP SCM Access to planning data and master data in the SAP Advanced Planning and Optimization (SAP APO) system is controlled by the APO authorization framework. The same level of authorization must be available to users accessing the SAP APO planning data and master data through the analytic applications of SAP Supply Chain Info Center as to the users working with the data in SCM Server. Users of the analytic applications of SAP Supply Chain Info Center accessing the planning data and master data replicated from the SAP APO system use SAP HANA studio users. There is no direct relationship between an application user (in SCM Server) and the corresponding user in the SAP HANA studio accessing the analytic applications. Therefore, it is necessary to configure various authorization-relevant settings in the SAP HANA studio to restrict access to the replicated data.
Authorization Settings Prerequisites You must ensure that users have the right level of authorization to access planning data replicated from SAP APO, and that it is available in the analytic applications of SAP Supply Chain Info Center. To do so, ensure that the following authorization-relevant settings have been made: To enable access to the analytic user interfaces of SAP Supply Chain Info Center, an administrator has created user accounts in the SAP HANA studio. You have installed and activated the virtual data model views for SAP Supply Chain Management (SAP SCM) in the SAP HANA studio. You have configured data replication between the SCM server and the SAP HANA server. For more information, see the Installation chapters in this guide, as well as the documentation available on SAP Help Portal at http://help.sap.com/hba
Application Help SAP HANA Live for SAP SCM .
Settings for Planners Grant authorization to users that only need to access the analytic application, such as a demand planner, or supply network planner, as follows: 1. Create a new role that will be assigned to the planners. This role can be based on the template role sap.hba.apps.apoan.roles::Planner. If the created role is based on this template, step 2 can be skipped. 2. Assign the following SQL privileges to the created role: SELECT, INSERT and, DELETE privileges for the following table: SAP_HBA.sap.hba.apps.apoan.db::APOAN_SDP_SELECTION SELECT privilege on the following sequences: SAP_HBA.sap.hba.apps.apoan.db::APOAN_UI_SELECTION_ID SAP_HBA.sap.hba.apps.apoan.db::APOAN_SDP_SELECTION_ID SELECT privilege on the following tables: _SYS_BI.BIMC_PROPERTIES _SYS_REPO.ACTIVE_OBJECT _SYS_REPO.INACTIVE_OBJECT SAP_HBA.sap.hba.apps.apoan.db::APOAN_CUSTOM_MEASURES SAP_HBA.sap.hba.apps.apoan.db::APOAN_CUSTOM_MEASURES_TEXT
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 33 of 44
SAP_HBA.sap.hba.apps.apoan.db::APOAN_CUSTOM_MEASURES_PARAMS SELECT privilege on the following runtime objects: _SYS_BIC.sap.hba.apps.apoan.views/SupportedMeasuresMetadata _SYS_BIC.sap.hba.apps.apoan.views/SupportedScenariosMetadata _SYS_BIC.sap.hba.apps.apoan.views/CustomMeasuresMetadata _SYS_BIC.sap.hba.apps.apoan.views/NavigationTargets _SYS_BIC.sap.hba.apps.apoan.views/AttributesMetadata SELECT privilege on the following calculation views: _SYS_BIC.sap.hba.scm-apo/Location _SYS_BIC.sap.hba.scm-apo/Product 3. Create new analytic privileges for granting full access (empty analytic privilege) to the following calculation views from the package sap.hba.apps.apoan.views: SupportedMeasuresMetadata SupportedScenariosMetadata CustomMeasuresMetadata NavigationTargets AttributesMetadata
Note You can create the analytic privilege in any package. You must then assign the created analytic privileges to the role that is used for the planners. 4. Assign the SELECT SQL privileges to the created role for the runtime objects that are generated when you activate a replication model. These SELECT privileges must be assigned only to the query views. The SELECT SQL privilege must be granted to all views for a particular replication model; they are in the package sap.hba.apps.apogo.REPLICATIONMODELNAME, where REPLICATIONMODELNAME is the name of the replication model. You must grant SELECT privilege only to the views with the suffix “query”. The runtime objects are in the schema _SYS_BIC. An example of such a runtime object for a Demand Planning replication model is _SYS_BIC.sap.hba.apps.apogo.REPLICATIONMODELNAME/SCICDemandPlanQuery.
Note You must assign the SELECT SQL privilege to all of the following views that the planner would like to use: views that have the suffix “query” views that have been generated for specific replication models 5. Create new analytic privileges granting either full or limited access to the calculation views that are generated in the system when you activate a new replication model. The views that are authorization-relevant can be found in the package sap.hba.apps.apogo.REPLICATIONMODELNAME, where REPLICATIONMODELNAME is the name of the replication model that you used. For all the views included in these packages ending with the suffix “query” , you should create analytic privileges. The analytic privilege should define the restrictions. You can also use empty analytic privileges that grant full access to the planning data of these replication models.
Note You can create the analytic privilege in any package. You must then assign the created analytic privileges to the role that is used for the planners. Repeat this step for each replication model that the planner would like to use.
Settings for System Administrators To grant additional authorization to administrator users so that they can import and activate the generated virtual data model views from the XML files that the system generates, proceed as follows: Assign them to the standard MODELING role or its equivalent Ensure that administrator users have the following privileges for the package sap.hba.scm-apo: REPO.EDIT_IMPORTED_OBJECTS REPO.ACTIVATE_IMPORTED_OBJECTS REPO.MAINTAIN_IMPORTED_PACKAGES Ensure they are enabled to grant the roles and authorization to the users of the analytic applications of the SAP Supply Chain Info Center. Ensure that the _SYS_REPO user has SELECT, INSERT and UPDATE object privileges for the SAP_SCM schema In addition to the authorization that is relevant for planners, you must also do the following: 1. Create a new role to be assigned to the administrators. This role can be based on the template role sap.hba.apps.apoan.roles::Administrator. If the created role is based on this template, you can skip steps 2, 3 and 4. 2. Assign the SQL privileges SELECT, INSERT, UPDATE, and DELETE for the following tables to the created role: SAP_HBA.sap.hba.apps.apoan.db::APOAN_CUSTOM_MEASURES SAP_HBA.sap.hba.apps.apoan.db::APOAN_CUSTOM_MEASURES_TEXT SAP_HBA.sap.hba.apps.apoan.db::APOAN_CUSTOM_MEASURES_PARAMS 3. To the created role, assign the application privilege sap.hba.apps.apoan.WebContent.admin::Execute. 4. Assign SELECT privilege on the following calculation views: _SYS_BIC.sap.hba.scm-apo/Location _SYS_BIC.sap.hba.scm-apo/Product
Recommendation SAP recommends that you define the authorizations as SAP HANA roles, which can then be more easily assigned to existing and new users. Such a role can, for example, contain the necessary SQL privileges for accessing the application-specific tables, the metadata views, and for assigning analytic privileges to the metadata calculation views. Additional roles can include analytic privileges assigned to the generated views (see the Process section).
Note
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 34 of 44
It is possible to use the special analytic privilege _SYS_BI_CP_ALL to grant full access to the metadata views and all generated replication model views (see the Process section). SAP recommends that you use this special privilege in exceptional cases only, and create separate analytic privileges instead for each calculation view that is relevant for reporting for the particular planner. For more information, see SAP Help Portal at http://help.sap.com/hana_appliance
,
Security Information SAP HANA Security Guide .
Caution This special analytic privilege will also grant full access to all other activated views with granted SELECT object privileges.
Defining Restrictions on Views in the SAP HANA Studio After the system administrator has activated and replicated a replication model in the SAP APO system and imported the generated views to the SAP HANA studio, the next step is defining restrictions on these views so that the users accessing the data through the analytical applications of SAP Supply Chain Info Center have the right levels of authorization. Access to the data for users of the analytical applications of SAP Supply Chain Info Center can be restricted as follows: By restricting the range of “planning book”, “data view” and “planning version” combinations that a particular user can see. By defining a restriction for a subset of planning data that a particular user can access through the analytical applications. Restricting the Range of Planning Book, Data View and Planning Version Combinations Analytic privileges for the metadata views can be created with restrictions that are defined, for example, on the attributes PlanningBook, DataView and PlanningVersion, or on Product, Location and Customer. Alternatively, one analytic privilege can be created with no restriction, which makes it possible to select all combinations.
Note This does not mean that the user automatically has access to the underlying data as well.
Restricting for a Subset of Planning Data To restrict a subset of planning data, the system administrator must define a restriction in the form of analytic privileges of the query views for each generated replication model. For each replication model, the analytic privileges must be defined for the views in the package sap.hba.apps.apogo.REPLICATIONMODELNAME, where REPLICATIONMODELNAME is the name of the replication model. The views for which the analytic privileges are to be defined are the ones with the suffix “query”.
1.10.2.3 Authorization for SAP Invoice and Goods Receipt Reconciliation Users of the SAP Invoice and Goods Receipt Reconciliation application accessing the data replicated from the SAP ECC system use SAP HANA studio users. There is no direct relationship between a user in ECC Server and the corresponding user in the SAP HANA studio accessing the analytic application. Therefore, it is necessary to configure various authorization-relevant settings in the SAP HANA studio to restrict access to the replicated data.
Authorization Settings Prerequisites You must ensure that users have the right level of authorization to access data replicated from SAP ECC, and that it is available in the analytic application. To do so, ensure that the following authorization-relevant settings have been made: To enable access for users to the SAP Invoice and Goods Receipt Reconciliation application, an administrator has created users in the SAP HANA studio. You have installed and activated the virtual data model views for ECC and SAP Invoice and Goods Receipt Reconciliation in the SAP HANA studio. You have configured data replication between the ECC server and the SAP HANA server. For more information, see the Installation Information chapter in this guide, as well as the documentation available on SAP Help Portal at http://help.sap.com/hba SAP Invoice and Goods Receipt Reconciliation .
Application Help SAP HANA Live for SAP ERP
Settings for Business Users Grant authorization to users that only need to access the analytic application as follows: 1. Create and assign analytic privileges to users for granting access to the following query views from the package sap.hba.apps.grircm.views: GRIRAccountingDocumentQuery GRIRClearingMonitorDigestQuery GRIRClearingMonitorQuery GRIRClearingMonitorStatusClearedQuery GRIRClearingMonitorStatusOpenQuery GRIRClearingMonitorStatusQuery GRIRFiscalYearPeriodQuery GRIRGoodsReceiptQuery GRIRInvoiceReceiptQuery GRIRNumberOfOpenItemsQuery GRIROpenItemQuery GRIROwnUserContactDataQuery
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 35 of 44
GRIRPurchaseOrderClearingAgingQuery GRIRPurchaseOrderHistoryQuery GRIRPurchaseOrderQuery GRIRPurOrdHistoryWithDeliveryCostsQuery GRIRStatusNumberOfPurOrdItemsQuery GRIRUserContactDataQuery GRIRUserDefaultContactDataQuery GRIRVendorContactDataQuery GRIRVendorDefaultContactDataQuery
Recommendation SAP recommends that you create analytic privileges for the above query views with restrictions on the view attributes according to your business requirements. 2. Create and assign analytic privileges to users for granting full access to the non-query views consumed by the query views listed above. These views are part of the SAP Invoice and Goods Receipt Reconciliation virtual data model. Include the views listed below from the package sap.hba.apps.grircm.views: GRIRAccountingDocument GRIRClearingMonitor GRIRClearingMonitorDigest GRIRClearingMonitorStatus GRIRClearingMonitorStatusCleared GRIRClearingMonitorStatusOpen GRIRFiscalYearPeriod GRIRGoodsReceipt GRIRInvoiceReceipt GRIRNumberOfOpenItems GRIROpenItem GRIRPurchaseOrder GRIRPurchaseOrderClearingAging GRIRPurchaseOrderHistory GRIRPurchaseOrderHistoryWithDeliveryCosts GRIRStatusNumberOfPurchaseOrderItems GRIRUserContactData GRIRUserDefaultContactData GRIRVendorContactData GRIRVendorDefaultContactData 3. Create and assign analytic privileges to users for granting full access to the non-query views consumed by the SAP Invoice and Goods Receipt Reconciliation Monitor application from SAP HANA Live for ECC. These views are part of the SAP HANA Live for ECC virtual data model. Include the views listed below from the package sap.hba.ecc: AccountingDocumentType AccountingPeriod BKPF BSEG CalendarYearBasedVariant CommunicationMediumTypeName CompanyCode Country CreditControlArea Currency DunningArea DunningBlockingReason FinancialAccountType FiscalFirstPeriod FiscalYearBasedVariant FiscalYearLastPeriod FiscalYearPeriod FiscalYearPeriodBeginDate GLAccount GLAccountInChartOfAccounts GLAccountInCompanyCode MaximumDunningLevel PaymentBlockingReason PaymentDifferenceReason PaymentMethodForCountry Plant PlantName PostedAccountingDocumentEntryView ProfitCenter PurchaseOrderHistory PurchaseOrderHistoryCategory PurchaseOrderHistoryDeliveryCost PurchasingDocumentHeader PurchasingDocumentItem
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 36 of 44
SpecialGLCode SpecialLastPeriod SpecialPeriodWithDate StorageLocation UnitOfMeasureName UserContactData UserDefaultContactData UserEmailAddressData UserFaxData UserMobilePhoneData UserOfficeData UserPhoneData ValuationArea Vendor VendorCellPhoneData VendorContactData VendorDefaultContactData VendorEmailAddressData VendorFaxData VendorPhoneData Year
Recommendation SAP recommends that you create one analytic privilege containing all non-query view references. The restriction for this analytic privilege must be empty, which means that this analytic privilege grants full access to the non-query views mentioned above. 4. When business users work with the application SAP Invoice and Goods Receipt Reconciliation, you must assign them SQL SELECT, UPDATE, and INSERT privileges for the following: Schema: SAP_HBA Catalog object: sap.hba.apps.grircm.db/GRIRCMSTATUS SAP HANA database table: sap_hba_apps_grircm_db_GRIRCMSTATUS (this is delivered with the application) The application checks the user’s SQL SELECT, UPDATE, and INSERT privileges, as well as the user’s read privilege while data is being updated. In this case, access is granted on row level. 5. Grant SELECT privilege on the following query views: GRIRAccountingDocumentQuery GRIRClearingMonitorDigestQuery GRIRClearingMonitorQuery GRIRClearingMonitorStatusClearedQuery GRIRClearingMonitorStatusOpenQuery GRIRClearingMonitorStatusQuery GRIRFiscalYearPeriodQuery GRIRGoodsReceiptQuery GRIRInvoiceReceiptQuery GRIRNumberOfOpenItemsQuery GRIROpenItemQuery GRIROwnUserContactDataQuery GRIRPurchaseOrderClearingAgingQuery GRIRPurchaseOrderHistoryQuery GRIRPurchaseOrderQuery GRIRPurOrdHistoryWithDeliveryCostsQuery GRIRStatusNumberOfPurOrdItemsQuery GRIRUserContactDataQuery GRIRUserDefaultContactDataQuery GRIRVendorContactDataQuery GRIRVendorDefaultContactDataQuery
Recommendation SAP recommends that you do not grant SYSTEM user permissions to users accessing the SAP Invoice and Goods Receipt Reconciliation application, as this will give them full access to the data.
Defining Restrictions on Views in the SAP HANA Studio You can restrict access to data for users of the SAP Invoice and Goods Receipt Reconciliation application as follows: By defining row-based access restrictions by analytic privileges on query views according to your requirements for data access control. For example, in the query view GRIRClearingMonitorQuery, you can assign the restriction on the attribute SAPClient in the analytic privilege. This ensures client isolation, which means that this analytic privilege grants access to view the data for that particular client only. If you do not assign any restriction on the attribute SAPClient in the analytic privilege, this analytic privilege grants access to view data for all clients. In the analytic privilege, you can restrict the range of attribute values and their combinations that a particular user can see in the application. Access to the SAP HANA view GRIROwnUserContactData, which is used in the application to retrieve the SAP ERP user maintained in the application for a given SAP HANA user, can be restricted as follows: By assigning the appropriate row-based analytic privilege for the attribute “User”, you can ensure that a user has access to the correct SAP ERP user only. The contact data of the SAP ERP user is used in the application for outgoing calls if telephony integration is configured and enabled.
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 37 of 44
Recommendation SAP recommends that you define the authorizations as SAP HANA roles, which can then be more easily assigned to existing and new users. Such a role can, for example, contain the necessary SQL privileges for accessing the query views and non-query views, and for assigning analytic privileges to the query views and non-query views.
Metadata for Authorizations You can define authorizations on the level of view fields. SAP delivers metadata, that is, authorization objects with the corresponding fields and activities, for the following views: GRIRClearingMonitorDigestQuery GRIRNumberOfOpenItemsQuery GRIRPurchaseOrderclearingAgingQuery GRIRClearingMonitorQuery GRIRClearingMonitorStatusQuery GRIROpenItemQuery GRIRPurchaseOrderQuery GRIRAccountingDocumentQuery GRIRPurchaseOrderHistoryQuery GRIRPurOrdHistoryWithDeliveryCostsQuery GRIRGoodsReceiptQuery GRIRInvoiceReceiptQuery GRIRVendorContactDataQuery GRIRVendorDefaultContactDataQuery GRIRClearingMonitorStatusClearedQuery GRIRClearingMonitorStatusOpenQuery This metadata is available in the SAP HANA Live Authorization Assistant. For more information, see the section SAP HANA Live Authorization Assistant under Privileges, as well as the documentation available on SAP Help Portal at Assistant .
http://help.sap.com/hba
SAP HANA Live Tools SAP HANA Live Authorization
1.10.2.4 Authorization for SAP ERP - Production Planning You must maintain the following additional authorization when a business user works with query views that require the use of the factory calendar in the application SAP Manufacturing: For the activation of the query views MfgOrderItemBacklogQuery, MfgOrderItemDueDateAdherenceQuery, MfgOrderOperationBacklogQuery, and MfgOrderOperationDurationQuery and the reuse views consumed by these query views, the user _SYS_REPO has to be assigned the role AFL__SYS_AFL_ERPA_EXECUTE_WITH_GRANT_OPTION. On the Object Privileges tab, in addition to the relevant query views, the business user also requires the SQL privilege for table TFACS (pre-defined schema SAP_ECC), which is the table for the factory calendar.
1.10.2.5 Authorization for SAP Access Control Role Analytics Users of the SAP Access Control Role Analytics application accessing the data replicated from the SAP GRC system use SAP HANA studio users. There is no direct relationship between a user in GRC Server and the corresponding user in the SAP HANA studio accessing the analytic application. Therefore, it is necessary to configure various authorization-relevant settings in the SAP HANA studio to restrict access to the replicated data.
Authorization Settings General Settings You must ensure that users have the right level of authorization to access data replicated from SAP GRC, and that it is available in the analytic application. To do so, ensure that the following authorization-relevant settings have been made: To enable access to the SAP Access Control Role Analytics application, an administrator has created users in the SAP HANA studio. You have installed and activated the virtual data model views for GRC in the SAP HANA studio. You have configured data replication between the GRC server and the SAP HANA server. For more information, see the Installation Information section of this guide, as well as the documentation available on SAP Help Portal at solutions for GRC .
http://help.sap.com/hba
Application Help SAP HANA Live for SAP
Settings for Business Users Grant authorization to users that only need to access the analytic application as follows: 1. Create and assign analytic privileges to users for granting access to the following query views from the package sap.hba.apps.grcra-reuse.views: AccessControlCriticalLevelQuery AccessControlRoleActionQuery AccessControlRoleComparisonQuery AccessControlRoleSensitivityQuery AccessControlRoleTypeQuery AccessControlUserRoleRelationQuery BusRoleMgmtConnGroupQuery BusRoleMgmtRoleQuery FreqUsedRolesDetailQuery
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 38 of 44
FreqUsedRolesQuery OrphanedRolesDetailQuery OrphanedRolesQuery UnusedRolesDetailQuery UnusedRolesQuery
Recommendation SAP recommends that you create analytic privileges for the above query views with restrictions on the view attributes according to your business requirements. 2. Grant the following SQL privileges to the user: In the Unused Role Analysis for the SAP Access Control Role Analytics application, users can choose to deprovision unused roles. You must assign SELECT, INSERT and UPDATE privileges to them for the table SAP_HBA.sap.hba.apps.grcra-reuse.db::GRCANA_DEPROVISION. SELECT privilege on the following query views: _SYS_BIC.sap.hba.apps.grcra-reuse.views/AccessControlCriticalLevelQuery _SYS_BIC.sap.hba.apps.grcra-reuse.views/AccessControlRoleActionQuery _SYS_BIC.sap.hba.apps.grcra-reuse.views/AccessControlRoleComparisonQuery _SYS_BIC.sap.hba.apps.grcra-reuse.views/AccessControlRoleSensitivityQuery _SYS_BIC.sap.hba.apps.grcra-reuse.views/AccessControlRoleTypeQuery _SYS_BIC.sap.hba.apps.grcra-reuse.views/AccessControlUserRoleRelationQuery _SYS_BIC.sap.hba.apps.grcra-reuse.views/BusRoleMgmtConnGroupQuery _SYS_BIC.sap.hba.apps.grcra-reuse.views/BusRoleMgmtRoleQuery _SYS_BIC.sap.hba.apps.grcra-reuse.views/FreqUsedRolesDetailQuery _SYS_BIC.sap.hba.apps.grcra-reuse.views/FreqUsedRolesQuery _SYS_BIC.sap.hba.apps.grcra-reuse.views/OrphanedRolesDetailQuery _SYS_BIC.sap.hba.apps.grcra-reuse.views/OrphanedRolesQuery _SYS_BIC.sap.hba.apps.grcra-reuse.views/UnusedRolesDetailQuery _SYS_BIC.sap.hba.apps.grcra-reuse.views/UnusedRolesQuery
Note SAP recommends that you do not grant SYSTEM user permissions to users accessing the SAP Access Control Role Analytics application, as this will give them full access to the data. Defining Restrictions on Views in the SAP HANA Studio You can restrict access to data for users of the SAP Access Control Role Analytics application as follows: By defining row-based access restrictions by analytic privileges on query views according to your data access control requirements. For example, in the query view UnusedRolesQuery, you can assign the restriction on the attribute SAPClient in the analytic privilege. This ensures client isolation, which means that this analytic privilege grants access to view the data for that particular client only. If you do not assign any restriction on the attribute SAPClient in the analytic privilege, this analytic privilege grants access to view data for all clients. In the analytic privilege, you can restrict the range of attribute values and their combinations that a particular user can see in the application.
Recommendation SAP recommends that you define the authorizations as SAP HANA roles, which can then be more easily assigned to existing and new users. Such a role can, for example, contain the necessary SQL privileges for accessing the query views and non-query views, and for assigning analytic privileges to the query views and non-query views.
More Information For more information, see the SAP HANA Security Guide (including SAP HANA Database Security) available on SAP Help Portal at http://help.sap.com/hana_appliance
Security Information .
1.10.2.6 Authorization for SAP HANA Live for Manufacturing Users of SAP HANA Live for Manufacturing accessing the data replicated from the SAP ECC system use SAP HANA studio users. There is no direct relationship between a user in ECC Server and the corresponding user in the SAP HANA studio accessing the analytic application. Therefore, it is necessary to configure various authorization-relevant settings in the SAP HANA studio to restrict access to the replicated data.
Authorization Settings General Settings You must ensure that users have the right level of authorization to access data replicated from SAP ECC, and that it is available in the analytic application. To do so, ensure that the following authorization-relevant settings have been made: To enable access to SAP HANA Live for Manufacturing, an administrator has created users in the SAP HANA studio. You have installed and activated the virtual data model views for OEE in the SAP HANA studio. You have configured data replication between the ECC server and the SAP HANA server. For more information, see the Installation chapters in this guide, as well as the documentation available on SAP Help Portal at http://help.sap.com/hba Manufacturing .
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Application Help SAP HANA Live for SAP ERP (VDM)
Page 39 of 44
Settings for Business Users Grant authorization to users that only need to access the analytic application as follows: In addition to the authorization that is relevant for planners, you must also do the following: 1. Create and assign analytic privileges to users for granting access to the following query views from the package sap.hba.oee: AttachedChildMachineEventsQuery AttachedMachineEventsBySpeedLossQuery AttachedMachineEventsQuery AttachedRootCauseMachinesQuery DistributedOEELossesByMachineQuery EffectiveUnscheduledDowntimeQuery OEEAllLossesQuery OEELossesByReasonQuery OEEQuery OEEQuery_V2 QualityLossByLossReasonQuery ScheduledDowntimeByLossReasonQuery ScheduledDowntimeQuery ShopFloorDataCollectionReportQuery SpeedLossByLossReasonQuery UnscheduledDowntimeByLossReasonQuery
Recommendation SAP recommends that you create analytic privileges for the above query views with restrictions on the view attributes according to your business requirements. 2. Create and assign analytic privileges to users for granting full access to the non-query views consumed by the query views listed above. These views are part of the SAP HANA Live for Manufacturing virtual data model. Include the views listed below from the package sap.hba.oee: OEEAllDataElements OEECorporationHierarchy OEEGlobalHierarchy OEEGlobalLossReason OEEKPITargets OEELevelBasedCorporationHierarchy OEELoadingTime OEELossesByReason OEELossReasonHierarchy OEEMachineLossesByReason OEEMachineLossReasonHierarchy OEEPlantHierarchy OEEPlantLossReason OEEShiftDefinition ProductionRun ProductionRunForMachine ProductionRunHeader ProductionRunHeaderAndData PeoductionRunHeaderAndInterval ProductionRunHeaderAndIntervalEvent QualityLossByLossReason QualityLossReasonHierarchy ScheduledDowntime ScheduledDowntimeByLossReason ScheduledDowntimeLossReasonHierarchy ScheduledDowntimeLossReasonHierarchy_V2 ShopFloorDataCollectionElement ShopFloorDataElementTypes SpeedLossByLossReason SpeedLossReasonHierarchy UnscheduledDowntimeByLossReason UnscheduledDowntimeLossReasonHierarchy
Recommendation SAP recommends that you create one analytic privilege containing all non-query view references. The restriction for this analytic privilege must be empty, which means that this analytic privilege grants full access to the non-query views mentioned above. 3. When business users work with the application SAP HANA Live for Manufacturing, you must assign them following authorization: SQL SELECT, UPDATE, DELETE and INSERT privileges on schema SAP_HBA Role: sap.hba.apps.oee:BusinessUser 4. Grant SELECT privilege on the following query views: AttachedChildMachineEventsQuery AttachedMachineEventsBySpeedLossQuery AttachedMachineEventsQuery AttachedRootCauseMachinesQuery DistributedOEELossesByMachineQuery
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 40 of 44
EffectiveUnscheduledDowntimeQuery OEEAllLossesQuery OEELossesByReasonQuery OEEQuery OEEQuery_V2 QualityLossByLossReasonQuery ScheduledDowntimeByLossReasonQuery ScheduledDowntimeQuery ShopFloorDataCollectionReportQuery SpeedLossByLossReasonQuery UnscheduledDowntimeByLossReasonQuery 5. The SAP HANA Live for Manufacturing app SAP OEE Analysis Report also supports custom development. For this, the application privilege sap.hba.apps.oee:Admin is required.
1.10.2.7 Authorization for SAP HANA Live for Global Trade Services SAP HANA Live for Global Trade Services (GTS) provides an enhanced authorization check that you can activate in Customizing. For more information, see SAP Note 1892050
.
1.10.2.8 Authorization for SAP Working Capital Analytics Authorization Concept The general authorization concept applies as described in the Privileges section. The relevant query views consumed by Working Capital Analytics are: sap.hba.apps.wca.dso.s.v/WCAClearedReceivableQuery sap.hba.apps.wca.dso.s.v/WCADaysSalesOutstandingQuery sap.hba.apps.wca.dso.s.v/WCADSORevenueQuery sap.hba.apps.wca.dso.s.v/WCAReceivableHistoryQuery sap.hba.apps.wca.dso.s.v/WCARevenueQuery sap.hba.apps.wca.dso.s.v/WCAOpenReceivableQuery sap.hba.apps.wca.dso.s.v/WCAReceivableQuery sap.hba.apps.wca.dpo.s.v/WCAClearedPayableQuery sap.hba.apps.wca.dpo.s.v/WCADaysPayableOutstandingQuery sap.hba.apps.wca.dpo.s.v/WCADPOExpenseQuery sap.hba.apps.wca.dpo.s.v/WCAPayableHistoryQuery sap.hba.apps.wca.dpo.s.v/WCAExpenseQuery sap.hba.apps.wca.dpo.s.v/WCAOpenPayableQuery sap.hba.apps.wca.dpo.s.v/WCAPayableQuery sap.hba.ecc/CompanyCodeQuery sap.hba.ecc/CurrencyQuery sap.hba.ecc/YearMonthQuery sap.hba.ecc/ExchangeRateQuery sap.hba.ecc/SAPClientQuery In addition, the following authorization concept is needed for Path Persistence: The authorization for the read/write access to the database table can be controlled by granting privileges to the views and procedures. Read Access SQL object privileges (SELECT) for the runtime objects of the following query views: “_SYS_BIC”.“sap.hba.apps.reuse.apf.s.v/AnalysisPathQuery” “_SYS_BIC”.“sap.hba.apps.reuse.apf.s.v/AnalysisPathCountQuery” Analytic privileges for sap.hba.apps.reuse.apf.s.v/AnalysisPathQuery and sap.hba.apps.reuse.apf.s.v/AnalysisPathCountQuery, defining which rows of the view the user is allowed to select Write Access SQL EXECUTE object privilege for the following procedures: sap.hba.apps.reuse.apf.s.logic/InsertAnalysisPath sap.hba.apps.reuse.apf.s.logic/UpdateAnalysisPath sap.hba.apps.reuse.apf.s.logic/DeleteAnalysisPath Moreover, SQLSELECT object privileges for the following tables/views of schema _SYS_BI are required: BIMC_ALL_CUBES BIMC_CONFIGURATION BIMC_CUBES BIMC_DIMENSIONS BIMC_MEASURES BIMC_PROPERTIES
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 41 of 44
BIMC_VARIABLE_ASSIGNMENT BIMC_VARIABLE_VALUE BIMC_VARIABLE_VIEW BIMC_VARIABLE
Running SAP Working Capital Analytics The SAP Working Capital Analytics application is accessed using a URL that contains an SAP-specific parameter. For security reasons, SAP strongly recommends the following:
Recommendation Do not save the URL in your browser favorites. If you save the URL in the browser favorites, it can be manipulated by script or browser plugins, for example. Instead, create a shortcut on your desktop that you can use to start the application. When finishing your work, make sure you close the browsing session using the Logout button. For any application extension (such as the use of additional charts), ensure that both the extension and its libraries are trustful.
1.10.2.9 Authorization for SAP HANA Live for SAP CRM Besides the standard functionality for modelling authorizations based on analytic privileges, SAP HANA Live for SAP CRM offers the following additional possibilities for authorization restrictions: Authorization based on organizational data: An employee is only allowed to select business transactions to which they are assigned as the employee responsible. A manager is also allowed to select all business transactions belonging to their assigned organizational unit and its child organization units. Authorization based on the Access Control Engine (ACE) If the ACE is active in an SAP CRM system, a user is only allowed to access business transactions for which the ACE has granted the specific authorization. The calculation views delivered in SAP HANA Live for SAP CRM do not include such authorization checks in the models. Whilst it is possible to restrict the selected results using appropriate WHERE clauses when executing a query, this approach does not provide an integrated authorization check and requires the application to explicitly provide the necessary restrictions. SAP HANA Live for SAP CRM provides several examples and reusable views to implement such authorization checks directly in reporting models. This restricts the selected business transactions automatically, based on the available authorizations. For more information, see SAP Note 1848159
.
To access the OData services of the sap.hba.apps.CRMHLQ package, the SAP HANA user requires the assignment of the SAP HANA role sap.hba.apps.crmhlq.roles::crmhlq. In addition, the SAP HANA user requires authorizations to access the VDM calculation views in sap.hba.crm.
1.10.2.10 Authorization for SAP HANA Live for SAP CRM and SAP ERP Cross-Analytics Users of SAP HANA Live for SAP CRM and SAP ERP cross-analytics have authorization to access all SAP HANA Live application content in all the associated SAP systems. Access of a user to the SAP HANA Live application content from an specific SAP system is controlled using analytic privileges. To create authorization for a user based on analytic privileges, proceed as follows: 1. Create a new analytic privilege. 2. Add the SAP HANA Live for SAP CRM and SAP ERP cross-analytics VDM to this analytic privilege. 3. Maintain logical system values for the attributes CRMLogicalSystem and SDLogicalSystem. 4. Assign this analytic privilege to the user. To access the OData services of the sap.hba.r.x.CRM package, the SAP HANA user requires the assignment of the SAP HANA role sap.hba.r.x.crm.roles::xcrm. In addition, the SAP HANA user requires authorization to access the VDM calculation views in the sap.hba.crm and sap.hba.ecc packages. For each SAP CRM and each SAP ERP system combination, you must create a corresponding analytic privilege. Regarding performance, see SAP Note 2064076
.
1.10.2.11 Authorization for SAP HANA Live for Risk Management SAP HANA Live for Risk Management provides authorization checks in the back end for the virtual data models Loss Events, Risks, and Risk Analysis. For more information, see SAP Note 2069650
.
1.10.2.12 Authorization for SAP HANA Live for Utilities, edition for SAP CRM PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 42 of 44
In SAP HANA Live for Utilities, edition for SAP CRM, the analytic privileges for query views sap.hba.crmiu/UtilitiesContractQuery and sap.hba.crmiu/UtilitiesQuotationQuery can be generated based on the authorization object CRM_ISUITY. You do so using the SAP HANA Live authorization assistant.
1.10.2.13 Authorization for SAP HANA Live for Product Revenue Accounting The user interfaces of SAP HANA Live for SAP Business Suite rely on the access control mechanisms of the underlying SAP HANA database. As a prerequisite, it is assumed that every business user (any user accessing SAP HANA Live content in the SAP HANA database) is created as a named SAP HANA database user. To control the business user’s access to SAP HANA Live application content and displayed data, the relevant authorization settings have to be configured within the SAP HANA database. For more information, see SAP Note 2142327
.
1.10.3 Communication Channel Security SAP highly recommends using SSL to protect network communications. The following table illustrates the communication channels used by SAP HANA Live for SAP Business Suite, the protocol used for the connection, and the type of data transferred. Communication Path
Protocol Used
Type of Data Transferred
Data Requiring Special Protection
Front end client using a Web browser to SAP HANA extended application services
HTTP, HTTPS
All application data
Not relevant
Recommendation SAP recommends using HTTPS.
More Information For more information, see SAP Help Portal at
http://help.sap.com/hana_appliance
Security Information SAP HANA Security Guide .
1.10.4 Communication Destinations Connection Destinations Destination
Delivered
Type
User, Authorizations
Operational System
No
RFC
Data Import User
Description
http://help.sap.com/hana_applianc e Security Guide – TriggerBased Data Replication Using SAP LT Replication Server
1.10.5 Internet Communication Framework Security SAP HANA extended application services is an optional component of the SAP HANA database providing a consumption model that is exposed through HTTP. The programming model of SAP HANA extended application services provides a means to map the database model, consisting of tables, views, and stored procedures, to the consumption model. This mapping can be done in a declarative way or by writing application-specific code that runs in SAP HANA extended application services. You define only those services that are needed for the applications running on your system. SAP HANA supports OData services by adding the definition file to SAP HANA content. Application-specific OData services on SAP HANA extended application services The OData service model definition enables developers to rapidly create services for existing SAP HANA database artifacts. Application-specific XSJS services on SAP HANA extended application services If application developers need more control over the processing logic, SAP HANA extended application services offers XSJS services using server-side JavaScript List of SAP HANA services used by the application: Service Type (XSJS/ODATA)
Authentication Method
URL Path
Supported HTTP Methods
ODATA
HTTP Basic
/CustomersCollection
GET
XSJS
HTTP Basic
/UpdateConfiguration
POST
SAP HANA Live is not Internet-facing applications and is intended to be run entirely in the intranet.
More Information For more information, see the following:
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 43 of 44
For more information, see the following: http://www.odata.org/media/16352/[ms-odata].pdf http://help.sap.com/hana_appliance
Security Information SAP HANA Security Guide .
1.10.6 Data Storage in SAP Invoice and Goods Receipt Reconciliation All data of SAP HANA Live solutions is stored in the database. There is no storage of data on the file system. Note the following: If a processor is entered, the data is saved when choosing OK. The current user is automatically entered as the person who last changed the data. If a comment is entered, the data is saved when choosing Save Comment. The current user is automatically entered as the processor and as the person who last changed the data. If the status is changed on the UI, the data is saved directly without clicking a button. The current user is automatically entered as the processor and as the person who last changed the data. These changes are stored in the SAP HANA database table sap.hba.apps.grircm.db::GRIRCMSTATUS in schema SAP_HBA. The definition of this table is delivered in the file sap.hba.apps.grircm.db.GRIRCMSTATUS.hdbtable. By activating this file, the corresponding table will be created.
Note If you entered comments prior to SP03, note the following: As of SAP Invoice and Goods Receipt Reconciliation 1.0, SP03, the field NOTE (datatype Char512) in table GRIRCMSTATUS has been replaced by the field GRIR_NOTE. This is where your comments are now saved. Previous comments are no longer displayed. If you want previous comments to be displayed, you must transfer them to the new field using an equivalent SQL statement. You must adapt sample code as needed: update "SAP_HBA"."sap.hba.apps.grircm.db::GRIRCMSTATUS" set "GRIR_NOTE" = "NOTE" where "NOTE" != '' and length("GRIR_NOTE") = 0;
Local Storage The local storage of the browser (if supported) is used to store configuration/personalization data permanently. This data contains no confidential data, but only default values (such as client) or metadata for OData service requests to the SAP HANA database. The stored data can be deleted using the standard features of the browser.
1.10.7 Cross-Site Request Forgery (XSRF) Protection All applications have a built-in mechanism for XSRF protection for data-changing requests.
PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 44 of 44
View more...
Comments
