mass transaction

6
Data Migration with LSMW Skip to end of metadata    Added by Guest, last edited by Jyoti Prakash on Nov 21, 2012 (view change)   show comment Go to start of metadata SAP Data Migration with LSMW Purpose This wiki page will guide you, how data migration can be done by using LSMW. Introduction Legacy System Migration Workbench ( LSMW) is a tool recommended by SAP that you can use to transfer data once only or periodically from legacy systems into an R/3 System. This is one of the very powerful tools available in SAP to upload large amount of data to the system. This tools is comparable to ecatt or scatt. But the advantage LSMW has over them is the amount of data processed in single session. Moreover LSMW is easer to learn and execute. Through LSMW one can create Master data, create transactional data, modify existing master data etc. This tool is very useful when some mass changes are to be carried out and no standard SAP transactions are available for that. There are few standard objects available in LSMW e.g. material master, vendor master, customer master, purchasing info record, purchase requisitions, purchase orders etc. Using these standard objects one can do mass data upload and mass transactions. Apart from this LSMW provides another functionality of recording the transaction and then carrying that out many times with large data. eg for that can be mass deletion of purchase requisitions, mass deletion of planned orders etc. For creating simple projects user can go to tcode LSMW and get started. All the steps are listed very nicely and system will not allow user to skip the steps enlisted. User will need to create Project, Subproject and Object. Input tools Input to LSMW can be with  simple excel sheet  text tab delimited file(text file e.g. notepad). Example  A LSMW project in step wise manner is presented below: Simply enter the field names in the first line of the table, and the LSM Workbench's import routine automatically generates the input file for your conversion program. The LSM Workbench lets you check the data for migration against the current settings of your customizing. The check is performed after the data migration, but before the update in your database. LSMW data migration for sales order VA01 / XD01 customer  LSMW using session method for data migration as follows

Upload: uday1969

Post on 16-Oct-2015

64 views

Category:

Documents


0 download

DESCRIPTION

MASS Transaction

TRANSCRIPT

Data Migration with LSMWSkip to end of metadata Added by Guest, last edited byJyoti Prakashon Nov 21, 2012(view change) show commentGo to start of metadataSAP Data Migration with LSMWPurposeThis wiki page will guide you, how data migration can be done by using LSMW.IntroductionLegacy System Migration Workbench (LSMW) is a tool recommended by SAP that you can use to transfer data once only or periodically from legacy systems into an R/3 System.This is one of the very powerful tools available in SAP to upload large amount of data to the system. This tools is comparable to ecatt or scatt. But the advantage LSMW has over them is the amount of data processed in single session. Moreover LSMW is easer to learn and execute.Through LSMW one can create Master data, create transactional data, modify existing master data etc. This tool is very useful when some mass changes are to be carried out and no standard SAP transactions are available for that. There are few standard objects available in LSMW e.g. material master, vendor master, customer master, purchasing info record, purchase requisitions, purchase orders etc. Using these standard objects one can do mass data upload and mass transactions. Apart from this LSMW provides another functionality of recording the transaction and then carrying that out many times with large data. eg for that can be mass deletion of purchase requisitions, mass deletion of planned orders etc.For creating simple projects user can go to tcode LSMW and get started. All the steps are listed very nicely and system will not allow user to skip the steps enlisted. User will need to create Project, Subproject and Object.Input toolsInput to LSMW can be with simple excel sheet text tab delimited file(text file e.g. notepad).ExampleA LSMW project in step wise manner is presented below:Simply enter the field names in the first line of the table, and the LSM Workbench's import routine automatically generates the input file for your conversion program.The LSM Workbench lets you check the data for migration against the current settings of your customizing. The check is performed after the data migration, but before the update in your database.LSMW data migration for sales order VA01 / XD01 customerLSMW using session method for data migration as followsE.g. forXD01(createcustomer)initially there will be 20 steps but after processing 1 step it will reduced to 14 for session method.TCodeLSMWEnter Project Name Sub project name Object name Execute the transaction

1.Maintain object Attributes Execute Select Batch Input recording Go to - recording overview Create Recording name Enter transaction code Start recording Do recording as per your Requirement Save & click on back button or press F3 button from your keybroad. Enter recording name in LSMW screen Save & click on back button or press F3 button from your keybroad

Now there will be 14 steps.

2.Maintain Source Structures Enter the name of internal table. Display change Create Save & click on back button or press F3 button from your keybroad

3.Maintain Source Fields Display change Select structure Source_fields & Copy fields. (a dialogue window will pop out ) Select a From data file Apply source fields a. Enter No. of field's b. Length of fields c. Attach the file Save & click on back button or press F3 button from your keybroadadditional info.

