Controlling material master access through field groups

Hello SAP Gurus,
We want to control the material master access (MM01/02) using field groups. I am unable to find any authorization object provided by SAP which can control access at field group level.
My scenarios is that certain group of people should be able to only display the fields in MM02 tcode and certain group of people should be able to change it. Please suggest if there is any config which will enable me to do this.
Thanks and Regards
Amit Gupta

Dear usen the following authorization object to contol the field entry on view level,
I donot think at field group level it is there
M_MATE_STA
status are nothiong but views
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

Similar Messages

In material master MRP3 screen "checking group" field is missing,

Dear All,
I am facing above problem.
can anybody help me to recall this field.
Kishor

Kishor
The reason for this is that the field Checking group may be hidden in the customisation.you have to chage it to Optional or mandatory
This is done in Field group setting
SPRO>Logistics general>Material Master>Field selection
I am not recalling the exact path.You find with the above path

In material master standerd price field not updating in group currency

In material master accounting 1 tab, under price and values table. standerd price is not updating in group currency.
Can you sugest me how to resolve this issue

Hi,
As per My Knowledge,Wht ever currency is assigned as company code currency , tht will only be updated in Material Master as Per standard.
Thanks
Goutam

Material Master Update through BAPI - Follow up material not updated

Hi Experts,
I am updating the material master through a custom transaction using the BAPI 'BAPI_MATERIAL_SAVEDATA'. Rest of the fields are updating correctly except for discontinuation ind., effective out date & follow-up material.
When I try to update it through MM02 it is working fine. However, when I pass the same data through BAPI it is throwing an error message that 'the material XXXXXX does not exist or is not activated'.
Please advice.
Thanks & Regards,
Ashu Arora

Some more fields need to be updated along with the discont. indicator. Now working fine.

In material master not all fields show the description of their value

Gurus -
Certain fields in the material master show their description text along.
Example -
Base Unit of Measure - EA      each
The description Text 'Each' which represent 'EA' comes from text Table T006A-MSEHT
Not all fields in material master show the description of what they represent. (only appear on F4 popup)
I want this description to come up for MARA-MAGRV field.
I want the configured value description for this field to appear on the screen.
I have 3 values put in this MARA-MAGRV
Z001 - description text 1
Z002 - description text 2
Z003 - description text 3
in MM01/MM02/MM03 only Z001 is see, not it description.
Here is what i tried
Added TVEGRT-BEZEI (desc field) in Transaction OMSR and assigned selection group 103 which holds MARA-MAGRV field too
any config missing?? what say?
Advises appreciated!
Thanks

You have to find out the conversion routine for domain MAGRV and enter in the convers. routine field.
if did not find one than you have create custom (take ABAPer help)
go to SE11 adn enter the domain MAGRV and hit display
on the definition tab you will see the conversion routine
here you need to populate the appo. conversion routine to see the text on the materia screen.
Conversion takes place when converting the contents of a screen field
from display format to SAP-internal format and vice versa and when
outputting with the ABAP statement WRITE, depending on the data type of
the field.
If standard conversion is not suitable, it can be overridden by
specifying a conversion routine in the underlying domain.
A conversion routine is identified by its five-place name and is stored
as a group of two function modules. The function modules have a fixed
naming convention. The following function modules are assigned to
conversion routine xxxxx:
o CONVERSION_EXIT_xxxxx_INPUT
o CONVERSION_EXIT_xxxxx_OUTPUT
The INPUT module performs the conversion from display format to internal
format. The OUTPUT module performs the conversion from internal format to
display format.
If a screen field refers to a domain with a conversion routine, this
conversion routine is executed automatically each time an entry is made
in this screen field or when values are displayed with this screen field.

Material master upload through flat file using the BAPI_MATERIAL_SAVEDATA

Hi Guys,
I need to upload the material master using the BAPI, I need to update the all the views in the material master, Could any one can help please?
I using EXCEL file is input file and suggest me the, excel file format, if could you suggest it would be very help to me.
Thanks,
Gourisankar.

