ASSERTION_FAILED

[Former Member]

Hi Experts

Please provide the reaon for this dump error.

I am using the transaction /DBM/VM for vehicle creation.

Category	ABAP Programming Error
Runtime Errors	ASSERTION_FAILED
ABAP Program	/DBM/CL_VEH_DBMVEHICLE========CP

Application Component  IS-A-DBM

Date and Time

22.05.2012 14:18:55

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.

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) "

Trigger Location of Runtime Error

    Program                                 /DBM/CL_VEH_DBMVEHICLE========CP

    Include                                 /DBM/CL_VEH_DBMVEHICLE========CM00S

    Row                                     30

    Module type                             (METHOD)

    Module Name                             /DBM/IF_OE_OBJECT~SAVE

Source Code Extract

Line  SourceCde

    1 METHOD /dbm/if_oe_object~save.

    2 *The update task function module calls should be put here but in

    3 *case of vehicle the underlying VMS issues in update task fm calls

    4 *so only the iobject update task is generated here.

    5 DATA:

    6 lx_iobject_error      TYPE REF TO /dbm/cx_veh_iobject_error,

    7 lo_action             TYPE REF TO /dbm/cl_veh_action,

    8 lv_action             TYPE vlc_action,

    9 ls_main_action        TYPE cvlc03,

10 ls_action	TYPE cvlc03,
11 ls_incoming_action	TYPE vlcc_cvlc03_ps,

12 ls_elementary_action  TYPE vlcc_cvlc03_ps,

13 lr_vlcdiavehi	TYPE REF TO vlcdiavehi,
14 lt_vlcdiavehi	TYPE TABLE OF vlcdiavehi,
15 lr_vlcactdata_head	TYPE REF TO vlcactdata_head_s,
16 lr_vlcactdata_item	TYPE REF TO vlcactdata_item_s,
17 ls_vlcactdata	TYPE vlcactdata,
18 ls_vlcstatus	TYPE vlcstatus,
19 lt_vlcstatus	TYPE vlcstatus_t,
20 lt_vlc_msgs	TYPE vlch_mssg_pt,
21 lx_layer_not_found	TYPE REF TO /dbm/cx_veh_layer_not_found.

22

23 TRY.

24   mo_iobject->set( ).

25   mo_iobject->save( ).

26 CATCH /dbm/cx_veh_nothing_done.

27 CATCH /dbm/cx_veh_iobject_error INTO lx_iobject_error.

28 ENDTRY.

29

>>> ASSERT lx_iobject_error IS NOT BOUND.

31

32 get_action( IMPORTING eo_action = lo_action ).

33 lo_action->get_action_flavour( IMPORTING es_action_flavour = ls_main_action ).

34 IF ls_main_action-intrlk = abap_true.

35   is_save_pending( IMPORTING ev_action = lv_action ).

36   lo_action->get_action_flavour( EXPORTING iv_action = lv_action

37	IMPORTING es_action_flavour = ls_action ).

38   MOVE-CORRESPONDING ls_main_action TO ls_incoming_action.

39   MOVE-CORRESPONDING ls_action TO ls_elementary_action.

40   lo_action->get_action_text( IMPORTING ev_action_text = ls_incoming_action-aktiont ).

Thanks

Rajaram

[Former Member]

Check this SAP Note 1717638 . This should resolve the dump.

Priya

[Former Member]

Hi Priya

After implementing the note 1717638 still i am having the dump,

Any other note needs to be implemented ?

Can you pls tell me what could be the reason.

Regards

Rajaram

[Clemenss]

Hi raja,

The method calls mo_iobject->set( ) or  mo_iobject->save( ) raised an exception which is caught into exception object lx_iobject_error.

ASSERT lx_iobject_error IS NOT BOUND.

means that the execution is halted and a dump is created if an exception occurred. ASSERT statement is a quick method replacing the old-sytle message type 'X' way.

Ckeck the SAP Note 1717638 as mentioned. If this does not help, put a breakpoint at mo_iobject->set( ) to see where the exception is raised. You can inspect the exception object at the CATch statement.

Things like this are frequently caused by missing or incomplete customizing.

Regards

Clemens

[Former Member]

Hi Clemens

As you told after the debugging i came to know the exception lx_iobject_error as

"An internal number range interval cannot be determined for category DBM_PASSENGERCAR"

So i asked functional to fix this issue.

Thanks for your reply.

Regards

Rajaram