hana sp5 dxc inst en

PUBLICSAP HANA Appliance Software SPS 05Document Version: 1.0 - 2012-12-13

SAP HANA Direct Extractor Connection Implementation Guide

Table of Contents

1 Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.1 About this Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41.2 Related Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

1.2.1 Planning Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.2.2 Further Useful Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

1.3 Important SAP Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

2 Overview of the SAP HANA Direct Extractor Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82.1 Setup steps in SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2.1.1 Enabling SAP HANA XS and SAP Web Dispatcher Services. . . . . . . . . . . . . . . . . . . . . . . . . . 102.1.2 Setup of SAP HANA Direct Extractor Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

2.2 Delivery Unit Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.3 Application Server Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2.3.1 Restarting the SAP HANA XS Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.3.2 Testing the Setup of the DXC Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.3.3 Creating a DXC User in SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132.3.4 Creating a DXC Schema in SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.4 Setup Steps in the SAP Business Suite System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132.4.1 Create an HTTP Connection to the SAP HANA System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.4.2 Configure DXC HTTP Interface Destination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142.4.3 Choose the System-Wide Setting for DataSources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.4.4 Create and Populate a Table to Specify the DataSources Used by DXC. . . . . . . . . . . . . . . . . . 162.4.5 Indicate the Table Used to Specify the DataSources for Use with DXC. . . . . . . . . . . . . . . . . . .172.4.6 Designate the Schema in SAP HANA to Store IMDSOs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

3 Configuration Steps that Utilize BW Functionality to Enable DXC. . . . . . . . . . . . . . . . . . . . . . . . . 183.1 Install Business Content DataSources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.2 Replicate DataSources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

3.2.1 Create Source Systems for Clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.2.2 Verify the Creation of the In-Memory DataStore Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3.3 Create InfoPackages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.4 Monitor Data Load in the Source SAP Business Suite System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.5 Verifying Data Transfer in the SAP HANA Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213.6 Create a Process Chain for Regular Data Transfer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.7 Monitoring the Activation Process of In-Memory DataStore Objects in SAP HANA. . . . . . . . . . . . . . . . . 223.8 Setup Email Alerting for the Activation Process of In-Memory DataStore Objects in SAP HANA. . . . . . . 233.9 DXC and SAP HANA Data Modeling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

2P U B L I C 2012 SAP AG. All rights reserved.

SAP HANA Direct Extractor Connection Implementation GuideTable of Contents

3.10 Further Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

4 Appendix DXC System Landscape Variants: The Sidecar Approach. . . . . . . . . . . . . . . . . . . . 26

5 References. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

SAP HANA Direct Extractor Connection Implementation GuideTable of Contents

P U B L I C 2012 SAP AG. All rights reserved. 3

1 Getting Started

The SAP HANA Direct Extractor Connection (DXC) Implementation Guide provides information about setup and technical configuration of the SAP HANA Direct Extractor Connection (DXC). This guide also includes information about the basic operation of the SAP HANA Direct Extractor Connection, in particular the scheduling and monitoring of extraction and load.

1.1 About this Document

This implementation 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.

Note: 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 for 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 documentationThis implementation 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 ConnectionThis 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 WarehouseThis 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 ApproachThis section gives an overview of the sidecar approach, which covers the following use cases: 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). 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.


SAP HANA Direct Extractor Connection Implementation GuideGetting Started

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

Tip: 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

The following section gives an overview of documents covering planning topics and further useful links.

1.2.1 Planning InformationFor 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/

SAP HANA Administration Guide http://help.sap.com/hana > SAP HANA ApplianceAdministration 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/platformsTo 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 LinksThe 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

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 about 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 cause an error when you try to generate the In-Memory DataStore Object in SAP HANA.Before applying this note 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.



SAP Note Number Title Description

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.

1781102 SAP HANA DXC with BW 730 SP8 or higher

Provides additional information if you want to use SAP HANA Direct Extractor Connection (DXC) with an SAP BW 730 SP8 or higher system as part of the DXC system landscape architecture.



2 Overview of the SAP HANA Direct Extractor Connection

