[Ugrapde ECC 5.0] Dump in PA-CM

Hi all,
We are currently upgrading from 4.6C to ECC 5.0
We have got a problem when switching from Display to Modify in the HRCMP0001D transaction. A dump is generated with the following text :
The exception 'CX_HRPA_INVALID_PARAMETER' was raised but was not caught at any
stage in the
call hierarchy.
Since exceptions represent error situations, and since the system could
not react adequately to this error, the current program,
'CL_HRPA_RESOLVE_EXCEPTION=====CP', had to
be terminated.
It did find a OSS Note <b>885513</b> which seems to be related but is for FI-TV-COS and not for PA-CM. And - I assume - the corrections apply to FI-TV programs...
Has anybody experienced something similar ?
Best regards,
Guillaume

Hi Sinchan, hi Suresh
Sorry for the delay.
What I did is that I added the
* an event to avoid a short dump due to CE framework
LOAD-OF-PROGRAM.
PERFORM do_nothing(sapfp50p).
into the program RHCMP_STARTNF that is called when you launch the transaction HRCMP0001D
It is far better now !
For the moment, we are just upgrading 'existing' functionalities but we are studying ECM also, for the future.
Best regards,
Guillaume

Similar Messages

Details of ECC 6.0 dumps

Hi Gurus,
Can anyone give me ecc 6.0 dumps details which i can download through market place.
Regards
Hemant

Hi Hemant,
Again It's hard to tell those "Material No" as they are specific to version which you haven't provided well as i said when you go to: http://service.sap.com/swdc => Installations and Upgrades => A - Z Index => Select "E" ERP (ECC) => SAP ERP 6.0 => IDES Version => Windows Server => ORACLE => and under the download tab you wll find the 5x material nos
Again there's no way to tell the material nos so be at your own and start digging.
Thanks,
Salim

ECCS Flexible upload dump GETWA_NOT_ASSIGNED

Hi gurus!
I'm trying to upload some financial statements for the ECCS module using transaction CXCD (Data monitor). When i double clic the company to upload the data, using the corresponding method, it returns a dump with a GETWA_NOT_ASSIGNED message in program FICUPL90.
In QAS enviroment it works, but in the sandbox enviroment (which is a copy of the QAS).
Does any body know what can i do?

HI
Your issue is relates to below dump
"GETWA_NOT_ASSIGNED" " " "FICUPL90" bzw. "FICUPL_LCL_UPLOAD" "RUN"
then refer the below note.
909439
Regards
Madhu M

Error in Zreport while upgrading from 46C to ECC 6

Hello Experts,
I am facing problems in 1 Zreport while i have upgraded that report from 4.6C to ECC 6. Dump is reported while running the program.
Error is : "Access non-existent storage area."
error is coming @ line : ADD <f1> THEN <f2> UNTIL <f3> GIVING v_totval.
FIELD-SYMBOLS: <f1> TYPE ANY,
               <f2> TYPE ANY,
               <f3> TYPE ANY.
DATA: v_totval LIKE lfc1-um01h.
IF <f1> IS ASSIGNED AND
     <f2> IS ASSIGNED AND
     <f3> IS ASSIGNED.
    ADD <f1> THEN <f2> UNTIL <f3> GIVING v_totval.
ENDIF.
can you ppl please tell me any solution as its urgent !
thanks in advance.

this is fine for me.
DATA: BEGIN OF numbers,
          one   TYPE p VALUE 10,
          two   TYPE p VALUE 20,
          three TYPE p VALUE 30,
          four TYPE p VALUE 40,
          five TYPE p VALUE 50,
        END OF numbers,
        sum     TYPE i.
SELECT-OPTIONS position FOR sum.
ADD numbers-one THEN numbers-two
                  UNTIL numbers-five
                  ACCORDING TO position
                  GIVING sum.
A

BPC 7.5 and BI 7.0

Hello experts,
We are running BPC 7.0 MS with SQL 2008. We have drill through capabilities in some applications and we run SSIS packages to bring data from Staging database to the bpc table (Both bpc and staging are in same server).
Now we are planning to bring BI 7.0 and upgrade to 7.5 MS for better drill through capabilities. I would appreciate if someone explain how the data flow happens in a similar environment (R/3 - BI and BPC 7.5 MS) I am looking in terms of how SSIS is setup and whether they use staging database for drill throughs.
I keep hearing about 7.5 MS with improved drill through features. Can someone shed light on that area as well.
Thanks in advance.
Mani

Hello experts,
We are running BPC 7.0 MS with SQL 2008. We have drill through capabilities in some applications and we run SSIS packages to bring data from Staging database to the bpc table (Both bpc and staging are in same server).
Now we are planning to bring BI 7.0 and upgrade to 7.5 MS for better drill through capabilities. I would appreciate if someone explain how the data flow happens in a similar environment (R/3 - BI and BPC 7.5 MS) I am looking in terms of how SSIS is setup and whether they use staging database for drill throughs.
I keep hearing about 7.5 MS with improved drill through features. Can someone shed light on that area as well.
Thanks in advance.
Mani
================================================
Hi Mani,
Please forgive me I cannot answer all questions you made above because of limitation of my knowledge,
Regarding relationship with R/3(ECC) and BPC 7.5 MS and BI,
It is one of way you have staging table to see FI/FM and CO data for sales and expenses, you need to handle SSIS with RFC as you mentioned, why don't you directly go to the table of FI/FM and CO with ITS. SAP ITS(Internet Transport Service?) is an application that generates URL(Drill through is based on URL) from ECC. This will make you more flexible for your future application roadmap since you make a bridge intuitively to the OLTP from OLAP.
If not, you can use RFC to connect ECC direclty or dump data from ECC using SSIS(including RFC). Please refer to the following
http://download.microsoft.com/download/A/4/D/A4D3C6FA-408F-4E77-8892-ED4C7E4ECF8A/Microsoft_BI_Interoperability_with_SAP_White_Paper-042309-r2v100-F5.docx
Hope this helps,
YH Seo

Dunning in ECC 6.0 UC_OBJECTS_NOT_CHARLIKE Dump

