Tranformation activation throws short dump

Hi all,
I am on SP9 earlier when assinging formulas in transformations i used to get "ASSERTION_FAILED" error. I searched for oss note and installed the following notes (along with there prequisites) in the below order
971020
1008381
1011638.
Now on activation i get a syntax error.
Runtime Errors SYNTAX_ERROR
Date and Time 01/09/2007 13:47:19
Short text
Syntax error in program "CL_RSTRAN_GEN=================CP ".
 What happened?
Error in the ABAP Application Program
The current ABAP program "CL_RSTRAN_TRFN================CP" had to be terminated because it has come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program
 "CL_RSTRAN_GEN=================CP " in include
 "CL_RSTRAN_GEN=================CM00T " in
 line 54:
 "Field "I_NO_FREE" is unknown. It is neither in one of the specified ta"
 "bles nor defined by a "DATA" statement. "DATA" statement. "DATA" state"
 "ment."
The include has been created and last changed by:
 Created by: "BSHKSC "
 Last changed by: "SAP "

Hi Everyone,
We are on support package 9. I had the same assertion failed issues during imports. There were three key notes I wanted to implement, 1008381, 1011638, and 980549. These triggered the need for the rest to be implemented as well. Despite all those notes, we still have the short dump for the the syntax error with "I_NO_FREE" for CL_RSTRAN_GEN. I think there may be one or two other side effects as well since we are seeing other short dumps as well.
Thanks everyone. Craig
=========NOTES IMPLEMENTED===========
0000965972 Time-dependent master data - no data is read
0000976162 Currency trans/unit conversion: Target currency/unit initial
0000977225 Query on remote char terminates with ASSIGN_TYPE_CONFLICT
0000977926 Error BRAIN 070 occurs when filling a unit DataStore
0000979607 Runtime attribute: For example, source system is unavailable
0000980549 Endless D0/WHILE with inconsistent metadata
0000981806 RSUOM 065: No quantity conversion possible
0000983478 Request terminates with CX_SY_CONVERSION_ERROR
0000991119 RSM2 720 - Record (0) or segment (0001) unknown
0000995479 Breakpoints in der Simulation der Transformation
0001007327 RSTRAN 302 Exception .. aufgetreten DatenSatz geskipped
0001007765 Syntaxfehler bei Aktivierung einer Transformation
0001008381 Syntax error although the formula or routine is correct
and...
0001011638, 0000930495, 0000965507, 0000968517, 0000973258, 0000984890,
0000986199

Similar Messages

0PROJECT_ATTR datasource throws short dump in bw

0PROJECT_ATTR datasource throws short dump in BW. On checking the same at source system level in R3 using RSA3 transaction, the error has been cornered that "Project I0640-03/0001 does not exist".
Now i would like to know the related transaction codes to even more corner the problem.
Can anyone help me out in this.
Regards
Baskar
Message was edited by: Baskar Rajagopalan

For information, I dont have authorisation to use SE93.
AS of now the problem has already been cornered that the issue is in R3 extraction only.
Message was edited by: Baskar Rajagopalan

APD is throwing short dump

Hi ,
When I try to check /execute an APD it is raising a short dump with the following message. It is happening with all the customer APD's in the system. Is there any configuration needs to setup to avoid the shortdumps.
Here are the details of error message.
"Termination occurred in the ABAP program "SAPLRRMS" - in "RRMS_X_MESSAGE".
The main program was "RSAN_PR_DSGN_MAIN_TLOGO ".
In the source code you have the termination point in line 82
of the (Include) program "LRRMSU13". "
Regards,
Ramesh

Hello,
On short dump (check ST22 transaction), will probably see the following:
SY-MSGID R7
SY-MSGNO 057
SY-MSGV1 <INFOOBJECT>
SY-MSGV2 A
So please, follow the instructions below:
1. If the infoobject is active version exists. reactivate it again.
2. Please check note 1032937 APD: Partitioning with compound characteristic
This should help for your problem.
Thanks
Edward John

System Throws short dump while executing data source 2LIS_11_VASCL in RSA3.

Hello Experts,
I got short dump while executing data source 2LIS_11_VASCL in RSA3.
The details are as follow.
When importing object "MC11VA0SCL_TAB", the structure did not match the
structure of the target object. The error occurred in component
no. 567.
This may be due to one of the following reasons:
- the structure is actually different (the next field has, for
example, a different data type) or
- the same sequence of components were exported and imported,
but the fields were from other include units.
I have checked source and target fields and those are of same length and data type.
Could you please give some points why this short dump occurs.
Thanks
Konda Reddy

