Restricting PM user by material type

Hi everyone,
I want to restrict access to PM users and limit to only allow them maintenance to material type - assemblies (IBAU - Maintenance Assembly). We are using a customized material type (ZBAU - same name used for Auth group) which references the standard IBAU material type.
I have created an authorisation group for this and it is maintained in T134. Authorisations in both objects M_MATE_WGR & M_MATE_MAR are restricted to ZBAU (which is my Auth group) in the authorisation group field (BEGRU), and the other objects which bring in the Auth group field are also restricted to ZBAU. However when I test this my test user can still maintain other material besides ZBAU.
Please advise.
Thanks a lot.

Hi,
There could be two reasons for that
1) if the access is coming from some other role in the user master.
2) The Authorization group field doent retrict access to material which are not attached to any specific authorization grp.
as per you note u attached ZBAU to grp ZBAU but make sure the other material tpye which you want the users to not have access to be added to a differenet authorization group. if they are not a part of any auth group they will be able to acess all those material types..
Hope this helps
Manohar

Similar Messages

Shall i restrict CS01, CS02 by Material type wise

Dear all Gurus,
Please help me out to restrict the CS01 & CS02 by material type wise.
Thanks in Advance
pabale

Dear Mr. Devendra,
Please let me know the configuration in details becoz i want to restrict the user for not to change the HALB TYPE BOM in CS02 but in case of FERT type he can change.
e.g.
BOM Creation user has to rights to create / change the BOM of material type FERT.
BOM Creation user has to rights to create / but no change authority the BOM of material type HALB.Change rights we have to assign to authority.
Hope from you positive feed back and thanks for immediate respond to both.
Regards,
Pabale

Restrict the user   based on document type on migo transaction-prepare GRN

Hi,
We are running ECC6.0 R/3 system.We had a requirement as follows
In MIGO transaction , we want to restrict the user on document type i.e. we want that a particular user can prepare GRN for document type STO only. He cannot prepare GRN for other document type.
We checked SU24->maintain check indicators for transaction codes->enter migo->execute->check indicator.This returned us the authorisation objects present in Migo transaction.We checked the help of all these objects,but none of them we found suitable for above mentioned requirement.We were planning to find out the proper authorisation object to add to Profile generater.
The following is the objects which we have checked for.
A_B_ANLKL-->     Asset Postings: Company Code/Asset Class
A_B_BWART-->     Asset Postings: Asset Class/Transaction Type
B_USERSTAT-->     Status Management: Set/Delete User Status
B_USERST_T-->     Status Management: Set/Delete User Status using Process
C_AFKO_AWK-->     CIM: Plant for order type of order
C_CACL_DSG-->     Interface Design
C_DRAW_BGR-->     Authorization for authorization groups
C_DRAW_DOK-->     Authorization for document access
C_DRAW_TCD-->     Authorization for document activities
C_DRAW_TCS-->     Status-Dependent Authorizations for Documents
C_KLAH_BKP-->     Authorization for Class Maintenance
C_STUE_BER-->     CS BOM Authorizations
C_STUE_WRK-->     CS BOM Plant (Plant Assignments)
C_TCLA_BKA-->     Authorization for Class Types
C_TCLS_BER-->     Authorization for Org. Areas in Classification System
C_TCLS_MNT-->     Authorization for Characteristics of Org. Area
F_BKPF_BUK-->     Accounting Document: Authorization for Company Codes
F_BKPF_BUP-->     Accounting Document: Authorization for Posting Periods
F_BKPF_KOA-->     Accounting Document: Authorization for Account Types
F_FICA_FOG-->     Funds Management: authorization group of fund
F_FICA_FSG-->     Funds Management: authorization group for the funds center
F_FICB_FKR-->     Cash Budget Management/Funds Management FM Area
F_KNA1_APP-->     Customer: Application Authorization
F_LFA1_APP-->     Vendor: Application Authorization
F_SKA1_BUK-->     G/L Account: Authorization for Company Codes
G_GLTP -->       Spec. Purpose Ledger Database (Ledger, Record Type,
                               Version)
J_1IDEP_SL-->     Authorization object for depot sale transaction
J_1IEXC_OT-->     Authorization object for Other Excise Invoice Create
J_1IEX_PST-->     Autorization object for posting Other Excise invoice
J_1IGRPT1-->     Auth. for PART1 at GR
J_1IINEX -->            Incoming Excise Invoice
J_1IRG23D-->     Authorisation object for Depo Transactions
K_CCA-->                     CO-CCA: Gen. Authorization Object for Cost Center
                                Accounting
