SMSY generating runtime error on adding new system

[Former Member]

In our solution manager system, while trying to add a new system details

via SMSY transaction we are getting the Runtime Errors

OBJECTS_OBJREF_NOT_ASSIGNED.

Please find the dump details.

-

---

Runtime Errors OBJECTS_OBJREF_NOT_ASSIGNED

Exception CX_SY_REF_IS_INITIAL

Date and Time 29.05.2008 10:47:54

-

---

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.

-

---

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 "UPDATE_HOST_LCR" "(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: "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.

-

---

Information on where terminated

Termination occurred in the ABAP program "SAPLSMSY_ACTUALIZE_DATA" - in

"UPDATE_HOST_LCR".

The main program was "SAPLSMSY_MAIN ".

In the source code you have the termination point in line 2013

of the (Include) program "LSMSY_ACTUALIZE_DATAF01".

The termination is caused because exception "CX_SY_REF_IS_INITIAL" occurred in

procedure "UPDATE_HOST_LCR" "(FORM)", but it was neither handled locally nor

declared

in the RAISING clause of its signature.

The procedure is in program "SAPLSMSY_ACTUALIZE_DATA "; its source code begins

in line

1983 of the (Include program "LSMSY_ACTUALIZE_DATAF01 ".

-

---

Source Code Extract

Line SourceCde

1983 FORM UPDATE_HOST_LCR USING IV_HOST STRUCTURE SMSY_HOST.

1984

1985 DATA:

1986 ACCESSOR TYPE REF TO CL_SLD_ACCESSOR,

1987 VALUE TYPE STRING,

1988 VALUE1 TYPE STRING,

1989 EX TYPE REF TO CX_SLD_API_EXCEPTION,

1990 T_INAMES TYPE SLD_T_STRING,

1991 INSTREF TYPE REF TO CL_SLD_CIM_INSTANCE,

1992 SYSTREF TYPE REF TO CL_SLD_CIM_INSTANCE,

1993 CLNTREF TYPE REF TO CL_SLD_CIM_INSTANCE,

1994 LINKREF TYPE REF TO CL_SLD_CIM_INSTANCE,

1995 INSTHANDLE TYPE STRING,

1996 SYSTHANDLE TYPE STRING,

1997 CLNTHANDLE TYPE STRING,

1998 LINKHANDLE TYPE STRING,

1999 T_KEYPROP TYPE SLD_T_VALUELIST,

2000 I TYPE I,

2001 PROPLIST TYPE SLD_T_VALUELIST,

2002 PROPERTY TYPE SLD_S_VALUELIST,

2003 FILTER TYPE REF TO CL_SLD_FILTER.

2004

2005 DATA STRING TYPE STRING.

2006 DATA IV_SYSTEM TYPE SMSY_SYSTEM_SAP.

2007

2008 GET_SLD_TOP_INFO.

2009

2010 * Test the connection to the SLD server:

2011 TRY.

2012

>>>>> ACCESSOR->PING( ).

2014

2015 CATCH CX_SLD_API_EXCEPTION INTO EX.

2016 VALUE = EX->GET_TEXT( ).

2017 MSGMACRO 'SCDT_LIS_IF' 'E' 11 'LCR_ERROR'.

2018 ENDTRY.

2019

2020

2021 * Catch all exceptions potentially triggered by the API:

2022 TRY.

2023

2024

2025 * Create a new instance representation object for class SAP_BCSystem.

2026 * If an accessor object is supplied in the constructor, the object

2027 * reference of the representation can be used in other accessor

2028 * methods.

2029 CREATE OBJECT SYSTREF

2030 EXPORTING

2031 CLASSNAME = 'SAP_ComputerSystem'

2032 ACCESSOR = ACCESSOR.

-

---

I am already at the latest support package i.e13

Regards

Anthony

[Former Member]

Hi Anthony

Is your problem solved . I M facing the same problem . I found another thread which is suggesting to follow SAP note 1042815. But it seems that we need to change Some standard include to get it fixed .

Does SAP suggest to change their own program .

Waiting for your reply .