Help me for material master upload by using Direct Input method

Hi All,
Can any one help me out for developing Material Master Upload program by using Direct Input Method where we are also submitting the report to upload the data in SAP Database.

Thanks in Advance!
Ramkumar.K

Hi Kumar,
Thanks! I am using submit statement in my program as well but its populating all the views like Sales Organization Data, Sales - General / Plant Data, Accounting, and all the other views except the Basic Data View.. Eventhough i have populated the corresponding fields of the same.
I am also using structure BGR00, BMM00, BMMH1 to upload the data
Can you please help me on this..

Regards,
Ramkumar.K

Similar Messages

What is the standard program for Material Master upload using LSMW

Dear All
I am trying to use the MM upload using DATMIG_INF4. I want to know what are the different standard projects that are used for Material master upload.

Hi Amol,
You can load the material master using direct input method in LSMW ,details of which are as follows:
Object               0020   Material master
Method               0000
Program name         RMDATIND
Program type         D   Direct input
Please revert back in case of any doubt.
Cheers
VJ

Using Direct input method(LSMW)Can I upload only 3 fields for MM01

Using Direct input method(LSMW)Can I upload only Matnr,mbrsh,mtart fields for MM01.Otherwise I have to give all the mandatory fields.?

Hello TJK,
LSMW will work in the same way as you create normal material master with the transactions, here you are giving the value through flat file and creating material master with program.
You can create only one view with LSMW but you need to give all mandatory field on that particular view, so if you have only these three field as mandatory then yes it is possible, if you have any more field mandatory addition to these fields then it will not work out, during the last step it will throw error saying "maintain the value for field XXX"
Hope this helps.
Regards
Arif Mansuri

LSMW for material master upload

Hi gurus
i have one problem while uploading material master with LSMW.
I have murged 2 company codes in one so while creating material master system is asking me tax classification data in sales view for 2 country sales org and distrubition channel. I am using sap std LSMW for material master creation.
system is giving me error as " tax classification data not maintained completely".
need your valuable help to solve this problem

Tax classification data is mandatory field in Sales view of MM01.
Check out you mapping for the tax classification fields. usually classification value is 0 OR 1.
You can first test the values in MM01 Sales View with the legacy data you have and this way you will able to find the mandatory fields also and can see the valid values for the fields.
Remember you may have more than one Tax Classification values depending on the country code.
For that you can add those many columns in legacy data file and map them.
Hope it helps.

Help reqd on Material Master uploading in LSMW by view steps....

Hi all....
Pls understand my requirement and post ur replies...i dont need the basic LSMW learning steps for MM,Vendor etc.,like that...
My problem is...im want to upload my material master datas by steps like 1st i want to uplaod the basic views 1&2 for all the material types in one shot...
next thing i want to load the other views like purchasing sales mrp plant qm accounting etc., in single shot......like screen to be extended formats....im mm01 or by mm02...
when i did....no problem i've faced upto MRP loading...but the next view like plan,QM,accounting is not coming when recording in RUN batch input session..it says..."the material has been already extended and no input was given for this screen"....
Hope u understand,my problem....
if u have answers...pls post me on urgent basis.....
thanks...
sankar

Create purchase requisition by LSMW

Validations for gl master uploading by using BAPI

Hi Gurus,
We are trying to Upload the GL Masters by using the BAPI Programme. So can any body tell me the validations for uploading the GL Masters. Its very urgent for me so please any body help me out in this regard.
Thanks in Advance
Regards,
Siva.

Hello
Check this out
regards
http://help.sap.com/saphelp_erp2005vp/helpdata/en/02/056c40de05587ee10000000a155106/frameset.htm

Upload sales text for material master using LSMW direct input method

Hello Experts,
I was trying to upload sales text for a material master using LSMW direct input method.
I followed the following steps for the same
Tab dlimited Text file format
MATNR LONGTEXT LINE
MATERIAL1 LONGTEXT FOR MATERIAL MATERIAL1 1
Step1 -> Maintain object attributes
Object -> 0001
Method-> 0001
Program name -> /SAPDMC/SAP_LSMW_IMPORT_TEXTS
Program type -> D
Step2 -> Maintain Source Structure
Source structure -> LONG_TEXT Source structure for long text
Step 3-> Maintain souce file
Source Fields
ZLONG_TEXT Source structure for long text
 MATNR C(018) MATNR
 LTEXT C(132) LTEXT
