sap

SAP HANA 1.0

January 2015

English

Quick Guide

SAP SEDietmar-Hopp-Allee 1669190 WalldorfGermany

for SAP HANA Accelerated Finance and Controlling rapid-deployment solution V3

SAP Best Practices SAP HANA Accelerated Finance and Controlling rapid-deployment solution V2

Copyright© 2011 SAP AG. All rights reserved.

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

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

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle and Java are registered trademarks of Oracle.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG 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 SE of 11


Icons

Icon Meaning

Caution

Example

Note or Tip

Recommendation

Syntax

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

© SAP SE of 11


Contents

Quick Guide for SAP HANA Accelerated Finance and Controlling rapid-deployment solution V3 51 About This Quick Guide.....................................................................................................52 Solution Overview..............................................................................................................63 Implementation Methodology.............................................................................................64 System Requirements........................................................................................................7

4.1 System Landscape.......................................................................................................74.2 Implementation of Accelerator Functionality.................................................................94.3 Accelerated Transactions...........................................................................................104.4 Table list for acceleration............................................................................................10

5 Impact of the SAP ERP Rapid-Deployment Solution for Accelerated Finance and Controlling with SAP HANA.....................................................................................................11

5.1 Authorization Concept................................................................................................115.2 Transaction SE16H....................................................................................................11

© SAP SE of 11


Quick Guide for SAP HANA Accelerated Finance and Controlling rapid-deployment solution V3

1 About This Quick GuideThis Quick Guide helps consultants and customer project members to implement the SAP ERP rapid-deployment solution for Accelerated Finance and Controlling with SAP HANA™. The guide focuses on the technical aspects of the implementation and directs you to more detailed documentation.This document is aimed at consultants implementing the solution for customers who have already implemented at least one of the following SAP ERP components:

Component Description

FI-AA Asset Accounting

EC-PCA Profit Center Accounting

FI-GL (New G/L) General Ledger Accounting

FI-GL Classic General Ledger

FI-AP Accounts Payable

FI-AR Accounts Receivable

FI-SL Special Purpose Ledger

CO-OM Cost Center Accounting

CO-OM Overhead management

CO-OM Project System

IM Investment Management

CO-PC-ACT Material Ledger

CO-PC-OBJ Production Cost

CO-PA Profitability Analysis

PSM-FM Funds Management

PSM-GM Grantee Management

PSM-FG US Federal Government

Note that this guide does not include information about the installation, configuration, and system administration of SAP HANA appliance software and the SAP System Landscape Transformation Server. For more information about these topics, see SAP Help Portal at http://help.sap.com → SAP In-Memory Computing → SAP HANA Appliance Software.

© SAP SE of 11

http://help.sap.com/


2 Solution OverviewSAP HANA Accelerated Finance and Controlling rapid-deployment solution V2 has the following attributes:

It is based on SAP ERP 6.0 (all EHP levels) and SAP HANA 1.0 SPS05 or later

It supports the following scenarios: Scenario 1 – ERP Financial Accounting Accelerator with SAP HANA

Scenario 2 – ERP Controlling Accelerator with SAP HANA

Scenario 3 – ERP Material Ledger Accelerator with SAP HANA

Scenario 4 – ERP Production Cost Analysis Accelerator with SAP HANA

Scenario 5 – ERP profitability analysis Accelerator with SAP HANA

Scenario 6 – ERP Funds Management and Grantee Management Accelerator with SAP HANA

Scenario 7 – ERP US Federal Government Accelerator with SAP HANA

For more information about the scenarios, see the content library included in the step-by-step guide: Deploy → Train Key Users → Business Process Documentation.

It targets customers that have already implemented the following SAP ERP components:

Scenario 1 – Asset Accounting (FI-AA), Profit Center Accounting (EC-PCA), General Ledger (FI-GL New G/L), or Special Purpose Ledger (FI-SL)

Scenario 2 – Cost Center Accounting (CO-OM), Investment Management (IM), Overhead Management, or Project System

Scenario 3 – Material Ledger (CO-PC-ACT)

Scenario 4 – Production Cost (CO-PC-OBJ)

Scenario 5 – Profitability Analysis (CO-PA)

Scenario 6 – Funds Management (PSM-FM), Grantee Management(PSM-GM)

Scenario 7 – US Federal Government(PSM-FG)

3 Implementation MethodologyOverall project guidance is provided by a specific implementation roadmap, the step-by-step guide for the SAP HANA Accelerated Finance and Controlling rapid-deployment solution, which is a phased, delivery-oriented methodology that streamlines implementation projects for solution packages. The methodology supports project teams with templates, tools, questionnaires, and checklists, including guidebooks and accelerators to ensure the quick and pragmatic implementation of rapid-deployment solutions. To obtain access to the methodology, ask your SAP Consulting contact.

© SAP SE of 11


4 System Requirements4.1 System LandscapeThe customer needs to provide a system landscape with the required software components already installed to enable the project team to implement and configure the scope of the SAP HANA Accelerated Finance and Controlling rapid-deployment solution. Before the solution can be installed and activated, the SAP HANA appliance software needs to be completely installed and configured. The following graphic illustrates the required system landscape:

Alternatively, you can install the SLT component on the source ERP system as shown in the following graphic. Be aware of the additional software requirements for the source system if you want to adopt this option.

The minimum required release is SAP HANA 1.0 SPS 05. For more information about installing and configuring the SAP HANA appliance software, see the documentation on SAP Help Portal at http://help.sap.com → SAP In-Memory Computing → SAP HANA Appliance Software → Installation and Upgrade Information.

