When using in BI SAP NetWeaver 2004s (700 - SP 15) the transaction ST04old -> Detail analysis menu -> Summary report
The following short dump occurs:
Runtime Errors CONNE_IMPORT_WRONG_COMP_TYPE
Except. CX_SY_IMPORT_MISMATCH_ERROR
Date and Time 19.11.2008 15:14:08
-
-
-
-
Short text
Error when attempting to IMPORT object "TS_CHECK".
-
-
-
-
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLSTD4" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
-
-
-
-
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_IMPORT_MISMATCH_ERROR', was
not caught in
procedure "DB02_ORA_FILL_TS_CHECK__CRITOB" "(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:
When importing the object "TS_CHECK", the component no. 4 in the
dataset has a different type from the corresponding component
of the target object in the program "SAPLSTD4".
The data type is "I" in the dataset, but "N" in the program.
-
-
-
-
Missing RAISING Clause in Interface
Program SAPLSTD4
Include LSTD4U03
Row 1
Module type (FUNCTION)
Module Name DB02_ORA_FILL_TS_CHECK__CRITOB
-
-
-
-
Trigger Location of Exception
Program SAPLSTD4
Include LSTD4U03
Row 51
Module type (FUNCTION)
Module Name DB02_ORA_FILL_TS_CHECK__CRITOB
-
-
-
-
Source Code Extract
-
-
Line
SourceCde
-
-
21
DATA: BEGIN OF TD110.
22
INCLUDE STRUCTURE TD110_STRU.
23
DATA: END OF TD110.
24
25
CURR_TIME = SY-UZEIT.
26
CURR_DATE = SY-DATUM.
27
28
CALL FUNCTION 'GET_DB_ORA_RELEASE'
29
IMPORTING
30
ORACLE_RELEASE = ORA_REL.
31
32
IF FLAG_REFRESH = 'y'. FLAG_REFRESH = 'Y'. ENDIF.
33
flag_refresh = 'Y': Es soll in jedem Fall auf die DB zugegriffen werd.
34
35
CLEAR TS_CHECK. REFRESH TS_CHECK.
36
CLEAR CRITOBJ. REFRESH CRITOBJ.
37
CLEAR NR_CRIT_OBJ.
38
39
IF FLAG_REFRESH <> 'Y'.
40
41
Suche zunächst im Arbeitsspeicher !
42
CLEAR TS_CHECK_CACHE. READ TABLE TS_CHECK_CACHE.
43
IF NOT ( TS_CHECK_CACHE IS INITIAL ) .
44
TS_CHECK[] = TS_CHECK_CACHE[].
45
CRITOBJ[] = CRITOBJ_CACHE[].
46
OK_1 = 'Y'.
47
48
Suche danach in 'MONI' !
49
ELSE.
50
PERFORM PREPARE_MONIKEY USING 2.
>>>>>
IMPORT TS_CHECK CRITOBJ FROM DATABASE MONI(DB) ID MONIKEY.
52
53
IF SY-SUBRC = 0.
54
OK_1 = 'Y'.
55
TS_CHECK_CACHE[] = TS_CHECK[].
56
CRITOBJ_CACHE[] = CRITOBJ[].
57
ENDIF.
58
ENDIF.
59
60
'Same procedure' für datetime:
61
IF NOT ( TD110_CACHE IS INITIAL ).
62
DATETIME-MONI_DATE = TD110_CACHE-DATUM.
63
DATETIME-MONI_TIME = TD110_CACHE-UZEIT.
64
ELSE.
65
PERFORM PREPARE_MONIKEY USING 3.
66
IMPORT TD110 FROM DATABASE MONI(DB) ID MONIKEY.
67
IF SY-SUBRC = 0.
68
DATETIME-MONI_DATE = TD110-DATUM.
69
DATETIME-MONI_TIME = TD110-UZEIT.
70
TD110_CACHE = TD110.
-
-
Only related SDN post is following, but solved by changing permissions for saposcol.
Only related SAP Note is SAP Note Number 597743 "DB02: Poor entries for critical objects list", but not applicable for current SAP version.
For me strange is that this issue occurs on the development system, but not on the acceptance and production system.
Thanks in advance for any assistance.
KR
Gidion