Introducing Client-Specific Replication

Objective

After completing this lesson, you will be able to understand client-specific and cross-client replication.

Client-Specific Replication

By default, the SAP Landscape Transformation Replication Server loads and replicates the data of all defined tables. Client-specific tables are also loaded and replicated in their entirety, and not restricted to a certain client. The data load can be restricted by defining filter rules or by activating the client-specific load and replication.

A screenshot showing that the Read from Single Client checkbox is selected in the Source System Connection Details section

Prerequisites:

  • Restrict load and replication to a single client. To restrict a load to multiple, but not all, clients, you must define individual filter rules.
  • The RFC destination to the source system points to the relevant client. The relevant client is derived from the RFC connection.

Activation

When you create a new configuration, specify Read from Single Client.

Result

Database triggers are defined in such a way that they only record changes from the relevant client. Data that is loaded and replicated is restricted to the client defined in the RFC destination. Thus, smaller amounts of data are transferred.

Note

In configurations that do not use the new change data capture (CDC) recording mechanism introduced in SAP Landscape Transformation Replication Server 3.0 SP04 (the subscription-based CDC recording mechanism), this setting affects the creation of the triggers. The database triggers are defined in such a way that they only record changes from the relevant client.

If you want to filter on a three-client system (100, 200, 300) and want to transfer only data of two clients, for example 100 and 200, you must apply a transformation rule.