please go through this code
*& Report ZBAPI_MATERIAL_SAVEDATA
*& AUTHOR
*& PURPOSE : THIS REPORT USES BAPI MATERIAL SAVE DATA TO UPDATE AND CREATE
*&           THE MATERIAL
REPORT ZBAPI_MATERIAL_SAVEDATA NO STANDARD PAGE HEADING MESSAGE-ID (ZHNC).
TYPES:BEGIN OF TY_MAT,
       MATERIAL(4),
       IND_SECTOR(1),
       MATL_TYPE(4),
      BASIC_VIEW(1),
      SALES_VIEW(1),
      PURCHASE_VIEW(1),
      STORAGE_VIEW(1),
       MATL_GROUP(9),
       BASE_UOM(3),
       BASE_UOM_ISO(3),
      MATL_GROUP1(1),
      BASE_UOM1(1),
      BASE_UOM_ISO1(1),
       PLANT(4),
       DEL_FLAG(1),
       PUR_GROUP(3),
       BASE_QTY(13),
      PLANT2(4),
      DEL_FLAG5(1),
      PUR_GROUP1(1),
      BASE_QTY1(1),
      PLANT3(4),
       STGE_LOC(4),
       MRP_IND(1),
      PLANT4(4),
      STGE_LOC1(4),
      MRP_IND1(1),
       SALES_ORG(4),
       DISTR_CHAN(2),
       DEL_FLAG1(1),
       MIN_ORDER(13),
      SALES_ORG1(4),
      DISTR_CHAN1(2),
      DEL_FLAG2(1),
      MIN_ORDER1(1),
       LANGU(2),
      MATL_DESC(40),
   END OF TY_MAT.
DATA: IT_DATA TYPE TABLE OF TY_MAT,
      WA_DATA LIKE LINE OF IT_DATA.
*decalraing flag
data: v_flag value ''.
*DECLARING WORK AREAs TO BE PASSED TO THE FUNCTION MODULE.
DATA: BAPI_HEAD LIKE BAPIMATHEAD,
      BAPI_CLIENTDATA LIKE BAPI_MARA,
      BAPI_CLIENTDATAX LIKE BAPI_MARAX,
      BAPI_PLANTDATA LIKE BAPI_MARC,
      BAPI_PLANTDATAX LIKE BAPI_MARCX,
      BAPI_STORAGELOCATIONDATA LIKE BAPI_MARD,
      BAPI_STORAGELOCATIONDATAX LIKE BAPI_MARDX,
      BAPI_SALESDATA LIKE BAPI_MVKE,
      BAPI_SALESDATAX LIKE BAPI_MVKEX,
      BAPI_MAKT LIKE BAPI_MAKT,
      BAPI_RETURN LIKE BAPIRET2.
*INTERNAL TABLE TO HOLD THE MATERIAL DESCRIPTION
DATA: BEGIN OF IT_MAKT OCCURS 0.
INCLUDE STRUCTURE BAPI_MAKT.
DATA END OF IT_MAKT.
DATA:BEGIN OF IT_RET OCCURS 0.
INCLUDE STRUCTURE BAPIRET2.
DATA END OF IT_RET.
*INTERNAL TABLE TO HOLD HEADER DATA
DATA: IT_EXCEL TYPE ALSMEX_TABLINE OCCURS 0 WITH HEADER LINE.
*SELECTION-SCREEN ELEMENTS
SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001.
PARAMETER: FNAME TYPE RLGRAP-FILENAME OBLIGATORY DEFAULT 'C:\Documents and Settings\Administrator\Desktop\MATMAS.XLS' .
PARAMETERS: P_BEGCOL TYPE I DEFAULT 1 NO-DISPLAY,
            P_BEGROW TYPE I DEFAULT 1 NO-DISPLAY,
            P_ENDCOL TYPE I DEFAULT 100 NO-DISPLAY,
            P_ENDROW TYPE I DEFAULT 32000 NO-DISPLAY.
