MRP - MD03 -

Hi,
When is executed the MD03, SAP is creating planned orders when the material already has several documents associated (purchase requisition, purchase order, etc.) that fulfilled the reorder point, maximum stock level and Lot size, and this result is incorrect.
I have been reviewing the material master views (MRP1, MRP 2 and forecast) but I have not detected why SAP create these planned orders.
Could you please help me?
Thanks!

Hi,
    Go to the Transaction OPPJ and check the checking rule for your plant. Then go to Determine check and select your checking rule there. Go to the details, there you can see some check box like Include purchase orders, Include purchase requisitions,etc.. Here you make the check mark which are the receipts you want to included in MRP run.
Now the MRP will consider all these things and will not create new proposals.
Hope it will be clear.
Regards,
Vijay.

Similar Messages

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

  • Help me to guide create schedule lines in MRP

    hi
    This is my MRP initial screen
    Processing key          NETCH               Net change for total horizon
    Create purchase req.    1                   Purchase requisitions
    Delivery schedules       3                   Schedule lines
    Create MRP list           1                   MRP list
    Planning mode             3                   Delete and recreate planning data
    Scheduling                   1                   Basic
    I already Maintain the Source list in ME01 with Vendor & Plant then input the Scheduling agreement number and the MRP as 2.
    but i counld,t get schedule lines why
    thanks
    jai
    Edited by: Jai on Sep 30, 2008 12:55 PM
    Edited by: Jai on Sep 30, 2008 12:55 PM

    hi friends,
    once i run the MRP MD03 it creates only PR
    there is no schedule lines
    thats also my problem
    please expalin and solve my problem
    thanks
    jai

  • MRP type V1

    Dear All,
    Please let me know the settings in material master for MRP type V1. I have enetred lot size as MB. Minimum lot size 200, reorder point 100. After MRP run we received purchase requisistion of 200. Then we created sales order due to which now there is requirement of 300 pcs for that material but system is not considering the shortage of 100 pcs. please let me know the reason.
    Regards,
    SAP CONS

    Dear
    MRP Type V1 consider the re-order point quanity  and generate the requirement after MRP run .In your case , it frist consider the Re-Order point , then Minimum Order Quantity  and do not consider the Sales Order .But it will also consider the Sales Order as demand on priority if the Sales Order Quantity is more than the Re-Order Point .
    Let , say you do not have stock .U have Sales Order Quanity 2000 pc  and re-order point in Material Master 1800 pc , Mini Lot Size 1000 .If you run MRP-MD03,  the result will be  based on the MRP Type-V1 considering the re-order point qty after calculating Net Requirement and generate PR with 1000PC  and rest .
    More over , you are using MB-Monthly Lot size , it will club all the Monthly requirement as  PR in the Planning Horizon based on your MRP  run  date .
    So if you use , MRP Type PD , i hope it will consider your Sales Order Requirement along with your PIR
    Regardss
    JH

  • Question on MRP lot size.

    Greetings Gurus
    I have a question on running MRP and lot size. We would like to run MRP for our horizon period of 4 months.
    Basically, we want SAP to create a single purchase requisition for any requirements that falls within this 4 month period,
    But any requirements that fall outside of this, we want SAP to exclude (horizon MRP group set to 4 months)
    I am having difficulty making this happen.
    I think it may have to do with my lot size definition. Icopied lot size MB and changed the no of periods to 4.
    But when I run MRP (@MD03, Processing key = NETPL, Create PR= 1, DelScd = 3, everything else = 1),
    it creates 2 requisitions, one for theimmediate 4 month horizon period, but then it creates another requisition for the next 4 month period.  
    When I set my lot size to MB, it creates everything within the single 4 month horizon period as I expect, but it breaks it up into
    requisitions by month.
    Any advice on how I can accomplish this?
    Thanks in advance
    Regards
    Ken

    Hi Ken,
    Txn Code OMI4, make a copy of lot size MB to say Z3 & give a description as required, then change the value of No. of periods to 3 & save. Now you can assign this in your Material Master.
    you need copy as Z3 from MB and also assigned to material master (view MRP1), and the short term parameters as per below:
    - No of period = 4
    - Lot size proced = P
    - Lot size ind = M
    - Scheduling = 1, else <blank>
    For further any issues pls share with us.
    Regards
    Sanjeet Kumar

  • Purchase order minimum order quantity

    If mininum order quantity is 5000 for a particular material code. We have 3 PRs with quantity 2000, 1000, 500 ea. When we create PO w.r.t. these 3 PRs system creates PO with 5000 Ea quantity for each PR. There by the PO quantity is 15000.  Client requirement is that when these 3 prs are converted into a single PO, the quantities should get added first and then rounded.
    In this case 20001000500 = 3500 (added quantity) and then minimum quantity of 5000 should be ordered. Kindly suggest.

    Dear
    Goto MRP1 VIEW -Keep Mini  Lot size as 5000  .Test it in Sand box with a demand of 2000 and run MRP MD03 , I hope it will generate PR of 5000  if you do not have any stock .
    You can also keep period lot size ( MB/WB) in MRP1 view with Individual and Collective Indicator ( MRP4)   so that it will club all the requirement in that period and generate on PR of total qty
    Check and revert back
    Regards
    JH

  • Reg:Planning Strategy 40

    Hi friends,
    i need to know about planning strategy 40.
    For EX:
    1. suppose if we have  planned and created PIR from january to march(quarterly plan) for any product, now if we want to change the plan how the system will behave..can we change the PIR  which we have generated from JANUARY TO march.
    If it is possible to chnage ,,how to change the PIR..what will be the impacts.
    2' Can we create another PIR once again from january to march...or feB to march apart from existing PIR
    3. suppose if i have created PIR from january to march , and splitted into daily  plan, in between if the sales orders comes how this planning strategy 40 will behave.As it is make to stock.
    For Ex:
    We have planned 1000 numbers in the month of january, daily 50numbers production.
    Suppose if we get sales order for another 2000 apart from our planning 1000numbers ,how this planning strategy will behave.
    Thanks in addvance.

    Dear
    Planning startegy 40 works like follows :
    It is basically Consumption of PIR not Reduction of PIR .
    Example :Let say you have  PIR for 1000  for January  and it is appearing in MD04
    Now you have sales order for another 2000  for same month .Here PIR quantity is less than the Sales Order Qty ! Now run MRP -MD03/MD02 -NETCH , 2,1,3,3,2 and check the Result .Here PIR will be vanished and PR/Planned  of 2000PC will be appearing in MD04.So PIR is consumed by Sales Order .
    Now you have   PIR for 2000   and you have sales order for another 1000  for same month .Here PIR quantity is more  than the Sales Order Qty ! If you goto MD04-Sales Order will not appear at all .That means Sales Order is geting fullfilled by PIR deamnd. Now run MRP -MD03/MD02 -NETCH , 2,1,3,3,2 and check the Result .Here Sales will be vanished and PR/Planned  of 2000PC will be appearing in MD04.
    Refer : Re: Industry wise planning strategy usage
    Answer of your questions :
    1.You can goto MD62-Change and add PIR questiy at Material level , Plan Numbers , Product Group Level
    2.You can create but it will update th exsiting motnhly requirement  in the same planning table in MD62
    3.This question is answerd in the above explanation .
    Hope it helps
    Regards
    JH

  • Partial Production & Partial Sub contracting for halb material

    Hi,
    we have fert 1000 with halb 2000 and roh 3000. It's MTO Process and for fert i have selected collective indicator 2 and MRP Run with MD50. If halb 2000 stock is available it will be show as stock in md04 screen and if stock is not available we run mrp md03 for halb to genereate planned order. My client wants here to check the capacity availability to produce that halb..if it is available for say qty 1 then partially production order will be created and rest another qty say 1 more will be given to sub contract. In material master i have taken X as procurement type. when i am converting the planned order to purchase requsition i entered the item category as L with out any account assignment. I am not able to take goods receipt for sub contracted material because system is throwing error as account requires and assignment to co object. I also tried using account ssignment M but if do so the received sub contract material is shown against the sales order number stock..so again from there i need to trasfer to unrestriced for using to the header fert production order. I want the halb production order cost and subcontract cost to be accounted to sales order.
    Some one Please help me. Answers will be rewarded.
    John

    Hi,
    I believe your solution may be:
    1) make settings that while you release the production order system checks the capacity availability, if there then release the order otherwise do not release the order.
    2) I think you can go for production version option too where you can either go for external subcontracting or inhouse production.
    3) I think you have project systems there. So the cost will definately go to the project if the requirement is against a WBS elememnt for the project & the settings in FICO module have done by your Fi person.

  • Automatic reorder point

    Hi
    I have following setting in material.
    Mrp type -VM
    service level -- 80 %
    planned delivery time -- 2
    But system is not creating any proposals.

    Dear ,
    Both ROP-Automatic and Manual as well as FBP , system uses the Past Consumption (Movement Type 601, 261, etc -Consumption against Sales , projects , free issue of material through Movement Type -OMJJ-Material Master Update as Planned or Unplanned Total Conmtion in MMR-Forecasting View ) of certain period and Create Demand through Forecasting .
    Now this demand-Forecasted Demand or Re-Order Point (which also a demand qty ) will teated through MRP to have Procurement Element based on planning situation after Net Requirement Calcualation  and also Safety Stock..
    So basically , what you have to do as a test trial is as follows :
    1.Maintain Forceasting View of the Material master with Model Selection , Period Forecast , Persion per session , Initialisation Indicator , Paramter Optimisation , Histty periods min 6-12 motnhs .
    2.Goto Total Consumption tab , maitain total consumption ( planned or unplanned ) -Thi is basically happnes best on the Busness txn and OMJJ updates as explained above.Now hit Excetute Forceast -it will pop up with window with model as selected ( let say Moving average -G) , continue and then you will find basica valuses , MAD , Forceasted Demand ,ROP Qty  all are in date wise .Save this and now run MRP you will find result in MD04.Bsically there are two parts one is executing forcast to calcualte ROP automatically based on MRP type -VM and Forecasting view and then Run MRP-MD03
    Hope this is clear
    Regards
    JH

  • Nono-stock material as component to operation in General maint. tasl list

    Hello
    How to assign non-stock material as compopnent to operation in General task list?
    Edited by: Shiv SAP PM on Nov 25, 2010 6:32 AM

    Hi Shiv,
    Here is the solution:
    1. Create task list and enter the material code with required quantity. Keep MRP/PR column blank.
    2. Don't forget to maintain MRP view in the material master with reorder planing and minimum lot size data.
    3. Assign task list in maintenance plan.
    4. Schedule maintenance plan.
    5. Release maintenance order.
    6. Note the reservation number
    7. Run MRP MD03 - Single item, single level with material code
    8. Go to MD04 and check the PR number.
    9. Here your reservation number will convert into PR because non-stock material has stock zero in store.
    I have run this scenario successfully. I request you to try this. Item category is not required here.
    Vaibhav Mishra
    Edited by: Mishra_Vaibhav on Nov 26, 2010 6:24 AM

  • Sales order does not consumpt Independent requirement

    Hi Gurus,
    My material is as below:
    MRP Type: M0
    Stategy group:40      Planning with final assembly
    Consumption mode :2 Backward and forward consumption
    My independent Req is 'VSF  Planning with final assembly'
    My sales order item category is 'Zwac', rety is using ZWAC-M0-KSV 'Sales order with consumption'
    but before i create sales order:
    MRP element  Received/Requirement quantity   
    stock             
    IndReq              100-
    After that:
    MRP element  Received/Requirement quantity   
    stock             
    IndReq              100-
    Sales order        90-
    but i expected like this:
    MRP element  Received/Requirement quantity   
    stock             
    IndReq              10-
    Sales order        90-
    Do you know what i did wrong , thank you!
    Regards,
    dragsky

    Dear,
    If you have planning stategy 40 , then PIR qty will be consumed duirng MRP run if both PIR created with VSF and you have incomming Sales Order qty .Let say you have 100 pc PIR and also 150 pc of sales order , run MRP-MD03 ,  it will create 150 pc Planned order or PR .
    If your using and Sales Order is not getting consumed upon while running MRP , then couple of checks in this case :
    1.Is your PIR (created in MD61) "VSF"?
    The requirement type should be KSV to consume with VSF. Please check OVZI to check why your item category in Sales Order get the requirement type 041.
    Here you must have following set up :
    Requirement Class : 041 , Availablity , Requirement Check box Marked and Allocation Indicator-1 .This Alocation indicator basically Controls the consumption of customer requirements with planned independent requirements whereby the customer requirements type is only allocated one consumption strategy.If it blank that means no consumption with customer requirement .
    Please check If you want req. type 041 to consume with VSF, then you have the change the configuration of planning strategy. Use path Production -> Production Planning -> Demand Management -> Planned Independent Requirements -> Planning Strategy -> Define Strategy.
    2. What is the schedule line category in your SO ??  Is it "CP"? You are using customised item categoery zWAC which may be inharited from WAC-Order /Delivery Requirement (OVZI)
    Check and come back.Hope this will address the issue
    regards
    JH

  • Use of MRP Planning mode 2 and 3 in MD01,MD02,MD03

    Hi
    I am aware of Planning mode 1,2 and 3. . Planning file entry does the job of updating appropriate planning mode like Net change or Net change in horizon, BOM re-explode or reset proposal. But,I want to understand in what circumstances we prefer to go with planning mode 2 or 3 other than 1 in MD01 or MD02 or MD03 as anyway this is covered for all necessary items in planning file entry by system. I am fully aware of the functions of all three planning modes. Just I want to understand the situation in which it will be overwritten by user selecting 2 or 3 in MD01 or MD02 or MD03. Because I have never come across such situation where I deliberately run with planning mode 2 or 3 in MD01 or MD02 or MD03.
    Thanks in advance.

    Hi Sudhar,
    Planning Mode 1 is used when:
    1.Changes in date and quantity
    2.Requirement changes
    3.Changes in the lot-sizing procedure or MRP type
    Planning Mode 2 is used when:
    1.Changes to the material BOM
    2.Changes to the sales order BOM
    3.Changes to the phantom assembly BOM
    4.Changes to references assigned within BOM
    5.Changes to material classification
    Planning Mode 3 is used when:
    1.In-house production time changes
    2.Planned delivery time changes
    3.Scheduling margin key changes
    4.MRP controller changes
    Regards
    Vinod
    Edited by: Vinod Mohan on Mar 1, 2010 6:41 PM

  • MRP Run in MD01 and MD03 is different

    Dears,
    I am new to MRP processes. Maybe the problem is trivial maybe not.
    We have a 9 000 spare parts and would like to use a limited MRP to help operators to know which number of spare parts is coming to shortage.
    I set material master and made some settings in customizing for the plant I use.
    After that I choose one material which stock is below reorder point.
    I run MD03 and system works fine - it creates a planned order.
    However when I run MD01 (or se38 ->RMMRP000) with the same parameters as for MD03 , the system creates nothing. Only telling that MRP was run and which parameters I choose.
    I run MD16 to see maybe there are some planned order that system created and did not tell me, but nothing as well.
    Only MD03 works if I choose the material. However, collective run MD01 is not working.
    Any ideas?

    Hi Zhargal,
    Could you pls provide some more info on MRP control parameters you use while running MRP with MD01?
    Also refer the following thread for more info on MRP
    MRP: Frequently Asked Questions
    Regards
    Mangesh S

  • MD03- Run MRP for all the material

    Hi Expers,
    How to run the MRP for all the material in the Plant.In Transaction MD03 we can have the option for entering the only one material at one time.If we have 10000 material then do we have to run the MRP for 10000 time?
    Kindly guide me....
    Regards,
    Devi.

    MDBT transaction is used to for background MRP Run
    Click the below link for more details on how to proceed further.
    http://www.sap-img.com/pp019.htm
    Scheduling Background Jobs for MRP
    Transaction code : MDBT
    click Create Variant button (specified a variant name and click continue).
    Then fill in the following fields :- 
    Scope of Planning         : Optional (refer to Note if you want to specify a plant grouping)
    Plant                             : Your company Plant
    Processing Key             : NETCH
    Create PUrchase Req.  : 1
    Schedule lines               : 1
    Create MRP lists          : 1
    Planning mode              : 1
    Scheduling                    : 1
    Planning date                 : default date
    Click the Back button and you will be prompt Save Values.
    Type in a Description and click the Save button.
    After creating the variant, park your cursor at the variant and click the Schedule job button.
    Fill in the Date and Time value.
    Click Schedule periodically and you are prompt to choose the period.
    Click the Create button and you are done.
    To check, you can click the Show Scheduling button.
    Note :
    Define Scope of Planning for Total Planning in 'OM0E'.
    1. Choose New entries.
    2. Enter a key and a description for the scope of planning that you would like to define. Save your entries.
    3. Select the scope of planning and choose Sequence of plants/MRP areas.
    4. Choose new entries and enter the plants or the MRP areas in the sequence in which they are to be planned. 
        The counter determines the sequence.
    5. Save your entries.
    Hope this helps.
    Regards
    Dipak

  • Call Transaction MD03 MRP

    Hi,
    I want to make use of Transaction of 'MD03' (MRP) Program 'SAPMM61X',from my program. shall I use call transaction to do this? this program is a module pool, not an executable program. here I want to pass the plant value to the selection screen and get the message of MD03 into my program.
    could you please give me an idea for my problem?
    Thanks & regards
    Frank
    Message was edited by: Frank Rex
    Message was edited by: Frank Rex

    Hi,
    Is there any alternate to get the output list of the MD03?
    can we determine the error message using the call transaction for MD03, if yes how? Please give me some hints.
    Thanks & regards
    Frank

Maybe you are looking for