on 09-16-2019 9:49 PM
Hello,
Trying to run MD01N for 1 plant. I can run successfully for a couple of times but after I get the following message.
Category ABAP programming error
Runtime Errors MESSAGE_TYPE_X
ABAP Program CL_PPS4_MRP_DISPATCHER========CP
Application Component PP-MRP
Implemented note : 2673397. Did not resolve issue.
MRP Live run parameters:
System
Thank you.
Hi, We also faced dumps in MD01N when classic MRP was working just fine.
We implemented below notes and problem got resolved. Also, None of these notes were directly addressing the cause of dump statement but still it worked.
2847478 MRP Live Shortdump because of unnoticed overflow in BOM explosion
2814930 Dump in MRP Live with BOM explosion and use of revision levels
2902887 Numeric Overflow issue in MRP Live RUN
2743468 Incorrect rounding of fixed quantity observed in MRP Live
2673397 MESSAGE_TYPE_X runtime error in MD01N
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Den,
We have the same issue. Could you share your solution about this issue?
Thanks in advance.
Best Regards,
Yita
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Den,
Run the report 'pph_mrp_perf' in se38 to see the log
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Den
Usually, when this kind of MESSAGE_TYPE_X dump happens in CL_PPS4_MRP_DISPATCHER=>MAIN, you will also see another short dump with the error AMDP_EXECUTION_FAILED. Basically, first one of the HANA stored procedures ends with this dump and then the main program is terminated with MESSAGE_TYPE_X because the stored procedure failed.
The root cause of the issue is probably in the dump AMDP_EXECUTION_FAILED, so please check if you can find this dump and attach it to the thread.
Regards,
Caetano
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Caetano,
First of all, thank you for your answer.
Attach ST22 report. I just removed some sensitive data, hope you understand.
Regarding the notes:
- 2814930, we are not using revision levels in our master data. Does it still need to be implemented?
- 2827659, I did not see this error "“cannot convert xxx to the type VARCHAR(4) for column VERID" in the ST22 report, do I still need to implemented?
Regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Den
The short dump runtime error and the program is not enough to understand what is happening here. Please download the complete short dump and attach it to this question. You can download the dump opening it in transaction ST22 and choosing the option System - List - Save - Save and choose the option Unconverted.
In the meantime, I have checked for some notes and the following seems to be relevant for this short dump, so you can implement them and test in your system again:
2827659 Dump in MRP live: AMDP_EXECUTION_FAILED
2814930 Dump in MRP Live with BOM explosion and use of revision levels
Regards,
Caetano
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
108 | |
12 | |
11 | |
6 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.