SELECTION-SCREEN END OF BLOCK B1.
*DECLARATION OF EXCELAL TABLE
AT SELECTION-SCREEN ON VALUE-REQUEST FOR FNAME.
PERFORM F_GET_FILE USING FNAME.
START-OF-SELECTION.
PERFORM F_XLS_ITAB USING FNAME
                   CHANGING IT_EXCEL.
PERFORM F_MOVE_DATA.
perform F_GET_DATA.
*&      Form F_GET_FILE
      text
     -->P_FNAME text
     <--P_SY_SUBRC text
FORM F_GET_FILE USING    P_FNAME LIKE FNAME.
CALL FUNCTION 'KD_GET_FILENAME_ON_F4'
EXPORTING
   PROGRAM_NAME        = SYST-REPID
   DYNPRO_NUMBER       = SYST-DYNNR
FIELD_NAME          = ' '
STATIC              = ' '
MASK                = ' '
CHANGING
    FILE_NAME           = P_FNAME
EXCEPTIONS
MASK_TOO_LONG       = 1
OTHERS              = 2
IF SY-SUBRC <> 0.
MESSAGE E006(ZHNC).
ENDIF.
ENDFORM.                    " F_GET_FILE
*&      Form F_XLS_ITAB
      text
     -->P_FNAME text
     <--P_IT_EXCEL text
FORM F_XLS_ITAB USING    P_FNAME
                 CHANGING P_IT_EXCEL.
CALL FUNCTION 'ALSM_EXCEL_TO_INTERNAL_TABLE'
EXPORTING
    FILENAME                      = FNAME
    I_BEGIN_COL                   = P_BEGCOL
    I_BEGIN_ROW                   = P_BEGROW
    I_END_COL                     = P_ENDCOL
    I_END_ROW                     = P_ENDROW
TABLES
    INTERN                        = IT_EXCEL
EXCEPTIONS
   INCONSISTENT_PARAMETERS       = 1
   UPLOAD_OLE                    = 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_XLS_ITAB
*&      Form F_MOVE_DATA
      text
--> p1        text
<-- p2        text
FORM F_MOVE_DATA .
DATA : LV_INDEX TYPE I.
FIELD-SYMBOLS <FS>.
*--- Sorting the internal table
SORT IT_EXCEL BY ROW COL.
CLEAR IT_EXCEL.
LOOP AT IT_EXCEL.
MOVE IT_EXCEL-COL TO LV_INDEX.
*--- Assigning the each record to an internal table row
ASSIGN COMPONENT LV_INDEX OF STRUCTURE WA_DATA TO <FS>.
*--- Asigning the field value to a field symbol
MOVE IT_EXCEL-VALUE TO <FS>.
AT END OF ROW.
APPEND WA_DATA TO IT_DATA.
CLEAR WA_DATA.
ENDAT.
ENDLOOP.
ENDFORM.                    " F_MOVE_DATA
*&      Form F_GET_DATA
      text
