SAP TDMS 4.0 How to Carry Out Shell Creation

How-To Guide

Document Version: 1.1 2013-08-08

CUSTOMER

How To Use Shell Creation for SAP Test Data Migration Server Release 4.0

2

2012 SAP AG. All rights reserved.

How To Use Shell Creation for SAP Test Data Migration Server

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.

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 .

SAP Test Data Migration Server 4.0

Document History 2012 SAP AG. All rights reserved. 3

Document History

Version Date Change

1.0 2011-10-31 First version of the guide.

1.1 2013-08-08 New standard template for the guide

4



Table of Contents

Table of Contents

1 Business Scenario .......................................................................................................................................... 5 1.1 Understanding Shell Creation ................................................................................................................................ 5 1.2 Prerequisites ............................................................................................................................................................ 5

2 Step-by-Step Procedure ................................................................................................................................ 6 2.1 Preparing for a System Copy ................................................................................................................................. 6 2.2 Creating a Control File ............................................................................................................................................. 7 2.3 Defining Environment Parameters and Excluding Tables ................................................................................... 7

2.3.1 Maintaining the Target Database and Installation Directory .............................................................. 8 2.3.2 Determining the Tables to Be Excluded from Export .......................................................................... 8 2.3.3 Viewing the Size and Name of the Largest Tables (Optional) ............................................................ 8 2.3.4 Modifying the Control Files to Exclude Tables ..................................................................................... 8

2.4 Carrying Out the Database Export ......................................................................................................................... 9 2.5 Determining the Initial Size for Tables and for the Database ............................................................................. 11

2.5.1 Defining the Export Directory ............................................................................................................... 11 2.5.2 Retrieving the Table Size ....................................................................................................................... 11 2.5.3 Modifying the Table and Index Sizes ................................................................................................... 12 2.5.4 Calculating the Database Size in the Receiver System ..................................................................... 13 2.5.5 Updating the Control Files with a Modified Size for Tables and the Database ................................ 13

2.6 Carrying Out the System Copy ............................................................................................................................ 14 2.7 Creating a Reference Client and Installing SAP TDMS ...................................................................................... 14 2.8 Deleting Non-Relevant User and Address Data in the Receiver System .......................................................... 14


Business Scenario

2012 SAP AG. All rights reserved. 5

1 Business Scenario

You use SAP TDMS Shell Creation to set up the receiver system, which acts as a target system for other TDMS

migration solutions.

1.1 Understanding Shell Creation

A system shell is an SAP system that contains only cross-client data and the required client specific user and

address data (client 000), but no other client-specific data. From a technical perspective, a system shell only

contains SAP Basis tables and the table structures of other database tables.

Consequently, system shells are typically meant to be used as receiver systems for TDMS runs. Depending on

your specific requirements, you can also use a system shell as a development system.

SAP TDMS provides a process to create a system shell. The process combines the standard SAP System Copy

function (homogenous system copy with R3 load) with the reduction logic included in SAP TDMS. The shell

creation logic checks which tables can be excluded for the copy process. Only structures (not data) are

downloaded for these tables.

If the system you want to copy contains a lot of application data, we recommend that you create a system shell

rather than a standard system copy. In such cases, since Shell Creation does not transfer application data, the

amount of data for transfer is much smaller than for a system copy. Hence, the export and import takes less time.

1.2 Prerequisites

You are familiar with the process for creating a homogeneous system copy with R3Load.

You have ready access to the SAP System Copy Guide for the relevant database and system release.

You have ensured that all requirements and prerequisites described in the SAP System Copy Guide for the

relevant SAP release and database system are fulfilled.

You have made arrangements to have technical consultant who is specifically certified for SAP System Copy

carry out the system copy procedure onsite. We recommend an onsite technical consultant regardless of

whether the system to be migrated is a development system, a test system, or a production system. Having

the consultant available readily ensures that sufficient know-how is available to handle the complexity of the

procedure.

6



Step-by-Step Procedure

2 Step-by-Step Procedure

The Shell Creation process is used to copy all the application independent data from one system to the other

system. The standard SAP system copy process that uses SAPINST is at the core of the Shell Creation process.

2.1 Preparing for a System Copy

Carry out all preparations as described in the System Copy Guide for the appropriate database system and SAP

release. For shell creation, the homogenous system copy method with R3Load must be used. You can find the

current versions of all available system copy guides on SAP Service Marketplace at

http://service.sap.com/systemcopy

Some of the important steps in the System Copy Guide are:

Preparation of the hardware in the target system, for example, sufficient disk space.

