User Authorizations for Plant & Material Type
The requirement says
Get all the users having authorizations to transactions - QA11, QA12, MSC1N, MSC2N & MSC4N.
Then filter out the users to those who have access to Plant & material Type which are entered on the selction- screen.
now how to get those users who have access to Plant and/or Material Type entered on the selection-screen.
Plz reply
Thanks in advance
Hi suresh,
check the following standard program ,probably would be useful to you.
<b>RSUSR010 Transactions that can be executed by users, with Profile or Authorization</b>
If you want the table for "user profile change history ", below tables can help you:
<b>USH10
USH02
USH03
USH12
</b> Also check the following Tables would be useful,
<b>UST12</b>
Authorizations and Tcodes per Profile
<b>UST04</b>
Assignment of users to Profiles
<b>AGR_USERS</b>
Assignment of roles to users
<b>USOBT_C</b>
Authorizations associated with a transaction
<b>USR02</b>
Last logon date, locked IDs
<b>AGR_TCODES</b>
Assignment of roles to Tcodes (4.6 tcodes)
<b>USH02</b>
Change history for users (e.g. who last changed users via SU01)
<b>USH04</b>
Display history of who made changes to which User Ids
<b>
USR40</b>
Non-permitted passwords
<b>USR41</b>
Users with logon information (multiple logons)
I have given u all possible tables,and the standard program select the according to your need.
should solve ur problem.
Thanks & regards,
Pawan P. Khilari
Similar Messages
-
QM: Authorization for plant, insp type and transaction
Hi,
I haven't found a way to solve this problem. Maybe you know better.
I would like to create an authorization profile that allows a user to view inspection lots and results in plant A and B for certain inspection types. Furthermore, the user should be able to edit these lots and record results to these lots in plant A, but in plant B he should only be able to view them.
Any idea?
Thanks, Marcus.Hi ,
Please activate inspection type 08 stock transfer ..
If this inspection type is active then during stock transfer lot gets generated.
Also check QM active for this perticular movement in custamizing setting.
Regards
SANIL -
Uploading data in MM01 for different material types
Hi,
I have a doubt regarding uploading the data in MM01 for different material types.
Generally in MM01, we have different views for different material types. The number of views will vary depending upon the material type that we select.
I have a scenario, where in to upload the data, I have a flat file that consists of data for different message types. So, how to upload the data in such case.
Can anyone help me on the same by providing explanation or sample code...? What would be the possible ways to upload data in such scenario.
That would be of great help.
Thanks & Regards,
Pradeep.See the below code and use FM SELECTION_VIEWS_FIND..
REPORT zjpmuim306 NO STANDARD PAGE HEADING LINE-SIZE 250 MESSAGE-ID
zjpm001.
*& I N B O U N D V I A A B A P : Batch input Session method *
*& Development ID: IM_DD_306_LJP *
*& Report : ZJPMUIM306 *
*& The Purpose of the Object is to interface Create Input Record *
*& for SAP Migration from the Material master of BPCS All the *
*& information received at BPCS is collected into a single record. *
*& By using session method upload data from file ,one item is
*& created for one record *
*& Change Log: *
*& Init Who Date Text *
*& MALIKDH1 Seshu Reddy 26-07-2003 Initial Version *
Constants *
CONSTANTS:c_vkorg(4) type c value 'JP20', " Sales Organization
c_vtweg(2) type c value 'TR' , " Distribution Channel
c_werks(4) Type c value 'JP01' , " Plant
c_viewlist(15) VALUE 'KDEALBSZXVPCFQG'," View list
c_scm_view TYPE msichtausw-dytxt VALUE 'SCM View',
c_sd_view TYPE msichtausw-dytxt VALUE 'SD View',
c_seq_code(2) VALUE 'Z1', " Sequential Code
c_keep(1) TYPE c VALUE 'X', " Keep
c_group LIKE apqi-groupid VALUE 'IM306', " Session Name
c_tcode LIKE tstc-tcode VALUE 'MM02', " Transaction Code
c_blank(1) VALUE ' ', " Blank
c_intls(1) VALUE 'N'. " Logistic Status
Variables *
DATA: g_flag1(1), " Variable to hold
g_flag(1), " Variable to hold
g_file LIKE rlgrap-filename VALUE
'C:\Documents and Settings\seshur\Desktop\HCLT123.CSV'. " File name
Internal tables/ Work area *
Internal Table for Delimter
DATA : BEGIN OF t_delim OCCURS 0,
text(1000),
END OF t_delim.
Internal table for BDC processing
DATA : t_bdcdata LIKE bdcdata OCCURS 0 WITH HEADER LINE.
Internal table for holding the data which has to be uploaded.
DATA: BEGIN OF t_bpcs OCCURS 0,
matnr(15) TYPE c, " material no
dosage(40) TYPE c, " Dosage form(Local)
appearance(40) TYPE c, " Appearance
idcode(6) TYPE c, " Identification Code
prostformno(10) TYPE c, "SOP
weitab(7) TYPE c, " Weight/tablet
uom1(2) TYPE c, " UOM of Carton
uom2(2) TYPE c, " UOM of Case
carsize(14) TYPE c, " Carton size
cassize(14) TYPE c, " Case size
rupqty(11) TYPE c, " Round up
abvname(3) TYPE c, " Product short name
END OF t_bpcs.
*Internal table for t_bpcs
DATA: BEGIN OF t_mdata OCCURS 0,
matnr LIKE marc-matnr, " Material number
zzjp_dos_frm LIKE marc-zzjp_dos_frm, " Dosage form(Local)
zzjp_aprn LIKE marc-zzjp_aprn, " Appearance
zzjp_con_id LIKE marc-zzjp_con_id," Identification Code
zzjp_nyu_sop LIKE marc-zzjp_nyu_sop,"SOP
zzjp_wei_tab(10) type c , " Weight/tablet
zzjp_bio LIKE marc-zzjp_bio,"Biologics Indicator
zzjp_itf LIKE marc-zzjp_itf, " ITF code
zzjp_car(2) type c, " UOM of Carton
zzjp_cas(2) type c, " UOM of Case
zzjp_car_size(11) type c," Carton size
zzjp_cas_size(11) type c, " Case size
zzjp_rupqty(11) type c, " Round up
zzjp_init_ls LIKE marc-zzjp_init_ls, " Logistic Status
zzjp_re1 LIKE marc-zzjp_re1, "Document type(Local)
zzjp_re2 LIKE marc-zzjp_re2, "Report type
zzjp_re3 LIKE marc-zzjp_re3, "Shipping report type
zzjp_pro_id LIKE mvke-zzjp_pro_id," Product output sequence
zzjp_bu_id LIKE mvke-zzjp_bu_id, " Business unit indicator
zzjp_abv_name LIKE mvke-zzjp_abv_name," Product short name
zzjp_abv_id1 LIKE mvke-zzjp_abv_id1," Product short name output
zzjp_abv_id2 LIKE mvke-zzjp_abv_id2," Product short name internal
zzjp_spl_id LIKE mvke-zzjp_spl_id, " Sample internal order
END OF t_mdata.
Internal table for Mara Table
DATA: BEGIN OF t_mara OCCURS 0,
matnr LIKE mara-matnr, " material Number
vpsta LIKE mara-vpsta, " Maintenance status of complete material
pstat like mara-pstat, " Maintenance status
END OF t_mara.
Internal table for Material Master View Selection Screens
DATA: BEGIN OF t_bildtab OCCURS 0.
INCLUDE STRUCTURE mbildtab.
DATA: END OF t_bildtab.
internal table for T_bildtab
DATA: t_bildtab_dup LIKE t_bildtab OCCURS 0 WITH HEADER LINE.
*Work area for T_bildtab internal table(Views Selection)
DATA: BEGIN OF w_data,
flag1 type c,
anzd70 TYPE i,
field1(20) type c,
field2(20) type c,
field3(20) type c,
field4(20) type c,
count(2) TYPE c,
END OF w_data.
Main Processing *
START-OF-SELECTION.
Store data from file into internal table
PERFORM f_uplaod_data.
Transfer the uploaded data into t_mdata internal Table
PERFORM f_process_data.
Selecting The views based on Material number
PERFORM f_view_list.
Open a BDC Session
PERFORM f_bdc_open.
*Selecting the fields from mara table
SELECT matnr
vpsta
pstat
FROM mara
INTO TABLE t_mara
FOR ALL ENTRIES IN t_mdata
WHERE matnr = t_mdata-matnr.
SORT t_mara BY matnr.
SORT t_mdata BY matnr.
Transfer the uploaded data into BDCDATA structure
PERFORM f_process_bdc.
Close The BDC Session
PERFORM f_close_group.
*& Form F_VIEW_LIST *
Routine to used for Calling the function module *
Selection_views_find *
FORM f_view_list.
CALL FUNCTION 'SELECTION_VIEWS_FIND'
EXPORTING
bildsequenz = c_seq_code
pflegestatus = c_viewlist
TABLES
bildtab = t_bildtab
EXCEPTIONS
call_wrong = 1
empty_selection = 2
OTHERS = 3.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " F_VIEW_LIST
*& Form f612_view_sort *
Routine to used for Selecting The views based on Material Number *
FORM f612_view_sort.
t_bildtab_dup[] = t_bildtab[].
Reading the Internal table t_mara
READ TABLE t_mara WITH KEY matnr = t_mdata-matnr.
TRANSLATE t_mara-pstat USING ' $'.
CLEAR: w_data-flag1, w_data-anzd70.
LOOP AT t_bildtab_dup.
IF t_bildtab_dup-pstat CA t_mara-pstat.
w_data-anzd70 = w_data-anzd70 + 1.
IF t_bildtab_dup-kzanz IS INITIAL.
t_bildtab_dup-kzanz = 'X'.
w_data-flag1 = 'X'.
MODIFY t_bildtab_dup.
ENDIF.
ELSE.
IF NOT t_bildtab_dup-kzanz IS INITIAL.
CLEAR t_bildtab_dup-kzanz.
w_data-flag1 = 'X'.
MODIFY t_bildtab_dup.
ENDIF.
ENDIF.
ENDLOOP.
TRANSLATE t_mara-pstat USING '$ '.
IF NOT w_data-flag1 IS INITIAL.
SORT t_bildtab_dup BY kzanz DESCENDING idxbd ASCENDING.
ENDIF.
*Reading The internal table for T_bildtab_dup
READ TABLE t_bildtab_dup WITH KEY dytxt = c_scm_view.
IF t_bildtab_dup-kzanz = 'X'.
WRITE sy-tabix TO w_data-count.
w_data-count = w_data-count + 2.
IF w_data-anzd70 > 18.
w_data-count = w_data-count - 18.
ENDIF.
CONCATENATE 'MSICHTAUSW-DYTXT(' w_data-count ')' INTO w_data-field1.
CONCATENATE 'MSICHTAUSW-KZSEL(' w_data-count ')' INTO w_data-field2.
ENDIF.
READ TABLE t_bildtab_dup WITH KEY dytxt = c_sd_view.
IF t_bildtab_dup-kzanz = 'X'.
WRITE sy-tabix TO w_data-count.
IF w_data-anzd70 > 18.
w_data-count = w_data-count + 2.
w_data-count = w_data-count - 18.
ENDIF.
CONCATENATE 'MSICHTAUSW-DYTXT(' w_data-count ')' INTO w_data-field3.
CONCATENATE 'MSICHTAUSW-KZSEL(' w_data-count ')' INTO w_data-field4.
ENDIF.
ENDFORM. " f612_view_sort
*& Form f_uplaod_data *
Routine to used for Uploading the data from file to Internal table *
FORM f_uplaod_data.
CALL FUNCTION 'WS_UPLOAD'
EXPORTING
filename = g_file
filetype = 'DAT'
TABLES
data_tab = t_delim
EXCEPTIONS
conversion_error = 1
file_open_error = 2
file_read_error = 3
invalid_type = 4
no_batch = 5
unknown_error = 6
invalid_table_width = 7
gui_refuse_filetransfer = 8
customer_error = 9
OTHERS = 10.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
IF t_bpcs IS INITIAL.
LOOP AT t_delim.
SPLIT t_delim-text AT ',' INTO t_bpcs-matnr
t_bpcs-dosage
t_bpcs-appearance
t_bpcs-idcode
t_bpcs-prostformno
t_bpcs-weitab
t_bpcs-uom1
t_bpcs-uom2
t_bpcs-carsize
t_bpcs-cassize
t_bpcs-rupqty
t_bpcs-abvname.
APPEND t_bpcs.
ENDLOOP.
ENDIF.
ENDFORM. " f_uplaod_data
*& Form F_BDC_OPEN
Routine to create BDC Session to be processed
FORM f_bdc_open.
CALL FUNCTION 'BDC_OPEN_GROUP'
EXPORTING
client = sy-mandt
group = c_group
keep = c_keep
user = sy-uname
EXCEPTIONS
client_invalid = 1
destination_invalid = 2
group_invalid = 3
group_is_locked = 4
holddate_invalid = 5
internal_error = 6
queue_error = 7
running = 8
system_lock_error = 9
user_invalid = 10
OTHERS = 11.
IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ELSE.
MESSAGE S000 WITH 'Batch input session is created successfully'(T02).
ENDIF.
ENDFORM. " F_BDC_OPEN
*& Form F_PROCESS_BDC
Processing of BDCDATA Structure
FORM f_process_bdc.
LOOP AT t_mdata.
PERFORM f612_view_sort.
PERFORM f_bdc_dynpro USING 'SAPLMGMM' '0060'.
PERFORM f_bdc_field USING 'BDC_CURSOR'
'RMMG1-MATNR'.
PERFORM f_bdc_field USING 'BDC_OKCODE'
'=AUSW'.
PERFORM f_bdc_field USING 'RMMG1-MATNR'
t_mdata-matnr.
PERFORM f_bdc_dynpro USING 'SAPLMGMM' '0070'.
PERFORM f_bdc_field USING 'BDC_CURSOR'
'MSICHTAUSW-DYTXT(01)'.
IF w_data-anzd70 > 18.
PERFORM f_bdc_field USING 'BDC_OKCODE'
'=P+'.
PERFORM f_bdc_dynpro USING 'SAPLMGMM' '0070'.
PERFORM f_bdc_field USING 'BDC_OKCODE' '/00'.
ENDIF.
reading the t_bildtab internal table
READ TABLE t_bildtab_dup WITH KEY dytxt = c_scm_view.
IF t_bildtab_dup-kzanz = 'X'.
PERFORM f_bdc_field USING 'BDC_CURSOR'
w_data-field1.
PERFORM f_bdc_field USING w_data-field2 'X'.
g_flag = 'X'.
ENDIF.
reading the t_bildtab internal table
READ TABLE t_bildtab_dup WITH KEY dytxt = c_sd_view.
IF sy-subrc EQ 0.
g_flag = 'X'.
ENDIF.
IF t_bildtab_dup-kzanz = 'X'.
PERFORM f_bdc_field USING 'BDC_CURSOR'
w_data-field3.
PERFORM f_bdc_field USING w_data-field4 'X'.
g_flag1 = 'X'.
ENDIF.
IF g_flag = 'X' AND g_flag1 = 'X'.
PERFORM f_bdc_dynpro USING 'SAPLMGMM' '0080'.
PERFORM f_bdc_field USING 'BDC_CURSOR'
'RMMG1-VTWEG'.
PERFORM f_bdc_field USING 'BDC_OKCODE'
'=ENTR'.
PERFORM f_bdc_field USING 'RMMG1-WERKS'
c_werks.
PERFORM f_bdc_field USING 'RMMG1-VKORG'
c_vkorg.
PERFORM f_bdc_field USING 'RMMG1-VTWEG'
c_vtweg.
CLEAR g_flag.
CLEAR g_flag1.
ELSE.
IF g_flag = 'X'.
PERFORM f_bdc_dynpro USING 'SAPLMGMM' '0080'.
PERFORM f_bdc_field USING 'RMMG1-WERKS'
c_werks.
PERFORM f_bdc_field USING 'BDC_OKCODE' '/00'.
ELSE.
IF g_flag1 = 'X'.
PERFORM f_bdc_dynpro USING 'SAPLMGMM' '0080'.
PERFORM f_bdc_field USING 'BDC_CURSOR'
'RMMG1-VTWEG'.
PERFORM f_bdc_field USING 'RMMG1-WERKS'
c_werks.
PERFORM f_bdc_field USING 'RMMG1-VKORG'
c_vkorg.
PERFORM f_bdc_field USING 'RMMG1-VTWEG'
c_vtweg.
PERFORM f_bdc_field USING 'BDC_OKCODE'
'=ENTR'.
ENDIF.
ENDIF.
ENDIF.
*Processing of SCM View
PERFORM f_bdc_dynpro USING 'SAPLMGMM' '4000'.
PERFORM f_bdc_field USING 'BDC_CURSOR' 'MARC-ZZJP_DOS_FRM'.
PERFORM f_bdc_field USING 'MARC-ZZJP_DOS_FRM'
t_mdata-zzjp_dos_frm.
PERFORM f_bdc_field USING 'MARC-ZZJP_APRN'
t_mdata-zzjp_aprn.
PERFORM f_bdc_field USING 'MARC-ZZJP_CON_ID'
t_mdata-zzjp_con_id.
PERFORM f_bdc_field USING 'MARC-ZZJP_NYU_SOP'
t_mdata-zzjp_nyu_sop.
PERFORM f_bdc_field USING 'MARC-ZZJP_WEI_TAB'
t_mdata-zzjp_wei_tab.
PERFORM f_bdc_field USING 'MARC-ZZJP_CAR'
t_mdata-zzjp_car.
PERFORM f_bdc_field USING 'MARC-ZZJP_CAS'
t_mdata-zzjp_cas.
PERFORM f_bdc_field USING 'MARC-ZZJP_CAR_SIZE'
t_mdata-ZZJP_CAR_SIZE.
PERFORM f_bdc_field USING 'MARC-ZZJP_CAS_SIZE'
t_mdata-ZZJP_CAS_SIZE.
PERFORM f_bdc_field USING 'MARC-ZZJP_RUPQTY'
t_mdata-ZZJP_RUPQTY.
PERFORM f_bdc_field USING 'MARC-ZZJP_BIO'
t_mdata-zzjp_bio.
PERFORM f_bdc_field USING 'MARC-ZZJP_ITF'
t_mdata-zzjp_itf.
PERFORM f_bdc_field USING 'MARC-ZZJP_INIT_LS'
t_mdata-zzjp_init_ls.
PERFORM f_bdc_field USING 'MARC-ZZJP_RE1'
t_mdata-zzjp_re1.
PERFORM f_bdc_field USING 'MARC-ZZJP_RE2'
t_mdata-zzjp_re2.
PERFORM f_bdc_field USING 'MARC-ZZJP_RE3'
t_mdata-zzjp_re3.
PERFORM f_bdc_field USING 'BDC_OKCODE'
'/00'.
*Processing of SD View
PERFORM f_bdc_dynpro USING 'SAPLMGMM' '4000'.
PERFORM f_bdc_field USING 'BDC_CURSOR' 'MVKE-ZZJP_PRO_ID'.
PERFORM f_bdc_field USING 'MVKE-ZZJP_PRO_ID'
t_mdata-zzjp_pro_id.
PERFORM f_bdc_field USING 'MVKE-ZZJP_BU_ID'
t_mdata-zzjp_bu_id.
PERFORM f_bdc_field USING 'MVKE-ZZJP_ABV_NAME'
t_mdata-zzjp_abv_name.
PERFORM f_bdc_field USING 'MVKE-ZZJP_ABV_ID1'
t_mdata-zzjp_abv_id1.
PERFORM f_bdc_field USING 'MVKE-ZZJP_ABV_ID2'
t_mdata-zzjp_abv_id2.
PERFORM f_bdc_field USING 'MVKE-ZZJP_SPL_ID'
t_mdata-zzjp_spl_id.
PERFORM f_bdc_field USING 'BDC_OKCODE' '/00'.
PERFORM f_bdc_dynpro USING 'SAPLSPO1' '0300'.
PERFORM f_bdc_field USING 'BDC_OKCODE'
'=YES'.
perform f_bdc_insert.
REFRESH T_BDCDATA.
ENDLOOP.
ENDFORM. " F_PROCESS_BDC
*& Form f_bdc_dynpro
p_prog is the program name to which data is passed *
p_dyno is the screen number to which the data is passed
Routine for populating the BDCDATA structure with the
Screen related information
FORM f_bdc_dynpro USING p_prog
p_dyno.
t_bdcdata-program = p_prog.
t_bdcdata-dynpro = p_dyno.
t_bdcdata-dynbegin = 'X'.
APPEND t_bdcdata.
CLEAR t_bdcdata.
ENDFORM. " F_bdc_dynpro
*& Form F_BDC_FIELD
p_fnam is the field name to which value is passed
p_fval is the field value which is passed
p_fnam is the field name to which value is passed
p_fval is the field value which is passed
FORM f_bdc_field USING p_fnam
p_fval.
t_bdcdata-fnam = p_fnam.
t_bdcdata-fval = p_fval.
APPEND t_bdcdata.
CLEAR t_bdcdata.
ENDFORM. " F_bdc_field
*& Form F_PROCESS_DATA *
Routine to used for moving data from T_bpcs internal table to *
t_mdata Internal Table *
FORM f_process_data.
LOOP AT t_bpcs.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
input = t_bpcs-matnr
IMPORTING
output = t_mdata-matnr.
MOVE t_bpcs-dosage TO t_mdata-zzjp_dos_frm.
MOVE t_bpcs-appearance TO t_mdata-zzjp_aprn.
MOVE t_bpcs-idcode TO t_mdata-zzjp_con_id.
MOVE t_bpcs-prostformno TO t_mdata-zzjp_nyu_sop.
MOVE t_bpcs-weitab TO t_mdata-zzjp_wei_tab.
MOVE c_blank TO t_mdata-zzjp_bio.
MOVE c_blank TO t_mdata-zzjp_itf.
MOVE t_bpcs-uom1 TO t_mdata-zzjp_car.
MOVE t_bpcs-uom2 TO t_mdata-zzjp_cas.
MOVE t_bpcs-carsize TO t_mdata-zzjp_car_size.
MOVE t_bpcs-cassize TO t_mdata-zzjp_cas_size.
MOVE t_bpcs-rupqty TO t_mdata-zzjp_rupqty.
MOVE c_intls TO t_mdata-zzjp_init_ls.
MOVE c_blank TO t_mdata-zzjp_re1.
MOVE c_blank TO t_mdata-zzjp_re2.
MOVE c_blank TO t_mdata-zzjp_re3.
MOVE c_blank TO t_mdata-zzjp_pro_id.
MOVE c_blank TO t_mdata-zzjp_bu_id.
MOVE t_bpcs-abvname TO t_mdata-zzjp_abv_name.
MOVE c_blank TO t_mdata-zzjp_abv_id1.
MOVE c_blank TO t_mdata-zzjp_abv_id2.
MOVE c_blank TO t_mdata-zzjp_spl_id.
APPEND t_mdata.
ENDLOOP.
ENDFORM. " F_PROCESS_DATA
*& Form f_bdc_close
Routine to close the BDC Session
FORM f_close_group.
CALL FUNCTION 'BDC_CLOSE_GROUP'
EXCEPTIONS
not_open = 1
queue_error = 2
OTHERS = 3.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " f_close_group
*& Form f_bdc_insert
routine to input batch data into the Transaction MM02 from the
session created
FORM f_bdc_insert.
CALL FUNCTION 'BDC_INSERT'
EXPORTING
tcode = c_tcode
TABLES
dynprotab = t_bdcdata
EXCEPTIONS
internal_error = 1
not_open = 2
queue_error = 3
tcode_invalid = 4
printing_invalid = 5
posting_invalid = 6
OTHERS = 7.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " f_bdc_insert
Reward Points if it is useful
Thanks
Seshu -
Material Master views for every material type
HI Expertis,
I am facing to the big problem. My requirement is to identify the Material Master Views relevent to the each and every Material Type.
As an example, for the material type "FGTR" what should be the required views to create material master?
From the MM01 Txn i found 36 Material types. Also found the standard views in "OMS2" Txn. But in OMS2 txn it gives me almost all the views in material master.
Atlease i hope to categorize the material types which are going to use same material views. So i can ask abaper to develop it.
these are the required Material types : MODE, FGTR, WETT, KMAT, LEER, LGUT, FERT, FOOD, INTR, CONT, IBAU, HERS, NLAG, NOF1, UNBW, HIBE, VERP, FRIP, PIPE, FHMI, ROH, LEIH, HALB, DIEN, ERSA, HAWA
I would be gratefully thank u, if u can guided me on this matter.
Thanx & Regards,
Rashika.Hi,
You can ask your abaper to write a small program by using table t134(T134-PSTAT) and T132T .From this tables ,for each material type, you get all views.
User department Maintenance status
Work scheduling A
Accounting B
Classification C
MRP D
Purchasing E
Production resources/tools F
Costing G
Basic data K
Storage L
Forecasting P
Quality management Q
Warehouse management S
Sales V
Plant stocks X
Storage location stocks Z
hopw this will help you.
With Regards,
Jaheer -
Control the authorization base on material type level
Dear Experts,
We want to control some users only can create or modify the material base on material type level .
For instance , user A only can modify the 'ROH' type material , he can not maintain any 'FERT' type material .
I set the authorization object 'M_MATE_MAR' in the user A's profile , but it doesn't work .....
System : SAP4.7 x 200
DB : oracle9i
Has someone can tell me it is possibile to control the maintain authorization base on material type level ?
Or give me some suggestions.....
Many thanks
Best Regards,
Carlos ZhangHi
Yes this works & the authorisation object found by you is also correct.
For the object - M_MATE_MAR
Maintain the activity 01,02,03
Maintain the authorisation group - each material type can be assigned to an authorisation group. In OMS2 , you can assign the authorisation groups to the material type.
For E.g if the material type is ROH- enter the authorisation group as ROH.
Ensure that the user does not have this object, As If this object is present in any other role with authorisation group as * then the * will overirde any value.
Thanks & Regards
Kishore
Edited by: Kishore Kumar Chiluka on Jun 13, 2008 11:18 AM -
Allow mov type 261 and 262 for a material type only
Requirement is to allow movt type 261 and 262 for a particular material type.( Assume Only 261 - 262 issue transactions happen against that material type.)
User to be restricted, while material issue (migo), for the material type XXXX to 261 - 262 movt type only.
No any other movt type allowed for this material type while issuing material.
All suggestions welcomed.
Regards,
RakeshThanx amit.
But same user uses all other movt types for other material type also. -
Missing authorization for plant ' '
User is missing authorization for plant ' '
User trace gives the following missing authorization
Object:
M_IS_WERKS RC=4 MCINF=S039;WERKS=' '
Can anybody help me out to find the meaning of space( ' ' ) in plant or any field?
thank you in advace* Prüfung, ob Berechtigung für die Werke existiert
SELECT * FROM T001W INTO TABLE AW_HLP_T001W
WHERE WERKS IN AW_WERKS.
DESCRIBE TABLE AW_WERKS LINES SY-TFILL.
IF SY-TFILL > 0.
FLG_SELECT = 'X'.
ENDIF.
<b> clear aw_hlp_t001w-werks. " note 124769, ver.04
collect aw_hlp_t001w. " note 124769, ver.04</b>
LOOP AT AW_HLP_T001W.
AUTHORITY-CHECK OBJECT 'M_IS_WERKS'
ID 'MCINF' FIELD AW_MCINF
ID 'WERKS' FIELD AW_HLP_T001W-WERKS.
There must be a reason to add an empty line, which causes the silly authority check. As far as I understand Note 124769 you have got to add plant ' '. See Note 408003: ."Create an authorization for the authorization object M_IS_WERKS which contains the value WERK = . Refer to Note 124769." -
Doing GR for a material type, system should give a message like QI required
Dear Friends
While doing MIGO(GR) for a material type, system should give a message like Quality Inspection required
but Client requirement is not to maintain QM view or Inspection Type 01for material type
Any setting required
Thanks & Regards
GajendranathHi
Please check user exit QBCK0003 |Extended QM check for goods receipt
Regards
sujit -
Unable to create PR via SO for DIEN material type
Hi Gurus
Need yr expertise.. I have a request from user to create PR from Sales Order for DIEN material type..Is it possible to create PR from SO for DIEN material type?
When I try to create I hit an error "No comsumption account".. This is because DIEN material type do not have valuation class..
Pls advise on the possiblities to create PR from SO (3rd party process) for DIEN...
SanjayHi,
Not sure... but when you create the material master with DIEN as the material type the item category group will be deafulted to LEIS, change this to BANS or maintain TAS in the order and try. Please post the result.
Prase -
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 -
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
azHi,
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. -
How to add a default user group for multiple document type's?
Hi,
I am trying to add same default user group for different document types when MA is created. Is there any way to setup using a single "Document Security Template"? Or I need to create different templates for different document types?
Please confirm.
Thanks,
SaloniHi Saloni,
Based on what your specific requirement, it might be easier to do it with scripting.
If you are doing it using Document Security Templates, you would have to create a Document Security Template for each of the 6 MA types and assign the default group. Create another one and leave the Document Type field blank, so it will apply to the other 4 MA types that don't have a default group.
Regards,
Vikram -
Screen no. for HERS Material type
Hi Friends,
I am trying to write a mass uploading program for HERS material type.
When I go to Purchasing view of HERS material type "Manufacturing details" subscreen is showing below (like Internal Material no. & Mfr Part no). i.e. it is showing the sequence as General data - Purchasing values - Manufacturing detailssub screens. Actually I want the sequence as Manufacturing details- Genaral data - Purchasing values.
When I check in OM3TE 12 is assigned to HERS material type. When I checked in OM3TB for screen sequence of 12 --- in Purchasing view I could see screen no. as 3002. The sub screen sequence is also correct.
But when I go to trnasaction MM02 --purchasing view the screen no. is 4000. (it is the screen no. to come for standard 12 screen sequence.
Am doing corectly ?
I want to get screen as 3002 in Purchasing view of HERS material type and sequence should be Manufacturing details- Genaral data - Purchasing values.
Regards,
Sai KrishnaHi Sai Krishna ,
Goto OMT3B and change the Screen no of Subscreen ( Last Column ) to :
2312 -- 3rd Row
2311 -- 4th Row
2302 -- 5th Row
At first note all the numbers in last column and then change it.
Leave the others without any changes.
Regards
Ramesh Ch -
"Mfr part profile" setup for various material types
Hello All,
I'd like to set a default value of "Mfr part profile" field ("Purchasing" screen in 01 Std industry sequence) different for various material types. Currently I have 2 entries maintained in MaterialsManagement>Purchasing>MaterialMaster>DefineManufacturerPartProfile (one with AMPL management and one without). I'd like to get the first entry set as default for HAWA material type and the 2nd for ROH.
Thanks in advance for your help on this!
JacekHi Troinski,
Its not possible in SAP, you can create Z transaction for create material wth dafult values.
Thanks
Bala -
Valuation category for DIEN material type
Dear all,
I have a requirement in which I need to maintain two price for DIEN material type ,I have created two valuation type and asssigned to a valuation category and If Itry to assign valuation category in Material master it is Grayed out ,even if I try in field selection also it is not working ,can't we have two valaution prices for service material? is that SAP standard?
Regards
kanthacan any body help me
Kantha
Maybe you are looking for
-
Bapi For Service Po change not Getting Changed
hi, I need to change the qunatities in the Services tab of the PO to close it. So , I tried using BAPI_PO_CHANGE. I passed the po number and the structures poservices and poserviceaccess .But it is not getting affected. In the Bapi Documentation i re
-
Mac OS 10.4.11 Update
I'm wondering if there are any statistics regaurding the approval rating of the Mac OS X 10.4.11. I'd like to update, but I"ve read so many bad reviews, ranging from small operational anomalies to basic annihilation of the system. Would it be a good
-
Develop Edits made with LR 4.3 won't show up in ACDSee Pro 5
I use lightroom 4.3 to edit my CR2 files and ACDSee Pro 5 to catalog and sort my huge photo collection and I would love to use it for the CR2 images too. The problem is, that the develop edits that I make to the CR2 files using LR , won't dispay in A
-
New to Crystal - Crosstab?
Hello everyone...I am fairly new to Crystal and need some help. I need to pull info from a table as follows: Basically each employee has several records in this table. But I only need to see employees with the pay code 356 AND any of another set of
-
I receive an invalid user name message in Creative Suite 2
Jeff, I own CS2 and have had it on my Windows 7 computer until the computer crashed last week. I bought a new computer and it has Windows 8. I went to install my CS2 cds and it doesn't work. I read this thread and installed the software via the in