Extractor-Based Data Acquisition by SAP HANA Direct Extractor (1)

Installation and Configuration Guide

Extractor-based Data Acquisition by SAP HANA Direct Extractor Connection

SAP HANA Appliance Software SPS 04

Target Audience

■ Consultants ■ Administrators ■ Others

Public Document version 1.0 – 07/12/2012


2 April 2012

History of Changes

The SAP HANA Direct Extractor Connection (DXC) Installation and Configuration Guide is

regularly updated at http://service.sap.com/hana Installation and Initial

Configuration.

Make sure you have the latest version of this document by checking SAP Service Marketplace immediately before starting the installation.

The following table provides an overview of the most important changes that were made in the latest versions.

Master Guide Version Important Changes

1.00 (April 30, 2012) Initial version of the document

http://service.sap.com/hana


April 2012 3

Contents

1 Getting Started ............................................................................................... 5

1.1 About this Document................................................................................ 5

1.2 Related Information ................................................................................. 6

1.2.1 Planning Information ......................................................................... 6

1.2.2 Further Useful Links .......................................................................... 6

1.3 Important SAP Notes ............................................................................... 7

2 Overview of the SAP HANA Direct Extractor Connection ............................... 9

2.2 Setup steps in SAP HANA ..................................................................... 11

2.2.1 Enabling XSEngine and ICM Service .............................................. 11

2.2.2 Setup of SAP HANA Direct Extractor Connection ........................... 12

2.3 Delivery Unit Import ............................................................................... 12

2.4 Application Server Configuration ........................................................... 12

2.4.1 Testing the Setup of the DXC Application ....................................... 13

2.4.2 Creating a DXC User in SAP HANA ................................................ 13

2.4.3 Creating a DXC Schema in SAP HANA .......................................... 14

2.5 Setup Steps in the SAP Business Suite System .................................... 14

2.5.1 Create an HTTP Connection to the SAP HANA System ................. 14

2.5.2 Configure DXC HTTP Interface Destination .................................... 15

2.5.3 Choose the System-Wide Setting for DataSources ......................... 15

2.5.4 Create and Populate a Table to Specify the DataSources Used by DXC ................................................................................................. 16

2.5.5 Indicate the Table Used to Specify the DataSources for Use with DXC ................................................................................................. 17

2.5.6 Designate the Schema in SAP HANA to Store IMDSOs ................. 18

3 Configuration Steps Specific to SAP Business Warehouse ......................... 19

3.1 Install Business Content DataSources ................................................... 19

3.2 Replicate DataSources .......................................................................... 19

3.3 Create InfoPackages ............................................................................. 20

3.4 Monitor Data Load in the Source SAP Business Suite System .............. 21

3.5 Verifying Data Transfer in the SAP HANA Database ............................. 21

3.6 Create a Process Chain for Regular Data Transfer ............................... 22

3.7 Monitoring the Activation Process of In-Memory DataStore Objects in SAP HANA ............................................................................................. 24

3.8 Setup Email Alerting for the Activation Process of In-Memory DataStore Objects in SAP HANA ........................................................... 24

3.9 DXC and SAP HANA Data Modeling ..................................................... 25

3.10 Further Information .............................................................................. 25

4 Appendix – DXC System Landscape Variants: The “Sidecar” Approach ..... 27

5 References ................................................................................................... 29


4 April 2012

Getting Started

April 2012 5

1 Getting Started The SAP HANA Direct Extractor Connection (DXC) Installation and Configuration Guide provides information about setup and technical configuration of the SAP HANA Direct Extractor Connection (DXC). Additionally, this guide gives information about basic operation of the SAP HANA Direct Extractor Connection, particularly scheduling and monitoring of extraction and load.

1.1 About this Document

Purpose

This Installation and Configuration Guide is the central starting point for the technical implementation of the SAP HANA Direct Extractor Connection in an SAP HANA appliance. You can find scenario-specific information in this guide.

The central starting point for the technical upgrade of your SAP application/solution is the Upgrade Master Guide, which you can find on SAP Service Marketplace at http://service.sap.com/instguides.

Use this guide to get an overview of the SAP HANA Direct Extractor Connection, its delivery units, and its scenarios from a technical perspective. This guide refers you to the required detailed information about:

Import of delivery units

SAP Notes

Configuration documentation

For a general overview of the available SAP documentation, see The Main SAP Documentation Types.

This Installation and Configuration Guide consists of the following main sections:

Getting Started

This section gives an overview of the purpose of this document. It also contains references to the most important SAP Notes that apply to the installation and configuration of the SAP HANA Direct Extractor Connection.

Overview of the SAP HANA Direct Extractor Connection

This section gives an overview of the installation of the SAP HANA Direct Extractor Connection and the different setup steps.

Configuration Steps Specific to SAP Business Warehouse

This section gives an overview of the configuration of SAP Business Warehouse and how to transfer data from DataSources to SAP HANA using DXC.

Appendix – DXC System Landscape Variants: The “Sidecar” Approach

This section gives an overview of the “sidecar” approach which covers the following use cases:

o You want to implement DXC with an older version of SAP Business Suite system, that is, not based on SAP NetWeaver 7.0 or higher (for example 4.6C).

o You already use the embedded BW system and do not want to use it for the purpose of transferring data from BW to SAP HANA using DXC.

Getting Started

6 April 2012

References

This section gives an overview of related documents containing further information about the SAP HANA Direct Extractor Connection.

You can find the most current information about the technical implementation of the SAP HANA Direct Extractor Connection and the latest installation and configuration guides on SAP Service Marketplace at http://service.sap.com/instguides.

We strongly recommend that you use the documents available here. The guides are regularly updated.

1.2 Related Information

1.2.1 Planning Information

For more information about planning topics not covered in this guide, see the following content on SAP Service Marketplace:

Content Location on SAP Service Marketplace

Latest versions of installation and upgrade guides

http://service.sap.com/instguides

General information about the SAP HANA Direct Extractor Connection