K_CSKS     -->                CO-CCA: Cost Center Master
K_CSKS_SET-->     CO-CCA: Cost Center Groups
K_PCA-->                    EC-PCA: Responsibility Area, Profit Center
L_TCODE-->                    Transaction Codes in the Warehouse Management System
M_ANFR_BSA-->     Document Type in RFQ
M_ANFR_EKG-->     Purchasing Group in RFQ
M_ANFR_EKO-->     Purchasing Organization in RFQ
M_ANFR_WRK-->     Plant in RFQ
M_BEST_BSA-->     Document Type in Purchase Order
M_BEST_EKG-->     Purchasing Group in Purchase Order
M_BEST_EKO-->     Purchasing Organization in Purchase Order
M_BEST_WRK-->     Plant in Purchase Order
M_MATE_CHG-->     Material Master: Batches/Trading Units
M_MATE_STA-->     Material Master: Maintenance Statuses
M_MATE_WRK-->     Material Master: Plants
M_MRES_BWA-->     Reservations: Movement Type
M_MRES_WWA-->     Reservations: Plant
M_MSEG_BMB     -->Material Documents: Movement Type
M_MSEG_BWA-->     Goods Movements: Movement Type
M_MSEG_BWE-->     Goods Receipt for Purchase Order: Movement Type
M_MSEG_BWF-->     Goods Receipt for Production Order: Movement Type
M_MSEG_LGO-->     Goods Movements: Storage Location
M_MSEG_WMB-->     Material Documents: Plant
M_MSEG_WWA-->     Goods Movements: Plant
M_MSEG_WWE-->     Goods Receipt for Purchase Order: Plant
M_MSEG_WWF-->     Goods Receipt for Production Order: Plant
M_RAHM_BSA-->     Document Type in Outline Agreement
M_RAHM_EKG-->     Purchasing Group in Outline Agreement
M_RAHM_EKO-->     Purchasing Organization in Outline Agreement
M_RAHM_WRK-->     Plant in Outline Agreement
Q_TCODE     QM -->         Transaction Authorization
S_ADMI_FCD-->     System Authorizations
S_ALV_LAYO-->     ALV Standard Layout
S_BDS_DS-->     BC-SRV-KPR-BDS: Authorizations for Document Set
S_BTCH_ADM-->     Background Processing: Background Administrator
S_BTCH_JOB-->     Background Processing: Operations on Background Jobs
S_CTS_ADMI-->     Administration Functions in Change and Transport System
S_DATASET-->     Authorization for file access
S_DEVELOP-->     ABAP Workbench
S_DOKU_AUT-->     SE61 Documentation Maintenance Authorization
S_GUI-->                     Authorization for GUI activities
S_OC_DOC-->     SAPoffice: Authorization for an Activity with Documents
S_OC_ROLE-->     SAPoffice: Office User Attribute
S_OC_SEND-->     Authorization Object for Sending
S_PACKSTRU-->     Internal SAP Use: Package Structure
S_PRO_AUTH-->     IMG: New authorizations for projects
S_RFC-->                     Authorization Check for RFC Access
S_SCD0     -->                Change documents
S_SPO_DEV-->     Spool: Device authorizations
S_TABU_DIS-->     Table Maintenance (via standard tools such as SM30)
S_TCODE     -->                Transaction Code Check at Transaction Start
S_TRANSLAT-->     Translation environment authorization object
S_TRANSPRT-->     Transport Organizer
S_WFAR_OBJ-->     ArchiveLink: Authorizations for access to documents
V_LIKP_VST-->Delivery: Authorization for Shipping Points
V_VBAK_AAT-->Sales Document: Authorization for Sales Document Types
V_VBAK_VKO-->Sales Document: Authorization for Sales Areas

Have you executed a trace while a functional user executes the transaction code for the specific parameters? (i.e. document type). The trace will then show which objects are being checked; then look at the object documentation in txn Su21 to determine if there are any ways to restrict on the particular value; in some cases, if the authorization group field is being checked, additional configuration is needed in order to implement the security (Su21 will explain in detail for the particular object).

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

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

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

ME21N restriction by material types

Hi
We would like to restrict ME21N access by material type. I believe this is possible by turning on the authorisation check in SU24 for ME21N transaction for authorisation object M_MATE_MAR and once the relevant material types are maintained through T-code OMS2
Would these two changes suffice or do we need to activate any BADI in ME21N transaction to enable this authorisation check. I am not sure if M_MATE_MAR check is part of standard authorisation checks in ME21N. Please advise
Thanks & Regards
Dinesh N

Hi,
you mentioned article type but object M_MATE_WRK controls access on site level. Anyway, if ME21N performs check for this object then it will be executed. Hence I would suggest to run authorization trace to see which checks are executed. If check for your object is not there then there is standard BADI for POs that can be used to add additional authorization checks. So it will require some coding but not much. It's quite straight forward.
Cheers

Restricting the material types in MM01

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

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

SLED restriction to certain material types