Hi,
We are doing an upgrade from 4.6 to ECC 6.0 and when we execute transaction F150 for dunning we get the following runtime error does anyone have any idea what might cause this or how to resolve it.
Runtime Errors         UC_OBJECTS_NOT_CHARLIKE
Date and Time          03.10.2007 11:26:12
Short text
The current statement is only defined for character-type data objects.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLSTXV" 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
For the statement
"IF ... op1 CO op2 ..."
only character-type data objects are supported at the argument position
"op1".
In this case. the operand "op1" has the non-character-type "P". The
current program is a Unicode program. In the Unicode context, the type
'X' or structures containing not only character-type components are
regarded as non-character-type.
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:
"UC_OBJECTS_NOT_CHARLIKE" " "
"SAPLSTXV" or "LSTXVFXX"
"FORMAT_SYMBOLVALUE"
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... "sapqs2"
Network address...... "10.1.11.40"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "4x AMD64 Level"
Character length.... 8 Bits
Pointer length....... 64 Bits
Work process number.. 22
Shortdump setting.... "full"
Database server... "SAPQS2"
Database type..... "ORACLE"
Database name..... "QS2"
Database user ID.. "SAPSR3"
Char.set.... "English_United State"
SAP kernel....... 700
created (date)... "May 21 2007 22:16:42"
create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
Database version. "OCI_10201_SHARE (10.2.0.2.0) "
Patch level. 111
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, Windows
NT 6.0"
Memory consumption
Roll.... 16128
EM...... 12569712
Heap.... 0
Page.... 24576
MM Used. 2814704
MM Free. 1372640
User and Transaction
Client.............. 400
User................ "DALY_M"
Language key........ "E"
Transaction......... " "
Transactions ID..... "0F9B71DCFFA7F10BBB8A001A4BB0243C"
Program............. "SAPLSTXV"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "SAPLSTXV" - in "FORMAT_SYMBOLVALUE".
The main program was "SAPF150D2 ".
In the source code you have the termination point in line 599
of the (Include) program "LSTXVFXX".
The program "SAPLSTXV" was started as a background job.
Job Name....... "F150-20071001-HO001 -5"
Job Initiator.. "DALY_M"
Job Number..... 11261200
Source Code Extract
Line
SourceCde
569
570
      Bereitet Symbol entsprechend den Angaben auf
