Mm01/mm02 different views, bdc

Hello Abapers,
Is there a table that we can query, or a function that we can use to find out what views and only the applicable views (e.g. Basic Data 1, Basic Data 2, Purchasing, MRP 1, etc.) that are available for a certain material?
Any help would be much appreciated. Thanks.

Hello,
MARC-PSTAT will contain the information for the material and the views associated with it. For eg.
000000000000216038 3100 DEALSVQBG
For each view it will have a single letter associated with it.
A Work scheduling
B Accounting
C Classification
D MRP
E Purchasing
F Production resources/tools
G Costing
K Basic data
L Storage
P Forecasting
Q Quality management
S Warehouse management
V Sales
X Plant stocks
Z Storage location stocks
I thought you were using a bdc and wanted to use a view if it was present or not.
Regards,
Shekhar KUlkarni

Similar Messages

How to get the list data in MM01/MM02 Classification view

Hi,
Anyone know the FM that we use for getting the list in Clasification View of MM01/MM02?
Thanks,
Alfred

hii,
U can use the below fm to get the classification view in MM02..
CLFM_OBJECT_CLASSIFICATION
CLFM_OBJECTS_CLASSIFICATION
BAPI_OBJCL_CREATE_KEY
CLFM_CLASS_CLASSIFICATION
or if u want data from classificaton view then use this function module.
CLAF_CLASSIFICATION_OF_OBJECTS
Regards,
Anil N.

What is the process for mm01 datatransfer by selecting different views

what will be the basic thing to be done for selecting different views?

hi ..if want to upload master data for different views then first create material using MM01 and then update material for different views one by one in MM02..for mass data transfer u can use BDCs for MM01 and MM02
regards

Set cursor in a specific view of transaction MM01/MM02

Hi,
We have to check a condition in the user-exit EXIT_SAPLMGMU_001, for transaction MM01/MM02, and if the condition fails the client wants to set the cursor in a specific field from a specific view. Is it possible? I tried to use the sentence SET CURSOR referenced to a remote program but it doesn't work.
Does anybody knows how to solve this problem?
Thanks in advance
Regards
Maribel

Hi
I hope, you have read the documetation attached with this Standard Enhancement - MGA00001.
EXIT_SAPLMGMU_001
Where Is the Customer Exit - EXIT_SAPLMGMU_001 called?
The customer exit is in function module MATERIAL_UPDATE_ALL. The
function module checks the data for errors (logical relationships,
foreign keys, fixed domain values, and so on) when the material master
is updated.
Use
o New fields
You can make checks possible for new fields of your own. These
checks must be identical to the checks that you carry out for your
new fields in online maintenance.
o Existing fields
For existing fields, you can extend and intensify the checks.
You can also change data for descriptions and general material data
(MARA). For example, the descriptions can be generated from attributes
of the material.
Limitations
You cannot bypass existing checks.
Interface to Application
The respective data of the current logical transaction is contained in
the structures, for example, in structure WMARA for MARA. Nonrelevant
structures are transferred with their initial values.
General material data that can be changed (CMARA) has the structure
MARU. This MARA view contains fewer internal fields than MARA itself. If
WMARA is filled, CMARA is also filled when accessed.
The customer exit contains the exception APPLICATION_ERROR for your
self-defined error situations.
Using the language element MESSAGE .. RAISING APPLICATION_ERROR, you can
terminate the current (logical) transaction and display your message in
the log.
Also, I guess, have you put some code in the Includes available with the EXITS and then activated the Project in CMOD.
<b>Reward points</b>
Regards

Bdc for MM01 with classification view

Hi all,
I need to create materials using mm01 with classification view. since there is no bapi supporting this view, i am ding by bdc.
The problem is in classification view once i give the class type and name a screen pops with caption
characteristic value assignment, but theere are no charateristics displayed - wat values do i have to enter here >
once i leave this screen the characteristics show up one after the other and i can load the details. but then while tryin to save error comes staing incnsisitent value assigned. wat do i ener in the intermediate screen t avoid this error.
thanks

hi when you are creating a classification view with characteristics.. you need to do all at once... you cannot modify..
all you can do is delete the whole view and create with all the changed again.. I dont memorize the BAPI .. but you have BAPIdelete.. BAPIadd..

BDC with MM01/ MM02 from MARA table

