Run MRP in SAP SRM

Dear all,
we need your help.
current we are create 1 purchasing organization for multi company code.
i want to run MRP in ECC and create shopping card in SAP SRM , but is it purchasing organization has to be create for each company code so shoppingcart succed to be created ?
Regards,
Anggara Mahardika

Hi,
You just need to create one local purchase org in your SRM system.
Regards,
Nikhil

Similar Messages

  • Reports in SAP SRM

    The client I am working with is on SAP SRM 7.01 with a standalone scenario. Only when the invoice is posted and 3-way match is done, the follow-on documents are created in SAP. This is severely limiting the client to run reports in SAP SRM for day to day use.
    The client wants to run the following reports:
    Report 1: A report that shows the following columns and can be run in SRM GUI.
    Company Code, PO #, Line #, Ordered Quantity, Unit Price, UOM, Received Quantity, Invoiced Quantity
    Report 2: A report that shows the following columns and can be run in SRM GUI.
    Company Code, Invoice #, Supplier Name, WBS/Cost Center #, Invoice Amount, Invoice Create Date, Invoice Status
    Also, the client wants to extend these reports and create new ones based on the requirements.
    Any ideas on how to create these reports are welcome.
    Thanks in advance.

    Hi Kartikeya dixit,
    Thanks for your reply.
    My Scenario is like this..
    1.Selection Criteria Screen
    1.1 RFQ number : xxxxxxxxxx
    1.2 From Date : xx/xx/xxxx To Date : xx/xx/xxxx
    2.Based on the input criteria given above, get the details from FM bbp_pd_bid_getdetail for the rfq numbers given above for object_type=”BUS2200” and process_type = “RFQU”.
    3.Get the RFQ number, Created At i.e. object_id and created date.
    4.Item details can be obtained
    5.Bidder details can be obtained for partner_fct=”00000018”.From table BUT000 the fields partner, name_org1 can be obtained to print the Supplier code and supplier name.
    6.The RFX response details can be obtained using FM BBP_PD_QUOT_GETDETAIL to get the total value for the items in the rfx response.
    The object type to be selected is BUS2202 and process type = QUOT
    7.Display summation of the values for each supplier has to be displayed for each supplier.
    Can you help me what to do ....

  • SAP SRM UI (NXP) - Work Processes remain running

    Background:
    Shopping carts are being processed through the new SAP SRM UI (NXP). On occasion, dialog Work Processes are left in 'running' status even when there is nothing happening in the front end.
    It occurs for many standard programs, but when checking the WP details, all are pointing to the same class
    /IWFND/CL_MGW_RUNT_RCLNT_PRXY and function module /IWBEP/FM_MGW_CHANGESET.
    The /IWFND/*_LOG transactions aren't showing any errors or warning
    I haven't found any relevant SAP notes.
    Environment:
    Oracle 11 on AIX
    SRMNXP01                       100        0002 SRM Add-on New Experience
    GW_CORE                        190        0003 SAP GW CORE 190
    IW_BEP                         200        0007 Backend Event Provider
    IW_FND                         240        0003 SAP IW FND 240
    SAP_ABA                        701        0013 Cross-Application Component
    SAP_AP                         700        0029
    SAP_BASIS                      701        0013 SAP Basis Component
    SAP_BS_FND                     701        0013 SAP Business Suite Foundation
    SAP_BW                         701        0013 SAP Business Warehouse
    MDM_TECH                       710_700    0009 MDM_TECH 710 : Add-On Installation
    PI_BASIS                       701        0013 Basis Plug-In
    and some other bits and pieces (including SAP UI% and associated components)
    QUESTION:
    At the moment, I'm interested in a BASIS perspective; I want to ensure the platform (SRM_SERVER, GW_CORE, UI5, SRMNXP01, etc) is stable and functional. However, I'm not familiar with debugging / tuning / administrating the SAP Gateway (I still think SMG when I hear Gateway), so these may have fairly obvious answers to the right people, but ...
    1) What or where should I be looking for further clues ? My first thoughts are around the available network connections.
    2) Is there a transaction that provides real time monitoring of GW CORE ? I've found that the /IWBEP/VIEW_LOG and /IWFND/*_LOG transactions are only useful after the fact.
    thanks

    Hello Martin,
    such hanging work processes can have many causes. Which AIX version do you have? Please take a look at the note
    1873277 - Hanging Work processes on SAP Application Servers
    if it can be relevant in your case.
    Regards, Alwina

  • When SAP run mrp, it could only identifiy first 9 characters as material?

    Hi experts
      In SAP, Could we set when we run mrp, sap will only check the first 9 chars as mateiral number ?
    eg: material 12345-67890 and 12345-6789,  Could sap consider it as same material ? If there is any configure for this ?
    Thanks
    Alice

    Hi experts
    Our purpose is we need setup two material number like aaaa-aaaa1 and aaaa-aaaa2 for same part but from different localization source.
    Since they are same part , if mrp could only reconginze the first 9 character as materail number to run requirements ?   what does it mean planning material ? It could set the first 9 character as planning material different from the normal materail ?
    Thanks
    Alice

  • 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

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

  • FM or include that triggers Workflow in sap SRM 5.0.

    Hi All,
    Can anyone tell me the FM, for triggering a workflow in SAP SRM 5.0. I mean the name of the program or Include or an FM which finally triggers workflow while saving?
    Thanks,
    Edited by: Manoj Singh on Oct 6, 2011 6:51 PM

    Hi Gaurav,
    Thanks for responding. Yes, all the backend config are in place since I am able to successfully run an equivalent RFC (BBP_PD_SC_GETLIST) and another RFC named BBP_PD_SC_GETDETAIL from SE37. The problem seems to be something very specific to the ES. May I request you to run this ES at your end (if possible) and let me know the result possibly with the input and output message similar to the one I pasted in the origincal question.
    Thanks in advance,
    Nilay

  • SAP SRM Prod with Oracle DB and AIX 5.3 Performance Issue.

    Hi Basis Gurus,
    Today my SAP PRD system all of a sudden was running slow and users had difficulties executing TCodes as it took minutes before the screen appeared.My system is SAP SRM 4.00, Oracle Release 11.2.0.1.0 and AIX 5.3.
    From Basis point of view , we noticed that all the work process were hanged due to RFCs' occupying it.Couldnt investigate further on the system as we needed to restart asap because users needed to log on. A quick check on SICK shows no errors.What we managed to find out is that we needed to check this parameter below and set it accordingly:-
    rdisp/rfc_min_wait_dia_wp:-
    Definition
    Number of work processes kept free for other users.
    Use
    This parameter is used to reserve a number of dialog work processes for dialog mode. It prevents parallel RFCs from occupying all the processes.
    The parameter rdisp/wp_no_dia specifies the absolute number of dialog work processes.                               
    Unit: number of dialog work processes
    Default value: 1
    Example
    If 10 dialog work processes are configured for the instance (rdisp/wp_no_dia = 10) and the parameter rdisp/rfc_min_wait_dia_wp  = 3 is set, parallel RFCs can occupy a maximun of 7 dialog work processes. Three dialog work processes always remain free for dialog mode.
    There are 20 DIA processes in our system, perhaps reserving a minimum of about 5 work processes for DIA users will be useful via the parameter.
    So my first question would be is there any other suggestions besides adjusting the mentioned parameter above in order to ensure that no work processors going into hang state due to RFCs' occupying it as this issue always happens at the end of the month only when there are massive users accessing it.
    When we went for a restart of the system we encountered another issue. Steps to the issue are as below:-
    1) Did a proper shutdown of Oracle and SAP.
    2) When we start using startsap script, it doesn't start DB so we started DB manually but listener was having problem
        so we stopped all.
    3) We also did a cleanipc, it too throws below error:-
    sidadm> cleanipc <systemno> remove
                   exec(): 0509-036 Cannot load program cleanipc because of the following errors:
                   0509-130 Symbol resolution failed for cleanipc because:
                   0509-136   Symbol memmove (number 106) is not exported from
                   dependent module /usr/sap/sid/SYS/exe/run/libsapu16.so.
                   0509-192 Examine .loader section symbols with the
                   'dump -Tv' command.
    4) Also the Listener file has no contents,it's null file.
    5) This is another error :-
        exec(): 0509-036 Cannot load program /oracle/sid/112_64/bin/tnslsnr because of the following errors:
        0509-150   Dependent module /oracle/sid/112_64/lib/libttsh11.so could not be loaded.
        0509-101   The module has too many section headers
        or the file is damaged
    The libttsh11.so file was empty dated 25th timestamp as below in PRD:-
    -rw-rr    1 sid   dba               0 Nov 25 07:12 libttsh11.so
    Further checking has let me to understand this is an Oracle Bug from this link:-
    http://gavinsoorma.com/2009/12/11-1-0-6-clusterware-upgrade-to-11-1-0-7/
    This Oracle bug only happens in an Upgrade time and how could this happen to my Production system during a restart process.
    Also this system was restarted during the last weekend's maintainance window and it came up with no issues.
    6) We copied over the libttsh11.so from our QA environment to PRD and did a Startup:-
    -rwxr-x---    1 sid   dba        65967496 Nov 25 07:40 libttsh11.so (This is the copied over file from QA)
    7) After Startup everything has been in order till now.
    My second question is what went wrong with the libttsh11.so file. How could it be 0 size in PRD when no signs of changes had happen to the PRD system. Is this a proven Oracle Bug or something else since I have never encountered anything like this before. Hope all the Gurus here could shed some light into my 2 questions as I am looking for positive answers.
    Thank you.
    Regards,
    John

    Hi,
    Firstly I would suggest you to upgrade your database from Oracle Release 11.2.0.1.0 to Oracle Release 11.2.0.2 . This is the recommended Oracle 11g database version  for SAP solutions. Many of your problem will get resolved with it.
    Question 1:
    So my first question would be is there any other suggestions besides adjusting the mentioned parameter above in order to ensure that no work processors going into hang state due to RFCs' occupying it as this issue always happens at the end of the month only when there are massive users accessing it.
    For immediate resolution the approach you have followed is correct viz limiting number of dialog processes for RFC. Secondly you need to analyze why RFC processing takes so much time. You need check which programs are getting executed by those RFC.
    Generate EarlyWatch report for more detailed view
    Question 2:
    My second question is what went wrong with the libttsh11.so file. How could it be 0 size in PRD when no signs of changes had happen to the PRD system. Is this a proven Oracle Bug or something else since I have never encountered anything like this before.
    The libttsh11.so library cannot be found in the related directory.
    Cause
    The file system is mounted using CIO option, but per Note 257338.1 Direct I/O (DIO) and Concurrent I/O (CIO) on AIX 5L, an ORACLE_HOME on a filesystem mounted with "cio" option is not supported.
    Such a configuration will cause, installation, relinking and other unexpected problems.
    Solution
    Disable the CIO option on the filesystem.
    References
    NOTE:257338.1 - Direct I/O (DIO) and Concurrent I/O (CIO) on AIX 5L
    Hope this helps.
    Regards,
    Deepak Kori

  • 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

  • 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

  • Run MRP for multi Plant

    Dear all
    I want to ask you about running MRP for multi plant based on SAP ECC EHP4.
    I have a situation as below:
    I have 2 plant are 1000 and 2000. In plant 1000, I create a production order in plant 1000. The component is store in both of plant 1000 & 2000.
    So, when I run MRP. Does system will check stock from both plant 1000 & 2000?
    Because my company is keeping raw material in 2 plant, and there are one plant have been used for production.
    I want you confirm that Does SAP ECC EHP4 can run MRP for multi plant and the system will check stock on multi Plant?
    Thanks

    Hello,
    The scope of planning is used to control whether the total planning run is executed on a multi-plant level
    several plants
    one MRP area
    several MRP areas
    a combination of plants and MRP areas.
    Here the planning will cover all the material which is relevant for planning in all the above given areas.
    You can carry out the total planning run for the scope of planning online or in background mode. The planning run, however, must always be started with parallel processing.
    Hope it helps. Please revert back.
    Alok Tiwari

  • Run MRP for process order's requirements only

    Dear Gurus,
    is it possible to run MRP only for opened process orders, created on basis of planned orders?
    The issue caused by very often production plan changes:
    Example:
    - during the working week quntity of one producing finished good can be frequently changed:
    either down or up.
    All these plan changes are shown in data of opened process orders (there is no other useful way)
    To make such changes in MD62 won't be correct (plan and fact have to be compared)
    At this moment system generates purch requsitions on the basis of all requirements (planned orders and process orders for finished good).
    Partition of planned and process requirements will allow us to make the most accurate procurement supply.
    Thanks a lot to all who will answer.
    Viktor.

    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