sap EHP upgrade MAIN_NEWBAS/XPRAS_AIMMRG were negative

[Former Member]

Dear Experts,

I am upgrading my ERP DEV system from EHP4 to EHP7 in this system client 100 used as BW client and 300 as source client.

during execution phase  MAIN_NEWBAS/XPRAS_AIMMRG were negative .

_______________________________________________________________________________________________________

13.11.2014    16:22:03    AILDEV_DEV_00    DDIC    000    C    UNCAUGHT_EXCEPTION    CX_RSR_X_MESSAGE    SAPLRRMS

13.11.2014    16:19:28    AILDEV_DEV_00    DDIC    000    C    UNCAUGHT_EXCEPTION    CX_RSR_X_MESSAGE    SAPLRRMS

13.11.2014    16:06:12    AILDEV_DEV_00    DDIC    100    C    UNCAUGHT_EXCEPTION    CX_RSR_X_MESSAGE    SAPLRRMS

13.11.2014    15:59:14    AILDEV_DEV_00    DDIC    000    C    UNCAUGHT_EXCEPTION    CX_RSR_X_MESSAGE    SAPLRRMS

13.11.2014    15:56:39    AILDEV_DEV_00    DDIC    000    C    UNCAUGHT_EXCEPTION    CX_RSR_X_MESSAGE    SAPLRRMS

13.11.2014    15:29:12    AILDEV_DEV_00    DDIC    100    C    UNCAUGHT_EXCEPTION    CX_RSR_X_MESSAGE    SAPLRRMS

13.11.2014    15:23:57    AILDEV_DEV_00    DDIC    100    C    UNCAUGHT_EXCEPTION    CX_RSR_X_MESSAGE    SAPLRRMS

13.11.2014    15:23:02    AILDEV_DEV_00    DDIC    100    C    UNCAUGHT_EXCEPTION    CX_RSR_X_MESSAGE    SAPLRRMS

13.11.2014    14:44:50    AILDEV_DEV_00    DDIC    000    C    UNCAUGHT_EXCEPTION    CX_RSR_X_MESSAGE    SAPLRRMS

13.11.2014    14:42:22    AILDEV_DEV_00    DDIC    000    C    UNCAUGHT_EXCEPTION    CX_RSR_X_MESSAGE    SAPLRRMS

13.11.2014    14:37:17    AILDEV_DEV_00    DDIC    000    C    UNCAUGHT_EXCEPTION    CX_RSR_X_MESSAGE    SAPLRRMS

13.11.2014    14:34:45    AILDEV_DEV_00    DDIC    000    C    UNCAUGHT_EXCEPTION    CX_RSR_X_MESSAGE    SAPLRRMS

13.11.2014    14:25:50    AILDEV_DEV_00    DDIC    000    C    UNCAUGHT_EXCEPTION    CX_RSR_X_MESSAGE    SAPLRRMS

13.11.2014    14:23:22    AILDEV_DEV_00    DDIC    000    C    UNCAUGHT_EXCEPTION    CX_RSR_X_MESSAGE    SAPLRRMS

13.11.2014    14:16:18    AILDEV_DEV_00    DDIC    000    C    UNCAUGHT_EXCEPTION    CX_RSR_X_MESSAGE    SAPLRRMS

13.11.2014    14:13:47    AILDEV_DEV_00    DDIC    000    C    UNCAUGHT_EXCEPTION    CX_RSR_X_MESSAGE    SAPLRRMS

13.11.2014    13:58:32    AILDEV_DEV_00    DDIC    000    C    UNCAUGHT_EXCEPTION    CX_RSR_X_MESSAGE    SAPLRRMS

13.11.2014    13:56:03    AILDEV_DEV_00    DDIC    000    C    UNCAUGHT_EXCEPTION    CX_RSR_X_MESSAGE    SAPLRRMS

13.11.2014    13:48:10    AILDEV_DEV_00    DDIC    000    C    UNCAUGHT_EXCEPTION    CX_RSR_X_MESSAGE    SAPLRRMS

13.11.2014    13:45:36    AILDEV_DEV_00    DDIC    000    C    UNCAUGHT_EXCEPTION    CX_RSR_X_MESSAGE    SAPLRRMS

