# Material Master Change Log Report by Field and User

> A custom ALV report that lists material master changes for many materials by date, user, transaction, table and field, with old and new values. In an audit it answers questions such as "who changed the valuation class last quarter" in one run.

- Type: Report, Custom development, ALV report
- Module: MM
- Estimated effort: S (2–4 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/reports/material-master-change-log-report/


## Why is the standard not enough?

MM04 shows the change documents of one material. It does not list collectively how a given field (for example price control, MRP type, purchasing group) changed across all materials, for a given user or date range. SCU3 only helps for customizing tables with table logging switched on. Audit requests are therefore extracted by hand from CDHDR/CDPOS with SE16.

### Closest standard alternatives

- MM04: Shows the change documents of one material; gives no collective list by field or user.
- SCU3: Shows changes to tables with table logging switched on; does not cover material master change documents.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| CDHDR | Change document header: date, time, user and transaction (driving table) | Read | - | ECC + S/4 |
| CDPOS | Changed table, field, old and new value | Read | CDPOS-OBJECTCLAS = CDHDR-OBJECTCLAS AND CDPOS-OBJECTID = CDHDR-OBJECTID AND CDPOS-CHANGENR = CDHDR-CHANGENR | ECC + S/4 |
| MARA | Material type filter | Read | MARA-MATNR = CDHDR-OBJECTID | ECC + S/4 |
| MAKT | Material description | Read | MAKT-MATNR = MARA-MATNR AND MAKT-SPRAS = SY-LANGU | ECC + S/4 |
| DD03L | Data element of the changed field | Read | DD03L-TABNAME = CDPOS-TABNAME AND DD03L-FIELDNAME = CDPOS-FNAME | ECC + S/4 |
| DD04T | Field description (logon language) | Read | DD04T-ROLLNAME = DD03L-ROLLNAME AND DD04T-DDLANGUAGE = SY-LANGU | ECC + S/4 |

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_MATNR | Material | Range / multiple | MARA-MATNR | No |
| S_MTART | Material type | Range / multiple | MARA-MTART | No |
| S_UDATE | Change date | Range / multiple | CDHDR-UDATE | Yes |
| S_USER | Changed by | Range / multiple | CDHDR-USERNAME | No |
| S_TCODE | Transaction | Range / multiple | CDHDR-TCODE | No |
| S_TABNM | Table | Range / multiple | CDPOS-TABNAME | No |
| S_FNAME | Field name | Range / multiple | CDPOS-FNAME | No |
| P_NOINS | Exclude create entries | Checkbox | - | No |

## Output columns

| Column | Source |
|---|---|
| Date | CDHDR-UDATE |
| Time | CDHDR-UTIME |
| User | CDHDR-USERNAME |
| Transaction | CDHDR-TCODE |
| Material | MARA-MATNR |
| Description | MAKT-MAKTX |
| Material type | MARA-MTART |
| Table | CDPOS-TABNAME |
| Field | CDPOS-FNAME |
| Field description | Calculated: DD04T-SCRTEXT_M (through DD03L-ROLLNAME) |
| Org key | Calculated: Plant, valuation area, storage location or sales organization parsed from CDPOS-TABKEY |
| Change type | CDPOS-CHNGIND |
| Old value | CDPOS-VALUE_OLD |
| New value | CDPOS-VALUE_NEW |
| Change number | CDHDR-CHANGENR |

## How does the report work?

1. CDHDR is read for object class MATERIAL with the date (UDATE), user (USERNAME) and transaction (TCODE) criteria; the material filter is applied to the object key (OBJECTID).
2. For each change number the CDPOS lines are read: table (TABNAME: MARA, MARC, MARD, MBEW, MAKT, MVKE etc.), field (FNAME), change type (CHNGIND) and old / new value.
3. The table key (TABKEY) is parsed per table, and the plant, valuation area, storage location or sales organization is shown in its own column.
4. The field description is taken in the logon language from DD04T through the data element in DD03L.
5. The material type is added from MARA and the description from MAKT; the material type and field filters are applied. With "exclude create entries" selected, lines with CHNGIND = I are skipped.

## Authorization objects

- M_MATE_MAR: Master data display authorization by material type
- M_MATE_WRK: Master data display authorization by plant

## Frequently asked questions

### Do mass changes (MM17) and upload programs appear as well?

Yes. Every process that writes change documents leaves an entry in CDHDR/CDPOS. The transaction column shows whether the change came from MM02, MM17 or an upload program.

### Does it work with the long (40-character) material number?

Yes. The object key and table key are parsed according to the material number length in the system; the 40-character number in S/4HANA is supported.

### Does the report delete or change change documents?

No, it only reads. Change documents are an audit trail, so the report works with read-only authorization.

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=mm-material-master-change-log
