Lsmw configuration

dear sdn friends
could somebody please tell me how i can use a segment more than once???
we see a single segment for a idoc in lsmw 'Maintain Field Mapping and Conversion Rules' .
I  have to use a segment multiple times depending upon the products we have???
how is it possible Please help its a urgent?...
Thanks
pankaj

solved read SDN if any one have same question

Similar Messages

  • Issues with LSMW

    hi Group,
    I am facing issues while loading data into SAP they are as under:
    - I have created the LSMW recording and created the Session also but, I am not sure how to move this Project, Subproject into
      the Quality system?
      - if I create a Transport request, I am getting some warning message(eg., Application table is not to be meant for transporting)
        and until, we remove these warnings, Basis team will not move the object to Quality
      - if I use Importing/Exporting I have some authorization issues
    so I request you to give me inputs as to how to move the LSWM project+subproject to the Quality and which is the best option to do this movement?
    please provide inputs and help in going further in this issue.
    thanks for help in advance.
    Regards,
    Vishnu.

    These warnings are a known "problem" because the LSMW configuration tables /SAPDMC/... are flagged as application tables. You can tell your basis team that the rest of the world is ignoring these messages (in this particular case).
    Thomas

  • LSMW : Urgent SO - DI - Material Configuration Prob

    Hello all,
    [Direct Input Approach]
    In my quest for uploading Legacy system SO through LSMW . I have reached at the stage where I am able to create Sales Order successfully but only 1 problem is..
    Our client has customization done where by selecting a perticular value, the SO Item level table control shows few extra detail columns [extra charstics of material]. This is customized by Material Classification view.
    My LSMW script is creating Order Correctly but for each item it displays the Configuration Screen and I asks for manual intervation[say pressing F3].
    In my LSMW script if I programmatically supress this screen. Then those value doesn't apear in SO when we access it through VA02.
    has any one come accross this kind of prblem ? Please help me as this seems to be only hurdle in my SO upload.

    Hi!
    I think, you need two different alternatives:
    - You suppress the screen in LSMW -> no configuration data is filled -> later no configuration is available (columns missing). Do this for materials without configuration data.
    - You handle the additional screen and fill (at least one) configuration data. Later view and changing (maybe adding the rest of values) should be possible.
    Sales orders with configuration would be better created by BAPI - but this would be hard work to change right now (and this BAPI is not easy to handle in case of configuration).
    Regards,
    Christian

  • Configuration id with PR  create LSMW

    Hello Experts,
    I am doing LSMW for Purchase requisition( Header and Item)  by using the standard Program:
    Object                0080  
    Method               0000
    Program Name   RM06BBI0
    Program Type     B   Batch Input
    But I noticed that no internal object number( CUOBJ ) is generated by using this method but if i try to create the PR header and item through the standard transaction: ME51N, the internal object number is generated.
    I require this internal object number as i need to upload the configuration ( characteristics ) of the material assigned to the PR Item.
    Please suggest .
    Thanks and Best Regards,
    Sahil

    Hi Sahil,
    Can you please let me know, how did you solve this, because I am also facing the same issue.
    Best Regards
    Manoj

  • Configuration acquisition value for data load LSMW

    Experts,
    We want to load data through batch input. The script works fine but we have a problem with storing the historic acquisition value in a foreign currency. We have 10 areas defined of which we are using for this company area 01, 02 and 32 (foreign currency value). What happens at loading is that the other areas are copying the value from area 01. I would like to know what the transaction is for blocking the system to copy value into the non used areas and just open are 01, 02 and 32 to enter data.
    Thanks,
    Glenn

    can you check below message types in LSMW IDOC method
    /SAPMP/LOIPRO                   Production Order with Configuration Data
    CNPMAS                          Configuration profile
    CONFIG                          Configuration for transceiver
    DWLOAD                          Download transceiver configuration
    UPLOAD                          Configuration transceiver for upload

  • Unable to Configure Sales Order using SALESORDER_CREATEFROMDAT2

    I am using the basic type SALESORDER_CREATEFROMDAT2 02 idoc, created via LSMW, in order to create sales orders.  Everything works fine, except for the fact that I cannot set configuration characteristics. The sales order is saved, but when i look at it the value of my characteristic is not set.  Can you help me please?  Currently I do not know how to generate an idoc of this basic type from an existing order.  Knowing how to do this would be a great help. 
    For my test data, I am only attempting to create one line item (line 10) and configure one characteristic.
    Below is a list of the segments being used.  I have provided the fields with code for those fields I believe are relevant.   I have attempted to process idocs with and without segment E1BPCUPRT.  I have also processed idocs with and without the fields E1BPSDITM1-CONFIG_ID, E1BPSDITM1-INST_ID and E1BPSDITM1-MAT_EXT.   When these three fields are populated, the order is created but the order line items are dropped.  When these three fields are not populated, the order lines created but the characteristic value is not passed to the line item. 
    Target Structures Used
      E1SALESORDER_CREATEFROMDAT2 - Header Segment
        E1BPSDHD1 - Communication Fields: Sales and Distribution Document Header
        E1BPSDHD1X - Checkbox Fields for Sales and Distribution Document Header
        E1BPSDITM - Communication Fields: Sales and Distribution Document Item
          E1BPSDITM1 - Communication Fields: Sales and Distribution Document Item
    E1BPSDITM1-CONFIG_ID
      Rule Type:  Constant
        E1BPSDITM1-CONFIG_ID = '000001'.
    E1BPSDITM1-INST_ID
      Rule Type:  Constant
        E1BPSDITM1-INST_ID = '00000001'.
    E1BPSDITM1-MAT_EXT
      Rule Type:  ABAP Code
            concatenate '0000000000000000000000' E1BPSDITM-MATERIAL into
         E1BPSDITM1-MAT_EXT.
        E1BPSDITMX - Communication Fields: Sales and Distribution Document Item
        E1BPPARNR - Communications Fields: SD Document Partner: WWW
        E1BPSCHDL - Communication Fields for Maintaining SD Doc. Schedule Lines
        E1BPSCHDLX - Checkbox List for Maintaining SD Document Schedule Line
        E1BPCOND - Communication Fields for Maintaining Conditions in the Order
        E1BPCONDX - Communication Fields for Maintaining Conditions in the Order
        E1BPCUCFG - CU: Configuration Data
    E1BPCUCFG-POSEX <=== ORDER_ITEM-POSNR
      Rule Type:  Transfer (MOVE)
        E1BPCUCFG-POSEX = ORDER_ITEM-POSNR.
    E1BPCUCFG-CONFIG_ID
      Rule Type:  Constant
        E1BPCUCFG-CONFIG_ID = '000001'.
    E1BPCUCFG-ROOT_ID
      Rule Type:  Constant
        E1BPCUCFG-ROOT_ID = '00000001'.
    E1BPCUCFG-COMPLETE
      Rule Type:  Constant
        E1BPCUCFG-COMPLETE = 'T'.
    E1BPCUCFG-CONSISTENT
      Rule Type:  Constant
        E1BPCUCFG-CONSISTENT = 'T'.
        E1BPCUINS - Instances of Several Configurations
    E1BPCUINS-CONFIG_ID
      Rule Type:  Constant
        E1BPCUINS-CONFIG_ID = '000001'.
    E1BPCUINS-INST_ID
      Rule Type:  Constant
        E1BPCUINS-INST_ID = '00000001'.
    E1BPCUINS-OBJ_TYPE
      Rule Type:  Constant
        E1BPCUINS-OBJ_TYPE = 'MARA'.
    E1BPCUINS-CLASS_TYPE
      Rule Type:  Constant
        E1BPCUINS-CLASS_TYPE = '300'.
    E1BPCUINS-OBJ_KEY
      Rule Type:  ABAP Code
        * Target Field: E1BPCUINS-OBJ_KEY Object key
        Select single SATNR from MARA into E1BPCUINS-OBJ_KEY
          where BISMT = ORDER_ITEM-BISMT.
    E1BPCUINS-QUANTITY <=== ORDER_ITEM-KWMENG
      Rule Type:  Transfer (MOVE)
        E1BPCUINS-QUANTITY = ORDER_ITEM-KWMENG.
        E1BPCUPRT - Part_of Entries of Several Configurations  (Have tried with and without this segment)
    E1BPCUPRT-CONFIG_ID
      Rule Type:  Constant
        E1BPCUPRT-CONFIG_ID = '000001'.
    E1BPCUPRT-PARENT_ID
      Rule Type:  Constant
        E1BPCUPRT-PARENT_ID = '00000001'.
    E1BPCUPRT-INST_ID
      Rule Type:  Constant
        E1BPCUPRT-INST_ID = '00000001'.
    E1BPCUPRT-PART_OF_NO
      Rule Type:  Constant
        E1BPCUPRT-PART_OF_NO = '0010'.
    E1BPCUPRT-OBJ_TYPE
      Rule Type:  Constant
        E1BPCUPRT-OBJ_TYPE = 'MARA'.
    E1BPCUPRT-CLASS_TYPE
      Rule Type:  Constant
        E1BPCUPRT-CLASS_TYPE = '300'.
    E1BPCUPRT-OBJ_KEY
      Rule Type:  ABAP Code
        E1BPCUPRT-OBJ_KEY = E1BPCUINS-OBJ_KEY.
        E1BPCUVAL - Characteristic Values of Several Configurations
    E1BPCUVAL-CONFIG_ID
      Rule Type:  Constant
        E1BPCUVAL-CONFIG_ID = '000001'.
    E1BPCUVAL-INST_ID
      Rule Type:  Constant
        E1BPCUVAL-INST_ID = '00000001'.
    E1BPCUVAL-CHARC
      Rule Type:  ABAP Code
        E1BPCUVAL-CHARC = 'PRG_METRIC'.
    E1BPCUVAL-VALUE <=== ORDER_ITEM-ATWRT8
      Rule Type:  Transfer (MOVE)
        E1BPCUVAL-VALUE = ORDER_ITEM-ATWRT8.
        E1BPCUREF - CU: Reference Order Item / Instance in Configuration
    E1BPCUREF-POSEX <=== ORDER_ITEM-POSNR
      Rule Type:  Transfer (MOVE)
        E1BPCUREF-POSEX = ORDER_ITEM-POSNR.
    E1BPCUREF-CONFIG_ID
      Rule Type:  Constant
        E1BPCUREF-CONFIG_ID = '000001'.
    E1BPCUREF-INST_ID
      Rule Type:  Constant
        E1BPCUREF-INST_ID = '00000001'.
        E1BPSDTEXT - Communication Fields: SD Texts

    Hi Paaavan
    You can set a break-point include "FV45PFAP_VBAP_BEARBEITEN_VORBE" that is called by both the SAP Standard and BAPI where the data is prepared and checked in the internal table XVBAP. Compare both SAP standard VA01 and your 'Z' program for what may be different in XVBAP.
    I think the problem my be with regards to the business_object number that is hardcoded in the standard function module. It has given me issues before and hence I tend to use the function module  SD_SALESDOCUMENT_CREATE to create sales documents with.
    Regards,
    Marius

  • Create a Sales Order with Reference to Contract using IDoc / LSMW  ( AFS )

    Hi Gurus,
    I need to crate a Sales Order with reference to a Contract. I need to upload Sales Orders with reference to contract via LSMW.
    So far, I've been able to create the Sales Order with ref to contract. But, the Sales Order Quantity is not getting deducted from the Original Qty in Referred Contract ( When try to create another Sales Order referring to the same Contract.) When a Sales Order is created manually, this is working fine.
    Please tell me if I've missed some parameter which stopping it create the link to exact schedule line ( Sizes level )
    The Details of the IDoc which is been created via LSMW are as follows;
    Message Type: ORDERS
    Basic Type     : /AFS/ORDERS05
    Process Code : ORDE / DELO
    ( Tried with both process codes.  But the Identification is the same for both: IDOC_INPUT_ORDERS )
    *_In Header;_
    Segment : E1EDK02  - IDoc: Document header reference data *
    Qualifier : '043' - Vendor Contract Number ( Tried with ' 005' - Customer Contract, but it's not working )
    Contract Order is mapped for field BELNR
    *_In Item;_
    Segment : E1EDP02  - IDoc: Document Item Reference Data *
    Qualifier : '043' - Vendor Contract Number ( Tried with ' 005' - Customer Contract, but it's not working )
    Contract Order is mapped to field BELNR
    Line Item of the Contract is mapped to field ZEILE
    I also tried passing the Schedule line of Contract in Segment :  E1J3P01 AFS IDoc: Doc.item general data
    to following fields;
    J_3AETENV
    J_3AVGETE
    /AFS/UETENR
    Still its not getting updated in the VBEP also..
    Please help me with regard to this. Points will be awarded for your valuable contribution.
    Thanks.

    Hi,
    This issue is been resolved.
    One of my friend helped me with resolving this issue..
    Once the below mentioned configurations were done on SPRO, the Sales Order was created with reference to Contract and the Qty was reflected when tried to create a new Order referring the same contract.;
    u2022     SPRO --> SD  -->Sales  --> Sales Documents  --> Sales Document Header  --> Define Sales Document Types  --> Field : Outline agreement message; from blank to u201CBu201D.
    u2022     SPRO  -->SD  -->Sales  --> Sales Documents  --> Sales Document Header  --> Maintain Sales Document Types for AFS  --> Field : Outline agreement message; from blank to u201CAu201D

  • How can we move LSMW from Development server to Production

    Hi
    pls give me idea on
    1) how we can test lsmw
    2) how we can move from  one server  to another server
    3) how we can do you it to use periodically
    4)What is use of radio buttons once and periodic in maintain attributes screen
    thanks

    1.  By running the actual conversion.  I dont understand the question.
    2.  Depends on how your server is configured.  If this is configured to move LSMW projects through transports, then you can create a transport and move it.  If not you can just export the project and import it into PRD.
    3.Run the program /SAPDMC/SAP_LSMW_INTERFACE
    4.Not sure what you are asking.
    Albert

  • LSMW file upload from presentation server

    Hi,
    We are using LSMW to create new Document info records and will need to upload/ attach multiple files to the DIR.
    everything is working except in the IDOC processing stage, it errors out -
    "Error while checking in and storing:
    otlta134a\pcm\test1.txt"
    Its is unable to upload file from network drive, it works successfully when the same file is uploaded from application server.
    I have worked in other LSMW projects and have successfully loaded files from network drive.
    Please let me know what configuration setup is required, is it the content server or the gateway server?
    Thanks for all your help.

    Sheetal,
    I think this is the problem due to the authorization....
    try to open the file from AL11........... if u r still getting the problem better to contact the basis guys...
    If it is the problem with the authorization... once u get this error open another session with SU53 tcode.. take the authorization object and give it to basis guys to allow the permissions to u...

  • LSMW Error while Transporting

    Hi All
    Hi All
    I have configured LSMW in Quality for which i have only 1 Project under which there are 13 sub Project & under each sub project there is only one Object . Totally there are 13 objects  .
    Now i want to transport all of them in to a production . so i been to T.code : LSMW then to menu path  Extras -> Generate Change Request   . After this i have created one Request . Now am getting a error as mentioned below in bold letters .
    The object R3TR TABU /SAPDMC/LSMCUST is client-specific.
    The client in which you are currently working is set as follows:
    You can make changes to client-specific objects, but these changes are not recorded. You cannot include these objects in a request and then release them.
    To solve this go through the below steps :
    Delete the object from the request.
    Change the setting for client-specific objects in this client (Transaction SM30, table T000).
    I went through the SM30 > Table T000 but it is not related to the transporting the LSMW .
    Can any one help me . how to solve this issue .
    Please let me know at the earliest .
    Thanks in Advance .

    Hi,
    just export projects on desk enough, again import another desired client.
    When you export all the sub projects select directly project, if don't wont deselect the sub projects only then under export rules export the project on desk with same name(system will provide you) txt file.
    same like import another client.. no need to any modifications..
    You can use directly.

  • Enter G/L account error while uploading open contracts using lsmw

    Hi Experts,
    I have a flat file for Open Contracts.While trying to upload using LSMW -BAPI method(BUS2014), it is throwing error as 'Enter G/L account' though G/L is present in the flat file.I have done with the mapping in the 5th step.
    Checked all the configuration settings of G/L.everything is fine. Not getting where is it going wrong.
    please help me out.

    I've tried regarding Helmut's advise and it works.
    10 points (if i was a thread owner)

  • Creation of material using BAPI in LSMW without using material no.

    Hi SAP Gurus,
    I have a requirement of creating materials using the BAPI in LSMW.
    I tried to create a material using the BAPI (Business Object - BUS1001006 , and method - SAVEDATA) which should be created internally, but it is asking the material number to be given externally and my configuration is setup to create the material number internally.
    Even I looked into the material type which is associated with the number range and everything looks good.
    Is there any solution to create the material by using BAPI in LSMW without passing the material no. externally ?
    Appreciate your help.
    Kalikonda.

    Hi,
    it looks like it's not possible to call this BAPI wihtout material number. Here is a quote from BAPI documentation.
    When creating material master data, you must transfer the material
    number, the material type, and the industry sector to the method. You
    must also enter a material description and its language.
    Cheers

  • Classification view creation via LSMW for Material master

    Hi,
    We are planning to have an LSMW for creation of material master along with classification view for configurable materials.
    Though we see a flag to indicate classification view  - XEIC1                        Indicator: take Classification view into account
    We do not see a structure where in we can pass all the characteristics and the corresponding values.
    Is this something possible only with BAPIs such as -> BAPI_OBJCL_CREATE after creation of other view for that material.
    Regards,
    HR

    Hi,
    Thanks for the response. This is helpful.
    However, we were intending to use a single LSMW for creation of all views of material master including classification view. Right now we are using Program RMDATIND as direct input method in LSMW.
    Please let me know if there is a way to use single LSMW for creation of all views of material master.
    Thanks
    HR
    Edited by: Hema Rao on Jan 8, 2009 7:58 AM

  • Reg:lsmw

    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 to upload Business Partner through IDOC

    Hello,
    I have requirement to upload Business partner  through IDOC. I am using below message type and IDOC type.
    1:- Message Type :- CRMXIF_PARTNER_SAVE_M
    2:- Basic Type :- CRMXIF_PARTNER_SAVE_M02
    Could you please tell me what configuration I need to do for this? Like creating partner profile, port etc
    Also I need to extend this IDOC segment to take care of my Z fields.
    After extending the IDOC segment do I need to write code in order to update this Z filed or it will be take care and also how to extend existing IDOC.
    If any one have has done this before then please share the logic.
    Kindly help.
    Regards
    Sachin

    Hi,
    Try LSMW with the IDOC method.
    Message type: BUPAFS_FS_CREATE_FRM_DATA2
    Basic type: BUPAFS_FS_CREATE_FRM_DATA201
    You will need to setting for IDOC: port, partner type, etc.
    Manish

Maybe you are looking for