MRP fields in Material Master

Simplification (Deletion) is done on the following tabs in transaction

1. Lot Size data in MRP1 Tab:

o Unit of Measure Group (MARC-MEGRU)

2. Procurement in MRP2: MRP considers quota arrangements always, henceforth it

is not required to switch it on in the material master.
o Quota arr. usage. (MARC-USEQU)

3. BOM explosion /dependent Requirement tab in MRP4

o Selection Method (MARC-ALTSL)

1
 MRP in HANA

•The creation indicator for purchase requisitions is not available in

MRP Live . MRP always creates purchase requisitions if the material is
procured externally.

• The creation indicator for delivery schedule lines is not available in MRP
Live. MRP Live always creates delivery schedule lines if a valid delivery
schedule exists.

•The classic MRP was writing data into the following tables, which are no
longer populated by MRP live. If your custom code reads data from these
tables, then it should be adjusted to read data from the new data source
when moving from the classic MRP to MRP live.

2
 MRP Table Changes in HANA

Purpose Old Table New data source

Materials MRP was not able to MDKP Table PPH_DBVM with MSGID
plan populated

Various material master attributes MDKP Table MARC

controlling MRP functions such as
lotsizing

MRP list MDTB call function module

MD_MDPSX_READ_API

MRP planning file DBVM, MDVM Table PPH_DBVM

MRP runtime statistics MONI Table PPHMRPLOGITEM

3
 Production version
Production version are mandatory in S/4 HANA for Production
SAP ECC Logic SAP S/4HANA Logic Reason
Material master attribute "Selection Production versions are the only source of supply Simplification of the sourcing logic; symmetry
Method" MARC-ALTSL determines if MRP for in-house production. The material master of different sources of supply; only production
finds a BOM via the BOM's validity period, attribute MARC-ALTSL no longer exists. Sourcing versions are integrated into quota
the BOM's quantity range, or via selects material BOMs only if a suitable arrangements; only production versions make
production version production version exists. Sourcing does not sure BOM and routing fit together
need production versions to find make-to-order
and make-to-project bills of material, but
production versions are required to select
routings also if make-to-order or make-to-project
BOMs are used.

The order type attribute "Routing Production versions are the only source of supply Simplification of the sourcing logic
selection" T399X-ARBPA determines how a for in-house production. A production version
routing is determined during production references a routing. This routing is used to
order creation. The attribute can be create production orders
defined in customizing transaction OPL8.
The production version has a locking MRP only selects production versions that are The new status "Locked for automatic
indicator with values 'Locked' and 'Not neither 'Locked for any usage' nor "Locked for sourcing" corresponds to the "Relevant for
locked'. MRP only selects production automatic sourcing." automatic sourcing" indicator on the
versions that are not locked. purchasing info record (Symmetry); you can use
one production version (maybe with an
artificial routing) as the default for new
planned orders and manually dispatch these
planned orders to proper lines/work centers

4
 MRP AREA

MRP AREA are mandatory in S/4 HANA for MRP RUN .

Master data maintenance has been simplified and offers the following
benefits:

• Reduction of modeling alternatives for similar function of the MRP

planning on storage location level

• Support of a single modeling approach that provides the most

sophisticated features and function for planning on storage location
level

•Separate planning of every subcontractor is possible without having

to create an MRP-area-specific material master record.

5
 MRP AREA

The reason for this change are:

• The MRP logic is simplified. There is only one solution for planning
on storage location level

• The MRP area logic is more advanced than the logic for planning
on storage location level. All MRP types and lot-sizing procedures are
possible on MRP area level

• The system creates planning file entries on plant and MRP area
level. If planning is required on MRP area level, then the system only
plans the affected MRP area. The system does not create planning
file entries on storage location level and it did not do so in SAP ERP.
The SAP ERP MRP had to plan all separately planned storage
locations and the plant level every time inventory or an expected
receipt was changed in a single separately planned storage location.
Planning on MRP area level is more efficient 6
 Quality Management

Several transactions had been available for performing the same task.
To simplify working with the system, redundant transactions have been
removed
 Quality Management

The following table shows which new authorization object replaces with old authorization objects.