1.

1 Data Replication Using ABAP Report

The ABAP report Replicate Business Data for Advanced Compliance Reporting Service (report ID
RPACRS_BUS_DATA_REPLICATION) enables you to replicate transactional, configuration, and master
data from your SAP ERP systems to the HANA database on SAP Cloud Platform (SCP). Since data
replication using Smart Data Integration is not supported for SAP ERP’s EHP5 and lower releases, this
report provides a mechanism to replicate data and track replication status. The report calls the
uploadData REST API described on the Reporting Service help portal to replicate data.
You need to be assigned to the ACRS Data Administrators group on SCP to be able to replicate data
using this report.
Data replication using this report involves the following steps:
1. Creating RFC Destination to connect with SCP
2. Mapping RFC destination to source system
3. Maintaining data extraction parameters and their values
4. Replicating data using the report
All these steps are performed in your SAP ERP system.
If you wish to test data replication before you replicate data in your production system, you can first
create an RFC destination for your test account, complete the customizing activities for data replication,
and replicate data to your test account. After verifying that everything is working fine, you can repeat
the process for your production account.
For more information on replicating data using ABAP report, see SAP Note 2602411: Integration of SAP
ECC to SLH-ACR using API.
1.1.1 Creating RFC Destination
Follow the steps given below to create an RFC destination to connect to SAP Cloud Platform:
1. Run transaction sm59.
2. On the Configuration of RFC Connections page, select HTTP Connections to External Server and click

the create icon .

3. On the RFC Destination page, specify a name for the RFC connection in the RFC Destination field.
4. Select Connection Type as G.
5. On the Technical Settings tab, specify the Target Host value. Contact your SAP support team to know
the target host value. This value is different for test accounts and production accounts.
6. Specify the path prefix value
as/acrsmanagedatacore/dashboard/api/v1/uploadData?reportGroupID=VAT&
businessUnitID=FIN.
7. On the Logon & Security tab, specify your user ID and password for SCP.
Note: To successfully connect to the RFC destination and replicate data, your SCP user ID needs to
be assigned to the ACRS Data Administrator group.
8. Save the new RFC connection.
9. Click Connection Test to test the connection.
10. In case the connection fails, do the following:
o If the error message ICM_HTTP_CONNECTION_BLOCKED is displayed:
 1. Download the ssl certificate and update it in your SAP ERP system using transaction
STRUST. For information on how to download the ssl certificate, see
https://help.sap.com/viewer/d5ee677b372b46019a546e19aa205b4b/1.0.11/enUS/14114d
befe184930afa8a08387b89cc6.html.
2. Raise a DLM incident with component DEV-ERP-TECH to upload these certificates in the SCP.
3. After the certificates are uploaded, recheck whether the connection is working by clicking
Connection Test.
o If the error message ICM_HTTP_CONNECTION_FAILED is displayed:
1. In transaction sm59, under HTTP Connections to External Server, choose the RFC
connection.
2. On the Technical Settings tab, in the HTTP Proxy Options section, specify the Proxy Host as
proxy and Proxy Service as 8080.
3. Save the changes and click Connection Test to test the RFC connection again.
When the RFC connection is successful, your SAP ERP system can use it to connect to and replicate data
to the HANA database on SAP Cloud Platform.

1.1.2 Mapping RFC Destination to Source System

When data from different SAP ERP systems is exported to the HANA database on SCP, there needs to be
a way to identify the source system from which each data set is exported.
To achieve this, you need to maintain your SAP system ID, RFC connection name, and RFC destination
identifier using the customizing view V_GLO_ACRS_SNAME. Specify the usage type as data replication.

1.1.3 Maintaining Parameter Values for Data Extraction

