User Guide CUSTOMER

Document Version: 1.2 – 2020-01-23

SAP Landscape Transformation Replication Server

Replicating Data from an INDX-like Table to a Target System
Typographic Conventions

Type Style Description

Example Words or characters quoted from the screen. These include field names, screen titles,
pushbuttons labels, menu names, menu paths, and menu options.
Textual cross-references to other documents.

Example Emphasized words or expressions.

EXAMPLE Technical names of system objects. These include report names, program names,
transaction codes, table names, and key concepts of a programming language when they
are surrounded by body text, for example, SELECT and INCLUDE.

Example Output on the screen. This includes file and directory names and their paths, messages,
names of variables and parameters, source text, and names of installation, upgrade and
database tools.

Example Exact user entry. These are words or characters that you enter in the system exactly as
they appear in the documentation.

<Example> Variable user entry. Angle brackets indicate that you replace these words and characters
with appropriate entries to make entries in the system.

EXAMPLE Keys on the keyboard, for example, F 2 or E N T E R .

CUSTOMER SAP Landscape Transformation Replication Server

2 © 2020 SAP SE or an SAP affiliate company. All rights reserved. Typographic Conventions
Document History

Version Date Change

1.0 2016-10-26 Version for DMIS 2011 SP11.

1.1 2017-02-14 Version valid for DMIS 2011 SP11 and DMIS 2011 SP12.

1.2 2020-01-23 Updated version containing information about using rules with INDX-like
tables.

SAP Landscape Transformation Replication Server CUSTOMER

Document History © 2020 SAP SE or an SAP affiliate company. All rights reserved. 3
Table of Contents

1 Introduction ................................................................................................................................... 5
1.1 Prerequisites ................................................................................................................................... 5
1.2 Background Information About INDX-like Tables........................................................................... 5

2 Replicating Data from Table STXL to a Target System ........................................................... 6

2.1 Add Table STXL to INDX-like Table Settings .................................................................................. 6
2.1.1 Background...................................................................................................................... 6
2.1.2 Process ............................................................................................................................ 6
2.2 Specify a Target Table Template .................................................................................................... 8
2.2.1 Background...................................................................................................................... 8
2.2.2 Process ............................................................................................................................ 8
2.3 Map the Key Fields of Table STXL to the Target Table Template ................................................... 9
2.4 Activate and Save the INDX-like Table Settings ........................................................................... 10
2.4.1 Process .......................................................................................................................... 10
2.5 Specify Alternative Table Name (Optional) ................................................................................... 11
2.5.1 Process ........................................................................................................................... 11
2.6 Start the Initial Load or Replication Process for Table STXL .........................................................12
2.6.1 Process ...........................................................................................................................12

3 Working with Rules for INDX-like Tables ................................................................................. 13

3.1 Using an Event-Based Rule to Change Client Number ................................................................. 13
3.2 Using a Rule for Both the Initial Load and Replication Process .................................................... 13

CUSTOMER SAP Landscape Transformation Replication Server

4 © 2020 SAP SE or an SAP affiliate company. All rights reserved. Table of Contents
1 Introduction

SAP Landscape Transformation Replication Server can transfer the data from INDX-like tables to a table in the
target system in a readable format.
This document outlines how to transfer the data from an example INDX-like table (STXL) to a table in the target
system in a readable format.

1.1 Prerequisites

DMIS 2011 SP11 or higher is installed in the SAP Landscape Transformation Replication Server system.

Caution
• The source system must be an ABAP-based SAP system.
• SAP BW is not supported as a target system.

1.2 Background Information About INDX-like Tables

INDX-like cluster tables are tables in which the data is stored in a special way. They are designed to hold large
amounts of data assigned to a single key. From a technical perspective, these tables are normal transparent
tables but there are special methods to store the data in the tables, and to retrieve data from the tables.
Data in INDX-like tables is stored in a compressed and raw data format. It is therefore important to understand
how the data can be converted to a readable format.
Data is stored in INDX-like tables in components. Each component can have any data type available in the ABAP
Dictionary. In a normal database table, a primary key uniquely identifies a row in the database table. In INDX-like
tables, an INDX key uniquely identifies the data within a single logical area for the table. These logical areas are
known as relation IDs, or RELIDs.
A different set of components can be stored for each key. Usually, however, a single logical area (or a single
version of a logical area) has the same set of components, independent of the key.
This means that the data in a specific logical area in an INDX table can be accessed by providing a RELID and
component combination.
Because the data in the data cluster is provided in a compressed and raw data format, you must use a target table
template to represent a readable data format.

