Skip to Content

MRP live (MD01N) error "MESSAGE_TYPE_X, CL_PPS4_MRP_DISPATCHER========CP"

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:

  • Plant: XYZ1
  • Material Scope: A
  • All order BOM components : Check
  • Regenerative Planning: Check
  • Scheduling : 1
  • Planning mode : 3

System

  • S4HANA 1809
  • S4CORE: 103

Thank you.

Add a comment
10|10000 characters needed characters exceeded

Related questions

6 Answers

  • Posted on Sep 17, 2019 at 01:54 AM

    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

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Sep 17, 2019 at 10:33 PM

    st22-error-edit.txt

    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,


    st22-error-edit.txt (138.7 kB)
    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Sep 18, 2019 at 12:37 AM

    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

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Nov 06, 2019 at 07:53 AM

    Hi Den,

    Run the report 'pph_mrp_perf' in se38 to see the log

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 24, 2019 at 03:08 PM

    Hi Den,

    We have the same issue. Could you share your solution about this issue?

    Thanks in advance.

    Best Regards,

    Yita

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jun 08, 2020 at 12:32 PM

    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

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Raph

      Can you please post a new thread with your issue?

      There are many possible causes for this issue, so you should post a new question and provide additional details, such as attach the entire short dump, your release and all the possible details.

      Regards,
      Caetano

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.