OBJECTS_OBJREF_NOT_ASSIGNED" "CX_SY_REF_IS_INITIAL" ZAP2_INTERFACE_LOG46C"

Hello,
Pls i want immediate reply.. i got this error.. i will give full points...ps help me
Thanks in advance.
Runtime Errors         OBJECTS_OBJREF_NOT_ASSIGNED
Exception              CX_SY_REF_IS_INITIAL
Date and Time          16.09.2008 12:31:36
Short text
Access via 'NULL' object reference not possible.
What happened?
Error in the ABAP Application Program
The current ABAP program "ZAP2_INTERFACE_LOG46C" 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_REF_IS_INITIAL', was not
caught and
therefore caused a runtime error.
The reason for the exception is:
You attempted to use a 'NULL' object reference (points to 'nothing')
access a component (variable: "TYPE_DESCR").
An object reference must point to an object (an instance of a class)
before it can be used to access components.
Either the reference was never set or it was set to 'NULL' using the
CLEAR statement.
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:
"OBJECTS_OBJREF_NOT_ASSIGNED" "CX_SY_REF_IS_INITIAL"
"ZAP2_INTERFACE_LOG46C" or "ZAP2_INTERFACE_LOG46C"
"LOAD-OF-PROGRAM"
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... "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.. 0
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.... 0
MM Used. 990672
MM Free. 3196544
User and Transaction
Client.............. 050
User................ "MBAGGALA"
Language key........ "E"
Transaction......... "ZAP2_LOGGING_46C "
Transactions ID..... "48CF3452569D34B8E10000000A831C07"
Program............. "ZAP2_INTERFACE_LOG46C"
Screen.............. "SAPMSSY0 1000"
Screen line......... 3
Information on where terminated
Termination occurred in the ABAP program "ZAP2_INTERFACE_LOG46C" - in
"LOAD-OF-PROGRAM".
The main program was "ZAP2_INTERFACE_LOG46C ".
In the source code you have the termination point in line 20
of the (Include) program "ZAP2_INTERFACE_LOG46C".
Source Code Extract
Line
SourceCde
1
REPORT zap2_interface_log46c .
2
3
*& Report  ZAP2_INTERFACE_LOGGING                                      *
4
5
6
7
8
9
10
INCLUDE zap2_interface_logg46c_top .
11
INCLUDE zap2_interface_logg46c_cl1.
12
INCLUDE zap2_interface_logg46c_stato01.
13
INCLUDE zap2_interface_logg46c_set_f01.
14
15
LOAD-OF-PROGRAM.
16
17
IF kind_p IS INITIAL.
18
DATA type_descr2 TYPE REF TO cl_abap_elemdescr.
19
TYPE_DESCR ?= zap2_cl_abap_typedescr=>describe_by_data( kind_p-kind ).
>>>>>
FIXED_VALUES = TYPE_DESCR->GET_DDIC_FIXED_VALUES( SY-LANGU ).
21
22
23
LOOP AT fixed_values INTO fixed_value.
24
MOVE: fixed_value-low TO kind_p-kind,
25
fixed_value-ddtext TO kind_p-ddtext.
26
APPEND kind_p.
27
ENDLOOP.
28
ENDIF.
29
30
debug_l = 'X'.
31
sdebug_g = 'X'.
32
edebug_g = ' '.
33
return_g = 'X'.
34
35
START-OF-SELECTION.
36
37
IF NOT element IS INITIAL.
38
MOVE 'I' TO elemt_r-sign.
39
MOVE 'EQ' TO elemt_r-option.
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
0
SY-TABIX
0
SY-DBCNT
0
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
Logging tools 46c
SY-MSGTY
SY-MSGID
SY-MSGNO
000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
1
SY-DATUM
20080916
SY-UZEIT
123133
SY-XPROG
SY-XFORM
Active Calls/Events
No.   Ty.          Program                             Include                             Line
Name
2 EVENT        ZAP2_INTERFACE_LOG46C               ZAP2_INTERFACE_LOG46C                  20
LOAD-OF-PROGRAM
1 EVENT        ZAP2_INTERFACE_LOG46C               ???                                     0
SYSTEM-EXIT
Chosen variables
Name
Val.
No.       2 Ty.          EVENT
Name  LOAD-OF-PROGRAM
KIND_P
0000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000
0222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000
CL_GUI_CFW=>FLUSH_SITUATION_PBO
%_CDATE_%_APP_%
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
%_FSREG_001
SY-REPID
ZAP2_INTERFACE_LOG46C
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5453544545444454443342222222222222222222
A102F9E4526135FCF74630000000000000000000
%_DUMMY$$
0000
0000
2222
0000
KIND_P-KIND
32
0
0
TYPE_DESCR
F0000000
F0000000
SYST
########################################################################################X ####
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000E000200
0000000000000000000000000000000000000001000000000000000000000000000000000000010900000001520000
00000000000000000000000001000100000000080000000000000000000000000000000000000B000000000080000C
SY-LANGU
E
0
0
4
5
FIXED_VALUES
Table[initial]
FIXED_VALUE
00000000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000000
22222222222222222222222222222222222222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000000000000000000000000000000000000
SPACE
0
0
2
0
FIXED_VALUE-LOW
0000000000
0000000000
2222222222
0000000000
SESSION
                             00000000000000####
