Hide views in MM01 for all material type in one time

Hi,
I have a requirement to hide the views for all material type at at time.
i tried with OMS2 , it is allowing me to do for one matrial type.
could any one tell me how to hide the views for all material type in one short.
Thanks in adv..

Hi Rakesh,
Up to my knowledge it is not possible to do view setting for all material type in one shot simply because it is material type dependent.
If trying to change fields in material master then use OMS9. This also material type linked to field reference group. And we can change the setting of field selection group in one shot. This will affect the material types linked to it.
Hope it helps
sBk

Similar Messages

  • Uploading data in MM01 for different material types

    Hi,
    I have a doubt regarding uploading the data in MM01 for different material types.
    Generally in MM01, we have different views for different material types. The number of views will vary depending upon the material type that we select.
    I have a scenario, where in to upload the data, I have a flat file that consists of data for different message types. So, how to upload the data in such case.
    Can anyone help me on the same by providing explanation or sample code...? What would be the possible ways to upload data in such scenario.
    That would be of great help.
    Thanks & Regards,
    Pradeep.

    See the below code and use FM SELECTION_VIEWS_FIND..
    REPORT zjpmuim306 NO STANDARD PAGE HEADING LINE-SIZE 250 MESSAGE-ID
    zjpm001.
    *&   I N B O U N D  V I A   A B A P : Batch input Session method     *
    *&   Development ID: IM_DD_306_LJP                                   *
    *&   Report        : ZJPMUIM306                                      *
    *&   The Purpose of the Object is to interface Create Input Record   *
    *&   for SAP Migration from the Material master of BPCS All the      *
    *&   information received at BPCS is collected into a single record. *
    *&   By using session method upload data from file ,one item is
    *&   created for one record                                          *
    *&   Change Log:                                                     *
    *&   Init       Who              Date         Text                   *
    *&  MALIKDH1   Seshu Reddy    26-07-2003   Initial Version           *
                             Constants                                   *
    CONSTANTS:c_vkorg(4) type c value 'JP20',        " Sales Organization
              c_vtweg(2) type c value 'TR' ,         " Distribution Channel
              c_werks(4) Type c value 'JP01' ,       " Plant
              c_viewlist(15) VALUE 'KDEALBSZXVPCFQG'," View list
              c_scm_view TYPE msichtausw-dytxt VALUE 'SCM View',
              c_sd_view TYPE msichtausw-dytxt VALUE 'SD View',
              c_seq_code(2) VALUE 'Z1',              " Sequential Code
              c_keep(1) TYPE c VALUE  'X',           " Keep
              c_group LIKE apqi-groupid VALUE 'IM306', " Session Name
              c_tcode  LIKE tstc-tcode VALUE 'MM02',  " Transaction Code
              c_blank(1) VALUE ' ',                   " Blank
              c_intls(1) VALUE 'N'.                  " Logistic Status
                  Variables                                      *
    DATA: g_flag1(1),  " Variable to hold
          g_flag(1),   " Variable to hold
          g_file LIKE rlgrap-filename VALUE
         'C:\Documents and Settings\seshur\Desktop\HCLT123.CSV'. " File name
           Internal tables/ Work area                           *
    Internal Table for Delimter
    DATA : BEGIN OF t_delim OCCURS 0,
           text(1000),
           END OF t_delim.
    Internal table for BDC processing
    DATA : t_bdcdata LIKE bdcdata OCCURS 0 WITH HEADER LINE.
    Internal table for holding the data which has to be uploaded.
    DATA: BEGIN OF t_bpcs OCCURS 0,
          matnr(15) TYPE c,  " material no
          dosage(40) TYPE c, " Dosage form(Local)
          appearance(40) TYPE c, " Appearance
          idcode(6) TYPE c,     " Identification Code
          prostformno(10) TYPE c, "SOP
          weitab(7) TYPE c,    " Weight/tablet
          uom1(2) TYPE c,     " UOM of Carton
          uom2(2) TYPE c,     " UOM of Case
          carsize(14) TYPE c, " Carton size
          cassize(14) TYPE c, " Case size
          rupqty(11) TYPE c,  " Round up
          abvname(3) TYPE c,  " Product short name
          END OF t_bpcs.
    *Internal table for t_bpcs
    DATA: BEGIN OF t_mdata OCCURS 0,
          matnr  LIKE marc-matnr, " Material number
          zzjp_dos_frm LIKE marc-zzjp_dos_frm, " Dosage form(Local)
          zzjp_aprn LIKE marc-zzjp_aprn, " Appearance
          zzjp_con_id LIKE marc-zzjp_con_id," Identification Code
          zzjp_nyu_sop LIKE marc-zzjp_nyu_sop,"SOP
          zzjp_wei_tab(10) type c , " Weight/tablet
          zzjp_bio  LIKE marc-zzjp_bio,"Biologics Indicator
          zzjp_itf LIKE marc-zzjp_itf, " ITF code
          zzjp_car(2) type c, " UOM of Carton
          zzjp_cas(2) type c, " UOM of Case
          zzjp_car_size(11) type c," Carton size
          zzjp_cas_size(11) type c, " Case size
          zzjp_rupqty(11) type c,  " Round up
          zzjp_init_ls LIKE marc-zzjp_init_ls, " Logistic Status
          zzjp_re1 LIKE marc-zzjp_re1, "Document type(Local)
          zzjp_re2 LIKE marc-zzjp_re2, "Report type
          zzjp_re3 LIKE marc-zzjp_re3, "Shipping report type
          zzjp_pro_id LIKE mvke-zzjp_pro_id," Product output sequence
          zzjp_bu_id LIKE mvke-zzjp_bu_id, " Business unit indicator
          zzjp_abv_name LIKE mvke-zzjp_abv_name," Product short name
          zzjp_abv_id1 LIKE mvke-zzjp_abv_id1," Product short name output
          zzjp_abv_id2 LIKE mvke-zzjp_abv_id2," Product short name internal
          zzjp_spl_id LIKE mvke-zzjp_spl_id,  " Sample internal order
          END OF t_mdata.
    Internal table for Mara Table
    DATA: BEGIN OF t_mara OCCURS 0,
          matnr LIKE mara-matnr,  " material Number
          vpsta LIKE mara-vpsta,  " Maintenance status of complete material
          pstat like mara-pstat,  " Maintenance status
          END OF t_mara.
    Internal table for Material Master View Selection Screens
    DATA: BEGIN OF t_bildtab OCCURS 0.
            INCLUDE STRUCTURE mbildtab.
    DATA: END OF t_bildtab.
    internal table for T_bildtab
    DATA: t_bildtab_dup LIKE t_bildtab OCCURS 0 WITH HEADER LINE.
    *Work area for T_bildtab internal table(Views Selection)
    DATA: BEGIN OF w_data,
          flag1 type c,
          anzd70 TYPE i,
          field1(20) type c,
          field2(20) type c,
          field3(20) type c,
          field4(20) type c,
          count(2) TYPE c,
          END OF w_data.
                Main Processing                           *
    START-OF-SELECTION.
    Store data from file into internal table
      PERFORM f_uplaod_data.
    Transfer the uploaded data into t_mdata internal Table
      PERFORM f_process_data.
    Selecting The views based on Material number
      PERFORM f_view_list.
    Open a BDC Session
      PERFORM f_bdc_open.
    *Selecting the fields from mara table
      SELECT matnr
             vpsta
             pstat
        FROM mara
      INTO TABLE t_mara
      FOR ALL ENTRIES IN t_mdata
      WHERE matnr = t_mdata-matnr.
      SORT t_mara BY matnr.
      SORT t_mdata BY matnr.
    Transfer the uploaded data into BDCDATA structure
      PERFORM f_process_bdc.
    Close The BDC Session
      PERFORM f_close_group.
    *&      Form  F_VIEW_LIST                                             *
             Routine to used for Calling the function module            *
              Selection_views_find                                      *
    FORM f_view_list.
      CALL FUNCTION 'SELECTION_VIEWS_FIND'
           EXPORTING
                bildsequenz     = c_seq_code
                pflegestatus    = c_viewlist
           TABLES
                bildtab         = t_bildtab
           EXCEPTIONS
                call_wrong      = 1
                empty_selection = 2
                OTHERS          = 3.
      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.                    " F_VIEW_LIST
    *&      Form  f612_view_sort                                          *
      Routine to used for Selecting The views based on Material Number  *
    FORM f612_view_sort.
      t_bildtab_dup[] = t_bildtab[].
    Reading the Internal table t_mara
      READ TABLE t_mara WITH KEY matnr = t_mdata-matnr.
      TRANSLATE t_mara-pstat USING ' $'.
      CLEAR: w_data-flag1, w_data-anzd70.
      LOOP AT t_bildtab_dup.
        IF t_bildtab_dup-pstat CA t_mara-pstat.
          w_data-anzd70 = w_data-anzd70 + 1.
          IF t_bildtab_dup-kzanz IS INITIAL.
            t_bildtab_dup-kzanz = 'X'.
            w_data-flag1 = 'X'.
            MODIFY t_bildtab_dup.
          ENDIF.
        ELSE.
          IF NOT t_bildtab_dup-kzanz IS INITIAL.
            CLEAR t_bildtab_dup-kzanz.
            w_data-flag1 = 'X'.
            MODIFY t_bildtab_dup.
          ENDIF.
        ENDIF.
      ENDLOOP.
      TRANSLATE t_mara-pstat USING '$ '.
      IF NOT w_data-flag1 IS INITIAL.
        SORT t_bildtab_dup BY kzanz DESCENDING idxbd ASCENDING.
      ENDIF.
    *Reading The internal table for T_bildtab_dup
      READ TABLE t_bildtab_dup WITH KEY dytxt = c_scm_view.
      IF t_bildtab_dup-kzanz = 'X'.
        WRITE sy-tabix TO w_data-count.
        w_data-count = w_data-count + 2.
        IF w_data-anzd70 > 18.
          w_data-count = w_data-count - 18.
        ENDIF.
        CONCATENATE 'MSICHTAUSW-DYTXT(' w_data-count ')' INTO w_data-field1.
        CONCATENATE 'MSICHTAUSW-KZSEL(' w_data-count ')' INTO w_data-field2.
      ENDIF.
      READ TABLE t_bildtab_dup WITH KEY dytxt = c_sd_view.
      IF t_bildtab_dup-kzanz = 'X'.
        WRITE sy-tabix TO w_data-count.
        IF w_data-anzd70 > 18.
              w_data-count = w_data-count + 2.
          w_data-count = w_data-count - 18.
        ENDIF.
        CONCATENATE 'MSICHTAUSW-DYTXT(' w_data-count ')' INTO w_data-field3.
        CONCATENATE 'MSICHTAUSW-KZSEL(' w_data-count ')' INTO w_data-field4.
      ENDIF.
    ENDFORM.                    " f612_view_sort
    *&      Form  f_uplaod_data                                           *
    Routine to used for Uploading the data from file to Internal table *
    FORM f_uplaod_data.
      CALL FUNCTION 'WS_UPLOAD'
           EXPORTING
                filename                = g_file
                filetype                = 'DAT'
           TABLES
                data_tab                = t_delim
           EXCEPTIONS
                conversion_error        = 1
                file_open_error         = 2
                file_read_error         = 3
                invalid_type            = 4
                no_batch                = 5
                unknown_error           = 6
                invalid_table_width     = 7
                gui_refuse_filetransfer = 8
                customer_error          = 9
                OTHERS                  = 10.
      IF sy-subrc <> 0.
             MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
             WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
      IF t_bpcs IS INITIAL.
        LOOP AT t_delim.
          SPLIT t_delim-text AT ',' INTO t_bpcs-matnr
                                         t_bpcs-dosage
                                         t_bpcs-appearance
                                         t_bpcs-idcode
                                         t_bpcs-prostformno
                                         t_bpcs-weitab
                                         t_bpcs-uom1
                                         t_bpcs-uom2
                                         t_bpcs-carsize
                                         t_bpcs-cassize
                                         t_bpcs-rupqty
                                         t_bpcs-abvname.
          APPEND t_bpcs.
        ENDLOOP.
      ENDIF.
    ENDFORM.                    " f_uplaod_data
    *&      Form  F_BDC_OPEN
          Routine  to create BDC Session to be processed
    FORM f_bdc_open.
      CALL FUNCTION 'BDC_OPEN_GROUP'
           EXPORTING
                client              = sy-mandt
                group               = c_group
                keep                = c_keep
                user                = sy-uname
           EXCEPTIONS
                client_invalid      = 1
                destination_invalid = 2
                group_invalid       = 3
                group_is_locked     = 4
                holddate_invalid    = 5
                internal_error      = 6
                queue_error         = 7
                running             = 8
                system_lock_error   = 9
                user_invalid        = 10
                OTHERS              = 11.
      IF sy-subrc <> 0.
        MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
      ELSE.
      MESSAGE S000 WITH 'Batch input session is created successfully'(T02).
      ENDIF.
    ENDFORM.                    " F_BDC_OPEN
    *&      Form  F_PROCESS_BDC
          Processing of BDCDATA Structure
    FORM f_process_bdc.
      LOOP AT t_mdata.
        PERFORM f612_view_sort.
        PERFORM f_bdc_dynpro USING 'SAPLMGMM' '0060'.
        PERFORM f_bdc_field USING 'BDC_CURSOR'
                                      'RMMG1-MATNR'.
        PERFORM f_bdc_field USING 'BDC_OKCODE'
                                      '=AUSW'.
        PERFORM f_bdc_field USING 'RMMG1-MATNR'
                                      t_mdata-matnr.
        PERFORM f_bdc_dynpro USING 'SAPLMGMM' '0070'.
        PERFORM f_bdc_field USING 'BDC_CURSOR'
                                  'MSICHTAUSW-DYTXT(01)'.
        IF w_data-anzd70 > 18.
          PERFORM f_bdc_field       USING 'BDC_OKCODE'
                                      '=P+'.
          PERFORM f_bdc_dynpro      USING 'SAPLMGMM' '0070'.
          PERFORM f_bdc_field  USING 'BDC_OKCODE' '/00'.
        ENDIF.
    reading the t_bildtab internal table
        READ TABLE t_bildtab_dup WITH KEY dytxt = c_scm_view.
        IF t_bildtab_dup-kzanz = 'X'.
          PERFORM f_bdc_field       USING 'BDC_CURSOR'
                                        w_data-field1.
          PERFORM f_bdc_field       USING w_data-field2 'X'.
          g_flag = 'X'.
        ENDIF.
    reading the t_bildtab internal table
        READ TABLE t_bildtab_dup WITH KEY dytxt = c_sd_view.
        IF sy-subrc EQ 0.
          g_flag = 'X'.
        ENDIF.
        IF t_bildtab_dup-kzanz = 'X'.
          PERFORM f_bdc_field       USING 'BDC_CURSOR'
                                        w_data-field3.
          PERFORM f_bdc_field       USING w_data-field4 'X'.
          g_flag1 = 'X'.
        ENDIF.
        IF g_flag = 'X' AND g_flag1 = 'X'.
          PERFORM f_bdc_dynpro      USING 'SAPLMGMM' '0080'.
          PERFORM f_bdc_field       USING 'BDC_CURSOR'
                                        'RMMG1-VTWEG'.
          PERFORM f_bdc_field       USING 'BDC_OKCODE'
                                        '=ENTR'.
          PERFORM f_bdc_field       USING 'RMMG1-WERKS'
                                        c_werks.
          PERFORM f_bdc_field       USING 'RMMG1-VKORG'
                                        c_vkorg.
          PERFORM f_bdc_field       USING 'RMMG1-VTWEG'
                                        c_vtweg.
          CLEAR g_flag.
          CLEAR g_flag1.
        ELSE.
          IF g_flag = 'X'.
            PERFORM f_bdc_dynpro      USING 'SAPLMGMM' '0080'.
            PERFORM f_bdc_field       USING 'RMMG1-WERKS'
                                        c_werks.
            PERFORM f_bdc_field      USING 'BDC_OKCODE' '/00'.
          ELSE.
            IF g_flag1 = 'X'.
              PERFORM f_bdc_dynpro      USING 'SAPLMGMM' '0080'.
              PERFORM f_bdc_field       USING 'BDC_CURSOR'
                                            'RMMG1-VTWEG'.
              PERFORM f_bdc_field       USING 'RMMG1-WERKS'
                                          c_werks.
              PERFORM f_bdc_field       USING 'RMMG1-VKORG'
                                            c_vkorg.
              PERFORM f_bdc_field       USING 'RMMG1-VTWEG'
                                            c_vtweg.
              PERFORM f_bdc_field       USING 'BDC_OKCODE'
                                             '=ENTR'.
            ENDIF.
          ENDIF.
        ENDIF.
    *Processing of SCM View
        PERFORM f_bdc_dynpro      USING 'SAPLMGMM' '4000'.
        PERFORM f_bdc_field       USING 'BDC_CURSOR' 'MARC-ZZJP_DOS_FRM'.
        PERFORM f_bdc_field       USING 'MARC-ZZJP_DOS_FRM'
                                      t_mdata-zzjp_dos_frm.
        PERFORM f_bdc_field       USING 'MARC-ZZJP_APRN'
                                      t_mdata-zzjp_aprn.
        PERFORM f_bdc_field       USING 'MARC-ZZJP_CON_ID'
                                      t_mdata-zzjp_con_id.
        PERFORM f_bdc_field       USING 'MARC-ZZJP_NYU_SOP'
                                      t_mdata-zzjp_nyu_sop.
        PERFORM f_bdc_field       USING 'MARC-ZZJP_WEI_TAB'
                                      t_mdata-zzjp_wei_tab.
        PERFORM f_bdc_field       USING 'MARC-ZZJP_CAR'
                                      t_mdata-zzjp_car.
        PERFORM f_bdc_field       USING 'MARC-ZZJP_CAS'
                                      t_mdata-zzjp_cas.
        PERFORM f_bdc_field       USING 'MARC-ZZJP_CAR_SIZE'
                                      t_mdata-ZZJP_CAR_SIZE.
        PERFORM f_bdc_field       USING 'MARC-ZZJP_CAS_SIZE'
                                      t_mdata-ZZJP_CAS_SIZE.
        PERFORM f_bdc_field       USING 'MARC-ZZJP_RUPQTY'
                                       t_mdata-ZZJP_RUPQTY.
        PERFORM f_bdc_field       USING 'MARC-ZZJP_BIO'
                                      t_mdata-zzjp_bio.
        PERFORM f_bdc_field       USING 'MARC-ZZJP_ITF'
                                      t_mdata-zzjp_itf.
        PERFORM f_bdc_field       USING 'MARC-ZZJP_INIT_LS'
                                      t_mdata-zzjp_init_ls.
        PERFORM f_bdc_field       USING 'MARC-ZZJP_RE1'
                                      t_mdata-zzjp_re1.
        PERFORM f_bdc_field       USING 'MARC-ZZJP_RE2'
                                      t_mdata-zzjp_re2.
        PERFORM f_bdc_field       USING 'MARC-ZZJP_RE3'
                                      t_mdata-zzjp_re3.
        PERFORM f_bdc_field       USING 'BDC_OKCODE'
                                      '/00'.
    *Processing of SD View
        PERFORM f_bdc_dynpro      USING 'SAPLMGMM' '4000'.
        PERFORM f_bdc_field       USING 'BDC_CURSOR' 'MVKE-ZZJP_PRO_ID'.
        PERFORM f_bdc_field       USING 'MVKE-ZZJP_PRO_ID'
                                      t_mdata-zzjp_pro_id.
        PERFORM f_bdc_field       USING 'MVKE-ZZJP_BU_ID'
                                      t_mdata-zzjp_bu_id.
        PERFORM f_bdc_field       USING 'MVKE-ZZJP_ABV_NAME'
                                      t_mdata-zzjp_abv_name.
        PERFORM f_bdc_field       USING 'MVKE-ZZJP_ABV_ID1'
                                      t_mdata-zzjp_abv_id1.
        PERFORM f_bdc_field       USING 'MVKE-ZZJP_ABV_ID2'
                                      t_mdata-zzjp_abv_id2.
        PERFORM f_bdc_field       USING 'MVKE-ZZJP_SPL_ID'
                                      t_mdata-zzjp_spl_id.
        PERFORM f_bdc_field      USING 'BDC_OKCODE' '/00'.
        PERFORM f_bdc_dynpro      USING 'SAPLSPO1' '0300'.
        PERFORM f_bdc_field       USING 'BDC_OKCODE'
                                      '=YES'.
    perform f_bdc_insert.
    REFRESH T_BDCDATA.
      ENDLOOP.
    ENDFORM.                    " F_PROCESS_BDC
    *&      Form  f_bdc_dynpro
      p_prog is the program name to which data is passed                *
      p_dyno is the screen number to which the data is passed
        Routine for populating the BDCDATA structure with the
        Screen related information
    FORM f_bdc_dynpro USING    p_prog
                               p_dyno.
      t_bdcdata-program  = p_prog.
      t_bdcdata-dynpro   = p_dyno.
      t_bdcdata-dynbegin = 'X'.
      APPEND t_bdcdata.
      CLEAR t_bdcdata.
    ENDFORM.                    " F_bdc_dynpro
    *&      Form  F_BDC_FIELD
          p_fnam is the field name to which value is passed
          p_fval is the field value which is passed
       p_fnam is the field name to which value is passed
       p_fval is the field value which is passed
    FORM f_bdc_field USING    p_fnam
                              p_fval.
      t_bdcdata-fnam = p_fnam.
      t_bdcdata-fval = p_fval.
      APPEND t_bdcdata.
      CLEAR t_bdcdata.
    ENDFORM.                    " F_bdc_field
    *&      Form  F_PROCESS_DATA                                          *
         Routine to used for moving data from T_bpcs internal table to  *
         t_mdata Internal Table                                         *
    FORM f_process_data.
      LOOP AT t_bpcs.
        CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
             EXPORTING
                  input  = t_bpcs-matnr
             IMPORTING
                  output = t_mdata-matnr.
        MOVE t_bpcs-dosage TO t_mdata-zzjp_dos_frm.
        MOVE t_bpcs-appearance TO t_mdata-zzjp_aprn.
        MOVE t_bpcs-idcode  TO t_mdata-zzjp_con_id.
        MOVE t_bpcs-prostformno TO t_mdata-zzjp_nyu_sop.
        MOVE t_bpcs-weitab TO t_mdata-zzjp_wei_tab.
        MOVE c_blank TO t_mdata-zzjp_bio.
        MOVE c_blank TO t_mdata-zzjp_itf.
        MOVE t_bpcs-uom1 TO t_mdata-zzjp_car.
        MOVE t_bpcs-uom2 TO t_mdata-zzjp_cas.
        MOVE t_bpcs-carsize TO t_mdata-zzjp_car_size.
        MOVE t_bpcs-cassize TO t_mdata-zzjp_cas_size.
        MOVE t_bpcs-rupqty TO t_mdata-zzjp_rupqty.
        MOVE c_intls TO t_mdata-zzjp_init_ls.
        MOVE c_blank TO t_mdata-zzjp_re1.
        MOVE c_blank TO t_mdata-zzjp_re2.
        MOVE c_blank TO t_mdata-zzjp_re3.
        MOVE c_blank TO t_mdata-zzjp_pro_id.
        MOVE c_blank TO t_mdata-zzjp_bu_id.
        MOVE t_bpcs-abvname TO t_mdata-zzjp_abv_name.
        MOVE c_blank TO t_mdata-zzjp_abv_id1.
        MOVE c_blank TO t_mdata-zzjp_abv_id2.
        MOVE c_blank TO t_mdata-zzjp_spl_id.
        APPEND t_mdata.
      ENDLOOP.
    ENDFORM.                    " F_PROCESS_DATA
    *&      Form  f_bdc_close
          Routine to close the BDC Session
    FORM f_close_group.
      CALL FUNCTION 'BDC_CLOSE_GROUP'
           EXCEPTIONS
                not_open    = 1
                queue_error = 2
                OTHERS      = 3.
      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.                    " f_close_group
    *&      Form  f_bdc_insert
         routine to input batch data into the Transaction MM02 from the
         session created
    FORM f_bdc_insert.
    CALL FUNCTION 'BDC_INSERT'
             EXPORTING
                  tcode            = c_tcode
             TABLES
                  dynprotab        = t_bdcdata
             EXCEPTIONS
                  internal_error   = 1
                  not_open         = 2
                  queue_error      = 3
                  tcode_invalid    = 4
                  printing_invalid = 5
                  posting_invalid  = 6
                  OTHERS           = 7.
        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.                    " f_bdc_insert
    Reward Points if it is useful
    Thanks
    Seshu

  • Material Master views for every material type

    HI Expertis,
    I am facing to the big problem. My requirement is to identify the Material Master Views relevent to the each and every Material Type.
    As an example, for the material type "FGTR" what should be the required views to create material master?
    From the MM01 Txn i found 36 Material types. Also found the standard views in "OMS2" Txn. But in OMS2 txn it gives me almost all the views in material master.
    Atlease i hope to categorize the material types which are going to use same material views. So i can ask abaper to develop it.
    these are the required Material types : MODE, FGTR, WETT, KMAT, LEER, LGUT, FERT, FOOD, INTR, CONT, IBAU, HERS, NLAG, NOF1, UNBW, HIBE, VERP, FRIP, PIPE, FHMI, ROH, LEIH, HALB, DIEN, ERSA, HAWA
    I would be gratefully thank u, if u can guided me on this matter.
    Thanx & Regards,
    Rashika.

    Hi,
    You can ask your abaper to write a small program by using table t134(T134-PSTAT) and T132T   .From this tables ,for each material type, you get all views.
    User department Maintenance status
    Work scheduling A
    Accounting B
    Classification C
    MRP D
    Purchasing E
    Production resources/tools F
    Costing G
    Basic data K
    Storage L
    Forecasting P
    Quality management Q
    Warehouse management S
    Sales V
    Plant stocks X
    Storage location stocks Z
    hopw this will help you.
    With Regards,
    Jaheer

  • How hide views in MM01

    Hello Experts,
    i am new to SPRO settings
    I have a requirement to hide the views in MM01 transaction.
    i want to hide MRP views and and some other views.
    Could anybody tell me how to acheive this.
    Thanks
    Note : Subject is FAQ,please search forum before posting.
    Edited by: Jeyakanthan A on Dec 25, 2011 12:13 AM

    > I have a requirement to hide the views in MM01 transaction.
    >
    > i want to hide MRP views and and some other views.
    Hi, From T-code OMS2 select the material type for which you do not want the MRP view, double click on the material type & deselect the MRP (all 4 MRP views are connected to these tab only) tab for that material type & save. Test & check.

  • Screen no. for HERS Material type

    Hi Friends,
    I am trying to write a mass uploading program for HERS material type.
    When I go to Purchasing view of HERS material type "Manufacturing details" subscreen is showing below (like Internal Material no. & Mfr Part no). i.e. it is showing the sequence as General data - Purchasing values - Manufacturing detailssub screens. Actually I want the sequence as Manufacturing details- Genaral data - Purchasing  values.
    When I check in OM3TE 12 is assigned to HERS material type. When I checked in OM3TB for screen sequence of 12 --- in Purchasing view I could see screen no. as 3002. The sub screen sequence is also correct.
    But when I go to trnasaction MM02 --purchasing view the screen no. is 4000. (it is the screen no. to come for standard 12 screen sequence.
    Am doing corectly ?
    I want to get screen as 3002 in Purchasing view of HERS material type and sequence should be Manufacturing details- Genaral data - Purchasing  values.
    Regards,
    Sai Krishna

    Hi Sai Krishna ,
    Goto OMT3B and change the Screen no of Subscreen ( Last Column ) to :
    2312 -- 3rd Row
    2311 -- 4th Row
    2302 -- 5th Row
    At first note all the numbers in last column and then change it.
    Leave the others without any changes.
    Regards
    Ramesh Ch

  • Allow mov type 261 and 262 for a material type only

    Requirement is to allow movt type 261 and 262 for a particular material type.( Assume Only 261 - 262 issue transactions happen against that material type.)
    User to be restricted, while material issue (migo), for the material type XXXX to 261 - 262 movt type only.
    No any other movt type allowed for this material type while issuing material.
    All suggestions welcomed.
    Regards,
    Rakesh

    Thanx amit.
    But same user uses all other movt types for other material type also.

  • Print in different page for different material type in Sapscript

    Hi all
    How do I do the above matter?
    Currently I have a script that print all material according to some condition.
    My client request to have a different page of material list for different material type.
    Please advise
    az

    Hi,
    1) Sort the internal table by material type.
    call func 'OPEN_FORM'.
    loop at itab.
    at new mattype.
    if mattype = 'A'.
      call fun 'START_FORM'.
       exporting
        page   =    'PAGEA'.
    elseif mattype = 'B'.
      call fun 'START_FORM'.
       exporting
        page   =    'PAGEB'.
    endat.
    call func 'WRITE_FORM'.
    AT end of mattype.
    call function 'END_FORM'.
    endat.
    endloop.
    call function 'CLOSE_FORM'.
    Thanks,
    Nethaji.

  • It should be possible to set default behavior for all file types

    It should be possible to set a default action for all file types. I'm so tired of having to manually sit and say "save this file" because Firefail always defaults to "open with" and has disabled the "Do this automatically for files like this from now on."
    And spare me the zealotry religious excuses for why its the fault of websites and not Firefail
    ''edited to remove swearing''

    I do want users to have full control to be able to set any folder view they want by using Apply to Folders; I just want to set the initial/default view to Detail because that matches what the majority of my users want.
    That is, what registry setting changes when I go to a picture folder, change the view to Detail, and click Apply to Folders? Having done that, I still retain the ability to change it to some other view and apply that to folders. But what registry setting
    represents the change I just made when applying Detail view to all Picture folders.?
    This settings is simple via GUI, but it is related a lot of registry keys, I made a test in my machine, capture the "Apply to Folders" process using Regshot tool (this is a small tool which can compare the regsitry changes after you change some
    settings), and this is the result:
    this is part of the registry changes, a plenty of registry keys and values need to be changed. hard to list them here. if you have interests, I recommend the tool Regshot, it can help you capture the regsitry changes.
    NOTE: Please Note: The third-party product discussed here is manufactured by a company that is
    independent of Microsoft. We make no warranty, implied or otherwise, regarding this product's
    performance or reliability.
    Yolanda Zhu
    TechNet Community Support

  • Doing GR for a material type, system should give a message like QI required

    Dear Friends
    While doing MIGO(GR) for a material type, system should give a message like Quality Inspection required
    but Client requirement is not to maintain QM view or Inspection Type 01for  material type
    Any setting required 
    Thanks & Regards
    Gajendranath

    Hi
    Please check user exit QBCK0003 |Extended QM check for goods receipt                        
    Regards
    sujit

  • "Mfr part profile" setup for various material types

    Hello All,
    I'd like to set a default value of "Mfr part profile" field ("Purchasing" screen in 01 Std industry sequence) different for various material types. Currently I have 2 entries maintained in MaterialsManagement>Purchasing>MaterialMaster>DefineManufacturerPartProfile (one with AMPL management and one without). I'd like to get the first entry set as default for HAWA material type and the 2nd for ROH.
    Thanks in advance for your help on this!
    Jacek

    Hi Troinski,
    Its not possible in SAP, you can create Z transaction for create material wth dafult values.
    Thanks
    Bala

  • Valuation category for DIEN material type

    Dear all,
    I have a requirement in which I need to maintain two price for  DIEN material type ,I have created two valuation type and asssigned to a valuation category and If Itry to assign valuation category in Material master it is Grayed out ,even if I try in field selection also it is not working ,can't we have two valaution prices for service material? is that SAP standard?
    Regards
    kantha

    can any body help me
    Kantha

  • How to configure Alpha Numeric No range for the Material Type

    Dear Expert,
    i kindly request for expert help on alpha numeric no range for the Material Type.
    business is looking for material no like 910442208571D. at present we have no range like 9000000000000 to 9999999999999
    how i can configure in the system??
    pl. help me on this
    Thanks a lot
    H shah

    Hi,
    System will not bring alphanumeric number of materials automatically during MM01.
    Check use exit MGA00002 - Material Master (Industry): Number Assignment.
    Also check 2 Function Modules:
    EXIT_SAPLMG02_001 - Customer Exit: Internal Material Number Assignment
    EXIT_SAPLMG02_002 - Customer Exit: External Material Number Assignment.
    Regards,
    Biju K

  • HELP for all 5 TYPES of  STO  Stock Transport Orders with detailed scenario

    PLEASE help me understanding the detailed scenarios for all 5 TYPES of STO s
    as in my day to day job activities , i frequently handles issues related to STO s
    PLEASE HELP WITH DETAILED STEP BY STEP SCENARIOS

    Hi Jagatram,
    Standard SAP has the following methods For Stock transport order:
    1) One Step Transfer stock without using purchasing documents; Use movement type 301.
    2) Two Step Transfer stock without using purchasing documents; Use movement type 303 in Supplying plant and movement type 305 in receiving plant.
    3) Using Standard Transport Order (STO) without delivery in two steps. STO created in T-Code ME27, receiving plant posts goods issue (for returns), movement type 351 and supplying plant post goods receipt from using movement type 101.
    4) Using Standard Transport Order (STO) with delivery in one step. STO created in T-Code ME27, Receiving plant creates shipment and Goods issue document (for materials to be returned) with movement type 647 and goods receipt document with movement type 101 both created in one step.
    5) Using Standard Transport Order (STO) with delivery in two steps. STO created in T-Code ME27, Receiving plant creates shipment and Goods issue posted (for materials to be returned) with movement type 641.Goods receipt is posted in the supplying plant, movement type 101.
    6) Using Transportation scheduling agreement (TSA) with delivery in two steps. TSA created in T-Code ME37. Receiving plant creates shipment and Goods issue document (for materials to be returned) with movement type 641. Goods receipt is posted in the supplying plant, movement type 101.
    To achieve it, necessary configurations has to be done in Tcode- OMGN.
    SPRO>> Materials management>> Purchasing>> Purchase Order>> Set up Stock transport Order:
    1. Plant: For the receiving plant, maintain customer No-Plant (If using STO with delivery), for the Sales Org, Dist channel and Division.
    2. Checking Rule: Create checking rule.
    3. Define checking rule : Usually no change required here.
    4. Assign delivery type/checking rule: Assign the document type(UB) - Supplying plant- Delivery type(NL).
    5. Purchasing document type: Maintain the supplying plant- Receiving plant relationships for the doc type-UB, either 1-step or 2-step, as per business.
    Hope this helps!
    Regards,
    Shilpa

  • Condition record not pulled for all material

    Hi,
    I have three materials in sales order. now, for each material , I am maintaining some condition record in VK11. the problem i face is, if in case I don't maintain condition recrod for condtion ZCD1 for the first material A in sales order, the condtion records that I have maintain for the same condtion ZCD1 for the following materials are also not getting pulled. that's true for all conditiond in my pricing procedure. only those conditions for which system could find records for the first material, it pulls it for all other materials that follow material A in sales order. otherwise, system gives the messgae " condition record has been found but not set "
    what could be the reason? this is certainly not the standard behavior.
    Thanks,
    Binita

    I have checked this with creating new records for all material for all condtions. but, it is possible that a particular price condtion may not be maintained for the first material and which can very well be maintained for the folllowing materials. in that case, they are not pulled. the records are there for sure for other materials as 1) i could see them in VK13 and 2) the condition analysis tells me that condtion record is found but not set. no clue what it has got anything to do with first material..as soon as i maintain that condtion for first material (even zero value in Vk11), they start appearing for other materials as they are maintained.
    Thanks,
    Binita

  • ME21N : Donu2019t copy the price for all condition types from last po

    Dear.
    When I create a purchase order the price for all condition types are copied from last purchase order inside the info-record.
    But I have some condition types like FRA1 or FRA2 that I donu2019t want that system transfer price from last purchase order.
    How can I do that ?
    Thanks.

    Hi Cris,
    Go to SPRO>MM>PUR>Info Record>Define Price History> Here with your Purchasing organization if the tick is active that
    Specifies that the order price history (PO price history) is to be updated with the effective price.
    Normally, the order price history is updated with the net price.
    Procedure
    Set this indicator if you want the order price history to be updated with the effective price.
    Thanks
    Diwakar

Maybe you are looking for

  • What is the "Live" page and need help in data merge

    Hello, Im very new to indesign so bare with me. Im trying to data merge (Need to create a merge template?) and from what I understand is that I need it to be on the "Live" page. Someone on the forum suggested this..... There are two ways to set up th

  • Not allow users to disable startup script

    I have written a User Login script for indesign and have successfully implemented in Indesign CS3. However, anyone can disable the login script that I have put in the Startup script by modifying the Preference setting of the Indesign.  I would be ver

  • Annoyed with Nokia support

    I purchased a brand new Nokia E55 on 16-September 2009 and from day 1 it did not work. it would freeze up, restart and refuse to even software update. I went to Nokia care in Melbourne and they gave me a replacement (refurbished) unit after 1 week. W

  • Why can't I access my inbox email on my desktop computer?

    It says no access to Thunderbird...I've not changed anything Please help

  • Mac OS X Leopard Firewall/default open ports rpcbind?

    Hi, I'm looking into hardening/securing mac os x leopard and noticed that port 111 rpcbind is open. Is rpcbind open by default? What are leopards default open ports on a fresh install? Also is there any way to run openbsd/freebsd PF firewall? Thanks!