Create material using LSMW

Hello LSMW experts,
I want to upload material master from flat file with some Plant and Sales Organization views in single load. But I am not sure how to map the header data (basic data), sales organization and plant data to the tool. Do I need to have separate files for basic data, sales org, and plant?
Is there anybody can help me on this? Thanks in advance.
Zamri

hi,
Check this link for uploading material master in LSMW using RMDATIND direct input program..
http://help.sap.com/bp_blv1500/BL_US/documentation/LSMW_EN_US.doc
~~Guduri

Similar Messages

Creating Material using LSMW

Hi Guys!
I have a LSMW in which I have to upload 7 files, one per tab (MM01, CREATING MATERIALS), and I decided tu use a direct input, but how can I build the structures of my files? One of the tabs should be header (All the 7 files have 7 fields in common between them) and the rest as items? Should i have to create one structure per file?
Could you please help me on that?
Best Regards,
Gabriela.

> but how can I build the structures of my files? One of the tabs should be header (All the 7 files have 7 fields in common between them) and the rest as items?
First, I guess that each file has only one structure (it means all lines have exactly the same fields at the same positions).
When you create the source structures (one per file in your case), you can define a hierarchy (create one as the child of another one, by simply positioning your cursor). The relationship between structures (files) is made implicitly by using the same field names, that must be positioned at the beginning of the structure. Note: you can link 2 structures with several fields.
> Should i have to create one structure per file?
That's mandatory, otherwise you can't process the files!

I can create material using inbound Idoc of type MATMAS01, but not MATMAS05

I can create material using inbound Idoc of type MATMAS01 in WE19, but MATMAS05 failed. In fact I used same data ( different material number), and same inbound function, but got different result.
What is different between MATMAS01 and MATMAS05? Is there some configuation need for MATMAS05?
My system is ECC5.0. Thanks.

Hi, nagaraj
this is inbound IDoc, not outbound IDoc, so we can't assign Basic type in WE20, only can assign Message type.
In WE82, there are 5 records about Messagetype MATMAS:
     Message type   Basic type     Release
      MATMAS         MATMAS01        30A
      MATMAS         MATMAS02        30D
      MATMAS         MATMAS03        40A
      MATMAS         MATMAS04        46C
      MATMAS         MATMAS05        470
   I think it should be ok.
In WE57, there 2 records are exist:
   FM_name                 BasicType       MessageType
IDOC_INPUT_MATMAS01       MATMAS01         MATMAS
IDOC_INPUT_MATMAS01       MATMAS05         MATMAS
so I think all configurations should be ok.
Message was edited by:
        liu bin

Create material using bapi ' bapi_material_savedata'

Hi Experts,
i was tring to create material using bapi ' bapi_material_savedata' but the material is not updating in the table.
please find the code and suggest me if any modification
data: la_headdata type BAPIMATHEAD,
la_clientdata type BAPI_MARA,
la_CLIENTDATAX type BAPI_MARAX,
la_return type BAPIRET2.
data: i_materialdescription type table of BAPI_MAKT,
wa_materialdescription like line of i_materialdescription.
*la_headdata-MATERIAL = int_matnum-MATERIAL.
*LOOP AT int_matnum.
la_headdata-MATERIAL = int_matnum-MATERIAL.
write : int_matnum-material.
*ENDLOOP.
la_headdata-MATERIAL = '100000518'."int_matnum-MATERIAL.
la_headdata-IND_SECTOR = p_indsr.
la_headdata-MATL_TYPE = p_matype.
la_clientdata-BASE_UOM = 'FT3'.
la_clientdata-pur_valkey = ' '.
la_CLIENTDATAX-BASE_UOM = 'X'.
la_clientdata-MATL_GROUP = '01'.
la_CLIENTDATAX-MATL_GROUP = 'X'.
wa_materialdescription = 'TEST'.
append wa_materialdescription to i_materialdescription.
clear: wa_materialdescription.
CALL FUNCTION 'BAPI_MATERIAL_SAVEDATA'
EXPORTING
headdata = la_headdata
CLIENTDATA = la_clientdata
CLIENTDATAX = la_CLIENTDATAX
PLANTDATA =
PLANTDATAX =
FORECASTPARAMETERS =
FORECASTPARAMETERSX =
PLANNINGDATA =
PLANNINGDATAX =
STORAGELOCATIONDATA =
STORAGELOCATIONDATAX =
VALUATIONDATA =
VALUATIONDATAX =
WAREHOUSENUMBERDATA =
WAREHOUSENUMBERDATAX =
SALESDATA =
SALESDATAX =
STORAGETYPEDATA =
STORAGETYPEDATAX =
FLAG_ONLINE = ' '
FLAG_CAD_CALL = ' '
IMPORTING
RETURN = la_return
TABLES
MATERIALDESCRIPTION = i_materialdescription
UNITSOFMEASURE =
UNITSOFMEASUREX =
INTERNATIONALARTNOS =
MATERIALLONGTEXT =
TAXCLASSIFICATIONS =
RETURNMESSAGES =
PRTDATA =
PRTDATAX =
EXTENSIONIN =
EXTENSIONINX =
Please Help me
Regards,
Naresh