http://service.sap.com/<quick link>

SAP HANA Administration Guide http://help.sap.com/hana SAP HANA

Appliance Administration Guide

Sizing, calculation of hardware requirements - such as CPU, disk and memory resource - with the Quick Sizer tool

http://service.sap.com/quicksizer

Released platforms and technology-related topics such as maintenance strategies and language support

http://service.sap.com/platforms

To access the Platform Availablity Matrix directly, enter http://service.sap.com/pam.

Network security http://service.sap.com/securityguide

High Availability http://www.sdn.sap.com/irj/sdn/ha

Performance http://service.sap.com/performance

Information about Support Package Stacks, latest software versions and patch level requirements

http://service.sap.com/sp-stacks

1.2.2 Further Useful Links

The following table lists further useful links on SAP Service Marketplace:

Content Location on SAP Service Marketplace

Information about creating error messages http://service.sap.com/message

SAP Notes search http://service.sap.com/notes

Getting Started

April 2012 7

1.3 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.

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 Title Description

1583403 Direct extractor connection to SAP HANA

Main note for setup steps required in the source SAP Business Suite system.

1670518 SAP HANA Direct Extractor Connection: Monitoring

Provides information on how to monitor SAP HANA Direct Extractor Connection (DXC), in particular the activation processing for In-Memory DataStore Objects (IMDSOs).

1688750 DataSource: Reading a property in the source system

Apply this note to the source SAP Business Suite system only if you have the “sidecar” scenario described in section Appendix – DXC System Landscape Variants: The "Sidecar" Approach.

1701750 DataSource: Secondary Index on the PSA

If your DataSource is missing a key, apply this note to any BW systems connected to the SAP Business Suite system you are using with DXC.

1677278 DataSource: Changing the Key Definition (A version)

Provides a report where you can define a semantic key for any DataSources that are missing keys. DataSources without keys will cause an error when you try to generate the In-Memory DataStore Object in SAP HANA.

Before applying this not to your SAP Business Suite system, first apply SAP note 1701750 to any BW systems connected to the SAP Business Suite system you are using with DXC.

1710236 SAP HANA DXC: DataSource Restrictions

Lists specific DataSources not supported by DXC.

1714852 Troubleshooting SAP HANA DXC issues

Guidance for troubleshooting DXC issues and the

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








Getting Started

8 April 2012

appropriate action to take.

1665553 Handling issues with IMDSO activation – SAP HANA DXC

Discusses how to report issues with In-Memory DataStore Object activation to SAP.

1714933 DXC: Partitioning In-Memory DSO tables

Provides information about partitioning active data tables of IMDSOs where large data volume is expected.




April 2012 9

2 Overview of the SAP HANA Direct Extractor Connection

SAP HANA Direct Extractor Connect (DXC) is a means for providing out-of-the-box foundational data models to SAP HANA, which are based on SAP Business Suite entities. DXC is also a data acquisition method. The rationale for DXC is essentially simple, low TCO data acquisition for SAP HANA leveraging existing delivered data models.

Customer projects may face significant complexity in modeling entities in SAP Business Suite systems. In many cases, data from different areas in SAP Business Suite systems requires application logic to appropriately represent business documents. SAP Business Content DataSource Extractors have been available for many years as a basis for data modeling and data acquisition for SAP Business Warehouse; now with DXC, these SAP Business Content DataSource Extractors are available to deliver data directly to SAP HANA.

