First-hand knowledge.

Reading Sample
This sample chapter introduces the architecture behind the replication of
data to an SAP BW or SAP BW/4HANA system and then offers a high-level
summary of the replication process. It discusses the various relevant authori-
zation objects and their significance. Subsequently, it walks readers step-by-
step through how to set up the replication process using SAP LT Replication
Server, SAP BW, or SAP BW/4HANA. Finally, it covers ways to react to planned
outage scenarios when replicating data.

“Loading and Replication to SAP BW

or SAP BW/4HANA”
Contents

Index

The Authors

Prathyusha Garimella, Shashidhar Garimella

SAP Landscape Transformation Replication Server

The Practical Guide

317 pages | 02/2024 | $89.95 | ISBN 978-1-4932-2525-5

www.sap-press.com/5821
 Chapter 3
Loading and Replication to 3
SAP BW or SAP BW/4HANA
Over the past few decades, with the proliferation of digital technologies,
IoT devices, and online platforms, the volume, velocity, and variety of
data have grown exponentially. With such data, however, it is import-
ant to react quickly, in real time, to give businesses the power to respond
to market conditions and customer needs. Real-time data is almost
always more lucrative. Organizations are aware that most data possess
a limited lifespan, so the quicker they can transform this data into
insights, the greater the value of such data will become.

SAP Business Warehouse (SAP BW) and SAP BW/4HANA play a crucial role in enhanc-
ing decision-making for businesses. They enable organizations to consolidate and
combine massive amounts of data from diverse sources, aiding in improved decision-
making. This centralized data repository provides a solid foundation for decision-
making, allowing stakeholders to access accurate and consistent information across
the enterprise. By structuring and storing data in SAP BW or SAP BW/4HANA, organi-
zations can run advanced analytics using tools like SAP Analytics Cloud, SAP Business-
Objects Business Intelligence tools, and non-SAP business intelligence tools to unlock
valuable insights, track trends, and predict future outcomes. With real-time data repli-
cation and extraction capabilities, SAP BW ensures that decision-makers have instant
access to valuable insights, enabling them to make informed and timely decisions.
However, the path to such real-time analytics is often not easy. Traditionally, SAP BW
users have faced an uphill battle to source data in real time in the first place, then parse
it through various stages of cleansing and transformations to make it to the reporting
layer. These challenges include the following:
쐍 Managing heaps of data is difficult as most organizations still rely on batch loads
that run periodically during periods of lower load on the system (e.g., nightly or
weekend loads).
쐍 Inefficient resource utilization occurs as most data extractors are custom built and
incapable of bringing delta (changed-only) data into SAP BW, thereby requiring full
loads. These loads are not only unnecessary but end up taking massive amounts of
storage, computing resources, and time.

67
3 Loading and Replication to SAP BW or SAP BW/4HANA 3.1 Architecture

SAP LT Replication Server can easily help address challenges such as these. Because SAP required to establish the connection successfully. Given its superior capabilities
LT Replication Server uses a trigger-based approach to capture changes (deltas), the over the former approach, this scenario is recommended for data replication in
data transfers no longer need to be full loads. This drastically reduces the volume com- most cases.
ing into an SAP BW or SAP BW/4HANA system as those loads that were earlier being 3
This chapter will introduce the architecture behind the replication to an SAP BW or SAP
introduced in full (because delta loads were not possible on these extractors) can now
BW/4HANA system, and then offer a high-level summary of the replication process. In
use delta records instead. Another advantage is SAP LT Replication Server’s support for
the later sections of this chapter, we will explore the various authorization objects and
both SAP and non-SAP systems. This could be a game changer to meet and realize most
their significance. Subsequently, we will look at how to set up the replication process
real-time analytic requirements in SAP BW and SAP BW/4HANA.
using SAP LT Replication Server, SAP BW, or SAP BW/4HANA. In addition, we will also
SAP LT Replication Server provides two distinct scenarios for replicating data, depend- look at ways to react to planned outage scenarios when replicating data.
ing on the release:
쐍 Replication to persistent staging area (SAP BW 7.00 or later, not applicable to Note
SAP BW/4HANA) Throughout this chapter, except where specifically noted, all references to SAP BW also
This option involves transferring data to the persistent staging area layer of SAP BW apply to SAP BW/4HANA.
using web service DataSources, which are then processed forward to the relevant
InfoProviders. It is important to note that this scenario exclusively supports trans-
parent tables and does not support pool or cluster tables.
3.1 Architecture
Warning! The ODP framework is available as a standard component of SAP NetWeaver 7.30 or
Note that this scenario was primarily aimed at customers on SAP BW 7.40 or earlier. later. The biggest advantage of using ODP over other mechanisms is its utility. The ODP
However, as of the time of writing this book, SAP BW 7.4 and older releases have framework not only provides a platform to perform the extraction and load using effi-
reached their end of mainstream maintenance. So this option, though it may still be cient delta handling but also offers a central storage location within the SAP landscape
available in select/rare SAP BW installations across the world, should not be considered for subsequent consumption by subscribers/consumers. As depicted in Figure 3.1, the
for any active development efforts. Hence, we strongly advise you to consider the ODP framework involves two aspects: providers and subscribers.
newer scenario utilizing operational data provisioning (ODP), detailed ahead. This
framework is discussed in greater detail in Section 3.1. The focus of this chapter will be
on the scenario using ODP, and not on the older one. Provider Subscriber/Consumer

쐍 Replication via ODP (for SAP BW releases greater than or equal to 7.40 and all SAP
SAP LT SAP Data
BW/4HANA versions) Replication Server Services
This option includes performing replication using the ODP framework that is inte-
grated with SAP LT Replication Server. This framework allows SAP LT Replication
SAP ERP Extractors Operational Data
Server to be a provider for ODP, enabling the storage of data from both connected Provisioning Target SAP BW
SAP systems and non-SAP systems. If you choose this approach to replicate data into
ODQ
SAP BW, you can load data directly to SAP BW InfoProviders using the data transfer SAP HANA Views
process, bypassing the persistent staging area layer completely. The delta handling
and associated functions are then taken over by the ODP infrastructure. For this sce- SAP S/4HANA
SAP BW Source
nario to function seamlessly, the source system must operate on a supported data- Embedded Analytics
base, with an SAP NetWeaver release of 620 or later. Older SAP source systems,
starting from version 4.6c, are supported as well, though manual setup steps are
Figure 3.1 ODP Architecture: Providers and Subscribers

68 69
3 Loading and Replication to SAP BW or SAP BW/4HANA 3.2 Overview of the Replication Process

The data from providers are written into central storage areas known as operational SAP LT Replication Server system. During the setup, a unique identifier, known as the
delta queues (ODQs). This data is propagated forward to other consumers, known as queue alias, is defined. In the target SAP BW system, a logical system of type ODP-SLT
subscribers. Queue is created, with the same unique identifier referred to as the ODP context in SAP
Data in an ODQ can be monitored centrally using Transaction ODQMON. This transac- BW. The subscribing SAP BW system connects to the SAP LT Replication Server system's 3
tion displays delta queues, a list of all providers and subscribers. The main advantage of ODP interface using this identifier to retrieve data from the correct source system.
the ODP framework is its extract once, deploy many concept. The data from the pro- Figure 3.2 illustrates the architecture of this replication scenario.
vider (SAP LT Replication Server, SAP ERP extractors, SAP HANA views, source SAP BW)
SAP LT Replication
is extracted only once and kept in the ODP layer. Consumers/subscribers (SAP Data Ser- Server Configuration Subscription to
ODP Context A
vices, target SAP BW, SAP S/4HANA embedded analytics) then fetch this data as needed. ODP Context A
SAP LT Replication Server SAP BW 7.30/7.40
This eliminates the system having to read from a source system multiple times and
RFC RFC
avoids the problem of clogging source system resources, which is a major concern for SAP System ODP Framework Info DSO
Connection Connection Cube
most users when attempting to load data from SAP ERP or SAP S/4HANA. In addition, ODQ
the data stored in ODP is highly compressed, as much as 90 percent, which alleviates
SAP BW/4HANA
Non-SAP Database ODQ RFC
storage concerns for SAP users. The data in the ODP system is kept until the last sub-
System Connection Connection
scriber has read the most recent data. The default retention period is 24 hours, but the aDSO
aDSO
SAP LT Replication
system offers the flexibility to define and change this period. Server Configuration
Subscription to
ODP Context B
ODP Context B
The main advantage of using SAP LT Replication Server to load to SAP BW is that you
can perform delta loads onto SAP BW DataSources that do not have delta mechanisms
available. While with native SAP BW you only get data from SAP systems and some Source SAP LT Replication Server Subscriber Type SAP BW