The SAP HANA Direct Extractor Connection (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 for SAP HANA. 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 the state of 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 purposes. 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 RationaleThe following key points sum up the rationale for the SAP HANA Direct Extractor Connection:

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

Significantly reduces complexity of data modeling tasks in SAP HANA Speeds up time lines for SAP HANA implementation projects

Provide semantically rich data from SAP Business Suite to SAP HANA: Ensures that data appropriately represents the state of business documents from ERP Application logic to give the data the appropriate contextual meaning is already built into many extractors

Simplicity/Low TCO: Re-uses existing proprietary extraction, transformation, and load mechanism built into SAP Business

Suite systems over a simple HTTP(S) connection to SAP HANA No additional server or application needed in system landscape

Change data capture (delta handling): Efficient data acquisition only bring new or changed data into SAP HANA DXC provides a mechanism to properly handle data from all delta processing types


SAP HANA Direct Extractor Connection Implementation GuideOverview of the SAP HANA Direct Extractor Connection

Default DXC Configuration for SAP Business SuiteDXC is available in the following 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 more 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.

In SAP HANA, an In-Memory DataStore Object (IMDSO) is generated, 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. In general terms, the extraction and load process is virtually the same as those used for extracting and loading SAP Business Warehouse you rely on InfoPackage scheduling, the data load monitor, process chains, and so on which are all well known from operating SAP Business Warehouse.

Note:

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.

2.1 Setup steps in SAP HANAThis section describes the following steps: Enabling XSEngine and ICM Service Setup of SAP HANA Direct Extractor Connection

2.1.1 Enabling SAP HANA XS and SAP Web Dispatcher ServicesEnsure that the following SAP HANA components are running:

SAP HANA Extended Application Services (SAP HANA XS)Process name: hdbxsengine; Service name: xsengine

The SAP Web Dispatcher serviceProcess name: sapwebdisp_hdb

If these services are not running, proceed as follows to enable them:1. Open the SAP HANA studio.2. Right-click your SAP HANA instance and select Administration from the context menu to open the

Administration Console 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.You change the configuration value for the host the system's master indexserver service resides on (from 0 to 1). The master indexserver service's host is displayed in the Landscape tab. Make sure you change the host configuration not the system configuration.

Note: The configuration settings for the DXC application should already be defined for the xsengine service on the master index server's host. Check that the settings are correct. If you need to manually set the configuration settings, make the changes only on the master index server's host. Do not



change the system setting (in the System screen area of the Change Configuration Value dialog box); only change the host setting of the master index servers host (in the Hosts screen area of the Change Configuration Value dialog box).

5. Choose 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.You change the configuration value for the host the system's master indexserver service resides on (from 0 to 1). The master indexserver service's host is displayed in the Landscape tab.

Note: Do not change the system setting (in the System screen area of the Change Configuration Value dialog box); only change the host setting of the master index servers host (in the Hosts screen area of the Change Configuration Value dialog box).

8. Choose Save to save the new value.

Check if SAP HANA XS is running by accessing the following URL:

http://:80

Where is the name of the host on which the SAP HANA system's master indexserver resides and is the instance number of the specified SAP HANA system.

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

If the SAP HANA XS and the SAP Web Dispatcher services are operational, you should see the following information displayed:

SAP XSEngine is up and running.

2.1.2 Setup of SAP HANA Direct Extractor ConnectionThe 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.2 Delivery Unit Import

Before importing the delivery unit, prepare the delivery unit archive for import. As of SPS5, the delivery unit is no longer downloaded from the SAP Service Marketplace; the delivery unit is included as non-automated content. After you apply SPS5, you can import the delivery unit from the following location on the installed system: /usr/sap/HDB/SYS/global/hdb/content.



Note: If it is not possible to access this server location, copy the delivery unit archive (HANA_DXC.tgz) to a folder on a client and import the delivery unit from there.

To import the delivery unit, do the following:1. Open the 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 SAP HANA Content node, choose Delivery Unit and choose 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 choose OK.

The status in the Object import simulation should display green lights.6. Keep the existing defaults (make sure Activate objects is checked), and choose 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.3 Application Server ConfigurationThe use of the DXC application has to be enabled with the SAP HANA Extended Application Services (SAP HANA XS) component of SAP HANA. To enable the DXC application, add an entry to the application server configuration, as follows:

Note: The configuration settings for the DXC application should already be defined for the xsengine service on the master index server's host. Check that the settings are correct. If you need to manually set the configuration settings, make the changes only on the master index server's host.

1. Open the SAP HANA studio and select the SAP HANA instance.2. Open the Administration Console 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 in the System screen area, enter libxsdxc.

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

6. Choose Save.

2.3.1 Restarting the SAP HANA XS ServerIf you encounter problems when setting up the DXC component, try restarting the SAP HANA XS server (xsengine service).1. In the Administration Console perspective of the SAP HANA studio, choose the Landscape tab.2. Right-click the xsengine service and select Stop.

The status light changes to yellow and then to red.



3. Right-click the xsengine service and select Start.

2.3.2 Testing the Setup of the DXC ApplicationTo check if the setup of the SAP HANA Direct Extractor Connection application is successful and works as expected, proceed as follows:

Check if DXC is operational. The DXC application should be accessible now by using the following URL:http://:80/sap/hana/dxc/dxc.xscfunc

Where is the name of the host on which the SAP HANA system's master indexserver resides and is the instance number of the specified SAP HANA system.

If the check is successful, you see a success message.

2.3.3 Creating a DXC User in SAP HANACreate 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 perform the following steps:1. Open the 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.7. Choose the green Deploy icon.

2.3.4 Creating a DXC Schema in SAP HANACreate a schema for use with the SAP HANA Direct Extractor Connection that is owned by the DXC user.

Note:

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

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

create schema owned by

Example:

create schema R3TSCHEMA owned by DXCUSER

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

2.4 Setup Steps in the SAP Business Suite SystemSetup in the SAP Business Suite comprises the following steps:



Apply SAP note 1583403 to the SAP Business Suite systemApply SAP note 1583403 using the transaction SNOTE. Note 1583403 adds the DXC functionality to the SAP Business Suite system. Note, too, that there are several manual steps that must be performed, as described in note 1583403. Steps 1 through 11 are described in detail in this document. However, be sure to perform the steps described in note 1583403 under the sections entitled Manual Pre-implement, which describe some steps to perform in transactions SE91 and SAAB.

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 ObjectsFor more information, refer to SAP note 1583403.

2.4.1 Create an HTTP Connection to the SAP HANA SystemIn 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

choose Create.2. Provide a name for the HTTP destination, for example DXC_HANA_CONNECTION_.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.

Tip: The port number is 80 of your SAP HANA database.

4. In the Path Prefix field, enter /sap/hana/dxc/dxc.xscfunc.5. On the Logon & Security tab, choose Basic Authentication and provide the user name and password of your

DXC user.6. Choose Save.

2.4.2 Configure DXC HTTP Interface DestinationCreate 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.

a) In the OBJECT field, enter the value PSA_TO_HDB_DESTINATION.b) In the VALUE field, enter the name of the HTTP destination you created, for example

