Hide material Type in MM01

Dear Experts ,
The standard material types available are many, but we use only 8 of them.
How can i hide the irrelevant material types from being displayed in MM01 screen?
Reagrds
Anis

Hi Anis,
As u only want to use 8 Matl Types specifically required,
then as said by all gurus u can either not assign Number range to them the remaining or else
U can block the MM01 and use Material type specific T Codes ie ,
MMR1 - Raw Material
MMB1 - Semi-Finished Product
MMF1 - Finished Product
MMI1 - Operating Supplies
MMH1 - Trading Goods
MMU1 - Non-Valuated Material
MMN1 - Non-Stock Material
MMV1 - Packaging
MML1 - Empties
MMS1 - Service(s)
MMK1 - Configurable Material
MMP1 - Maintenance Assembly
MMW1 - Competitor Product
MMG1 - Returnable Packaging
Hope this helps
Regards

Similar Messages

Is it possible to hide a certain material type in MM01?

Dear All,
Is it possible to hide a certain material type in MM01?
We would want to restrict the users from creating a material by using certain materials type.
regards,
Shetty

You have two options, either remove the assignment of number ranges in MMNR or block the user from using it via authorization.

How to Restrict Material Type in MM01 ?

*Hi experts,*
*How to restrict material type ? i wanted to restrict the end-user not to access any other material types than Raw material,Semi-finished goods. it means when end user trying to create material then if he enters other than these two material types then he should get error saying that "your not authorized to select that xyz material type".*
*I have tried to restrict the object M_MATE_MAR(Material Master : Material type) but am unable to do so. is there any other object which take care of Material types ? did i selected correct object or not??*
*can anyone help out.*

Hi,
You have to make few configuration settings before you actually restrict at the object level. The solution is clearly discussed in the below thread:
how to restrict material master by material type t-code MM01
Hope this helps!!
Regards,
Raghu

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)

Restricting the material types in MM01

Dear experts,
Our client is using few materila types like-HIBE,NLAG,ROH
We have upgraded from 4.6B to ECC6. Now many other material types have come .
While creating material in MM01,selecting the required material type among the many is inconvient.
1)One way of removing the unnecessary mat types is deleting others in OMS2,
The other way of restricting is --
2) I can enter the authorisation group in OMS2 for the required material types and i can assign to M_MATE_MAR object in the required role, but it is not working
Do i need to create authorisation group in any customisation for entering in the OMS2, because what i entered in OMS2 is not displaying in PFCG of the authorisation object under authorisation group.I have checked in SM30 also ,the same authorisation groups under T134 table are updated. Even though,mat types are not restricted in MM01 under material type field.
Please suggest any other way of restricting the display of material types in Material type field of MM01 instead of deleting unwanted the material types in OMS2 transaction
Regards,
Dayanand

You can use the material type specific transactionsminstead of MM01, remove the authorizations of MM01 transaction and add the required material type creation transactions
example - Goor Matreials create(special)
HIBE,NLAG,ROH
MMB1                 Create Semifinished Product(HALB)
MMF1                 Create Finished Product(FERT)
MMG1                 Create Returnable Packaging
MMH1                 Create Trading Goods
MMI1                 Create Operating Supplies(HIBE)
MMK1                 Create Configurable Material(KMAT)
MML1                 Create Empties
MMN1                 Create Non-Stock Material
MMP1                 Create Maintenance Assembly
MMR1                 Create Raw Material(ROH)
MMS1                 Create Service
MMU1                 Create Non-Valuated Material
MMV1                 Create Packaging
MMVH                 Create Centrally: Decentral.Shipping
MMW1                 Create Competitor Product

Defining Material types in MM01

Dear All,
I want to know how to define material types. Here client needs to bring same material under inventory and non inventory.
Example
1.100 is one material number.some times they required to bring the 100 material into stock and some of the times they want to book the material 100 in direct consumption account after taking GRIN.(no issue posting)
Now how could i define the material type for material 100.
Thanks
Shobana

Hello Shobana,
If your client wants to post the same material some time as inventory material and some time non-inventory material then you need not to define any new material type, but this can be handled at transaction level.
- Create Material as normal material with MM01
1. When you want to stock this material in inventory :
Create the purchase order without any account assignment so when you receive material it will post to inventory account and you will be able to keep that as stock material
2. When you want to post this material in directly to cost account (direct consumption) :
Create the purchase order with account assignment (i.e. cost center, assets) so when you receive material it will directly post this material to cost account but not to inventory account and you will not be able to keep that as stock material
Hope this helps.
Regards
Arif Mansuri

Restrict Material Type for MM01

