Dump while doing goods issue against order with movement type 261

Question

Hi Team,
We are integrating Asset management process along with the goods issue against the order which is created with a business partner for movement type 261.
when we try to complete the process the system gives us a dump as described below.
please look through the dump and advice for the same.
Short text
    The current application triggered a termination with a short dump.
What happened?
    The current application program detected a situation which really
    should not occur. Therefore, a termination with a short dump was
    triggered on purpose by the key word MESSAGE (type X).
Error analysis
    Short text of error message:
    System error in the FI/CO interface
    Long text of error message:
     Diagnosis
         Updating of the FI/CO interface was called with object type "MKPF"
         yet the checks were run for object type "AMBU".
     System Response
         Checking and updating must be for the same object type.
     Procedure
         It has to do with a system error from the calling applications.
    Technical information about the message:
    Message class....... "RW"
    Number.............. 103
    Variable 1.......... "MKPF"
    Variable 2.......... "AMBU"
   Variable 3.......... " "
   Variable 4.......... " "
rigger Location of Runtime Error
   Program                                 SAPLMBWL
   Include                                 LMBWLU21
   Row                                     62
   Module type                             (FUNCTION)
   Module Name                             MB_POST_GOODS_MOVEMENT
46    IF xmkpf-xabln IS INITIAL.                               "note 434093
47        CALL FUNCTION 'MB_XAB_NUMBER_GET'.                   "note 434093
48    ENDIF.                                                   "note 434093
49
50 ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_01 SPOTS ES_SAPLMBWL STATIC.
51
52 ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_02 SPOTS ES_SAPLMBWL.
53    CALL FUNCTION 'MB_CREATE_MATERIAL_DOCUMENT_UT'
54         EXCEPTIONS
55           error_message = 4.
56 *  As soon as we have started to put things into UPDATE TASK, we must
57 *  ensure that errors definitely terminate the transaction.
58 *  MESSAGE A is not sufficient because it can be catched from
59 *  external callers which COMMIT WORK afterwards, resulting in
60 *  incomplete updates. Read note 385830 for the full story.
61    IF NOT sy-subrc IS INITIAL.
>>>       MESSAGE ID sy-msgid TYPE x NUMBER sy-msgno WITH            "385830
63                  sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
64 *     MESSAGE A263.
65    ENDIF.
66 * Optische Archivierung
67 * Spaete Erfassung mit Barcode
68 * Redesign of barcode handling -> note 780365
69   PERFORM barcode_update(sapmm07m) USING xmkpf-mblnr
70                                          xmkpf-mjahr
71                                          barcode.
72
73   MOVE-CORRESPONDING xmkpf TO emkpf.
74   CALL FUNCTION 'MB_MOVEMENTS_REFRESH'
75     EXCEPTIONS
76       error_message = 4.
77    MOVE-CORRESPONDING xmkpf TO emkpf.
ource Code Extract
ine  SourceCde
  32 *    BKPF as well. There is no other way to forward XBLNR to FI as not
  33 *    every document is posted by MB_CREATE -> a new function module in
  34 *    MBWL for transferring the information, called by FI, meant to load
  35 *    the complete function group for all MBxx postings when this isn't
  36 *    required (Performance). Would be the better way to transport the
  37 *    information after switching off MBxx in later release.
  38 *    corresponding IMPORT ... FROM MEMORY ... can be found in
  39 *    AC_DOCUMENT_POST (FORM FI_DOCUMENT_PREPARE (LFACIF5D))
  40      l_mem_id = 'MKPF-XBLNR'.                                   " 641365
  41      EXPORT xblnr = xblnr_sd TO MEMORY ID l_mem_id.             " 641365
  42    ELSE.                                                        "1245374
  43      l_mem_id = 'MKPF-XBLNR'.                                   "1245374
  44      FREE MEMORY ID l_mem_id.                                   "1245374
  45    ENDIF.

Answer 1

Couple of notes are mentioned (385830, 780365 etc) and check whether these notes are applied.  If so, check with the ABAPer and go through the source code corrections explained in the respective notes.
You may also go through the following notes
1)  Note 386656 - FBV4: RW103 'System error in the FI/CO interface'
2)  Note 388316 - RW103 "System error in the FI/CO interface"
3) Note 543463 - Inconsistent Posting in budgetary ledger and/or RW102/RW103
thanks
G. Lakshmipathi