Mass Material Master Upload Program
Short answer: A custom program that creates or updates material master data in bulk from Excel or CSV rows, including the basic data, plant and valuation views. It checks everything in test mode first, then lists the result and error message for every row.
- Estimated effort
- M · 4–6 working days
- System
- ECC and S/4HANA
- Tables
- 4
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
Why is the standard not enough?
MM17 only changes existing materials in bulk; it neither creates new materials nor reads a file. LSMW needs technical setup and is not recommended for many objects in S/4HANA. The Migration Cockpit is designed for the initial data migration. Companies that create hundreds of materials every month need a templated upload with a test mode that business users can run themselves.
Who uses it? Master data teams, MM consultants and purchasing or planning teams that introduce new products.
Closest standard alternatives
Tables used
The tables the program reads and updates. ECC and S/4HANA differences are marked separately.
| Table | Role | Access | System |
|---|---|---|---|
| MARAGeneral Material Data | General material data: type, industry sector, base unit, material group | Write | ECC + S/4 |
| MAKTMaterial Descriptions | Material description (per language) | Write | ECC + S/4 |
| MARCPlant Data for Material | Plant data: MRP type, purchasing group | Write | ECC + S/4 |
| MBEWMaterial Valuation | Valuation data: valuation class, price control and price | Write | ECC + S/4 |
S/4HANA notes
- MBEW: In S/4HANA the Material Ledger is mandatory and valuation data is read through a compatibility view. Prices remain readable; validate value calculations against the currency and valuation view in use.
BAPIs and functions used
- BAPI_MATERIAL_SAVEDATACreate and change material master data. Creates or updates the material with all views for each row
- BAPI_TRANSACTION_COMMITCommit a BAPI transaction. Saves successful rows permanently
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| P_FILE | Upload file (XLSX or CSV) | Single value | — | Yes | C:\temp\malzemeler.xlsx |
| P_TEST | Test mode (check without posting) | Checkbox | — | No | X |
| P_UPDATE | Update existing materials | Checkbox | — | No | — |
Input file columns
The columns of the upload template and the SAP fields they are written to. Columns with an asterisk are mandatory.
| # | Column | Target field | Required |
|---|---|---|---|
| 1 | Material (blank = internal number) | MARA-MATNR | No |
| 2 | Material type | MARA-MTART | Yes |
| 3 | Industry sector | MARA-MBRSH | Yes |
| 4 | Description | MAKT-MAKTX | Yes |
| 5 | Base unit | MARA-MEINS | Yes |
| 6 | Material group | MARA-MATKL | No |
| 7 | Plant | MARC-WERKS | Yes |
| 8 | MRP type | MARC-DISMM | No |
| 9 | Purchasing group | MARC-EKGRP | No |
| 10 | Valuation class | MBEW-BKLAS | No |
| 11 | Price control | MBEW-VPRSV | No |
| 12 | Price | By rule Written to MBEW-VERPR when price control is V, to MBEW-STPRS when it is S | No |
Sample upload file
| 1 | Material (blank = internal number) | Material type * | Industry sector * | Description * | Base unit * | Material group | Plant * | MRP type | Purchasing group | Valuation class | Price control | Price |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2 | ROH | M | Carton box 60x40 | PC | 01 | 1000 | PD | 001 | 3000 | V | 5.10 | |
| 3 | RM-2051 | ROH | M | Steel sheet 3 mm | KG | 02 | 1000 | PD | 002 | 3000 | V | 64.80 |
| 4 | FG-5003 | FERT | M | Packed product C | PC | 10 | 2000 | PD | 7920 | S | 295 |
Result list columns
| # | Column | Source |
|---|---|---|
| 1 | Row | Calculated Row number in the file |
| 2 | Material | MARA-MATNR |
| 3 | Status | Calculated From the BAPI return messages: created, updated or error |
| 4 | Message | Calculated First error or success message from the BAPI return table |
Sample result list
| Row | Material | Status | Message |
|---|---|---|---|
| 2 | 100000123 | Created | Material 100000123 created |
| 3 | RM-2051 | Created | Material RM-2051 created |
| 4 | FG-5003 | Error | Purchasing group is required for plant 2000 |
How does the program work?
- The file (XLSX or CSV) is read from the user’s PC or, in a background job, from the application server; the first row is skipped as the header.
- Every row is checked for mandatory fields and values: material type, industry sector, unit of measure, plant and valuation class must exist in the system.
- The row is mapped to the BAPI_MATERIAL_SAVEDATA structures: header, basic data, description, plant data and valuation data.
- In test mode the BAPI is called and the change is rolled back, so every error is visible without posting.
- In a real run BAPI_TRANSACTION_COMMIT is called after each successful row; results and messages are listed per row, and failed rows can be downloaded as a separate file.
Performance notes
Run files above a few thousand rows as a background job. Committing per row isolates failed rows; for very large volumes, committing per package can be considered.
Features
- Test mode (check without posting)
- Line-by-line result and error log
- Download failed lines as a separate file The corrected file can be uploaded again with the same template.
- Export to Excel An empty upload template can be downloaded as Excel.
- Runs as a background job
Authorization objects
- M_MATE_MARMaster data maintenance authorization by material type
- M_MATE_WRKMaster data maintenance authorization by plant
Frequently asked questions
Can this program be used on S/4HANA?
Yes. BAPI_MATERIAL_SAVEDATA is supported on S/4HANA as well. The Migration Cockpit is recommended for the initial migration; this program is for the ongoing need to create materials in daily operations.
Which views can be loaded?
The template covers basic data, plant and valuation views. Sales, warehouse or accounting views can be added to the template as needed; each extra view increases the effort range.
What happens to failed rows?
Failed rows are not saved and are listed with their messages. They can be downloaded as a separate file, corrected and uploaded again.
Related reports
Stock Aging Report
A custom ALV report that shows how many days each material has been in stock since its last goods receipt and which age bucket (0–30, 31–90, 91–180, …
Let us build this program for your system
Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.