MESSAGE_TYPE_X
highProgram Called MESSAGE TYPE X — Intentional Fatal Dump
Module: ABAP
What this means
MESSAGE_TYPE_X is not a system error — it is a deliberate program action. When ABAP code executes MESSAGE ... TYPE 'X', it intentionally triggers a short dump. SAP and custom programs use this to signal an unrecoverable application state where continuing execution would cause data corruption. Common triggers: inconsistent Customising that the program cannot safely work around; a required master data record (cost centre, GL account, profit centre) that is missing; period-end processing finding open items that should have been cleared; or a custom program using MESSAGE TYPE X as a substitute for proper error handling. The key distinction: this dump was chosen, not caused by a system fault.
Open ST22 and read the message text carefully — it will tell you exactly what condition the program detected. Unlike most dumps, the ST22 entry for MESSAGE TYPE X contains a human-readable description of the business problem. Resolve the underlying data or Customising issue that the message describes. If the dump comes from a standard SAP program, check OSS for notes relating to that message class and number. If it is from a custom program and the message text is not informative, the code needs to be improved.
Quick Info