DXC_HANA_CONNECTION_.

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



2. Choose Insert, and then choose Execute (F8) to create the table entry.

2.4.3 Choose the System-Wide Setting for DataSourcesIn 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 is located inside the SAP Business Suite system, unless you are using the sidecar approach discussed in section Appendix DXC System Landscape Variants: The Sidecar Approach.

Caution:

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 for some purpose other than DXC (or you might do so at some point in the future), the choice you make in this section is very important.

Embedded BWIf you are using the embedded BW, depending on the choices you make in this section, the embedded BW could potentially be completely disabled.

Remote BWIf you have a remote BW connected to this SAP Business Suite system, it will not be affected (no matter what choice you make in this section).

Tip:

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

1. Use transaction SA38 to execute the program SAP_RSADMIN_MAINTAIN.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: 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 embedded BW inside an SAP Business Suite system, which is very often not 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 described in section Appendix DXC System Landscape Variants: The Sidecar Approach).

SYSTEMOnly 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).

DATASOURCEOnly 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 choose Insert.

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

2.4.4 Create and Populate a Table to Specify the DataSources Used by DXCNote: The steps described in this section are only required if you choose the value DATASOURCE for the PSA_TO_HDB entry object.

Create a Customer-Specific Database TableIf 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.

a) In the Database Table field, enter a custom table name, for example ZDXCDATASOURCES.b) In the Short Description field, provide a description for the table, for example DataSources for DXC.

