When performing the LT03 for a delivery order

Question

The system runs forever; then ABAP dumps.  None of us here are experts in ABAP at all.  This is not happening in our QA client only in the production client so I am at a lsot as to why.  My initial though was due to changing serialization level from one to none but when I tried to duplicate the error in QA, it works,  Below is the message ...anyone with advice?
Short text
Time limit exceeded.
What happened?
The program "SAPLZAF_MM_SERIAL" has exceeded the maximum permitted runtime
without
interruption and has therefore been terminated.
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
After a specific time, the program is terminated to make the work area
available to other users who may be waiting.
This is to prevent a work area being blocked unnecessarily long by, for
example:
- Endless loops (DO, WHILE, ...),
- Database accesses with a large result set
- Database accesses without a suitable index (full table scan)
The maximum runtime of a program is limited by the system profile
parameter "rdisp/max_wprun_time". The current setting is 1800 seconds. If this
time limit is
exceeded, the system attempts to cancel any running SQL statement or
signals the ABAP processor to stop the running program. Then the system
waits another 60 seconds maximum. If the program is then still active,
the work process is restarted.
How to correct the error
Programs with long runtime should generally be started as background
jobs. If this is not possible, you can increase the system profile
parameter "rdisp/max_wprun_time".
Depending on the cause of the error, you may have to take one of the
following measures:
- Endless loop: Correct program;
- Dataset resulting from database access is too large:
Instead of "SELECT * ... ENDSELECT", use "SELECT * INTO internal table
(for example);
- Database has unsuitable index: Check index generation.
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:
"TIME_OUT" " "
"SAPLZAF_MM_SERIAL" or "LZAF_MM_SERIALU01"
"ZAF_MM_SERIAL"
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... "WIC-PD-ECCSCS"
Network address...... "10.200.1.245"
Operating system..... "Linux"
Release.............. "2.6.16.60-0.39.3-smp"
Hardware type........ "x86_64"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "WIC-PD-ORC-01"
Database type..... "ORACLE"
Database name..... "ECP"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Aug 23 2009 20:22:37"
create on........ "Linux GNU SLES-9 x86_64 cc3.3.3"
Database version. "OCI_102 (10.2.0.2.0) "
Patch level. 221
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "Linux 2.6"
Memory consumption
Roll.... 16192
EM...... 20949240
Heap.... 0
Page.... 57344
MM Used. 10428296
MM Free. 2138248
User and Transaction
Client.............. 400
User................ "TNIDA"
Language key........ "E"
Transaction......... "LT03 "
Transactions ID..... "4C7C27CEFAB745B2E10000000AC801F1"
Program............. "SAPLZAF_MM_SERIAL"
Screen.............. "SAPML03T 0102"
Screen line......... 68
Information on where terminated
Termination occurred in the ABAP program "SAPLZAF_MM_SERIAL" - in
"ZAF_MM_SERIAL".
The main program was "SAPML03T ".
In the source code you have the termination point in line 33
of the (Include) program "LZAF_MM_SERIALU01".
Source Code Extract
Line SourceCde
3 ""Local Interface:
4 *" IMPORTING
5 *" REFERENCE(LGORT) TYPE LGORT_D OPTIONAL
6 *" REFERENCE(WERKS) TYPE WERKS_D OPTIONAL
7 *" REFERENCE(MATNR) TYPE MATNR OPTIONAL
8 *" REFERENCE(SERNR) TYPE GERNR OPTIONAL
9 *" REFERENCE(LGNUM) TYPE LGNUM OPTIONAL
10 *" EXPORTING
11 *" REFERENCE(LGPLA) TYPE LGPLA
12 *"----
13
14
15 REFRESH: it_objk, it_ser03, it_lqua.
16
17 * Select serial number for all material documents
18 SELECT * FROM objk
19 INTO TABLE it_objk
20 WHERE taser = 'SER03'
21 AND sernr eq sernr
22 AND matnr eq matnr.
Select documents details for serial numbers.
25 SELECT * FROM ser03
26 INTO TABLE it_ser03
27 FOR ALL ENTRIES IN it_objk
28 WHERE obknr = it_objk-obknr
29 AND werk = werks
30 AND lagerort = lgort.
31
32 * Select storage bin details for all selected materials documents.
>>>>> SELECT * FROM lqua
34 INTO TABLE it_lqua
35 FOR ALL ENTRIES IN it_ser03
36 WHERE wenum = it_ser03-mblnr
37 AND lgnum = lgnum.
38 * AND lgpla = lgpla.
39
40
41 * Populate the output table
42 LOOP AT it_objk INTO wa_objk.
43 READ TABLE it_ser03 INTO wa_ser03 WITH KEY obknr = wa_objk-obknr.
44 IF sy-subrc = 0.
45 READ TABLE it_lqua INTO wa_lqua WITH KEY wenum = wa_ser03-mblnr
46 matnr = wa_objk-matnr.
47 IF sy-subrc = 0.
48 wa_ser-werks = wa_lqua-werks.
49 wa_ser-lgort = wa_lqua-lgort.
50 wa_ser-matnr = wa_lqua-matnr.
51 wa_ser-sernr = wa_objk-sernr.
52 wa_ser-lgnum = wa_lqua-lgnum.
Contents of system fields
Name Val.
SY-SUBRC 0
SY-INDEX 1
SY-TABIX 10
SY-DBCNT 33702
SY-FDPOS 40
SY-LSIND 0
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY 31
SY-UCOMM TATB
SY-TITLE Create Transfer Order for Delivery: Generate TO Item
SY-MSGTY E
SY-MSGID L9
SY-MSGNO 202
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO 0
SY-DATUM 20100831
SY-UZEIT 084745
SY-XPROG SAPCNVE
SY-XFORM CONVERSION_EXIT

Answer 1

I managed to remove the serial numbers from the delivery and then tried LT03.  It ran for a long time however; I did manage to get it thru that way.  Added the serial numbers back in vlo02n and post goods issue just fine.
Still curious as why the system is lagging so long and woul ABAP out if a serial numebr is in the LT03 when trying to create a TO...please any clues would be good.