Job SAP_COLLECTOR_FOR_PERFMONITOR - short dump (DBIF_SETG_SQL_ERROR)

Hi gurus,
Good day.
I would like to ask for your help with regard to the short dump that we experienced with Job SAP_COLLECTOR_FOR_PERFMONITOR (program RSCOLL00). The error is DBIF_SETG_SQL_ERROR.
Date       Time     Message text
24.11.2008 02:30:39 Job started
24.11.2008 02:30:39 Step 001 started (program RSCOLL00)
24.11.2008 02:30:44 ABAP/4 processor: DBIF_SETG_SQL_ERROR
24.11.2008 02:30:44 Job cancelled
ORA-01455 is said to be the reason why we encountered DBIF_SETG_SQL_ERROR.
Database error text........: "ORA-01455: converting column overflows integer datatype"
Can you advise an OSS Note or certain solution that can fix this issue? Thank you very much!

This looks like an SAP Upgrade ECC 6 Problem, right?
Do you have any idea where I can check the date when the ECC 6 upgrade or patch has been made?
I'm an ABAPer and to be honest, currentlly, I don't have any idea if the client really did an ECC 6 upgrade --- when they did it. I will just check the table that you sent.
I just had the impression that it might be due to an ECC 6 Upgrade since I saw this case over the Internet:
"DBIF_SETG_SQL_ERROR" and "ORA-03106: fatal two-task communication protocol error" after ERP 6.0 Upgrade ( http://sap.ittoolbox.com/groups/technical-functional/sap-basis/dbif_setg_sql_error-and-ora-03106-fatal-two-task-communication-protocol-error-after-erp-60-upgrade-1640408 ).
Yes, we are also experiencing DBIF_SETG_SQL_ERROR (ORA-03106). But, I'm taking care of DBIF_SETG_SQL_ERROR (ORA-01455).
By the way, I saw that jobs EU_PUT and EU_REORG are being executed in background every morning at around 1 AM. And we are receiving the error DBIF_SETG_SQL_ERROR (ORA-01455) at around 2 AM - 3 AM, and a few at around 3 AM - 5 AM.
With these I have two questions:
(1) Do you think we still need to rerun EU_PUT and EU_REORG? Perhaps before 2 AM ?
(2) Do you think this is a Basis Issue and nothing to do with ABAP anymore?
Thank you very much!

Similar Messages

ABAP/4 processor: UNCAUGHT_EXCEPTION - Activation job cancelled short dump

Hi All,
I loaded data to the new table of ODS successfully. But the data is not available for reporting.
When i try to activate the request,it shows no error bt neither does data *** to active table .I checkd in sm37 for logs, it shows ABAP/4 processor: UNCAUGHT_EXCEPTION error. It shows that CX_SDB_ORA_PROGRAM_ERROR exception was raised.
I also checked in table RSODSACTREQ in SE16 and found that status was 0 (means activation successful) n operation was U (means updating) .........
The same problem persists for activation job for any ODS.......The support package has been upgraded from 11 to 14 recently.......
Please help me resolve this issue.
Regards,

Prithi,
Check out for invalid char's in the PSA.....
Check monitoring for invalid char's .. some time it will reach up to New data table and while activation it may get struc...
hope there is some prob with invalid char's aor length of char.... Special char..like @__ in PSA .
Cheer's
HVR.

Short Dumps - How to find out in which process it occured.

Hi,
I see quiet a bunch of short dumps in ST22. Like "Message Type X". I wanted to find out in which job/process short dumps have occured?
Please help me out...
Thanks in Advance....:)
Regards,
Habeeb

Hi ,
The simplest way is to double click on a particluar dump in st22 and go in details like -What happened? ,What can you do?,How to correct the error etc .
there were plenty of options available according ot that u can dig out the error and find out the cause
(tip-usually job were failed due to some Z programs ,so better way is to search for Z* ,it will give the related object or program in most of the cases.)
hope it helps....
Regards,
Chetan R

SAP job SAP_COLLECTOR_FOR_PERFMONITOR getting failed with abap dump LOAD_PROGRAM_NOT_FOUND

Dear Experts,
Background job SAP_COLLECTOR_FOR_PERFMONITOR getting failed with abap dump LOAD_PROGRAM_NOT_FOUND.
As it is hourly scheduled job and it gets finished 22 times in a day but other 2 times fails with abap dump.
Finished Job log
Job started
Step 001 started (program RSCOLL00, variant , user ID Bharath)
Clean_Plan:Cleanup of DB13 Plannings
Clean_Plan:started by RSDBPREV                       on server
Clean_Plan:Cleaning up jobs of system DEV
Clean_Plan:finished
Job finished
Failed Job Log
Job started
Step 001 started (program RSCOLL00, variant , user ID Bharath)
Internal session terminated with a runtime error (see ST22).
Kindly suggest on this..
Thanks,
Bharath.

Dear Divyanshu,
Our system in ERP 6.0 EHP5 with SP level 10. The ABAP Dump shows below error.
|Short text                                                                                        |
|    Program "RSORA811" not found.                                                                 |
|What happened?                                                                                    |
|    There are several possibilities:                                                              |
|                                                                                                  |
|    Error in the ABAP Application Program                                                         |
|                                                                                                  |
|    The current ABAP program "RSCOLL00" had to be terminated because it has                       |
|    come across a statement that unfortunately cannot be executed.                                |
|    or                                                                                            |
|    Error in the SAP kernel.                                                                      |
|                                                                                                  |
|    The current ABAP "RSCOLL00" program had to be terminated because the                          |
|    ABAP processor detected an internal system error.                                             |
|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                                                                                    |
|    On account of a branch in the program                                                         |
|    (CALL FUNCTION/DIALOG, external PERFORM, SUBMIT)                                              |
|    or a transaction call, another ABAP/4 program                                                 |
|    is to be loaded, namely "RSORA811".                                                           |
|                                                                                                  |
|    However, program "RSORA811" does not exist in the library.                                    |
|                                                                                                  |
|    Possible reasons:                                                                             |
|    a) Wrong program name specified in an external PERFORM or                                     |
|       SUBMIT or, when defining a new transaction, a new                                          |
|       dialog module or a new function module.                                                    |
|    b) Transport error                                                                            |
|Information on where terminated                                                                   |
|    Termination occurred in the ABAP program "RSCOLL00" - in                                      |
|     "LOOP_AT_SYSTEMS_AND_REPORTS".                                                               |
|    The main program was "RSCOLL00 ".                                                             |
|                                                                                                  |
|    In the source code you have the termination point in line 535                                 |
|    of the (Include) program "RSCOLL00".                                                          |
|    The program "RSCOLL00" was started as a background job.                                       |
|    Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"                                               |
|    Job Initiator.. " bharath"                                                                       |
|    Job Number..... 18243400
Kindly check and suggest..
Thanks,
Bharath.

Short dump while executing job SM:EXEC SERVICES for EWA alert generation

Hello All,
I'm getting short dump error while executing job SM:EXEC SERVICES for EWA alert generation.I'm using EHP1@SP22 of Sol Man.
Please find the logs
Error in the ABAP Application Program
The current ABAP program "SAPLDSVAS_PROC" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "RDSVASCABAP_TRANS__________073
" in include "RDSVASIABAP_TRANS__________073 " in
line 1782:
"Field "STATEMENT_SUMMARY001019" is unknown. It is neither in one of th"
"e specified tables nor defined by a "DATA" statement. "DATA" statement"
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 "SAPLDSVAS_PROC" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
If anyone came across such kind of dump, please reply asap, due to this, i could not generate EWA report for R/3 system 6.04.
Thanks,
Anand.

>
Anand Tigadikar wrote:
> Thx Paul, but i already did checked this note and its not solving my issue
Dear Anand,
Did you perform a complete service definition replacement for SDCC/SDCCN as described in the note?
These are manual steps you need to perform on the system and are not code corrections.
I would suggest you perform it, if you have not, and check the SDCCN logs to review the process ran cleanly.
Note: Please make sure SDCC_OSS is functioning and a connection to SAP can be made before
deleting the service definitions.
If you have already replaced the service defintions on the Solution Manager system, then no point doing it again. However checking a note and applying it are not the same thing. So I am uncertain if you replaced the service definitions or not. The dump you are getting in SM:EXEC SERVICES suggests its due to a problem with the service definitons. The recommendation is to replace them according to the process described in SAP Note 727998. If you have not done so please do so.
If you have successfully replaced the service definitions are you still getting the same dump, or has it possibly changed?
Regards,
Paul

How to Fetch Cancelled Jobs info along with the Short Dump Text

Hi Gurus,
I need to develop a report to fetch the cancelled jobs information for the given period. I also need to display the "Error Analysis" part of the Short Dump if it exists.
I am able to fetch the Failed Jobs information and the Job log details using the FM "BP_JOBLOG_READ". But I need to show the "Error Analysis Text" on the report , if there is any Short Dump Exists for the Dump.
Please give me your ideas to fetch the Error Analysis part of the short dump for a given Batch Job Name.
Thanks in Advance.
Best Regards,
Sumalatha

The dump information is in table SNAP. You could identify which dump you want by the date & time of the failed job - let's hope you don't have more than one dump with the same time. If it is ambiguous you could also compare the program name of the failed step with the program name in the SNAP data.
The error analysis texts are in table SNAPT keyed according to which error occurred (which is data element code FC right at the start of the first record in the SNAP data). You will have to expand out the includes, and substitute the variable codes using values from the SNAP data. There is standard code to do this that you could copy - see program SAPMS380.
To find out the details of the SAP process you could run transaction ST22 via the debugger and use the same mechanism.
best wishes
Ed
PS Note these details apply to recent systems I think there may be differences if you go back to before ?2004, but I don't have such a system so can't check. You didn't say what release you have.

DDIC job 'SAP_COLLECTOR_FOR_PERFMONITOR' fail 2 times daily

Hi Gurus,
we have an issue with DDIC job 'SAP_COLLECTOR_FOR_PERFMONITOR'.
this job daily fails at 08am and 10pm of system time throwing ST22 dump.
DDIC job log is 'Job started
Step 001 started (program RSCOLL00, variant , user ID DDIC)
Database system not supported
ABAP/4 processor: TSV_TNEW_PAGE_ALLOC_FAILED
Job cancelled
ST22 runtime Runtime error 'TSV_TNEW_PAGE_ALLOC_FAILED' occurred for users 'DDIC'.
Runtime Errors         TSV_TNEW_PAGE_ALLOC_FAILED
Date and Time          06/17/2009 20:07:11
Short text
No more storage space available for extending an internal table.
What happened?
     You attempted to extend an internal table, but the required space was
     not available.
