dump in migo

[former_member228442]

hi everyone,i get a dump in migo,and it only occurs when move type equal 202

thanks for any help.

[former_member228442]

i debug into the code,and find that at first it creates a belnr number by using a function

the table has only one line,and the value of the field 'BELNR_I' is '$        1',the generated belnr is in field 'BELNR_E'

and then loop table 'mt_acdoc_projected' to get generated belnr by matching field 'BELNR_I'

as you can see,the value in table 'mt_acdoc_projected' is '%      1' and '&       1',but in table 'mt_acdoc_number' there is only one line with value '&      1',so the sy-subrc return 4 when read table with key .

i don't know what happened with it,maybe there are some error in item table?

[Sandra_Rossi]

When you have a short dump with standard SAP program, first search for SAP corrections (as explained in the SAP note). There are lots of notes for "CL_FINS_ACDOC_POSTING_EVENTS ASSERTION_FAILED".

[former_member228442]

thanks,i also searched notes before i write this post,but i find many notes and don't know which to choose,now i find  2201429 maybe can solve this problem.i will try it right now.

[former_member228442]

hi, i find the describe of note 2201429 is suitable with my problem, but the note can't stop migo dump, i use enhancement to change standard code at last.

i write code like this

**********************************************************************

*修复BUG

     DATA LS_mt_acdoc_number2 LIKE LINE OF mt_acdoc_number.

     READ TABLE mt_acdoc_number INTO LS_mt_acdoc_number2

           WITH KEY belnr_i = '%       1'

           .

     IF SY-SUBRC NE 0.

       READ TABLE mt_acdoc_number

        INTO LS_mt_acdoc_number2

       WITH KEY belnr_i = '$       1'.

       if sy-subrc = 0.

       LS_mt_acdoc_number2-belnr_i = '%       1'.

       APPEND LS_mt_acdoc_number2 TO mt_acdoc_number.

       endif.

     ENDIF.

**********************************************************************

[Sandra_Rossi]

You should better contact SAP support rather than doing a correction yourself.

[former_member228442]

yeah,you are right

[edwin_weijers3]

please try to apply OSSnote 2239887. It resolved for me a similar issue with transaction MBST. You can use transaction SNOTE to apply the fix.