non-SAP/ETL sources, SAP LT Replication Server offers a much more robust and seam-
Figure 3.2 Setup of SAP LT Replication Server Replication to SAP BW
less integration, even with non-SAP systems. Only around a third (33 percent, approxi-
mately) of DataSources can deliver delta data; the rest must be fully loaded each time.
Upon SAP BW's request to replicate a source table, the initial data load is transferred
With the trigger technology of SAP LT Replication Server, all transparent tables are
from the source system to the ODQ, then to the SAP BW system. After this, the delta
enriched with delta capabilities, which decreases the amount of transferred data enor-
data is continuously transferred in real time from the source system to the ODQ, where
mously. This, combined with the ability to fetch delta data instantly and thus give
it awaits retrieval by the subscriber. Notably, if needed, data can be replicated without
instant access to new data, is a key differentiator and a driving factor to choose SAP LT
performing an initial load, and an initial load can be carried out during any subsequent
Replication Server to load data into SAP BW.
replication of data.
There are three possible setup options possible depending on your SAP BW or SAP
Note
BW/4HANA type, release, and support packages. Note that in this list, specifically, refer-
SAP LT Replication Server with SAP BW is not meant to be or seen as a replacement for ences to SAP BW only apply to SAP BW and not to SAP BW/4HANA:
standard extractors (SAPI based). It is usually recommended to use this mechanism for
scenarios with limited or low transformation logic (e.g., transparent tables). Traditional 쐍 Option 1
SAP-delivered extractors involve a high degree of transformation logic that has been Setup with scheduled data transfer process into SAP BW data targets possible with
developed and perfected by SAP over years and decades and cannot be replicated. SAP BW 7.30 SP 8 or higher. The mode of data injection into an SAP BW object is via a
Hence, it is recommended to use these extractors where available. scheduled data transfer process load, as depicted in Figure 3.3.
쐍 Option 2
Setup with data transfer process into SAP BW data targets and real-time data acqui-
sition (RDA) daemon possible with SAP BW 7.40 SP 5. The mode of data injection into
3.2 Overview of the Replication Process
an SAP BW object is via an RDA daemon with data transfer process load, as depicted
When loading to SAP BW via SAP LT Replication Server, the latter functions as the target in Figure 3.4.
configuration, where transferred data is persisted temporarily in the ODQ layer of the

70 71
3 Loading and Replication to SAP BW or SAP BW/4HANA 3.3 Authorizations

쐍 Option 3 On close observation, these three options only differ in the mode and frequency of the
Setup with data transfer process into advanced Data Store Objects (aDSOs) with delta data reaching the SAP BW destination object. With SAP BW/4HANA, the only sup-
streaming mode. Possible with SAP BW 7.5 SP 3 and any release of SAP BW/4HANA. ported options will be option 1 (with data targets as aDSOs only) or option 3.
The mode of data injection into an SAP BW object is with a data transfer process load 3
run in streaming mode, as depicted in Figure 3.5.
3.3 Authorizations

Real SAP LT Replication Server Data

SAP BW >=7.30 SP8 To successfully initialize and replicate data to SAP BW or SAP BW/4HANA, the users
Time Transfer
SAP System Process involved will need to be granted certain roles. The roles to be granted depend on the
ODP Framework
responsibilities expected to be carried out by the user. Because the process involves
DSO
Any Database replication, transferring data from one system to another, the security setup will need
ODQ Info
Real Cube to be performed in more than one system. This section will focus on the roles that need
Non-SAP Time ODQ
System
to be granted to the users in the SAP LT Replication Server system as well as the target
SAP BW or SAP BW/4HANA system. For information regarding the roles necessary in
Any Database Any Database Scheduled Any Database the source system, see Chapter 7, Section 7.3 and Section 7.4. Information regarding the
authorization objects as well as the corresponding fields involved will also be discussed
in depth in Chapter 7.
Figure 3.3 Setup of Replication in SAP BW: Scheduled Data Transfer Process Load
The different roles and authorizations needed in various systems involved in the repli-
cation are illustrated in Figure 3.6 and are as follows:

Real SAP LT Replication Server Data

SAP BW >=7.40 SP5
쐍 SAP_IUUC_REPL_ADMIN
Time Transfer
SAP System Process This role is relevant for SAP LT Replication Server system. Grant this role to the user
ODP Framework
who will need to create, display, or modify the configuration in the SAP LT Replica-
DSO
Any Database tion Server system in Transaction LTRC.
ODQ Info
Real Cube
Non-SAP Time ODQ
System

Any Database Any Database RDA Any Database

Daemon
SLT Admin
SAP BW USER
SAP_IUUC_REPL_ADMIN
SAP_IUUC_REPL_REMOTE
Figure 3.4 Setup of Replication in SAP BW: Data Transfer Process Load Using RDA Daemon SLT Display
SAP_IUUC_REPL_DISPLAY

RFC SAP LT RFC

RFC USER Connection Connection
SAP LT Replication Server Data Replication
Real SAP BW >=7.50 SP3 SAP_IUUC_REPL_REMOTE Server
Time Transfer
SAP System Process Any SAP BW/4HANA
ODP Framework RFC USER
SAP_IUUC_REPL_REMOTE
Any Database ODQ aDSO
Real aDSO
SAP Source SAP LT Replication Server SAP BW or SAP BW/4HANA
Non-SAP Time ODQ System System System
System

Any Database Any Database Streaming SAP HANA Database Figure 3.6 Authorizations in Various Systems Involving Replication to SAP BW or
Mode SAP BW/4HANA

Figure 3.5 Setup of Replication in SAP BW: Data Transfer Process Load Run in Streaming Mode

72 73
3 Loading and Replication to SAP BW or SAP BW/4HANA 3.4 Configuring the Replication Process

쐍 SAP_IUUC_REPL_DISPLAY 쐍 Managing loads in the target system:

This role is relevant for SAP LT Replication Server system. This role can be generated – Creating a logical system
and used to display configurations only; no action such as modification of existing
– Creating transfer objects
configurations or creation of new configurations is permitted with this role. This 3
– Creating an aDSO
role also does not allow changes to any other settings.
쐍 S_RS_RDEMO
This role is relevant in the SAP BW and/or SAP BW/4HANA system. This role is used 3.4.1 Creating a Configuration in SAP LT Replication Server
to configure and monitor the data provisioning process in the SAP BW system. The first step involved in replication to SAP BW or SAP BW/4HANA is the creation of a
쐍 SAP_IUUC_REPL_REMOTE configuration in SAP LT Replication Server. The following steps can be used to create
The data transfer process requires the use of RFC users with specific authorizations. this configuration:
To establish a connection from the source system to the SAP LT Replication Server
1. In Transaction LTRC, click the New Configuration icon, as highlighted in Figure 3.7.
system, an RFC connection needs to be created. This connection should utilize an
This will open a wizard titled Create Configuration.
RFC user with the SAP_IUUC_REPL_REMOTE role. If the RFC connection to the source or
target system points to the same system where the SAP LT Replication Server is
operating, a NONE connection can be used for this purpose. To do so, simply enter
“NONE” in the RFC Destination field.
쐍 SAP_IUUC_REPL_ADMIN_BW_ODQ
This role is relevant for the system in which the ODP framework will be used—that
is, the SAP LT Replication Server system. To enable the subscription from the SAP BW
system to the ODP framework, it is essential to use an RFC user with the SAP_IUUC_
REPL_ADMIN_BW_ODQ role. When configuring the logical system in SAP BW of type ODP-
SLT Queue, you will be prompted to provide a user for the callback connection,
which facilitates data transfer from ODP to SAP BW. The user used for this connec- Figure 3.7 New Configuration Creation
tion must have the S_BI-WHM_RFC and S_BI-WX_RFCA profiles assigned to it. These pro-
files are necessary to ensure a seamless and secure data transfer process between the 2. In this wizard, under the Specify General Data section, provide a Configuration
ODP framework and the SAP BW or SAP BW/4HANA system. Name and Description, as depicted in Figure 3.8, and click Next.