ECC6.0,Kernel700,patch 185,oracle 10.2.0.4.0
regards
nag

Hi,
Check this note "Note 945279 - Workload Collector terminates due to memory problems"
With Regards,
Saurabh

Job SAP_COLLECTOR_FOR_PERFMONITOR canceled

Good evening everybody,
The job SAP_COLLECTOR_FOR_PERFMONITOR is being canceled hourly with the log below:
                                                                                Date       Time     Message text                                                  Message class Message no. Message type
04.08.2009 15:30:55 Job started                                                        00           516          S
04.08.2009 15:30:55 Step 001 started (program RSCOLL00, variant , user name DDIC)      00           550          S
04.08.2009 15:30:57 ABAP/4 processor: CONVT_OVERFLOW                                   00           671          A
04.08.2009 15:30:57 Job cancelled                                                      00           518          A
The dump generated in the ST22 is CONVT_OVERFLOW
Overflow when converting from 15362394
What happened?
The current ABAP/4 program "RSHOST2M " had to be terminated because
one of the statements could not be executed.
This is probably due to an error in the ABAP/4 program.
Everyone can help me to solve this issue? Our SAP version is R/3 4.6C.
Best Regards,
Fábio Karnik Tchobnian

Dear Friend,
Thanks for your help.
I apllied the part below from the note 903220
To remove the corrupted data in table MONI:
1. Call transaction ST03
2. With Goto -> Performance database -> Contents of Database
3. Select entry you want to delete
4. Further info will be '** delete**'
5. Confirm the delete
05.08.2009 Page 2 of 2
SAP Note 903220 - Short dumps CONVT_OVERFLOW in RSHOSTDB
or RSHOST2M
A sufficient way to find out which entries to delete would be:
- check when the short dump occured first
- delete the OS entries from MONI since the day before the first
short dump occured
The job SAP_COLLECTOR_FOR_PERFFMONITOR now is not being canceled anymore , however it is happening the same dump dump from a differente program after the job is finished as the log below from the ST22
ABAP runtime errors    CONVT_OVERFLOW
       Occurred on     05.08.2009 at 15:50:38
Overflow when converting from "-3.10504e+231"
What happened?
The current ABAP/4 program "SAPLSTUW " had to be terminated because
one of the statements could not be executed.
This is probably due to an error in the ABAP/4 program.
What can you do?
Note the actions and input that caused the error.
Inform your SAP system administrator.
You can print out this message by choosing "Print". Transaction ST22
allows you to display and manage termination messages, including keeping
them beyond their normal deletion date.
Error analysis
When attempting to convert the value "-3.10504e+231",
an overflow occurred.
Do you have some advice?
Best Regards
Fábio Karnik Tchobnian:

Job SAP_COLLECTOR_FOR_PERFMONITOR keep on running

Dear All,
I am facing problem in prd ,we have 2 active node the job SAP_COLLECTOR_FOR_PERFMONITOR keep on running eg   44,21sec,tan I have to cancel it manual this is suddenly. this happened with not all the hourly jobs ,but only 1 or 2 time in a day a any time.
Please find the below . Please suggest how to solved it
We are using ECC6 on oracle 10g
25     BGD     1696     Running          Yes     4               2     SWNCTOTAL     000     DDIC     Insert     SWNCMONI
Sm37 log
Job started
Step 001 started (program RSCOLL00, variant , user ID DDIC)
Clean_Plan:Cleanup of DB13 Plannings
Clean_Plan:started by RSDBPREV                       on server nodea
Clean_Plan:Cleaning up jobs of system PRD
Clean_Plan:finished
Database destination not found
Cannot determine operating system data for database
kind regards,
kumar

