Different material types

Could you please explain/ help with the below queries.. with some practical example, if possible.... differehnce between FHMI (production resources/tools) and HIBE (operating supplies) and ROH (raw materials)?
Actually for all above mentioned types.. it is written as procured externally for processing.... so i have doubts why three diff material types as all are procured for same purposes.... like use for production...
Regards,
Krupesh Kothari.

Hi ,
FHMI (production resources/tools)
Production resources/tools are procured externally and used in the manufacture of products. A material master record of this material type can contain purchasing data, but no sales data. It is managed on a quantity basis. Examples of production resources/tools are apparatus, equipment, and measuring and testing devices.
HIBE (operating supplies)
Operating supplies are procured externally and required for the manufacture of other products. A material master record of this material type can contain purchasing data but no sales data.
ROH (raw materials)
Raw materials are always procured externally and then processed. Since raw materials cannot be sold, a material master record of this material type contains no sales data.
Regards,
Anupam

Similar Messages

Different Material Types in different Plants

Hi,
I have 2 Plant under a Company Code. A material being produced in plant A has to be sent to Plant B for further processing. I would like to maintain single material master for both the plants, but different Material Types. Material has to be treated as Finished Goods in Plant A and Raw Material at Plant B. Could any one please let me know how I can MAP it in SAP.
Regards,
Nagaraja Achar.

Hi,
For the Same material Code you can not maintain two material types in two plants..
But you can make a Z* mat type with all the relevant views of FG & ROH..
For Plant 1 it will have all the views
and for Plant 2 extend only the ROH relevant views...
Thx
Raju

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.

Use of different material types

Hi Experts ,
My client is thinking of expansion of its plant . This new plant would be copy of their already existing plant at another location . Now some of materials for manufacturing finish materials are same in both plants but they both use different material types . That is here there is only one mat type where there they use 4 mat types .
Now do I need to create new plant here or I can use the same existing plant for creation of new materials ? If I want to use the same plant then would be the effect on valuation of mat. Can these mat with different mat types be transported successfully ?

Hi Neal,
So you did enjoy your weekend!!! Good good; well you go to IMG ( SPRO ) and on to ENTERPRISE STRUCTURE >> ASSIGNMENT >> LOGISTICS EXECUTION; and just in case you miss out the warehouse number, ENTERPRISE STRUCTURE >> DEFINITION >> LOGISTICS EXECUTION . You will find the links there. Unfortunately I created a screenshot for you but I just do not know how to attach it.
The list I was talking about was MRP List or Stock overview list ( MD05 / MD04 ). There are two more transactions that I think might come in handy. Check them out:
LS26 - stock overview of warehouse.
LL01 - warehouse activity monitor.
Since the plant and warehouse will be linked, I guess there would be no discrimination on checking stock but I am pretty sure system checks warehouse stock first. That is the entire procedure. I hope it helps. Do reward points if I was able to answer your query.
Regards,
Sreekant.

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

BDC for MM with different material types.

Hi, Can anyone explain me how the MM01 tcode can be handled in BDC, when material with different material types are present in the flat file. Different material types have different views and hence different recordings....How to handle this scenario?

Based on different types of material, you can able to find out which all views are required to call through BDC. Try to find out views by using tables MARA, MAKT, MARD, MARC etc. Once it is confirmed you can call views using screen numbers.
Here I don't think so more than one recording is required. Record MM01 transaction using Basic Data1, once you go inside the transaction select all the views required to complete the MM01 transaction. It will record all the views (hence screen numbers), then you can switch/call views based on screen numbers.
Hope this helps you to resolve your query.

GR output quantity for different material types using 101 mvt

Hi All
Is it possible to have separate GR slip quantities for the same movement type (101) but for different stock types.
I would like 3 GR slips for mvt type 101 for directly procured materials AND
I would like 1 GR slip for mvt type 101 for stock materials
Therefore, the material type on goods receipt would decide how many GR slips would be printed.
What config is necessary?
Thanks in advance
Darren

material type is fixed for a material, it is not changed for GR.
you can make no of GRs or one po.
for stock items you need to make one PO and matrial for account assignment need separete PO.
account assignment PO > material direclty goes to cost center and consumption accouont
no configuration required.

Stock transfer of different material type

Sir,
finish material of one plant is raw material for other plant. i've to use intercompany stock transfer. How should i cope up with material types? How accounting and excise register entries will effect?

Dear shailesh jagtap
Hi how r u??
Actually The first and foremeost thing that you should remember is that Finished goods should always have Sales View and not Purchase view,Secondly Raw material should never have Sales View.
And Semi finish can have Purchase as well as Sales view.
So if u got stuck in the situation wherein u have to purchase the material and also sell
in that case use material type as HALB
Whereas in some cases if at all it is required then in that case u can set the Purchase view to finish goods or u can set sales view for ROH(Raw amterial)
in logistic general-Material master -AMterial types just for ROH or FERT select the views u require
REgds
shailesh

Different material type picking in LSMW.

Hi,
In creating the MM data through LSMW,
Ist material picks ZRFM material type which is not having purch & Acc views,
where as next 9 materials picks HALB material type(Correct mat type).
In input file, all materials(10 Nos) have HALB mat type and corresponding fields.
Can you tell, wha could be the reason.
Madhu.

