Skip to Content
0
Former Member
Sep 18, 2009 at 06:29 AM

ASSERTION_FAILED with program RGIMOVV0 during XPRA PHASE

49 Views

Hello guys,

i'm having a problem applying support package EHP3 into an ECC system .

some short part of the dump text :

Runtime Errors ASSERTION_FAILED

Date and Time 17.09.2009 15:05:51

-


-


Short text

The ASSERT condition was violated.

-


-


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

"RGIMOVV0" or "RGIMOVV0"

"FILL_LEDGER_SCENARIOS"

-


Information on where terminated

Termination occurred in the ABAP program "RGIMOVV0" - in

"FILL_LEDGER_SCENARIOS".

The main program was "RGZZGLUX ".

In the source code you have the termination point in line 1724

of the (Include) program "RGIMOVV0".

The program "RGIMOVV0" was started as a background job.

Job Name....... "RDDEXECL"

Job Initiator.. "DDIC"

Job Number..... 15054200

-


-


Source Code Extract

-


Line

SourceCde

-


1694

1695

ENDFORM. " create_add_mov_for_gl_ledger

1696

1697

&----


1698

*& Form fill_ledger_scenarios

1699

&----


1700

  • text

1701

----


1702

FORM fill_ledger_scenarios USING iv_fieldmovement TYPE feldmodif

1703

iv_interface TYPE gl_interface

1704

is_t881 TYPE t881

1705

it_ledger_scen TYPE ty_ledger_scen_tab

1706

it_scen_fields TYPE ty_scen_fields_tab

1707

it_cust_fields TYPE ty_cust_fields_tab.

1708

1709

DATA: ls_ledger_scen TYPE fagl_ledger_scen,

1710

ls_scen_field TYPE fagl_scen_fields,

1711

ls_field_move TYPE fagl_field_move,

1712

ls_field_movec TYPE fagl_field_movec,

1713

ls_cust_field TYPE fagl_cust_fields,

1714

lv_lfieldname TYPE dfies-lfieldname.

1715

1716

LOOP AT it_ledger_scen INTO ls_ledger_scen.

1717

LOOP AT it_scen_fields INTO ls_scen_field

1718

WHERE scenario = ls_ledger_scen-scenario

1719

AND interface = iv_interface.

1720

READ TABLE gt_field_move INTO ls_field_move

1721

WITH TABLE KEY totable = is_t881-tab

1722

tofield = ls_scen_field-field

1723

interface = iv_interface.

>>>>>

ASSERT sy-subrc = 0.

1725

  • co-pa interface table is generated, so first check if field really exists

1726

IF iv_interface = gc_copa_interface.

1727

MOVE ls_field_move-fromfield TO lv_lfieldname.

1728

CALL FUNCTION 'DDIF_NAMETAB_GET'

1729

EXPORTING

1730

tabname = ls_field_move-fromtable

1731

lfieldname = lv_lfieldname

1732

EXCEPTIONS

1733

OTHERS = 1.

1734

CHECK sy-subrc = 0.

1735

ENDIF.

1736

PERFORM append_field USING ls_ledger_scen-client iv_fieldmovement ls_scen_field-field

1737

ls_field_move-fromtable ls_field_move-fromfield ls_field_move-exitname.

1738

ENDLOOP.

1739

ENDLOOP.

1740

1741

LOOP AT it_cust_fields INTO ls_cust_field.

1742

READ TABLE gt_field_movec INTO ls_field_movec

1743

WITH TABLE KEY totable = is_t881-tab

-


did someone of you experience a problem of this kind?

Even performing a local copy I experienced the same and running the program RGIMOVV0 from se38 leads to the same dump. Our development is in stuck .

Regards to all