2. Choose 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:

a) In the Field column, enter the value DATASOURCE.b) Select the checkboxes in the Key and Initial Values columns.c) 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:

a) In the Field column, enter the value LOGSYS.b) Select the checkbox in the Key column. Do not select the checkbox in the Initial Values column.c) In the Data element column, enter the value RSSLOGSYS.

8. Press ENTER to apply the changes.9. Choose Save.

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

Tip: 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. Choose Technical Settings.



12. In the next screen, enter APPL2 in the Data Class field, and choose 0 in the Size category field.13. Choose Save and then choose the green circle with an arrow to return to the previous screen.14. Choose Activate to activate the table. Activation warnings can generally be ignored in this case.

Create Table Entries for Specific DataSourcesCreate table entries for the specific DataSources that you 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 choose Create.2. Enter the specific DataSource name and logical system name for the relevant client.

Tip: There is no value help drop-down here, so you need to know the exact technical name for the DataSource and logical system name, and enter them with the correct 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 use with DXC.

2.4.5 Indicate the Table Used to Specify the DataSources for Use with DXCNote:

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

1. Use transaction SA38 to execute the program SAP_RSADMIN_MAINTAIN.a) In the OBJECT field, enter the value PSA_TO_HDB_DATASOURCETABLE.b) 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. Choose Insert, and then choose Execute (F8).

2.4.6 Designate the Schema in SAP HANA to Store IMDSOsWithin 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:1. Use transaction SA38 to execute the program SAP_RSADMIN_MAINTAIN.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.



3 Configuration Steps that Utilize BW Functionality to Enable DXC

The default system landscape architecture for DXC involves the use of the embedded BW in the SAP Business Suite system (for solutions based on SAP NetWeaver 7.0 or higher). If you are working with this default system landscape architecture, follow the steps outlined in this section, which involves utilizing some parts of the embedded BW to enable DXC directly to SAP HANA. If you are working with the sidecar variation, refer to the appendix listed in the related links.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, we recommend that you work with someone who is familiar not only with DataSources but also with 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 using DXC. For further information about working with the various SAP BW concepts and tasks described in this guide, refer to the SAP BW documentation and online help at http://help.sap.com/nw_platform > Application Help SAP Library SAP NetWeaver Business Warehouse .In addition, if you are unsure which SAP Business Content DataSources you should work with, we recommend that you work with someone who has knowledge of the specific domain area.Related LinksAppendix DXC System Landscape Variants: The Sidecar Approach [page 26]

3.1 Install Business Content DataSources

To install Business Content DataSources proceed as follows:1. Use transaction RSA5 to start the Installation of DataSource from Business Content.2. Select the specific DataSource that you want to install and choose Activate DataSources.

3.2 Replicate DataSourcesThe next steps involve working in the BW Data Warehousing workbench (transaction RSA1).

Caution: Consider the client to use for the BW client carefully. Be aware that once you decide which client in your system is the BW client, the transaction RSA1 or other BW-related functions cannot be used in any other


SAP HANA Direct Extractor Connection Implementation GuideConfiguration Steps that Utilize BW Functionality to Enable DXC

client. It is very difficult to change to another client later, as once you execute transaction RSA1, many configurations are performed automatically.

3.2.1 Create Source Systems for ClientsIn 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 into the SAP HANA database. For further information about creating source systems for this purpose, refer to the SAP BW documentation and online help at http://help.sap.com/nw_platform > Application Help SAP Library 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, choose the Activate icon.

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

3.2.2 Verify the Creation of the In-Memory DataStore ObjectsYou can see the In-Memory DataStore Object in the Modeler perspective of the SAP HANA studio:1. Log on to the SAP HANA studio with the DXC user.2. In the Modeler 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: /BIC/A00

This is the active data table that stores all of the data that is 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, and so on.

/BIC/A40This 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 a proper sequence of records and ensures that all delta processing types (change data capture) are handled appropriately.

/BIC/A70, /BIC/A80, /BIC/AAO, etc.These are technical tables used to control the activation process.

Note: 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, refer to SAP note 1714933.



