LSMW Complete Guide

Data Migration of Non-SAP Systems to SAP-Systems
Quick Introduction to Working with the Legacy System Migration Workbench Version 1.7
lsm@sa .com !o"ember 1# $%1&
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 RELEASES.....................................................................................................................................4 1.4 COSTS...............................................................................................................................................................4 1.5 DELIVERY.........................................................................................................................................................4 1.6 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............................................................................................................................................1' 3.5 FIELD MAPPIN" ON PAPER.............................................................................................................................12 3.6 CREATE OB%ECT OVERVIEW..........................................................................................................................13 3. ADMINISTRATION...........................................................................................................................................1 3.! RECORDIN"S..................................................................................................................................................1 3.# PREPARATIONS FOR USIN" IDOC INBOUND PROCESSIN"..............................................................................1! 4 GENERAL TIPS FOR THE PROCEDURE IN A MIGRATION USING LSMW AND DXWORKBENCH......................................................................................................................................................24 4.1 R(3)CUSTOMI$IN" .........................................................................................................................................25 4.2 WHICH DATA SHOULD BE MI"RATED?...........................................................................................................25 4.3 RUN THE MANUAL PROCESS...........................................................................................................................25 4.4 WHICH IMPORT TECHNI*UE WILL BE USED?..................................................................................................25 4.5 CREATE THE RECORDIN"...............................................................................................................................25 4.6 DETERMINE THE SOURCE STRUCTURES..........................................................................................................26 4. CREATE TEST DATA IN D+)WORKBENCH......................................................................................................26 4.! MAPPIN" ON PAPER.......................................................................................................................................26 4.# ENTER THE RULES AND TEST OUT OF LSMW................................................................................................26 4.1' CREATE PRO%ECT& SUBPRO%ECT AND RUN IN D+)WORKBENCH..................................................................26 4.11 IMPORT THE DATA........................................................................................................................................2 5 DATA MIGRATION STEP B! STEP..........................................................................................................28 5.1 MAINTAIN OB%ECT ATTRIBUTES....................................................................................................................2! 5.2 MAINTAIN SOURCE STRUCTURES..................................................................................................................2# 5.3 MAINTAIN SOURCE FIELDS............................................................................................................................31 5.3.1 Create Individual Source Fields............................................................................................................31 5.3.2 Maintain Source Fields in Table Form..................................................................................................34 5.3.3 Copy Source Fields from t!er Sources................................................................................................35 5.4 MAINTAIN STRUCTURAL RELATIONSHIPS......................................................................................................36 5.5 MAINTAIN FIELD MAPPIN" AND CONVERSION RULES..................................................................................3! 5.5.1 For t!e "dvanced #ser$ %isplay &ariant' (rocessin) Times................................................................41 5.5.2 For t!e "dvanced #ser$ *lobal &ariables............................................................................................43 5.5.3 For t!e "dvanced #ser$ *lobal Functions............................................................................................43 5.5.4 For t!e "dvanced #ser$ +eusable +ules , -amin) Conventions........................................................44 5.6 MAINTAIN FI+ED VALUES& TRANSLATIONS AND USER)WRITTEN ROUTINES.............................................................................................................................................................46 5. SPECIFY FILES...............................................................................................................................................4# 5.! USE WILDCARDS IN FILE NAMES..................................................................................................................56 5.# ASSI"N FILES................................................................................................................................................5! 5.1' READ DATA................................................................................................................................................5! 2
Legacy System Migration Workbench 5.1..1 %isplay +ead %ata...............................................................................................................................5/ 5.11 CONVERT DATA..........................................................................................................................................5# 5.11.1 *eneral +emar0s..................................................................................................................................5/ 5.11.2 "dditional Function for 1"(I2I%oc.....................................................................................................3. 5.12 DISPLAY CONVERTED DATA........................................................................................................................61 5.13 IMPORT DATA..............................................................................................................................................61 5.13.2 Import %ata 4it! %irect Input.............................................................................................................31 5.13.3 Import %ata 4it! 1"(I or I%oc Tec!ni5ue.........................................................................................32 " RECORDINGS..................................................................................................................................................."3 6.1 DETAILED DESCRIPTION OF THE PROCESS.....................................................................................................63 7 TRANSPORT LSMW PRO#ECTS.................................................................................................................."" .1 "ENERATE CHAN"E RE*UEST.......................................................................................................................66 .2 E+PORT PRO%ECT...........................................................................................................................................66 .3 IMPORT PRO%ECT............................................................................................................................................6! 8 PERIODIC DATA TRANSFER......................................................................................................................."$ $ LONG TEXTS....................................................................................................................................................72 #.1 LON" TE+TS IN THE SAP SYSTEM................................................................................................................ 2 #.2 DETERMINE TE+T KEY STRUCTURE.............................................................................................................. 3 #.3 DEVELOP OB%ECTS FOR LON" TE+TS VIA OB%ECT '''1............................................................................... 4 #.4 DEVELOP OB%ECTS FOR LON" TE+TS VIA OB%ECT 2'''............................................................................... #.5 IMPORT TE+TS...............................................................................................................................................!1 1% TIPS AND TRICKS.........................................................................................................................................82 1'.1 DETERMINE THE TRANSACTION CODE AT RUNTIME...................................................................................!2 1'.2 SKIP A RECORD...........................................................................................................................................!2 1'.3 SKIP ALL RECORDS OF A TRANSACTION....................................................................................................!2 1'.4 DUPLICATE A RECORD................................................................................................................................!2 1'.5 E+TRA HANDLIN" FOR ,POS)IDOCS-........................................................................................................!3 11 UPGRADE FROM LSMW 1.% TO LSMW 1.7.............................................................................................85 11.1 DIFFERENCES BETWEEN VERSION 1.' AND VERSION 1.
OF THE
LSM WORKBENCH................................!5
12 TRANSFER OF LSMW DATA FROM &ERSION 1.% TO &ERSION 1.7................................................87 13 UPGRADE FROM LSMW 1.5 TO LSMW 1.7.............................................................................................88 13.1 NOTES ON THE UP"RADE TO LSMW 1. ....................................................................................................!! 13.2 CORRECTIONS.............................................................................................................................................!! 13.3 DEVELOPMENTS..........................................................................................................................................!! 14 FINAL REMARKS..........................................................................................................................................$%
1 Introduction
1 1 Pur!ose of t"is Introduction
This introduction is intended to allow a quick entry into the work with the Legacy System Migration Workbench Version 1.7 ( LSM Workbench !.
1 2 #SM $or%benc"& $"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 S)* systems1 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 S)* 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 Su!!orted (eleases
Version 1.7 (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 - Deli/ery
The LSM Workbench is not &art o( the standard S)* 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<%=>>7%73>?<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%benc" 0ersions

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.
S)*%System includes S)*%"#$, )*6 >.4 and @"M $.4B LSMW has its own names&ace and there are no &roblems known with the industry solutions yet
Legacy System Migration Workbench .n )ugust 1<<?, +ersion 1.4 o( the LSM Workbench was made a+ailable to the &ublic. Cntil today, LSMW has been requested more than 1,444 times. .n Dune 1<<<, +ersion 1.A o( the LSM Workbench has been released. Since Duly 1<<<, +ersion 1.= , since se&tember >444 +ersion 1.7 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.7 com&ared with +ersion 1.4.
1 1 Su!!ort
0or &roblem messages +ia S)*5et (6nline Ser+ice System!, entry 22-#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/, E", 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 3 Significance of Data Migration

/ata migration comes in the end o( S)* im&lementation. )t this time, the S)* system is normally installed and a&&lication customiFing is (inished (in the best case!. )n e:amination o( S)* im&lementation &ro1ects by S)* @onsulting has shown that data migration is about >4G o( the total im&lementation e:&enses. This &ortion may rise u& to 34G 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 S)* im&lementation &ro1ects are +ery &romising2 -oth the e:&enses and the costs o( data migration could be reduced signi(icantly.
1 4 ,asic Princi!les of t"e #SM $or%benc"

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 customiFed in the (rame o( migration customiFing 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
Legacy System Migration Workbench Most o( the (unctions should reside in the S)* system. 5o collection o( indi+idual &rograms on di((erent &lat(orms. The quality and consistence o( the data im&orted into the S)* system 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
Accelerating Data Migration& #SM $or%benc" 7o8 #SM $or%benc" 8or%s

5ne or se/eral files
#egacy data on PC
(ead data Structure relations 9ield ma!!ing Con/ersion rules Con/erted data
(ead data
#egacy data on a!!lication ser/er
Con/ert data
(63 Standard
,atc" In!ut !rocessing Direct In!ut !rocessing IDoc inbound !rocessing
S)* )H Duly 1<<<
>1
Schematic Flow of Data Migration with the LSM Workbench
The main ad+antages o( the LSM Workbench+ *art o( the S)* system 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. Heneration 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 Preconditions
The LSM Workbench is a tool that su&&orts data trans(er (rom non%S)* systems to S)* systems. 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 S)* a&&lication! -e(ore you can a&&ly the LSM Workbench, you absolutely need a data migration conce!t. The (ollowing items should be considered in &articular2 Make sure that S)* customiFing 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 the S)* system 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 the S)* system +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 the S)* system 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)* systemI 5ote2 The LSMW does not e:tract data. .n which (orm is the legacy data a+ailableI /etermine accordingly which o( the LSMW (unctions will be a&&lied. .( only a &art o( your legacy system will be re&laced by S)*, 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 must absolutely be ans8ered before t"e tool 8ill be usedJ
3 Startu! and Pre!arations

3 1 Aut"ori:ations
Aut"ori:ation le/el /is&lay Profile -KLSMWKSE6W 9unction The user can dis&lay all &ro1ects he has the authoriFation (or and their work ste&s. Ee#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 authoriFation, and can change and co&y ob1ects. The user can use all (unctions made a+ailable by the tool.
8:ecute @hange
-KLSMWK878@ -KLSMWK@EH
)dministrate
-KLSMWK)LL
Please note2 The &ro(iles listed abo+e are not included in the &ro(iles o( the standard S)* system. There(ore you ha+e to ado&t them (enter the &ro1ect names! and add the required &ro(iles to your user master record.
3 2 Initial Transaction
To start working with the LSM Workbench, use transaction #SM$2
LSM Workbench
!nitial Screen
3 3 Pro;ect+ Sub!ro;ect and 5b;ect

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 &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 =uidance
)(ter selecting an ob1ect, E)*E( or C+)*!),E leads you to the interacti+e &rocess guide. Eere you are guided through the indi+idual ste&s o( data migration.
1*
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 Eere 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 +ff2 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 Eere, 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.
11
&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 S)* 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 *@.
12
3 . Create 5b;ect 5/er/ie8

This (unction is a+ailable as &ushbutton in order to enable you to create an ob1ect o+er+iew at any time2
13
+b%ect +verview- Heneral /ata, Structures, Structure "elations
+b%ect +verview- Source Structures # Target Structures
1)
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 S)* 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 1 Administration
.n the initial screen, you can dis&lay the administration (unctions +ia /oto $dministration. Eere 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 3 (ecordings
.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. Eowe+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.
11
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 J Cse 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 =.
LSM Workbench2 "ecordings
3 4 Pre!arations for <sing IDoc Inbound Processing

./ocs (.ntermediate /ocuments! were de+elo&ed (or e:changing messages between di((erent systems ("#$ "#$B "#$ "#>B "#$ non%S)* system!. Since it is a standard inter(ace to the S)* 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.
13
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& 0ersion& 5utbound 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 0ersion2 (9C destination2 Name of !ort2 assigned by the system $ (./oc record ty&es S)* "elease 3.:! 5ame o( the S)* System Legacy System Migration Workbench
Then the partner type should be de(ined or selected. S)* recommends2 Partner ty!e2 CS (Cser!
)s o( release 3.A), this &artner ty&e is a+ailable in the standard system. C& 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 CS 14
Legacy System Migration Workbench (e!ort name& 9orm routine2 S"ort descri!tion&
/SAPDMC/SAP_LSMW_PARTNERTYPES READ_USER any
0inally a &artner number should be de(ined or selected. S)* recommends2 Partner number2 Partner ty!e2 Partner status2 Ty!e2 #anguage2 Person in c"arge2 LSMW CS ) (acti+e! CS /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 Heneric decision task classi(ied com&letely Sending to ob1ects and to E" ob1ects is acti+e
2*
Legacy System Migration Workbench To do this, you can start automatic customiFing. )(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 S)* 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.
21
22
Legacy System Migration Workbench 1erifying Workflow C'stomi2ing
23
) =eneral Ti!s for t"e Procedure in a migration using #SM$ and D2-$or%benc"
T./ LSM W0123/45. ( D+)W0123/45. 67 8 900: 9.89 7;<<0197 9./ 91847=/1 0= >898 =10? 404)SAP 7@79/?7 90 R(3. C01/ =;4596047 0= 9./ LSM W0123/45.: 1. I?<019 >898 =10? 8 :/A85@ 7@79/? 2. C04B/1964A >898 =10? 697 016A648: C:/A85@ 7@79/?D =01?89 90 9./ 981A/9 CSAPD =01?89 3. I?<01964A 9./ >898 ;764A 9./ 7984>81> 649/1=85/7 0= SAP CID05 6430;4> <105/7764A& 3895. 64<;9& >61/59 64<;9D C01/ =;4596047 0= 9./ D+ W0123/45.: 1. D898 6?<019 2. M04690164A =01 >898 6?<019 3. C1/89/ 84> />69 9/79 >898 4. R/79819 =;4596048:69@
LSMW -). DXWB /0(12. 3* 1/*. 4) '(534)-,4()
"ecommendation F01 3895. 64<;9 ( >61/59 64<;9: ;7/ 9./ 9/79 =;4596048:69@ 64 D+)W0123/45. 84> 1;4 9./ E.0:/ 6?<019 <105/77 =10? LSMW F01 BAPI ( ID05: ;7/ D+)E0123/45. 84> >0 ?8<<64A 84> 504B/17604 B68 84 LSMW 03F/59 G LSMW 584 3/ 58::/> =10? D+)E0123/45. 87 8 9872 C=10? 4.6C 04D
B/=01/ ;764A 9./ LSM W0123/45. 01 D+ W0123/45.& @0; 4//> 8 '()'*+, =01 >898 ?6A189604.
2)
) 1 (63-Customi:ing
Make sure that the Customi:ing o( your S)* system is (inished.
The ideal &ro1ect 2 0irst (inish customiFing Then, run data migration
) 2 $"ic" data s"ould be migrated'

A48:@H/ 9./ >898 /I67964A 64 9./ :/A85@ 7@79/? 90 >/9/1?64/ E.65. >898 E6:: 3/ 4//>/> 64 9./ =;9;1/ C8:70 =10? 8 3;764/77)0</1896048: <0649 0= B6/ED.
) 3 (un t"e manual !rocess

I>/496=@ 9./ 91847859604C7D 64 R(3 @0; E849 90 ;7/ =01 3164A64A 9./ >898 6490 9./ SAP S@79/?. H/1/& 69 ?8@ 8:70 3/ 1/:/B849 E./9./1 9./ >898 67 1/J;61/> =01 7989679658: C/B8:;89604D <;1<07/7 01 =01 =;19./1 <105/7764A 64 9./ 7@79/?. T/79 9./ 1/:/B849 91847859604 64 R(3 ?84;8::@ E69. 9/79 >898 =10? 9./ 0:> 7@79/? 84> ?82/ 7;1/ 9.89 8:: 1/J;61/> =6/:>7 81/ =6::/>. T./1/ ?8@ 3/ 1/J;61/> =6/:>7 9.89 >0 409 5011/7<04> 90 84@ >898 E64>0E 64 9./ :/A85@ 7@79/?. I4 7;5. 8 587/& 8776A464A 8 =6I/> B8:;/ 01 >/=6464A 9./ =6/:> 87 0<96048: =01 >898 91847=/1 ?8@ 3/ 8<<10<1689/. Het acquainted with the terminology o( the rele+ant data ob1ect. 8.g. 7/412 @reate customer master (see also the 01 hel&!
) ) $"ic" im!ort tec"ni>ue 8ill be used'

C./52 9./ 649/1=85/7 <10B6>/> 3@ 9./ 8<<:6589604. I7 9./1/ 8 3895. 64<;9 <10A18? 84> 84 ID05 C=01 /I8?<:/D? Y0; ?6A.9 .8B/ 8 :002 89 9./ <10A18? :63181@ 64 9./ D+)W0123/45. 89 9.67 <0649. W.65. ?/9.0> 7.0;:> 3/ ;7/> 64 @0;1 <10F/59? I4 587/ 0= B/1@ 7?8:: >898 J;849696/7& 69 ?8@ 3/ /876/1 90 5811@ 0;9 9./ 91847=/1 ?84;8::@. W69. B/1@ :81A/ >898 B0:;?/7& .0E/B/1& 3895. 64<;9 9/5.40:0A@ ?8@ :/8> 90 /I5/776B/:@ :04A 1;496?/7. R0;A. /796?89/ =01 9./ 1/J;61/> 96?/: 1'''' 1/501>7 </1 .0;1K 9.67 B8:;/& .0E/B/1& ?8@ B81@ 79104A:@ >/</4>64A 04 9./ .81>E81/. B895. 64<;9 7/77604 81/ L/87@M 64 <079<105/7764A .s a recording neededI /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 )d+antages o( recordings2
.ncludes screen sequences that may +ary (e.g. with di((erent material ty&es!
Smaller number o( target (ields )+ailable (or almost e+ery transaction
) - Create t"e recording

.( you use a recording2 "ecord the transaction and &rocess the recording.
S&eci(y
0ield names 0ield descri&tion /e(ault +alues
2-
) . Determine t"e source structures

D/9/1?64/ 9./ 70;15/ 791;59;1/7 84> =6/:>7 I7 9./ /I<019 >04/ 6490 ?;:96<:/ =6:/7 01 6490 04 7/J;/4968: =6:/? N09/: LSMW 01 D+)W0123/45. >0 409 >0 /I<0197 /e(ine the record structures o( the legacy data and introduce them to the S)* system. @ase 12 /ata is a+ailable in one or more (iles. @ase >2 /ata (still! resides in the legacy system and the legacy system &ro+ides a (unction (or e:&orting the data. @ase $2 /ata (still! resides in the legacy system and the legacy system does not &ro+ide a (unction (or e:&orting the data..
.ntroduce these structures to the S)* system.
.ntroduce this (these! record structure(s! to the S)* system.
/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 the S)* system.
) 1 Create test data in D2-$or%benc"

V68 N"090 )O A48:@H/ =6:/7 84> >898 791;59;1/7M @0; A/9 90 8 91847859604 E./1/ 84 /I8?<:/ 6?<019 =6:/ 584 3/ 51/89/> 90 9/79 9./ 6?<019. T.67 =6:/ 584 3/ =6::/> ?84;8::@ =01 9/79 <;1<07/7. F01 ?079 0= 9./ 3;764/77 03F/597 @0; .8B/ 9./ <077636:69@ 90 51/89/ 8 9/79 =6:/ 0;9 0= >898 8:1/8>@ <079/> 64 9./ SAP 7@79/?.
) 3 Ma!!ing on !a!er
D/B/:0< 8 ?8<<64A <:84 64 E1699/4 =01?: A776A4 9./ :/A85@ 7@79/? =6/:>7 90 9./ SAP =6/:>7. A <1649/> 03F/59 0B/1B6/E =10? LSMW ?6A.9 ./:< 89 9.67 <0649. D/9/1?64/ 9./ =01? C/.A. B68 PMOVE, 01 8776A4/> 85501>64A 90 8 1;:/D 64 E.65. 9./ :/A85@ 7@79/? >898 7.8:: 3/ 91847=/11/> 90 9./ SAP S@79/?. I= 8<<:6583:/& >/=64/ 9./ 8::0589604 1;:/7 CLSM)649/148: 48?/: P91847:89604 1;:/7,D.
) 4 ?nter t"e rules and test out of #SM$

E49/1 9./ 1;:/7 84> 9/79 79/<7 1/8>64A 84> 504B/1964A 0;9 0= LSMW (ead data O automatically by &ushing a button Con/ert 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 reusable rules&

Maintain the translation tables (03 hel& (or right%hand column!. 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.
) 1* Create !ro;ect+ sub!ro;ect and run in D2-$or%benc"

C1/89/ <10F/59& 7;3<10F/59 84> 1;4 64 9./ D+)W0123/45. ;4> >/=64/ 9./ 98727& =01 /I8?<:/: 1. 9872: ?8<<64A 84> 504B/1964A 2.
Legacy System Migration Workbench 2. 9872: 6?<019
F01 9872 ?8<<64A 84> 504B/1964A 9./ ?6A189604 03F/59 51/89/> 64 LSMW 584 3/ 58::/>K 9./ 6?<019 67 >04/ E69. 9./ 0;9<;9 =6:/ 0= LSMW CIII.:7?E.504BD
) 11 Im!ort t"e data

Start the run in /7 workbench /e&ending on the ob1ect ty&e2
-atch in&ut # recording2 Henerate batch in&ut session. "un batch in&ut session.
/irect in&ut Start direct in&ut session.
./ocs # -)*.2 Trans(er con+erted data to ./oc inbound &rocessing. @heck inbound &rocessing.
21
- 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 5b;ect Attributes

.n this ste&, ob1ect ty&e and im&ort technique are selected.
Maintain 6b1ect )ttributes
23
Legacy System Migration Workbench 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. Eere, 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.

.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.
Caution
.( 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$.$!.
Note2 @oncerning (lag Penable structure relation (or 8/./@34Q &lease ha+e a look at cha&ter 8rror2 "e(erence source not (ound
- 2 Maintain Source Structures

.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#subordinatedI
Caution
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.
24
Maintain So'rce Str'ct'res .n the abo+e e:am&le, one or se+eral (or no! item records @CST6M8"K@65T)@TS may e:ist (or each header record @CST6M8"KE8)/8". Eere, it is not determined yet whether these records are stored in one (ile or in two (iles.
3*
- 3 Maintain Source 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 Indi/idual Source 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
31
32
'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
33
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.A=, i.e. no triad se&arators, decimal &oint!. .( data (or se+eral structures is stored in one file the (ield Identifying field /alue has to be maintained. Please maintain only one identifying field /alue !er structure A 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 Source 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
3)
Legacy System Migration Workbench 0ield ty&e N@N 0ield length 14 0ield te:t R (ield name
- 3 3 Co!y Source 9ields from 5t"er Sources
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 BteCt se!arated by tabsD& .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;ect& Source (ields may be co&ied (rom the source structure o( another ob1ect. Co!y from data re!ository&
3-
Legacy System Migration Workbench Source (ields may be co&ied (rom a structure o( the S)* /ata /ictionary. 9rom data file Bfield names in 1st lineD 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 Structural (elations"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 S)* 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 .
3.
Maintain Str'ct'ral (elationships
.n the abo+e e:am&le, the (ields o( S)* structures -H"44, -S544, -S5)1, and -S5-1 are (illed by the (ields (rom @CST6M8"KE8)/8", the (ields o( S)* structure -S5VS are (illed by the (ields (rom @CST6M8"K@65T)@TS.
Note 12 Many -atch .n&ut and /irect .n&ut &rograms use a control record named -H"44 or -.444. 'ou should always assign the to& le+el source structure (Theader structureP! 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.
31
#SM$& Structure (elations

Target TKEeader TK*osition Source SKEeader1 SKEeader> SK*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 Con/ersion (ules

.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.
N(,*: S0?/ =6/:>7 81/ <1/7/9 3@ 9./ 7@79/?. T./7/ =6/:>7 81/ 58::/> P9/5.4658: =6/:>7, 81/ ?812/> E69. PD/=8;:9 7/9964A,. T./ 50>64A =01 9./7/ =6/:>7 67 409 >67<:8@/> E./4 =6179 /49/164A 9./ =6/:>?8<<64AK 69 584 3/ >67<:8@/> B68 9./ >67<:8@ B816849 C7// 5.5.1D. C.84A64A 9./ >/=8;:9 7/9964A ?8@ 7/160;7:@ 8==/59 9./ =:0E 0= 9./ >898 504B/17604. I= @0; /1104/0;7:@ 5.84A/> 9./ >/=8;:9 7/9964A& @0; 584 1/7901/ 69 3@ 5.00764A 67tras +estore default.
33
0ield Ma&&ing2 Tree o( Target 0ields (or the Target Structures Selected
The (ollowing (unctions are a+ailable2 9ield documentation & /is&lays a short documentation (or the target (ield the cursor is &ositioned on. The documentation may branch o(( to (urther in(ormation. Possible /alues & /is&lays a selection list o( all +alues &ossible (or this target (ield.
#ongteCt 6 Documentation
& Maintenance o( the documentation (or a (ield etc.
Assign a source 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.
!ote2 .( you choose Extras $'to"Fieldmapping, LSMW will gi+e suggestions (or assigning source (ields to target (ields. (emo/e t"e assignment of a source 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 con/ersion rules. The de(ault rule is Mo+e . Eowe+er, you can select +arious standard techniques +ia &ushbutton.
34
Conversion ('les- Select ('le
Assign rules&
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 -H"44, -.444! 0or batch in&ut recording2 N#N as nodata character 0or -)*.s, ./ocs2 @lear (ield (i.e.2 character (ield blankB numeric (ield N44...4N!
Mo/e2
The data is trans(erred using )-)* command Mo+e . 0or source (ields that are not o( ty&e N@N or N5N, this means2 Pac%ed field Date field Cn&ack to target (ield *o&u& to select ) ) ) Amount field internal (ormat user (ormat ... ''''MM// W".T8...T6... e.g. 41.14.1<<?
,atc" in!ut6direct in!ut& The amount +alue is edited according to the (ormat settings in the user master. ,APIs+ IDocs2 The amount +alue kee&s the internal calculation (ormat.
)*
Legacy System Migration Workbench Constant& The target (ield is assigned a (i:ed +alue. 9iCed /alue BreusableD2 ) (i:ed +alue ob1ect (+ariable! named 0VKU(i:ed+alueV 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 BreusableD2 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.=. <ser-8ritten routine BreusableD& The system creates the (rame o( a (orm routine ()-)* subroutine! with name &re(i: urK . 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!. PrefiC& S&eci(y any &re(i: to &recede the contents o( the source (ield. SuffiC& S&eci(y any su((i: (ollow the contents o( the source (ield. Concatenation2 'ou can concatenate two or more source (ields. Transfer left-;ustified& Trans(ers the contents o( the source (ield in le(t%1usti(ied (orm. A,AP coding& /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 S)* editor (unctions, such as Check (synta: check!, &retty &rinter, etc., are a+ailable there. Cnder !nsert you can add the (ollowing to your coding2 source fields2 all source (ields a+ailable are dis&layed (or selection global /ariable2 see A.7 global functions2 see A.A.$
29I?#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!B 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 U(ield in the data trans(er structureV is initial. U(ield in 7%structureV R L7L. else. U(ield in 7%structureV R L L. 8ndi(.
Note2 Via Extras "# fill 5"str'ct'res the coding (or whole structures can be added
- - 1 9or t"e Ad/anced <ser& Dis!lay 0ariant+ Processing Times

Define dis!lay /ariant& .n work ste& Maintain (ield ma&&ing and con+ersion rules , select NW 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. )1
Legacy System Migration Workbench 'ou can s&eci(y the in(ormation to be dis&layed.
Define Display 1arian t =lobal data definitions2 /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. Processing times2 Eere you can insert your own coding at s&eci(ic &rocessing times. The (ollowing &rocessing times are a+ailable2 Processing time __BEGIN_OF_PROCESSING__ Meaning -e(ore the beginning o( data &rocessing Default 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
.nitialiFe 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 )(ter (inishing transaction &rocessing )(ter (inishing data &rocessing )2
Tra s+er_re,-rd.
__END_OF_TRANSACTION__ __END_OF_PROCESSING__
Tra s+er_!ra sa,!$- . (blank!
9orm routines2 /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. Tec"nical fields2 /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 fields2 /is&lays initial (ields. Coding2 /is&lays the stored coding.
Note2 Cnder 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 Ad/anced <ser& =lobal 0ariables

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 /ariable 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 Descri!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 Cser ./ 5ame o( the batch in&ut session @urrent number o( the current batch in&ut session
- - 3 9or t"e Ad/anced <ser& =lobal 9unctions

The LSM Workbench &ro+ides a series o( (unctions that can be used in any &osition o( the )-)* coding.
)3
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 function !ra s+er_re,-rd.
Descri!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 Ad/anced <ser& (eusable (ules F Naming Con/entions

"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 S)* system. /ata ob1ect de(inition in the S)* 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 117,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 @E)"1 (about A,>44 data elements! or 708L/ (about 1$,A44 data ))
Legacy System Migration Workbench 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. ?Cam!le& No 1 > 9ield -CS"S @6K @6/8 Data element -CS"S @6K@6/8 Domain -CS"S -CS"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.
)-
- . Maintain 9iCed 0alues+ Translations and <ser-8ritten (outines

.n this ste& you can &rocess the reusable rules o( a &ro1ect2
&rocess (e'sable ('les 9iCed /alue2 Eere 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
).
Translation2 Eere 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.
)1
Legacy System Migration Workbench Control information2 Eere 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 /alues2 Eere 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 6S (lag was set are included.
Inter/al translation /alues& Eere 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 . )3
Im !ortant
/uring translation, only +alues (or which the 6S (lag was set are included.
- 1 S!ecify 9iles
.n this ste& you describe all (iles to be used in the (ollowing ste&s2 'our legacy data on the *@ and#or S)* ser+er The (ile (or the read data The (ile (or the con+erted data
)4
-*
-1
Specify Files If your legacy data is on t"e PC& 1. .n change mode, &osition the cursor on the line Legacy data X 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.
-2
File on Frontend 6&C7- &roperties If your legacy data is on t"e SAP ser/er2 1. .n change mode, &osition the cursor on the line Legacy data on S)* 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. Cnder @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 S)* system uses user ./ UsidVadm with regard to the o&erating system. There(ore, make sure that you ha+e read#write authoriFation (or the selected directory .
-3
File on S$& 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 @CST6M8"K5CM-8"2 -)
/is&lay Merge 0ields
9ile of read data& Eere, 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 con/erted 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.
--
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 (NWN! to the name o( your (ile. The &ossible +alues (or NWN can be s&eci(ied under Values (or wildcard .
- 3 <se $ildcards 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 (W1.t:t and W>.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
-.
Specify Files- ,sing Wildcards
Note& 'ou can also use a wildcard in the names o( the (iles o( read data and con+erted data.
-1
- 4 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* (ead Data
Proceeding& .( 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 Heneral 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.
-3
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 (ead 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. C!an)e display 8::0E7 90 7/:/59 /69./1 8 04/):64/ 01 ?;:96):64/ B6/E. Display color palette dis&lays the colors (or the indi+idual hierarchy le+els.
- 11 Con/ert Data
- 11 1 =eneral (emar%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... . Eere, 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.
-4
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.
- 11 2 Additional 9unction for ,API6IDoc

.( 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 siFe can be determined using &arameter 5umber o( ./ocs &er &ackage . The de(ault +alue is A4.
.*
- 12 Dis!lay Con/erted 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

Henerate 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
- 11 1 Im!ort Data 8it" ,atc" In!ut

- 13 1 1 =enerate ,atc" In!ut 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 (un ,atc" In!ut Session The &rogram goes to S)* standard transaction SM$A. Eowe+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" Direct In!ut

- 13 2 1 Start Direct In!ut 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.
.1
- 13 3 Im!ort Data 8it" ,API or IDoc Tec"ni>ue

/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 S)* 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 creation1 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/. customiFing. 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.
!ote 212 *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.!
!ote 2$2 /uring the &rocessing o( inbound ./ocs, so%called work items are created in the standard &rogram. This are elements o( the S)* 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<$=?.
!ote 2&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 8ackgro'nd processing !mport $LE4!Doc &erformance0
'ou can do the (ollowing in addition to these two &rocessing ste&s2 -reate I/oc o"er"iew2 This dis&lays a Tstatus o+er+iew which allows to dis&lay indi+idual ./ocs with the drill%down technique.
.2
. (ecordings
*er(orm a transaction Ttrial runPB This is no simulation modeJ 'our in&ut is &osted in the systemJ *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 Descri!tion of t"e Process

.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.
.3
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( the S)* system. 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. Eere 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.
.)
&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
Gou may use field names re!eatedly 7o8e/er+ in field ma!!ing a field name can only be used once 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.
.-
1 Trans!ort #SM$ Pro;ects

The LSM Workbench &ro+ides data trans&ort (or a &ro1ect +ia both the S)* 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 S)* system and e+ery client.!
1 1 =enerate C"ange (e>uest

@hoosing this (unction creates an S)* change request containing all in(ormation about an LSMW &ro1ect. This S)* change request can be e:&orted # im&orted with the usual means o( S)* correction and trans&orting. 'ou can (ind this (unction in the initial screen under Extras "# Create change re9'est. When trans&orting LSMW data this way, you can trace the trans&orts any time in S)* 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.!
1 2 ?C!ort Pro;ect
.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.
..
.1
Export &ro%ect- *ro1ect Table o( @ontents
Note2 The selected elements are e:&orted together with their documentation.
1 3 Im!ort Pro;ect
The e:&orted ma&&ing and rules can be im&orted into another S)* 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 analyFed. )(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.
.3
3 Periodic 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 S)* 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.
.4
Frame &rogram for &eriodic Data *ransfer- Selection Screen
1*
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
RAALTD01 RAALTD11 RCCLBI01 RCCLBI02 RCCLBI03 RCCTBI01 RCSBI010 RCSBI020 RCSBI030 RCSBI040 RCVBI010 RFBIBL00 RHALTD0 0 RLBEST00 RLPLAT00 RMDATIN D RPUSTD0 0
*arameter used @reate batch in&ut session -., /., @all Transaction, Test Lock mode )ction Cser grou&
7 7 7 7 7 7 7 7
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. 11
4 #ong TeCts
T0 91847=/1 :04A 9/I97& 9./1/ 81/ 9E0 <077636:696/7: D61/59 64<;9 <10A18? (SAPDMC(SAPQLSMWQIMPORTQTE+TS C03F/59 '''1& ?/9.0> '''1DK 9.67 03F/59 67 409 8B86:83:/ 64 9./ 7984>81> <10A18?. T0 ?82/ 69 8B86:83:/& 1;4 9./ =0::0E64A <10A18? : /SAPDMC/SAP_LSMW_SXDA_TEXTS D61/59 64<;9 <10A18? RST+LITF C03F/59 2'''& ?/9.0> ''''DK 90 3/ 83:/ 90 ;7/ 9.67 03F/59& @0; .8B/ 90 >0E4:08> 9./ 91847<019 =10? SAPNET C.99<:((7/1B65/.78<.50?(LSMWD 84> 6?<019 69 6490 @0;1 7@79/?
4 1 #ong TeCts in t"e SAP System

L04A 9/I97 C9/I97 50B/164A ?01/ 9.84 04/ :64/D 81/ 7901/> 64 8 9/I9 <00: 64 9./ SAP 7@79/?. T./ 2/@ 0= 8 :04A 9/I9 67 50?<07/> 0= =0;1 <8197: K*6 74*2. OB6ECT ID M*-)4)8 A<<:6589604 03F/59 T/I9 ID E9-5+2* AUFK R O1>/1 9/I97 6b1ect A/F8 NA.E SPRAS A59;8: 9/I9 2/@ L84A;8A/ .d 8OPF R 6rder header te:t .d POSN R 6rder item te:t .d R.EL R 6rder con(irmation te:t ' 1)2 C404/D T992 4 C0*': ,-32* TT7OB& TT7OT TT7ID& TT7IT
L*)8,0 1'
6rder number T/I9 :84A;8A/
12
4 2 Determine TeCt Hey Structure

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
T./ =0::0E64A 8<<:6/7 64 9./ 830B/ /I8?<:/ 0= 8 ?89/168: 78:/7 9/I9: 6-D8@T R MVS8 ./ R 4441 5)M8

Material number (1? characters! ; Sales organiFation (3 characters! ; /istribution channel (> characters!
13
4 3 De/elo! 5b;ects for #ong TeCts /ia 5b;ect ***1

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

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

T87T06"M)T 0ormat (ield (> characters!
F6/:> TE+TFORMAT 50498647 9/I9 =01?89964A 64=01?89604. T0 76?<:@ ?8< 9./ =6/:> 1:1& /49/1 5.81859/1 STS. F01 9./ ?89/168: 78:/7 9/I9 64 9./ /I8?<:/& 8 ?6A189604 03F/59 50;:> :002 87 =0::0E7:
Long *exts- Source 0ields
1)
Long *ext- Structural "elationshi&s
1-
Long *ext- 0ield Ma&&ing
Note2 Statement onKchangeKtrans(erKrecord. 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.$!.
1.
4 ) De/elo! 5b;ects for #ong TeCts /ia 5b;ect 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@#LSMWKT87TET87T #S)*/M@#LSMWKT87T6-D8ST #S)*/M@#LSMWKT87T5)M8 #S)*/M@#LSMWKT87T./ #S)*/M@#LSMWKT87TL)5HC)H8 #S)*/M@#LSMWKT87T06"M #S)*/M@#LSMWKT87TST'L8 #S)*/M@#LSMWKT87T0."STCS8" #S)*/M@#LSMWKT87T0."ST/)T8 #S)*/M@#LSMWKT87T0."STT.M8 #S)*/M@#LSMWKT87TL)STCS8" #S)*/M@#LSMWKT87TL)ST/)T8 #S)*/M@#LSMWKT87TL)STT.M8 #S)*/M@#LSMWKT87TT.TL8 #S)*/M@#LSMWKT87TT.TL81 #S)*/M@#LSMWKT87TT.TL8> #S)*/M@#LSMWKT87TM).5 #S)*/M@#LSMWKT87TL.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
11
Structural "elationshi&s
13
14
3*
4 - Im!ort TeCts
T/I97 81/ 6?<019/> 6490 9./ SAP 7@79/? 3@ ?/847 0= >61/59 64<;9. T./ 1/:/B849 >61/59 64<;9 <10A18? 584 3/ /876:@ 58::/> =10? 9./ LSM W0123/45. B68 Start %irect Input Session.
Im !ortant
A=9/1 9./ 6?<019 0= :04A 9/I97& 70?/96?/7 9./7/ 584409 3/ 1/8> E69.64 9./ 5011/7<04>64A 8<<:6589604. V68 =;459604 ?0>;:/ SREADQTE+TS& 9./ 9/I97 81/ =0;4>& 9.;7& 9./@ 81/ 7901/> 5011/59:@ 64 9./ >898387/. S0?/ 8<<:65896047 .8B/ 8 =6/:> 64 9./ ?879/1 >898 E.65. 7.0E7 E./9./1 8 :04A 9/I9 /I6797 01 409. T.67 =6/:> 67 409 =6::/> 3@ 9./ >61/59 64<;9 <10A18?7 C7645/ 9./7/ <10A18?7 8<<:@ 90 8:: 8<<:65896047& 84> 89 1;496?/ 69 67 409 240E4 E.65. 8<<:6589604 8 9/I9 3/:04A7 90. T./1/ 81/ 2 <07763:/ 70:;96047: 1. T./ =:8A 67 7;<<:6/> 3@ 8 ;7/1)>/=64/> 1/<019 8=9/1 9./ 6?<019 2. I4 9./ =6/:> 8776A4?/497 ( ?8<<64A 84 ;<>89/ 67 50>/> 04 9./ 1/7</596B/ 983:/K .0E/B/1& 9.67 9.89 9./ =:8A 67 7/9 8:1/8>@ >;164A 9./ 504B/17604 6= 9./ 9/I9 67 409 6?<019/> :89/1& 9./ =:8A 67 7/9& .0E/B/1& 40 :04A 9/I9 67 8B86:83:/.
31
1* Ti!s and Tric%s

1* 1 Determine t"e Transaction Code at (untime
Situation2 '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. ?Cam!le2 @ustomer master Solution2 .nsert under Hlobal /ata 2 TABLES3 8NA1. A>> 9./ =0::0E64A 50>64A =01 =6/:> BKN'')TCODE: 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 (ecord
Situation2 '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 Solution2 $+ <,- d$!$- ". s2$'_re,-rd. e d$+.
1* 3 S%i! All (ecords of a Transaction

Situation2 'ou want to ski& all records o( a transaction de&ending on a certain condition. Solution2 $+ <,- d$!$- ". s2$'_!ra sa,!$- . e d$+.
1* ) Du!licate a (ecord
Situation2 'ou want to create two (or more! target records (rom a source record. ?Cam!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 the S)* system, a -S5VS record has to be (illed (or each contact &erson. Solution2 '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... 32
C1/89/ 9./ =0::0E64A 1;:/7: ... 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 -S5VS records.
1* - ?Ctra 7andling for IP5S-ID5CsJ

$"at is a IP5S-ID5CJ' O These are ./ocs where the control record (8/.K/@34! has to be (illed with source data (e:am&le message ty&e W*CW-W, where the store number is trans(erred +ia the control record!. This means control record 8/.K/@34 needs to be a+ailable as target structure in ste& Pmaintain structure relationsQB in the (ieldma&&ing rules and &rocessing &oints ha+e to be identical to the other target structures
7o8 does t"e !rocessing loo% li%e for IP5S-ID5CsJ' Ste! Imaintain ob;ect attributesJ *lease set (lag P8nable structure relation (or 8/./@34Q
33
Ste! Imaintain structure relationsJ *lease assign a source structure to target structure 8/.K/@342
Ste! Imaintain fieldma!!ing and con/ersion rulesJ 8/.K/@34 is a+ailable as target structure inclusi+e &rocessing &oints
In all ot"er ste!s t"ere are no c"anges
3)
11 <!grade from #SM$ 1 * to #SM$ 1 1

11 1 Differences ,et8een 0ersion 1 * and 0ersion 1 1 of t"e #SM $or%benc"
The (ollowing lists the main di((erences between +ersion 1.4 and 1.7 o( the LSM Workbench2 Transaction code2 The transaction code is LSMW (in +ersion 1.42 /LSM !. Version 1.4 is still a+ailable a(ter installing +ersion 1.7. 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 con/ention2 The names (or &ro1ect, sub&ro1ect and ob1ect can be assigned (reely without any restrictions. C"anged descri!tion2 5ew2 "ecording instead o( Cser%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 R letter!. 8+ery recording is assigned to e:actly one &ro1ect. C"anged descri!tion2 5ew2 "eusable rules instead o( @entral rules . 5b;ect attributes2 .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 tec"ni>ues2 .n addition to standard batch in&ut#standard direct in&ut and recording, -)*. and ./ocs are a+ailable as additional im&ort techniques. Source structures2 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. Source fields2 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 C&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!. Structural relations2 The &rogram dis&lays the in(ormation whether a structure is a required segment. 9ield ma!!ing and rules2

Dis!lay /ariant2 'ou can select the elements to be dis&layed2 Hlobal data, &rocessing times, technical (ields, initial (ields, coding. Processing 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 documentation+ 9) "el!2 Symbols &er target (ield Source fields not assigned2 Men' Extras So'rce fields not assigned dis&lays the source (ields that are not assigned. Additional con/ersion tec"ni>ues /ia !us"button& *re(i:, su((i:, trans(er le(t%1usti(ied, user% written routine =lobal functions& .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,!$- . ?ditor& @heck the coding (or a target (ieldB insert source (ields, global +ariables, global (unctionsB *retty *rinter. 3-
Legacy System Migration Workbench Com!arison 8it" Data (e!ository2 5o longer required. $7?(? relations"i!s2 5o longer required. 9iles2 )ll de(initions in connection with (iles are merged in the two &rocessing ste&s Specify files and $ssign files. Eere YWL 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. Action log2 )ll actions (or an ob1ect are stored in an action log. Do8nload6u!load rules2 @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!lay6c"ange2 .n many (unctions you can switch between Display and Change. Documentation2 '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. (ecordings2 Version 1.7 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.
3.
12 Transfer of #SM$ Data from 0ersion 1 * to 0ersion 1 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.7, 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.7. 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 account& Version 1.7 no longer has a generation lock. Cser%written )-)* coding should be checked +ia synta: check. Cser%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 structuresB in +ersion 1.7 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.
31
13 <!grade from #SM$ 1 - to #SM$ 1 1

13 1 Notes on t"e <!grade to #SM$ 1 1
)ll ob1ects created under LSMW 1.A are ke&t in LSMW 1.7. Trans(erring data (rom LSMW 1.4 to LSMW 1.7 is still &ossible. Trans&orting rules (rom LSMW 1.A to LSMW 1.7 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)*KLSMWK"8*)."K1A once, and check the settings ( S&eci(y (iles !. &rogram
@heck the (ieldma&&ing (or 8V8"' 6-D8@T. .( you ha+e created coding (or the &rocessing &oints KK-8H.5K60K"8@6"/KK, 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 Corrections
Ste! numbering and 8elcome !o!u!2 5umbering 6n#6(( %%V Welcome &o&u& is dis&layed again2 8rror corrected. Interfaces of function modules com!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 c"ange re>uest2 5o authoriFation check2 was added. 5b;ect attributes2 When &ressing 03 (or standard -.#/. ob1ects, ob1ects with numbers U ?444 are dis&layed only2 8rror corrected. 9ield ma!!ing2 /escri&tions and documentation (or target (ields o( ./oc segments were &artly not (ound2 8rror corrected. <ser-8ritten routines2 /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 con/ersion !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 con/ersion !rogram 2 Cnder certain conditions, the rules were con(used2 8rror corrected. Co!y an ob;ect2 03 % Eel& (or sub&ro1ect, ob1ect, source structure did not work2 8rror corrected. When the ob1ect contained wildcards, the co&y &rocess abended2 8rror corrected. !lease see note 1.3.)) for furt"er c"anges
13 3 De/elo!ments
Dis!lay K-L c"ange2 .n the ste&s screen you can s&eci(y whether the &rogram switches to dis&lay or change mode when you double%click. Source fields2 0ield de(inition is now &ossible with table control as well.
33
Legacy System Migration Workbench 9ield ma!!ing+ dis!lay attributes2 .tem KK06"MK"6CT.58SKK is dis&layed se&arately (or selection. Technical (ields are marked with rulety&e T/e(ault settingP. The de(ault setting can be restored +ia Extras (estore defa'lt. The &rocessing &oint KK-8H.5K60K"8@6"/KK is &reset. =lobal functions2 )dditional global (unction trans(erKthisKrecord N77777N, to trans(er the s&eci(ied segment. S!ecify file2 StandardiFation2 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
Default file names for read and con/erted data 2 -lanks within a word are re&laced by underscores. (ead data2 Csage o( sorted internal tables yielding a massi+e &er(ormance gain when merging se+eral (iles. IDoc inbound !rocessing2 '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@K.5-6C5/K)S'5@E"656CS. (This (unction module creates ./ocs in the database.! @ontrol &rogram (or &eriodic data trans(er2 5ow also works together with wildcards (W! in (ile names. Some im&ortant &arameters o( -.#/. &rograms are (orwarded to the outside.
34
1) 9inal (emar%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
4*

LSMW Complete Guide

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

LSMW Complete Guide

Uploaded by

Copyright:

Available Formats

Data Migration of Non-SAP Systems to SAP-Systems

lsm@sa .com !o"ember 1# $%1&

Legacy System Migration Workbench

Legacy System Migration Workbench

1 2 #SM $or%benc"& $"at is it'

1 . #SM $or%benc" 0ersions

1 3 Significance of Data Migration

1 4 ,asic Princi!les of t"e #SM $or%benc"

Accelerating Data Migration& #SM $or%benc" 7o8 #SM $or%benc" 8or%s

,atc" In!ut !rocessing Direct In!ut !rocessing IDoc inbound !rocessing

S)* )H Duly 1<<<

Schematic Flow of Data Migration with the LSM Workbench

Legacy System Migration Workbench

Legacy System Migration Workbench

3 Startu! and Pre!arations

Legacy System Migration Workbench

3 3 Pro;ect+ Sub!ro;ect and 5b;ect

Legacy System Migration Workbench

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

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 5b;ect 5/er/ie8

Legacy System Migration Workbench

+b%ect +verview- Heneral /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 4 Pre!arations for <sing IDoc Inbound Processing

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!

Legacy System Migration Workbench

Legacy System Migration Workbench 1erifying Workflow C'stomi2ing

Legacy System Migration Workbench

LSMW -). DXWB /0(12. 3* 1/*. 4) '(534)-,4()

Legacy System Migration Workbench

) 2 $"ic" data s"ould be migrated'

) 3 (un t"e manual !rocess

) ) $"ic" im!ort tec"ni>ue 8ill be used'

)d+antages o( standard migration ob1ects2 )d+antages o( recordings2

Smaller number o( target (ields )+ailable (or almost e+ery transaction

) - Create t"e recording

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

Legacy System Migration Workbench

) . Determine t"e source structures

.ntroduce these structures to the S)* system.

.ntroduce this (these! record structure(s! to the S)* system.

) 1 Create test data in D2-$or%benc"

) 4 ?nter t"e rules and test out of #SM$