3.4 Configuring the Replication Process

In this section, we will look at the detailed steps involved in replication to SAP BW or
SAP BW/4HANA. We will look at how a table in the source system (ABAP-based) can be
loaded initially to an aDSO in SAP BW/4HANA. Then we will see how a new row added
to source system table is replicated into the aDSO in the target system. Note that
although these steps are listed for SAP BW/4HANA, the same steps are applicable also Figure 3.8 Configuration Name and Description
for SAP BW on SAP HANA.
3. In the Specify Source System section of the wizard, use the radio buttons shown in
The configuration steps can be categorized broadly into three sections:
Figure 3.9 to select whether the source system is ABAP-based or non-SAP-based. For
쐍 Creating a configuration in SAP LT Replication Server an ABAP-based source system, select the RFC Connection radio button. Select DB
쐍 Activating the ODP system Connection for a non-SAP source system and provide all necessary details for the
connection. For this example, select RFC Connection because we are using an SAP

74 75
3 Loading and Replication to SAP BW or SAP BW/4HANA 3.4 Configuring the Replication Process

source system. Provide the name of the RFC destination if one already exists. If an There are two options available for this setting: Performance Optimized and
RFC connection to the source does not exist or you want to create a new one regard- Resource Optimized. The Performance Optimized option is used to enhance the
less, use Transaction SM59 to do so. Your other options are as follows: speed of loading process while the Resource Optimized option is used in cases where
– Select the Allow Multiple Usage checkbox if this source system will be used in the source system and SAP LT Replication Server are in the same system. 3
multiple configurations. You can use a source system in up to four configura-
tions.
– Select the Read from Single Client option if you want to read data from only one
client as opposed to allowing reads from multiple SAP system clients.
Click Next when the setup of the source system details is complete.

Figure 3.9 Specify Source System

4. In the Specify Target System section of the wizard, use the radio buttons shown in Figure 3.11 Specify Transfer Settings
Figure 3.10 to select if the target system is RFC Connection based, DB Connection
based, or Other. This example involves replicating to an ODP context as the target Other important fields are as follows:
system, so select the Other radio button and choose Operational Data Provisioning – No. of Data Transfer Jobs
(ODP) from the Scenario for RFC Communication dropdown. Note that some earlier You can specify the number of jobs that are used for the data transfer process in
SAP systems use the ODP option in the RFC Connection radio button, so be sure to SAP LT Replication Server.
select the ODP option appropriately based on your SAP release. – No. of Initial Load Jobs
In the Queue Alias field, enter a six-digit alphanumeric identifier as shown in Figure You can specify the number of jobs that are used for the initial load in the SAP LT
3.10. The queue alias must be unique in the SAP LT Replication Server system and in Replication Server system.
the target SAP BW system, so choose this identifier with caution. This identifier will – No. of Calculation Jobs
be used as the ODP context. For reading types 1 and 3, this is the number of jobs used to calculate the data
transfer portions for the initial load. For reading types 4 and 5, it is the number of
jobs that transfer the portions to table DMC_INDXCL.
Click Next when the settings are complete.
6. On the Review and Create page of the wizard, you can check all the settings that have
been inputted into the wizard so far. Click Create to finish the setup and create the
configuration.

Figure 3.10 Specify Target System This concludes the steps involved to create a new configuration. Upon successful cre-
ation of the configuration, it should be added to the list of all available configurations
5. Next, the Specify Transfer Settings page appears in the wizard, as shown in Figure in the home page of Transaction LTRC.
3.11. Under Data Transfer Settings, select the appropriate Initial Load Mode option.

76 77
3 Loading and Replication to SAP BW or SAP BW/4HANA 3.4 Configuring the Replication Process

This ensures the configuration is ready to be used in the context of ODP usage. The
recipient SAP BW system, also known as the subscriber SAP BW system, takes the lead
for this replication and handles the orchestration of the load. The exact table or selec-
tion of tables that are to be replicated can only be defined in the SAP BW system. How- 3
ever, Transaction LTRC can still be used for debugging, monitoring, and other
troubleshooting purposes. The transformation and data transfer process can be used to
specify how the data is written to SAP BW and with what frequency.
With this step complete, the next few sections involve the creation of the receiving arti-
facts in the subscriber SAP BW system.
Figure 3.12 Configuration Creation Successful
3.4.3 Creating a Logical System in SAP BW
You should also see a Configuration <Configuration_Name> Created message, as
Creation of a logical system can be done in Transaction RSA1 in traditional SAP BW or
shown in Figure 3.12.
via SAP BW modeling tools in Eclipse. Due to the increasing number of innovations
happening in SAP BW modeling tools and most functionality being deprecated in tra-
3.4.2 Activating ODP Usage for SAP LT Replication Server ditional SAP BW screens such as Transaction RSA1 in order to replace them with their
Executing the ODP/ODQ replication scenario in the context of SAP LT Replication counterparts in the modeling tools, this section will focus on content creation in the
Server requires the activation of a specific, active Business Add-In (BAdI) implementa- modeling tools via Eclipse. However, for older SAP BW systems, these steps can be per-
tion. This step is only necessary for the first SAP LT Replication Server configuration formed in SAP GUI screens as well.
instance that uses ODP infrastructure. To activate the BAdI, click Configuration in the In the SAP BW modeling tools, after adding the SAP BW project and mapping the
home screen and navigate to the Expert Functions tab, then scroll down to the ODP/ respective SAP BW system, navigate to [Project] • Data Sources. From the context menu
ODQ Specific Functions section and select the Activate/Deactivate BAdI Implementa- of [ODP_SLT] ODP-SLT Queue, select New • Source System, as shown in Figure 3.14.
tion option, as depicted in Figure 3.13.

Figure 3.14 New Source System in SAP BW Modeling Tools

This opens up the wizard to create a new logical system. Finish the creation of the
source system. Ensure that you choose the ODP option during the creation of this sys-
tem. An important point to note here is that this source system should match the tar-
get system (ODP) mentioned in the SAP LT Replication Server configuration. Hence, the
Figure 3.13 Activate/Deactivate BAdI Implementation RFC connection to this system should be created in parallel with or prior to defining the

78 79
3 Loading and Replication to SAP BW or SAP BW/4HANA 3.4 Configuring the Replication Process

source system in SAP BW. After the source system is created, it can be seen under the This ensures that the structure for the new DataSource will resemble the selected table
navigation path [ODP] ODP—Other. This is because the step specifying the ODP con- in the remote/source system. Choose Next. In the Selection Operational Data Provider
text has not been performed yet. Now, open this system and ensure the same queue section, select the table that needs to be replicated from the source system to the target
alias chosen at the time of creation of the configuration in the SAP LT Replication system, as shown in Figure 3.17. 3
Server system (as shown in Figure 3.10) is chosen as the ODP Context, as shown in
Figure 3.15.

Figure 3.15 ODP Context in Source System