Step 4-> Maintain structure relationship
Structure Relations
/SAPDMC/LTXTH Long Texts: Header <<<< ZLONG_TEXT Source structure for long text
 Select Target Structure /SAPDMC/LTXTH .
/SAPDMC/LTXTL Long Texts: Row <<<< ZLONG_TEXT Source structure for long text
 Select Target Structure /SAPDMC/LTXTL .
Step 5-> Maintain Field mapping and conversion rules
Here i have assigned constan rules to couple of them like
/SAPDMC/LTXTH Long Texts: Header
Fields
 OBJECT Texts: Application Object
 Rule : Constant
 Code: /SAPDMC/LTXTH-OBJECT = 'MVKE'.
 NAME Name
 Source: ZLONG_TEXT-MATNR (MATNR)
 Rule : Transfer (MOVE)
 Code: /SAPDMC/LTXTH-NAME = ZLONG_TEXT-MATNR.
 ID Text ID
 Rule : Constant
 Code: /SAPDMC/LTXTH-ID = '0001'.
 SPRAS Language Key
 Rule : Constant
 Code: /SAPDMC/LTXTH-SPRAS = 'E'.
/SAPDMC/LTXTL Long Texts: Row
Fields
 TEXTFORMAT Tag column
 Rule : Constant
 Code: /SAPDMC/LTXTL-TEXTFORMAT = '/'.
 TEXTLINE Text Line
 Source: ZLONG_TEXT-LTEXT (LTEXT)
 Rule : Transfer (MOVE)
 Code: /SAPDMC/LTXTL-TEXTLINE = ZLONG_TEXT-LTEXT.
Step6 -> Specify file
Legacy Data On the PC (Frontend)
 Data D:\Sales_Longtext.txt
Step7 -> Assign File
ZLONG_TEXT Source structure for long text
 Data D:\Sales_Longtext.txt
Step8 -> Read data
Output result
Source Structure Read Written Not Written
ZLONG_TEXT 1 1 0
Transactions Read: 1
Records Read: 1
Transactions Written: 1
Records Written: 1
Step 8 -> Display read data
Field Name Field Text Field Value
MATNR MATNR MATERIA1
LTEXT LTEXT SALES TEXT FOR Material MATERIAL1
Step 9 -> Convert data
File Read: ZNRD_PRJ1_ZNRD_SUBPRJ2_ZNRD_LTEXT.lsmw.read
File Written: ZNRD_PRJ1_ZNRD_SUBPRJ2_ZNRD_LTEXT.lsmw.conv
Transactions Read: 1
Records Read: 1
Transactions Written: 1
Records Written: 2
Step 10 -> Display converted data
1 /SAPDMC/LTXTH 1MVKE MATERIAL1 0001E
2 /SAPDMC/LTXTL 2/ SALES TEXT FOR Material MATERIAL1
Step 11 -> Start direct input program
Output result for the same
Legacy System Migration Workbench
Project: ZNRD_PRJ1 ORH
Subproject: ZNRD_SUBPRJ2 Upload long text
Object: ZNRD_LTEXT Long text tru direct input
File : ZNRD_PRJ1_ZNRD_SUBPRJ2_ZNRD_LTEXT.lsmw.conv
Long Texts in Total: 1
Successfully Transferred Long Texts: 1
Non-Transferred Long Texts: 0
Now when i check the material master sales view -> sales text it is empty.
Please help me with the same.
Regards,
Ranjith N

