SMSY generating runtime error on adding new system

[Former Member]

Hi,

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. Any help is appreciated.

Regards,

Sandeep.

Runtime Errors OBJECTS_OBJREF_NOT_ASSIGNED

Except. CX_SY_REF_IS_INITIAL

Date and Time 08.05.2008 05:53:40

-

---

-

---

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_SYSTEM_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.

-

---

-

---

Missing RAISING Clause in Interface

Program SAPLSMSY_ACTUALIZE_DATA

Include LSMSY_ACTUALIZE_DATAF01

Row 414

Module type (FORM)

Module Name UPDATE_SYSTEM_LCR

-

---

-

---

Trigger Location of Exception

Program SAPLSMSY_ACTUALIZE_DATA

Include LSMSY_ACTUALIZE_DATAF01

Row 445

Module type (FORM)

Module Name UPDATE_SYSTEM_LCR

-

---

-

---

Source Code Extract

-

---

Line

SourceCde

-

---

415
416	DATA:
417	ACCESSOR TYPE REF TO CL_SLD_ACCESSOR,
418	VALUE TYPE STRING,
419	VALUE1 TYPE STRING,
420	EX TYPE REF TO CX_SLD_API_EXCEPTION,
421	T_INAMES TYPE SLD_T_STRING,
422	INSTREF TYPE REF TO CL_SLD_CIM_INSTANCE,
423	SYSTREF TYPE REF TO CL_SLD_CIM_INSTANCE,
424	CLNTREF TYPE REF TO CL_SLD_CIM_INSTANCE,
425	LINKREF TYPE REF TO CL_SLD_CIM_INSTANCE,
426	INSTHANDLE TYPE STRING,
427	SYSTHANDLE TYPE STRING,
428	CLNTHANDLE TYPE STRING,
429	LINKHANDLE TYPE STRING,
430	T_KEYPROP TYPE SLD_T_VALUELIST,
431	PROPLIST TYPE SLD_T_VALUELIST,
432	PROPERTY TYPE SLD_S_VALUELIST.
433
434	DATA STRING TYPE STRING.
435	DATA INST_NR LIKE IV_SYSTEM-INST_NUMBER.
436
437	FORMAT INTENSIFIED OFF.
438
439	GET_SLD_TOP_INFO.
440	Create accessor object to SLD server:
441
442
443	set trace level for java logging.
444	0 = none, ..., 6 = finest.
>>>>>	ACCESSOR->SET_TRACELEVEL( TRACELEVEL ).
446
447
448	Test the connection to the SLD server:
449	TRY.
450
451	ACCESSOR->PING( ).
452
453	CATCH CX_SLD_API_EXCEPTION INTO EX.
454	VALUE = EX->GET_TEXT( ).
455	MSGMACRO 'SCDT_LIS_IF' 'E' 11 'LCR_ERROR'.
456	ENDTRY.
457
458	IF IV_SYSTEM-INST_NUMBER IS INITIAL.
459	INST_NR = 'UNKNOWN'.
460	ELSE.
461	INST_NR = IV_SYSTEM-INST_NUMBER.
462	ENDIF.
463	IF IV_SYSTEM-SYSTEMNAME(3) <> IV_SYSTEM-SYSTEMNAME.
464	EXIT.

-

---

[Former Member]

Applied corrections mentioned in note 1042815. It has solved the problem.