Describing Master Data for Provisions

In this lesson, you will learn about:

The relevant Material Master attributes
Mass Change of Material Master data on MRP area level

Scenario

You are involved in the implementation of the SAP S/4HANA Defense and Security industry solution. In order to do this, you first need to familiarize yourself with the relevant master data objects of the material master.

The Manage Product Master Data tile

The image shows a square icon labeled Manage Product Master Data, indicating a functionality to manage the master data for products.

The figure, The Manage Product Master Data Tile, shows the Manage Product Master Data tile. In the following, we will explain the functions of it.

The image shows a SAP screen for an MRP Area called 2nd Tank Platoon 50002368_P. The Procurement section of the screen displays a Special Procurement Type field with the value Supply relationships (99). This indicates that the MRP Area has a supply relationship defined, which is used for external procurement.

The special procurement type in the procurement section controls how the material is supplied to the force element. In order to make use of supply relationships, special procurement types need to be defined and assigned to the material master (here, Special Procurement Type 99 calls a BADI that determines the supplying storage location based on the supply relationship).

Supply relationships can be differentiated by a class / subclass of supply, which in Defense and Security implementations are mapped to External Material Group, and maintained as part of Basic Data in the Product Master.

The image shows two SAP screens for a product called Assault rifle Type 1. The first screen displays the product's general information, including its product type, group, and GTIN. The second screen focuses on the product's configuration, highlighting the Condition Management Requests field and the External Product Group as Non-consumable goods (57.000). The text overlay indicates that the Condition Management feature requires Batch Management.

The Condition Management field in the Basic Data section controls whether the material is subject to condition management. <blank> means that the material is not subject to condition management. Value '1' means that the material is subject to condition management without full batch management, meaning that the stock holdings of the material will be managed by batches equal to the condition management code. Value '2' means that the material is subject to full batch management. The first character of the 10-digit batch number represents the condition code. The remaining 9 digits represent the system-generated batch number.

The return code specifies whether the material needs to be returned.

Return to the logistics level determines to which level in the organization the material must be returned - for example, Depot, Supplying Unit, Industry Vendor.

Notice that Manage Product Master Data is a non-Defense and Security application and can therefore be found in SAP Core roles, such as SAP_BR_PRODMASTER_SPECIALIST.

The image shows a SAP screen for the Copy Material Master Data transaction, which is used to create material requests and purchase orders. The corresponding material master data for an FMPO (Force Module Planning Object) needs to be created. This data includes sales, purchasing, MRP Area, plant, and storage location information from the material master. The functionality to create this material master data in bulk can be accessed using the /ISDFPS/MATMAS_COPY transaction.

Using BAdI /ISDFPS/MATMASSRCDET, a customer-specific logic for material master creation, can be implemented.

/ISDFPS/MATMAS_COPY creates material master data for a force element; another force element can be defined as the reference template.

The system copies the relevant material master settings from the material master data of the template force element to the corresponding material master data of the target force element.

The image shows a SAP screen for the Mass Maintenance: Materials (Industry) transaction, which is used for mass changes, creations, and deletions of material master data. It also shows information about the FIORI App Mass Maintenance Material and the Report RMMDIBE. The key points are that the FIORI App allows mass changes, creations, and deletions of material master data, but does not support material master data on the MRP area level. The Report RMMDIBE, on the other hand, allows mass changes, creations, and deletions of material master data on the MRP area level.

As Defense and Security facilitates (or requires) the use of MRP areas, MRP area master data is of specific importance in Defense and Security implementations. Planning parameters (participation in MRP, reorder points, and so on) as well as the supplier determination logic are therefore dependent on MRP Area master data.

The report RMMDDIBE lets the user mass create or mass change MRP Area data of the material master.

It is possible to do the following:

Copy data from plant level
Copy data from another MRP Area
Create/Change MRP Area data with MRP and/or Forecast Profile
Create/Change MRP Area data by manually specifying input values
Set/Reset deletion flag
And so forth