Shortdump using F4
Hi Experts,
I am getting a dump like:
Runtime Errors
SAPSQL_WHERE_UNKNOWN_OPERATOR
Except. CX_SY_DYNAMIC_OSQL_SYNTAX
Error in the ABAP Application Program
The current ABAP program "SAPLSDH3" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_DYNAMIC_OSQL_SYNTAX',
was not caught in procedure "F4_GET_RESULT" "(FUNCTION)", nor was it
propagated by a RAISING clause.
Do you have a solution for this?
Thanks in advance.
Regards,
MR
Hi Matheus,
You should take a look at SAP note 1256059 (ITS search help: Short dump SAPSQL_IN_ITAB_ILLEGAL_OPTION); in order to solve the issue you will need to upgrade your Kernel Support Package Level to (at least) 180; SAP note 19466 will help you in this process.
I hope this helps.
Best regards,
Cristiano
Similar Messages
-
hi guys,
I am getting OPEN DATASET SHORTDUMP using below code.
can somebody suggest me alteration of code..
Dump says error in READ statement.
DATA : BEGIN OF IT_EDIT OCCURS 0,
CNO(5) TYPE C,
DATE(8) TYPE C,
VENDOR(10) TYPE C,
MATERIAL(18) TYPE C,
STARTDT(8) TYPE C,
ENDDT(8) TYPE C,
QUANTITY(13) TYPE N,
END OF IT_EDIT.
OPEN DATASET P_INFILE FOR INPUT IN TEXT MODE ENCODING DEFAULT.
DO.
IF NOT SY-SUBRC IS INITIAL.
EXIT.
ELSE.
<b> READ DATASET P_OUFILE INTO IT_EDIT.</b>
APPEND IT_EDIT.
ENDIF.
ENDDO.
CLOSE DATASET P_OUFILE.
Regards
Chandra.hi,
pls chk this sample code.
report zfiles_0001.
Parameters: d1 type localfile default '/usr/sap/TST/SYS/Data1.txt',
d2 type localfile default '/usr/sap/TST/SYS/Data2.txt'.
data: itab type table of string.
data: wa type string.
start-of-selection.
Read file
open dataset d1 for input in text mode.
if sy-subrc = 0.
do.
read dataset d1 into wa.
if sy-subrc <> 0.
exit.
endif.
append wa to itab.
enddo.
endif.
close dataset d1.
Copy to new file
open dataset d2 for output in text mode.
loop at itab into wa.
transfer wa to d2.
endloop.
close dataset d2.
Delete the first
delete dataset d1.
regards
anver
if hlpful pls mark points -
Identifying the calling ABAP WD component with 'SYSTEM_CALLSTACK'
Hi everybody,
When I try to trace a abap web dynpro component with the function 'SYSTEM_CALLSTACK', I get a very cryptic entry under "main program" like /1BCWDY/2A5JNGDP2YQFUSHKTBT2==CP. How can I find the name of the WD component with it? Thank you.
Regards,
JinchiHi Jinchi,
Just go to se38 and enter the name of the generated class, like /1BCWDY/2A5JNGDP2YQFUSHKTBT2==CP. Then navigate to the implementation section and double click at an include there. Within the include, at the top, there is comment section that contains the name of the component/view.
Btw.: Looking at a shortdump using st22 reveals the affected component/view within the description.
Best regards,
Thomas -
Dear all,
I have a question regarding a shortdump I'm getting when using transaction MIRO.
I think I know what is causing the shortdump but I'm not sure how to get rid of this shortdump.
Purchase order:
Quantity 1000
price per unit 1 euro
Invoice verification amount
1) Debit invoice 200 euro
2) credit memo 200 euro
3) credit memo 200 euro
As you can see in the invoice verification the end user has booked twice a credit memo to reverse invoice nr 1 instead of booking only 1 credit memo. In the invoice history we have now negative amount of 200 euro.
I'm not sure how to get rid of this negative quantity because if the user tries to post a debit invoice of 200 euro to make the balance zero then the user gets a short dump. I think this is because of the negative amount of 2oo euro.
Do you have suggestions on how to correct this?
regards,
CamillaHi all,
I have analyzed the problem a bit further and I noticed something weird that might be the cause of the shortdumps.
The 2 credit memo's that I gave in my example are reversals (MR8M) of the debit memo. So basically the user was able to reverse a debit memo twice. This should not be possible in SAP. I have tried to recreate the issue but I was not able to reverse a debit memo twice (this makes sense)
I'm not sure if it was because that the system was not stable at that time that the user managed to reverse a debit memo twice.
Has anyone experienced this issue before? Is there any solution to correct this? -
The STOP statement was used outside a report flow.
Hi Gurus,
when i am executing this program it is going to short dump.
pls help me out.
thanks in advance.
Runtime Errors STOP_NO_REPORT
Date and Time 06.10.2008 12:10:06
Short text
The STOP statement was used outside a report flow.
What happened?
Error in the ABAP Application Program
The current ABAP program "YMRP0003" 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 STOP statement is only useful in specific events of the report
processing (that is, the execution of a type 1 program). In this case,
there was no report flow, so the statement could not be executed.
How to correct the error
If the error occurred in your own ABAP program or in an SAP
program you modified, try to remove the error.
System environment
SAP-Release 700
Application server... "ciRDE"
Network address...... "10.131.28.7"
Operating system..... "HP-UX"
Release.............. "B.11.23"
Hardware type........ "ia64"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 3
Shortdump setting.... "full"
Database server... "hpx190"
Database type..... "ORACLE"
Database name..... "RDE"
Database user ID.. "SAPDAT"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Apr 21 2008 20:48:34"
create on........ "HP-UX B.11.23 U ia64"
Database version. "OCI_102 (10.2.0.1.0) "
Patch level. 157
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "HP-UX B.11"
Memory consumption
Roll.... 16192
EM...... 8379680
Heap.... 0
Page.... 65536
MM Used. 3492016
MM Free. 695200
User and Transaction
Client.............. 050
User................ "MBAGGALA"
Language key........ "E"
Transaction......... "CC31 "
Transactions ID..... "48E9EB60C2944602E10000000A831C07"
Program............. "YMRP0003"
Screen.............. "SAPMC29C 0020"
Screen line......... 22
Information on where terminated
Termination occurred in the ABAP program "YMRP0003" - in "SCM-MRP-FSE-12_02".
The main program was "SAPMC29C ".
In the source code you have the termination point in line 138
of the (Include) program "YMRP0003".
Source Code Extract
Line
SourceCde
108
109
110
*This function module read the status of an object
111
112
CALL FUNCTION 'STATUS_TEXT_EDIT'
113
EXPORTING
114
client = sy-mandt
115
flg_user_stat = lc_flagx
116
objnr = ls_ecm_data-objnr
117
only_active = lc_flagx
118
spras = sy-langu
119
IMPORTING
120
line = lf_sttxt
121
user_line = lf_asttx
122
EXCEPTIONS
123
object_not_found = 1
124
OTHERS = 2.
125
126
CHECK NOT sy-tcode EQ 'CC32'.
127
*-- Begin of Changes made by DGupta1 on 07/12/2006--
128
Changes are made to update the Change Number Dates While Calling CC32
129
from custom transaction YC06 only
130
CHECK NOT sw_yc06 EQ 'X'.
131
*-- End of Changes made by DGupta1 on 07/12/2006--
132
133
CHECK NOT lf_sttxt CS 'ECCM' AND NOT lf_sttxt CS 'ECOR'.
134
135
136
IF ls_ecm_data-datuv NE lc_maxdate.
137
MESSAGE s011.
>>>>>
STOP.
139
ENDIF.
140
141
142
IF lf_lastd < lf_artwd.
143
MESSAGE s012.
144
STOP.
145
ENDIF.
146
147
IF ls_ecm_data-lvorm = lc_flagx.
148
MESSAGE s013.
149
STOP.
150
ENDIF.
151
152
WRITE: lf_lastd TO lf_lastd_string.
153
WRITE: lf_artwd TO lf_artwd_string.
154
155
156
IF ls_ecm_data-ccart NE lc_fixd.
157
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
0
SY-TABIX
0
SY-DBCNT
1
SY-FDPOS
40
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
ARC0H
SY-UCOMM
FCBU
SY-TITLE
Create ECR: Object Types
SY-MSGTY
S
SY-MSGID
YMRP
SY-MSGNO
011
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20081006
SY-UZEIT
121006
SY-XPROG
SAPCNVE
SY-XFORM
CONVERSION_EXIT
Active Calls/Events
No. Ty. Program Include Line
Name
7 FORM YMRP0003 YMRP0003 138
SCM-MRP-FSE-12_02
6 FUNCTION SAPLXCCA ZXCCAU05 39
EXIT_SAPMC29C_005
5 FORM SAPMC29C MC29CFS1_SAVE_USER_EXIT 36
SAVE_USER_EXIT
4 FORM SAPMC29C MC29CFF2_FCODE_FCBU_EXECUTE 88
FCODE_FCBU_EXECUTE
3 FORM SAPMC29C MC29CFO1_OKCODE_CHECK 252
OKCODE_CHECK
2 MODULE (PAI) SAPMC29C MC29CI10_OKCODE 12
OKCODE
1 MODULE (PAI) SAPMC29C MC29CI10_DYNPRO_CALL 11
DYNPRO_CALL
Chosen variables
Name
Val.
No. 7 Ty. FORM
Name SCM-MRP-FSE-12_02
SY-REPID
YMRP0003
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5455333322222222222222222222222222222222
9D20000300000000000000000000000000000000
SY-TCODE
CC31
00000000000000000000
00000000000000000000
44332222222222222222
33310000000000000000
SW_YC06
0
0
2
0
LF_STTXT
CRTD
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
4554222222222222222222222222222222222222
3244000000000000000000000000000000000000
SYST-REPID
YMRP0003
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5455333322222222222222222222222222222222
9D20000300000000000000000000000000000000
LS_ECM_DATA-DATUV
20081006
00000000
00000000
33333333
20081006
LC_MAXDATE
29991231
00000000
00000000
33333333
29991231
%_PRINT
000 0###
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SY-MSGID
YMRP
00000000000000000000
00000000000000000000
54552222222222222222
9D200000000000000000
LC_FLAGX
X
0
0
5
8
SPACE
0
0
2
0
SY-MSGNO
011
000
000
333
011
LC_ITEM
EUR_SCM-PUR-FSE-12_02
000000000000000000000
000000000000000000000
455554425552454233533
552F33DD052D635D12F02
SY-MSGV1
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
SY-MSGV2
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
SY-MSGV3
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
SY-MSGV4
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
LF_LASTD
00000000
00000000
00000000
33333333
00000000
LF_ARTWD
00000000
00000000
00000000
33333333
00000000
SY-SUBRC
0
0000
0000
No. 6 Ty. FUNCTION
Name EXIT_SAPMC29C_005
ECM_ALT_DATE
Table IT_665[0x202]
\FUNCTION=EXIT_SAPMC29C_005\DATA=ECM_ALT_DATE
Table reference: 113
TABH+ 0(20) = 0000000000000000000000000000000000000000
TABH+ 20(20) = 000000710000029900000000000000CAFFFFFFFF
TABH+ 40(16) = 040000DB000006200010249401800000
store = 0x0000000000000000
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 113 (0x00000071)
label = 665 (0x00000299)
fill = 0 (0x00000000)
leng = 202 (0x000000CA)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000018
occu = 16 (0x00000010)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
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
ECM_DATA
050 01001020081006 00000000 00000000 dsfasdddffSS
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
3332222222222223333333333333322222222222233333333222222222222333333332222222222226766766666552
0500000000000000100102008100600000000000000000000000000000000000000000000000000004361344466330
ECM_EFFECTIVITY
Table IT_666[0x464]
\FUNCTION=EXIT_SAPMC29C_005\DATA=ECM_EFFECTIVITY
Table reference: 126
TABH+ 0(20) = 0000000000000000000000000000000000000000
TABH+ 20(20) = 0000007E0000029A00000000000001D0FFFFFFFF
TABH+ 40(16) = 040000DB000006800010249401800000
store = 0x0000000000000000
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 126 (0x0000007E)
label = 666 (0x0000029A)
fill = 0 (0x00000000)
leng = 464 (0x000001D0)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000020
occu = 16 (0x00000010)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
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
ECM_HIERARCHY
Table IT_667[0x120]
\FUNCTION=EXIT_SAPMC29C_005\DATA=ECM_HIERARCHY
Table reference: 110
TABH+ 0(20) = 0000000000000000000000000000000000000000
TABH+ 20(20) = 0000006E0000029B0000000000000078FFFFFFFF
TABH+ 40(16) = 040000DB000006B00010249401800000
store = 0x0000000000000000
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 110 (0x0000006E)
label = 667 (0x0000029B)
fill = 0 (0x00000000)
leng = 120 (0x00000078)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000021
occu = 16 (0x00000010)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
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
ECM_MNT_VALUE
0000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222223333333333333333222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ECM_OBJMNGREC
Table IT_668[0x600]
\FUNCTION=EXIT_SAPMC29C_005\DATA=ECM_OBJMNGREC
Table reference: 107
TABH+ 0(20) = 0000000000000000000000000000000000000000
TABH+ 20(20) = 0000006B0000029C0000000000000258FFFFFFFF
TABH+ 40(16) = 040000DB000005C0001024C401800000
store = 0x0000000000000000
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 107 (0x0000006B)
label = 668 (0x0000029C)
fill = 0 (0x00000000)
leng = 600 (0x00000258)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000016
occu = 16 (0x00000010)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
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
ECM_OBJ_TYPE
Table IT_669[28x192]
\FUNCTION=EXIT_SAPMC29C_005\DATA=ECM_OBJ_TYPE
Table reference: 116
TABH+ 0(20) = C0000009448BF3E0000000000000000000000000
TABH+ 20(20) = 000000740000029D0000001C000000C0FFFFFFFF
TABH+ 40(16) = 040000DB000005600010249421800000
store = 0xC0000009448BF3E0
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 116 (0x00000074)
label = 669 (0x0000029D)
fill = 28 (0x0000001C)
leng = 192 (0x000000C0)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000014
occu = 16 (0x00000010)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0xC0000009448B8270
pgHook = 0xC0000009448BF440
idxPtr = 0x0000000000000000
shmTabhSet = 0x0000000000000000
id = 195 (0x000000C3)
refCount = 1 (0x00000001)
tstRefCount = 0 (0x00000000)
lineAdmin = 48 (0x00000030)
lineAlloc = 48 (0x00000030)
shmVersId = 0 (0x00000000)
shmRefCount = 2 (0x00000002)
>>>>> 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
TRANS_TYP
H
0
0
4
8
D_ASTTX
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
SY-REPID
SAPLXCCA
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5454544422222222222222222222222222222222
310C833100000000000000000000000000000000
L_ITEM
EUR_SCM-MRP-FSE-12_02
000000000000000000000000000000
000000000000000000000000000000
455554424552454233533222222222
552F33DDD20D635D12F02000000000
LI_YBS00001
050EUR_SCM-MRP-FSE-12_02 YMRP0003 SCM-MRP-FSE-12_02
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
3334555544245524542335332222222225455333322222222222222222222222222222222544245524542335332222
050552F33DDD20D635D12F020000000009D2000030000000000000000000000000000000033DDD20D635D12F020000
SY-SUBRC
0
0000
0000
SYST
#######################(###############Z################################################XC####
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000E000100
0000000000000000000000020000000000000005000000000100000000000000000000000000010900000001540000
0000000100000A0000000108010001000000000A0000000000000000000000000000000000000B000008000083000C
LI_YBS00001-REPORT
YMRP0003
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5455333322222222222222222222222222222222
9D20000300000000000000000000000000000000
LI_YBS00001-FORM
SCM-MRP-FSE-12_02
000000000000000000000000000000
000000000000000000000000000000
544245524542335332222222222222
33DDD20D635D12F020000000000000
LS_YBS00001
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
LS_YBS00001-ENABLED
0
0
2
0
LS_YBS00001-REPORT
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
LS_YBS00001-FORM
000000000000000000000000000000
000000000000000000000000000000
222222222222222222222222222222
000000000000000000000000000000
SYST-REPID
SAPLXCCA
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5454544422222222222222222222222222222222
310C833100000000000000000000000000000000
No. 5 Ty. FORM
Name SAVE_USER_EXIT
RET_CODE
0
0000
0000
SY-SUBRC
0
0000
0000
SY-MSGID
YMRP
00000000000000000000
00000000000000000000
54552222222222222222
9D200000000000000000
DARSTAB[]
Table[initial]
AEDTB[]
Table IT_650[0x202]
\PROGRAM=SAPMC29C\DATA=AEDTB[]
Table reference: 129
TABH+ 0(20) = 0000000000000000C000000944A25D7000000000
TABH+ 20(20) = 000000810000028A00000000000000CAFFFFFFFF
TABH+ 40(16) = 0400000000000EF00010249401800000
store = 0x0000000000000000
ext1 = 0xC000000944A25D70
shmId = 0 (0x00000000)
id = 129 (0x00000081)
label = 650 (0x0000028A)
fill = 0 (0x00000000)
leng = 202 (0x000000CA)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000065
occu = 16 (0x00000010)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
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 = 0x0000000000000000
collHook = 0x0000000000000000
ext2 = 0xC000000944AFAD80
>>>>> 2nd level extension part <<<<<
tabhBack = 0xC000000944A23AF0
delta_head = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x0000000000000000
pb_handle = 0x0000000000000000
CC07
000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000
222222222222222222222222222222222222222222222222222222222222222
000000000000000000000000000000000000000000000000000000000000000
AENRB
050 01001020081006 00000000 00000000 dsfasdddffSS
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
3332222222222223333333333333322222222222233333333222222222222333333332222222222226766766666552
0500000000000000100102008100600000000000000000000000000000000000000000000000000004361344466330
DARSTAB
00000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000
22222222222222222222222222222222222222222200
00000000000000000000000000000000000000000000
AEEFB[]
Table IT_651[0x464]
\PROGRAM=SAPMC29C\DATA=AEEFB[]
Table reference: 105
TABH+ 0(20) = 0000000000000000C000000944AFADF000000000
TABH+ 20(20) = 000000690000028B00000000000001D0FFFFFFFF
TABH+ 40(16) = 0400000000000F500010249401800000
store = 0x0000000000000000
ext1 = 0xC000000944AFADF0
shmId = 0 (0x00000000)
id = 105 (0x00000069)
label = 651 (0x0000028B)
fill = 0 (0x00000000)
leng = 464 (0x000001D0)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000067
occu = 16 (0x00000010)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
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 = 0x0000000000000000
collHook = 0x0000000000000000
ext2 = 0xC0000009448F3220
>>>>> 2nd level extension part <<<<<
tabhBack = 0xC00000094482B060
delta_head = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x0000000000000000
pb_handle = 0x0000000000000000
DCTAB[]
Table IT_35[7x16]
\PROGRAM=SAPMC29C\DATA=DCTAB[]
Table reference: 25
TABH+ 0(20) = C000000944921280000000000000000000000000
TABH+ 20(20) = 00000019000000230000000700000010FFFFFFFF
TABH+ 40(16) = 0400000000001BB00010249401800000
store = 0xC000000944921280
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 25 (0x00000019)
label = 35 (0x00000023)
fill = 7 (0x00000007)
leng = 16 (0x00000010)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000133
occu = 16 (0x00000010)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)Dear Rajesh!
Please advise me, what have you done to resolve your problem!!??
I get next problem when i try to start some transaction:
Short text
Syntax error in program "SAPLPA_PACKAGE_SERVICES ".
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLSFW_COMMON" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "SAPLPA_PACKAGE_SERVICES " in
include "LPA_PACKAGE_SERVICES$25 " in
line 13:
"The type "TPCHK_FROZEN_OBJECTS_H" is unknown."
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 "SAPLSFW_COMMON" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
The following syntax error was found in the program SAPLPA_PACKAGE_SERVICES :
"The type "TPCHK_FROZEN_OBJECTS_H" is unknown."
Trigger Location of Runtime Error
Program SAPLSFW_COMMON
Include LSFW_COMMONU01
Row 117
Module type (FUNCTION)
Module Name SFW_GET_SWITCHPOS
Source Code Extract
Line
SourceCde
87
IF sy-subrc = 0.
88
<fs_switchpos>-switch_id = devc_resultline-switch_id .
89
<fs_switchpos>-state = devc_resultline-state .
90
<fs_switchpos>-text = devc_resultline-text .
91
92
INSERT <fs_switchpos> INTO TABLE resulttab. "Ergebnis merken
93
CONTINUE.
94
ENDIF.
95
96
97
READ TABLE gt_sfw_package INTO wa_sfw_package WITH TABLE KEY
98
devclass = lf_devclass
99
version = 'A' .
100
101
IF sy-subrc = 0. "Objekt ist in einem Paket mit Schalter
102
<fs_switchpos>-switch_id = wa_sfw_package-switch_id .
103
104
ELSE. "gucken, ob es sich um geschachtelte Pakete handelt
105
106
DO 20 TIMES.
107
108
CLEAR wa_superpackage .
109
110
READ TABLE gt_superpackage INTO wa_superpackage WITH TABLE KEY
111
devclass = lf_devclass.
112
113
IF sy-subrc = 0 .
114
lf_superpackage = wa_superpackage-parentcl.
115
ELSE.
116
>>>>>
CALL FUNCTION 'PA_GET_SUPER_PACKAGE_NAME'
118
EXPORTING
119
i_package_name = lf_devclass
120
i_direct_select = 'X'
121
IMPORTING
122
e_super_package_name = lf_superpackage.
123
124
125
wa_superpackage-devclass = lf_devclass .
126
wa_superpackage-parentcl = lf_superpackage .
127
INSERT wa_superpackage INTO TABLE gt_superpackage .
128
129
ENDIF.
130
131
IF lf_superpackage = space .
132
<fs_switchpos>-state = space .
133
<fs_switchpos>-switch_id = space .
134
EXIT. "Enstation !
135
ELSE .
136 -
Summation button in ALV report is giving shortdump
Dear All,
I have developed a ALV report. The report is a simple ALV report (Using REUSE_ALV_GRID_DISPLAY). When I am pressing the summation button at the top, it is giving a shortdump. The reason I have found out is the no. of columns are very large (45 to 50). Can anyone suggest how to handle this situation?
Best wishes,
AtanuHi atanu,
then you can use DO_SUM = 'X' (for the field which you want to sum option) in the fieldcat , this will try to sum while display it self.i mean in list display it will show the totals also.
then you need not to explicitly click on SUM button.
Regards
vijay -
Create a new record in pa0001 infotype using hr_infotype_opeation.......
Hi All,
i am inserting a new record in infotype pa0001 using hr_infotype_operation....
at the time system give the shortdumps
"The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X)."
please any one to give the solution....
thank
mahiYou need to use two BAPIs one before and one after 'HR_INFOTYPE_OPERATION',like this :
'BAPI_EMPLOYEE_ENQUEUE'
'HR_INFOTYPE_OPERATION'
'BAPI_EMPLOYEE_DEQUEUE'
Reward IF Found Helpful. -
Not able to use Commit after the function module STATUS_OBJECT_CREATE
I am using function module STATUS_OBJECT_CREATE
CALL FUNCTION 'STATUS_OBJECT_CREATE'
EXPORTING
CHGKZ = 'X'
CLIENT = SY-MANDT
OBJNR = LV_OBJNR3
OBTYP = 'IWE'
STSMA = 'ZS_RE_01'
IMPORTING
OBJNR = LV_OBJNR3.
STONR = LV_STONR.
IF SY-SUBRC = 0.
COMMIT WORK.
ENDIF.
i am getting error after the COMMIT WORK .
I am not getting any issue in the function module .after the function module i am using the COMMIT WORK and i am getting the following error message
Category ABAP Programming Error
Runtime Errors SAPSQL_ARRAY_INSERT_DUPREC
Except. CX_SY_OPEN_SQL_DB
ABAP Program SAPLBSVU
Application Component CA-GTF-TS-SMT
Date and Time 03/17/2014 07:01:29
|Short text |
| The ABAP/4 Open SQL array insert results in duplicate database records. |
|What happened? |
| Error in the ABAP Application Program |
| |
| The current ABAP program "SAPLBSVU" 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 |
| An exception occurred that is explained in detail below. |
| The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught |
| in |
| procedure "STATUS_UPDATE" "(FUNCTION)", nor was it propagated by a RAISING |
| clause. |
| Since the caller of the procedure could not have anticipated that the |
| exception would occur, the current program is terminated. |
| The reason for the exception is: |
| If you use an ABAP/4 Open SQL array insert to insert a record in |
| the database and that record already exists with the same key, |
| this results in a termination. |
| |
| (With an ABAP/4 Open SQL single record insert in the same error |
| situation, processing does not terminate, but SY-SUBRC is set to 4.) |
|How to correct the error |
| Use an ABAP/4 Open SQL array insert only if you are sure that none of |
| the records passed already exists in the database. |
| |
| 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: |
| |
| "SAPSQL_ARRAY_INSERT_DUPREC" "CX_SY_OPEN_SQL_DB" |
| "SAPLBSVU" or "LBSVUU01" |
| "STATUS_UPDATE" |
| |
| 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. |
| |
| The exception must either be prevented, caught within proedure |
| "STATUS_UPDATE" "(FUNCTION)", or its possible occurrence must be declared in |
| the |
| RAISING clause of the procedure. |
| To prevent the exception, note the following: |
|System environment |
| SAP Release..... 702 |
| SAP Basis Level. 0010 |
| |
| Application server... "sds6ci" |
| Network address...... "11.224.101.53" |
| Operating system..... "Linux" |
| Release.............. "2.6.18-194.el5" |
| Hardware type........ "x86_64" |
| Character length.... 16 Bits |
| Pointer length....... 64 Bits |
| Work process number.. 17 |
| Shortdump setting.... "full" |
| |
| Database server... "gctsdb01lds.hsi.hugh" |
| Database type..... "ORACLE" |
| Database name..... "DS6" |
| Database user ID.. "SAPDS4" |
| |
| Terminal.......... "GCTEMP02VDI" |
| |
| Char.set.... "C" |
| |
| SAP kernel....... 720 |
| created (date)... "Sep 14 2013 05:28:14" |
| create on........ "Linux GNU SLES-9 x86_64 cc4.1.2 use-pr130820" |
| Database version. "OCI_102, 10.2.0.5.0, V2, default" |
| |
| Patch level. 500 |
| Patch text.. " " |
| |
| Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*" |
| SAP database version. 720 |
| Operating system..... "Linux 2.6, Linux 3" |
| |
| Memory consumption |
| Roll.... 1317248 |
| EM...... 0 |
| Heap.... 0 |
| Page.... 0 |
| MM Used. 1242912 |
| MM Free. 53400 |
|User and Transaction |
| Client.............. 160 |
| User................ "DV018458" |
| Language key........ "E" |
| Transaction......... "SE38 " |
| Transaction ID...... "5323C30FC9364665E10000000BE06533" |
| |
| EPP Whole Context ID.... "002655EE0F241ED3ABB7D81260A28C44" |
| EPP Connection ID....... 00000000000000000000000000000000 |
| EPP Caller Counter...... 0 |
| |
| Program............. "SAPLBSVU" |
| Screen.............. "RSM13000 3000" |
| Screen Line......... 2 |
| Debugger Active..... "none" |
|Information on where terminated |
| Termination occurred in the ABAP program "SAPLBSVU" - in "STATUS_UPDATE". |
| The main program was "RSM13000 ". |
| |
| In the source code you have the termination point in line 60 |
| of the (Include) program "LBSVUU01". |
| The program "SAPLBSVU" was started in the update system. |
| The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in |
| procedure "STATUS_UPDATE" "(FUNCTION)", but it was neither handled locally nor |
| declared |
| in the RAISING clause of its signature. |
| |
| The procedure is in program "SAPLBSVU "; its source code begins in line |
| 1 of the (Include program "LBSVUU01 ". |
|Source Code Extract |
|Line |SourceCde |
| 30| LOOP AT jsto_upd WHERE chgkz = 'X'. |
| 31| CHECK: jsto_upd-chgnr > '000', |
| 32| jsto_upd-stsma NE jsto_upd-stsma_old. |
| 33| CLEAR jcdo_tab. |
| 34| MOVE-CORRESPONDING jsto_upd TO jcdo_tab. |
| 35| MOVE-CORRESPONDING chdat TO jcdo_tab. |
| 36| jcdo_tab-stsma_new = jsto_upd-stsma. |
| 37| APPEND jcdo_tab. |
| 38| ENDLOOP. |
| 39|* Änderungen zu Einzelstatus (Insert) |
| 40| LOOP AT jest_ins WHERE chgkz = 'X'. |
| 41| CHECK jest_ins-chgnr > '000'. |
| 42| CLEAR jcds_tab. |
| 43| MOVE-CORRESPONDING jest_ins TO jcds_tab. |
| 44| MOVE-CORRESPONDING chdat TO jcds_tab. |
| 45| jcds_tab-chind = 'I'. |
| 46| APPEND jcds_tab. |
| 47| ENDLOOP. |
| 48|* Änderungen zu Einzelstatus (Update) |
| 49| LOOP AT jest_upd WHERE chgkz = 'X'. |
| 50| CHECK jest_upd-chgnr > '000'. |
| 51| CLEAR jcds_tab. |
| 52| MOVE-CORRESPONDING jest_upd TO jcds_tab. |
| 53| MOVE-CORRESPONDING chdat TO jcds_tab. |
| 54| jcds_tab-chind = 'U'. |
| 55| APPEND jcds_tab. |
| 56| ENDLOOP. |
| 57|* Verbuchung Statusobjekte |
| 58| DESCRIBE TABLE jsto_ins LINES sy-tabix. |
| 59| IF sy-tabix > 0. |
|>>>>>| INSERT jsto CLIENT SPECIFIED |
| 61| FROM TABLE jsto_ins. |
| 62| ENDIF. |
| 63| DESCRIBE TABLE jsto_upd LINES sy-tabix. |
| 64| IF sy-tabix > 0. |
| 65| field-symbols <fs_jsto_line> like jsto_upd. |
| 66| loop at jsto_upd assigning <fs_jsto_line>. |
| 67| IF <fs_jsto_line>-chgnr = '000'. |
| 68| <fs_jsto_line>-chgnr = '999'. |
| 69| ENDIF. |
| 70|* on change of status profile delete user status related to old profile |
| 71| IF <fs_jsto_line>-STSMA NE <fs_jsto_line>-STSMA_OLD. |
| 72| DELETE FROM JEST CLIENT SPECIFIED WHERE |
| 73| MANDT = <fs_jsto_line>-MANDT AND |
| 74| OBJNR = <fs_jsto_line>-OBJNR AND |
| 75| STAT LIKE 'E%'. |
| 76| DELETE FROM JCDS CLIENT SPECIFIED WHERE |
| 77| MANDT = <fs_jsto_line>-MANDT AND |
| 78| OBJNR = <fs_jsto_line>-OBJNR AND |
| 79| STAT LIKE 'E%'. |i tried with out using commmit but it is not creating Status.
When i see the function module help and they are trying to COMMIT
FU STATUS_OBJECT_CREATE
Short Text
Create Status Object
Functionality
The function module generates a status object.
Take the object number from the object number management (function modules OBJECT_NUMNBER_GET_xx).
If no object number is given, the module takes a temporary object number that must be replaced later (function module STATUS_OBJECT_SWITCH_NUMBER).
Example
Creating an internal order with number 100123 (object type "ORC") for status profile "STATSCHEM" with final object number
call function 'OBJECT_NUMBER_GET_OR'
exporting
aufnr = '100123'
importing objnr = objektnummer.
call function 'STATUS_OBJECT_CREATE'
exporting
objnr = objektnummer
obtyp = 'ORC'
stsma = 'STATSCHEM'.
commit work.
Creating the same order with a temporary object number
data: objectkey like ionra.
* TBO00-REFSTRUCT for object type 'OR' is 'IONRA'
objectkey-aufnr = '100123'.
call function 'STATUS_OBJECT_CREATE'
exporting
i_objectkey = objectkey
obtyp = 'ORC'
stsma = 'STATSCHEM'.
importing
objnr = objektnummer.
call function 'OBJECT_NUMBER_GET_OR'
exporting
aufnr = '100123'
importing objnr = objektnummer_neu.
call function 'STATUS_OBJECT_SWITCH_NUMBER'
exporting
objnr_old = objektnummer
objnr_new = objektnummer_neu.
commit work.
Notes -
Shortdump in monitor after upgrade to BI 7.0
Hi guru's,
We just went through the technical upgrade to BI 7.0 . However we are still using RSA1OLD at the moment.
We are having an issue with the monitor. While checking failed loads, whenever we go from the details tab to the header tab, we get a shortdump.
In ST22 it tells me to look for notes with the following key words :
"MESSAGE_TYPE_X" " "
"SAPLRSSM_LOAD" or "LRSSM_LOADU14"
"RSSM_RSLDTDONE_READ"
But I wasn't able to find any related note.
Did anybody else encountered the same issue before ?
Thanks for your help !Hello SB,
Did you check the available OLAP cache? By default it is set to 4.0 MB, which is not sufficient. You can change that. Also, check the persistence method for the same.
May I reqeust you to kindly share the documentation you have for this upgrade?
We are planning the upgrade from 3.5 to 7.0 few weeks.
Would really appreciate your help.
Thanks & Best Regards,
Pramod. -
Shortdump "ITAB_DUPLICATE_KEY" in SICF when creating an alias
Hi
I'm trying to create a reference to the WSHANDLER service in SICF, on a WAS 7.00 system (IDES), but when i'm switching to the tab "Alias Target", the system generates a Shortdump (see below).
Have any of you experienced/solved this problem (It's on an IDES System so i'm afraid that help on the OSS isn't very likely )
I have found a post from [mani sahay,|DSWP;, with at reference to OSS Note 1042052, but it doesn't seem to exist
Any help on this issue would be very appreciated
Regards
Morten Nielsen
Dump
Runtime Errors ITAB_DUPLICATE_KEY
Date and Time 03.03.2008 11:42:00
Short text
A row with the same key already exists.
What happened?
Error in the ABAP Application Program
The current ABAP program "RSICFTREE" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
An entry was to be entered into the table
"\PROGRAM=RSICFTREE\DATA=GT_ALIAS_ICFS[]" (which should have
had a unique table key (UNIQUE KEY)).
However, there already existed a line with an identical key.
The insert-operation could have ocurred as a result of an INSERT- or
MOVE command, or in conjunction with a SELECT ... INTO.
The statement "INSERT INITIAL LINE ..." cannot be used to insert several
initial lines into a table with a unique key.
Trigger Location of Runtime Error
Program RSICFTREE
Include ICFTREE_FORMS
Row 2.663
Module type (FORM)
Module Name INIT_ALIAS_TREETABLESHi Morten, I have the exact same problem with creating a reference service to the WEBGUI in SICF.System is ECC 6.0. Did you ever get this resolved? Thanks, Julie
-
BPC 7.5 NW on BW 7.3 - Short Dump when using BADI
Hello all,
When migrating from MS bpc to Netweaver we've had to move some logic from script to BADI.
(Runlogic not supported)
However we now get shortdumps in when calling the BADI'
It works in BW 7.0 but now that we are on BW7.3 the error appears and shordumps occur.
During the upgrade SAP have updated the Class CL_UJR_WRITE_BACK to include a method "GET_DELTA"
That's where we have the problem. No OSS notes for it yet.
The problem shortsumps as follows:
Short Dump Log.
Category ABAP Programming Error
ABAP Program CL_UJR_WRITE_BACK=============CP
Application Component CPM-BPC
"ASSIGN_TYPE_CONFLICT" " "
"CL_UJR_WRITE_BACK=============CP" bzw.
"CL_UJR_WRITE_BACK=============CM00U"
"GET_DELTA"
Error occurs at line statement
ASSIGN COMPONENT uj00_cs_fieldname-keyfigure OF STRUCTURE <ls_data> TO <l_value>.
Any help out there?
Please.........
Thanks
PaulHi Paul,
First of all, there is a How To Guide for RUNLOGIC implementation. It uses BAdI approach as well, but doesn't call WRITE_BACK that can change from version to version.
Second, you should be able to see that method GET_DELTA is being called under
IF D_CALC_DELTA eq abap_true and df_bw_delta eq abap_false.
D_CALC_DELTA is set to TRUE only in Method WRITE_BACK_INT; I hope you aren't using that one.
DF_BW_DELTA is taken from DM Package parameters. Can you check what you have there or put just a break-point in PACKAGE_LOGIC_1 to see what value those 2 variables have?
Hope this helps,
Gersh -
Shortdump problem for loadinf data from ODS to InfoCube
hai
im trying to load the data from ODS to InfoCube.But i got the following error like below
Short dump in the Warehouse
Diagnosis
The data update was not completed. A short dump has probably been logged in BW providing information about the error.
<b>System response
"Caller 70" is missing.
Further analysis:
Search in the BW short dump overview for the short dump belonging to the request. Pay attention to the correct time and date on the selection screen.
You get a short dump list using the Wizard or via the menu path "Environment -> Short dump -> In the Data Warehouse".
Error correction:
Follow the instructions in the short dump.</b>
I looked at the shortdump.But it says that there is no shortdump for that particular date selection.
pls tell me wht i have to do
i ll assing the points
bye
rizwanHi Rizwan,
Why does the error occurs ?
This error normally occurs whenever BW encounters error and is not able to classify them. There could be multiple reasons for the same
o Whenever we are loading the Master Data for the first time, it creates SIDs. If system is unable to create SIDs for the records in the Data packet, we can get this error message.
o If the Indexes of the cube are not deleted, then it may happen that the system may give the caller 70 error.
o Whenever we are trying to load the Transactional data which has master data as one of the Characteristics and the value does not exist in Master Data table we get this error. System can have difficultly in creating SIDs for the Master Data and also load the transactional data.
o If ODS activation is taking place and at the same time there is another ODS activation running parallel then in that case it may happen that the system may classify the error as caller 70. As there were no processes free for that ODS Activation.
o It also occurs whenever there is a Read/Write occurring in the Active Data Table of ODS. For example if activation is happening for an ODS and at the same time the data loading is also taking place to the same ODS, then system may classify the error as caller 70.
o It is a system error which can be seen under the Status tab in the Job Over View.
What happens when this error occurs ?
The exact error message is System response "Caller 70" is missing.
It may happen that it may also log a short dump in the system. It can be checked at "Environment -> Short dump -> In the Data Warehouse".
What can be the possible actions to be carried out ?
If the Master Data is getting loaded for the first time then in that case we can reduce the Data Package size and load the Info Package. Processing sometimes is based on the size of Data Package. Hence we can reduce the data package size and then reload the data again. We can also try to split the data load into different data loads
If the error occurs in the cube load then we can try to delete the indexes of the cube and then reload the data again.
If we are trying to load the Transactional and Master Data together and this error occurs then we can reduce the size of the Data Package and try reloading, as system may be finding it difficult to create SIDs and load data at the same time. Or we can load the Master Data first and then load Tranactional Data
If the error is happening while ODS activation cause of no processes free, or available for processing the ODS activation, then we can define processes in the T Code RSCUSTA2.
If error is occurring due to Read/Write in ODS then we need to make changes in the schedule time of the data loading.
Once we are sure that the data has not been extracted completely, we can then go ahead and delete the red request from the manage tab in the InfoProvider. Re-trigger the InfoPackage again.
Monitor the load for successful completion, and complete the further loads if any in the Process Chain.
(From Re: caller 70 missing).
Also check links:
Caller 70 is missing
Re: Deadlock - error
"Caller 70 Missing" Error
Caller 70 missing.
Bye
Dinesh -
Transfer amount fields to app. server using fieldsymbol
Hi,,
I am facing a strange problem while using fieldsymbols .Here is my requirement.
I have a custom table records ( which also contains amount fields ) in fieldsymbol , which i need to transfer to application server . But when i am trying to transfer to file , using Transfer <final> to p_file , amount fields are not getting converted to characted format and program is going to shortdump. After that i tried assigning this <final> to another fieldsymbol , of type c (using casting ) , records were able to transfer to file but the amount fields are not being converted to readable format (i.e unknown symbols , like #p## ) .
I even tried SAP_CONVERT_TO_TEX_FORMAT to convert the contents to text format but i am unable to transfer with fixed length to application server file..
As it is a dynamic program , i am using fieldsymbols instead of internal tables.
Can anybody please help me transferring amounts also to appl .server file , with fixed length..
Thanks in advance..Hi
The <field symbols> doesn't change the format of the field, so you need to convert it in char format before transfering it to file.
DATA: WA TYPE STRING.
MOVE <FINAL> TO STRING.
TRANSFER WA TO P_FILE.
Max -
Shortdump upon calculating settlement rule in co-product-orders w/rule PP6
Hello,
We use production orders with co-products. Production Order Type contains distribution rule PP6 (settlement of co-products by actual cuantities). We have installed the MILL-funcionality
If we create a production order for a small quantity, the system gives a shortdump upon calculating the distribution rules in the settlement rule in the order.
Key-words in shortdump:
COMPUTE_INT_TIMES_OVERFLOW
CX_SY_ARITHMETIC_OVERFLOW
in procedure "MILL_IT_CALCULATE_BASEQUANTITY" "(FUNCTION)"
If we create the order with a sufficient big quantity, information messages appear, telling that are rounding errors creating the settlement rule in the order. The order nevertheless is created correctly and no shortdump appears.
We already implemented notes 1349991 and 1524822 but they dont resolve this problem.
Any clues?
Thanks for any answer on this strange problem we face.
AartThanks,
We aplied the notes you suggested but it didnt sove the problem.
Any sugestions?
Thanks.
Aart -
Does anyone use cvapi_doc_checkin WITHOUYT datacarrier entries in TDWD/E ?
At the end of this post, there's a piece of ABAP foo-code that:
1) calls BAPI_DOCUMENT_CREATE2 to create a DMS document (external content server = OpenText)
2) then calls CVAPI_READ_FILE2TABLE to get a PDF into binary "drao" format (Note that the foo-code calls a z-copy of CVAPI_READ_FILE2TABLE because the original SAP copy doesn't type the filesize parameter, so the code shortdumps if filesize gets larger than 9999.
3) then calls CVAPI_DOC_CHECKIN to check in the created document with the PDF in binary drao format.
The foo-code works fine - all return codes are 0 with no error messages in ls_return or ls_messages.
The problem is that when you go to CV03n, the PDF doesn't appear in the table at the bottom of the screen because there's no entry for the dttrg (data carrier) in tables TDWD/E etc.
So: here are my two questions:
1) Has anyone successfully used CVAPI_DOC_CHECKIN and CV03 without the correct "dttry" entries in TDWD/E etc.?
2) If not - if the entries in these tables are required, could someone supply the values for their EXTERNAL CONTENT-SERVER DTTRG in their TDWD/TDWE tables?
Thanks for any insight that anyone can provide here.
Here's the foo-code:
*& Report ZFOO_C100198_CHECKIN
REPORT ZFOO_C100198_CHECKIN.
FIELD-SYMBOLS:
<fs_fils> TYPE bapi_doc_files2,
<fs_filscv> TYPE cvapi_doc_file.
DATA:
ls_dms_filename TYPE filep,
ls_dms_filename2 TYPE filep,
ls_documentdata TYPE bapi_doc_draw2,
ls_doctype TYPE dokar,
ls_docnumber TYPE doknr,
ls_docpart TYPE doktl_d,
ls_docversion TYPE dokvr,
ls_dms_wsapp TYPE dappl VALUE 'PDF'.
DATA:
lt_documentfiles TYPE bapi_tt_doc_files2,
lt_documentfiles_cv TYPE cvapi_tbl_doc_files,
ls_return TYPE bapiret2,
ls_retrnc TYPE bapiret2,
lt_drao TYPE dms_tbl_drao,
ls_status TYPE cvapi_doc_status,
ls_messages TYPE messages.
ls_dms_filename = '/sap_dirs/interfaces/out/4500000009C10019820100706104222.pdf'.
ls_dms_filename2 = '4500000009C10019820100706104222.pdf'.
ls_documentdata-documenttype = 'DRW'.
ls_documentdata-wsapplication1 = ls_dms_wsapp.
ls_documentdata-docfile1 = ls_dms_filename2.
ls_documentdata-statusextern = 'AR'.
ls_documentdata-datacarrier1 = '/IKOS/DCCM'.
APPEND INITIAL LINE TO lt_documentfiles ASSIGNING <fs_fils>.
<fs_fils>-docfile = ls_dms_filename2.
<fs_fils>-wsapplication = 'PDF'.
<fs_fils>-storagecategory = '/IKOS/DCCM'.
<fs_fils>-sourcedatacarrier = '/IKOS/DCCM'.
CALL FUNCTION 'BAPI_DOCUMENT_CREATE2' EXPORTING
DOCUMENTDATA = ls_documentdata
IMPORTING
DOCUMENTTYPE = ls_doctype
DOCUMENTNUMBER = ls_docnumber
DOCUMENTPART = ls_docpart
DOCUMENTVERSION = ls_docversion
RETURN = ls_return
TABLES
DOCUMENTFILES = lt_documentfiles.
COMMIT WORK.
CALL FUNCTION 'ZCV120_READ_FILE2TABLE'
EXPORTING
PF_FILE = ls_dms_filename
* IMPORTING
* PFX_FILE_SIZE =
TABLES
PTX_DATA = lt_drao.
* EXCEPTIONS
* READ_ERROR = 1
* OTHERS = 2
IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
APPEND INITIAL LINE TO lt_documentfiles_cv ASSIGNING <fs_filscv>.
<fs_filscv>-filename = ls_dms_filename2.
<fs_filscv>-dappl = 'PDF'.
<fs_filscv>-storage_cat = '/IKOS/DCCM'.
<fs_filscv>-dttrg = '/IKOS/DCCM'.
CALL FUNCTION 'CVAPI_DOC_CHECKIN'
EXPORTING
PF_DOKAR = ls_doctype
PF_DOKNR = ls_docnumber
PF_DOKVR = ls_docversion
PF_DOKTL = ls_docpart
* PS_DOC_STATUS = ls_status
IMPORTING
PSX_MESSAGE = ls_messages
TABLES
PT_FILES_X = lt_documentfiles_cv
PT_CONTENT = lt_drao.
COMMIT WORK.Hi,
the solution was to add parameters hostname and pf_ftp_dest (hostname specifies the host, where the calling process runs).
CALL FUNCTION 'BAPI_DOCUMENT_CREATE2'
EXPORTING
documentdata = ls_doc
hostname = hostname
pf_ftp_dest = 'SAPFTPA'
* pf_http_dest = 'SAPHTTP'
IMPORTING
documenttype = lf_doctype
documentnumber = lf_docnumber
documentpart = lf_docpart
documentversion = lf_docversion
return = return
TABLES
documentdescriptions = itabtexts
objectlinks = itabobjectlinks
documentfiles = itabfiles.
Maybe you are looking for
-
More generic overlays in print module
Currently there's a way to place the identity plate on images in the print module, but it could use some work. Here are some additional features I'd like to see: Instead of using the specific identity plate as overlay, the print module should use mor
-
Word 2007 - Acrobat : filename with periods (.)
Just a quick question : since we upgraded to Office 2007, one of my users complains that when he converts his Word documents to PDF (through the virtual printer in Word), the filename is automatically cut, it stops at the first period (.) which could
-
Manual replica creation of DeDup Volumes
Hi, we are on the way to update a lot of our file Servers to Windows Server 2012. DeDup will be enabled on the volumes. We are going to to backup these voumes via DPM2012SP1. Now my question: Is it possible to create a Manual replica (for example wit
-
Move files back into TimeMachine backupdb
Running Mac OS X Snow Leopard 10.6.8 Stupid me, I hit cmd-delete by habit on a folder whithin the Backups.backupdb/computername folder on my TimeMachine backup drive. One of the "yyyy-mm-dd-hhmmss" folder was moved to the Trash. I managed to move the
-
When I connect my camcorder to the imac the screen on the camcorder goes grey and green lettering is on this screen, PC CONNECT, then a window opens on the pc, it tells me I have inserted a blank DVD, now this DVD is full as I only used it last week,