Hello Experts, I was trying to upload sales text for a material master using LSMW direct input method.
I followed the following steps for the same
Tab dlimited Text file format
MATNR LONGTEXT LINE
MATERIAL1 LONGTEXT FOR MATERIAL MATERIAL1 1 *************************************************************************************************************
Step1 -> Maintain object attributes
Object -> 0001
Method-> 0001
Program name -> /SAPDMC/SAP_LSMW_IMPORT_TEXTS
Program type -> D
Step2 -> Maintain Source Structure
Source structure -> LONG_TEXT Source structure for long text
Step 3-> Maintain souce file Source Fields
ZLONG_TEXT Source structure for long text
MATNR C(018) MATNR
LTEXT C(132) LTEXT
Step 4-> Maintain structure relationship
Structure Relations
/SAPDMC/LTXTH Long Texts: Header <<<< ZLONG_TEXT Source structure for long text
Select Target Structure
/SAPDMC/LTXTH . /SAPDMC/LTXTL Long Texts: Row <<<< ZLONG_TEXT Source structure for long text
Select Target Structure /SAPDMC/LTXTL .
Step 5-> Maintain Field mapping and conversion rules
Here i have assigned constan rules to couple of them like
/SAPDMC/LTXTH Long Texts: Header
Fields
OBJECT Texts: Application Object
 Rule : Constant
 Code: /SAPDMC/LTXTH-OBJECT = 'MVKE'.
NAME Name
 Source: ZLONG_TEXT-MATNR (MATNR)
 Rule : Transfer (MOVE)
 Code: /SAPDMC/LTXTH-NAME = ZLONG_TEXT-MATNR.
ID Text ID
 Rule : Constant
 Code: /SAPDMC/LTXTH-ID = '0001'.
SPRAS Language Key
 Rule : Constant
 Code: /SAPDMC/LTXTH-SPRAS = 'E'.
/SAPDMC/LTXTL Long Texts: Row
Fields
TEXTFORMAT Tag column
 Rule : Constant
 Code: /SAPDMC/LTXTL-TEXTFORMAT = '/'.
TEXTLINE Text Line
 Source: ZLONG_TEXT-LTEXT (LTEXT)
 Rule : Transfer (MOVE)
 Code: /SAPDMC/LTXTL-TEXTLINE = ZLONG_TEXT-LTEXT.
Step6 -> Specify file Legacy
Data On the PC (Frontend)
 Data D:\Sales_Longtext.txt
Step7 -> Assign File ZLONG_TEXT
Source structure for long text
 Data D:\Sales_Longtext.txt
Step8 -> Read data
Output result
Source Structure Read Written Not Written
ZLONG_TEXT 1 1 0
Transactions Read 1
Records Read: 1
Transactions Written: 1
Records Written: 1
Step 8 -> Display read data
Field Name Field Text Field Value
MATNR MATNR MATERIA1
LTEXT LTEXT SALES TEXT FOR Material MATERIAL1
Step 9 -> Convert data
File Read: ZNRD_PRJ1_ZNRD_SUBPRJ2_ZNRD_LTEXT.lsmw.read
File Written: ZNRD_PRJ1_ZNRD_SUBPRJ2_ZNRD_LTEXT.lsmw.conv
Transactions Read: 1
Records Read: 1
Transactions Written: 1
Records Written: 2
tep 10 -> Display converted data
1 /SAPDMC/LTXTH 1 MVKE MATERIAL1 0001 E
2 /SAPDMC/LTXTL 2/ SALES TEXT FOR Material MATERIAL1
Step 11 -> Start direct input program
Output result for the same
Legacy System Migration Workbench Project:
ZNRD_PRJ1 ORH
Subproject: ZNRD_SUBPRJ2 Upload long text
Object: ZNRD_LTEXT Long text tru direct input
File : ZNRD_PRJ1_ZNRD_SUBPRJ2_ZNRD_LTEXT.lsmw.conv
Long Texts in Total: 1
Successfully Transferred Long Texts: 1
Non-Transferred Long Texts: 0
Now when i check the material master sales view -> sales text it is empty. Please help me with the same.
Regards,
Ranjith N

LSMW FOR MATERIAL MASTER USING BAPI_MATERIAL_SAVEDATA

Hi Gurus,
Im trying to develop lsmw for material master upload using bapi method.
Object:BUS1001006
BAPI:BAPI_MATERIAL_SAVEDATA
MESSAGE TYPE: MATMAS_BAPI
BASIC TYPE : MATMAS_BAPI01.
I m unable to find parameters to load gross_weight volume and volume unit and also problem loading the custom fields of material master. Any body who has worked on this one, can you please help me.
Thanks
venkat