For SAP HANA sizing guidelines (RAM, CPU, Disk) see SAP note 1514966. SAP HANA In-Memory Database can also be sized using SAP QuickSizer. Please go to http://service.sap.com/quicksizer for further information.

© SAP SE of 11

http://service.sap.com/quicksizer

https://service.sap.com/sap/support/notes/1514966

http://help.sap.com/


Before the solution can be deployed, you need to check whether the following requirements have been met:

Check whether the required kernel is installed on the SAP ERP systemYou need to use one of the following SAP Kernels, including the necessary DBSL (database shared library for the SAP HANA database):SAP Kernel 720 64-bit Unicode with patch level 103 or higher;SAP Kernel 720EXT 64-bit Unicode with patch level 103 or higher;For an overview and information about installing the required software components, see SAP Note 1597627.

Check whether the DB client is installed on the ERP application serversHANA DB client needs to be installed on all application servers. , For additional installation information, see SAP note 1517236.

Check whether the SAP Landscape Transformation Replication Server is availableThe SLT system is the default approach for replication and is required for all scenarios. For more information about installation and configuration, see the SAP HANA Installation Guide - Trigger-Based Replication (SLT) on SAP Help Portal at http://www.help.sap.com → SAP In-Memory Computing → SAP HANA Appliance Software → Installation and Upgrade Information.

© SAP SE of 11

http://www.help.sap.com/




4.2 Implementation of Accelerator Functionality

The preconditions for using the ERP accelerators with SAP HANA as HDB are as follows:1. SAP Kernel 7.20 (DCK) 64-bit Unicode with at least patch level 100 and at least

HANA-DBSL patch level 100. Only when you use SAP Kernel 7.20 can you set up a connection with a HDB system. For more information, see Note 1597627.

If you are using a non-Unicode (NUC) SAP Kernel, see note 1700052.2. It is recommended to apply at least the following support packages to your system

Product Product Version

Component Comments

SAP ERP ECC 6.0 EHP0

ECC 6.0 EHP2 This EHP version is not applicable to scenarios ERP Funds Management and Grantee Management Accelerator and ERP US Federal Government Accelerator with SAP HANA

ECC 6.0 EHP3

ECC 6.0 EHP4

ECC 6.0 EHP5

ECC 6.0 EHP6

SAP NW SAP NW 7.00SAP NW 7.01 SAP NW 7.02SAP NW 7.03

Trigger-Based Replication Using SAP LT

SAP LT Replication Server

DMIS Check note 1605140 to get exact DMIS component version according to ERP version and SAP HANA versionRefer to the SAP HANA Enterprise 1.0 SP05 Installation Guide: Installing Trigger-Based Replication on the SAP Service Marketplace at http://service.sap.com/hana

SAP HANA SAP HANA 1.0 SP05 or above

SAP HANA ServerSAP HANA ClientSAP HANA Studio

Refer to SAP Notes: 1523337, 1514967

The acceleration solution is in continuous development and it’s always recommended to apply the latest support packages for each enhancement package. If you use an SAP ERP system on a lower support package level, you

© SAP SE of 11



http://service.sap.com/hana


may implement the attached SAP Notes instead to activate the accelerator functionality.

4.3 Accelerated TransactionsWith SAP HANA Accelerated Finance and Controlling rapid deployment solution, you can drastically increase the speed to execute reports and the amount of data that you can analyze. This document attached here describes the complete list of accelerated transactions and other objects (BW Data Source, etc). Depending on the configuration carried out in your project, your scenario may differ from the descriptions in this document.

4.4 Table list for accelerationTo accelerate certain business function, the corresponding tables need to be replicated to HANA server. You can find the detail table list required for SAP HANA Accelerated Finance and Controlling rapid deployment solution below. For detail steps how replicate the tables, please refer to configuration guide V29 - ERP Finance and Controlling Accelerator with SAP HANA – General Configuration.

© SAP SE of 11


5 Impact of the SAP ERP Rapid-Deployment Solution for Accelerated Finance and Controlling with SAP HANA

5.1 Authorization Concept

The SAP authorization concept regulates user access to transactions and business data in SAP systems. Authorization objects for each business object that are assigned to user roles define whether a user is allowed access to business data. When you use drilldown reporting in SAP ERP, the authorization check is applied when the data has been read from the database. The data to be displayed is filtered according to the authorization granted to the user. If a user has selected data for which the user role is insufficient, the data read from the database is not displayed.

Authorization is rather complex and is described extensively in the system administration guide. For a short introduction, you can refer to note 20534.

To speed up the reading process and avoid selection of additional data by the report, the process sequence has been changed in the context of reading data from SAP HANA for the following processes: Drilldown Reporting (that is, General Ledger Accounting (New) and FI-SL if data reading

is activated upon each navigation step) Line Item Browser Financial Statements (Period Accounting)

The authorization check is performed based on the selection restrictions specified on the selection screen. If the user does not have sufficient authorization for all data records to be selected, the selection restrictions have to be corrected before the program can be executed. For example, user is authorized for account group XYZ only. The user doesn’t enter a restriction for accounts, so the selection would also include accounts with account group ABC. The program will generate a corresponding error message. Therefore, variants used previously may not be usable without modification.

5.2 Transaction SE16HThis transaction can be used in the SAP ERP system to view the content of tables in the SAP HANA database without having to access the SAP HANA studio.For more information about transaction SE16H, see SAP Note 1636416.

© SAP SE of 11


sap

Documents