3.3 Create InfoPackagesIn 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 loadsOtherwise, if delta processing is not available, either create an InfoPackage for full load or create 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 choose Save.3. On the Schedule tab, select the appropriate time for the job to execute, and choose Start to schedule the

extraction job.

3.4 Monitor Data Load in the Source SAP Business Suite SystemAfter 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 choose the Monitor

icon.The Monitor - Administrator Workbench dialog appears.

2. Choose the Status tab to display detailed information about the data load.

Note: 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. Choose the Details tab to display detailed information about the records that have been transferred. You can navigate through the structure of the processed data packets:a) Look for Processing (Data Packets), and choose a data package.b) Expand the node Update PSA. You should see a message similar to the following example:

Data package 1 saved to remote SAP HANA DB

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

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



Note:

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

3.5 Verifying Data Transfer in the SAP HANA DatabaseYou can verify which data has been loaded into the SAP HANA database.1. Log on to the SAP HANA studio with the DXC user.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/A00, 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.When the data load activation is completed, all records from all the data packages 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/A00, 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. 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 TransferAfter 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, srefer to the SAP BW documentation and online help at http://help.sap.com/nw_platform > Application Help SAP Library

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.



Note: If you have master data loads in your process chain, it automatically adds 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.

3.7 Monitoring the Activation Process of In-Memory DataStore Objects in SAP HANAMost 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.1. Log on to the SAP HANA studio with the DXC user.2. Expand the Catalog node and then expand the SYS node.3. Locate the M_EXTRACTORS view.

Note: 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)

You can 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 that you want to monitor. The activation status table of the IMDSO is displayed

in the Table Name column with the naming convention /BIC/AAO, 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 HANAThe SAP HANA statistics server features alerting for various aspects of operating the system; it includes an automatic email alerting mechanism to inform designated administrators of issues arising within SAP HANA. The statistics server includes a feature where the records of the M_EXTRACTORS view are evaluated at 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 the the SAP HANA studio, change to the Administration Console perspective, and chose the Alerts tab.2. Choose the Configure Check Settings icon.3. In the Configure Check Settings dialog, enter the appropriate values in the following fields:

a) Sender Email Addressb) SMTP Serverc) SMTP PortTypically an email address is created in the company email system which is used for sending alerts for this purpose. These are general settings for all types of statistics server alerts in SAP HANA.

Tip:



Normally, you can skip the section Recipients Email Address for All Checks unless you want to receive emails notifying you of any type of error condition in SAP HANA.

4. Choose Configure Recipients for Specific Checks.5. Select the checkbox for Check In-Memory DataStore Object Activation.6. Choose Add Recipients.7. In the subsequent dialog, type in the email address of any administrators or specialists who should receive an

email in case an In-Memory DataStore Object activation fails.8. Choose OK and then choose OK in the Configure Check Settings dialog.

3.9 DXC and SAP HANA Data ModelingFor 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, for example: Creating attribute views Creating analytic views Creating calculation viewsThe basis for data modeling is the active data tables. Remember, the naming convention of the active table for the IMDSO is /BIC/A00, for example, /BIC/A0VER_SCARR_ATR00. When creating SAP HANA data models, utilize the active data tables of the relevant IMDSOs as base tables in data modeling.

3.10 Further InformationIn the following sections you will find a few clarifying comments about further considerations.

Type of DataWe recommend that you 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 pose challenges in working with an SAP HANA appliance, because the SAP HANA appliance 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 because 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 SAP HANA offers its own set of benefits. For a list of DataSources not supported with DXC, refer to SAP note 1710236.

In addition, 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 the SAP HANA appliance (unlike in BW, no layering concept exists in the SAP HANA appliance). Although DXC 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 are not duplicated and any new records are added. Remember that if you delete transactional records in the Business Suite system (in cases where the DataSource does not offer delta handling), the deletion does not propagate the deletion through to the IMDSO in the SAP HANA appliance.

DataSources Without KeysOne requirement for DXC is that DataSources or extract structures have a unique semantic key defined. This is important for DXCs features in SAP HANA, because 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 receive an error message. If you run into this issue, refer to SAP notes 1677278 and 1701750.

Caution:

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.

ConclusionWe recommend that you explore DXCs 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.



