LSMW demo
Hi everyone....
I'm looking for LSMW step by step procedure document......or any material regarding LSMW........Pls help me
Thanking you.......
Hi,
1. Maintain Attributes:
Here you have to choose the second option and you can do the recording how this should work. Then assign the same to the Batch Input Recording name.
2. Maintain Source structure:
Create a structure name
3. Maintain Source field:
In this you have to create a structure same as taht of the input file
eg: name
age
4. Maintain structure relations:
This will link the structure to the input file.
5. Maintain field mapping and conversion rules:
Here is the place where you can do coding, depending upon the code you have written or assignment you have done the values will get picked up from the file and get processed.
6. Maintain field mapping and conversion rules:
If you have any fixed values you can define here.
7. Specify files:
Specify the input file path and type.
8. Assign files:
This will assign ur file to the Input file
9. Read Data:
This will read ur data from teh file.
10. Dispaly Read Data:
You can see the uploaded data
11. Convert Data
This will convert the data to the corresponding format for processing
12. Display Converted data:
13. Create batch input session
Here this will create a batch input session for processing
14. Run Batch Input session:
By clicking on the session and process the same you can do teh needfu.
Hope this helps you.
Similar Messages
-
Documentation for LSMW and BDC
can anybody give me documentation for LSMW and bdc and its relevance in asset accounting.
Hi Anand,
there are several threads available in this forum for this topic. kindly do a search- you will get several useful material.
i have given u couple of useful links
LSMW
LSMW demo
BDC & LSMW
The last thread has both the topic u have asked about.
Thanks
Janani
award points if helpful -
Can anyone give the steps to create a lsmw for Customer master(XD01) using recording method or Standard/Direct input method
thanks,
Dinesh Enter T-code LSMW
Enter project name (LSMW-DEMO)
Click on create entry button (shift+F1)
Enter the description
Press enter button
Enter sub project name & description
Press enter button
Enter object & object name
Press enter button
Click on continue (F8) button
System displays 21 steps
(Focus on the 1st step)
Step (1): - Maintain object attributes
Click on object attributes
Click on execute button (ctrl +F8)
Click on display change (ctrl+F1)
Click on batch INPUT recording (radio button)
Click on go to and select recordings overview
Click on u201Ccreate recordingu201Dbutton. (Ctrl+F1)
Enter name (RECCUST) of recording & description (RECORDING FOR CUSTOMER)
Enter owner (SAPUSER)
Press enter button
Enter the transaction code (VDOL)& press enter button
Create CMR using the general process
System displays the newly created customer number
Click on default ALL
System displays field names for which date is maintained
Note these fields names in a text tile
Click on save button
Click on back button
Click on back button
Enter the recording name in recoding field ex RECCUST
Press enter button
Click on save button
Click on back button
Observation: -
1) The cursor position is automatically changed to second step. After every step completion the cursor position is changed to succeeding step.
2) Steps are reduced to 14
Step (2) :- Maintain source structures
Click on execute button
Click on display change button
Click on create a structure button
Enter source structure name 2 description,& 2 press enter button
Click on save button
Click on back button
Step(3) :- Maintain source fields
Click on execute button
Click on display change button
(note)try to maintain the source field names same as target fields names
Click on the source structure
Click on copy fields button
Select upload (text separated with tabs) & press enter button
Click on save button
Click on back button
Step (4) :- Maintain structure relations
Click on execute button
Click on display change button
Observations :-source structure & target structure relations is already maintained
Click on save button
Click on back button
Step (5) :- Maintain field mapping 2 convention rules
Click on execute button
Click on display change button
Select the first field (under fields)
Click on u201Cextrasu201D & select u201Cauto field mappingu201D
Click on ok button(continue button)
Click on accept proposal
Continue clicking on accept proposal till all the fields are mapped
System displays auto field mapping complete
Press enter button
Click on save button
Click on back button
Step(6) :- Maintain fixed values transudation user defined routines
This step is optional
We may use this when creation changes are to be made like dollar to euro etc.
Step(7) :- Specify files
Select specify files
Click on enecute button
Click on display change button
Click on legacy data
Click on u201CAdd entryu201D button
Specify the file name (customer records file path)
Specify the name (CMR RECORDS)
Click on tabulator
Press enter button
Click on save button
Click on back button
Step(8) :-Assign files
Click on execute button
Click on display change button
Click on save button
Click on back button
Step(9):-import data
Click on execute button
Click on execute button again
Observations:-transactions read & transactions written are same & and equal to the no. of records maintained in text file.
Click on back button
Again click on back button
Step(10) :-Display imported data.
Click on execute button
Press enter button.(imported data is displayed)
Click on back button
Step(11) :-Convert data
Click on execute button
Again click on execute button
Observations :- transactions red & transactions written are same and are equal to records in the text file
Click on back button
Again click on back button
Step(12) :-Display converted data
Click on execute button
Press enter button
Click on back button
Step(13) :-Create batch input session
Click on create button
Again click on execute button
System displays a message saying that a u201Cbatch input folderu201D is created with specified number of transactions
Press enter button
Click on back button
Step(14) :- Run batch input session
Click on execute button
Select the required u201Csession nameu201D and click on u201Cprocess buttonu201D
Select u201Cforeground processu201D or u201Cbackground processu201Detc
Click on u201Cprocess buttonu201D -
Conversion utilities e.g. LSMW
What is conversion utilities?.
what is LSMW stands for?.
Please help me out.Ash,
Go through this:
LSMW
LSMW demo
http://help.sap.com/saphelp_nw04/helpdata/en/ad/2d54a41d7011d2b42e006094b944c8/frameset.htm
---Satish -
Material Master Mass Maintenance
Hi
How can we extend our matl master in bulk.. in the follwoing scenarios.
1. One matl master to many plants.. We have cases like 800 plants..
2. Many matl master (say 1000 masters) to single plant.
Regards
RamHi,
there are several threads available in this forum for LSMW. kindly do a search- you will get several useful material.
i have given u couple of useful links
LSMW
LSMW demo
BDC & LSMW
Reward points if helpful,
Regards,
Archit -
i created lsmw program for mm01 using direct input method .
i done upto defining source fields now i want to create the relation between structures ,In this step what to do can any body give suggetions
here i am sending what i have dine
Here I am defining source structures.this one is 2nd step
ZCPROJ - ZCSUB - ZCOBJ demo on object
Source Structures
|
|-----ZBSTRUC basic view structure
|-----ZMDES Material description
|-----ZALT ALT UOM Structure
|-----ZCLAS Classification structure
|-----ZSALV Sales view
|-----ZSALT sales taxes
|-----ZSALTX sales text
|-----ZPUR Purchasing
|-----ZPURT Purchasing text
|-----ZPLAN Plant data
|-----ZFORC forecasting
|-----ZWSH Work scheduling
|-----ZPLS plant data storage
|-----ZWMST WM Structure
|-----ZQMST QM Structure
|-----ZACCO account cost
3rd step defining source fields
ZCPROJ - ZCSUB - ZCOBJ demo on object
Source Fields
|
|--5 ZBSTRUC basic view structure
| |-----MATNR C(010) Material
| |-----MBRSH C(010) Industry sector
| |-----MTART C(010) Material type
| |-----AENNR C(010) Change number
| |-----MATNR1 C(010) material
| |-----MAKTX C(010) material description
| |-----MEINS C(010) asic unit of measure
| |-----MATKL C(010) Material group
| |-----BISMT C(010) old matrerial no
| |-----EXTWG C(010) External material group
| |-----SPART C(010) division
| |-----LABOR C(010) lab off
| |-----PRDHA C(010) product heirarchy
| |-----MSTAE C(010) material status
| |-----MSTDE C(010) valid from
| |-----MTPOS_MARA C(010) General item catogory group
| |-----FERTH C(010) Produc inspection memo
| |-----CADKZ C(010) cad indicator
| |-----WRKST C(010) basic material
| |-----KZUMW C(010) environmentally relevent indicator
| |-----ZZPCODE C(010) product code
| |-----ZZPMODEL C(010) product model
| |-----ZSWVER C(010) version
| |-----ZZMET C(010) meta class
| |-----ZEINR C(010) document
| |-----ZEIVR C(010) documentversion
| |-----ZEIAR C(010) document type
| |-----SATNR C(010) cross plat CM
| |-----BLATT C(010) page number
| |-----KZKFG C(010) material configurable
| |-----BRGEW C(010) gross weight
| |-----GEWEI C(010) weight unit
| |-----NTGEW C(010) net weight
| |-----VOLUM C(010) volume
| |-----VOLEH C(010) volme unit
| |-----GROES C(010) size/ deimension
| |-----MDZUO C(010) design documents attached
|
|--5 ZMDES Material description
| |-----MATNR C(010) material
| |-----SPRAS C(010) language
| |-----MAKTX C(010) material description
|
|--5 ZALT ALT UOM Structure
| |-----MATNR C(010) material
| |-----MAKTX C(010) material description
| |-----UMREN C(010) alt uom volume
| |-----MEINH C(010) alt uom
| |-----UMREZ C(010) base conversion factor
| |-----MEINS C(010) basic unit of measuer
|
|--5 ZCLAS Classification structure
| |-----MATNR C(010) material
| |-----MAKTX C(010) material description
| |-----KLART C(010) material type
| |-----CLASS C(010) mateial class
| |-----ATNAM C(010) internal charecteristic
| |-----ATWRT C(010) charecteristic value
|
|--5 ZSALV Sales view
| |-----MATNR C(010) material
| |-----MAKTX C(010) material description
| |-----VKORG C(010) sales organization
| |-----SPART C(010) division
| |-----MSTAV C(010) cross distribution channel status
| |-----MSTDV C(010) valid from
| |-----VMSTA C(010) Distribution channel specific status
| |-----VMSTD C(010) valid from
| |-----DWERK C(010) delivery plat
| |-----MATKL C(010) material group
| |-----SKTOF C(010) cash discount
| |-----AUMNG C(010) minimum order quantity
| |-----LFMNG C(010) min delivery quantity
| |-----SCMNG C(010) delivery unit quantity
| |-----RDPRF C(010) rounding frofile
| |-----VERSG C(010) material statistic group
| |-----KONDM C(010) material pricing group
| |-----KTGRM C(010) account assign ment group
| |-----MTPOS_MARA C(010) general item category group
| |-----MTPOS C(010) item category group
| |-----PMATN C(010) pricing material group
| |-----PRODH C(010) product heirarchy
| |-----MVGR1 C(010) material group1
| |-----MVGR2 C(010) material group2
| |-----MVGR3 C(010) material group3
| |-----MVGR4 C(010) material group4
| |-----MVGR5 C(010) material group5
| |-----ZMORT C(010) mat type
| |-----ZZCCODE C(010) char cdoe
| |-----ZZCVALU C(010) charecter value
|
|--5 ZSALT sales taxes
| |-----MATNR C(020) material
| |-----TALND C(003) tax country code
| |-----TAXKM C(010) taxclassification 1
| |-----TAXKM1 C(010) tax clasificaton 2
| |-----TAXKM2 C(010) tax classification3
| |-----TAXKM3 C(010) tax classification 4
| |-----TAXKM4 C(010) tax classification 5
| |-----TAXKM5 C(010) tax classification 6
| |-----TAXKM6 C(010) tax classification 7
| |-----TAXKM7 C(010) tax classification 8
| |-----TAXKM8 C(010) tax classification 9
|
|--5 ZSALTX sales text
| |-----RMATNR C(020) refrence material
| |-----MATNR C(020) material code
| |-----VKORG C(010) sales organization
| |-----VTWEG C(010) distribution channel
| |-----SPART C(010) division
| |-----DESC C(040) descrition
| |-----SPARS C(003) language
|
|--5 ZPUR Purchasing
| |-----MATKL C(010) material description
| |-----MMSTA C(010) plant specific material status
| |-----MMSTD C(008) valid from
| |-----KAUTB C(020) automatic purchase order
| |-----XCHPF C(020) batch management
| |-----EKWSL C(020) purchasing value key
| |-----WEBAZ C(020) goods receiving proc time
| |-----INSMK C(020) post into inspection stock
| |-----KZKRI C(020) critical part
| |-----USEQU C(020) quota arr usage
| |-----KORDB C(020) source list
| |-----FABKZ C(020) jit scheduling
|
|--5 ZPURT Purchasing text
| |-----REMATNR C(020) refrence material
| |-----MATNR C(020) material
| |-----WERKS C(010) plat
| |-----TEXT C(040) text line
| |-----SPRAS C(003) language
|
|--5 ZPLAN Plant data
| |-----MATNR C(020) material
| |-----WERKS C(010) plant
| |-----MEINS C(010) basic unit of measure
| |-----BRGEW C(010) gross weight
| |-----GEWEI C(010) weight unit
| |-----NTGEW C(010) net weight
| |-----MTVFP C(010) availability check
| |-----XCHPF C(010) batch management
| |-----TRAGR C(010) transportation group
| |-----LADGR C(010) loading group
| |-----XMCNG C(010) negative stocks
| |-----PRCTR C(010) profit center
| |-----SERNP C(010) serial number profile
| |-----STAWN C(010) commodity import code
| |-----MTVER C(010) export import group
| |-----CASNR C(010) cash number
| |-----HERKL C(010) contry of origin
| |-----HERKR C(010) regeion of orih\gin
| |-----PRENC C(010) excemption cert
| |-----PRENO C(010) excempton cert no
| |-----PREND C(010) issue date of cert no
| |-----ZDTCD C(010) import duty code
| |-----ZDTRT C(010) import date
| |-----DISGR C(010) mrp group
| |-----EKGRP C(010) purchasing group
| |-----MAABC C(010) abc indicator
| |-----MMSTA C(020) plant specific material status
| |-----MMSTD C(010) date of pim spe status
| |-----DISMM C(010) mrp type
| |-----MINBE C(010) reorder print
| |-----FXHOR C(010) planning time fence
| |-----LFRHY C(010) planing cycle
| |-----DISPO C(010) mrp controller
| |-----DISLS C(010) lot size key
| |-----BSTFE C(010) fixed lot size
| |-----MABST C(010) maximum stock level
| |-----BSTMI C(010) minimum lot size
| |-----BSTMA C(010) maximun lot size
| |-----BSTRF C(010) Rounding value
| |-----DIBER C(010) MRP area exists
| |-----BESKZ C(010) Procurement type
| |-----SOBSL C(010) Special procurement
| |-----LGPRO C(010) Prod. stor. location
| |-----USEQU C(010) Quota arr. usage
| |-----VSPVB C(010) Default supply area
| |-----RGEKZ C(010) Backflush
| |-----LGFSB C(010) Storage loc. for EP
| |-----FABKZ C(010) JIT sched. indicator
| |-----EPRIO C(010) Withdr. seq. group
| |-----SCHGT C(010) Bulk Material
| |-----DZEIT C(010) In-house production
| |-----PLIFZ C(010) Plnd delivery time
| |-----WEBAZ C(010) GR processing time
| |-----MRPPP C(010) Planning calendar
| |-----FHORI C(019) SchedMargin key
| |-----EISBE C(010) Safety stock
| |-----LGRAD C(010) Service level (%)
| |-----EISLO C(010) Min safety stock
| |-----RWPRO C(010) Coverage profile
| |-----SHFLG C(010) Safety time ind.
| |-----SHZET C(010) Safety time/act.cov.
| |-----SHPRO C(010) STime period profile
| |-----ZKROP C(010) ZKROP
| |-----ZZUSI C(010) ZZUSI
| |-----ZRPQT C(010) ZRPQT
| |-----ZZUS2 C(010) ZZUS2
| |-----ZRPCD C(010) ZRPCD
| |-----ZZUS3 C(010) ZZUS3
| |-----ZXKBR C(010) ZXKBR
| |-----ZZPACK C(010) ZZPACK
| |-----ZSKBR C(010) ZSKBR
| |-----ZRTRN C(019) ZRTRN
| |-----ZPDAY C(010) ZPDAY
| |-----ZRPRB C(010) ZRPRB
| |-----ZSTOP C(010) ZSTOP
| |-----ZZMCL C(010) ZZMCL
| |-----ZPRN_FLG1 C(010) ZPRN_FLG1
| |-----ZZSERIALIZED C(010) ZZSERIALIZED
| |-----ZPRN_FLG2 C(010) ZPRN_FLG2
| |-----ZZFRU C(010) ZZFRU
| |-----ZZMENGE C(010) ZZMENGE
| |-----PERKZ C(010) Period indicator
| |-----PERIV C(010) Fiscal Year Variant
| |-----STRGR C(010) Planning strategy group
| |-----VRMOD C(010) Consumption mode
| |-----VINT1 C(010) Bwd consumption per.
| |-----VINT2 C(010) Fwd consumption per.
| |-----MISKZ C(010) Mixed MRP
| |-----PRGRP C(010) Product group
| |-----PRWRK C(010) Production plant
| |-----UMREF C(010) Conversion factor
| |-----VPBME C(010) Planning matl BUnit
| |-----WZEIT C(010) Tot. repl. lead time
| |-----KZPSP C(010) Cross-project matl
| |-----STDPD C(010) ConfigurableMaterial
| |-----ALTSL C(001) Selection method
| |-----KAUSF C(010) Component scrap (%)
| |-----SBDKZ C(010) Individual/coll.
| |-----KZBED C(010) Requirements group
| |-----VERKZ C(010) Special stock maint.
| |-----AHDIS C(010) MRP dep.requirements
| |-----KZAUS C(010) Discontinuation ind.
| |-----AUSDT C(010) Effective-out date
| |-----NFMAT C(010) Follow-up material
| |-----SAUFT C(010) Sales value
| |-----SFEPR C(010) REM profile
| |-----MDACH C(010) Action control
| |-----DPLFS C(010) Fair share rule
| |-----DPLPU C(010) Push distribution
| |-----DPLHO C(010) Deployment horizon
|
|--5 ZFORC forecasting
| |-----MATNR C(020) Material_No
| |-----WERKS C(010) plant
| |-----PRMOD C(010) Forecast model
| |-----PERKZ C(010) Period indicator
| |-----PRDAT C(010) Last forecast
| |-----PERIV C(010) Fiscal Year Variant
| |-----VRBMT C(010) RefMatl: consumption
| |-----VRBWK C(010) RefPlant:consumption
| |-----VRBDT C(010) Date to
| |-----VRBFK C(010) Multiplier
| |-----PERAN C(010) Historical periods
| |-----ANZPR C(010) Forecast periods
| |-----PERIO C(010) Periods per season
| |-----PERIN C(010) Initialization pds
| |-----FIMON C(010) Fixed periods
| |-----KZINI C(010) Initialization
| |-----SIGGR C(010) Tracking limit
| |-----AUTRU C(010) Reset automatically
| |-----MODAW C(010) Model selection
| |-----MODAV C(010) Selection procedure
| |-----KZPAR C(010) Param.optimization
| |-----OPGRA C(010) Optimization level
| |-----GEWGR C(010) Weighting group
| |-----KZKFK C(010) Correction factors
| |-----ALPHA C(010) Alpha factor
| |-----BETA1 C(010) Beta factor
| |-----GAMMA C(010) Gamma factor
| |-----DELTA C(010) Delta factor
|
|--5 ZWSH Work scheduling
| |-----MATNR C(010) Material_No
| |-----WERKS C(010)
| |-----AUSME C(010) Unit of issue
| |-----FRTME C(010) Production unit
| |-----MMSTA C(010) Plant-sp.matl status
| |-----MMSTD C(019) Valid from
| |-----FEVOR C(010) Production scheduler
| |-----LGPRO C(010) Prod. stor. location
| |-----SFCPF C(010) SFCPF
| |-----MATGR C(010) MATGR
| |-----SERAIL C(010) Serial no. profile
| |-----OCMPF C(010) OCMPF
| |-----INSMK C(010) Stock type
| |-----KZKRI C(010) Critical part
| |-----VERKZ C(010) Special stock maint.
| |-----XCHPF C(010) Batch management
| |-----KZECH C(010) Batch entry
| |-----UNETO C(010) Underdely tolerance
| |-----UEETO C(010) Overdely tolerance
| |-----UEETK C(010) Unltd overdelivery
| |-----RUEZT C(010) Setup time
| |-----PRANZ C(010) Number of
| |-----DZEIT C(010) In-house production
| |-----EISBE C(010) Safety stock
| |-----BASMG C(010) Base quantity
|
|--5 ZPLS plant data storage
| |-----MATNR C(010) Material_No
| |-----WERKS C(010) plant
| |-----LGORT C(010) storage location
| |-----MEINS C(010) Base Unit of Measure
| |-----AUSME C(010) Unit of issue
| |-----LGPBE C(010) Storage bin
| |-----LWMKB C(010) LWMKB
| |-----TEMPB C(010) Temp. conditions
| |-----RAUBE C(010) Storage conditions
| |-----BEHVO C(010) Container reqmts
| |-----STOFF C(010) Haz. material number
| |-----ABCIN C(010) CC phys. inv. ind.
| |-----CCFIX C(010) CC indicator fixed
| |-----WESCH C(010) Number of GR slips
| |-----ETIAR C(010) Label type
| |-----ETIFO C(010) Label form
| |-----XCHPF C(010) Batch management
| |-----MAXLZ C(010) Max. storage period
| |-----LZEIH C(010) Time unit
| |-----MHDRZ C(010) Min. rem. shelf life
| |-----MHDHB C(010) Total shelf life
| |-----IPRKZ C(010) IPRKZ
| |-----RDMHD C(010) Rounding rule SLED
| |-----MHDLP C(010) Storage percentage
| |-----BRGEW C(010) Gross weight
| |-----GEWEI C(010) Weight unit
| |-----NTGEW C(010) Net weight
| |-----VOLUM C(010) Volume
| |-----VOLEH C(010) Volume unit
| |-----GROES C(010) Size/dimensions
| |-----XMCNG C(010) Neg. stocks in plant
| |-----LOGGR C(010) Log. handling group
| |-----SERAIL C(010) Serial no. profile
| |-----PRCTR C(010) Profit Center
| |-----EPRIO C(010) Withdr. seq. group
|
|--5 ZWMST WM Structure
| |-----MATNE C(010) MATNE
| |-----WERKS C(010)
| |-----LGNUM C(010) Warehouse Number
| |-----STOFF C(010) Haz. material number
| |-----LVSME C(010) LVSME
| |-----BRGEW C(010) Gross weight
| |-----GEWEI C(010) Weight unit
| |-----AUSME C(010) Unit of issue
| |-----VOLUM C(010) Volume
| |-----VOLEH C(010) Volume unit
| |-----VOMEM C(010) VOMEM
| |-----MKAPV C(010) MKAPV
| |-----BEZME C(010) BEZME
| |-----PLKPT C(010) PLKPT
| |-----XCHPF C(010) Batch management
| |-----LTKZA C(010) LTKZA
| |-----LTKZE C(010) LTKZE
| |-----LGBKZ C(010) LGBKZ
| |-----BLOCK C(010) Seq. blocked
| |-----BSSKZ C(010) BSSKZ
| |-----KZMBF C(010) Message to inv. mgmt
| |-----L2SKR C(010) L2SKR
| |-----KZZUL C(010) KZZUL
| |-----LHMG1 C(010) LHMG1
| |-----LHME1 C(010) LHME1
| |-----LETY1 C(010) LETY1
| |-----LHMG2 C(010) LHMG2
| |-----LHME2 C(010) LHME2
| |-----LETY2 C(010) LETY2
| |-----LHMG3 C(010) LHMG3
| |-----LHME3 C(010) LHME3
| |-----LETY3 C(010) LETY3
|
|--5 ZQMST QM Structure
| |-----MATNR C(010) Material_No
| |-----MEINS C(010) Base Unit of Measure
| |-----QMATV C(010) Inspection setup
| |-----AUSME C(010) Unit of issue
| |-----INSMK C(010) Stock type
| |-----QMATA C(010) QMATA
| |-----KZDKZ C(010) Documentation reqd
| |-----WEBAZ C(010) GR processing time
| |-----PRFRQ C(010) Inspection interval
| |-----RBNRM C(010) RBNRM
| |-----MMSTA C(010) Plant-sp.matl status
| |-----MMSTD C(010) Valid from
| |-----QMPUR C(010) QM proc. active
| |-----LANGU C(010) Language Key
| |-----ART C(010) ART
| |-----APA C(010) APA
| |-----AKTIV C(010) Total
|
|--5 ZACCO account cost
|
|-----MATNR C(010) Material_No
|-----WERKS C(019) plant
|-----BWTTY C(010)
|-----MLAST C(010) MLAST
|-----MLMAA C(010) MLMAA
|-----BKLAS C(010) Valuation Class
|-----EKLAS C(010) VC: Sales order stk
|-----QKLAS C(010) Proj. stk val. class
|-----VPRSV C(010) Price control
|-----PEINH C(010) Price unit
|-----VERPR C(010) Moving price
|-----STPRS C(010) Standard price
|-----LBKUM C(010) Total stock
|-----SALK3 C(010) Total value
|-----ZKPRS C(010) ZKPRS
|-----ZKDAT C(010) ZKDAT
|-----STPRV C(010) Previous price
|-----LAEPR C(010) Last price change
|-----BWPRS C(010) Tax price 1
|-----BWPS1 C(010) Tax price 2
|-----VJBWS C(010) Tax price 3
|-----BWPRH C(010) Commercial price 1
|-----BWPH1 C(010) Commercial price 2
|-----VJBWH C(010) Commercial price 3
|-----ABWKZ C(010) Devaluation ind.
|-----BWPEI C(010) Price unit
|-----XLIFO C(010) LIFO/FIFO-relevant
|-----MYPOL C(010) MYPOL
|-----NCOST C(010) NCOST
|-----EKALR C(010) EKALR
|-----HRKFT C(010) Origin group
|-----HKMAT C(010) Material origin
|-----KOSGR C(010) KOSGR
|-----AWSLS C(010) Variance Key
|-----SOBSK C(010) SOBSK
|-----LOSGR C(010) Planned lot size
|-----KZKUP C(010) Co-product
|-----FVIDK C(010) FVIDK
|-----PPRDZ C(010) Period
|-----PDATZ C(010) Fiscal year
|-----ZPLRP C(010) ZPLRP
|-----PPRDL C(010) PPRDL
|-----PDATL C(010) PDATL
|-----LPLPR C(010) LPLPR
|-----PPRDV C(010) PPRDV
|-----PDATV C(010) PDATV
|-----VPLPR C(010) PreviousPlannedPrice
|-----ZPLP1 C(010) ZPLP1
|-----ZPLD1 C(010) ZPLD1
|-----ZPLP2 C(010) ZPLP2
|-----ZPLD2 C(010) ZPLD2
|-----ZPLP3 C(010) ZPLP3
|-----ZPLD3 C(010) ZPLD3
In 4th step what to do could you pleas sggest me
ZCPROJ - ZCSUB - ZCOBJ demo on object
Structure Relations
|
|--5 BGR00 Batch Input Structure for Session Data
| Select Target Structure BGR00 .
|
|--5 BMM00 Material Master: Transaction Data for Batch Input
| Select Target Structure BMM00 .
|
|-----BMMH1 Material Master: Transfer of Main Data
| Select Target Structure BMMH1 .
|-----BMMH2 Material Master: Country Data for Batch Input (from 2nd Cty)
|-----BMMH3 Material Master: Forecast Values for Batch Input
|-----BMMH4 Material Master: Consumption Values for Batch Input
|-----BMMH5 Mat. Master: Descriptions for Batch Input (Except 1st Text)
|-----BMMH6 Material Master: Units of Measure for BTCI
|-----BMMH7 Material Master: Long Texts for Batch Input
|-----BMMH8 Material Master: Referential EANs for BTCI
in this step these structures are have some fields but in source structure which i created previous steps each structure have fields which are not there in these strcture
could you lease suggest me what to do
regard,
Chaitanya<b>>Place the cursor on Maintain Source Relations on the LSMW workbench screen and press the Execute button.
>Press the Display<->Change button to switch to Edit mode.
>Here you must map the fields of the source structure with the fields of the destination structure.
>This mapping is important as it will direct the data in the fields from the Source Structure (populated from flat file) to the appropriate fields in the Destination Structure.
Regards,
Pavan P.
</b> -
LSMW - Migration of Opportunites, Text field is missing !!!!
Hi everybody,
I try to migrate opportunites via LSMW into SAP CRM.
(Idoc: Message Type "CRMXIF_ORDER_SAVE_M,
Basic Type "CRMXIF_ORDER_SAVE_U04")
I have done this with one legacy system and it works fine.
But for the second legacy system I was not able to migrate the text. The Text is written into the corresponding structure "E101CRMXIF_TEXT_XT" as I did with the first legacy system.
TEXT_ID = '0001'
LANGUAGE = 'E'
After I convert the data I can see that everything is fine. For each text line a flag is set.
Within the IDOC, I can see the text as requested. When I open the opportunity in SAP everything is there except the text in the node tab.
Does anybody has an idea where the problem might be?
Thanks in advance.
PS: If I can not solve this problem, I will drive crazyHi,
I am looking for the mandatory fields that are required for migrating the following using IDOC in LSMW.. Please suggest.
Area Object Description
Master Data CUSTOMER Customer / Prospect / Site
Master Data CONTACT Contact Person
Master Data CONTACT_REL Contact Person Relationships
Installed Base IBASE Installed Base
Transactions SER_TICKET CC Ticket
Transactions SER_ORDER Service Order
Transactions SER_CONFIRM Service Confirmation
Transactions SER_CONTRACT Service Contracts
Transactions SAL_LEAD Lead
Transactions SAL_OPPORT Opportunity
Transactions SAL_QUOTE Quotation
Transactions SAL_DEMOREQUEST Demo Request
Transactions SAL_ORDER Sales Order
Transactions SAL_CONTRACT Frame Contracts
Transactions XXX_ACTIVITY Activities -
Dear Experts,
how to upload partner functions by using LSMW. I developed LSMW and if i go to partner function tab there is only one partner function field is available I need to upload 4 partner functions. Can any one help me out in this regard.
regards,
sivaHello Sivasai Myneni,
Demo Example 1
LSMW to Update Customer Master Records with Transaction Recording
Call Legacy System Migration Workbench by entering transaction code LSMW. Every conversion task is grouped together as
Project / Subproject / Object structure. Create a Project called LSMW_DEMO and a Subproject as CUSTOMERS and Object as
CUST_obj as shown in Figure 1.
Figure 1 Conversion Task with Project, Subproject and Object
The main screen of LSMW provides wizard-like step-by-step tasks, as shown in Figure 2. To complete your data conversion, you
need to execute these steps in sequence. Once a step is executed, the cursor is automatically positioned to the next step.
Note that these steps may look different depending upon your Personal menu settings. You could make step numbers visible by
Numbers on icon or hidden by Numbers off icon. You can execute a step by double-clicking on the row. Toggle icon
Doubleclick=Display or Doubleclick=Edit, makes the step in display mode or change mode.
Figure 2 LSMW Wizard initial screen
Step 1: Maintain Object attributes
In this example, you will be updating the customer master records with the help of recording a transaction (XD02). Choose radio
button Batch Input Recording and click on the recording overview icon to record the R/3 transaction. Enter the Recording name as
XD02_REC, the description as Customer Master Updates Recording, and the transaction code as XD02.
Figure 3 Object type Transaction Recording
The system calls the transaction code XD02 and prompts you to complete the Change
Customer transaction, as shown in Figure 4. Enter the key customer information (I entered customer number 1000, sales
organization 1000, distribution channel 01, and division 00) and choose Sales view within Sales area data. Make changes to
these three fields (I entered, sales office 1010, sales group 110, and customer group 01) and save the transaction.
Figure 4 Transaction recording for Transaction Code XD02
Once the transaction is completed, R/3 records the flow of screens and fields and saves the information, as shown in Figure 5.
Figure 5 Transaction recording overview
Note that the fields are populated with default values. The values you entered when you recorded the transaction are set by
default.
Note that if you have more fields in the recording than needed, you can remove them by clicking Remove Screen field icon.
Observe that the transaction-recording process stores field names in a technical format. By pressing the F1 key on individual
screen fields and then pressing the F9 key, the system displays technical names. You then can replace the technical names with
descriptive names. Double-click on the field RF02D-KUNNR and enter the name as KUNNR and the description as Customer
Account Number and remove the default value. (See Figure 6.)
Figure 6 Field attributes
Similarly, double-click on all other fields with default values and make appropriate changes. Once you have made changes, the
recording overview screen looks like what you see in Figure 7.
Figure 7 Transaction Recording Overview with screen field attributes
Save your changes. When you go back to the initial screen, you will see that the initial screen steps have changed. Since you want
to import data via the BDC method, the Direct Input and IDoc-related steps are hidden, as they are not relevant.
Step 2. Maintain Source Structures
Give a name and a description to the source structure (Figure 8).
Figure 8 Source Structure
Step 3. Maintain Source Fields
In this step, you need to list what fields are present in the source structure. The easiest way is to click on Table Maintenance icon
to enter Fieldname, Type and Length for each field as shown in Figure 9.
Figure 9 Source fields of source Structure
Note that your input file will have four fields as key fields and you need to update three fields in the system.
Step 4: Maintain Structure Relations
Execute a step to Maintain Structure Relations. (See Figure 10.) Since, there is only one Source and Target Structure, the
relationship is defaulted automatically.
Figure 10 Structure Relation
Step 5: Maintain field mapping and conversion rules
Field RF02D-D0310 represents that you chose Sales view for the customer Master screen accordingly its value should be set to
X. Keep your cursor on field RF02D-D0310 and click on Constant rule icon to choose the constant value of X.
If your source file already has the field value, you choose rule Source Field.
Keep cursor on field KUNNR and click on Assign Source field icon to choose source field CUSTOMER from structure XD02S as
shown in Figure 11.
Figure 11 Assign source fields
Similarly, assign Source Field rules to the remaining fields.
Once all the fields are mapped, you should have an overview screen as shown in Figure 12.
Figure 12 Field mapping and Conversion rules overview
Step 6: Maintain fixed values, translations, user-defined routines
You can also maintain re-usable translations and user-defined routines, which can be used across conversion tasks. In this case,
that step is not required.
Step 7: Specify files
In this step, we define how the layout of the input file is. The input file is a [Tab] delimited with the first row as field names. It is
present on my PC (local drive) as C:\XD02.txt. (See Figure 13.)
Figure 13 File attributes
Create an Excel file (Figure 14) with your data and save it as a Tab-delimited text file on your local drive (C:\) and name it XD02.
txt.
Figure 14 Source data in Excel file (saved as Tab delimited file)
Step 8: Assign files
Execute step Assign Files (Figure 15) and the system automatically defaults the filename to the source structure.
Figure 15 Assign file to Source Structure
Step 9: Read data
In this step, LSMW reads the data (Figure 16) from the source file (from your PCs local drive). You have the option to read only
selected rows and convert data values to Internal format.
Figure 16 Read Data
Step 10: Display read data
This step (Figure 17) is optional. If required, you can review the field contents for the rows of data read.
Figure 17 Display Read Data
Step 11: Convert data
This is the step that actually converts the source data (in source format) to a target format. Based on the conversion rules defined,
source fields are mapped to target fields.
Step 12: Display Converted data
Again this is an optional step to view how the source data is converted to internal SAP format (Figure 18).
Figure 18 Display Converted Data
Step 13: Create batch input session
Once the source data is converted in an internal format, you can create a batch session to process updates (Figure 19).
Figure 19 Create Batch Input Session
Step 14: Run Batch Input Session
You can execute the BDC session by Run Batch input session. Executing a batch input session is a standard SM35 transaction for
managing BDC sessions. Once you have successfully executed the batch input session, the customer master records are updated in
the system. You can confirm this by viewing the customer master records (XD03).
Note! Browsing thru these 14 steps, you may get a feeling that this is a very lengthy and time-consuming activity. However, for
the purposes of demonstration, I have made it detailed. Although it looks lengthy, actually it takes hardly few hours from start-to-
finish! After playing around with few simple LSMW scripts, you will find it so easy to change and create more complex ones.
Demo Example 2
LSMW to Update Customer Master Records with Standard Object
As an alternative to using Transaction Recording, you could also use a standard SAP object to update Customer Master Records.
Business Object 0050 is already pre-defined in the system with standard Batch Input Interface Program RFBIDE00.
Create an Object CUST_OBJ within Project as LSMW_DEMO and Subproject as CUSTOMERS as shown in Figure 20.
Figure 20 LSMW Object with Standard SAP Object
Note! For the Demo example 2, I will list only those steps that are different from the first demo example.
Step 1: Maintain Object attributes
You will be updating the customer master records with the help of Standard Batch Input; therefore, choose radio-button Standard
Batch/Direct Input as shown in Figure 21. Enter Object 0050 for Customer Master records and default method 0000 and click
on Save.
Figure 21 Standard Batch/Direct Input Object Attributes
Step 4: Maintain Structure Relations
Sales view of Customer Master is stored in table KNVV. Accordingly, you need to update structure BKNVV. However, in addition,
the Standard Object 0050 also requires updates to BGR00, BKN00 and BKNA1 structures. (If you do not maintain Structure
relations for mandatory entries, you might get a message such as Target structure BKNA1 needs a relation to a source structure.)
Even though you dont want to update any fields in these structures, you need to create a relationship with source structures. In
all, you need to create relationship for four target structures.
Create relationship between source structures XD02S with these target structures with icon Create Relationship .
Keep Cursor on these four target structures and click on icon Create Relation and structure relations are maintained as shown in
Figure 22.
Figure 22 Structure Relation
Step 5: Maintain field mapping and conversion rules
Keep your cursor on TCODE field and click on Insert Rule icon
Figure 23 LSMW Conversion Rules
Choose radio button Constant (Figure 23) to enter value XD02 transaction code.
Keep your cursor on field KUNNR and click on Assign source field icon
Choose source field Customer from source structure XD02S. (See Figure 24.)
Figure 24 Assign Source fields
Similarly, choose source fields for Sales Organization, Distribution Channel, and Division. (See Figure 25.)
Figure 25 Field Mapping and Conversion Rules
Scroll down to structure BKNVV fields and assign source fields to three fields Sales Office, Sales Group, and Customer Group
(Figure 26).
Figure 26 Field Mapping and Conversion Rules
Save and go back to main screen.
Step 12: Display Converted data
When you convert data, LSMW automatically converts into the appropriate structure layouts, as required by Standard program
(RFBIDE00). (See Figure 27).
Figure 27 Converted data into multiple structures
Note that if you had only one record in source file, the converted file has four records.
Earlier, creating this input file, so that the standard interface program can read it, was a big nightmare, the primary reason being
that it could have multiple record layouts. Even for a simple conversion with one input record, you would have to create this
complex file with many record layouts. The advantage of LSMW is that it prepares these multi-layout files automatically.
Step 13: Create batch input session
Once source data is converted in internal format, you can create a BDC session to process the updates (Figures 28 and 29).
Figure 28 Create BDC Session
Figure 29 BDC Session CUST_OBJ created
Regards
AK -
Unable to update VAP2 via LSMW
There is an LSMW for VAP2 transaction which uses records from the flat file to update the data.
I am trying to update the Salutation/Title of the contact person via VAP2 transaction using records from the flat file. In VAP2 transaction salutation/title appears as drop down menu, these recrods appear correctly in the Read Data and Display Converted Data step of LSMW but when I try to to update the same data in the last step of LSMW(Run Batch Input Session) it does not update the data also the data that appears in these screens of VAP2 is not correct one i.e. it is not from the flat file that I am using.
I am running the LSMW in foreground and I am providing the partner number at each step of the LSMW.
Please suggest me what could have gone wrong.Because you did a hard-reset already, I recommend the Nokia Software Recovery Tool because that tool makes sure you get all software/firmware components again, even the demo-stuff from mass storage. By the way, if you do not get Nokia Belle Refresh (111.040…), please give us your Product Code (dial *#0000#) so we can look into that, and why. Otherwise, the Nokia Store on the phone does not work anymore …
cms145 wrote:
I'm unable to sign in to Nokia Suite as "could not connect to server".
There you go … -
CAN U TELL ME THE PROCEDURE TO UPLOAD DAT USING LSMW AND SCAT.MY EMAIL ID IS [email protected] .PLEASE SEND ME THE SOFT COPY IN THIS ID.
Debassish,
Check the below links
[http://www.sap-img.com/general/lsmw-steps-for-data-migration.htm]
[http://www.scmexpertonline.com/downloads/SCM_LSMW_StepsOnWeb.doc]
[With demo|http://www.****************/Tutorials/LSMW/LSMWMainPage.htm]
Reward points if useful
Regards,
SVP -
Logical filename and logical path in lsmw
Hi all,
I am doing a lsmw for purchasing info record . i created a logicalpath and assigned a physical path to that . i created a logical filename and assigned the logical path .but when i assign that to the lsmw it is throwing error as 'LOGICAL PATH DOES NOT POINT TO PHYSICAL DIRECTORY' .
can anybody provide a solution for that .
Thanks & regards
Magesh anandanhi ,
goto the tcode file then u find the relation between the logical and physical paths ...and their assignment..
hope it will helps u..
regards,
venkat. -
Hello Friends
I want to find if anybody can guide me on how to get all open sales order tables , i want to create a format and create a flat file for uplodading the file , for this what do i need and how do i do it.
Also for creating LSWM can i use the existing one which i can just Assign the New file to the existing one .
Regards.Dear Mehmood,
I want to find if anybody can guide me on how to get all open sales order tables
You want to extract all the open sales orders- which you can get from Table:VBUP key in overall document status in selection screen ( You can use VBUK also- but if there are certain sales orders in which some of the items are completed or few of them open, using VBUK - you will not get exact records)
Secondly, you can get the data by using Query also- in SQVI
design a query with VBAK / VBAP & VBUP
so that from VBAK you can give time period & sales area details
from VBAP - you can enter plant relevant details to filter certain records & item category as well
where as VBUP- filter wth the status.
once downloaded store in flat file.
Now Create LSMW object by using batch input recording method. after mapping the relevant fields,
prepare the flat file in such a - it suits to the upload file / recording file. then you can upload the already downloaded n stored open sales orders in flat file.
Hope this is what you are looking for.
Regards,
ReazuddinMD -
Hi,
I have created a LSMW for updating sales office in the Sales order by using Direct input method.
While specify files;I specified the file saved in the Desktop.While saving I get an error saying 'Logical path is not specified'.
Can anyone tell me why this error occurs and how to rectify this??
Thanks in Advance.
Thanks&Regards,
Sophia XavierHI
Place the cursor on "legacy data" and click on "create" option.
You will get one screen. There, you have input box called "FILE". By selecting drop box or pressing F4 on that, you will get all folders, files available at ur PC.
Search for you file, and double click on ur file. Next give all mandatory information in that screen. Finally press ok and save your "specify screens". It can be saved.
Reward if it is useful.
Thanks.
Siva kumar -
Creation of partner functions for customer master with LSMW
Hello,
I try to create partner functions together with a customer via Batch Input in LSMW.
Object: 0050, method: 0000, program name: RFBIDE00, program type: B.
I use the structure BKNVP (Customer master partner functions) to create a new partner and set values for the fields KTONR and PARVW.
When I start the batch input the fields are filled in correctly in a new dynpro. After the confirmation of these values the dynpro changes back to the partner functions sscreen, but the value for KTONR isn'n being transferred. So I get an error message.
Is it only possible to update partner functions with that BI or what is going wrong ?
Thanks in advance and regards
AlexHi Alex,
Could you specify what error message you are getting?
Thanks!
Rudra -
Error in Creation of Purchase Requisition through LSMW
Hi
I am trying to craete a PR upload prog through LSMW batch input method. In the Specify File option I am giving the TXT file destination.The TXT file is saved at my desktop. But while saving it is givving an error as "No logical path has been specified", Message no. /SAPDMC/LSMW_OBJ_060046
If anyone can help me out.Hi,
I would suggest to create a new one for this as file is placed on your desktop. But you can refer the standard one with which you will get the idea for creation:
Standard logical file name for this is: MM_PURCHASING_REQUISITIONS
In this file location is default in location /usr/sap/trans/data/mmrequisitions, instead of this you can give your converted data file name from step 7 Specify file for e.g PROJECT00_CUTOVER_MB1C_1.lsmw.conv
You can refer or use standard logical path LOCAL_TEMPORARY_FILES for this scene.
Hope this solves your problem.
Regards,
Brajvir
Maybe you are looking for
-
Does Adobe Care Anymore?
Now that Quark XPress is all but dead (yay!), and there's no other comparable page-layout program, does Adobe really care about their customers? I'm prompted to pose that question since the introduction of InDesign CC and CC2014. I've been using Adob
-
Can Aperture store projects on an external drive?
Is it possible to store my aperture projects on an external drive or must it reside on the Mac drive? I use an external USB drive to store all of my photos on and just cannot see using HD space for these photos. Is it possible?
-
Hi, I'm considering buying a macbook pro. I currently have windows xp laptop. Is it possible to have a msn messenger with hotmail accounts on Mac's???
-
Adobe 8 won't download pdf doc's in one user profile on multi user profile computer. However, if we switch users to a different profile reader 8 works fine. I cannot uninstall 8 on the bad profile, brings up a user profile error message. Why is this
-
Functional module on extracting character and numeric value
Dear All, I have one file which type is character. It contains alphanumeric values. (Ex. 500G & 7KG etc.) I want to extract numeric and characteristic values. There is no pre-defined no. of digits means actual value may have 5, 6 7.. digits. Ex. 1)