Can MRP be run MRP Controller wise ?

We have only one plant. I want to run MRP for BOM items as well as ROL items. MRP can be run plant wise thru tcode MD01. I want to run mrp for only ROL items.
Please suggest
Regards,
( Rajneesh Gulati )

Hi,
Please find the required User exit details
This enhancement controls MRP run at MRP controller level.
System selects Materials under MRP Controller specified in user parameters (Par. ID = DGR)
Enhancement : M61X0001 (User exits PP-MRP materials planning)
Function Module:          EXIT_SAPLM61C_001
               EXIT_SAPMM61X_001
The user exit must be activated and the corresponding logic must be implemented. Here, the coding for both function modules (EXIT_SAPMM61X_001, EXIT_SAPLM61C_001) must be identical, that is, the Includes ZXM61U01 and ZXM61U02 should be identical.
For further information see documentation (transaction SMOD, extension M61X0001).
&----&  Include           ZXM61U01&----
CLEAR: no_planning, stop_planning.
CASE user_key.
-* select materials for one MRP controller (specified in user_par)---- 
WHEN '001'.    uxpar = user_par.   
CONDENSE uxpar.   
WRITE uxpar+0(3) TO dispo.   
IF dispo IS INITIAL.     
EXIT.   
ENDIF.   
IF mt61d-dispo <> dispo.     
no_planning = 'X'.   
ENDIF.
ENDCASE.
Hope this helps
Regards
Dheeraj