4 Appendix DXC System Landscape Variants: The Sidecar Approach

In this document we discuss the default configuration for DXC, which is available for SAP Business Suite systems based on SAP NetWeaver 7.0 or higher. This default configuration relies on the embedded BW which exists inside of SAP NetWeaver 7.0 or higher (for example, 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 (for example, 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. There might also 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 the DXC scenario.In order to enable DXC when such conditions exist, DXC can be implemented with the so-called sidecar approach. With the sidecar approach, 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 is not loaded into the connected SAP BW system; instead the data flow is 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 SAP HANA). The following illustration depicts another variation of the sidecar approach.


SAP HANA Direct Extractor Connection Implementation GuideAppendix DXC System Landscape Variants: The Sidecar Approach

In either of the sidecar approaches illustrated here, the steps to perform in the SAP Business Suite system must be performed in the sidecar BW system. SAP note 1583403 should be applied to the BW system using SNOTE; also make sure you follow the manual steps in this note as well, In addition, SAP note 1688750 must be applied to the SAP Business Suite source system. This sidecar BW is used in the same way that the embedded BW is utilized in the default configuration; it performs the same function from a remote BW system.If you proceed with this sidecar variation, the configuration steps described in the Install Business Content Datasources section of this document are performed in the SAP Business Suite system. The remaining configuration steps (from Replicate Datasources onwards) are performed in the BW sidecar system.

Caution: 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 with the sidecar approach you should use the setting DATASOURCE, and specify the particular DataSources that can be used with DXC.Caution: 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.

SAP HANA Direct Extractor Connection Implementation GuideAppendix DXC System Landscape Variants: The Sidecar Approach


5 References

For important information see: Important SAP Notes [page 6].


SAP HANA Direct Extractor Connection Implementation GuideReferences

www.sap.com/contactsap

2012 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 ads, 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 is a registered trademark of Oracle Corporation.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.Java is a registered trademark of Sun Microsystems, Inc.JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, 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 in several other countries all over the world. 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.

Table of Contents1 Getting Started1.1 About this Document1.2 Related Information1.2.1 Planning Information1.2.2 Further Useful Links

1.3 Important SAP Notes

2 Overview of the SAP HANA Direct Extractor Connection2.1 Setup steps in SAP HANA2.1.1 Enabling SAP HANA XS and SAP Web Dispatcher Services2.1.2 Setup of SAP HANA Direct Extractor Connection

2.2 Delivery Unit Import2.3 Application Server Configuration2.3.1 Restarting the SAP HANA XS Server2.3.2 Testing the Setup of the DXC Application2.3.3 Creating a DXC User in SAP HANA2.3.4 Creating a DXC Schema in SAP HANA

2.4 Setup Steps in the SAP Business Suite System2.4.1 Create an HTTP Connection to the SAP HANA System2.4.2 Configure DXC HTTP Interface Destination2.4.3 Choose the System-Wide Setting for DataSources2.4.4 Create and Populate a Table to Specify the DataSources Used by DXCCreate a Customer-Specific Database TableCreate Table Entries for Specific DataSources

2.4.5 Indicate the Table Used to Specify the DataSources for Use with DXC2.4.6 Designate the Schema in SAP HANA to Store IMDSOs

3 Configuration Steps that Utilize BW Functionality to Enable DXC3.1 Install Business Content DataSources3.2 Replicate DataSources3.2.1 Create Source Systems for Clients3.2.2 Verify the Creation of the In-Memory DataStore Objects

3.3 Create InfoPackages3.4 Monitor Data Load in the Source SAP Business Suite System3.5 Verifying Data Transfer in the SAP HANA Database3.6 Create a Process Chain for Regular Data Transfer3.7 Monitoring the Activation Process of In-Memory DataStore Objects in SAP HANA3.8 Setup Email Alerting for the Activation Process of In-Memory DataStore Objects in SAP HANA3.9 DXC and SAP HANA Data Modeling3.10 Further Information

Appendix DXC System Landscape Variants: The "Sidecar" Approach5 References

hana sp5 dxc inst en

Documents

sap hana system

sap hana database

sap ag

sap applicationsolution

sap hana xs server

important sap notes

sap service marketplace

sap hana data modeling242p