Can anybody suggest me for the following problem.
I want to construct a BDC with MM01/ MM02 from MARA table.
And I want the source file to be a notepad or Excel sheet. But i am not
getting, that how to write the data in Notepad/Excel sheet, to feed to the
master table according to the MM01/MM02 fields .

This is the sample code for creation of flatfile for MM01 this will be definetly helping you to create a flatfile.
REPORT ZBDC_FF MESSAGE-ID BCTRAIN .
TYPES: BEGIN OF STU,
       MATNR LIKE RMMG1-MATNR,
       MBRSH LIKE RMMG1-MBRSH,
       MTART LIKE RMMG1-MTART,
       MAKTX LIKE MAKT-MAKTX,
       MEINS LIKE MARA-MEINS,
       END OF STU.
DATA WA_ITAB TYPE STU.
DATA ITAB TYPE TABLE OF STU.
WA_ITAB-MATNR = 'T1'.              "MATERIAL NUMBER"
WA_ITAB-MBRSH = 'K'.                 "INDUSTRY SECTOR"
WA_ITAB-MTART = 'VKHM'.              "MATERIAL TYPE"
WA_ITAB-MAKTX = 'TOOLEMATERIAL'.     "MATERIAL DESCRIPTION"
WA_ITAB-MEINS = 'EE'.                "BASE UNIT OF MEASURE"
APPEND WA_ITAB TO ITAB.
CLEAR WA_ITAB.
*WA_ITAB-MATNR = 'TOL2'.              "MATERIAL NUMBER"
*WA_ITAB-MBRSH = 'M'.                 "INDUSTRY SECTOR"
*WA_ITAB-MTART = 'VKHM'.              "MATERIAL TYPE"
*WA_ITAB-MAKTX = 'TOOLEMATERIAL'.     "MATERIAL DESCRIPTION"
*WA_ITAB-MEINS = 'EA'.                "BASE UNIT OF MEASURE"
*APPEND WA_ITAB TO ITAB.
*CLEAR WA_ITAB.
*WA_ITAB-MATNR = 'TOL3'.              "MATERIAL NUMBER"
*WA_ITAB-MBRSH = 'M'.                 "INDUSTRY SECTOR"
*WA_ITAB-MTART = 'VKHM'.              "MATERIAL TYPE"
*WA_ITAB-MAKTX = 'TOOLEMATERIAL'.     "MATERIAL DESCRIPTION"
*WA_ITAB-MEINS = 'EA'.                "BASE UNIT OF MEASURE"
*APPEND WA_ITAB TO ITAB.
*CLEAR WA_ITAB.
*WA_ITAB-MATNR = 'TOL4'.              "MATERIAL NUMBER"
*WA_ITAB-MBRSH = 'M'.                 "INDUSTRY SECTOR"
*WA_ITAB-MTART = 'VKHM'.              "MATERIAL TYPE"
*WA_ITAB-MAKTX = 'TOOLEMATERIAL'.     "MATERIAL DESCRIPTION"
*WA_ITAB-MEINS = 'EA'.                "BASE UNIT OF MEASURE"
*APPEND WA_ITAB TO ITAB.
*CLEAR WA_ITAB.
CALL FUNCTION 'GUI_DOWNLOAD'
EXPORTING
FILENAME     = 'C:\Documents and Settings\chiranjeevi\Desktop\BDC.TXT'
TABLES
    DATA_TAB     = ITAB
IF SY-SUBRC <> 0.
MESSAGE S999 WITH 'EXECUTED'.
ENDIF.
Cheers!!!

Open Transaction MM01/MM02 with multiple views using CALL TRANSACTION

Hi All,
I want to open MM01/MM02 with multiple views using call transaction but in the parameter ID for Views (MMX) I can pass status of only one View.
SET PARAMETER ID 'MAT' FIELD v_mat.
SET PARAMETER ID 'VKO' FIELD ' '.
SET PARAMETER ID 'MTA' FIELD IT_MOFF-MTART.
SET PARAMETER ID 'MTP' FIELD IT_MOFF-MBRSH.
SET PARAMETER ID 'VTW' FIELD ' '.
SET PARAMETER ID 'BWT' FIELD ' '.
SET PARAMETER ID 'LGT' FIELD ' '.
SET PARAMETER ID 'MXX' FIELD 'K'. "Sales View
SET PARAMETER ID 'MM5' FIELD ' '.
CALL TRANSACTION 'MM02' AND SKIP FIRST SCREEN
Please suggest.
Regards,
Divya