Hello,
is it possilbe to restrict SLED Check by material type? Means e.g. I only want a SLED check for ROH. not for VERP.
(I know it's possible to define it by plant and movement type.)
Thank you.
Best regards, Paul.

I just tested it in my system,
In OMJ5 the SLED check for plant 0001 is set active
the check for movement type 101 is set to 1
I used a material that has no shelf life data maintained in material master, but is batch managed
I am able to do MIGO without entering a production date nor a SLED manually.
The batch is created with no data in this fields.
I do not receive any message (as expected).
Can it be that you removed the shelf life data from material master, but did not remove it from existing purchase orders?

Is there a user exit to restrict BOM change and display using material type?

Hi Gurus,
There’s a need to limit access to BOMs on a per material type however the client does not want to use the functionality of "BOM Authorization Group" in BOM header details.
Do we have a user exit that can satisfy the said requirement?
Thanks,
Mae

Hi
Restriction to Changes of BOM will have better control using authorization object .Go to PFCG with your basis guy and try to explore the objects
You can use C_AENR_BGR object to restrict.
Otherwise , try apply BADI BOM_UPDATE
Regards
JH

Restriction of user to isuue material (mb1a - 261) based on order type and

Dear friends
My client wants to restrict the users for issuig of materials against order ( mb1a - 261 mvt) Based on user id, plant and Order type.
I know it can be done with user id and Plant. But he is insisting on Order type.
Please suggest.

Dear R S Dhar,
It's not possible to control for this authoriozation for order type for performing 261 movement in MB1A.
You can control for movement type or based on storage location.
Check and revert back.
Regards
Mangalraj.S

How to restrict the users not to change receiving batch no. in 305 mov.type

Dear MM Guru,
We are using mov.type 303 & 305 for transferring the materials from one plant to another plant. t.code is MB1B (Non split valued item)
While receive the goods through 305 mov.type the user having the chance to change the receiving batch number. To control this changes, is there a way where we can restrict the users not to do the changes in receiving batch no. or can we do the GR with reference to the material document 303 mov.type.
Regards,
Sivanandan

Hi,
Generally there is a possibility to change the batch no. If you want to restrict it means go for enhancement. Use BADI to acheive this.In MB_MIGO_BADI you can set not to change the batch no. Hope it works. Thanking you.

How to Restrict Material Type in MM01 ?

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

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

Restricting issue of goods to cost center with respect to material type

Dear Users,
I have a requirement like we want to restrict issue of goods to cost center with respect to material type i.e., we want to issue goods to cost center only through reservation and that too only for specific material types. Is there any standard solution for this, please provide your suggestions.
Thanks,
Manoj

Hi Ajay,
Thanks for valuable input.
I also thought in the same line , but user has the following concern on this:
Assessment Cycle: As per Users, it cannot be used because this will allocate based on allocation basis. But they need, the values that was posted at the time of transaction and as per materials. So it wont be accurate through Assessment cycle,
OKB9: They have different Cost center for different valuation area for the same GL Account.
Hence through OKB9 also, we cannot post directly to COPA.
That's the reason the above option were not adopted.
My other concern to this is:
In CKM3, we have two lines under consumption, one for Normal sales PGI and other is Cost Center.
After doing revaluation of consumption in CKMLCP, we see one line under Cost Center :Revaluation of Consumption Figure"
My question, where can I see that figure whether in any table or in Cost Center report??
If that is also available we can try to match those values and post to COPA.
Let me know your thought on this.
Thanks and regards
Kami

Restricting Purchase order for a particular material type

Hi All,
How do I restrict a purchase order document type to be created for a particular material type.
For eample PO document type NB should allow to create for materials with the material type ROH only and restrict the other material types by issuing an error.
Many thanks in advance.
Regard,
Ravi

Hi Ravi,
This is not directly achievable in std. You will have to implement the check in a user exit, e.g. the BAdI ME_PROCESS_PO_CUST method PROCESS_ITEM.
But why this strange reqmt? Maybe there's another solution whuch would keep you in std?
BR
Raf

Authorisation restriction to change batch ( MSC2N ) by material type

Hi ,
We have a requirement wherein we want to restrict users from changing batch records ( MSC2N ) by material type. Viz. A user xyz should not have authorization to change batch for material type FERT.
We cannot use the authorization group ( BEGRU ) field of material master alongwith object M_MATE_CHG as this field is already being used for another purpose to restrict users by country for MM01,MM02 & MM03.
Please do let know if you know of any alternative method of doing so.

Hi,
The new authorization object will work only if the corresponding changes are made in the related program.
Open the program code for the MSC2N transaction (via Se93), and search for the string "AUTHORITY-CHECK". You will find a piece of code that checks for the authorization object M_MATE_CHG and its related field values. This will need to be changed to Z_MATE_CHG and its corresponding values.
You will need an ABAP-er for this.
Only then will the authorization check work correctly. Once this is done add the object in the corresponding role (and also change SU24 entry for MSC2N accordingly if required).
Regards,
Sanju.

Restricting stock overview (MMBE) based on material or material type?

Hi,
Can we restrict any user from viewing material stock (MMBE) for particular materials or material group or material types.
Thanks
Nilesh

HI,
I cannot think of a way this is possible. You can only make these restrictions for standard LIS reporting info structures where the authorisation objects exist.
For example, auth object M_IS_MTART exists for material type covering LIS Standard Analysis: Info Structure / Material Type, similar for material group.
The only other place for material type restrictions in is the material master from object M_MATE_MAR.
However, check with your basis guys maybe they can think of something.
Thanks.

Restricting PM user by material type

Similar Messages

Maybe you are looking for