Hi all,
Now it is asking me for the other fields,
E ,
The field MARA-XCHPF/BAPI_MARA-BATCH_MGMT is defined as a required field; it does not contain an entry
i have passed this val as
la_clientdata-batch_mgmt = 'X'.
even though i am getting the same error.
can you help me to solve the issue.
Tthanks
Naresh
Edited by: naresh.k.dasari on Jan 4, 2011 10:36 AM

Basic Data Upload to MATERIAL Using LSMW is not working

HI All,
we are using LSMW    /SAPDMC/SAP_LSMW_IMPORT_TEXTS program to upload the basic text of the material, all steps are executed correctly and shows records are transfered correctly , but the in MM03 the text is not uploading..
EPROC_PILOT - MASTER - TEXT_UPLOAD Basic long text 1line
Field Mapping and Rule
        /SAPDMC/LTXTH                  Long Texts: Header
            Fields
                OBJECT                       Texts: Application Object
                                    Rule :   Constant
                                    Code:    /SAPDMC/LTXTH-OBJECT = 'MATERIAL'.
                NAME                         Name
                                    Source: LONGTEXT-NAME (Name)
                                    Rule :   Transfer (MOVE)
                                    Code:    /SAPDMC/LTXTH-NAME = LONGTEXT-NAME.
                ID                           Text ID
                                    Source: LONGTEXT-ID (Text ID)
                                    Rule :   Transfer (MOVE)
                                    Code:    /SAPDMC/LTXTH-ID = LONGTEXT-ID.
                SPRAS                        Language Key
                                    Source: LONGTEXT-SPRAS (Language Key)
                                    Rule :   Transfer (MOVE)
                                    Code:    /SAPDMC/LTXTH-SPRAS = LONGTEXT-SPRAS.
                                             * Caution: Source field is longer than target field
            /SAPDMC/LTXTL                  Long Texts: Row
            /SAPDMC/LTXTL                  Long Texts: Row
                Fields
                    TEXTFORMAT                   Tag column
                                        Rule :   Constant
                                        Code:    /SAPDMC/LTXTL-TEXTFORMAT = 'L'.
                    TEXTLINE                     Text Line
                                        Source: LONGTEXT-TEXTLINE (Text Line)
                                        Rule :   Transfer (MOVE)
                                        Code:    /SAPDMC/LTXTL-TEXTLINE = LONGTEXT-TEXTLINE.
and at last it displaying as follws
LSM Workbench: Convert Data For EPROC_PILOT, MASTER, TEXT_UPLOAD
2010/02/01 - 10:14:25
File Read:          EPROC_PILOT_MASTER_TEXT_UPLOAD.lsmw.read
File Written:       EPROC_PILOT_MASTER_TEXT_UPLOAD.lsmw.conv
Transactions Read:                    1
Records Read:                         1
Transactions Written:                 1
Records Written:                      2
can any one tell us what could be problem
Regards
Channappa Sajjanar

Hi , thanks for your reply,
i run the all the steps .
when i run the program it gives message as follows
Legacy System Migration Workbench
Project:                              EPROC_PILOT     eProcurement Pilot
Subproject:                           MASTER          Master data Upload / Change
Object:                               TEXT_UPLOAD     Basic long text 1line
File :                                EPROC_PILOT_MASTER_TEXT_UPLOAD.lsmw.conv
Long Texts in Total:                  1
Successfully Transferred Long Texts: 1
Non-Transferred Long Texts:           0

