Material type in Material master

When we create a new MM, we have to select material type. Here we have different material types like HAWA, FERT etc.. if for our convenience if we want the Description of the Material type to be proposed along with code i.e Like HAWA - Trading goods. where to make this setting?
Venkat

Hi Venkat,
Hi Go to <b>IMG</b> then go to <b>Customising of local layout Icon (Alt+F12)</b> which is next to <b>help icon</b> in the menu bar.
Then click on that you will get list of Menu's, Select <b>OPTION</b> Menu there You will get a POP Screen,, there you select <b>Expert Tab</b>, in that You will have <b>Controls</b> in that you <b>select the check box for Show Keys in all drop down list</b> and click on <b>Apply</b> and then click on <b>Ok.</b>
Now if you go to <b>MM01</b> you can See also with <b>Material Type Description</b> you can see the <b>Type</b> also.
Cheers Buddy..
Regards
MBS

Similar Messages

  • Change documents of material master classification class type 001 and 300

    Dear guru ,
    I want to see the history of change documents of material master classification using MM02.
    The system allow to see the history only for class type 023.
    For class type 001 or 300 the change document isnu2019t available.
    I must do some settings or the function for these class type arenu2019t available ?
    Thanks.

    Dear ,
    changes in values for a characteristic can be monitored in CL20N but as for MM02/MM03 transaction only for class type 023.
    For class type 001 or 300 the change document isnu2019t available.
    Thanks.

  • Creation of Material Master for a material with Material Type NLAG

    Hello Sirs,
         I have to create a material which will be consumed directly. I would use the
    material type NLAG (Non stock material). If I create a material with this material type, will it contain an Accounting view where in I can maintain the price of the
    material? If it contains an Accounting view, which type of Price control should be
    used (Moving average or Standard)? Further, can we maintain an info record for
    a material with material type NLAG?How the price updation happens?
    Regards
    Yoga

    Hi Madhu,
        Thanks for your reply. But, I have one more doubt. For non stock materials, we
    will specify the cost centre and G/L account at the time of creation of Purchase order. Then, do we have to specify the valuation class at the time of creation of
    Material Master since there is no automatic account determination?
    Regards
    Yoga

  • Custom - Material Master Update using an IDOC (Message Type - MATMAS_BAPI)

    Hello everyone,
    I was writing a functional specs. Basically, I want to update the material master MM02 using an IDOC (MATMAS_BAPI01 - Basic Type & MATMAS_BAPI - Message Type). This is currently working.
    To my understanding, this currently uses function module - BAPI_IDOC_INPUT1 to update the material master after the IDOC is posted to SAP ECC from XI system.
    Now I want to add one small validation logic before it actually updates the material master (MM02).
    I looked around and found one exit - EXIT_SAPLMV02_002 in enhancement MGV00001. I was almost sure that this EXIT can be used to write the custom validation code before, actual MM02 updation.
    However while trying to establish a link between this EXIT and BAPI_IDOC_INPUT1, I found that EXIT_SAPLMV02_002 is actually a part of another function module - IDOC_INPUT_MATMAS01 and not BAPI_IDOC_INPUT1. I am stuck here if adding the custom logic in the exit really going to work.
    a bit of googling and I found from WE30 that the purpose of both these function modules are actually different. While BAPI_IDOC_INPUT1  actually create & updates the material master (also plant specific master data which is my need), IDOC_INPUT_MATMAS01 is just for maintenence of few fields in MM02 (may be custom fields).
    Can anyone point out if my thing is in right direction?
    Also please offer any solution where shall I put the Custom Logic in the EXIT or the some variants of
    BAPI_IDOC_INPUT1.
    A less technical explanation would be appreciated as I come from a functional background and invloved in this for writing the func specs. I want to make it sure that what I write is not useless and makes some sense.
    Thanks in advance,
    Arunesh

    Hi Lalit,
    Did some head breaking with the function module - BAPI_IDOC_INPUT1 to check whether it is calling the EXIT_SAPLMV02_002 internally. Couldn't get anywhere.
    On question of another EXIT in BAPI_IDOC_INPUT1, I don't see any. I am not very proficient in ABAP code, I must say though.
    I found the list of exits from google, almost same list everywhere.
    http://www.sapfans.com/forums/viewtopic.php?f=21&t=296637
    here I got the EXIT, I am talking about.
    Any other way to find either the EXIT or link the above?
    -- Arunesh

  • MRP TYPE for  Periodic planning in the material master.

    Dear gurus,
    i need planned the materials in the periodic modality, are there the type MRP in the material master for create the planned file ( table MDVM) one once a month or in the specific period chose ?
    Example :
    I need that the material master don't create a file planned ( MD20- TABLE MDVM) for a change of the requirement situation new , but i would like that the flag in the table ( MDVM) or file of the planning MRP created when the today date is in the period specific.
    31.3.2011  (or period 1.4.2011- 10-4-2011)Date for the create a file MRP and after when run MRP planned the material, for others scenary the system must not planned the material.
    Are there the MRP type for my problem? Or the customizing setting?
    Thanks a lot
    Dani

    Dani,
    Not sure if MRP type or customizing can help here. And even if we are able to achieve this requirement it will be applicable at plant level.
    However, try exploring option of periodic lot size (weekly, monthly, etc). This will work according to period you've set and should give you the results you are looking for.
    Regards,
    Himanshu

  • Authorization object M_MATE_MAR "Material Master - Material Types" in MM01

    Hi,
    We in CPS Energy are implementing VIrsa SOD conflicts on the roles that are in place in current SAP 4.6C version. The authorization object M_MATE_MAR is used by MM01(Creation of Material Master) transaction code & used at mutiple roles. We have restricted this authorization object by Material Type Authorization Group (BEGRU)as WMS1 & given activity a 01, 02 & 03 in a role. The same authorization object is used in Common roles also for displaying that is using transaction code MM03 (Display Material) but the activity & authorization group are ''. This '' is taking precedence over the the authorization object given in the other role.
    Please let us know how to put a control on this authorization object which is used widely by large number of users.
    Maintained Material Master: Material Types                              T-D119010802
    Activity                       01, 02, 03                                             ACTVT
    Authorization group          WMS1                                              BEGRU
    Any help is really appreciated
    Thanks
    Sree

    Hi Sree, your role with MM03 in it should not have * for actvt if it is only a display role.
    As it is a display role actvt 03 would be more suitable.  That way you could have display for all auth groups, but create and change/MM01&2 would be restricted to WMS1 (and any other materials with a blank auth group)

  • Kindly give authorization object for mrp type in material master

    Hi friends,
    Kind tell me what is the authorization object for MRP type in material master.
    Your help is considered more important.
    thanks in advance
    willaims

    hi,
    check your authorisation objects here:
    Go to PFCG --> Environment (at menu bar) --> authorization objects --> Display...
    Here see for MRP and MM for material managament in the tree structure...
    Regards
    Priyanka.P

  • Authorization material type in material master

    Hi expert,
    I want to know how to restrict users to create/change Material Master following
    the material type in the role.
    In role authorization Object: M_MATE_MAR Material Master: Material Types.
    I maintain material type like ROH , HALB , HAWA in authorization Group.
    But it is not work. Please help me.
    Thanks,

    Hi,
    Pl. check your role to users for the material master again for allowed material types. It should restrict the users only for the selected views only. This should be done for all the roles assigned to users in relation to materail master. (i.e. Create, Display & CHange). If you restrict the material type in create role only & it is not restricted in display role, then user will be able to create all the material types. hence restrict the material types in all roles related to material master (create, change, display) assigned to the user.
    Regards,
    Prashant

  • In Material Master Screen,functionally what is Picking Storage type in the

    In Material Master Screen,functionally what is Picking Storage type in the Warehouse Management Screen.Pls explain its functionality

    This indicator points to the customizing of picking strategies. This way SAP knows which picking strategy to take for a particular material, as the picking strategy may differ from material to material

  • Valuation type in material master

    Dear SAP GURU'S
    please tell me what is a valuation type, it's uses and what are it's setting so that i can get the valuation type in material master.
    thanks and regards.

    Hi Yogesh ,
    Valuation type  is A subdivision of a valuation category in split valuation.
    Example
    An enterprise manages its stocks of a material using the valuation category "Quality", comprising the following valuation types:
    High quality
    Average quality
    Inferior quality
    Valuation category: A criterion for the separate valuation of different stocks of a material managed under one material number for quality and other purpose ...
    If you have any further query on the same then let us know ........
    Thanks
    Kaushik

  • Wrong procurement type showing in the material master

    Hi,
    I am creating a material Procurement type is comming as E in the MRP2 view, To where it is comming?
    I have checked the material type setting in the tcode OMS2 and it below are showing there:
    Ext. purchase orders   2
    Int. purchase orders   2
    Hence it's allowed int. and ext. proc. then why in the material master procurement type is comming E not X.
    How can I change it?

    Check to see if you have assigned an MRP Profile which has defaulted Procurement Type. If this is the case, you will have to remove the MRP Profile before you can change the entry. Or you can maintain the MRP Profile by deselecting "Write-protected in material maintenance" and selecting "Only default value in material maintenance" for Procurement Type. The Transaction is MMD2.
    BR,
    Krishna

  • Material Master Extension to all the plants of same type

    Hi
    In the given scenario, we have  almost 200 plants where same materials are required , now when we create material master using Tcode MM01 we want to extend this material master to all the plants of same type in one go .Is it possible , if yes , how to go about it ?? please help, this is the specific customer requirment .
    ans will be rewarded
    rgds
    mojib

    Hi,
    Just go through the code
    report ZMM_FERT_CREATE_EXT_PLANT
           no standard page heading line-size 255.
    *include bdcrecx1.
    DATA : it_bdcdata LIKE bdcdata OCCURS 0 WITH HEADER LINE,
           it_bdcmsgcoll LIKE bdcmsgcoll OCCURS 0 WITH HEADER LINE.
    data : p_filex type string .
    types: BEGIN OF t_mm01,
            matnr(018),
            MAKTX(040),
            mtart(004),
            matkl(009),
            WGBEZ(020),
            bklas(004),
            vprsv(001),
            werks(004),
            vkorg(004),
            vtweg(002),
            sktof(001),
            versg(001),
            kondm(002),
            ktgrm(002),
            meins(003),
            gewei(003),
            j_1ichid(012),
            j_1isubind(001),
            j_1icapind(001),
            j_1igrxref(001),
            tragr(004),
            ladgr(004),
            mtvfp(002),
            xchpf(001),
            mtpos_mara(004),
            mtpos(004),
            ekgrp(003),
            BWTTY(010),
            meins1(003),
            meins2(003),
            meins3(003),
            sales_txt(040),
            purc_txt(040),
            mbrsh(001),
            verpr(015),
            peinh(006),
            stprs(015),
            brgew(017),
            ntgew(017),
            j_1ivalass(018),
            umrez1(006),
            umren1(006),
            umrez2(006),
            umren2(006),
            umrez3(006),
            umren3(006),
            lgort(004),
            TAXKM1(001),
            TAXKM2(001),
            HERKL(003),
            HERKR(003),
            J_1IMOOM(018),
          end of t_mm01.
    DATA : it_mm01 type table of t_mm01 with header line initial size 0.
    *Selection Screen                                              *
      SELECTION-SCREEN BEGIN OF BLOCK B WITH FRAME TITLE text-001.
                PARAMETERS: p_file like IBIPPARMS-PATH obligatory.
      SELECTION-SCREEN:END OF BLOCK B.
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file .
      PERFORM get_filename.
    *START-OF-SELECTION
      START-OF-SELECTION.
       PERFORM upload_data.
       PERFORM fill_data.
    *&      Form  upload_data
    *       text
    *  -->  p1        text
    *  <--  p2        text
    form upload_data .
    p_filex = p_file.
    CALL FUNCTION 'GUI_UPLOAD'
      EXPORTING
        filename                      = p_filex
        FILETYPE                      = 'ASC'
        HAS_FIELD_SEPARATOR           = '#'
    *   HEADER_LENGTH                 = 0
    *   READ_BY_LINE                  = 'X'
    *   DAT_MODE                      = ' '
    *   CODEPAGE                      = ' '
    *   IGNORE_CERR                   = ABAP_TRUE
    *   REPLACEMENT                   = '#'
    *   CHECK_BOM                     = ' '
    *   NO_AUTH_CHECK                 = ' '
    * IMPORTING
    *   FILELENGTH                    =
    *   HEADER                        =
      tables
        data_tab                      = it_mm01
    EXCEPTIONS
       FILE_OPEN_ERROR               = 1
       FILE_READ_ERROR               = 2
       NO_BATCH                      = 3
       GUI_REFUSE_FILETRANSFER       = 4
       INVALID_TYPE                  = 5
       NO_AUTHORITY                  = 6
       UNKNOWN_ERROR                 = 7
       BAD_DATA_FORMAT               = 8
       HEADER_NOT_ALLOWED            = 9
       SEPARATOR_NOT_ALLOWED         = 10
       HEADER_TOO_LONG               = 11
       UNKNOWN_DP_ERROR              = 12
       ACCESS_DENIED                 = 13
       DP_OUT_OF_MEMORY              = 14
       DISK_FULL                     = 15
       DP_TIMEOUT                    = 16
       OTHERS                        = 17
    IF sy-subrc <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    endform.                    " upload_data
    *&      Form  get_filename
    *       text
    *  -->  p1        text
    *  <--  p2        text
    form get_filename .
    CALL FUNCTION 'F4_FILENAME'
                   EXPORTING
                     PROGRAM_NAME        = SYST-CPROG
                     DYNPRO_NUMBER       = SYST-DYNNR
    *                 FIELD_NAME          = p_file
                   IMPORTING
                     FILE_NAME           = p_file .
                   if sy-subrc NE 0  .
                      write : / 'Enter File Name'.
                   endif.
    endform.                    " get_filename
    *&      Form  fill_data
    *       text
    *  -->  p1        text
    *  <--  p2        text
    form fill_data .
    *perform open_group.
    loop at it_mm01.
      clear it_bdcdata.
    refresh it_bdcdata.
    perform bdc_dynpro      using 'SAPLMGMM' '0060'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'RMMG1-MTART'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '=ENTR'.
    perform bdc_field       using 'RMMG1-MATNR'
                                   it_mm01-matnr.
    *                              '116100'.
    perform bdc_field       using 'RMMG1-MBRSH'
                                  'C'.
    perform bdc_field       using 'RMMG1-MTART'
                                  'FERT'.
    perform bdc_dynpro      using 'SAPLMGMM' '0070'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'MSICHTAUSW-DYTXT(16)'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '=ENTR'.
    perform bdc_field       using 'MSICHTAUSW-KZSEL(03)'
                                  'X'.
    perform bdc_field       using 'MSICHTAUSW-KZSEL(05)'
                                  'X'.
    perform bdc_field       using 'MSICHTAUSW-KZSEL(06)'
                                  'X'.
    perform bdc_field       using 'MSICHTAUSW-KZSEL(07)'
                                  'X'.
    perform bdc_field       using 'MSICHTAUSW-KZSEL(09)'
                                  'X'.
    perform bdc_field       using 'MSICHTAUSW-KZSEL(10)'
                                  'X'.
    perform bdc_field       using 'MSICHTAUSW-KZSEL(13)'
                                  'X'.
    perform bdc_field       using 'MSICHTAUSW-KZSEL(16)'
                                  'X'.
    perform bdc_dynpro      using 'SAPLMGMM' '0080'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'RMMG1-VTWEG'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '=ENTR'.
    perform bdc_field       using 'RMMG1-WERKS'
                                   it_mm01-werks.
    *                              '9010'.
    perform bdc_field       using 'RMMG1-LGORT'
                                   it_mm01-lgort.
    *                              'F901'.
    perform bdc_field       using 'RMMG1-VKORG'
                                   it_mm01-vkorg.
    *                              '1000'.
    perform bdc_field       using 'RMMG1-VTWEG'
                                   it_mm01-vtweg.
    *                              '03'.
    perform bdc_dynpro      using 'SAPLMGMM' '4000'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '/00'.
    perform bdc_field       using 'MAKT-MAKTX'
                                    it_mm01-maktx.
    *                              'Test ACEPHATE TECHNICAL 50kg'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'MVKE-MTPOS'.
    perform bdc_field       using 'MVKE-VERSG'
                                    it_mm01-versg.
    *                              '1'.
    perform bdc_field       using 'MVKE-KONDM'
                                    it_mm01-kondm.
    *                              '03'.
    perform bdc_field       using 'MVKE-KTGRM'
                                   it_mm01-ktgrm.
    *                              '01'.
    perform bdc_field       using 'MVKE-MTPOS'
                                    it_mm01-mtpos.
    *                              'NORM'.
    perform bdc_dynpro      using 'SAPLMGMM' '4000'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '/00'.
    perform bdc_field       using 'MAKT-MAKTX'
                                    it_mm01-maktx.
    *                              'Test ACEPHATE TECHNICAL 50kg'.
    perform bdc_field       using 'MARC-MTVFP'
                                   it_mm01-mtvfp.
    *                              '01'.
    perform bdc_field       using 'MARC-XCHPF'
                                   it_mm01-xchpf.
    *                              'X'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'MARC-LADGR'.
    perform bdc_field       using 'MARC-LADGR'
                                   it_mm01-ladgr.
    *                              '0003'.
    perform bdc_dynpro      using 'SAPLMGMM' '4004'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '/00'.
    perform bdc_field       using 'MAKT-MAKTX'
                                    it_mm01-maktx.
    *                              'Test ACEPHATE TECHNICAL 50kg'.
    perform bdc_field       using 'MARC-HERKL'
                                   it_mm01-HERKL.
    *                              'IN'.
    perform bdc_field       using 'MARC-HERKR'
                                   it_mm01-HERKR.
    *                              '01'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'J_1IASSVAL-J_1IVALASS'.
    perform bdc_field       using 'J_1IMTCHID-J_1ICHID'
                                   it_mm01-J_1ICHID.
    *                              '2913 00 90'.
    perform bdc_field       using 'J_1IMTCHID-J_1ISUBIND'
                                    it_mm01-J_1ISUBIND .
    *                              'X'.
    perform bdc_field       using 'J_1IMTCHID-J_1ICAPIND'
                                    it_mm01-J_1ICAPIND.
    *                              'F'.
    perform bdc_field       using 'J_1IMTCHID-J_1IGRXREF'
                                     it_mm01-J_1IGRXREF .
    *                              '2'.
    if  it_mm01-J_1IVALASS <> '0'.
    perform bdc_field       using 'J_1IASSVAL-J_1IVALASS'
                                    it_mm01-J_1IVALASS.
    *                              '0'.
    endif.
    perform bdc_dynpro      using 'SAPLMGMM' '4000'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '/00'.
    perform bdc_field       using 'MAKT-MAKTX'
                                   it_mm01-maktx.
    *                              'Test ACEPHATE TECHNICAL 50kg'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'MARC-EKGRP'.
    perform bdc_field       using 'MARC-EKGRP'
                                   it_mm01-ekgrp.
    *                              '002'.
    perform bdc_field       using 'MARC-XCHPF'
                                   it_mm01-xchpf.
    *                              'X'.
    perform bdc_dynpro      using 'SAPLMGMM' '4000'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '/00'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'MAKT-MAKTX'.
    perform bdc_field       using 'MAKT-MAKTX'
                                   it_mm01-maktx.
    *                              'Test ACEPHATE TECHNICAL 50kg'.
    perform bdc_field       using 'MARC-STEUC'
                                   it_mm01-J_1ICHID.
    *                              '2913 00 90'.
    perform bdc_field       using 'MARC-HERKL'
                                    it_mm01-HERKL.
    *                              'IN'.
    perform bdc_field       using 'MARC-HERKR'
                                   it_mm01-HERKR.
    *                              '01'.
    perform bdc_field       using 'J_1IMTCHID-J_1ICHID'
                                   it_mm01-J_1ICHID.
    *                              '2913 00 90'.
    perform bdc_field       using 'J_1IMTCHID-J_1ISUBIND'
                                    it_mm01-J_1ISUBIND.
    *                              'X'.
    perform bdc_field       using 'J_1IMTCHID-J_1ICAPIND'
                                   it_mm01-J_1ICAPIND.
    *                              'F'.
    perform bdc_field       using 'J_1IMTCHID-J_1IGRXREF'
                                    it_mm01-J_1IGRXREF.
    *                              '2'.
    perform bdc_dynpro      using 'SAPLMGMM' '4000'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '/00'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'MAKT-MAKTX'.
    perform bdc_field       using 'MAKT-MAKTX'
                                   it_mm01-maktx.
    *                              'Test ACEPHATE TECHNICAL 50kg'.
    perform bdc_field       using 'MARC-XCHPF'
                                    it_mm01-xchpf.
    *                              'X'.
    *perform bdc_field       using 'MARA-IPRKZ'
    *                              'D'.
    perform bdc_dynpro      using 'SAPLMGMM' '4000'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '/00'.
    perform bdc_field       using 'MAKT-MAKTX'
                                    it_mm01-maktx.
    *                              'Test ACEPHATE TECHNICAL 50kg'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'MBEW-STPRS'.
    perform bdc_field       using 'MBEW-BKLAS'
                                    it_mm01-bklas.
    *                              '7930'.
    perform bdc_field       using 'MBEW-VPRSV'
                                    it_mm01-vprsv.
    *                              'S'.
    perform bdc_field       using 'MBEW-PEINH'
                                    it_mm01-peinh.
    *                              '1'.
    perform bdc_field       using 'MBEW-VERPR'
                                    it_mm01-verpr.
    *                              '273.75'.
    perform bdc_field       using 'MBEW-STPRS'
                                   it_mm01-stprs.
    *                              '207'.
    perform bdc_dynpro      using 'SAPLSPO1' '0300'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '=YES'.
    CALL TRANSACTION 'MM01' USING it_bdcdata
                                    MODE 'A'
                                    UPDATE 'A'
                                    MESSAGES INTO it_bdcmsgcoll.
    CLEAR it_mm01.
    endloop.
    *perform bdc_transaction using 'MM01'.
    *perform close_group.
    endform.                    " fill_data
    *&      Form  bdc_dynpro
    *       text
    *      -->P_0297   text
    *      -->P_0298   text
    form bdc_dynpro  USING prog scr.
    CLEAR it_bdcdata.
      it_bdcdata-program = prog.
      it_bdcdata-dynpro  = scr.
      it_bdcdata-dynbegin = 'X'.
      APPEND it_bdcdata.
    endform.                    " bdc_dynpro
    *&      Form  bdc_field
    *       text
    *      -->P_0687   text
    *      -->P_IT_MM01_VPRSV  text
    form bdc_field  USING fnam fval.
    CLEAR it_bdcdata.
      it_bdcdata-fnam = fnam.
      it_bdcdata-fval  = fval.
      APPEND it_bdcdata.
    endform.                    " bdc_field
    Regards,
    Madhu.

  • Material master/Output type IDOC /MATMAS

    Hello ,
    I want to generate Idoc(MATMAS) whenever a material is created or changed. I could do the same for ME21N/ME22N for PO with PO idoc. Would like to know whether there is output types for material master or anything else so that i can generate Idoc for my senario.
    Thanks for ur time.
    Jeeva.

    Hi,
    the configurations which we do for material master is below...we don't give any output for material master,becoz its a master data not transactional data..
            For distributing master data like material master, vendor master, customer master we have standard transaction codes that are provided by sap.
    Bd10(send material master)
    Bd12(send customer master)
    Bd14(send vendor master)
    Bd30(bom’s)
    The order of Tcodes are:
               Bd54 (creating logical systems)
               Scc4 (assigning logical systems )
               Sm59 (rfc destination)
               We81 ( message type)                      
               We30 ( idoc type)
               We31 ( segment type)
               We82 (linking message type and idoc type)
               We21 (creating port)
               We20 (partner profiles)
               Bd64 (Distribution model)
               Bd10 (material master)
    Ex: material master.
         Message type: matmas.
         Idoc type: matmas05.
    Rewrad if helpful.
    Regards,
    Nagaraj

  • LSMW Material Master - create several valution types within one Run

    Hello @ll,
    i created a LSMW for material master migration, and i would like to create up to 4 different accounting views (based on different valuation types) within one LSMW Run.
    As there is the Field BWTAR on Structure BMM00, and the accounting fields on Structure BMMH1 i dont know if:
    1. this is possible in general with LSMW and
    2. if possible where i have to set the "transfer_record" commands...
    Does anybody have experience on this?
    BR,
    Gregor H.

    I never used the standard batch input method, so I cant answer this part. But with IDOC as import method I do this right now and it works without any problem
    The transfer record command is set in the  section of processing time  __END_OF_RECORD__
    you can display this section when you are in field mapping and conversion rules. choose from menu Extras > Layout and activate all boxes.

  • Message Type for Material Master Data Changes

    Hi all
    I'm managing Message Types for Material Master Data extraction from R\3 system to BW system, in order to load on BW only the changes done to some fields of MARA table that are delta relevant.
    Now from R/3 BD50 Transaction I can see that there is a message type that refer to changes done on MARA fields: RS0044.
    I would like to replace this message type with another one (RS0020) in order to align different systems.
    Now changes to material master data in R/3 system are recorder with both message types but only those with RS0044 message type are processed and loaded into BW system.
    So I would like to know:
    1. How is the message type related to the DataSource 0material?
    2. is it possible to replace a message type for BW?
    3. if yes, how can I do it?
    Thanks in advance.
    Elisa
    mail: [email protected]

    Hi Oscar!
    At the moment I'm using Delta queue of 0MATERIAL. I know that in the queue there are all the new and changed records.
    But I would like to be able not to load all the changed records, but only those that refer to some fields of MARA table.
    E.g. if the gross weight of a material is modified I don't want to load this change on BW with Delta loading .
    I've seen that from R/3 Transaction BD52 you can set only delta relevant fields referred to a specific message type and to delete the other fields.
    As I'm able to do this directly in the Development system and Test System, I haven't got the authorization of doing it in the Production system.
    That's why I need to include this setting in a CR and then ask to transport it from Test to Production system.
    But message types referred to MARA field changes are different between the two systems.
    And it seems they are automatically created.
    Is it true?
    Thanks
    Elisa

  • Multiple class types for material master classification display default.

    Hello,
    We are running on R/3 4.7.  We use several different class types for our material masters (001 and Z01).  The problem this creates is the end user having to constantly tell the system which class type to use when going to the classification screen for different materials with different class types.  If a user views one material's classification page with a particular class type (001) then looks at another material with a different class type (Z01) the system tries to pull in information from the last materials class type (001).  The system tells the user there are no assignments for the class (001) in the material their viewing but there is one for class type (Z01).  The user then has to select the class type that applies to the material master their trying to view.  Is there a way for the system to automatically see when a material has only one class type assigned to it for it to automatically default it in without the user having to specify the class type?
    Thanks,
    JRW

    Hi,
    Check the configuration, have you maintained default class type for material type.
    Logistic General> Material Master> Basic Setting> Material Type> Define attributes of Material Types>Select the material type> Double click on material type--> Class type
    Edited by: P. Dhamane on Jun 4, 2010 3:21 PM