--> p1        text
<-- p2        text
FORM F_GET_DATA .
LOOP AT IT_DATA INTO WA_DATA.
MOVE-CORRESPONDING WA_DATA TO BAPI_HEAD.
BAPI_HEAD-BASIC_VIEW ='X'.
BAPI_HEAD-SALES_VIEW ='X'.
BAPI_HEAD-PURCHASE_VIEW ='X'.
BAPI_HEAD-STORAGE_VIEW ='X'.
MOVE-CORRESPONDING WA_DATA TO BAPI_CLIENTDATA.
BAPI_CLIENTDATAX-MATL_GROUP = 'X'.
BAPI_CLIENTDATAX-BASE_UOM = 'X'.
BAPI_CLIENTDATAX-BASE_UOM_ISO = 'X'.
MOVE-CORRESPONDING WA_DATA TO BAPI_PLANTDATA.
BAPI_PLANTDATAX-PLANT = BAPI_PLANTDATA-PLANT.
BAPI_PLANTDATAX-DEL_FLAG = 'X'.
BAPI_PLANTDATAX-PUR_GROUP = 'X'.
BAPI_PLANTDATAX-BASE_QTY = 'X'.
MOVE-CORRESPONDING WA_DATA TO BAPI_STORAGELOCATIONDATA.
BAPI_STORAGELOCATIONDATA-PLANT = BAPI_PLANTDATA-PLANT.
BAPI_STORAGELOCATIONDATAX-PLANT = BAPI_STORAGELOCATIONDATA-PLANT.
BAPI_STORAGELOCATIONDATAX-STGE_LOC = BAPI_STORAGELOCATIONDATA-STGE_LOC.
BAPI_STORAGELOCATIONDATAX-MRP_IND = 'X'.
MOVE-CORRESPONDING WA_DATA TO BAPI_SALESDATA.
BAPI_SALESDATAX-SALES_ORG = BAPI_SALESDATA-SALES_ORG.
BAPI_SALESDATAX-DISTR_CHAN = BAPI_SALESDATA-DISTR_CHAN.
BAPI_SALESDATAX-DEL_FLAG = BAPI_SALESDATA-DEL_FLAG.
BAPI_SALESDATAX-MIN_ORDER = 'X'.
REFRESH IT_MAKT.
IT_MAKT-LANGU = WA_DATA-LANGU.
IT_MAKT-MATL_DESC = WA_DATA-MATL_DESC.
APPEND IT_MAKT.
CLEAR IT_RET.
REFRESH IT_RET.
PERFORM F_CALL_BAPI.
READ TABLE IT_RET WITH KEY TYPE = 'S'.
IF SY-SUBRC EQ 0.
PERFORM F_BAPI_COMMIT.
WRITE:/ 'MATERIAL CREATED OR UPDATED SUCESSFULLY WITH MATERIAL NO',WA_DATA-MATERIAL.
ELSE.
MESSAGE E000(ZHNC) WITH 'ERROR IN CREATING THE MATERIAL'.
*WRITE: / 'ERROR IN CREATIN MATERIAL',IT_RET-MESSAGE.
*PERFORM F_DOWNLOAD.
ENDIF.
*ENDIF.
ENDLOOP.
ENDFORM.                    " F_GET_DATA
*&      Form F_CALL_BAPI
      text
--> p1        text
<-- p2        text
FORM F_CALL_BAPI .
CALL FUNCTION 'BAPI_MATERIAL_SAVEDATA'
EXPORTING
    HEADDATA                   = BAPI_HEAD
   CLIENTDATA                 = BAPI_CLIENTDATA
   CLIENTDATAX                = BAPI_CLIENTDATAX
   PLANTDATA                  = BAPI_PLANTDATA
   PLANTDATAX                 = BAPI_PLANTDATAX
   STORAGELOCATIONDATA        = BAPI_STORAGELOCATIONDATA
   STORAGELOCATIONDATAX       = BAPI_STORAGELOCATIONDATAX
   SALESDATA                  = BAPI_SALESDATA
   SALESDATAX                 = BAPI_SALESDATAX
IMPORTING
   RETURN                     = IT_RET
TABLES
   MATERIALDESCRIPTION        = IT_MAKT
UNITSOFMEASURE             =
UNITSOFMEASUREX            =
INTERNATIONALARTNOS        =
MATERIALLONGTEXT           =
TAXCLASSIFICATIONS         =
RETURNMESSAGES             =
PRTDATA                    =
PRTDATAX                   =
EXTENSIONIN                =
EXTENSIONINX               =
APPEND IT_RET.
ENDFORM.                    " F_CALL_BAPI
*&      Form F_BAPI_COMMIT
      text
--> p1        text
<-- p2        text
FORM F_BAPI_COMMIT .
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
WAIT         =
IMPORTING
RETURN        =
ENDFORM.                    " F_BAPI_COMMIT

Control Material Master Views with IDOC load