Preparation of the software in the target system, for example, DB instance and appropriate SAP kernel.

Availability of all required CDs and DVDs for the system copy in the appropriate version.

1. Provide the system details for the sender system, the control system, and the receiver system (R3 logins, OS

logins for ADM and root).

2. Create statistics in your source database. If you have up-to-date statistics available, you can skip the step in

which R3SETUP/SAPINST creates statistics in the source database in preparation for the export.

3. Provide all media that are necessary for the installation of a database instance in the receiver system.

4. Provide a local R3SETUP/SAPINST directory in the sender system and in the receiver system. You can start

the setup tools from this directory. Each directory should be 300 MB in size.

5. Provide up-to-date versions of R3LOAD, R3LDCTL and R3SZCHK in your kernel directory.

You can find details about R3SZCHK in SAP Note 1047369:- Faster DB Accesses for R3szchk Using Oracle

DBSL.

6. Provide a directory or share via NFS export in the sender system and the receiver system to store the export

data. For a normal system copy, 10% of the database size is sufficient, but it may be necessary to extend this

space. For a shell system copy, even less space may be required due to the reduced tables. Since an import

via NFS is not officially recommended by the System Copy Guide, for best results, provide local storage on the

receiver system as a target for the database import.

7. Provide contact persons for the areas of SAP Basis Administration, OS Admin and DB Admin, who can take

care of any issues in their respective areas in a timely manner.

8. Carry out the following checks:

Ensure that the receiver system already exists (that is, the central instance is installed) and has the same

release level as that of the sender system. If the receiver system does not yet exist, pre-install an installed and

patched database parameterized in accordance with SAP recommendations on the target server. You can

either copy the export directory to the system (which would require sufficient local disk space) or mount it via

NFS in advance. However, we do not recommend the use of NFS.

Ensure the consistency of the ABAP Dictionary and the database of the source system. In particular, make

sure that no objects (tables, indexes) existing in the database are missing from the ABAP Dictionary and vice




versa. If there are differences that you can tolerate, you can edit DBDIFF accordingly (transaction DB02 ->

Checks -> Database -> ABAP Dictionary). Create any missing objects in the database.

For more information, see SAP Note 33814 - Warnings of inconsistencies between database & R/3 DDIC.

If an object is not required any longer, delete it from the database or enter it in table DBDIFF. Also, create

objects that are missing at the database level and only exist in the dictionary in transaction DB02.

9. Important Information for UNIX operating systems:

The ADM user on the Unix operating system must have file access permissions to read and write all files

under the installation directory (for example, the files DBEXPORT.R3S or DDL*.TPL) and under the export

directory (for example, the files *.EXT or *.STR). Otherwise, some activities can end with an error.

Note

Ensure that you carry out the export from the database server.

2.2 Creating a Control File

Create the control files required for the system copy on the server of the source system. Ensure that these files

