Error on BED,AED,SED in MIGO

Question

Hi experts,
When i am working on MIGO and if i enter the Excise values on item level ( BED,SED,ECS) i am getting a DUMP error. I have asked all the ABAPers and they are unaware of it. I am not sure if it is a ABAP enhancement problem or MM problem.
The following is the error :
Runtime Errors         MESSAGE_TYPE_X
Date and Time          01.03.2012 16:55:29
Short dump has not been completely stored (too big)
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:
    Balance in transaction currency
    Technical information about the message:
    Message classe...... "F5"
    Number.............. 702
    Variable 1.......... 00
    Variable 2.......... " 100.000"
    Variable 3.......... "INR"
    Variable 4.......... " "
Trigger Location of Runtime Error
    Program                                 SAPLMBWL
    Include                                 LMBWLU21
    Row                                     59
    Module type                             (FUNCTION)
    Module Name                             MB_POST_GOODS_MOVEMENT
Line  SourceCde
   29 *    when a goods movement for an inbound or outbound delivery is posted
   30 *    directly from VL31N/ VL01N, XBLNR is not yet known when we call
   31 *    CKMV_AC_DOCUMENT_CREATE, but the number is supposed to be stored in
   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    ENDIF.
   43    IF xmkpf-xabln IS INITIAL.                               "note 434093
   44        CALL FUNCTION 'MB_XAB_NUMBER_GET'.                   "note 434093
   45    ENDIF.                                                   "note 434093
   46
   47 ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_01 SPOTS ES_SAPLMBWL STATIC.
   48
   49 ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_02 SPOTS ES_SAPLMBWL.
   50    CALL FUNCTION 'MB_CREATE_MATERIAL_DOCUMENT_UT'
   51         EXCEPTIONS
   52           error_message = 4.
   53 *  As soon as we have started to put things into UPDATE TASK, we must
   54 *  ensure that errors definitely terminate the transaction.
   55 *  MESSAGE A is not sufficient because it can be catched from
   56 *  external callers which COMMIT WORK afterwards, resulting in
   57 *  incomplete updates. Read note 385830 for the full story.
   58    IF NOT sy-subrc IS INITIAL.
>>>>>       MESSAGE ID sy-msgid TYPE x NUMBER sy-msgno WITH            "385830
   60                  sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
   61 *     MESSAGE A263.
   62    ENDIF.
   63 * Optische Archivierung
   64 * Spaete Erfassung mit Barcode
   65 * Redesign of barcode handling -> note 780365
   66   PERFORM barcode_update(sapmm07m) USING xmkpf-mblnr
   67                                          xmkpf-mjahr
   68                                          barcode.
   69
   70   MOVE-CORRESPONDING xmkpf TO emkpf.
   71   CALL FUNCTION 'MB_MOVEMENTS_REFRESH'
   72     EXCEPTIONS
   73       error_message = 4.
   74    MOVE-CORRESPONDING xmkpf TO emkpf.
   75    CALL FUNCTION 'MB_MOVEMENTS_REFRESH'
   76         EXCEPTIONS
   77           error_message = 4.
   78    IF NOT sy-subrc IS INITIAL.
any help will be useful guys.
thanks in advance guys

Answer 1

Hi,
It seems from the error that balance in transaction currency is the cause so try this
Go to OBYZ -> Procedures
Select the tax procedure you are using say TAXINN
Here for all your ED conditions type
Like JMOP,JMX1 for BED
JAOP,JAX1 for AED
also for all condition type E Cess ,HE cess ,VAT ,CST assign CalType --> 17 (Rounding As per T001R)
And save
Now go to SPRO-> IMG->SAP NetWeaver ->General settings ->Currencies ->Define rounding rules for currencies->
OR use OB90 directly
here maintain a entry For your company code ,Cureency (INR), Rounding unit (100)
Save the entry
Now try to run a new cycle you will find system is rounding off all the tax amounts
Please check and revert