SAP Landscape Transformation Replication Server CUSTOMER

Introduction © 2020 SAP SE or an SAP affiliate company. All rights reserved. 5
2 Replicating Data from Table STXL to a
Target System

Table STXL is an INDX-like table in an ABAP-based SAP source system. You want to replicate the records from
this table (in a readable format) to a table in the target system.

2.1 Add Table STXL to INDX-like Table Settings

2.1.1 Background

The first step is to add table STXL to INDX-like Table Settings, in order to obtain the required information from the
knowledge base.

If the knowledge base for INDX-like tables contains information about an INDX-like table, the system displays this
information in one or more rows. Such rows have the value Knowledge Base in the field Source. Each row
corresponds to a specific logical area in the INDX-like table, identified by the RELID and component combination.
You can use these rows to transfer data from the INDX-like table to the target table in a readable form.

2.1.2 Process

In transaction LTRS (Advanced Replication Settings), right-click the node INDX-like Table Settings and choose Add
Table. Specify table STXL. The system automatically displays the relevant information associated with the table
under RELID and Component Combinations. In the case, this is a row with the RELID and component combination
TX / TLINE. This information is derived from the knowledge base (SAP Landscape Transformation Replication
Server provides a knowledge base for INDX-like tables that contains information about known logical areas and
their structures).

CUSTOMER SAP Landscape Transformation Replication Server

6 © 2020 SAP SE or an SAP affiliate company. All rights reserved. Replicating Data from Table STXL to a Target System
 RELID and Component Combination TX / TLINE

SAP Landscape Transformation Replication Server CUSTOMER

Replicating Data from Table STXL to a Target System © 2020 SAP SE or an SAP affiliate company. All rights reserved. 7
2.2 Specify a Target Table Template

2.2.1 Background

You have identified row with the RELID and component combination that you want to transfer. You use a target
table template to transfer the data from the row to a table in the target system in a readable format.

Caution

Prior to DMIS SP11, target table templates were specified in table IUUC_INDX_OBJECT.

2.2.2 Process

The system can generate a target table template for a row. To do this, select a row and choose the Generate
Template pushbutton.

In the Template Location field, you can view the system where the template will be created. By default, the system
creates the target table template in the SAP Landscape Transformation Replication Server system. The system
creates the template in the SAP Landscape Transformation Replication Server system with the naming
convention /1LT/<Mass Transfer ID>_<Name of Component>.

Generating the Target Table Template

CUSTOMER SAP Landscape Transformation Replication Server

8 © 2020 SAP SE or an SAP affiliate company. All rights reserved. Replicating Data from Table STXL to a Target System
2.3 Map the Key Fields of Table STXL to the Target Table
Template

In order to map the records from table STXL to the corresponding fields of the target table template, you need to
map the key fields. That is, you need to map the key fields identified by the RELID and component combination to
fields in the target table template. To do this, select the relevant row, and choose the Map Key Fields pushbutton.

Choosing the Map Key Fields Pushbutton

To map the key fields of STXL (column Source Table Field Name) to the key fields of the target table template,
choose the pushbutton View Mapping Proposals.

Choosing the View Mapping Proposals Pushbutton

SAP Landscape Transformation Replication Server CUSTOMER

Replicating Data from Table STXL to a Target System © 2020 SAP SE or an SAP affiliate company. All rights reserved. 9
2.4 Activate and Save the INDX-like Table Settings

2.4.1 Process

In order for the settings to take effect during the replication process, select the Use checkbox for the RELID and
component combination TX / TLINE.

Caution
If the Use checkbox is not selected for any RELID and component combination, then the INDX-like table cannot be
replicated to the target system.

Selecting the Use Checkbox

CUSTOMER SAP Landscape Transformation Replication Server

10 © 2020 SAP SE or an SAP affiliate company. All rights reserved. Replicating Data from Table STXL to a Target System
2.5 Specify Alternative Table Name (Optional)

2.5.1 Process

By default, SAP Landscape Transformation Replication Server creates the table in the target system based on the
name of the target table template. In this example, it will create the table /1LT/113_TLINE.

If required, you can specify an alternative name, for example ZSTXL. To do this enter the alternative table name in
the column Alternative Table Name.

Column Alternative Table Name

SAP Landscape Transformation Replication Server CUSTOMER

Replicating Data from Table STXL to a Target System © 2020 SAP SE or an SAP affiliate company. All rights reserved. 11
2.6 Start the Initial Load or Replication Process for Table
STXL

2.6.1 Process