Hi,
Do you see ZRFM as material type for the 1st entry in display read data or display converted data ?
I thinkyou are using a recording and in the recording you may have had entered ZRFM against material type. Go into change recording and clear the default value in the recording.
Pavan

Help needed for creating 1 invoice for 2 different material types.

Dear, Gurus
I really need help here I have spent 3 days cracking my head trying to solve the problem. Problem is client was creating invoice with reference to order and while invoice was being made it would cause an invoice split. The materials involved are Trading Good and Service Material. They would like only 1 invoice. Note nothing was different except material group and item cat. of the material. payment terms billing dates partners everything is same.
Current item config for Trading Good material is ZMPI-project item cat.
Copying requirements   023 Item ord.ref. w/o AZ        Billing quantity     A
Data VBRK/VBRP         000                                           Pos./neg. quantity   +
                                                                                Pricing type         K
                                                                                PricingExchRate type
                                                                                Price source
Current item config for service Material is TAD-Service
Copying requirements   002 Item/order-related          Billing quantity     A
Data VBRK/VBRP         001 Inv.split (sample)            Pos./neg. quantity   +
                                                                                Pricing type         G
                                                                                PricingExchRate type
                                                                                Price source
I was told to change Data VBRK/VBRP to 003 One Invoice which I did in both of these item cat. and yes they worked perfectly but at time of creating the invoice for service material the qty that showed was 11. Note: In sales order it is 1 qty. So I went back into the config of item cat TAD and changed copying requirement to 023 instead of 002 but nothing changed. Seems a qty of 10 is referencing something else which I have no idea what or where it is picking this up from. Just to see or test things I went into the sales order and tried changing the service material qty then a weird popup appears and says service order 12344456 has been blocked. (Seriously I have no idea why this would happen or should be existing at all.) Even if for some reason it is being referenced the service order that is existing is qty 1.
I really really do need help and if someone can help me that would be god sent.
Regards, Ali

You did not mention what value is maintained in the field billing quantity in the copy control->Item settings. Check for the service item, what value is assigned. Put value A and re-test.
Note that whenever you change any settings in configuration side, you need to create a new documents to test the results of the settings. You should not use the existing documents.
When you say the document is blocked, then check the status of the sales order to find the reason for blocking (like credit block, approval etc)..
Regards,

Issue in selecting material types as a saleable material

I have created different material types for finished good , like finished good, trading goods , physician sample , imported physician sample and promo materials.
i want at the time of sales all above types of material should be available for sale.
kindly help me out that how can i restrict system to sale only these material types.

Hi shadab
For the material types you want to sell stocks update the value and quantity and value in OMS2 for the plant where as for the material types which you don't wont to sell the stock don't update the quantity and value in OMS2 for the plant.Secondly for the material types which you don't want to sell the stock also don't maintain any stock.
But if you want all above material types for sale then maintain stock to create sales order and in OMS2 also update the quantity and value for the plant
Regards
Srinath

Valuation class & material type

Hi all ,
Can anyone plz tell me the answer on following
What establishes the relationship between a valuation class and material type
A.     Valuation grouping code
B.     G/L account
C.     Valuation category
D.     Valuation grouping code.
E.     Account category reference
Thanks in advance
Shreek

i think more than one answer should be correct for this question. The valuation class makes it possible to:
Post the stock values of materials of the same material type to different G/L accounts
Post the stock values of materials of different material types to the same G/L account
On the other hand, a account category reference is Group of valuation classes that the system uses to check whether the valuation class you have entered is allowed when you maintain accounting data in a material master record.
So i think the answer should be G/L account, Account category reference and Valuation category.
Please refer to the site:
http://help.sap.com/saphelp_470/helpdata/en/47/60feb949f011d1894c0000e829fbbd/content.htm
http://www.sap-img.com/mm024.htm
I think it will be helpful to you.
Thanks,
Nisha

Material type in Material master

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

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

Material Type Change Implication

Hi all,
What are the implication of changing the material type of existing materials?
Kiki

Hi Kiki
Implication of material typpe change. First of all you can change if the stock is nil.
1) If you have maintained different storage location for different material type. The location will change.
2) Further The valuation for each material type is different.
we have to change accordingly.
3) Screen group selection is based on the material type, this will change.
4) Procurement type will be based on the material type.
5) Material group is based on material type.
6) Even base unit will be different for different material type. in some industries for Ex FERT and HALB will be in PC, EA etc., and ROH will be in Kgs.
Hope this will clear your doubt.
Regards
J . Saravan

Authorization based on Material Type.

Hello Expert,
We have different material type but we want give access based on Material Type to User.
For Eg. In Transaction Code :- ME39 Display Scheduling agreement Schedule
I wants to restrict user from access/Component Overview of particular material type.
how to do this, This is the client requirement.
thanks,

Hi Julius,
of course it is not possible. the multitude of application transactions cares nothing about authorisation objects bound to the material master like M_MATE_MAR or the other one with authorisation groups (which has the additional disadvantage that you would have to group all materials ...)
This subject has been stated in this forum various times, I put a small link farm here (only the most recent/relevant from the search function ):
So, here goes ... one more time: ME39 does not care about material master related authorisation objects unless you make it do so by coding something or other ...
Edited by: Mylène Dorias on Jan 18, 2010 8:29 AM

Different material types

Similar Messages

Maybe you are looking for