2538949 - ASSERTION_FAILED occurs during job EU_INIT (SAPRSEUB) running

Symptom

In order to build up where-used list index for all the objects including SAP standard ones, you executed report SAPRSEUB (EU_INIT) as a background job.But during the running of SAPRSEUB (EU_INIT), dump ASSERTION_FAILED occurred as below:

Category

ABAP Programming Error

Runtime Errors

ASSERTION_FAILED

ABAP Program

CL_ABAP_COMPILER==============CP

Application Component

BC-ABA-LA

	Short text
		The ASSERT condition was violated.



	What happened?
		In the running application program, the ASSERT statement recognized a
		situation that should not have occurred.
		The runtime error was triggered for one of these reasons:
		- For the checkpoint group specified with the ASSERT statement, the
		activation mode is set to "abort".
		- Via a system variant, the activation mode is globally set to "abort"
		for checkpoint groups in this system.
		- The activation mode is set to "abort" on program level.
		- the ASSERT statement is not assigned to any checkpoint group.



	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
		The following checkpoint group was used: "No checkpoint group specified"

		If in the ASSERT statement the addition FIELDS was used, you can find
		the content of the first 8 specified fields in the following overview:
		(not used)
		(not used)
		(not used)
		(not used)
		(not used)
		(not used)
		(not used)
		(not used)



	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:

		ASSERTION_FAILED " "
		CL_ABAP_COMPILER==============CP or "CL_ABAP_COMPILER==============CM03S"
		GET_STRUCTURE_SYMBOL

	Information on where terminated
		Termination occurred in the ABAP program "CL_ABAP_COMPILER==============CP" -
		in "GET_STRUCTURE_SYMBOL".
		The main program was "SAPMSSY1 ".

		In the source code you have the termination point in line 20
		of the (Include) program "CL_ABAP_COMPILER==============CM03S".

	Line		SourceCde

	1		method GET_STRUCTURE_SYMBOL .
	2		data:
	3		L_FROM type I,
	4		L_TO type I,
	5		L_COMPONENT type SCR_COMPONENT,
	6		L_FULL_NAME type STRING.
	7
	8		field-symbols:
	9		<L_ITEM> like line of TYPE_CHILDS,
	10		<L_TYPE> like line of TYPES.
	11
	12		create object P_RESULT.
	13
	14		L_FROM = P_ENTRY-REF_OFFSET.
	15		L_TO = P_ENTRY-REF_OFFSET + P_ENTRY-CHILD_CNT - 1.
	16		loop at TYPE_CHILDS from L_FROM to L_TO assigning <L_ITEM>.
	17		READ_TABLE_INDEX TYPES <L_ITEM>-TYPE_OFFSET <L_TYPE>.
	18		L_COMPONENT-NAME = <L_TYPE>-STR.
	19		TYPE_FULL_NAME( exporting P_TYPE_ID = <L_ITEM>-TYPE_OFFSET importing P_RESULT = L_FULL_
	>>>>>		GET_SYMBOL TYPE L_COMPONENT-TYPE L_FULL_NAME <L_TYPE> ?=.
	21		append L_COMPONENT to P_RESULT->COMPONENTS.
	22
	23
	24		endloop.
	25
	26

Environment

Netweaver based systems

Product

SAP NetWeaver 7.1 ; SAP NetWeaver 7.2 ; SAP NetWeaver 7.3 ; SAP enhancement package 1 for SAP NetWeaver 7.3 ; SAP enhancement package 2 for SAP NetWeaver 7.0

Keywords

ASSERTION_FAILED, GET_STRUCTURE_SYMBOL, CL_ABAP_COMPILER, EU_INIT, SAPRSEUB, where-used list, , KBA , BC-DWB-UTL , Workbench Utilities , BC-ABA-LA , Syntax, Compiler, Runtime , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.