Material Requirements Planning (MRP) Process in SAP Business One
Material Requirements Planning (MRP) Process in SAP Business One
Material Requirements Planning (MRP) Process in SAP Business One
Business One
At the end of this document, you will be able to:
We begin by introducing the concepts behind MRP in better to understand the process
and its recommendations.
We discuss the definitions and planning data required to run the MRP wizard including
the Forecast.
Then we explain the steps of the MRP wizard
Finally we examine the MRP results and see how to automatically generate production
or purchasing documents from the recommendations.
I/ Business Scenario
OEC Computers sells office equipment and supplies.
Some of the items they sell are assembled and manufactured at OEC Computers’ labs.
The procurement manager, would like to be able to plan ahead for sales demand and
item availability
II/ MRP Concepts
In the example shown, you can see an illustration of the recommendations given by
MRP.
At the top, we see the situation before MRP is run.
The initial stock quantity is represented in gold. Initially there were 20 pieces in
stock.
A purchase order exists for 30 pieces. We expect those receipts shortly in the
future based on the lead times for the items.
We have requirements for 40 pieces from existing sales orders.
We have a sales forecast for 50 additional pieces in the near future and later on
we expect demand for additional 30 pieces.
When we run MRP, we receive recommendations for three purchase orders to fulfill the
requirements.
MRP considered the initial stock, planned supply and existing and forecasted demand.
III/ MRP Components
In order to understand the MRP logic better, let’s look in more detail at the 3 types of
sources used in the MRP run: Demand, Stock on Hand and Supply.
Demand tells us how much item quantity will be needed in the future. Demand is
derived from the following sources:
To meet the demands, the wizard looks at the stock on hand (item quantities currently
in the warehouse) and expected supply.
The expected supply of item quantity is derived from the following sources:
Before running MRP, you need to define planning data. The main planning data consists
of definitions in the item master data records. In addition, there is also an option to
define a forecast for anticipated demand of the items.
Once the planning data is set up, you can run the MRP wizard on demand.
The results of the MRP run are recommendations for creating documents to produce,
purchase or transfer the needed items.
The final step in the MRP process is to use the recommendations to create the needed
supply documents (such as production orders, inventory transfer requests or purchase
orders) to meet the demand. These documents can be automatically generated via the
Order Recommendation window.
In this next section, we will go through each MRP process step in detail. For each step
you will see how MRP is integrated with the procurement and production processes.
Here we see a list of suggested actions to perform before running the MRP wizard
None of these definitions are mandatory and you may decide that some are not relevant
for you, but you should at least be familiar with them before running the MRP wizard for
the first time.
No particular order of definition is required.
We will start by learning about the forecast functionality, and the way to define it.
Then we will go over the planning data and inventory level definitions in the item master
data, relevant for the MRP run.
And finally, we will see how the holidays and weekend definitions can affect the MRP
results.
1/ Defining Planning Data: Forecast
You can create forecasts to plan purchasing, production or transfers in advance, even
before you receive other actual requirements like sales orders.
In OEC computers, sales orders are often received at short notice. Some of the items
they sell have long lead times. If OEC Computers relied on only sales orders to drive
their production and purchasing, they would not be able to meet demand because on
the customers’ required dates.
That is why they use forecasts. By using a forecast, they can purchase or produce items
based on predictions of when the items will be needed. When the actual sales orders
arrive, they are able to supply the goods even at short notice.
In the image we see an illustration of a weekly forecast for the Hard Disk item in OEC
Computers. To make sure there are sufficient hard disks on hand to meet expected
orders, Michelle prepares a weekly forecast for the item. She bases her forecast on last
years sales figures and adds a certain margin for the current year. Then, when she runs
MRP, the recommended quantities already include the forecasted demand.
At OEC, they have found that some items sell better in different regions. To handle the
differences, they create and maintain forecasts for items per warehouse.
To avoid duplication of sales order demand and forecast demand, you can define in the
general settings that forecasts are consumed by actual sales orders.
You can learn about more about forecasts and how they are consumed in the topics
MRP – Intelligent Forecast and MRP – Forecast Consumption.
2/ Create a Forecast
One way to simplify the process of creating a forecast is to use the option to
automatically generate forecasts.
The first step is to choose the Generate Forecast button in the Forecasts window to
open the Generate Forecast – Setup window. You have the option to choose a basic
forecast or an intelligent forecast. These choices are discussed in more detail in later
course topics. In this example, we will choose the basic forecast.
The second step is to define the criteria for adding items to the forecast. You can choose
to add all items related to a certain default warehouse, a preferred vendor, an item
group or specific properties.
You also have the option to use advanced settings to project forecast quantities based
on historic sales information.
The historical data can derive from either sales orders or deliveries and invoices.
You can choose between a simple average and a periodic average:
o In the Simple Average option, the system sums up all quantities of the
item in the historic period and then divides the entire quantity evenly for
each period in the forecast.
o The periodic average can be daily, weekly or monthly, depending on the
periodic view of the forecast. In the periodic average, no actual average
calculation is made. The system just updates the quantity sold (or ordered)
in the corresponded period of the historic period.
The historical period is defined by entering a History Start Date. The system
automatically enters an end date. This end date creates the same time range
defined in the main Forecasts window.
On the Planning Data tab of the Item Master Data window, you can set definitions
relevant for the MRP run.
For each item you can define whether or not it is included in the MRP run by choosing
MRP or None in the Planning Method field.
In the Procurement Method field you can define whether you purchase the item or
produce it.
This setting affects the default for the type of recommendation you receive from
the MRP run.
You can choose between the options Buy to receive recommendations for
purchasing the item and Make to receive recommendations for Production
Orders (taking demand and supply data for all BOM components into account).
Note in both cases the recommendation can be to transfer the item from another
warehouse. We will talk about the MRP recommendations later on in this training.
Besides the Planning Method and Procurement Method there is additional data that can
be used for planning.
The Order Interval field specifies the frequency for order recommendations. You can
define the intervals you need. You can define many intervals and choose the relevant
interval for each item when needed. The Order Interval definition can be useful when an
agreement exists with a vendor, for example, to order once a week – for example on
Mondays only. MRP automatically groups recommended orders into interval groups for
your convenience.
The Order Multiple specifies the lot size to use in an MRP run. For example, if the value
is 50, MRP will recommend order the item in multiples of 50. So if you need 80 items
and the value is 50, the system will recommend ordering 100 items.
The Minimum Order Quantity field allows you to specify a minimum lot size.
The Order Multiple and Minimum Order Quantity definitions can also be a
representation of a supply agreement with the vendor.
The Lead Time field is used to calculate the duration of time to produce the item or
receive the item when buying it.
The last field in the list is the Tolerance Days. An expected supply may arrive within a
few days after the actual demand date and sometimes it would be ok to delay delivery.
This functionality minimizes recommendations and satisfies demand with the expected
supply due within the tolerance period. In the Tolerance Days field, indicate how many
days you are willing to tolerate.
If you are using the advanced availability to promise functionality (ATP), you will also
have the option to specify a checking rule. For more information on advanced ATP, see
the course topic on automating the sales process.
In addition to entering the planning data directly in each item master data record, you
can also define the planning data at the item group level. This definition is copied
automatically to the item master data as a default.
Let’s look at a basic scenario involving two items that OEC Computers resells:
Both items were defined as Buy items because they are not manufactured in-house by
OEC Computers.
The first is a keyboard and the second is a hard disk.
Look at the upper table. You can see there are different demand quantities for the items
for weeks 13 and 14.
The keyboard demand is 400 units for week 13, but since the order is due in the
beginning of the week and the lead time of the Keyboard is 3 days, the
recommendation appears in week 12.
The demand for the 300 units appear in week 13 for the same reason.
Now let us look at the hard disk item.
The demand for week 13 is 80 units but since the Order Multiple definition of the item is
50, the recommendation quantity is 100.
Note that the recommendation appears in week 11 since the lead time for this item is 10
days.
The demand for week 14 rounds up to 150 and appears two weeks before the due week.
We will continue to explore the planning data effect on the MRP results later on in this
training, using the same items and planning data definitions.
In the item master data we can define three types of desired inventory level of an item:
Required, Minimum and Maximum levels.
According to the values set in the minimum or maximum fields, the system can
generate automatic warnings or restrictions when issuing sales or purchasing
documents.
When managing required quantity, the system can recommend to purchase the
quantity needed to reach the required level of inventory.
Note the required quantity is managed in purchasing units of measure and the
minimum and maximum levels are managed in inventory units.
Just like sales orders and forecasts, predefined inventory levels can also generate a
demand for quantity in the MRP run.
When running the wizard the user can choose whether or not to consider one of the
defined inventory levels.
Note, the image displayed here reflects the definitions needed when managing
inventory by the company level.
When the Manage Inventory by Warehouse box is checked, the definition of the
quantities is done at the warehouse level.
After you have entered the MRP definitions, you are ready to run the MRP wizard.
The wizard is a 6-step process and the final step presents recommendations derived
from the parameters defined in the former steps.
In the next slides we will look into each step:
Throughout this process we will use the basic scenario and build a wizard that will
provide us recommendations.
1/ MRP Wizard - Step 1: Scenario Selection
An MRP scenario is a set of parameters defined throughout the wizard steps. The
scenario contains all the details for how to determine the results of the MRP run.
You can define several MRP scenarios for each company, but only one scenario can be
used for each MRP run.
You can create a new scenario or choose a saved one from a former MRP run.
Let us create a scenario for the first quarter of the year.
2/ MRP Wizard - Step 2: Scenario Details
a) Planning Horizon
In step 2 of the Wizard we also define lead time and display definitions.
Look at the definitions affecting lead time calculation.
You can decide whether to consider holidays or not. Michelle chooses to consider
holidays for both production and purchase items since no production takes place
at OEC during holidays and most deliveries from suppliers are also delayed due
to local holidays.
Another important definition is the Ignore Cumulative Lead Time check box. This
definition is relevant for BOM items. If this checkbox is selected then the lead
time will be taken from the lead time defined in the item master data. Otherwise,
the lead time will be the sum of the lead times of all the recommended BOM
components.
In step 4 of the wizard, you can decide whether to run the wizard by the company level
or the warehouse level and choose which warehouses participate in the MRP run.
The first option is to consolidate inventory quantities, demand and supply by the
company level. This means all requirements and recommendations are calculated
for the default warehouse. This also means no inventory transfer request
recommendations will be given.
The second option is to consider each warehouse separately. With this option,
each warehouse has its own existing inventory and its own demand and supply.
This also means that if there is a demand for quantity that exists in another
warehouse, the system can recommend an inventory transfer request from the
warehouse holding the desired quantity to the warehouse with the demand.
Michelle chooses to run MRP at the warehouse level.
Look at the Include Data Source table. The definitions made here are relevant for both
Company and Warehouse preference.
You can decide for each warehouse if its initial quantities and sources of supply or
demand are considered. For example if you have a sales order containing multiple rows
from different warehouse, only the rows involving warehouses that are marked with
Include Demand, will be considered as demand in the MRP calculation.
The warehouse list is ordered by location. In the image we see an expanded view of all
the warehouses that exist in the company.
Note, even when running the MRP by Company, if a warehouse is not included as
demand and the inventory level of the item is managed by warehouse, then the MRP
calculation will not consider the non-included warehouses.
In step 5 you decide on the type of sources to consider in the MRP run and the type of
recommendations to be given by the MRP Wizard.
Check the box of the sources you wish to include. You can also restrict specific
documents. For example if you want to exclude a certain sales order because you think
it may be canceled, in addition to checking the Sales Orders box, you should also check
the Restrict Sales Orders box and choose the sales orders to include.
In addition to document sources, there are two more types of demand sources:
The first is the Inventory Level. Here you choose the level of inventory you wish to
fulfill. In the Inventory Level drop down list you can find the same inventory levels
that can be managed for the item in the Inventory tab of the Item Master Data. In
OEC Computers many items are managed by a predefined Required level.
The second field is the Forecast. Here we can choose pre-defined forecasts to
consider as additional demand in the MRP run. We will not use a forecast in the
basic scenario.
b) Recommendations
c) Time Range
Another important definition in step 5 of the wizard is the Time Range definition.
When running the MRP, you can decide whether to include historical data, prior to the
MRP start date, in the MRP calculation.
If we choose the option Within Planning Horizon then MRP calculations does not
consider data prior to the wizard start date. If the start date is earlier than today,
consolidated data between the start date and today will appear in the Past Due Data
column. The first period column will display data starting from today.
If you do choose to include historical data, all documents before the start date are
considered in MRP calculations. All data and recommendations are summed together
into the Historic Data column. Note that the Historic Data column appears only when
choosing to include the historical data option.
X/ MRP Reports
The first is the Initial Inventory. The Initial Inventory derives from the Final
Inventory of the former period. The initial inventory of the first column represents
the current quantity of the item in the company, according to the warehouses
included in the wizard.
The Supply quantity is the expected positive inventory receipts from the following
selected documents for each period: Purchase Order, Production Order (for the
parent item), Purchase Blanket Agreement (according to the planned frequency)
and Inventory Transfer Request (for the receiving warehouse). Note the Supply
row also includes the MRP recommendations for each period.
The Demand quantity is the expected inventory releases from the following
selected documents for each period: Sales Order, Sales Blanket Agreement
(according to the planned frequency) , Reserve Invoice, Recurring Order
Transactions (according to their planned due date), non consumed Forecast,
Production Order (for the lower level items), defined inventory levels and
Inventory Transfer Request (for the source warehouse).
The last row is the Final Inventory which sums the Initial Inventory plus the Supply
quantity minus the Demand quantity.
1/ MRP Report Timeline
This diagram shows the timeline of the MRP report grid from the Historic Data to the
Future Data. Using this diagram we will also summarize what we have learned so far
about the different MRP report periods and also talk about the Future Data column.
We already learned that the Historic Data column only appears in the MRP report if we
choose the option Include Historical Data in the Time Range definition in step 5 of the
wizard. This column holds all historic data up to the start date of the planning horizon,
consolidated together.
If the start date of the planning horizon is earlier than today then all the data that
relates to the period between the start date and today is consolidated in the Past Due
Data column. If the start date is today then no data will be presented in this column.
We also saw that the data related to the period between today and the planning
horizon end date is split up and presented in multiple columns according to the View
Data in Periods Of definition made in step 2 of the wizard.
The Future Data column displays consolidated data related to the lead time period
which follows the planning horizon end date. In our case, since the lead time of the hard
disk item is set to 10 days, the Future Data column will display all demand with due
dates set within the next 10 days following the MRP wizard end date. Respectively, in
the Future Data column, we will see recommendations (in the supply and
recommendation rows) that satisfy this demand.
SAP Business One uses different colors to visualize the MRP results.
The lead time for an item is displayed in dark grey cells and means that the
recommended order is unable to meet demands of orders with due date within the lead
time. The lead time is calculated from today. In our example the lead time is 10 days and
today March 10th (Monday of week 11). This means the lead time ends on March 20th,
in week 12. Therefore weeks 11 and 12 are colored in dark grey.
The Past Due Data column always appears in dark grey since it represents demand with
due date earlier than today. Using the same logic, and assuming the lead time of the
item is greater than zero, then the first period column will be in dark grey as well, in our
example it is week 11.
The rest of the period columns are displayed in pale grey.
The only row colored in white is the item row. Item row cells are displayed in white if the
total of the supply and initial quantity exceeds the demand.
Recommendations that cannot be fulfilled or not fulfilled on time (commonly due to the
lead time defined), appear in red and so is the supply of that recommendation.
Note that in some cases negative quantities may appear in the initial and final inventory
rows. This negative quantity also appears in red.
Negative quantity appears when a demand is not fulfilled or not fulfilled on time. One
reason can be a delay of supply due to tolerance days definition.
Another reason can be when we choose to view the report without previewing the MRP
results. Let us examine this option in the next slide.
There are two ways to view the MRP Report: with the MRP recommendations included
and without recommendations. The Preview MRP Run Results checkbox is unchecked in
this example, meaning that the numbers we see in the Supply row do not include
recommendations from this MRP run.
Look at the Past Due Data column. We started with initial quantity of 560 units and in
the demand cell we see a total of 500 units.
Let us look at week 11 column. We already learned that the final inventory value
becomes the initial inventory of the following period. Therefore, the initial inventory of
Week 11 is 60 units which was the final inventory of the Past Due Data column.
When we look at the final inventory of week 12, we see a total of -20 units that appears
in red. This is the result of the following calculation:
The source of the demand and supply. The source can be:
o The number of the document that created the demand or supply,
o The name of the forecast that created the demand,
o If the item is a BOM then the top level item number of the lower level item
requirement appears
o And if the item has a pre-defined inventory level requirement then the
item number appears.
Note that an empty source column in a supply pegging information means this is
an MRP recommendation.
In the image we see the sales order numbers in the source column.
In the Pegging Information window we can also find:
o The Type column that contains the name of the source document type,
o The Due Date, Quantity and Warehouse of the source
o And a Remarks field. In this column we can find automatic remarks that
indicates, according to the type of the pegging information if it is a
recommendation, supply from recommendation, a regular supply source
or a demand.
First, we minimize the number of generated documents and thus reduce logistics
and maintenance costs.
Second, we may also achieve greater quantity related discounts
XIV/ Summary
Here are some key points to take away from this course: