0001583403- Direct Extractor Connection to SAP HANA

SAP Note

Header Data

Symptom

You want to connect your ERP system to an SAP HANA (peer-to-peer) system and extract SAP Business Content DataSources or customer-specific DataSources to the SAP HANA system.

Other Terms

Reason and Prerequisites

This is a special development.

Solution

Provided that you do not have to implement this SAP Note as a prerequisite for another, we would like to point out that this is a special development that you require only if you want to send data from your ERP system to a remote SAP HANA database. Implement the correction instructions of this SAP Note using transaction SNOTE (even if you have a newer support package level installed on your system this current SAP Note may contain corrections for the DXC feature). Read the guide that is mentioned in SAP Note 1665602 to configure the SAP HANA database accordingly. In the ERP system, activate the feature as follows:

1. In transaction SM59, create an HTTP destination of the type G (external system). Enter the target host and port of your remote SAP HANA database and also enter the following path prefix:

a) For SAP HANA Revisions 20 and 21: "/dec".

b) As of HANA Revision 22: "/dec/dec.xscfunc".

c) As of HANA Revision 25: "/dxc/dxc.xscfunc".

d) As of HANA Revision 35: "/sap/hana/dxc/dxc.xscfunc".

On the logon and security tab page, choose "Basic Authentication" and enter the user and password.

2. Execute the program SAP_RSADMIN_MAINTAIN and create the entry Object = PSA_TO_HDB_DESTINATION/Value = . Ensure that you use upper and lower case letters correctly.

3. Create an additional entry Object = PSA_TO_HDB

You have three options for the value:

GLOBAL

In this case, all DataSources (that you load in the embedded BW of the current system; there is more information about this below) are replicated to the external in-memory database.In the current system, you can no longer carry out additional BW processes or reports. However, you can still replicate to other remote BW systems.

SYSTEM

In this case, you can specify the clients that you want to be replicated to the external SAP HANA database. The remaining clients are replicated to the PSA. For each client from which data is to be replicated to the SAP HANA database, create an additional entry with the program SAP_RSADMIN_MAINTAIN, namely Object = PSA_TO_HDB_, Value = X.

DATASOURCE

In this case, you can specify the DataSources that you want to be replicated to the external SAP HANA database. The remaining DataSources are replicated to the PSA. For this, use transaction SE11 to create a customer-specific database table with

1583403 - Direct extractor connection to SAP HANA

Version 36 Validity: 29.08.2014 - active Language English

Released On 29.08.2014 14:13:55 Release Status Released for Customer Component BW-WHM-DST Data Staging Priority Recommendations / Additional Info Category Special development

the following fields (both fields are key fields): DATASOURCE TYPE ROOSOURCER LOGSYS TYPE RSSLOGSYS Allow table maintenance for the table (or generate a maintenance view) because this makes sense. Activate the table. Create an additional entry with the program SAP_RSADMIN_MAINTAIN, namely Object = PSA_TO_HDB_DATASOURCETABLE, Value = . Enter the DataSources that you want to replicate to the SAP HANA database into your table.

4. With this function, tables in which the data is stored are generated in the SAP HANA database for each DataSource. By default, the system tries to create the tables in one schema that has the same name as the master data ID (SID) of the ERP system. You extract the data from this schema. If this schema does not exist, you can create an additional entry in the table RSADMIN, namely Object = PSA_TO_HDB_SCHEMA / Value = . In addition, ensure that the user that you have entered in the HTTP destination is the owner of the selected schema.

5. Become familiar with the use of a BW; study the documentation or online help for data retrieval in BW if you are not already familiar with this.

6. In transaction RSA5, install the SAP DataSources whose data you want to replicate if these are not already activated, or create customer-specific DataSources in transaction RSO2.

7. Call transaction RSA1.Note that as a result, the embedded BW is configured as initial and you can no longer use transaction RSA1 and other BW functions in another client. In particular, this is important regarding organizational considerations (which user in which client should administer the replication?).

8. If the data to be replicated comes from the current client, use the myself source system. Otherwise, create a special system for each client to be extracted.

9. In transaction RSA1, execute the metadata replication of the DataSources as 7.x DataSources (type RSDS) for the source system and then activate them. As a result, an in-memory DataStore object is created with the name of the DataSource in the remote SAP HANA database. Specifically, several tables are created with the naming convention /BIC/A[DataSource][xx], where [xx] is a two-digit number.00 is the active table that you can use for reporting; 40 is the activation queue into which the BW writes the data.