Once done, activate the source system using the Activate button in the toolbar above.
Figure 3.17 Choose ODP Source for Replication
The newly added source system should then be displayed under the [ODP-SLT] ODP—
SLT Queue tree in the navigation page on the left. For the purpose of our example, we will use a flight booking scenario, so pick the stan-
dard SAP-delivered table SFLIGHT. For other replications, choose the appropriate tables
3.4.4 Creating Transfer Objects in SAP BW here. Choose Next. In the next screen, choose the Application Component and select
the appropriate DataSource Type that best matches the source that is being replicated.
The next step is to create objects in SAP BW that are meant to transfer data: Data-
In our example, we will use the Transaction Data option, as shown in Figure 3.18.
Sources, transformations, data transfer processes, and aDSOs.
To create a DataSource, go to the context menu of the newly created source system and
choose New • DataSource. In the New DataSource window, select the Proposal from
Operational Data Provider option, as shown in Figure 3.16.

Figure 3.18 Choose DataSource Type

Click the Finish button to enter the maintenance of the DataSource. In the Extraction
tab, the Extractor-Specific Properties section is prefilled with the queue alias for ODP
Context and the provider name (SFLIGHT in our example) as the Operational Data Pro-
vider, as shown in Figure 3.19.
Figure 3.16 Select ODP Template

80 81
3 Loading and Replication to SAP BW or SAP BW/4HANA 3.4 Configuring the Replication Process

ODQ_CHANGEMODE ODQ_ENTITYCNTR RECORDMODE Description

U 1 After-image

D -1 R Reverse-image (i.e., before- 3

image without a subsequent
after-image)

D 0 D (Incomplete) delete-image
(i.e., only key components
need to be specified)

U 0 A Additive image (aggregation

of before- and after-image
Figure 3.19 Extraction Settings in DataSource Maintenance for summable nonkey com-
ponents; after-image for
other nonkey components)
Under Extraction Properties, you can see that Overwrite Delta with Deletions (Delta
Queue) is autoselected for Delta Process. This means the extractor here is capable of Table 3.1 RecordMode Logic in ODP Scenarios (Cont.)
pulling in regular delta records as well as deltas with deletions, which are passed on via
the delta queue in ODP Complete the rest of the field settings, then click the Activate button. This completes
Similarly, the Fields tab contains settings related to each field that is sourced in the the creation and activation of the DataSource, and it is now ready to be used for further
metadata of the table definition. It is important to note that two new fields, ODQ_CHANGE- propagation of data.
MODE and ODQ_ENTITYCNTR, have been added to the existing fields, as shown in Figure
3.20. Tip
To make locating the newly created objects easier for future reference, they can be
added to your Favorites.

3.4.5 Creating an Advanced DataStore Object

Figure 3.20 ODQ_CHANGEMODE and ODQ_ENTITYCNTR As the next step, we will now create an aDSO that will take in and eventually persist the
data. To do so, go to the context menu of the InfoArea in which you want to create this
These fields combined are meant to indicate the type of change and the number of aDSO and choose New • DataStore Object (Advanced).
records affected by the change and are intended to be mapped to the RECORDMODE field of Enter a Name and Description for this aDSO. If preferred, the DataSource name
the transformation. These entries are listed in Table 3.1. (SFLIGHT in our example) can be chosen as a template. Then click Finish.

ODQ_CHANGEMODE ODQ_ENTITYCNTR RECORDMODE Description

In the aDSO maintenance, specify appropriate settings as preferred. In cases such as
ours, it is sensible to create an aDSO that supports the change log by selecting the Write
C 1 N New-image (i.e., after-image Change Log option as shown in Figure 3.21.
without a preceding before-
image) This is because the sender delta process in the DataSource is analogous to AIMD, which
means an intermediate aDSO layer is needed to capture and interpret delta data
U -1 X Before-image (summable
records if necessary. For legacy SAP BW objects, these settings represent the classic
nonkey components need to
DSO. After completing the configuration with the necessary settings for the aDSO, click
have reversed sign)
the Activate icon in the toolbar at the top to finish the creation and activation of the
Table 3.1 RecordMode Logic in ODP Scenarios aDSO. The aDSO is now ready to be loaded with the data from remote source system.

82 83
3 Loading and Replication to SAP BW or SAP BW/4HANA 3.4 Configuring the Replication Process

The preferred next step is to create another aDSO that resembles the settings of the Activate the transformation. Next, create a new data transfer process by selecting it
InfoCube. Note that these objects and the need to create each may differ from case to from the context menu of the aDSO. Ensure the delta mode is activated for this data
case depending on the delta process type specified by the extractor. transfer process.
Now execute this data transfer process by selecting the Execute in Background option
3
from its maintenance screen. You may choose to open the data transfer process moni-
tor by selecting the Execute and Open Monitor button in the subsequent popup. This
will open the DTP Monitor screen of the SAP BW cockpit screen, as shown in Figure 3.23,
if SAP BW/4HANA is being used. Alternatively, this process can also be triggered from
Transaction RSA1.

Figure 3.21 Maintenance of aDSO Figure 3.23 DTP Monitor in SAP BW Cockpit

As next steps, create the transformation and map the DataSource and aDSO defined in Figure 3.23 shows the data transfer process ran successfully, so let’s look at the total
the earlier steps. Observe how the ODQ_CHANGEMODE and ODQ_ENTITYCNTR fields from the records available in the aDSO, as shown in Figure 3.24. You can do this by going to
DataSource are automatically mapped to the 0RECORDMODE field of the aDSO, as shown in Transaction SE16 and accessing the count of the records of the relevant active table of
Figure 3.22. your aDSO.

Figure 3.22 RecordMode Mapping in Transformation

Figure 3.24 Total Records in aDSO after Initial Load

84 85
3 Loading and Replication to SAP BW or SAP BW/4HANA 3.4 Configuring the Replication Process

Now go to Transaction ODQMON in the source system—that is, the SAP LT Replication If circumstances prevent the completion of the aforementioned steps (such as the
Server system in which the configuration was created. Here you will see a new queue unavailability of the target system), you can end the subscription through the follow-
created with SLT_REPLICATOR as the provider and SAP Business Warehouse as a sub- ing alternative method. In Transaction ODQMON, locate the subscription and select
scriber, as shown in Figure 3.25. This is a nice way to filter down to the required queues Edit • End Subscription from the top menu. Upon receiving a prompt to confirm the 3
with a subscriber and provider combination, if you want to see only a limited list of deletion of the delta queue and termination of the subscription, click Yes to finalize the
queues from a big list of available queues in the operational delta queue. process.
In Figure 3.24, you can see the number of records loaded into the target aDSO was 414.
To confirm if this number matches the data volume in the source table (SFLIGHT), let’s
run a simple SQL query to fetch the total count of this table in the SQL editor. Figure 3.27
shows that the total number in the source was 414 records.

Figure 3.25 Delta Queues in Transaction ODQMON

You can get more details about the subscriber (the data transfer process, in this case) by
Figure 3.27 SQL Query Showing Record Count in Source Table
double-clicking the queue name (Flight in this example). You can continue to drill
down further to get more information about this queue and subscriber by double-
Details about the load statistics indicating the number of records read and calculated
clicking the data transfer process. Here, you will see the number of records loaded
can also be derived in the SAP LT Replication Server system by going to the Load Statis-
under Rows as well as the Extraction Mode, as shown in Figure 3.26.
tics tab of the configuration in Transaction LTRC, as shown in Figure 3.28.

Figure 3.26 Monitoring Delta Queues

In this example, the extraction mode is Initial Data (Delta Init). In cases where delta
Figure 3.28 Load Statistics of Configuration in Transaction LTRC
queues encounter an error state hindering data transfer to subscribers, a substantial
amount of data might accumulate within the ODP system. In this case, check the active
This confirms that the total volume (414 records) matches what is in the source table
status of the subscriber linked to the relevant tables. If the subscription is deemed
via the SQL editor, the SAP LT Replication Server system under Load Statistics, the ODP
unnecessary, halting data replication from the subscriber's end can be performed by
system via Transaction ODQMON, and the data transfer process via the SAP BW cock-
terminating the ongoing request within SAP BW system and removing the associated
pit.
data transfer process. Consequently, this process also ensures the appropriate deletion
of the corresponding queue within ODP.