Hello all,
I am wondering how best to control which views are available during IDoc processing for Material Master.
For example I just want the Basic Data 1 and Basic Data 2 tabs, I am only populating the relevant data and placing a value of u201CKu201D in the Maintenance Status fields. This seems to work and avoids the warnings I seem to encounter when I neglect to add values for the Maintenance Status fields.
The warning I get at times tell me the IDoc is attempting to extend all available views, then it makes them available once I view my Material with MM03, however because there is no data in them I canu2019t go into the tabs. That is fine because I can go to the Basic data tabs, but I was disappointed to see the other tabs enabled, but inaccessible.
With Direct Input I used to be able to simply indicate which views I want. Now it seems I must request the maintenance views that then translate to actual views.
Please help.
Thanks

Yes I have experience in that area, and I fill the PSTAT as well. But you can also run a program (is in IMG > Logistic Gerneral > material master) to regenerate PSTAT after you have loaded all materials.
I use IDOC loading method for SAP system mergers. Sent Material master in legacy system using ALE as IDOC collection to a file, then use this file as source for LSMW, and as IDOC to IDOC mapping is just 1:1 I use use this methd in this case.
When loading from Excel file, I started using BAPI import method a few rollout waves back (but not because there is something difficult with IDOC, just to get used to this method).

Mass maintainenance of material master for the field MARC-NCOST,SOBSK

Hi
While maintaining two fields NCOST and SOBSK for hude materials using MM17 transaction, the transaction executed properly while saving the transaction. There is no warning and error messages for all materials. But it was not updated in material master or in tables. for other field relavent to MRP updated correctly.
when I am maintaining manually for each material it is taking the value update the same.
Please explain the problem why it was not updating and let me know the solution.
Regards
Kishore

Hi,
Thanks for ur response.
I am getting green light. Please note the application message given below.
"The material cannot be maintained since no maintainable data transferred
Message no. MG160
Diagnosis
You wanted to maintain an existing material master record as follows:
By changing it
However, you have not yet maintained the material master record for the organizational levels and data fields specified, or user departments selected. You can therefore process this data only in Create mode.
By extending it
However, you have already fully created the material master record for the organizational levels and data fields specified, or user departments selected. You can therefore process this data only in Change mode.
In both cases, this message can appear if there is no maintainable user department left. This occurs if you have not set the Check required fields indicator when transferring data (program RMDATIND). Although the absence of an entry in required fields does not then necessarily result in an error, the number of maintainable user departments is reduced accordingly.
Procedure
Depending on the cause, maintain the material master record in Create or Change mode, or also transfer the missing required fields."
where can I find IDoc list for this transaction.
Regards
Kishore

Material master update through BAPI

Hello Experts,
We are using BAPI_MATERIAL_SAVEREPLICA to update material master . It is required to update RefPlant:consumption (MARC-VRBWK) in forecast view . We could not find any field corresponding to MARC-VRBWK in table parameters PLANTDATA .
Please help me if there is any way to update RefPlant:consumption (MARC-VRBWK ) in forecast view by using BAPI_MATERIAL_SAVEREPLICA .
If there is any other BAPI to update the field please let me know .
Regards,
Kiran.

Hi Suhas,
I tried EXTENSIONIN & EXTENSIONINX approach but the MARC-VRBWK was not reflected. I did some research and came to know that these extensions can be used to update the custom fields . If there is any way to update the standard field like MARC-VRBWK using extension please let me know . It would be great help .
Thanks,
Kiran.

In Material master safety stock field is in display

Hi,
As a consultant i am able to change the Safety stock field in MRP view in the test system and Production also,but for the user this particular field is in display mode wheras other field in the MRP view user is able to change.
Kindly help me if,there is any settings for the same.
Regards,
Prashant

Hi Prashant,
Have you checked if there is any configuration made to lock same fields on material master? Follow the below path please;
Logistics u2013 General ==> Material Master ==> Field Selection ==> Define Lock-Relevant Fields
May be someone defined some fields as u201Clock-relevantu201D in customizing and during creation or changing of material master he/she set this indicator. You are able to change those fields because you may have SAP_ALL authorization whereas others may not.
Best regards

Material Master Price Unit field MBEW-PEINH