The BAPI_MATERAIL_SAVEDATA support the gross_weight or the volume via the tables UNITSOFMEASURE and UNITSOFMEASUREX.
eg.
UNIT_OF_WT =KG
ALT_UNIT = PCS
NUMERATOR = 1
DENOMINATR =1
GROSS_WT =1000
All the customer specific field are supported by the EXTENSIONIN and EXTENSIONINX tables.

LSMW FOR MATERIAL MASTER USING BAPI_MATERIAL_SAVEDATA -Adding Custom Fields

Hi Gurus,
I'm developing LSMW for Material Master Upload using BAPI method.
Object:BUS1001006
BAPI:BAPI_MATERIAL_SAVEDATA
MESSAGE TYPE: MATMAS_BAPI
BASIC TYPE : MATMAS_BAPI03.
There is a requirement to use/map a custom field. Upon research custom field can be added to the parameter EXTENSIONIN and EXTENSIONINX, but I have no Idea on how to do it with LSMW. Please advise what approach is needed.
Thanks and Regards,
Jay

Hi Gurus,
I got the following code below.
The custom field won't get updated.... Please advise on what should I do... I've checked different forums and still can't come up with the solution... Please advise..
REPORT ztest_extend_matmas1.
STRUCTURE
TABLES:
bapimathead, "Headerdata
bapi_mara, "Clientdata
bapi_marax, "Clientdatax
bapi_marc, "Plantdata
bapi_marcx, "Plantdatax
bapi_makt, "Material description
bapiparex, "Extensionstruktur
bapiparexx,
bapiret2. "Return messages
DATA:
bapi_te_mara LIKE bapi_te_mara,
bapi_te_marax LIKE bapi_te_marax,
v_file TYPE string.
INTERNAL TABLE
*to store the output data
DATA:BEGIN OF it_material_number OCCURS 0.
        INCLUDE STRUCTURE bapimatinr.
DATA:END OF it_material_number.
*for materialtext
DATA:BEGIN OF it_materialdesc OCCURS 0.
        INCLUDE STRUCTURE bapi_makt .
DATA:END OF it_materialdesc.
*für z-feld
DATA:BEGIN OF it_bapiparex OCCURS 0.
        INCLUDE STRUCTURE bapiparex.
DATA:END OF it_bapiparex.
*für z-feldx
DATA:BEGIN OF it_bapiparexx OCCURS 0.
        INCLUDE STRUCTURE bapiparexx.
DATA:END OF it_bapiparexx.
*to return messages
DATA:BEGIN OF it_return2 OCCURS 0.
        INCLUDE STRUCTURE bapiret2.
DATA:END OF it_return2.
DATA:BEGIN OF it_return OCCURS 0.
        INCLUDE STRUCTURE bapiret1.