Dear Sunny
Thanks for you suggestion , no it happened any time and there is sufficient no of background process are free
I have see it stuck in table SWNCMONI while Insert ans i have checked the snote .Please suggest
sm21 log
Time     Type Nr Clt User        TCode Priority Grp N Text
04:51:46 DIA 001 100 BASIS               AB 0 Run-time error "TIME_OUT" occurred
04:51:46 DIA 001 100 BASIS               AB 1 > Short dump "101021 045146 clusa " generated
04:51:46 DIA 001 100 BASIS               D0 1 Transaction Canceled SY 002 ( Time limit exceeded. )
05:01:04 RD                                      Q0 I Operating system call connect failed (error no. 10061)
05:01:45 RD                                      Q0 I Operating system call connect failed (error no. 10060)
05:01:45 DIA 000 100 BASIS               R4 9 Communication error, CPIC return code 017, SAP return code 236
05:01:45 DIA 000 100 BASIS               R6 4 > CPI-C function: CMINIT(SAP)
05:20:11 RD                                      Q0 I Operating system call connect failed (error no. 10060)
05:20:11 DIA 001 100 BASIS               R4 9 Communication error, CPIC return code 017, SAP return code 236
05:20:11 DIA 001 100 BASIS               R6 4 > CPI-C function: CMINIT(SAP)
05:20:24 RD                                      Q0 I Operating system call connect failed (error no. 10061)
05:21:18 RD                                      Q0 I Operating system call connect failed (error no. 10060)
05:21:18 DIA 001 100 BASIS               R4 9 Communication error, CPIC return code 017, SAP return code 236
05:21:18 DIA 001 100 BASIS               R6 4 > CPI-C function: CMINIT(SAP)
05:22:56 RD                                      Q0 I Operating system call recv failed (error no. 10054)
08:46:50 BTC 025 000 DDIC                       BY 4 Database error 24909 at UPD access to table TST01
08:46:50 BTC 025 000 DDIC                       F6 H Database error: TemSe->XRTAB(3)->1 for table TST01 key
08:46:56 RD                                      Q0 I Operating system call recv failed (error no. 10054)
08:47:11 BTC 025 000 DDIC                       F3 T Invalid object name for TemSe object: " "
08:47:13 BTC 025 000 DDIC                       EC F Failed to create log for job SAP_COLLECTOR_FOR_PERFMONITOR 19301600 %NEWSTEP/
08:47:13 BTC 025 000 DDIC                       F2 0 Calling program reports invalid handle for TemSe object (magic==X'NULL-ptr')
08:47:13 BTC 025 000 DDIC                       R4 7 Delete session 001 after error 023
09:38:51 DP                                      Q0 I Operating system call recv failed (error no. 10054)
09:38:51 DP                                      Q0 4 Connection to user 9850 ( ), terminal 90 (233 ) lost
10:00:24 RD                                      Q0 I Operating system call recv failed (error no. 10054)
10:00:24 RD                                      S2 3 Connection to CPI-C client 101 was closed
10:00:24 DIA 001 100 PORTAL                R4 9 Communication error, CPIC return code 020, SAP return code 223
10:00:24 DIA 001 100 PORTAL                R5 A > Conversation ID: 909935
10:00:24 DIA 001 100 PORTAL                R6 4 > CPI-C function: CMSEND(SAP)
10:26:36 DP                                      Q0 I Operating system call recv failed (error no. 10
and just now the sm37 log is different
Job started
Step 001 started (program RSCOLL00, variant , user ID DDIC)
Clean_Plan:Cleanup of DB13 Plannings
Clean_Plan:started by RSDBPREV                       on server
Clean_Plan:Cleaning up jobs of system PRD
Clean_Plan:finished
Database destination not found
Cannot determine operating system data for database
Buffer statistics for clusa transferred to MONI
Please suggest
Kind Regards,
Kumar
Edited by: kumar9 on Oct 21, 2010 12:30 PM
Edited by: kumar9 on Oct 21, 2010 2:37 PM

RE: Short dump after activation of BADI

Hi all,
We are getting short dumps in all the transactions after activating the BADI 'BADI_LAYER'
We are not able to execute any of the transactions.
The details of runtimeerror
Runtime Errors RAISE_EXCEPTION
Date and Time 30.07.2007 09:58:06
Short text
Exception condition "SINGLE_EXIT_MULTIPLY_ACTIVE" raised.
What happened?
The current ABAP/4 program encountered an unexpected
situation.
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
A RAISE statement in the program "CL_EXITHANDLER================CP" raised the
exception
condition "SINGLE_EXIT_MULTIPLY_ACTIVE".
Since the exception was not intercepted by a superior
program, processing was terminated.
Short description of exception condition:
For detailed documentation of the exception condition, use
Transaction SE37 (Function Library). You can take the called
function module from the display of active calls.
How to correct the error
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:
"RAISE_EXCEPTION" " "
"CL_EXITHANDLER================CP" or "CL_EXITHANDLER================CM001"
"GET_INSTANCE"
or
"CL_EXITHANDLER================CP" "SINGLE_EXIT_MULTIPLY_ACTIVE"
or
"SAPMF05A " "SINGLE_EXIT_MULTIPLY_ACTIVE"
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... "sapdevp"
Network address...... "192.168.0.205"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "4x Intel 80686"
Character length.... 16 Bits
Pointer length....... 32 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "SAPDEVP"
Database type..... "ORACLE"
Database name..... "TDV"
Database user ID.. "SAPSR4"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Apr 2 2006 23:08:16"
create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version. "OCI_10103_SHARE "
Patch level. 52
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"
Memory consumption
Roll.... 8176
EM...... 6271344
Heap.... 0
Page.... 57344
MM Used. 1728072
MM Free. 360856
User and Transaction
Client.............. 400
User................ "FIUSER01"
Language key........ "E"
Transaction......... "FB50 "
Program............. "CL_EXITHANDLER================CP"
Screen.............. "SAPMF05A 1010"
Screen line......... 7
Information on where terminated
Termination occurred in the ABAP program "CL_EXITHANDLER================CP" -
in "GET_INSTANCE".
The main program was "SAPMF05A ".
In the source code you have the termination point in line 145
of the (Include) program "CL_EXITHANDLER================CM001".
Source Code Extract
Line
SourceCde
115
SELECT SINGLE is_impl FROM badiisimpled INTO is_impl
116
WHERE badi_name = mig_badi_name.
117
IF sy-subrc NE 0.
118
 not yet filled
119
is_impl = cl_enh_badi_tool_utilities=>update_badiisimpled( mig_badi_name ).
120
ENDIF.
121
122
IF is_impl = 'X'.
123
 ok at least one implementation found
124
act_imp_existing = 'X'.
125
ENDIF.
126
127
ENDIF.
128
ENDIF.
129
ELSE.
130
131
check how many implementations exist for an exit
132
CALL METHOD cl_badi_flt_data_trans_and_db=>act_imps_per_flt_val
133
EXPORTING
134
runtime_call = seex_true
135
exit_name = exit_name
136
EXCEPTIONS
137
singular_exit_multiply_active = 1
138
no_active_implementation = 2
139
only_default_implementation = 3
140
OTHERS = 4.
141
CASE sy-subrc.
142
WHEN 0.
143
act_imp_existing = seex_true.
144
WHEN 1.
>>>>>
RAISE single_exit_multiply_active.
146
WHEN 2.
147
act_imp_existing = seex_false.
148
WHEN 3.
149
act_imp_existing = seex_false.
150
def_impl = seex_true.
151
WHEN 4.
152
RAISE data_incons_in_exit_managem.
153
ENDCASE.
154
155
new parameter considered for performance purposes
156
IF act_imp_existing = seex_true OR
157
def_impl = seex_true OR
158
null_instance_accepted = seex_false.
159
160
ok, then do your job
161
CREATE OBJECT exit TYPE (abs_type_classname).
162
CATCH SYSTEM-EXCEPTIONS move_cast_error = 1.
163
instance ?= exit.
164
ENDCATCH.
Contents of system fields
Name
Val.
SY-SUBRC
1
SY-INDEX
0
SY-TABIX
0
SY-DBCNT
2
SY-FDPOS
1
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
FSKB
SY-UCOMM
SY-TITLE
Enter G/L Account Document: Company Code TJ01
SY-MSGTY
S
SY-MSGID
B!
SY-MSGNO
015
SY-MSGV1
00001140
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20070730
SY-UZEIT
095806
SY-XPROG
SY-XFORM
Active Calls/Events
No. Ty. Program Include Line
Name
5 METHOD CL_EXITHANDLER================CP CL_EXITHANDLER================CM001 145
CL_EXITHANDLER=>GET_INSTANCE
4 METHOD CL_EXIT_MASTER================CP CL_EXIT_MASTER================CM004 2
CL_EXIT_MASTER=>CLASS_CONSTRUCTOR
3 METHOD CL_EX_FI_HEADER_SUB_1300======CP CL_EX_FI_HEADER_SUB_1300======CM003 53
CL_EX_FI_HEADER_SUB_1300=>IF_EX_FI_HEADER_SUB_1300~PUT_DATA_TO_SCREEN_PBO
2 FORM SAPMF05A MF05AF00_D0100_PRE_APPL_SUB_2 50
D0100_PRE_APPL_SUB_PBO
1 MODULE (PBO) SAPMF05A MF05AO00_D0100_PRE_APPL_SUB 10
D0100_PRE_APPL_SUB
Chosen variables
Name
Val.
No. 5 Ty. METHOD
Name CL_EXITHANDLER=>GET_INSTANCE
EXIT_NAME
BADI_LAYER
44445445452222222222
2149FC19520000000000
00000000000000000000
00000000000000000000
NULL_INSTANCE_ACCEPTED
2
0
0
0
ACT_IMP_EXISTING
2
0
0
0
INSTANCE
F0000000
F0000000
%_SPACE
2
0
0
0
RSJOBINFO
00000000000000 ##
2222222222222222222222222222222233333333333333222222222222222222222222222222222200
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
%_DUMMY$$
2222
0000
0000
0000
SEEX_TRUE
X
5
8
0
0
SYST-REPID
CL_EXITHANDLER================CP
4454545444444533333333333333334522222222
3CF589481E4C52DDDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
<%_TABLE_BADIISIMPLED>
SY-REPID
CL_EXITHANDLER================CP
4454545444444533333333333333334522222222
3CF589481E4C52DDDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
SY-SUBRC
1
0000
1000
SY-XPROG
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
No. 4 Ty. METHOD
Name CL_EXIT_MASTER=>CLASS_CONSTRUCTOR
%_SPACE
2
0
0
0
SYST-REPID
CL_EXIT_MASTER================CP
4454545544554533333333333333334522222222
3CF5894FD13452DDDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
SY-REPID
CL_EXIT_MASTER================CP
4454545544554533333333333333334522222222
3CF5894FD13452DDDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
CL_EXIT_MASTER=>LAYER_EXIT
F0000000
F0000000
%_DUMMY$$
2222
0000
0000
0000
No. 3 Ty. METHOD
Name CL_EX_FI_HEADER_SUB_1300=>IF_EX_FI_HEADER_SUB_1300~PUT_DATA_TO_SCREEN_PBO
IM_BKPF
TJ01 2007SA00000000200707300400000000000000000000000000000000000000
2225433222222222233335433333333333333333333333333333333333333333333333333333333222222222222222
0004A01000000000020073100000000200707300400000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
IM_X_NO_INPUT
2
0
0
0
FLT_VAL
IN
44
9E
00
00
<EXIT_OBJ>-IMP_CLASS
<FLT_CACHE_LINE>-OBJ
|
| F0000000 |
| F0000000 |
| %_DUMMY$$ |
| |
| 2222 |
| 0000 |
| 0000 |
| 0000 |
| ME->INSTANCE_BADI_TABLE |
| Table[initial] |
| <EXIT_OBJ> |
| ??? |
| ?????? |
| ?????? |
| <%_L001> |
| ??? |
| ?????? |
| ?????? |
| RSJOBINFO |
| 00000000000000 ## |
| 2222222222222222222222222222222233333333333333222222222222222222222222222222222200 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| SY-REPID |
| CL_EX_FI_HEADER_SUB_1300======CP |
| 4454554454444455554533333333334522222222 |
| 3CF58F69F851452F352F1300DDDDDD3000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| <%_L001>-METHOD_NAME |
| ??? |
| ?????? |
| ?????? |
| EXIT_OBJ_TAB |
| Table[initial] |
| SY-SUBRC |
| 1 |
| 0000 |
| 1000 |
| ME |
|
F0000000
C0003000
SXRT_TRUE
X
5
8
0
0
No. 2 Ty. FORM
Name D0100_PRE_APPL_SUB_PBO
*BSEG-STBUK
2222
0000
0000
0000
%_DUMMY$$
2222
0000
0000
0000
SY-REPID
SAPMF05A
5454433422222222222222222222222222222222
310D605100000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
SYST-REPID
SAPMF05A
5454433422222222222222222222222222222222
310D605100000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
KDBTAB-DMBTR
0.0.0.0.0.0.1.
0000000
000000C
%_SPACE
2
0
0
0
KDPTAB-BELNR
2222222222
0000000000
0000000000
0000000000
KDPTAB-GJAHR
0000
3333
0000
0000
0000
KDPTAB-BUZEI
000
333
000
000
000
KDBTAB-XRUND
2
0
0
0
SPACE
2
0
0
0
F05ACTRL
2
0
0
0
SYST
######################################ð#######################################~######### C####
00000000000000000000000000000000000000F0000000000000000000000000000000000000107000000050240000
000000200000000000002010100010000000000000000010400000000000000000000000000080E000200080030100
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000040000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000000000D000000C
BSED
0000000# ############## 0000000000000000
2222222222222222233333330200000000000000223333333333333333222222222222222222222222222222222222
00000000000000000000000000000C000000C000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000C0000000C000000C000000000000000000000000000000000000000000000000000000
SY-SUBRC
1
0000
1000
G_APPL_SUB_ACTIVE
X
5
8
0
0
CHAR_X
X
5
8
0
0
%_ARCHIVE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
BKPF-BUKRS
TJ01
5433
4A01
0000
0000
BKPF
TJ01 2007SA00000000200707300400000000000000000000000000000000000000
2225433222222222233335433333333333333333333333333333333333333333333333333333333222222222222222
0004A01000000000020073100000000200707300400000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
G_APPL_SUB_DISABLE
2
0
0
0
T005-INTCA
IN
44
9E
00
00
No. 1 Ty. MODULE (PBO)
Name D0100_PRE_APPL_SUB
C_FIELD_DIALOG_ALL
BUTTON_DIALOG_ALL
4555445444444544422222222222222222222222222222222222222222222222222222222222222222222222222222
2544FEF491CF7F1CC00000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Internal notes
The termination was triggered in function "ab_jfune"
of the SAP kernel, in line 2561 of the module
"//bas/700_REL/src/krn/runt/abfunc.c#10".
The internal operation just processed is "FUNE".
Internal mode was started at 20070730095806.
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
SAP (R) - R/3(TM) Callstack, Version 1.0
Copyright (C) SAP AG. All rights reserved.
Callstack without Exception:
App : disp+work.EXE (pid=4436)
When : 7/30/2007 9:58:6.359
Threads : 2
Computer Name : SAPDEVP
User Name : SAPServiceTDV
Number of Processors: 4
Processor Type: x86 Family 6 Model 15 Stepping 6
Windows Version : 5.2 Current Build: 3790
State Dump for Thread Id 250c
eax=34d52300 ebx=000003f8 ecx=0001ccc0 edx=34d039e0 esi=000003f8 edi=00000000
eip=7c82ed54 esp=053fceb4 ebp=053fcf24 iopl=0 nv up ei ng nz ac po cy
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00200297
function : KiFastSystemCallRet
7c82ed54 c3 ret
7c82ed55 8da42400000000 lea esp,[esp] ss:053fceb4=7c822124
7c82ed5c 8d642400 lea esp,[esp] ss:6627b4c7=00002100
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
053fcf24 77e6ba42 000003f8 0001d4c0 00000000 053fcf5c ntdll!KiFastSystemCallRet
053fcf38 0100b3aa 000003f8 0001d4c0 00000001 7c38b5c8 kernel32!WaitForSingleObject
053fcf5c 0055b4ac 0055b4e5 7c38b5c8 7c38b5c8 7c38b5c8 disp+work!NTDebugProcess
053fcf60 0055b4e5 7c38b5c8 7c38b5c8 7c38b5c8 01d35ab0 disp+work!NTStack
053fcf7c 0055b519 7c38b5c8 00000000 008536a8 7c38b5c8 disp+work!CTrcStack2
053fcf88 008536a8 7c38b5c8 00000000 005f0059 00300030 disp+work!CTrcStack
053fcfac 008569fa 6d1d037c 0000001b 00000000 01cfc168 disp+work!rabax_CStackSave [abrabax.c (6871)
053fd084 006aaaf4 0134837c 0134835c 00000a01 235f1640 disp+work!ab_rabax
053fd0c0 0067bb56 00000003 34cf5708 00000000 053fd128 disp+work!ab_jfune
053fd128 007af183 00000000 34cf5708 053fd274 34cf8c26 disp+work!ab_extri
053fd13c 00837a37 00000000 34cf7dd6 00596fa0 34cf68b4 disp+work!ab_xevent
053fd148 00596fa0 34cf68b4 000003db 34cf7dd6 00000000 disp+work!ab_dstep
053fd274 00597fa1 34cf5708 34cf5708 053ffd04 00597b13 disp+work!dynpmcal
053fd284 00597b13 34cf5708 34cf5708 00000003 053ffd04 disp+work!dynppbo0
053fd2a0 0056dcf1 34cf5708 0006e768 00000000 0000000c disp+work!dynprctl
053ffd04 00471848 00000013 07de0048 00000001 00494960 disp+work!dynpen00
053ffd14 00494960 0000000c 00000000 00000003 00000002 disp+work!Thdynpen00
053ffee0 00494ee2 00000001 00000000 00000000 00430000 disp+work!TskhLoop
053fff00 00421150 00000000 00000000 7ffd8000 053fff60 disp+work!ThStart
053fff14 00401080 00000003 003f6850 00000001 00000000 disp+work!DpMain
053fff60 011a94a0 00000003 003f6850 003f78f8 01bd5000 disp+work!nlsui_main
053fffc0 77e523e5 00000000 00000000 7ffd8000 88602680 disp+work!wmainCRTStartup
053ffff0 00000000 011a935d 00000000 00905a4d 00000003 kernel32!IsProcessorFeaturePresent
State Dump for Thread Id 27bc
eax=00000001 ebx=00000103 ecx=fffffffe edx=003f01f8 esi=00000000 edi=00000000
eip=7c82ed54 esp=075dfec0 ebp=075dff04 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246
function : KiFastSystemCallRet
7c82ed54 c3 ret
7c82ed55 8da42400000000 lea esp,[esp] ss:075dfec0=7c821514
7c82ed5c 8d642400 lea esp,[esp] ss:6845e4d3=50004500
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
075dff04 010f7ffc 000006c0 00000000 00000000 003f77d0 ntdll!KiFastSystemCallRet
075dff84 7c349565 00000000 00000000 00000000 0587ff08 disp+work!SigIMsgFunc
075dffb8 77e6608b 0587ff08 00000000 00000000 0587ff08 MSVCR71!endthreadex
075dffec 00000000 7c3494f6 0587ff08 00000000 00000000 kernel32!GetModuleFileNameA
List of ABAP programs affected
Index
Typ
Program
Group
Date
Time
Size
Lang.
0
Prg
SAPMF05A
0
22.05.2007
11:37:49
1563648
E
1
Prg
SAPMSSYD
0
10.01.2007
12:33:28
21504
E
2
Prg
SAPFSYSCALLS
0
09.09.2004
14:18:32
8192
E
3
Typ
TFDIR
0
13.02.2005
17:31:57
3072
4
Prg
SAPLAPAR_EBPP_SERVICES
4
03.01.2007
11:23:55
114688
E
5
Typ
T042ZEBPP
0
08.01.2002
14:42:24
2048
6
Typ
T020
0
24.02.1999
03:17:19
3072
7
Typ
RFOPT2
0
11.12.2003
15:00:17
5120
8
Prg
SAPFF001
0
22.05.2007
11:37:49
195584
E
9
Typ
SWOTOBJID
0
04.05.1995
15:20:52
2048
10
Prg
SAPLSWOR
10
10.01.2007
12:33:34
292864
E
11
Typ
TFBUF
0
30.11.1998
22:08:34
3072
12
Typ
ACC_KONTEXT
0
08.01.2003
17:30:26
3072
13
Typ
BKPF
0
13.03.2006
11:01:29
18432
14
Prg
SAPLFACSCORE
14
01.12.2006
22:00:12
13312
E
15
Typ
T001
0
25.08.2005
22:03:13
13312
16
Prg
SAPLACHD
16
03.01.2007
11:23:55
51200
E
17
Prg
SAPFSPOR
0
09.09.2004
14:18:32
15360
E
18
Prg
SAPLSCNT
18
18.02.2005
14:16:06
30720
E
19
Typ
DYCBOX
0
20.08.1998
11:16:53
3072
20
Prg
SAPLSVSM
20
18.02.2005
14:16:06
27648
E
21
Prg
SAPLSGUI
21
10.01.2007
12:33:33
82944
E
22
Prg
SAPLSTTM
22
05.07.2005
13:10:18
69632
E
23
Prg
SAPLSBDC
23
05.07.2005
13:10:18
44032
E
24
Prg
CL_DATAPROVIDER===============CP
24
28.02.2005
21:00:46
49152
E
25
Prg
%_CCNTL
24
18.02.2005
14:15:08
15360
E
26
Typ
OBJ_RECORD
0
14.02.1998
08:30:43
2048
27
Prg
SAPLSTUP
27
08.03.2005
19:04:31
73728
E
28
Prg
SAPLCNDP
28
01.12.2006
22:04:33
193536
E
29
Prg
SAPSHDTV
18
05.01.2005
16:26:16
33792
E
30
Typ
SHDSTU
0
14.12.1998
23:15:34
2048
31
Typ
SHDSTCIU
0
14.12.1998
23:15:34
2048
32
Prg
SAPFGUICNTL
0
18.02.2005
14:15:08
24576
E
33
Prg
SAPLOLEA
33
05.07.2005
13:10:18
96256
E
34
Prg
SAPLSFES
34
10.01.2007
13:26:20
256000
E
35
Prg
SAPLSPLUGIN
35
09.09.2004
14:18:36
8192
E
36
Typ
ARFCRDATA
0
13.02.2005
18:20:24
7168
37
Prg
SAPLGRFC
37
13.02.2005
18:20:25
16384
E
38
Typ
SWCBCONT
0
15.11.2000
17:55:11
3072
39
Typ
OLE_VERBS
0
04.04.1995
16:02:20
2048
40
Typ
OLE_PA
0
04.04.1995
16:02:19
2048
41
Typ
ACGL_HEAD
0
11.12.2003
14:59:21
8192
42
Typ
RF05A
0
11.04.2005
11:50:21
38912
43
Typ
TCURC
0
01.12.1999
12:14:40
2048
44
Prg
SAPLFAGL_ACTIVATION_SERVICES
44
30.04.2007
17:00:55
45056
E
45
Prg
SAPLSTR9
45
09.05.2006
10:39:47
39936
E
46
Prg
CONTEXT_X_TR_SYS_PARAMS
45
09.05.2006
10:39:47
40960
E
47
Typ
TCONT
0
09.09.2004
14:18:43
2048
48
Typ
CONTEXTB
0
09.09.2004
14:15:52
6144
49
Typ
FAGL_ACTIVEC
0
19.08.2004
16:55:10
5120
50
Typ
FAGL_CHECK_SETUP
0
11.12.2003
15:01:05
2048
51
Prg
SAPLSHD0
51
03.01.2007
06:52:22
232448
E
52
Prg
SAPLBFFM3
52
10.01.2007
13:15:21
169984
E
53
Typ
OFIWA
0
15.04.1998
00:11:05
2048
54
Typ
FTEXTS
0
20.08.2001
12:13:26
3072
55
Prg
SAPLITSR
55
10.01.2007
14:23:52
107520
E
56
Typ
FMRFC
0
13.08.1997
12:32:59
2048
57
Typ
TBE01
0
20.01.2003
16:41:38
2048
58
Typ
TBE31
0
03.09.1997
03:01:11
2048
59
Typ
TBE31
0
03.09.1997
03:01:11
2048
60
Typ
TBE11
0
03.09.1997
03:01:06
2048
61
Prg
CONTEXT_X_SP_INFO
55

Hello Sowmya
The BAdI BADI_LAYER is not defined for Multiple-Use (see checkbox on tabstrip Attributes).
Apparently you have created several implementation of this BAdI and activated several (at least 2) of these implementations.
If you inactivate all except a single implementation the BAdI (and all transactions using this BAdI) should work again.
Regards
Uwe

Short dump in custom report in production

Hi Experts,
I have a custom report which is run through SM37 as a background job. it takes long time to run and then get canceled with       short dump in production but it runs fine in development.
description of short dump.
Runtime Errors         DBIF_RSQL_SQL_ERROR
Exception              CX_SY_OPEN_SQL_DB
Date and Time          03.05.2010 11:33:06
Short text
|    SQL error in the database when accessing a table.

Hi,
Please go through the below notes
[Note 1379839 - RuntimeError DBIF_RSQL_SQL_ERROR Exception CX_SY_OPEN_SQL_DB|https://service.sap.com/sap/support/notes/1379839]
[Note 1098183 - RunErr dbif_rsql_sql_error with exception CX_SY_OPEN_SQL_DB|https://service.sap.com/sap/support/notes/1098183]
[Note 1410849 - Runtime error DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"|https://service.sap.com/sap/support/notes/1410849]
This is mainly program error and need corrections...
Compare the Patch level on both DEV and PRD server. Also make sure, whether program you are using on developement is modified (Corrected) or standard one.
If you search for the SAP Notes with "DBIF_RSQL_SQL_ERROR Exception CX_SY_OPEN_SQL_DB" string, you will get several hits. See the notes which are applicable in your scenario...
Regards.
Sumit Nene

Short dump error report

What is the purpose of short dump error report generated by the system? What r the major parts/section of this report?

hi please look through this:
Whenever any transaction or any process is executed it hits an ABAP code.
If there is any issue in executing the code the situation is called "ABAP DUMP" or 'Short Dump'
Transaction ST22 is used to check any ABAP Dump within a given duration.
U can also fix the issue with the help of ABAP editor (Transaction Code SE38) if u r good with ABAP.
you can select back to the last 14 days if you are
running the SAP_REORG_ABAPDUMPS job (program RSSNAPDL) which deletes te
old ABAP dumps every day, possibly further if you run it weekly or
monthly.
sap-basis sap-basisAll Groups Ignore this text box. It is used to detect spammers.If you enter anything into this text box, no search results will be displayed.
SAP Groups > Technical-functional > sap-basis > Message
About This Group | Invite peers to join this group
<< Prev thread < Prev msg Next msg > Next thread >>
short dump----urgent
Reply from Keith Lewis on 5/2/2003 3:22:00 AM
Good explanation Joy, but it is not only limited to the current day and
yesterday. If you click on the Selection button you can select previous
days as well. In fact you can select back to the last 14 days if you are
running the SAP_REORG_ABAPDUMPS job (program RSSNAPDL) which deletes te
old ABAP dumps every day, possibly further if you run it weekly or
monthly.
Cheers
Keith
SAP R/3 Support Specialist
Information Services International
Tel +44 1664 41 6178 Mobile +44 7887 627818
E-mail email@removed
Archive Page - http://www.ittoolbox.com//I/sap-r3-basis.asp
Dear sreenivas
If you receive an error message in the R/3 System log (SM21), or if you
see
a terminated update in the update service analysis transaction (SM13), or
DB
realated error ,check for dumps using the dump analysis transaction
(transaction ST22), or choose Tools -> Administration -> Monitoring ->
Dump
analysis.
Transaction ST22 enables you to analyze short dumps from the current and
previous day.
The dump analysis function shows you:
What happened
What you can do
How to correct the error
The dump analysis function also provides an error ID and keywords that you
can use to search in SAPNet, as well as information about:
The system environment
Users and transactions
Transaction ST22 enables you to analyze the following data:
Date, time, user, client
Contents of system and data fields
Contents of internal tables and application tables
ST22 is a very nice feature in SAP. This is where all the system errors
and users mistakes showed up. If there is a problem that you cannot
solve and you contact SAP support, they look at this area to analyze it.
This gives us lead where to handle the problems.
Error analysis
How to correct the error
System environment
User, transaction...
Information on where termination occurred
Contents of system fields
Chosen variables
Active calls / events
Internal notes
Active calls in SAP kernel
List of ABAP programs affected
List of internal tables
Directory of application tables (contents)
Directory of data areas (administration information)
Directory of data areas (contents)
ABAP control blocks CONT
End of runtime analysis
i think this would be helpful
regards
sravani

Timeout Short Dump on a Data Query to a blank table.

Hi,
My program gives a short dump on quering a blank table. The dump says timeout.
what could the possible problem be.
regards,

Runtime Error          TIME_OUT
       Occurred on     02/19/2009 at   10:35:35
Time limit exceeded.
What happened?
The program "SAPLE31C" has exceeded the maximum permitted runtime without
interruption, and has therefore been terminated.
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
After a certain length of time, the program is terminated. In the case
of a work area, this means that
- endless loops (DO, WHILE, ...),
- database accesses producing an excessively large result set,
- database accesses without a suitable index (full table scan)
do not block the processing for too long.
The system profile "rdisp/max_wprun_time" contains the maximum runtime of a
program. The
current setting is 5400 seconds. Once this time limit has been exceeded,
the system tries to terminate any SQL statements that are currently
being executed and tells the ABAP processor to terminate the current
program. Then it waits for a maximum of 60 seconds. If the program is
still active, the work process is restarted.
successfully processed, the system gives it another 5400 seconds.
Hence the maximum runtime of a program is at least twice the value of
the system profile parameter "rdisp/max_wprun_time".
How to correct the error
You should usually execute long-running programs as batch jobs.
If this is not possible, 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 an unsuitable index: Check index generation.
You may able to find an interim solution to the problem
~~~~~~~
The line to which it points is a select query on a table that has not records.

Short dump: : OBJECT_NOT_STRUCTURED

Hi,
We are getting the shortdump in BWP, ERROR MESSAGE :OBJECT_NOT_STRUCTURED.
due this the user are not able to see the reports.
This for the infocube : 0RPA_C01
Message no: RSBK257
Short dump
Runtime Errors OBJECT_NOT_STRUCTURED
Date and Time 21.12.2008 03:02:52
 Short text
 Invalid operand type for the MOVE-CORRESPONDING statement.
 What happened?
 Error in the ABAP Application Program
 The current ABAP program "/RTF/CL_KYF_TRANSFORM=========CP" had to be
 terminated because it has
 come across a statement that unfortunately cannot be executed.
 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
 The MOVE-CORRESPONDING statement can only be used on operands with a
 structured type.
 In the case at hand, this condition is not fulfilled: Operand "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... "ndflapp7"
 Network address...... "192.168.4.38"
 Operating system..... "SunOS"
 Release.............. "5.10"
 Hardware type........ "sun4v"
 Character length.... 16 Bits
 Pointer length....... 64 Bits
 Work process number.. 18
 Shortdump setting.... "full"
 Database server... "ndflbwp"
 Database type..... "DB6"
 Database name..... "BWP"
 Database user ID.. "SAPBWP"
 Char.set.... "C"
 SAP kernel....... 700
 created (date)... "Feb 3 2008 21:08:24"
 create on........ "SunOS 5.9 Generic_117171-13 sun4u"
 Database version. "DB6_81 "
 Patch level. 146
 Patch text.. " "
 Database............. "DB6 08.02., DB6 09."
 SAP database version. 700
 Operating system..... "SunOS 5.9, SunOS 5.10"
 Memory consumption
 Roll.... 2713920
 EM...... 0
 Heap.... 39801136
 Page.... 24576
 MM Used. 42159048
 MM Free. 235944
 User and Transaction
 Client.............. 700
 User................ "BWREMOTE"
 Language key........ "E"
 Transaction......... " "
 Transactions ID..... "494D622862192FB7E1000000C0A80426"
 Program............. "/RTF/CL_KYF_TRANSFORM=========CP"
 Screen.............. "SAPMSSY0 1000"
 Screen line......... 6
 Information on where terminated
 Termination occurred in the ABAP program "/RTF/CL_KYF_TRANSFORM=========CP" -
 in "CALCULATE_KEYFIGURE_DS".
 The main program was "RSBATCH_EXECUTE_PROZESS ".
 In the source code you have the termination point in line 29
 of the (Include) program "/RTF/CL_KYF_TRANSFORM=========CM004".
 The program "/RTF/CL_KYF_TRANSFORM=========CP" was started as a background job.
 Job Name....... "BIDTPR_9161_1"
 Job Initiator.. "BWREMOTE"
 Job Number..... 03023200
 Source Code Extract
 Line SourceCde
 1 method calculate_keyfigure_ds.
 2
 3 field-symbols: SINGLE_REF
 F0000000
 F0000000
 /RTF/CL_KYF_TRANSFORM=>S_MONITOR+148(100)
 00000000000000000000000000000000000000000000000000
 00000000000000000000000000000000000000000000000000
 22222222222222222222222222222222222222222222222222
 00000000000000000000000000000000000000000000000000
 /RTF/CL_KYF_TRANSFORM=>S_MONITOR
 000
 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
 2222222222222222222223332222222222222222222222222222222222222222222222222222222222222222222222
 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
 %_SPACE
 0
 0
 2
 0
 SY
 #######ᗹ###################A###P#################<#############################T#######䵘 C####
 0000000100000000000000000000000000000000000000000000000000000000000000000000000000000004000000
 000000050000000000000000000000000000000800000000000000000000000000000000000000000000000D000000
 0000000F00000000000000000004000500000009000000000300000000000000000000000000010500010005240000
 0300010900000100000001000101010000000008000000040C000000000000000000000000000604000E000803000C
 %_EXCP
 F0000000
 F0000000
 %_DUMMY$$
 0000
 0000
 2222
 0000
 /RTF/CL_KYF_TRANSFORM=>HLP_STRUC_DS
 C0000000
 F0000000
 <L_STRUC>
 SYST-REPID
 /RTF/CL_KYF_TRANSFORM=========CP
 0000000000000000000000000000000000000000
 0000000000000000000000000000000000000000
 2554244545455544544543333333334522222222
 F246F3CFB96F421E36F2DDDDDDDDDD3000000000
 LT_APPL_MONITOR
 Table[initial]
 No. 7 Ty. METHOD
 Name LCL_TRANSFORM=>COMPUTE_14_1
 REQUEST
 DTPR_4C872RDREWJJFKCBYOIXF7GVA
 000000000000000000000000000000
 000000000000000000000000000000
 455553433354545444444544543454
 4402F4387224257AA6B329F9867761
 DATAPACKID
 000001
 000000
 000000
 333333
 000001
 SOURCE_FIELDS
 1000000000001600000030202008121910010000000004000000000000000038022008121917294320081219172957
 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
 3333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333
 1000000000001600000030202008121910010000000004000000000000000038022008121917294320081219172957
 RESULT
 000000000
 00000000C
 MONITOR
 Table[initial]
 IS_S_FIELDS-BASEQUANTITY
 000000000
 00000000C
 SOURCE_FIELDS-BASEQUANTITY
 0000000
 000000C
 IS_S_FIELDS-DISTDISC
 000000000
 00000000C
 SOURCE_FIELDS-DISTDISC
 00000000
 0000000C
 IS_S_FIELDS-DISTTAX
 000000000
 00000000C
 SOURCE_FIELDS-DISTTAX
 00000000
 0000000C
 IS_S_FIELDS-DISTTENDER
 000000000
 00000000C
 SOURCE_FIELDS-DISTTENDER
 00000000
 0000000C
 IS_S_FIELDS-REDUCTIONAMOUNT
 000000000
 00000000C
 SOURCE_FIELDS-REDUCTIONAMOUNT
 00000000
 0000000C
 IS_S_FIELDS-TAXAMOUNT
 000000000
 00000000C
 SOURCE_FIELDS-TAXAMOUNT
 00000000
 0000000C
 IS_S_FIELDS-COMMAMOUNT
 000000000
 00000000C
 SOURCE_FIELDS-COMMAMOUNT
 00000000
 0000000C
 IS_S_FIELDS-TENDERAMOUNT
 000000000
 00000000C
 SOURCE_FIELDS-TENDERAMOUNT
 00000000
 0000000C
 RS_C_TRUE
 X
 0
 0
 5
 8
 IS_S_FIELDS-LINEITEMCOUNT
 000000000
 00000010C
 SOURCE_FIELDS-LINEITEMCOUNT
 1
 0000
 0001
 IS_S_FIELDS-TOTALSALESAMOUNT
0.0.0.0.0.0.1. #
 000000020
 00000010C
 SOURCE_FIELDS-TOTALSALESAMOUNT
0.0.0.0.0.1. #
 00000020
 0000010C
 IS_S_FIELDS-REDUCTIONAMOUNTN
 000000000
 00000000C
 SOURCE_FIELDS-REDUCTIONAMOUNTN
 00000000
 0000000C
 IS_S_FIELDS-REDUCTIONAMOUNTG
 000000000
 00000000C
 SOURCE_FIELDS-REDUCTIONAMOUNTG
 00000000
 0000000C
 SY-REPID
 GP4AQKW51YXT96BMBCFL1TYQBS6
 0000000000000000000000000000000000000000
 0000000000000000000000000000000000000000
 4534545335553344444435554532222222222222
 70411B751984962D236C14912360000000000000
 CS_TARGET-FIELDNM
 BASE_QTY
 000000000000000000000000000000
 000000000000000000000000000000
 445455552222222222222222222222
 2135F1490000000000000000000000
 SYST-REPID
 GP4AQKW51YXT96BMBCFL1TYQBS6
 0000000000000000000000000000000000000000
 0000000000000000000000000000000000000000
 4534545335553344444435554532222222222222
 70411B751984962D236C14912360000000000000
 %_SPACE
 0
 0
 2
 0
 IS_S_FIELDS
 000 00001000120081219172957##### ###################
 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
 0000000000000000000000000000000000000000000000000000000000000000000000000C00000C00000000C00000
 3332222222222222222222222222222222222222222222333333333333333333333330000020000000000000000000
 00000000000000000000000000000000000000000000000000100012008121917295700000000000000C00000000C0
 CS_TARGET
 BASE_QTY ##################
 000000000000000000000000000000000000000000000000
 0000000000000000000000000000000000C00000000000C0
 445455552222222222222222222222000000000000000000
 2135F149000000000000000000000000000000C000000000
 %_DUMMY$$
 0000
 0000
 2222
 0000
 No. 6 Ty. METHOD
 Name LCL_TRANSFORM=>EXECUTE
 I_MASTER_DATA_EXIST
 0
 0
 2
 0
 I_R_INBOUND
 80000007
 B0000004
 I_R_LOG
 3000000C
 2000004D
 I_R_REQUEST
 0000000F
 B0000064
 I_R_TRFN_CMD
 D0000002
 B0000004
 E_R_OUTBOUND
 3000000C
 3000004C
LSSUPP-_13
 0
 0
 2
 0
 RS_C_FALSE
 0
 0
 2
 0
 RSJOBINFO
 00000000000000 ##
 0000000000000000000000000000000000000000000000000000000000000000000000000000000000
 0000000000000000000000000000000000000000000000000000000000000000000000000000000000
 2222222222222222222222222222222233333333333333222222222222222222222222222222222200
 0000000000000000000000000000000000000000000000000000000000000000000000000000000000
CURRRULE-RULEID
 917760
 00
 0E
 SCREEN
 %_17NNS0000026337_%_%_%_%_%_%_
 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
 2533445333333333352525252525252222222222222222222222222222222222222222222222222222222222222222
 5F17EE30000026337F5F5F5F5F5F5F0000000000000000000000000000000000000000000000000000000000000000
CURRRULE-STEPID
 16777248
 0
 1
LSSUPP-_14
 0
 0
 2
 0
LTMSG
 Table[initial]
G1-BASE_QTY
 000000000
 00000000C
 ME
 0000000F
 C0000063
 L_REQUEST
 DTPR_4C872RDREWJJFKCBYOIXF7GVA
 000000000000000000000000000000
 000000000000000000000000000000
 455553433354545444444544543454
 4402F4387224257AA6B329F9867761
 I_R_INBOUND->N_DATAPAKID
 000001
 000000
 000000
 333333
 000001
 <_YS_SC_1>
 1000000000001600000030202008121910010000000004000000000000000038022008121917294320081219172957
 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
 3333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333
 1000000000001600000030202008121910010000000004000000000000000038022008121917294320081219172957
LSMSG
 000
 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
 2222222222222222222223332222222222222222222222222222222222222222222222222222222222222222222222
 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
 SPACE
 0
 0
 2
 0
 No. 5 Ty. METHOD
 Name CL_RSTRAN_TRFN_CMD=>IF_RSBK_CMD_T~TRANSFORM
 I_R_INBOUND
 80000007
 B0000004
 I_R_LOG
 3000000C
 2000004D
 I_R_SELSET
 F0000000
 F0000000
 I_R_FILTER
 F0000000
 F0000000
 E_R_OUTBOUND
 3000000C
 3000004C
 ME->IF_RSBK_CMD~N_REQUID
 9161
 002C
 0039
 L_R_REQUEST_MAIN
 F0000000
 B0000004
 %_DUMMY$$
 0000
 0000
 2222
 0000
 L_R_REQUEST
 0000000F
 B0000064
 SYST-REPID
 CL_RSTRAN_TRFN_CMD============CP
 0000000000000000000000000000000000000000
 0000000000000000000000000000000000000000
 4455555445554454443333333333334522222222
 3CF23421EF426EF3D4DDDDDDDDDDDD3000000000
 LR_EXE
 0000000F
 C0000063
 ME->C_METH_EXECUTE
 EXECUTE
 0000000
 0000000
 4544554
 5853545
 ME->N_CHECK_ONLY_SIDS
 0
 0
 2
 0
 ME
 D0000002
 B0000004
 ME->N_TH_BP
 Table IT_475[0x24]
DATA=N_TH_BP
 Table reference: 164
 TABH+ 0(20) = 0000000000000000000000000000000000000000
 TABH+ 20(20) = 000000A4000001DB0000000000000018FFFFFFFF
 TABH+ 40(16) = 04000114000004700010839401800000
 store = 0x0000000000000000
 ext1 = 0x0000000000000000
 shmId = 0 (0x00000000)
 id = 164 (0x000000A4)
 label = 475 (0x000001DB)
 fill = 0 (0x00000000)
 leng = 24 (0x00000018)
 loop = -1 (0xFFFFFFFF)
 xtyp = TYPE#000009
 occu = 16 (0x00000010)
 access = 4 (ItAccessHashed)
 idxKind = 0 (ItIndexNone)
 uniKind = 1 (ItUnique)
 keyKind = 3 (user defined)
 cmpMode = 2 (cmpSingleMcmpR)
 occu0 = 1
 groupCntl = 0
 rfc = 0
 unShareable = 0
 mightBeShared = 0
 sharedWithShmTab = 0
 isShmLockId = 0
 gcKind = 0
 isUsed = 1
 isCtfyAble = 1
 >>>>> Shareable Table Header Data <<<<<
 tabi = Not allocated
 pghook = Not allocated
 idxPtr = Not allocated
 shmTabhSet = Not allocated
 id = Not allocated
 refCount = Not allocated
 tstRefCount = Not allocated
 lineAdmin = Not allocated
 lineAlloc = Not allocated
 shmVersId = Not allocated
 shmRefCount = Not allocated
 shmIsReadOnly = Not allocated
 >>>>> 1st level extension part <<<<<
 regHook = Not allocated
 collHook = Not allocated
 ext2 = Not allocated
 >>>>> 2nd level extension part <<<<<
 tabhBack = Not allocated
 delta_head = Not allocated
 pb_func = Not allocated
 pb_handle = Not allocated
 L_S_BP
 000000000000
 000000000000
 000000000000
 333333333333
 000000000000
 SY-REPID
 CL_RSTRAN_TRFN_CMD============CP
 0000000000000000000000000000000000000000
 0000000000000000000000000000000000000000
 4455555445554454443333333333334522222222
 3CF23421EF426EF3D4DDDDDDDDDDDD3000000000
 RSTR_STEPTYPE
 NO_UPDATE INITIAL DIRECT CONS
 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
 4455544542222222222222222222224445444222222222222222222222224454452222222222222222222222224445
 EFF5041450000000000000000000009E9491C000000000000000000000004925340000000000000000000000003FE3
 RSTR_STEPTYPE-DIRECT
 DIRECT
 000000000000000000000000000000
 000000000000000000000000000000
 445445222222222222222222222222
 492534000000000000000000000000
 I_R_INBOUND->N_DATAPAKID
 000001
 000000
 000000
 333333
 000001
 SY-SUBRC
 4
 0000
 0004
 SPACE
 0
 0
 2
 0
 L_SEGID
 0000
 0000
 0000
 3333
 0000
 RSAWC_C_TFC-DISPLAY
 DISPLAY
 0000000000000000000000000000000000000000000000000000000000000000000000
 0000000000000000000000000000000000000000000000000000000000000000000000
 4455445222222222222222222222222222222222222222222222222222222222222222
 4930C19000000000000000000000000000000000000000000000000000000000000000
 No. 4 Ty. METHOD
 Name CL_RSBK_PROCESS=>PROCESS_REQUEST
 SY-REPID
 CL_RSBK_PROCESS===============CP
 0000000000000000000000000000000000000000
 0000000000000000000000000000000000000000
 4455544555444553333333333333334522222222
 3CF232BF02F3533DDDDDDDDDDDDDDD3000000000
 ME
 F0000000
 E0000001
 ME->N_S_CURSOR_R-NODE
 -2
 FFFF
 FFFE
 ME->P_R_LOG_STEP
 3000000C
 2000004D
 %_DUMMY$$
 0000
 0000
 2222
 0000
 ME->P_R_INBOUND
 80000007
 B0000004
 ME->P_R_OUTBOUND
 3000000C
 3000004C
 L_R_TRANSFORM
 D0000002
 B0000004
 ME->N_S_CURSOR_R+36(8)
 D0000002
 B0000004
 SPACE
 0
 0
 2
 0
 SY
 #######ᗹ###################A###P#################<#############################T#######䵘 C####
 0000000100000000000000000000000000000000000000000000000000000000000000000000000000000004000000
 000000050000000000000000000000000000000800000000000000000000000000000000000000000000000D000000
 0000000F00000000000000000004000500000009000000000300000000000000000000000000010500010005240000
 0300010900000100000001000101010000000008000000040C000000000000000000000000000604000E000803000C
 ME->N_R_DP
 C0000003
 D0000002
 No. 3 Ty. METHOD
 Name CL_RSBK_PROCESS=>IF_RSBATCH_EXECUTE~EXECUTE
 I_PARAMETER
 ÿ#######4102##########(##########################P#R#O#C#E#S#S«#####(ª######ª######ª######ª###
 F0000080333300000000002000800000000000000000000005050404040505A000002A000000A000000A000000A000
 F6111200410200005F00008005A70000000000000000000000020F03050303BF00008A800004A60000CA800004A800
 E_RETURN
 E_T_MSG
 Table[initial]
 RSBTC_C_STATUS-OK
 @08@
 0000
 0000
 4334
 0080
 %_FSREG_001
 SY-XFORM
 CONVERSION_EXIT
 000000000000000000000000000000
 000000000000000000000000000000
 444545544454545222222222222222
 3FE65239FEF5894000000000000000
 SYST-REPID
 CL_RSBK_PROCESS===============CP
 0000000000000000000000000000000000000000
 0000000000000000000000000000000000000000
 4455544555444553333333333333334522222222
 3CF232BF02F3533DDDDDDDDDDDDDDD3000000000
 ME
 F0000000
 E0000001
 %_ARCHIVE
 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
 2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
 %_PRINT
 001RSBATCH_EXEC X8##A
 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
 2222333554454454544222222222222222222222222222222222222222222222222222222222222222222222253004
 00000012321438F5853000000000000000000000000000000000000000000000000000000000000000000000088001
 %_VIASELSCR
 0
 4
 L_R_ERROR
 F0000000
 F0000000
 No. 2 Ty. FUNCTION
 Name RSBATCH_EXECUTE_PROCESS
 ID
 DTPR_9161_1
 000000000000000000000000000000
 000000000000000000000000000000
 455553333532222222222222222222
 4402F9161F10000000000000000000
 I_DIALOG_DEBUG_MODE
 0
 0
 2
 0
 PROCESS
 3
 0000
 0003
 G_T_SERVER_100
 00
 000000000000000000000000000000000000000000000000000000000000000000000000000000000000
 000000000000000000000000000000000000000000000000000000000000000000000000000000000000
 222222222222222222222222222222222222222222222222222222222222222222222222222222222332
 000000000000000000000000000000000000000000000000000000000000000000000000000000000000
 L_S_CTRL-LANGU
 E
 0
 0
 4
 5
 SY-LANGU
 E
 0
 0
 4
 5
 SYST-REPID
 SAPLRSBATCH
 0000000000000000000000000000000000000000
 0000000000000000000000000000000000000000
 5454554454422222222222222222222222222222
 310C232143800000000000000000000000000000
 SPACE
 0
 0
 2
 0
 G_NUM3
 000
 000
 000
 333
 000
 %_DUMMY$$
 0000
 0000
 2222
 0000
 SY-REPID
 SAPLRSBATCH
 0000000000000000000000000000000000000000
 0000000000000000000000000000000000000000
 5454554454422222222222222222222222222222
 310C232143800000000000000000000000000000
 L_MODULE_NAME
 CL_RSBK_PROCESS
 0000000000000000000000000000000000000000
 0000000000000000000000000000000000000000
 4455544555444552222222222222222222222222
 3CF232BF02F35330000000000000000000000000
 %_SPACE
 0
 0
 2
 0
 %_CX_TABLEVIEW_ID
 2
 0000
 0002
 L_S_CTRL-PROCESS_TYPE
 DTP_LOAD
 0000000000
 0000000000
 4555444422
 440FCF1400
 %_CX_TABSTRIP_ID
 3
 0000
 0003
 L_S_CTRL-BATCH_ID
 DTPR_9161_1
 000000000000000000000000000000
 000000000000000000000000000000
 455553333532222222222222222222
 4402F9161F10000000000000000000
 %_CX_TABLEVIEW_VERSION
 0
 0
 0
 3
 0
 L_S_CTRL-BATCH_PROCESS
 3
 0000000000
 0000000000
 2222222232
 0000000030
 %_CX_TABSTRIP_VERSION
 0
 0
 0
 3
 0
 L_PARAMETER
 ÿ#######4102##########(##########################P#R#O#C#E#S#S«#####(ª######ª######ª######ª###
 F0000080333300000000002000800000000000000000000005050404040505A000002A000000A000000A000000A000
 F6111200410200005F00008005A70000000000000000000000020F03050303BF00008A800004A60000CA800004A800
 L_R_BATCH_EXECUTE
 F0000000
 E0000001
 L_RETURN
 L_T_MSG
 Table[initial]
 CTRL_200_VAL-CX
 No. 1 Ty. EVENT
 Name START-OF-SELECTION
 SYST-REPID
 RSBATCH_EXECUTE_PROZESS
 0000000000000000000000000000000000000000
 0000000000000000000000000000000000000000
 5544544545445545554545522222222222222222
 2321438F5853545F02FA53300000000000000000
 L_T_CTRL
 Table[initial]
 SCREEN
 %_17NNS0000026337_%_%_%_%_%_%_
 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
 2533445333333333352525252525252222222222222222222222222222222222222222222222222222222222222222
 5F17EE30000026337F5F5F5F5F5F5F0000000000000000000000000000000000000000000000000000000000000000
 L_S_CTRL
 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
 2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
 L_LINES
 0
 0000
 0000
 L_S_CTRL-BATCH_PROCESS
 0000000000
 0000000000
 2222222222
 0000000000
 L_S_PAR-WP_NO
 000
 000
 222
 000
 ID
 DTPR_9161_1
 000000000000000000000000000000
 000000000000000000000000000000
 455553333532222222222222222222
 4402F9161F10000000000000000000
 L_PROCESS
 3
 0000
 0003
 %_DUMMY$$
 0000
 0000
 2222
 0000
 L_S_HEADER-HOLD_PAR_PROCS
 0
 0
 2
 0
 %_SPACE
 0
 0
 2
 0
 SYST
 #######ᗹ###################A###P#################<#############################T#######䵘 C####
 0000000100000000000000000000000000000000000000000000000000000000000000000000000000000004000000
 000000050000000000000000000000000000000800000000000000000000000000000000000000000000000D000000
 0000000F00000000000000000004000500000009000000000300000000000000000000000000010500010005240000
 0300010900000100000001000101010000000008000000040C000000000000000000000000000604000E000803000C
 PROCESS
 3
 0000
 0003
 L_S_HEADER-PROCESS_TYPE
 DTP_LOAD
 0000000000
 0000000000
 4555444422
 440FCF1400
 RSBTC_C_PROCESS-DTP_LOAD
 DTP_LOAD
 0000000000
 0000000000
 4555444422
 440FCF1400
 Internal notes
 The termination was triggered in function "ab_jmvco"
 of the SAP kernel, in line 1521 of the module
 "//bas/700_REL/src/krn/runt/abmvco.c#6".
 The internal operation just processed is "MVCO".
 Internal mode was started at 20081221030232.
 Active Calls in SAP Kernel
 Lines of C Stack in Kernel (Structure Differs on Each Platform)
 DoStack2 ( 0x106186020, 0xffffffff7fff9eb0, 0x10054b9a4, 0x0, 0x14, 0x1034d8af0 ), at 0x10054b
 CTrcStack2 ( 0x106186020, 0x0, 0x19c00, 0x103547870, 0x101e1c9a4, 0x1034d8af0 ), at 0x10054b54
 __1cQrabax_CStackSave6F_v_ ( 0x103775c00, 0x3775c00, 0x103edabe0, 0x1023314de, 0x100000000, 0x
 ab_rabax ( 0x0, 0x0, 0x2000000, 0x100000000, 0x3ed9800, 0x3547800 ), at 0x100cd53b0
 __1cIab_jmvco6F_v_ ( 0xffffffff7fffafbc, 0xfffffffe319fc20c, 0x600000000000000, 0x1069d1ca4, 0
 __1cIab_extri6F_i_ ( 0x100000000, 0x62cac00, 0x548, 0x1, 0x0, 0xa9 ), at 0x10076ecf8
 __1cJab_xevent6FpkH_i_ ( 0x0, 0x0, 0x0, 0x0, 0x4c, 0x106186800 ), at 0x100a4f6f0
 __1cIab_trigg6F_i_ ( 0x106109f20, 0x106189968, 0x100a4f038, 0x4, 0x0, 0x0 ), at 0x100a4f174
 ab_run ( 0x106a1adb8, 0x106189400, 0x102335bac, 0x0, 0x10618685c, 0x0 ), at 0x100d3d254
 dynpmcal ( 0x10690c420, 0x6, 0xc, 0x103a0eec8, 0x100577d80, 0x103547864 ), at 0x1005703ac
 dynppai0 ( 0x10690c420, 0x10690da2c, 0x0, 0x1035478c8, 0x0, 0x1061a6894 ), at 0x10056d608
 dynprctl ( 0x10690c420, 0x0, 0x1035317c0, 0x1300, 0x1, 0x128c ), at 0x10056bc4c
 dynpen00 ( 0x10682df80, 0x10690c420, 0x10690c420, 0x102c30000, 0x2c30000, 0x100000000 ), at 0
 TskhLoop ( 0xffffffff7108b230, 0x103530000, 0x3f36, 0xffffffffffffe080, 0xffffffff70007d38, 0
 ThStart ( 0x1, 0x2a7400, 0x1002a7400, 0x100000000, 0x1, 0x0 ), at 0x1002a7f0c
 DpMain ( 0x3c7bc00, 0x3530000, 0x100000000, 0x1, 0x0, 0x0 ), at 0x1001d9698
 List of ABAP programs affected
 Index Typ Program Group Date Time Size Lang.
 0 Prg RSBATCH_EXECUTE_PROZESS 0 09.07.2008 04:18:32 39936 E
 1 Prg SAPMSSY0 1 08.07.2008 17:53:04 92160 E
 2 Prg SAPMSSYD 1 05.09.2006 14:20:30 21504 E
 3 Prg SAPFSYSCALLS 1 07.03.2005 18:01:13 8192 E
 4 Prg RSDBRUNT 0 08.07.2008 18:16:58 254976 E
 5 Prg SAPLSPRI 5 08.07.2008 18:48:22 342016 E
 6 Typ PRI_PARAMS 0 27.10.1998 15:01:35 5120
 7 Typ ARC_PARAMS 0 08.08.1997 14:45:20 5120
 8 Typ PRI_LAYOUT 0 04.09.2002 14:38:36 3072
 9 Typ PRIPAR_EXT 0 03.06.2004 11:20:21 3072
 10 Typ PRIPAR_EX2 0 01.02.2001 17:17:24 2048
 11 Typ PRIPAR_EX3 0 03.06.2004 11:20:21 3072
 12 Typ TPRI_DEF 0 01.02.2001 17:50:49 5120
 13 Typ USR01 0 08.07.2008 17:43:16 4096
 14 Typ TSP1D 0 02.02.1998 15:00:56 5120
 15 Prg SAPLSPOO 15 08.07.2008 18:46:51 152576 E
 16 Prg SAPLRSPOLSTDRV 16 18.11.2005 14:39:34 57344 E
 17 Typ TSPOPTIONS 0 06.12.1996 16:09:18 2048
 18 Typ TSP03 0 13.08.1998 16:56:08 6144
 19 Prg SAPCNVE 19 07.03.2005 18:01:13 8192 E
 20 Prg SAPLSPOC 20 08.07.2008 18:48:51 137216 E
 21 Typ RSPOCHECK 0 14.07.1997 13:01:20 4096
 22 Typ TSP03A 0 10.06.1997 01:43:11 3072
 23 Typ DEVPAR 0 01.02.2001 17:10:21 3072
 24 Typ RSPOATTR 0 19.01.2000 18:34:33 2048
 25 Typ RSSCR 0 23.11.1999 09:24:41 5120
 26 Prg RSDBSPBL 0 07.03.2005 18:01:13 72704 E
 27 Prg SAPDB__S 0 07.03.2005 18:01:13 19456 E
 28 Typ VARID 0 11.04.1997 18:32:23 7168
 29 Typ SSCRFIELDS 0 02.05.1997 13:16:39 5120
 30 Prg %_CSYDB0 0 07.03.2005 18:01:13 36864 E
 31 Prg RSDBSPVA 0 08.07.2008 16:32:53 133120 E
 32 Typ RSVAMEMKEY 0 16.12.1996 19:31:50 2048
 33 Prg RSDBSPMC 0 05.09.2006 14:14:08 79872 E
 34 Typ DDSHDESCR 0 28.11.1997 16:26:30 4096
 35 Typ SPPARAMS 0 07.03.1997 14:48:48 2048
 36 Prg SAPLICON 36 08.07.2008 18:16:58 27648 E
 37 Prg %_CICON 36 08.07.2008 18:16:57 107520 E
 38 Typ ICONT 0 05.09.2006 14:14:08 2048
 39 Prg SAPLSABE 39 07.03.2005 18:01:13 13312 E
 40 Prg SAPLSECU 40 08.07.2008 17:43:16 87040 E
 41 Typ RSSUBINFO 0 22.11.1999 21:15:17 3072
 42 Prg RSDBSPVD 0 08.07.2008 13:55:28 88064 E
 43 Typ DFIES 0 19.12.2004 17:28:52 10240
 44 Typ VARI 0 16.12.1996 19:38:11 6144
 45 Typ RSDSFIELDS 0 16.12.1996 19:31:30 3072
 46 Prg %_CRSDS 0 07.03.2005 18:01:13 10240 E
 47 Typ RSDSEXPR 0 16.12.1996 19:31:30 3072
 48 Typ RVARI 0 18.06.1999 11:23:08 4096
 49 Prg SAPLSVAR 49 08.07.2008 18:48:35 766976 E
 50 Typ VARIS 0 14.03.1997 19:25:50 2048
 51 Typ RSVARKEY 0 16.12.1996 19:31:51 2048
 52 Prg SAPLSSEL 52 08.07.2008 18:16:58 1155072 E
 53 Typ RSCONVERT 0 01.02.2001 17:18:21 4096
 54 Prg RSDBSPDS 0 08.07.2008 18:16:57 56320 E
 55 Typ RSEXFCODE 0 18.07.1997 17:04:17 2048
 56 Prg SAPLDSYA 56 08.07.2008 17:48:56 45056 E
 57 Prg SAPFSDS1 56 07.03.2005 18:01:13 53248 E
 58 Typ TDCLD 0 14.07.1998 14:53:43 5120
 59 Prg SAPLSDOD 59 23.01.2006 17:31:16 46080 E
 60 Typ DOKIL 0 07.04.1997 18:29:04 3072
 61 Prg SAPLLANG 61 08.07.2008 13:44:44 10240 E
 62 Typ T002 0 08.07.2008 13:44:44 2048
 63 Prg SAPFSPOR 0 08.07.2008 20:08:30 15360 E
 64 Typ RSPARINT 0 10.03.1995 17:53:00 2048
 65 Prg SAPLSTUP 65 08.07.2008 17:39:04 74752 E
 66 Prg SAPLCNDP 66 08.07.2008 16:30:09 195584 E
 67 Prg SAPLSCNT 67 07.03.2005 18:01:13 30720 E
 68 Prg SAPSHDTV 67 07.03.2005 18:01:13 33792 E
 69 Prg SAPFGUICNTL 1 07.03.2005 18:01:13 24576 E
 70 Prg SAPLOLEA 70 08.07.2008 14:26:43 96256 E
 71 Prg SAPLSGUI 71 08.07.2008 17:53:04 84992 E
 72 Prg SAPLSTTM 72 18.11.2005 14:35:29 69632 E
 73 Prg SAPLSBDC 73 08.07.2008 17:40:32 44032 E
 74 Prg SAPLSFES 74 08.07.2008 18:48:19 261120 E
 75 Prg SAPLTHFB 75 08.07.2008 18:47:19 394240 E
 76 Typ WPINFO 0 08.02.1999 14:18:32 6144
 77 Prg SAPLURFC 77 08.07.2008 17:49:18 22528 E
 78 Prg SAPLSPLUGIN 78 07.03.2005 18:01:13 8192 E
 79 Typ SWCBCONT 0 07.10.1997 12:13:50 3072
 80 Typ OLE_VERBS 0 09.02.1995 13:23:37 2048
 81 Typ OLE_PA 0 13.01.1995 11:06:59 2048
 82 Typ SSCRTEXTS 0 15.08.1997 14:15:15 3072
 83 Typ RSBATCHHEADER 0 23.01.2006 19:24:22 6144
 84 Prg SAPLRSBATCH 84 09.07.2008 03:46:40 595968 E
 85 Typ RSBATCHDEBUG 0 14.06.2004 17:15:14 4096
 86 Typ BAL_S_MSG 0 01.02.2001 17:04:55 7168
 87 Prg /1BCDWBEN/SAPLREN0002 87 23.11.2005 13:29:42 237568 E
 88 Prg SAPLSENA 88 08.07.2008 14:29:56 33792 E
 89 Typ RSBATCHCTRL 0 17.09.2004 14:15:41 5120
 90 Typ RSBATCHDATA 0 18.04.2005 09:27:49 6144
 91 Prg SAPLBTCH 91 08.07.2008 18:48:44 1871872 E
 92 Prg SAPLRSSM 92 23.11.2005 13:29:30 1007616 E
 93 Prg SAPLSYDB 93 08.07.2008 16:32:36 63488 E
 94 Prg CL_RSBK_PROCESS===============CP 94 09.07.2008 03:32:34 94208 E
 95 Typ RSBK_S_CMD_R 0 14.06.2004 17:14:04 3072
 96 Typ RSBKCMDPROP 0 18.11.2005 16:13:41 5120
 97 Prg IF_RSBATCH_CALLBACK===========IP 84 09.07.2008 04:09:32 9216 E
 98 Prg IF_RSBATCH_EXECUTE============IP 84 07.03.2005 18:01:13 8192 E
 99 Typ RSBK_S_PROCESS 0 19.04.2005 14:56:01 3072
 100 Typ RSBK_S_CMD_MEMENTO 0 17.09.2004 14:15:27 2048
 101 Prg CL_RSBK_REQUEST===============CP 101 09.07.2008 04:16:32 161792 E
 102 Prg CL_RSBK_REQUEST_GENERAL=======CP 102 09.07.2008 04:16:32 35840 E
 103 Prg SAPLRRSI 103 09.07.2008 04:21:08 246784 E
 104 Typ RSD_S_COB_PRO 0 09.07.2008 02:12:20 23552
 105 Prg CL_RSR========================CP 105 09.07.2008 04:03:31 154624 E
 106 Typ RSR_S_CHANM 0 12.09.2003 11:33:26 2048
 107 Typ RSD_S_DTA 0 09.07.2008 02:12:21 27648
 10

check the status of the background job , if job has faild
the reasion may be because of chaing in the extract structure in the source system.
so we can replicate the data source to resolve this issue.
And also make a check with extract structure using the T.coad RSA3, to find
no of records and to find out any chainges in the structure .

Short dump while using FM "BAPI_GOODSMVT_CREATE" in background

Hi Sir,
I am using the FM "BAPI_GOODSMVT_CREATE" to create the Goods movement. While running the program through a job in background, article docu is generated successfully,,but at the same time it gives short dump in ST22.
Short text
Exception condition "CNTL_ERROR" raised.
A RAISE statement in the program "CL_GUI_CUSTOM_CONTAINER=======CP" raised the
exception
condition "CNTL_ERROR".
Since the exception was not intercepted by a superior
program, processing was terminated.
Please tell me what can be the possible reason for the same and how to avoid the same?
Warm regards
Krishan

There's at least one note addressing this. You should be able to find it quite easily.
Rob

Job SAP_COLLECTOR_FOR_PERFMONITOR - short dump (DBIF_SETG_SQL_ERROR)

Similar Messages

Maybe you are looking for