Using BAPI to upload Equipment Master (IE01)

Hi,
Can any one help to do below object...that i need for resume.
Pls provide me compelete details with code or else give me guidelines in detail to carrayout.....
i should be thankful to you....
Using BAPI to upload Equipment Master (IE01). Fields that are uploaded are Equipment category, valid to date, Equip. Description, object type, Acquisition value, Acquisition date, Maintenance Plan, plan section, catalog profile. Input file is accessed from application server. Error log file is created at application server.
with regards
bheem

If this is a onetime load, you can use LSMW to do this.
Object 0400. Must easier than writing a report from scratch.
Albert

Similar Messages

Unable to use SCAT to upload material master in ECC 6

HI
I am unable to use SCAT to upload material master in ECC 6,
an error is triggering
"Releases higher than 6.40 are not permitted
Message no. TT005
Diagnosis
With Web Application Server Release 6.40, you cannot create new automated CATT test cases. However, you can create manual CATT test cases"
canany body please help me to use SCAT
Sreeram

you have to read yourself:
http://help.sap.com/erp2005_ehp_04/helpdata/EN/1b/e81c3b84e65e7be10000000a11402f/frameset.htm
I certainly do not use SCAT or SECATT to load master data, especially not material master.
A material master has dynamic screens, based on the material type the view selection will be different, based on entries made in MRP view fields become hidden or mandatory. Such things canot be done with a static recording.
SAP provides batch input programs and BAPIs for material master load and additonally loading per IDOC in LSMW (which offers as well batch input and Bapi methods)

Interface Using BAPI for Uploading shipment datas

Can any1 send me the example code for Inbound Interface using BAPI for Uploading shipment datas.please kindly send me the programs which u using with BAPI

Hi
Except hiring (or new joinee) for all other actions you can use below Function Module.
HR_INFOTYPE_OPERATION.
~~~Ganesh Kumar K.

Check for Partner on Equipment Master (IE01)

We have a requirement to check that sold-to partner function is mandatory during equipment creation (IE01). This can be done via configuration. However, the requirement is also to allow users to delete this partner using IE02. Hence they only want the partner to be mandatory during IE01 and not IE02.
I believe only way to do this is using a user-exit. We know of a user-exit IEQM0003 that is allows us to put in logic before equipment is saved. However, this user-exit doesn't have parameters to partner data.
Is there any other user-exit that can be used?

You could check to see if you could read the partner from the memory within the FM. However you could potentially accomplish the same using the following steps without programming..
You could use the View profile settings in configuration and transaction variant functionality (SHD0) to accomplish this.
-> As a first step Make sure to add the Partner view as a sub screen to the very first screen using View profile settings for the equipment category in SPRO. (This will force the partner field to be available directly on the initial screen when a piece of equipment is created).
---> Now create a Transaction variant for the standard transaction IE01 and here select the sold to partner custom type and leave the value field blank.Now on the configuration for the Transaction set the Partner type to be imported with value "SP" and mark the content field to be mandatory.Leave all other settings to default and save and exit.
---> Now set this Transaction variant as a standard variant for this transaction.
This should do the trick.The user will be forced to enter the sold to party on the screen.However for change transaction(IE02) the user can delete this partner type without any issues.
Regards
Narasimhan

Additional filed in Equipment Master IE01

I want to add additional fileds in Equipment Master - user field
Is there any user exit & Badi for this, i need Drop down also for these fields for report purpose
Thanks
Prakash
Edited by: prakash balasubramanian on Jun 4, 2008 6:08 AM