DATA:END OF it_return.
DATA
lt_messages      TYPE bapiret2_t.
PROCESSING
*bapimathead-material = it_material_number-material.
bapimathead-material = '100-2520'.
bapimathead-ind_sector = 'P'.
bapimathead-matl_type = 'AEM'.
bapimathead-basic_view = 'X'.
bapimathead-purchase_view = 'X'.
bapimathead-inp_fld_check = 'I'.
*bapimathead-BASIC_VIEW = 'X'.
*bapimathead-SALES_VIEW = 'X'.
*bapimathead-PURCHASE_VIEW = 'X'.
*bapimathead-MRP_VIEW = 'X'.
*bapimathead-FORECAST_VIEW = 'X'.
*bapimathead-WORK_SCHED_VIEW = 'X'.
*bapimathead-PRT_VIEW = 'X'.
*bapimathead-STORAGE_VIEW = 'X'.
*bapimathead-WAREHOUSE_VIEW = 'X'.
bapi_mara-matl_group = '0001'.
bapi_mara-old_mat_no = '100-251'.
bapi_mara-base_uom = 'ST'.
bapi_marax-matl_group = 'X'.
bapi_marax-old_mat_no = 'X'.
bapi_marax-base_uom = 'X'.
bapi_marc-plant = '1000'.
bapi_marcx-plant = '1000'.
it_materialdesc-langu = 'EN'.
it_materialdesc-matl_desc = 'DESC'.
APPEND it_materialdesc.
*bapi_te_mara-material = it_material_number-material.
bapimathead-material = '100-2520'.
*bapi_te_mara-zzforst = '4148'.
bapi_te_mara-material = '100-2520'.
bapi_te_mara-zzmar_field1 = '4148'.
*bapi_te_marax-material = it_material_number-material.
bapimathead-material = '100-2520'.
*bapi_te_marax-zzforst = 'X'.
bapi_te_marax-material = '100-2520'.
bapi_te_marax-zzmar_field1 = 'X'.
it_bapiparex-structure = 'BAPI_TE_MARA'.
it_bapiparex-valuepart1 = bapi_te_mara.
APPEND it_bapiparex.
it_bapiparexx-structure = 'BAPI_TE_MARAX'.
it_bapiparexx-valuepart1 = bapi_te_marax.
APPEND it_bapiparexx.
CALL FUNCTION 'BAPI_MATERIAL_SAVEDATA'
EXPORTING
    headdata            = bapimathead
    clientdata          = bapi_mara
    clientdatax         = bapi_marax
    plantdata           = bapi_marc
    plantdatax          = bapi_marcx
IMPORTING
    return              = it_return2
TABLES
    materialdescription = it_materialdesc
    extensionin         = it_bapiparex
    extensioninx        = it_bapiparexx
    returnmessages      = lt_messages.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
THanks and Regards,
Jay
Edited by: jhayyy on May 17, 2011 6:54 AM

LSMW Direct Input Method RMDATIND tax classification material

Hi folks,
I am loading material master data throught LSMW using direct input method. In MM01 for a particular sales org we have tax classifcation for three different countries US, CA and GB. Could anyone tell me how do I post the tax classification Material data in the table control for these three different countries.
COUNTRY COUNTRY TAX CATG. TAX CATEG.       TAX CLASSIF
CA     Canada     CTX1     GST (Canada)     ...........
CA     Canada     CTX2     PST (Canada)     ...........
CA     Canada     CTX3     PST (Base+GST) Cdn...........
GB     United Kingdom     MWST     Output Tax...........
US     USA     UTXJ     Tax Jurisdict.Code     ...........
US     USA     UTX2     County Sales Tax     ...............
US     USA     UTX3     City Sales Tax     .............
Points will be rewarded for the answers.
Thanks,
Raj

Hi,
Not sure about the same requirement of countries & tax codes for all the materials for your upload.
If this is the case,
enable the
Extras->DisplayVariant
from the menu of the LSMW & check all the check boxes. Now you see the
__END_OF_RECORD__
for the structure
BMMH2
which has to be mapped with the input structure in the Maintain structure relations step.
double click on the
__END_OF_RECORD__
which will lead to ABAP editor & then put the following code:
* Canada
bmmh2-stype = '3'.
bmmh2-aland = 'CA'.
bmmh2-taty1 = 'CTX1'.
bmmh2-taxm1 = '1'.
transfer_record.
bmmh2-stype = '3'.
bmmh2-aland = 'CA'.
bmmh2-taty1 = 'CTX2'.
bmmh2-taxm1 = '1'.
transfer_record.
else if you have a different set of countries with different tax codes for the set of materials,
You need to have a separate file for this & map the fields to the structure fields of
BMMH2
Hope this helps.
Best Regards, Murugesh AS
Message was edited by:
        Murugesh Arcot

Customer Master Conversion - Direct input method

Hi,
I want to extend the sales area of the customers who are already existing using Direct Input Method. But I am getting the Error.
Thanks
Raghavendra

Hi Raghavendra,
Can you tell what error ur getting?Also which structure you are using ? I think the structure BKNVV / BKNZA needs to be extend for this additional extended sales area.
Also try to use Batch input seesion methos. in that you may get the structure name which we need to extend.
Pradeep

Most use ful t code for Material Master changing

