Run MRP by vendor

Hi,
Do you know if there is any way to run MRP by vendor ?
We would like to define for a planning run only material of a particular vendor.
Thanks,
PYR
Edited by: Pierre-Yves Ryckwaert on Apr 7, 2008 2:49 PM

I suggest you use 'MD01' specifying using a user-exit (created in customizing) and a user-exit parameter. First, you create a user-exit in the customizing, then with the help of an abaper you program the exit 'EXIT_SAPMM61X_001' where you  code something like this:
clear: no_planning, stop_planning.
   case user_key.
    when 'ZVE'. " Your user-exit
       data wa_lfa1 type lfa1.
       data lv_lifnr type lifnr.
       if user_par is initial. " Stop planning if user parameter is not specified
         stop_planning = 'X'.
       else.
         move user_par to lv_lifnr. " This is the user-exit parameter
         call function 'CONVERSION_EXIT_ALPHA_INPUT' " Convert the vendor code
           exporting
             input         = lv_lifnr
           importing
             output        = lv_lifnr.
         select single * from lfa1 into wa_lfa1 where lifnr eq lv_lifnr. " Verify that vendor exists
         if sy-subrc ne 0. " ¿Doesn't exist? then no planning
           stop_planning = 'X'.
         endif.
When you execute 'MD01' you specify user-exit = 'ZVE' and user-exit parameter = 'the vendor code'.
Hope it helps.

