Hi Experts,
Can anyone please help me on this issue.?
I have 2 Queues MCEX17_1 & MCEX18_1,suddenly these 2 queues has been stucked and entries are not processing to RSA7.Because of these 2 queues,daily we are getting 300 dumps(Below is the Dump details) in R3 system.
ERROR MESSAGE: LUWs in status NOSEND must be picked up by the application.
Appreciate your help...Full Points will be assigned
ST22 DUMP:
Runtime errors MESSAGE_TYPE_X
Occurred on 12.01.2012 at 21:06:10
-
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.
-
Error analysis
-
Short text of error message:
Structures have changed (sy-subrc=2)
Technical information about the message:
Diagnosis
You are using the 'Queued Delta' update method. You cannot use
report RMBWV3nn (nn = the number of the relevant application in the
logistics cockpit) to transfer an entry from extraction queue
MCEXnn to the corresponding delta queue because one of the
structures that is being used has been changed since the document
was posted.
System Response
The entry is not transferred to the delta queue.
Procedure
See SAP Note 328181.
Procedure for System Administration
Message classe...... "MCEX"
Number.............. 194
Variable 1.......... 2
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
"SAPLMCEX" or "LMCEXU22"
"MCEX_UPDATE_18"
-
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
To obtain this, select the "Print" function on the current screen.
-
2. A suitable hardcopy prinout of the system log.
To obtain this, call the system log with Transaction SM21
and select the "Print" function to print out the relevant
part.
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, you can either use the "PRINT" command in the editor or
print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
-
System environment
-
SAP Release.............. "620"
Application server....... "awssvsmds027"
Network address.......... "10.192.0.52"
Operating system......... "SunOS"
Release.................. "5.10"
Hardware type............ "sun4u"
Character length......... 8 Bits
Pointer length........... 64 Bits
Work process number...... 1
Short dump setting....... "full"
Database server.......... "awssvsmds022"
Database type............ "ORACLE"
Database name............ "AWP"
Database owner........... "SAPR3"
Terminal................. " "
Character set............ "en_US"
SAP kernel............... "640"
Created on............... "May 29 2011 21:42:39"
Created in............... "SunOS 5.8 Generic_117350-38 sun4u"
Database version......... "OCI_920 "
Patch level.............. "378"
Patch text............... " "
Supported environment....
Database................. "ORACLE 8.1.7.., ORACLE 9.2.0.., ORACLE
10.1.0.., ORACLE 10.2.0.., ORACLE 11.2.0.."
SAP database version..... "640"
Operating system......... "SunOS 5.8, SunOS 5.9, SunOS 5.10, SunOS 5.11"
-
User, transaction...
-
Client.............. 420
User................ "BC-BATCH"
Language key........ "E"
Transaction......... " "
Program............. "SAPLMCEX"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
-
Information on where terminated
-
The termination occurred in the ABAP program "SAPLMCEX" in "MCEX_UPDATE_18".
The main program was "RMCEXUP1 ".
The termination occurred in line 156 of the source code of the (Include)
program "LMCEXU22"
of the source code of program "LMCEXU22" (when calling the editor 1560).
The program "SAPLMCEX" was started as a background job.
-
Source code extract
-
001260
001270 IF NOT I_DDIC_HASH IS INITIAL.
001280
001290 IF gf_tmsp_hash_ok IS INITIAL.
001300
001310 CALL FUNCTION 'MCEX_GEN_AND_CHECK_HASH'
001320 EXPORTING
001330 I_FUNCNAME = 'MCEX_UPDATE_18'
001340 I_COLLECTIVE_RUN = 'X'
001350 I_APPLICATION = '18'
001360 I_STORED_DDIC_HASH = I_DDIC_HASH
001370 I_STORED_TMSP_HASH = I_TMSP_HASH
001380 IMPORTING
001390 E_DDIC_HASH = I_DDIC_HASH
001400 E_TMSP_HASH = lf_TMSP_HASH
001410 EXCEPTIONS
001420 HASH_COMPARE_OK = 1
001430 HASH_COMPARE_NOT_OK = 2
001440 NO_INTERFACE = 3
001450 HASH_ERROR = 4
001460 DDIC_ERROR = 5
001470 OTHERS = 6 .
001480
001490 IF I_TMSP_HASH = lf_tmsp_hash.
001500 gf_tmsp_hash_ok = true.
001510 ENDIF.
001520 case sy-subrc.
001530 when 0. " Compare OK - do nothing
001540 when 1. "Compare OK - do nothing
001550 when 2. " Compare not ok - abort
-
> message x194(mcex) with sy-subrc.
001570 when others.
001580 message x193(mcex) with sy-subrc.
001590 endcase.
001600 endif.
001610 endif.
001620 * HASH*****************************************************************
001630
001640 *-- Internal tables must be global due to IMPORT routines
001650 REFRESH: mc18i00ntf_tab,
001660 mc18i00itm_tab,
001670 mc18i00cse_tab,
001680 mc18i00tsk_tab,
001690 mc18i00act_tab.
001700 CLEAR: mc18i00ntf_tab,
001710 mc18i00itm_tab,
001720 mc18i00cse_tab,
001730 mc18i00tsk_tab,
001740 mc18i00act_tab.
001750
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.