2.2    SAP S/4HANA Changes

With the new Inventory Management (IM) module with SAP S/4HANA, SAP has made major changes, including restructuring the backend table structures and phasing out a number of older transaction codes. The table structure changes have been implemented to simplify and speed up processing in the IM module. In addition SAP S/4HANA has introduced a full suite of SAP Fiori apps to enable IM processes.

The following subsections include details of transactions that have been made obsolete in SAP S/4HANA, configuration changes that are applicable for IM in SAP S/4HANA, SAP Fiori apps that support the IM processes, and the master data simplifications supported in IM.

2.2.1    Transaction Code Changes

The following transactions have been made obsolete in SAP S/4HANA. The recommendation going forward is to leverage Transaction MIGO for these obsoleted transactions: MB01, MB02, MB03, MB04, MB05, MB0A, MB11, MB1A, MB1B, MB1C, MB31, MBNL, MBRL, MBSF, MBSL, MBST, and MBSU.

The transactions in Table 2.1 are still available, but will be phased out in future releases, so you should use the corresponding SAP Fiori apps instead.

Old Transaction	SAP Fiori app
MMBE_OLD	Stock – Single Material
MMBE	Stock – Single Material
MB51	Material Documents Overview
MB52	Stock – Multiple Materials
MB5B	Stock – Multiple Materials

Table 2.1    Transactions Being Phased Out and the Corresponding Recommended SAP Fiori App

As mentioned, SAP S/4HANA has also made database changes to the traditional table structures used in IM. In the traditional SAP Business Suite applications, data was stored in various tables such as table MKPF (Document Header Data), table MSEG (Document Item Data), and some additional hybrid tables to store data attributes (e.g., table MCHB and table MSSA). In SAP S/4HANA, all tables are converted to a single table, MATDOC. All IM goods movement data will be stored in table MATDOC. Tables MKPF and MSEG have been made obsolete.

2.2.2    Configuration Changes

Configuration in the IM module hasn’t changed much with SAP S/4HANA. The only significant change for IM configuration is its dependency with mandatory changes in the Material Ledger (ML) functionality for material valuation. In SAP S/4HANA, the ML function is mandatory to support flexible valuation methods in multiple currencies. You’ll need to work with your finance teams to coordinate these changes in the system.

2.2.3    SAP Fiori Applications

Within SAP S/4HANA, the user experience has been enhanced leveraging SAP Fiori apps for most end-user transactions. SAP Fiori apps can be modified to suit users’ preferences and roles. A typical SAP Fiori app tile screen is shown in Figure 2.1. SAP Fiori provides a personalized, role-based, and user-friendly experience to access transactional/analytical applications.

Figure 2.1    Materials Management - Warehouse Processing (Inventory Management) Home Page Tile

2.2.4    SAP Catch Weight Management

The SAP Catch Weight Management solution is often leveraged in food processing industries that have the need to track a single item throughout the supply chain in two units of measure, one for valuation and one for supply chain processing. Most often, the single item is tracked in a unit of weight.

SAP Catch Weight Management has been enabled within SAP S/4HANA. The SAP Catch Weight Management solution was only supported in the Industry Solution offering in SAP S/4HANA until the 1709 update, where the solution was expanded as a general offering.

SAP Catch Weight Management is a cross-functional solution. It integrates with Procurement, IM, Production, Quality Management, and Sales and Distribution.

2.2.5    Master Data Simplifications—Material Master

No IM-specific material master data simplifications have been identified. The only significant change is an expansion of the material master to 40 characters, as outlined in Chapter 3, Manufacturing.