Error while creating material using MMS1

Hi All ,
I am trying to create material (Material type - DIEN) using MMS1.... but its giving error as "The field Component 1 is defined as a required field; it does not contain an entry" .
Pls suggest / advice on how to correct this error ....
Thanks ,
Mridul .

hi,
i believe some finctional consultant having knowledge in MM module can easily help u out on this.
reg,
nj

Create Material using MATMAS05 IDOC

Hi Gurus,
Please tell me what are the mandatory fields and tables for those fields to create a Material using MATMAS05 standard IDOC.

Hi,
Fields are never mandatory while sending the idocs. Its the segment which is mandatory.
If you see the definition of MATMAS05 idoc in transaction WE30 you will find E1MARAM and E1MAKTM, as a mandatory segment. It means that you can't send an Idoc without this segment. If you go in segment details than even if you populate a single field in the segment E1MARAM and E1MAKTM then you can send the idocs.
KR Jaideep,

Upload Of Vendor Create Data using LSMW

Hi,
I am trying to upload the vendor data for more than 1000 records from flat file structure to sap using LSMW (standard batch/ direct input) for XK01 transaction code. For uploading the house and street address i have created additional fields STR_SUPPL1 and STR_SUPPL2 in addition to STRAS. But in "Maintain Field Mapping and Conversion Rules" I am not able to locate the fields for mapping STR_SUPPL1 and STR_SUPPL2. Can any one please suggest me how to go about it. Thanks in advance.
Regards,
Sangram

Hi
As per your requirements when you r uploading the data in the "Maintain Field Mapping and Conversion Rules" it will display your field and some additional fields,and there you have to select for which field you r going to upload the data.
You have mentioned that you have created some two extra field as STR_SUPPL1 and STR_SUPPL2.Can you plz clarify me where you have declared those fields and how.
If you have done it in "Maintain Object Attributes" than it should display in the Field Mapping or you check it with " Maintain Source Fields" part,wheather you have enter all the fields appropriately or not.
I hope this will help you to solve your problem.
Thanks
Mrutyunjaya Tripathy

Classification of Material using LSMW

Hello
I using LSMW in order to create the characteristic. There are 4000 datas. This characteristis are going to be assigned to the class in order to have a classification of the materials.
Details:
In the 1rs step: I select object 0150 Characteristic and the program RCCTBI01
But I don't know if I have to use 0140 for class wich has the same program or 0130Classification and has this program RCCTB03.
But at the end when I created the batch imput the system generate the following message: Transaction not supported Message no. BL001
I have been trying with this transacctions: CT01, CT02, CT03, CT04, CL02, CL20N AND ALWAYS I OBTAIN THE SAME MESSAGE.
THANK YOU VERY MUCH FOR YOUR HELP

I never used batch input for classification, I usually do it with IDOC method.
In any case you have to create 3 objects.
One for the class
once for the characteristics
and then one for the classification.
regarding Batch Input, there is an OSS note 213120
As of Release 4.6A, the transactions of the class system are no longer suited for batch input.
If you have batch inputs from previous releases, you can continue using these since the old transactions still exist.
Where possible, use BAPIs or Direct Input instead of batch input. The old transactions will be eliminated in one of the future releases, so that the batch inputs will have to be converted anyway.
If you still want to use your own batch inputs, use the old transaction codes (such as CT01/02/03). If this should not work, use the alternatives mentioned above.

Create Material- Using authority by material type

Hi Experts
I want to set authority for user to create material by using material type. User will create only those material in which they are assigned in specific material type.
Please help me to solve this problem.

Hi,
You can proceed in the following way regarding this issue
1] In OMS2, maintain the Authorization Group for a particular Material Type
2] Maintain this Authorization Group in the activities of MM01 T-code with the help of Basis
3] This will ensure that authorized user only can create material master for that material type
Regards,
Amol

Problem while Creating BOM using LSMW Direct Input

Hi all ,
I am trying to create the BOM Using LSMW Direct Input Method .
I am getting problem at step 9 that is Read Data.
It is able to read the values from header and item files .
but it is not able to write , so the Written is 0 always .
I put the field names first in the flat file and correcponding values below it with tab delimited.
Please let me know where the Problem would be.... I am trying this from long time ..
Regards ,
Raj