Only one common DataStore object is created for all source systems from which the relevant DataSource is loaded.Therefore, the client of the source system is added to the DataStore object as an additional column if it is not already displayed in the metadata of the DataSource.

Consult the documentation of the SAP HANA database about structuring and administering a DataStore object in preparation for later report modeling (for example, report only for the active data of the DataStore object since this makes sense) and administration.

10. Create an InfoPackage for the DataSource and start this.Full InfoPackages and delta InfoPackages are possible. Managing the data in the remote DataStore object corresponds to the maintenance of the PSA for the DataSource; this means that the data requests are displayed as updated in the PSA; however, they actually only exist in the remote SAP HANA database. Therefore, deleting requests from the PSA leads to requests being deleted from the remote DataStore object. If required, consult the relevant BW documentation.

11. The activation of the data in the DataStore object (the same way as for a DataStore object in BW), that is, copying and merging the data from the table with the suffix 40 to the table with the suffix 00, is automatically triggered when the load request is successfully completed. However, become familiar with the administration process of this activation process directly in the remote SAP HANA database.

12. Note: Due to the equalization PSA = DataStore object, each request must be successful or not available at all in the DataStore object before an additional request can be requested.Otherwise, there are errors during the activation of data in the DataStore object. Therefore, always avoid the QM action "green" for partially-updated requests

13. In addition, green requests cannot be activated in the DataStore if there are still red requests with a smaller request number in the same DataStore. Therefore, delete incorrect requests that cannot be repaired from the PSA = DataStore in PSA maintenance before you request new data.

Before you implement the correction instructions, you must first read Note 875986, which provides information about transaction SNOTE.

------------------------------------------------------------------------ |Manual Pre-Implement. | ------------------------------------------------------------------------ |VALID FOR | |Software Component SAP_BWBusiness Inform...| | Release 700SAPKW70021 - SAPKW70027 | | Release 701SAPKW70104 - SAPKW70110 | | Release 702SAPKW70201 - SAPKW70209 | | Release 731Until SAPKW73101| | Release 730SAPKW73001 - SAPKW73005 | ------------------------------------------------------------------------

l Call transaction SE91 and create message 236 in the message class RSDS with the following short text:

Data package &1 saved to remote SAP HANA DB

l In transaction SAAB, create the checkpoint group RSDS_HDB_PUSH with the short text "Trace CL_RSDS_HDB_PUSH=>SEND".

------------------------------------------------------------------------ |Manual Pre-Implement. | ------------------------------------------------------------------------ |VALID FOR | |Software Component SAP_BWBusiness Inform...| | Release 700SAPKW70021 - SAPKW70027 | | Release 701SAPKW70104 - SAPKW70110 | | Release 702SAPKW70201 - SAPKW70209 | | Release 731Until SAPKW73101| | Release 730SAPKW73001 - SAPKW73004 | ------------------------------------------------------------------------

l In transaction SE91, create the following messages in the message class RSDS.

600: Error & 1 occurred during HTTP call for destination &2 (see long text)

Long text:

During the creation of an HTTP communication, error &V1& occurred

indicating the following:

1: argument_not_found

2: destination_not_found

3: destination_no_authority

4: plugin_not_active

5: internal_error

6: OTHERS. .

601: Error &1 occurred during HTTP communication to & 2 (see long text)

Long text:

During communication, erroroccurred indicating the following:

1: http_communication_failure

2: http_invalid_state

3: http_processing_failed

4: http_invalid_timeout

5: OTHERS

602: Error in the HANA DB system: &1 &2 &3 & 4

603: Send confirmation to SAP HANA database system

604: Confirmation sent successfully to SAP HANA database system

605: Implement SAP Note 1688750 in source system &1.

l In transaction SAAB, create the checkpoint group RSDS_HDB_PUSH.

Validity

Correction Instructions

Software Component From Rel. To Rel. And Subsequent

SAP_BW 700 702

711 730

731 731

740 740

SAP_BW_VIRTUAL_COMP 701 701

711 711

Correction Instructions

Causes - Side Effects

Support Packages & Patches

Software Component Valid from Valid to Number

SAP_BW 700 731 1071274

SAP_BW 700 731 1073987

SAP_BW 700 731 1160865

SAP_BW 700 740 1193704

SAP_BW 700 740 1254511

SAP_BW 700 731 1453539

SAP_BW 700 700 1453686

SAP_BW 700 731 1465861

