To run MRP status of WBS

Dear All,
To run MRP from MD51 against a WBS what is the status of WBS to be?
WBS should be in CRTD or REL.
Pls share your views
Thanks

Dear All,
Pls share your views
Thanks

Similar Messages

  • Grouping, Pegging and Distribution (GPD) when run MRP for PS

    Dear all,
    As you know, MRP is a core of Planning Process. So when you run MRP for PS, SAP can't check stock in general stock and project stock at the same time. Now, my client have accept to run MRP base on project stock. But there are some problem when they give me requirement and actually situation in their company. One of them as below:
    They have 3 WBS element (WBS 1, WBS 2, WBS 3) and they use the same material A. Their requirement is they want to run MRP to plan material for 3 WBS.
    Solution 1: use MD51 and run MRP for Project definition and each of WBS element have respective project stock, the system will generate some of planned order for each oder reservation. After that, I will convert all of planned order to PR => PO => Good Receipt for each WBS element. When run MD04, I can see the stock for each project stock for respective WBS element.
    Ok, I will talk about the limited of this solution. I suppose after complete technical for all of order reservation in WBS 1 and in project stock of WBS 1 have 3 material A not be use. But in WBS 2 is missing 3 material A. So when I run MRP again for WBS 2 by tcode MD51, the system will generate new planned order for this missing material A. This is not logic because I have enough material A for reservation in WBS 1. So I suggest my client that you should transfer material A from WBS 2 to WBS 1, they agree with me if they don't have many WBS element. But they have about 300 WBS element and they can't do transfer posting between many many WBS element. This solution 1 is not be accept.
    Solution 2: I use GPD for this requirement. Firstly I will group WBS 1, WBS 2 and WBS 3 into WBS group. So use tcode MD04, I can see only WBS group and all of order reservation in each WBS 1, 2, 3 be showed on MD04 table. When I run MRP, the system will generate planned order for them. After that, I will conver all to PR => PO => Good receipt to WBS group. And in MD04 table, I can see project stock for WBS group. I begin transfer material from WBS group to each WBS 1, 2, 3. When all of order reservation in WBS 1 is technical complete, the material in WBS 1 have 3 material A not be use. And in WBS 2, I have a new order reservation and it be assigned 4 material A. At this time, project stock on WBS group is 0 but in WBS 1 is 3. But when I run MRP by tcode MD51, the system generate planned order with amount is 4. I wonder that why SAP does not check all material on all WBS element in WBS group to suggest a planned order with amount is 1. If SAP can solve this problem, my client will be accept this solution.
    Hoping you support me.
    Thanks, Regards
    Hoai Vu

    Hi Ahmed Rifaee
    Thanks for your reply, I will talk about process in SAP.
    So, I have 2 WBS element, that's simple because my project is have about 200 WBS element.
    WBS1 have 2 order reservation for each actvity and material A0001 be use in 2 order reservation.
    Order Reservation 1 needs 3  A0001
    Order Reservation 2 needs 5  A0001
    WBS2 have 1 order reservation for each activity and material A0001 be use in it
    Order Reservation 3 needs 4  A0001
    1.)     If I don't group 2 WBS1 and WBS2 to one WBS group, SAP will have 2 project stock for each WBS. and when I run MRP, WBS1 and WBS2 run independent base on current project stock at each WBS. So, although project stock WBS1 is run out of A0001 while A0001 still exist A0001 in project stock WBS2, SAP still generat planned order for missing part A0001 in project stock WBS1.
    2.)     If I use GPD by group WBS1 and WBS2, I can solve this problem easy because they will use only one project stock for WBS group. Ok, after I good receipt A0001 into project stock, I'm sure that I have enough A0001 for 2 WBS1 and WBS2. But I can trace which reservation be ordered to delivery to them exactly. I try to use tcode MD09 to trace from Purchase order to Order reservation but I have just to trace in case PO have not been good receipted. I wonder that Pegging can help me in this case (PO have been good receipted).
    Can you give me any idea for these problem
    Thanks, Regards
    Hoai Vu

  • WBS status to run MRP

    Dear All,
    To run MRP from MD51 against a WBS what is the status of WBS to be?
    WBS should be in CRTD or REL.
    Pls share your views
    Thanks

    Dear All,
    Pls share your views
    Thanks

  • Run MRP for production order/maintenance order has been release

    Hi all,
    please tell me how to configure for running mrp for production order/maintenance order has been release. as you know, i want production order has not release will not appear in MD04. I think that is the way for running mrp will not take care about this production order has not release
    Thanks all

    Hi Hoai,
    It is impossible to exclude production order from net requirement calculation in MRP run. You may take a look at the online documentation under the PP-MRP area.
    Material Requirements Planning (PP-MRP)
       Planning Process
         Net Requirements Calculation
           Net Requirements Calculation for MRP
    But there is a way to temporarily exclude production order from MRP. That is you can set the 'delivery completed' indicator in 'Goods receipt' Tab in in production order. Please note that this order will not appear in MD04. Actually to some degree, this order could be considered as completed because ticking the indicator could set status 'DLV' for the order. But you still can execute confirmation, goods issue and goods receipt activities. This way is just a workaround. You may
    consider it.
    Or maybe you can consider the useage of BADI: MD_CHANGE_MRP_DATA to change the MRP run data to see if this could fulfill your requirement.
    Regards,
    Rachel

  • MRP status F is not visible

    Hi all,
    Hope somebody can help me in this issue. I have created a sales order for a material which already has some stock and I have done the allocation run. And the allocation was successfully carried out but still my sales order number is appearing in MRP status T not in F. What could be the reason and what I should do to proceed further?

    let me tell you one more thing is when i change screen resoloution it shows me that status bar but when i recall this screen or another screen the status bar is hide, please let me know if i miss any setting or configuration

  • 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

  • Standard report to check MRP status

    Hi,
    Is there any standard reports to check the materials based on the MRP status? (Eg: Materials that are under A(Free and avilable) etc etc)
    Im using SAP 6.0
    Thanks in advance.

    Hi,
    1. MD04 - Stock requirement list
    2. MD05 - MRP list
    3. MD06 - MRP list collectively
    4. MD07 - Stock requirement list collectively.
    Please see if need anything more.
    Regards,
    Anil

  • 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

  • Complete MRP status according to Sales order schedule line data

    Dear All,
    Please help me to get technical configuration releted to
    "complete MRP status according to Sales order schedule line data"
    or MRP w.r.t. Schedule line
    Please send fields and table and logic specification .
    Thanks & Regards,
    Ashish Gautam

    You can use following Fm for change sales order
    CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
      EXPORTING
        salesdocument     = p_vbeln
        order_header_in   = s_order_header_in
        order_header_inx  = s_order_header_inx
        behave_when_error = 'P'
      TABLES
        return            = it_return
        order_item_in     = i_order_item_in
        order_item_inx    = i_order_item_inx
        schedule_lines    = i_sched
        schedule_linesx   = i_schedx.

  • 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

