https://launchpad.support.sap.

com/#/notes/2227579

ONE Support Launchpad

SAP ONE Support Launchpad is loading, please

wait...
<p style="font-size:26px">SAP ONE Support Launchpad can not be displayed.</p>
<p>Please enable JavaScript in your browser and try again.</p>

This is taking longer than usual. Try reloading the page.

 Information about Outdated Browsers

 Visit SAP Support Portal or SAP.com

Terms of Use Copyright and Trademarks Legal Disclosure Privacy 沪ICP备09046015号

-2
More
More
More
More

SAP Note

Knowledge Base

10

User Bright (S0017135282)

Show ChangesDownload for SNOTEExport as PDFMark as FavoriteShare by EmailOpen in New
WindowDescriptionSoftware ComponentsReferencesLanguages
Description
Component:PP-MRP
Priority:Recommendations / Additional Info
Category:Upgrade information
Release Status:Released for Customer
Corrections:0
Manual Activities:0
Prerequisites:0

Symptom

You are using a SAP ERP system and intend to perform the system conversion to SAP
S/4HANA.

The custom code check shows those customer objects that are affected by
simplifications.

SAP objects used by the customer objects have been changed in a syntactically
incompatible way.

Other Terms

S/4 simplification, PP, PP-MRP, Storage Location, piece

list SI_PP2_STOR_LOC_MRP, MARD, DISKZ, MRP area, ...

Reason and Prerequisites

In SAP ERP, storage locations can be excluded from MRP planning or they can be
planned separately from other storage locations. In the latter case a reorder point
procedure with maximum lot size is used which triggers transport reservations to fill up
the storage location.

MRP areas cover the very same business requirements. Materials with MRP-area-
specific MRP type 'ND' (no MRP) can be used instead of materials with a storage
location excluded from MRP. Materials with MRP-area-specific MRP type 'VB' (reorder
point planning) can be used instead of materials with separately planned storage
locations. The storage location functionality is a subset of the MRP areas capabilities.

The S/4HANA MRP only plans on plant and MRP area level. Planning on storage
location level is no longer supported.

Solution

You must remove or adapt the usages of SAP objects in your custom code, as indicated
by the custom code check.

Please check whether the usage of SAP objects in your custom code is still required
even in a S/4HANA context. Check whether customer specific reports and evaluations
can be replaced by new S4 apps like the MRP cockpit. If that is the case you should
delete your development objects which are not necessary anymore.
If the usage of SAP objects in your custom code is still required you have to adapt your
coding ensuring that the changed development objects are used in a manner which is
compatible with the business behavior in SAP S/4HANA.

Based on the scope of this development topic, the number of concerned development
objects and their possible usage in customer code it is unfortunately not possible to
describe all possible impacts and scenarios to be checked regarding this issue.
Therefore only some main impacts are described here together with necessary
adjustments of your customer code.

Changes regarding the master data

As described in the Simplification Item storage locations to be excluded from MRP

planning or to be planned separately are replaced by appropriate storage location MRP
areas. Based on that appropriate material master settings to exclude storage location or
to plan them separately (MRP4 view in material master) do not exist in S4HANA.
Instead of this appropriate scenarios have to be modelled using MRP areas.

If appropriate conditions have been checked in the old custom code, these checks have
to be adjusted. Checks regarding the storage location indicator (MARD-DISKZ = '1' or
'2') will provide no appropriate results in S/4HANA as these indicators are not set any
longer. Instead of this it has to be checked whether a storage location MRP area exists
for concerned material (entry in table MDMA for the MATNR, WERKS and BERID
where BERID is the key of the MRP area --> see customizing tables for storage location
MRP areas MDLV and MDLG as well).

Appropriate checks regarding existing MRP areas can be done for example using the
function modules MD_MRP_AREA_GET, MD_MRP_AREA_GET_ALL or
MD_GET_ALL_MATERIAL_DB.

Changes regarding the assignment of applicational data

In many customer-specific use cases planning data will be read and evaluated to
select customer-specific information or determine additional KPIs to fulfill certain
business need. This is usually done by using the function modules of function group
M61X like AUFBAUEN_MDPSX_ANZEIGEN
or MD_STOCK_REQUIREMENTS_LIST_API. Appropriate function modules can be
used furthermore to select the required data but it might be necessary to adjust the
calling program to get the required information.

Regarding those adjustments the main aspects are explained here using the example of
function module MD_STOCK_REQUIREMENTS_LIST_API:

 Generally all evaluations of the planning segments for storage location MRP will
not work any longer (MDPSX-PLAAB = '06' or '07') --> instead of this the
planning situation for the MRP area has to be determined
  The determination of the planning situation for storage location MRP area
requires that the function module will be called explicitly with reference to the key
of storage location MRP area (BERID). Available MRP areas can be determined
using one of the function modules mentioned above
 As MRP areas are always active in S4HANE it is generally recommended to call
the function module with reference to the key of MRP area (BERID). This is valid
even in case of plant MRP areas or subcontracting MRP areas. If the function
module will be called without specifying the MRP area, it provides an overall
planning result list that includes all available MRP areas within one list. This can
be useful for certain use cases but the evaluation of single MRP areas like
storage location or subcontracting MRP areas is more complicate

Testing of custom code

Generally it is strongly recommended to test the custom code which shall be used
furtherly in S/4HANA in very detail even if no adjustments have to be done to the
custom code. Sometimes changes in the behavior of the used standard objects only
occur in very rare combination regarding master and transactional data.

See More
Software Components
Software Component From To And Subsequent
SAP_APPL 600 600
SAP_APPL 602 602
SAP_APPL 603 603
SAP_APPL 604 604
SAP_APPL 605 605
SAP_APPL 606 606
SAP_APPL 616 616
SAP_APPL 617 617
More
 See More
References
This document refers to
Number Title
2190420 SAP S/4HANA: Recommendations for adaption of customer specific code
More
See More
This document is referenced by
Number Title
2599850 How to create MRP area
2268045 S4TWL - Storage Location MRP
More
See More
Languages

 Deutsch
 日本語
 Português (Machine Translation)

See More
Contact UsShare Your FeedbackAbout the LaunchpadStatus
Terms of UseLegal DisclosurePrivacy
Privacy Statement
ix
ix