If the number of fields are more, it is preferable to use the same field name as SAP Table field name. The benefit of this can be seen on Step 5.

4.Maintain Structure Relations Display change Save & click on back button or press F3 button from your keybroad

5.Maintain Field Mapping & Conversion Rule Display change Click on source field, select exact field from structure and Enter Repeat these steps for all fields. Save & click on back button or press F3 button from your keybroadadditional info.

If in Step 3, the field names are same as the SAP Table field names, then the field mapping can be simplified byExtras --> Auto Field Mapping.In the pop-up window, selectNo Confirmation.

6.Maintain Fixed Values, Transaction, User Defined Execute Save & Press click on button

7.Specify Files Display change Click on legacy data Attach flat file Give description Select tabulators Enter Save & Press click on buttonadditional info.An advantage of using LSMW over other methods of data upload is that if you have the column names in the first row of the input file, then the columns need not be in the same order as the file definition (Step 3). LSMW will move the value to the appropriate field by comparing the field name and the column name.

8 .Assign File Execute Display change Save & click on click on button

9.Import Data Execute Display change Save & click on back button or press F3 button from your keybroad

10.Display Imported Data Enter ok, this will show records only. click on back button or press F3 button from your keybroad

11.Convert Data Execute Display change Save & click on back button or press F3 button from your keybroad

12.Display Converted Data Execute Display change Save & click on back button or press F3 button from your keybroad

13.Create Batch Input Session Tick keep batch input folder Press on F8 button on keyboard Click on back button or press F3 button from your keybroad

14.Run Batch Input Session Use TCodeSM35will come Object name will be shown here; Select object & process

AP Test Data Migration Server (SAP TDMS) is a high-speed data extraction tool that transfers relevant business data from your SAP production system to your development, test, quality assurance, or training system.By enabling the transfer of just the relevant set of application data from the SAP production system, SAP TDMS allows you to create a lean and consistent non-production system.SAP TDMS can be used in the test phase of SAP Application Lifecycle Management.Setting up your non-production can present the following challenges:Managing a high volume of data, which could lead to increasing costsProtecting sensitive data through complex authorizationPerforming post-transfer processing adjustments after carrying out a system or client copySAP TDMS enables you to better manage and control your non-production environment by providing the following advantages:Efficient management of lean non-production systems with datasets reduced by 70 percent on an averageEasier creation and refresh of non-production systemsImproved data control through the creation of efficient and consistent non-production systems, in turn leading to reduced costs and better quality of workComprehensive data protection for sensitive organizational data

I just check the Transaction Code: MASS at Header Level. It provides the field to enter Sales Document Number (From & to). Regular Sales Order & Return Sales Order have separate number range. This can be checked through Transaction Code: VOV8. Select the Number Range Object, say '01' for OR in Standard & '13' for RE in Standard. Next, check the Number Range in Transaction Code: VN01. Here you will get the Number Range assigned & Current Number being used by the system.

Alternatively, Check Number Range through Transaction Code: SE16 in Table VBAK for relevant Sales Document Type & Period & then use Transaction Code: MASS.

Customer, vendor, materialXD99XK99MASSPurchase order, Purchase Requisition, Purchase infoGL Account, ObjectTypeName

BUS0015Profit center

BUS1001Materials (industry)

BUS1001001Materials (retail)

BUS1006Business Partner

BUS1133Rental units

BUS1178001Mass Maintenance Mat

BUS2012Purchase orders

BUS2013Purch. Sched. Agrmt

BUS2014Purchase Contract

BUS2031Customer Quotation

BUS2032Sales orders

BUS2034Customer Contract

BUS2104Appropriation Req.

BUS2105Purchase Requisition

BUS3003Purchasing Info Rec.

BUS3006G/L Account

CA_CONTACCContract Account

FORCE_LSForceEl (Log. Syst.)

KNA1Customers

LFA1Vendors

Object TypeBUS1001

Var. nameVar. short text

GOGO

ID_PRCTRSchnellerfassung Profit Center

IGEN_MATIDES GENERIC MAT CHANGE

SCM240_40SCM240 Reset Strategies to 40 PWFA

T-F2##_SFCFert.profil 00003 APO-Pumpen Werk 1000

T-F2##_X0APO-Pumpen in Werk 1000

Normal JV FI Material

BDC or LSMWFalt file format data

Excel formatics idoc Hourly or monthly triggerIdoc - idoc is immediately or time SAP is updated

What challenges Open items