Runtime Errors in MR8M

[former_member217601]

Hi all,

I hope this is the appropriate forum, because it happens in MM-IV area.

Have anyone experience this; when trying to cancel an already posted invoice in MR8M, the system issued an error with sort text: Exception condition "SYSTEM_ERROR" raised.

Details as follow:

Runtime Errors         RAISE_EXCEPTION
Date and Time          18.07.2012 16:32:22
 Short text
     Exception condition "SYSTEM_ERROR" raised.
 What happened?
     The current ABAP/4 program encountered an unexpected
     situation.
 Error analysis
     A RAISE statement in the program "SAPLFACI" raised the exception
     condition "SYSTEM_ERROR".
     Since the exception was not intercepted by a superior
     program, processing was terminated.
     Short description of exception condition:
     For detailed documentation of the exception condition, use
     Transaction SE37 (Function Library). You can take the called
     function module from the display of active calls.
     -
 Trigger Location of Runtime Error
     Program                                 SAPLFACI
     Include                                 LFACIF3T
     Row                                     69
     Module type                             (FORM)
     Module Name                             INSERT_NEW_ITEMS
 Source Code Extract
 Line  SourceCde
    39       PERFORM CHECK_SINGLE_MONAT_GJAHR USING    IACCIT_FI-BUKRS
    40                                               g_group_ledger"/glflex/
    41                                                 ACCHD_FI-GLVOR"/glflex/
    42                                                 IACCIT_FI-KOART
    43                                                 IACCIT_FI-HKONT
    44                                                 IACCIT_FI-GJAHR
    45                                                 ACCHD_FI-LDGRP
    46                                        CHANGING IACCIT_FI-MONAT.
    47     ENDLOOP.
    48   ENDIF.
    49
    50 * Check document type and account type
    51   READ TABLE ACCIT_FI WITH KEY KOART = CHAR_V. "according to note 458162
    52   IF SY-SUBRC NE 0.                            "according to note 458162
    53     LOOP AT IACCIT_FI.
    54       PERFORM CHECK_SINGLE_BLART USING IACCIT_FI-BLART
    55                                        IACCIT_FI-KOART
    56                                        ACCIT_FI-AWTYP.
    57     ENDLOOP.
    58   ENDIF.
    59 *
    60 * end of note 581376
    61 *
    62 * Insert new items/amounts into ACCIT_FI/ACCCR_FI
    63   LOOP AT IACCIT_FI.
    64 * Check if item with this POSNR already exists
    65     LOOP AT ACCIT_FI WHERE POSNR EQ IACCIT_FI-POSNR.
    66       EXIT.
    67     ENDLOOP.
    68     IF SY-SUBRC IS INITIAL.
 >>>>>       RAISE SYSTEM_ERROR.
    70     ENDIF.
    71 * Insert new amounts
    72     LOOP AT IACCCR_FI WHERE POSNR EQ IACCIT_FI-POSNR.
    73       ACCCR_FI = IACCCR_FI.
    74       ACCCR_FI-ISTAT = CHAR_2.
    75       APPEND ACCCR_FI.
    76     ENDLOOP.
    77 * Insert new item
    78     ACCIT_FI = IACCIT_FI.
    79     ACCIT_FI-ISTAT = CHAR_2.
    80     APPEND ACCIT_FI.
    81   ENDLOOP.
    82
    83 ENDFORM.                               " INSERT_NEW_ITEMS
    84 *&---------------------------------------------------------------------*
    85 *&      Form  SET_XNEGP_FROM_NEIGHBOURS
    86 *&---------------------------------------------------------------------*
    87 *        Cancel of invoice in MM with crosscompany postings
    88 *----------------------------------------------------------------------*

Please help. Thank you.

[former_member217601 · Accepted solution]

Additional info: this is an invoice without PO reference.

[former_member182673 · Accepted solution]

The invoice you are trying to cancel, is it an MM invoice?, I have my doubts. The dump details refer the field POSNR which is actually sales order item number. So if it is a sales invoice, then obviously you cannot use MR8M for its cancellation , you have to use VF11 transaction.

[former_member217601 · Accepted solution]

Hi Ramesh,

I have checked the document, and verified that it is an MM invoice.

I ran the VF11 just to be sure, and the system cannot accept the document.

[former_member182673 · Accepted solution]

Then let me know how that invoice posted, if not against a PO, then against what? is it against a Delivery note or bill of lading etc.?

[former_member186100 · Accepted solution]

hi Bayu,

not sure if it will help us , but could you share accounting entries for the MIRO document you are looking to reverse. And one more thing , it is always useful and quick way to identify problem via debugging the code during execution with the help of abaper.

[former_member217601 · Accepted solution]

Hi Ramesh, it is an invoice for a material (direct journal).

[former_member217601 · Accepted solution]

Here is the accounting document.

The order currency of the vendor is different from the invoice. Can it raise a problem?

[former_member182673 · Accepted solution]

Order currency of the vendor has no relevance here.

One thing I could see is that there is zero amount posted to FX account in IDR currency, but 0.14 has been posted in USD currency. May be this is the source of the problem.

Alternately you can try posting a credit memo with exact opposite entries using MIRO to nullify the postings instead of using MR8M. While the history of the invoice won't show it as this invoice is cancelled by the new credit memo posted manually, but the end effect in financial postings will be anyway be achieved, which I think is more important.

[former_member217601 · Accepted solution]

Hi Ramesh, thank you for your solution proposal. It is a very good idea, and I have proposed it to my customer, who also happen to see this.

My tests have indeed confirmed that the forex posting triggered the error. I have tried to create another document which did not have/create the FX posting acccount, and I was able to cancel it.

Do you have suggestion on how to correct this condition?

Thank you.

[former_member182673 · Accepted solution]

Even if you post an invoice involving FX, it might work correctly now. So such kind of things happen but cannot be replicated also. What you can do is it take this issue to SAP through OSS message.

BTW did you searched for SAP notes regarding this issue, if not then start searching and if you don't find, you can take up with SAP.

[former_member217601]

Thank you all for sharing your feedback. I really appreciate it.