ABAP run time error in STMS

[former_member228881]

Hi,

We tried to do sap patch upgradation, it ended with error. After that when i try to go for STMS it shows the following error. Because of this i am not able to import anything into the system. Please check and help me out in solving this issue.

Category	ABAP Programming Error
Runtime Errors	SYNTAX_ERROR
ABAP Program	SAPLSUU1

Application Component  BC-SEC-USR-ADM

Date and Time

24.05.2013 01:16:23

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|Short text	|
|	Syntax error in program "SAPLSUU1 ".	|

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|What happened?	|
|	Error in the ABAP Application Program	|
|	|
|	The current ABAP program "SAPLSUSK" had to be terminated because it has	|
|	come across a statement that unfortunately cannot be executed.	|
|	|
|	The following syntax error occurred in program "SAPLSUU1 " in include "LSUU1U09	|
|	" in	|
|	line 262:	|
|	"The type or line type "USRXX_DELETE" cannot be converted to table "USR"	|
|	"07" in the key part"	|
|	" "	|
|	" "	|
|	|
|	The include has been created and last changed by:	|
|	Created by: "SAP "	|
|	Last changed by: "SAP "	|
|	Error in the ABAP Application Program	|
|	|
|	The current ABAP program "SAPLSUSK" had to be terminated because it has	|
|	come across a statement that unfortunately cannot be executed.	|

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|Error analysis	|
|	The following syntax error was found in the program SAPLSUU1 :	|
|	"The type or line type "USRXX_DELETE" cannot be converted to table "USR"	|
|	"07" in the key part"	|
|	" "	|
|	" "	|

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|Trigger Location of Runtime Error	|
|	Program	SAPLSUSK	|
|	Include	LSUSKU01	|
|	Row	136	|
|	Module type	(FUNCTION)	|
|	Module Name	SUSR_RFC_USER_INTERFACE	|

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|Source Code Extract

|

----------------------------------------------------------------------------------------------------

|Line |SourceCde

|

----------------------------------------------------------------------------------------------------

|  106|  PERFORM parameter_check	|
|  107|	USING  user	|
|  108|	activity	|
|  109|	password	|
|  110|	user_group	|
|  111|	valid_from	|
|  112|	valid_until	|
|  113|	user_type.	|
|  114|	|
|  115|  "<<< note 1413686	|
|  116|  "--- enqueue user:	|
|  117|  IF activity <> act_show.	|
|  118|	|
|  119|	CALL FUNCTION 'SUSR_USER_ENQUEUE'	|
|  120|	EXPORTING	|
|  121|	bname  = user_name	|
|  122|	TABLES	|
|  123|	return = lt_return.	|
|  124|	|
|  125|	READ TABLE lt_return ASSIGNING <lp_return> WITH KEY type = 'E'.	|
|  126|	|
|  127|	IF sy-subrc = 0.	|
|  128|	"user is already lock by another process	|
|  129|	MESSAGE ID <lp_return>-id TYPE <lp_return>-type NUMBER <lp_return>-number	|
|  130|	WITH <lp_return>-message_v1 <lp_return>-message_v2	|
|  131|	<lp_return>-message_v3 <lp_return>-message_v4	|
|  132|	RAISING update_error.	|
|  133|	ENDIF.	|
|  134|	|
|  135|	"--- collect necessary data which shouldn't be changed:	|
|>>>>>|	CALL FUNCTION 'SUSR_USER_ALIAS_GET'	|
|  137|	EXPORTING	|
|  138|	user_name = user_name	|
|  139|	IMPORTING	|
|  140|	alias	= ld_alias_old	|
|  141|	EXCEPTIONS	|
|  142|	OTHERS	= 0.	|
|  143|	|
|  144|	CALL FUNCTION 'SUSR_USER_REFUSER_GET'	|
|  145|	EXPORTING	|
|  146|	user_name = user_name	|
|  147|	IMPORTING	|
|  148|	REFUSER   = ld_refuser_old	|
|  149|	EXCEPTIONS	|
|  150|	OTHERS	= 0.	|
|  151|	|
|  152|  ENDIF.   " activity <> act_show	|
|  153|  ">>> note 1413686	|
|  154|	|
|  155|  CASE activity.	|

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|Active Calls/Events

|

----------------------------------------------------------------------------------------------------

|No.   Ty.	Program	Include	Line   |
|	Name	|

----------------------------------------------------------------------------------------------------

|	8 FUNCTION	SAPLSUSK	LSUSKU01	136  |
|	SUSR_RFC_USER_INTERFACE	|
|	7 FUNCTION	SAPLSUSK	LSUSKU01	136  |
|	SUSR_RFC_USER_INTERFACE	|
|	6 FUNCTION	SAPLTMSM	LTMSMU19	122  |
|	TMS_CFG_CREATE_USER_TMSADM	|
|	5 FUNCTION	SAPLTMSM	LTMSMU05	254  |
|	TMS_MGR_CONFIGURE_CLIENT	|
|	4 MODULE (PAI) SAPLTMSU	LTMSUI01	240  |
|	USER_COMMAND_0120	|
|	3 FUNCTION	SAPLTMSU	LTMSUU06	126  |
|	TMS_UI_CONFIGURE_CLIENT	|
|	2 FUNCTION	SAPLTMSU	LTMSUU04	91  |
|	TMS_UI_CONFIGURE_SYSTEM	|
|	1 MODULE (PBO) SAPLTMSU	LTMSUO01	95  |
|	STATUS_0100	|

----------------------------------------------------------------------------------------------------

Regards,

RaJiTh R s

[DavidLY]

Hello,

This issue is resolved with SAP note 1671117 but if SNOTE is locked, you have to implement the note manually.

Next time before starting the upgrade, you can avoid this error by deactivating the option 'Check for active DDIC user' in SPAM->Extras->Settings->Import queue.

Check SAP note 822379 also.

Regards,

David

[former_member228881]

Hi David,

Thanks for the reply..

still the same error continues???

Is there any other solution??

Regards,

RaJiTh R s

[DavidLY]

Hello,

For the error, solution would be to implement the SAP Note 1671117

or
SPAM   > Extras   > Settings   > Import Queue
    > Uncheck "Check for active DDIC user"
(deactivate the DDIC check in SPAM); which is not possible in current scenario as SPAM is locked.

SAP Note 1671117 contains quite large number corrections to implement manually.

So the best way would be to restore the system and start the the import again after unchecking the DDIC Check.

Regards,

David