hi ,
Yes i am specify files i am attaching 2 files .
ones is header and the other is line item data .
my strucure is :
Hi ,
I am still getting problem while for writing the records after reading the data .....
my header structure :
STYPE
MATNR
WERKS
SELAL
STLAN
DATUV
ZTEXT
my item structure :
STYPE
MATNR
WERKS
SELAL
POSTP
MENGE
my header data :
STYPE     MATNR     WERKS     SELAL     STLAN     DATUV     ZTEXT
1     388     0110     20     1     06.01.2009     SAMPLE ZTEXT
my item data :
STYPE     MATNR1     WERKS     SELAL     POSTP     MENGE
1     388     0110     20     N     1234
1     382     0110     20     N     12345
Above text files are delimited by tabulator.
Please guide me . The files are reading but unable to write .....
Regards,
Raj

How to create material using BAPI Methods?

hi,
how to create material master dat using BAPI?
could u guide me
i will be waiting for reply.
REGARDS
ESWAR.

Hi eswar,
Try this code to create gods mmovement...
DATA: GOODSMVT_HEADER LIKE BAPI2017_GM_HEAD_01,
      " Material Document Header Data
      GOODSMVT_CODE LIKE BAPI2017_GM_CODE,
      " Assign code to transaction for BAPI goods movement
      MATERIALDOCUMENT LIKE BAPI2017_GM_HEAD_RET-MAT_DOC,
      " Number of Material Document
      GOODSMVT_ITEM LIKE BAPI2017_GM_ITEM_CREATE OCCURS 0 WITH HEADER
      LINE,
      " Create Material Document Item
      RETURN LIKE BAPIRET2 OCCURS 0 WITH HEADER LINE
      " Return table for messages
*Fill values in header
GOODSMVT_HEADER-PSTNG_DATE = '20030825'.
GOODSMVT_HEADER-DOC_DATE = '20030802'.
*Fill GOODSMVT_CODE
GOODSMVT_CODE-GM_CODE = '05' .
*Fill Item Table
GOODSMVT_ITEM-MATERIAL = '100-100'.
GOODSMVT_ITEM-PLANT = '1000'.
GOODSMVT_ITEM-STGE_LOC = '0001'.
GOODSMVT_ITEM-MOVE_TYPE = '501'.
GOODSMVT_ITEM-ENTRY_QNT = '50'.
GOODSMVT_ITEM-ITEM_TEXT = 'Test Sanket'.
*GOODSMVT_ITEM-COSTCENTER = '1000'.
APPEND GOODSMVT_ITEM.
*Create Good's movement
CALL FUNCTION 'BAPI_GOODSMVT_CREATE'
EXPORTING
    GOODSMVT_HEADER = GOODSMVT_HEADER
    GOODSMVT_CODE    = GOODSMVT_CODE
IMPORTING
    MATERIALDOCUMENT = MATERIALDOCUMENT
TABLES
    GOODSMVT_ITEM    = GOODSMVT_ITEM
    RETURN           = RETURN.
*Commit BAPI
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
    WAIT = 'X'.
*Display Goods movement number
FORMAT COLOR 6 INVERSE ON.
READ TABLE RETURN WITH KEY TYPE = 'E'.
IF SY-SUBRC = 0.
WRITE: /,'ERROR! Goods movement not created'.
ELSE.
WRITE: /,'Goods movent number',MATERIALDOCUMENT COLOR 5,
           'posted for material',GOODSMVT_ITEM-MATERIAL.
ENDIF.
FORMAT COLOR OFF INVERSE OFF.
try this on report program and create a goods movement.
Sanket.

Create material using bapi_material_savedata

Hi.
I'm having prob with creation of material using bapi_material_savedata. When creating new material we use internal numbering so I use first bapi_material_getintnumber'. the number from that bapi is what i used in bapi_material_savedata. However, I getting an error that says 'matnr <from bapi>does not exists', why is this so? do i need to put the commit after the bapi_material_getintnumber and before calling the bapi_material_savedata?
Please help.
thnx.

hi
good
go through this example and use accordingly
REPORT ZBAPIMM01 LINE-SIZE 255 NO STANDARD PAGE HEADING
                 LINE-COUNT 065(001).