DXC is a batch-driven data acquisition technique; it should be considered as a form of extraction, transformation and load although its transformation capabilities are limited to user exit for extraction (for more information, see http://help.sap.com/saphelp_nw04/helpdata/en/49/ae67401d4988448036b180dc9ec1e6/frameset.htm and http://help.sap.com/saphelp_nw70/helpdata/en/6e/fe6e420f00d242e10000000a1550b0/content.htm).

A key point about DXC is that in many use cases, batch-driven data acquisition at certain intervals is sufficient (for example, every 15 minutes).

Overview of the DXC Rationale:

Leverage pre-existing foundational data models of SAP Business Suite entities for use in SAP HANA data mart scenarios:

o Significantly reduces complexity of data modeling tasks in SAP HANA

o Speeds up timelines for SAP HANA implementation projects

Provide semantically rich data from SAP Business Suite to SAP HANA:

o Ensures that data appropriately represents the state of business documents from ERP

o Application logic to give the data the appropriate contextual meaning is already built into many extractors

Simplicity / Low TCO:

o Re-uses existing proprietary extraction, transformation, and load mechanism built into SAP Business Suite systems over a simple http(s) connection to SAP HANA

o No additional server or application needed in system landscape

Change data capture (delta handling):

o Efficient data acquisition – only bring new or changed data into SAP HANA

o DXC provides a mechanism to properly handle data from all delta processing types

Default DXC Configuration for SAP Business Suite

DXC is available in different configurations based on the SAP Business Suite system.

The default configuration is available for SAP Business Suite systems based on SAP NetWeaver 7.0 or higher – such as ECC 6.0.

The alternative configuration is available for SAP Business Suite systems based on releases lower than SAP NetWeaver 7.0 – such as SAP ERP 4.6, for example. For more

http://help.sap.com/saphelp_nw04/helpdata/en/49/ae67401d4988448036b180dc9ec1e6/frameset.htm

http://help.sap.com/saphelp_nw04/helpdata/en/49/ae67401d4988448036b180dc9ec1e6/frameset.htm

http://help.sap.com/saphelp_nw70/helpdata/en/6e/fe6e420f00d242e10000000a1550b0/content.htm

http://help.sap.com/saphelp_nw70/helpdata/en/6e/fe6e420f00d242e10000000a1550b0/content.htm


10 April 2012

information about the configuration with a SAP Business Suite system based on releases lower than SAP NetWeaver 7.0, see section Appendix – DXC System Landscape Variants: The "Sidecar" Approach.

An SAP Business Suite system is based on SAP NetWeaver. As of SAP NetWeaver version 7.0, SAP Business Warehouse (BW) is part of SAP NetWeaver itself, which means a BW system exists inside SAP Business Suite systems such as ERP (ECC 6.0 or higher). This BW system is referred to as an “embedded BW system”. Typically, this embedded BW system inside SAP Business Suite systems is actually not utilized, since most customers who run BW have it installed on a separate server, and they rely on that one. With the default DXC configuration, we utilize the scheduling and monitoring features of this embedded BW system, but do not utilize its other aspects such as storing data, data warehousing, or reporting / BI. DXC extraction processing essentially bypasses the normal dataflow, and instead sends data to SAP HANA. The following illustration depicts the default configuration of DXC.

An In-Memory DataStore Object (IMDSO) is generated in SAP HANA, which directly corresponds to the structure of the DataSource you are working with. This IMDSO consists of several tables and an activation mechanism. The active data table of the IMDSO can be utilized as a basis for building data models in SAP HANA (attribute views, analytical views, and calculation views).

Data is transferred from the source SAP Business Suite system using an HTTP connection. Generally, the extraction and load process is virtually the same as when extracting and loading SAP Business Warehouse – you rely on InfoPackage scheduling, the data load monitor, process chains, etc – which are all well known from operating SAP Business Warehouse.

DXC does not require BW on SAP HANA. Also with DXC, data is not loaded into the embedded BW system. Instead, data is redirected into SAP HANA.


April 2012 11

2.2 Setup steps in SAP HANA

This section describes the following steps:

Enabling XSEngine and ICM Service

Setup of the Direct Extractor Connection

2.2.1 Enabling XSEngine and ICM Service

Ensure that the necessary technology components in SAP HANA are running, that is:

the XSEngine

the ICM service

If these services are not running, proceed as follows to enable them:

1. Open SAP HANA studio.

2. Right-click your SAP HANA instance and select Administration from the context menu to open the Administration perspective of your SAP HANA instance.

3. Select the Configuration tab. Expand the daemon.ini section and then the sapwebdisp section.

For the instances parameter, a green light showing the number 1 on the Host column should be displayed.

4. If the value 1 is not displayed, double-click the instances parameter and change the

configuration value from 0 to 1.

5. Click Save to save the new value.

6. Continuing in the daemon.ini section, expand the xsengine section.

For the xsengine parameter, a green light showing the number 1 on the Host column should be displayed.

7. If the value 1 is not displayed, double-click the instances parameter and change the

configuration value from 0 to 1.

8. Click Save to save the new value.

Check if the XSEngine is running by accessing the following URL:

http://<hostname>:80<instance number>

The port name in this URL may differ on your system, depending on the instance number of your installation.

If the XSEngine and ICM are operational, you should see the following information on your

screen: SAP XSEngine is up and running.


12 April 2012

2.2.2 Setup of SAP HANA Direct Extractor Connection

The setup of the SAP HANA Direct Extractor Connection application consists of the following

parts.

Import the delivery unit for DXC

Configure the XS Application server to utilize DXC

Verify that DXC is operational

2.3 Delivery Unit Import

Prerequisites

Prior to importing the delivery unit, prepare the delivery unit archive for import. Acquire the delivery unit archive from the SAP Service Marketplace at http://service.sap.com/swdc and save it to a location on your local computer.

Importing the delivery unit

For importing the delivery unit, do the following:

1. Open SAP HANA studio and change to the SAP HANA modeler perspective.

2. On the Quick launch tab, in the Content section choose Import.

3. In the Import dialog, expand the HANA Content node, choose Delivery Unit and click Next.

4. Select Client and navigate to the location on your local computer where you have stored the delivery unit archive.

5. Select the delivery unit archive and click OK.

The status in the Object import simulation should display green lights.

6. Keep the existing defaults, and click Finish.

In the lower right part of the screen you should see a tab display for Job Log, with a progress indicator under Current. Once the delivery unit import is completed, the

message Completed Successfully is displayed.

2.4 Application Server Configuration

The use of the DXC application has to be enabled with the XSEngine component of SAP HANA. To do so, an entry has to be added in the application server configuration.

1. Open the SAP HANA studio and select the instance of the SAP HANA database.

2. Open the Administration perspective and select the Configuration tab.

3. Expand the xsengine.ini section and then the application_container section.

4. Right-click the application_list parameter and select Change from the context menu.

5. In the New Value field, enter libxsdxc.

If another value is already there, put a comma after the existing value and add the value libxsdxc, for example searchservice, libxsdxc.

http://service.sap.com/swdc


April 2012 13

6. Click Save.

In order to make the new configuration effective, the XSEngine has to be restarted.

1. In the Administration perspective of SAP HANA studio, choose the Landscape tab.

2. Right-click the xsengine service and select Stop.

The status light will change to yellow and then to red.

3. Right-click the xsengine service again and select Start missing services.

2.4.1 Testing the Setup of the DXC Application

You can check if the setup of the SAP HANA Direct Extractor Connection application was successful and works as expected. To check the setup, a python script is provided. Proceed as follows:

1. Unzip the file DXCConnectionTest.zip.

2. Use ftp or a similar utility to place the connection test file from the ZIP file on the Linux file system, in location such as /usr/sap/<SID>/HDC<sysnum>/backup.

3. Run the python script with the following command (provide password for SYSTEM user):

python connectionTest.py --httpport=80<instance number> --dbpwd

=<password for SAP HANA database>

If the connection test was successful, you will see the following results:

Testing connectivity of url: http://localhost:80<instance

number>/DXC/DXC.xscfunc

Using database user 'SYSTEM' and password '<password>'

Sending first request (unauthorized)... done. Response status is

401 Unauthorized (as expected)

Sending second request (authorized)... done. Response status is

200 OK (as expected)

CONNECTION TEST SUCCESSFUL

4. Check if DXC is operational. The DXC application should be accessible now by using the following URL:

http://<hostname>:80<instance number>/dxc/dxc.xscfunc

If the check is successful, you will be prompted to save a file with the name

dxc.xscfunc to your computer. The contents of this file are not important; the test is

successful if calling this URL produces this file.

2.4.2 Creating a DXC User in SAP HANA

Create a user who has the privileges to execute the DXC extraction and load. To create this user – in the following sections referred to as the DXC user – do the following:

1. Open SAP HANA studio and select your SAP HANA system.

2. In the navigation tree, select Catalog Authorization Users.

3. Right-click Users and select New User.

4. In the User Name field, enter an appropriate name, for example DXCUSER.

5. Select internal authentication, enter a password and confirm the password.

6. On the Granted Roles tab, add the roles PUBLIC and MONITORING.


14 April 2012

7. Click the green Deploy icon.

2.4.3 Creating a DXC Schema in SAP HANA

Create a schema for use with the SAP HANA Direct Extractor Connection which is owned by the DXC user.

You should create a distinct schema for each specific SAP Business Suite system that you will connect to this SAP HANA system with DXC.

1. In SAP HANA studio, execute the following SQL statement:

create schema <SCHEMANAME> owned by <DXCUSERNAME>

Example:

create schema R3TSCHEMA owned by DXCUSER

2. Click Deploy or press F8 to create the schema.

2.5 Setup Steps in the SAP Business Suite System

Setup in the SAP Business Suite comprises the following steps:

Create an HTTP Connection to the SAP HANA System

Configure DXC HTTP Interface Destination

Choose the System-Wide Setting for DataSources

Create and Populate a Table to Specify the DataSources Used by DXC

(only if you choose the setting DATASOURCE)

Indicate the Table Used to Specify the DataSources for Use with DXC

(only if you choose the setting DATASOURCE)

Designate the Schema in SAP HANA to Store In-Memory DataStore Objects

For more information, please refer to SAP note 1583403.

2.5.1 Create an HTTP Connection to the SAP HANA System

In the SAP Business Suite system, create an HTTP destination of type G using the transaction SM59.

1. On the Configuration of RFC Connections screen, select the node HTTP Connections to External Server and click the Create icon.

2. Provide a name for the HTTP destination, for example DXC_HANA_CONNECTION_<SID>.

3. In the Technical Settings tab, enter the target host name and the port number of your remote SAP HANA system in the Target Host and Service No. fields.

The port number is 80<instance number> of your SAP HANA database.

4. In the Path Prefix field, enter /dxc/dxc.xscfunc.



April 2012 15

5. On the Logon & Security tab, choose Basic Authentication and provide the user name and password of your DXC user.

6. Click Save.

2.5.2 Configure DXC HTTP Interface Destination

Create an entry in the table RSADMIN, which is the primary BW configuration table. In this table, the HTTP destination to the SAP HANA system created earlier is designated as the connection used for DXC.

1. Use transaction SA38 to execute the program SAP_RSADMIN_MAINTAIN.

o In the OBJECT field, enter the value PSA_TO_HDB_DESTINATION.

o In the VALUE field, enter the name of the HTTP destination you created, for example

DXC_HANA_CONNECTION_<SID>.

Make sure that you use upper and lower case letters for the name of the HTTP destination correctly.

2. Click Insert, and then click Execute (F8) to create the table entry.

2.5.3 Choose the System-Wide Setting for DataSources

In this configuration step, you specify the extent of the use of DXC in the source SAP Business Suite system. Keep in mind that subsequent references to SAP BW typically refer to the embedded BW system which lives inside the SAP Business Suite system, unless you are using the “sidecar” approach discussed in section Appendix – DXC System Landscape Variants: The "Sidecar" Approach.

The choice you make for this next configuration setting determines whether the normal BW functionality is available in the system you are using with DXC. - If you are using the embedded BW, depending on your choice, the

embedded BW could potentially become completely disabled. - If you have a remote BW connected to this SAP Business Suite system, it

would not be affected (no matter what choice you make in this section). Nontheless, if you are using the embedded BW for some purpose other than DXC (or you might in the future), the choice in this section is very important.

Take time to discuss the implications of the choice you make here, and make the choice only after proper consideration.


2. Create an additional entry object PSA_TO_HDB. In the VALUE field, enter either the value

GLOBAL, SYSTEM or DATASOURCE, depending on the option which is best in your scenario:

o GLOBAL

All DataSources are available for use with DXC. When you choose this value, it is no longer possible to execute any BW processes or reports in the source system.

Keep in mind that this refers to the BW system used with DXC (which is typically the the embedded BW inside an SAP Business Suite system, which is very often not


16 April 2012

used). If you have a separate SAP BW system connected to this SAP Business Suite system, this setting has no impact (except in the “sidecar” scenario, where it does, see section Appendix – DXC System Landscape Variants: The "Sidecar" Approach).

o SYSTEM

Only the specified clients are used with DXC. The remaining clients are available for DataSources to be extracted, transformed and loaded into the PSA of the SAP BW system (typically this is the embedded BW).

o DATASOURCE

Only the specified DataSources are used with DXC. Any DataSources not specified can be extracted, transformed and loaded into the PSA of the SAP BW system. If this SAP BW system (embedded BW or sidecar BW) is used for other purposes besides DXC, then choose this option. However, keep in mind that any DataSources you choose to be used by DXC cannot be used in this (embedded or sidecar) SAP BW system.

3. Once you have decided on the appropriate configuration setting, enter the text for that choice (for example DATASOURCE), and click Insert.

4. Click Execute (F8) to create the table entry.

2.5.4 Create and Populate a Table to Specify the DataSources Used by DXC

The steps described in this section are only required if you choose the value DATASOURCE for the PSA_TO_HDB entry object.

If you decide to use the DATASOURCE setting, then in order to be able to use specifc DataSources with DXC, you have to create a customer-specific database table to list the DataSources to use with DXC.

1. Use transaction SE11 to create a new table.

o In the Database Table field, enter a custom table name, for example

ZDXCDATASOURCES.

o In the Short Description field, provide description for the table, for example

DataSources for DXC.

2. Click Create.

3. On the Delivery and Maintenance tab, in the Delivery Class field, select C, and choose

Display/Maintenance Allowed from the Data Browser/Table View Maint. List.

4. Change to the Fields tab.

5. Fill out the first table row as follows:

o In the Field column, enter the value DATASOURCE.

o Select the checkboxes in the Key and Initial Values columns.

o In the Data element column, enter the value ROOSOURCER.

6. Press ENTER to apply the changes and to change to the next table row.

7. Fill out the next table row as follows:

o In the Field column, enter the value LOGSYS.


April 2012 17

o Select the checkbox in the Key column. Do not select the checkbox in the Initial Values column.

o In the Data element column, enter the value RSSLOGSYS.

8. Press ENTER to apply the changes.

9. Click Save.

A dialog box appears where you can enter an appropriate customer package (starting with “Z”) for the object directory entry.

If you are not sure which package to use, consult with someone responsible for transporting objects in your system landscape.

10. In the next dialog box, assign this to a change request for eventual transport.

11. Click Technical Settings.

12. In the next screen, enter APPL2 in the Data Class field, and choose 0 in the Size category field.

13. Click Save and then click the green circle with an arrow to return to the previous screen.

14. Click Activate to activate the table. Activation warnings can generally be ignored in this case.

Create table entries for the specific DataSources that you will use with DXC. You can add entries to this table later if you decide to work with additional DataSources.

1. Use transaction SE16, enter the table name you created in the previous section, for example ZDXCDATASOURCES and click Create.

2. Enter the specific DataSource name and logical system name for the relevant client.

There is no value help dropdown here, so you will need to know the exact technical name for the DataSource and logical system name, and enter them with proper spelling.

3. Repeat this action for all DataSources (and all associated relevant clients) that you want to use with DXC.

You have successfully created and populated a table to designate the specific DataSources / clients that you will use with DXC.

2.5.5 Indicate the Table Used to Specify the DataSources for Use with DXC

The steps described in this section are only required if you choose the value DATASOURCE for the PSA_TO_HDB entry object.


o In the OBJECT field, enter the value PSA_TO_HDB_DATASOURCETABLE.


18 April 2012

o In the VALUE field, enter the name of the name of the table you created in the previous section to hold the specific DataSources you want to enable for DXC, for example ZDXCDATASOURCES.

2. Click Insert, and then click Execute (F8).

2.5.6 Designate the Schema in SAP HANA to Store IMDSOs

Within the SAP HANA database, an In-Memory DataStore Object (IMDSO) is generated for each DataSource. An IMDSO is a set of tables with an activation mechanism. In order to make sure that the IMDSOs are generated in the appropriate schema into the SAP HANA database, assign the DXC schema to be used. Use the schema that you created in SAP HANA.

Perform the following actions:


2. Create the entry object PSA_TO_HDB_SCHEMA. In the VALUE filed, enter the name of the

SAP HANA database schema to use, for example R3TSCHEMA.

For more information about creating DXC schema, see the section Creating a DXC Schema in SAP HANA.


April 2012 19

3 Configuration Steps Specific to SAP Business Warehouse

The next steps require SAP Business Warehouse (BW) knowledge, in particular working with DataSources, InfoPackages, and Extraction/Load in a BW context. If you do not have prior SAP BW knowledge, you are encouraged to work with someone such as a consultant who is familiar with DataSources as well as data load scheduling and monitoring in BW. Although data is not sent into BW when working with DXC, BW functionality is used to provide foundational data models to SAP HANA and to transfer data to SAP HANA via DXC. For further information about working with the various SAP BW concepts and tasks described in this guide, please refer to the SAP BW documentation and online help at http://help.sap.com/nw_platform <your SAP NetWeaver Platform version>

Application Help SAP Library <your language> SAP NetWeaver Business Warehouse.

Additionally, if you are unsure which SAP Business Content DataSources you should work with, you are encouraged to work with someone who has knowledge of the specific domain area.

3.1 Install Business Content DataSources

1. Use transaction RSA5 to start the Installation of DataSource from Business Content.

2. Select the specific DataSource that you want to install and click Activate DataSources.

3.2 Replicate DataSources

The next steps involve working in the BW Data Warehousing workbench (transaction RSA1).

Consider the client to use for the BW client carefully. Be aware that once you have decided which client in your system is the BW client, the transaction RSA1 or other BW-related functions cannot be used in any other client. It is very difficult to change to another client later, as once you have executed transaction RSA1, many configurations are performed automatically.

In order to be able to transfer data, you have to create source systems for any clients in the SAP Business Suite system that should be able to extract data and load it to the SAP HANA database. For further information about creating source systems for this purpose, please refer to the BW documentation at http://help.sap.com/nw_platform <your SAP

NetWeaver Platform version> Application Help SAP Library <your language> SAP NetWeaver Business Warehouse.

1. Right-click the source system you are working with and select Replicate DataSources. If prompted about the type of DataSource, choose DataSource for all; do not choose the old 3.x type DataSource.

All DataSources that have been installed using transaction RSA5 are transferred to the Data Warehousing workbench.

2. Right-click the DataSource(s) you want to work with and select Change.

3. In the Change DataSources dialog, click the Activate icon.

This creates an In-Memory DataStore Object (IMDSO) in the SAP HANA database that corresponds to the DataSource structure.

http://help.sap.com/nw_platform



20 April 2012

You can see the In-Memory DataStore Object in the modeling perspective of SAP HANA studio:

1. Log on to SAP HANA studio with the DXC user.

2. In the Modeling perspective, locate and expand the schema that you created for this source system, for example R3TSCHEMA.

3. Expand the folder for Tables and you should see the tables that make up the IMDSO.

The tables include the DataSource with the following naming convention:

o /BIC/A<DATASOURCENAME>00

This is the active data table. This is the table that will end up storing all of the data that gets loaded into this IMDSO from DXC. This table is the one to use in SAP HANA data modeling – it is a base DB (columnar) table that can be used in attribute views, analytic views, calculation views, etc.

o /BIC/A<DATASOURCENAME>40

This is the activation queue table. When a DXC extraction/load job executes, it loads the entire series of data packages for this job into this activation queue, and then in a separate step they are activated into the active data table. This activation mechanism preserves proper sequence of records and ensures that all delta processing types (change data capture) are handled appropriately.

o /BIC/A<DATASOURCENAME>70, /BIC/A<DATASOURCENAME>80,

/BIC/A<DATASOURCENAME>AO, etc.

These are technical tables used to control the activation process.

If you expect a significant data volume to accumulate in a particular IMDSO, for performance reasons it makes sense to partition the active data table of that IMDSO. For information on partitioning the active data table of an IMDSO, please refer to SAP note 1714933.

3.3 Create InfoPackages

In order to be able to load the DataSources into the SAP HANA database, you have to create InfoPackages for the DataSources. In some cases, it is feasible to have delta processing (change data capture). In this case, create the following InfoPackages:

One InfoPackage for the delta initialization

One InfoPackage for the regular delta data loads

Otherwise, if delta processing is not available, create an InfoPackage for full load, or several InfoPackages for full load using selection criteria.

After the InfoPackage has been created, schedule it to load data into your IMDSO in the SAP HANA database.

1. In the Data Warehousing workbench, right-click the DataSource you are working with and select Create InfoPackage.

2. In the Create InfoPackage dialog, select the appropriate options and click Save.

3. On the Schedule tab, select the appropriate time for the job to execute, and click Start to schedule the extraction job.



April 2012 21

3.4 Monitor Data Load in the Source SAP Business Suite System

After the data load is started, you can monitor the status of the InfoPackages.

1. In the Data Warehousing Workbench, select the InfoPackage you want to monitor and click the Monitor icon.

The Monitor - Administrator Workbench dialog appears.

2. Click the Status tab to get detailed information about the data load.

The data is loaded into the activation queue table for the corresponding IMDSO in the SAP HANA database, although a status message is displayed stating that the request was successfully loaded to PSA.

3. Click the Details tab to get detailed information about the records that have been transferred.

You can navigate through the structure of the processed data packets:

1. Look for Processing (Data Packets), and choose a data package.

2. Expand the node Update PSA. You should see a message like this:

Data package 1 saved to remote SAP HANA DB

You can also expand the node for Subsequent Processing; errors in the activation process will be displayed here.

After the data for a given extraction job has successfully been loaded into the activation queue of the IMDSO, the data is immediately activated into the active data table of the IMDSO.

The order in which data is loaded is important for data consistency. Therefore, all subsequent data activation for an IMDSO will be blocked if a (failed) request is still available in the activation queue table of the IMDSO. If you encounter such an activation failure, please refer to SAP note 1665553.

3.5 Verifying Data Transfer in the SAP HANA Database

You can verify which data has been loaded into the SAP HANA database.


2. Expand the Catalog node, and expand the node for the schema for the specific SAP Business Suite system from which you scheduled an extraction / load job.

3. Find the activation queue table of the IMDSO you are working with.

The naming convention of the active table for the IMDSO is /BIC/A<name of the

DataSource>00, for example /BIC/A0VER_SCARR_ATR00.

4. Right-click this table and select Open Content.

You should see records of the data packages temporarily stored in the activation queue table. If the table is empty (and you see success indicators in the data load monitor, see Monitor Data Load in the Source SAP Business Suite System), then the records have been activated into the active data table.



22 April 2012

When the data load activation is completed, all records from all the data packages will reside in the active data table of the IMDSO. This table holds the historical records also. The naming convention of the active table for the IMDSO is /BIC/A<name of the

DataSource>00, for example /BIC/A0VER_SCARR_ATR00.

5. Right-click this table and select Open Content.

You should see all data extracted from this DataSource there.

While it may be interesting to see the main tables of the IMDSO that store data, the aforementioned steps (checking table contents) are not typically performed in normal operations, however. For this purpose a monitoring view and alerting features in the SAP HANA statistics server are provided (see sections Monitoring the Activation Process of In-Memory DataStore Objects in SAP HANA and Setup Email Alerting for the Activation Process of In-Memory DataStore Objects in SAP HANA).

3.6 Create a Process Chain for Regular Data Transfer

Once you perform any initial data loads, including delta initializations, you can create a process chain for extractions and loads at a regular interval, using the appropriate InfoPackages. This document does not provide explicit detail for the practice of creating process chains, please consult the BW documentation at http://help.sap.com/nw_platform <your SAP NetWeaver Platform version>

Application Help SAP Library <your language> SAP NetWeaver Business Warehouse, or consult colleagues who have knowledge of BW process chains for information on how to work with them. The following illustration gives an example of a process chain.



April 2012 23

If you have master data loads in your process chain, it will automatically add a change run process to follow. This is not necessary for DXC loads into the SAP HANA database; you can delete the ones automatically added to your process chain, and ignore any warnings about the change run.


24 April 2012

3.7 Monitoring the Activation Process of In-Memory DataStore Objects in SAP HANA

Most of the monitoring tasks are performed using the BW monitoring features in the embedded BW of the SAP Business Suite system (or in the attached BW in the “sidecar” scenario mentioned in section Appendix – DXC System Landscape Variants: The "Sidecar" Approach). InfoPackage monitoring and Process Chain monitoring covers nearly all of the processing steps involved in extracting data from the source system and loading it into the activation queue of the SAP HANA IMDSO. The only step that is not handled with this type of monitoring is the activation processing of the IMDSO. Since this action takes place solely inside SAP HANA, its monitoring is decoupled from the other processes which are driven from the BW S-API.

SAP HANA provides a monitoring view that holds the status of IMDSO activation. This view resides in the schema SYS; its technical name is M_EXTRACTORS. You can view status information in this table.


2. Expand the Catalog node, and then expand the SYS node.

3. Locate the M_EXTRACTORS view.

The view is displayed with its description first. To locate the view, search for the following description: Direct extractor connection (DXC) status information

(M_EXTRACTORS)

It might be easier to move the pane divider towards the right and look for the technical name M_EXTRACTORS.

4. Right-click the M_EXTRACTORS view, and select Open Content.

5. Look for the DataSource name which you want to monitor. The activation status table of the IMDSO is displayed in the Table Name column with the naming convention

/BIC/A<name of the DataSource>AO, for example /BIC/A0VER_SCARR_ATRAO.

6. Check the value in the Status column, successful activations have the value OK.

3.8 Setup Email Alerting for the Activation Process of In-Memory DataStore Objects in SAP HANA

The SAP HANA statistics server features altering for various aspects of operating the system; it includes an automatic email alerting mechanism to inform designated administrarors of issues arising within SAP HANA. The statistics server includes a feature where the records of the M_EXTRACTORS view are evaluated on a regular interval (once every 15 minutes) to check if any activations have failed. In the event of a failed activation, administrators can receive an email informing about the failure, so that appropriate corrective action can be taken.

To set up email alerting in case of failure of the activation of an IMDSO, proceed as follows:

1. In SAP HANA studio, change to the Administration perspective, and chose the Alerts tab.

2. Click the Configure Check Settings icon.

3. In the Configure Check Settings dialog, enter the appropriate values in the following fields:

o Sender Email Address


April 2012 25

o SMTP Server

o SMTP Port

Typically an email address is created in the company email system which is used for sending alerts for this pupose.

Please note, that these are general settings for all types of statistics server alerts in SAP HANA.

Normally you can skip the section Recipients Email Addess for All Checks (unless you want to get emails for any type of error condition in SAP HANA).

4. Click Configure Recipients for Specific Checks.

5. Select the checkbox for Check In-Memory DataStore Object Activation.

6. Click Add Recipients.

7. In the subsequent dialog, type in the email address of any administrators or specialists who should get an email in case an In-Memory DataStore Object activation fails.

8. Click OK, and then click OK in the Configure Check Settings dialog.

3.9 DXC and SAP HANA Data Modeling

For each DataSource represented in the example process chain, there is a corresponding In-Memory DataStore Object (IMDSO) that is loaded. In the SAP HANA database, several data modeling tasks have to be performed which include:

creating attribute views

analytical views

calculation views

The basis for data modeling is the active data tables. Remember, the naming convention of

the active table for the IMDSO is /BIC/A<name of the DataSource>00, for example

/BIC/A0VER_SCARR_ATR00. When creating SAP HANA data models simply utilize active

data tables of the relevant IMDSOs as base tables in data modeling.

3.10 Further Information

In the following sections you will find a few clarifying comments about further considerations.

Type of Data

It makes sense to consider the type of data the DataSource provides, in the context of your use case. The SAP HANA Direct Extractor Connection (DXC) is available for all SAP Business Content DataSources. There are a very small number of DataSources related to inventory data, however, which will pose challenges in working with an SAP HANA appliance, since the SAP HANA applicance does not have a concept like BW does of “non-cumulative key figures”. There are special features in BW designed for working with inventory data that are not available in SAP HANA natively. For example, a DataSource like 2LIS_03_BF (Material Movements data) is not well suited for use with DXC since it provides data that essentially requires the special features for inventory that BW provides. In such use cases (inventory data), we recommend working with BW itself instead of the SAP HANA appliance. Of course, BW on HANA offers its own set of benefits. For a list of DataSources not supported with DXC, please refer to SAP note 1710236.



26 April 2012

Also, some SAP Business Content DataSources do not provide delta handling (change data capture). This is not particularly problematic for DXC, but you should be aware that the In-Memory DataStore Object (IMDSO) that is generated by DXC does not include a change log, and therefore the IMDSO itself cannot generate delta datasets for use by another data mart in SAP HANA appliance (unlike in BW, no layering concept exists in SAP HANA appliance). While DXC certainly works with DataSources that do not have a delta mechanism, in some cases this may mean long-running extraction jobs transferring large datasets to the SAP HANA appliance. Any identical records will not be duplicated, and of course any new records will be added – but be aware that if you delete transactional records in the Business Suite system (in cases where the DataSource does not offer delta handling), the deletion will not propagate the deletion through to the IMDSO in the SAP HANA appliance.

DataSources Without Keys

One requirement for DXC is that DataSources or extract structures have a unique semantic key defined. This is important for DXC’s features in SAP HANA, since with the IMDSO, database tables are created where a primary key is necessary. If you try to activate a DataSource for DXC that does not have a key, you will get an error message. If you run into this issue, refer to SAP notes 1677278 and 1701750.

It is important to first apply SAP note 1701750 to any BW system that is connected to the source SAP Business Suite system you are working with before applying SAP note 1677278.

Conclusion

We encourage you to explore DXC’s value for a significant number of use cases. Its simplicity, as well its provision of foundational models from SAP Business Suite systems that offer semantically rich data in a straightforward manner, surely offers unique advantages for your SAP HANA project.






April 2012 27

4 Appendix – DXC System Landscape Variants: The “Sidecar” Approach

In this Installation and Configuration Guide we discussed the default configuration for DXC, in use with SAP Business Suite systems based on SAP NetWeaver 7.0 or higher. Again, this default configuration relies on the “embedded BW” which exists inside of SAP NetWeaver 7.0 or higher (e.g. ECC 6.0). However, in some cases, customers may be interested in implementing DXC with an SAP Business Suite system that is older, and therefore not based on SAP NetWeaver 7.0 or higher (e.g. 4.6C). Another use case might be that the “embedded BW” is already in use. As a consequence, the customer might be reluctant to use it for this purpose; also there may be some general preference to avoid the use of the embedded BW system on an SAP Business Suite system, even though it is primarily used for scheduling and monitoring of extraction jobs in that scenario.

In order to enable DXC when such conditions exist, DXC can be implemented with a “sidecar” approach. This means, that instead of using the “embedded BW” inside the SAP Business Suite system, a separate connected BW system can be used as an intermediary system for scheduling and managing the extraction job in the connected SAP Business Suite system, which sends the extracted data directly to SAP HANA. Extracted data will not be loaded into the connected SAP BW system; instead the data flow will be redirected to the SAP HANA system.

The following illustration depicts the basic “sidecar” approach.

Another similar variation is available to customers running “SAP NetWeaver BW Powered by SAP HANA” (aka BW on HANA). The following illustration depicts another variation of the “sidecar” approach.


28 April 2012

In either of the sidecar approaches illustrated here, the steps outlined to perform in the SAP Business Suite system (which are based on SAP note 1583403), must be performed in the “sidecar” BW system. In addition, SAP note 1688750 must be applied to the SAP Business Suite source system. This “sidecar” BW is used in very much the same way that the “embedded BW” is utilized in the default configuration; it simply performs the same function from a remote BW system.

If you decide to utilize the “sidecar” approach, the choices outlined in section Choose the System-Wide Setting for DataSources are particularly important. If this BW is used for any other purpose than DXC, then certainly with the “sidecar” approach you should use the setting DATASOURCE, and specify the particular DataSources that can be used with DXC.

When you choose to utilize a particular DataSource with DXC, you cannot use that DataSource for normal BW operations in the “sidecar” BW system. In other words, the use of a particular DataSource with DXC in the “sidecar” approach is a “binary” decision: Either a DataSource can be used with DXC or it can be used in the normal manner to load data into the “sidecar” BW system – it cannot be used for both purposes.



References

April 2012 29

5 References

List of SAP Notes

The following table lists all SAP Notes mentioned in this Installation and Configuration Guide.

SAP Note Number Title Description

1583403 Direct extractor connection to SAP HANA

Gives instructions on how to connect your ERP system to an SAP HANA database.

1670518 SAP HANA Direct Extractor Connection: Monitoring

Provides information on how to monitor SAP HANA Direct Extractor Connection (DXC), in particular the activation processing for In-Memory DataStore Objects (IMDSOs).

1688750 DataSource: Reading a property in the source system

Apply this note to the source SAP Business Suite system only if you have the “sidecar” scenario described in section Appendix – DXC System Landscape Variants: The “Sidecar” Approach.

1701750 DataSource: Secondary Index on the PSA

If your DataSource is missing a key, apply this note to any BW systems connected to the SAP Business Suite system you are using with DXC.

1677278 DataSource: Changing the Key Definition (A version)

Provides a report where you can define a semantic key for any DataSources that are missing keys. DataSources without keys will cause an error when you try to generate the In-Memory DataStore Object in SAP HANA.

Before applying this not to your SAP Business Suite system, first apply SAP note 1701750 to any BW systems connected to the SAP Business Suite system you are using with DXC.

1710236 SAP HANA DXC: DataSource Restrictions

Lists specific DataSources not supported by DXC.

1714852 Troubleshooting SAP HANA DXC issues

Guidance for troubleshooting DXC issues and the appropriate action to take.

1665553 Handling issues with IMDSO activation – SAP HANA DXC

Discusses how to report issues with In-Memory DataStore Object activation to SAP.

1714933 DXC: Partitioning In-Memory DSO tables

Provides information about partitioning active data tables of IMDSOs where large data volume is expected.











References

30 April 2012

© Copyright 2012 SAP AG. All rights reserved

SAP Library document classification: PUBLIC

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, PowerPoint,

Silverlight, and Visual Studio 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, z10, z/VM,

z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power

Systems, POWER7, POWER6+, POWER6, POWER, PowerHA,

pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV,

GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2,

AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter

Planet are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the United

States and other countries. Adobe, the Adobe logo, Acrobat,

PostScript, and Reader are trademarks or registered trademarks of

Adobe Systems Incorporated in the United States and other countries.

Oracle and Java are registered trademarks of Oracle and its affiliates.

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. Apple, App Store,

iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C,

Retina, Safari, Siri, and Xcode are trademarks or registered trademarks

of Apple Inc. IOS is a registered trademark of Cisco Systems Inc.

RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold,

BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry

Storm2, BlackBerry PlayBook, and BlackBerry App World are

trademarks or registered trademarks of Research in Motion Limited.

Google App Engine, Google Apps, Google Checkout, Google Data

API, Google Maps, Google Mobile Ads, Google Mobile Updater,

Google Mobile, Google Store, Google Sync, Google Updater, Google

Voice, Google Mail, Gmail, YouTube, Dalvik and Android are

trademarks or registered trademarks of Google Inc. INTERMEC is a

registered trademark of Intermec Technologies Corporation. Wi-Fi is a

registered trademark of Wi-Fi Alliance. Bluetooth is a registered

trademark of Bluetooth SIG Inc. Motorola is a registered trademark of

Motorola Trademark Holdings LLC. Computop is a registered

trademark of Computop Wirtschaftsinformatik GmbH. 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. Crossgate, m@gic EDDY, B2B 360°, and B2B 360°

Services are registered trademarks of Crossgate AG in Germany and

other countries. Crossgate 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.

Disclaimer

Some components of this product are based on Java™. Any code

change in these components may cause unpredictable and severe

malfunctions and is therefore expressively prohibited, as is any

decompilation of these components.

Any Java™ Source Code delivered with this product is only to be used

by SAP’s Support Services and may not be modified or altered in any

way.

Documentation in the SAP Service Marketplace

You can find this documentation at the following Internet address:

service.sap.com/instguides

SAP AG

Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 24 F +49/18 05/34 34 20 www.sap.com

SAP AG


SAP AG


Typographic Conventions

Type Style Represents

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, names of variables and parameters, source code as well as names of installation, upgrade and database tools.

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.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such

as F2) or the ENTER key.

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Extractor-Based Data Acquisition by SAP HANA Direct Extractor (1)

Documents

inmemory datastore object

memory datastore object

memory datastore objects

green light showing

large data volume

delivery unit archive

psa to hdb entry object

data warehousing workbench