mrp config
mrp config
a) Number ranges
The number range ID’s are maintained for the following objects:
the Planned orders
the reservations,
the dependent requirements,
the simulative dependent requirements,
the purchase requisitions,
the MRP Lists,
In this section only the number range ID’s are maintained. While the actual number
range is configured, for the number range ID, using a transaction code OMI2 (for the
above mentioned objects created in the planning run). One can also use the transaction
code OMI3 for the objects created manually in the front end.
Every number range interval, created using OMI2 and OM13, has an ID, which can be
allocated to the objects at plant level, i.e., every plant can have a different number
range for the objects mentioned above.
b) Availability Check rule for Backorder Processing
As per standard SAP, the Availability checking rule for the backorder processing is “PP”,
though you can have your own availability check rules created or configured.
Every Availability checks rule (availability checking scope defined) has a set of receipts
(Purchase orders, Production orders) and issues (Sales orders, dependent
requirements, reservations, planned independent requirements etc) which are to be
considered or not to be considered during the SAP availability checks.
To have the checking rule work along with the configuration, you should have the
Availability checking groups maintained in the material master. The Checking groups
are configured to be associated with the checking rules (checking scopes).
The availability checking rule (checking rule scope) has to be maintained, for a given
SAP functionality and it has to be assigned to the availability checking group maintained
in the material master. The SAP functionalities that use availability checks to check the
availability of the header materials as well as components at the plant at the time of
sales order creation, the availability checks of the header material at the time of sales
order delivery, the availability checks for components in production – thus reporting the
missing parts list, the backorder processing etc.
c) Reporting
This configuration is used for the following purposes.
• To configure the objects, which are to be considered in the calculation of the
“receipts days supply” like the production orders/process orders, firmed planned
orders, purchase orders, assigned planned orders, firmed purchase requisitions, QM
Inspection lots, reservations, safety stocks
• To configure the reporting of “periods totals” in terms of a defined period (day,
week, month, periods as per planning calendar) of in Stock requirement list, MRP
list, simulative MPR or interactive MRP
d) MRP Controllers
This is a mandatory configuration. Here you can configure the list of MRP controllers for
the plant. A MRP Controller is a person or a group of people, which is responsible for
planning a material or a given list of materials.
You have to assign the MRP controller to the Material Master MRP 1 View, so as to
delegate the responsibility of the planning and evaluation of planning for that material.
e) Floats
Floats are buffers in the total lead time, that are provided in production/process order or
in the planned orders created manually or during an MRP run. The schedule margin key
is used in the Material Master MRP 2 View. It is used in MRP as well as in production
order.
The floats are defined using the scheduling margin key.
Opening period: Number of working days between the date that the order is created and
the planned start date. This time is available for the MRP controller to convert a planned
order into a purchase requisition or a production order.
Float after production: Number of working days between the scheduled finish date and
the order finish date; used as a float in production scheduling.
Float before production: Number of working days between the order start date and the
scheduled start date; used as a float in production.
Scheduling release period: Number of workdays between the planned start date and the date for
releasing the order. If the order release indicator is set, the production order is released by a background
program that takes all dates into account.
Plant Plant Margin Opening Fl. Before Fl. After Release
Name Key Period (In Production (In Production (In Period (In
Days) Days) Days) Days)
0001 0001 001 5 2 2 5
0001 0001 002 5 3 3 5
0001 0001 002 5 4 4 5
f) Special Procurement
The special procurement function helps you to configure and assign special
procurement to the materials which can be used during an MRP run while creating the
procurement proposal.
The special procurement functions are withdrawal from alternate plant, production in
alternate plant, subcontracting, direct production, phantom item planning,
https://sites.google.com/site/sapswords/home/learn-sap-pp/sap-material-master/sap-
mrp2-view
Example: For Stock Transfer from Plant C001 to Plant C002
Create the Special procurement key (Key number = 12 as an example) in the plant
C002 with the procurement type as “F” and special procurement as “U” (Stock transfer)
and the special procurement plant as “C001”. Normally when creating the special
procurement key use Z, Y or X to the Key number, so instead of having Key number as
12, we could have something like Z2 or YA etc.
a) MRP Procedures
MRP Procedures defines the type of MRP to be used – Reorder point planning
methods, Material requirement planning or demand based planning methods, Forecast
based planning methods, Time phased planning methods, MPS and the no planning
procedures to mark a material with a MRP types that does not plan a material at all.
b) Firming Type
In the category of MRP procedure called – MRP or demand based planning method and
MPS, SAP offers 8 different MRP types with Firming namely P1, P2, P3, P4 and M0,
M1, M2, M3, M4.
When working with the planning time fence, one needs to set the firming methods & the scheduling
methods of the procurement proposals within the planning time fence.
Firming type 0 1 2 3 4
MRP Types M0 P1 P2 P3 P4
M1 M2 M3 M4
Firming Methods for Procurement Proposals in the Planning time fence
No Firming of Procurement Proposals within X
the planning time fence
Automatic Firming of Procurement X X
Proposals within the planning time fence
Manual Firming of Procurement within the X X
planning time fence (No Automatic Firming
of the procurement proposals )
Treatment with New Order Proposals in the Planning time Fence
Automatic Creation of New Procurement X X
Proposals to cover the shortages within the
planning time fence. But the dates of these
new Procurement Proposals are pushed
outside the planning time fence
No New Procurement Proposals created to X X
Cover the material shortages within the
planning time fence
c) Include External Requirements
The inclusion of external requirements in net requirement calculations is available to be
set, when you are working with reorder point planning based MRP types. Actually there
are 2 options in this field, i.e., include external requirements in the total planning horizon
or restrict the inclusion of the external requirements only within the replenishment lead
time.
For example:
If the external requirements are set to be considered in the total horizon (of 7 weeks)
then in the today’s MRP run, the Customer demand will be considered as it falls in the
planning horizon and it will reduce the warehouse stock proportionately which would
trigger the reorder point planning procurement once the stock falls below the reorder
point.
If the external requirements are set to be considered in the Replenishment lead time,
let’s say the Replenishment lead time is 1 week, then in that case, only in a MRP run
triggered one week before the start date of the external demand, this customer demand
will be considered, thus triggering reduction in warehouse stocks.
Fig MRP - Config 11
SAP also offers an option to select the additional external requirements that should also
be included in the net requirement planning calculations like the - components supplied
to the vendor in a subcontracting case, reservations set for the components in a
production order, reservations of components in plant maintenance orders,
requirements to satisfy the Stock transfer order to another plant, stock transfer
requisitions created for Stock transfer orders, requirements raised because of stock
transfer delivery schedules.
c) Forecasting for MRP
Forecasting MRP Types have a “forecasting indicator” as obligatory, unlike other MRP
types which normally have the forecasting indicator set to optional.
Also the historical data is updated in the material master as total consumption (planned
consumption plus unplanned consumption) or unplanned consumption. When the
consumption is planned as per the MRP reservations, planned consumption is updated
and when the consumption is not planned as per the reservation or is greater than the
reservation quantities, then unplanned consumption is updated.
In MRP type configuration, you have an option of choosing the type of historical
consumption of a material to be used for planning whether total consumption (planned +
unplanned consumption) or unplanned consumption.
After choosing the historical date type, you should configure, the type of forecast
requirements to be considered in MRP planning run, whether total consumption
(planned + unplanned consumption) or unplanned consumption.
The reduction method for forecast requirements is also configurable. The default is
reduction by consumption.
d) Planning method
The MRP type offers you to plan the materials in an external system, like the MRP Type
X0. The indicator called the planning method allows you to choose external planning so
as to plan materials in the external system.
e) Automatic Calculations
You can have the safety stock and the reorder point calculated automatically by the
system, when you are using the automatic reorder point planning methods. In the
automatic calculations the system uses the forecast data.
Configuring SAP MRP Scope of Planning for the Total Planning Run
Configuring SAP MRP Scope of Planning for the Total Planning Run
SAP provides an option to plan multiple plants together or multiple MRP areas in one
planning run in a sequence. Transaction code OM0E can be used for configuration or
the logical SAP path – SAP Customizing Implementation Guide > Production > MRP >
Planning > Define Scope of Planning for Total Planning, can be used to configure.
Step 1 – Define the Name of the Scope of planning run
Step 2 – Define the plants or MRP areas to be included in the planning run arranged in
a sequence. The sequence is defined by the first field called
Configuring SAP MRP Planning time fence and Roll Forward Period
Configuring SAP MRP Planning time fence and Roll Forward Period
The transaction path to configure the planning time fence and roll forward period is:
SAP Customizing Implementation Guide > Production > Material Requirements
Planning > Planning > MRP Areas > MRP Calculation > Define Planning Time Fence
and Roll Forward Period
Planning Time Fence:
The planning time fence is the number of work days, within which you can protect the
master plan (or in other words the procurement proposals of a master plan) from being
disturbed or changed from any automatic changes (of an MRP Run). The procurement
proposals are firmed so as to protect them from any changes. The firming of the
procurement proposals (planned orders, purchase requisitions, delivery schedules) in
the planning time fence prevents the proposals in the time fence from being adopted in
the next planning run.
In other words, in the planning time fence, the system does not create or delete any
procurement proposals nor does it changes the existing proposals.
The system calculates the time fence from today’s date plus the “number of days mentioned as planning
time fence” in the material master or in the MRP configuration (where you can define the planning time
fence for plant or for a given MRP group). It is needless to say that any new requirements are not
included in this time period nor the existing requirements are changed. MRP carries its usual planning
outside this fence without interrupting this fenced period.
Configure Planning Time fence and Roll Forward Period
Plant MRP Group Planning Time fence Roll forward Period
0001 0001 14 3-
0001 0002 14 2-
It is logical that any procurement proposal lying outside this fence would start moving in
to the fence one by one; when the fence moves ahead on the time scale. When they
move in to this fence, they are automatically firmed for protection.
Firming for automatically created procurement proposals:
The automatically created procurement proposals in the MRP Run are not firmed by the
system, so that they are available for adjusting dates and quantities in the next planning
run, in cases where there is change in BOM or task list.
You can though manually firm the planned orders individually or collectively using
transaction code MD19
Note - Automatically created planned orders in the planning time fence are only remain
firm till they are in the planning run.
Firming for manually created procurement proposals:
For manually created or changed procurement proposals or even when you reschedule
the planned order in the graphical planning table, the system always marks them with a
firming indicator. Though you can remove or delete this firming indicator.
Firming for component’s planned orders:
In case of a planned order, you can manually firm it by selecting the “firming planned
order Indicator” in the planned order header. And in order to make sure that the BOM
levels below are not exploded or changed in a planning run, you have to set the “firming
components indicator”
See the below Example – Planning time fence is 3 days.
Plannin
g Start
Date
Today – Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8
Day 1
Planning time fence
Planned Planned Planned Planned Planned Planned Planned Planned
Order 1 Order 2 Order 3 Order 4 Order 5 Order 5 Order 6 Order 7
Auto Auto Auto Not-firmed Firmed Not- Not- Not-
Firmed Firmed Firmed firmed firmed firmed
Next
Planning
Start Date
Planning time fence
Planned Planned Planned
Order 4 Order 5 Order 5
Auto Auto Auto
Firmed Firmed Firmed
Roll Forward Period
The Roll Forward Period adds the functionality of automatic deletion of firmed planned
orders, from the master plan. It also creates new proposals to cover any requirements
pending during the MRP run. This period can be defined for number of days in past or
future. The system deletes all the firmed planned orders that lie before the roll forward
period.
Using the roll forward period, you can have the system delete all useless old firmed
planned orders, which otherwise the system would never had deleted, since they were
firmed. This allows for reorganizing the planned orders.
Configuring SAP MRP Areas
Configuring SAP MRP Areas
Long ago, SAP MRP was only at the plant level or at MRP controller level (activated
through a user exit). Then SAP came up with the concept of running MRP at MRP
areas. You can define your own area for which you want to run MRP without disturbing
other areas.
Running MRP for MRP Areas: For running MRP at a MRP area, you would have to
create a scope of planning in MRP configuration, which contain the MRP area or a set
of MRP areas arranged in sequence of planning.
Assigning MRP areas: To have the “MRP Areas” work, you have to activate the MRP
areas and then create them and then assign them to the material master MRP 1 view. If
a MRP area is not assigned to the material, then it will work as per the plant level MRP
area.
Configuring MRP areas
Step 1: Activate MRP Area: Use the transaction path: SAP Customizing Implementation
Guide > Production > Material Requirements Planning > Master Data > MRP Areas >
Activate MRP for MRP Areas
Step 2: Define MRP Areas: Use transaction path: SAP Customizing Implementation
Guide > Production > Material Requirements Planning > Master Data > MRP Areas >
Define MRP Areas
Types of MRP Areas:
Plant MRP Areas: You can create one MRP area for several plants, so that when you
run the MRP for this MRP area, the run is for all the plants configured in the MRP area.
Storage Location MRP Areas: You can create MRP areas for several storage locations
at a plant. You cannot use one storage location in multiple MRP areas.
Subcontractors MRP Areas: You can create MRP areas for several subcontractors for a
plant. You cannot use one subcontractor in multiple MRP areas.
Configuring SAP MRP Dynamic Safety Stock (Range of coverage
Profile)
Configuring SAP MRP Dynamic Safety Stock (Range of coverage Profile)
The Range of coverage profile is configured for the use of Dynamic safety stock for a
given material. The range of coverage configuration contains the parameters for the
calculation of the dynamic safety stock. The dynamic safety stock is a stock calculated
based on the average daily requirements for a period rather than the actual
requirements over the period, therefore it is more statistical value rather than an
absolute value.
Safety stock as we know is used to cover the fluctuations in the requirements, so is the
dynamic safety stock, the only difference being, the safety stock is an absolute value
provided directly for a material whereas the dynamic safety stock is calculated by the
system on the basis of the coverage period and average daily stock calculated internally
by the system.
The Dynamic safety stock is calculated in every planning run.
The transaction path is: SAP Customizing Implementation Guide > Production >
Material Requirements Planning > Planning > MRP Calculations > Define Range of
Coverage Profile (Dynamic Safety Stock)
Range of coverage Configuration:
Fig MRP - Config 12
Configuration for calculation of average daily requirement for a period
Period indicator - Indicate the type of period, whether week or month or according to PP
planning calendar. (Let’s say it is W – Week)
Number of Periods – Number of periods used to calculate the average daily
requirements (Let’s say it is 13 Weeks)
Type of Period length – It defines the number of days in the period, if the period length
is in terms of workdays, then the factory calendar work days are considered, if the
period length is in terms of calendar days then it is considered in terms of Gregorian
calendar, and if it is terms of standard days, then you would have to enter the number of
days in a period in the configuration (Let’s say that the configuration was done with
workdays and the factory calendar has 7 days per week)
Therefore Average daily requirement =
= Requirements in the period (Requirements in 13 Weeks – Lets say 910 Units) /
(Number of Periods – Lets say 13 Weeks) * (Number of days in the period – Lets say 7
days)
= 910 / (13*7)
= 10 Units
Configuration parameters for calculation of Dynamic Safety Stock for the Range
of Coverage
You can define 3 different range of coverage – minimum, maximum, and target range of
coverage, which is used to calculate 3 different stocks using the average daily
requirements (range of coverage multiplied by the period length). The Target range of
coverage defined here would be used to calculate the Dynamic Safety Stock for the
period of the coverage.
The Period of the coverage is specified in the configuration. The coverage’s and the
periods for which they should work for, are defined for 2 separate period lengths and the
3rd period length is for the rest of horizon.
In the example, we have defined the safety stock to cover a period of 7 days (minimum,
target and the maximum range of coverage). The minimum, target and the maximum
stock is calculated for the average daily requirement over the respective coverage
periods.
You can check the minimum, maximum, target stock levels, minimum range of
coverage, maximum range of coverage, target range of coverage in the MRP List or
Stock requirements list’s “Period Total Display” Section.
As per our example, for the first period of 13 weeks, all the 3 stocks levels – minimum,
maximum, and target stock levels would be 70 Units and for the next period of 26 weeks
it will be 70 units as well and for the rest of the horizon it will be 70 units again.
Normally when the available stock falls below the minimum stock level, SAP planning
run, would immediately create planned orders to suffice at least the target stock level.
For example if the minimum stock level is 30 and the maximum is 80 and the target
stock is 50 units, then if the available stocks fall below the 30 units mark, SAP creates a
procurement proposal for 50 units to reach back to the target stock level. Whereas in
the example below, all the 3 stocks types are 70 units, therefore when the stocks fall
below the 70 units, the system will try to raise a procurement proposal to reach back to
70 units.
As per our example in the configuration screen shot –
Dynamic safety stock Dynamic safety Dynamic safety Dynamic safety
formula summarized stocks for the 1st stocks for the 2nd stocks for the rest
as = Average Daily period of 13 weeks period of 26 weeks of the Horizon
Stock * Range of
coverage
Minimum safety 70 Units 70 Units 70 Units
stock
Target safety stock 70 Units 70 Units 70 Units
Maximum safety 70 Units 70 Units 70 Units
stock
Another Example of Dynamic Safety Stock