TABLES: T001L, "Storage Locations
        MARA, "General Material Data
        MAKT, "Material Descriptions
        MBEW, "Material Valuation
        MARC. "Plant Data for Material
DATA: BAPI_HEAD   LIKE BAPIMATHEAD,
      BAPI_MAKT   LIKE BAPI_MAKT,    "Material Description
      BAPI_MARA1 LIKE BAPI_MARA,    "Client Data
      BAPI_MARAX LIKE BAPI_MARAX,
      BAPI_MARC1 LIKE BAPI_MARC,    "Plant View
      BAPI_MARCX LIKE BAPI_MARCX,
      BAPI_MBEW1 LIKE BAPI_MBEW,    "Accounting View
      BAPI_MBEWX LIKE BAPI_MBEWX,
      BAPI_RETURN LIKE BAPIRET2.
DATA: BEGIN OF INT_MAKT OCCURS 100.
        INCLUDE STRUCTURE BAPI_MAKT.
DATA: END OF INT_MAKT.
DATA: BEGIN OF INT_MAT OCCURS 100,
         WERKS(4),     "Plant
         MTART(4),     "Material type
         MATNR(18),    "Material number
         MATKL(9) ,    "Material group
         MBRSH(1),     "Industry sector
         MEINS(3),     "Base unit of measure
         GEWEI(3),     "Weight Unit
         SPART(2),     "Division
         EKGRP(3),     "Purchasing group
         VPRSV(1),     "Price control indicator
         STPRS(12),    "Standard price
         PEINH(3),     "Price unit
         SPRAS(2),     "Language key
         MAKTX(40),     "Material description
       END OF INT_MAT.
SELECT-OPTIONS:
            PLANT    FOR MARC-WERKS OBLIGATORY MEMORY ID PLT,
            MATERIAL FOR MARA-MATNR MEMORY ID MAT,
            MATLTYPE FOR MARA-MTART MEMORY ID MTY,
            DIVISION FOR MARA-SPART MEMORY ID DIV.
PARAMETERS: F_FILE LIKE RLGRAP-FILENAME
             DEFAULT 'C:\DATA\ZMATERIAL.XLS' MEMORY ID F_FILE,
             GETDATA AS CHECKBOX, "Tick to download materials data to local harddisk
             UPDDATA AS CHECKBOX. "Tick to update date to Materials Master
IF GETDATA = 'X'.
   PERFORM DOWNLOAD_DATA.
   PERFORM DOWNLOAD_FILE.
ENDIF.
IF UPDDATA = 'X'.
   PERFORM UPLOAD_FILE.
   PERFORM UPDATE_MM.
ENDIF.
FORM DOWNLOAD_DATA.
SELECT * FROM MARC WHERE LVORM EQ ' '
                      AND WERKS IN PLANT
                      AND MATNR IN MATERIAL.
    CLEAR MARA.
    SELECT SINGLE * FROM MARA WHERE MATNR = MARC-MATNR.
    CHECK MATLTYPE.
    CHECK DIVISION.
    CLEAR MBEW.
    SELECT SINGLE * FROM MBEW WHERE MATNR = MARC-MATNR
                                AND BWKEY = MARC-WERKS.
    CLEAR MAKT.
    SELECT SINGLE * FROM MAKT WHERE SPRAS = 'EN'
                                AND MATNR = MARC-MATNR.
    WRITE:/ MARC-WERKS,    "Plant
            MARA-MTART,    "Material type
            MARA-MATNR,    "Material number
            MARA-MATKL,    "Material group
            MARA-MBRSH,    "Industry sector
            MARA-MEINS,    "Base unit of measure
            MARA-GEWEI,    "Weight Unit
            MARA-SPART,    "Division
            MARC-EKGRP,    "Purchasing group
            MBEW-VPRSV,    "Price control indicator
            MBEW-STPRS,    "Standard price
            MBEW-PEINH,    "Price unit
            MAKT-SPRAS,    "Language key
            MAKT-MAKTX.    "Material description
            INT_MAT-WERKS = MARC-WERKS.    "Plant
            INT_MAT-MTART = MARA-MTART.    "Material type
            INT_MAT-MATNR = MARA-MATNR.    "Material number
            INT_MAT-MATKL = MARA-MATKL.    "Material group
            INT_MAT-MBRSH = MARA-MBRSH.    "Industry sector
            INT_MAT-MEINS = MARA-MEINS.    "Base unit of measure
            INT_MAT-GEWEI = MARA-GEWEI.    "Weight Unit
            INT_MAT-SPART = MARA-SPART.    "Division
            INT_MAT-EKGRP = MARC-EKGRP.    "Purchasing group
            INT_MAT-VPRSV = MBEW-VPRSV.    "Price control indicator
            INT_MAT-STPRS = MBEW-STPRS.    "Standard price
            INT_MAT-PEINH = MBEW-PEINH.    "Price unit
            INT_MAT-SPRAS = MAKT-SPRAS.    "Language key
            INT_MAT-MAKTX = MAKT-MAKTX.    "Material description
            APPEND INT_MAT.
            CLEAR INT_MAT.
