on ‎2011 Dec 06 2:26 PM
Hi,
How is a user assigned as MRP controller and, what are the specific customization / master data settings done?
I know that MRP controller is defined in customization for each plant and is assigned in the material master.
I want to know how a person who is assigned as MRP controller can log into the system and know what all material he has to plan and check the procurement proposals for those materials.
please give specific answers. thanks.
Sushant
Request clarification before answering.
Hi Sushant,
The MRP-Controller references are used in SAP to indicate responsibility/ownership for a group of materials, specifically in relation with the follow-up on the outcome of material-requirement-planning calculation (MRP-run).
In T-code SPRO the MRP-controller-codes are created in table V_T024D
The MRP-Ctrl-records will typically contain information on Plant/MRP-Ctrl code/MRP Controller name (full name)/ Recipient-name (this field can be filled with the SAP user-name) /Tel.number/Purchasing-group/Business-area/Profit centre.
In the MRP-1 view of the material masterdata records a relationship is created between the material-record and the MRP-controller (=responsible) for a particular material. On a regular basis a material-requirement-planning-calculation (MRP-run) will be made to balance supply and demand for the materials for an organization. The result of the MRP-run will be visible in SAP as planned purchase-requisitions, planned production-orders and action-messages in T-code MD06.
Through their relation with a material-record, these planned purchase requistions, planned production-orders and the exception-report-messages will also be tagged with the MRP-controller code.
The exception-report shows traffic lights and "exception group-codes" per mrp-group/plant/material/mrp-controller/vendor to indicate which action need to be taken (other selection-restrictions are also available in MD06). A drill-down on the materialnumber will bring the information of MD04 and will give access to stock-information / purchase-requisitions / open purchase-orders / planned orders / production-orders. T-code MD06 provides an action-list for the MRP-controllers / procurement-officers / production-planners. The MRP-Controller will decide to release the planned requisitions (for purchase-items)/ release planned production orders (for production-items) and will take action upon the information in T-code MD06 to expedite, postpone, change or cancel material-requirements. SAP allows an individual release of planned purchase-requisitions with T-code MD14; T-codes ME54N and ME55 support collective releases of the purchase-requisitions.
The release of individual planned production-orders can be done in T-code CO02 (or as a drill-down from report CO26 to CO02 )
A collective planned production-order release can be made with T-codes COHV and COOIS
Hopefully it is clear now that the MRP-controller-code is in no way the equivalent of the SAP-user-account and cannot be used to log-into the system or to log material-movements,
It is used as an additional identifier to make usefull selections in MRP-related transaction-screens and to indicate responsibility/ ownership
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That is with User Profile.The user will be assigned with relevant authorization for MRP controller with authorization object "M_MTDI_ORG".Check in PFCG with user profile.Its better take help of your Basis person.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
can u look to Authorization object "M_MTDI_ORG" for field DISPO
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
MRP Controller is not always mapped to user on one-to-one basis. There are lot of cases where one user is assigned many MRP controllers and many users can have one MRP controllers. Normally the MRP planning is set in background for the entire plant, using customer enhancements it can be set per MRP controllers. But most the planning data can be viewed per MRP controller using MD07. There other report transactions where MRP controller is one of the field, so they can be used for their designated purpose.
| User | Count |
|---|---|
| 59 | |
| 30 | |
| 21 | |
| 11 | |
| 4 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.