Dear All,
Can any one give me most useful T-codes for create, change and display material master.
I have one T-code which is very useful for material master it is "MM50". With help of this tcode you can see material extend detail and also you can delete mass material with help of this tcode.
So please use it and also give me other this type of tcodes.
Regards,
Mahesh Wagh

Hi,
MM17, LSMW, MM50 --- These are the 3 main transactions which is used frequently to Mass change the Material master.
There is one more option is there using BDC Upload.
Batch Data Communication or BDC is a batch interfacing technique that SAP developed. It is mainly used for uploading data into the SAP R/3 system. BDC works by simulating the user input from transactional screen via an ABAP program.
The data input data file will come in the form of a flat file which the user save as file type txt file or prn file from the Microsoft Excel program. An Abaper will create a program to read the text file and upload into the SAP system.
Transaction -- SHDB will be used to record the change material master. After, the simulation, the Abaper can generate a sample program and modify from there. It makes the programming easier and faster.
For a BDC upload you need to write a program which created BDC sessions.
hope you got it. Take a help of ABAPer for this BDC Upload.
rgds
Chidanand

Step by step instruction for Using LSMW Recoding method for Material Master

Guys,
Can some one explain step by step procedure for uploading the materials master data to R/3 by using LSMW Recoding method. By the time you reply I will go through the rule of uploading the data..
Thanks guys,
Dhanu.

Hi,
The Legacy System Migration Workbench (LSMW) is a tool recommended by SAP that you can use to transfer data once only or periodically from legacy systems into an R/3 System.
The LSM Workbench covers the following steps:
(1)Read the legacy data from one or several files (e.g. spreadsheet tables, sequential files)
(2)Convert the data from source format to target format
(3)Import the data using standard interfaces (Batch Input, Direct Input, BAPI, IDoc).
The Steps for LSME are:
Example: Customer Master upload:
LSMW to Update Customer Master Records with Transaction Recording
Call Legacy System Migration Workbench by entering transaction code LSMW. Every conversion task is grouped together as Project / Subproject / Object structure. Create a Project called LSMW_DEMO and a Subproject as CUSTOMERS and Object as CUST_REC
Step 1: Maintain Object attributes
In this example, you will be updating the customer master records with the help of recording a transaction (XD02). Choose radio button Batch Input Recording and click on the recording overview icon to record the R/3 transaction. Enter the Recording name as XD02_REC, the description as Customer Master Updates Recording, and the transaction code as XD02.
Step 2. Maintain Source Structures
Give a name and a description to the source structure
Step 3. Maintain Source Fields
In this step, you need to list what fields are present in the source structure. The easiest way is to click on u2018Table Maintenanceu2019 icon to enter Fieldname, Type and Length for each field
Step 4: Maintain Structure Relations
Execute a step to u2018Maintain Structure Relationsu2019. Since, there is only one Source and Target Structure, the relationship is defaulted automatically.
Step 5: Maintain field mapping and conversion rules
Field RF02D-D0310 represents that you chose u2018Sales viewu2019 for the customer Master screen accordingly its value should be set to X. Keep your cursor on field RF02D-D0310 and click on Constant rule icon to choose the constant value of u2018Xu2019.
If your source file already has the field value, you choose rule u2018Source Fieldu2019.
Keep cursor on field u2018KUNNRu2019 and click on u2018Assign Source fieldu2019 icon to choose source field CUSTOMER from structure XD02S
Step 6: Maintain fixed values, translations, user-defined routines
You can also maintain re-usable translations and user-defined routines, which can be used across conversion tasks. In this case, that step is not required.
Step 7: Specify files
In this step, we define how the layout of the input file is. The input file is a [Tab] delimited with the first row as field names. It is present on my PC (local drive) as C:\XD02.txt.
Step 8: Assign files
Execute step u2018Assign Filesu2019 and the system automatically defaults the filename to the source structure.
Step 9: Read data
In this step, LSMW reads the data from the source file (from your PCu2019s local drive). You have the option to read only selected rows and convert data values to Internal format.
Step 10: Display read data
This step is optional. If required, you can review the field contents for the rows of data read.
Step 11: Convert data
This is the step that actually converts the source data (in source format) to a target format. Based on the conversion rules defined, source fields are mapped to target fields.
Step 12: Display Converted data
Again this is an optional step to view how the source data is converted to internal SAP format
Step 13: Create batch input session
Once the source data is converted in an internal format, you can create a batch session to process updates.
Step 14: Run Batch Input Session
You can execute the BDC session by Run Batch input session. Executing a batch input session is a standard SM35 transaction for managing BDC sessions. Once you have successfully executed the batch input session, the customer master records are updated in the system. You can confirm this by viewing the customer master records (XD03).
Follow the link for material master
http://www.sap123.com/showthread.php?t=98
Regards,
Biju K

