PP- RUN MPR PROCESS

- COLLECTIVE MRP ( PLANT / PLANNER GROUP / MRP GROUP)

- INDIVIDUAL ( Multilevel / Onelevel)
- MRP MASTER DATA : Lot size / Delivery Time
- Firm Purchase orders

Details

Description Test
Date / time: 15.03.2019
Location Tondela (Portugal) ; Soria (Spain)
Attachments

Topics PP- MD01 / MD03 / MD02

Follow-up Meeting
Date / time:
Location

Responsable

Name Function Abbreviation

Christof Jaschkewitz HUF Velbert CJ
Guillermo Lacasa Insa Ingeniering Consultant GLI

Meeting minutes SAP S/4 HANA Rollout 1 / 10

PP-MRP
* I= Information, D = Decision, A= Action

1. INTRODUCTION TO MRP PROCESS

The MRP is based on several informations as input as control information:

- Independent requirements
- The actual demand coming via EDI ( Sales Schedule agreement) and sales documents.
- The actual stock level
The control informations are put in:
Material master in the view MRP1 and MRP2.

After process MRP we should have to analyse MRP results and exceptions messages ( see MD06
document)

MRP process will automatically create:

- Planned orders ( in house production )
- Purchase requisitions or vendor schedule lines ( external procurment).

Launching MRP

1) Automatic
MRP process can be carry out as automatic process (JOB) scheduled as certain date or period.
- We could carry out whole plant parts
- We can create variants of the process in order to select by grouping ( BOM levels, MRP
controller...)
2) Manual
Manual execution transations , explained bellow: MD01, MD02, MD03
- All parts plant or grouping parts (exit fields)
- Single item single level BOM
- Single item multilevel BOM explosion

2. MRP TRANSTIONS

2.1 MRP Run transation: TOTAL MRP PLANT

Direct: /nMD01
Full : Logistics / Materials Management / Material Requirements Planning
(MRP) / MRP / Planning / Total Planning/ online.

This transacction is part of the taskchain process ( first MRP or MPS) and the second one
( Purchase process)

Parameters control

The control parameters to process MRP

SAP S/4 HANA Rollout 2 / 10

Optional parameters:

In order to get result screen after the MRP process:

Optional parameters :

Select materials by MRP controler or MRP group ( material master data) in order to the MRP
process the materials which below
- Put User exit key: MRP
- Put user parameters : code of MRP controler in the master data

SAP S/4 HANA Rollout 3 / 10

 - Put user parameters : code of MRP Group in the master data
Z001 : Master father (MPS process)
Z002: SubProduction
Z003: Purchase parts

The system will be carry out MRP for those materials which cointain this MRP in the master data
MRP1 view.

2.1 MRP Single item – Multi level

Direct: /nMD02
Full : Logistics / Materials Management / Material Requirements Planning
(MRP) / MRP / Total Planning / Multilevel single item

Only the MRP affects to this material and the rest of partnumbers in their BOM explosion
levels

SAP S/4 HANA Rollout 4 / 10

Optional parameters:

Also Plan Unchanged components: Affects not only undergone parts

Display results prior to saving: Show MRP list screen before save.

Display Material list : display ranking list of material processed.

SAP S/4 HANA Rollout 5 / 10

2.3 MRP Single level – Single item

Direct: /nMD03
Full : Logistics / Materials Management / Material Requirements Planning
(MRP) / MRP / Total Planning / Single level single item

Only the MRP affects to this material, no explosion BOM.

3. MASTER DATA

3.1 MRP Master data : Lot size

The most important lote size are the Periodics : PB/TB/WB/W1/W2 where the system groups several
requirements within a time interval ( daily / weekly / Monthly)

TB
Daily lote size
Requirements Date from PP order/Sales order = Delivery date for Purchasing

PB
Period lot size = posting period

SAP S/4 HANA Rollout 6 / 10

The system groups several requirements within a time interval together to form a lot
In PB periods of flexible length equal to posting periods.

PK
Period lot size base in planning calender

MB
Monthly lote size
The system groups several requirements within Month. Lot Delivery date for Purchasing at the
begining of the the month

W2

Weekly lote size

Delivery date for Purchasing at the end of the week

W1
Weekly lote size
Delivery date for Purchasing at the begining of the week

WB
Weekly lote size
Requirements Date from PP order/ Sales order = Delivery date for Purchasing

H1
Replen to max stck after covering reqs
Replenish to maximum stock level

2W
2 Weeks lote size
Delivery date for Purchasing at the begining of the first week

DY Consumption-Based Planning
Dynamic lot size creation in the Lot size field and the Lot size independent costs and storage costs
indicator. Starting from the shortage date, successive requirements are grouped together to form lots
until additional storage costs become greater than lot size independent costs

EX Lot-for-lot order quantity

Exact lot size base on requirements ( one per one)

FS Dynamic lot size

 Dynamic lot size creation in the Lot size field and the Lot size independent costs and storage costs
indicator. Starting from the shortage date, successive requirements are grouped together to form lots
until additional storage costs become greater than lot size independent costs

FX Fixed order quantity

Fix quantity lot size from master data MRP1 (fixed lot size)

GR Groff reorder procedure

The Groff reorder procedure is based on the fact that additional storage costs are equal to the saving
in lot size independent costs according to the classical lot sizing formula for the minimum costs.
Additional storage costs resulting from an increase in the lot size are, therefore, compared with the
resulting savings in lot size independent costs

3.2 MRP Master data : Delivery time

SAP S/4 HANA Rollout 7 / 10

Time that vendor needs to be procured their goods. All the purchase parts quantities to the vendor
have to be sent before that period due to it causes issues about the availability.
It does not take any impact in the scheduling of the Purchase requesition or Schedule but if there is no
margin in between the last deal and the MRP date , the Schedule line will be scheduled forward in the
future

Result:

3.3 Firming planned orders and schedule lines

3.3.1 Firming planned orders manually(/nMD04)

When a planned order it’s changed manually the system automatically assumed it as a firm and later
the MRP process will never change it.
Note: Production orders always are fix under the point of view of the MRP process.

Proceed: Doble click inside planned order in MD04

click modify
After planned order modification (date/ qauntity ) you will see the option activated

SAP S/4 HANA Rollout 8 / 10

3.3.2 Firming planned orders semi-automatically (/nMD04)

In order to fix several planned order in a period, select:

3.3.3 Firming schedule lines (/nME32L)

We can get a firm schedule (*) lines through the trade-off zone during the labour days you put in
there. But you can not avoid to get new Schedule lines in this period. To solve this one: binding field.

SAP S/4 HANA Rollout 9 / 10

This is the "semi-firm" zone, giving the vendor the go-ahead to procure necessary input materials to
manufacture the item ordered. Schedule lines falling within this time zone are thus less binding that
those falling within the firm zone.

In the "Firm Zone" field, enter the number of calendar days (calculated from the SA release creation
date) after which the firm zone ends and the offset zone begins.

In this example vendor schedule lines are fixed during 20 labour days from the beginning.

SAP S/4 HANA Rollout 10 / 10