Similar Messages

  • Generate Delivery Schedules via MRP Planning run

    The company wants to create Scheduling Agreements and generate the Delivery Schedules from the MRP Planning run - MRP 2 view via JIT.
    Can you generate Delivery Schedules from Schedule Agreements if the company does not have an EDI server or APO set up?
    Thanks,

    Shirley Globe,
    You seem to be putting the experts to the test.
    As it was told you, you can generate schedule lines via MRP run. MRP run can be done (e.g.) trough MD01 /MD02 / MD03. Of course, you have to use the proper selection parameters to achieve your goal.
    http://help.sap.com/erp2005_ehp_04/helpdata/EN/f4/7d2da044af11d182b40000e829fbfe/frameset.htm
    As for how to use SA with MRP please check SAP online help:
    http://help.sap.com/erp2005_ehp_04/helpdata/EN/3b/66596eda7b11d1b6330000e8a738dc/frameset.htm
    Regards,
    Csaba
    Edited by: Csaba Szommer on Apr 9, 2009 7:40 PM

  • Can we run MRP for perticular ITEMS or Can we run MRP on MRP Group wise

    Dear Friends,
    Out of all Material masters MRP should be run on some meterial.
    Is there any way to run MRP on perticular 1 MRP Group ?
    Is there any way to run MRP on selected MATERILS ?
    Waiting for ur help.
    Thanks...
    Yogesh.

    Hi Yogesh,
    It is possible with the enhancement -> M61X0001, take the help of your abaper & he / she would implement your logic.
    In customizing, SPRO - Production - MRP - Planning - User Exit: Mtl selection for planning run define a key & assign it in MD01 initial screen.
    If helpful award points
    Regards,
    Vivek

  • Run Sales order wise MRP - AFS material

    Dear Experts,
                       Here my client asking to run the MRP for sales order wise. recently we did the AFS implementation for one of our client. there is an common T-code for MRP run, for AFS material is /AFS/MD02 . they are using material based BOM ( Bill of material). so there might be common material for different sales order i.e if am using material XXXX for Sales order 500 mean , same material will present in  Sales order 510 too. current system
    ( T-code /AFS/MD02) will run MRP of material XXXX Both 500,510 sales order but my requirement is i need to restrict to single sales order.
    any one guide me to resolve my requirements.
    Thanks in advance...
    Regards,
       Thangam.P

    Dear Venkat,
    You are right MD50 does not support AFS material.
    Please Try running : /AFS/MD02.
    Also Check SAP Note: Note 981747 - FAQ - AFS Production Planning
    Hope it will help you.
    Regards,
    Alok Tiwari

  • When can i see when was the last MRP had run?

    Hi All,
    as per my understanding in MD03 we first run MRP & then we can see the list in MD04. so suppose now some MRP relevant parameters are changing then unless we run MD03 again , these changes wont reflect in MD04. is it correct?
    now i want to see when was last MD03 was run, then where can i see this?
    any help will be highly appreciated.
    Thanks
    Anubhab.

    Hi Anubhab,
    For MRP run there are several transactions usefull for bussiness requirement.( MD01, MD02, MD03,MD50 etc)
    so when ever there is any change in MRP relevant parameter, entry in planning file will happen and it will be executed in next MRP run,
    You can see the date and time of last MRP run in MD05.
    Hope it help you
    regards
    Ritesh

  • Material in two plants, I run MRP with the BOM is not found in prod plant

    Hi all,
    I have plant 1020 material 12345
    Plant 1020 is the production plant for material 12345
    The material 12345 exists in plant 1070.
    The material 12345 in plant 1070 has no MRP.
    Plant 1020 material 12345 config in MM03
    MRP1 --> MRP Type = PD
    MRP1 --> MRP Controller = G03
    MRP3 --> Planning material = PLAN_1020_GR03
    MRP3 --> Planning plant = 1020
    Plant 1070 material 12345 config in MM03
    MRP1 --> MRP Type = P3
    MRP1 --> MRP Controller = 017
    MRP3 --> Planning material = empty
    MRP3 --> Planning plant = empty
    The BOM in cs11 for plant 1020 material 12345
    has 3 components
    Comp#1
    Comp#2
    Comp#3
    The Dependency is code
    TABLE TB_1020_SUPERBOM (PP_nuance_interne = $ROOT.PP_nuance_interne,
    PP_dim_billette_bom = $ROOT.PP_dim_billette_bom,
    PP_CODE_LONG_BILL = $ROOT.PP_CODE_LONG_BILL,
    pp_component_bom =$self.pp_component_bom).
    The dependency is not found because it is looking for it in the plant 1070 and not the plant 1020.
    When the MRP runs for a Delivery type stock transfer order I get
    CONFIG_1020_BILLET <---- This is the BOM item component field in CS11 in the Basic data tab
    Comp#2
    Comp#3
    instead of
    Comp#1
    Comp#2
    Comp#3
    When I run MRP for the same material, if there's no
    "Delivery based on Stock transfert orders" the MRP associates the correct components
    Hope this explains m'I situation.
    Regards!
    Curtis

    Hi,
    If you want a reply in one line, it would be SAP R/3 does not supoort this feature.
    You will have to go for APO module.
    There are few things which can be done in R/3 side, as in maintaining a scope for MRP run in OM0E, maintaining special procurement key etc etc, but all these will not do any check of stock in another plant & can only help in a very limited way if all any for your specific need.
    But SAP R/3 provides a cross plant evaluation via MD48 to know the stock & demands at all plants, this can help only for evaluation purpose.
    Hope it clarifies.
    Regards,
    Vivek

  • How to run MRP for BOM as well as ROL items

    We have only one plant. I  want to run MRP for BOM items as well as ROL items.  MRP can be  run plant wise thru tcode MD01.  I want to run mrp for only ROL items.
    Please suggest
    Regards,
    ( Rajneesh Gulati )
    Edited by: Rajneesh  Gulati on Jun 20, 2008 11:33 AM

    As I understand for Quartz, I think you should create a security subject for it in your code. I guess the background tasks in Quartz work in separate threads. It is not recommended in EJB application. you can use EJB timer service instead.
    -Albert

  • How to run mrp as a background job

    Hi
    my client is asking me to  schedule an  mrp  run for 1 plant at 8pm.
    how do i do this. can i schedule mrp in such a way that it automatically runs every day at 8pm.
    is there ane report where i can get all the planned orders that are generated for that mrp run irrespective of material.

    Deepu,
    I can't imagine why a person would want to see ALL planned orders for an MRP run.  If this is a legitimate requirement, you could do an SE16 display of table PLAF.
    In most companies, planning workload is divided up amongst various MRP controllers.  Each controller wishes to see only the planned orders that are relevant for his products.
    CO41 is a transaction that is designed for the mass conversion of planned orders to production orders.  However, the initial display screen is in fact a listing of planned orders.  This is the type of report that a planner would be more likely to wish to review.  It allows branching to MD04 and to other relevant screens which would help a planner to make the relevant decisions.
    Regards,
    DB49

  • MRP areas and MRP controller..

    In a plant if there are some 100 x materials and 100 y materials..
    The requirement is when the 100x materials are planned ,The 100 y materials should not be planned(i e 100 y materials should not be considered in planning). How to map this in MRP.
    I have heard that using MRP controllers or MRP areas this can be achieved.But I don know how?
    If anybody cud help me in how to proceed this?

    HI
    This can be achieved through the user exit in MD01 based on MRP controller assing different MRP controller for X and Y material and with the help of ABAP you can use exit in MD01 and run mrp  with that  exit in MD01
    sorry the user exit which is used in my scenario which is  same as of yours is M61X0001 as Suggeste by Mr Mangalraj
    Regards
    Anupam Sharma
    Edited by: anupam sharma on Nov 26, 2009 11:15 AM
    Edited by: anupam sharma on Nov 26, 2009 11:17 AM

  • What are the dependent master data for running MRP

    Hi Experts,
                      My client wants to Run MRP After 8 Months of implementation. Now i want to know
    1) What are the Master Data need to be check. They are Using the Strategy 20.
    2) They have confirmed sales order for few customers. Forecast sales orders for few customers.How to map it in sap.
    3) Where will i get Gross Requirement in SAP. Because  MRP run will generates the net requirements.
    4) Is there any report in SAP displays the Forecast values for the selected material.
    Please help me on the above points.
    Thanks
    Satheesh

    HI Vishwa Upadhyay,
                                     Thank you Once again,
    The first point is cleared. Can you please suggest me on the 2,3& 4 points please. What are the configuration settings needed for the different sales order type( i.e.. confirmed and forecast)
    Thanks
    Satheesh.N

  • Not running MRP but has Purch Req with Sales Order as pegged reqmnt in AFS

    Hello Gurus!
    MRP run is activated in the Plant but we do not run MRP (no MRP batch job nor manual MRP). However, there are materials that have Purch Reqs with creation indicator as MRP showing pegged reqmnt from Sales Order even if Item category is the same.
    My initial check shows that those materials with issue has MRP Indicator as BLANK(Multi-level, transaction dependent MRP) and those that do not generate Purch Req from SOs has N(No transaction-dependent MRP). However, transaction dependent MRP is not activated.
    Can you provide areas where I should check/other probable cause of this?
    Your valuable insights is deeply appreciated. Thanks!

    Hello?
    I just want to update how this was resolved.
    I found out that MRP Indicator field in AFS MRP view for the materials with MRP generated Purch Reqs is maintained as BLANK(Multi-level, transaction dependent MRP) in AFS MRP view instead of N(No transaction-dependent MRP) but there is no transaction group maintained. So MRP run is triggered whenevert there is MRP relevant transactions performed.

  • Dump while running MRP: MD03:   PERFORM_CONFLICT_TAB_TYPE CX_SY_DYN_CALL_IL

    Dear All,
    I am trying to run MRP for a single item at a single level. The program is giving a dump.
    If anyone knows a way around kindly tell me.
    Thanks. Anu.
    SHORT DUMP:
    Runtime errors         PERFORM_CONFLICT_TAB_TYPE                                         
    Exception              CX_SY_DYN_CALL_ILLEGAL_TYPE                                       
           Occurred on     28.02.2008 at   12:19:49                                                                               
    Illegal type when passing an internal table to a FORM                                                                               
    What happened?                                                                               
    Error in ABAP application program.                                                                               
    The current ABAP program "SAPLEINU" had to be terminated because one of the              
    statements could not be executed.                                                                               
    This is probably due to an error in the ABAP program.                                    
    A FORM was called incorrectly.                                                                               
    What can you do?                                                                               
    Print out the error message (using the "Print" function)                                 
    and make a note of the actions and input that caused the                                 
    error.                                                                               
    To resolve the problem, contact your SAP system administrator.                           
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer                 
    termination messages, especially those beyond their normal deletion                     
    date.                                                                               
    Error analysis                                                                               
    An exception occurred. This exception is dealt with in more detail below                 
    . The exception, which is assigned to the class 'CX_SY_DYN_CALL_ILLEGAL_TYPE',           
    was neither                                                                             
    caught nor passed along using a RAISING clause, in the procedure                         
    "ME_UPDATE_AGREEMENT_PO" "(FUNCTION)"                                                   
    Since the caller of the procedure could not have expected this exception                 
    to occur, the running program was terminated.                                           
    The reason for the exception is:                                                         
    Incorrect FORM call.                                                                     
    The FORM call is incorrect for parameter number 1.                                       
    The current internal table passed to the formal table parameter has                      
    a type that is not compatible with the type of the formal parameter.                     
    The condition selected below has been violated:                                                                               
    (" ") The access types defined for the tables are incompatible.                          
          The following hierarchy shows the compatibility rules:                                                                               
    ANY_TABLE                                                                               
                        INDEX_TABLE   HASHED_TABLE                                           
                STANDARD_TABLE    SORTED_TABLE                                                                               
    A concrete access type is only compatible with types higher                        
          in the hierarchy. For example, STANDARD_TABLE is compatible                        
          with INDEX_TABLE and ANY_TABLE, but not with HASHED_TABLE.                                                                               
    ("X") The line types of the tables are incompatible.                                                                               
    (" ") The table keys of the tables are not identical.                                                                               
    (" ") One of the tables has a UNIQUE key, but the other has a                            
          NON-UNIQUE key.                                                                               
    How to correct the error                                                                               
    The exception must either be prevented, caught within the procedure                      
    "ME_UPDATE_AGREEMENT_PO"                                                                
    "(FUNCTION)", or declared in the procedure's RAISING clause.                             
    To prevent the exception, note the following:                                                                               
    You may able to find an interim solution to the problem                                  
    in the SAP note system. If you have access to the note system yourself,                  
    use the following search criteria:                                                                               
    "PERFORM_CONFLICT_TAB_TYPE" CX_SY_DYN_CALL_ILLEGAL_TYPEC                                 
    "SAPLEINU" or "LEINUU04"                                                                 
    "ME_UPDATE_AGREEMENT_PO"                                                                 
    If you cannot solve the problem yourself, please send the                                
    following documents to SAP:                                                                               
    1. A hard copy print describing the problem.                                                
       To obtain this, select the "Print" function on the current screen.                       
    2. A suitable hardcopy prinout of the system log.                                           
       To obtain this, call the system log with Transaction SM21                                
       and select the "Print" function to print out the relevant                                
       part.                                                                               
    3. If the programs are your own programs or modified SAP programs,                          
       supply the source code.                                                                  
       To do this, you can either use the "PRINT" command in the editor or                      
       print the programs using the report RSINCL00.                                                                               
    4. Details regarding the conditions under which the error occurred                          
       or which actions and input led to the error.

    Dear All,
    I am trying to run MRP for a single item at a single level. The program is giving a dump.
    If anyone knows a way around kindly tell me.
    Thanks. Anu.
    SHORT DUMP:
    Runtime errors         PERFORM_CONFLICT_TAB_TYPE                                         
    Exception              CX_SY_DYN_CALL_ILLEGAL_TYPE                                       
           Occurred on     28.02.2008 at   12:19:49                                                                               
    Illegal type when passing an internal table to a FORM                                                                               
    What happened?                                                                               
    Error in ABAP application program.                                                                               
    The current ABAP program "SAPLEINU" had to be terminated because one of the              
    statements could not be executed.                                                                               
    This is probably due to an error in the ABAP program.                                    
    A FORM was called incorrectly.                                                                               
    What can you do?                                                                               
    Print out the error message (using the "Print" function)                                 
    and make a note of the actions and input that caused the                                 
    error.                                                                               
    To resolve the problem, contact your SAP system administrator.                           
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer                 
    termination messages, especially those beyond their normal deletion                     
    date.                                                                               
    Error analysis                                                                               
    An exception occurred. This exception is dealt with in more detail below                 
    . The exception, which is assigned to the class 'CX_SY_DYN_CALL_ILLEGAL_TYPE',           
    was neither                                                                             
    caught nor passed along using a RAISING clause, in the procedure                         
    "ME_UPDATE_AGREEMENT_PO" "(FUNCTION)"                                                   
    Since the caller of the procedure could not have expected this exception                 
    to occur, the running program was terminated.                                           
    The reason for the exception is:                                                         
    Incorrect FORM call.                                                                     
    The FORM call is incorrect for parameter number 1.                                       
    The current internal table passed to the formal table parameter has                      
    a type that is not compatible with the type of the formal parameter.                     
    The condition selected below has been violated:                                                                               
    (" ") The access types defined for the tables are incompatible.                          
          The following hierarchy shows the compatibility rules:                                                                               
    ANY_TABLE                                                                               
                        INDEX_TABLE   HASHED_TABLE                                           
                STANDARD_TABLE    SORTED_TABLE                                                                               
    A concrete access type is only compatible with types higher                        
          in the hierarchy. For example, STANDARD_TABLE is compatible                        
          with INDEX_TABLE and ANY_TABLE, but not with HASHED_TABLE.                                                                               
    ("X") The line types of the tables are incompatible.                                                                               
    (" ") The table keys of the tables are not identical.                                                                               
    (" ") One of the tables has a UNIQUE key, but the other has a                            
          NON-UNIQUE key.                                                                               
    How to correct the error                                                                               
    The exception must either be prevented, caught within the procedure                      
    "ME_UPDATE_AGREEMENT_PO"                                                                
    "(FUNCTION)", or declared in the procedure's RAISING clause.                             
    To prevent the exception, note the following:                                                                               
    You may able to find an interim solution to the problem                                  
    in the SAP note system. If you have access to the note system yourself,                  
    use the following search criteria:                                                                               
    "PERFORM_CONFLICT_TAB_TYPE" CX_SY_DYN_CALL_ILLEGAL_TYPEC                                 
    "SAPLEINU" or "LEINUU04"                                                                 
    "ME_UPDATE_AGREEMENT_PO"                                                                 
    If you cannot solve the problem yourself, please send the                                
    following documents to SAP:                                                                               
    1. A hard copy print describing the problem.                                                
       To obtain this, select the "Print" function on the current screen.                       
    2. A suitable hardcopy prinout of the system log.                                           
       To obtain this, call the system log with Transaction SM21                                
       and select the "Print" function to print out the relevant                                
       part.                                                                               
    3. If the programs are your own programs or modified SAP programs,                          
       supply the source code.                                                                  
       To do this, you can either use the "PRINT" command in the editor or                      
       print the programs using the report RSINCL00.                                                                               
    4. Details regarding the conditions under which the error occurred                          
       or which actions and input led to the error.

  • MRP issue after MRP run

    Hello Everyone,
    We have a issue in the MRP process. When we run MRP it creates PR for additional quantity then needed not considering the Purhcase Order that exisits already. Below example will explain you in detail.
    Product A Plant ABC
    Stock 4
    Product A safety stock = 8
    Purchase Order creatred = 3
    So when MRP run it should create another Purchase requistion for Quantity 1 (4-8+3 =1). But it is creating a Purhcase Requistion for Qty 4 which means it is not looking into the Purhcase Order Qty 3 that is coming in. There is no minimum lot size or any rounding rule.
    Please can you tell me if there is a settings/config where we allow/not allow the Purchase Order to be considered during MRP run. I think it should be a plant specific config as for our other plant I dont see this happening.
    Any help will be appreciated.
    Thanks
    SAP Fan

    hi,
    Few checks:
    1. Check rescheduling horizon...
    2. check the plannning key set while running the MRP....is it NETCH...try with NETPL or NEUPL if doing for first time...
    Regards
    Priyanka.P

  • The problem about running MRP by MDBT

    Hello everydody,
    I encountered a strange problem in SAP system when I runned MRP by using MDBT.
    Usually running MRP has two ways.First running MRP by using T-code MD02 ; second running MRP by using T-code MDBT in the background.In my SAP system,I used T-code MDBT to run MRP, and the MPR parameter is below:
    Scope of planning
    Plant                             2000
    Processing key             NETCH 
    Create purchase req.      1      
    Schedule lines                 3      
    Create MRP list                1      
    Planning mode                 3      
    Scheduling                      1      
    Planning date             2010.06.30
    Normally if I choosed the Planning mode 3 Delete and recreate planning data,then after running MRP ,the Plan orders' number and purchase requestions number should be changed and produced new numbers.
    But I used T-code MDBT to run MRP, the Plan orders' number wasn't changed,the purchase requestions' number was changed. If I used T-code MD02 to run MRP, the  parameter is the same as above.After running MRP,the plan orders' number and the purchase reequestions' number were changed.
    I don't know how caused this happening.
    Is  there anybody who can help reslove this problem?
    Thanks & Best regards!

    Hi,Nikolai
    I was spending vacation, i can't get that now, and i will send it to you as soon as possible,i think maybe that error occured beacause I updated the metadata from V 9.0.2 and imported it into the new version of Builder?

  • Using MD50 to run MRP for Sale Order

    Dear all,
    I have some problem when using MD50 with Mill Product Industry.
    When SAP system not activate Mill Product yet. I used transaction code MD50 to run MRP for Sale Order, the system have generated planned order for multilevel. But when SAP system have activated Mill Product, I used transaction code MD50 to run MRP for Sale Order, the system only generate planned order for single level. I think that we have to configure something based on Mill Product Industry. So can you help me for this
    Thanks, Regards

    Hi,
    Check with following links which may help you resolve your issue :
    http://www.sap.com/sme/whysap/industries/millproducts/index.epx
    http://help.sap.com/saphelp_di471/helpdata/en/4e/1796374b088e5ce10000009b38f8cf/frameset.htm
    http://help.sap.com/content/documentation/industry/docu_is_mill.htm
    Regards,
    Tejas

Maybe you are looking for