ENDSELECT.
ENDFORM.
FORM DOWNLOAD_FILE.
call function 'WS_DOWNLOAD'
EXPORTING
    FILENAME                      = F_FILE
    FILETYPE                      = 'DAT'
FILETYPE                      = 'WK1'
tables
    data_tab                      = INT_MAT
EXCEPTIONS
    FILE_OPEN_ERROR               = 1
    FILE_WRITE_ERROR              = 2
    INVALID_FILESIZE              = 3
    INVALID_TYPE                  = 4
    NO_BATCH                      = 5
    UNKNOWN_ERROR                 = 6
    INVALID_TABLE_WIDTH           = 7
    GUI_REFUSE_FILETRANSFER       = 8
    CUSTOMER_ERROR                = 9
    OTHERS                        = 10.
IF SY-SUBRC = 0.
   FORMAT COLOR COL_GROUP.
   WRITE:/ 'Data Download Successfully to your local harddisk'.
   SKIP.
ENDIF.
ENDFORM.
FORM UPLOAD_FILE.
call function 'WS_UPLOAD'
EXPORTING
    FILENAME                      = F_FILE
    FILETYPE                      = 'DAT'
FILETYPE                      = 'WK1'
tables
    data_tab                      = INT_MAT
EXCEPTIONS
    FILE_OPEN_ERROR               = 1
    FILE_WRITE_ERROR              = 2
    INVALID_FILESIZE              = 3
    INVALID_TYPE                  = 4
    NO_BATCH                      = 5
    UNKNOWN_ERROR                 = 6
    INVALID_TABLE_WIDTH           = 7
    GUI_REFUSE_FILETRANSFER       = 8
    CUSTOMER_ERROR                = 9
    OTHERS                        = 10.
IF SY-SUBRC = 0.
   FORMAT COLOR COL_GROUP.
   WRITE:/ 'Data Upload Successfully from your local harddisk'.
   SKIP.
ENDIF.
ENDFORM.
FORM UPDATE_MM.
LOOP AT INT_MAT.
Header
    BAPI_HEAD-MATERIAL        = INT_MAT-MATNR.
    BAPI_HEAD-IND_SECTOR      = INT_MAT-MBRSH.
    BAPI_HEAD-MATL_TYPE       = INT_MAT-MTART.
    BAPI_HEAD-BASIC_VIEW      = 'X'.
    BAPI_HEAD-PURCHASE_VIEW   = 'X'.
    BAPI_HEAD-ACCOUNT_VIEW    = 'X'.
Material Description
    REFRESH INT_MAKT.
    INT_MAKT-LANGU           = INT_MAT-SPRAS.
    INT_MAKT-MATL_DESC       = INT_MAT-MAKTX.
    APPEND INT_MAKT.
Client Data - Basic
    BAPI_MARA1-MATL_GROUP     = INT_MAT-MATKL.
    BAPI_MARA1-BASE_UOM       = INT_MAT-MEINS.
    BAPI_MARA1-UNIT_OF_WT     = INT_MAT-GEWEI.
    BAPI_MARA1-DIVISION       = INT_MAT-SPART.
    BAPI_MARAX-MATL_GROUP = 'X'.
    BAPI_MARAX-BASE_UOM   = 'X'.
    BAPI_MARAX-UNIT_OF_WT = 'X'.
    BAPI_MARAX-DIVISION   = 'X'.