In transaction LTRC (SAP LT Replication Server Cockpit), you can start the initial load or the replication process
for the INDX-like table STXL. SAP Landscape Transformation Replication Server will transfer the data from the
INDX-like table STXL to the relevant table in the target system in a readable format.

CUSTOMER SAP Landscape Transformation Replication Server

12 © 2020 SAP SE or an SAP affiliate company. All rights reserved. Replicating Data from Table STXL to a Target System
3 Working with Rules for INDX-like Tables

Caution

Only event-based rules can be used for INDX-like tables. Field-based rules are not supported. For event-based
rules, the following events are available:
• Begin of Processing (BOP)
• Begin of Block (BOT)
• End of Block (EOT)
• End of Processing (EOP)

3.1 Using an Event-Based Rule to Change Client Number

If required, you can change the client number of an INDX table in the target system. You can do this by using an
include program.
The general process is as follows:

1. Choose event-based rule with type BOT (BEGIN OF BLOCK).

2. Insert your code by using an include program. Example code for table PCL1:

FIELD-SYMBOLS: <LS_PCL1> LIKE LINE OF _IT_IO_S_PCL1.

LOOP AT _IT_IO_S_PCL1 ASSIGNING <LS_PCL1>.

<LS_PCL1>-CLIENT = '100'.
ENDLOOP.

3.2 Using a Rule for Both the Initial Load and Replication
Process

It is possible to use an event-based rule for the initial load and for the replication process.

Example

SAP Landscape Transformation Replication Server CUSTOMER

Working with Rules for INDX-like Tables © 2020 SAP SE or an SAP affiliate company. All rights reserved. 13
You want to load and replicate the component TLINE of table STXL (RELID = 'TX') and you want to add an
additional field SYSTEM_ID (CHAR 3) to the target table. This field SYSTEM_ID is filled using an event-based rule
that can be used for the initial load and the replication process.

To do this, proceed as follows:

1. In the SAP LT Replication Server system, create a transparent table. This table must be identical to the
template structure that the system would create for table STXL in transaction LTRS (when you press the
Generate Template button in INDX-like Table Settings) but contains the additional field SYSTEM_ID. In this
example, the created table is called ZHAE_TLINE_TEMPL.

2. In transaction LTRS, add table STXL to the INDX-like Table Settings. Enter the newly created table
ZHAE_TLINE_TEMPL in column Target Table Template (it is not necessary to generate a template now). The
template location is SLT System. Map the key fields and save.

CUSTOMER SAP Landscape Transformation Replication Server

14 © 2020 SAP SE or an SAP affiliate company. All rights reserved. Working with Rules for INDX-like Tables
 In the example above, the target table will obtain the name ZHAE_STXL_TX. If you leave the column
Alternative Table Name empty, the target table name is ZHAE_TLINE_TMPL, too.

3. In the Rule Assignment section, you create an event-related filter rule for the event End of Block. The coding
of the include ZHAE_RULE_STXL is shown below.

SAP Landscape Transformation Replication Server CUSTOMER

Working with Rules for INDX-like Tables © 2020 SAP SE or an SAP affiliate company. All rights reserved. 15
 If the object _IT_IO_R_ZHAE_TLINE_TMPL can be assigned to the field symbol
<_it_io_r_zhae_tline_tmpl>, the object _IT_IO_R_ZHAE_TLINE_TMPL exists: this means the coding is
executed during the initial load of the table.

If the object _IT_IO_R_ZHAE_TLINE_TMPL_I can be assigned to the field symbol

<_it_io_r_zhae_tline_tmpl>, the object _IT_IO_R_ZHAE_TLINE_TMPL_I exists: this means the
coding is executed during the replication of the table.
In both cases, the additional field is filled with the value 'HIP'.

CUSTOMER SAP Landscape Transformation Replication Server

16 © 2020 SAP SE or an SAP affiliate company. All rights reserved. Working with Rules for INDX-like Tables
www.sap.com/contactsap

© 2020 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any
form or for any purpose without the express permission of SAP SE
or an SAP affiliate company.
The information contained herein may be changed without prior
notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other
software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company
for informational purposes only, without representation or warranty
of any kind, and SAP or its affiliated companies shall not be liable for
errors or omissions with respect to the materials. The only
warranties for SAP or SAP affiliate company products and services
are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein
should be construed as constituting an additional warranty.
SAP and other SAP products and services mentioned herein as well
as their respective logos are trademarks or registered trademarks of
SAP SE (or an SAP affiliate company) in Germany and other
countries. All other product and service names mentioned are the
trademarks of their respective companies. Please see
www.sap.com/corporate-en/legal/copyright/index.epx for
additional trademark information and notices.