Bala,
Have a look at user-exit ITOB0001via TCode SMOD
Also see BADIs EQUI_SCR* via TCode SE18
Have a look [here|http://www.sapfans.com/forums/viewtopic.php?p=648307] for a list of PM/CS user-exits, BADIs, Etc
PeteA

BDC Equipment Master IE01

Hi all,
I am doin master upload for equipment.The equipments are succesfully created.But for certain records deletion flag needs to be set and sub equipments need to be created.This is possible only in change equipment ie IE02.So while I go to change mode it is givin me the message
S Equipment 20 is already locked by user <my username>
and the rest of d things not updated.I tried to give FM: DEQUEUE_EIEQUI to release the lock aftr IE01 and befor calln IE02.But still same message comin.
Do anyone have a solution for dis.Any help would be appreciated.

It is either a bug (check SAP notes), or more probably an asynchronous update/lock which is not finished yet.
So simply execute the BDC in synchonous update mode (S or L). For more information, read paragraph #12 in [wiki BDC FAQ about errors|http://wiki.sdn.sap.com/wiki/display/ABAP/BatchInputFAQ#BatchInputFAQ-WhyBDCbehavesdifferently%3F] for more information, and [wiki BDC about update mode|http://wiki.sdn.sap.com/wiki/display/ABAP/BatchInput-+BDC#BatchInput-BDC-Updatemode].

Problem in uploading material master data using BAPI?

Hi all,
I am using BAPI_MATERIAL_SAVEDATA to upload materail master data. Here i have to pass moving average price values in two currenices(using account_view and valuationdata in BAPI). But i found only one field for moving average price i.e moving_pr in valuationdata.
Please help me on how to upload the moving average price in two currencies?
Thanks,
Aravind.

Hi
There is function module BAPI_MATERIAL_SAVEREPLICA where
VALUATIONDATA parameter is in the tables tab.
But I didn't test it. Try, may be it works as you need.

F-22, Need to upload the document using BAPI

we have requirement to use BAPI for uploading document to f-22,
For the BAPI when we input data all the data are correctly posted except posting keys,
Our requirement is to use the customized posting for crediting customer and standard posting key for debiting GL account,
We have input the required posting key in BAPI but still its not picking the posting key, its taking the standard posting key,
Document type used is DC and DB,
so is there any relation between document type and posting key, any idea from where BAPI is picking Posting key?

Hello,
it was originally not intended to use the BAPI to post
payment documnents. For simplicity the posting keys are not
at the BAPI's interface, instead they are defaulted with
the standard posting keys depending on account type and debit/credit
indicator.
Please see note 487722 which explains how to pass addditional data
to the BAPI in parameter EXTENSION1. You can implement the
Business Transaction Event (BTE) RWBAPI01 to populate the posting
key (t_accit-bschl) from EXTENSION1 parameter.
I hope this helps!
BR,
Raquel

Creating a sales document using BAPI in web dynpro by uploading a file

Hi ALL,
Can some one help me how to create a sales document using BAPI by uploading a file as input...Can someone provide me a sample program....
Thanks n Regards,
Praveenn.
Edited by: praveenn on Aug 23, 2011 12:42 PM

Hi Sri,
Thx for the response...
Here is the code that i followed for creating a BAPI_SALESORDER_CREATE1 by uploading a text file as input.
Just create a Attribute in the VIEW CONTEXT of type String.
method ONACTIONCREATE_SO .
types : Begin of ty_data,
         sales_org type vkorg,
         doc_type   type AUART,
         DISTR_CHAN type VTWEG,
         DIVISION   type spart,
         material   type matnr,
         partn_role type PARVW,
         PARTN_NUMB type kunnr,
       end of ty_data.
DATA :it_table TYPE TABLE OF ty_data,
         i_data   TYPE TABLE OF string,
         l_string TYPE string,
         wa_table TYPE ty_Data,
         l_xstring TYPE xstring,
         fields TYPE string_table,
         lv_field TYPE string.
DATA: wa_order_header_in TYPE BAPISDHD1,
      it_order_items_in TYPE TABLE OF BAPISDITM,
      wa_order_items_in TYPE BAPISDITM,
      it_order_partners TYPE TABLE OF BAPIPARNR,
      wa_order_partners TYPE BAPIPARNR,
      it_return TYPE TABLE OF BAPIRET2,
      wa_return TYPE BAPIRET2.
DATA : sales_doc type bapivbeln-vbeln.
DATA:
   node_zfinal_node TYPE REF TO if_wd_context_node,
   elem_zfinal_node TYPE REF TO if_wd_context_element,
   stru_zfinal_node TYPE if_main_view=>element_zfinal_node .
get single attribute
wd_context->get_attribute(
EXPORTING
name = 'DATASOURCE'
IMPORTING
value = l_xstring ).
CALL FUNCTION 'HR_KR_XSTRING_TO_STRING'
    EXPORTING
      in_xstring = l_xstring
    IMPORTING
      out_string = l_string.
SPLIT l_string AT cl_abap_char_utilities=>newline INTO TABLE i_data.
LOOP AT i_data INTO l_string.
   SPLIT l_string AT cl_abap_char_utilities=>horizontal_tab INTO TABLE fields.
    READ TABLE fields INTO lv_field INDEX 1.
    wa_table-sales_org = lv_field.
    READ TABLE fields INTO lv_field INDEX 2.
    wa_table-doc_type = lv_field.
    READ TABLE fields INTO lv_field INDEX 3.
    wa_table-DISTR_CHAN = lv_field.
    READ TABLE fields INTO lv_field INDEX 4.
    wa_table-DIVISION = lv_field.
    READ TABLE fields INTO lv_field INDEX 5.
    wa_table-material = lv_field.
    READ TABLE fields INTO lv_field INDEX 6.
    wa_table-partn_role = lv_field.
    READ TABLE fields INTO lv_field INDEX 7.
    wa_table-partn_numb = lv_field.
APPEND wa_table TO it_table.
ENDLOOP.
loop at it_table into wa_table.
clear : wa_order_header_in.
wa_order_header_in-sales_org   = wa_table-sales_org.
wa_order_header_in-doc_type    = wa_table-doc_type.
wa_order_header_in-distr_chan = wa_table-distr_chan.
wa_order_header_in-division    = wa_table-division.
clear : wa_order_items_in.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
    input         = wa_table-material
IMPORTING
   OUTPUT        = wa_order_items_in-material.
*wa_order_items_in-req_qty = wa_table-req_qty.
append wa_order_items_in to it_order_items_in.
clear : wa_order_partners.
wa_order_partners-partn_role = wa_table-partn_role.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
    input         = wa_table-partn_numb
IMPORTING
   OUTPUT        = wa_order_partners-partn_numb
*wa_order_partners-partn_numb = wa_table-partn_numb.
append wa_order_partners to it_order_partners.
endloop.
CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
EXPORTING
SALESDOCUMENTIN               =
    order_header_in               = wa_order_header_in
ORDER_HEADER_INX              =
SENDER                        =
BINARY_RELATIONSHIPTYPE       =
INT_NUMBER_ASSIGNMENT         =
BEHAVE_WHEN_ERROR             =
LOGIC_SWITCH                  =
TESTRUN                       =
CONVERT                       = ' '
IMPORTING
   SALESDOCUMENT                 = sales_doc
tables
   RETURN                        = it_return
   ORDER_ITEMS_IN                = it_order_items_in
ORDER_ITEMS_INX               =
    order_partners                = it_order_partners.
ORDER_SCHEDULES_IN            =
get message manager
DATA: l_current_controller TYPE REF TO if_wd_controller,
       l_message_manager    TYPE REF TO if_wd_message_manager.
       l_current_controller ?= wd_this->wd_get_api( ).
DATA: v_message_text TYPE string.
When Sales Order is created commit the data
IF NOT sales_doc IS INITIAL.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
   EXPORTING wait = 'X'.
CONCATENATE 'Sales Document' sales_doc 'has been created.' INTO v_message_text SEPARATED BY space.
Report Success message
CALL METHOD l_message_manager->report_success
EXPORTING
message_text = v_message_text.
ELSE.
v_message_text = 'Error Creating Sales Order'.
Report Error message
CALL METHOD l_message_manager->report_error_message
EXPORTING
message_text = v_message_text.
ENDIF.
endmethod.
Edited by: praveenn on Aug 30, 2011 2:41 PM

BAPI function create Customer master(T-code XD01)??

Hi All,
i want to create BDC program using BAPI function create Customer master(upload customer master),but i do not know which BAPI function for create Customer master.
Does anyone know,please tell me which BAPI function i can use?
Thanks.
Van Dung

Hi Amit Gujargoud,
I can use LSMW upload the data from legacy system to sap system., but my manager he did not want to use LSMW.He wants to use BAPI function for upload customer master.
I saw this BAPI function create customer master : BAPI_CUSTOMER_CREATEFROMDATA1,
BAPI_CUSTOMER_CREATEFROMDATA,
it is not enough field for input data.
example : if i want input : customer code,company code, Sales organiration,Distribution channel,Division.
So This BAPI function have not paramaters input this field.
Thanks for your answer
Van Dung.

Dropdown in Manufacturer field in Equipment Master

Hi Experts
Manufacturer (HERST) field in Equipment master(IE01) is free text field of 30 characters.
We want to add dropdown to this field so that we could validate/select values to this field.
Is there a user exit or easy way to achieve this. I found a user exit IEQM0007 but it does not add a dropdown.
Your thoughts.
Thanks
Gaurav

Gaurav:
I saw this before. Actually, we pu a dropdown not only for the manufacturer, but also for the model. The problem is that i don't remeber wich u.e we used, but it's quite not difficult to abap programmer tracing it. Perhaps it could modify the field type, replacing it for some one with the dropdown propertie. You will have to use an Z table (and maintain it), so consider that also
Hope this help.
Ezequiel

Equipment Master data changing automatically

Dear All,
this is weird but our SAP system is changing equipment's master data once it is created.
we have blocked all the possible chances of using T code "IE02-EQUIPMENT MASTER DATA CHANGE" at user end.
we are finding it very difficult to track because every time the equipment's action log displays new SAP ID's . we have checked with same ID but any where it is not possible for that user to have an authorization for IE02
it mainly changes the master data such as description/Manufacturer/Model number etc into some weird information. and this is happening at any time where in some cases it has been found that at 3:00 am or 4:00 am. we had also checked any background job is running at same timing but we couldn't found out any such case and this is happening without any prior notice so it is difficult for us also to monitor the same
if you have gone through same experience please share with us.
thanks
kiran

Kiran,
I fee that you must investigate through table CDHDR. Run Tcode SE16 --> Give value CDHDR --> Enter.
Here input values as under ( OBJECTCLAS, OBJECTID, USERNAME) and Execute.
In the output, you observe the values of fields TCODE, UDATE. You will come to know whether these changes are happening through IE02 or some other Tcode.
Also you should try without giving the USERNAME also. In this case you will get the lines of both normal changes and surprise change also in the output, where you are likely to find out what is happening.
In a similar way, you can investigate through table CDPOS also.
Jogeswara Rao 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

Material Master Upload using Bapi getting error "****** not a valid unit of

Hi Gurus,
i am uploading material master using BAPI Material_master_save_data , where the volume and Unit of Volume is Blank, Still i am getting error as "****** not a valid unit of volume ".kindly help me to resolve the issue.Many Thanks In advance.

Jurgen,
I could able to solve the issue for invalid unit Error ....Now i am getting **** unit of measure is not defined , pls check your entry or else i am getting alternate unit of mesure is same as base unit of measure .
I have used below logic for Purchase Order Unit and Base Unit of measure .
      if wa_upload-unmsr EQ wa_upload-ord_uom .
        bapi_mara1-base_uom = wa_upload-unmsr.
        bapi_mara1-po_unit = wa_upload-ord_uom .
      elseif wa_upload-unmsr NE wa_upload-ord_uom.
        wa_upload-ord_uom = wa_upload-alt_uom.
        bapi_mara1-po_unit = wa_upload-ord_uom.
      endif.
Many Thanks for your help.

Material master upload using BAPI...

Helo SDNers,
I am trying to upload material master using BAPI.
data : begin of t_mat occurs 0,
        material type matnr,             " Material - MATNR
        ind_sec type mbrsh,              " Industry sector - MBRSH
        mat_typ type mtart,              " Material type - MTART
        plant type werks_d,              " plant - WERKS_D
        stge_loc type lgort_d,           " Storage location - LGORT_D
        sales_org type vkorg,            " Sales org - VKORG
        distr_chan type vtweg,           " Distribution channel - VTWEG
        mat_desc type maktx,             " Material description - MAKTX
        base_uom type meins,             " Base unit of measurement- MEINS
        mat_grp type matkl,              " material group - MATKL
        division type spart,             " Division - SPART
        gen_itmcatmgrp type MTPOS,       " General item category group -MTPOS_MARA
        gros_weight type BRGEW,          " Gross weight - BRGEW
        net_weight type NTGEW,          " Net weight - NTGEW
        mat_grppack type MAGRV,          " Material group pack - MAGRV
        delv_plant type DWERK_EXT,       " Delivery plant
        tax_clasif type TAXKM,           " Tax classification
        item_catgrp type MTPOS,          " Item category group
        aval_check type MTVFP,           " Availability check
        trans_grp type TRAGR,            " Transportation group
        load_grp type LADGR,             " Loading group
        pur_grp type EKGRP,              " Purchasing grp,
        mrp_type type DISMM,             " MRP type
        mrp_contr type DISPO,            " MRP Controller
        lot_size type DISLS,             " Lot size,
        gr_processing type WEBAZ,        " GR Processing time
        schdmargin_key type FHORI,       " Schedule margin key
        batch_mangment type XCHPF,       " Batch management
        strog_cond type RAUBE,           " Storage condition
        source_list type KORDB,          " Source list
        mrp_grp type DISGR,              " MRP group
        reorder_point type MINBE,        " Reorder point
        procurement_type type BESKZ,     " Procurement type
        sp_procurement_type type SOBSL, " Special Procurement type
        inhouse_prod type DZEIT,                    " Inhouse production
        safety_stock type EISBE,         " Safety stock
        strategy_group type STRGR,       " Strategy group
        availabilty_grp type MTVFP,      " Availability group
        batch_entry type KZECH ,         " Batch entry
        valuation_class type BKLAS,      " Valuation class
        price_control type VPRSV,        " Price control
        moving_price type VERPR,         " Moving price
        standard_price type STPRS,       " Standard price - STPRS
        langu(2),                        " Language
end of t_mat.
this is my internal table i have these many content in my excel file
please explain me what the following code does .....
move-corresponding wa to bapi_head.
bapi_head-basic_view = 'X'.
bapi_head-sales_view = 'X'.
bapi_head-purchase_view = 'X'.
bapi_head-mrp_view = 'X'.
bapi_head-forecast_view = 'X'.
bapi_head-work_sched_view = 'X'.
bapi_head-prt_view = 'X'.
bapi_head-storage_view = 'X'.
bapi_head-warehouse_view = 'X'.
bapi_head-quality_view = 'X'.
bapi_head-account_view = 'X'.
bapi_head-cost_view = 'X'.
and also please help with an example how do i upload data from IT (my internal table) using BAPI.
Regards,
Ranjith N

Hi ,
First you upload your Excel data into Internal Table.
Move all data to Respected BAPI Structures.
and then call 'BAPI_MATERIAL_SAVEDATA' and pass all structures.
Sample Code:
CALL FUNCTION 'ALSM_EXCEL_TO_INTERNAL_TABLE'
    EXPORTING
      filename                = p_fname
      i_begin_col             = v_c1
      i_begin_row             = l_v_r
      i_end_col               = v_cl
      i_end_row               = v_rl
    TABLES
      intern                  = i_excel
    EXCEPTIONS
      inconsistent_parameters = 1
      upload_ole              = 2
      OTHERS                  = 3.
IF sy-subrc eq 0.
    LOOP AT i_excel.
      CASE i_excel-col.
        WHEN 0001.
          wa_final-field1 = i_excel-value.
        WHEN 0002.
          wa_final-field2 = i_excel-value.
        WHEN 0003.
          wa_final-field3 = i_excel-value.
        WHEN 0004.
          wa_final-field4 = i_excel-value.
        WHEN 0005.
          wa_final-field5 = i_excel-value.
        WHEN 0006.
          wa_final-field6 = i_excel-value.
        WHEN 0007.
          wa_final-field7 = i_excel-value.
        WHEN 0008.
          wa_final-field8 = i_excel-value.
        WHEN 0009.
          wa_final-field9 = i_excel-value.
        WHEN 0010.
          wa_final-field10 = i_excel-value.
        WHEN 0011.
          wa_final-field11 = i_excel-value.
        WHEN 0012.
          wa_final-field12 = i_excel-value.
        WHEN 0013.
          wa_final-field13 = i_excel-value.
        WHEN 0014.
          wa_final-field14 = i_excel-value.
        WHEN 0015.
          wa_final-field15 = i_excel-value.
        WHEN 0016.
          wa_final-field16 = i_excel-value.
      ENDCASE.
*-at end of each row, a record needs to append the internal table
      AT END OF row.
        APPEND wa_final TO i_final.
        CLEAR: wa_final.
      ENDAT.
    ENDLOOP.
ENDIF.
Move all your Inatrnal tbale data to respected BAPI structures
*&      Form MOVE_HEADDATA
   * Move Header data to BAPI Header.
FORM move_headdata .
Move Header Data to BAPI Fields
MOVE : wa_final-matnr      TO wa_mathead-material,
         wa_final-mbrsh      TO wa_mathead-ind_sector,
         wa_final-mtart      TO wa_mathead-matl_type.
To get UOM
SELECT SINGLE * FROM t006 INTO t006 WHERE msehi = wa_final-meins.
MOVE: t006-isocode TO wa_mara-base_uom_iso,
        c_x          TO wa_marax-base_uom_iso.
**-- Move Material Descriptions
PERFORM move_materialdescription .
ENDFORM.                    " MOVE_HEADDATA
*&      Form MOVE_CLIENTDATA
      * Move Basic data to Clientdata
FORM   move_clientdata .
MOVE : wa_final-spart      TO wa_mara-division,
         wa_final-bismt      TO wa_mara-old_mat_no,
         wa_final-extwg      TO wa_mara-extmatlgrp,
         wa_final-mtpos_mara TO wa_mara-item_cat,
         wa_final-groes      TO wa_mara-size_dim,
         wa_final-zeivr      TO wa_mara-doc_vers,
         wa_final-ekwsl      TO wa_mara-pur_valkey.
MOVE : c_x      TO wa_marax-division,
         c_x      TO wa_marax-old_mat_no,
         c_x      TO wa_marax-extmatlgrp,
         c_x      TO wa_marax-item_cat,
         c_x      TO wa_marax-size_dim,
         c_x      TO wa_marax-doc_vers,
         c_x      TO wa_marax-pur_valkey.
ENDFORM.                    " MOVE_CLIENTDATA
*&      Form MOVE_STORAGELOCATIONDATA
      * Move storage location data to STORAGELOCATIONDATA
FORM move_storagelocationdata .
CLEAR: wa_mard,wa_mardx.
MOVE : wa_final-werks      TO wa_mard-plant,
         wa_final-lgort      TO wa_mard-stge_loc.
MOVE : wa_final-werks      TO wa_mardx-plant,
         wa_final-lgort      TO wa_mardx-stge_loc.
ENDFORM.                    " MOVE_STORAGELOCATIONDATA
*&      Form MOVE_SALESDATA
     * Move Salesdate to SALESDATA
FORM move_salesdata .
MOVE : wa_final-vkorg      TO wa_mvke-sales_org,
         wa_final-vtweg      TO wa_mvke-distr_chan,
         wa_final-dwerk      TO wa_mvke-delyg_plnt,
         wa_final-versg      TO wa_mvke-matl_stats,
         wa_final-ktgrm      TO wa_mvke-acct_assgt,
         wa_final-mtpos      TO wa_mvke-item_cat,
         wa_final-mvgr1      TO wa_mvke-matl_grp_1,
         wa_final-mvgr2      TO wa_mvke-matl_grp_2,
         wa_final-mvgr3      TO wa_mvke-matl_grp_3,
         wa_final-mvgr4      TO wa_mvke-matl_grp_4,
         wa_final-mvgr5      TO wa_mvke-matl_grp_5,
         wa_final-vrkme      TO wa_mvke-sales_unit.
MOVE : wa_final-vkorg      TO wa_mvkex-sales_org,
         wa_final-vtweg      TO wa_mvkex-distr_chan,
         c_x                 TO wa_mvkex-delyg_plnt,
         c_x                 TO wa_mvkex-matl_stats,
         c_x                 TO wa_mvkex-acct_assgt,
         c_x                 TO wa_mvkex-item_cat,
         c_x                 TO wa_mvkex-matl_grp_1,
         c_x                 TO wa_mvkex-matl_grp_2,
         c_x                 TO wa_mvkex-matl_grp_3,
         c_x                 TO wa_mvkex-matl_grp_4,
         c_x                 TO wa_mvkex-matl_grp_5,
         c_x                 TO wa_mvkex-sales_unit.
ENDFORM.                    " MOVE_SALESDATA
*&      Form MOVE_MATERIALDESCRIPTION
      * Move MATERIALDESCRIPTION to Material Description
FORM move_materialdescription .
CLEAR: wa_makt,i_makt.
MOVE : wa_final-maktx TO wa_makt-matl_desc,
         sy-langu       TO wa_makt-langu.
APPEND wa_makt TO i_makt.
CLEAR wa_makt.
ENDFORM.                    " MOVE_MATERIALDESCRIPTION
*&      Form basic_data
FORM basic_data .
**-- Move Material Data at Storage Location Level
PERFORM move_storagelocationdata .
MOVE : wa_final-vkorg      TO wa_mvke-sales_org,
         wa_final-vtweg      TO wa_mvke-distr_chan.
MOVE : wa_final-vkorg      TO wa_mvkex-sales_org,
         wa_final-vtweg      TO wa_mvkex-distr_chan.
**-- Move Material Data at Client Level
PERFORM move_clientdata .
IF ALT_UOM is not Given in flat file Move BASEUOM as ALT_UOM
IF wa_final-meinh EQ c_space.
    MOVE : wa_final-meins     TO wa_marm-alt_unit,
           wa_final-meins     TO wa_marmx-alt_unit.
ELSE.
    MOVE : wa_final-meinh      TO wa_marm-alt_unit,
            wa_final-umren      TO wa_marm-numerator.
    MOVE : wa_final-meinh     TO wa_marmx-alt_unit,
           c_x                TO wa_marmx-numerator.
ENDIF.
MOVE : wa_final-numtp      TO wa_marm-ean_cat,
         wa_final-brgew      TO wa_marm-gross_wt,
         wa_final-volum      TO wa_marm-volume,
         wa_final-voleh      TO wa_marm-volumeunit,
         wa_final-gewei      TO wa_marm-unit_of_wt.
APPEND wa_marm TO i_marm.
CLEAR wa_marm.
MOVE : c_x                TO wa_marmx-ean_cat,
         c_x                TO wa_marmx-gross_wt,
         c_x                TO wa_marmx-volume,
         c_x                TO wa_marmx-volumeunit,
         c_x                TO wa_marmx-unit_of_wt.
APPEND wa_marmx TO i_marmx.
CLEAR wa_marmx.
ENDFORM.                    " basic_data
*&      Form sales_data1
FORM sales_data1 .
Move Sales & Plant Data
MOVE : wa_final-werks      TO wa_marc-plant,
         wa_final-mtvfp      TO wa_marc-availcheck,
         wa_final-ladgr      TO wa_marc-loadinggrp,
         wa_final-prctr      TO wa_marc-profit_ctr.
MOVE : wa_final-werks      TO wa_marcx-plant,
         c_x                 TO wa_marcx-availcheck,
         c_x                 TO wa_marcx-loadinggrp,
         c_x                 TO wa_marcx-profit_ctr.
MOVE: wa_final-tragr      TO wa_mara-trans_grp,
        c_x                 TO wa_marax-trans_grp.
**-- Move Sales Data
PERFORM move_salesdata .
Move Tax Data
MOVE : 'JP'              TO wa_mlan-depcountry_iso,
        'MWAR'             TO wa_mlan-tax_type_1,
         wa_final-taklv    TO wa_mlan-taxclass_1.
APPEND wa_mlan TO i_mlan.
CLEAR wa_mlan.
ENDFORM.                    " sales_data1
*&      Form purchase_data
FORM purchase_data .
Move Plant Data
MOVE : wa_final-werks      TO wa_marc-plant,
         wa_final-werks      TO wa_marcx-plant.
Move PO data
MOVE : wa_final-ekgrp TO wa_marc-pur_group,
         wa_final-kautb TO wa_marc-auto_p_ord,
         wa_final-usequ TO wa_marc-quotausage,
         wa_final-kordb TO wa_marc-sourcelist,
         c_x             TO wa_marcx-pur_group,
         c_x             TO wa_marcx-auto_p_ord,
         c_x             TO wa_marcx-quotausage,
         c_x             TO wa_marcx-sourcelist.
MOVE: wa_final-matkl TO wa_mara-matl_group,
        wa_final-bstme TO wa_mara-po_unit,
         c_x            TO wa_marax-matl_group,
         c_x            TO wa_marax-po_unit.
ENDFORM.                    " purchase_data
*&      Form mrp_data
FORM mrp_data .
**-- Move Material Data at Storage Location Level
PERFORM move_storagelocationdata .
Move All MRP data
MOVE: wa_final-diskz TO wa_mard-mrp_ind,
        c_x            TO wa_mardx-mrp_ind.
MOVE : wa_final-werks TO wa_marc-plant,
         wa_final-dismm TO wa_marc-mrp_type,
         wa_final-dispo TO wa_marc-mrp_ctrler,
         wa_final-beskz TO wa_marc-proc_type,
         wa_final-sobsl TO wa_marc-spproctype,
         wa_final-mtvfp TO wa_marc-availcheck,
         wa_final-minbe TO wa_marc-reorder_pt,
         wa_final-fxhor TO wa_marc-pl_ti_fnce,
         wa_final-disls TO wa_marc-lotsizekey,
         wa_final-bstmi TO wa_marc-minlotsize,
         wa_final-bstma TO wa_marc-maxlotsize,
         wa_final-bstfe TO wa_marc-fixed_lot,
         wa_final-mabst TO wa_marc-max_stock,
         wa_final-ausss TO wa_marc-assy_scrap,
         wa_final-dzeit TO wa_marc-inhseprodt,
         wa_final-plifz TO wa_marc-plnd_delry,
         wa_final-webaz TO wa_marc-gr_pr_time,
         wa_final-fhori TO wa_marc-sm_key,
         wa_final-eisbe TO wa_marc-safety_stk,
         wa_final-strgr TO wa_marc-plan_strgp,
         wa_final-wzeit TO wa_marc-replentime,
         wa_final-lgfsb TO wa_marc-sloc_exprc,
         wa_final-sbdkz TO wa_marc-dep_req_id,
         wa_final-kzbed TO wa_marc-grp_reqmts,
         wa_final-miskz TO wa_marc-mixed_mrp,
         wa_final-stlal TO wa_marc-alternative_bom,
         wa_final-stlan TO wa_marc-bom_usage.
MOVE : wa_final-werks TO wa_marcx-plant,
         c_x            TO wa_marcx-mrp_type,
         c_x            TO wa_marcx-mrp_ctrler,
         c_x            TO wa_marcx-proc_type,
         c_x            TO wa_marcx-spproctype,
         c_x            TO wa_marcx-availcheck,
         c_x            TO wa_marcx-reorder_pt,
         c_x            TO wa_marcx-pl_ti_fnce,
         c_x            TO wa_marcx-lotsizekey,
         c_x            TO wa_marcx-minlotsize,
         c_x            TO wa_marcx-maxlotsize,
         c_x            TO wa_marcx-fixed_lot,
         c_x            TO wa_marcx-max_stock,
         c_x            TO wa_marcx-assy_scrap,
         c_x            TO wa_marcx-inhseprodt,
         c_x            TO wa_marcx-plnd_delry,
         c_x            TO wa_marcx-gr_pr_time,
         c_x            TO wa_marcx-sm_key,
         c_x            TO wa_marcx-safety_stk,
         c_x            TO wa_marcx-plan_strgp,
         c_x            TO wa_marcx-replentime,
         c_x            TO wa_marcx-sloc_exprc,
         c_x            TO wa_marcx-dep_req_id,
         c_x            TO wa_marcx-grp_reqmts,
         c_x            TO wa_marcx-mixed_mrp,
         c_x            TO wa_marcx-alternative_bom,
         c_x            TO wa_marcx-bom_usage.
ENDFORM.                    " mrp_data
*&      Form accounting_data
FORM accounting_data .
Move Plant Data
MOVE: wa_final-werks TO wa_marc-plant,
        wa_final-werks TO wa_marcx-plant.
Move Account Data
MOVE : wa_final-werks TO wa_mbew-val_area,
          wa_final-bklas TO wa_mbew-val_class,
          wa_final-vprsv TO wa_mbew-price_ctrl,
          wa_final-verpr TO wa_mbew-moving_pr,
          wa_final-peinh TO wa_mbew-price_unit,
          wa_final-stprs TO wa_mbew-std_price.
MOVE : wa_final-werks TO wa_mbewx-val_area,
          c_x TO wa_mbewx-val_class,
          c_x TO wa_mbewx-price_ctrl,
          c_x TO wa_mbewx-moving_pr,
          c_x TO wa_mbewx-price_unit,
          c_x TO wa_mbewx-std_price.
ENDFORM.                    " accounting_data
*&      Form cost_data
FORM cost_data .
Move Plant Data
MOVE: wa_final-werks TO wa_marc-plant,
        wa_final-awsls TO wa_marc-variance_key,
        wa_final-verid TO wa_marc-prodverscs,   " Production Version
        wa_final-werks TO wa_marcx-plant,
        c_x            TO wa_marcx-variance_key,
        c_x            TO wa_marcx-prodverscs.
Move Cost Data
MOVE : wa_final-werks TO wa_mbew-val_area,
          wa_final-bklas TO wa_mbew-val_class,
          wa_final-vprsv TO wa_mbew-price_ctrl,
          wa_final-ekalr TO wa_mbew-qty_struct.
MOVE : wa_final-werks TO wa_mbewx-val_area,
          c_x            TO wa_mbewx-val_class,
          c_x            TO wa_mbewx-price_ctrl,
          c_x            TO wa_mbewx-qty_struct.
ENDFORM.                    " cost_data
Call All Structures in to BAPI
CALL FUNCTION 'BAPI_MATERIAL_SAVEDATA'
    EXPORTING
      headdata             = wa_mathead
      clientdata           = wa_mara
      clientdatax          = wa_marax
      plantdata            = wa_marc
      plantdatax           = wa_marcx
      storagelocationdata = wa_mard
      storagelocationdatax = wa_mardx
      valuationdata        = wa_mbew
      valuationdatax       = wa_mbewx
      salesdata            = wa_mvke
      salesdatax           = wa_mvkex
    IMPORTING
      return               = i_return
    TABLES
      materialdescription = i_makt
      unitsofmeasure       = i_marm
      unitsofmeasurex      = i_marmx
      taxclassifications   = i_mlan.
IF i_return-type = 'A' OR i_return-type = 'E' .
    DATA : l_v_string TYPE string,
           l_v_msg1   TYPE string,
           l_v_msg2   TYPE string.
    MOVE i_return-message TO l_v_string.
    CONDENSE l_v_string.
    PERFORM fill_error_table USING 'E'
                                   'ZMSG_MM'
                                   '098'
                                   v_reccon
                                   l_v_string
    v_error = v_error + 1.
    CLEAR: l_v_string.
ELSEIF i_return-type = 'S'.
    PERFORM fill_error_table USING 'S'
                                         i_return-id
                                         i_return-number
                                        i_return-message_v1
                                       i_return-message_v2
                                       i_return-message_v3
                                       i_return-message_v4.
    v_success = v_success + 1.
ENDIF .
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
    EXPORTING
      wait = 'X'.
IF sy-subrc = 0.
    COMMIT WORK AND WAIT.      "for the update to table Transcation
ENDIF.
Regards,
Siva.

Using BAPI to upload Equipment Master (IE01)

Similar Messages

Maybe you are looking for