How to Use PM BAPI for equipment Master upload : BAPI_EQUIPMENT_SAVEREPLICA

Hi ,
How to use PM BAPI for equipment Master upload : BAPI_EQUIPMENT_SAVEREPLICA.
May i know what are the input parameters & fields mandatory
for each Table structures ct_data , ct_datax , it_descript , it_longtext.
Can any one explain me Step by Step Process.
B'cos i tried with below code. Equipment is not getting created.
wa_itab-equipment_ext = '000000000100000001'.
wa_itab-descript      = 'Test 2 -> Lube Oil Pump'.
wa_itab-text_language = 'EN'.
wa_itab-sdescript     = 'Short Description'.
APPEND wa_itab TO it_itab.
CLEAR wa_itab.
LOOP AT it_itab INTO wa_itab.
    ct_data-ta_guid       = '000000000000000001'.
    ct_data-equipment_ext = wa_itab-equipment_ext.
    ct_data-descript      = wa_itab-descript     .
    ct_data-valid_date    = sy-datum.
    ct_data-equicatgry    = 'M'.
    APPEND ct_data.
    CLEAR ct_data.
    ct_datax-ta_guid       = '000000000000000001'.
    ct_datax-equipment_ext = 'X'.
    ct_datax-equipment     = 'X'.
    APPEND ct_datax.
    CLEAR ct_datax.
    it_descript-ta_guid       = '000000000000000001'.
    it_descript-text_language = wa_itab-text_language.
    it_descript-descript      = wa_itab-sdescript    .
    APPEND it_descript.
    CLEAR it_descript.
    it_longtext-ta_guid        = '000000000000000001'.
    it_longtext-text_language = wa_itab-text_language.
    it_longtext-text_id        = 'LTXT'.
    it_longtext-text_line      = 'SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS'.
    APPEND it_longtext.
    CLEAR it_longtext.
    it_longtext-ta_guid        = '000000000000000001'.
    it_longtext-text_language = wa_itab-text_language.
    it_longtext-text_id        = 'INTV'.
    it_longtext-text_line      = 'aaaaaaaaaaaaaaa'.
    APPEND it_longtext.
    CLEAR it_longtext.
    it_longtext-ta_guid        = '000000000000000001'.
    it_longtext-text_language = wa_itab-text_language.
    it_longtext-text_id        = 'INTV'.
    it_longtext-text_line      = 'bbbbbbbbbbbb'.
    APPEND it_longtext.
    CLEAR it_longtext.
    it_longtext-ta_guid        = '000000000000000001'.
    it_longtext-text_language = wa_itab-text_language.
    it_longtext-text_id        = 'INTV'.
    it_longtext-text_line      = 'cccccccccccccccc'.
    APPEND it_longtext.
    CLEAR it_longtext.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
call BAPI-function in this system
    CALL FUNCTION 'BAPI_EQUIPMENT_SAVEREPLICA'
      TABLES
        ct_data     = ct_data
        ct_datax    = ct_datax
        it_descript = it_descript
        it_longtext = it_longtext
        return      = return
      EXCEPTIONS
        OTHERS      = 1.
    IF sy-subrc = 0.
      CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'.
      WRITE : 'Successful'.
    ENDIF.
    IF NOT return IS INITIAL.
      LOOP AT return.
        IF return-type = 'A' OR return-type = 'E'.
          WRITE : 'Error'.
        ENDIF.
      ENDLOOP.
    ENDIF.
    REFRESH return.
