LSMW操作.docx
《LSMW操作.docx》由会员分享,可在线阅读,更多相关《LSMW操作.docx(55页珍藏版)》请在冰豆网上搜索。
LSMW操作
DataMigrationof
Non-SAPSystemstoSAP-Systems
QuickIntroductiontoWorkingwiththe
LegacySystemMigrationWorkbench
Version1.8.0
January28,2003
TableofContents
1Introduction4
1.1PurposeofthisIntroduction4
1.2LSMWorkbench:
Whatisit?
4
1.3SupportedReleases4
1.4Costs4
1.5Delivery4
1.6LSMWorkbenchVersions4
1.7Support5
1.8SignificanceofDataMigration5
1.9BasicPrinciplesoftheLSMWorkbench5
2Preconditions7
3StartupandPreparations8
3.1Authorizations8
3.2InitialTransaction8
3.3Project,SubprojectandObject9
3.4UserGuidance10
3.5FieldMappingonPaper12
3.6CreateObjectOverview13
3.7Administration16
3.8Recordings16
3.9PreparationsforUsingIDocInboundProcessing17
4GeneralTipsfortheProcedureinamigrationusingLSMWandDX-Workbench21
4.1SAP-Customizing22
4.2Whichdatashouldbemigrated?
22
4.3Runthemanualprocess22
4.4Whichimporttechniquewillbeused?
22
4.5Createtherecording22
4.6Fillobjectattributes23
4.7Determinethesourcestructures23
4.8CreatetestdatainDX-Workbench23
4.9Mappingonpaper23
4.10Maintainstructurerelations23
4.11Dataexport23
4.12EntertherulesandtestoutofLSMW24
4.13Createproject,subprojectandruninDX-Workbench24
4.14Importthedata24
5DataMigration–StepbyStep25
5.1MaintainObjectAttributes25
5.2MaintainSourceStructures26
5.3MaintainSourceFields28
5.3.1CreateIndividualSourceFields28
5.3.2MaintainSourceFieldsinTableForm30
5.3.3CopySourceFieldsfromOtherSources31
5.4MaintainStructuralRelationships32
5.5MaintainFieldMappingandConversionRules34
5.5.1FortheAdvancedUser:
DisplayVariant,ProcessingTimes37
5.5.2FortheAdvancedUser:
GlobalVariables39
5.5.3FortheAdvancedUser:
GlobalFunctions40
5.5.4FortheAdvancedUser:
ReusableRules—NamingConventions41
5.6MaintainFixedValues,TranslationsandUser-writtenRoutines42
5.7SpecifyFiles45
5.8UseWildcardsinFileNames50
5.9AssignFiles52
5.10ReadData52
5.10.1DisplayReadData53
5.11ConvertData53
5.11.1GeneralRemarks53
5.11.2AdditionalFunctionforBAPI/IDoc54
5.12DisplayConvertedData55
5.13ImportData55
5.13.2ImportDatawithDirectInput55
5.13.3ImportDatawithBAPIorIDocTechnique56
6Recordings57
6.1DetailedDescriptionoftheProcess57
7TransportLSMWProjects60
7.1GenerateChangeRequest60
7.2ExportProject60
7.3ImportProject61
8PeriodicDataTransfer62
9LongTexts65
9.1LongTextsintheSAPSystem65
9.2DetermineTextKeyStructure66
9.3DevelopObjectsforLongTextsviaObject000167
9.4DevelopObjectsforLongTextsviaObject200070
9.5ImportTexts74
10TipsandTricks75
10.1DeterminetheTransactionCodeatRuntime75
10.2SkipaRecord75
10.3SkipAllRecordsofaTransaction75
10.4DuplicateaRecord75
10.5Errormessagesintheconversionlog76
10.6ExtraHandlingfor“POS-IDOCs”76
11UpgradefromLSMW1.0toLSMW1.878
11.1DifferencesBetweenVersion1.0andVersion1.8oftheLSM Workbench78
12TransferofLSMWDatafromVersion1.0toVersion1.880
13UpgradefromLSMW1.5toLSMW1.881
13.1NotesontheUpgradetoLSMW1.881
13.2Corrections81
13.3Developments81
14FinalRemarks83
1Introduction
1.1PurposeofthisIntroduction
ThisintroductionisintendedtoallowaquickentryintotheworkwiththeLegacySystemMigrationWorkbenchVersion1.8("LSMWorkbench").
1.2LSMWorkbench:
Whatisit?
TheLSMWorkbenchisanSAP-basedtoolthatsupportsYouwhentransferringdatafromnon-SAPsystems("LegacySystems")toSAPsystemsonceorperiodically.
Thetoolsupportsconversionofdataofthelegacysysteminaconvenientway.ThedatacanthenbeimportedintotheSAPsystemviabatchinput,directinput,BAPIsorIDocs.
Furthermore,theLSMWorkbenchprovidesarecordingfunctionthatallowstogeneratea"datamigrationobject"inanentryorchangetransaction.
1.3SupportedReleases
LSMWVersion1.8canbeimplementedforsystemsthatusethefollowingreleases:
4.6A,4.6B,4.6Cand4.6D.LSMWVersion1.72isavailableforreleasesfrom4.0upto(butnotincluding)4.6.
LSMWVersion1.0canbeimplementedforreleasesolderthan4.0.
1.4Costs
SAPmakesthistoolavailabletotheircustomersandpartnersfreeofcharge.
1.5Delivery
TheLSMWorkbenchisnotpartofthestandardSAPsystem.Ifyouareinterestedinthisproduct,pleasecontactSAPvia:
∙SAPNet(OnlineServiceSystem):
componentBC-SRV-DX-LSMor
∙SAPNet:
Thereyoufindallavailableinformationanddocumentationandthesoftwareitself(transportfile).Amongothers,thefollowingaccompanyingmaterialisavailable:
∙ChecklistfortheusageoftheLSMWorkbench
∙PresentationoftheLSMWorkbench(PowerPointpresentation)
1.6LSMWorkbenchVersions
Version1.0oftheLSMWorkbenchwasmadeavailabletoabout350interestedcustomersandpartnersintheframeoftheFirstCustomerShipmentbetweenMarch1998(CeBIT)andmiddleofAugust1998.Theresultingexperiencesandfeedbackweretakenintoaccountinthefurtherdevelopment.
LSMWVersion1.0wasmadegloballyavailableinAugust1998andsincethenhasbeenrequestedmorethan1000times.LSMWVersions1.5and1.6werepublishedin1999.
LSMWversion1.7hasbeenavailablesinceSeptember2000andwasreplacedbyLSMWVersion1.8inFebruary2003.(SAPR/3BasisRelease4.6ismandatoryforVersion1.8.)
Forallpersonsalreadyfamiliarwithversion1.0oftheLSMWorkbench,section11providesacompactoverviewofthemodificationsinversion1.7comparedwithversion1.0.
1.7Support
ForproblemmessagesviaSAPNet(OnlineServiceSystem),entry"BC-SRV-DX-LSM"isavailableinthecomponenthierarchy.Whenyouenteramessage,pleasespecifythenumberoftheLSMWorkbenchversionyouareusing.(Todisplaytheversionnumber,selectExtrasDisplayLSMWversionintheinitialscreenoftransactionLSMW.)
Note:
IfproblemsoccurafterstepConvertdata,pleasedirectlycontactthespecialdepartmentresponsibleforthemodule(FI,CO,MM,SD,HR,etc.).AllstepsfollowingthedataconversionarenotLSMWorkbenchfunctions.ThereforetheLSMWteamcannotprovidesupportforthesefunctions.
1.8SignificanceofDataMigration
DatamigrationcomesintheendofSAPimplementation.Atthistime,theSAPsystemisnormallyinstalledandapplicationcustomizingisfinished(inthebestcase).
AnexaminationofSAPimplementationprojectsbySAPConsultinghasshownthatdatamigrationisabout20%ofthetotalimplementationexpenses.Thisportionmayriseupto40%insmallerimplementationprojects.
Asignificantreductionoftheexpensesfordatamigrationresultsinacorrespondingsignificantreductionofthetotalprojectbudgetandtheprojectruntime.
TheexperienceswiththeLSMWorkbenchinSAPimplementationprojectsareverypromising:
Boththeexpensesandthecostsofdatamigrationcouldbereducedsignificantly.
1.9BasicPrinciplesoftheLSMWorkbench
TheLSM WorkbenchwasdevelopedonthebasisoftheR/2-R/3 Migration Workbenchthathasbeenusedmanyhundredtimesinthepastandisstillusedpresently.
ThefollowingconceptsandtechniquesfromtheR/2-R/3 Migration Workbenchwereadopted:
∙Businessobjectsinsteadofindividualtablesorfieldcontentsaremigrated.
∙Theconversionrulestobedefinedareflexibleandcanbecustomizedintheframeofmigrationcustomizingtomeettheactualsituationintheprojectintheusersystem.
∙Preprogrammedconversionprogramsarenotdelivered.Theseprogramsarerathergeneratedonthebasisofthedefinedrules.
TheLSMWorkbenchwasdevelopedonthebasisofthefollowingprinciples:
∙MostofthefunctionsshouldresideintheSAPsystem.Nocollectionofindividualprogramsondifferentplatforms.
∙ThequalityandconsistenceofthedataimportedintotheSAPsystemshouldbemoreimportantthanspeedandperformanceofdatamigration.
∙Existingknowledgeandcodingshouldbeused.
∙Thedeveloped"mapping"andrulesshouldbereusableandthusbeusedrepeatedlyinprojects.
Onthisbasis,aconceptwasdevelopedthatisrepresentedinthefollowingchart:
SchematicFlowofDataMigrationwiththeLSMWorkbench
ThemainadvantagesoftheLSM Workbench:
∙PartoftheSAPsystemandthusindependentofindividualplatforms
∙Avarietyoftechnicalpossibilitiesofdataconversion:
∙Dataconsistencyduetostandardimporttechniques:
−Batchinput
−Directinput
−BAPIs(BusinessApplicationProgrammingInterfaces)
−IDocs(IntermediateDocuments)
Theimporttechniquetobeusedinanindividualcasedependsonthebusinessobject.
∙Generationoftheconversionprogramonthebasisofdefinedrules
∙Clearinteractiveprocessguide
∙Interfacefordataonfrontendandonapplicationserver
∙Creationofdatamigrationobjectsonthebasisofrecordedtransactions
∙Charge-freeforSAPcustomersandSAPpartners
2Preconditions
TheLSMWorkbenchisatoolthatsupportsdatatransferfromnon-SAPsystemstoSAPsystems.ThemainfunctionsoftheLSMWorkbenchare:
1.Importdata(legacydatainspreadsheettablesand/orsequentialfiles)
2.Convertdata(fromsourceformattotargetformat)
3.Importdata(intothedatabaseoftheSAPapplication)
BeforeyoucanapplytheLSMWorkbench,youabsolutelyneedadatamigrationconcept.Thefollowingitemsshouldbeconsideredinparticular:
∙MakesurethatSAPcustomizingisfinished.
∙Determinethedatacontainedinyourlegacysystemandwhichofthedatawillberequiredinthefuture(withrespecttobusinessoperation).
∙Decidewhetheritmakessensetousethistoolwithrespecttothe