Dear All,
When i run transaction MM01 system allows to create material with external number using alpha numeric for those types which
are not required.
e.g i am using fert and halb only and assigned number range to these two only ,,,
but wen i create material using MM01 and select material type beverage and give material number A123 suppose , then it allows to create it,,,,
i want to restrict system only to create those are being assigned with number ranges,
please guide,
Thanks

Create an authorization group using se54 and assign permitted material type to it. Also check following posting :
http://www.sapfans.com/forums/viewtopic.php?=&p=829019

Material types like ROG, HALB etc. (are hidded) in MM01

Hi,
I am not able to see material types like ROG, HALB etc. (are hidded). Only descreption is displayed.
What needs to be done so that I can also able to see the material types in MM01
Regards,
Shetty

Hi,
In MM01 Go to customize local layout-->options--->flag 'show keys in all dropdown list' and flag 'sort items by key'.
The material types will be diplayed with keys .
Regards,
Venkatesh

Hiding material types

Hello gurus,
we do not need all standard material types. But I would not like to completely delete them in case we needed them in the future.
Unfortunatelly our users get confused by all the unnecessary entrys in the drop down list at material master creation (MM01). Is there any way to hide material types in that list?
Thanks in advance
Alicia

Dear,
Dont think there is any way by which you can hide material types, as material type is the basic requirement, depending upon which material is created.
End users should be made aware of using right material types/its consequences and effects and should be given proper training.
Try to put an authorization group on each type you don't use and make it impossible for anyone to use them.
If your Basis team able to create transaction variants for you. Then don't allow anyone to have MM01 and instead only allow the variants. In this way you can also separately control/assign who creates raw mats, finished goods, intermediates, etc..
If you do not assign any number range for these material types, when user trying to create system gives a message as 'NO. RANGE NOT EXISTS.
And finally, a simpliest way is mark the material types which you dont want to use 'DO NOT USE' and later on can be changed.
Regards,
Syed Hussain.

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

HOW TO HIDE UNWANTED MATERIAL TYPES IN MMO1

Dear all!
In the production client, while creating material by MM01, except some material types to be shown and others to be hidden.
If all material type are shown then the users getting confused which one to chosen. So, how to remove or hide the unwanted material types?
Thanks in advance.
Regards,
Siva.

User special transactions:
MMR1 - Raw Material
MMB1 - Semifinished Product
MMF1 - Finished Product
MMI1 - Operating Supplies
MMH1 - Trading Goods
MMU1 - Non-Valuated Material
MMN1 - Non-Stock Material
MMV1 - Packaging
MML1 - Empties
MMS1 - Service(s)
MMK1 - Configurable Material
MMP1 - Maintenance Assembly
MMW1 - Competitor Product
MMG1 - Returnable Packaging

How to restrict material master by material type t-code MM01

Hi,
how to restrict Materilal master by Material type in t-code MM01
I do restrict by M_MATE_MAR authorization object . After i see there not restrict.
Amit

>
sapvinithbasis wrote:
> hi
> plz help me out in solving this issue
> regards vinith
Vinith,
I have explained in great detail exactly what you need to do at every stage. The steps I have outlined are the same that I follow every time that I want to apply material type restrictions.
I strongly recommend that you contact your security admin to help with this, alternatively engage the services of a trained/experienced security admin who can come on site and go through this with you.
If you have done the following then it will work:
1. Assign auth group to material type via OMS2
2. Verified that check for M_MATE_MAR is active
3. Ensured that M_MATE_MAR does not contain the auth group/s which you assigned via OMS2 (that includes *)
This is the last comment I will make on this topic.
Cheers
Alex

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

How to keep Industry sector and Material Type in Display for Tcode MM01

How to keep Industry sector and Material Type in Display for Tcode MM01( create material Initial screen)
Thanks,

Hi
Yes, your requirement is possible using screen variant
1. use tcode SHD0
2. give transaction as MM01
3. goto screen variant tab - assign some name - enter program name and screen name
(from mm01 - F1 help)
4. goto transaction variant tab - assign some name - assign already defined screen variant name
5. goto standad variant tab - transaction variant name already fetched automatically - click on active button (it was placed after transaction variant name
Raju

Version category field for material type trading goods in mm01

hi everyone,
In MM01 for trading goods material type, we have version category field in basic data1 as list box, but there is no values in it. As we are using SAP DBM 7.0. can anyone tell me how to get or configure those values in list box?
Thanks in Advance!!!

I could only find that this tcode can be used for maintaining the version types. VTCU.
Could not help u much as this version is not activated in my system

Hide material Type in MM01

Similar Messages

Maybe you are looking for