Query for MRP Purchase Requisition

Hi Gurus,
Currently system is creating Purchase requisition for BOM Material, which I don't want system should create PR for this material.
I know MRP type ND but i need someother ways to stop it
Appricate your response
Thanks
Sastry

Hi,
You can try the following option-
1) Tcode - MM02-> MRP1 view - > Plant sp-matl status - 01 ( Blocked for procment/whse)
2) Tcode - MM02-> MRP2 view - > Procurement type - Blank(No procurement)
Sudarshan

Similar Messages

  • Issue on Number Range for MRP Purchase Requisition

    Hi Gurus,
    Please help me on the issue explained below.
    We are already using SAP ECC 6.0 and SRM 5.0 and now we are implementing Plant Maintenance Module.As a result of this implementation ,we have created number of PR document types and assigned to unique number ranges in ECC. One of these document types has been maintained for MRP group for a material type in order to identify the MRP purchase requisitions created on the shortage of the materials for these material types.
    This functionality is working fine. MRP run for the materials is picking the appropriate PR document but number range of the document is not the same what was assigned to the linked document type.Some other number series is getting picked by system .
    There is setting under SPRO Consumption Based PlanningNumber RangesPurchase Requisitions
    Here, number range assignment is against plant. This is the same number range which is being taken by system on running MRP. But the desired number range is the one which has been linked to PR document type.
    If I change the number range above then number range for MRP PR in present system will get affected..
    Can you please advise me on above so that PR generated on MRP run should have appropriate number range?
    Thanks & Regards,
    Niti

    Hi,
    As per my understanding, what you have mentioned above is exactly the way SAP is designed. Its SAP Standard behaviour.
    But if you check your PR document type - no:range & the CBP no:range both will be same only since both refers to the same object.
    Please check the PR document type that you have assigned in the CBP & its no:ranges.
    Thanks & Regards,
    Ram

  • Purchase Requisition Release strategy for MRP based Requisition

    Hello Gurus
    We want to set up the urchase Requisition Release strategy for MRP based Requisition ..Any can one Please share your experience about the impact down the road?
    Thanks
    Nick

    Hi,
    If you want include the MRP related PR in Release strategy.
    You need to include the field CEBANESTKZ-Creation Indicator (Purchase Requisition/Schedule Lines) in one of the characteristics which you create and include the characteristics value as per the field values like AReal time, BMRP, CConverted Planned order etc.. and include the charactristic in the Release Strategy will release group & release codes.
    So when ever the PR is created through MRP run then this creation indicator will update in the PR as per that release Strategy will trigger in the PR.
    there is one more option you need to create the separate document type as MRP PR then create document type as characteristics and include the values of all these document types and include in Release strategy.
    But it will  not pop up for direct PR from MRP run only trigger when planned order is converted to PR manually there you need to select this MRP document type then release strategy will trigger.
    I think first one is best suited.
    rgds
    Chidanand

  • How can i develope a report for getting purchase requisition details

    how can i develope a report for getting purchase requisition details like mrp controller release date unit of measure

    Hi,
      Go to Tcode ME53(Purchase requisition display). Give any preq number and click the item overview button..
    in the next page click select one item and press item details button(or F2 button)..In the next page all your requiresd fields will be there.. put cursor in reqd field and press f1.. in the pop up box press techical details(hammer button) to get the field name as well as the transparent table.. Use those fields and table in ur program..
    hope it helps
    Award points if it helps

  • How to create a purchase order for a purchase requisition

    Dear Experts,
       Explain the steps for creating purchase order for a purchase requisition.
    and where can i find this purchase requisition field in PO creation.

    Hi Ravi,
    Check out these documents:
    http://www.olemiss.edu/projects/sap/MM_Create_PO_with_Ref_to_a_PR.pdf
    http://www.sap.com/africa/services/education/pdf/Work_Instruction.pdf
    Regards,
    Chandra Sekhar

  • Material Number mandatory for PR exceptP for Service Purchase Requisition

    Hi All,
         Our client's new requirement is we need to give material number mandatory for Purchase Requisition. But it should not affect for Service Purchase Requisition (as we don't have material number with material type DIEN. Till now, we were using Acc Assignment Category K and Item Category D with only Short Text description). We have separate document type for Service Purchase Requisition(ZSRV).
        In order to make Material number mandatory, in PR, we need to give in "Define Screen Layout  at Document Level for PR",right? Is there any way to give, "Material Number Mandatory at Document Type Level"?
    Please suggest.
    Regards,
    rosh

    hi sridhar,
      Thank you for your answer. So as you said, there is no possibility to make material number as mandatory at DOCUMENT TYPE level through Customzining, right?
    Regards,
    Rosh

  • ENABLE SRM WORKFLOW FOR EXTERNAL PURCHASE REQUISITIONS

    Hi,
    Iu2019m creating a shopping cart using an external approver.  We require external requisition to be completed by the purchasibg manager.
    The changes were implemented as outlined in the document
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/5082a622-7310-2c10-1a9b-ef31dd69a770
    I create the purchase req in the external system and the transfer the requisition to SRM.  A shopping cart is then created. This  shopping cart goes to the purchasing manager for completion. Upon completion by purchasing manager, a message appears to say 'External requisitions do not require an approval process' and
    the workitem remains in their inbox.
    This workflow processed correctly for normal shopping carts.   I canu2019t understand why it does work for external purchasing requisitions.
    thanks
    Ann

    Hi Any one got answere this issue. I also implemented the steps provided in the document created by Prasannau2019s. The workflow is getting triggered for external requisitions now but when we are changing the PR in ECC and transferring again that time its not gettign triggered neighther its restarting the exisiting approval workflow in process (if any).
    Thanks,
    Swapnil

  • Link a MRP Purchase Requisition to a  Purchase Requisition Workflow

    Hello Gurus,
    I have a Purchase Requisition Workflow  already created.
    I want to create a MRP purchase requisition that start my workflow.
    How can I do that?
    Thanks in advance,

    Hello Charlie.
    Our release strategy hasn't classification. When we I create a MRP purchase requesition, the release stratagy is already assigned to that. however the worklow is not started.
    thanks

  • How to configure an automatic vendor assignment for a purchase requisition

    hi guys,
    how to configure an automatic vendor assignment for a purchase requisition in sap
    Thanks in advance

    hi Swathi,
    Check these Links out
    http://help.sap.com/saphelp_erp2005/helpdata/en/75/ee11e655c811d189900000e8322d00/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/5e/372e3b7532394ce10000000a114084/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/4d/2b912a43ad11d189410000e829fbbd/frameset.htm
    Regards,
    Santosh

  • How to create new requisitioner in sap mm for raising purchase requisition?

    How to create new requisitioner in sap mm for raising purchase requisition?

    Hi Dear,
    There is some link will help you to create Purchase Requisition and other MM Documents.
    http://www.docstoc.com/docs/11307932/SAP-MM-Manual-Create-Purchase-Requistion
    http://www.r3.duke.edu/training/stepbystep/#purch
    http://sapdocs.info/sap/materials-management-2/download-sap-purchasing-user-training-ppt-material/
    Regards
    Aamir

  • SRM Workflow for external Purchase requisitions ECC

    Dear experts,
    We are in SRM 7 Classic scenario , ECC 6. Using SRM process controlled workflow . We want to enable SRM workflow for external Purchase requisitions. As per SAP note 505030 topic 16 , approval is not triggered in SRM for external requirements. So we need to find a new solution as it's a clinet requirement.
    Current  scenario:
    External purchase requisition created from ME51N or Plant maintenance are sent to SOCO for buyer completion. External PRs generate a SC BUS2121 EXTR in status approved.
    Desired scenario:
    We want those external requirements to be sent to SRM for approval (approval with completion + approval)
    After implementing changes suggested in Prasannau2019s document (http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/5082a622-7310-2c10-1a9b-ef31dd69a770 ) , the Workflow is still not triggered for the external PRs, the SC is created but remains in status awaiting approval. No work item is created (neither in BBP_PD not in SWI6, not in SWIA).
    Can anyone provide some guidance on what else need to be changed in order to activate SRM Workflow for external PRs?
    Many thanks in advance,
    Nuria
    Edited by: NuriaUB on Dec 28, 2011 5:14 PM

    Hi Any one got answere this issue. I also implemented the steps provided in the document created by Prasannau2019s. The workflow is getting triggered for external requisitions now but when we are changing the PR in ECC and transferring again that time its not gettign triggered neighther its restarting the exisiting approval workflow in process (if any).
    Thanks,
    Swapnil

  • MRP reports for all Purchase Requisitions

    I want a SAP standard report that will give me a list of all Purchase Requisition created via MRP run, it can also include manually createed PR's. The main aim is for the Materials Mansger to view all PR's, even if he/she don't have the authorization to release it.

    Doesn't standard transactions (ME55, ME5A) suit your requirement?

  • MRP Purchase requisition not generating to Max stock

    Hello Gurus,
    We have implemented consumption based planning. Purhcase requisitions are automatically created based on the stock reaching reorder point.
    MRP type used is VB
    Lot Size   used is  HB
    Min lot size       is  1
    Max lot size     is   11
    Rounding value  is 1
    MRP is run using program RMMRP000 setup as a batch job.
    But the problem is purchase requisition is generated only for 1 quantity. There is no stock available in the plant and there are no open purchase requisitions or purchase orders for the item.
    So please let me know what is missing that the lot size HB is not generating PR for max stock.
    Thanks,
    Narayan

    Yesterday you wrote  Max lot size     is   11 today  Max lot size is        0
    What shall I believe now?
    The calculation of quantity in reorder point planning is described in
    Reorder Point Planning Procedure - MRP Procedures - SAP Library

  • How to de-activate Qty and Price fields for Service purchase requisition

    Dear all,
    We have a request to de-activate (leave it as "Display") the fields of quantity and gross price when changing a service purchase requisition of a specific document type.
    In example: We want that purchase requisition type NB, allows in change mode (ME52 or ME52N) to change the quantity and gross price of the services. On the other hand, these two fields must be only visible for order type ZNB. Besides this must be happening only for services.
    Changing PT9 or PT9B will affect also the creation, and if we only configure based on transacction and document type does not work.
    Any help will be highly appreciatted.
    Cheers

    Hi,
    You may have to write a output requirement routine and assign the same to the output type in NACE.
    But i don't think you will get the old and new data of Purchase order in requirement routine (program : SAPLV61B).  You may have to export the data into memory from either a BADI method or User exit and then import the same in requirement routine.
    Regards
    Vinod

  • Workflow for MM purchase Requisition steps required

    Dear all,
            I am trying to configure purchase requisition Workflow.
            I am working with Work flow, WS 00000038
            I have assigned agents to TS 20000162
            Now how to proceed further, do i need to maintain some more settings
            or i should try to test system.
            Regards,
            Gaurav sood

    Under the assumption that things have not changed much since 4.70, here's quick introduction:
    The workflow is started only when a relevant release strategy is found, so customizing of release strategies is a very important (first) step here.
    In the Implementation Guide you find the customizing in the following path:
    Materials Management
    -- Purchasing
    -- -- Purchase Requisition
    -- -- -- Release Procedure
    -- -- -- -- Procedure with Classification
    Only the procedures with classification are relevant if you want to use workflow to notify about requisitions waiting for release.
    First you must set up a classification class if that has not already been done. Derive your characteristics from the structure CEBAN. The online help is not too bad, I had never set up classifications before and managed to get it working.
    If you need data that are not available in CEBAN, or you want to modify them for the purpose of determining the release strategy there is an enhancement you can implement, and there are customer fields you can use. The enhancement definition's name is M06B0002.
    As an example of what you can do, I have used it to set the company code in one of the customer fields, and to change the account assignment type. However, whether you need this enhancement or not depends strongly on what data you use to determine your release procedures (a step in customizing you will get to later).
    When that is done you define release groups and release codes. Release codes are defined within each release group. Whether you should use one group or several groups is often a matter of choice.
    I myself prefer using several groups even if I don't have to, so long as it doesn't lead to having to define duplicate release strategies (which you will soon get to). So, if there is some characteristic that clearly separates your release strategies, e.g. the highest amount that does NOT require release etc, you can define one group for each value (group) of this characteristic.
    For instance, if some company codes require release for everything worth more than 100EUR while the default is to require release from 10.000EUR you could create to release groups. None of your release strategies will be duplicates since the value from which release is required will be different and you thus need to have that as a characteristic.
    You then check that the set-up of release indicators is OK, and then you are ready to start defining the strategies. Release stragies are defined within each release group, and use one or more release codes (two or more release indicators).
    It is fairly self-explanatory once you get into the screens. The thing to be observant about is to not define overlapping strategies, as this will prevent the solution from working.
    When you are done, and have tested the solution in DEV it is time to transport it to the QA system. That's when I got a rather unpleasant surprise. The classification data are not transported, so both the characteristics and class, as well as the classification data in each release strategy had to be redefined. And in roughly two hours I have to do it again in production.
    It is possible to transport classification information, it is described in SAP OSS Notes (different solutions for different versions).

Maybe you are looking for