Skip to Content

SAP strategy for the digital economy is based on the concept of simplification. The SAP strategy is to accelerate business innovation through radical simplification.

 

This concept was also used on the new SAP S/4HANA, on-premise edition 1511 and several application scenarios available on the ECC were simplified. The idea is to make the S/4 HANA implementation faster and easier, in order to accelerate the return on investment and also make the life of the consultants easier.

 

A complete list of the simplified scenarios is available on SAP Help and it is available on the following link:

 

http://uacp.hana.ondemand.com/http.svc/rc/PRODUCTION/pdfa4322f56824ae221e10000000a4450e5/1511%20000/en-US/SIMPL_OP1511.p…

 

Between those scenarios, some are specific to Material Requirements Planning and changes were made on functionalities that were part of the standard system for a long time.

 

Some of the most relevant changes are the following:

 

1 – Simplified sourcing

 

The source determination carried out by MRP was completely redesigned for internal and external procurement.

For internal procurement, a BOM selection method is no longer available for selection. Now, the BOM is always selected according to the production version, therefore, it is mandatory to have a production version.

For external procurement, the source list is no longer relevant to MRP and it is enough to have a valid info record, in order to have a vendor selected for a planned order or purchase requisition by MRP.

With these changes, the source determination on MRP is similar to the source determination on APO and, according to SAP, unified source of supply model is the basis for future innovations in sourcing.

 

2 – Storage location planning

The default option to plan a storage location separately is the storage location MRP area. It means that the option to define on the material master that a storage location will be planned separately or excluded from MRP is no longer available.

With the storage location MRP area, there is a separate planning file entry, which means that the MRP area is planned independently. This is a good thing from a performance point of view, since we don’t need to plan the entire material just because a change happened on the storage location planned separately.

Besides that, the storage location planned separately runs a very simple reorder point MRP type, while the MRP are offers almost the same settings available on the material master.

 

3 – Subcontracting

Planning of components provided to the vendor must be now carried out with MRP areas. A separate stock segment for the vendor is not available anymore and the main reason is the performance. It is also now easier to use subcontracting MRP areas, since we simply need to create them on customizing and they will be available for all the materials.

 

4 – Planning file

The old planning file entry tables were replaced by the new table PPH_DBVM, with simplified update logic, consistency and for update performance.

There is also a new report and transactions to create and check the consistency of the planning file.

 

 

Header 1 Header 2
/wp-content/uploads/2016/03/9781493213993_267_2d_910979.png

If you want to learn more about MRP Live, Fiori Apps and MRP on S/4 HANA, my new e-book will be published in April.

See more details on Running MRP on SAP HANA (SAP PRESS)        – by    SAP PRESS

To report this post you need to login first.

11 Comments

You must be Logged on to comment or reply to a post.

      1. Siddheshwar Rajguru

        Hello,

        I think PPH_MRP_START is the program for MRP live , I could not find PPH_MRP_DISPATCHER , so this is having interface compatibility with third party tool Autosys..

        Thanks

        Sid

        (0) 
        1. Caetano Almeida Post author

          Hello

          You are right, PPH_MRP_DISPATCHER is the correct report for the ERP releases (EHP7, EHP8). For S/4 HANA you should use PPH_MRP_START.

          Regards
          Caetano

          (0) 
  1. G S

    Can we run LTP on S/4 HANA like MD01N ? Is there an equivalent “simplified” LTP tcode ?

    (0) 
  2. G S

    I see the MD01N tcode does not generate MRP lists…..if thats true then how will a planner review the exception messages ? Will MD04 become the replacement ? if yes then there are some exception message which dont show in MD04. How will MRP live in the current state address that ?

    (0) 

Leave a Reply