0000000000000000000000000000000000000000000000000000F000
0000000000000000000000000000000000000000000000000000F000
00000000222222222222222222222222222222333333333333330000
00000000000000000000000000000000000000000000000000000000
KIND_P[]
Table[initial]
CTIME-LOW
000000
000000
000000
333333
000000
CL_GUI_CONTROL=>LIFETIME_DEFAULT
No.       1 Ty.          EVENT
Name  SYSTEM-EXIT
SY-XPROG
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
SY-XFORM
000000000000000000000000000000
000000000000000000000000000000
222222222222222222222222222222
000000000000000000000000000000
Internal notes
The termination was triggered in function "ab_jclom"
of the SAP kernel, in line 4706 of the module
"//bas/700_REL/src/krn/runt/abmethod.c#8".
The internal operation just processed is "clom".
Internal mode was started at 20080916123133.
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
(0)  0x4000000003b5b450  CTrcStack + 0x1b0 at dptstack.c:227 [dw.sapRDE_DVEBMGS02]
(1)  0x4000000004d564b0  Z16rabaxCStackSavev + 0x1d0 [dw.sapRDE_DVEBMGS02]
(2)  0x4000000004d5c1a0  ab_rabax + 0x3570 [dw.sapRDE_DVEBMGS02]
(3)  0x40000000040a2310  Z8abjclomv + 0x1690 [dw.sapRDE_DVEBMGS02]
(4)  0x40000000040557d0  Z8abextriv + 0x440 [dw.sapRDE_DVEBMGS02]
(5)  0x4000000003f79bb0  Z9abxeventPKt + 0xb0 at abrunt1.c:281 [dw.sapRDE_DVEBMGS02]
(6)  0x4000000003dc02b0  Z8ablogdbv + 0xb70 at ablogdb.c:116 [dw.sapRDE_DVEBMGS02]
(7)  0x4000000004345ea0  ab_subm + 0x20 at absubmit.c:595 [dw.sapRDE_DVEBMGS02]
(8)  0x4000000001cb97c0  N_ab_subm + 0x20 at dymainstp.c:4769 [dw.sapRDE_DVEBMGS02]
(9)  0x4000000001cc3610  dynpmcal + 0x3f0 at dymainstp.c:2275 [dw.sapRDE_DVEBMGS02]
(10) 0x4000000001cba000  dynppbo0 + 0x280 at dymainstp.c:540 [dw.sapRDE_DVEBMGS02]
(11) 0x4000000001cc13e0  dynprctl + 0x340 at dymainstp.c:358 [dw.sapRDE_DVEBMGS02]
(12) 0x4000000001cacc00  dynpen00 + 0xae0 at dymain.c:1651 [dw.sapRDE_DVEBMGS02]
(13) 0x4000000001fff3d0  Thdynpen00 + 0x520 at thxxhead.c:4843 [dw.sapRDE_DVEBMGS02]
(14) 0x4000000001fc9b80  TskhLoop + 0x5690 at thxxhead.c:3958 [dw.sapRDE_DVEBMGS02]
(15) 0x4000000001fbf320  ThStart + 0x460 at thxxhead.c:1164 [dw.sapRDE_DVEBMGS02]
(16) 0x4000000001576800  DpMain + 0x5f0 at dpxxdisp.c:1095 [dw.sapRDE_DVEBMGS02]
(17) 0x4000000002c30590  nlsui_main + 0x30 [dw.sapRDE_DVEBMGS02]
(18) 0x4000000002c30520  main + 0x60 [dw.sapRDE_DVEBMGS02]
(19) 0xc000000000050150  main_opd_entry + 0x50 [/usr/lib/hpux64/dld.so]
List of ABAP programs affected
Index
Typ
Program
Group
Date
Time
Size
Lang.
0
Prg
ZAP2_INTERFACE_LOG46C
0
15.09.2008
13:34:03
103424
E
1
Prg
SAPMSSY0
1
11.08.2008
21:12:03
92160
E
2
Prg
SAPMSSYD
1
16.08.2006
12:06:37
21504
E
3
Prg
SAPFSYSCALLS
1
09.09.2004
14:18:32
8192
E
4
Prg
ZAP2_CL_ABAP_TYPEDESCR========CP
4
21.08.2008
18:03:55
23552
E
5
Prg
ZAP2_CL_ABAP_ELEMDESCR========CP
5
21.08.2008
18:03:55
21504
E
6
Prg
ZAP2_CL_ABAP_DATADESCR========CP
6
21.08.2008
18:03:55
14336
E
7
Prg
CL_ABAP_REFDESCR==============CP
7
05.07.2005
13:10:15
24576
E
8
Prg
CL_ABAP_DATADESCR=============CP
8
05.07.2005
13:10:15
19456
E
9
Prg
CL_ABAP_TYPEDESCR=============CP
9
05.07.2005
13:10:15
30720
E
10
Prg
CL_ABAP_ELEMDESCR=============CP
10
03.07.2006
10:26:16
36864
E
11
Prg
CL_ABAP_STRUCTDESCR===========CP
11
04.08.2008
19:40:50
40960
E
12
Prg
CL_ABAP_COMPLEXDESCR==========CP
12
05.07.2005
13:10:15
17408
E
13
Prg
CL_ABAP_TABLEDESCR============CP
13
05.07.2005
13:10:15
25600
E
14
Prg
CL_ABAP_CLASSDESCR============CP
14
05.07.2005
13:10:15
30720
E
15
Prg
CL_ABAP_OBJECTDESCR===========CP
15
05.07.2005
13:10:15
34816
E
16
Prg
CL_ABAP_INTFDESCR=============CP
16
05.07.2005
13:10:15
25600
E
17
Prg
ZAP2_CL_ABAP_STRUCTDESCR======CP
17
21.08.2008
18:03:55
18432
E
18
Prg
ZAP2_CL_ABAP_COMPLEXDESCR=====CP
18
21.08.2008
18:03:55
14336
E
19
Prg
ZAP2_CL_ABAP_TABLEDESCR=======CP
19
21.08.2008
18:03:55
18432
E
20
Prg
CX_SY_REF_IS_INITIAL==========CP
20
05.07.2005
13:10:16
10240
E
21
Typ
SCX_SRCPOS
0
18.05.2004
14:07:11
5120
22
Prg
CX_DYNAMIC_CHECK==============CP
22
05.07.2005
13:10:16
10240
E
23
Prg
CX_ROOT=======================CP
23
04.08.2008
18:59:23
11264
E
24
Prg
CX_NO_CHECK===================CP
24
05.07.2005
13:10:16
10240
E
25
Prg
CL_GUI_CFW====================CP
25
28.02.2005
21:03:09
168960
E
26
Typ
SYST
0
09.09.2004
14:18:12
31744
27
Typ
DDFIXVALUE
0
04.08.2008
15:09:55
3072
28
Prg
CL_GUI_CONTROL================CP
28
28.02.2005
21:03:09
112640
E
29
Prg
%_CCNTL
28
18.02.2005
14:15:08
15360
E
30
Typ
OBJ_RECORD
0
14.02.1998
08:30:43
2048
31
Prg
CL_GUI_OBJECT=================CP
31
04.08.2008
19:41:02
376832
E
32
Prg
IF_CACHED_PROP================IP
28
18.02.2005
14:12:55
5120
E
Directory of Application Tables
Name                                     Date       Time       Lngth
Val.
Program  ZAP2_INTERFACE_LOG46C
SYST                                     09.09.2004 14:18:12   00004612
\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\x0001\0
ABAP Control Blocks (CONT)
Index
Name
Fl
PAR0
PAR1
PAR2
PAR3
PAR4
PAR5
PAR6
Source Code
Line
1791
00
0000
ZAP2_INTERFACE_LOGG46C_SET_F01
653
1792
CMPS
20
0247
0038
0038
ZAP2_INTERFACE_LOG46C
17
1794
BRAF
02
002A
ZAP2_INTERFACE_LOG46C
17
1795
STCK
05
0000
ZAP2_INTERFACE_LOG46C
19
1796
ASSI
0F
0000
0052
400E
0000
0000
0000
0000
ZAP2_INTERFACE_LOG46C
19
1800
CLCC
00
0013
ZAP2_INTERFACE_LOG46C
19
1801
clcm
10
0002
0013
0001
0000
0000
0000
0000
ZAP2_INTERFACE_LOG46C
19
1805
PAR1
00
00E3
ZAP2_INTERFACE_LOG46C
19
1806
PAR1
C5
400E
ZAP2_INTERFACE_LOG46C
19
1807
PAR2
00
0000
0001
0000
ZAP2_INTERFACE_LOG46C
19
1809
CAST
00
0000
0031
400E
ZAP2_INTERFACE_LOG46C
19
1811
STCK
06
0000
ZAP2_INTERFACE_LOG46C
19
>>>>>
clom
10
0002
0031
0009
0000
0000
0000
0000
ZAP2_INTERFACE_LOG46C
20
1816
PAR1
01
00B7
ZAP2_INTERFACE_LOG46C
20
1817
PAR1
C1
0032
ZAP2_INTERFACE_LOG46C
20
1818
PAR2
00
0000
0001
0000
ZAP2_INTERFACE_LOG46C
20
1820
LOOP
03
0243
0032
0033
0000
0000
0000
0000
ZAP2_INTERFACE_LOG46C
23
1824
LOOP
05
0000
0032
0033
0000
0000
0000
0000
ZAP2_INTERFACE_LOG46C
23
1828
BRAN
05
0008
ZAP2_INTERFACE_LOG46C
23
1829
MOVE
FF
00F2
00E3
00E5
ZAP2_INTERFACE_LOG46C
24

Hi Madan,
It is BASIS issue, Please ask to find SNOTE correction for this issue. I am unable to recollect that note number.
I am also face the same problem when I am installing the business content.
Thanks,
Chandra