Hello,
In my experience I've always dealt with the Price Unit being equal to 1000 (1.00 for 1 ; 1000.00 for 1000). It is my understanding that this was decided upon due to the decimal point limitation. In my new project, everything is set to 1. Is this an issue at all? If a few parts are less than .01, could just those be set to per 100 or 1000?

Hi,
the price unit can be set on plant level of material master.
nd it is highly suggested to set the price unit to a level where the valuation price is something like 494,99 / 1000 units instead of 4,95 / 10 units or 0,50 / 1 unit (I've already rounded the values as SAP would do).
best regards, Christian

Material master distribution through BD10 is not working

hi i am learning and created all the customizing setting to send material master data from sending system to the receiving system but the sending system shows idoc has been sent to port Ok with status 03 but i dont see the material being created in the receiving system. Where am i going wrong? Do i need to trigger BD11 in the receiving system?

Hi Suresh...
              After reaching port with status 03..
              we have to run the program RBDMOIND for status conversion..
              Once we run this program all the IDoc's which are at port are
              sent to their receiving partner...and status becomes 12...

Material Master Table (Blank Fields)

Gurus,
I need help in finding out which fields in Mara are not commonly used. I need 3 to 5 fields with Character data types.
Will be utilizing this uncommonly used fields for other fieldnames (e.g. ISH_AGENT1, ISH_AGENT2, etc) that are not implemented.
Thanks in advance

My guess...depends from organization to organization
hw they use the table....
regards,
chaithanya k

Adding field in material master

Hi All,
I am trying to add field manufacture part number in material master. In field selection Manufacture part number (mara-mfrpn) field is optional. I checked the field selection group at material type level, transaction code field selection group (MM01.MM02,MM03) and Industry sector specific field selection, every where the fieild is optional but it is not coming up in material master. Please let me know if i m missing some config.
Regards
Chetan

Hi Chetan,
Use material type HERS.
Also find the following link useful.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/106f94ee-8dc2-2a10-a485-882871fa5c11?QuickLink=index&overridelayout=true
Also from link http://help.sap.com/saphelp_470/helpdata/en/75/ee15c655c811d189900000e8322d00/content.htm
some part is copied
Create material master records
If you work with MPNs, the number of manufacturers of a manufactured part corresponding to one of your firmu2019s own materials determines the number of material master records you have to create:
If there is just one MPN corresponding to one of your firmu2019s own materials, you can enter it and the manufacturer directly in the master record for your own material. In this case, you need not create an MPN Material.
If there are several MPN materials corresponding to one of your firmu2019s own materials, you must create MPN material master records with the material type HERS. In the Purchasing view, enter the manufacturer part number, the manufacturer (this can be either a vendor master record or a manufacturer master record), and your firmu2019s own, inventory-managed material.
The MPN material master records are assigned to your firmu2019s own material. Stocks are managed with respect to the firmu2019s own material.
0.8 cm steel bolts with a diameter of 0.5 cm are identified and stocked in your enterprise as the firmu2019s own, inventory-managed material RAW_S_08.
The manufacturer Meyer & Co. sells these bolts under the number 8001 (the manufacturer part number). This information is stored in the MPN material master record S_MEYER.
The manufacturer Smith Corp. supplies similar bolts under the number 4711. This information is stored in the MPN material master record S_SMITH.
The MPN material master records S_MEYER and S_ SMITH are assigned to the material master record RAW_S_08.
Hope it helps
sBk

Account assignment group is different in Intercompany Billing from Material Master

Hello,
Account assignment group is different in Intercompany Billing from Material Master.
Account assignment group in Billing and Intercompany Billing is feched from Material Master.
In Material Master, account assignment group is assigned as 12.
In Billing, account assignment group is 12 but in Intercompany Billing, account assignment group is 13.
Please help me to understand why in Intercompany Billing, account assignment group is 13.
Best Regards,
Debashri Dutta

Check the table MVKE for the values maintained for field KTGRM. You can see the sales org-DC combinations for which the AAG is maintained as 13 for this material. This may give you clues for investigation.

Controlling material master access through field groups

Similar Messages

Maybe you are looking for