571
572
form format_symbolvalue using fs_line
573
fs_value
574
fs_valuelength.
575
576
field-symbols:
577
<work>.
578
data:
579
fs_vallen like integer,
580
fs_techlen type i,
581
fs_vis_len type i.
582
583
valpos    = 0.
584
valoffset = 0.
585
clear: fs_value,fs_valuelength.
586
587
*... Pruefen Initialwert und Initialwertunterdrueckung .................
588
if value_initial = true and value_noinit = true.
589
exit.
590
endif.
591
592
*... Wert komprimieren .................................................
593
if value_condense = true.
594
condense val. if val(1) = space. shift val. endif.
595
endif.
596
597
*... Local date format .................................................
598
if value_ldate = true.                                             "JPN
>>>>>
if <value_raw> co '0123456789 '.                                "JPN
600
write <value_raw> to val using edit mask '==JPDAT'.           "JPN
601
endif.                                                          "JPN
602
endif.                                                             "JPN
603
604
*... Offset bearbeiten .................................................
605
if offlen > 0.
606
assign fs_line+offpos(offlen) to <work>.
607
valpos = <work>.
608
endif.
609
610
*... Laenge bearbeiten .................................................
611
if lenlen > 0.                       "...angegebene Wertlaenge
612
assign fs_line+lenpos(lenlen) to <work>.
613
vallen = <work>.
614
if vallen > val_max.                                    " B20K079471
615
message a799 with val_max itcvd-name vallen.         " B20K079471
616
endif.                                                  " B20K079471
617
elseif value_dictlen = true.         "...Dictionary-Laenge
618
vallen = itcvd-outputlen.
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
2
SY-TABIX
4
SY-DBCNT
267
SY-FDPOS
5
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
FI Dunning - Print Program
SY-MSGTY
S
SY-MSGID
B!
SY-MSGNO
015
SY-MSGV1
00001040
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20071003
SY-UZEIT
112612
SY-XPROG
SAPCNVE
SY-XFORM
CONVERSION_EXIT
Active Calls/Events
No.   Ty.          Program                             Include                             Line
Name
13 FORM         SAPLSTXV                            LSTXVFXX                              599
FORMAT_SYMBOLVALUE
12 FUNCTION     SAPLSTXV                            LSTXVU02                               73
GET_TEXTSYMBOL
11 FORM         SAPLSTXC                            LSTXCFSC                             1256
SC_GET_TEXTSYMBOL
10 FORM         SAPLSTXC                            LSTXCFSC                              495
SC_TOKEN
9 FORM         SAPLSTXC                            LSTXCFPA                              310
PA_ACTUAL
8 FORM         SAPLSTXC                            LSTXCFPA                              156
PA_BODY
7 FUNCTION     SAPLSTXC                            LSTXCU03                              147
WRITE_FORM
6 FORM         SAPLF150                            LF150U07                             1151
WRITE_LINE
5 FUNCTION     SAPLF150                            LF150U07                              242
PRINT_DUNNING_NOTICE
4 FUNCTION     SAPLF150                            LF150U19                               29
FI_PRINT_DUNNING_NOTICE
3 FUNCTION     SAPLBFFM                            LBFFMU65                               54
OPEN_FI_PERFORM_00001720_E
2 FORM         SAPF150D2                           SAPF150D2                             556
OFI_DUN_ACT
1 EVENT        SAPF150D2                           SAPF150D2                             139
START-OF-SELECTION
Chosen variables
Name
Val.
No.      13 Ty.          FORM
Name FORMAT_SYMBOLVALUE
FS_VALUE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
FS_VALUELENGTH
0
0000
0000
VALUE_INITIAL
2
0
TRUE
X
5
8
SYST-REPID
SAPLSTXV
5454555522222222222222222222222222222222
310C348600000000000000000000000000000000
VALUE_NOINIT
2
0
VALUE_CONDENSE
2
0
SYST
####################################################D#######x###############$#################
0000000000000000000000001000000000000000000000000000400000007000000000000000200000000000000000
2000000040005000000000004000000000000000B10050001000400010008000000000000000410000000000000000
VAL
2,925.00
2222222223233323322222222222222222222222222222222222222222222222222222222222222222222222222222
0000000002C925E0000000000000000000000000000000000000000000000000000000000000000000000000000000
SY-REPID
SAPLSTXV
5454555522222222222222222222222222222222
310C348600000000000000000000000000000000
VALUE_LDATE
X
5
8
SY
####################################################D#######x###############$#################
0000000000000000000000001000000000000000000000000000400000007000000000000000200000000000000000
2000000040005000000000004000000000000000B10050001000400010008000000000000000410000000000000000
<VALUE_RAW>
####P#
0000950
000220C
C_TOKEN_URL_END
)U
25
95
INACTIVE_FCODES[]
Table[initial]
OFFLEN
0
0000
0000
FS_LINE
&MHND-WRSHB(L)&,,&MHND-FAEDT&,,&MHND-VERZN(L)&
24444255544242222244442444452222444425455424222
6D8E4D723828C96CC6D8E4D615446CC6D8E4D652AE8C960
<WORK>
2
0
OFFPOS
0
0000
0000
No.      12 Ty.          FUNCTION
Name GET_TEXTSYMBOL
*RSTXV
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
TX2EMPTY
2
0
%_DUMMY$$
2222
0000
LINE
&MHND-WRSHB(L)&,,&MHND-FAEDT&,,&MHND-VERZN(L)&
24444255544242222244442444452222444425455424222
6D8E4D723828C96CC6D8E4D615446CC6D8E4D652AE8C960
ITCVD
MHND-WRSHB
4444255544222222222222222222222222222222222222222222222222222222222222222222222222222222222222
D8E4D72382000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SY-FLENG
47
2000
F000
ITCVD[]
Table IT_166[5x292]
FUNCTION-POOL=STXVDATA=ITCVD[]
Table reference: 127
TABH+ 0(20) = 309F3D57FE070000000000000000000000000000
TABH+ 20(20) = 7F000000A60000000500000024010000FFFFFFFF
TABH+ 40(16) = 04DC0000100B000010000000C9248001
store        = 0x309F3D57FE070000
ext1         = 0x0000000000000000
shmId        = 0     (0x00000000)
id           = 127   (0x7F000000)
label        = 166   (0xA6000000)
fill         = 5     (0x05000000)
leng         = 292   (0x24010000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000040
occu         = 16    (0x10000000)
access       = 1     (ItAccessStandard)
idxKind      = 1     (ItIndexLinear)
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         = 0x40B73D57FE070000
pgHook       = 0x0000000000000000
idxPtr       = 0x90033E57FE070000
shmTabhSet   = 0x0000000000000000
id           = 135   (0x87000000)
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 16    (0x10000000)
lineAlloc    = 16    (0x10000000)
shmVersId    = 0     (0x00000000)
shmRefCount = 1     (0x01000000)
>>>>> 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
VALUE_SIGN_RIGHT
2
0
SCROLL_LINES
13
0000
D000
NAM
MHND-WRSHB
4444255544222222222222222222222222222222222222222222222222222222222222222222222222222222222222
D8E4D72382000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SY-SUBRC
0
0000
0000
SUM
2
0
ITCVD-SUM
2
0
ZEROLEN
2
0
VALUE_RAW
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
VALUE_RIGHT
2
0
VALUE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
VALUE_LENGTH
0
0000
0000
VAL_MAX
255
F000
F000
SY-MSGID
B!
42222222222222222222
21000000000000000000
TTDTG
22222222222222222222222222222222222222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000000000000000000000000000000000000
SPACE
2
0
SY-MSGNO
015
333
015
SY-MSGV1
00001040
33333333222222222222222222222222222222222222222222
00001040000000000000000000000000000000000000000000
SY-MSGV2
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
No.      11 Ty.          FORM
Name SC_GET_TEXTSYMBOL
SY-REPID
SAPLSTXC
5454555422222222222222222222222222222222
310C348300000000000000000000000000000000
UNRESOLVED
2
0
C_PC_BARCROT_270
270
333
270
RSTXC-TDDEBUG
2
0
TRUE
X
5
8
SY
####################################################D#######x###############$#################
0000000000000000000000001000000000000000000000000000400000007000000000000000200000000000000000
2000000040005000000000004000000000000000B10050001000400010008000000000000000410000000000000000
OP_ERROR_OFFS
0
0000
0000
DBABAPBREAK
2
0
FCODE_PRINT
PRNT
55452222222222222222
02E40000000000000000
PC_ID_CODEPAGE
CP
45
30
PC_ID_ULINE
UL
54
5C
TX_CATALOG-TDSPRAS
E
4
5
PROTPAGE_ALL
ALL
444
1CC
<SC_LINE>
&MHND-WRSHB(L)&,,&MHND-FAEDT&,,&MHND-VERZN(L)&
24444255544242222244442444452222444425455424222
6D8E4D723828C96CC6D8E4D615446CC6D8E4D652AE8C960
PROTPAGE_OFF
OFF
444
F66
%_PRINT
HOFI001SAPF150D2_                                                                      X X8 ¼ÿ
44443335454333435222222222222222222222222222222222222222222222222222222222222222222222252532BF
8F69001310615042F000000000000000000000000000000000000000000000000000000000000000000000080880CF
POS
0
0000
0000
C_AMP_SYM_MAXLEN
132
8000
4000
NAME
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SUM
2
0
PROTNEXT_SAME_PAGE
SAME-PAGE
5444254442
31D5D01750
FT_STRING
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
FT_STRING_LEN
0
0000
0000
VALUE_RAW
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
OSS_NOTE_0658270
2
0
G_IS_CFONT
2
0
APPLICATION_NORMAL
TN
54
4E
FCODE_PRINTER_FONTS
PFON
54442222222222222222
06FE0000000000000000
OFF
2
0
No.      10 Ty.          FORM
Name SC_TOKEN
BOTLINES-TDLINE+0(8)
22222222
00000000
SPACE
2
0
PC_ID_BOX_BEGIN
BB
44
22
APPLICATION_NORMAL
TN
54
4E
L_LENGTH
47
2000
F000
SYST-REPID
SAPLSTXC
5454555422222222222222222222222222222222
310C348300000000000000000000000000000000
UNIT_POINT
PT
55
04
EVENTS-TDSCANSTAT
1
3
1
FCODE_CATALOG
CATA
44542222222222222222
31410000000000000000
%_VIASELSCR
0
4
FCODE_CREATE
CREA
45442222222222222222
32510000000000000000
IS_ESCAPE
2
0
SYMBOL
000000000000000000
2223333333333333333332222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
FCODE_PREVIEW
PREV
55452222222222222222
02560000000000000000
OTF-TDPRINTPAR
2222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000
FCODE_DOCU
ODOC
44442222222222222222
F4F30000000000000000
No.       9 Ty.          FORM
Name PA_ACTUAL
SYST-REPID
SAPLSTXC
5454555422222222222222222222222222222222
310C348300000000000000000000000000000000
DEVICE_TELEX
TELEX
54445222
45C58000
PA-INTERRUPT
2
0
FALSE
2
0
PA-EXIT
2
0
ARCHIVE_ONLY
2
3
2
FCODE_EDIT_MAIN
MAIN
44442222222222222222
D19E0000000000000000
OP_SYMBOL
2
0
PA_TOKEN
3
0000
3000
SCREEN
%_17SNS0000149933_%_%_%_%_%_%_
2533545333333333352525252525252222222222222222222222222222222222222222222222222222222222222222
5F173E30000149933F5F5F5F5F5F5F0000000000000000000000000000000000000000000000000000000000000000
C_BMP_BACKGROUND_NOPRI
2
3
2
STATUS_CUSTOMER
CUS
455
353
TRANSTAT_ACTIVE
0
3
0
ATTRIBUTES_FONT
002
333
002
No.       8 Ty.          FORM
Name PA_BODY
%_DUMMY$$
2222
0000
PC_OUT_PAGE
P
5
0
PC_ID_PRINT_CONTROL
PC
54
03
FCODE_PRINTER
PATT
54552222222222222222
01440000000000000000
PA-INTERRUPT
2
0
PC_ID_BOX_BEGIN
BB
44
22
TRANSLATION_WANTED
0
3
0
FLAG_RDI_ACTIVE
2
0
%_SPACE
2
0
G_BITMAP_TABL
##########ÿÿÿÿ
2222222222222222222222222222222222222222220000000000FFFF
0000000000000000000000000000000000000000000000000000FFFF
SYST-REPID
SAPLSTXC
5454555422222222222222222222222222222222
310C348300000000000000000000000000000000
G_BITMAP_TABL[]
Table[initial]
WTYPE_VARIABEL
VAR
54522
61200
PC_ID_BOX_END
BE
44
25
FALSE
2
0
PC_ID_LINK_END
LE
44
C5
No.       7 Ty.          FUNCTION
Name WRITE_FORM
ELEMENT
531
333
531
FUNCTION
SET
545
354
TYPE
BODY
4445
2F49
WINDOW
MAIN
4444
D19E
PENDING_LINES
2222
0000
PC_ID_TELECOM
/T
25
F4
RSJOBINFO
00000000000000                                  ####
222222222222222222222222222222223333333333333322222222222222222222222222222222220000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000
OP_PAGE_MAX
99999
33333
99999
%_DUMMY$$
2222
0000
ELEMENTS-TDFROMLINE
157
9000
D000
SYSTEM_WINDOW_MAIN
MAIN
44442222
D19E0000
BOOLEAN
2
0
ETYPE
3
3
3
ETYPE_CURRENT
3
3
3
C_PC_INFO_FORM
04
33
04
SY-XFORM
CONVERSION_EXIT
444545544454545222222222222222
3FE65239FEF5894000000000000000
ETYPE_BOTTOM
2
3
2
SYST
####################################################D#######x###############$#################
0000000000000000000000001000000000000000000000000000400000007000000000000000200000000000000000
2000000040005000000000004000000000000000B10050001000400010008000000000000000410000000000000000
C_PC_INFO_PAGE
05
33
05
APPLICATION_NORMAL
TN
54
4E
PC_BOTTOM_HEIGHT
0
0000
0000
FT-BOT_HEIGHT
0
0000
0000
SYST-REPID
SAPLSTXC
5454555422222222222222222222222222222222
310C348300000000000000000000000000000000
No.       6 Ty.          FORM
Name WRITE_LINE
%_DUMMY$$
2222
0000
No.       5 Ty.          FUNCTION
Name PRINT_DUNNING_NOTICE
I_F150D2
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
I_F150V
20071001HO001 00000000
3333333344333233333333222222222222222222222222222222222222222222222222222222222222222222222222
200710018F001000000000000000000000000000000000000000000000000000000000000000000000000000000000
I_ITCPO
#HOFI           XLIST1S    HO00107
2222222222222222222222222222222222222222222222222222222222220444422222222222544553522224433333
00000000000000000000000000000000000000000000000000000000000008F69000000000008C9341300008F00107
I_MAHNV
40020071001HO001 F A
33333333333443332424
400200710018F0010601
I_MHNK
40020071001HO001 DFAS 0000000028                                      0 2007100120071001
3333333333344333244452333333333322222222222222222222222222222222222222322333333333333333322222
400200710018F001046130000000002800000000000000000000000000000000000000000200710012007100100000
I_MOUT
X
5
8
I_OFI
X
5
8
I_UPDATE
2
0
T_FIMSG[]
Table IT_63[0x236]
PROGRAM=SAPF150D2FORM=OFI_DUN_ACTDATA=T_FIMSG[]
Table reference: 46
TABH+ 0(20) = 0000000000000000C0501D57FE07000000000000
TABH+ 20(20) = 2E0000003F00000000000000EC000000FFFFFFFF
TABH+ 40(16) = 04000000301F000002000000C1048001
store        = 0x0000000000000000
ext1         = 0xC0501D57FE070000
shmId        = 0     (0x00000000)
id           = 46    (0x2E000000)
label        = 63    (0x3F000000)
fill         = 0     (0x00000000)
leng         = 236   (0xEC000000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000132
occu         = 2     (0x02000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 2     (cmpSingleMcmpR)
occu0        = 0
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
ref

It's a SAPscript issue, and it depends whether it's standard SAP or something you've done yourself. Looking at the call stack it appears to be standard SAP so I'd suggest searching on OSS. Avoid searching on "SAPLSTXV" , "LSTXVFXX" or
"FORMAT_SYMBOLVALUE" as these are generic SAPscript terms.

How to avoid short dump in ECC 5.0

Hi
Can anyone tell me how to avoid short dump in ECC 5.0
I'm told we can avoid program going to short dump, instead IT WILL GRACEFULLY EXIT..

Hi
By implementing the code as for every unsuccess/failure conditions control has come out of the program. then only u can avoid dumps even though u code the not perfect functionality.
Regards,
kumar

Dump while setting a break point in ECC 6.0

Dear Experts,
In ECC 6.0, when I try to put a break point in the program to stop the control there. I am not able to do so, it is going to dump. The dump message is also not very clear. Do anyone of you are facing the same problem. Any idea why is this happening and how do I fix it.
Can it be due to the improper installation? Please respond.

First of all thanks to Mickey, Nitin, Anki, Sujit, Red, Madhu, Vibin for the quick response...To be honest I did not expect such a response as a new member to the SDN community...I am sorry I could not mention the detail about the dump initially...Here is the detailed description..
Issue: In ECC 6.0, when I write a simple ABAP program (e.g. 'Hello World' program). When I try to keep the cursor on any abap statement and click on the 'session break point' icon in the tool bar to set the break point, i get a status message 'Compling SAPLBREA in separate task and finally i get the dump.
Dump Detail :
Runtime Errors: DBIF_REPO_SQL_ERROR
Short Text : SQL error 1115 occurred when accessing program 'LNAVIDAT' part "SRC".
Program: SAPLBREA
Include: LBREATOP
Row: 41
There is a an include being called at line no 41, which is "Include LNAVIDAT".
Now when I click on the 'debugger' icon in the dump...It points to a functional module "RS_SET_BREAKPOINT"
Also, while double clicking on this include to see the code within, it issues an error message saying "SQL error occurred when accessing the table TRDIR".
Or
While trying to display the code of the include LNAVIDAT in se38 to see what is wrong with that i get another dump and this time it points to be SELECT query in the dump which is:
SELECT SINGLE * from PROGDIR WHERE name = rs38m-programm
and state = active.
Thereafter, i keep getting dumps when i try to go to any T.codes (e.g. se11, se38 etc.). until i log off and log in again. Hope this helps you guys understanding the problem. Being new to SAP, I have no clue why is this happening and how to fix it. Thanks in Advance.

ABAP dump in ecc 6.0 for F110 transaction

HI All,
We have recently upgraded to ECC 6.0 from 4.6C.
While displaying the proposal/exception list using F110 transaction for the program RFZALI20. The ABAP dump says "Unable to interpret "1 5D " as a number". It is failing for Key for print parameters (PRI_PARAMS-PRKEYEXT).
Has anyone faced this issue?
Thanks in advance.
-APK

HI Balaji,
We could get over this issue by changing the print parameters in the variant we have used.
The variant had some print parameters selected (having green check) even though there are no parameters which are selected. So, I have created a varaint without the print parameters option checked (no more green check in the extended selection).
Hope this is clear.
-Pradeep

ECC 6.0 IDES Dump

Hi All,
I am facing some problem in my ECC 6.0 IDES..
I Am getting frequent Dumps when I check ST22..
It says "DDIC_TYPE_INCONSISTENCY"...
The error is as below....
Short text
    Inkonsistenz im Dictionary für die Struktur "MCVBAPB".
What happened?
    The current ABAP/4 program had to be terminated because the
    ABAP/4 processor detected an internal system error.
What can you do?
    Please make a note of the actions and input which caused the error.
    To resolve the problem, contact your
    SAP system administrator.
    Select the "Print" function to obtain a hardcopy of the
    current termination message.
Error analysis
    There is an internal system error.
    eliminated with ABAP/4.
How to correct the error
    It is probably not possible to eliminate the system error
    with ABAP/4 alone.
    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,
    please use the following search criteria:
    "SAPLMCEX" "DDIC_TYPE_INCONSISTENCY"
    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,
    please use the following search criteria:
    "SAPLMCEX" "DDIC_TYPE_INCONSISTENCY"
    If you cannot solve the problem yourself, please send the
    following documents to SAP:
Information on where terminated
    The termination occurred during generation of the ABAP/4 program "SAPLMCEX".
    The termination occurred in line 23
    of the source code of program "LMCEX$17" (when calling the editor 230).
Source Code Extract
Line SourceCde
    1 *******************************************************************
    2 *   THIS FILE IS GENERATED BY THE FUNCTION LIBRARY.               *
    3 *   NEVER CHANGE IT MANUALLY, PLEASE!                             *
    4 *******************************************************************
    5 FUNCTION $$UNIT$$ MCEX_FILL_XS_11
    6
    7     IMPORTING
    8        REFERENCE(SUHIE) TYPE !TFCS-SUHIE
    9        REFERENCE(XMCKOMV) TYPE !MCKOMVB OPTIONAL
   10        REFERENCE(XMCVBAK) TYPE !MCVBAKB OPTIONAL
   11        REFERENCE(XMCVBAP) TYPE !MCVBAPB OPTIONAL
   12        REFERENCE(XMCVBAPF) TYPE !MCVBAFB OPTIONAL
   13        REFERENCE(XMCVBEP) TYPE !MCVBEPB OPTIONAL
   14        REFERENCE(XMCVBFA) TYPE !MCVBFAB OPTIONAL
   15        REFERENCE(XMCVBKD) TYPE !MCVBKDB OPTIONAL
   16        REFERENCE(XMCVBPA) TYPE !MCVBPAB OPTIONAL
   17        REFERENCE(XMCVBUK) TYPE !MCVBUKB OPTIONAL
   18        REFERENCE(XMCVBUP) TYPE !MCVBUPB OPTIONAL
   19        REFERENCE(XMCFPLT) TYPE !MCFPLTB OPTIONAL
   20        REFERENCE(INTERFACE_VERSION_11) TYPE !I
   21            DEFAULT CON_MC11_FROM_2000_1
   22     EXPORTING
>>>>>        REFERENCE(XS_ACTIVE) TYPE !MCCONTROL-LOGGING .
Internal notes
    The termination was triggered in function "ab_RxDdicTypeError"
    of the SAP kernel, in line 1053 of the module
     "//bas/700_REL/src/krn/runt/abucutil.c#2".
The internal operation just processed is " ".
Internal mode was started at 20080704015252.
Es liegt eine Inkonsistenz für die DDIC-Struktur "MCVBAPB" vor, d.h.
das zugehörige Dictionary-Laufzeitobjekt (NAMETAB) ist fehlerhaft.
Die Anzahl der Komponenten der Struktur (NAMETAB-Komponente "fldcnt")
ist mit 355 angegeben. Wenn man alle Unterstrukturen auflöst und die
tatsächliche Gesamtanzahl aller Komponenten rekursiv berechnet, kommt
man allerdings auf einen anderen Wert.
Der Fehler wird dadurch verursacht, daß die Struktur "MCVBAPB" oder eine ihrer
Unterstrukturen verändert wurde und bei der anschließenden Aktivierung
ein Fehler auftrat. Bitte prüfen Sie das Laufzeitobjekt der Struktur "MCVBAPB"
im Dictionary, um die genaue Fehlerursache zu analysieren.
Falls in Ihrem System der Programm RSDDCHECK bereits vorhanden ist,
können Sie die Struktur "MCVBAPB" auch mit Hilfe dieses Programms überprüfen.
ive Calls in SAP Kernel
es of C Stack in Kernel (Structure Differs on Each Platform)
(R) - R/3(TM) Callstack, Version 1.0
yright (C) SAP AG. All rights reserved.
lstack without Exception:
       : disp+work.EXE (pid=3000)
n      : 7/4/2008 1:52:53.468
eads   : 2
puter Name       : UCLIDES
r Name           : SAPServiceUCI
ber of Processors: 2
cessor Type: x86 Family 15 Model 4 Stepping 7
dows Version     : 5.2 Current Build: 3790
te Dump for Thread Id cb4
=00000016 ebx=0000041c ecx=064c4008 edx=00000000 esi=0000041c edi=00000000
=7ffe0304 esp=0558c8d0 ebp=0558c940 iopl=0         nv up ei pl zr na po nc
001b ss=0023 ds=0023 es=0023 fs=003b gs=0000             efl=00200246
ction :
     7ffe02eb 0000             add     ,al                     ds:00000016=??
     7ffe02ed 0000             add     ,al                     ds:00000016=??
     7ffe02ef 0000             add     ,al                     ds:00000016=??
     7ffe02f1 0000             add     ,al                     ds:00000016=??
     7ffe02f3 0000             add     ,al                     ds:00000016=??
        7ffe02f5 0000             add     ,al                     ds:00000016=??
        7ffe02f7 0000             add     ,al                     ds:00000016=??
        7ffe02f9 0000             add     ,al                     ds:00000016=??
        7ffe02fb 0000             add     ,al                     ds:00000016=??
        7ffe02fd 0000             add     ,al                     ds:00000016=??
        7ffe02ff 008bd40f34c3     add     ,cl          ds:c33413f0=00
        7ffe0305 9c               pushfd
        7ffe0306 810c2400010000   or      dword ptr ,0x100 ss:0558c8d0=77f43741
        7ffe030d 9d               popfd
        7ffe030e c3               ret
        7ffe030f 90               nop
        7ffe0310 90               nop
        7ffe0311 90               nop
        7ffe0312 90               nop
        7ffe0313 90               nop
        7ffe0314 90               nop
        7ffe0315 90               nop
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
0558c8cc 77f43741 77e41817 0000041c 00000000 0558c914
0558c940 77e4168f 0000041c 0001d4c0 00000000 01034bf9 ntdll!NtWaitForSingleObject
0558c974 0056da03 0056da3c 7c38b5e8 7c38b5e8 7c38b5e8 kernel32!WaitForSingleObject
0558c978 0056da3c 7c38b5e8 7c38b5e8 7c38b5e8 01dd88c0 disp+work!NTStack
0558c994 0056da70 7c38b5e8 00000000 0086bbf4 7c38b5e8 disp+work!CTrcStack2
0558c9a0 0086bbf4 7c38b5e8 00000000 005f0059 00300030 disp+work!CTrcStack
0558c9c4 0086f036 0000015a 2236bd48 2237fff4 0558ca58 disp+work!rabax_CStackSave [abrabax.c (7020)
0558d26c 0081352c 01479ae0 01479ab0 0000041d 1f95a010 disp+work!ab_rabax
0558d284 00a392a8 22370256 00000163 0558d300 00000000 disp+work!ab_RxDdicTypeError [abucutil.c (10
0558d2b0 00a39390 220b2908 220b2908 220b2908 00000000 disp+work!FirstLevelChildCnt [scsypar.c (342
0558d32c 00a398ea 0558d364 220b2908 055907b8 0559077c disp+work!UcTypeToTree
055907c0 00a399b2 055907dc 220b2908 00000000 22370256 disp+work!UcTypeToFragView [scsypar.c (3845)
05590808 00a32d20 220b2908 220b2908 21f0bb98 00a037d6 disp+work!sc_tparUcFragView [scsypar.c (3897
05590818 00a037d6 220b2908 220b2908 220c3034 220b2908 disp+work!sc_loadflds
055908bc 00a041eb 220b2908 220076f8 00000000 0559090c disp+work!GenerateType
055908d0 00a07b37 220b2908 00000000 00000002 222ade94 disp+work!cg_TypeGenInfo
0559090c 00a0a098 222ade94 222ade94 05590b5f 05590b44 disp+work!datcr_funcpar
05590b60 00a4b3ea 222ade94 00000000 220e6004 220e6004 disp+work!cg_datcr
05590b88 00a4a943 222ade94 00000000 00000002 00000000 disp+work!sc_datcr_set
05590bec 00a5315e 220e6004 00000002 21754b40 220b2908 disp+work!sc_FuncParAdd
05590c28 00a2fdd2 21754b40 00000002 00000009 00009b35 disp+work!sc_cdatcr
05597e88 00b7a44f 00200020 00200020 00000002 00000002 disp+work!rs_oper_abap3088 [rsabap44.c (3459
0559e90c 009eeabc 000000af 02ac1b3c 02ab1350 02ab130c disp+work!rs_expan_abap
0559e920 00a23c61 000000af 0559ea3c 2217e0f0 00000000 disp+work!sc_expan
0559ea14 00a232ce 00000000 0559ea3c 0559eae0 00000000 disp+work!parse
0559ea54 00a1fb5d 221700ec 00000000 00000000 00000000 disp+work!sc_check
0559eabc 00a23340 00000000 00000000 00000005 2177e100 disp+work!ProcessText
0559eaf8 00a788d1 00000076 00000000 00000001 00000001 disp+work!sc_check
0559f148 00b48465 00000000 00000000 00000000 00000000 disp+work!sc_inclu
055a5bcc 009eeabc 00000076 02ac1b3c 02ab1350 02ab130c disp+work!rs_expan_abap
055a5be0 00a23c61 00000076 055a5cfc 2177e0f0 00000000 disp+work!sc_expan
055a5cd4 00a232ce 00000000 055a5cfc 00000000 00000005 disp+work!parse
055a5d14 00a788d1 00000076 00000000 00000001 00000001 disp+work!sc_check
055a6364 00b48465 00200020 00200020 00200020 00200020 disp+work!sc_inclu
055acde8 009eeabc 00000076 02ac1b3c 02ab1350 02ab130c disp+work!rs_expan_abap
055acdfc 00a23c61 00000076 055acf18 217700ec 00000000 disp+work!sc_expan
055acef0 00a232ce 00000000 055acf18 00000000 00000000 disp+work!parse
055acf30 00a246fd 02acfdf8 055ad548 055ad4dc 009e9cd8 disp+work!sc_check
055acf40 009e9cd8 00000000 00000000 00000000 0647520c disp+work!sc_checkStart
055ad4dc 007f9c32 055ad548 00000001 00000000 00000000 disp+work!cg_generate
055ad524 007f9daf 055ad548 00000000 00000000 055afcac disp+work!ab_gabap
055afcb8 0054a4c1 07f1a654 00012762 07f1a654 00007528 disp+work!ab_genprog_remote
055afcf0 00499ff6 07f1a648 0000276e 00000301 00000003 disp+work!ThrtRpcExec
055afee0 0049b6e7 00000001 00000000 00000000 00430000 disp+work!TskhLoop
055aff00 0042171c 00000000 00000000 7ffdf000 055aff60 disp+work!ThStart
055aff14 00401080 00000003 05716768 00000001 00000000 disp+work!DpMain
055aff60 011d9ae0 00000003 05716768 05717338 01c37000 disp+work!nlsui_main
055affc0 77e4f38c 00000000 00000000 7ffdf000 00000000 disp+work!wmainCRTStartup
055afff0 00000000 011d999d 00000000 00905a4d 00000003 kernel32!TerminateThread
State Dump for Thread Id fa4
eax=00000012 ebx=00000103 ecx=0761ff00 edx=00000000 esi=00000000 edi=00000000
eip=7ffe0304 esp=0761fec0 ebp=0761ff04 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 :
        7ffe02eb 0000             add     ,al                     ds:00000012=??
        7ffe02ed 0000             add     ,al                     ds:00000012=??
        7ffe02ef 0000             add     ,al                     ds:00000012=??
        7ffe02f1 0000             add     ,al                     ds:00000012=??
        7ffe02f3 0000             add     ,al                     ds:00000012=??
        7ffe02f5 0000             add     ,al                     ds:00000012=??
        7ffe02f7 0000             add     ,al                     ds:00000012=??
        7ffe02f9 0000             add     ,al                     ds:00000012=??
        7ffe02fb 0000             add     ,al                     ds:00000012=??
        7ffe02fd 0000             add     ,al                     ds:00000012=??
        7ffe02ff 008bd40f34c3     add     ,cl          ds:c33410d7=00
        7ffe0305 9c               pushfd
        7ffe0306 810c2400010000   or      dword ptr ,0x100 ss:0761fec0=77f42845
        7ffe030d 9d               popfd
        7ffe030e c3               ret
        7ffe030f 90               nop
        7ffe0310 90               nop
        7ffe0311 90               nop
                7ffe0311 90               nop
        7ffe0312 90               nop
        7ffe0313 90               nop
        7ffe0314 90               nop
        7ffe0315 90               nop
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
0761febc 77f42845 77e60226 000006ec 00000000 00000000
0761ff04 01127ee6 000006ec 00000000 00000000 05a731b8 ntdll!NtFsControlFile
0761ff84 7c349565 00000000 00000000 00000000 05a73250 disp+work!SigIMsgFunc
0761ffb8 77e4a990 05a73250 00000000 00000000 05a73250 MSVCR71!endthreadex
0761ffec 00000000 7c3494f6 05a73250 00000000 00000000 kernel32!FlsSetValue
Can any of you, suggest solution....

Hi
There is a problem with the version management of the objects transported. This might be the possibility after seeing the log.
Regards
Bhaskar
Edited by: bhaskar1818 on Jul 4, 2008 2:53 PM

ECC 6.0 bar chart short dump

We are starting an upgrade from 4.7(non-Unicode) to ECC 6.0(Unicode), using SAPgui for Windows (version 7.10). In our 4.7 systems, the graphical bar chart on the Project Planning Board (txn CJ2C) works as expected. However, in the 6.0 development system, before displaying the gantt chart, the system short dumps with CREATE_ERROR.
I have searched the forums and looked through OSS notes and was unable to find anything that described the problem or was pertinent to our release. I have debugged through the transaction and am finding that the short dump occurs in method cl_gui_barchart=>constructor around the following code:
at line 83 if the system is unicode (which it is), the code calls method cl_gui_frontend_services=>check_gui_support, exporting 'ganttcontrol'/'usedataasstream' and expecting a result in variable l_guisupp_data_as_string. When it returns from the check_gui_support method, l_guisupp_data_as_string is blank, so the next "if" statement raises an error that is not handled:
     if l_guisupp_data_as_string = abap_true.
     .....code not executed because the variable = abap_false.
     else.
     .....raise create_error.    <<<<< this is where the dump occurs.
     endif.
Note that in the debugger, if I force l_guisupp_data_as_string to be = abap_true, the gantt chart/barchart displays as expected. (gotta love the debugger) But since it is standard SAP code I would prefer to resolve the problem without a modification and am hoping someone out there can point me in the right direction.
This short dump occurs with gui versions 710 and lower. (I personally am using sapgui version 710, patch level 7.) Has anyone had problems like this with the graphical elements in SAP or does anyone have a suggestion as to why the gui is not displaying the barchart correctly in our unicode system?
Sorry for the very long message, but thanks in advance for the help!
Amanda Salt
Edited by: Amanda Salt on Jun 17, 2008 11:14 PM

We are starting an upgrade from 4.7(non-Unicode) to ECC 6.0(Unicode), using SAPgui for Windows (version 7.10). In our 4.7 systems, the graphical bar chart on the Project Planning Board (txn CJ2C) works as expected. However, in the 6.0 development system, before displaying the gantt chart, the system short dumps with CREATE_ERROR.
I have searched the forums and looked through OSS notes and was unable to find anything that described the problem or was pertinent to our release. I have debugged through the transaction and am finding that the short dump occurs in method cl_gui_barchart=>constructor around the following code:
at line 83 if the system is unicode (which it is), the code calls method cl_gui_frontend_services=>check_gui_support, exporting 'ganttcontrol'/'usedataasstream' and expecting a result in variable l_guisupp_data_as_string. When it returns from the check_gui_support method, l_guisupp_data_as_string is blank, so the next "if" statement raises an error that is not handled:
     if l_guisupp_data_as_string = abap_true.
     .....code not executed because the variable = abap_false.
     else.
     .....raise create_error.    <<<<< this is where the dump occurs.
     endif.
Note that in the debugger, if I force l_guisupp_data_as_string to be = abap_true, the gantt chart/barchart displays as expected. (gotta love the debugger) But since it is standard SAP code I would prefer to resolve the problem without a modification and am hoping someone out there can point me in the right direction.
This short dump occurs with gui versions 710 and lower. (I personally am using sapgui version 710, patch level 7.) Has anyone had problems like this with the graphical elements in SAP or does anyone have a suggestion as to why the gui is not displaying the barchart correctly in our unicode system?
Sorry for the very long message, but thanks in advance for the help!
Amanda Salt
Edited by: Amanda Salt on Jun 17, 2008 11:14 PM
I just installed the latest patch on the SAPgui, so I am now running:
Release: 710 Final Release
File Version: 7100.2.8.1039
Build: 983952
Patch Level: 8
But I am still getting the short dump. I have done extensive searches of SAP Help, OSS notes, and this and other forums (even just looking up the problem on "google") but can't seem to find anything that applies to this scenario. I'm not very familiar with the methods in cl_gui_frontend_services, so if anyone can give me a pointer of where else I can look, I would greatly appreciate it!
I also have edited the Subject line to be more informative about the problem

Dump during testing of ECC 6.0

Dear All,
My client is upgrading from 4.7 to ECC 6.0. During testing of the new system dumps for some transactions have been arising.
For the transaction codes F-06, F-07, FBL5N and FB02 same kinds of errors have been found with similar program u201CSAPMF05Lu201D in the line no 1023. In the BSEG table the value of Docln is found out to be u201C#u201D for all the documents that have been imported from 4.7 to ECC 6.0.
Please note that these transactions are still working fine in the 4.7 system.
Below is the detail description of the error that we are receiving in ECC6.0 for the above mentioned transaction codes.
Steps to recreate the dump:
1.     Go to T-code FBL5N
2.     Provide the u201Ccustomer accountu201D, u201Ccompany codeu201D and u201Copen at key dateu201D. Then Execute.
3.     Double click on the Doc date and the dump occurs.
How do we go about it..
Regards,
Arvind

My issue has been resolved after running below program which SAP has recommended.
Run this report in the Dev --->ZF_DOCLN_UPDATE_YJ
*& Report ZF_DOCLN_UPDATE_YJ
*&Report to update the DOCLN field in BSEG, which has a hex value and is
*&shown as # to initial. Please note this report is not to be used for
*&FAGLFLEXA table problems.
REPORT zf_docln_update_yj.
TABLES: bseg.
DATA: BEGIN OF itab_bseg OCCURS 0,
bukrs LIKE bseg-bukrs,
belnr LIKE bseg-belnr,
gjahr LIKE bseg-gjahr,
buzei LIKE bseg-buzei,
docln LIKE bseg-docln,
END OF itab_bseg.
DATA: cnt TYPE i,
cnt_commit TYPE i.
FIELD-SYMBOLS: <docln>.
CONSTANTS: c_badchar(2) TYPE x VALUE '0000',
c_commit TYPE i value 10000.
SELECTION-SCREEN BEGIN OF BLOCK 001 WITH FRAME.
SELECT-OPTIONS: p_bukrs FOR bseg-bukrs,
p_gjahr FOR bseg-gjahr,
p_belnr FOR bseg-belnr,
p_buzei FOR bseg-buzei.
PARAMETERS: update AS CHECKBOX,
detail AS CHECKBOX.
SELECTION-SCREEN END OF BLOCK 001.
SELECT *
INTO CORRESPONDING FIELDS OF TABLE itab_bseg
FROM bseg
WHERE bukrs IN p_bukrs
AND belnr IN p_belnr
AND buzei IN p_buzei
AND gjahr IN p_gjahr.
ASSIGN itab_bseg-docln(1) TO <docln> CASTING TYPE x.
LOOP AT itab_bseg.
IF <docln> EQ c_badchar.
IF update = 'X'.
ADD 1 TO cnt_commit.
UPDATE BSEG SET docln = space
WHERE bukrs = itab_bseg-bukrs
AND belnr = itab_bseg-belnr
AND gjahr = itab_bseg-gjahr
AND buzei = itab_bseg-buzei.
IF cnt_commit GE c_commit.
COMMIT WORK.
CLEAR cnt_commit.
ENDIF.
ENDIF.
ADD 1 TO cnt.
ELSE.
DELETE itab_bseg.
ENDIF.
ENDLOOP.
IF update = 'X'.
COMMIT WORK.
FORMAT COLOR COL_NEGATIVE INTENSIFIED.
WRITE: /'Update Run'.
FORMAT COLOR COL_NEGATIVE INTENSIFIED OFF.
ELSE.
FORMAT COLOR COL_HEADING INTENSIFIED.
WRITE: /'Test Run'.
FORMAT COLOR COL_HEADING INTENSIFIED OFF.
ENDIF.
FORMAT COLOR COL_GROUP INTENSIFIED.
WRITE: /'Report run by ',sy-uname, 'at',sy-uzeit.
FORMAT COLOR COL_GROUP INTENSIFIED OFF.
ULINE.
SKIP 2.
ULINE.
FORMAT COLOR COL_GROUP INTENSIFIED.
WRITE: /'DOCLN changed for Documents'.
FORMAT COLOR COL_GROUP INTENSIFIED OFF.
ULINE.
WRITE: /5 'CoCode',
15 'Doc Num',
30 'Line no',
45 'Fiscal Year',
60 'Six-Figure Line Item for Ledger'.
ULINE.
IF detail EQ 'X'.
LOOP AT itab_bseg.
WRITE:/5 itab_bseg-bukrs,
15 itab_bseg-belnr,
30 itab_bseg-buzei,
45 itab_bseg-gjahr,
60 itab_bseg-docln.
ENDLOOP.
ENDIF.
WRITE: /1 'BSEG Line Item Update Count:', cnt.

Short Dump with VA22 transaction in ECC 6

Hi All,
We are on ECC 6 and facing a short dump whenever we are trying to save some quotation. We are getting the following error.
There is probably an error in the program "SAPLSYDB". The program is triggered in the update task. There, the following ABAP/4 statements are not allowed:
CALL SCREEN
CALL DIALOG
CALL TRANSACTION
SUBMIT
"POSTING_ILLEGAL_STATEMENT" " "
"SAPLSYDB" or "LSYDBU27"
"DB_COMMIT".
Is there a sap note for this. Any link or pointer to this will be highly appreciated.
Regards,
Jayant

Hello,
This looks like a problem for SAP. I assume that you have not modified the
program SAPLSYDB. I also assume that you have searched the Service Marketplasce
for any OSS notes. My next step would be to create a message to SAP to get them to
have a look.
Regards
Greg Kern

Short Dump with Fetch in ECC 6.0

Hello Friends,
I have a query sth like this.
<b>fetch next cursor wc_cursor
into table it_bdi_entry
package size s_pkg.</b>
it_bdi_entry is a internal table of type bdi_entry.
When i use this fetch statement in ECC 6.0 and the fetching row is not all char (like bdi_entry) then i see a short dump saying sth like the source and target are not of same types. How do i overcome this error. please suggest. Thanks in advance.

HI Ramu
I doubt the dump is due to UNICODE compliancy.
In UNICODE systems, we can transfer data between structures only when the structure are similar or having only character fields.
To avoid the dump, we might need to handle field by field.
Hope this helps.
Kind Regards
Eswar

Short dump in ECC 6.0 during delta load

Hi,
We are currently working in BI upgrade project
from BW 2.1c to BI 7.0
At the same time R/3 is being upgraded from 4.0B to ECC 6.0
During delta load we are getting short dump in R/3 system.
Below is the short dump detalis
The current ABAP prgm "SAPMSSY1" had to be terminated because it has come across a statement that unfortunately cannot be executed.
The following syntax error occured in program "/BI0/SAPLQI2LIS_11_VAITM" in include "/BI0/SAPLQI2LIS_11_VAITM" is not Unicode-compatible, according to its attributes.
If any help can be provided on this issue it would be great.
Regards,
Nikhil
Edited by: Nikhil Sakhardanday on Sep 11, 2008 1:58 PM

Hi,
did you made UCCHECK ?
/manfred

[Ugrapde ECC 5.0] Dump in PA-CM

Similar Messages

Maybe you are looking for