13.11.2014    13:18:41    AILDEV_DEV_00    DDIC    000    C    UNCAUGHT_EXCEPTION    CX_RSR_X_MESSAGE    SAPLRRMS

13.11.2014    13:03:54    AILDEV_DEV_00    DDIC    000    C    INSERT_PROGRAM_NAME_BLANK        SAPLSEOP

log XPRASUPG.ELG

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

XPRA ERRORS and RETURN CODE in SAPR740XPRA90000134.DEV

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

2 EPU114XXPRA "RSD_XPRA_REPAIR_RSCHAVL_740" has already been executed in a previous step

3 ETP000

3 ETP000 **************************************************

3 ETP000

2 EPU115XReport "RSODSO_XPRA_GUID_TO_SID" started: "20141113162203"

1AETR012XProgram canceled (job "RDDEXECL", number "16220200")

1AEPU320 See job log"RDDEXECL""16220200""DEV"

1 ETP111 exit code          : "12"

>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<

XPRAs are application reports that run at the end of an upgrade.

Most XPRA reports have a report documentation that explains what

the report does and how errors can be corrected.

Call transaction se38 in the SAP system, enter the report name,

select 'Documentation' and click the 'Display' button.

>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<

________________________________Dump detail _____________________________________

Category	ABAP Programming Error
Runtime Errors	INSERT_PROGRAM_NAME_BLANK
ABAP Program	SAPLSEOP

Application Component  BC-DWB-TOO-CLA

Date and Time

13.11.2014 13:03:54

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

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

|Short Text	|
|	Invalid program name with INSERT statement.	|

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

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

|What happened?	|
|	Error in the ABAP Application Program	|
|	|
|	The current ABAP program "SAPLSEOP" 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	|
|	You attempted to insert a program called " " into the database,	|
|	but this name is invalid because it either begins with a blank	|
|	or contains blanks. Blanks are permitted only at the	|
|	end of the name. The program name is the field "FILENAME" and its hexadecimal	|
|	value is 2222222222222222222222222222222222222222.	|
|	|

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

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

|How to correct the error	|
|	Probably the only way to eliminate the error is to correct the program.	|
|	-	|
|	If the error occurs in a non-modfied SAP program, you might be able to	|
|	find a solution in the SAP Notes system. If you have access to the SAP	|
|	Notes system, check there first using the following keywords:	|
|	|
|	"INSERT_PROGRAM_NAME_BLANK"	|
|	"SAPLSEOP" bzw. LSEOPU03	|
|	"SEO_METHOD_GENERATE_INCLUDE"	|

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

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

|System environment	|
|	SAP Release..... 740	|
|	SAP Basis level 0000	|
|	|
|	Application server... SIDDEV	|
|	Network address...... xx.xx.xx.xx	|
|	Operating system... Linux	|
|	Release.............. 2.6.40-0.27-default	|
|	Hardware type....... x86_64	|
|	Character length..... 16 Bits	|
|	Pointer length........ 64 Bits	|
|	Work process number... 13	|
|	Shortdump setting. full	|
|	|
|	Database server... SIDDEV	|
|	Database type..... ORACLE	|
|	Database name..... DEV	|
|	Database user ID SAPSR3	|
|	|
|	Terminal..........	|
|	|
|	Character set C	|
|	|
|	SAP kernel....... 742	|
|	Created on....... Sep  2 2014 15:05:39	|
|	Created at....... Linux GNU SLES-11 x86_64 cc4.3.4 use-pr140815	|
|	Database version OCI_112, 11.2.0.4.0, V2, default	|
|	Patch level....... 17	|
|	Patch text.......	|
|	|
|	Database............. ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*	|
|	SAP database version. 742	|
|	Operating system... Linux 2.6, Linux 3	|
|	|
|	Memory consumption	|
|	Roll.... 0	|
|	EM...... 0	|
|	Heap.... 17366816	|
|	Page.... 40960	|
|	MM used. 7212472	|
|	MM free. 4325832	|

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

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