Hi,
This error is not between BI and R/3. It is within R/3. You may have setup data and then modified the datasource.
Delete setup data, generate your datasource again. Setup data and try again.
If you are on a live system with data setup after a downtime and you do not want to delete it, then bring your datasource to the original state when you setup data and pull data.
Cheers....

Queries on infoset throwing short dump

hello all,
We have some queries based on infoset. These queries are throwing dump
Dump info
Category               ABAP Programming Error
Runtime Errors         GETWA_NOT_ASSIGNED
ABAP Program           SAPLRSQ_ISET_RUNTIME
Application Component BW-BEX
i found following
Infoset status - active.
Queries status - active
Queries executing till Selection screen
Infoset - data loaded
Pls help to fix this issue
Thanks

Hi,
Run your Query in RSRT in debug mode( Select SQL Query ). Try to analyze where it's getting failed. You can even analyze the dump in ST22.
Check the definition of your Infoset joins.
Regards,
Suman

Short dump because of start routine.

Hi ,
I have a start routine to delete the certain records of Source package based on some condition .
My code is supposed to delete the source package when the 0DOC_CATEG ( Documant category )
is equal to 'B' or 'G'.Below is my code :
 LOOP AT SOURCE_PACKAGE into <SOURCE_FIELDS> .
 *IF <SOURCE_FIELDS>-DOC_CATEG EQ 'B'
 *OR <SOURCE_FIELDS>-DOC_CATEG EQ 'G'.
 DELETE SOURCE_PACKAGE from <SOURCE_FIELDS> .
 ENDIF.
 ENDLOOP.
There is no synatx error but at the runtime when executing DTP, it throws short dump.
Could somebody tell me what is the issue and if there is any alternate way of code .
Thanks,
Vels

Hi siggi,
The short dump is as follows:
Runtime Errors GETWA_NOT_ASSIGNED
Error analysis
 You attempted to access an unassigned field symbol
 (data segment 32774).
 This error may occur if
 - You address a typed field symbol before it has been set with
 ASSIGN
 - You address a field symbol that pointed to the line of an
 internal table that was deleted
 - You address a field symbol that was previously reset using
 UNASSIGN or that pointed to a local field that no
 longer exists
 - You address a global function interface, although the
 respective function module is not active - that is, is
 not in the list of active calls. The list of active calls
 can be taken from this short dump.

Transformations short dump

Hi All,
While saving or activating infocube transformations in BI development system getting abap short dump.
Short dump:
Runtime Errors         ASSERTION_FAILED
Date and Time          04.08.2009 12:35:44
Short dump has not been completely stored (too big)
Short text
     The ASSERT condition was violated.
What happened?
     In the running application program, the ASSERT statement recognized a
     situation that should not have occurred.
     The runtime error was triggered for one of these reasons:
     - For the checkpoint group specified with the ASSERT statement, the
       activation mode is set to "abort".
     - Via a system variant, the activation mode is globally set to "abort"
       for checkpoint groups in this system.
     - The activation mode is set to "abort" on program level.
     - The ASSERT statement is not assigned to any checkpoint group.
Error analysis
     The following checkpoint group was used: "No checkpoint group specified"
     If in the ASSERT statement the addition FIELDS was used, you can find
     the content of the first 8 specified fields in the following overview:
     " (not used) "
     " (not used) "
     " (not used) "
     " (not used) "
     " (not used) "
     " (not used) "
Trigger Location of Runtime Error
    Program                                 CL_RSTRAN_GEN_STEPGRP=========CP
    Include                                 CL_RSTRAN_GEN_STEPGRP=========CM00O
    Row                                     19
    Module type                             (METHOD)
    Module Name                             OPEN_IF
Source Code Extract
Line SourceCde
    1 METHOD open_if.
    2
    3   DATA:
    4     ls_step_gen TYPE ty_s_gen_param_step.
    5
    6   READ TABLE o_t_step_gen INTO ls_step_gen
    7     WITH TABLE KEY r_step_ = i_r_step_.
    8   ASSERT sy-subrc = 0.
    9   IF ls_step_gen-r_step_exe IS BOUND.
   10     EXIT.
   11   ENDIF.
   12
   13   IF o_if = if_rstran_gen_root=>c_s_status-open.
   14     r_true = rs_c_false.
   15   ELSEIF o_if = space.
   16     r_true = rs_c_true.
   17     o_if = if_rstran_gen_root=>c_s_status-open.
   18   ELSE.
>>>>>     ASSERT 1 = 2. "Invalid call
   20   ENDIF.
   21
   22 ENDMETHOD.
Can anybody tell me why it is throwing short dump in this case.
Suggest me necessary actions to resolve this issue.
Thanks,

