Data Migration of Non-SAP Systems To R/3: September 5, 2000

Data Migration of Non-SAP Systems to R/3
Quick Introduction to Working with the Legacy System Migration Workbench Version 1.7
lsm@sa .com Se tember !" #$$$
Legacy System Migration Workbench
Table of Contents
1 INTRODUCTION................................................................................................................................................4 1.1 PURPOSE OF THIS INTRODUCTION.............................................................................................................. 4 1.2 LSM WORKBENCH: WHAT IS IT?.............................................................................................................. 4 1.3 SUPPORTED R/3 RELEASES....................................................................................................................... 4 1.4 COSTS...................................................................................................................................................... 4 1.5 DELIVERY................................................................................................................................................ 4 1. LSM WORKBENCH VERSIONS................................................................................................................... 4 1.! SUPPORT.................................................................................................................................................. 5 1." SI#NIFICANCE OF DATA MI#RATION......................................................................................................... 5 1.$ BASIC PRINCIPLES OF THE LSM WORKBENCH ..........................................................................................5 2 PRECONDITIONS..............................................................................................................................................7 3 STARTUP AND PREPARATIONS...................................................................................................................8 3.1 AUTHORI%ATIONS..................................................................................................................................... " 3.2 INITIAL TRANSACTION.............................................................................................................................. " 3.3 PRO&ECT' SUBPRO&ECT AND OB&ECT......................................................................................................... " 3.4 USER #UIDANCE...................................................................................................................................... $ 3.5 FIELD MAPPIN# ON PAPER...................................................................................................................... 11 3. CREATE OB&ECT OVERVIEW................................................................................................................... 12 3.! ADMINISTRATION................................................................................................................................... 1 3." RECORDIN#S.......................................................................................................................................... 1 3.$ PREPARATIONS FOR USIN# IDOC INBOUND PROCESSIN#..........................................................................1! 4 GENERAL TIPS FOR THE PROCEDURE...................................................................................................21 5 DATA MIGRATION STEP BY STEP.........................................................................................................23 5.1 MAINTAIN OB&ECT ATTRIBUTES............................................................................................................. 23 5.2 MAINTAIN SOURCE STRUCTURES............................................................................................................ 24 5.3 MAINTAIN SOURCE FIELDS..................................................................................................................... 25 5.3.1 Create Individual Source Fields...........................................................................................................25 5.3.2 Maintain Source Fields in Table Form.................................................................................................31 5.3.3 Copy Source Fields from Ot er Sources...............................................................................................32 5.4 MAINTAIN STRUCTURAL RELATIONSHIPS................................................................................................ 33 5.5 MAINTAIN FIELD MAPPIN# AND CONVERSION RULES..............................................................................35 5.5.1 For t e !dvanced "ser# $isplay %ariant& 'rocessin( Times...............................................................3) 5.5.2 For t e !dvanced "ser# *lobal %ariables...........................................................................................+, 5.5.3 For t e !dvanced "ser# *lobal Functions...........................................................................................+, 5.5.+ For t e !dvanced "ser# -eusable -ules . /amin( Conventions.......................................................+1 5. MAINTAIN FI(ED VALUES' TRANSLATIONS AND USER)WRITTEN ROUTINES.................................................................................................................................................... 43 5.! SPECIFY FILES....................................................................................................................................... 4 5." USE WILDCARDS IN FILE NAMES............................................................................................................ 53 5.$ ASSI#N FILES........................................................................................................................................ 55 5.1* READ DATA........................................................................................................................................ 55 5.1,.1 $isplay -ead $ata..............................................................................................................................50 5.11 CONVERT DATA.................................................................................................................................. 5 5.11.1 *eneral -emar1s.................................................................................................................................50 5.11.2 !dditional Function for 2!'I3I$oc....................................................................................................5) 5.12 DISPLAY CONVERTED DATA................................................................................................................. 5" 5.13 IMPORT DATA...................................................................................................................................... 5" 5.13.2 Import $ata 4it $irect Input.............................................................................................................55 5.13.3 Import $ata 4it 2!'I or I$oc Tec ni6ue........................................................................................0, 6 RECORDINGS...................................................................................................................................................61 .1 DETAILED DESCRIPTION OF THE PROCESS............................................................................................... 1 7 TRANSPORT LSMW PRO ECTS..................................................................................................................64 !.1 #ENERATE CHAN#E RE+UEST................................................................................................................ 4 !.2 E(PORT PRO&ECT................................................................................................................................... 4 2
Legacy System Migration Workbench !.3 IMPORT PRO&ECT.................................................................................................................................... 5 8 PERIODIC DATA TRANSFER.......................................................................................................................66 ! LONG TE"TS....................................................................................................................................................7# $.1 LON# TE(TS IN THE R/3 SYSTEM........................................................................................................... !* $.2 DETERMINE TE(T KEY STRUCTURE........................................................................................................ !1 $.3 DEVELOP OB&ECTS FOR LON# TE(TS VIA OB&ECT ***1...........................................................................!2 $.4 DEVELOP OB&ECTS FOR LON# TE(TS VIA OB&ECT 2***...........................................................................!5 $.5 IMPORT TE(TS....................................................................................................................................... !$ 1# TIPS AND TRIC$S.........................................................................................................................................8# 1*.1 DETERMINE THE TRANSACTION CODE AT RUNTIME..............................................................................."* 1*.2 SKIP A RECORD................................................................................................................................... "* 1*.3 SKIP ALL RECORDS OF A TRANSACTION............................................................................................... "* 1*.4 DUPLICATE A RECORD......................................................................................................................... "* 11 UPGRADE FROM LSMW 1.# TO LSMW 1.6............................................................................................82 11.1 DIFFERENCES BETWEEN VERSION 1.* AND VERSION 1.
OF THE
LSM WORKBENCH.............................."2
12 TRANSFER OF LSMW DATA FROM %ERSION 1.# TO %ERSION 1.6...............................................84 13 UPGRADE FROM LSMW 1.5 TO LSMW 1.6............................................................................................85 13.1 NOTES ON THE UP#RADE TO LSMW 1. ............................................................................................... "5 13.2 CORRECTIONS..................................................................................................................................... "5 13.3 DEVELOPMENTS.................................................................................................................................. "5 14 FINAL REMAR$S..........................................................................................................................................87
1 Introd !tion
1"1 P r#ose of t$is Introd !tion
This introduction is intended to allow a quick entry into the work with the Legacy System Migration Workbench Version 1.6 ( LSM Workbench !.
1"2 %SM &or'ben!$( &$at is it)

The LSM Workbench is an "#$%based tool that su&&orts 'ou when trans(erring data (rom non%S)* systems ( Legacy Systems ! to "#$ once or &eriodically. The tool su&&orts con+ersion o( data o( the legacy system in a con+enient way. The data can then be im&orted into the "#$ system +ia batch in&ut, direct in&ut, -)*.s or ./ocs. 0urthermore, the LSM Workbench &ro+ides a recording (unction that allows to generate a data migration ob1ect in an entry or change transaction.
1"3 S ##orted R/3 Releases

Version 1.6 (this +ersion! o( the LSM Workbench can be used in "#$ systems with the (ollowing maintenance le+els2 *"+A, *"+-, *".A, *".-, *"/A, *"/- and *"/C" 0or maintenance le+els earlier than 3.4 &lease use +ersion 1.4 o( the LSM Workbench.
1"* Costs
S)* makes this tool a+ailable to their customers and &artners %ree o% charge.
1". Deli0ery
The LSM Workbench is not &art o( the standard "#$ system. .( you are interested in this &roduct, &lease contact S)* +ia2 S)*5et (6nline Ser+ice System!2 8mail2 0a:2 S)*5et2 com&onent 77%LSM or or
lsm9sa&.com ;3<%6==>%>3=?<4
htt&2##ser+ice.sa&.com#lsmw
There you (ind all a+ailable in(ormation and documentation and the so(tware itsel( (trans&ort (ile!. )mong others, the (ollowing accom&anying material is a+ailable2 @heck list (or the usage o( the LSM Workbench *resentation o( the LSM Workbench (*ower*oint &resentation!
1"/ %SM &or'ben!$ 1ersions

Version 1.4 o( the LSM Workbench was made a+ailable to about $A4 interested customers and &artners in the (rame o( the 0irst @ustomer Shi&ment between March 1<<? (@e-.T! and middle o( )ugust 1<<?. The resulting e:&eriences and (eedback were taken into account in the (urther de+elo&ment. .n )ugust 1<<?, +ersion 1.4 o( the LSM Workbench was made a+ailable to the &ublic. Bntil today, LSMW has been requested more than 1,444 times. .n Cune 1<<<, +ersion 1.A o( the LSM Workbench has been released. *
Legacy System Migration Workbench Since Culy 1<<<, +ersion 1.6 o( the LSM Workbench has been a+ailable. 0or all &ersons already (amiliar with +ersion 1.4 o( the LSM Workbench, section 11 &ro+ides a com&act o+er+iew o( the modi(ications in +ersion 1.6 com&ared with +ersion 1.4.
1"2 S ##ort
0or &roblem messages +ia S)*5et (6nline Ser+ice System!, entry 33-%SM is a+ailable in the com&onent hierarchy. When you enter a message, &lease s&eci(y the number o( the LSM Workbench +ersion you are using. (To dis&lay the +ersion number, select Extras Display LSMW version in the initial screen o( transaction LSMW.!
Note( .( &roblems occur a(ter ste& Convert data, &lease directly contact the s&ecial de&artment res&onsible (or the module (0., @6, MM, S/, D", etc.!. )ll ste&s (ollowing the data con+ersion are not LSM Workbench (unctions. There(ore the LSMW team cannot &ro+ide su&&ort (or these (unctions.
1"4 Signifi!an!e of Data Migration

/ata migration comes in the end o( "#$ im&lementation. )t this time, the "#$ system is normally installed and a&&lication customiEing is (inished (in the best case!. )n e:amination o( "#$ im&lementation &ro1ects by S)* @onsulting has shown that data migration is about =4F o( the total im&lementation e:&enses. This &ortion may rise u& to 34F in smaller im&lementation &ro1ects. ) signi(icant reduction o( the e:&enses (or data migration results in a corres&onding signi(icant reduction o( the total &ro1ect budget and the &ro1ect runtime. The (irst e:&eriences with the LSM Workbench in "#$ im&lementation &ro1ects are +ery &romising2 -oth the e:&enses and the costs o( data migration could be reduced signi(icantly.
1"5 -asi! Prin!i#les of t$e %SM &or'ben!$

The LSM Workbench was de+elo&ed on the basis o( the &'#(&') Migration Workbench that has been used many hundred times in the &ast and is still used &resently. The (ollowing conce&ts and techniques (rom the &'#(&') Migration Workbench were ado&ted2 -usiness ob1ects instead o( indi+idual tables or (ield contents are migrated. The con+ersion rules to be de(ined are (le:ible and can be customiEed in the (rame o( migration customiEing to meet the actual situation in the &ro1ect in the user system. *re&rogrammed con+ersion &rograms are not deli+ered. These &rograms are rather generated on the basis o( the de(ined rules.
The LSM Workbench was de+elo&ed on the basis o( the (ollowing &rinci&les2 Most o( the (unctions should reside in "#$. 5o collection o( indi+idual &rograms on di((erent &lat(orms. The quality and consistence o( the data im&orted into "#$ should be more im&ortant than s&eed and &er(ormance o( data migration. 8:isting knowledge and coding should be used. The de+elo&ed ma&&ing and rules should be reusable and thus be used re&eatedly in &ro1ects.
6n this basis, a conce&t was de+elo&ed that is re&resented in the (ollowing chart2
A!!elerating Data Migration( %SM &or'ben!$ 7o8 %SM &or'ben!$ 8or's

6ne or se0eral files
%ega!y data on PC
Read data Str !t re relations 9ield ma##ing Con0ersion r les Con0erted data
Read data
%ega!y data on a##li!ation ser0er
Con0ert data
R/3 Standard
-at!$ In# t #ro!essing Dire!t In# t #ro!essing IDo! inbo nd #ro!essing
S)* )G Culy 1<<<
=1
Schematic Flow of Data Migration with the LSM Workbench
The main ad+antages o( the LSM Workbench* *art o( "#$ and thus inde&endent o( indi+idual &lat(orms ) +ariety o( technical &ossibilities o( data con+ersion2 /ata consistency due to standard im&ort techniques2

-atch in&ut /irect in&ut -)*.s (-usiness )&&lication *rogramming .nter(aces! ./ocs (.ntermediate /ocuments!
The im&ort technique to be used in an indi+idual case de&ends on the business ob1ect. Generation o( the con+ersion &rogram on the basis o( de(ined rules @lear interacti+e &rocess guide .nter(ace (or data in s&readsheet (ormat @reation o( data migration ob1ects on the basis o( recorded transactions @harge%(ree (or S)* customers and S)* &artners
2 Pre!onditions
The LSM Workbench is a tool that su&&orts data trans(er (rom non%S)* systems to "#$. The main (unctions o( the LSM Workbench are2 1. .m&ort data (legacy data in s&readsheet tables and#or sequential (iles! =. @on+ert data ((rom source (ormat to target (ormat! $. .m&ort data (into the database o( the "#$ a&&lication! -e(ore you can a&&ly the LSM Workbench, you absolutely need a data migration !on!e#t. The (ollowing items should be considered in &articular2 Make sure that "#$ customiEing is (inished. /etermine the data contained in your legacy system and which o( the data will be required in the (uture (with res&ect to business o&eration!. /ecide whether it makes sense to use this tool with res&ect to the data +olume to be trans(erred. .t may be easier to trans(er +ery small data +olumes into "#$ manually. .n the case o( a +ery large data +olume, batch in&ut or ./oc techniques may cause e:tremely long runtimes. ) rough landmark (or estimating the required time2 14 444 records &er hour where this +alue may +ary considerably de&ending on the hardware a+ailable. .denti(y the transaction(s! in "#$ +ia which you want to im&ort the data into your S)* system. .t may be rele+ant whether you need the data (or statistical analysis or (or (urther &rocessing in the system. "un the rele+ant transaction in "#$ manually with test data (rom the legacy system and see which (ields must be (illed. There may be required (ields that do not corres&ond to data (ields in the legacy system. .n such a case, you should better assign a (i:ed +alue or establish an o&tional (ield (or data trans(er. Ma& the (ields in ad+ance in written (orm2 )ssign the source (ields to the target (ields. /etermine the (orm in which non%S)* data will be trans(erred into the S)* system (e.g. +ia Mo+e or according to a rule!. .( a&&licable, de(ine the translation rules (LSMW%internal name2 translation !. .n which way will the data be e:tracted (rom the non%S)* systemH 5ote2 The LSMW does not e:tract data. .n which (orm is the legacy data a+ailableH /etermine accordingly which o( the LSMW (unctions will be a&&lied. .( only a &art o( your legacy system will be re&laced by "#$, determine which (unction will be &ro+ided by the S)* system and which by the legacy system. .( a&&licable, set u& a conce&t o( data (lows and inter(ace architecture.
These questions will be answered di((erently (or e+ery customer and m st absol tely be ans8ered before t$e tool 8ill be sed I
3 Start # and Pre#arations

3"1 A t$ori:ations
A t$ori:ation le0el /is&lay Profile -JLSMWJSD6W 9 n!tion The user can dis&lay all &ro1ects and their work ste&s. De#she cannot switch to change mode. The user can dis&lay data, and read, con+ert and im&ort data. The user has 8:ecute authoriEation, and can change and co&y ob1ects. The user can use all (unctions made a+ailable by the tool.
8:ecute @hange
-JLSMWJ878@ -JLSMWJ@DG
)ll
-JLSMWJ)LL
*lease take into account2 The &ro(iles listed abo+e are not included in the &ro(iles o( the standard "#$ system. There(ore you ha+e to add the required &ro(iles to your user master record.
3"2 Initial Transa!tion

To start working with the LSM Workbench, use transaction %SM&2
LSM Workbench
!nitial Screen
3"3 Pro;e!t, S b#ro;e!t and 6b;e!t

6n the initial screen, you can create a new &ro1ect, corres&onding sub&ro1ects and ob1ects +ia Edit "# Create new entry. *ro1ect2 )n ./ with a ma:imum o( 14 characters to name your data trans(er &ro1ect. .( you want to trans(er data (rom se+eral legacy systems, you may create a &ro1ect e.g. (or e+ery legacy system. Sub&ro1ect2 )n ./ with a ma:imum o( 14 characters that is used as (urther structuring attribute. 6b1ect2 )n ./ with a ma:imum o( 14 characters to name the business ob1ect.
.n the initial screen, $ll ob%ects &ro+ides a list o( all &ro1ects created already. My ob%ects dis&lays a list o( all ob1ects you created &ersonally. $ll ob%ects of the pro%ect dis&lays all ob1ects o( the selected &ro1ect as tree structure. &ro%ect doc'mentation dis&lays any documentation written (or the indi+idual 4
Legacy System Migration Workbench &o&u&s and &rocessing ste&s. you can &rint the &ro1ect documentation out, send it and sa+e it in +arious (ile (ormats. Select Doc'mentation to enter your notes. )(ter clicking, a &o&u& is dis&layed in which you can write down your &ersonal documentation. The documentation (unction is additionally a+ailable under $dministration and (ecordings in the (irst se+en ste&s o( data migration. -elow, you (ind an e:am&le (or a &ro1ect with se+eral sub&ro1ects and ob1ects. This re&resentation is dis&layed by &ushing the button $ll ob%ects of the pro%ect2
Example for a &ro%ect Str'ct're
3"* <ser = idan!e

)(ter selecting an ob1ect, E)*E( or C+)*!),E leads you to the interacti+e &rocess guide. Dere you are guided through the indi+idual ste&s o( data migration. 5
LSM Workbench- *he Main Steps of Data Migration
This &o&u& &ro+ides the (ollowing (unctions2 Exec'te2 8:ecuted the selected &rocessing ste&. &ersonal men'2 Dere you can make an indi+idual selection (rom the dis&layed &rocessing ste&s. *ressing button Main ste&s automatically acti+ates all &rocessing ste&s mandatory (or a data con+ersion. )'mbers +n or +ff 2 you can acti+ate or deacti+ate the numbering o( the indi+idual &rocessing ste&s. Do'ble click . Display or Do'ble click . Change2 Dere, you can determine whether dis&lay mode or change mode is selected by double clicking. +b%ect overview2 /is&lays all in(ormation on the selected ob1ect. $ction log2 /is&lays a detailed o+er+iew (date, user name, time! (or all &rocessing ste&s already carried out. you can reset the action log +ia Extras (eset action log. This action is stored with a re(erence to the user and the date.
1+
&ersonal Men'- $ll &rocessing Steps $vailable
3". 9ield Ma##ing on Pa#er

-e(ore you start working with the LSM Workbench, you should (irst ma& the required ob1ect on &a&er. To do this, create and &rint out the ob1ect o+er+iew . )t this time, the o+er+iew only dis&lays the list and descri&tion o( the "#$ structures and their (ields. 'ou may use it as a guideline (or assigning the corres&onding structures and (ields o( the source system to these target structures and target (ields. 'ou can also download the o+er+iew in table (orm and (ill the table in 8:cel to ha+e the ma&&ing as a (ile on your *@.
11
3"/ Create 6b;e!t 60er0ie8

This (unction is a+ailable as &ushbutton in order to enable you to create an ob1ect o+er+iew at any time2
12
+b%ect +verview- General /ata, Structures, Structure "elations
+b%ect +verview- Source Structures # Target Structures
13
6b1ect 6+er+iew2 "ules
6b1ect o+er+iew in table (orm 1*
Note2 you may use this be(ore the de+elo&ment o( (ield ma&&ing and rules to &rint out the "#$ structures (or an ob1ect including the record descri&tion in order to carry out ma&&ing on &a&er .
6+er+iew o( "eusable "ules
1.
3"2 Administration
.n the initial screen, you can dis&lay the administration (unctions +ia /oto $dministration. Dere you can (ind a list o( all e:isting &ro1ects. .t enables you to create, &rocess, dis&lay, delete, co&y or rename &ro1ects, sub&ro1ects, ob1ects and reusable rules. -y double%clicking on an entry you can branch to the entry dis&lay. -y &ositioning the cursor on an entry, you can store a &ersonal note +ia Doc'mentation. 0or e+ery &rocessing action, the name o( the &erson who made the last change and the date o( the last change are stored.
LSM Workbench2 )dministration
3"4 Re!ordings
.n the initial screen, you can dis&lay the recording (unctions +ia /oto (ecordings0 .( neither a standard batch in&ut &rogram nor a standard direct in&ut &rogram nor an ./oc is a+ailable (or a data ob1ect, you can create a new ob1ect using the recording (unction o( the LSM Workbench. Dowe+er, also in cases where a standard &rogram is a+ailable, it may make sense to use the recording (unction in order to reduce the number o( target (ields.
1/
Note( The recording (unction records a (i:ed screen sequence. .t cannot be used (or migrating data containing a +ariable number o( items or (or transactions with dynamic screen sequences I Bse the documentation (unction2 Make sure that you are working in change mode. *osition the cursor on an entry and select Doc'mentation. ) &o&u& is dis&layed where you can write down your own notes. 0or a detailed descri&tion o( the recording (unction see section 6.
LSM Workbench2 "ecordings
3"5 Pre#arations for <sing IDo! Inbo nd Pro!essing

./ocs (.ntermediate /ocuments! were de+elo&ed (or e:changing messages between di((erent systems ("#$ "#$K "#$ "#=K "#$ non%S)* system!. Since it is a standard inter(ace to the "#$ a&&lications, this technique can also be used (or trans(erring data. To do this, howe+er, some &resettings and &re&arations are required (settings ha+e to be done (or eache &ro1ect!. 0or a summary o( these requirements see Settings !Doc inbo'nd processing in the LSM Workbench.
12
LSM Workbench- Settings (or ./oc .nbound *rocessing
The (irst requirement is a (ile &ort (or the (ile trans(er. .( required, create a &ort o( the (ile ty&e +ia Maintain ports. To do this, &osition the cursor on 0ile and &ress Create. 'ou should be in change mode. S)* recommends2 Port2 Name( 1ersion( 6 tbo nd file LSMW Legacy System Migration Workbench $ (./oc record ty&es S)* "elease 3.:! *lease enter a (dummy! &hysical directory and a (ile name, i.e. L(ilelsmwM
)s an addition, you can s&eci(y a t&+, ort. This &ort is required, i( you do not want to create a (ile during data con+ersion but submit the data in &ackages directly to (unction module IDoc_Inbound_Asynchronous. S)* recommends2 Port2 1ersion 2 R9C destination 2 Name of #ort2 assigned by the system $ (./oc record ty&es S)* "elease 3.:! 5ame o( "#$ System Legacy System Migration Workbench
Then the partner type should be de(ined or selected. S)* recommends2 Partner ty#e 2 BS (Bser!
)s o( release 3.A), this &artner ty&e is a+ailable in the standard system. B& to release 3.4inclusi+e, this &artner ty&e is not a+ailable in the standard &rogram and should be added. S)* recommends2 Partner ty#e( @reate BS
14
Legacy System Migration Workbench Re#ort name( 9orm ro tine2 S$ort des!ri#tion(
/SAPDMC/SAP_LSMW_PARTNERTYPES READ_USER any
0inally a &artner number should be de(ined or selected. S)* recommends2 Partner n mber2 Partner ty#e 2 Partner stat s2 Ty#e 2 %ang age2 Person in !$arge2 LSMW BS ) (acti+e! BS /8 or 85 'our user ./
-cti.ate I/oc inbound rocessing
@on(irm with 'es (to be done once (or each system!
Veri%y work%low customi0ing (to be done once (or each system!
The (ollowing entries o( the work(low runtime system should be marked with a green check mark2 Work(low )dministrator maintained Work(low "0@ destination com&letely con(igured Generic decision task classi(ied com&letely Sending to ob1ects and to D" ob1ects is acti+e
15
Legacy System Migration Workbench To do this, you can start automatic customiEing. )(ter this you should set item Monitoring 1ob (or work items with errors to not scheduled . (This means that you unmark the ./ Monitoring o( W.s with tem&orary errors .! .( you do not do this, the "#$ system tries o+er and o+er again to &ost incorrect ./ocs created during data migration. @heck the (unction with *est (FC destination. The (ollowing message should be dis&layed2 N*ingN e:ecuted success(ully. The "0@ destination (or the S)* -usiness Work(low is (ully con(igured.
1erifying Workflow C'stomi2ing
2+
* =eneral Ti#s for t$e Pro!ed re

Make sure that the C stomi:ing o( your "#$ system is (inished.
The ideal &ro1ect 2 0irst (inish customiEing Then, run data migration
Get acquainted with the terminology o( the rele+ant data ob1ect.

8.g. 7/412 @reate customer master (see also the 01 hel&! .denti(y the (ields to be (illed in your system.
/ecide whether you want to use an e:isting im&ort &rogram (batch in&ut, direct in&ut, -)*.s, ./ocs! or a recording2
)d+antages o( standard migration ob1ects2 .ncludes screen sequences that may +ary (e.g. with di((erent material ty&es! )d+antages o( recordings2 Smaller number o( target (ields )+ailable (or almost e+ery transaction
.( you use a recording2 "ecord the transaction and &rocess the recording.
S&eci(y 0ield names 0ield descri&tion /e(ault +alues
/e(ine the re!ord str !t res o( the legacy data and introduce them to "#$.
@ase 12 /ata is a+ailable in one or more (iles. .ntroduce these structures to "#$. @ase =2 /ata (still! resides in the legacy system and the legacy system &ro+ides a (unction (or e:&orting the data. .ntroduce this (these! record structure(s! to "#$. @ase $2 /ata (still! resides in the legacy system and the legacy system does not &ro+ide a (unction (or e:&orting the data.. /e(ine the record structure o( the data you need. 8:&ort this data by means o( a &rogram to be written in the legacy system. .ntroduce this (these! record structure(s! to "#$.
/e+elo& field ma##ing and !on0ersion r les.
Bse the ob%ect overview (or 0ield ma&&ing on &a&er .
Read data O automatically by &ushing a button Con0ert data

The le(t column o( the translation table is (illed automatically, i( this was set accordingly in translation control. ) sequential (ile is created.
Maintain the re sable r les(
Maintain the translation tables (03 hel& (or right%hand column!.
21
Legacy System Migration Workbench S&eci(y your (i:ed +alues.
Maintain the translation tables and generate a new con+ersion. *lease note2 at this &oint the &rocessing ste&s are not sequential. .m&ort the data. -atch in&ut # recording2 Generate batch in&ut session. "un batch in&ut session.
/e&ending on the ob1ect ty&e2
/irect in&ut Start direct in&ut session.
./ocs # -)*.2 Trans(er con+erted data to ./oc inbound &rocessing. @heck inbound &rocessing.
22
. Data Migration > Ste# by Ste#

.( you want to create or change ob1ects, make sure that you are working in change mode. To acti+ate this mode, click Change in the corres&onding &rocessing ste&. 6nly this mode &ro+ides all (unctions required (or changing.
."1 Maintain 6b;e!t Attrib tes

.n this ste&, ob1ect ty&e and im&ort technique are selected.
Maintain 6b1ect )ttributes
5ame your ob1ect. -y entering data into (ield +wner3 add the &ro1ect to the list o( all &ro1ects you created. 'ou can dis&lay it a(terwards in the initial screen under My ob%ects. @hoose whether data trans(er is one%time or &eriodic. .n the case o( &eriodic trans(er, (iles cannot be read (rom the *@. This adds &rocessing ste& Frame program for the periodic data transfer . 0lag whether the (ile names are system de&endant (this gi+es you the chance to later on enter (ile names &er system id! Select the ob1ect ty&e and im&ort technique. Dere, an 03 hel& is a+ailable (or the in&ut (ield. This hel& dis&lays the rele+ant lists (rom which you can select the ob1ects.
23
Legacy System Migration Workbench .n the case o( batch in&ut and direct in&ut, a documentation is a+ailable (or the &rogram under &rogram name (see symbol glasses!. .( you want to carry out batch in&ut recording, you can enter (urther recordings by clicking the arrow.
Ca tion
.( you a&&ly im&ort technique -)*. or ./oc, the &rogram checks during the sa+e o&eration whether a so%called &artner agreement is already a+ailable (or the &reset &artner (see section $.<! and the selected message ty&e. .( this is not the case, the system tries to create them (see also section A.1$.$!.
."2 Maintain So r!e Str !t res

.n this ste& you de(ine the structures o( the ob1ect with name, descri&tion and the hierarchical relationshi&s2 .n the &o&u&, click Change. 'ou can now de(ine, change, relink or remo+e structures. )ll these (unctions are a+ailable +ia &ushbuttons. When you de(ine more than one structure, a &o&u& is dis&layed querying the relations between the structures2 same le+el#subordinatedH
Ca tion
0or migration ob1ects created +ia transaction recording, you may only de(ine one structure &er recording here, since only one (lat target structure &er recording is a+ailable.
Maintain So'rce Str'ct'res .n the abo+e e:am&le, one or se+eral (or no! item records @BST6M8"J@65T)@TS may e:ist (or each header record @BST6M8"JD8)/8". Dere, it is not determined yet whether these records are stored in one (ile or in two (iles.
2*
."3 Maintain So r!e 9ields

.n this section, (ields are created and maintained (or the structures de(ined in the &receding ste&.
Maintain So'rce Fields
There are se+eral &ossibilities o( de(ining and maintaining the source (ields.
."3"1 Create Indi0id al So r!e 9ields

Make sure that you are in change mode and the cursor is &ositioned on a source structure or an e:isting source (ield. @licking on Create field dis&lays the (ollowing &o&u&2
2.
2/
22
24
25
'ou can select the (ield ty&e (rom an underlying list with (ield ty&e categories and the corres&onding (ield descri&tion2
So'rce Fields- &ossible Field *ypes
3+
Legacy System Migration Workbench /uring data read, you can s&eci(y whether date +alues are con+erted into the internal date (ormat (''''MM//! and amount (ields are con+erted into the calculation (ormat (1=$3.A6, i.e. no triad se&arators, decimal &oint!. .( data (or se+eral structures is stored in one file the (ield Identifying field 0al e has to be maintained. Please maintain only one identifying field 0al e #er str !t re ? 0or (ields o( to& hierarchy le+el structures, ./ selection &arameter can be set during (ead4Convert data. .( you set this indicator, the corres&onding (ield is made a+ailable as selection &arameter when reading or con+erting data. )s a rule, this is used (or testing.
."3"2 Maintain So r!e 9ields in Table 9orm

Make sure that you are in change mode and the cursor is &ositioned on a source structure or an e:isting source (ield. @licking on *able Maintenance dis&lays the (ollowing screen2
Maintain So'rce Fields in *able Form When you enter a (ield name and &ress Enter, the (ollowing +alues are &ro&osed2
31
0ield ty&e N@N 0ield length 14 0ield te:t P (ield name
."3"3 Co#y So r!e 9ields from 6t$er So r!es
Make sure that you are in change mode and the cursor is &ositioned on a source structure or an e:isting source (ield. Selecting Copy So'rce Fields dis&lays the (ollowing &o&u&2
Copy So'rce Fields- Selecting the So'rce <#load @teAt se#arated by tabsB( .t is assumed that the source (ield descri&tion is stored in a te:t (ile the columns o( which are se&arated by tabs, e.g.2
0ield /escri&tion Co#y from anot$er ob;e!t( Source (ields may be co&ied (rom the source structure o( another ob1ect. Co#y from data re#ository(
32
Legacy System Migration Workbench Source (ields may be co&ied (rom a structure o( the "#$ /ata /ictionary. 9rom data file @field names in 1st lineB Source (ields may be co&ied (rom a data (ile. This (ile must be stored on the *@ in the (orm o( te:t se&arated by tabs and contain the (ield names in the (irst line.
8:am&le o( a data (ile (rom which the source (ields are to be co&ied (rom
."* Maintain Str !t ral Relations$i#s

The structural relationshi&s de(ine the relationshi&s between source and target structures. The &ossible target structures are de(ined during the selection o( the ob1ect ty&e and the im&ort technique. .n general, there are target structures that must be selected (required segments!. .n this case the (ollowing note is dis&layed2 This structure must be selected . To de(ine structural relationshi&s, &osition the cursor on a (ield o( the "#$ structures # target structures. @licking (elationship o&ens a window that dis&lays the e:isting source structures (or selection. .( you want to change the relation, remo+e the e:isting relation (irst. To do this, a &ushbutton is a+ailable as well. .n addition, you can use Check to check the structural relationshi&s (or errors. The status bar then dis&lays an error message or message2 The structural relationshi&s do not contain any errors .
33
Maintain Str'ct'ral (elationships
.n the abo+e e:am&le, the (ields o( "#$ structures -G"44, -Q544, -Q5)1, and -Q5-1 are (illed by the (ields (rom @BST6M8"JD8)/8", the (ields o( "#$ structure -Q5VQ are (illed by the (ields (rom @BST6M8"J@65T)@TS.
Note 12 Many -atch .n&ut and /irect .n&ut &rograms use a control record named -G"44 or -.444. 'ou should always assign the to& le+el source structure (Rheader structureS! to this control record.
Note 22 .t might be necessary to assign two or more source structures to one target structure. .n this case you should &roceed as (ollows2 @reate the source structures in the usual way. Then assign the subordinate source structure to the target structure. Thus, the (ields o( both source structures will be a+ailable (or the (ields o( the target structure.
3*
%SM&( Str !t re Relations

Target TJDeader TJ*osition So r!e SJDeader1 SJDeader= SJ*osition
LOOP AT S_Header1. LOOP AT S_Header2 WHERE ... T_Header <<< S_Header1, S_Header2 LOOP AT S_POSITION WHERE ... T_POSITION <<< S_POSITION ENDLOOP. ENDLOOP. ENDLOOP.
Structure relations2 8:am&le
.". Maintain 9ield Ma##ing and Con0ersion R les

.n this ste&, you assign source (ields to target (ields and de(ine how the (ield contents will be con+erted. )ll (ields o( all target structures, which you selected in the &re+ious ste&, will be dis&layed. 0or each target (ield the (ollowing in(ormation is dis&layed2

0ield descri&tion )ssigned source (ields (i( any! "ule ty&e ((i:ed +alue, translation etc.! @oding.
Note2 Some (ields are &reset by the system. These (ields are called Rtechnical (ieldsS are marked with R/e(ault settingS. The coding (or these (ields is not dis&layed when (irst entering the (ieldma&&ingK it can be dis&layed +ia the dis&lay +ariant (see A.A.1!. @hanging the de(ault setting may seriously a((ect the (low o( the data con+ersion. .( you erroneously changed the de(ault setting, you can restore it by choosing Extras (estore defa'lt0
3.
0ield Ma&&ing2 Tree o( Target 0ields (or the Target Structures Selected
The (ollowing (unctions are a+ailable2 9ield do! mentation ( /is&lays a short documentation (or the target (ield the cursor is &ositioned on. The documentation may branch o(( to (urther in(ormation. Possible 0al es ( /is&lays a selection list o( all +alues &ossible (or this target (ield.
%ongteAt / Do! mentation
( Maintenance o( the documentation (or a (ield etc.
Assign a so r!e field( To assign a source (ield, &osition the cursor on a target (ield in the tree structure and select $ssign so'rce field. This dis&lays a list o( all a+ailable source (ields (or selection. 'ou can assign the (ields by double%clicking on them.
1ote2 .( you choose Extras $'to"Fieldmapping, LSMW will gi+e suggestions (or assigning source (ields to target (ields. Remo0e t$e assignment of a so r!e field( To remo+e a source (ield assigned be(ore, &osition the cursor on a target (ield in the tree structure and select (emove so'rce field. .( one source (ield has been assigned only, this (ield is remo+ed. .( se+eral source (ields ha+e been assigned, a list o( all source (ields assigned is dis&layed (or selection. The corres&onding source (ield can then be selected by double%clicking on it. )(ter assigning the source (ields, you de(ine the !on0ersion r les. The de(ault rule is Mo+e . Dowe+er, you can select +arious standard techniques +ia &ushbutton.
3/
Conversion ('les- Select ('le
Assign r les(
Initial2
This deletes the coding assigned to the target (ield. .n addition, source (ields assigned to the target (ields are remo+ed as well. /e&ending on the ob1ect ty&e, the target (ield is assigned the (ollowing +alue2

0or standard batch in&ut#standard direct in&ut2 )odata characters (determined e.g. in session header -G"44, -.444! 0or batch in&ut recording2 N#N as nodata character 0or -)*.s, ./ocs2 @lear (ield (i.e.2 character (ield blankK numeric (ield N44...4N!
Mo0e2
The data is trans(erred using )-)* command Mo+e . 0or source (ields that are not o( ty&e N@N or N5N, this means2 Pa!'ed field Date field Bn&ack to target (ield *o&u& to select ) ) Amo nt field internal (ormat user (ormat ''''MM// W".T8...T6... e.g. 41.14.1<<?
) ... -at!$ in# t/dire!t in# t( The amount +alue is edited according to the (ormat settings in the user master. -APIs, IDo!s2 The amount +alue kee&s the internal calculation (ormat.
32
Legacy System Migration Workbench Constant( The target (ield is assigned a (i:ed +alue. 9iAed 0al e @re sableB 2 ) (i:ed +alue ob1ect (+ariable! named 0VJT(i:ed+alueU is assigned to the target (ield. This (i:ed +alue ob1ect is (illed with an actual +alue in ste& Maintain (i:ed +alues, translations and user%written routines . Translation @re sableB 2 The target (ield is assigned coding carrying out (ield contents con+ersion using a translation table. The +alues o( this translation table can be entered in ste& Maintain (i:ed +alues, translations and user%written routines see A.6. <ser-8ritten ro tine @re sableB( The system creates the (rame o( a (orm routine ()-)* subroutine! with name &re(i: urJ . This routine can be reused, i.e. it can also be used in other ob1ects o( the &ro1ect. With all kinds o( reusable rules, the LSM Workbench &ro&oses one to three &ossible names. 6ne name is recommended by the system. S)* recommends you to use the &ro&osed name. 0or details regarding naming con+entions, see A.A.3. When creating user written routines &lease kee& in mind that2 % the correct amount o( source (ields has been linked (regarding the amount o( in&ut &arameters! % the source (ields are related in correct sequence (i.e. the sequence o( the &arameters!. PrefiA( S&eci(y any &re(i: to &recede the contents o( the source (ield. S ffiA( S&eci(y any su((i: (ollow the contents o( the source (ield. Con!atenation 2 'ou can concatenate two or more source (ields. Transfer left-; stified( Trans(ers the contents o( the source (ield in le(t%1usti(ied (orm. A-AP !oding( /ouble%clicking on a target (ield branches o(( to the )-)* editor. There you can edit generated )-)* coding or write and sa+e your own coding. ) large &art o( the usual standard "#$ editor (unctions, such as Check (synta: check!, &retty &rinter, etc., are a+ailable there. Bnder !nsert you can add the (ollowing to your coding2 so r!e fields2 all source (ields a+ailable are dis&layed (or selection global 0ariable2 see A.> global f n!tions 2 see A.A.$
39ID%D( This is a s&ecial (unction (or &rocessing o( ./ocs. .n some cases an L7%structureM e:ists in addtion to the data trans(er structure (where the +alues (or the im&ort can be (ound!K the (ields o( this L7%structureM ha+e to be (illed with L7M or blank to decide i( the corres&onding (ield in the data trans(er structure should be trans(ered or not. The (ollowing coding is generated automatically2
.( not T(ield in the data trans(er structureU is initial. T(ield in 7%structureU P L7L. else. T(ield in 7%structureU P L L. 8ndi(.
Note2 Via Extras "# fill 5"str'ct'res the coding (or whole structures can be added
."."1 9or t$e Ad0an!ed <ser( Dis#lay 1ariant, Pro!essing Times

Define dis#lay 0ariant( .n work ste& Maintain (ield ma&&ing and con+ersion rules , select NV dis&lay +ariantN. This dis&lays &o&u& Define display variant. This (unction is use(ul mainly to ad+anced users who want to modi(y their (ield ma&&ing. 'ou can s&eci(y the in(ormation to be dis&layed. 34
Define Display 1arian t =lobal data definitions 2 /is&lays label __GLOBAL_DATA (or global data de(initions and declarations. There, you can de(ine a +ariable, structures, tables, etc., to be used in the (ield ma&&ing o( your own coding. Pro!essing times2 Dere you can insert your own coding at s&eci(ic &rocessing times. The (ollowing &rocessing times are a+ailable2 Pro!essing time __BEGIN_OF_PROCESSING__ Meaning -e(ore the beginning o( data &rocessing Defa lt setting (blank! (blank!
__BEGIN_OF_TRANSACTION__ -e(ore the beginning o( transaction data &rocessing __BEGIN_OF_RECORD__ -e(ore a&&lying the con+ersion rules (or a source structure
.nitialiEe the structure <segme !" (5ame o( target structure! -atch .n&ut, /irect .n&ut2 <segme !" # $ $!_<segme !". -)*., ./oc2 g_ed$dd_seg am # %...%. g_ed$dd_seg &m # %....%. g_ed$dd_'sg &m # %......%. g_ed$dd_()e*e) # %..%. C)ear <segme !".
__END_OF_RECORD
)(ter a&&lying the con+ersion rules (or a source structure
Tra s+er_re,-rd.
__END_OF_TRANSACTION__ __END_OF_PROCESSING__
)(ter (inishing transaction Tra s+er_!ra sa,!$- . &rocessing )(ter (inishing data &rocessing (blank!
35
Legacy System Migration Workbench 9orm ro tines2 /is&lays label __FOR._RO/TINES__ (or (orm routines ()-)* subroutines!. There, you can de(ine )-)* subroutines to be used in your own coding (or (ield ma&&ing. Te!$ni!al fields 2 /is&lays the so%called technical (ields. These are target (ields (or which LSMW &ro&oses a con+ersion rule (e.g. constant!. )s a rule, modi(ications need not be made. Initial fields 2 /is&lays initial (ields. Coding 2 /is&lays the stored coding.
Note2 Bnder menu item Extras So'rce fields not assigned you can dis&lay the source (ields not yet assigned, i.e. you can see whether there is data which has not yet been adequately dealt with.
."."2 9or t$e Ad0an!ed <ser( =lobal 1ariables

The LSM Workbench internally uses a number o( global +ariables. 1. 0rom the list o( work ste&s, select Field mapping and conversion r'le. =. -ranch o(( to the coding by double%clicking on a target (ield $. Select !nsert /lobal variable. This +ariable can be used in your )-)* coding. =lobal 0ariable g_'r-0e,! g_s&1'r-0 g_-10e,! g_re,-rd g_, !_re,-rds_read g_, !_re,-rds_s2$''ed g_, !_re,-rds_!ra s+erred g_, !_!ra sa,!$- s_read g_, !_!ra sa,!$- s_s2$''ed g_, !_!ra sa,!$- s_!ra s+erred g_, !_!ra sa,!$- s_gr-&' g_&ser$d g_gr-&' ame g_gr-&' r Des!ri#tion @urrent &ro1ect @urrent sub&ro1ect @urrent ob1ect @urrent target structure 5umber o( records read 5umber o( records ski&&ed 5umber o( records trans(erred to a (ile 5umber o( transactions read 5umber o( transactions ski&&ed 5umber o( transactions trans(erred to a (ile 5umber o( transactions in the current batch in&ut session Bser ./ 5ame o( the batch in&ut session @urrent number o( the current batch in&ut session
."."3 9or t$e Ad0an!ed <ser( =lobal 9 n!tions

The LSM Workbench &ro+ides a series o( (unctions that can be used in any &osition o( the )-)* coding.
*+
5ote2 These (unctions allow to &artially considerably in(luence the (low o( the data con+ersion &rogram. *lease do a&&ly these (unctions with care. 1. 0rom the list o( work ste&s, select Field mapping and conversion r'le. =. -ranch o(( to the coding by double%clicking on a target (ield $. Select !nsert /lobal f'nctions. The (ollowing (unctions are a+ailable2
=lobal f n!tion !ra s+er_re,-rd.
Des!ri#tion Trans(ers the current record (i.e. (or the current target structure! to the out&ut bu((er.
!ra s+er_!($s_re,-rd %...%. Trans(ers a record o( another target structure to the out&ut bu((er. The name o( the target structure has to be s&eci(ied as argument in single quotes. a!_+$rs!_!ra s+er_re,-rd. - _,(a ge_!ra s+er_re,-rd. !ra s+er_!ra sa,!$- . s2$'_re,-rd. s2$'_!ra sa,!$- . Trans(ers the current record to the out&ut bu((er, i( it is the (irst transaction. Trans(ers the current record to the out&ut bu((er, i( it has changed com&ared to the last record. Writes the current transaction to an out&ut (ile. )ll records o( the out&ut bu((er are trans(erred to the out&ut (ile. The current record is not trans(erred to the out&ut bu((er. The current transaction is not written to the out&ut (ile.
."."* 9or t$e Ad0an!ed <ser( Re sable R les E Naming Con0entions

"eusable rules are rules that are a+ailable across the &ro1ect. They can be used in all ob1ects o( a &ro1ect. "eusable rules are2 (i:ed +alues, translations, and user%written routines. .( you assign a reusable rule to a target (ield, the system &ro&oses one to three di((erent names. To understand the naming con+entions, we should look at the de(inition o( data ob1ects in the "#$ system. /ata ob1ect de(inition in the "#$ system is &er(ormed on three le+els2 Domain( 6n the lowest le+el, technical attributes are de(ined, e.g. (ield ty&e, (ield length, +alue table or (i:ed +alues. Data element( 6n the second le+el, semantic characteristics are de(ined on the basis o( a domain and its characteristics, e.g. language%de&endent te:ts, documentation. 9ield2 6n to& le+el, attributes o( the (ield in the conte:t o( a structure or table are de(ined on the basis o( a data element, e.g. (oreign key relations, search hel&s. This means in &articular2 0or a domain, there normally are se+eral data elements which re(er to the domain. () count in the "#$ system, "elease 3.A) &roduces the (ollowing (igures2 /omains2 about ==,444, data elements2 about 11>,444, (ields2 about 1,4=?,444! S)* recommends to acce&t the names de(aulted by the system as a rule. )n e:ce&tion is gi+en, i( the domain is +ery general such as @D)"1 (about A,=44 data elements! or 708L/ (about 1$,A44 *1
Legacy System Migration Workbench data elements. .( you used the name o( the domain in this case, the reusable rule might not be usable (or another (ield, since this (ield may ha+e a com&letely di((erent meaning. This naming &rocedure kee&s the number o( con+ersion rules small and maintains the consistency in data con+ersion. DAam#le( No" 9ield 1 = -BQ"S @6J @6/8 Data element -BQ"S @6J@6/8 Domain -BQ"S -BQ"S Name @om&any code @om&any code
-oth (ields are named @om&any code . The (ield names are di((erent, the domain is the same. Thus both (ields should be (illed with the same (i:ed +alue or the same translation or user%written routine.
*2
."/ Maintain 9iAed 1al es, Translations and <ser-8ritten Ro tines

.n this ste& you can &rocess the reusable rules o( a &ro1ect2
&rocess (e'sable ('les 9iAed 0al e2 Dere you can s&eci(y length, ty&e, (lag (or lowercase#u&&ercase and +alue in addition to the descri&tion.
Change Fixed 1al'e
*3
Translation 2 Dere you can enter in(ormation on the source (ield and the target (ield2
Change translation 4 So'rce field3 target fields
.( you are creating a new translation you ha+e to sa+e data be(ore you can change to Control information .
**
Legacy System Migration Workbench Control information 2 Dere you can de(ine the translation ty&e. 'ou can s&eci(y which o( the two translation tables will be searched (or a +alue (irst and which alternati+e will be selected, i( no suitable entry is (ound2
1(1 translation 0al es2 Dere you s&eci(y the +alue table to be used during translation. 'ou may also u&load the +alues (rom a *@ (ile (te:t se&arated by tabs!. .n addition, 03 hel& is a+ailable in column 5ew +alue .
Im #ortant
/uring translation, only +alues (or which the 6Q (lag was set are included.
Inter0al translation 0al es( Dere you s&eci(y the +alue table to be used during translation by inter+als. 'ou may also u&load the +alues (rom a *@ (ile (te:t se&arated by tabs!. .n addition, 03 hel& is a+ailable in column 5ew +alue . *.
Im #ortant
/uring translation, only +alues (or which the 6Q (lag was set are included.
."2 S#e!ify 9iles

.n this ste& you describe all (iles to be used in the (ollowing ste&s2 'our legacy data on the *@ and#or "#$ ser+er The (ile (or the read data The (ile (or the con+erted data
*/
*2
*4
Specify Files If yo r lega!y data is on t$e PC( 1. .n change mode, &osition the cursor on the line Legacy data W on *@ ((rontend! . =. Select $dd entry. ) &o&u& is dis&layed. $. S&eci(y (ile &ath (03 hel&!, (ile name and descri&tion and other &ro&erties.
*5
File on Frontend 6&C7- &roperties If yo r lega!y data is on t$e R/3 ser0er2 1. .n change mode, &osition the cursor on the line Legacy data on "#$ ser+er (a&&lication ser+er! . =. Select $dd entry0 ) &o&u& is dis&layed. $. S&eci(y (ile &ath, (ile name and descri&tion. 3. Bnder @ode&age ./ , s&eci(y the indicator o( the legacy systemNs character set. A. /etermine the technical record descri&tion and the se&arators.
Note( *lease note that the "#$ system uses user ./ TsidUadm with regard to the o&erating system. There(ore, make sure that you ha+e read#write authoriEation (or the selected directory .
.+
File on (48 Server- Maintain &roperties *lease consider the (ollowing notes2 .( a (ile contains data (or se+eral source structures, the (ield sequence has to corres&ond to the source structure de(inition. .( a (ile contains data (or a single source structure, either the (ield sequence has to corres&ond to the source structure de(inition or (ield names ha+e to be s&eci(ied at the beginning o( the (ile which can be used (or assigning the columns to the (ields. .( a (ile contains end%o(%line indicators (te:t (ile!, &acked (ields are not allowed. .( a (ile contains se&arators, &acked (ields are not allowed. *@ (iles and ser+er (iles may be mi:ed at will. .n the (ollowing ste&, a (ile containing data (or se+eral source structures can be assigned to se+eral source structures. .n the (ollowing ste&, a (ile containing data (or a single source structure can be assigned to one single source structure only. .( se+eral (iles are used in an ob1ect, the corres&onding source structures ha+e to contain (ields o( the same name. .n our e:am&le, this is (ield @BST6M8"J5BM-8"2 .1
/is&lay Merge 0ields
9ile of read data( Dere, the (ile name is entered. We recommend you to use (ile e:tension .lsmw.read to di((erentiate the read data (rom the con+erted data.
9ile of !on0erted data( S&eci(y the (ile name. We recommend you to use (ile e:tension .lsmw.con+ . 0ields Logical &ath and Logical (ile name should be (illed only i( this is required (or the subsequently called batch in&ut or direct in&ut &rogram ((ields only are shown in this case! 0or both (ields, 03 hel& is a+ailable.
.2
Note 12 5ames (or &aths and (iles can be (reely assigned according to the o&erating systemNs naming con+entions.
Note 22 .( your (iles are stored in se+eral sets o( (iles, you can add a wildcard (NVN! to the name o( your (ile. The &ossible +alues (or NVN can be s&eci(ied under Values (or wildcard .
."4 <se &ild!ards in 9ile Names

8:am&le (or the usage o( wildcards in (ile names2 LetNs assume that the legacy data is stored in the (ollowing (our (iles2 0ile 12 D34.$g4P&r,(ase Orders4PO Header 1.!5! 0ile =2 D34.$g4P&r,(ase Orders4PO P-s$!$1.!5!
0ile $2 D34.$g4P&r,(ase Orders4PO Header 2.!5! 0ile 32 D34.$g4P&r,(ase Orders4PO P-s$!$2.!5!
Two (iles each (V1.t:t and V=.t:t! (orm a set , i.e. (ile = contains the &osition data (or the header records in (ile 1, (ile 3 contains the &osition data (or the header records in (ile $. When reading the data, (iles 1 and = shall be &rocessed be(ore (iles $ and 3. This is achie+ed by means o( the (ollowing settings2
.3
Specify Files- ,sing Wildcards
Note( 'ou can also use a wildcard in the names o( the (iles o( read data and con+erted data.
.*
."5 Assign 9iles

.n this ste&, you assign de(ined (iles to the source structures2
$ssign Files
Note2 .( you change (ile names or &ro&erties subsequently, the (ile assignment is ke&t.
."1+ Read Data

Pro!eeding( .( you want to &rocess all data belonging to an ob1ect, click on Exec'te. The &rocess is started. .( you want to migrate a &art o( the data only, you can limit the number o( data to be migrated in (ield General selection &arameters . Make your selection in (ield Transaction number (rom ... to ... . Multi&le selection is &ossible.
.( you marked one or se+eral source (ields as selection &arameters when de(ining the source (ields, these (ields are also o((ered as selection &arameters. .n addition, two check bo:es are o((ered2 )mount (ield2 )mount (ields are con+erted into calculation (ormat (with decimal &oint!. /ate (ield2 /ate (ields are con+erted into internal (ormat (''''MM//!.
.( you use a wildcard in the (ile names (or the in&ut (iles, and at least one +alue has been de(ined (or the wildcard, a selection &arameter (or the wildcard is o((ered as well. .( you do not make any entry here, all wildcard +alues de(ined are &rocessed.
..
Data (ead &rogram- With ,ser"defined Selection &arameter
Note2 0irst, the system checks whether the data read &rogram is still u&%to%date. .( this is not the case, it is regenerated automatically.
."1+"1 Dis#lay Read Data

.n this ste&, you can dis&lay all or a &art o( the read data in table (orm. @licking on a line dis&lays all in(ormation (or this line in a clear way. The same ha&&ens when you click on Field contents. Change display allows to select either a one%line or multi%line +iew. Display color palette dis&lays the colors (or the indi+idual hierarchy le+els.
."11 Con0ert Data

."11"1 =eneral Remar's
With regard to o&eration, this work ste& essentially corres&onds to work ste& "ead /ata (see A.?!. .( you do not make any data selection, con(irm the &rocess by clicking on Exec'te. 6therwise, make your selection in (ield Transaction number (rom ...to... . Dere, multi&le selection o( transaction numbers is &ossible as well. .( you marked one or se+eral source (ields as selection &arameters when de(ining the source (ields, these (ields are also o((ered as selection &arameters. .( you use a wildcard in the (ile names (or the in&ut (iles, and at least one +alue has been de(ined (or the wildcard, a selection &arameter (or the wildcard is o((ered as well. .( you do not make any entry here, all wildcard +alues de(ined are &rocessed.
./
Data Conversion &rogram- With ,ser"defined Selection &arameter
Note2 0irst, the system checks whether the data con+ersion &rogram is still u&%to%date. .( this is not the case, it is regenerated automatically.
.2
."11"2 Additional 9 n!tion for -API/IDo!

.( the LSMW ob1ect is based on a -)*. or an ./oc, (urther selection &arameters are dis&layed on the data con+ersion &rogram selection screen2
Convert Data2 0urther Selection *arameters (or -)*.#./ocs .( you select Create file, a (ile is created during data con+ersion. .( you select @reate ./ocs directly , ./ocs are collected during data con+ersion and submitted (or ./oc creation in &ackages. The &ackage siEe can be determined using &arameter 5umber o( ./ocs &er &ackage . The de(ault +alue is A4.
."12 Dis#lay Con0erted Data

See section A.14.1.
."13 Im#ort Data

The ste&s dis&layed by the &rogram de&end on the selected ob1ect ty&e2 Standard batch in&ut or recording2
.4
Legacy System Migration Workbench Generate batch in&ut session "un batch in&ut session
Standard direct in&ut2
Start direct in&ut session
-)*. or ./oc2

Start ./oc creation Start ./oc &rocessing @reate ./oc o+er+iew Start ./oc &ost&rocessing
."12"1" Im#ort Data 8it$ -at!$ In# t

."13"1"1 =enerate -at!$ In# t Session .n this ste&, the standard batch in&ut &rogram belonging to the ob1ect is directly called. The name o( the (ile with the con+erted data is already &ro&osed. The batch in&ut sessions to be generated are named a(ter the LSMW ob1ect. ."13"1"2 R n -at!$ In# t Session The &rogram goes to "#$ standard transaction SM$A. Dowe+er, only the batch in&ut sessions (or the selected ob1ect are dis&layed.
Note2 .( you used the name o( the ob1ect in other &ro1ects or sub&ro1ects as well, batch in&ut sessions (rom these ob1ects may also be dis&layed.
."13"2 Im#ort Data 8it$ Dire!t In# t

."13"2"1 Start Dire!t In# t Session /e&ending on the ob1ect ty&e, either the standard direct in&ut &rogram belonging to the ob1ect is called or you can select a direct in&ut &rogram or a direct in&ut transaction.
.5
."13"3 Im#ort Data 8it$ -API or IDo! Te!$niF e

/ata stored in a (ile by means o( the ./oc technique is generally im&orted in two ste&s. 'ou can call these ste&s in LSM Workbench2 Start I/oc creation. 0irst, the (ile o( the con+erted data is read. The in(ormation &ackages contained are stored in the "#$ database in ./oc (ormat. .t is, howe+er, not stored in the database o( the corres&onding a&&lication. The system assigns a number to e+ery ./oc. Then the (ile o( the con+erted data is deleted. Start I/oc rocessing. The ./ocs created in the (irst ste& are submitted to the corres&onding a&&lication &rogram. This a&&lication &rogram checks the data and &osts it in the a&&licationMs database, i( a&&licable.
Note2 Ste& Start I/oc creation2 is not &er(ormed, i( you selected o&tion @reate ./ocs directly during data con+ersion. Whether the second ste& is automatically initiated de&ends on the settings o( the )L8%8/. customiEing. 6ne essential setting is made in the so%called &artner agreement ((or a &artner and a message ty&e, see section A.=!. This agreement s&eci(ies whether the ./ocs are to be &rocessed immediately or by means o( a background &rogram.
1ote 312 *artner agreements automatically created by the LSM Workbench are set as (ollows2 .nitiation by background &rogram . ('ou can manually change this setting at any time.!
1ote 3#2 /uring the &rocessing o( inbound ./ocs, so%called work items are created in the standard &rogram. This are elements o( the "#$ work(low that are usually not required during data migration. 0or in(ormation on how O and with which consequences O the creation o( work items can be su&&ressed see "#$ 5ote no. 13<$6?.
1ote 3)2 @/%"6M .nter(ace )d+iser &ro+ided by S)* contains use(ul in(ormation that hel&s to increase &er(ormance in connection with ./oc &rocessing. 0ollow the &ath *echnology !nterfaces 9ackgro'nd processing !mport $LE4!Doc &erformance0
'ou can do the (ollowing in addition to these two &rocessing ste&s2 ,reate I/oc o.er.iew 2 This dis&lays a Rstatus o+er+iew which allows to dis&lay indi+idual ./ocs with the drill%down technique.
/+
/ Re!ordings
*er(orm a transaction Rtrial runSK This is no simulation modeI 'our in&ut is &osted in the systemI *ost&rocess recording2 )ssign (ield names, (ield te:ts and de(ault +alues Sa+e recording2 This generates the abo+e structure in the /ata "e&ository. .n $ttrib'tes for an ob%ect you can assign any number o( recordings to an ob1ect. This way you can run +arious transactions in succession (or one data record.
/"1 Detailed Des!ri#tion of t$e Pro!ess

.n the initial screen you select (unction (ecordings under /oto.
(ecordings- +verview
Note2 "ecordings are assigned to e:actly one &ro1ect. Select (ecordings Create recording. 0ill the dis&layed (ields.
/1
Create (ecording )(ter &ressing Contin'e you can start to record the transaction whose transaction code you ha+e to enter (irst.
Create (ecording- Enter *ransaction Code
Note2 .( you do not know the transaction code o( the transaction you selected2 Select System Create session0 This dis&lays the initial screen o( "#$. Then select the rele+ant a&&lication com&onent. This dis&lays the rele+ant dialog screen. Select the transaction you want to record and then System Stat's. The re&ository data includes the transaction code. 5ow you can e:ecute the selected transaction. Dere you should in&ut +alues in all the (ields you intend to (ill with the +alues (rom you legacy data later. )(ter the recording has (inished, you can &rocess it. 'ou can delete or add (ields.
/2
&rocess (ecording 'ou can assign (ield names (reely. /uring the generation o( the batch in&ut session, the contents o( these (ields are assigned to the target (ields dis&layed in the le(t column. The (ollowing (unctions are a+ailable2 Defa'lt2 )ssigns the (ield name o( the rele+ant target (ield and its (ield descri&tion. (eset2 /eletes (ield names and (ield descri&tions. /ouble%click2 8dits (ields names, (ield descri&tions and de(ault +alues.
Im #ortant
Go may se field names re#eatedly" 7o8e0er, in field ma##ing a field name !an only be sed on!e" 0or all (ields in which you did not s&eci(y a (ield name the s&eci(ied de(ault +alue is used (or the batch in&ut session generation. Thus these de(ault +alues can be considered as constants. This is use(ul in &articular with check bo:es (e.g. MM41, +iew selection!. )(ter you sa+ed, the status line dis&lays the (ollowing message2 /ata sa+ed success(ully . The recording is now a+ailable among the attributes (or the ob1ect.
/3
2 Trans#ort %SM& Pro;e!ts

The LSM Workbench &ro+ides data trans&ort (or a &ro1ect +ia both the "#$ trans&ort system and down%#u&load. (8:cluded are the &resettings (or ./oc inbound &rocessing. These &resettings should be manually created in e+ery "#$ system and e+ery client.!
2"1 =enerate C$ange ReF est

@hoosing this (unction creates an "#$ change request containing all in(ormation about an LSMW &ro1ect. This "#$ change request can be e:&orted # im&orted with the usual means o( "#$ correction and trans&orting. 'ou can (ind this (unction in the initial screen under Extras "# Create change re:'est. When trans&orting LSMW data this way, you can trace the trans&orts any time in "#$ correction and trans&orting.
Note 1( When im&orting such a request, the com&lete &ro1ect is deleted (rom the target system (irst. .t is then created again.
Note 2( When e:&orting the trans&ort request, all changes to the selected &ro1ect made until the time o( e:&ort are entered (not only until the time o( creation o( the trans&ort request.!
2"2 DA#ort Pro;e!t

.n the initial screen, select Extras Export pro%ect. This (irst dis&lays the structure tree o( the selected &ro1ect. Via Select 4 Deselect you can select whether the entire &ro1ect or &arts o( the &ro1ect are e:&orted. Then select Export. The &rogram then creates an )S@.. (ile.
/*
Export &ro%ect- *ro1ect Table o( @ontents
Note2 The selected elements are e:&orted together with their documentation.
2"3 Im#ort Pro;e!t

The e:&orted ma&&ing and rules can be im&orted into another "#$ system. 6n the selection screen, select Extras "# !mport. The &rogram then &rom&ts you to enter the name o( the *@ (ile. The (ile is im&orted and the contents are analyEed. )(ter the analysis, a list o( the sub&ro1ects and ob1ects (ound is dis&layed. 'ou can now mark the ob1ects to be im&orted. *ro1ect data e:isting already are check%marked. They are o+erwritten by the im&ort. 'ou can &re+ent a &ro1ect already e:isting in the target system (rom being o+erwritten by using (unction .m&ort under di((erent name .
Note2 The selected elements are im&orted together with their documentation.
/.
4 Periodi! Data Transfer

To a limited e:tent, the LSM Workbench also su&&orts &eriodic data trans(er. *reconditions are2 The LSMW ob1ect has been created and tested com&letely. The source a&&lication &eriodically makes a+ailable one or se+eral (iles on the "#$ a&&lication ser+er. The LSMW ob1ect does not access (iles on the (rontend. (0iles on the (rontend cannot be read in batch mode.!
.( all these conditions are met, you can set select button *eriodic in ste& Maintain ob1ect attributes . Then, ste& @ontrol &rogram (or &eriodic data trans(er is dis&layed in the o+er+iew o( work ste&s. This &rogram carries out the (ollowing ste&s in sequence2

"ead data @on+ert data .m&ort data
This &rogram (name2 /SAPDMC/SAP_LSMW_INTERFACE ! can be used according to your requirements.
//
Frame &rogram for &eriodic Data *ransfer- Selection Screen
/2
Note 12 S&eci(ication o( a (lag (ile is o&tional.
Note 22 ) (lag (ile ser+es (or creating a handshake with the a&&lication &ro+iding the in&ut (ile(s!2 The control &rogram (or &eriodic data trans(er is only e:ecuted i( the s&eci(ied (lag (ile e:ists. )(ter (inishing data trans(er, the control &rogram (or &eriodic data trans(er deletes the (lag (ile. The &ro+iding a&&lication should beha+e in a com&lementary way2 -e(ore new (iles are created, a check is carried out as to whether the (lag (ile e:ists. .( this is the case, the &rogram sto&s. 6therwise, the (iles are generated, and the (lag (ile is created.
Note 32 Some o( the standard batch in&ut and direct in&ut &rograms use additional &arameters. Some o( these &arameters are also used in other &rograms. 0or in(ormation about which &arameters are used in which &rogram, &lease re(er to the coding o( &rogram /SAPDMC/SAP_LSMW_INTERFACE. *rogram Test run without u&date
RAALTD0 1 RAALTD1 1 RCCLBI01 RCCLBI02 RCCLBI03 RCCTBI01 RCSBI010 RCSBI020 RCSBI030 RCSBI040 RCVBI010 RFBIBL00 RHALTD0 0 RLBEST00 RLPLAT00 RM DATIN D RPUSTD0 0
*arameter used @reate batch in&ut session -., /., @all Transaction, Test Lock mode )ction Bser grou&
7 7 7 7 7 7 7 7
/4
Note *2 'ou can s&eci(y +ariants (or the read &rogram, the con+ersion &rogram and (in case -atch#/irect .n&ut! the -atch or /irect .n&ut &rogram. These +ariants ha+e to be de(ined be(ore.
/5
5 %ong TeAts
To trans(er long te:ts, there are two &ossibilities2 /irect in&ut &rogram #S)*/M@#S)*JLSMWJ.M*6"TJT87TS (ob1ect 4441, method 4441!K this ob1ect is not a+ailable in the standard &rogram. To make it a+ailable, run the (ollowing &rogram: /SAPDMC/SAP_LSMW_SXDA_TEXTS /irect in&ut &rogram "ST7L.T0 (ob1ect =444, method 4444!K to be able to use this ob1ect, you ha+e to download the trans&ort (rom S)*58T (htt&2##ser+ice.sa&.com#LSMW! and im&ort it into your system
5"1 %ong TeAts in t$e R/3 System

Long te:ts (te:ts co+ering more than one line! are stored in a te:t &ool in "#$. The key o( a long te:t is com&osed o( (our &arts2 Hey field OB6ECT ID Meaning )&&lication ob1ect Te:t ./ DAam#le )B0Q P 6rder te:ts 6b1ect A/F8 NA.E SPRAS )ctual te:t key Language .d 8OPF P 6rder header te:t .d POSN P 6rder item te:t .d R.EL P 6rder con(irmation te:t >4 1%= (none! T992 3 C$e!' table TT7OB, TT7OT TT7ID, TT7IT
%engt$ 14
6rder number Te:t language
2+
5"2 Determine TeAt Hey Str !t re

There is no uni(orm rule (or the structure o( the actual te:t key NA.E. To determine the +alues (or OB6ECT and ID (or a s&eci(ic te:t ty&e and the structure o( NA.E, &roceed as (ollows2

/is&lay a te:t o( the required te:t ty&e (e.g. order header te:t! and branch o(( to the editor. There you can dis&lay the required in(ormation +ia /oto ;eader2
The (ollowing a&&lies in the abo+e e:am&le o( a material sales te:t2 6-C8@T P MVQ8 ./ P 4441 5)M8

Material number (1? characters! ; Sales organiEation (3 characters! ; /istribution channel (= characters!
21
5"3 De0elo# 6b;e!ts for %ong TeAts 0ia 6b;e!t +++1

The (ollowing target structures are a+ailable2 /SAPDMC/LTXTH2 Long te:t header

ST'*8 "ecord ty&e (technical (ield, +alue P N1N! 6-C8@T ./ S*")S ST'*8 T87TL.58 )&&lication ob1ect Te:t ./ Language "ecord ty&e (technical (ield, +alue P N=N! )&&lication ob1ect 5)M8 Te:t name
/SAPDMC/LTXTL2 Long te:t te:t line

T87T06"M)T 0ormat (ield (= characters!
0ield T87T06"M)T contains te:t (ormatting in(ormation. To sim&ly ma& the (ield 121, enter character NVN. 0or the material sales te:t in the e:am&le, a migration ob1ect could look as (ollows2
Long *exts- Source 0ields
22
Long *ext- Structural "elationshi&s
23
Long *ext- 0ield Ma&&ing
Note2 Statement onJchangeJtrans(erJrecord. has the e((ect that the te:t header is trans(erred only, i( it has changed com&ared to the &re+ious record (see A.A.$!.
2*
5"* De0elo# 6b;e!ts for %ong TeAts 0ia 6b;e!t 2+++

*lease ha+e a look at the documentation (or &rogram "ST7L.T0 (irst. There you will (ind +ery use(ul in(ormation concerning the (ile (ormat the im&ort &rogram needs. The (ollowing target structures are a+ailable (de(ined during the im&ort o( ob1ect =444!2 #S)*/M@#LSMWJT87TDT87T #S)*/M@#LSMWJT87T6-C8QT #S)*/M@#LSMWJT87T5)M8 #S)*/M@#LSMWJT87T./ #S)*/M@#LSMWJT87TL)5GB)G8 #S)*/M@#LSMWJT87T06"M #S)*/M@#LSMWJT87TST'L8 #S)*/M@#LSMWJT87T0."STBS8" #S)*/M@#LSMWJT87T0."ST/)T8 #S)*/M@#LSMWJT87T0."STT.M8 #S)*/M@#LSMWJT87TL)STBS8" #S)*/M@#LSMWJT87TL)ST/)T8 #S)*/M@#LSMWJT87TL)STT.M8 #S)*/M@#LSMWJT87TT.TL8 #S)*/M@#LSMWJT87TT.TL81 #S)*/M@#LSMWJT87TT.TL8= #S)*/M@#LSMWJT87TM).5 #S)*/M@#LSMWJT87TL.58
Most o( the (ields (or these structures are technical (ields and are (illed by de(ault.
) migration ob1ect could look as (ollows2
Source 0ields
2.
Structural "elationshi&s
2/
22
24
5". Im#ort TeAts

Te:ts are im&orted into the "#$ system by means o( direct in&ut. The rele+ant direct in&ut &rogram can be easily called (rom the LSM Workbench +ia Start Direct !np't Session.
Im #ortant
)(ter the im&ort o( long te:ts, sometimes these cannot be read within the corres&onding a&&lication. Via (unction module N"8)/JT87TN, the te:ts are (ound, thus, they are stored correctly in the database. Some a&&lications ha+e a (ield in the master data which shows whether a long te:t e:ists or not. This (ield is not (illed by the direct in&ut &rograms (since these &rograms a&&ly to all a&&lications, and at runtime it is not known which a&&lication a te:t belongs to. There are = &ossible solutions2 1. The (lag is su&&lied by a user%de(ined re&ort a(ter the im&ort =. .n the (ield assignments # ma&&ing an u&date is coded on the res&ecti+e tableK howe+er, this that the (lag is set already during the con+ersion i( the te:t is not im&orted later, the (lag is set, howe+er, no long te:t is a+ailable.
25
1+ Ti#s and Tri!'s

1+"1 Determine t$e Transa!tion Code at R ntime
Sit ation 2 'ou want to trans(er data a &art o( which has already been created in the system. 'ou want to decide at runtime whether the data is created or changed. DAam#le2 @ustomer master Sol tion 2 .nsert under Global /ata 2 TABLES3 8NA1. )dd the (ollowing coding (or (ield -Q544%T@6/82 Se)e,! ,-& !:;< +r-m 2 a1 =(ere 2& $+ s>?d1, ! # 9. 12 99?!,-de # %7D91%. e)se. 12 99?!,-de # %7D92%. e d$+. r # <a)!e_2& de &mmer".
1+"2 S'i# a Re!ord

Sit ation 2 'ou want to ski& a record de&ending on a certain condition, i.e. this record shall not be con+erted and trans(erred to the out&ut (ile Sol tion 2 $+ <,- d$!$- ". s2$'_re,-rd. e d$+.
1+"3 S'i# All Re!ords of a Transa!tion

Sit ation 2 'ou want to ski& all records o( a transaction de&ending on a certain condition. Sol tion 2 $+ <,- d$!$- ". s2$'_!ra sa,!$- . e d$+.
1+"* D #li!ate a Re!ord

Sit ation 2 'ou want to create two (or more! target records (rom a source record. DAam#le2 'our customer master o( legacy (iles consists o( one record containing among other things the (ields 0irst name , 5ame , *hone number (or two contact &ersons. .n "#$, a -Q5VQ record has to be (illed (or each contact &erson. Sol tion 2 'our legacy structure is assumed to look as (ollows2 C/ST C&s!-mer mas!er ... @ORNA.E1 F$rs! ame -+ +$rs! ,- !a,! 'ersNACHNA.E1 Name -+ +$rs! ,- !a,! 'ersTELEFON1 P(- e &m1er -+ +$rs! ,- !a,! 'ers@ORNA.E2 F$rs! ame -+ se,- d ,- !a,! 'ersNACHNA.E2 Name -+ se,- d ,- !a,! 'ersTELEFON2 P(- e &m1er -+ se,- d ,- !a,! 'ers... 4+
Legacy System Migration Workbench @reate the (ollowing rules2 ... B8N@8?NA.E1 C/ST?NACHNA.E1 :.-*e< B8N@8?TELF1 C/ST?TELEFON1 :.-*e< B8N@8?NA.E@ C/ST?@ORNA.E1 :.-*e< and add End_of_Record B8N@8?NA.E1 # C/ST?NACHNA.E2. B8N@8?TELF1 # C/ST?TELEFON2. B8N@8?NA.E@ # C/ST?@ORNA.E2. transfer_record. ... at &rocessing time. This creates two -Q5VQ records.
41
11 <#grade from %SM& 1"+ to %SM& 1"/

11"1 Differen!es -et8een 1ersion 1"+ and 1ersion 1"/ of t$e %SM &or'ben!$
The (ollowing lists the main di((erences between +ersion 1.4 and 1.6 o( the LSM Workbench2 Transa!tion !ode2 The transaction code is LSMW (in +ersion 1.42 /LSM !. Version 1.4 is still a+ailable a(ter installing +ersion 1.6. Hey field names2 5ew2 *ro1ect instead o( Legacy system , Sub&ro1ect instead o( Legacy system release , 6b1ect instead o( Migration ob1ect . )ll these key (ields now ha+e a length o( 14 &laces (in +ersion 1.4, they had (our &laces!. Naming !on0ention 2 The names (or &ro1ect, sub&ro1ect and ob1ect can be assigned (reely without any restrictions. C$anged des!ri#tion 2 5ew2 "ecording instead o( Bser%de(ined migration ob1ect class . The name o( a recording may ha+e u& to 14 characters and should meet the )-)* naming con+entions (e.g. (irst character P letter!. 8+ery recording is assigned to e:actly one &ro1ect. C$anged des!ri#tion 2 5ew2 "eusable rules instead o( @entral rules . 6b;e!t attrib tes2 .n the ob1ect attributes, the ob1ect and im&ort ty&es are de(ined. (.n +ersion 1.4, this de(inition was already made +ia the selected ob1ect name.! 'ou can now assign any number o( recordings to an ob1ect. Im#ort te!$niF es2 .n addition to standard batch in&ut#standard direct in&ut and recording, -)*. and ./ocs are a+ailable as additional im&ort techniques. So r!e str !t res2 The name may ha+e a length o( u& to =A characters. .n(ormation on the identi(ication o( a record is now (ound with the source (ields. 5ow, you can also de(ine se+eral structures at the to& hierarchy le+el. So r!e fields 2 5ow, additional (ield ty&es (or amount (ields )MT1, )MT=, )MT$, )MT3 are a+ailable. The record descri&tion o( a structure can be com(ortably trans(erred +ia the Copy symbol (rom +arious sources2 B&load (rom (ile, co&y o( another ob1ect, co&y (rom /ata "e&ository, (rom data (ile (with (ield names in the (irst line!. 0ields (or structures o( the to& hierarchy le+el can be marked as selection &arameters ((or !mport4convert data!. Str !t ral relations2 The &rogram dis&lays the in(ormation whether a structure is a required segment. 9ield ma##ing and r les2

Dis#lay 0ariant2 'ou can select the elements to be dis&layed2 Global data, &rocessing times, technical (ields, initial (ields, coding. Pro!essing times2 'ou can com&lete the )-)* coding at +arious times o( data con+ersion. .n +ersion 1.4, you used additional includes with user%de(ined routines. 9ield do! mentation, 9* $el# 2 Symbols &er target (ield So r!e fields not assigned 2 Men' Extras So'rce fields not assigned dis&lays the source (ields that are not assigned. Additional !on0ersion te!$niF es 0ia # s$b tton( *re(i:, su((i:, trans(er le(t%1usti(ied, user%written routine =lobal f n!tions( .n addition to the (unctions !ra s+er_re,-rd and s2$'_re,-rd already a+ailable in +ersion 1.4, other (unctions are a+ailable2 !ra s+er_!($s_re,-rd, a!_+$rs!_!ra s+er_re,-rd, - _,(a ge_!ra s+er_re,-rd, !ra s+er_!ra sa,!$- , s2$'_!ra sa,!$- . Dditor( @heck the coding (or a target (ieldK insert source (ields, global +ariables, global (unctionsK *retty *rinter. 42
Com#arison 8it$ Data Re#ository2 5o longer required. &7DRD relations$i#s 2 5o longer required. 9iles2 )ll de(initions in connection with (iles are merged in the two &rocessing ste&s Specify files and $ssign files. Dere XVL may be used as wildcard. Im ort data2 "e&laces and enhances (unctions Spreadsheet !nterface and ;ost !nterface o( +ersion 1.4. 5ow, you can use any combination o( *@ and ser+er (iles. /ate (ields and amount (ields are con+erted into an internal or calculation (ormat by de(ault. .( required, the (ile im&ort &rogram generates itsel( again. ,on.ert data2 The data to be con+erted is &rocessed target%oriented. A!tion log2 )ll actions (or an ob1ect are stored in an action log. Do8nload/ #load r les2 @an now be carried out simultaneously (or all &arts o( a &ro1ect. The dataset &roduced in this &rocess is considerably smaller than in +ersion 1.4. Dis#lay/!$ange 2 .n many (unctions you can switch between Display and Change. Do! mentation 2 'ou can store your documentation at a total o( =A le+els. The total documentation (or a &ro1ect can be (urther &rocessed in hierarchical (orm. Re!ordings2 Version 1.6 does not generate a data re&ository structure (or a recording. The data o( a recording are stored in LSMW internal tables. There is no change (rom the userMs &oint o( +iew.
43
12 Transfer of %SM& Data from 1ersion 1"+ to 1ersion 1"/

When trans(erring data (rom other systems, e:&ort them under +ersion 1.4 and im&ort them under +ersion 1.4 as well. To trans(er data to 1.6, use LSM Workbench *ransfer LSMW data from version < on the initial screen. The same a&&lies to trans(erring data (rom the same system. 5ormally all LSM Workbench data trans(erred using the standard &rocedure can easily be trans(erred into +ersion 1.6. S&ecial (eatures to be taken into account mainly concern ad+anced users who already made com&le: modi(ications to the LSM Workbench during data migration with LSM Workbench +ersion1.4. Please ta'e into a!!o nt( Version 1.6 no longer has a generation lock. Bser%written )-)* coding should be checked +ia synta: check. Bser%de(ined translation +ariants will be lost. .ncludes created in +ersion 1.4 and included in the ob1ect attributes +ia (lag should be trans(erred manually. .( you used perform skip_record or perform transfer_record so (ar, you can assign a corres&onding &rocessing time to the coding now. The s&eci(ications (or identi(ying source structures in (iles should be maintained subsequently this means2 i( there is data (or more than one structure in a source (ile the s&eci(ications had to be done +ia o((set and +alue during the de(inition o( the source structuresK in +ersion 1.6 the s&eci(ication is done +ia (ield L.denti(ying (ield +alueM in the de(inition o( the source (ields )(ter trans(erring the data (rom +ersion 1.4, (ield ma&&ing should be checked in any case. .( you used recordings, you should switch to change mode (or each recording and sa+e the changes there.
4*
13 <#grade from %SM& 1". to %SM& 1"/

13"1 Notes on t$e <#grade to %SM& 1"/
)ll ob1ects created under LSMW 1.A are ke&t in LSMW 1.6. Trans(erring data (rom LSMW 1.4 to LSMW 1.6 is still &ossible. Trans&orting rules (rom LSMW 1.A to LSMW 1.6 is &ossible. Vice +ersa, the s&eci(ications (or the (iles may ha+e to be corrected. The (ile settings may ha+e to be corrected. 0irst, run #S)*/M@#S)*JLSMWJ"8*)."J1A once, and check the settings ( S&eci(y (iles !. &rogram
@heck the (ieldma&&ing (or 8V8"' 6-C8@T. .( you ha+e created coding (or the &rocessing &oints JJ-8G.5J60J"8@6"/JJ, sa+e this. Then restore the de(ault. 0inally you can insert your own coding again. )ll &rograms generated in LSMW 1.A ha+e to be regenerated manually.
13"2 Corre!tions
Ste# n mbering and 8el!ome #o# # 2 5umbering 6n#6(( %%U Welcome &o&u& is dis&layed again2 8rror corrected. Interfa!es of f n!tion mod les !om#atible 8it$ *"+ 2 .n some (unction modules, tables with re(erence ty&e are used. The entered ty&e is a structure, howe+er. This is tolerated in 3.4-. When testing the indi+idual (unction module, a synta: error is re&orted, howe+er. Create !$ange reF est2 5o authoriEation check2 was added. 6b;e!t attrib tes2 When &ressing 03 (or standard -.#/. ob1ects, ob1ects with numbers T ?444 are dis&layed only2 8rror corrected. 9ield ma##ing 2 /escri&tions and documentation (or target (ields o( ./oc segments were &artly not (ound2 8rror corrected. <ser-8ritten ro tines2 /uring creation, 1 in&ut &arameter and 1 out&ut &arameter were assumed automatically. 5ow, these +alues can be entered in a &o&u&. Dis#lay data read #rogram, data !on0ersion #rogram 2 When one o( these (unctions were called be(ore the corres&onding &rogram had been created, a termination occurred2 8rror corrected. Dis#lay read data2 6n the detail screen, &acked (ields were dis&layed without decimal &laces2 8rror corrected. =enerate t$e data !on0ersion #rogram 2 Bnder certain conditions, the rules were con(used2 8rror corrected. Co#y an ob;e!t2 03 % Del& (or sub&ro1ect, ob1ect, source structure did not work2 8rror corrected. When the ob1ect contained wildcards, the co&y &rocess abended2 8rror corrected.
13"3 De0elo#ments
Dis#lay I-J !$ange 2 .n the ste&s screen you can s&eci(y whether the &rogram switches to dis&lay or change mode when you double%click. So r!e fields2 0ield de(inition is now &ossible with table control as well. 9ield ma##ing, dis#lay attrib tes 2 .tem JJ06"MJ"6BT.58SJJ is dis&layed se&arately (or selection. Technical (ields are marked with rulety&e R/e(ault settingS. The de(ault setting can be restored +ia Extras (estore defa'lt. The &rocessing &oint JJ-8G.5J60J"8@6"/JJ is &reset.
4.
=lobal f n!tions 2 )dditional global (unction trans(erJthisJrecord N77777N, to trans(er the s&eci(ied segment. S#e!ify file2 StandardiEation2 0ile on the 0rontend and (iles on the a&&lication ser+er. )ll (iles can (inde&endent o( the location!

contain data (or one or more source structures, ha+e se&arators or not, (ield names at the start o( the (ile (one record &er source structure! or not, be a te:t or binary (ile, ha+e a di((erent @ode&age. 0rom a&&lication ser+er2 all @ode&age 0rom 0rontend2 )S@.. or .-M%/6S
Defa lt file names for read and !on0erted data 2 -lanks within a word are re&laced by underscores. Read data2 Bsage o( sorted internal tables yielding a massi+e &er(ormance gain when merging se+eral (iles. IDo! inbo nd #ro!essing 2 'ou can now additionally s&eci(y a t"0@ &ort. /uring data con+ersion you can determine whether a (ile is to be created or the data is directly trans(erred in &ackages to (unction module ./6@J.5-6B5/J)S'5@D"656BS. (This (unction module creates ./ocs in the database.! @ontrol &rogram (or &eriodic data trans(er2 5ow also works together with wildcards (V! in (ile names. Some im&ortant &arameters o( -.#/. &rograms are (orwarded to the outside.
4/
1* 9inal Remar's
There only is to wish you success in your data migration &ro1ect. We are looking (orward to recei+ing your (eedback (e%mail2 lsm9sa&.com ! 'ours sincerely 'our S)* LSMW team
42

Data Migration of Non-SAP Systems To R/3: September 5, 2000

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Data Migration of Non-SAP Systems To R/3: September 5, 2000

Uploaded by

Copyright:

Available Formats

Data Migration of Non-SAP Systems to R/3

lsm@sa .com Se tember !" #$$$

Legacy System Migration Workbench

Legacy System Migration Workbench

1"2 %SM &or'ben!$( &$at is it)

1"3 S ##orted R/3 Releases

1"/ %SM &or'ben!$ 1ersions

1"4 Signifi!an!e of Data Migration

1"5 -asi! Prin!i#les of t$e %SM &or'ben!$

Legacy System Migration Workbench

A!!elerating Data Migration( %SM &or'ben!$ 7o8 %SM &or'ben!$ 8or's

-at!$ In# t #ro!essing Dire!t In# t #ro!essing IDo! inbo nd #ro!essing

S)* )G Culy 1<<<

Schematic Flow of Data Migration with the LSM Workbench

Legacy System Migration Workbench

Legacy System Migration Workbench

3 Start # and Pre#arations

3"2 Initial Transa!tion

3"3 Pro;e!t, S b#ro;e!t and 6b;e!t

Example for a &ro%ect Str'ct're

3"* <ser = idan!e

Legacy System Migration Workbench

LSM Workbench- *he Main Steps of Data Migration

Legacy System Migration Workbench

&ersonal Men'- $ll &rocessing Steps $vailable

3". 9ield Ma##ing on Pa#er

Legacy System Migration Workbench

3"/ Create 6b;e!t 60er0ie8

Legacy System Migration Workbench

+b%ect +verview- General /ata, Structures, Structure "elations

+b%ect +verview- Source Structures # Target Structures

Legacy System Migration Workbench

6b1ect 6+er+iew2 "ules

6b1ect o+er+iew in table (orm 1*

Legacy System Migration Workbench

6+er+iew o( "eusable "ules

Legacy System Migration Workbench

LSM Workbench2 )dministration

Legacy System Migration Workbench

LSM Workbench2 "ecordings

3"5 Pre#arations for <sing IDo! Inbo nd Pro!essing

Legacy System Migration Workbench

LSM Workbench- Settings (or ./oc .nbound *rocessing

/SAPDMC/SAP_LSMW_PARTNERTYPES READ_USER any

-cti.ate I/oc inbound rocessing

@on(irm with 'es (to be done once (or each system!

Veri%y work%low customi0ing (to be done once (or each system!

1erifying Workflow C'stomi2ing

Legacy System Migration Workbench

* =eneral Ti#s for t$e Pro!ed re

Get acquainted with the terminology o( the rele+ant data ob1ect.

S&eci(y 0ield names 0ield descri&tion /e(ault +alues

/e+elo& field ma##ing and !on0ersion r les.

Bse the ob%ect overview (or 0ield ma&&ing on &a&er .

Read data O automatically by &ushing a button Con0ert data

Maintain the re sable r les(

Maintain the translation tables (03 hel& (or right%hand column!.

Legacy System Migration Workbench S&eci(y your (i:ed +alues.

/e&ending on the ob1ect ty&e2

/irect in&ut Start direct in&ut session.

Legacy System Migration Workbench

. Data Migration > Ste# by Ste#

."1 Maintain 6b;e!t Attrib tes