|User and Transaction	|
|	Client................. 000	|
|	User.................. DDIC	|
|	Language key.......... E	|
|	Transaction.........	|
|	Transaction ID...... 5464EA29A6254816E1000000C0A8070E	|
|	|
|	EPP whole context ID...... 00000116470052004F00550050005F00	|
|	EPP connection ID........ 00000000000000000000000000000000	|
|	EPP call counter......... 0	|
|	|
|	Program.............. SAPLSEOP	|
|	Screen.............. SAPMSSY0	1000	|
|	Screen line.......... 6	|
|	Active debugger..... "none"	|

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

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

|Information on where terminated	|
|	The termination occurred in ABAP program "SAPLSEOP", in	|
|	"SEO_METHOD_GENERATE_INCLUDE". The main program	|
|	was "RDDEXECU".	|
|	|
|	In the source code, the termination point is in line 401 of (Include)	|
|	program "LSEOPU03".	|
|	Program "SAPLSEOP" was started as a background job.	|
|	|
|	Job name....... RDDEXECL	|
|	Job initiator.. DDIC	|
|	Job number...... 13014602	|

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

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

|Source Code Extract

|

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

|Line |SourceCde

|

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

|  371|	|
|  372|	if sy-subrc <> 0.	|
|  373|	if new = seox_true.	|
|  374|	system-call delete method mtdkey-cpdname	|
|  375|	of class mtdkey-clsname.	|
|  376|	endif.	|
|  377|	message e007 with text-cre text-min	|
|  378|	raising internal_error_insert_report.	|
|  379|	endif.	|
|  380|	|
|  381|	if editor_lock is supplied or generated is supplied.	|
|  382|	perform update_method_trdir	|
|  383|	using filename file_inactive editor_lock generated.	|
|  384|	endif.	|
|  385|	|
|  386|	read report filename into source state file_active.	|
|  387|	if sy-subrc <> 0.	|
|  388|	refresh empty_source.	|
|  389|	append seop_src_inactive_new to empty_source.	|
|  390|	insert report filename from empty_source	|
|  391|	extension type srext_ext_class_method	|
|  392|	state file_active	|
|  393|	program type 'I'.	|
|  394|	|
|  395|	if editor_lock is supplied or generated is supplied.	|
|  396|	perform update_method_trdir	|
|  397|	using filename file_active editor_lock generated.	|
|  398|	endif.	|
|  399|	endif.	|
|  400|  else.	|
|>>>>>|	insert report filename from source	|
|  402|	extension type srext_ext_class_method	|
|  403|	state file_active	|
|  404|	program type 'I'.	|
|  405|	if editor_lock is supplied or generated is supplied.	|
|  406|	perform update_method_trdir	|
|  407|	using filename file_active editor_lock generated.	|
|  408|	endif.	|
|  409|  endif.	|
|  410|	|
|  411|  if suppress_index_update = seox_false.	|
|  412|	if not implementation is initial or not implementation_expanded is initial.	|
|  413|	clear empty_source.	|
|  414|	concatenate method_statement mtdkey-cpdname '.'	|
|  415|	into source_line_string separated by space.	|
|  416|	append source_line_string to empty_source.	|
|  417|	append endmethod_statement to empty_source.	|
|  418|	|
|  419|	call function 'RS_PROGRAM_INDEX_DELTA'	|
|  420|	exporting	|

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

[GSerfiotis]

We are facing the same issue. Did you find a solution?

[manumohandas82]

Hi George ,

Are you using the latest SUM tool for the upgrade . Please search for the error in the SAP note 1981278

Thanks ,

Manu

[Reagan]

The SUM Central Note 1926261 - Central Note - Software Update Manager 1.0 SP11 [lmt_007] is addressing this issue.

Here is what the note says:

---------------------< D024828 FEB/28/2014 >--------------------------
Runtime error INSERT_PROGRAM_NAME_BLANK in phase XPRAS_AIMMRG
If the update or upgrade stops in phase XPRAS_AIMMRG with the runtime error INSERT_PROGRAM_NAME_BLANK, see SAP Note 1941711 for more information and further instructions.

Check if the SAP note 1941711 - Dump: INSERT_PROGRAM_NAME_BLANK during After-Import processing of SXCI / SXSD helps you.

Reagan