LSMW for Workcenter, BOM & Routings

Hello people,
I am new to LSMW. We are on ECC 6.0 & all master data is in Plant X, now we want all master data in  plant Y. Same plant but we are creating virtual plant. So all master data will be as it is. 
I need to copy existing Workcenter, Routing, BOMs from Plant X to Y.
for example If i do manually, CR01 - copy with reference..it works
1> should i go with Batch input recording and record copy with reference for LSMW?
2> or Standard SAP program for LSMW?
Can you please tell me the detail process... It would be great help!
Thanks

Hello,
Please look into the below link for more details on LSMW:
http://help.sap.com/saphelp_erp60_sp/helpdata/en/87/f3ae63e68111d1b3ff006094b944c8/frameset.htm
Also for BOM transfer there is already thread:
BOM Uploading through LSMW
Hope the information is useful
Regards

Similar Messages

  • LSMW for Equipment BOM

    Hi,
    I have 100 Equipments
    Some equipment have 5 BOM items, Some have 3 BOM items. It varies
    How i should create LSMW - Recording Method for this?
    I need to create two LSMWs ?
    Thnks

    hi Alagasen
    why don't you use standard object "create material BOM",change the transaction code from CS01 to IB01
    and do the mapping and upload
    regards
    Seenu

  • LSMW for equipment bom kde

    Can someone please specify the steps required to create an equipment bom lsmw

    hi Alagasen
    why don't you use standard object "create material BOM",change the transaction code from CS01 to IB01
    and do the mapping and upload
    regards
    Seenu

  • LSMW Batch Input Recording for Create BOM

    Dear All,
    I want to do LSMW for Creating BOM using Batch Input Recording,
    I know that i have to make 2 time Recording, first for the BOM Header and second for the BOM item
    For the BOM header i have done it, but for the BOM item i got some trouble with the item number (POSNR),
    when i run the LSMW, for the first item (item 0010) was success, but for the item 0020, it can't work and i got error
    message " NO BATCH INPUT FOR SAPLCSDI 0150"
    How is the recording step by step for BOM Item so the Item number can increase well?
    Very need your help,
    Regards,
    Marufat

    Hello Santosh,
    Thanks for the reply,
    I already check in SM35 where i also thought that the main problem is about adding the new item number,
    but when i tried to do repeat recording, i can not find any entry for adding the line item, so the line item after 0010 cannot be input
    Is there any solution?
    Regards,
    Marufat

  • Using ECN for creating Bom

    Hi Friends
    We usually use ECN for making any changes to Bom or Routing.  Any idea whether change number could also be used for creating Boms, Routings? Or  rather, when we do not put an ecn number while creating Bom, system should give an hard stop.
    thanks and regards
    L.Ramesh

    Hi Mr.Ramesh,
    As u asked,ECN can be made as a mandatory field while creating & changing a material,BOM,Routing.
    <b>1.For material,ECN can be made as mandatory by using a field exit.For Field exit,you can check in SE37.
    2.For BOM,Check in SPRO-Prod-Basic Data-BOM-Control Data for BOM-Define modification parameters(OS27).Also Check in OS25,for more settings.
    Check whether there's a tick mark in the check box for EC Management Active.
    3.For routing,Check in OP5A,Prod-Basic Data-Rotuing-Control Data-Define Field Selection.</b>
    I hope this will be helping you.
    If useful reward your points.
    Thanks & Regards
    Mangal

  • Lsmw for BOM and Routig

    Hi. I am new to this lsmw stuff. i have to  upload my boms and routings.i am thinking of doing lsmw for that.can u please guide me . how to do that, which is the best way to do that. can i use recording for uploading  the bill of materials and routing.
    can some one send me a template for uploading boms and routings.

    Dear,
    Please refer this link,
    [LSMW|lsmw for bom component]
    Regards,
    R.Brahmankar

  • LSMW FOR BOM CREATING.

    Hi Guys,
    I have a requirement where i create lsmw for bom upload using batch input. I m trying to create only one source structure and source fields assigned to this source structure but when finally im executing it its creating the first line item correctly but for all the second line items onwards its saying that Alternative already exists... My functional guy says that its creating just the first component in the bom and for the second component its trying to create another bom...and while its checking for the header which is already created its giving us error..
    I dont know how to handle this.....guys its a little urgent....plz help me out.
    here is a snap shot of the errors..
    10:25:44     Session BOM-CREATE is being processed by user KALVALV in mode N on server psdux07                              0                                                           0     S     00     300
    10:25:44     Creating BOM for material 10000240     CS01     1     SAPLCSDI     0140     7     S     29     030
    10:25:45     Transaction was processed successfully     CS01     1                                                           0     S     00     355
    10:25:45     Alternative 1 already exists     CS01     2     SAPLCSDI     0100     1     E     29     003
    10:25:45     Transaction error     CS01     2                                                           0     S     00     357
    10:25:45     Creating BOM for material 10000346     CS01     3     SAPLCSDI     0140     7     S     29     030
    10:25:45     Transaction was processed successfully     CS01     3                                                           0     S     00     355
    10:25:45     Alternative 1 already exists     CS01     4     SAPLCSDI     0100     1     E     29     003
    10:25:45     Transaction error     CS01     4                                                           0     S     00     357
    10:25:45     Creating BOM for material 10000347     CS01     5     SAPLCSDI     0140     7     S     29     030
    10:25:46     Transaction was processed successfully     CS01     5                                                           0     S     00     355
    10:25:46     Alternative 1 already exists     CS01     6     SAPLCSDI     0100     1     E     29     003
    10:25:46     Transaction error     CS01     6                                                           0     S     00     357
    10:25:46     Creating BOM for material 10000785     CS01     7     SAPLCSDI     0140     7     S     29     030
    10:25:46     Transaction was processed successfully     CS01     7                                                           0     S     00     355
    10:25:46     Alternative 1 already exists     CS01     8     SAPLCSDI     0100     1     E     29     003
    10:25:46     Transaction error     CS01     8                                                           0     S     00     357
    10:25:46     Creating BOM for material 10001252     CS01     9     SAPLCSDI     0140     7     S     29     030
    10:25:46     Transaction was processed successfully     CS01     9                                                           0     S     00     355

    Hi,
    You need to define the two structure header and detail. Both files should have the key fields:
    For example: Both file have Plant, Material Number, BOM Usage & Valid From.
    Then BGR00 and BICSK should be mapped to BOM_HEADER and BICSP to BOM_DETAIL structure.
    Then just do the mapping and should work.
    Hope this helps.
    Regards,
    Bharati Singh

  • [Help ] - LSMW for BOM

    Hello all,
    I am trying to create a LSMW to migrate BOMs.
    I am using object 0030 and method 0001.
    http://picasaweb.google.pt/adelmosilva/SAPScreenShots/photo#5225399426725436898
    Then, I have created 2 structures, one for the BOM header and one for the Item.
    Do I have to create 4 structures, one for each table?
    My text file has the following data:
    http://picasaweb.google.pt/adelmosilva/SAPScreenShots/photo#5225400798442244802
    Is this correct?
    Thanks in advance,
    Adelmo Silva

    Hello Silva,
    It depends on what fields you want to update in BOM. for my LSMW I do not use Object, methods. I just record whatever fields I need to populate.
    You can also choose to just record the fields that you need to populate under Batch input recording option.
    Yes, some times it takes more than 2 structures to load all the fields I need.
    Hope this helps.
    Thanks,
    Ram

  • Define own no ranges for Boms & Routings(task list type)

    hello all,
    I need to confirm if we can have seperate no ranges for materials Boms or routings on the same client?
    I think we can assign a new Bom no range but can't have different no ranges for different material boms on the same system. Moreover, using CS90 we can only define the internal no range for material boms?
    For task list we can define external no ranges but this gets assigned to the task list types. Is it possible to define our own task list type? I don't think so, but not a 100% sure.
    Pls can somebody confirm this for me.
    Many thanks.

    hi
    what you mentioned is correct there is no option of creating the task list types and also of youcan have external number ranges for BOMs check t-code SNUM with object STUE.
    -ashok

  • LSMW for BOM Object Dependencies

    Dear Sir,
    I can use LSMW to upload BOM component without object dependencies.
    If the BOM component have object dependencies, how to upload OD using LSMW.
    Who can help me !

    Hi all
    I have so much OD to be upload, how can I do that through LSMW ?
    No expert can help me ?
    Regards,

  • LSMW for equipment creation-Standard Batch/Direct Input

    Hi,
    We developed an LSMW with standard batch / direct input method for creating equipment masters.
    We used Object =0400 ( equipment ) and method = 0001 ( batch input)
    We maintained source structures and source fileds. In the source field , we maintained only those fields that we need from table IBIPEQUI but in the order given in this structure.
    Also we maintained filed mapping and field convertion rules for the above source fields.
    When we run LSMW step - Display converted data , we see that
    Transactions Read:                   1
    Records Read:                          1
    Transactions Written:                0
    Records Written:                       0
    Not sure what could have gone wrong?
    Please provide some clues to the following questions.
    1) Should the source structure be same as fields from stuc. IBIPEQUI and should it include all the fields in the source structure?
    2) Is field mapping required or not ?
    3) We are getting an error - transaction is not supported in direct input mode.
    Thanks in advance
    Rgds,
    Rajesh

    1. Source fields are( same as IBIPEQUI structure ; the tab delimited file matches with these fields)
    TCODE                          C(020)    Transaction Code
    RECORDNAME                     C(008)    Record name
    EQUNR                          C(018)    Equipment
    DATSL                          C(008)    Valid On
    EQTYP                          C(001)    Equipment category
    EQKTX                          C(040)    EQKTX
    BEGRU                          C(004)    Authorization Group
    EQART                          C(010)    Technical obj. type
    GROES                          C(018)    Size/dimensions
    INVNR                          C(025)    Inventory number
    BRGEW                          C(017)    Gross Weight
    GEWEI                          C(003)    Weight unit
    ELIEF                          C(010)    Vendor
    ANSDT                          C(008)
    ANSWT                          C(017)    Acquisition Value
    WAERS                          C(005)    Currency
    HERST                          C(030)    Manufacturer
    HERLD                          C(003)    Country of manufact.
    BAUJJ                          C(004)    Construction year
    BAUMM                          C(002)    Construction month
    TYPBZ                          C(020)    Model number
    SERGE                          C(030)    ManufSerialNumber
    MAPAR                          C(030)    ManufactPartNo.
    GERNR                          C(018)    Serial number
    GWLEN                          C(008)    Warranty end date
    KUND1                          C(010)    Customer
    KUND2                          C(010)    End customer
    KUND3                          C(010)    Operator
    SWERK                          C(004)    Maintenance plant
    STORT                          C(010)    Location
    MSGRP                          C(008)    MSGRP
    BEBER                          C(003)    Plant section
    ARBPL                          C(008)    Work center
    ABCKZ                          C(001)    ABC indicator
    EQFNR                          C(030)    Sort field
    BUKRS                          C(004)    Company Code
    ANLNR                          C(012)    Asset Number
    ANLUN                          C(004)    ANLUN
    GSBER                          C(004)    Business Area
    KOSTL                          C(010)    Cost Center
    PROID                          C(024)    PROID
    DAUFN                          C(012)    Standing order
    AUFNR                          C(012)    Order
    TIDNR                          C(025)    Technical IdentNo.
    SUBMT                          C(018)    Construction type
    HEQUI                          C(018)    Superord. Equipment
    HEQNR                          C(004)    Position
    EINZL                          C(001)    Single installation
    IWERK                          C(004)    Planning plant
    INGRP                          C(003)    Planner group
    GEWRK                          C(008)    Main work center
    WERGW                          C(004)    Plant for WorkCenter
    RBNR                           C(009)    Catalog profile
    TPLNR                          C(030)    Functional Location
    DISMANTLE                      C(001)    DismIndic.
    VKORG                          C(004)    Sales Organization
    VTWEG                          C(002)    Distribution Channel
    SPART                          C(002)    Division
    MATNR                          C(018)    Material
    SERNR                          C(018)    BOM explosion number
    WERK                           C(004)    WERK
    LAGER                          C(004)    LAGER
    CHARGE                         C(010)    CHARGE
    KUNDE                          C(010)
    KZKBL                          C(001)    Load records
    PLANV                          C(003)    PLANV
    FGRU1                          C(004)    FGRU1
    FGRU2                          C(004)    FGRU2
    STEUF                          C(004)    Control key
    STEUF_REF                      C(001)    STEUF_REF
    KTSCH                          C(007)    Standard text key
    KTSCH_REF                      C(001)    Std text referenced
    EWFORM                         C(006)    EWFORM
    EWFORM_REF                     C(001)    EWFORM_REF
    BZOFFB                         C(002)    Ref. date for start
    BZOFFB_REF                     C(001)    BZOFFB_REF
    OFFSTB                         C(007)    Offset to start
    EHOFFB                         C(003)    Unit
    OFFSTB_REF                     C(001)    OFFSTB_REF
    BZOFFE                         C(002)    Ref. date for finish
    BZOFFE_REF                     C(001)    BZOFFE_REF
    OFFSTE                         C(007)    Offset to finish
    EHOFFE                         C(003)    Unit
    OFFSTE_REF                     C(001)    OFFSTE_REF
    WARPL                          C(012)    Maintenance Plan
    IMRC_POINT                     C(012)    Measuring point
    INDAT                          C(008)    Inverse date
    INTIM                          C(006)    Processing time OC Workbe
    INBDT                          C(008)    Start-up date
    GWLDT                          C(008)    Guarantee
    AULDT                          C(008)    Delivery date
    LIZNR                          C(020)    License number
    MGANR                          C(020)    Master warranty
    REFMA                          C(018)    REFMA
    VKBUR                          C(004)    Sales Office
    VKGRP                          C(003)    Sales Group
    WARR_INBD                      C(001)    Inbound warranty
    WAGET                          C(001)    Warranty inheritance poss
    GAERB                          C(001)    Indicator: Pass on warran
    ACT_CHANGE_AA                  C(001)    ACT_CHANGE_AA
    STRNO                          C(040)    STRNO
    DATLWB                         C(008)    Date Last Goods Movmnt
    UII                            C(072)    UII
    IUID_TYPE                      C(010)    IUID Type
    UII_PLANT                      C(004)    Plant Responsible for UII
    2, source structure is assigned to target structure IBIPEQUI
    3. In the assign files step - all settings given above are correctly maintained.
    4. Field mapping
    TCODE                        Transaction Code
                        Rule :   Default Settings
                        Code:    IBIPEQUI-TCODE = 'IE01'.
    RECORDNAME                   IBIP: Name of the Data Transfer Record
                        Rule :   Default Settings
                        Code:    IBIPEQUI-RECORDNAME = 'IBIPEQUI'.
    EQUNR                        Equipment Number
                        Source:  ZIE01_002_SOURCE-EQUNR (Equipment)
                        Rule :   Transfer (MOVE)
                        Code:    if not ZIE01_002_SOURCE-EQUNR is initial.
                                   IBIPEQUI-EQUNR = ZIE01_002_SOURCE-EQUNR.
                                 endif.
    DATSL                        Date valid from
                        Source:  ZIE01_002_SOURCE-DATSL (Valid On)
                        Rule :   Transfer (MOVE)
                        Code:    if not ZIE01_002_SOURCE-DATSL is initial.
                                   IBIPEQUI-DATSL = ZIE01_002_SOURCE-DATSL.
                                 endif.
    EQTYP                        Equipment category
                        Source:  ZIE01_002_SOURCE-EQTYP (Equipment category)
                        Rule :   Transfer (MOVE)
                        Code:    if not ZIE01_002_SOURCE-EQTYP is initial.
                                   IBIPEQUI-EQTYP = ZIE01_002_SOURCE-EQTYP.
                                 endif
    When I read data with 1 record uploaded ( in the assign fields step , I did not choose "fields names at start of file" and also saved the file with tab delimited text format without field names), it shows as
    Transactions Read:                    2
    Records Read:                         2
    Transactions Written:                 2
    Records Written:                      2
    I uploaded only one record but it reads as 2 records and can not figure out why 2 records?
    Also when I checked display converted data , it shows 2 records .
    First record shows
    TCODE         Transaction Code                                             IE01
    RECORDNAME    IBIP: Name of the Data Transfer Record                       IBIPEQUI
    EQUNR         Equipment Number
    DATSL         Date valid from                                              05072010
    EQTYP         Equipment category                                           H
    EQKTX         Description of technical object                              PNEUMATIC PIPE BENDER
    BEGRU         Technical object authorization group
    EQART         Type of Technical Object                                     MECH-PRESS
    GROES         Size/dimension                                               1000X500X1500MM
    INVNR         Inventory number
    BRGEW         Gross Weight     : IBIP Character Structure                  50
    GEWEI         Weight Unit                                                  KG
    ELIEF         Vendor number
    ANSDT         Acquisition date
    ANSWT         Acquisition Value: IBIP Character Structure
    All the fields following this , are blank.
    2nd record shows
    TCODE         Transaction Code                                             IE01
    RECORDNAME    IBIP: Name of the Data Transfer Record                       IBIPEQUI
    EQUNR         Equipment Number                                             2009
    DATSL         Date valid from
    EQTYP         Equipment category                                           S
    EQKTX         Description of technical object                              1006324
    BEGRU         Technical object authorization group
    EQART         Type of Technical Object
    GROES         Size/dimension                                               20100406
    uploaded values are jumbled in 1st and 2nd record.
    Hope to receive your valuable ideas for finding out the reason and corrective action required.
    Rgds,
    Rajesh
    I
    Edited by: Rajesh63 on Jul 6, 2010 10:37 PM

  • Is there is any BAPI/FM/LSMW for BOMBOS Interface?

    I have a requirement to write a custom program to transfer BOM to BOS. This we can do through CG37, But I want to execute CG37 functionality through custom program. Could you please let me know if any one knows BAPI/FM/LSMW for this? Thanks in advance.
    You can send information to [email protected]
    Thanks
    Srini

    Dear Srinivass
    Kannan is right; but why can you not use Cg37? Here you have a user interface to populate the data; and if you drill down you can see how it is designed. But you need to pay attention. The BOMBOS interface will work (according to my knowledgeI) only if you "trigger" the generation of the worklist; and this is done "different" using a different function module; I believe at the "end" 'C1L0_BOM_TRIGGER_GEN_WL is used as well. BOMBOS is not discussed often here.
    E.g. check: http://www.se80.co.uk/sapfms/c/c1l0/c1l0_bom_trigger_gen_wl.htm
    consolut - C1L0_BOM_TRIGGER_GEN_WL - EHS: BOMBOS - Initialisierung; Erstellung BOM-Eintrag in ESTWL (sorry I found by hazard only german klink; but there is similar link in english)
    May be check as well: SAP EHS Management for Beginners; some references to threads regaridng BOMBOS are available there as well.
    C.B.

  • Lsmw for routing

    I am trying to upload routing using LSMW.
    which is the best way to use batch input or direct input.  I dont have a choice fof using badis or BDC
    can we upload routing without writing any code in LSMW.
    so i created three files
    header
    operation
    component allocation.
    what should be the link between these three files.I did lsmw for BOM. there i ve used material number as link. bou i didnt find material number in routing lsmw. so what should be the reference.
    can we take group counter number as reference.
    can some one provide me the source file structures for this LSMW for routing.
    thanks.

    Hi,
    You can use the standard LSMW for routing. As you mentioned first you upload the header and take the group no. as reference and upload the operation. and the components will be automatically assigned to the routing with the first operation.
    Thanks and Regards,
    Satish

  • Creating an LSMW for routing

    Hi
    I have managed to create a LSMW model, that wil create (CA01) a routing.
    My problem is that components (from the BOM) is not assigned to operations.
    When I display converted data, just before I create a batch input session, I can can see selected components is assigned to an operation.
    When I use transaction CA03 afterwards, behind the TAB " CompAlloc" there is no materials that has been assigned to operations. 
    Has anyone any experience on this issue?

    Dear,
    As said by Bala,get the help from ABAP programmer and go for a BDC for
    creation of routing.
    I have not worked or used LSMW for routing,so could not give a reply for your
    question.
    Regards
    Mangal

  • Fields for Super BOM, Work Center & Super Routing for Variant Config

    hi! gurus,
    Please can you give me mandatory fields & values for Super BOM, Work Center & Super Routing for Variant Config
    thank you

    Hi,
    In the Super BOM you need to maintain the object dependencies.
    Workcenter fields are as usual for other production processes.
    Also you can use search option in the forum to view the threads posted in the past. There are many posts related to variant configuration.
    Regards,
    Senthilkumar

Maybe you are looking for