I do not exactly understand what you mean, but what i already did:
- I checked that the fields are from the same type.
- KUNNR is initialized! I already had a look to the debugger, that's why i'm posting this in this forum.
any more comments on this ?
maybe i have to change anything in the z-transaction. Btw, this is what the parameter looks like in the transaction:
SELECTION-SCREEN BEGIN OF BLOCK Debitoren WITH FRAME TITLE text-001.
PARAMETERS pkunnr type kna1-kunnr OBLIGATORY.
SELECTION-SCREEN END OF BLOCK Debitoren.
Edited by: Sven Delangle on Sep 3, 2010 2:42 PM

How to restrict a User to access only 2-3 views in MM01/MM02 ???

Hi,
Can anyone tell me how can I restrict a User to access only 2-3 views in MM01/MM02 and also the User should not be allowed to change the View selection by clicking on the Select Views button ?.
Regards,
Lucky

Hi Prashant,
Can this only be done through changes in Authorization Objects ? Is not there any setting which can be done in SPRO for this ?
Hi Sheshagiri,
I could not exactly understand how the access to MM Views can be restricted to User through TCode OMT3B i.e. in SSeq. 01 and Screen 07 ? Subscreen 2154 is for Mat. Groups ? Please explain your answer in detail.
Regards,
Lucky

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

Error in adding custom fields to mm01/mm02/mm03 trx

Hello People,
To add my custom fields in the basic view tab of MM01 transaction, i have performed the following steps:-
1. Inserted the append structure in MARA table with the required fields.
2. Copied function group 'MGD1' to 'ZMGD1' and then set the layout of screen '0001' as per my requirement.
3. Then i made changes in spro as
SPRO->Logistics-General->Material Master->Configuring the material master->define structure of data screens for each screen sequence and inserted my program name( of function group 'ZMGD1') and screen number(0001) in 21(Std ind.(short) tab pages)->7(Basic Data 1)->8(sequence).
Now, if i click on SPRO option (view data screen), then i can see my fields added in basic data view...
but when i execute 'MM01/MM02/MM03' trx there my added fields do not appear....
Does anyone know where i am missing out??
Please suggest...
Thanks in advance..
Rgds,
Abhi

Here are some notes I have from when I recently added a new screen/subscreen to Material Master transactions. Hopefully this information will help you.
This guide should be used in conjunction with OSS note 44410 and IMG notes Logistics->Logistics Material Master->Material->Configure Customized Material Master.
Online Maintenance.
1. Add fields to append structure ZAEMARA.
Use data dictionary maintenance u2013 SE11
2. Generate table MARA.
3. Add fields to view MARU and generate.
Use data dictionary maintenance u2013 SE11.
4. Create new sub-screen or add new fields to screen SAPLYMM1 9001.
Use Screen Painter u2013 SE51.
Change flow logic to add fields to field: statement and to add any validation required. Generate screen.
If this is the first time additional data has been added to material master it will be necessary to create a new function group and associated programs. See Configure Customised Material Master paragraph Requirements.
5. If new sub-screen, add to Customer main screen.
Transaction OMT3.
Double click on u2018Std industry sequenceu2019.
Choose customer screen and Details.
Change the first occurrence of 0001 (blank screen) to new screen number.
Save.
Back arrow.
Click on Transport button and choose required transport.
6. To include in 'Copy with Reference' processing - MM01, add new MARA fields to table T130F. (in each client)
Use Transaction SM31. (make a copy of another ZZ field by typing over existing name).
Add to transport manually:- R3TR TABU T130F + individual keys
7. Test Material create, change, display.

How to activate the new fields on material master(MM01/MM02/MM03) for existing Materials

Hi,
We have a requirement to add some custom fields as a new tab in additional data option(Descriptions, Unit of measure, etc.) in Basic data of Material master (MM01/MM02/MM03). I have successfully added and these custom fields and they are not part of standard(MARA, MARC) but a custom table and the updates are also done in custom table.
For new materials, I can see the new tab in additional data screens of basic data view and I could successfully create/change/display using MM01/MM02/MM03. However I cannot see the new tab/fields for existing materials in the system in all 3 tcodes (MM01/MM02/MM03). This is not a main view in material master so that I can extend it by MM01.
Is there any setting or mass generation program I have top perform so that I can see and maintain these new fields for existing materials. Appreciate any leads or help on this.
Thanks,
Harry