Plant - Purchasing
    BAPI_MARC1-PLANT      = INT_MAT-WERKS.
    BAPI_MARC1-PUR_GROUP = INT_MAT-EKGRP.
    BAPI_MARCX-PLANT      = INT_MAT-WERKS.
    BAPI_MARCX-PUR_GROUP = 'X'.
Accounting
    BAPI_MBEW1-VAL_AREA   = INT_MAT-WERKS.
    BAPI_MBEW1-PRICE_CTRL = INT_MAT-VPRSV.
    BAPI_MBEW1-STD_PRICE = INT_MAT-STPRS.
    BAPI_MBEW1-PRICE_UNIT = INT_MAT-PEINH.
    BAPI_MBEWX-VAL_AREA   = INT_MAT-WERKS.
    BAPI_MBEWX-PRICE_CTRL = 'X'.
    BAPI_MBEWX-STD_PRICE = 'X'.
    BAPI_MBEWX-PRICE_UNIT = 'X'.
    WRITE:/ BAPI_HEAD, BAPI_MARC1.
    call function 'BAPI_MATERIAL_SAVEDATA'
      exporting
        HEADDATA                   = BAPI_HEAD
        CLIENTDATA                 = BAPI_MARA1
        CLIENTDATAX                = BAPI_MARAX
        PLANTDATA                  = BAPI_MARC1
        PLANTDATAX                 = BAPI_MARCX
      FORECASTPARAMETERS         =
      FORECASTPARAMETERSX        =
      PLANNINGDATA               =
      PLANNINGDATAX              =
      STORAGELOCATIONDATA        =
      STORAGELOCATIONDATAX       =
        VALUATIONDATA              = BAPI_MBEW1
        VALUATIONDATAX             = BAPI_MBEWX
      WAREHOUSENUMBERDATA        =
      WAREHOUSENUMBERDATAX       =
      SALESDATA                  = BAPI_MVKE1
      SALESDATAX                 = BAPI_MVKEX
      STORAGETYPEDATA            =
      STORAGETYPEDATAX           =
      IMPORTING
        RETURN                     = BAPI_RETURN
      TABLES
        MATERIALDESCRIPTION        = INT_MAKT
      UNITSOFMEASURE             =
      UNITSOFMEASUREX            =
      INTERNATIONALARTNOS        =
      MATERIALLONGTEXT           =
      TAXCLASSIFICATIONS         =
      RETURNMESSAGES             =
      PRTDATA                    =
      PRTDATAX                   =
      EXTENSIONIN                =
      EXTENSIONINX               =
IF BAPI_RETURN-TYPE = 'E'.
   WRITE:/ 'Error Message ', BAPI_RETURN.
ENDIF.
ENDLOOP.
ENDFORM.
*---End of Program
thanks
mrutyun^

Create material using reference material

Hi All,
I need to create a material using a reference material. I am using the BAPI_MATERIAL_SAVEREPLICA and passing the reference material in the PL_REF_MAT field. But this is not working fine. I have searcged the forums as well but couldn't find any solution.
Another solution that I am thinking to implement is to use BAPI_MATERIAL_GETALL and get the details of the reference material and then pass those details to the BAPI_MATERIAL_SAVEREPLICA. But as the structures for the two BAPI's are different I need to mapo each field one by one which is quite cumbersome as each view of the material has almost 100 or more fields.
Please suggest.
Thanks,
Manish

Hi Goutam,
You can use the BAPI BAPI_MATERIAL_SAVEDATA, which will create/update the material. You can pass the reference material in the filed BAPI_MARA-PL_REF_MAT. And you can pass reference material for all view like this.

Creating Material Using BAPI

Hi Friends,
I want to create a material using BAPI, can anyone give me some sample program or can any one give me links which earlier posted this problem.
Points for sure for sample program.
thanks and regards
Vijaya