Hi Shiva,
Let me explain my problem.
I have one infocube, two transformations. In the infocube I have added few master data objects directly into the corresponding dimensions and mapped to read from master data with current date.
Now I am changing Current date to End date in the transformations. After changing Current date to End date from Calendar Month or Calendar Day activating the transformations. While activating the transformations getting short dump.
Here I am using time dependent master data.
Thanks

ABAP Program Short Dump in BW

I have created a dynamic program which would read any table name as input parameter and print the contents. Its working if I use a small table(3 fields) and the same program is throwing short dump if pass a big table.
Shortdump
"SAPSQL_SELECT_TAB_TOO_SMALL" C
"ZBW_DYNAMIC_ITAB1" or "ZBW_DYNAMIC_ITAB1"
"START-OF-SELECTION"
Error in the line below
 61
 62 * Select Data from table.
>>>>> select * into table <dyn_table>
 64 from (p_table).
 65
Program
*& Report ZBW_DYNAMIC_ITAB1
REPORT ZBW_DYNAMIC_ITAB1.
type-pools: slis.
field-symbols: <dyn_table> type standard table,
 <dyn_wa>,
 <dyn_field>.
data: alv_fldcat type slis_t_fieldcat_alv,
 it_fldcat type lvc_t_fcat.
type-pools : abap.
data : it_details type abap_compdescr_tab,
 wa_details type abap_compdescr.
data : ref_descr type ref to cl_abap_structdescr.
data: new_table type ref to data,
 new_line type ref to data,
 wa_it_fldcat type lvc_s_fcat.
selection-screen begin of block b1 with frame title text .
parameters: p_table(30) type c.
selection-screen end of block b1.
Get the structure of the table.
ref_descr ?= cl_abap_typedescr=>describe_by_name( p_table ).
it_details[] = ref_descr->components[].
loop at it_details into wa_details.
clear wa_it_fldcat.
wa_it_fldcat-fieldname = wa_details-name .
wa_it_fldcat-datatype = wa_details-type_kind.
wa_it_fldcat-intlen = wa_details-length.
wa_it_fldcat-decimals = wa_details-decimals.
append wa_it_fldcat to it_fldcat .
endloop.
Create dynamic internal table and assign to FS
call method cl_alv_table_create=>create_dynamic_table
 exporting
 it_fieldcatalog = it_fldcat
 importing
 ep_table = new_table.
assign new_table->* to <dyn_table>.
Create dynamic work area and assign to FS
create data new_line like line of <dyn_table>.
assign new_line->* to <dyn_wa>.
Select Data from table.
select * from (p_table) into table <dyn_table>
Write out data from table.
loop at <dyn_table> into <dyn_wa>.
do.
 assign component sy-index of structure <dyn_wa> to <dyn_field>.
 if sy-subrc <> 0.
 exit.
 endif.
 if sy-index = 1.
 write:/ <dyn_field>.
 else.
 write: <dyn_field>.
 endif.
enddo.
endloop.

Hi,
The dynamic table that is generated is not converting the exact output length in case of packed numbers.
Foe eg : If there is an packed field of length 7 , the dynamic table is converting it to Char 7 , but the actual output length of Pack 7 is 15.Hence it is giving short dump saying that Internal Table length is not sufficient.
Probably it might have worked for smaller tables for you because you might not have used Packed field in there.
Regards,
Vijay.

Short dumps, tuning

What are techniques used for tuning query performance? Please explain in detail?
What are short dumps how can we check?
What methodologies we follow for the PSA cleansing? Where exactly is the PSA change log where we can delete the request based on timestamp details am using BW 3.1c?
plz help points assured....

Hi,
For query performance please check the following link
http://help.sap.com/saphelp_nw2004s/helpdata/en/41/b987eb1443534ba78a793f4beed9d5/frameset.htm
Short dumps:
A short dump is an program error because of which the process terminates. It is notified and can be viewed in t-code ST22 on a particular usernaem where you can analyze the reason for short dump.
and refer these links
http://publib.boulder.ibm.com/tividd/td/ITMAN/SC32-9195-00/en_US/HTML/sap_add06.htm
short dump
Short dump while loading data?
Update rules activation gives short dump?
Delete of Master Data creates short dump?
PSA:
check the following link
http://help.sap.com/saphelp_nw70/helpdata/EN/bd/c627c88f9e11d4b2c90050da4c74dc/frameset.htm
Hope it help u.
Assign Points if it helps.
Regards,
RKC
Edited by: RKC on Mar 7, 2008 11:29 AM

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 while Activating a Heirarchy