Hello Harry,
Goto t.code SPRO ---> Display IMG ---> Logistics - General --> Material master --> Configuring the material master --> Create program for customized screens
Use the above path and create the screen and assign it to the sequence using the below link as reference.
**************** - Tips - Implementing screen exits for MM01/MM02/MM03
Regards,
Thanga

Purchase Order Text in MM01, MM02 dependant on Planyt ??

Hello,
In SAP standard, the purchase order text in MM01, MM02, MM03 will not be depedant on the plan , Is there any ways or configuration that allows user to create this text dependant on the plan in MM01 ?
Thanks

Hello,
I am afraid I must confirm you, that the System is working as designed.
Although the System asks for a plant when maintaining the Purchase Order Text view, the text is stored at client level and not at plant level.
The basic data text, the inspection text, the internal comment, the material description and the sales text are as well maintained at client level. The only text that can be maintained at plant level is the material memo in the MRP 4 view.
You can maintain plant specific texts in the purchasing info record.
Regards,
Mauro

Exit in MM01/MM02

Hello experts,
I need a exit in the Tcode MM0x to check the number range of the material.
ie) when the user enters a material number in MM02 and press the button Select
views I need to check the material number range is available in a customised table.
Any ideas.
Thanks in Advance.
Vasanth

Hi vasanth,
There are three exits available for MM01 & MM02.
Exit Name           Description
MGA00001            Material Master (Industry): Checks and Enhancements
MGA00002            Material Master (Industry): Number Assignment
MGA00003            Material Master (Industry and Retail): Number Display
Probably, the first exit may be of use to you. Beacuse, The customer exit is in function module MATERIAL_UPDATE_ALL. The function
module checks the data for errors (logical relationships, foreign keys,
fixed domain values, and so on) when the material master is updated.
Use
    o   New fields
        You can make checks possible for new fields of your own. These checks
        must be identical to the checks that you carry out for your new
        fields in online maintenance.
    o   Existing fields
        For existing fields, you can extend and intensify the checks.
    You can also change data for descriptions and general material data
    (MARA). For example, the descriptions can be generated from attributes of
    the material.
Regards,
JLN
P.S. mark points for all helpful answers

Add a custom-field in the table MARC and manage it in MM01/MM02/MM03

Good day to all of you!
I have this task: To add a custom-field to the table MARC. This custom-field will be managed through the MM01/MM02/MM03 transaction as follows:
In the Basic Data 1 or Basic Data 2 the custom-field data will be added. Let's say the field is MATNR OBSOLETE.
I have searched and implemented the things in customizing: Made a copy of function group MGD1, added the field on the screen.
MY PROBLEM! How to manage it??? When the user enters MM01/MM02/MM03 and update this field, the field should be updated in MARC.
1. I am not sure that this custom-field should be on Basic Data1 or Basic Data2.They want it at plant level.
2. How to manage the data transfer from SAP Standard Program and my Custom Function Group.
PLs: Do not paste me link to sap technical site with that example, because there takes the custom fields and UPDATE a CUSTOM TABLE. I need to update MARC!
All the documentations i have read until now tell you how to add the field, ONLY the first part of the SOLUTION.
Any help, pls?
Good day and thank you!