Maybe you are looking for

  • Iphone and windows xp 64

    I've been pulling my hair out for 4 days now. Is there any possible way of setting up an iphone if you have windows xp professional x64? It seems as if I am caught between regular windows xp and vista, because there doesn't appear to be a version of

  • Database Adapter ResultSet in BPEL Processing

    Hi I have an issue regarding processing a result set in BPEL. My DBAdpater returns a number of rows from a given stored procedure call and it is not that obvious, from the documentation, on how to process the results set one at a time, for example in

  • Selection in query

    HI Gurus, I have a problem. I am doing AP aging report. I want to display a field called status ( net due date - last date). Last date should be given as a variable in selection screen, but the problem is last date is not in DSO on which the report i

  • API to update/ create Organization EIT

    Hi All, I 'am trying to find the API to update/ create EITs for HR Organizations. While I can find the API to update person and assignments hr_assignment_extra_info_api/ hr_person_extra_info_api, I 'am not able to find out the API/ package for Organi

  • ABAP HR - PYXX_READ_PAYROLL_RESULT not fetching results

    My first 2 FM's are fetching the correct values . Now I am passing the SEQNR(00005 in my case) returned by 2nd FM to the 3rd FM ( PYXX_READ_PAYROLL_RESULT  ) , the table payroll remains empty.I checked in debug mode also that payroll-INTER-RT is empt