Hi Experts,
I have a hierarchy which is in M version, I am trying to copy hierarchy from Quality to Dev system.
The hierarchy in DEV system is in M version. When I try to activate the Hierarchy I am getting a short dump which I am not able to understand.
I have tried also with the ABAP programe to activate it but still I am getting this.
Sorry to paste all the dump but can any one advise what could be reasons behind heirarchy not getting activated.
Thanks,
Tati.
Please find the Dump message.
What happened?
 Error in the ABAP Application Program
 The current ABAP program "CL_RSSH_MESSAGE_HANDLER=======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
 Only message types A, E, I, W, S, and X are allowed.
Information on where terminated
 Termination occurred in the ABAP program "CL_RSSH_MESSAGE_HANDLER=======CP" -
 in "CALL_MESSAGE".
 The main program was "RSSH_HIERM_START_NEU ".
 In the source code you have the termination point in line 11
 of the (Include) program "CL_RSSH_MESSAGE_HANDLER=======CM003".
Source Code Extract
Line SourceCde
 1 METHOD call_message .
 2
 3 FIELD-SYMBOLS: <l_s_msg> TYPE gt_s_msg.
 4
 5 READ TABLE p_t_msg INDEX 1 ASSIGNING <l_s_msg>.
 6 IF sy-subrc <> 0.
 7 MESSAGE x000.
 8 ENDIF.
 9
 10 <l_s_msg>-handled = rs_c_true.
>>>>> MESSAGE ID <l_s_msg>-msgid TYPE <l_s_msg>-msgty NUMBER <l_s_msg>-msgno
 12 WITH <l_s_msg>-msgv1 <l_s_msg>-msgv2 <l_s_msg>-msgv3 <l_s_msg>-msgv4.
 13
 14
 15 ENDMETHOD. "CALL_MESSAGE

Hi Prasad,
Have you changed the 'Object Status' from INA to ACT when using the program RSDG_TRFN_ACTIVATE?
You can also refer to the note SAP Note 1030987 - Activation of transformations dumps
regards,
Ashvin

DBIF_REPO_SQL_ERROR short dumps while activating data in ODS

Hi All,
We are using BW3.5 with Oracle 9.2 on AIX 5.3 box, from the past few days we are getting DBIF_REPO_SQL_ERROR short dumps frequently while activating data in ODS.
Runtime Error          DBIF_REPO_SQL_ERROR
Date and Time          08.01.2008 13:01:08
     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.
     Internal call code.........: "[REPO/*/43/LOAD/CX_SY_OPEN_SQL_DB=============CP
     Please check the entries in the system log (Transaction SM21).
     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:
     "DBIF_REPO_SQL_ERROR" C
     "SAPLRSSM_PROCESS" or "LRSSM_PROCESSF04"
     "CHECK_IF_ANALYZE_IS_NESSESSARY"
System environment
    SAP Release.............. "640"
    Application server....... "psapdb"
    Network address.......... "158.58.65.11"
    Operating system......... "AIX"
    Release.................. "5.3"
    Hardware type............ "00CD615C4C00"
    Character length......... 16 Bits
    Pointer length........... 64 Bits
    Work process number...... 22
    Short dump setting....... "full"
    Database server.......... "psapdb"
    Database type............ "ORACLE"
    Database name............ "BWP"
    Database owner........... "SAPBWP"
    Character set............ "C"
    SAP kernel............... "640"
    Created on............... "Oct 29 2006 20:49:57"
    Created in............... "AIX 1 5 00538A4A4C00"
    Database version......... "OCI_920 "
    Patch level.............. "155"
    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"
Memory usage.............
Roll..................... 16192
EM....................... 16759424
Heap..................... 0
Page..................... 24576
MM Used.................. 6604384
MM Free.................. 1772536
SAP Release.............. "640"
User and Transaction
    Client.............. 200
    User................ "R3REMOTE"
    Language key........ "E"
    Transaction......... " "
    Program............. "SAPLRSSM_PROCESS"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
Information on where terminated
    The termination occurred in the ABAP program "SAPLRSSM_PROCESS" in
     "CHECK_IF_ANALYZE_IS_NESSESSARY".
    The main program was "RSPROCESS ".
    The termination occurred in line 1143 of the source code of the (Include)
     program "LRSSM_PROCESSF04"
    of the source code of program "LRSSM_PROCESSF04" (when calling the editor
     11430).
    The program "SAPLRSSM_PROCESS" was started as a background job.
    Job name........ "BI_PROCESS_ODSACTIVAT"
    Job initiator... "RPRIYANKA"
    Job number...... 02010102
