Solved: MESSAGE_TYPE_X short dump

Former Member · ‎08-06-2015

Hi all,

I've this Short Dump in Tcode ST22

Runtime Errors MESSAGE_TYPE_X

Date and Time 06.08.2015 09:36:19

----------------------------------------------------------------------------------------------------

|Short text |

| The current application triggered a termination with a short dump. |

----------------------------------------------------------------------------------------------------

|What happened? |

| The current application program detected a situation which really |

| should not occur. Therefore, a termination with a short dump was |

| triggered on purpose by the key word MESSAGE (type X). |

----------------------------------------------------------------------------------------------------

|What can you do? |

| Note down which actions and inputs caused the error. |

| |

| To process the problem further, contact you SAP system |

| administrator. |

| |

| Using Transaction ST22 for ABAP Dump Analysis, you can look |

| at and manage termination messages, and you can also |

| keep them for a long time. |

----------------------------------------------------------------------------------------------------

|Error analysis |

| Short text of error message: |

| |

| Long text of error message: |

| |

| Technical information about the message: |

| Message class....... " " |

| Number.............. 000 |

| Variable 1.......... " " |

| Variable 2.......... " " |

| Variable 3.......... " " |

| Variable 4.......... " " |

----------------------------------------------------------------------------------------------------

|Information on where terminated |

| Termination occurred in the ABAP program "SAPLMBWL" - in |

| "MB_POST_GOODS_MOVEMENT". |

| The main program was "SAPMSSY1 ". |

| |

| In the source code you have the termination point in line 64 |

| of the (Include) program "LMBWLU21". |

----------------------------------------------------------------------------------------------------

|Source Code Extract |

----------------------------------------------------------------------------------------------------

|Line |SourceCde |

----------------------------------------------------------------------------------------------------

| 34|* BKPF as well. There is no other way to forward XBLNR to FI as not |

| 35|* every document is posted by MB_CREATE -> a new function module in |

| 36|* MBWL for transferring the information, called by FI, meant to load |

| 37|* the complete function group for all MBxx postings when this isn't |

| 38|* required (Performance). Would be the better way to transport the |

| 39|* information after switching off MBxx in later release. |

| 40|* corresponding IMPORT ... FROM MEMORY ... can be found in |

| 41|* AC_DOCUMENT_POST (FORM FI_DOCUMENT_PREPARE (LFACIF5D)) |

| 42| l_mem_id = 'MKPF-XBLNR'. " 641365 |

| 43| EXPORT xblnr = xblnr_sd TO MEMORY ID l_mem_id. " 641365 |

| 44| ELSE. "1245374 |

| 45| l_mem_id = 'MKPF-XBLNR'. "1245374 |

| 46| FREE MEMORY ID l_mem_id. "1245374 |

| 47| ENDIF. |

| 48| IF xmkpf-xabln IS INITIAL. "note 434093 |

| 49| CALL FUNCTION 'MB_XAB_NUMBER_GET'. "note 434093 |

| 50| ENDIF. "note 434093 |

| 51| |

| 52|ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_01 SPOTS ES_SAPLMBWL STATIC. |

| 53| |

| 54|ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_02 SPOTS ES_SAPLMBWL. |

| 55| CALL FUNCTION 'MB_CREATE_MATERIAL_DOCUMENT_UT' |

| 56| EXCEPTIONS |

| 57| error_message = 4. |

| 58|* As soon as we have started to put things into UPDATE TASK, we must |

| 59|* ensure that errors definitely terminate the transaction. |

| 60|* MESSAGE A is not sufficient because it can be catched from |

| 61|* external callers which COMMIT WORK afterwards, resulting in |

| 62|* incomplete updates. Read note 385830 for the full story. |

| 63| IF NOT sy-subrc IS INITIAL. |

|>>>>>| MESSAGE ID sy-msgid TYPE x NUMBER sy-msgno WITH "385830 |

| 65| sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4. |

| 66|* MESSAGE A263. |

| 67| ENDIF. |

| 68|* Optische Archivierung |

| 69|* Spaete Erfassung mit Barcode |

| 70|* Redesign of barcode handling -> note 780365 |

| 71| PERFORM barcode_update(sapmm07m) USING xmkpf-mblnr |

| 72| xmkpf-mjahr |

| 73| barcode. |

| 74| |

| 75| MOVE-CORRESPONDING xmkpf TO emkpf. |

| 76| CALL FUNCTION 'MB_MOVEMENTS_REFRESH' |

| 77| EXCEPTIONS |

| 78| error_message = 4. |

| 79| IF NOT sy-subrc IS INITIAL. |

| 80| MESSAGE ID sy-msgid TYPE x NUMBER sy-msgno WITH "385830 |

| 81| sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4. |

| 82|* MESSAGE A261. |

| 83| ENDIF. |

----------------------------------------------------------------------------------------------------

thanks for your help.

regards.

Former Member · ‎08-07-2015

Hi Carlos,

Message type X can occur due to various reasons. As a timely fix, you can try to reload the data again and see if this is resolved. Usually the error doesn't repeat when you reload as I can see it shows a vague indication of something specifically wrong. It can be sometime due to the servers overload. just give it a reload and see how it works.

Thanks

former_member183424 · ‎08-07-2015

There might be some user exit or badi causes this dump. Try the solution given in this KBA document 1910162 - Runtime Error 'MESSAGE_TYPE_X' is raised when trying to post goods movements

MESSAGE_TYPE_X short dump

Accepted Solutions (1)

Accepted Solutions (1)

Answers (1)

Answers (1)

Re: 261 Consumption in WM

Re: Services for object inbound delivery

Re: SSAM 2310 Deploy Error: "ReferenceError: chalk...

Re: traffic light in delivery

Re: Handling resource for S/4 HANA embedded PPDS