Error in Duty MIRO(Urgent)

Dear Experts,
I have got an issue like this...
User is trying to do Duty MIRO wrto Import PO.It has got 20 line items.
While doing in MIRO,Conditions are displaying two times for only two line items out of 20 line items.
We are using following conditions...Additional Duty,IN Basic Customs,IN CVD,Ecess-Total Customs and Ecess on CVD.
What would be the reason for this?
In POit is showing only once.
Please help me in this issue....
Regards
MK

Hi Suresh,
These conditions are maintained at Header Level only.
Eventhough why it is appearing for only two items???
Please do reply me.
Regards
MK

Similar Messages

Personnel Data Iview Error (It's very Urgent)

Hi All,
Personal Data
Critical Error
A critical error has occured. Processing of the service had to be terminated. Unsaved data has been lost.
Please contact your system administrator.
failed to create or init instance of model 'com.sap.xss.hr.per.in.pdata.model.HRXSS_PER_P0002_IN' in scope APPLICATION_SCOPE with instanceId 'null'
Caused by: com.sap.tc.webdynpro.progmodel.model.api.WDModelException: failed to create instance of model 'com.sap.xss.hr.per.in.pdata.model.HRXSS_PER_P0002_IN'
     at com.sap.tc.webdynpro.progmodel.model.api.WDModelFactory.getNewModelInstance(WDModelFactory.java:392)
     at com.sap.tc.webdynpro.progmodel.model.api.WDModelFactory.getOrCreateModelInstanceFromScopeMaintainer(WDModelFactory.java:329)
     ... 65 more
Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: no jcoMetadata found for RFC function 'HRXSS_PER_GET_F4_P0002_IN'! Please verify, that your model is consistent with the ABAP backend: 'EC6'.
Hi Please help me to solve this error it's very urgent ?
thanks and regards,
Phanikumar.

Hi Ashutosh Gulkhobre,
I coppied the dump from the ST22.
Now please tell me solution fro this error ?
Runtime Errors         OBJECTS_OBJREF_NOT_ASSIGNED_NO
Exception              CX_SY_REF_IS_INITIAL
Date and Time          27.06.2007 09:54:55
     Short text
          Access via 'NULL' object reference not possible.
     What happened?
          Error in the ABAP Application Program
          The current ABAP program "SAPLHRXSS_PER_MAC" had to be terminated because it
           has
          come across a statement that unfortunately cannot be executed.
     What can you do?
          Note down which actions and inputs caused the error.
          To process the problem further, contact you SAP system
          administrator.
          Using Transaction ST22 for ABAP Dump Analysis, you can look
          at and manage termination messages, and you can also
          keep them for a long time.
     Error analysis
          An exception occurred that is explained in detail below.
          The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
           caught in
          procedure "HRXSS_PER_CLEANUP" "(FUNCTION)", nor was it propagated by a RAISING
           clause.
          Since the caller of the procedure could not have anticipated that the
          exception would occur, the current program is terminated.
          The reason for the exception is:
          You attempted to use a 'NULL' object reference (points to 'nothing')
          access a component.
          An object reference must point to an object (an instance of a class)
          before it can be used to access components.
          Either the reference was never set or it was set to 'NULL' using the
          CLEAR statement.
     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:
          "OBJECTS_OBJREF_NOT_ASSIGNED_NO" "CX_SY_REF_IS_INITIAL"
          "SAPLHRXSS_PER_MAC" or "LHRXSS_PER_MACU04"
          "HRXSS_PER_CLEANUP"
          If you cannot solve the problem yourself and want to send an error
          notification to SAP, include the following information:
          1. The description of the current problem (short dump)
             To save the description, choose "System->List->Save->Local File
          (Unconverted)".
          2. Corresponding system log
             Display the system log by calling transaction SM21.
             Restrict the time interval to 10 minutes before and five minutes
          after the short dump. Then choose "System->List->Save->Local File
          (Unconverted)".
          3. If the problem occurs in a problem of your own or a modified SAP
          program: The source code of the program
             In the editor, choose "Utilities->More
          Utilities->Upload/Download->Download".
          4. Details about the conditions under which the error occurred or which
          actions and input led to the error.
          The exception must either be prevented, caught within proedure
          "HRXSS_PER_CLEANUP" "(FUNCTION)", or its possible occurrence must be declared
           in the
          RAISING clause of the procedure.
          To prevent the exception, note the following:
     System environment
          SAP-Release 700
          Application server... "ptgsap10"
          Network address...... "192.168.1.18"
          Operating system..... "Windows NT"
          Release.............. "5.2"
          Hardware type........ "2x Intel 80686"
          Character length.... 16 Bits
          Pointer length....... 32 Bits
          Work process number.. 0
          Shortdump setting.... "full"
          Database server... "PTGSAP10"
          Database type..... "ORACLE"
          Database name..... "EC6"
          Database user ID.. "SAPSR3"
          Char.set.... "C"
          SAP kernel....... 700
          created (date)... "Aug 29 2006 00:18:21"
          create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
          Database version. "OCI_10201_SHARE (10.2.0.1.0) "
          Patch level. 75
          Patch text.. " "
          Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
          SAP database version. 700
          Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
          Memory consumption
          Roll.... 8176
          EM...... 2090448
          Heap.... 0
          Page.... 0
          MM Used. 1208256
          MM Free. 880672
     User and Transaction
          Client.............. 001
          User................ "ESS_USER1"
          Language Key........ "E"
          Transaction......... " "
          Program............. "SAPLHRXSS_PER_MAC"
          Screen.............. "SAPMSSY1 3004"
          Screen Line......... 2
          Information on caller of Remote Function Call (RFC):
          System.............. "########"
          Database Release.... 645
          Kernel Release...... 700
          Connection Type..... "E" (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
          Call Type........... "synchron and non-transactional (emode 0, imode 0)"
          Inbound TID.........." "
          Inbound Queue Name..." "
          Outbound TID........." "
          Outbound Queue Name.." "
          Client.............. "###"
          User................ "############"
          Transaction......... " "
          Call Program........." "
          Function Module..... "HRXSS_PER_CLEANUP"
          Call Destination.... "ptgsap10_EC6_10"
          Source Server....... "EPSAND1"
          Source IP Address... "192.168.1.36"
          Additional information on RFC logon:
          Trusted Relationship " "
          Logon Return Code... 0
          Trusted Return Code. 0
          Note: For releases < 4.0, information on the RFC caller are often
          only partially available.
     Information on where terminated
          Termination occurred in the ABAP program "SAPLHRXSS_PER_MAC" - in
           "HRXSS_PER_CLEANUP".
          The main program was "SAPMSSY1 ".
          In the source code you have the termination point in line 13
          of the (Include) program "LHRXSS_PER_MACU04".
          The termination is caused because exception "CX_SY_REF_IS_INITIAL" occurred in
          procedure "HRXSS_PER_CLEANUP" "(FUNCTION)", but it was neither handled locally
           nor declared
          in the RAISING clause of its signature.
          The procedure is in program "SAPLHRXSS_PER_MAC "; its source code begins in
           line
          1 of the (Include program "LHRXSS_PER_MACU04 ".
     Source Code Extract
     Line     SourceCde
         1     FUNCTION hrxss_per_cleanup.
         2     *"----
         3     ""Local interface:
         4     *" EXPORTING
         5     *"     VALUE(MESSAGES) TYPE BAPIRETTAB
         6     *"----
         7
         8     * CALL METHOD mac_adapter->cleanup
         9     *    IMPORTING
        10     *      messages = messages.
        11
        12     * TRY.
     >>>>>       CALL METHOD xss_adapter->cleanup
        14         .
        15     * CATCH CX_HRPA_VIOLATED_ASSERTION .
        16     * ENDTRY.
        17       IF NOT xss_adapter2 IS INITIAL.
        18         CALL METHOD xss_adapter2->cleanup.
        19       ENDIF.
        20
        21     ENDFUNCTION.
     Contents of system fields
     Name     Val.
     SY-SUBRC     0
     SY-INDEX     2
     SY-TABIX     13
     SY-DBCNT     30
     SY-FDPOS     0
     SY-LSIND     0
     SY-PAGNO     0
     SY-LINNO     1
     SY-COLNO     1
     SY-PFKEY
     SY-UCOMM
     SY-TITLE     CPIC and RFC Control
     SY-MSGTY
     SY-MSGID
     SY-MSGNO     000
     SY-MSGV1
     SY-MSGV2
     SY-MSGV3
     SY-MSGV4
     SY-MODNO     0
     SY-DATUM     20070627
     SY-UZEIT     095455
     SY-XPROG     SAPLHRXSS_PER_MAC
     SY-XFORM     HRXSS_PER_CLEANUP
     Active Calls/Events
     No.   Ty.          Program                             Include                             Line
           Name
         4 FUNCTION     SAPLHRXSS_PER_MAC                   LHRXSS_PER_MACU04                      13
           HRXSS_PER_CLEANUP
         3 FORM         SAPLHRXSS_PER_MAC                   LHRXSS_PER_MACU04                       1
           HRXSS_PER_CLEANUP
         2 FORM         SAPMSSY1                            SAPMSSY1                               85
           REMOTE_FUNCTION_CALL
         1 MODULE (PBO) SAPMSSY1                            SAPMSSY1                               30
           %_RFC_START
     Chosen variables
     Name
         Val.
     No.          4     Ty.      FUNCTION
     Name      HRXSS_PER_CLEANUP
     MESSAGES
          Table[initial]
     SY-XFORM
          HRXSS_PER_CLEANUP
             455555545544444552222222222222
             82833F052F3C51E500000000000000
             000000000000000000000000000000
             000000000000000000000000000000
     %_DUMMY$$
             2222
             0000
             0000
             0000
     XSS_ADAPTER2
             F0000000
             F0000000
     No.          3     Ty.      FORM
     Name      HRXSS_PER_CLEANUP
     SYST-REPID
          SAPLHRXSS_PER_MAC
             5454455555545544422222222222222222222222
             310C82833F052FD1300000000000000000000000
             0000000000000000000000000000000000000000
             0000000000000000000000000000000000000000
     %_%_MESSAGES
          Table[initial]
     No.          2     Ty.      FORM
     Name      REMOTE_FUNCTION_CALL
     %_DUMMY$$
             2222
             0000
             0000
             0000
     SY-REPID
          SAPMSSY1
             5454555322222222222222222222222222222222
             310D339100000000000000000000000000000000
             0000000000000000000000000000000000000000
             0000000000000000000000000000000000000000
     SYST-REPID
          SAPMSSY1
             5454555322222222222222222222222222222222
             310D339100000000000000000000000000000000
             0000000000000000000000000000000000000000
             0000000000000000000000000000000000000000
     HEADER
             000000000000
             000000000000
     TYPE
          3
             0000
             3000
     SY-XPROG
          SAPLHRXSS_PER_MAC
             5454455555545544422222222222222222222222
             310C82833F052FD1300000000000000000000000
             0000000000000000000000000000000000000000
             0000000000000000000000000000000000000000
     %_ARCHIVE
             2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
             0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
             0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
             0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
     RC
          0
             0000
             0000
     SY-XFORM
          HRXSS_PER_CLEANUP
             455555545544444552222222222222
             82833F052F3C51E500000000000000
             000000000000000000000000000000
             000000000000000000000000000000
     %_SPACE
             2
             0
             0
             0
     No.          1     Ty.      MODULE (PBO)
     Name      %_RFC_START
     %_PRINT
              000                                                                                0###
             2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223000
             0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
             0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
             0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
     RFCTYPE_INTERNAL
          3
             0000
             3000
     Internal notes
          The termination was triggered in function "method_call_iref"
          of the SAP kernel, in line 2203 of the module
           "//bas/700_REL/src/krn/runt/abmethod.c#7".
          The internal operation just processed is "METH".
          Internal mode was started at 20070627095455.
     Active Calls in SAP Kernel
     Lines of C Stack in Kernel (Structure Differs on Each Platform)
     SAP (R) - R/3(TM) Callstack, Version 1.0
     Copyright (C) SAP AG. All rights reserved.
     Callstack without Exception:
     App       : disp+work.EXE (pid=24080)
     When      : 6/27/2007 9:54:55.565
     Threads   : 2
     Computer Name       : PTGSAP10
     User Name           : SAPServiceEC6
     Number of Processors: 2
     Processor Type: x86 Family 6 Model 11 Stepping 1
     Windows Version     : 5.2 Current Build: 3790
     State Dump for Thread Id 6cd0
     eax=000a7358 ebx=00000464 ecx=00000248 edx=00000000 esi=00000464 edi=00000000
     eip=7c82ed54 esp=0549c640 ebp=0549c6b0 iopl=0         nv up ei ng nz ac po cy
     cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000             efl=00200297
     function : KiFastSystemCallRet
             7c82ed54 c3               ret
             7c82ed55 8da42400000000   lea     esp,[esp]              ss:0549c640=7c822124
             7c82ed5c 8d642400         lea     esp,[esp]              ss:27f2ac53=????????
     FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
     0549c6b0 77e6ba12 00000464 0001d4c0 00000000 0549c6e8 ntdll!KiFastSystemCallRet
     0549c6c4 0101f939 00000464 0001d4c0 00000001 7c38b5c8 kernel32!WaitForSingleObject
     0549c6e8 005641c2 005641fb 7c38b5c8 7c38b5c8 7c38b5c8 disp+work!NTDebugProcess [ntstcdbg.c (501)]
     0549c6ec 005641fb 7c38b5c8 7c38b5c8 7c38b5c8 01d87888 disp+work!NTStack [dptstack.c (1367)]
     0549c708 0056422f 7c38b5c8 00000000 0085f2b9 7c38b5c8 disp+work!CTrcStack2 [dptstack.c (352)]
     0549c714 0085f2b9 7c38b5c8 00000000 005f0059 00300030 disp+work!CTrcStack [dptstack.c (182)]
     0549c738 008626fb 3ccf0c10 00008006 00000000 00660bd8 disp+work!rabax_CStackSave [abrabax.c (7020)
     0549cfe0 0067f9fc 01285324 012852e4 0000089b 2054de20 disp+work!ab_rabax [abrabax.c (1243)]
     0549d010 006914a8 00000003 3cda5308 00000000 0549d078 disp+work!method_call_iref [abmethod.c (2203
     0549d078 007c8d1e 00000000 3cda5308 0549d1c4 3cda67e8 disp+work!ab_extri [abextri.c (552)]
     0549d08c 008433d6 00000000 3cda6768 0059fdb0 3cda64b4 disp+work!ab_xevent [abrunt1.c (281)]
     0549d098 0059fdb0 3cda64b4 00000008 3cda6768 00000000 disp+work!ab_dstep [abdynpro.c (491)]
     0549d1c4 005a2ae2 3cda5308 3cda5308 0549fd04 005a2654 disp+work!dynpmcal [dymainstp.c (2394)]
     0549d1d4 005a2654 3cda5308 3cda5308 00000003 0549fd04 disp+work!dynppbo0 [dymainstp.c (542)]
     0549d1f0 00577116 3cda5308 00000004 00000000 0000001a disp+work!dynprctl [dymainstp.c (359)]
     0549fd04 004741c6 0000001a 00000001 00000001 0049792f disp+work!dynpen00 [dymain.c (1464)]
     0549fd14 0049792f 00000004 00000000 00000003 00000002 disp+work!Thdynpen00 [thxxhead.c (4683)]
     0549fee0 00497ead 00000001 00000000 00000000 00430000 disp+work!TskhLoop [thxxhead.c (4395)]
     0549ff00 004214f1 00000000 00000000 7ffd5000 0549ff60 disp+work!ThStart [thxxhead.c (1153)]
     0549ff14 00401080 00000003 056368d8 00000001 00000000 disp+work!DpMain [dpxxdisp.c (1119)]
     0549ff60 011bf720 00000003 056368d8 056378c8 01c05000 disp+work!nlsui_main [thxxanf.c (82)]
     0549ffc0 77e523cd 00000000 00000000 7ffd5000 80938fd6 disp+work!wmainCRTStartup [crtexe.c (395)]
     0549fff0 00000000 011bf5dd 00000000 00905a4d 00000003 kernel32!IsProcessorFeaturePresent
     State Dump for Thread Id 6408
     eax=00000001 ebx=00000103 ecx=0770fee8 edx=7c82ed54 esi=00000000 edi=00000000
     eip=7c82ed54 esp=0770fec0 ebp=0770ff04 iopl=0         nv up ei pl zr na po nc
     cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000             efl=00000246
     function : KiFastSystemCallRet
             7c82ed54 c3               ret
             7c82ed55 8da42400000000   lea     esp,[esp]              ss:0770fec0=7c821514
             7c82ed5c 8d642400         lea     esp,[esp]              ss:2a19e4d3=????????
     FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
     0770ff04 0110e0b7 000006e0 00000000 00000000 059ca9d8 ntdll!KiFastSystemCallRet
     0770ff84 7c349565 00000000 00000000 00000000 0563a508 disp+work!SigIMsgFunc [signt.c (594)]
     0770ffb8 77e66063 0563a508 00000000 00000000 0563a508 MSVCR71!endthreadex
     0770ffec 00000000 7c3494f6 0563a508 00000000 00000000 kernel32!GetModuleFileNameA
     List of ABAP programs affected
     Index     Typ     Program     Group     Date     Time     Size     Lang.
          0     Prg     SAPMSSY1          0     11.04.2005     09:27:15         21504     E
          1     Prg     SAPLHRXSS_SER_AUTHORITHY_CHECK          1     13.02.2005     19:00:30         16384     E
          2     Prg     SAPLASTAT_TRIG          2     09.09.2004     14:18:33         13312     E
          3     Typ     ASTAT_TYP2          0     10.11.1998     05:35:18          2048
          4     Typ     ASTAT_TYP1          0     30.11.1998     15:54:16          2048
          5     Prg     SAPLSAUTHTRACE          5     07.03.2005     08:51:05         57344     E
          6     Typ     USOBHASH          0     02.07.2003     13:15:24          3072
          7     Prg     SAPLSECH          7     05.07.2005     13:10:18         26624     E
          8     Typ     CVERS          0     09.11.2000     14:05:49          2048
          9     Prg     SAPLHRXSS_PER_MAC          9     10.02.2004     14:21:15         49152     E
         10     Prg     CX_SY_REF_IS_INITIAL==========CP         10     05.07.2005     13:10:16         10240     E
         11     Typ     SCX_SRCPOS          0     18.05.2004     14:07:11          2048
         12     Prg     CX_DYNAMIC_CHECK==============CP         12     05.07.2005     13:10:16         10240     E
         13     Prg     CX_ROOT=======================CP         13     05.07.2005     13:10:16         11264     E
         14     Prg     CX_NO_CHECK===================CP         14     05.07.2005     13:10:16         10240     E
         15     Prg     CX_SY_NO_HANDLER==============CP         15     05.07.2005     13:10:16         10240     E
         16     Typ     SYST          0     09.09.2004     14:18:12         31744
     Directory of Application Tables
     Name                                     Date       Time       Lngth
         Val.
     Program      SAPMSSY1
     SYST            . .            : :          00004612
          \0\0\0\0\x000D\0\x000F\0\0\0\0\0\0\0\0\0\0\0\0\0\x001E\0\0
     ABAP Control Blocks (CONT)
     Index     Name     Fl     PAR0     PAR1     PAR2     PAR3     PAR4     PAR5     PAR6     Source Code     Line
       246     FUNC     03     0020                                   LHRXSS_PER_MACU03            1
       247     PAR2     02     0000     001B     C000                         LHRXSS_PER_MACU03            1
       249     FUNC     13     0003                                   LHRXSS_PER_MACU03            1
       250     PAR2     01     0000     0011     C001                         LHRXSS_PER_MACU03            1
       252     FUNC     FF     0000                                   LHRXSS_PER_MACU03            1
       253     ENDF     00     0000                                   LHRXSS_PER_MACU03            1
       254     -
     00     0000                                   LHRXSS_PER_MACU03            1
       255     STCK     02     C001                                   LHRXSS_PER_MACU03            1
       256     CPOP     00     0000                                   LHRXSS_PER_MACU03            1
       257     -
     00     0000                                   LHRXSS_PER_MACU03            1
       258     FUNP     3E     0000     0011     8000     0000     8000     0000     0000     LHRXSS_PER_MACU04            1
       262     FUNP     80     0000     0000     0000     0000     0000     0000     0000     LHRXSS_PER_MACU04            1
     >>>>>     METH     03     0000     0000     8006     0000     0000     0000     0000     LHRXSS_PER_MACU04           13
       270     PAR2     00     0000     0001     0000                         LHRXSS_PER_MACU04           13
       272     CMPS     20     024B     001B     001B                         LHRXSS_PER_MACU04           17
       274     BRAF     05     0007                                   LHRXSS_PER_MACU04           17
       275     METH     03     0000     0001     8006     0000     0000     0000     0000     LHRXSS_PER_MACU04           18
       279     PAR2     00     0000     0001     0000                         LHRXSS_PER_MACU04           18
       281     FUNE     00     0000                                   LHRXSS_PER_MACU04           21
       282     -
     00     0000                                   LHRXSS_PER_MACU04           21
Thanks and Regards,
Phanikumar

Error Pl help-Very urgent!

Am getting the following error.Please help very urgent
500 Translator.CompilationFailedExceptionCompiler errors:
Found 1 semantic error compiling "D:/JRun4/servers/default/default-ear/default-war/WEB-INF/jsp/jrun__quicklinks2ejspf.java":
502. for (Enumeration e = prioLinkBean.getGlobalTop() ; e.hasMoreElements() ;)
<---------->
*** Error: "prioLinkBean" is either a misplaced package name or a non-existent entity.
Translator.CompilationFailedExceptionCompiler errors:
Found 1 semantic error compiling "D:/JRun4/servers/default/default-ear/default-war/WEB-INF/jsp/jrun__quicklinks2ejspf.java":
502. for (Enumeration e = prioLinkBean.getGlobalTop() ; e.hasMoreElements() ;)
<---------->
*** Error: "prioLinkBean" is either a misplaced package name or a non-existent entity.

prioLinkBean.getGlobalTop();
are u sure this method returns an Enumeration ???
post ur code!
[email protected]

Error in MIRO - Urgent

Hi all,
I had created a PO that contains an item i.e. cement. The price per kg is 171. The PO was old and the price changed when the material was recieved. so we want to post susequent debit in MIRO. while posting the difference, system is giving error that "Price too high (tolerance limit of 0.00 PKR exceeded) ". please suggest that what we should do?. we have done the same things many time before.
regards,
AI.

if u change the tolerance limits from 0 to any limit or do not check then the user willbe able to manipulate the price in the invoice generation thru miro which means in a normal scenario if a vendor is liable to get a sum of lets say rs.10/item,becoz of the generosity of ur user he can get rs.9 or rs.11/item.
regards,
indranil

Error while posting INvoice in MIRO *** URGENT****

Hi,
System is not allowing me to save an invoice in MIRO which says Reference date and Asset value date in the LINE ITEM are not in date format "//--" though we have left thefields as dafault (and have entered nothing there).
These fields are filled with some default format with say like "//" . I have deleted these dots and i have tried to post the invoice again. Still the system says Reference date / Asset value date in the line item is not in date format "//".
This problem is arising only when i try to pass capital bills and not for others.
This problem was not there even before upgradation to 6.0 (Recently upgraded from 4.7)
Do i need to change these fields as optional ??? Why it was not there previously ??
Pls advise.

Hi,
Change the date format from Manu Bar> System > User Profile> Own Data> goto tab Defaults and change the date format to DD/MM/YYYY before doing MIRO.
Thanks
VK

Error when doing MIRO

Hi,
We get the error as below while doing MIRO.
'Customization for GM1 j_1iindcus missing in table'
How do we proceed?
Regards

hI,
You maintain the customization data in following path as metioned below
SPRO>Logistics General>Tax On Goods Movements>India>Basic Settings>Maintain Company Code settings
1.Company Code - your company code
2.Cenvat Document Type - ED
3.Utl FI Document Type - ED
4.Select check box Debit account override
5.Select Automatic Balance adjustment indicator check box
6.Select Immediate credit on capital goods check box
7.Select First Month as April
8.Excise selection days 30
9.No of Excise Invoices 10
10.Excise Invoice Selection procedure FICO or LIFO as per client requirement
11.Select Rounding duty on procurement
12.Select Rounding duty on removal
13.Excise rate for CVD - M
14.Exchange rate type for exports - M
15.CVD Account - Assign your CVD account
this will solve your problem.
bye
Sridhar Thota
We get the error as below while doing MIRO.
'Customization for GM1 j_1iindcus missing in table'
How do we proceed?

Error while posting MIRO

Hi Experts
I got a error like this while posting MIRO
"No amount authorization for customers/vendors in company code 401"
I tried to look out in T043 Table,since i cant able to go further
Let me know the reason for this error and the settings to do
Regards
Amuthan M

Hi,
While creating tolerance group you are specified the authorization group/ Just delete the name of the group you have created and keep it blank OR assign the user to that group and save.
Note:
If you create tolerance groups then the group must be assigned to the users in t.code:OB57 who are posting the transaction. Defining and assigning the tolerance groups to employees is not going to solve, you have to enter the amount ranges of tolerance for G/L document, Customer and Vendor posting.
In t.code:OBA4 create an entry for your company code. (Group creation is not compulsory). If your requirement permits better keep the group column empty. when no group is created its for all users.Double click on company code and enter upper limits and permitted payment differences and save.In t.code:OBA3 enter the ranges for payment differences and any other columns as per your requirement..
Regards,
Biju K

Error while posting MIRO document

Dear All
When i try to post the invoice through MIRO transactions, i get short dump. I am posting this invoice with 3 decimals for example 1.235
Overflow during the arithmetical operation (type P) in program "SAPLFDMM".
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_ARITHMETIC_OVERFLOW', was not
caught in
procedure "DETERMINE_AMOUNTS" "(FORM)", nor was it propagated by a RAISING
clause.
If you have access to the SAP notes system first try searching with the
following keywords:
"COMPUTE_BCD_OVERFLOW"
"BCD_FIELD_OVERFLOW" (Until release 4.0a, this runtime error occurred at this
position)
"SAPLFDMM" or "LFDMMF00"
"DETERMINE_AMOUNTS"
Please help..

Hi,
Try Changing the settings for the following
System --> User Profile --> Own Data --> Maintain User Profile
In the defaults tab change the Decimal Notation and then do the MIRO transaction.
I remember similar kind of dump which we were getting and it got resolved by changing the Default Decimal Notation..
Just try for remaining values of the decimal notations and execute the MIRO transaction..
Just try this...
Regards
Sindo Ouspeh

Error while posting MIRO - PO is changed

Dear Guru's
I am getting an error message
PO is changed
Message no. ZFI_INWARD_REG026
while posting the invoice using Miro ..
I know this custom message But how to debug /clear this error message. I do checked in the OMRM - Error message is not maintained in that.
guide me to solve this..
Regards
Anandh

Hi
I have found the error message under Enhancement - Classic BADI (impl) - IF_EX_INVOICE_UPDATE~CHANGE_BEFORE_UPDATE method
IF wa_ti_mrmrseg-ebeln IS NOT INITIAL.
    IF wa_ti_mrmrseg-ebeln NE wa_inward_reg_no-po_number.
      MESSAGE e026(zfi_inward_reg).
    ENDIF.
ENDIF.
--- How to find the reason for triggering this message and how to resolve this issue.
regards
anand

Error in posting MIRO Invoice after downpayment made to vendor

Dear Experts,
I got the below errror message when i post the MIRO with Refernce to PO. Please help me to resolve the same.
Bank line items are only permitted in one FI document
Message no. FI240
Diagnosis
You have entered more than one bank line item or bank clearing line item but only one expense or revenue line item in a document. This document cannot be converted to a payment online in Funds Management as the corresponding bank accounts are in different accounting documents.
Procedure
Split the posting between several documents so that the used bank lines can be posted in one accounting document. (For example, in the case of cross company codes, use only the bank accounts of just one company code).
System Response
Procedure
Regards
Anil

Dear Prakash,
Thank you for your reply.
Below is the error message.
Bank line items are only permitted in one FI document
Message no. FI240
Diagnosis
You have entered more than one bank line item or bank clearing line item but only one expense or revenue line item in a document. This document cannot be converted to a payment online in Funds Management as the corresponding bank accounts are in different accounting documents.
Procedure
Split the posting between several documents so that the used bank lines can be posted in one accounting document. (For example, in the case of cross company codes, use only the bank accounts of just one company code).
System Response
Procedure

Error message in MIRO entry: Message no M8285

During the Invoice verification entry (MIRO), for a USD invoice (Company code currency is INR), I am getting the following error message "Balance in USD Currency Type 10" Message no M8285
The document is successfully getting stimulated in USD currency but when attempted to post, this message is displayed
During invoice entry, the system is taking the exchange rate maintained in OB08 for the posting date. Any clue to the cause of the problem?

HI,
search SAPNET notes using "MIRO" and "M8285" as search terms. There are some notes, check especially 1319322.
Best regards, Christian

ABAP RUNTIME ERROR WHILE DOING MIRO

Runtime Errors                                                       MESSAGE_TYPE_X
Date and Time                                                       23.02.2011                    17:07:24
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).
     What can you do?
               Note down which actions and inputs caused the error.
               To process the problem further, contact you SAP system
               administrator.
               Using Transaction ST22 for ABAP Dump Analysis, you can look
               at and manage termination messages, and you can also
               keep them for a long time.
     Error analysis
               Short text of error message:
               Error creating the document in Profitability Analysis
               Long text of error message:
                Diagnosis
                    An error was found while the system was processing the FI/CO
                    document in Profitability Analysis.
                System Response
                    The document cannot be processed any further.
                Procedure
                    Contact your system administrator.
               Technical information about the message:
               Message class....... "KE"
               Number.............. 476
               Variable 1.......... " "
               Variable 2.......... " "
               Variable 3.......... " "
               Variable 4.......... " "
     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:
               MESSAGE_TYPE_X " "
               RK2RF001 or "RKEVRK2R_FIX"
               MOVE_VALUE_FIELDS_FI
               If you cannot solve the problem yourself and want to send an error
               notification to SAP, include the following information:
               1. The description of the current problem (short dump)
                  To save the description, choose "System->List->Save->Local File
               (Unconverted)".
               2. Corresponding system log
                  Display the system log by calling transaction SM21.
                  Restrict the time interval to 10 minutes before and five minutes
               after the short dump. Then choose "System->List->Save->Local File
               (Unconverted)".
               3. If the problem occurs in a problem of your own or a modified SAP
               program: The source code of the program
                  In the editor, choose "Utilities->More
               Utilities->Upload/Download->Download".
               4. Details about the conditions under which the error occurred or which
               actions and input led to the error.
System environment
               SAP-Release 701
               Application server... "FPELECCPRD"
               Network address...... "192.168.0.24"
               Operating system..... "Windows NT"
               Release.............. "6.0"
               Hardware type........ "16x AMD64 Level"
               Character length.... 16 Bits
               Pointer length....... 64 Bits
               Work process number.. 1
               Shortdump setting.... "full"
               Database server... "FPELECCPRD\FTP"
               Database type..... "MSSQL"
               Database name..... "FTP"
               Database user ID.. "ftp"
               Terminal.......... "PUNE143"
               Char.set.... "C"
               SAP kernel....... 701
               created (date)... "Feb 24 2009 23:27:20"
               create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
               Database version. "SQL_Server_8.00 "
               Patch level. 32
               Patch text.. " "
               Database............. "MSSQL 9.00.2047 or higher"
               SAP database version. 701
               Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
                NT 6.0"
               Memory consumption
               Roll.... 16192
               EM...... 29328880
               Heap.... 0
               Page.... 221184
               MM Used. 20281392
               MM Free. 664288
     User and Transaction
               Client.............. 900
               User................ "FABUPLO"
               Language key........ "E"
               Transaction......... "MIRO "
               Transactions ID..... "1C413FE0E2E7F1C88D54E61F1346F073"
               Program............. "RK2RF001"
               Screen.............. "SAPLMR1M 6000"
               Screen line......... 34
     Information on where terminated
               Termination occurred in the ABAP program "RK2RF001" - in
                "MOVE_VALUE_FIELDS_FI".
               The main program was "SAPLMR1M ".
               In the source code you have the termination point in line 2749
               of the (Include) program "RKEVRK2R_FIX".

Hi
Normally what we understand is we should not have a COPA doc in case of MIRO unless and untill one has got the Purchase Price Variance in the entry and for the same the OKB9 setting has been made while the GL account either doesnot have cost element for the period or the PA structure is not complete.
The above can be the probable reason for the dump. I hope if you try to investigate the problem on the above line you will find out the solution to the problem
regards
Debashis

Account dertermination error while doing MIRO for third party PO

Hello,
This is regarding error message while doing MIRO (IR)
There is already a PO in the system with item category S ( Third Party ) &
Acc assignment object u2013 C (Sales order).
For this PO , I could find 10 invoices already posted in the system.
Between when these invoices were posted , there were some changes done to the PO.
But even after those changes , many invoices were posted in the system,
But now , when I try to post the invoice , I am getting the below error message.
the error message is ** Account determination for entry SKPL WRX 0002 _ 1020 not possible** while posting.
Message no. M8147
Diagnosis
The system did not find an account for this transaction. This means that the account determination for key SKPL WRX 0002 _ 1020 is not maintained in MM Customizing (Valuation). The key is made up of:
u2022 Chart of account
u2022 Transaction key (= Posting transaction)
u2022 Valuation grouping code
u2022 Account grouping code
u2022 Valuation class
System Response
The system cannot update a G/L account for this transaction. You cannot post the transaction.
Procedure
Contact your system administrator.
If you have the authorization, check the Account determination in Customizing for Valuation.
Proceed
Note
The relevant posting transaction can be found in Table T030A.
I have checked the entry in OMWD, where valuation grouping code is maintained against the valuation area & company code.
PLEASE SUGGEST ME SOME SOLUTION.
Thanks,
Vinoth

Hi Raman,
Yes, still i am getting error.
before when the invoice is posted , there is no error.
there are some 10 invoices posted already , but there are some changes done in the PO , after that they could post two invoices but for the third invoice , i am getting this error.
when the invoive is posted without error , these are the account movements that are hit
Here
441510 is a vendor account
61799410 is a WBS element G/L account
27411000 is a G/L for tax.
What could have pulled out this WRX error (Account determination for entry SKPL WRX 0002 _1020 not possible ) for me????
can u suggest me some solutions.
Thanks,
Vinoth

Error while doing miro of network purchase order ( no funds center entered/

Hi,
we are facing one problem while doing miro of network service purchase order. System is giving message 'No funds center entered/derived in item 00030'.
We have activated funds management in Jul'10. The said network service PO belong to previous year. Also we have changed
commitment item of GL account related to concerned service order in Jul'10 & posted GRN one in apr'10 & one aug'10.
System is not allowing to cancel the service entry sheet.
Can anybody help on this.
regards
abhishek

we had activated the trace facility for FMDEIRIVE & found that all FC/Commitment item derived correctly. But while posting the document it is throwing an error.
Regards
Abhishek

Error while doing MIRO-Overflow for arithmetical operation (type P) in prog

Hi ,
I am getting the error while doing the MIRO as below-
Runtime Errors         COMPUTE_BCD_OVERFLOW
Exception              CX_SY_ARITHMETIC_OVERFLOW
Date and Time          20.05.2009 10:07:03
Short text
     Overflow during the arithmetical operation (type P) in program "SAPLMRMC".
What happened?
     Error in the ABAP Application Program
     The current ABAP program "SAPLMRMC" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
What can you do?
     Note down which actions and inputs caused the error.
     To process the problem further, contact you SAP system
     administrator.
     Using Transaction ST22 for ABAP Dump Analysis, you can look
     at and manage termination messages, and you can also
     keep them for a long time.
Error analysis
     An exception occurred that is explained in detail below.
     The exception, which is assigned to class 'CX_SY_ARITHMETIC_OVERFLOW', was not
      caught in
     procedure "MRM_AMOUNT_QUANTITY_PROPOSE" "(FUNCTION)", nor was it propagated by
      a RAISING clause.
     Since the caller of the procedure could not have anticipated that the
Please let me know how can this be removed.

Hi,
There can be some problem with tolerances set in the customizing.
In my case, I was getting this error because of delivery date variance. The difference between delivery date maintained in PO and invoice date was huge and hence the multiplication of price of PO and difference of delivery date was huge and that was the reason for error.
Similarly in your case also, there will be some tolerance limit problem.
Please check your tolerance limits set in customizing.
Regards,
Mihir Popat

Error in Duty MIRO(Urgent)

Similar Messages

Maybe you are looking for