conversion of logical system names -...

White Paper

ABAP Post-Copy Automation

Document Version: 2.0 – 2014-07-24

CUSTOMER

Conversion of Logical System Names BDLS Task

2

© 2014 SAP SE. All rights reserved.

Conversion of Logical System Names

Typographic Conventions

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, F2 or ENTER .


Document History

© 2014 SAP SE. All rights reserved. 3

Document History

Version Date Change

1.0 2014-07-08 Initial Version

2.0 2014-07-24 Note for multiple logical system name conversion task updated

4



Table of Contents

Table of Contents

1 Overview .......................................................................................................................................................... 5

2 Concept ........................................................................................................................................................... 6 2.1 Logical system name conversion ........................................................................................................................... 6 2.2 Conversion preparation (optimized) ..................................................................................................................... 6

3 Scenario Examples ......................................................................................................................................... 7 3.1 Multiple logical system name conversion task ..................................................................................................... 7 3.2 Running BDLS conversion with preparation task ................................................................................................. 8

4 Conversion Log Details .................................................................................................................................. 9

5 More Information ......................................................................................................................................... 10


Overview


1 Overview

The BDLS conversion task STCT_SC_CONV_BDLS is an automated procedure for converting logical system

names. The conversion is done using the programs and the logic, used in transaction BDLS. It supports multiple

name pair conversion as well as multiple client conversions. When performing multiple client conversions, the

client-dependent and client-independent table conversion is done only once, so that the amount of tables for

conversion is reduced. The task also has built-in checks that verify the parameter consistency. You use this task

to simplify and to reduce the manual effort when converting logical system names, thereby avoiding errors during

this procedure.

The optimize BDLS task STCT_SC_PREPARE_BDLS is optional and complementary to the BDLS conversion task.

This task determines all tables that are relevant for the conversion by executing report RBDLS_CHECK. It

analyzes the system and collects detailed table information for optimizing the actual conversion task. It is

recommended that you run this task in the preparation phase, before the actual conversion runs. By default, the

standard tables are processed in parallel batch jobs.

Note

The BDLS conversion and preparation tasks are part of ABAP post-copy automation (PCA). ABAP PCA is

part of SAP Landscape Virtualization Management, enterprise edition software. SAP Landscape

Virtualization Management is an add-on to SAP NetWeaver 7.3 and SAP NetWeaver 7.4.

To use ABAP PCA, you must own an SAP Landscape Virtualization Management, enterprise edition

license. For more information, see the Installation and Configuration Guides for ABAP PCA on SAP

Service Marketplace at http://service.sap.com/isntlvm.

6




Concept

2 Concept

2.1 Logical system name conversion

The task uses the standard BDLS program to convert the logical system names. The conversion is divided into the

following phases:

Standard table conversion

Standard tables are processed using program RBDLSMAP. The conversion jobs are executed in parallel. To

speed up the conversion, it is recommended that as many batch work processes are configured as possible.

Special table conversion

Special tables, for example very large tables are processed at the end using an SAP-specific and a customer-

specific program. For standard SAP tables, they are defined in table BDLSEXT and for customer-specific

tables, in table BDLSEXZ. This is also then processed by program RBDLSMAP.

By configuring the RFC destination, it is possible to execute remote client conversions in the local system. With

this function, the client-dependent and client-independent table conversions are done only for the first client.

Succeeding client conversions are done only for client-dependent tables.

Note

Special table conversion is also executed per client when performing multiple client conversion.

Therefore, customer specific programs must be adjusted to avoid being executed multiple times.

Logical system name pairs are processed one pair after another during the multi-pair conversion. Similarly, for

multi-client conversion clients are also processed one after the other.

2.2 Conversion preparation (optimized)

The optimize BDLS conversion task executes the program RBDLS_CHECK; this generates a list of relevant tables

and the number of entries of the old logical system name in the corresponding table. This information can then be

used to execute the conversion task. Since the conversion task has specific input, it runs the conversion more

efficiently by processing only the relevant tables.


Scenario Examples


3 Scenario Examples

3.1 Multiple logical system name conversion task

The conversion of multiple name pairs is possible by specifying the old and new name in the logical system name

mapping, in the multiple selection fields.

Note

The multiple selection fields can contain predefined names from other tasks, such as the BW task Select

System Connections to be Retained After Copy or the optimize BDLS task. It is recommended

that you check and validate the multiple selection entries. For more information, see chapter

Configuration for System Refresh of BW/BW Source Systems or chapter Configuration for Initial Copy of

BW/BW Source Systems in the BW post-copy automation guide on SAP Service Marketplace at

http://servcie.sap.com/instlvm.

The task multiple selections UI supports include and exclude table functions for specific table conversions.

Depending on your database and your database roll area settings, set the number of entries per commit

parameter as large as possible. Making this parameter larger than that supported by your database can cause

runtime errors. Since diverse database platforms are in-use today, it is recommended that you further use your

preferred parameter, the number you currently use.

Depending on the given parameters, the following job execution mode can either be selected or is predefined by

the task.

Single job execution

The conversion is done exactly as in the case of transaction BDLS. The tables are processed sequentially

using program RBDLSMAP. An example of a created job is SAP_SCTC_BDLSMAP_000, where all tables can be

displayed in a spool list.

Concurrent jobs based on table name

The tables are grouped alphabetically or with special characters which are predefined as follows:

A – V: One job for each character

/A - /B: One job

/C - /I: One job

/J - /Z: One job

W – Z, 0 – 9, /0 - /9: One job in total