SAP_BW 700 731 1479129

SAP_BW 700 731 1493682

SAP_BW 700 731 1501594

SAP_BW 700 740 1608555

SAP_BW 700 740 1755515

SAP_BW 700 702 1798579

SAP_BW 700 702 1798581

SAP_BW 700 731 1070323

SAP_BW 700 731 1052358

SAP_BW 700 702 1043155

SAP_BW 700 702 1026094

SAP_BW 700 702 1019473

SAP_BW 700 731 1025099

SAP_BW 700 701 1019559

SAP_BW 700 731 1024471

SAP_BW 700 731 1024311

SAP_BW 700 731 1022585

SAP_BW 701 701 1453685

SAP_BW 702 702 1021755

SAP_BW 730 730 1019558

SAP_BW 730 730 1019557

SAP_BW 730 730 1019556

SAP_BW 730 740 1798526

SAP_BW 730 731 1043154

SAP_BW 730 731 1011519

SAP_BW 731 731 1381172

SAP_BW 740 740 1254510

Notes / Patches corrected with this note

Note Reason From Version To Version Note Solution Version Support Package The table does not contain any entries

The following SAP Notes correct this Note / Patch

Note Reason From Version To Version Note Solution Version Support Package

1583403 0 0 1769444 1 1583403 0 0 2099622 1

Support Packages

Software Component Release Support Package

SAP_BW_VIRTUAL_COMP 701 SAPK-70129INVCBWTECH

701 SAPK-70130INVCBWTECH









SAP_BW 700 SAPKW70034

700 SAPKW70028

700 SAPKW70028

References

This document refers to:

SAP Notes

700 SAPKW70034

700 SAPKW70029

700 SAPKW70029

700 SAPKW70032

700 SAPKW70030

700 SAPKW70030

700 SAPKW70031

700 SAPKW70031

700 SAPKW70028

700 SAPKW70029

700 SAPKW70030

701 SAPKW70112

701 SAPKW70112

701 SAPKW70113

701 SAPKW70112

701 SAPKW70113

701 SAPKW70111

701 SAPKW70113

701 SAPKW70113

701 SAPKW70111

701 SAPKW70117

701 SAPKW70111

701 SAPKW70117

701 SAPKW70115

701 SAPKW70114

702 SAPKW70213

702 SAPKW70210

702 SAPKW70214

702 SAPKW70215

702 SAPKW70212

702 SAPKW70211

702 SAPKW70213

702 SAPKW70217

702 SAPKW70212

702 SAPKW70212

702 SAPKW70211

702 SAPKW70217

702 SAPKW70211

702 SAPKW70213

702 SAPKW70210

730 SAPKW73004

730 SAPKW73010

730 SAPKW73013

730 SAPKW73005

730 SAPKW73006

730 SAPKW73008

730 SAPKW73007

730 SAPKW73009

731 SAPKW73114

731 SAPKW73103

731 SAPKW73105

731 SAPKW73102

731 SAPKW73106

731 SAPKW73109

731 SAPKW73104

731 SAPKW73107

740 SAPKW74009

740 SAPKW74004

1688750 DataSource: Reading a property in the source system

This document is referenced by:

SAP Notes (9)

1677278 DataSource: Changing the key definition (A version) 1665602 Setup & Config: SAP HANA Direct Extractor Connection (DXC) 1665553 Handling issues with IMDSO activation - SAP HANA DXC 1581161 SAPBWNews NW BW 7.02 ABAP SP09 1567706 SAPBWNews NW7.0 BW ABAP Support Package 27 1510977 Prelimenary Version SAPBWNews NW BW 7.11 ABAP SP08 1419539 SAPBWNews NW BW 7.01 ABAP SP10

1567706 SAPBWNews NW7.0 BW ABAP Support Package 27 1581161 SAPBWNews NW BW 7.02 ABAP SP09 2148186 DXC Data Activation Fails: Could not find update operations for activation xx 1510977 Prelimenary Version SAPBWNews NW BW 7.11 ABAP SP08 1677278 DataSource: Changing the key definition (A version) 1688750 DataSource: Reading a property in the source system 1665553 Handling issues with IMDSO activation - SAP HANA DXC 1665602 Setup & Config: SAP HANA Direct Extractor Connection (DXC) 1419539 SAPBWNews NW BW 7.01 ABAP SP10

0001583403- Direct Extractor Connection to SAP HANA

Documents

Transcript of 0001583403- Direct Extractor Connection to SAP HANA