Hi Alex,
In which way you are trying to update that custom filed. Have you written any logic in EXITS/BADIS?
http://pavelgk.pbworks.com/f/6729224-Implement-Screen-Exit-for-MM01-Adding-New-Fields-in-Screen.pdf
and
Just read the OSS note mentioned earlier.
Symptom
You want to integrate customer-specific fields in material master maintenance.
Other terms
SAPLMGMM, RMDATIND, ALE, CI_MMH1, EXIT_SAPLMGMU_001
Solution
To add customer-specific fields to an existing material master table (such as MARA or MARC) , you can proceed as follows as of Release 3.0C:
      1. Use an append structure to add the fields to the required table in the Dictionary (this is not a modification; for details, see the SAP document "ABAP/4 Dictionary"). In Release 3.x, the length of the field names must be the same as the standard five character fields. This is necessary because of dynamic assignments. As of Release 4.0A, the lengths of the field names can be longer than five characters. If the changes of the fields should be recorded in the change document and taken into account during ALE distribution, set the 'Change document-relevant' indicator for the corresponding data elements. For table MARA in Release 3.x, you must also enhance the database view MARU because the database changes are carried out using this view. This small modification is no longer necessary as of Release 4.0A because the database view MARU is enhanced automatically when you enhance table MARA or the include EMARA (which is the data part of table MARA).
      2. Enhancing online maintenance in customized material master maintenance:
      Define a subscreen with your customer-specific fields in a customer-specific function group created as a copy of the standard function group MGD1.
      In Customizing, assign this subscreen to a maintenance screen using the "Copy customized material master" function. For details, see the Implementation Guide (IMG). As of Release 4.0A, program COPYMGD1 is available. You can use this program to create customer-specific function groups as required. This program is also incorporated in the Customizing function 'Configure customized material master'. Ensure that each field of the subscreen has a field statement in the flow logic, otherwise the data is not transported correctly. You can use subscreen SAPLMGD1 2002 as an example.
      If you want these fields to be subject to standard field selection, you must add new entries for them to the central field table for material master maintenance (T130F):
      Application examples for standard field selection:
      The field is mandatory and is to be flagged with a "?".
      The field belongs exclusively to the purchasing user department. Purchasing data and MRP data are both contained on one screen. However, the MRP controller is not to see the purchasing data.
      The following data is required for each field:
            a) Field name        (T130F-FNAME)
            b) Field selection group (T130F-FGRUP)
            Here, you should use a standard field group if the customer field is subject to the same field selection as the standard fields of the standard field group. If it is not, use a customer-specific field group.
            You must then check and, if necessary, modify the attribute of the field group using the function "Maintain field selection for data screens" in Customizing under "Logistics Basic Data -> Material Master".
            Field groups 111 through 120 that are not used in the standard system are reserved as customer-specific field groups. As of Release 3.0F, additional customer field groups are available. (For details, see the IMG).
            c) Maintenance status (T130F-PSTAT)
            List of the user departments that may maintain the field. You can display possible values by using the input help for the maintenance status field in the Customizing activity "Configure Material Master" when maintaining logical screens.
            d) Reference        (T130F-KZREF)
            This indicator must be set if the field from the reference material should be proposed during creation with reference.
Note: You cannot yet use Customizing to enhance table T130F; you can use only transaction SE16 (Data Browser) or transaction SM31. Future releases will include a separate Customizing function for maintaining customer-specific fields. See Note 306966. By implementing this note you can add entries to table T130F within Customizing. This type of maintenance is possible as of Release 4.5B.
You may change the entries for standard fields only with regard to the reference data and field selection group. Changing other data for standard fields constitutes a modification. Therefore, you cannot use the Customizing function "Assign Fields to Field Groups" to change this data.
In addition, you must not add new standard fields to table T130F.
      3. If you want to maintain customer-specific fields using data transfer by direct input or via ALE distribution, proceed as follows:
      Add the fields to central field table T130F (see above).
      Add the customer-specific fields to the data structures for the data transfer (for example, BMMH1 for the main data).
      Also, add the customer-specific fields to the tables in which the incorrect data is stored during direct input. These tables have the same name as the corresponding master data table and also have the suffix _TMP.
      For example: If you add customer-specific fields to table MARA, you should add the same fields to table MARA_TMP.
      If you use ALE, you must also add fields to the IDoc. To process enhanced IDocs, you can use enhancement MGV00001 with customer exit EXIT_SAPLMV01_002 for creating the IDocs and customer exit EXIT_SAPLMV02_002 for posting the IDocs.
      Prior to Release 3.0E, enhancing structure BMMH1 constitutes a modification. In this case, you must add the new fields tot the end of the structure before the last field (SENDE = record end indicator).
      As of Release 3.0F, structure BMMH1 contains the customer include CI_MMH1, which is part of the enhancement MGA0001. Here, you must proceed as follows:
            a) Add the customer-specific fields to include CI_MMH1.
            The names of the fields in CI_MMH1 must be identical to those of the corresponding fields in material master tables MARA, MARC and so on.
            Important: The fields must be CHAR type fields. Therefore, create CHAR type data elements whose lengths are identical to the output length of your fields in table MARA and so on. Use these data elements in include CI_MMH1, but use the field names from table MARA and so on.
            b) Activate include CI_MMH1.
            c) If you have not used customer structure ZMMH1 before, create it as a copy of structure BMMH1 and delete the standard fields that you do not require. You are not permitted to delete field STYPE and include CI_MMH1 when doing this. If you have already used structure ZMMH1, add include CI_MMH1 to it.
            d) Activate structure ZMMH1. This also adds the customer-specific fields to ZMMH1.
