Dear guys,
we have upgraded our ERP 6.03 to 6.06 and after that when calling several transactions ( MB1B, MB1A,MB11, MB01, MB1C, MB0A,MB04, MIGO, MBRL,MBSU,MBST,MB02,MB21,VL31N,MB31 ) the following error dump occurs:
Category ABAP Programming Error
Runtime Errors SYNTAX_ERROR
ABAP Program SAPLMIGO
Application Component MM-IM
Date and Time 12.12.2013 11:45:36
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Short text |
| Syntax error in program "SAPLMIGO ". |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|What happened? |
| Error in the ABAP Application Program |
| |
| The current ABAP program "????????????????????????????????????????" had to be |
| terminated because it has |
| come across a statement that unfortunately cannot be executed. |
| |
| The following syntax error occurred in program "SAPLMIGO " in include "LMIGOKM1 |
| " in |
| line 299: |
| "O objeto de dados "LS_MKPF" não possui componentes com o nome "MSR_ACT" |
| "IVE"." |
| " " |
| " " |
| |
| The include has been created and last changed by: |
| Created by: "SAP " |
| Last changed by: "SAP " |
| Error in the ABAP Application Program |
| |
| The current ABAP program "????????????????????????????????????????" had to be |
| terminated because it has |
| come across a statement that unfortunately cannot be executed. |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|What can you do? |
| Please eliminate the error by performing a syntax check |
| (or an extended program check) on the program "SAPLMIGO ". |
| You can also perform the syntax check from the ABAP Editor. |
| |
| If the problem persists, proceed as follows: |
| 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 |
| The following syntax error was found in the program SAPLMIGO : |
| "O objeto de dados "LS_MKPF" não possui componentes com o nome "MSR_ACT" |
| "IVE"." |
| " " |
| " " |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|How to correct the error |
| Probably the only way to eliminate the error is to correct the program. |
| - |
| 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..... 731 |
| SAP Basis Level. 0009 |
| |
| Application server... "dc1hjed0" |
| Network address...... "10.182.10.50" |
| Operating system..... "HP-UX" |
| Release.............. "B.11.31" |
| Hardware type........ "ia64" |
| Character length.... 16 Bits |
| Pointer length....... 64 Bits |
| Work process number.. 14 |
| Shortdump setting.... "full" |
| |
| Database server... "dc1hjed0" |
| Database type..... "ORACLE" |
| Database name..... "JED" |
| Database user ID.. "SAPSR3" |
| |
| Terminal.......... "uecnbk6031" |
| |
| Char.set.... "C" |
| |
| SAP kernel....... 720 |
| created (date)... "Sep 15 2013 19:42:08" |
| create on........ "HP-UX B.11.31 U ia64" |
| Database version. "OCI_112, 11.2.0.3.0, V1, default" |
| |
| Patch level. 500 |
| Patch text.. " " |
| |
| Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*" |
| SAP database version. 720 |
| Operating system..... "HP-UX B.11.31" |
| |
| Memory consumption |
| Roll.... 0 |
| EM...... 12569376 |
| Heap.... 0 |
| Page.... 16384 |
| MM Used. 1126096 |
| MM Free. 3061024 |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|User and Transaction |
| Client.............. 150 |
| User................ "FORKERGI" |
| Language key........ "P" |
| Transaction......... "MIGO " |
| Transaction ID...... "52A8B251E6FC2F61E10000000AB60A32" |
| |
| EPP Whole Context ID.... "001E0BFDA2F61ED398E5B8314462D100" |
| EPP Connection ID....... 00000000000000000000000000000000 |
| EPP Caller Counter...... 0 |
| |
| Program............. "????????????????????????????????????????" |
| Screen.............. " " |
| Screen Line......... 0 |
| Debugger Active..... "none" |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Information on where terminated |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Contents of system fields |
----------------------------------------------------------------------------------------------------
|Name |Val. |
----------------------------------------------------------------------------------------------------
|SY-SUBRC|0 |
|SY-INDEX|0 |
|SY-TABIX|0 |
|SY-DBCNT|0 |
|SY-FDPOS|0 |
|SY-LSIND|0 |
|SY-PAGNO|0 |
|SY-LINNO|1 |
|SY-COLNO|1 |
|SY-PFKEY| |
|SY-UCOMM| |
|SY-TITLE| |
|SY-MSGTY| |
|SY-MSGID| |
|SY-MSGNO|000 |
|SY-MSGV1| |
|SY-MSGV2| |
|SY-MSGV3| |
|SY-MSGV4| |
|SY-MODNO|3 |
|SY-DATUM|20131212 |
|SY-UZEIT|114527 |
|SY-XPROG| |
|SY-XFORM| |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Internal notes |
| The termination was triggered in function "ab_genprog" |
| of the SAP kernel, in line 1843 of the module |
| "//bas/720_REL/src/krn/runt/abgen.c#11". |
| The internal operation just processed is " ". |
| Internal mode was started at 20131212114527. |
| Program name.........: "SAPLMIGO ". |
| Error message........: "O objeto de dados "LS_MKPF" não possui componentes com |
| o nome "MSR_ACT". |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Active Calls in SAP Kernel |
----------------------------------------------------------------------------------------------------
|Lines of C Stack in Kernel (Structure Differs on Each Platform) |
----------------------------------------------------------------------------------------------------
|(0) 0x400000000312b0b0 CTrcStack2 + 0x1d0 at dptstack.c:228 [dw.sapJED_DVEBMGS00] |
|(1) 0x400000000312b490 CTrcStack + 0x30 [dw.sapJED_DVEBMGS00] |
|(2) 0x4000000003355800 _Z16rabax_CStackSavev + 0x1c0 at abrabax.c:8695 [dw.sapJED_DVEBMGS00] |
|(3) 0x400000000335d150 ab_rabax + 0x4090 at abrabax.c:1439 [dw.sapJED_DVEBMGS00] |
|(4) 0x400000000338a580 ab_genprog + 0x1430 at abgen.c:1843 [dw.sapJED_DVEBMGS00] |
|(5) 0x40000000026df1a0 _Z7newloadPKtjPj + 0x14a0 at abload1.c:352 [dw.sapJED_DVEBMGS00] |
|(6) 0x400000000252b790 ab_load + 0x170 at abload1.c:159 [dw.sapJED_DVEBMGS00] |
|(7) 0x40000000021b89f0 ab_LoadMainProg + 0x90 at abdynpro.c:307 [dw.sapJED_DVEBMGS00] |
|(8) 0x4000000002274d20 dystartx + 0x820 at dytransact.c:1058 [dw.sapJED_DVEBMGS00] |
|(9) 0x4000000002aebd80 dy_cdiag + 0x22a0 at dynpabsv.c:1967 [dw.sapJED_DVEBMGS00] |
|(10) 0x400000000211fbe0 _Z15ab_ctransactionv + 0x3a0 at abtcod.c:699 [dw.sapJED_DVEBMGS00] |
|(11) 0x400000000285a3e0 _Z10ab_retdynpi + 0x2100 at abdynpro.c:822 [dw.sapJED_DVEBMGS00] |
|(12) 0x400000000284fe70 ab_dstep + 0x250 at abdynpro.c:637 [dw.sapJED_DVEBMGS00] |
|(13) 0x40000000024f7810 dynpmcal + 0xdb0 at dymainstp.c:2900 [dw.sapJED_DVEBMGS00] |
|(14) 0x40000000025531d0 dynppai0 + 0x670 at dymainstp.c:1227 [dw.sapJED_DVEBMGS00] |
|(15) 0x40000000028a3d00 dynprctl + 0x330 at dymainstp.c:471 [dw.sapJED_DVEBMGS00] |
|(16) 0x400000000240aa30 dynpen00 + 0x990 at dymain.c:2070 [dw.sapJED_DVEBMGS00] |
|(17) 0x4000000002b0c8e0 Thdynpen00 + 0x3c0 at thxxhead.c:5291 [dw.sapJED_DVEBMGS00] |
|(18) 0x40000000029a0180 TskhLoop + 0x3bc0 at thxxhead.c:4296 [dw.sapJED_DVEBMGS00] |
|(19) 0x4000000002c53270 ThStart + 0x870 at thxxhead.c:1174 [dw.sapJED_DVEBMGS00] |
|(20) 0x400000000235d430 DpMain + 0x6f0 at dpxxdisp.c:1198 [dw.sapJED_DVEBMGS00] |
|(21) 0x400000000200d840 main + 0x80 at thxxanf.c:80 [dw.sapJED_DVEBMGS00] |
|(22) 0xc00000000006e9b0 main_opd_entry + 0x50 [/usr/lib/hpux64/dld.so] |
----------------------------------------------------------------------------------------------------