ENDLOOP.
Regards
SUrendar

Hi ,
How to use PM BAPI for equipment Master upload : BAPI_EQUIPMENT_SAVEREPLICA.
May i know what are the input parameters & fields mandatory
for each Table structures ct_data , ct_datax , it_descript , it_longtext.
Can any one explain me Step by Step Process.
B'cos i tried with below code. Equipment is not getting created.
wa_itab-equipment_ext = '000000000100000001'.
wa_itab-descript      = 'Test 2 -> Lube Oil Pump'.
wa_itab-text_language = 'EN'.
wa_itab-sdescript     = 'Short Description'.
APPEND wa_itab TO it_itab.
CLEAR wa_itab.
LOOP AT it_itab INTO wa_itab.
    ct_data-ta_guid       = '000000000000000001'.
    ct_data-equipment_ext = wa_itab-equipment_ext.
    ct_data-descript      = wa_itab-descript     .
    ct_data-valid_date    = sy-datum.
    ct_data-equicatgry    = 'M'.
    APPEND ct_data.
    CLEAR ct_data.
    ct_datax-ta_guid       = '000000000000000001'.
    ct_datax-equipment_ext = 'X'.
    ct_datax-equipment     = 'X'.
    APPEND ct_datax.
    CLEAR ct_datax.
    it_descript-ta_guid       = '000000000000000001'.
    it_descript-text_language = wa_itab-text_language.
    it_descript-descript      = wa_itab-sdescript    .
    APPEND it_descript.
    CLEAR it_descript.
    it_longtext-ta_guid        = '000000000000000001'.
    it_longtext-text_language = wa_itab-text_language.
    it_longtext-text_id        = 'LTXT'.
    it_longtext-text_line      = 'SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS'.
    APPEND it_longtext.
    CLEAR it_longtext.
    it_longtext-ta_guid        = '000000000000000001'.
    it_longtext-text_language = wa_itab-text_language.
    it_longtext-text_id        = 'INTV'.
    it_longtext-text_line      = 'aaaaaaaaaaaaaaa'.
    APPEND it_longtext.
    CLEAR it_longtext.
    it_longtext-ta_guid        = '000000000000000001'.
    it_longtext-text_language = wa_itab-text_language.
    it_longtext-text_id        = 'INTV'.
    it_longtext-text_line      = 'bbbbbbbbbbbb'.
    APPEND it_longtext.
    CLEAR it_longtext.
    it_longtext-ta_guid        = '000000000000000001'.
    it_longtext-text_language = wa_itab-text_language.
    it_longtext-text_id        = 'INTV'.
    it_longtext-text_line      = 'cccccccccccccccc'.
    APPEND it_longtext.
    CLEAR it_longtext.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
call BAPI-function in this system
    CALL FUNCTION 'BAPI_EQUIPMENT_SAVEREPLICA'
      TABLES
        ct_data     = ct_data
        ct_datax    = ct_datax
        it_descript = it_descript
        it_longtext = it_longtext
        return      = return
      EXCEPTIONS
        OTHERS      = 1.
    IF sy-subrc = 0.
      CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'.
      WRITE : 'Successful'.
    ENDIF.
    IF NOT return IS INITIAL.
      LOOP AT return.
        IF return-type = 'A' OR return-type = 'E'.
          WRITE : 'Error'.
        ENDIF.
      ENDLOOP.
    ENDIF.
    REFRESH return.
ENDLOOP.
Regards
SUrendar

Issue in LSMW for material master using standard input program RMDATIND!!

Hello guys,
I have a issue in LSMW for material master.
I have a custom field in MARA table. which I want to add in my LSMW.
I added the field in BMMH1 structure. I'm passing the value to this field, But it is not populated in the table when I run it.
Is there anything else I need to do apart from addition of field in the structure BMMH1.
Thanks in advance for your help.
Regards,
Sumeet....

see oss note 44410, it gives you a step by step overview.
https://service.sap.com/sap/support/notes/44410

Help me for material master upload by using Direct Input method

Similar Messages

Maybe you are looking for