Run program RMDATING. This program generates routines which are supplied to your customer-specific fields from the input file. As of Release 4.5A, you also need to activate the routines/function modules generated by program RMDATING (especially, the MAT_MOVE_BMMH1_XXXX modules). Details about this subject (especially the procedure when using customer structure ZMMH1) are described in the IMG for transferring the material data under item 'Maintain Transfer Structure'. Also, check the declaration of structure WA in program RMMMBIMC to see whether it is declared with sufficient length. If necessary, enhance the declaration (for the time being, this still constitutes a minor modification).
In addition, lengthen domain DI_DATA with CHAR 5000. As of Release 3.1H, this has already been done.
Important: When using customer-specific fields, you can use only structure ZMMH1 to transfer the data. Otherwise, after the next SAP upgrade which contains new standard fields in structure BMMH1, the input files no longer match. If you want these new standard fields to be transferred, add them after your customer-specific fields (the order of the fields in structure ZMMH1 does not need to be the same as the order of the fields in BMMH1).
If you want foreign key dependencies or fixed domain values to be checked, or another check for a customer field, this is possible up to and including Release 3.0D only by modifying the corresponding check function modules. As of Release 3.0E, you can use function exit EXIT_SAPLMGMU_001 (SAP enhancement MGA00001) for these purposes.
If you want to use engineering change management to schedule future changes for your customer-specific fields or you want to use the 'Display at Key Date' function, execute program GENERATE in addition. This program generates the necessary assignments for interpreting the change documents. With regard to engineering change management, you must read Notes 60281, 60973, and 48962.
To date, it is not possible to integrate customer-specific tables in material master maintenance without making a modification. However, you can create customer-specific development objects containing the essential additional logic. You can then integrate these development objects in your system as part of only a minor modification.
check this link. It may helps you to solve your issue.
Thanks
Sravan

How is ALE working when attached document into MM01/MM02 (MATMAS? DOCMAS?)

Hi folks,
Iu2019m currently working on a project which require to know about :
u2022     SAP Document Management System (DMS) via CV01n/CV02n/CV03n
u2022     SAP Material Management (MM) via MM01/MM02/MM03 with u201CDocument Datau201D view in u201CAdditional Datau201D in order to assign a Document Data to a material
u2022     SAP ALE (iDocs) related to document linking with material (MATMAS ? DOCMAS ? etc.)
We need today to understand more the process of linking a document to a material and u201Ctransportu201D the change data through iDocs:
- DOCMAS is apparently transporting changes done on documents in CV01n/CV02n.
- MATMAS, ZMATMAS or ZMATMASR do not seem to transport any changes about documents linked to material into "Document Data" tab of "Additional Data" button in MM01/MM02
So,
- how can we detect changes done into "Document Data" tab of MM01/MM02 and transport via iDocs ?
- Moreover, which data should be transported ( document number, etc.) ?
Thanks in advance
Pierre

Hello Gerald
have you created your webtemplate with the WAD 7.0? Then you can only access it via the "new" Bex Web Java runtime with this URL:
http://<server>:<j2ee-port>/irj/servlet/prt/portal/prtroot/pcd!3aportal_content!2fcom.sap.pct!2fplatform_add_ons!2fcom.sap.ip.bi!2fiViews!2fcom.sap.ip.bi.bex?TEMPLATE=MYTEMPLATE
The path /sap/bw/BEx points to the "old" ABAP runtime.
But why do you want to integrate your template in the BPS web page, anyway? If you put your application into the portal, you can create a page in the portal with an iView for BPS and a second iView for the Bex 7.0 webtemplate. I think this would be much more convenient.
Best regards
Martin

Mm01/mm02 different views, bdc

Similar Messages

Maybe you are looking for