Skip to Content

WRP1 per site and vendor

Hi experts, is it possible to make WRP1 to make a purchases requisitions grouped or splitted by site and vendor at the same time? Is there an standard way? or is there a BADi or user-exit that I should implement?

Thanks in advance

Add a comment
10|10000 characters needed characters exceeded

Related questions

4 Answers

  • Posted on Nov 13, 2012 at 04:55 PM

    moved from SAP ERP - Logistics Materials Management (SAP MM) to SAP for Retail

    as WRP1 is a retail specific transaction

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 13, 2012 at 09:15 PM

    Hi Nelson,

    As far as I know you could configure WRP1 to create purchasing requisitions (rather than PO/STO/Delivery directly). You can then use the standard options in ME59N to create PO by site & vendor.

    cheers

    Marcus

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Nov 16, 2012 at 08:18 AM

    Hi Nelson,

    There are some steps given below please see that, i hope your requirement will full-fill.

    Defining Planning Control Parameters for the MRP Run

    After going through this step, you would learn about the available planning control parameters to choose when you run MRP using various transaction codes in SAP.

    MRP can be run for a material or it can be run for a plant or it can be run for multiple plants configured in a scope of planning run.

    Planning is defined to run at single item level, i.e., for the header level materials only (along with explosion of dependent requirements directly below the header material in the BOM structure, levels below are neglected) or at multiple item level where planning is carried out for the header level as well as for all the dependent BOM levels.

    When you run the planning in SAP through the various available transaction codes, the selection screen gives you an option for selecting values for the following parameters. The selection screen shown below is a typical transaction code to run MRP. The Planning control parameters would be the same in all the SAP MRP Run Transaction codes.

    The following transaction code as shown in the screen shot below is MD01, which is one of the transactions used for running MRP in SAP.

    Processing Key

    The Processing key decides the type of planning run that needs to be carried out for the material – net change planning or net change planning in the planning horizon or regenerative planning. You have to choose one of the given options, when running MRP.

    Selection of Materials for Planning - Method 1:

    SAP MRP Run can use the NETCH planning or Regenerative Planning or the NETCH in the planning horizon method, to evaluate which materials are to be considered for planning. This is the recommended planning method.

    Whenever there is a change in the situation of a material, i.e., any change relevant to SAP MRP, the system creates a “planning file entry” in order to have SAP MRP consider it for an MRP Run. This is called “Net change planning” (NETCH). The Net change method - NETCH can be used for running MRP because planning all the materials regardless of a change would overload the system. These changes are categorized as an introduction of a demand put for the material or creation of reservation for the material or the material has a sales order created, or the material is issued for production or the material is issued to the sales order delivery or the material is received from a purchase order or production order or the receipts or demands are deleted.

    This is the recommended processing key, though when you start to use MRP for the first time, it is always nice to use the method 3 called regenerative planning in which the system plans all the materials in the plant or plans for all the materials in the scope of planning run.

    Selection of Materials for Planning - Method 2:

    Planning all the materials for a plant (all the materials included in the planning file) in an MRP run is called “Regenerative Planning (NEUPL)” which is used when you go-live for the first time and when you would be using the system for the first time.

    Selection of Materials for Planning - Method 3:

    You can alternatively use the “Net change planning in the planning horizon – (NETPL)” where the SAP MRP run takes place for only those materials which have undergone changes within the predefined Planning Horizon.

    Transaction code to Create Planning File Entry – MD20 / Transaction code to Display Planning File Entry – MD21

    Create Purchase Requisition Key

    This planning control parameter can control, whether you want the procurement proposal to be created as a purchase requisition rather than planned orders (Purchase requisitions are created for the externally procured materials) in the planning horizon or in the opening period. You also have an option to have the system always create planned orders instead of purchase requisitions.

    When the requirement lies in the opening period and you have an option of “creation of purchase requisitions in the opening period, MRP would process creation of requisitions instead of planned orders, though when the requirement lies outside the opening period, the system would always create planned orders. Opening period is the number of workdays before the order start date accounted as buffer time for the MRP controller to process the planned orders in to purchase requisitions.

    The procurement proposals can be created as purchase requisitions only if the procurement type in MRP views is set as “X” (both external procured and in house production) and “F” (externally procured)

    Delivery Schedules

    This control parameter is used for controlling the automatic creation of schedule lines (for scheduling agreements).

    You can control whether you want the schedule lines to be created in the planning horizon or just in the opening period or you never want it to be created.

    Creation of MRP List

    The results of the planning run are included in the MRP list after the planning run. This control parameter controls whether the system should create the MRP list for all the planned order or whether it should not at all create MRP lists or whether it should create MRP list only for the planned order which are in exception.

    You determine for which exception messages the system should create MRP lists in the configuration for MRP - Define and group exception messages.

    Planning Mode

    It is a known fact that the system plans the un-firmed planned order, purchase requisitions and scheduling agreements, again in the next planning run. This control parameter controls the very same thing.

    You have an option to use the following planning modes:

    Adopt Planning data – Whenever there is a change in requirement quantities or dates or change in lot sizing procedure, for the un-firmed planned orders, the system re-explodes the BOM for the new adjusted quantities in the MRP run.

    Re-explode BOM and routing – For all the existing procurement proposals, which are un-firmed regardless of whether they have been added with quantities or changed for dates, the system re-explodes the BOM and Routing for them. The BOM is exploded if there has been a change in the BOM master data, material classification or change in production versions or BOM explosion numbers. The existing procurement proposals are not deleted but they are worked upon.

    Delete and Recreate Planning data – For all the existing procurement proposals, which are un-firmed regardless of whether they have been added with quantities or changed for dates, the system deletes the existing procurement proposals and re-explodes the BOM and Routing for them, thereby creating new procurement proposals.

    Scheduling types

    For in-house manufactured materials, the system offers two types of scheduling:

    Basic Date scheduling – where the lead times in the material master are used to calculate the planned order start and end dates. You can use this scheduling type if the lead times are pretty much constant for a product and the detailed scheduling is not what you seek for. In such cases building of Routing/Recipe is not required and you can live with the timings set in the material master.

    Lead time Scheduling – where the addition of all the operation times in the Routings/Recipes are used to calculate the planned order start and end dates. The capacity requirements are also calculated for the planned order. This type of scheduling is used when you are interested in detailed scheduling and capacity allocation on the work centers. In organization where you have to build Routings/Recipes and carry out detailed time study so as to create the task lists.

    Thanks & Regards

    Sanjeet Kumar

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Nov 16, 2012 at 08:23 AM

    Hi Nelson,

    Try this BADI : MD_CHANGE_MRP_DATA

    Thanks

    Sanjeet Kumar

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Sanjeet, thanks for the response but have you tried this solution? I mean, I already saw all this options but they do not adapt on what I'm looking for and don't get me wrong I truly learn a lot but it is also very most important to have a proven solution from you guys, thanks anyway.

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.