Also we have a failed job here. Here is the job log.
Job log overview for job:    BI_PROCESS_ODSACTIVAT / 02010102
Date       Time     Message text
08.01.2008 13:01:00 Job started
08.01.2008 13:01:00 Step 001 started (program RSPROCESS, variant &0000000000188, user ID R3REMOTE)
08.01.2008 13:01:02 Activation is running: Data target HBCS_O25, from 1,758 to 1,767
08.01.2008 13:01:02 Data to be activated successfully checked against archiving objects
08.01.2008 13:01:02 SQL: 01/08/2008 13:01:02 R3REMOTE
08.01.2008 13:01:02 ANALYZE TABLE "/BIC/AHBCS_O2540" DELETE
08.01.2008 13:01:02 STATISTICS
08.01.2008 13:01:02 SQL-END: 01/08/2008 13:01:02 00:00:00
08.01.2008 13:01:02 SQL: 01/08/2008 13:01:02 R3REMOTE
08.01.2008 13:01:02 BEGIN DBMS_STATS.GATHER_TABLE_STATS ( OWNNAME =>
08.01.2008 13:01:02 'SAPBWP', TABNAME => '"/BIC/AHBCS_O2540"',
08.01.2008 13:01:02 ESTIMATE_PERCENT => 1 , METHOD_OPT => 'FOR ALL
08.01.2008 13:01:02 INDEXED COLUMNS SIZE 75', DEGREE => 1 ,
08.01.2008 13:01:02 GRANULARITY => 'ALL', CASCADE => TRUE ); END;
08.01.2008 13:01:05 SQL-END: 01/08/2008 13:01:05 00:00:03
08.01.2008 13:01:05     SQL-ERROR: 603 ORA-00603: ORACLE server session terminated by fat al error
08.01.2008 13:01:05 System error: RSDU_ANALYZE_TABLE_ORA/ ORACLE
08.01.2008 13:01:08 ABAP/4 processor: DBIF_REPO_SQL_ERROR
08.01.2008 13:01:08 Job cancelled
Listener is working fine, Checked the RFC connections, Tried restarting the system, tried adding space to the TEMP tablespace as well as PSAPBWP, but they didn't work.
Please help.

The problem got solved as there were DB errors like ORA-01114: IO error writing block to file 256 (block # 126218).
Here the point to be notes is file 256. The number greater than 255 indicates a temp datafile. This indicates an issue with PSAPTEMP tablespace. When checked on PSAPTEMP tablespace, one of the filesystems where one temp data file sitting was full. The filesystem was 100% full. This will prevent the temp datafile to grow and shrink as and when required.
So, adding more space to the filesystem solved the problem.
Thanks to everyone who have shown interest in solving my problem.

Short dump while activating process chain

Please let me know the cause of short dump while activating process chain.. when trying to activate local process chains in metachain it is causing dump

Can you share more details about error.
Have you done any changes to local chain? or is this is new chain?
Try to remove meta chain from schedule, later activate your local chain and meta chain.
schedule your meta chain.

Short Dump while activating Transformation through Program

HI All,
I am getting short dump while activating - Inactive Transformation through Program RSDG_TRFN_ACTIVATE.
However while i can activate single Transformation but if run without selection, I am getting this dump.
Short Description of Dump -
Category
ABAP Programming Error
Runtime Errors
ASSERTION_FAILED
ABAP Program
CL_RSAR_FORMULAS==============CP
Application Component BW-WHM-DST
Date and Time
Please Guide.
Prasad

Hi Prasad,
Have you changed the 'Object Status' from INA to ACT when using the program RSDG_TRFN_ACTIVATE?
You can also refer to the note SAP Note 1030987 - Activation of transformations dumps
regards,
Ashvin

ODS activation, short dump COMPUTE_INT_PLUS_OVERFLOW. How to solve?

Hello Gurus,
We are on BW 3.1.
We have an issue - ODS activation failed due to a short dump.
Runtime Error          COMPUTE_INT_PLUS_OVERFLOW
Exception              CX_SY_ARITHMETIC_OVERFLOW
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
In the current program "SAPLRSSM_PROCESS",
using + or 'ADD' to add the values 2137304138 and 12410267 resulted in a
value greater than 2147483647 or samller than -2147483648. This
leads to a whole number overflow.
Could you please guide me to solve this?
Please let me know if you need more details.
Thanks,
raj

This dump is happening because of the overflow of the size assigned for the variable.
This dump can be avoided by changing the declaration of the variable definition.
DATA: variable_name type p decimals 0.
                          OR
DATA: varibale_name(25) type n decimals 0
Try this. This will resolve your dump.
regards,
brijesh

Tranformation activation throws short dump

Similar Messages

Maybe you are looking for