MESSAGE_TYPE_X - In PR5
All,
I am done some code changes in Program ZEX_SAPLXRSA related to structure ZAMC11VA0ITM ,And field has been added in DS-2LIS_11_VAITM.
All chnages transported to Production System,setup tables filling done and pulled data to ODS.
In daily loads before starting loads in R/3 2LIS-02,03,11,13 V3 Jobs could be running , but today 2LIS 11 R/3 job cancelled due to shoort dump ( MESSAGE_TYPE_X ) in PR5 System.
Once this 2LIS 11 R/3 Job is in finished status only i can pull the data to BW,All my daily loads dependent on 2LIS 11(SALES Data) PLease suggest.
How could i resolve the dump(MESSAGE_TYPE_X ) in PR5 to success the 2LIS 11 R/3 Job.
Please suggest ASAP.
Hi ,
Can you please paste the dump here?
MESSAGE_TYPE_X is a generic dump and it occurs for a variety of reasons.
Regards,
SK
Similar Messages
-
MESSAGE_TYPE_X IN BI_CONT 7.03 INSTALLATION
Hi,
i am installing bi_cont 7.03, installation stuck at xpra_excution IN SAPKIBIII4 WITH LOG BELOW
Runtime Errors MESSAGE_TYPE_X
Date and Time 13.06.2009 14:15:25
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:
System error in program LRSDG_IOBJ_DB_READF40 and form REGULAR_IOBJ_GET_
FOR_META (see long text)
Long text of error message:
Diagnosis
This internal error is an intended termination resulting from a
program state that is not permitted.
Procedure
Analyze the situation and inform SAP.
If the termination occurred when you executed a query or Web
template, or during interaction in the planning modeler, and if you
can reproduce this termination, record a trace (transaction RSTT).
For more information about recording a trace, see the documentation
for the trace tool environment as well as SAP Note 899572.
Technical information about the message:
Message class....... "BRAIN"
Number.............. 299
Variable 1.......... "LRSDG_IOBJ_DB_READF40"
Variable 2.......... "REGULAR_IOBJ_GET_FOR_META"
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" " "
"SAPLRSDG_IOBJ_DB_READ" or "LRSDG_IOBJ_DB_READF40"
"REGULAR_IOBJ_GET_FOR_META"
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 700
Application server... "test"
Network address...... "192.168.10.248"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "4x AMD64 Level"
Character length.... 8 Bits
Pointer length....... 64 Bits
Work process number.. 11
Shortdump setting.... "full"
Database server... "TEST"
Database type..... "ORACLE"
Database name..... "KIL"
Database user ID.. "SAPKIL"
Char.set.... "English_United State"
SAP kernel....... 700
created (date)... "May 31 2009 20:44:02"
create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
Database version. "OCI_10201_SHARE (10.2.0.1.0) "
Patch level. 210
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0"
Memory consumption
Roll.... 16128
EM...... 62848560
Heap.... 0
Page.... 40960
MM Used. 37341136
MM Free. 12932688
User and Transaction
Client.............. 000
User................ "DDIC"
Language key........ "E"
Transaction......... " "
Transactions ID..... "85F657DE8ED8F1739C680015170F3C4D"
Program............. "SAPLRSDG_IOBJ_DB_READ"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "SAPLRSDG_IOBJ_DB_READ" - in
"REGULAR_IOBJ_GET_FOR_META".
The main program was "RDDEXECU ".
In the source code you have the termination point in line 31
of the (Include) program "LRSDG_IOBJ_DB_READF40".
The program "SAPLRSDG_IOBJ_DB_READ" was started as a background job.
Job Name....... "RDDEXECL"
Job Initiator.. "DDIC"
Job Number..... 14151900
Source Code Extract
Line SourceCde
1 ----
2 * INCLUDE LRSDG_IOBJ_DB_READF40 *
3 ----
4
5
6 ----
7 * Form REGULAR_IOBJ_GET_FOR_META
8 ----
9 * read a regular InfoObject as Meta InfoObject
10 ----
11 * --> I_INFOCUBE InfoCube
12 * --> I_IOBJNM InfoObject
13 * <-> C_T_COB_PRO InfoCube specific InfoObject properties
14 ----
15 FORM regular_iobj_get_for_meta USING i_infocube TYPE rsinfocube
16 i_iobjnm TYPE rsiobjnm
17 CHANGING c_t_cob_pro TYPE rsd_t_cob_pro.
18
19 DATA: l_s_cob_pro TYPE rsdcobpro.
20
21 CALL FUNCTION 'RSD_IOBJ_INCL_ATR_NAV_GET'
22 EXPORTING
23 i_iobjnm = i_iobjnm
24 i_objvers = rs_c_objvers-active
25 IMPORTING
26 e_s_cob_pro = l_s_cob_pro
27 EXCEPTIONS
28 iobj_not_found = 1
29 illegal_input = 2.
30 IF sy-subrc <> 0.
>>>>> MESSAGE x299(brain) WITH 'LRSDG_IOBJ_DB_READF40'
32 'REGULAR_IOBJ_GET_FOR_META'.
33 ENDIF.
34
35 * time charact --> time dimension / In BEX not visible
36 IF i_iobjnm = rsd_c_chanm-date OR
37 i_iobjnm = rsd_c_timnm-calday.
38 l_s_cob_pro-chasel = rsd_c_chasl-not_allowed.
39 l_s_cob_pro-chanav = rsd_c_chanv-not_allowed.
40
41 ** from 3.0 these InfoObjects are marked as META objects
42 * l_s_cob_pro-iobjtp = rsd_c_objtp-meta.
43 * the olap processor uses 0DATE / 0CALDAY as default for exceptional aggregation -
44 * therefore it has to be in the cobpro
45 * but it must not be of type META, since then day of validity logic
46 * does not work
47 * solution for 3.0: OLAP processor uses the flags CHASEL and CHANAV to determine
48 * if 0DATE / 0CALDAY is part of the infocube
49
50 * leave dimension empty
Contents of system fields
Name Val.
SY-SUBRC 1
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 Execute Post-Import Methods and XPRAs for Transport Request
SY-MSGTY X
SY-MSGID BRAIN
SY-MSGNO 299
SY-MSGV1 LRSDG_IOBJ_DB_READF40
SY-MSGV2 REGULAR_IOBJ_GET_FOR_META
SY-MSGV3
SY-MSGV4
SY-MODNO 0
SY-DATUM 20090613
SY-UZEIT 141519
SY-XPROG SAPLSYST
SY-XFORM SYSTEM_HOOK_OPEN_DATASET
Active Calls/Events
No. Ty. Program Include Line
Name
16 FORM SAPLRSDG_IOBJ_DB_READ LRSDG_IOBJ_DB_READF40 31
REGULAR_IOBJ_GET_FOR_META
15 FUNCTION SAPLRSDG_IOBJ_DB_READ LRSDG_IOBJ_DB_READU32 101
RSD_ALL_META_IOBJ_GET
14 METHOD CL_RSD_DTA====================CP CL_RSD_DTA====================CM021 658
CL_RSD_DTA=>BUILD_SNG_DTA_PRO
13 METHOD CL_RSD_DTA====================CP CL_RSD_DTA====================CM00H 90
CL_RSD_DTA=>BUILD_DTA_PRO
12 METHOD CL_RSD_DTA====================CP CL_RSD_DTA====================CM00I 110
CL_RSD_DTA=>UPDATE_DTA_BUF
11 METHOD CL_RSD_CUBE===================CP CL_RSD_CUBE===================CM006 197
CL_RSD_CUBE=>IF_RSD_DTA~DTA_GET_INFO
10 METHOD CL_RSD_DTA====================CP CL_RSD_DTA====================CM001 157
CL_RSD_DTA=>IF_RSD_DTA~DTA_GET_INFO
9 FORM SAPLRSDI LRSDIF20 63
COB_GET_FROM_BUFFER
8 FUNCTION SAPLRSDI LRSDIU05 42
RSD_COB_PRO_GET
7 FORM SAPLRSDDK6 LRSDDK6F01 342
CONVERT_A_TO_M_VERSION
6 FUNCTION SAPLRSDDK6 LRSDDK6U06 89
RS_DAGR_AFTER_IMPORT
5 FUNCTION SAPLRSVERS LRSVERSU07 102
RS_AFTER_IMPORT_D
4 FORM SAPLSCTS_EXE_EXP LSCTS_EXE_EXPF02 351
CALL_IMP_METHODS_IN_CLIENT
3 FORM SAPLSCTS_EXE_EXP LSCTS_EXE_EXPF02 87
CALL_IMP_METHODS
2 FUNCTION SAPLSCTS_EXE_EXP LSCTS_EXE_EXPU02 103
TRINT_CALL_AFTER_IMP_METHOD
1 EVENT RDDEXECU RDDEXECU 168
START-OF-SELECTION
PLEASE HELP ME OUT TO SOLVE IT I HAVE GONE THROUGH SIMILAR POST and the notes there is corrction but how to implement the correction i dont know
sunilhi,
i would request yiu all to pay attention on this and help me out
CALL FUNCTION 'RSD_IOBJ_INCL_ATR_NAV_GET'
EXPORTING
i_iobjnm = i_iobjnm
i_objvers = rs_c_objvers-active
IMPORTING
e_s_cob_pro = l_s_cob_pro
EXCEPTIONS
iobj_not_found = 1
illegal_input = 2.
IF sy-subrc <> 0.
MESSAGE x299(brain) WITH 'LRSDG_IOBJ_DB_READF40'
'REGULAR_IOBJ_GET_FOR_META'.
ENDIF.
+ time charact --> time dimension / In BEX not visible+*
IF i_iobjnm = rsd_c_chanm-date OR
i_iobjnm = rsd_c_timnm-calday.
l_s_cob_pro-chasel = rsd_c_chasl-not_allowed.
l_s_cob_pro-chanav = rsd_c_chanv-not_allowed.
+* from 3.0 these InfoObjects are marked as META objects+*
+ l_s_cob_pro-iobjtp = rsd_c_objtp-meta.+*
+ the olap processor uses 0DATE / 0CALDAY as default for exceptional aggregation -+*
+ therefore it has to be in the cobpro+*
+ but it must not be of type META, since then day of validity logic+*
+ does not work+*
+ solution for 3.0: OLAP processor uses the flags CHASEL and CHANAV to determine+*
+ if 0DATE / 0CALDAY is part of the infocube+**
PLEASE HELP WITH SOME WORK AROUND
sanjeev -
ABAP program "SAPLCNTL" in "CHECK_OO": MESSAGE_TYPE_X
Hi,
I have a problem with a program with ALV-list. Sometimes it terminates with a dump. I can not reproduce the dumps and I can not find the reason for it. I do not know, if it only terminates on some clients.
In the program the alv table is refreshed with CL_GUI_ALV_GRID=>REFRESH_TABLE_DISPLAY. After this there is also a statement CALL METHOD cl_gui_cfw=>flush.
Can anyone help?
Kindly regards
Frank
Runtime Error MESSAGE_TYPE_X
Date and Time 11.11.2008 11:24:28
ShrtText
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?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
is especially useful if you want to keep a particular message.
Error analysis
Short text of error message:
Control Framework: Invalid Processing of ABAP Object Control
Technical information about the message:
Diagnosis
You want to edit a control created with ABAP objects techniques
(class-based Control Framework) using a function module (function
module-based Control Framework). The system does not support this.
The Class ID of the control is SAP.DataProvider.1.
System response
The transaction is terminated.
Procedure
Contact the person responsible for the SAP System.
Message classe...... "DC"
Number.............. 007
Variable 1.......... "SAP.DataProvider.1"
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
Variable 3.......... " "
Variable 4.......... " "
How to correct the error
Probably the only way to eliminate the error is to correct the program.
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"MESSAGE_TYPE_X" C
"SAPLCNTL" or "LCNTLF01"
"CHECK_OO"
If you cannot solve the problem yourself and you wish to send
an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
To obtain this, select in the current display "System->List->
Save->Local File (unconverted)".
2. A suitable printout of the system log
To obtain this, call the system log through transaction SM21.
Limit the time interval to 10 minutes before and 5 minutes
after the short dump. In the display, then select the function
"System->List->Save->Local File (unconverted)".
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, select the Editor function "Further Utilities->
Upload/Download->Download".
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
System environment
SAP Release.............. "640"
Application server....... "gl3ap4"
Network address.......... "194.69.46.206"
Operating system......... "AIX"
Release.................. "5.3"
Hardware type............ "00C2809E4C00"
Character length......... 16 Bits
Pointer length........... 64 Bits
Work process number...... 8
Short dump setting....... "full"
Database server.......... "glince215"
Database type............ "ORACLE"
Database name............ "GL3"
Database owner........... "SAPSR3"
Character set............ "C"
SAP kernel............... "640"
Created on............... "Feb 18 2008 23:36:16"
Created in............... "AIX 1 5 00538A4A4C00"
Database version......... "OCI_920 "
Patch level.............. "221"
Patch text............... " "
Supported environment....
Database................. "ORACLE 9.2.0.*.*, ORACLE 10.1.0.*.*, ORACLE
10.2.0.*.*"
SAP database version..... "640"
Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"
Memory usage.............
Roll..................... 16192
EM....................... 16759424
Heap..................... 0
Page..................... 139264
MM Used.................. 4672968
MM Free.................. 3703952
SAP Release.............. "640"
User and Transaction
Client.............. 001
User................ "PB754"
Language key........ "D"
Transaction......... "ZVLA "
Program............. "SAPLCNTL"
Screen.............. "ZTCOCKPT 2000"
Screen line......... 4
Information on where terminated
The termination occurred in the ABAP program "SAPLCNTL" in "CHECK_OO".
The main program was "ZTCOCKPT ".
The termination occurred in line 178 of the source code of the (Include)
program "LCNTLF01"
of the source code of program "LCNTLF01" (when calling the editor 1780).
Source Code Extract
Line SourceCde
148 *---------------------------------------------------------------------*
149 * FORM %_CONTROL_DISPATCH *
150 *---------------------------------------------------------------------*
151 *
152 *---------------------------------------------------------------------*
153 * --> OKCODE *
154 *---------------------------------------------------------------------*
155 FORM %_CONTROL_DISPATCH.
156 * CALL FUNCTION 'CONTROL_DISPATCH'
157 * EXPORTING
158 * FCODE = SY-UCOMM
159 * EXCEPTIONS
160 * CB_NOT_FOUND = 1
161 * OTHERS = 2.
162 ENDFORM.
163
164 FORM REGISTERGLOBALOCXEVENT
165 USING SHELLID TYPE I EVENT TYPE I.
166 CALL METHOD OF CL_GUI_OBJECT=>H_GUI 'RegisterGlobalOCXevent'
167 NO FLUSH
168 EXPORTING #1 = SHELLID
169 #2 = EVENT.
170 ENDFORM.
171
172 form check_OO using p_handle type cntl_handle.
173 * check sy-uname = 'KSCHMIDT'.
174 call method cl_gui_cfw=>get_subscriber_by_id
175 exporting shellid = p_handle-shellid
176 exceptions others = 1.
177 if sy-subrc = 0.
>>>>> message X007 with p_handle-clsid.
179 endif.
180
181 endform.
182
183 form check_oo_2 using p_shellid type i.
184 data l_handle type cntl_handle.
185 * check sy-uname = 'KSCHMIDT'.
186 call method cl_gui_cfw=>get_subscriber_by_id
187 exporting shellid = p_shellid
188 exceptions others = 1.
189 if sy-subrc = 0.
190 call function 'CNTH_HANDLE_BY_SHELLID'
191 exporting shellid = p_shellid
192 importing h_control = l_handle
193 exceptions others = 1.
194 message X007 with l_handle-clsid.
195 endif.
196 endform.
Contents of system fields
Name Val.
SY-SUBRC 0
SY-INDEX 0
SY-TABIX 12
SY-DBCNT 1
SY-FDPOS 1
SY-LSIND 0
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY STAT2000
SY-UCOMM NSEL
SY-TITLE ZTCOCKPT Cockpit: Transporte Aufträge Lieferungen
SY-MSGTY X
SY-MSGID DC
SY-MSGNO 007
SY-MSGV1 SAP.DataProvider.1
SY-MSGV2
SY-MSGV3
SY-MSGV4
Active Calls/Events
No. Ty. Program Include Line
Name
11 FORM SAPLCNTL LCNTLF01 178
CHECK_OO
10 FUNCTION SAPLCNTL LCNTLU13 16
CONTROL_DESTROY
9 FUNCTION SAPLCNDP LCNDPU07 22
DP_DESTROY
8 FUNCTION SAPLCNDP LCNDPU10 103
DP_CONTROL_ASSIGN_TABLE
7 METHOD CL_GUI_ALV_GRID_BASE==========CP CL_GUI_ALV_GRID_BASE==========CM01U 37
CL_GUI_ALV_GRID_BASE=>SET_TOOLBAR_BUTTONS
6 METHOD CL_GUI_ALV_GRID===============CP CL_GUI_ALV_GRID===============CM01M 52
CL_GUI_ALV_GRID=>SET_TOOLBAR
5 METHOD CL_GUI_ALV_GRID===============CP CL_GUI_ALV_GRID===============CM01P 432
CL_GUI_ALV_GRID=>SOFT_REFRESH_TABLE_DISPLAY
4 METHOD CL_GUI_ALV_GRID===============CP CL_GUI_ALV_GRID===============CM00T 116
CL_GUI_ALV_GRID=>REFRESH_TABLE_DISPLAY
3 MODULE (PBO) ZTCOCKPT ZTCOCKPT 652
PBO_ALV_2000
2 FORM ZTCOCKPT ZTCOCKPT 167
ALVAUSGABE
1 EVENT ZTCOCKPT ZTCOCKPT_INC 213
START-OF-SELECTION
Chosen variables
Name
Val.
No. 11 Ty. FORM
Name CHECK_OO
SY-REPID
SAPLCNTL
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5454445422222222222222222222222222222222
310C3E4C00000000000000000000000000000000
%_VIASELSCR
0
4
P_HANDLE-SHELLID
128
0008
0000
BS_CENTER
768
0000
0030
%_DUMMY$$
0000
0000
2222
0000
FONT_ITALIC
1
0000
0001
SY-SUBRC
0
0000
0000
SY-XFORM
XAB_READ
000000000000000000000000000000
000000000000000000000000000000
544554442222222222222222222222
812F25140000000000000000000000
SY-MSGID
DC
00000000000000000000
00000000000000000000
44222222222222222222
43000000000000000000
SS_SIMPLE
11
0000
000B
SS_BLACKRECT
4
0000
0004
SPACE
0
0
2
0
SY-MSGNO
007
000
000
333
007
SY-MSGV1
SAP.DataProvider.1
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
54524676576766672322222222222222222222222222222222
310E414102F69452E100000000000000000000000000000000
P_HANDLE-CLSID
SAP.DataProvider.1
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
5452467657676667232222222222222222222222222222222222222222222222222222
310E414102F69452E10000000000000000000000000000000000000000000000000000
SY-MSGV2
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
SY-MSGV3
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
SY-MSGV4
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
No. 10 Ty. FUNCTION
Name CONTROL_DESTROY
NO_FLUSH
X
0
0
5
8
H_CONTROL
OBJHOLE2## 7263 ####
00000000FF000000000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000FF000000000000000000000000000000000000000000000000000000000000000000000000000000000000
44444443FF222222222222222222222222222222222223333222222222222222222222222222222222222222080022
F2A8FC52FF000000000000000000000000000000000007263000000000000000000000000000000000000000000A00
BS_DEFPUSHBUTTON
1
0000
0001
BS_LEFT
256
0000
0010
THIS_DUMMY_VALUE
0
0000
0000
BS_PUSHBUTTON
0
0000
0000
H_CONTROL-OBJ+16(4)
-1
FFFF
FFFF
SYST-REPID
SAPLCNTL
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5454445422222222222222222222222222222222
310C3E4C00000000000000000000000000000000
H_CONTROL-HANDLE_TYPE
NO_OC
0000000000
0000000000
4454422222
EFFF300000
CNTL_TYPE_OCX
OCX
0000000000
0000000000
4452222222
F380000000
CNTL_TRUE
1
0000
0001
IS_ITSAC_767A497173BF11D28BB
0
0
2
0
AC_EXPORTS_4E238C5273BF11D28BB
Table[initial]
AC_EXPO_WA_4E238C5273BF11D28BB
000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222233333333322222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
No. 9 Ty. FUNCTION
Name DP_DESTROY
H_DP
OBJHOLE2## 7263 ####
00000000FF000000000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000FF000000000000000000000000000000000000000000000000000000000000000000000000000000000000
44444443FF222222222222222222222222222222222223333222222222222222222222222222222222222222080022
F2A8FC52FF000000000000000000000000000000000007263000000000000000000000000000000000000000000A00
G_STRETCH_UNICODE_COLS_VALID
X
0
0
5
8
%_DUMMY$$
0000
0000
2222
0000
SY-SUBRC
0
0000
0000
SYST-REPID
SAPLCNDP
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5454444522222222222222222222222222222222
310C3E4000000000000000000000000000000000Hi Frank,
I doubt it is related to function 'LVC_FIELDCATALOG_MERGE' since the current SAP help documentation talks about using this function for the purpose that I'm sure you are using it. The short dump states that the problem is caused by the use of an "old" function-module-based control framework function combined with the class-based OO CFW.
Diagnosis
You want to edit a control created with ABAP objects techniques
(class-based Control Framework) using a function module (function
module-based Control Framework). The system does not support this.
If you look at the call sequence in the short dump, function module 'CONTROL_DESTROY' is being called (which then calls function 'CHECK_OO' from which the error is sent). Function module 'CONTROL_DESTROY' is in function group CNTL which is part of the "old" function-module-based CFW.
Since the 'CONTROL_DESTROY' function is ultimately called as a result of your Z-program legitimately calling the standard SAP method CL_GUI_ALV_GRID=>REFRESH_TABLE_DISPLAY, I'd say you might want to consider opening a customer message with SAP providing as much detail and background as possible. But before you bother to do that (or while you are waiting to hear back from SAP) you may want to double-check your Z-program to make sure you aren't calling some other function modules from function groups CNTL or CNT0 (the "old" CFW function modules).
I've included just the call sequence from your short dump here for easier reference. Notice the order of the calls from 1 to 11, ending with functions 'CONTROL_DESTROY' and 'CHECK_OO'. I think 'CONTROL_DESTROY' may be causing the problem (??):
Active Calls/Events
No. Ty. Program Include Line
Name
11 FORM SAPLCNTL LCNTLF01 178
CHECK_OO
10 FUNCTION SAPLCNTL LCNTLU13 16
CONTROL_DESTROY
9 FUNCTION SAPLCNDP LCNDPU07 22
DP_DESTROY
8 FUNCTION SAPLCNDP LCNDPU10 103
DP_CONTROL_ASSIGN_TABLE
7 METHOD CL_GUI_ALV_GRID_BASE==========CP CL_GUI_ALV_GRID_BASE==========CM01U 37
CL_GUI_ALV_GRID_BASE=>SET_TOOLBAR_BUTTONS
6 METHOD CL_GUI_ALV_GRID===============CP CL_GUI_ALV_GRID===============CM01M 52
CL_GUI_ALV_GRID=>SET_TOOLBAR
5 METHOD CL_GUI_ALV_GRID===============CP CL_GUI_ALV_GRID===============CM01P 432
CL_GUI_ALV_GRID=>SOFT_REFRESH_TABLE_DISPLAY
4 METHOD CL_GUI_ALV_GRID===============CP CL_GUI_ALV_GRID===============CM00T 116
CL_GUI_ALV_GRID=>REFRESH_TABLE_DISPLAY
3 MODULE (PBO) ZTCOCKPT ZTCOCKPT 652
PBO_ALV_2000
2 FORM ZTCOCKPT ZTCOCKPT 167
ALVAUSGABE
1 EVENT ZTCOCKPT ZTCOCKPT_INC 213
START-OF-SELECTION
Regards,
Jamie
P.S. Please report back here if you find a solution (or if SAP finds one as a result of your customer message). -
ABAP MESSAGE_TYPE_X -DUmp Due to Change in hiring process for HK ?
Hi,
I changed the Hiring process , just added new infotype 0105 into the process for HK , after that i got an ABAP "MESSAGE_TYPE_X" dump when i tried to save PA30 .
See the below Error :
with the key 50002134567880 9999123119712134256206528473C_VBA in
table PA0342. It is possible that the record does not exist. The
following are a few of the possible causes for this:
o The code in table PA0342 is not correctly specified in the data
dictionary (SE11). Compare with another PAnnnn table.
o An infotype may have an additional view infotype for which the
record is not available. This situation can occur when system
settings for infotype views (T582V) are changed.
o Problems with database.
o There may be other causes.Try running the report rpu03420 for that pernr. Anyway 0342 is an infotype specific to HongKong.
~Suresh -
MESSAGE_TYPE_X while running t-code RSPCM
Recently we have refreshed our BI stage system and after refresh RSPCM t-code throwing the dump MESSAGE_TYPE_X.
We have analyzed the ABAP dump and found the OSS note 1381311 to resolve the problem. As per the note the issue is occurring due to transaction BDLS was used to rename the source system after system refresh.
As per OSS note 1381311, we cannot proceed with supportpack, so we planned to apply the note via correcction. While applying the note, SNOTE requesting to implement the following SAP notes as a prerequsite. Please let us know which are all
the notes needs to be implemented to fix the problem.
Awaiting your earliest reply.
Current level of support pack in SBI is SAPKW70018Hi Srini,
Juan is right , You have to update the SAP GUI with latest patch.
One more thing the TCode RSPCM can be executed without an issue in our Production System
Gui PAtch is also depend on SAP application patch & sap kernal
It seems there is patch difference in Developement & production system
Thanks
Anil
Edited by: Anil Bhandary on Oct 22, 2009 6:57 PM -
Hello Experts
I am encountering below dump in development server , even after required settings being done in RZ12 by basis team.
BI develoment is recently refreshed from quality.
Dump:MESSAGE_TYPE_X
Analysis:
Invalid PBT server group name: BWXXX
Technical information about the message:
Diagnosis
The system tried to initialize the environment for processing
parallel RFCs using the function module SPBT_INITIALIZE. The server
group name specified was found to be invalid. The server group name
describes a group of servers on which the parallel RFCs should be
processed.
System response
Procedure
You can use Transaction RZ12 to determine which PBT server groups
are configured in your system. You should only use one of the
server group names listed there to process parallel RFCs.
Anybody has faced such kind of issue?Hi Kanchan,
This error means function module SPBT_INITIALIZE is being run with an incorrect GROUP_NAME parameter.
To verify this, you can goto transaction se37 and run function SPBT_INITIALIZE with same group name, & you should get the same dump directly.
Please do following steps to solve this problem.
1. In RSA1, choose the affected ODS object under InfoProvider and go to the manage screen
2. In the menu choose Goto -> ODS Object Customizing
3. Maintain the right Server Group
Also, make sure that the name of the server group is in upper case in RSODSO_SETTINGS.
Make sure that this note has been implemented:
1292280 P21:BATCH: Dialog server group permitted in uppercase only
The dump can also happen due to improper resource allocation, so please also check:
727709 MESSAGE_TYPE_X short dump and SPBT_INITIALIZE
356750 module SPBT_INITIALIZE generates short dump
74141 Resource Management for tRFC and aRFC
Please check the profile parameter settings as described in Note 74141 to ensure that every server can provide at least one dialog process for processing.
Rgds,
Colum
Edited by: Colum Cronin on Mar 19, 2010 8:52 AM -
Short dump MESSAGE_TYPE_X in displaying data from BPC Virtualcube
Hi Experts,
I am experiencing an error when try to display data from a BPC VirtualProvider Infocube (both from Workbench and with LISTCUBE transaction).
This kind of virtualcube is auto generated by BPC.
When I do some kind of selection I obtain this error: MESSAGE_TYPE_X
Short text of error message:
System error in program SAPLRRK0 and form CHECK_KHANDLE (see long text)
Technical information about the message:
Message class....... "BRAIN"
Number.............. 299
Variable 1.......... "SAPLRRK0"
Variable 2.......... "CHECK_KHANDLE"
I have another BPC vitualprovider and this doesnu2019t happen.
I would use this cube inside a multiprovider, that has a BI cube too, and get the data through a BEx query. But the query throws the error and stopped.
I know that there could be problems with BPC structures (i.e. changes in tech name when transporting it), but at the moment I donu2019t see other solution to compare BI to BPC data.
I went through other posts in sdn forum for this issue, but I am not able to get the exact solution,
please help
Thanks,
Marco
System version:
BW: 701 level 0007
BPC: 750 level 0005Hi Lokesh,
I read the note you have indicated.
For the first note 1479393: I donu2019t have hierarchies and the error appears in a different program to what is indicated in the note. This is where terminated:
Termination occurred in the ABAP program "SAPLRRK0" - in "CHECK_KHANDLE".
The main program was "GP4LQ7N6RS4RUB6HA69UREYGPKB ".
In the source code you have the termination point in line 34
of the (Include) program "LRRK0F05".
Furthermore, there are no calculated measures nor members in the MDX statement, because I just try to display the data from the virtualcube.
For the second 1448691: yes, it could be a performance related problem. Indeed, when I apply stronger filters, the error doesnu2019t occur and I got the data. But the system is already patched to SAPKW70107.
So, do you have any other ideas?
Thanks,
Marco -
0BBP_BIGURE - MESSAGE_TYPE_X in attrib change
Hi,
When I load the 0BBP_BIGURE hierarchy from SRM 5.0 to BI 7.0 in process chain I always get a MESSAGE_TYPE_X dump in the Attrib Change. If I activate the hierarchy, I don't get an error.
I think the reason is that the RSDDCHNGPROT is not filled, but I'm not sure about this. Did anyone else have this problem ?
kind regards
PieterHello Dinesh,
Here is the most useful info in the dump
Error analysis
Short text of error message:
System error in program SAPLRSDDS and form GET_CNSID_AND_OBJECTS_2-1- (see long text)
Technical information about the message:
Message classe...... "BRAIN"
Number.............. 299
Variable 1.......... "SAPLRSDDS"
Variable 2.......... "GET_CNSID_AND_OBJECTS_2-1-"
Variable 3.......... " "
Variable 4.......... " "
kind regards
Pieter -
MESSAGE_TYPE_X error
Hello all,
We are facing an issue, that "Message_type_X " short dump occurs .
the actual short dump message is:
"MESSAGE_TYPE_X" " " |
"CL_RSQ_ISET_SERVICE===========CP" or "CL_RSQ_ISET_SERVICE===========CM016"
"EXTEND_FIELD_BUFFER" .
kindly help me..
|hi,
kindly check SAP Note 1137254 , it might be helpfult to you
also check in sm21 about system log, in ST22 check on information on where termiinated and in error analysis that will give you some clue on job which is effected
regards
laksh -
Regarding message_type_x
Hi Experts,
During Upgrade from version 4.6c to Ecc6.0
I am facing the following runtime error with the standard include
LKKBFF01.
The error is due to MESSAGE_TYPE_X in the LKKBFF01.
MESSAGE X000(0K) WITH L_MESSAGE L_LINE L_WORD.
Can any one give the solution for the above problem.
<REMOVED BY MODERATOR>
Best Regards,
venkata Siva Reddy.
Edited by: Alvaro Tejada Galindo on Apr 23, 2008 11:53 AMcheck the oss notes..
note 203388..
regards,
venkat. -
MESSAGE_TYPE_X in POS Retail
Hi,
I'm facing a short dump error is POS DM. When I read data from the remote cube using LISTCUBE / RSA3 (checking the datasource), I'm getting MESSAGE_TYPE_X error in the following line, this is due to the SY-SUBRC NE 0.
If NOT SY-SUBRC IS INITIAL.
MESSAGE X000(/POSDM/COMMON) with " " " " " ".
ENDIF.
My datasource is 0RT_PA_TRAN_CON_REM
Please let me know if there is any OSS for this.
Thanks,
ChandranHi,
This behaviour can be observed if there were changes done to tablespace in the target system during deletion (for example: the tablespace assigned to ZAGILE_ECO does not exist anymore). Do check for ORA-00959 errors in the system logs in such a situation.
Also check if the table ZAGILE_ECO has already been deleted. In that case, you can just ignore the error and change the status of the activity to complete via tha troubleshooter.
Regards,
Suman -
ABAP Runtime error MESSAGE_TYPE_X in process chain
in our daily load process chain we have a level where datas are getting loaded in to a cube from 4 dso thru dtp. in this level the DTP fails approximately twice in a week. the DTP is shown in red in the log view. when we check the message its showin MESSAGE_TYPE_X ABAP runtime error.
if we give repeat it runs sucessfully and the following process are going well.
do u ppl have any ideas abt this.Hi,
This failure would happen for many reasons, like,
Source system connection failure
Short dump.
System overload
Non availability od work processes as a reasonthe load would have been timed out.
Locked due to another load.
That is the reason as to which the load when repeated is successful, as by then,
The source connection would have been restored
there would be free processes available
The other load would have completed.
Regards,
Savitha -
Message_type_x short dump while deleting request from infocube
Hi,
While deleting one of the erroneous requests from some infocubes,
system is resulting in short dump "MESSAGE_TYPE_X".
This is happening only with respect to some infocubes.
Description of short dump:
Short text of error message:
System error in program RSMDATASTATE and form RSM_DATASTATE_CHECK-5- (see long text)
Can any one of you please help with this?
Regards,
Nilima RodriguesHi NILIMA,
I got same problem with my InfoPackage last month with same error msg.
that error come due to data inconstancy in data base table.
in my case i am unable to open my InfoPackage and after double clicking it was giving dump with same error.
If u know abap then just change the sy-subrc value from 4 to 0 before dump line code it will resolve your problem.
for this on dump screen click on debugger button then it opens your code and shows line on which u getting dump with table name check your entry in table ok
if u unable u find table then do one thing just put break point before dump line and open fresh rsa1 and go to same cube and double click it will stop on your debugger point just press f5 button it shos sy-subrc 4 convert it to 0 and press edit button and press f8 .
Regards
Ankit -
ABAP/4 processor: MESSAGE_TYPE_X
Hi Friends,
I have put the process chains for Transfer exchange rate
1) first i have prepare start Variant -- Immediate -- save
2) abap program drag and drop : program name given : RSIMPCURR
varient create and save schedule .
some errors are shown
ABAP/4 processor: MESSAGE_TYPE_X
Step 001 started (program RSPROCESS, variant &0000000002503, user ID BWREMOTE)
Thanks.Are you loading the selection values of this program?
Check and confirm by running the program manually in SE38?
Thanks. -
ABAP/4 processor: MESSAGE_TYPE_X while creating bulk shipment cost
Hi All,
while bulk shipment cost creation using SAP program 'ROIGTRSL' in background , some jobs are failing very raarly in prodcution, if i check in job log it's showing message 'ABAP/4 processor: MESSAGE_TYPE_X'
how to avoid this error, is there any OSS note?
regards,
DSKHi kumar,
see this link
http://www.sts.tu-harburg.de/teaching/sap_r3/ABAP4/abapdocu.txt
chk below....
Try this program RS_TRANSTRU_ACTIVATE_ALL to activate
Check if any transports imported in the system ( some one else might have transported BI objects for other requirements, they might have missed to check the dependency ). if so recollect your objects in development system and transport those objects again.
Check if any support packs or OSS notes are imported in your system. Massage type X error is so
generic error so please review the system logs( tcode : SLG1) and analyize the problem.
Cheers
nagendra
Maybe you are looking for
-
How can I eject the disc and start over and get into the OSX system?
-
Looking to pool all our songs onto one iTunes Match account. Is this possible?
-
Only 0EA of material available
Hi Gurus, Can anybody please throw some light on the error. "only 0EA of material are avialable" We are trying to send a returns PO to a vendor. The stock is now sitting in blocked stock. The delivery is created but the delivery quantity and the pic
-
Loading new URL in root window
Hi, I want to automatically download a zipfile from a certain location. Want i wanted to do is when the user click a button, i load new url in the current (root window) which will automatically show the download popup from mozilla/IE. Is there a way
-
I've got two iTunes accounts with apps under each - how can I reconcile them both under one account and one email address?