Similar Messages

  • FB01 Error- OBJECTS_OBJREF_NOT_ASSIGNED/CX_SY_REF_IS_INITIAL

    Hi, we have encountered several errors using Transaction FB01.. Please help. Thanks in advance.
    Runtime Errors         OBJECTS_OBJREF_NOT_ASSIGNED
    Exception              CX_SY_REF_IS_INITIAL
    Date and Time          02/17/2010 17:52:57
    Short text
         Access via 'NULL' object reference not possible.
    What happened?
         Error in the ABAP Application Program
         The current ABAP program "SAPLSLVC_FULLSCREEN" 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_REF_IS_INITIAL', was not      caught in    procedure "HTML" "(FORM)", 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:     You attempted to use a 'NULL' object reference (points to 'nothing')
        access a component (variable: "GT_GRID-TOP").     An object reference must point to an object (an instance of a class)
        before it can be used to access components.     Either the reference was never set or it was set to 'NULL' using the
        CLEAR statement.

    Hi ,
    We have the same problem here. DId you fix this error?  Can you please tell us How to reolve this problem?
    Thanks.

  • Lr_bol_entity - OBJECTS_OBJREF_NOT_ASSIGNED - CX_SY_REF_IS_INITIAL

    Hi Experts,
    I am trying to provide access to a program which has the following code.
    LOOP AT it_actid INTO lw_actid.
          lv_low = lw_actid-activity_id.
          lr_bol_query_service->clear_query_parameter_values( ).
          lr_bol_query_service->insert_selection_param( iv_index           = 1
                                                        iv_attr_name       = 'OBJECT_ID'
                                                        iv_sign            = 'I'
                                                        iv_option          = 'EQ'
                                                        iv_low             =  lv_low ).
          lr_result ?= lr_bol_query_service->get_query_result( ).
          IF lr_result  IS BOUND.
            CLEAR : lr_bol_entity .
            lr_bol_entity ?= lr_result->get_first( ).
    The last statement doesn't retrieve any boll objects & the system dumps. i have no clue what this method is trying to read & to my surprise the Trace on ST01 doesn't show any failure !! I wonder what AUth object would solve this issue. But while SAP_ALL is assigned it works & the trace during that time alo doesn't show any extra auth objects being checked !!
    Please developers/Security Consultants throw some light here .
    Cheers.
    Shawn.

    Hi Shawn, could you post please the data declarations? Maybe there is a declaration mismatch (the type of the reults entitties is another than the entity variable that you are using). Which Query(name) are you using?
    Best regards
    Christian

  • OBJECTS_OBJREF_NOT_ASSIGNED

    Hello,
    Pls i want immediate reply.. i got this error.. i will give full points...ps help me
    Runtime Errors         OBJECTS_OBJREF_NOT_ASSIGNED
    Exception              CX_SY_REF_IS_INITIAL
    Date and Time          02.08.2008 13:31:48
    Short text
    Access via 'NULL' object reference not possible.
    What happened?
    Error in the ABAP Application Program
    The current ABAP program "ZNARI_CLASS" 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_REF_IS_INITIAL', was not
    caught and
    therefore caused a runtime error.
    The reason for the exception is:
    You attempted to use a 'NULL' object reference (points to 'nothing')
    access a component (variable: "CAL1").
    An object reference must point to an object (an instance of a class)
    before it can be used to access components.
    Either the reference was never set or it was set to 'NULL' using the
    CLEAR statement.
    How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    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:
    "OBJECTS_OBJREF_NOT_ASSIGNED" "CX_SY_REF_IS_INITIAL"
    "ZNARI_CLASS" or "ZNARI_CLASS"
    "START-OF-SELECTION"
    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... "lenita"
    Network address...... "192.168.10.253"
    Operating system..... "Windows NT"
    Release.............. "5.2"
    Hardware type........ "2x Intel 801586"
    Character length.... 16 Bits
    Pointer length....... 32 Bits
    Work process number.. 1
    Shortdump setting.... "full"
    Database server... "LENITA"
    Database type..... "MSSQL"
    Database name..... "PRD"
    Database user ID.. "prd"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Apr 2 2006 23:08:16"
    create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
    Database version. "SQL_Server_8.00 "
    Patch level. 52
    Patch text.. " "
    Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
    SAP database version. 700
    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
    Memory consumption
    Roll.... 8176
    EM...... 13587912
    Heap.... 0
    Page.... 204800
    MM Used. 569680
    MM Free. 474136
    User and Transaction
    Client.............. 222
    User................ "ABAPUSER"
    Language key........ "E"
    Transaction......... "SE38 "
    Program............. "ZNARI_CLASS"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
    Information on where terminated
    Termination occurred in the ABAP program "ZNARI_CLASS" - in
    "START-OF-SELECTION".
    The main program was "ZNARI_CLASS ".
    In the source code you have the termination point in line 17
    of the (Include) program "ZNARI_CLASS".
    Source Code Extract
    Line
    SourceCde
    1
    2
    *& Report  ZNARI_CLASS
    3
    4
    5
    6
    7
    8
    9
    REPORT  ZNARI_CLASS.
    10
    11
    12
    13
    DATA : CAL1 TYPE REF TO ZCALLING4.
    14
    15
    START-OF-SELECTION.
    16
    >>>>>
    CALL METHOD CAL1->DISPLAY.
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    0
    SY-INDEX
    0
    SY-TABIX
    1
    SY-DBCNT
    0
    SY-FDPOS
    0
    SY-LSIND
    0
    SY-PAGNO
    0
    SY-LINNO
    1
    SY-COLNO
    1
    SY-PFKEY
    SY-UCOMM
    SY-TITLE
    REPORT TO CALL GLOBAL CLASS.
    SY-MSGTY
    SY-MSGID
    SY-MSGNO
    000
    SY-MSGV1
    SY-MSGV2
    SY-MSGV3
    SY-MSGV4
    SY-MODNO
    0
    SY-DATUM
    20080802
    SY-UZEIT
    133147
    SY-XPROG
    RSDBRUNT
    SY-XFORM
    %_INIT_PBO_FIRST
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    1 EVENT        ZNARI_CLASS                         ZNARI_CLASS                            17
    START-OF-SELECTION
    Chosen variables
    Name
    Val.
    No.       1 Ty.          EVENT
    Name  START-OF-SELECTION
    CAL1
    F0000000
    F0000000
    %_DUMMY$$
    2222
    0000
    0000
    0000
    Internal notes
    The termination was triggered in function "ab_jclom"
    of the SAP kernel, in line 4703 of the module
    "//bas/700_REL/src/krn/runt/abmethod.c#6".
    The internal operation just processed is "clom".
    Internal mode was started at 20080802133147.
    Active Calls in SAP Kernel
    Lines of C Stack in Kernel (Structure Differs on Each Platform)
    SAP (R) - R/3(TM) Callstack, Version 1.0
    Copyright (C) SAP AG. All rights reserved.
    Callstack without Exception:
    App       : disp+work.EXE (pid=2640)
    When      : 8/2/2008 13:31:48.187
    Threads   : 2
    Computer Name       : LENITA
    User Name           : SAPServicePRD
    Number of Processors: 2
    Processor Type: x86 Family 15 Model 3 Stepping 4
    Windows Version     : 5.2 Current Build: 3790
    State Dump for Thread Id b64
    eax=0a400000 ebx=00000340 ecx=00000002 edx=00000058 esi=00000340 edi=00000000
    eip=7c8285ec esp=053fbea0 ebp=053fbf10 iopl=0         nv up ei ng nz ac po cy
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000297
    function : KiFastSystemCallRet
    7c8285ec c3               ret
    7c8285ed 8da42400000000   lea     esp,[esp]              ss:053fbea0=7c827d0b
    7c8285f4 8d642400         lea     esp,[esp]              ss:294aa4b3=????????
    FramePtr ReturnAd Param#1  Param#2  Param#3  Param#4  Function Name
    053fbf10 77e61c8d 00000340 0001d4c0 00000000 053fbf48 ntdll!KiFastSystemCallRet
    053fbf24 0100b3aa 00000340 0001d4c0 00000001 7c38b5c8 kernel32!WaitForSingleObject
    053fbf48 0055b4ac 0055b4e5 7c38b5c8 7c38b5c8 7c38b5c8 disp+work!NTDebugProcess [ntstcdbg.c (501)]
    053fbf4c 0055b4e5 7c38b5c8 7c38b5c8 7c38b5c8 01d35ab0 disp+work!NTStack [dptstack.c (1365)]
    053fbf68 0055b519 7c38b5c8 00000000 008536a8 7c38b5c8 disp+work!CTrcStack2 [dptstack.c (352)]
    053fbf74 008536a8 7c38b5c8 00000000 005f0059 00310030 disp+work!CTrcStack [dptstack.c (182)]
    053fbf98 008569fa 4119dfb8 00000000 00000000 053fc030 disp+work!rabax_CStackSave [abrabax.c (6871)
    053fc070 006cf952 013a80e8 013a80b0 0000125f 1e1fc1c8 disp+work!ab_rabax [abrabax.c (1213)]
    053fd09c 0067bb56 00000008 4119e8f4 00000000 053fd104 disp+work!ab_jclom [abmethod.c (4703)]
    053fd104 007af315 51bd965c 00000000 053fd130 00000000 disp+work!ab_extri [abextri.c (552)]
    053fd118 007af71f 01410030 00000000 0000000c 00000000 disp+work!ab_xevent [abrunt1.c (339)]
    053fd130 008a6581 51bd8150 00000000 0000008e 00000025 disp+work!ab_trigg [abrunt1.c (141)]
    053fd148 00596b3d 51bd8150 51bd965c 00000000 00590053 disp+work!ab_run [absubmit.c (403)]
    053fd270 00598503 00000000 51bd8150 00000000 00000000 disp+work!dynpmcal [dymainstp.c (2273)]
    053fd284 00597b13 00000001 51bd8150 00000003 053ffd04 disp+work!dynppai0 [dymainstp.c (1108)]
    053fd2a0 0056dcf1 51bd8150 00000001 00000000 00000002 disp+work!dynprctl [dymainstp.c (359)]
    053ffd04 00471848 00000013 ffffffff 00000001 00494960 disp+work!dynpen00 [dymain.c (1405)]
    053ffd0c ffffffff 00000001 00494960 00000002 01c72400 disp+work!Thdynpen00 [thxxhead.c (4632)]
    053ffee0 00494ee2 00000001 00000000 00000000 00430000 <nosymbols>
    053fff00 00421150 00000000 00000000 7ffdb000 053fff60 disp+work!ThStart [thxxhead.c (1145)]
    053fff14 00401080 00000003 055569d0 00000001 00000000 disp+work!DpMain [dpxxdisp.c (1113)]
    053fff60 011a94a0 00000003 055569d0 055574a0 01bd5000 disp+work!nlsui_main [thxxanf.c (82)]
    053fffc0 77e6f23b 00000000 00000000 7ffdb000 00000000 disp+work!wmainCRTStartup [crtexe.c (395)]
    053ffff0 00000000 011a935d 00000000 00905a4d 00000003 kernel32!ProcessIdToSessionId
    State Dump for Thread Id cb0
    eax=00000001 ebx=00000103 ecx=7c829f59 edx=00440000 esi=00000000 edi=00000000
    eip=7c8285ec esp=0763fec0 ebp=0763ff04 iopl=0         nv up ei pl zr na po nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000246
    function : KiFastSystemCallRet
    7c8285ec c3               ret
    7c8285ed 8da42400000000   lea     esp,[esp]              ss:0763fec0=7c8270fb
    7c8285f4 8d642400         lea     esp,[esp]              ss:2b6ee4d3=????????
    FramePtr ReturnAd Param#1  Param#2  Param#3  Param#4  Function Name
    0763ff04 010f7ffc 000006c0 00000000 00000000 0555fb18 ntdll!KiFastSystemCallRet
    0763ff84 7c349565 00000000 00000000 00000000 0555fa80 disp+work!SigIMsgFunc [signt.c (594)]
    0763ffb8 77e64829 0555fa80 00000000 00000000 0555fa80 MSVCR71!endthreadex
    0763ffec 00000000 7c3494f6 0555fa80 00000000 00000000 kernel32!GetModuleHandleA
    List of ABAP programs affected
    Index
    Typ
    Program
    Group
    Date
    Time
    Size
    Lang.
    0
    Prg
    ZNARI_CLASS
    0
    02.08.2008
    13:31:45
    16384
    E
    1
    Prg
    SAPMSSY0
    1
    02.12.2006
    16:29:39
    90112
    E
    2
    Prg
    SAPMSSYD
    1
    02.12.2006
    16:29:36
    21504
    E
    3
    Prg
    SAPFSYSCALLS
    1
    09.09.2004
    14:18:32
    8192
    E
    4
    Prg
    RSDBRUNT
    0
    02.12.2006
    16:29:28
    251904
    E
    5
    Typ
    RSSCR
    0
    30.03.2005
    10:21:45
    5120
    6
    Prg
    RSDBSPBL
    0
    30.03.2005
    10:21:58
    72704
    E
    7
    Prg
    SAPDB__S
    0
    30.03.2005
    10:22:01
    18432
    E
    8
    Prg
    RSDBSPMC
    0
    02.12.2006
    16:12:36
    78848
    E
    9
    Typ
    DDSHDESCR
    0
    03.09.1997
    03:05:16
    4096
    10
    Typ
    SPPARAMS
    0
    07.05.1997
    13:10:38
    2048
    11
    Typ
    SPPARAMS
    0
    07.05.1997
    13:10:38
    2048
    12
    Prg
    SAPLSABE
    12
    09.09.2004
    14:18:36
    13312
    E
    13
    Prg
    SAPLSECU
    13
    06.02.2007
    17:51:46
    86016
    E
    14
    Typ
    RSSUBINFO
    0
    14.10.1999
    22:01:03
    3072
    15
    Prg
    %_CRSDS
    0
    18.02.2005
    14:15:39
    10240
    E
    16
    Typ
    RSDSEXPR
    0
    20.08.1998
    10:57:18
    3072
    17
    Prg
    SAPFSPOR
    1
    09.09.2004
    14:18:32
    15360
    E
    18
    Prg
    SAPLSCNT
    18
    18.02.2005
    14:16:06
    30720
    E
    19
    Typ
    DYCBOX
    0
    20.08.1998
    11:16:53
    3072
    20
    Prg
    SAPLSVSM
    20
    18.02.2005
    14:16:06
    27648
    E
    21
    Prg
    SAPLSGUI
    21
    02.12.2006
    16:29:39
    82944
    E
    22
    Prg
    SAPLSTTM
    22
    05.07.2005
    13:10:18
    69632
    E
    23
    Prg
    SAPLSBDC
    23
    05.07.2005
    13:10:18
    44032
    E
    24
    Prg
    CL_DATAPROVIDER===============CP
    24
    28.02.2005
    21:00:46
    49152
    E
    25
    Prg
    %_CCNTL
    24
    18.02.2005
    14:15:08
    15360
    E
    26
    Typ
    OBJ_RECORD
    0
    14.02.1998
    08:30:43
    2048
    27
    Prg
    SAPLSTUP
    27
    08.03.2005
    19:04:31
    73728
    E
    28
    Prg
    SAPLCNDP
    28
    02.12.2006
    15:06:02
    193536
    E
    29
    Prg
    SAPSHDTV
    18
    05.01.2005
    16:26:16
    33792
    E
    30
    Prg
    SAPFGUICNTL
    1
    18.02.2005
    14:15:08
    24576
    E
    31
    Prg
    SAPLOLEA
    31
    05.07.2005
    13:10:18
    96256
    E
    32
    Prg
    SAPLSFES
    32
    06.02.2007
    17:51:50
    256000
    E
    33
    Prg
    SAPLSPLUGIN
    33
    09.09.2004
    14:18:36
    8192
    E
    34
    Typ
    ARFCRDATA
    0
    13.02.2005
    18:20:24
    7168
    35
    Prg
    SAPLGRFC
    35
    13.02.2005
    18:20:25
    16384
    E
    36
    Typ
    SWCBCONT
    0
    15.11.2000
    17:55:11
    3072
    37
    Typ
    OLE_VERBS
    0
    04.04.1995
    16:02:20
    2048
    38
    Typ
    OLE_PA
    0
    04.04.1995
    16:02:19
    2048
    39
    Prg
    CX_SY_REF_IS_INITIAL==========CP
    39
    05.07.2005
    13:10:16
    10240
    E
    40
    Typ
    SCX_SRCPOS
    0
    18.05.2004
    14:07:11
    2048
    41
    Prg
    CX_DYNAMIC_CHECK==============CP
    41
    05.07.2005
    13:10:16
    10240
    E
    42
    Prg
    CX_ROOT=======================CP
    42
    05.07.2005
    13:10:16
    11264
    E
    43
    Prg
    CX_NO_CHECK===================CP
    43
    05.07.2005
    13:10:16
    10240
    E
    Directory of Application Tables
    Name                                     Date       Time       Lngth
    Val.
    Program  ZNARI_CLASS
    SYST                                     09.09.2004 14:18:12   00004612
    \0\0\0\0\x0001\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\x0001
    ABAP Control Blocks (CONT)
    Index
    Name
    Fl
    PAR0
    PAR1
    PAR2
    PAR3
    PAR4
    PAR5
    PAR6
    Source Code
    Line
    38
    PERP
    80
    0002
    <SYSINI>
    49
    39
    ENDM
    00
    0000
    <SYSINI>
    50
    40
    00
    0000
    <SYSINI>
    50
    41
    xper
    06
    E90D
    0012
    0019
    <SYSINI>
    55
    43
    PERP
    80
    0001
    <SYSINI>
    55
    44
    PERP
    80
    0002
    <SYSINI>
    55
    45
    ENDM
    00
    0000
    <SYSINI>
    56
    46
    00
    0000
    <SYSINI>
    56
    47
    xper
    06
    2F0C
    001F
    001D
    ZNARI_CLASS
    9
    49
    PERP
    80
    0001
    ZNARI_CLASS
    9
    50
    PERP
    80
    001E
    ZNARI_CLASS
    9
    51
    00
    0000
    ZNARI_CLASS
    9
    >>>>>
    clom
    00
    0000
    0020
    0001
    0000
    0000
    0000
    0000
    ZNARI_CLASS
    17
    56
    PAR2
    00
    0000
    0001
    0000
    ZNARI_CLASS
    17
    58
    00
    0000
    ZNARI_CLASS
    17
    59
    xper
    06
    0DB9
    0021
    0022
    ZNARI_CLASS
    18
    61
    PERP
    80
    0001
    ZNARI_CLASS
    18
    62
    PERP
    80
    0023
    ZNARI_CLASS
    18
    63
    00
    0000
    ZNARI_CLASS
    18
    64
    PARA
    00
    0000
    0024
    0025
    ZNARI_CLASS
    18
    regards,
    Balaram

    Hello,
    From what you display it seems that you have a program called ZNARI_CLASS that was called directly or by another application.
    This program has its code started like this:
    Line      SourceCde
    1      &----
    2      *& Report ZNARI_CLASS
    3      *&
    4      &----
    5      *&
    6      *&
    7      &----
    8      
    9      REPORT ZNARI_CLASS.
    10      
    11      
    12      
    13      DATA : CAL1 TYPE REF TO ZCALLING4.
    14      
    15      START-OF-SELECTION.
    16      
    >>>>>      CALL METHOD CAL1->DISPLAY.
    Well, by the time it was called the variabel CAL1 was empty. This variable is defined by:
    DATA : CAL1 TYPE REF TO ZCALLING4.
    Which means that ZCALLING4 was empty too so the program tried to display an empty variable (CAL1) and generated the short dump:
    You attempted to use a 'NULL' object reference (points to 'nothing')
    access a component (variable: "CAL1").
    Diogo.

  • Asset Fiscal Year Change - Error - OBJECTS_OBJREF_NOT_ASSIGNED

    Hi All,
    Good Morning,
    I completed the dep.run for the year 2008. after this i did the year end activity through AJAB and then tried to change the fiscal year through AJRW.
    In the Test run showing successfully without any errors with green light, but when i executed it background the job was cancelled due to this error - OBJECTS_OBJREF_NOT_ASSIGNED,  CX_SY_REF_IS_INITIAL and in the Error analysis:
    The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
    caught in
    procedure "EXECUTE_PROCESS" "(METHOD)", nor was it propagated by a RAISING
    clause.
    So please give me any possible hint to resolve this issue.
    Best Regards,
    Soma

    Hi,
    The support package is SAP_APPL 600 level-10.
    Program............. "CL_FAA_DC_PROCESS_HANDLER=====CP"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
    source code:
    METHOD execute_process .
      DATA:    lo_previous        TYPE  REF TO object.
      DATA:    lo_instance        TYPE  REF TO object.
    create object, if no instance reference is delivered by caller
      CALL METHOD cf_faa_dc_segments=>find
        EXPORTING
          id_asset_id      = is_processing_info-asset_id
          id_process       = is_processing_info-process
          id_fyear         = is_processing_info-fyear
          ib_keep_instance = is_processing_info-keep_instance
        IMPORTING
          eo_previous      = lo_previous
          eo_instance      = lo_instance.
      eo_segment_handle ?= lo_instance.
    pass instance for asset data access to object
      CALL METHOD eo_segment_handle->set_handle1
        EXPORTING
          io_handle = is_processing_info-asset_instance.
    pass instance reference of previous container to actual object
      IF NOT is_processing_info-previous_handle IS INITIAL.
        lo_previous = is_processing_info-previous_handle.
      ENDIF.
    Continued................
    Regards,
    Soma

  • Problem with Export to Excel from ALV view.

    Hello @all,
    i have a problem on my webdynpro application. I use the component SALV_WD_TABLE. I become display my data but when i want to export the table to ecel, i became a short dump with the message in the browser: Access via 'NULL' object reference not possible.
    When i look at ST22. The system show this text.
    What happened?
        Error in the ABAP Application Program
        The current ABAP program "CL_SALV_WD_A_MODEL_TABLE======CP" 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_REF_IS_INITIAL', was no
         caught in
        procedure "IF_SALV_BS_MODEL_COLUMN~GET_HEADER_BIND_DDIC_FIELD" "(METHOD)
         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:
        You attempted to use a 'NULL' object reference (points to 'nothing')
        access a component (variable: "LR_HEADER").
        An object reference must point to an object (an instance of a class)
        before it can be used to access components.
        Either the reference was never set or it was set to 'NULL' using the
        CLEAR statement.
    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:
        "OBJECTS_OBJREF_NOT_ASSIGNED" "CX_SY_REF_IS_INITIAL"
        "CL_SALV_WD_A_MODEL_TABLE======CP" or "CL_SALV_WD_A_MODEL_TABLE======CM0
        "IF_SALV_BS_MODEL_COLUMN~GET_HEADER_BIND_DDIC_FIELD"
        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
    "IF_SALV_BS_MODEL_COLUMN~GET_HEADER_BIND_DDIC_FIELD" "(METHOD)", or its
      possible occurrence must be declared in the
    RAISING clause of the procedure.
    To prevent the exception, note the following:
    Information on where terminated
        Termination occurred in the ABAP program "CL_SALV_WD_A_MODEL_TABLE======CP" -
         in "IF_SALV_BS_MODEL_COLUMN~GET_HEADER_BIND_DDIC_FIELD".
        The main program was "SAPMHTTP ".
        In the source code you have the termination point in line 19
        of the (Include) program "CL_SALV_WD_A_MODEL_TABLE======CM030".
        The termination is caused because exception "CX_SY_REF_IS_INITIAL" occurred in
        procedure "IF_SALV_BS_MODEL_COLUMN~GET_HEADER_BIND_DDIC_FIELD" "(METHOD)", but
         it was neither handled locally nor declared
        in the RAISING clause of its signature.
        The procedure is in program "CL_SALV_WD_A_MODEL_TABLE======CP "; its source
         code begins in line
        1 of the (Include program "CL_SALV_WD_A_MODEL_TABLE======CM030 ".
    Source Code Extract
    Line  SourceCde
        1 method if_salv_bs_model_column~get_header_bind_ddic_field.
        2
        3   data:
        4     ls_column type if_salv_bs_model_columns=>s_type_column.
        5
        6   ls_column = me->if_salv_bs_model_columns~get_column( column ).
        7
        8 *... get column
        9   data:
       10     lr_column type ref to cl_salv_wd_column.
       11
       12   lr_column ?= ls_column-r_column.
       13
       14   data:
       15     lr_header type ref to cl_salv_wd_column_header.
       16
       17   lr_header = lr_column->get_header( ).
       18
    >>>>>   value = lr_header->get_ddic_binding_field( ).
       20
       21 endmethod.
    i hope anybody can help me.
    Regards
    Chris

    Dear
    How you resolved this issue please let us know.
    Thanks

  • Background landscape fetch getting cancelled in solman

    Dear All,
    I m getting Abap dump in Solution Manager .One of my Background process is getting cancelled Job 'Landscape Fetch' .
    I m pasting the dump here.
    Runtime Errors         OBJECTS_OBJREF_NOT_ASSIGNED
    xception              CX_SY_REF_IS_INITIAL
    ate and Time          07.06.2010 13:00:37
    Short text
    Access via 'NULL' object reference not possible.
    What happened?
        Error in the ABAP Application Program
        The current ABAP program "SAPLSMSY_ACTUALIZE_DATA" 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.
      The exception must either be prevented, caught within proedure
    "SMSYAD_GET_DATA_FROM_LCR" "(FUNCTION)", or its possible occurrence must be
    declared in the
    RAISING clause of the procedure.
    To prevent the exception, note the following:
        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_REF_IS_INITIAL', was not
         caught in
        procedure "SMSYAD_GET_DATA_FROM_LCR" "(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:
        You attempted to use a 'NULL' object reference (points to 'nothing')
        access a component (variable: "ACCESSOR").
        An object reference must point to an object (an instance of a class)
        before it can be used to access components.
        Either the reference was never set or it was set to 'NULL' using the
        CLEAR statement.
    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:
        "OBJECTS_OBJREF_NOT_ASSIGNED" "CX_SY_REF_IS_INITIAL"
        "SAPLSMSY_ACTUALIZE_DATA" or "LSMSY_ACTUALIZE_DATAU14"
        "SMSYAD_GET_DATA_FROM_LCR"
        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
    The exception must either be prevented, caught within proedure
    "SMSYAD_GET_DATA_FROM_LCR" "(FUNCTION)", or its possible occurrence must be
    declared in the
    RAISING clause of the procedure.
    I refer the following note number and implimented that 1042815.But its not working.
    I refer this follwing thread Re: Solution Manager 4.0  Re-Configuration
    Kindly suggest me how to resolve this.
    Regards
    Ashok

    Hello Ashok singh
    I think that this note below will help you to solve this issue. There's a PDF attached in this note that will help you to check this issue step by step. I believe that this issue is being caused by a problem with SLD.
      Number              768452
      Short text          Troubleshooting SLDCHECK - Releases 640, 70X

  • Run time Error while Creating Expense request

    Dear Friends ,
    In   E-Payment ( Expense  Claim )   creation , While clicking on Enter Receipts application is going to run time error for only one user.    
    Run time Error Info :
    Runtime Errors         OBJECTS_OBJREF_NOT_ASSIGNED
    Exception              CX_SY_REF_IS_INITIAL
    Short text
         Access via 'NULL' object reference not possible.
    What happened?
         Error in the ABAP Application Program
         The current ABAP program "CL_WDR_P13N_UTILITIES=========CP" 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_REF_IS_INITIAL', was not
        caught in
       procedure "PRESET" "(METHOD)", 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:
       You attempted to use a 'NULL' object reference (points to 'nothing')
       access a component (variable: "LR_CONTEXT_ELEMENT").
       An object reference must point to an object (an instance of a class)
       before it can be used to access components.
       Either the reference was never set or it was set to 'NULL' using the
       CLEAR statement.
    How to correct the error 
         Probably the only way to eliminate the error is to correct the program.
       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:
       "OBJECTS_OBJREF_NOT_ASSIGNED" "CX_SY_REF_IS_INITIAL"
       "CL_WDR_P13N_UTILITIES=========CP" or "CL_WDR_P13N_UTILITIES=========CM002"
       "PRESET"
    Information on where terminated
        Termination occurred in the ABAP program "CL_WDR_P13N_UTILITIES=========CP" -
         in "PRESET".
        The main program was "SAPMHTTP ".
        In the source code you have the termination point in line 60
        of the (Include) program "CL_WDR_P13N_UTILITIES=========CM002".
        The termination is caused because exception "CX_SY_REF_IS_INITIAL" occurred in
        procedure "PRESET" "(METHOD)", but it was neither handled locally nor declared
        in the RAISING clause of its signature.
        The procedure is in program "CL_WDR_P13N_UTILITIES=========CP "; its source
         code begins in line
        1 of the (Include program "CL_WDR_P13N_UTILITIES=========CM002 ".
    Regards,
    Suresh .

    Hi Agrawal
    As you are getting run-time error after entering the sold to party and material and the error is in SAPLV61Z ,
    close the session for sometime and open again and then create sales order and then enter sold to party and material and then check wheather you are getting or not. If you are still facing the problem then take the help of the ABAP & BASIS consultant's.
    Regards
    Srinath

  • DBIF_RSQL_SQL_ERROR - while dataloading from PSA to InfoCube!

    Hi Friends,
    I know this topic has been posted before too and i have gone through almost all the threads related to this topic but could not find the solution for this issue. Here is the details:
    I am in Production and loading data to one the cube through PSA. Data comes fine till PSA (arround 1 million records). But when I am updating data to Infocube through DTP I am getting the following error:
    Dump: ABAP/4 processor: DBIF_RSQL_SQL_ERROR
    when i click on the error it says the following:
    DBIF_RSQL_SQL_ERROR
    CX_SY_OPEN_SQL_DB
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB'
    According the previous threads on this issue its a Table space issue in Database. But I am sure its not table space issue as my other loads are successfull with much more number of records. I checked in DB02 too and see no problem with the table space.
    I tried selective loading through DTP and my data load was successfull. But this is not the way we want to load the data. we dont want to give any selections in InfoPacakge.  
    I tried to see in ST22 and see the following dumps:
    CONNE_IMPORT_WRONG_COMP_TYPE    CX_SY_IMPORT_MISMATCH_ERROR
    OBJECTS_OBJREF_NOT_ASSIGNED
    CX_SY_REF_IS_INITIAL
    DBIF_RSQL_SQL_ERROR
    CX_SY_OPEN_SQL_DB
    DBIF_RSQL_SQL_ERROR
    CX_SY_OPEN_SQL_DB
    I tried to delete infocube index first before load from PSA. but it did not work for me.
    i would highly appriciate any help from ur side and will awarded with points.
    Thanks,
    Manmit

    Thanks Srinivas. I can not reduce the package size because i am loading data from PSA to InfoCube through DTP. This DTP is created upon a data source which is a genereted export datasource i.e. <b>8XYZABC</b> which does not allow me to change the package size and this is decided at run time. I can see the following under the Extraction Tab of DTP :
    <b>The package size corresponds to package size in source.
    It is determined dynamically at runtime.</b>
    Any idea how to solve this prob?

  • Solution Manager 4.0  Re-Configuration

    hi everyone,
    I am trying to re configure my Solution manager 4.0.  I have deleted my previous business client 100, and created a new one using
    client copy 000. I now have a fresh client 100 in my solman, SOLCLNT100. My problem now is, in tcode SMSY, there is still
    existing systems which i cannot delete.  Whenever i try to delete my QAS in the systems tab, it shows me this message,
    You cannot delete the system as long as it is still used in logical components. How do i delete this logical component assignment if
    i have deleted everything already including my systems in tcode DSWP/SOLUTION_MANAGER? I want to delete this logical assignment
    so i can re configure my SOLMAN.
    many thanks

    Dear Raguraman,
    I m getting same error in Solman.I m trying to implimnet that note in solman but giving message This note is note valid correction instruction.
    i m pasting the dump here.
    Runtime Errors         OBJECTS_OBJREF_NOT_ASSIGNED
    Exception              CX_SY_REF_IS_INITIAL
    Date and Time          07.06.2010 13:00:37
    Short text
    Access via 'NULL' object reference not possible.
    What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLSMSY_ACTUALIZE_DATA" 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_REF_IS_INITIAL', was not
    caught in
    procedure "SMSYAD_GET_DATA_FROM_LCR" "(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:
    You attempted to use a 'NULL' object reference (points to 'nothing')
    access a component (variable: "ACCESSOR").
    An object reference must point to an object (an instance of a class)
    before it can be used to access components.
    Either the reference was never set or it was set to 'NULL' using the
    CLEAR statement.
    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:
    "OBJECTS_OBJREF_NOT_ASSIGNED" "CX_SY_REF_IS_INITIAL"
    "SAPLSMSY_ACTUALIZE_DATA" or "LSMSY_ACTUALIZE_DATAU14"
    "SMSYAD_GET_DATA_FROM_LCR"
    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
    "SMSYAD_GET_DATA_FROM_LCR" "(FUNCTION)", or its possible occurrence must be
    declared in the
    RAISING clause of the procedure.
    |    To prevent the exception, note the following: 
    Please suggest me how to solve this.
    Regards
    Ashok

  • Short Dump Applicant Infotype

    Dear All,
    we have to create a client infotype for an applicant implementation.
    We create succesfully the infotype in transaction PM01.
    The problem is that when we want to test the new infotype in PB30, the system show us a short dump:
    The current ABAP program "SAPFP50P" had to be terminated because it has....
    OBJECTS_OBJREF_NOT_ASSIGNED
    CX_SY_REF_IS_INITIAL
    The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL'
    (variable: "INFOTYPE_CHECK").
    Can you please tell me which is the solution? We are not sure if we need any adittional add-on in the system to customize RC module.
    Many thanks in advance,
    Laura

    Hello Laura
    Check the following steps correctly to create a HR Infotype:
    1) Go to Transaction PM01.
    2) Enter the custom Infotype number which you want to create (Should be a 4 digit number, start with 9).
    3) Select the 'Employee Infotype' radio button.
    4) Select the 'PS Structure Infotype'.
    5) Click on Create... A separate table maintenance window appears...
    6) Create a PS structure with all the fields you want on the Infotype
    7) Save and Activate the PS structure
    8) Go back to the initial screen of PM01.
    9) Click on 'All' push button. It takes a few moments.
    10) Click on 'Technical Characteristics'. Infotype list screen appears
    11) Click on 'Change'(pencil) button
    12) Select your Infotype and click on 'Detail' (magnifying glass) button
    13) Give 'T591A' as subtype table
    14) Give 'T591S' as subtype txt tab
    15) Give your subtype field as subtype field
    16) Save and come back to PM01 initial screen
    17) Click on 'Infotype Characteristics' ... Infotype list screen appears
    18) Click on 'Change' (pencil) button
    19) Click on 'New Entries'
    20) Enter your Infotype number and short text
    21) Here we have to set different Infotype Characteristics as per the requirement. (Better open another session with some standard Infotype's infotype characteristics screen and use as the reference to fill yours)
    22) Save your entries.
    23) Now the Infotype is created and ready to use.
    24) If you want to change the layout of the Infotype as per your requirement...
    25) In the PM01 initial screen...Select 'Screen' radio button and give 2000 as the screen name, then click on edit.
    26) In the next screen.. Select 'Layout Editor' and click 'Change'.
    27) Screen default layout appears...here you can design/modify the screen..change the attributes of the fields..etc.
    28) Save and activate. (Don't forget to 'Activate at every level)
    Subtype Creation :
    Transaction PM01 Goto Subtype Characteristics. Click on Append and then subtype. Enter the name and description of subtype on screen.
    Then goto technical Characteristics and maintain the details of subtype there. I.e name of subtype i.e. component name defined in PSnnnn. Subtype table is T591A.
    Subty.text tab is T591S and time const tab is T591A.
    See:
    http://help.sap.com/saphelp_46c/helpdata/en/4f/d5268a575e11d189270000e8322f96/content.htm
    HR related site:
    http://www.sapdevelopment.co.uk/hr/hrhome.htm
    Enhancement of Infotype
    Check the following
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PAXX/PYINT_INFOTYP.pdf
    Infotype Enhancement overview screen
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/60a7586d-edd9-2910-68a8-8204303835a1

  • Runtime error from null value

    I have a request to create a Function Module that will be assigned to an Action Box, which when executed will copy long text for Quality Notification tasks.  I have the module created and working, but after my code is executed a runtime error happens due to a null value being passed to a method in the SAP program QM07_UPDATE_ACTIONBOX.  It looks to me like it is trying to perform some kind of cleanup tasks, and is trying to delete a node tree that does not exist.  My code did nothing with any kind of node tree, so I am not sure how to avoid this runtime error.  My code works as desired, except for this error that occurs after my code is processed.  Any assistance would be greatly appreciated!  Below are more details from the error received...
    Error analysis
        An exception occurred that is explained in detail below.
        The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not caught in procedure "QM07_UPDATE_ACTIONBOX" "(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:
        You attempted to use a 'NULL' object reference (points to 'nothing') access a component (variable: "TREE_ACTIONBOX").   An object reference must point to an object (an instance of a class) before it can be used to access components.  Either the reference was never set or it was set to 'NULL' using the CLEAR statement.
    Information on where terminated
        Termination occurred in the ABAP program "SAPLQM07" - in "QM07_UPDATE_ACTIONBOX".  The main program was "SAPLIQS0 ".
        In the source code you have the termination point in line 39 of the (Include) program "LQM07U12".  The termination is caused because exception "CX_SY_REF_IS_INITIAL" occurred in procedure "QM07_UPDATE_ACTIONBOX" "(FUNCTION)", but it was neither handled locally nor declared in the RAISING clause of its signature.
        The procedure is in program "SAPLQM07 "; its source code begins in line 1 of the (Include program "LQM07U12 ".
       28 * bei Tree werden Knoten und Items gelöscht bei Table Control wird
       29 * nur g_control_tab neu aufgebaut
       30   if g_tree = c_x.
       31 *---- Löschen der bestehenden Knoten und Items
       32
       33 * Tabelle der Knotenschlüssel erzeugen
       34     loop at g_node_tab into l_node.
       35       append l_node-node_key to l_dnodes_tab.
       36     endloop.
       37
       38 * Items
    >>>>>     call method tree_actionbox->delete_all_items_of_nodes
       40       EXPORTING
       41         node_key_table          = l_dnodes_tab
       42       EXCEPTIONS
       43         failed                  = 1
       44         cntl_system_error       = 2
       45         error_in_node_key_table = 3
       46         dp_error                = 4.

    Yes, I have searched the notes.  I used the keywords suggested in the dump...
    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:
    "OBJECTS_OBJREF_NOT_ASSIGNED" "CX_SY_REF_IS_INITIAL"
    "SAPLQM07" or "LQM07U12"
    "QM07_UPDATE_ACTIONBOX"

  • Runtime error from OCI on OpenVMS

    Hello,
    I hope that this is the appropriate forum to post this question. If not please accept my apologies, and point me in the correct direction.
    Client Environment: OpenVMS V8.3-1H1, Itanium (IA-64), Oracle Release 10.2.0.4.0
    We have ported some C++ code from Oracle 8.17.3 to 10.2.0.4.0, and moved from the OpenVMS Alpha architecture to the Itanium architecture at the same time. Our code now compiles and links and runs, but while attempting to load data into the database, we get the following error traceback (no ORA- error is produced):
    %SYSTEM-F-FLTINV_F, floating invalid fault, PC=000000000F0D7551, PS=0000001B
    ----- End of Exception message
    0 FFFFFFFF804017C2 FFFFFFFF804017C2
    libclntsh lnxren lnxren 87529 0000000000000B11 000000000F0D7551
    libclntsh ttcx2y ttcf2n 428454 0000000000007292 000000000DD35592
    libclntsh ttcacs ttcacs 414366 0000000000001AB2 000000000DD276B2
    libclntsh ttcdrv ttcdrv 1450241 00000000000051F2 000000000DD71692
    libclntsh nioqwa nioqwa 159960 00000000000000B2 000000000D431EE2
    libclntsh upiprv upirtrc 418201 00000000000022D2 000000000D066B72
    libclntsh kpudfo kpuexes 403257 0000000000003F22 000000000CB07F22
    libclntsh upiexf upiex0 402095 0000000000001C62 000000000D081742
    libclntsh upiexf upiexn 401773 0000000000000092 000000000D07FB72
    libclntsh oci ociexn 280403 0000000000004FC2 000000000CFCE212
    TORRENT DATABASE exec #263 00000000000022F2 0000000000FA91B2
    TORRENT TABLE flushCursor #1332 0000000000028332 0000000000FEF9F2
    TORRENT TABLE flushInsertCursor #1348 0000000000023BF2 0000000000FEB2B2
    TORRENT FILE load #819 000000000000A532 0000000000FFA3F2
    TORRENT SCHEMA primeTables #395 0000000000007DC2 0000000000F9ABC2
    TORRENT MAIN main #103 0000000000001112 0000000000F90412
    Any help you can provide on resolving this error would be greatly appreciated. So far, the web has not provided any insight.
    Thanks;
    Glenn

    Yes, I have searched the notes.  I used the keywords suggested in the dump...
    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:
    "OBJECTS_OBJREF_NOT_ASSIGNED" "CX_SY_REF_IS_INITIAL"
    "SAPLQM07" or "LQM07U12"
    "QM07_UPDATE_ACTIONBOX"

  • Loading Issue in PSA..

    Hi Xperts,
    when i am loading the data in PSA.it takes longer time.
    And when i am checking in ST22.i am getting this dump message,
    "DBIF_RSQL_SQL_ERROR     CX_SY_OPEN_SQL_DB"
    Error text message,
    CALL FUNCTION 'RSDU_DB_COMMIT'. "Commit falls duprec bei insert!
      c_lines = 0.
      SORT g_t_u BY
      KEY_DPCW03TDP
      KEY_DPCW03TDT
      KEY_DPCW03TDU
      KEY_DPCW03TD1
      KEY_DPCW03TD2
      KEY_DPCW03TD3
      KEY_DPCW03TD4
    INSERT (l_facttab) FROM TABLE g_t_u.
    c_lines  = sy-dbcnt.
    Check requid if no inconsistency is happened********************
    CALL FUNCTION 'RSM_INFOCUBE_WRITE_CHECK'
      EXPORTING
        i_infocube        = 'DPCW03TD'
        i_rnsid           = i_req_sid
      EXCEPTIONS
        write_not_allowed = 1
    i have created the generic data source by using infoset queries(having two different data sources).
    And i have successfully transported the data sources to quality.Now when i am executing the infopackage.i am getting the above error in monitor screen.
    i have also got some other error messages when loading to PSA.
    The messages are,
    TSV_TNEW_OCCURS_NO_ROLL_MEMORY
    CALL_FUNCTION_SEND_ERROR
    CALL_FUNCTION_REMOTE_ERROR
    OBJECTS_TABLES_NOT_COMPATIBLE
    OBJECTS_OBJREF_NOT_ASSIGNED---CX_SY_REF_IS_INITIAL.

    HI,.
    DBIF_RSQL_SQL_ERROR CX_SY_OPEN_SQL_DB  is an Error related to table space.
    Sytem will show this error is your table space is less.
    This can happen if
    1. multiple loads are running on same table.
    or
    2. There exist old log files in table which should be cleared on regular interval
    Ask your DBA team to increase the table space  and schedule the load again.
    regards,
    Tate.

  • OBJECTS_OBJREF_NOT_ASSIGNED Exep CX_SY_REF_IS_INITIAL in LDB ADA

    Hello all,
    in the report Z_ISR_IMPAC note: (912375) when user runs a large range of 'Asset numbers' the reports abbends with the runtime error (Runtime Errors OBJECTS_OBJREF_NOT_ASSIGNED Exception CX_SY_REF_IS_INITIAL ).
    this happen in the LDB ADA in sentence, PUT ANLAV.
    Does anyone knows a possible solution to prevent this to happen?
    I would appreciate any help with this issue.
    Moderator message - Please respect the 2,500 character maximum when posting. Post only the relevant portions of the dump
    Edited by: Rob Burbank on May 11, 2010 4:55 PM

    This issue had been solved,  the problem was in the users SAPlogon, the solution was updating it for the patch 9 and now is working well.

Maybe you are looking for

  • Safari 7 in Mavericks-Web image quality problems?

    Suddenly, my browser image quality has gone south. Web page images load, but they are very poor quality, and blocky. I have made no changes to settings, nor updates. Any ideas on how to fix this?

  • Asynchronous reserveFinally failed

    We have implemented an NWDI (NW2004s SP10) server, the problem we experience is caused due to an old test configuration in the begin of the project. The default trace is full of the following errors: asynchronous reserveFinally failed I know where th

  • LSO Hide a button

    Hello, I'm working with LSO and I want hide Next Button, Back Buton al TOC Button ... it's possible with un-select the check in Display Options ... but there are other way to do that ... ussing Code HTML o something like that?... please Help me

  • 32 seconds of SD video takes 15 minutes to process...and only 35 mins left!

    I am really getting worried about the power of my brand new MacBook Pro. We already know that my brand new $2000 machine can't handle editing 720p video, and now I am trying to perform an image stabilization on 32 seconds of 640 x 480 video. Its been

  • Error on first reboot after install

    Hi folks, Hopefully someone can help me with this. I am new to Solaris and unix in general, please bear with me. I downloaded the ISO images for 8 2/02 and burned the disks. I installed from Software disk 1. The install proceeded normally as far as I