86 87
3 Loading and Replication to SAP BW or SAP BW/4HANA 3.5 Managing Outages When Replicating Data

Now let’s look at the system behavior for a delta record. To do so, let’s add a new record On further examination, you can confirm the details of this new record in the relevant
to the source table SFLIGHT as shown in Figure 3.29. Here we use Transaction SE16 to add table of the aDSO, as shown in Figure 3.31, and ensure it matches accurately with what
a new record in the source system. was defined in the table in the source.
3

Figure 3.31 New Record in Target aDSO

Real-Time Data Transfer

In this section, you saw a new record brought into the target aDSO successfully. How-
ever, it is important to note that this record was only loaded to the aDSO when the
data transfer process was executed manually. In the real world, it is difficult to ensure
the data is sourced in real time if this data transfer process needs to be executed man-
ually each time. To keep the scenario truly happening in real time, what we need is for
the data transfer process to be executed automatically when there is a delta record cre-
ated in the source table.
Such a scenario is made possible in SAP BW/4HANA system via a feature known as
streaming. With streaming enabled for a process chain, this data transfer process can
Figure 3.29 New Record Created in Source Table
be called automatically to ensure any new data in the source is seamlessly transferred
to an SAP BW/4HANA system without human intervention and in real time. Such a pro-
Now run the data transfer process to ensure this record is extracted into the SAP BW
cess chain designed for streaming purposes can be initiated and run at a high fre-
system. As shown in Figure 3.30, the new record arrives at the target aDSO.
quency. This enables the real-time updating of data to aDSOs. As a result, process
chains offer a comprehensive approach for both periodic and highly frequent schedul-
ing needs, encompassing streaming capabilities. This dual functionality contributes to
streamlining the architecture of SAP BW/4HANA. The setting to enable a process chain
for streaming or not is determined by a specific attribute configured within the process
chain itself.
For more details on the streaming feature, see http://s-prs.co/v582101.

3.5 Managing Outages When Replicating Data

You have now learned how to initialize and load data into SAP BW. As long as the repli-
cation runs, this process can be repeated. Any errors that happen in SAP BW or SAP LT
Replication Server can also be rectified and the process can be rerun. However, how are
these processes affected at the time of a planned outage? What happens to the replica-
tions and the status of the SAP LT Replication Server scenarios if the source system is
Figure 3.30 Data Transfer Process Run after Creation of New Record in Source

88 89
3 Loading and Replication to SAP BW or SAP BW/4HANA 3.5 Managing Outages When Replicating Data

down? What happens when SAP LT Replication Server or the target system is down? In summary, if the source system is down, it impacts the table replication, but does not
These are the scenarios we will consider in the upcoming sections. impact the data.
When using SAP LT Replication Server, unscheduled downtimes or other system events
can disrupt the replication of data. This section is specific to unplanned outages and
3
3.5.2 SAP LT Replication Server Is Down
defines how to react when such events occur. It is quite surprising that in such situa-
When SAP LT Replication Server goes down, there is no data movement between
tions, the target system is typically not in sync with the source system, which leads to
sources and targets. If SAP LT Replication Server goes down, triggers are still active in
data inconsistency. To handle situations of data inconsistency, you can perform a par-
the source system. In this case, SAP LT Replication Server triggers continue to capture
tial load of data or selective data loads from the source system to the target system. A
the data changes and insert them into respective logging tables. As a result, the logging
partial load refers to data replicated to the target system with filter criteria in place,
table keeps growing, consuming system memory.
such as data for a specific time or specific company codes.
When SAP LT Replication Server is back up and running, tables in the replication phase
SAP LT Replication Server replications involve source, SAP LT Replication Server, and
pick up and replicate data from where the process left off.
target systems, so let’s understand what happens in the following unplanned outage
situations:
Note
쐍 When the source system is down
For tables in an initial load or calc process, we recommended restarting the table repli-
쐍 When SAP LT Replication Server is down
cation.
쐍 When the target system is down

In summary, if SAP LT Replication Server is down, it impacts the table replication but
3.5.1 Source System Is Down does not impact the data.

When the source goes into an unplanned outage, there is no scope for the changes to
occur in the system within the application table; ultimately it does not cause any 3.5.3 Target System Is Down
impact to the data. Because the source system is down and SAP LT Replication Server is
When the final target SAP BW system is down, data cannot be written to the SAP BW
connected to the source via an RFC connection, the replication in SAP LT Replication
system by the ODP framework. This data will continue to reside in the ODP framework
Server will be in an error status and replication cannot continue. You see RFC commu-
until SAP BW resumes communications from the ODP framework. Once SAP BW is
nication failure errors in SAP LT Replication Server when the source system is no longer
operational, it interacts with the ODP framework, consumes data from the ODP queue,
in communication with SAP LT Replication Server.
and finally writes to the SAP BW system.
SAP LT Replication Server tries constantly to connect to the source system, and that
generates lots of communication failure logs in SAP LT Replication Server. If you want
Note
to avoid these unnecessary logs, you can deactivate the configuration pointing to the
SAP LT Replication Server’s role in the ODP scenario is to read from the source system
source system that is currently down.
and write into the ODP framework within SAP LT Replication Server. Once data is writ-
You can activate the configuration again once the source system is up and running. ten in the ODP framework, the delta data captured in the logging table in the source
Tables in the replication phase will be automatically resumed or continue replications system will be lost. It is SAP BW’s responsibility to interact with the ODP framework in
from where they were paused. If an access plan calculation was in process in the source SAP LT Replication Server, get the data from the queue, and write it into SAP BW.
system, because the system was down, background calculation jobs will have failed and
you can see that calculation process failed in SAP LT Replication Server. In summary, if the target system is down, it impacts the table replication, but does not
impact the data.
Note
For tables in an initial load or calc process, we recommended restarting the table repli-
cation.

90 91
Contents

Preface ....................................................................................................................................................... 13

1 Introduction 19

1.1 SAP Real-Time Replication Tools .................................................................................... 20

1.2 SAP LT Replication Server Technical Functionality ................................................. 21

1.3 Architecture ............................................................................................................................. 23

1.4 Replication Scenarios ........................................................................................................... 24
1.4.1 ABAP to ABAP Scenario ......................................................................................... 24
1.4.2 ABAP/Non-ABAP to SAP BW Scenario .............................................................. 25
1.4.3 ABAP/Non-ABAP to SAP S/4HANA Scenario (Central Finance) ............... 26
1.4.4 ABAP/Non-ABAP to SAP Data Services Scenario .......................................... 27
1.4.5 ABAP to SAP Data Intelligence Cloud Scenario ............................................. 27
1.5 Sizing Considerations .......................................................................................................... 28

1.6 Deployment Options ............................................................................................................ 30

1.7 Installation ............................................................................................................................... 32

1.8 SAP LT Replication Server: Multisupport System .................................................... 33

1.9 Features ..................................................................................................................................... 35

1.9.1 Email Notifications ................................................................................................ 35
1.9.2 Replication Logging ............................................................................................... 36
1.9.3 Archival Features .................................................................................................... 37
1.10 Use Cases ................................................................................................................................... 37
1.10.1 Data Migration ........................................................................................................ 37
1.10.2 Data Consolidation ................................................................................................ 43
1.10.3 Real-Time Reporting .............................................................................................. 44
1.11 Summary ................................................................................................................................... 47

2 Loading and Replication to SAP HANA 49

2.1 Architecture ............................................................................................................................. 50

2.2 Overview of Replication Process .................................................................................... 51

7
Contents Contents