hi
good
go through this REPORT z_bapi_salesorder_create.
Parameters
Sales document type
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text FOR FIELD p_auart.
PARAMETERS: p_auart TYPE auart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Sales organization
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text1 FOR FIELD p_vkorg.
PARAMETERS: p_vkorg TYPE vkorg OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Distribution channel
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text2 FOR FIELD p_vtweg.
PARAMETERS: p_vtweg TYPE vtweg OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Division.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text3 FOR FIELD p_spart.
PARAMETERS: p_spart TYPE spart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SKIP 1.
Sold-to
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text4 FOR FIELD p_sold.
PARAMETERS: p_sold TYPE kunnr OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Ship-to
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text5 FOR FIELD p_ship.
PARAMETERS: p_ship TYPE kunnr OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SKIP 1.
Material
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text6 FOR FIELD p_matnr.
PARAMETERS: p_matnr TYPE matnr   OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Quantity.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text7 FOR FIELD p_menge.
PARAMETERS: p_menge TYPE kwmeng OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Plant
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text9 FOR FIELD p_plant.
PARAMETERS: p_plant TYPE werks_d OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Data declarations.
DATA: v_vbeln            LIKE vbak-vbeln.
DATA: header             LIKE bapisdhead1.
DATA: headerx            LIKE bapisdhead1x.
DATA: item               LIKE bapisditem OCCURS 0 WITH HEADER LINE.
DATA: itemx              LIKE bapisditemx OCCURS 0 WITH HEADER LINE.
DATA: partner            LIKE bapipartnr OCCURS 0 WITH HEADER LINE.
DATA: return             LIKE bapiret2    OCCURS 0 WITH HEADER LINE.
DATA: lt_schedules_inx   TYPE STANDARD TABLE OF bapischdlx
                         WITH HEADER LINE.
DATA: lt_schedules_in    TYPE STANDARD TABLE OF bapischdl
                         WITH HEADER LINE.
Initialization.
INITIALIZATION.
v_text   = 'Order type'.
v_text1 = 'Sales Org'.
v_text2 = 'Distribution channel'.
v_text3 = 'Division'.
v_text4 = 'Sold-to'.
v_text5 = 'Ship-to'.
v_text6 = 'Material'.
v_text7 = 'Quantity'.
v_text9 = 'Plant'.
Start-of-selection.
START-OF-SELECTION.
Header data
Sales document type
header-doc_type = p_auart.
headerx-doc_type = 'X'.
Sales organization
header-sales_org = p_vkorg.
headerx-sales_org = 'X'.
Distribution channel
header-distr_chan = p_vtweg.
headerx-distr_chan = 'X'.
Division
header-division = p_spart.
headerx-division = 'X'.
headerx-updateflag = 'I'.
Partner data
Sold to
partner-partn_role = 'AG'.
partner-partn_numb = p_sold.
APPEND partner.
Ship to
partner-partn_role = 'WE'.
partner-partn_numb = p_ship.
APPEND partner.
ITEM DATA
itemx-updateflag = 'I'.
Line item number.
item-itm_number = '000010'.
itemx-itm_number = 'X'.
Material
item-material = p_matnr.
itemx-material = 'X'.
Plant
item-plant    = p_plant.
itemx-plant   = 'X'.
Quantity
item-target_qty = p_menge.
itemx-target_qty = 'X'.
APPEND item.
APPEND itemx.
Fill schedule lines
lt_schedules_in-itm_number = '000010'.
lt_schedules_in-sched_line = '0001'.
lt_schedules_in-req_qty    = p_menge.
APPEND lt_schedules_in.
Fill schedule line flags
lt_schedules_inx-itm_number = '000010'.
lt_schedules_inx-sched_line = '0001'.
lt_schedules_inx-updateflag = 'X'.
lt_schedules_inx-req_qty     = 'X'.
APPEND lt_schedules_inx.
Call the BAPI to create the sales order.
CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
       EXPORTING
            sales_header_in     = header
            sales_header_inx    = headerx
       IMPORTING
            salesdocument_ex    = v_vbeln
       TABLES
            return              = return
            sales_items_in      = item
            sales_items_inx     = itemx
            sales_schedules_in = lt_schedules_in
            sales_schedules_inx = lt_schedules_inx
            sales_partners      = partner.
Check the return table.
LOOP AT return WHERE type = 'E' OR type = 'A'.
    EXIT.
ENDLOOP.
IF sy-subrc = 0.
    WRITE: / 'Error in creating document'.
ELSE.
Commit the work.
    COMMIT WORK AND WAIT.
    WRITE: / 'Document ', v_vbeln, ' created'.
ENDIF.
thanks
mrutyun^

Create material using LSMW

Similar Messages

Maybe you are looking for