are saved in the folder where the SAPinst is to be run (mentioned in the System Copy Guide as

or "installation directory."

1. Log on to the operating system as user ADM.

2. Go to the folder mentioned above and start R3ldctl with the following parameters:

-l

-p

Note

Ensure that you always use the same SAPINST directory during the export process. When you later start

SAPINST for the export, remember to change to cd /mysapinstdirectory. You can then start SAPINST

from this directory.

2.3 Defining Environment Parameters and Excluding Tables

In this phase, you prepare for the data export from the source system and create control data for the system copy

process that is specific to shell creation.

Process Flow

1. Specify the required system parameters.

2. Specify the tables whose content you want to exclude from the system copy.

3. Export the required information for the tables whose content you want to exclude.

Note

For SAP Release 4.6C, the export of the information is a part of the next phase.

8




2.3.1 Maintaining the Target Database and Installation Directory

Shell Creation programs and activities must know the location of the control files belonging to the system copy

tools, for example, the installation directory.

In this activity, define the required parameter values for shell creation.

Note

o The target DB system is the target system database system.

o The Installation directory is in the sender system.

2.3.2 Determining the Tables to Be Excluded from Export

This activity locates the tables whose contents are not meant to be copied (for example, most client-specific

tables). This activity ensures that only the contents of tables that are actually needed in the shell system are

exported.

Nevertheless, the activity copies the table definitions of the excluded tables. In other words, the activity creates

the structures of the tables without any content.

2.3.3 Viewing the Size and Name of the Largest Tables (Optional)

This optional activity locates the tables that are to be exported with their complete dataset and which contain a

very large number of records. The export process for these large tables can take very long. The function checks a

set of tables in the sender system for their respective size. In general, the activity evaluates most of the text tables

(STX*).

To improve the performance of the export process, you can split up the large tables using standard SAP splitting

tools (such as R3TA) before starting the export. Using the table splitting option does not have any impact on the

end result, but can result in a significant performance improvement.

2.3.4 Modifying the Control Files to Exclude Tables

This activity adds the exclusion information of the tables defined as to be excluded to the control files. The

exclusion information is available with the earlier activity Determine Tables to be Excluded from the Export.

This activity execution differs according to the Basis release of the system:

1. First, the activity copies the files containing entries that are defined in the CNVTDMS_13_EXCTB table.

2. For each affected 4.6C "STR" (structure) file, the activity creates a backup STR.SAVE.

In releases after 4.6C, the activity saves a single TPL file under < SAVEDDL > < DB system > < .TPL >.




Note

The activity only creates the SAVE files if changes are made, thus aiding transparency.

3. Under release 4.6C, the STR files are altered. Here, the program searches through the files and deletes any

tables or indexes found in the CNVTDMS_13_EXCTB table.

4. In releases after 4.6C, you have to modify the TPL file based on entries from the CNVTDMS_13_EXCTB table

added following the appropriate command negdat, negtab or negind.

Note

The 4.6C STR files are under the export directory and after this release the files are under the installation

directory.

5. If you repeat the activity, the activity reads and alters the SAVE files before writing them back as an STR or

TPL file.

Important Information for UNIX operating systems:

The ADM user on the UNIX operating system must have the file access permissions to read and write all

files under the installation directory (for example, the files DBEXPORT.R3S or DDL*.TPL) and under the

export directory (for example the files *.STR). Otherwise this activity ends with an error.

For release 4.6C, errors are generated during the activity for obvious problems (such as incorrect code

generation). Other messages can be generated, most commonly, the message informing that no changes

were made to a file.

The message has the following appearance: xxxxxxx.STR // No changes made to file.

This information is provided simply to improve the transparency of the transaction. This message, combined

with the creation of the SAVE files, allows the user to see exactly what has taken place.

2.4 Carrying Out the Database Export

Proceed with the database export as described in your System Copy Guide. Carry out the steps described in the

relevant chapter (R3load Procedures or Database Independent System Copy) of the System Copy Guide..

Note

Ensure that you carry out the instructions for R3LOAD and not the database.

Proceed until the export of the database is completed (until Setting Up the Target System).

Note

Do not start the import step or preparation since you are required to execute more steps in the

package before the actual import can be done.

10




R3LOAD Restrictions

SAPinst generates a database dump of all SAP objects that are defined in the ABAP Dictionary. Other objects are

not exported by SAPinst.

Changes to database objects that were not maintained in the ABAP Dictionary (transaction SE14), such as the

distribution of tables over several tablespaces/dbspaces, are lost after the system copy.

No indexes longer than 18 characters are allowed on the database to be exported.

No transactions on export-relevant database objects are allowed by the process during the export to ensure a

consistent database export. Failure in this regard results in a restart of the export process.

Hence, we recommend that you shut down the SAP system for the export. However, ensure that the database

is still running.

Activities Related to the System Copy Tools

During the standard system copy process, group all tables of the SAP system into packages, so that all tables

with the same data class belong to the same package. The processing unit for one unload/load process is a

package.

Every installation service (dialog instance installation, for example) must have its own separate installation

directory whenever you start SAPinst.

Package Splitting

Do not use the option to split the STR files (the package splitting option). This might lead to an empty export

file. Splitting is only recommended for non-excluded tables.

Do not carry out package splitting for any package that is empty (that is, a package with no export data).

SAPinst Working Directory

Make sure that the working directory of SAPinst is the previously defined installation directory ().

Migration Monitor

If the Migration Monitor is used or called from SAPinst, you must make sure that the modified .TPL file from

the installation directory () is used by SAPinst.

As of NetWeaver '04 SR1, the Migration Monitor is integrated into SAPinst and called by default. In this case,

select the option to start the Migration Monitor manually.

Call the Migration Monitor with the following additional parameter:

ddlFile = /DDL.TPL ( = the database you selected in the previous

activity).

You can add the parameter to the parameter file export_monitor_cmd.properties.

Starting the System Export

For SAP Release 4.6C, Use R3setup to start the system export. In this case, the R3setup stops the execution

after R3szchk has finished. Before continuing with the R3setup, complete the steps listed in the later sections

of this shell creation guide.

The information activity Export the Database in the process tree for Shell Creation provides information about

when you can continue with the R3setup.

If you are using the shell creation for a BW system, refer to the note below for potential problems that may

arise if the correct system copy procedures are not followed during the shell creation of TDMS BI.




The data loads to some infocubes may result in duplicate key errors. Follow the instructions in the note provided

below to avoid this error.

Caution

Follow the instructions provided in the SAP Notes 942540 and 771209. If you do not follow this note, the

import of SAPDFACT could fail with BCP errors. These notes specify some steps to be followed before

export and some steps to be followed after export but before import.

2.5 Determining the Initial Size for Tables and for the Database

In this phase, SAP TDMS determines the initial size of all excluded tables and the initial database size of the shell

system. This is necessary because the system copy tool uses the original size values from the sender system.

If it is not required to reduce the initial table and database size of the shell system, you can skip this phase.

Note

In case of SAP Release 4.6C, you cannot skip the entire phase. Carry out the steps until and including

activity Export the Database - Continuation (TDSHL_EXPORT_SOURCE_SYSTEM_CONTINUE).

Process Flow

1. Specify the export directory.

2. In case of SAP Release 4.6C, export information about the excluded tables and continue the R3setup export

step.

3. Import the original table and index sizes from the sender system.

4. Calculate the expected size of the tables and indexes in the shell system.

5. Calculate the expected total database size in the shell system.

6. Export the table and database sizes for the shell system to the control files.

2.5.1 Defining the Export Directory

In this activity, declare the export directory. The export directory is the directory where the R3load dump files are

located. The export directory contains the subdirectories DATA, DB and DB/ (for example,

ADA, ORA, MSS, DB2, DB4, DB6) that is, the directory to which the copy tool (SAPinst/R3load) has saved

the exported data.

2.5.2 Retrieving the Table Size

This activity carries out the following steps:

12




Reads the original table and index sender system sizes from the EXT files.

Writes the values to the CNVTDMS_13_EXCTB table.

Stores the database-specifc files in the export directory : / DB / .

Adds the index entries which are to be excluded from the table CNVTDMS_13_EXCTB (this is the same table

used by the activity Determination of Tables to Be Excluded from Export, which adds tables to be exported).

Determines the initial size of the tables and indices in the shell system based on the above data.

2.5.3 Modifying the Table and Index Sizes

This activity determines the initial table and index size in the shell system. Each table and index has the same size

as in the sender system unless a method is specifically selected. An exception is the COPY method.

In this activity, you can assign a calculation method to the excluded tables. This calculation method is in turn used

by the copy process to calculate the reduction ratio for the tables whose data are excluded from export. Data size

reduction depends on the selected method.

These customizing entries can be defined by the user but SAP delivers general entries in the self-explanatory

CNVTDMS_13_SIZE table. As mentioned, you can define your own methods (see the maintenance dialog for the

table). If you do not assign a method to a table, the Shell Creation process creates the table with the same size as

in the source system by the copy process.

You can assign a method by selecting a standard template or a package template. Predefined templates are

available for the TDTIM and TDMDC packages and all user-defined packages.

If you select a template, all size determination methods are copied by the activity to the corresponding excluded

tables and indices. TDTIM is the default package. The first time the activity is run, the TDTIM values are selected

by the activity and an information message is displayed.

You can choose to assign methods manually.

Template Maintenance:

Templates are located in table CNVTDMS_13_TEMPL. You can maintain the templates and the migration solution in

the table in transaction CNVTDMS_13_TEMPL.

The Shell Creation process automatically assigns the template you specify to a shell creation package and the

relevant migration solution.

For each TDMS migration solution, you can create a size template. The activity Modifying the Table and Index

Sizes selects the appropriate size template for the migration solution. The activity also includes all entries you

make for the migration solution in the template.

Use of the Field METHOD:

This field specifies the method to determine table size in the shell system. The size of tables in the shell system

can be different from the size of tables in the source system. To determine the size of a table in the shell system,

you can assign a method. The table size value of the shell system is calculated by the function and the value of this

method during the shell creation process.

Predefined methods and user defined methods can be used in this field.

The method ' ' (space) is equal to method COPY; both are assigned to the function COPY. Methods ' ' (space) and

COPY copy the source size to the shell system size.

Only predefined operators can be used while defining the function of a method (for example: copy, ratio, value).




Use of the Field TABLENAME:

This field specifies a table in a size template for excluded tables.

If you swap between different modes, that is, between the All Values and Template or Assigned Values and

Template, a dialog box appears where you need to confirm any changes you made. The message can appear even

if you have not made any explicit changes since the CNVTDMS_13_SIZE values were calculated by the activity with

the selected tables, resulting in a change of state. Choosing Save causes the CNVTDMS_13_EXCTB to be modified

with the currently selected data.

After you select a new template using the input help, press ENTER twice to refresh the field values: the first time

to leave the dialog box that prompts you to press ENTER twice, and the second time to refresh the screen

contents.

The Template Name field may include a value even if you do not select the Template option. In this case, the values

displayed are originally derived from the named template. However, if you reselect the template a dialog box

appears asking you to save your entries. SAP TDMS refreshes the currently displayed values with the newly-

selected and calculated template values.

The COPY method results in the shell size being copied from the source size. Since this has the same effect as

leaving the method blank, the COPY value is suppressed from the method field.

When you execute the activity, you can maintain the table entries for each migration solution. Save your entries

and return to the migration package.

2.5.4 Calculating the Database Size in the Receiver System

This activity calculates the size of all excluded tables and indexes in the sender system and the shell system. The

activity displays the difference between the two as the reduction value.

The function shows the database size of the sender system. This value is taken by the activity from the system

copy control file. The activity calculates a recommended database size for the shell system by subtracting a

percentage difference from the sender system size. This difference is calculated by cumulating the differing sizes

of the exclude tables in the sender and shell systems. You can, however, change this value.

If this activity runs on a database system IBM DB2 UDB for iSeries or IBM DB2 UDB for zSeries, no database size

is calculated. Instead, only the reduction value is displayed.

2.5.5 Updating the Control Files with a Modified Size for Tables and the Database

In preparation for the system copy import step, this activity exports the table/index and database sizes of the

shell system (as defined in the previous activities) to the respective control files.

Important Information for UNIX operating systems:

The ADM user on the UNIX operating system must have the file access permissions to read and write all

*.EXT, .XML and .TPL files in the directory export_directory/DB/. Otherwise, this activity ends

with an error and the export of the table sizes does not take place.

This activity is not necessary for the database system DB2 for zOS.

14




2.6 Carrying Out the System Copy

Proceed with the standard system copy process as described in the System Copy Guide. Start with the transfer of

the export files to the target host (chapter Transferring the Export Files to the Target Host) and complete the

system copy as described in the System Copy Guide.

Keep in mind that some reports and transactions are not required here (and may terminate) because most of the

application data is not copied by the shell creation process to the shell system. For example, the checks for

financials data described in chapter Final Activities do not work here.

2.7 Creating a Reference Client and Installing SAP TDMS

In this step, you complete the reference client 000 of the shell system and make DMIS and other add-on

components available. This step is necessary to retrieve the following information:

The SAP Standard Customizing of client 000

The Add-on data if TDMS and other Add-ons that are used in the shell system.

Perform a client copy (client export, import) from the sender to the shell system on the reference client (client

000).

Because a remote client copy into client 000 is not possible, use transaction SCC8 to export the client. Use client

copy profile SAP_ALL. When the export is completed, import the client copy transports to client 000 in the shell

system (transaction STMS).

2.8 Deleting Non-Relevant User and Address Data in the Receiver System

Due to the shell creation procedure and the implemented handling of the user and address data, the following

situation exists in the shell system:

All address data (for user and business objects) is available in all clients of the shell system in the same way

as for the source system.

All user data and related data is available in all clients of the shell system in the same way as for the source

system.

RFC users and users for background processes are also available and can be used.

To prepare the shell system for further use, you must carry out some clean-up tasks. These tasks are

described below.

We recommend that you proceed as follows to clean up the shell system:

1. Delete unnecessary clients (using transaction SCC5).

2. Clean up user data and related data in the available clients.

3. Check the user records in all existing clients and lock or delete unnecessary user records.

4. Clean up the address data (delete all addresses except the user addresses):

o To clean up the address data for a client, you can run a TDMS Standard Deletion Package (TDDEL) for

this client.




o To clean up the address data for a client, you can also delete the client (using transaction SCC5) and then

copy it again from the source system (using transaction SCC9 and copy profile SAP_UCSVA TDMS

process is typically divided into phases that impact the sender system and the receiver system. The

sender system is a critical system because it is typically the production system, which is heavily used by

many users who expect a fast response time and no system downtimes. Hence, the use of snapshots

should minimize the impact of SAP TDMS runs on the sender system.

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

The information contained herein may be changed without prior

notice.

Some software products marketed by SAP AG 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 AG 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 AG 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.

Documents

SAP TDMS 4.0 How to Carry Out Shell Creation