2.3 Authorizations ........................................................................................................................ 52 4.3.2 Creating Predefined Migration Objects .......................................................... 101
4.3.3 Triggering Table Load and Replication ............................................................ 106
2.4 Configuring Replication Process ..................................................................................... 54
2.4.1 Creating SAP LT Replication Server Configuration ...................................... 54 4.4 Managing Outages When Replicating Data .............................................................. 112
2.4.2 Triggering Table Load and Replication ............................................................ 57 4.4.1 Source System Is Down ........................................................................................ 113
4.4.2 SAP LT Replication Server Is Down .................................................................... 114
2.5 Managing Outages When Replicating Data .............................................................. 63
4.4.3 Target SAP S/4HANA System Is Down ............................................................ 114
2.5.1 Source System Is Down ........................................................................................ 64
2.5.2 SAP LT Replication Server Is Down .................................................................... 65 4.5 Summary ................................................................................................................................... 115
2.5.3 Target SAP HANA System Is Down ................................................................... 65
2.6 Summary ................................................................................................................................... 65
5 Loading and Replication to Cloud Applications 117

3 Loading and Replication to SAP BW or 5.1 Using SAP Data Services ..................................................................................................... 118
5.1.1 Architecture .............................................................................................................. 120
SAP BW/4HANA 67
5.1.2 Overview of the Replication Process ................................................................ 121
5.1.3 Authorizations ......................................................................................................... 123
3.1 Architecture ............................................................................................................................. 69
5.1.4 Configuring the Replication Process ................................................................ 124
3.2 Overview of the Replication Process ............................................................................ 70 5.1.5 Managing Outages When Replicating Data .................................................. 143
3.3 Authorizations ........................................................................................................................ 73 5.2 Using SAP Data Intelligence Cloud ................................................................................ 144
3.4 Configuring the Replication Process ............................................................................. 74 5.2.1 Architecture .............................................................................................................. 146
3.4.1 Creating a Configuration in SAP LT Replication Server .............................. 75 5.2.2 Overview of the Replication Process ................................................................ 147
3.4.2 Activating ODP Usage for SAP LT Replication Server .................................. 78 5.2.3 Authorizations ......................................................................................................... 149
3.4.3 Creating a Logical System in SAP BW .............................................................. 79 5.2.4 Configuring the Replication Process ................................................................ 151
3.4.4 Creating Transfer Objects in SAP BW .............................................................. 80 5.2.5 Managing Outages When Replicating Data .................................................. 166
3.4.5 Creating an Advanced DataStore Object ........................................................ 83 5.3 Summary ................................................................................................................................... 168
3.5 Managing Outages When Replicating Data .............................................................. 89
3.5.1 Source System Is Down ........................................................................................ 90
3.5.2 SAP LT Replication Server Is Down .................................................................... 91 6 Scheduled Downtime: Recovery Procedures 169
3.5.3 Target System Is Down ......................................................................................... 91
3.6 Summary ................................................................................................................................... 92 6.1 SAP Source System Undergoing Upgrade Process .................................................. 170
6.1.1 Initial Steps ............................................................................................................... 170
6.1.2 Drop the SAP LT Replication Server Triggers in the Source System ....... 172
6.1.3 Recreate the SAP LT Replication Server Triggers .......................................... 175
4 Loading and Replication to Central Finance and
6.1.4 Compare the Structure and Resolve Inconsistencies ................................. 178
SAP S/4HANA 93 6.1.5 Final Steps ................................................................................................................. 179
6.2 DMIS Upgrade in Source System and SAP LT Replication Server ..................... 181
4.1 Architecture ............................................................................................................................. 94
6.2.1 Initial Steps ............................................................................................................... 181
4.2 Authorizations ........................................................................................................................ 97 6.2.2 Drop the SAP LT Replication Server Triggers in the Source System ....... 183
4.3 Configuring Replication Process ..................................................................................... 98 6.2.3 Recreate the SAP LT Replication Server Triggers .......................................... 186
4.3.1 Creating the SAP LT Replication Server Configuration .............................. 98

8 9
Contents Contents

6.2.4 Compare the Structure and Resolve Inconsistencies ................................. 188 7.3.4 User Roles for ABAP Targets ................................................................................ 231
6.2.5 Final Steps ................................................................................................................. 190 7.3.5 User Roles for the SAP HANA Target System ................................................ 232
6.3 Target SAP HANA System Undergoing Patch Upgrade ........................................ 192 7.3.6 Limiting Access in Source System ..................................................................... 239

6.3.1 Initial Steps ............................................................................................................... 193 7.4 Network and Communication Security ....................................................................... 243
6.3.2 Connection Test ...................................................................................................... 194 7.4.1 Configuring Access to ABAP Source Systems ................................................ 244
6.3.3 Final Steps ................................................................................................................. 197 7.4.2 Configuring Access to Non-ABAP Source System ........................................ 245
6.4 Source System Undergoing Database Migration .................................................... 198 7.4.3 Configuring Access to Target SAP HANA System ........................................ 245

6.4.1 Initial Steps ............................................................................................................... 198 7.5 Summary ................................................................................................................................... 246

6.4.2 Drop the SAP LT Replication Server Logging Tables in the
Source System ......................................................................................................... 200
6.4.3 Recreate the SAP LT Replication Server Triggers and Logging Tables ... 201
6.4.4 Final Steps ................................................................................................................. 203
8 Performance Optimization 249

6.5 Source Transition from On-Premise to Private Cloud ........................................... 204

8.1 Optimizing Initial Data Loads .......................................................................................... 249
6.6 Switch Replications from One SAP LT Replication Server System 8.1.1 Preparation Activities ............................................................................................ 251
to Another ................................................................................................................................. 208 8.1.2 Reading Types .......................................................................................................... 251
6.7 Summary ................................................................................................................................... 211 8.1.3 Parallelization Job Settings ................................................................................. 264
8.1.4 Filter Unwanted Data ........................................................................................... 265
8.1.5 Planning the Initial Load ...................................................................................... 267
8.2 Performing and Optimizing Data Replication .......................................................... 267
7 Security 213
8.2.1 Options for Logging Tables ................................................................................. 268
8.2.2 Generic Ranges and Range Conditions ........................................................... 270
7.1 User Management ................................................................................................................ 213 8.2.3 Filter Conditions ...................................................................................................... 274
7.1.1 SAP LT Replication Server ..................................................................................... 214
8.3 Subscription-Based Change Data Capture ................................................................. 275
7.1.2 ABAP Source System .............................................................................................. 214
7.1.3 Non-ABAP Source System .................................................................................... 215 8.4 Summary ................................................................................................................................... 275

7.2 Authorization Objects ......................................................................................................... 215

7.2.1 S_DMIS ....................................................................................................................... 216
7.2.2 S_DMC_S_R .............................................................................................................. 218 9 Transformations 277
7.2.3 S_DMIS_SLT .............................................................................................................. 219
7.2.4 S_DMIS_MOM ......................................................................................................... 219
9.1 Type Mapping ......................................................................................................................... 277
7.2.5 S_DHCDCACT ........................................................................................................... 220
9.1.1 Data Type Handling for Source and Target System .................................... 278
7.2.6 S_DHBASACT ........................................................................................................... 221
9.1.2 Global Mapping Values ........................................................................................ 283
7.2.7 S_DHCDCCDS .......................................................................................................... 222
9.1.3 Mapping Values for Table .................................................................................... 284
7.2.8 S_DHCDCTAB ........................................................................................................... 224
7.2.9 S_DHCDCSTP ........................................................................................................... 224 9.2 Rule Assignment .................................................................................................................... 286
7.2.10 S_DMISIUCA ............................................................................................................. 225 9.2.1 Field-Based Rules .................................................................................................... 286
9.2.2 Event-Based Rules .................................................................................................. 288
7.3 Roles and Privileges .............................................................................................................. 226
9.2.3 Filter Rules ................................................................................................................ 290
7.3.1 User Roles for SAP LT Replication Server ......................................................... 227
7.3.2 User Roles for ABAP Source System ................................................................. 228 9.3 Summary ................................................................................................................................... 291
7.3.3 User Roles for Non-ABAP Source System ........................................................ 230