Maybe you are looking for

  • Two ISPs - A&B

    Hi Experts, I am stucked with a scenerio and requesting suggestion to make that functional. 1) We having two locations (eg Location A & B) with nearby distance. Both location are having WAN connectivities with different ISPs say ISP A & ISP B.. 2) At

  • Depreciation posted as debit instead of credit

    Hello Gurus' For few Assets only,  Deprecation in 7th month (Calender year is followed) got posted as debit instead of credit & also amount posted was 6 times than the usual monthly depreciation. Please help. Thanks, VK

  • Continuous Grey Screen w/ Progress Bar

    I restarted my Macbook Pro and when the Apple logo appeared, a progress bar loaded to about 45 percent then the Mac shutdown.  This happens every time I turn on my computer.  I've tried Safe-Boot, Single User Mode and COMMAND R and none of that has w

  • Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. when open external list

    Hi i created a external list based on a external content type in shaepoint designer but i got this error in event viewer when i open this list Could not open connection using 'data source=xxxx;initial catalog=xxx;integrated security=SSPI;pooling=True

  • Security on Acrobat Form

    My client gave me a form with Changing the Document: Not Allowed and Document Assembly: Not Allowed. Is there any way that I can make myself a copy, as the developer, of this form with full access? Somehow copying the content and creating a new file?