Similar Messages

  • Running MD06 by Vendor

    Hi,
    I have a vendor that we purchase about 8 different items from.  These item/vendor has been set up in purchasing info records and my source list is correctly maintained.  The problem I'm having is that when I run MD06 by vendor, I get absolutely no information concerning those parts.  No requirements, no purchasing requisitions, nothing.  If I run the same report MD06, by MRP Controller, I see all the parts and their requirements.
    Can someone give me an idea of what I might be missing?
    Thanks, js

    First run your MD06 for MRP controller and find out that any Pur reqs or POs are assigned to the vendor for which you are trying to get through MD06.
    If any reqs or POs are created for the vendro than only it pull the data when you run MD06 with vendor otherwsie you wont see anything in the report.
    I just pull in my system and it is showing with vendor also but only those POs which are created for particular vendor.
    selection would be
    vendor number plus check all the Box and enter the date range so it wont take to long

  • Best MRP type and strategy to run MRP for component using PIR and forecast

    Hi Experts,
      I want to run MRP for Component parts. I need to run MRP based on Planned independent requirements and Forecast Data.
    Which is the best suited MRP type and strategy.
    Please help to share bestpractices if any. thank you.
    Rayudu

    Hi,
    is the components you are talking are Semi finished materials or Raw materials and Packing materials which are procured from vendors ???....
    It is not a good idea to maintain planning strategy for Components which are part of BOM...these materials are automatically planned when the header materials of these components are planned....
    If these components are not part of any BOM then you can try the option of using forecast based planning.. MRP type  VV and maintain the forecasting view in the material master
    You can also explore the option of consumption based planning like manual or automatic reorder point planning...
    Thanks
    Kumar

  • 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

  • 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

  • Ignore the number of schedule lines in sale order item when run MRP

    Dear All,
    I have a problem when I create production order (discrete manufacturing)
    When I create a sale order with one sale order item and 3 schedule lines for this sale order item.
    After that, I run MRP for this sale order, what I get is 3 planned orders for 3 schedule lines. It means that I will have 3 production orders for 1 sale order item.
    I want  create one production order for one sale order item whatever the number of schedule lines in sale order item.
    I think I have to config in MRP. Please help me.
    Thanks in advance

    Dear
    Check in OPPQ then look in Master data Availability Check & strategy for material also check whether u have maintained strategy for same material and see did u extended sales views for other material
    As u said 3 schedule lines for this sale order item check whether u have extended sales views for next material
    With Regards
    Pushpalas

  • One pr for multiple materials with line items while running mrp

    Hi SAP gurus,
                  I am config the system for MRP as per my client requerement.
                     We use CBP for different RAW materialsfor example they having a 10 materials for planning,were,
             MRP type is VB,
              LOT size is FX,with Different Reorder points and fix order quantity for all materials,
             My client whant run MRP for all these materials in single time that means they whant multiple item at single levels,
            i soles these requirement with the help of Product Group(sop) and its working but when we running md02 for product group all materials have planed and they give different purchase requistion numbers for all these materials but my client Wants single purchase requistion with line items for all these materials.
         Pls give me the solution for that requirement.
    thanks and Regards,
    abhi

    this is not the way SAPs MRP run works.
    Where is the benefit for this?
    the requisitions are not even split into header and item table, it is just one table EBAN, and either way you would get exact the same number of records in EBAN.

  • 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.

  • 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

  • What precoution should be taken to run MRP after GO-Live ?

    Dear All,
    Please give the inputs for run MRP at plan level.
    Also suggest the what type of precoution should be taken to carry out this task.
    What type of problem is to be faced after MRP run.
    Thanks In advance
    Vijay Mankar

    Dear Sir,
    Actualy,we gone live on 1st Feb, we have created the manual production order till date, & dispatched the material by maintaining the schedule line.
    Now, I have to put Plant independent requirement in Planning table.
    & convert the planned order to production order collectively by COHV on the bas
    Our aim is give production Plan for tommorow. We also used to maintain schedule lines.
    I have to give the production plan for 12 feb,
    Please revert me as soon as possible.
    Regards,
    Vijay Mankar

  • 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

  • PR not generating after running MRP

    Hi Gurus,
    System generate PR after MRP run where in material MRP Type is maintained as PD, but system doesn't create PR for those material which have MRP Type = VM. If I change the MRP Type to PD & then run the MRP, even then system doesn't create PR for that msterials.
    My system most of the materials got MRP Type VM, suggest me the solution for this issue.
    Regards,
    Shantanu

    1.MRP Type -VM , Lot Size -EX
    2.Procurement Type -E for FG and F for ROH
    3.Planning Startegy -10 or 40 in FG/SFG and 20 for componenet
    4.Planned Delivery Time in MRP2 VIEW
    Configuration : InSPRO -MRP -Check MRP Type -VM-check the details like Re-Orde point .Safety Stock both the automatic calcvualtion box are marked .
    Finally as a sample test , select any material -mm02-execute forecast in mm02-forecasting view -exectute forecast -then save .Run MRP in MD03-1,1,3,3,1.NETCH indicator and check the result in MD04.

  • Run MRP and Collective Purchase Requisition

    Hi all, I have a question for all. Very be kindly when receive your answer.
    When I run MRP, the system will be generate one Purchase Requisition for one item in BOM (10 items in BOM). So, I want to collect all requirement in BOM to only one Purchase Requisition. Does the system can support for this scenario???
    Thanks all

    >
    Hoai Vu wrote:
    > Thank all,
    > Your answer is helpfull for me, but not satisfy for my company. I have two maintenance order (MO):
    > MO 1 from DIEN department have:
    > Component A: 2
    > Component B: 3
    > MO 2 from CO department have:
    > Component C: 4
    > Component B: 5
    > When I run MRP, the system generate 3 PR
    > PR 1 for component A: 2 (from MO 1)
    > PR 2 for component B: 8 (from MO 1 and MO 2)
    > PR 3 for component C: 4 (from MO 2)
    >
    > So when the other department have a requiment for component B from CO department with quantity is 8, and the warehouse keeper will give 8 components B for CO department because they have a PR 2. So the stock of B is zero and we don't have material B for MO 1. I don't know why SAP does't have keep B and good issue only 4 for CO department. I wonder that why MRP generate one PR for component B instead of two PR.
    > And the second question is how to configure sytem. Becaus when I create a PO from PR, the system does not assign PR number into account assignment
    >
    > Thanks all
    >
    Hoai Vu wrote:
    > Dear all,
    > I would like to update my question and hope that everybody support me to solve this problem.
    > Thanks all
    Dear Hoai,
    What is the strategy maintained for header materials, i guess it is MTO ( make to order )
    If the strategy is MTO then go to MRP - 4 view for all components and make it as 1
    Then check the result
    Regards
    Madhu

Maybe you are looking for