10 11
Index

A Communication channel ........... 52, 96, 122, 147

Communication issue ........................................ 307
ABAP Dictionary .................................................... 278 Communication security .................................. 243
data types ............................................................ 279 Communication user type ............................... 214
ABAP source system .............................. 23, 24, 214 Compare Table Structures report ......... 178, 188
Activity type ............................................................ 216 Connection check ................................................. 296
Advanced Data Store Object (aDSO) ................. 72 Connection Management app ............... 158, 161
create ....................................................................... 83 Create Predefined Load and Replication
records ..................................................................... 85 Objects report ................................................... 102
Application Interface Framework (AIF) ........ 113 Cross-Database Comparison application ... 302
Architecture ............................................................... 23
Archival feature ........................................................ 37 D
Authorization ................. 52, 73, 97, 123, 149, 230
fields ...................................................................... 216 Data acquisition logic ............................................ 97
Authorization object ........................................... 215 Data consolidation ................................................. 43
S_DHBASACT ..................................................... 221 Data discovery ....................................................... 145
S_DHCDCACT .................................................... 220 Data filtering ............................................................. 38
S_DHCDCCDS ................................. 222, 230, 241 Data flow .................................................................. 133
S_DHCDCSTP ..................................................... 224 validate ................................................................ 135
S_DHCDCTAB .................................................... 224 Data governance and compliance ................. 145
S_DMC_S_R ........................................................ 218 Data injection ........................................................... 72
S_DMIS ................................................................. 216 Data integration ................................................... 145
S_DMIS_MOM ................................................... 219 Data integrity ......................................................... 239
S_DMIS_SLT ....................................................... 219 Data migration ......................................................... 37
S_DMISIUCA ...................................................... 225 Data Monitor .......................................................... 264
Data pipeline .......................................................... 145
B Data provisioning ...................... 57, 107, 209, 293
Data replication ............................... 43, 52, 96, 122
Background job ............................................... 59, 294 cannot replicate from table ......................... 306
Batch job ................................................................... 128 optimization ...................................................... 267
execute ................................................................. 136 Data Transfer Monitor ................................ 61, 139
Begin of record (BOR) .......................................... 289 Data transfer process .............. 21, 71, 85, 88, 210
Bidirectional data replication ............................. 35 Data transformation ........ 35, 38, 51, 52, 96, 122
Data type .................................................................. 285
C Data type handling .............................................. 278
Data validation ......................................................... 43
Calculation job ................................................ 59, 110 Data visualization ................................................ 145
California Consumer Privacy Act (CCPA) .... 145 Database connection ................................... 55, 243
CDS view ................................................................... 223 Database migration ............................................. 198
Central Finance ................................................. 26, 93 drop logging tables ......................................... 200
architecture ........................................................... 94 final steps ............................................................ 203
source structure ................................................ 108 initial steps ......................................................... 198
Central monitoring .............................................. 293 recreate triggers and tables ......................... 201
Change log .................................................................. 83 DataSource ................................................... 70, 80, 81
Changed-data capture ......................................... 132 Datastore connection ................................ 128, 130
Cloud application ....................................... 117, 152 test ......................................................................... 130
Cloud connector .................................................... 147 Delete Triggers report ........................................ 183
Cluster table .................................................. 126, 261 Delta data .................................................................... 21

313
Index Index

Delta queue ................................................................ 86 H N Reading type ............................... 100, 126, 251, 252
monitor ................................................................... 86 1 (range calculation) ....................................... 252
Delta record ................................................................ 88 Health check ............................................................ 299 Network security ................................................... 243 3 (primary key order) ...................................... 256
Deployment options .............................................. 30 Non-ABAP source system .................................. 215 4 and 5 (sender queue) ................................... 259
Dialog user ............................................................... 244 I Number of records ............................................... 261 Performance Optimized ................................ 100
Display Replication Statistics report ...... 63, 112 Resource Optimized ........................................ 100
DMIS add-on ................ 33, 57, 106, 128, 150, 236 InfoProvider .............................................................. 68 O Real-time data replication ............................ 35, 38
DMIS upgrade ......................................................... 181 Initial load ........................................ 21, 62, 107, 126 Real-time load ........................................................ 109
activate configuration ................................... 191 optimize ............................................................... 249 Object type .............................................................. 216 Real-time reporting ................................................ 44
drop trigger ........................................................ 183 options .................................................................. 254 On-premise to cloud migration ...................... 204 RecordMode logic ................................................... 82
final steps ............................................................ 190 plan ........................................................................ 267 Open Database Connectivity (ODBC) .............. 53 Recovery procedure ............................................ 170
initial steps ......................................................... 181 Initial user ................................................................ 232 Operational data provisioning (ODP) ............. 20, Replicated table ..................................................... 236
recreate triggers ............................................... 186 Installation ................................................................. 32 68, 125 Replication error ................................................... 305
resolve inconsistencies ................................... 188 Internet of Things (IoT) ....................................... 145 context ................................................... 71, 80, 130 Replication flow .................................................... 160
Duplicate key .......................................................... 305 framework ..................................................... 69, 74 create .................................................................... 160
J object ..................................................................... 130 load type ............................................................. 163
E usage ........................................................................ 78 task ........................................................................ 162
Job log .......................................................................... 60 Operational delta queue (ODQ) ......................... 70 Replication logging ................................................. 36
Email notification .......................................... 35, 294 Job server .................................................................. 136 Outage ...................................... 63, 89, 112, 143, 166 Replication object ................................................ 103
checks .................................................................... 296 Replication of multiple sources ........................ 35
frequency ............................................................. 295 L P Replication process ................................................ 21
recipients ............................................................. 298 Replication role ..................................................... 235
End of record (EOR) .............................................. 289 Latency check .......................................................... 297 Package size ................................................... 256, 261 Replication user ........................................... 234, 238
Error handling ................................... 38, 52, 96, 122 Limiting access ....................................................... 239 Parallelization job settings ............................... 264 Report
Event-based rule .................................................... 288 Load balancing ....................................................... 150 Partial load ............................................................... 112 ADBC_TEST_CONNECTION ......................... 194
create .................................................................... 288 Load statistics ................................. 61, 87, 111, 140 Patch upgrade ........................................................ 192 CNV_NOTE_ANALYZER_SLT ....................... 190
include program ............................................... 290 Logging table ............................ 51, 58, 94, 120, 146 connection name ............................................. 196 DMC_UPLOAD_OBJECT ................................ 102
line of code .......................................................... 289 cannot create ..................................................... 308 connection test ................................................. 194 IUUC_SCHEDULE_TABLE_OPER_INFO ..... 28
check ............................................................ 171, 181 final steps ............................................................ 197 Reset Load and Replication Status
F entries .................................................................... 297 initial steps ......................................................... 193 report ................................................. 176, 186, 202
option .................................................................... 268 Performance optimization ....... 52, 97, 123, 249 Reset Status for Triggers and Logging
Field-based rule ..................................................... 286 structure ............................................................... 138 Persistent staging area .......................................... 68 Tables report .................................. 175, 186, 201
assignment ......................................................... 287 update/don't update ....................................... 302 Predefined migration object .............. 93, 94, 101 Resolve Inconsistencies between Proxy
Filter ........................................................................... 146 Logical system .......................................................... 79 Privilege .................................................................... 226 Table and Target Table report ........... 179, 189
condition ................................................... 266, 274 Long-running job .................................................. 299 Provider ....................................................................... 70 Revoking access .................................................... 236
rule ............................................................... 266, 290 RFC connection .................... 54, 76, 100, 152, 269
Filtering ....................................................................... 51 Q Role ............................................................................ 226
M
Flat file .................................................... 133, 140, 142 <REPLICATION SCHEMA>_DATA_
Freeze triggers ........................................................ 239 Machine learning .................................................. 145 Query transformation ........................................ 134 PROV ................................................................ 235
Function module .................................................. 149 Managed database connection .......................... 50 Queue alias ......................................................... 71, 76 <REPLICATION_SCHEMA>_POWER_
Mapping value ........................................................ 284 USER ................................................................. 235
G <REPLICATION_SCHEMA>_SELECT_
Mass transfer ........................................................... 253 R
Mass transfer ID (MTID) ........... 57, 106, 286, 294 USER ................................................................. 235
General Data Protection Regulation Metadata management ...................................... 145 Range ......................................................................... 255 <REPLICATION_SCHEMA>_USER_
(GDPR) .................................................................. 145 Microsoft Azure ........................................... 159, 168 condition ............................................................. 272 ADMIN ............................................................ 235
Global mapping values ....................................... 283 Microsoft SQL Server system ........................... 278 configure ............................................................. 262 REPLICATION_SCHEMA>_SELECT_
Granting access ...................................................... 236 Migration Workbench ........................................... 95 define table manually .................................... 272 USER_GRANTABLE ..................................... 235
Grouping field ........................................................ 271 Monitoring ..................................................... 122, 293 generic table ....................................................... 270 S_RS_RDEMO ....................................................... 74
Multisupport system ............................................. 33 table SFLIGHT .................................................... 273 SAP_IUUC_REPL_ADMIN ............. 73, 227, 231
RDA daemon .............................................................. 71 SAP_IUUC_REPL_ADMIN_BW_ODQ .......... 74
Read module .............................................................. 95 SAP_IUUC_REPL_DISPLAY .......................... 227
READ_METADATA action .................................. 240