Each table-set is assigned to a conversion job and can run independently using program RBDLSMAP. 26 jobs are

created and run in parallel to convert the standard tables.

Example of created batch jobs

SAP_SCTC_BDLS000_1001 - All tables starting with letter A (A*) are converted.

SAP_SCTC_BDLS000_1026 - All tables starting with letters W to Z and numbers 0 to 9 are converted.

SAP_SCTC_BDLSMAP_000 - Special tables are converted with program RBDLSMAP.

Concurrent jobs based on table entry

http://servcie.sap.com/instlvm

8




Scenario Examples

- Use Optimize BDLS Conversion Task - see Section 3.2.

Consistency checks are always done before the task execution. To explicitly determine whether all parameters are

OK, choose the Check Task list Run button. This checks the RFC destinations if defined, whether correct

authorizations are set in the target client, and whether the RFC connection is working properly.

A direct link to display the current job logs is available by selecting Details at the end of the task log.

3.2 Running BDLS conversion with preparation task

The optimize BDLS task must first be added manually to the standard BDLS task list. To optimize the conversion

time, run the preparation task before the conversion task. Relevant tables resulting from the analysis are

automatically transferred to the conversion task as input parameters. Use the multiple selection of single values in

the preparation task UI to specify the old logical system names intended for conversion. The old logical system

name must be configured in transaction BD54. Select cross-client when performing multi-client conversion to

include configured names in the target client.

Optimize BDLS task results is an important piece of data that is used for the actual BDLS conversion task. The

result can be displayed in the Details link of the task log. It shows the corresponding client, the configured logical

system name, the table name where it is located, field names, and corresponding entries in the database row

count.

The result data is transferred automatically to the conversion task for execution. The old logical system names

and the relevant tables are then copied to the corresponding fields. Entering the matching new logical system

name and RFC destination (if required) completes the parameter input. The transferred parameters can be

displayed in the Details link of the conversion task log. The relevant tables are displayed.

The concurrent job based on table entry mode is only selectable and predefined when preparation task results are

available. The tables are grouped depending on the results determined by the task. The rule is to distribute the

batch jobs according to the table entry size. Tables with higher number of entries have higher priority to get their

own batch job assignment.

Example of created batch jobs

SAP_SCTC_BDLS000_2001 - The table with the highest amount of entries is converted.

SAP_SCTC_BDLS000_2004 - The tables with the lowest amount of entries are converted.

To speed up the conversion, it is recommended that you configure as many batch work processes as possible.

The consistency check verifies whether the transferred parameters have been changed and with that are no

longer identical with the preparation results.

Removed parameters are logged as message with a warning.

Parameter must not be added. To keep data consistent, adding parameters is logged as message with an error.


Conversion Log Details


4 Conversion Log Details

The conversion task log Details link takes you directly to the batch job overview with the corresponding date and

time stamps of the corresponding task run. It shows the exact jobs created by the conversion task provided that

the batch jobs are still accessible.

The details of the processed tables can be displayed as follows:

1. Select the spool icon.

The spool list displays the corresponding program name, for example RBDLSMAP.

2. In the output controller, select the ABAP list icon (below the type column).

Unhighlighted table names indicate that the table was processed with the corresponding field name, number

of relevant entries, and the number of converted entries. You can see the special conversion details in the last

job SAP_SCTC_BDLSMAP_000 only.

3. To display the exact parameters used for the actual conversion, go back to the job overview.

4. Double click the job name, for example SAP_SCTC_BDLS000_1002.

5. Select Step.

6. Select the program name.

7. To display the used BDLS program variant, go to Variant.

10




More Information

5 More Information

For more information about using the post-copy automation content to configure extensive technical

scenarios automatically, see the ABAP post-copy automation configuration guide on SAP Service

Marketplace at http://service.sap.com/instlvm.

For more information about the BDLS conversion task STCT_SC_CONV_BDLS and the BDLS preparation task

STCT_SC_PREPARE_BDLS, see the description which is available in the Help column of the task lists.

For more information about transaction BDLS, search for Conversion of Logical Systems within your SAP

NetWeaver release on SAP Help Portal.

http://service.sap.com/instlvm

www.sap.com/contactsap

Material Number


No part of this publication may be reproduced or transmitted in any

form or for any purpose without the express permission of SAP SE.

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.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered

trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System ads, System i5, System

p, System p5, System x, System z, System z10, System z9, z10, z9,

iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS,

S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise

Server, PowerVM, Power Architecture, POWER6+, POWER6,

POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,

BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2

Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,

Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are

trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and

other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either

trademarks or registered trademarks of Adobe Systems

Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the

Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,

VideoFrame, and MultiWin are trademarks or registered trademarks

of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered

trademarks of W3C®, World Wide Web Consortium, Massachusetts

Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc.,

used under license for technology invented and implemented by

Netscape.

SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge,

ByDesign, SAP Business ByDesign, and other SAP products and

services mentioned herein as well as their respective logos are

trademarks or registered trademarks of SAP SE in Germany and in

several other countries all over the world. All other product and

service names mentioned are the trademarks of their respective

companies. Data contained in this document serves informational

purposes only. National product specifications may vary.

These materials are subject to change without notice. These

materials are provided by SAP SE and its affiliated companies ("SAP

Group") for informational purposes only, without representation or

warranty of any kind, and SAP Group shall not be liable for errors or

omissions with respect to the materials. The only warranties for SAP

Group 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.

conversion of logical system names -...

Documents