RFC Error while posting GR

[former_member158944]

Runtime Errors MESSAGE_TYPE_X
Date and Time 01.07.2009 14:25:17
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|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: |
| Internal error: Multiple call of update function module |
| |
| Long text of error message: |
| Diagnosis |
| In the FORM routine Buchen_Ausfuehren (program SAPMM07M), an error |
| message was issued by a Business Add-In (BAdI) or function module. |
| This is not permitted, because it could lead to data |
| inconsistencies. For this reason, the update of the material |
| document was also terminated with a termination message (dump). |
| Note that this message (M7 372) is not the responsible error |
| message. |
| System Response |
| Procedure |
| Contact your system administrator. |
| Procedure for System Administration |
| If there is an active implementation of the Business Add-In |
| MB_DOCUMENT_BADI, check that no error message is issued in the |
| MB_DOCUMENT_BEFORE_UPDATE method. |
| |
| Technical information about the message: |
| Message class....... "M7" |
| Number.............. 372 |
| Variable 1.......... " " |
| Variable 2.......... " " |
| Variable 3.......... " " |
| Variable 4.......... " " |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|How to correct the error |
| Probably the only way to eliminate the error is to correct the program. |
| - |
| |
| If the error occures in a non-modified SAP program, you may be able to |
| find an interim solution in an SAP Note. |
| If you have access to SAP Notes, carry out a search with the following |
| keywords: |
| |
| "MESSAGE_TYPE_X" " " |
| "SAPMM07M" or "MM07MFB9_BUCHEN_AUSFUEHREN" |
| "BUCHEN_AUSFUEHREN" |
| |
| If you cannot solve the problem yourself and want to send an error |
| notification to SAP, include the following information: |
| |
| 1. The description of the current problem (short dump) |
| |
| To save the description, choose "System->List->Save->Local File |
| (Unconverted)". |
| |
| 2. Corresponding system log |
| |
| Display the system log by calling transaction SM21. |
| Restrict the time interval to 10 minutes before and five minutes |
| after the short dump. Then choose "System->List->Save->Local File |
| (Unconverted)". |
| |
| 3. If the problem occurs in a problem of your own or a modified SAP |
| program: The source code of the program |
| In the editor, choose "Utilities->More |
| Utilities->Upload/Download->Download". |
| |
| 4. Details about the conditions under which the error occurred or which |
| actions and input led to the error. |
| |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|System environment |
| SAP-Release 701 |
| |
| Application server... "scm7srv" |
| Network address...... "192.168.75.1" |
| Operating system..... "Windows NT" |
| Release.............. "5.2" |
| Hardware type........ "4x AMD64 Level" |
| Character length.... 16 Bits |
| Pointer length....... 64 Bits |
| Work process number.. 0 |
| Shortdump setting.... "full" |
| |
| Database server... "SCM7SRV\EH4" |
| Database type..... "MSSQL" |
| Database name..... "EH4" |
| Database user ID.. "eh4" |
| |
| Terminal.......... "scm7srv" |
| |
| Char.set.... "C" |
| |
| SAP kernel....... 701 |
| created (date)... "Feb 24 2009 23:27:20" |
| create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00" |
| Database version. "SQL_Server_8.00 " |
| |
| Patch level. 32 |
| Patch text.. " " |
| |
| Database............. "MSSQL 9.00.2047 or higher" |
| SAP database version. 701 |
| Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows |
| NT 6.0" |
| |
| Memory consumption |
| Roll.... 16192 |
| EM...... 20949200 |
| Heap.... 0 |
| Page.... 1105920 |
| MM Used. 15281504 |
| MM Free. 1474560 |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|User and Transaction |
| |
| Client.............. 800 |
| User................ "SAPUSER" |
| Language key........ "E" |
| Transaction......... "MB1C " |
| Transactions ID..... "C28466DE2FA0F1228229C2FBE9AA4F0A" |
| |
| Program............. "SAPMM07M" |
| Screen.............. "SAPMM07M 0421" |
| Screen line......... 63 |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|Information on where terminated |
| Termination occurred in the ABAP program "SAPMM07M" - in "BUCHEN_AUSFUEHREN". |
| The main program was "SAPMM07M ". |
| |
| In the source code you have the termination point in line 34 |
| of the (Include) program "MM07MFB9_BUCHEN_AUSFUEHREN". |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|Source Code Extract |
----------------------------------------------------------------------------------------------------
|Line |SourceCde |
----------------------------------------------------------------------------------------------------
| 4|*---------------------------------------------------------------------* |
| 5|* Die Verbuchungstabellen werden verbucht. * |
| 6|*---------------------------------------------------------------------* |
| 7| |
| 8|* consider the tables XEKBE_MA and XEKBZ_MA for the "MAA EhP4 |
| 9|* PO history of postings with multi account assignment "MAA EhP4 |
| 10| |
| 11|ENHANCEMENT-POINT MM07MFB9_BUCHEN_AUSFUEHREN_006 SPOTS ES_SAPMM07M STATIC . |
| 12| |
| 13|*&---------------------------------------------------------------------* |
| 14|*& Form buchen_ausfuehren |
| 15|*&---------------------------------------------------------------------* |
| 16|* text |
| 17|*----------------------------------------------------------------------* |
| 18|FORM buchen_ausfuehren. |
| 19| |
| 20| DATA: |
| 21| ls_dm07m TYPE dm07m, |
| 22| ls_vm07m TYPE vm07m. |
| 23| |
| 24|ENHANCEMENT-POINT mm07mfb9_buchen_ausfuehren_005 SPOTS es_sapmm07m STATIC. |
| 25| STATICS: statics_lock TYPE char1. |
| 26| |
| 27| DATA:ls_isc_me_post_history TYPE isc_me_post_history. |
| 28| |
| 29| def_break 'BUCHEN_AUSFUEHREN'. "#EC * |
| 30| BREAK-POINT ID mb_buchen_ausfuehren. |
| 31| |
| 32|* statics_lock secures that BUCHEN_AUSFUEHREN is only processed once! |
| 33| IF statics_lock = x. |
|>>>>>| MESSAGE x372(m7). |
| 35| ENDIF. |
| 36| statics_lock = x. |
| 37| |
| 38|ENHANCEMENT-POINT buchen_ausfuehren_09 SPOTS es_sapmm07m. |
| 39| |
| 40|* Consistency check |
| 41| DATA: l_switch_off TYPE char1. |
| 42| GET PARAMETER ID 'M7373_DISABLE' FIELD l_switch_off. |
| 43| IF l_switch_off IS INITIAL. |
| 44| CALL FUNCTION 'MB_CONSISTENCY_CHECK' |
| 45| EXPORTING |
| 46| it_xmseg = xmseg[] |
| 47| it_xvm07m = xvm07m[] |
| 48| EXCEPTIONS |
| 49| missing_zustd_t156m = 1 |
| 50| OTHERS = 2. |
| 51| IF sy-subrc <> 0. |
| 52| MESSAGE a373 WITH sy-subrc. |
| 53| ENDIF. |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|Contents of system fields |
----------------------------------------------------------------------------------------------------
|Name |Val. |
----------------------------------------------------------------------------------------------------
|SY-SUBRC|0 |
|SY-INDEX|0 |
|SY-TABIX|1 |
|SY-DBCNT|1 |
|SY-FDPOS|0 |
|SY-LSIND|0 |
|SY-PAGNO|0 |
|SY-LINNO|1 |
|SY-COLNO|1 |
|SY-PFKEY|H4HL |
|SY-UCOMM|BU |
|SY-TITLE|Enter Other Goods Receipts: Collective Processing |
|SY-MSGTY|X |
|SY-MSGID|M7 |
|SY-MSGNO|372 |
|SY-MSGV1| |
|SY-MSGV2| |
|SY-MSGV3| |
|SY-MSGV4| |
|SY-MODNO|1 |
|SY-DATUM|20090701 |
|SY-UZEIT|142515 |
|SY-XPROG|SAPLBPFC |
|SY-XFORM|%_CONTROL_EXIT_DYNPRO |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|Active Calls/Events |
----------------------------------------------------------------------------------------------------
|No. Ty. Program Include Line |
| Name |
----------------------------------------------------------------------------------------------------
| 3 FORM SAPMM07M MM07MFB9_BUCHEN_AUSFUEHREN 34 |
| BUCHEN_AUSFUEHREN |
| 2 FORM SAPMM07M MM07MFF0_FCODE_BEARBEITEN 51 |
| FCODE_BEARBEITEN |
| 1 MODULE (PAI) SAPMM07M MM07MI00 609 |
| FCODE_BEARBEITEN |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|Chosen variables |
----------------------------------------------------------------------------------------------------
|Name |

[PeterJonker]

And the question IS ????????????????????????????????????

What did you do already to investigate this ??????????????????????

Did you follow the instructions in the dump, the ones you popsted here ????????????????

Looks to me you have implemented a BADI in a wrong way. On first glance it might be that you try to book a post which is already booked.

The error states that you are trying to book something twice:

|* statics_lock secures that BUCHEN_AUSFUEHREN is only processed once!

IF statics_lock = x.

MESSAGE x372(m7).

ENDIF.

Did you check that ?

[former_member201275]

I can recommend trying 2 possibilities:

1. MESSAGE_TYPE_X is likely kernel problem.

You'd want to update your kernel level up to latest version.

That'll solve most cases

2. upgrade the GUI patch or uninstall and reinstall the same GUI same patch level.

Try the GUI first.