Skip to Content
Technical Articles
Author's profile photo Prakash Pol

Mass Creation & Maintenance of Warehouse Product Master in EWM

It is very common in all SAP EWM projects; be it an implementation, support or roll-out project that the mass creation and maintenance of EWM warehouse product master data is needed always, either as part of a regular master data maintenance or during the warehouse go-live.

My blog here explains the various methods available to manage the warehouse product master data mass creation/change or the mass maintenance in EWM.

Pre-requisite: The basic product master views must already exist in EWM. In Classical EWM, you CIF materials from ERP and create the product master in SCM-EWM system. In Decentral EWM on S/4 HANA, you send the material data to EWM system using BD10 transaction via ALE IDoc.

Method 1: Use of the Warehouse Monitor for mass creation and change of warehouse product master data

I have shown below an example on how to use EWM warehouse monitor for the mass extension or creation of warehouse product master. In similar way, one can also perform the mass master data changes.

Step 1: In the EWM Warehouse Monitor, selected the node Product Master Data –> Warehouse Attributes to check what all products are not extended for product master.

Selected the radio button and used the option-only those products without Warehouse Data.

as expected the monitor has shown all those products for which there is no warehouse product master data exist.

Step 2: Selected the products for which the mass creation of warehouse product master views is needed and clicked on the “Mass Change/Create” in the “More Methods” option.

Step 3: In the pop-up, entered the data that we wanted to populate in the warehouse product master for the selected products, under the “Warehouse Data” section

Step 4: After proceeding further, the system has provided the info. that we have selected those products for which no warehouse data exist. After continuing next, the monitor had also given the pop-up message to confirm on how many fields we wished to populate and how many are the total data sets that would get updated with the mass run.

Step 5: Once confirmed as “Yes” in the previous step, system has automatically performed the mass creation or update of the data fields in the product master data. To verify if the data is successfully updated or not, select same warehouse monitor node and choose radio button “Choose Only Products with Warehouse Master Data” and execute.

As shown below, system has performed the mass update successfully with values entered in step 3.

Method 2: Batch update from external files transaction: /SCWM/MIG_PRODUCT 

Using a transaction code /SCWM/MIG_PRODUCT one can perform the mass maintenance of the product including an extension the product master to a warehouse number and populating the data fields of master data.

Step 1: Populated the upload file template provided by SAP.

As provided in the SAP note 2602348, I used the file template named SCWM MIGR fields.xlsx. I have then populated the data in this file for the respective data fields to be updated in the warehouse product master. Saved this file as .CSV format in the local drive.

Below example shows that the upload file data is populated for a product number 1021, in order to perform the update of the Process Type Determination Indicator (Field: PTDETIND) Z4.

Step 2: Executed the transaction /SCWM/MIG_PRODUCT

Selected “Upload to EWM” option and the check-box “Product Master Data”. Next I have provided the warehouse number and party entitled to dispose for which upload of the master data is to take place.

Step 3: Selected the product master .CSV file using the upload file path from the local drive & then executed the program.

program would show the detailed log confirming if the upload has been successful & which tables were updated by the /SCWM/MIG_PRODUCT program.

Step 4: Checked in the warehouse monitor if warehouse product master is extended to warehouse number and updated with the data fields from the upload file for example- the process type determination indicator Z4 from our test file.

The output showed that with the program /SCWM/MIG_PRODUCT, the warehouse product master is successfully extended for warehouse number and also updated with process type determination indicator added in upload file.


Key References:

  1. SAP note: 2602348
  2. SAP note: 2627825

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Martin Prokop
      Martin Prokop

      Excelent article, Prakash!

      We use Slotting for product master creation/changing as it is automatical and can be run in a background job. But it takes about 7h for 100.00 products... Not very fast...


      Author's profile photo Prakash Pol
      Prakash Pol
      Blog Post Author

      Thanks for your feedback, Martin!

      As you rightly said, slotting is another method of making mass changes in warehouse product master views. The methods mentioned in my article would be also good for initial go-live (during data migration/cutover) and during the regular maintenance cycles, where the slotting as an established process in the EWM system not commonly used.

      Author's profile photo Raghava S
      Raghava S

      Hi Prakash,

      Nice blog..thanks for sharing your knowledge with such awesome blogs.

      qq: Did you use /scwm/mig_product for mass storage type data creation as well?

      if not any idea what options we have?


      Best Regards,


      Author's profile photo Sweta Somsetwar
      Sweta Somsetwar

      Hi Prakash,

      In non- S/4 EWM we use BADI called while CIF material master to automatically update warehouse views in EWM. These BADI's can no longer be used in S/4 as we use IDocs for material master transfer.

      Do we have any such way to automatically create/update warehouse views in Decentral EWM on S/4 HANA from non-S/4 ERP system?


      Sweta Somsetwar

      Author's profile photo Accenture Application Team
      Accenture Application Team


      does anyone have available the csv template for use of the /scwm/mig_product to upload fixed bins from local file?