For each report category, different extractors need to be used to replicate relevant business data from
your SAP ERP system to the HANA database on SCP. For transaction data extractors, you need to specify
values for parameters; for example, you need to specify company code and fiscal period for extracting
tax line items data. Replication tasks are created for extractors and data is replicated from the SAP ERP
system to the HANA database on SCP based on the parameter values you specify.
Follow the steps given below to maintain parameter values for extractors:
1. Using transaction sm34, open the customizing view cluster ACRSVC_CUST_CONFIG.
2. Select the report category for which you want to replicate data.
3. Select the RFC destination to which you want to replicate data.
4. Click Continue.
Relevant extractors are automatically added, their replication tasks are created, and these details
are displayed on the Relevant Extractors view.
5. On the Relevant Extractors view , select a transaction data extractor from the list and click
Parameter Values.
6. Verify the RFC destination, extraction model, and extractor name, and click Continue.
7. Switch to edit mode and press F4 to select parameters for the extractor.
8. Select a parameter from the list and press Enter.
The parameter group and type are updated automatically.
9. For parameters of type EQ, specify the value in the Low Value column.
For parameters of type BT, specify the value range using the Low Value and High Value columns.
For example, for BUKRS (company code), specify the company code value in the Low Value column,
whereas for FISCPER (fiscal period), specify the fiscal period range using the Low Value and High
Value columns.
10. Save your changes.
Replication tasks are created for the extractors. If you specify multiple parameter values for an
extractor, multiple replication tasks are created for it.
11. To view the replication tasks created for extractors, on the Relevant Extractors view, select all
extractors and click Replication Tasks.

In the example below, data replication for extractor 0FI_GL_4 will take place for company codes 1210
and 1410, and for fiscal periods January 1, 2018, to December 31, 9999. Two replication tasks will be
created for this extractor – one for each company code.

Parameter Group Parameter Name OP Low Value High Value

1 BUKRS EQ 1210

1 FISCPER BT 20180101 99991231

2 BUKRS EQ 1410

2 FISCPER BT 20180101 99991231

1.1.4 Replicating Data Using ABAP Report

After you complete the first three set up and customizing activities required for replicating data, you can
run the Replicate Business Data for Advanced Compliance Reporting Service report (report ID
RPACRS_BUS_DATA_REPLICATION) in your SAP ERP system to start data replication.
Follow the steps given below to run the report and track data replication:
1. Run transaction dr_acrs or in transaction se38, specify the report name
RPACRS_BUS_DATA_REPLICATION to open the Replicate Business Data for Advanced Compliance
Reporting Service report.
2. Specify the RFC destination in the RFC Destination field.
3. Choose the report category for which you wish to replicate data.
4. Select the extraction type if you want to replicate only transaction data, or master data, or
configuration data. If you do not select an extraction type, all three types of data is replicated.
5. Select one or more replication task IDs if you want to replicate data only using the corresponding
extractors.
6. Specify the maximum data package size in megabytes. Since the size of data to be replicated can be
large, for efficient data replication, it is recommended to divide the data into batches of size up to
50 MB.
7. If you want to run this report in recovery mode, select the Recovery Run check box. In recovery
mode, the report replicates data only for the packages or extractors for which it encountered an
error in the previous report run. In this case, do not select any extraction type of replication task ID.
8. Click Execute.
 The report starts replicating data for the report category based on the configurations you have
made.
When you execute this report, it builds REST APIs containing data from database tables relevant for the
selected report category and sends these APIs to the SCP. Based on the maximum package size
specified, data is split into multiple packages.
When data replication is complete, replication status is displayed as the report output. The upper area
of the output screen displays a list of replication runs. Double-click the replication run to view the
replication status for each replication task. A replication task is created for each value you specify for the
leading parameter of each extractor. For example, if you configure two company codes for extractor
0FI_GL_4, then two replication tasks are created for it.
You can also track replication status using the Collect Report Data app. The External ID and Extraction
Package values displayed in the report’s output are displayed as the Upload ID and File ID respectively
in the Collect Report Data app.
As this report generally takes a long time to replicate data, you can schedule this report to run on a
periodic basis and later view the report output using transaction DR_ACRS_APP_LOD_DISP, by
specifying the object value as ACRS.