on 2025 Jan 09 6:54 AM
Hi Mates,
An issue has occurred where a change made by someone in the ABAP team to a standard material-related object has resulted in dumps across all material-related transactions. We need guidance on how to identify the root cause of the error and the best approach to rectify it without impacting the system further. Any suggestions or best practices to resolve this efficiently would be greatly appreciated.
Request clarification before answering.
Hello @KiranSAP3
Root cause
A standard SAP object (include LMGMM01D) was modified → field `MARA-MATFI` doesn’t exist → syntax dump.
1. Go to SE38 → SAPLMGMM → Include LMGMM01D (line 62)
2. Find the custom change using `MARA-MATFI`
3. Either:
Replace with valid field from MARA
Or remove/comment the custom code
4. Run SNOTE / SPAU / SPDD → check for modifications
5. If standard object modified → restore original via version management
Avoid direct changes in SAP standard
Move logic to Z-enhancement / BAdI / implicit enhancement
revert recent transport or restore original SAP code.
Thanks,
Sravan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 9 | |
| 5 | |
| 4 | |
| 4 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.