Planned Requirements in SAP PP

Planned independent requirements are used to perform Demand Management functions. A planned independent requirement contains one planned quantity and one date, or a number of planned independent requirements schedule lines, that is, one planned quantity split over time according to dates.

Integration

Create planned independent requirements as follows:

• Manually by entering quantities and dates
• Automatically by copying the material forecast
• Automatically by copying the results of Sales and Operations Planning
• Automatically by copying the original plan
• Automatically by copying the planned independent requirements of another material, or by copying another planned independent requirements version of the same material.

You must maintain the fiscal year variant in the Forecast requirements section of the material master record if either:

• You copy the planned results from Sales and Operations Planning, and you use a fiscal year variant as the planning period.
• You maintain planned independent requirements with reference to a fiscal year variant.

 

Planned Independent Requirements (PIR)

Planned Independent Requirements are planned production or sales quantities that are based on some sort of forecast procedure (e.g. Material Forecast or S&OP procedure). These numbers are used in MRP to calculate procurement and/or production quantities for a material.

 

Want to acquire industry skills and gain complete knowledge of SAP PP? Enrol in Instructor-Led live SAP PP Training to get Job Ready!

(Planned) Dependent Requirements

Dependent requirements is a demand that is dependent on another material. E.g. components of a bill of material are often planned on the basis of the demand for the material of which it is a part.

Example

You plan to sell 200 bikes in the month of January 2009 based on sales in the same month of 2008. These 200 bikes are a Planned Independent Requirement for 01/2009.

Since every bike is produced using two pedals the 200 bikes you plan to sell in January 2009 result in 400 pedals you need to procure. These 400 pedals is a planned dependent requirement for 01/2009.

On the basis of these numbers, MRP can calculate including current stock levels how many bikes and pedals you actually need to produce/procure.

 

Stock/Requirements List

In the stock/requirements list, the most up-to-date stock and requirements situation is displayed.

The main difference between the MRP list and the stock/requirements list is that each time the stock/requirements list is called up, the system selects the various MRP elements and displays the most up-to-date situation. You thus always see the current availability situation of the material in the stock/requirements list. Changes that are made after the planning date are displayed directly, so the list is therefore dynamic.

Stock/requirements lists are not saved in a fixed state in the system, but are subject to change and only exist in the working memory.

 

Comparison

The screen layout of both lists is basically the same.

The system automatically runs the rescheduling check directly when both lists are created and put forward rescheduling proposals.

The number of exception messages displayed in each list is roughly the same. The only difference lies in the fact that, due to the nature of the list, no exception messages can occur for newly planned MRP elements in the stock/requirements list.

Directly after the planning run, both lists contain the same information. As soon as a change relevant to MRP is made, the system updates the information in the stock/requirements list.

As stock/requirements lists are subject to change, they cannot be set with a processing indicator.

Checkout our Blog on SAP PP Tutorial

 

Structure

Each MRP list is divided into a header and items.

Material data, such as the material number, the plant, and MRP parameters, are recorded in the MRP list header.

The items, on the other hand, contain information on the individual MRP elements (planned orders, purchase orders, reservations, sales orders, and so on). These are grouped by MRP data into individual planning segments. The beginning of each new planning segment is highlighted. The system carries out the net requirements calculation for each segment separately.

 

Planning Segments

The following segments are individually displayed and individually planned:

Net segment: Consists of that part of the list for which the net requirements calculation in planning was carried out on the plant level.

Gross segment: Groups together with the gross requirements and the corresponding procurement proposals for gross requirements planning.

Storage location segment: For every separately planned storage location or for every location, which is not included in MRP.

• Individual customer segment
• Individual project segment
• Segment for planning without final assembly

Displays the requirements that are planned without the final assembly. This means that their procurement is triggered by the incoming sales orders and non-convertible planned sales orders with the order type VP.

• Segment for direct production planning
• Segment for direct procurement planning
• Direct production segment
• Direct procurement segment
• Segment for the provision of material for subcontracting.