314 315
Index Index

Role (Cont.) Secondary database connection ....................... 95 Transaction (Cont.) Trigger ................................................ 46, 59, 109, 306
SAP_IUUC_REPL_REMOTE ................... 74, 228, Secure Network Communications (SNC) ..... 150 IUUC_REPL_EN ................................................. 294 IUUC ...................................................................... 174
229, 231 Security ..................................................................... 213 LTRC ........................................... 38, 54, 75, 98, 251 job .......................................................................... 137
Rule assignment .................................................... 286 Selection parameter ............................................. 253 LTRS ...................................................... 36, 257, 283 list .......................................................................... 172
Runtime object ...................................................... 110 Sender queue ................................................ 259, 275 MWB ......................................................................... 95 logic ....................................................................... 138
Sequence number .................... 111, 165, 303, 308 ODQMON .................................... 70, 86, 121, 142 reset ....................................................................... 176
S Service Marketplace ............................................. 156 PFCG ...................................................................... 216 Troubleshooting ................................................... 305
Size of read portions ............................................ 258 RSA1 .................................................................. 79, 85 Type mapping ........................................................ 277
SAP Business Technology Platform Sizing ............................................................................ 28 SAINT ....................................................................... 33
(SAP BTP) ............................................................. 155 Source application table ....................................... 45 SE11 .................................................................. 58, 109 U
SAP Business Warehouse (SAP BW) ... 26, 67, 70 Source system ................................... 75, 94, 99, 120 SE16 ................................................................. 58, 109
data target ............................................................. 71 analysis ................................................................... 41 SE38 ........................................................................ 236 Unmanaged database connection ................... 50
modeling tools ..................................................... 79 database ............................................................... 270 SM37 ............................................................... 59, 110 User management ............................................... 213
SAP BW cockpit ......................................................... 85 specify ................................................................... 125 SM59 ............................................................... 55, 125
SAP BW/4HANA ......................................... 67, 71, 72 Source transition ................................................... 204 SNRO ..................................................................... 308 V
SAP Data Intelligence Cloud ...................... 27, 118 activate configuration ................................... 207 Transfer job ............................................................. 126
architecture ........................................................ 146 adjust RFC connections .................................. 205 Transfer object .......................................................... 80 View Unprocessed Logging Table Records
assign role ........................................................... 155 monitoring .......................................................... 207 Transfer settings .............................................. 55, 76 report .......... 171, 180, 181, 191, 193, 197, 198,
connection .......................................................... 158 Space ........................................................................... 155 Transformation .................................. 121, 146, 277 205, 207
connection management ............................. 150 SQL editor ................................................................... 87 Transparent table .................................................. 250 View Unprocessed Logging Table report ....... 62
deploy ................................................................... 155 SQL privilege ........................................................... 233
establish connection ....................................... 149 SQL schema .............................................................. 233
instance ................................................................ 156 Statistics .................................................................... 165
launchpad ........................................................... 160 Structural inconsistencies ................................. 308
use .......................................................................... 144 Subscriber ................................................................... 70
SAP Data Services ................. 20, 27, 117, 120, 123 Subscription-based change data capture .... 275
architecture ........................................................ 120 Switch replications ............................................... 208
configuration ..................................................... 124 system A ............................................................... 208
create project ..................................................... 128 system B ............................................................... 208
data replication ................................................ 118 SYS schema .............................................................. 214
Designer ............................................................... 128 System privilege .................................................... 233
job ........................................................................... 130 System upgrade ..................................................... 170
job log ................................................................... 140 drop triggers ....................................................... 172
table overview ................................................... 137 final steps ............................................................. 179
SAP HANA .................................................. 24, 49, 214 initial steps .......................................................... 170
architecture ........................................................... 50 recreate triggers ................................................ 175
authorizations ..................................................... 53 resolve inconsistencies ................................... 178
data types ............................................................ 281
reading type 1 .................................................... 255 T
schemas ............................................................... 238
SAP HANA smart data integration .................... 20 Table does not exist ............................................. 307
SAP HANA Studio ................................................. 293 Table field ................................................................. 285
SAP LT Replication Server Cockpit ......... 36, 191, Table load ......................................................... 57, 164
214, 293 replication ........................................................... 107
SAP NetWeaver platform ................................... 213 Table replication ...................................................... 57
SAP Replication Server .......................................... 20 Table-to-table replication .................................. 111
SAP S/4HANA ............................................. 27, 93, 94 Target system .......................................... 42, 76, 100
SAP Solution Manager ........................................ 301 connection details ............................................ 125
SAP source system .................................................. 50 Task ............................................................................. 165
SAPconnect ............................................................. 294 Transaction
Scheduled downtime .......................................... 169 for troubleshooting ......................................... 309
Schema target ............................................................ 61 IUUC_REMOTE .... 59, 109, 138, 172, 183, 210

316 317
 First-hand knowledge.

Prathyusha Garimella works as a senior consultant at SAP Amer-

ica, Inc. With over a decade of IT experience spanning the globe,
Prathyusha has successfully deployed various SAP solutions for
large corporations, mostly featuring in the Fortune 100 companies
worldwide, enabling financial and business transformation capabil-
ities. She is an expert in the ETL and data management concepts,
with extensive experience in implementations in SAP as well as non-
SAP solutions. Her expertise in architecture, design, and configura-
tion has provided invaluable guidance to these organizations, resulting in increased
efficiency and improved business outcomes.

Shashidhar Garimella is an accomplished principal architect at SAP

America Inc., known for his exceptional skills and expertise in the
field of enterprise software solutions. With a career spanning over
a decade, Shashidhar has made significant contributions to the ar-
eas of SAP analytics, EIM, data management, financial planning,
and corporate closing portfolios, which have empowered numer-
ous corporations to optimize their operations and drive business
success.

Prathyusha Garimella, Shashidhar Garimella

SAP Landscape Transformation Replication Server

The Practical Guide We hope you have enjoyed this reading sample. You may recommend or pass it on to
others, but only in its entirety, including all pages. This reading sample and all its parts are
317 pages | 02/2024 | $89.95 | ISBN 978-1-4932-2525-5
protected by copyright law. All usage and exploitation rights are reserved by the author
www.sap-press.com/5821 and the publisher.