Runtime Error  CONVT_OVERFLOW in MIGO

Hi,
We have this issue:
When we try to do a Good Receipt for a particular material,  the good receipt is posted, but the system show this message: Runtime Error  CONVT_OVERFLOW  (Overflow when converting from "2.1252e+09") and the good receipt can not be displayed.
This material has a price (VEF 64.400,00) and the material quantity has not decimals (for example: 1,00).
When we changed the price in the purchase order (for example: VEF 10,00) the good receipt was posted and the good receipt can be displayed.
Would you please help us with this situation?
Best Regards,
Marielita

Hi Mariela,
Please refer the below notes
SAP Note No. 192057  CONVT_OVERFLOW in MB_UPDATE_MATERIAL_VALUES  <<<<<<<<<<<<<
SAP Note No. 831197>> Dump CONVT_OVERFLOW in goods movements with ML
SAP Note No. 192057 Should solve your issue .
Rgs
SB

Similar Messages

  • Runtime Errors: CONVT_OVERFLOW while executing transaction sm66

    Hello Everyone,
    There are two Application serevrs out of which I am getting the following error while executing transaction SM66 only in one i.eCI server but if i remote login to other system and try SM66 its working fine.
    Please suggest
    Runtime Errors         CONVT_OVERFLOW
    Exception              CX_SY_CONVERSION_OVERFLOW
    Date and Time          02.04.2011 00:41:01
    Short text
         Overflow when converting from "2.90113e+09"
    Error analysis
         An exception occurred that is explained in detail below.
         The exception, which is assigned to class 'CX_SY_CONVERSION_OVERFLOW', was not
          caught in
         procedure "TH_WP_DETAIL_INFO" "(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:
         When attempting to convert the value "2.90113e+09",
         an overflow occurred.
         There is probably an error in the program
         "SAPLTHFB".
    How to correct the error
         Probably the only way to eliminate the error is to correct the program.
         You may able to find an interim solution to the problem
         in the SAP note system. If you have access to the note system yourself,
         please use the following search criteria:
         "SAPLTHFB" "CONVT_OVERFLOW"
    If you cannot solve the problem yourself, please send the
    following documents to SAP:
    1. A hard copy print describing the problem.
        To obtain this, select the "Print" function on the current screen.
    2. A suitable hardcopy prinout of the system log.
        To obtain this, call the system log with Transaction SM21
        and select the "Print" function to print out the relevant
        part.
    3. If the programs are your own programs or modified SAP programs,
        supply the source code.
        To do this, you can either use the "PRINT" command in the editor or
        print the programs using the report RSINCL00.
    4. Details regarding 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
    "TH_WP_DETAIL_INFO" "(FUNCTION)", or its possible occurrence must be declared
      in the
    RAISING clause of the procedure.
    To prevent the exception, note the following:
    tem environment
    SAP-Release 700
    Application server... "POSDMCI"
    Network address...... ""
    Operating system..... "SunOS"
    Release.............. "5.10"
    Hardware type........ "sun4u"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 1
    Shortdump setting.... "full"
    Database server... "POSDMDB"
    Database type..... "ORACLE"
    Database name..... "BP2"
    Database user ID.. "SAPSR3"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Apr 2 2006 21:14:52"
    create on........ "SunOS 5.9 Generic_117171-13
    Database version. "OCI_101 "
    Patch level. 52
    Patch text.. " "
    Database............. "ORACLE 9.2.0.., ORACLE
    SAP database version. 700
    Operating system..... "SunOS 5.9, SunOS 5.10"
    Memory consumption
    Roll.... 16192
    EM...... 8379696
    Heap.... 0
    Page.... 40960
    MM Used. 720912
    MM Free. 3466336
    Information on where terminated
        Termination occurred in the ABAP program "SAPLTHFB" - in "TH_WP_DETAIL_INFO".
        The main program was "SAPMSM66 ".
        In the source code you have the termination point in line 82
        of the (Include) program "LTHFBU26".
        The termination is caused because exception "CX_SY_CONVERSION_OVERFLOW"
         occurred in
        procedure "TH_WP_DETAIL_INFO" "(FUNCTION)", but it was neither handled locally
         nor declared
        in the RAISING clause of its signature.
        The procedure is in program "SAPLTHFB "; its source code begins in line
        1 of the (Include program "LTHFBU26 ".

    Hello Everyone,
    There are two Application serevrs out of which I am getting the following error while executing transaction SM66 only in one i.eCI server but if i remote login to other system and try SM66 its working fine.
    Please suggest
    Runtime Errors         CONVT_OVERFLOW
    Exception              CX_SY_CONVERSION_OVERFLOW
    Date and Time          02.04.2011 00:41:01
    Short text
         Overflow when converting from "2.90113e+09"
    Error analysis
         An exception occurred that is explained in detail below.
         The exception, which is assigned to class 'CX_SY_CONVERSION_OVERFLOW', was not
          caught in
         procedure "TH_WP_DETAIL_INFO" "(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:
         When attempting to convert the value "2.90113e+09",
         an overflow occurred.
         There is probably an error in the program
         "SAPLTHFB".
    How to correct the error
         Probably the only way to eliminate the error is to correct the program.
         You may able to find an interim solution to the problem
         in the SAP note system. If you have access to the note system yourself,
         please use the following search criteria:
         "SAPLTHFB" "CONVT_OVERFLOW"
    If you cannot solve the problem yourself, please send the
    following documents to SAP:
    1. A hard copy print describing the problem.
        To obtain this, select the "Print" function on the current screen.
    2. A suitable hardcopy prinout of the system log.
        To obtain this, call the system log with Transaction SM21
        and select the "Print" function to print out the relevant
        part.
    3. If the programs are your own programs or modified SAP programs,
        supply the source code.
        To do this, you can either use the "PRINT" command in the editor or
        print the programs using the report RSINCL00.
    4. Details regarding 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
    "TH_WP_DETAIL_INFO" "(FUNCTION)", or its possible occurrence must be declared
      in the
    RAISING clause of the procedure.
    To prevent the exception, note the following:
    tem environment
    SAP-Release 700
    Application server... "POSDMCI"
    Network address...... ""
    Operating system..... "SunOS"
    Release.............. "5.10"
    Hardware type........ "sun4u"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 1
    Shortdump setting.... "full"
    Database server... "POSDMDB"
    Database type..... "ORACLE"
    Database name..... "BP2"
    Database user ID.. "SAPSR3"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Apr 2 2006 21:14:52"
    create on........ "SunOS 5.9 Generic_117171-13
    Database version. "OCI_101 "
    Patch level. 52
    Patch text.. " "
    Database............. "ORACLE 9.2.0.., ORACLE
    SAP database version. 700
    Operating system..... "SunOS 5.9, SunOS 5.10"
    Memory consumption
    Roll.... 16192
    EM...... 8379696
    Heap.... 0
    Page.... 40960
    MM Used. 720912
    MM Free. 3466336
    Information on where terminated
        Termination occurred in the ABAP program "SAPLTHFB" - in "TH_WP_DETAIL_INFO".
        The main program was "SAPMSM66 ".
        In the source code you have the termination point in line 82
        of the (Include) program "LTHFBU26".
        The termination is caused because exception "CX_SY_CONVERSION_OVERFLOW"
         occurred in
        procedure "TH_WP_DETAIL_INFO" "(FUNCTION)", but it was neither handled locally
         nor declared
        in the RAISING clause of its signature.
        The procedure is in program "SAPLTHFB "; its source code begins in line
        1 of the (Include program "LTHFBU26 ".

  • Runtime error SAPSQL_ARRAY_INSERT_DUPREC  during migo

    Hi Friends,
    When I try doing MIGO with reference to a PO and save the document it gives me runtime error SAPSQL_ARRAY_INSERT_DUPREC.
    I have check the buffer, and the no. range everything is perfect, but still i am getting this error.
    Can anyone please give me the possible solution for this. Is there any SAP note that I need to apply.
    Regards,
    Wasim.

    Hello Wasim,
    The common cause of this termination is the material document             
    number range as per note 31793 - SAPSQL_ARRAY_INSERT_DUPREC.                                                                               
    So please check if the current numbers are synchronized with the          
    database tables:                                                                               
    OMBT trx x MKPF table                                                     
    OMH6 trx x EKKO table                                                                               
    If it has the same number range the sort dump should not be raised        
    anymore.                                                                               
    The main root causes are:                                                 
    -> when you are transporting number ranges from one client to another;                                                                               
    -> when you face a shut down in your system and you have defined a        
    buffer application server tolerance in transaction SNRO;                                                                               
    -> when you are doing the posting by using BAPI's and for some reason     
    the BAPI failed.                                                                               
    I hope it helps you.                                                      
    Best Regards,
    Fábio Almeida
    MM Consultant

  • Runtime Error SYNTAX_ERROR with MIGO tcode

    Hi Gurus,
    I got a new issue now. while executing MIGO tcode getting SYNTAX_ERROR dump, please check below dump details..
    Category               ABAP Programming Error
    Runtime Errors         SYNTAX_ERROR
    ABAP Program           SAPLVBDOCUBATCH_DM
    Application Component  LO-BM
    Date and Time          09.01.2012 16:27:51
    What happened?
        Error in the ABAP Application Program
        The current ABAP program "SAPLMIGO" had to be terminated because it has
        come across a statement that unfortunately cannot be executed.
        The following syntax error occurred in program "SAPLVBDOCUBATCH_DM " in include
         "LVBDOCUBATCH_DM$39 " in
        line 8:
        ""RL034" must be a flat structure. You cannot use internal tables, stri"
        "ngs, references, or structures as components."
        The include has been created and last changed by:
        Created by: "SAP "
        Last changed by: "SAP "
        Error in the ABAP Application Program
        The current ABAP program "SAPLMIGO" had to be terminated because it has
        come across a statement that unfortunately cannot be executed.
    Error analysis
        The following syntax error was found in the program SAPLVBDOCUBATCH_DM :
        ""RL034" must be a flat structure. You cannot use internal tables, stri"
        "ngs, references, or structures as components."
    i have tried to check syntax of program SAPLVBDOCUBATCH_DM and it is giving error, please help me solve this issue.
    Additional Information:ECC6.0 EHP5(recently upgraded from ECC6.0) nd DB:Oracle 10.2.0.2 OS:windows
    Thanks,
    Venkat

    Hello Team,
    This is Solved..
    As per dump when we go n check table RL034 through SE11 there one Object type is wrong so with Abaper help it got corrected then the problem was solved.
    Thanks all for your time.
    Venkat

  • GETTING RUNTIME ERROR POSITNG GR-MIGO

    Dear All,
    While Posting GR thru MIGO, we'r getting short fump while posting the transaction after check made.
    Pls advise what happened exactly and how to fix this......
    We'r getting this error/short dump only from today and wants to know whether its getting affected by any patches implemented by Basis consultant.
    FYR
    The below description displaying in Runtime error while posting GR-MIGO after check completed OK.
    Short Text
    Syntax error in program "SAPLFAGL_MIG_OPITEMS ".
    What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLGLIN" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program "SAPLFAGL_MIG_OPITEMS " in
    include "LFAGL_MIG_OPITEMSTOP " in
    line 42:
    "The type "FAGL_MIG_BELNR_DOCNR" is unknown."
    The include has been created and last changed by:
    Created by: "SAP "
    Last changed by: "BS1SUDHA "
    Error in the ABAP Application Program
    The current ABAP program "SAPLGLIN" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    Error analysis
    The following syntax error was found in the program SAPLFAGL_MIG_OPITEMS :
    "The type "FAGL_MIG_BELNR_DOCNR" is unknown."
    Trigger Location of Runtime Error
    Program SAPLGLIN
    Include LGLINF90
    Row 3,340
    Module type (FORM)
    Module Name SET_DOCNR
    Source Code Extract
    Line SourceCde
    3310 MOVE BEL_TAB-REFACTIVITY TO BEL_ST-REFACTIV.
    3311 MOVE-CORRESPONDING BEL_ST TO TAB_FAGLFLEXA .
    3312 IF T881-GLFLEX = '1'.
    3313 MOVE BEL_TAB-DOCNR_GLFLEX TO TAB_FAGLFLEXA-DOCNR.
    3314 ENDIF.
    3315 MODIFY TAB_FAGLFLEXA .
    3316 ELSE.
    3317 CLEAR BEL_TAB.
    3318 LOOP AT BEL_TAB WHERE BUKRS = TAB_FAGLFLEXA_ADD-BUCHKREIS
    3319 AND ACTIVITY = TAB_FAGLFLEXA-ACTIV
    3320 AND DOCNRVORL = TAB_FAGLFLEXA-DOCNR.
    3321 IF T881-GLFLEX = '1'.
    3322 IF UF-INTERFACE = GC_AC_INTERFACE.
    3323 CHECK BEL_TAB-RLDNR = TAB_FAGLFLEXA-RLDNR.
    3324 ENDIF.
    3325 CHECK NOT BEL_TAB-DOCNR_GLFLEX IS INITIAL.
    3326 ELSE.
    3327 CHECK NOT BEL_TAB-DOCNR IS INITIAL.
    3328 ENDIF.
    3329 MOVE-CORRESPONDING BEL_TAB TO BEL_ST.
    3330 MOVE BEL_TAB-REFACTIVITY TO BEL_ST-REFACTIV.
    3331 MOVE-CORRESPONDING BEL_ST TO TAB_FAGLFLEXA .
    3332 IF T881-GLFLEX = '1'.
    3333 MOVE BEL_TAB-DOCNR_GLFLEX TO TAB_FAGLFLEXA-DOCNR.
    3334 ENDIF.
    3335 MODIFY TAB_FAGLFLEXA .
    3336 EXIT.
    3337 ENDLOOP.
    3338 ENDIF.
    3339 IF NOT TAB_FAGLFLEXA_ADD-GLSIP IS INITIAL.
    CALL FUNCTION 'FAGL_MIG_GET_DOCNR'
    3341 EXPORTING
    3342 iv_rldnr = TAB_FAGLFLEXA-rldnr
    3343 iv_bukrs = TAB_FAGLFLEXA-rbukrs
    3344 iv_gjahr = TAB_FAGLFLEXA-gjahr
    3345 iv_belnr = TAB_FAGLFLEXA-belnr
    3346 iv_buzei = TAB_FAGLFLEXA-buzei
    3347 IMPORTING
    3348 ev_docln = TAB_FAGLFLEXA-docln.
    3349 MODIFY TAB_FAGLFLEXA .
    3350 ENDIF.
    3351 ENDLOOP.

    Hi Babu
    Please check in SM12 what is the cause and probably you have to take this to an good ABAPER.
    regards
    Yogesh

  • Getting ABAP runtime error while doing MIGO-GR against PO.

    Hi,
    Getting ABAP runtime error message while doing GR against PO.
    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 pointers
    Code Formatted by: Alvaro Tejada Galindo on Jan 14, 2010 6:00 PM

    Hi ,
    Any inputs
    for this error
    No RFC destination is defined for SAP Global Trade Services
    Regards
    Ashu

  • Run time error CONVT_OVERFLOW

    dear Sir
    we have window 7 for new oc as soon runned teh program cv01n i got run time error msg  CX_SY_CONVERSION_OVERFLOW,plese guide
    Runtime Errors         CONVT_OVERFLOW                                                              
    Except.                CX_SY_CONVERSION_OVERFLOW                                                   
    Date and Time          03.05.2010 14:26:31                                                                               
    Short text                                                                               
    Overflow when converting from "-1"                                                           
    What happened?                                                                               
    Error in the ABAP Application Program                                                                               
    The current ABAP program "SAPLCV120" 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_CONVERSION_OVERFLOW', was not               
         caught in                                                                               
    procedure "SYS_GET_WINDOW_SYSTEM" "(FORM)", 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:                                                             
        When attempting to convert the value "-1", an overflow occurred.                             
    How to correct the error                                                                         
        If the error occurred in your own ABAP program or in an SAP                                  
        program you modified, try to remove the error.                                                                               
    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:                                                                               
    "CONVT_OVERFLOW" "CX_SY_CONVERSION_OVERFLOW"                                                 
        "SAPLCV120" or "LCV120F28"                                                                   
        "SYS_GET_WINDOW_SYSTEM"                                                                               
    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                               
        "SYS_GET_WINDOW_SYSTEM" "(FORM)", 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... "APP2"                                                                 
        Network address...... "132.147.166.13"                                                       
        Operating system..... "Windows NT"                                                           
        Release.............. "5.2"                                                                  
        Hardware type........ "2x IA64 Level 3"                                                      
        Character length.... 16 Bits                                                                 
        Pointer length....... 64 Bits                                                                
        Work process number.. 0                                                                      
        Shortdump setting.... "full"                                                                               
    Database server... "DB"                                                                      
        Database type..... "MSSQL"                                                                   
        Database name..... "ELP"                                                                     
        Database user ID.. "elp"                                                                               
    Char.set.... "C"                                                                               
    SAP kernel....... 700                                                                        
        created (date)... "Aug 23 2009 22:38:30"                                                     
        create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"                             
        Database version. "SQL_Server_8.00 "                                                                               
    Patch level. 221                                                                               
    Patch text.. " "                                                                               
    Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"                             
        SAP database version. 700                                                                    
        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.... 655360                                                                               
    MM Used. 3095760                                                                               
    MM Free. 1091456                                                                               
    User and Transaction                                                                               
    Client.............. 900                                                                     
        User................ "CPTN_SAPC5"                                                            
        Language key........ "E"                                                                     
        Transaction......... "CV03N "                                                                
        Transactions ID..... "C29156DF1F2DF180BE040017A4AB426D"                                                                               
    Program............. "SAPLCV120"                                                             
        Screen.............. "SAPLCV110 0101"                                                        
        Screen line......... 3  
    regards
    kunal

    Hi Kunal,
    you can display both type of document 2003 and 2007 also. You need to configure these applications in define workstation application by using t-code DC30.
    then you can display these files.
    Regards,
    Ravindra

  • GETWA_NOT_ASSIGNED - Runtime Error in MIGO

    Dear All
    I am receiving GETWA_NOT_ASSIGNED - Runtime Error in MIGO transaction for a particular user only in production system. I am not able to narrow down is this transaction specific or user issue.  I searched the forum and not able to get reason.  If someone knows about ths kindly give me a hint.
    Regards,
    Venkat

    Hi,
    Please check if any User Exit BADI implemented and have a look into below thread
    Reg Dump in MIGO Transaction
    GETWA_NOT_ASSIGNED run time error_MIGO processing stock transport order
    Shiva

  • Runtime Error in MIGO after upgrade from 4.6c to ECC 6.0

    hi,
        We are doing a upgrade project from 4.6c to ECC 6.0 and when we are posting the MIGO a runtime error is occuring from the method
    "IF_EX_MB_DOCUMENT_BADI~MB_DOCUMENT_BEFORE_UPDATE" which is
    in the class "ZCL_IM_MMIM_STK_TRANSFER".
    The error is as follows :
    method IF_EX_MB_DOCUMENT_BADI~MB_DOCUMENT_BEFORE_UPDATE
    >>>>>CALL FUNCTION 'Z_MM_STK_TSFR'  
    TABLES     
    T_XMKPF = XMKPF
    T_XMSEG = XMSEG.  
    END METHOD.
    the errror is showing at function  'Z_MM_STK_TSFR'   .
    I would be happy if anyone could give any inputs i hav also put chek in unicode in attributes in main program however still the error is arising.
    thanks in advance

    hi,
         thanks for the inputs i have done the syntax check on the main program and the FM the error which is coming is Field "ENJPREVIEW" is unknown. its neither in one of the specified tables nor defined by a DATA 'statement' . THis error is showing in the include LMEDRUCKF1K.
    Thanks in advance

  • Runtime error in MIGO for subcontracting order

    Hi All
    We have an issue in subcontracting process. We are trying to complete goods receipt for the multiple line items for subcontracting PO.
    These multiple line item contains serialized materials. When we are trying to complete the GR, We are getting runtime error saying u201COnly 0 serial numbers entered instead of 1u201D
    Any pointers in resolving this issue will be a great help to us.

    Mohandevegowda wrote:
    Hi All

    > We have an issue in subcontracting process. We are trying to complete goods receipt for the multiple line items for subcontracting PO.

    > These multiple line item contains serialized materials. When we are trying to complete the GR, We are getting runtime error saying u201COnly 0 serial numbers entered instead of 1u201D

    > Any pointers in resolving this issue will be a great help to us.
    Hi,
    Pls check whether you have maintained the serial no for the material in mm01 tcode. When it comes to subcontracting process you will create a BOM by listing all your materials but when you take GR from subcontractor after some action is performed on that list of materials then definitely you have to manually give the serial no in MIGO or check automatic serial no there.you might have not placed anything over there.
    Thanks

  • Migo runtime error

    i got a purchase order ,than i go to migo posting,
    enter apurchase order and plant
    press enterkey , select item Ok check box
    document is ok, but material item green symbol
    than post document ,error is runtime error
    this regards
    janaki

    Hi,
    Check the Dump details with your Basis/ABAP person.
    The will be able to identify the issue and help you to resolve
    Regards
    Merwyn

  • Help me Please !!!! Runtime errors         DBIF_RSQL_SQL_ERROR      alway

    Hi guru's,
    I have a genric data source with function module which feeds data to a genric ods in bw.
    But at time of data upload i see quality status in manage of ods green saying (0 of 0 records extracted) but it asks me to check dump in st22 which is as follows
    Runtime Errors         DBIF_RSQL_SQL_ERROR
    Exception              CX_SY_OPEN_SQL_DB
           Occurred on     30.01.2008 at 10:41:31
    An SQL error occurred when accessing a table.
    What happened?
    What can you do?
    Make a note of the actions and input which caused the error.
    To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
    termination messages, especially those beyond their normal deletion
    date.
    Error analysis
    An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
    neither
    caught nor passed along using a RAISING clause, in the procedure
    "STORAGE_LOC_GET" "(METHOD)"
    Since the caller of the procedure could not have expected this exception
    to occur, the running program was terminated.
    The reason for the exception is:
    How to correct the error
    The exception must either be prevented, caught within the procedure
    "STORAGE_LOC_GET"
    "(METHOD)", or declared in the procedure's RAISING clause.
    To prevent the exception, note the following:
    Database error text........: "ORA-04030: out of process memory when trying to
    allocate 1332 bytes (callheap,qkkele)"
    Internal call code.........: "[RSQL/READ/T001L ]"
    Please check the entries in the system log (Transaction SM21).
    You may able to find an interim solution to the problem
    in the SAP note system. If you have access to the note system yourself,
    use the following search criteria:
    "DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC
    "SAPLMIGO" or "########################################"
    "STORAGE_LOC_GET"
    If you cannot solve the problem yourself, please send the
    following documents to SAP:
    1. A hard copy print describing the problem.
       To obtain this, select the "Print" function on the current screen.
    2. A suitable hardcopy prinout of the system log.
       To obtain this, call the system log with Transaction SM21
       and select the "Print" function to print out the relevant
       part.
    3. If the programs are your own programs or modified SAP programs,
       supply the source code.
       To do this, you can either use the "PRINT" command in the editor or
       print the programs using the report RSINCL00.
    4. Details regarding the conditions under which the error occurred
       or which actions and input led to the error.
    System environment
    SAP Release.............. "620"
    Application server....... "TOGR3PRD1"
    Network address.......... "10.1.9.9"
    Operating system......... "Windows NT"
    Release.................. "5.2"
    Hardware type............ "8x Intel 801586"
    Character length......... 8 Bits
    Pointer length........... 32 Bits
    Work process number...... 1
    Short dump setting....... "full"
    Database server.......... "TOGR3PRD2"
    Database type............ "ORACLE"
    Database name............ "PRD"
    Database owner........... "SAPPRD"
    Character set............ "Thai_Thailand.874"
    SAP kernel............... "640"
    Created on............... "Sep 19 2005 00:05:54"
    Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
    Database version......... "OCI_920_SHARE "
    Patch level.............. "91"
    Patch text............... " "
    Supported environment....
    Database................. "ORACLE 8.1.7.., ORACLE 9.2.0.., ORACLE
    10.1.0.."
    SAP database version..... "640"
    Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
    User, transaction...
    Client.............. 900
    User................ 0060302
    Language key........ "E"
    Transaction......... "MIGO "
    Program............. "SAPLMIGO"
    Screen.............. "SAPLMIGO 0001"
    Screen line......... 15
    Information on where terminated
    The termination occurred in the ABAP program "SAPLMIGO" in "STORAGE_LOC_GET".
    The main program was "SAPLMIGO ".
    The termination occurred in line 0 of the source code of the (Include)
    program "########################################"
    of the source code of program "########################################" (when
    calling the editor 00).
    Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
    the
    procedure "STORAGE_LOC_GET" "(METHOD)" but was not handled locally, not
    declared in the
    RAISING clause of the procedure.
    The procedure is in the program "SAPLMIGO ". Its source code starts in line 158
    of the (Include) program "LMIGOBU2 ".
    Contents of system fields
    SY field contents..................... SY field contents.....................
    SY-SUBRC 4                             SY-INDEX 1
    SY-TABIX 0                             SY-DBCNT 1
    SY-FDPOS 1                             SY-LSIND 0
    SY-PAGNO 1                             SY-LINNO 1
    SY-COLNO 1                             SY-PFKEY MIGO_STATUS
    SY-UCOMM MIGO_OK_TAKE_VALUE
    SY-TITLE Goods Issue Others - 0060302 &#3627;&#3609;.&#3649;&#3612;&#3609;&#3585;&#3649;&#3621;&#3632;&#3592;&#3609;&#3607;.&#3588;&#3621;&#3633;&#3591;&#3626;&#3636;&#3609;&#3588;&#3657;&#3634;,&#3588;&#3621;
    SY-MSGTY E                             SY-MSGID MICK
    SY-MSGNO 004                           SY-MSGV1
    SY-MSGV2                               SY-MSGV3
    SY-MSGV4
    Active calls / events
    No.... Type........ Name..........................
           Program
           Include                                  Line
           Class
         7 METHOD       STORAGE_LOC_GET
           SAPLMIGO
           LMIGOBU2                                   173
           LCL_MIGO_BUFFER
         6 METHOD       LINE_CHECK
           SAPLMIGO
           LMIGOKL4                                   217
           LCL_MIGO_KERNEL
         5 METHOD       LINE_MODIFY
           SAPLMIGO
           LMIGOKL1                                   123
           LCL_MIGO_KERNEL
         4 METHOD       VALUECOPY
           SAPLMIGO
           LMIGOTV3                                   370
           LCL_MIGO_TABLEVIEW
         3 METHOD       LIF_MIGO_FRAME~OKCODE_HANDLER
           SAPLMIGO
           LMIGOTV2                                   174
           LCL_MIGO_TABLEVIEW
         2 METHOD       OKCODE_DISPATCH
           SAPLMIGO
           LMIGOFR2                                   171
           LCL_MIGO_FRAME
         1 MODULE (PAI) PAI_OKCODE_DISPATCH
           SAPLMIGO
           LMIGOPAI                                    11
    Chosen variables
         7 METHOD       STORAGE_LOC_GET
           SAPLMIGO
           LMIGOBU2                                   173
    I_PLANT
                                   2222
                                   0000
    I_STORAGE_LOC                  2031
                                   3333
                                   2031
    E_STORAGE_LOC
                                   222222222222222222
                                   000000000000000000
    %_FUN*TV_GOSPLIT               <initial>
                                   <initial>
                                   <initial>
    GOITEM-KZVBR
                                   2
                                   0
    <%_TABLE_T001L>                ???
    %_SPACE
                                   2
                                   0
    %_ARCHIVE
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... +  40
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... +  80
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... + 120
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... + 160
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... + 200
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... + 240
                                   222222222222222
                                   000000000000000
    SYST-REPID                     SAPLMIGO
                                   5454444422222222222222222222222222222222
                                   310CD97F00000000000000000000000000000000
    <%_TABLE_TQSS1>                ???
    SY-REPID                       SAPLMIGO
                                   5454444422222222222222222222222222222222
                                   310CD97F00000000000000000000000000000000
    %_DUMMY$$
                                   2222
                                   0000
    GODYNPRO-DETAIL_ZEILE          0000
                                   3333
                                   0000
    LCL_MIGO_GLOBALS=>KERNEL->S_CO WA
                                   54
                                   71
    LS_T001L
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... +  40
                                   22222222222222222222222222222
                                   00000000000000000000000000000
    OREF_DETAIL_MATERIAL          
    SY-SUBRC                       4
                                   0000
                                   4000
    GOITEM_TV                      0017
                                   3333222222222222222222222222222222222222
                                   0017000000000000000000000000000000000000
    ... +  40                                    G152 Wh F SV U65 -025 -050
                                   2222222222222243332562425525332233322333
                                   0000000000000071520780603605650D0250D050
    ... +  80                                    X#######
                                   2222222222222250000000222222222222222222
                                   000000000000008000020C000000000000000000
    ... + 120                                 4020111650-002-005          9
                                   2222222222233333333332333233322222222223
                                   000000000004020111650D002D00500000000009
    ... + 160                      03                                ######
                                   3322222222222222222222222222222222000000
                                   0300000000000000000000000000000000000000
    ... + 200                      #                                      0
                                   0222222222222222222222222222222222222223
                                   C000000000000000000000000000000000000000
    ... + 240                      000000000000000
                                   333333333333333
                                   000000000000000
    SY-XPROG                       SAPCNVE
                                   5454454222222222222222222222222222222222
                                   3103E65000000000000000000000000000000000
    %_FL1*TV_GOFREIGHT             1
                                   0000
                                   1000
    SY-XFORM                       CONVERSION_EXIT
                                   444545544454545222222222222222
                                   3FE65239FEF5894000000000000000
    %_FUN*TV_GOSERIAL              1
                                   0000
                                   1000
         6 METHOD       LINE_CHECK
           SAPLMIGO
           LMIGOKL4                                   217
    IS_OLD_GOITEM                            00000002000000000000     X
                                   2222222222333333333333333333332222252222
                                   0000000000000000020000000000000000080000
    ... +  40                         903H   - 1   1         201
                                   2223334222223222322222222233322222222222
                                   0009038000D01000100000000020100000000000
    ... +  80
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... + 120
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... + 160
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... + 200
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... + 240
                                   222222222222222
                                   000000000000000
    CS_GOITEM                                00000002000000000000     X
                                   2222222222333333333333333333332222252222
                                   0000000000000000020000000000000000080000
    ... +  40                         903H   - 1   1         201
                                   2223334222223222322222222233322222222222
                                   0009038000D01000100000000020100000000000
    ... +  80
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... + 120
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... + 160
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... + 200
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... + 240
                                   222222222222222
                                   000000000000000
    LC_BATCH_CONVERSION_ACTIVE     1
                                   3
                                   1
    LCL_MIGO_CURSOR=>VALUE         FG Rework
                                   4425676762222222222222222222222222222222
                                   670257F2B0000000000000000000000000000000
    ... +  40
                                   2222222222
                                   0000000000
    %_FL1*TV_GOSPLIT               <initial>
                                   <initial>
                                   <initial>
    LS_GOPLANT
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... +  40
                                   22222222222222222222222222222
                                   00000000000000000000000000000
    GOITEM-EXVKW                   #######
                                   0000000
                                   000000C
    ME->PS_GOHEAD+746(3)           TH
                                   542
                                   480
    LS_GOPLANT-LAND1
                                   222
                                   000
    LS_GOT001L
                                   222222222222222222
                                   000000000000000000
    SY                             ########################################
                                   0000000000000000000000000000000000000000
                                   1000100000001000000000000000000000000000
    ... +  40                      ########################################
                                   0000000000000000000000000000000000001000
                                   100010001000000010000000000000000000A000
    ... +  80                      ################<#######################
                                   0000000000000000300000000000000000000000
                                   0000000050004000C00000000000000000000000
    ... + 120                      ####################################p###
                                   0000000000000000000000000000000010007000
                                   00000000000000000000000000000000A0000000
    ... + 160                      ####<#######pb## C#############   E1   0
                                   0000300000007600240000000000000222432223
                                   0000C00000000200030030000C0000C000510000
    ... + 200                      0010001     ####D$S                 900
                                   3333333222220000425222222222222222223332
                                   0010001000001000443000000000000000009000
    ... + 240                           00
                                   222223322222222
                                   000000000000000
    OREF_HEADER_GENERAL           
    LS_GOITEM-WERKS
                                   2222
                                   0000
    LS_GOITEM-LGORT                2031
                                   3333
                                   2031
    OREF_SPLIT_QUANTITY           
    ME                            
    LS_GOITEM                                00000002000000000000     X
                                   2222222222333333333333333333332222252222
                                   0000000000000000020000000000000000080000
    ... +  40                         903H   - 1   1         201
                                   2223334222223222322222222233322222222222
                                   0009038000D01000100000000020100000000000
    ... +  80
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... + 120
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... + 160
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... + 200
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... + 240
                                   222222222222222
                                   000000000000000
         5 METHOD       LINE_MODIFY
           SAPLMIGO
           LMIGOKL1                                   123
    I_LINE                         2
                                   0000
                                   2000
    I_TABIX                        0
                                   0000
                                   0000
    I_INSERT
                                   2
                                   0
    I_FORCE_CHANGE
                                   2
                                   0
    I_AUTHORITY_CHECK
                                   2
                                   0
    I_STATUS_DELAYED               X
                                   5
                                   8
    I_DEPENDENT_TABLES
                                   2
                                   0
    IT_GOSERIAL                    Table[initial]
    IT_GOFREIGHT                   Table[initial]
    CS_GOITEM                                00000002000000000000     X
                                   2222222222333333333333333333332222252222
                                   0000000000000000020000000000000000080000
    ... +  40                         903H   - 1   1         201
                                   2223334222223222322222222233322222222222
                                   0009038000D01000100000000020100000000000
    ... +  80
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... + 120
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... + 160
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... + 200
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... + 240
                                   222222222222222
                                   000000000000000
    ME                            
    LS_OLD_GOITEM                            00000002000000000000     X
                                   2222222222333333333333333333332222252222
                                   0000000000000000020000000000000000080000
    ... +  40                         903H   - 1   1         201
                                   2223334222223222322222222233322222222222
                                   0009038000D01000100000000020100000000000
    ... +  80
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... + 120
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... + 160
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... + 200
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... + 240
                                   222222222222222
                                   000000000000000
    LS_NEW_GOITEM                            00000002000000000000     X
                                   2222222222333333333333333333332222252222
                                   0000000000000000020000000000000000080000
    ... +  40                         903H   - 1   1         201
                                   2223334222223222322222222233322222222222
                                   0009038000D01000100000000020100000000000
    ... +  80
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... + 120
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... + 160
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... + 200
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... + 240
                                   222222222222222
                                   000000000000000
    ABAP_FALSE
                                   2
                                   0
    GODYNPRO-UMCHA
                                   2222222222
                                   0000000000
    ME->PT_GOITEM                  Table IT_156[20x2752]
    L_TABIX                        2
                                   0000
                                   2000
         4 METHOD       VALUECOPY
           SAPLMIGO
           LMIGOTV3                                   370
    LS_TARGET_GOITEM-GLOBAL_COUNTE 000002
                                   333333
                                   000002
    L_CHECKFIELD                   GOITEM-LGOBE
                                   444544244444222222222222222222
                                   7F945DDC7F25000000000000000000
    L_STATUS                       1229932294
                                   0
                                   6
    G_SUB_TAXES
                                   2222
                                   0000
    LCL_MIGO_SCREENMODIFICATION=>C 960038918
                                   0
                                   6
    L_FIELD_TARGET                 LS_TARGET_GOITEM-LGORT
                                   4555454455444544244455222222222222222222
                                   C3F412754F7F945DDC7F24000000000000000000
    ... +  40
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... +  80
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... + 120
                                   222222222222
                                   000000000000
    <L_VALUE_TARGET>               2031
                                   3333
                                   2031
    <L_VALUE_SOURCE>               2031
                                   3333
                                   2031
    LCL_MIGO_GLOBALS=>KERNEL      
    L_TARGETLINE                   2
                                   0000
                                   2000
    ABAP_TRUE                      X
                                   5
                                   8
    LS_TARGET_GOITEM                         00000002000000000000     X
                                   2222222222333333333333333333332222252222
                                   0000000000000000020000000000000000080000
    ... +  40                         903H   - 1   1         201
                                   2223334222223222322222222233322222222222
                                   0009038000D01000100000000020100000000000
    ... +  80
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... + 120
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... + 160
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... + 200
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... + 240
                                   222222222222222
                                   000000000000000
    %_CX_GRID_ID                   1
                                   0000
                                   1000
         3 METHOD       LIF_MIGO_FRAME~OKCODE_HANDLER
           SAPLMIGO
           LMIGOTV2                                   174
    I_OKCODE                       MIGO_OK_TAKE_VALUE
                                   4444544554445544542222222222222222222222
                                   D97FFFBF41B5F61C550000000000000000000000
    ... +  40
                                   222222222222222222222222222222
                                   000000000000000000000000000000
    GOSPLIT                                                    #######
                                   2222222222222222222222222222000000022222
                                   0000000000000000000000000000000000C00000
    ... +  40
                                   222222222222222222222222222222
                                   000000000000000000000000000000
    LCL_MIGO_GLOBALS=>KERNEL      
    GOSEARCH_PO
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... +  40
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... +  80
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... + 120
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... + 160                                                    0000000000
                                   2222222222222222222222222222223333333333
                                   0000000000000000000000000000000000000000
    ... + 200                      000000
                                   3333332222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... + 240                      000000
                                   333333
                                   000000
    LS_CONTROL
                                   222222222222222
                                   000000000000000
    %_CX_TABSTRIP_VERSION          0
                                   3
                                   0
    GOSEARCH_ORD
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... +  40
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... +  80
                                   222222222222
                                   000000000000
    RSJOBINFO                                                      00000000
                                   2222222222222222222222222222222233333333
                                   0000000000000000000000000000000000000000
    ... +  40                      000000
                                   3333332222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... +  80                      ####
                                   0000
                                   0000
    ME                            
         2 METHOD       OKCODE_DISPATCH
           SAPLMIGO
           LMIGOFR2                                   171
    I_OKCODE
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... +  40
                                   222222222222222222222222222222
                                   000000000000000000000000000000
    L_MSG_STRING
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... +  40
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... +  80
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... + 120
                                   222222222222222222222222222222
                                   000000000000000000000000000000
    LCL_MIGO_GLOBALS=>EXTERNAL_CAL 0000000000
                                   3333333333
                                   0000000000
    L_OKCODE                       MIGO_OK_TAKE_VALUE
                                   4444544554445544542222222222222222222222
                                   D97FFFBF41B5F61C550000000000000000000000
    ... +  40
                                   222222222222222222222222222222
                                   000000000000000000000000000000
    SCREEN                         OK_NEW_ITEMS
                                   4454455454452222222222222222222222222222
                                   FBFE57F945D30000000000000000000000000000
    ... +  40
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... +  80
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... + 120                                              00001#10000 ####
                                   2222222222222222222222223333303333320000
                                   0000000000000000000000000000101000000000
         1 MODULE (PAI) PAI_OKCODE_DISPATCH
           SAPLMIGO
           LMIGOPAI                                    11
    LCL_MIGO_FRAME=>TRACE_INFOS
                                   2
                                   0
    LCL_MIGO_GLOBALS=>EXTERNAL_CAL 0000000000
                                   3333333333
                                   0000000000
    LCL_MIGO_GLOBALS=>EXTERNAL_CAL 0000
                                   3333
                                   0000
    LCL_MIGO_GLOBALS=>EXTERNAL_CAL 00000
                                   33333
                                   00000
    OKCODE
                                   2222222222222222222222222222222222222222
                                   0000000000000000000000000000000000000000
    ... +  40
                                   222222222222222222222222222222
                                   000000000000000000000000000000
    Application Calls
    No dump information available
    Application Information
    No dump information available
    Internal notes
    The termination occurred in the function "HandleRsqlErrors" of the SAP
    Basis System, specifically in line 773 of the module
    "//bas/640_REL/src/krn/runt/absapsql.c#16".
    The internal operation just processed is "SQLS".
    The internal session was started at 20080130103952.
    Internal call code.........: "[RSQL/READ/T001L ]"
    Active calls in SAP kernel
    SAP (R) - R/3(TM) Callstack, Version 1.0
    Copyright (C) SAP AG. All rights reserved.
    Callstack without Exception:
    App       : disp+work.EXE (pid=4832)
    When      : 1/30/2008 10:41:32.722
    Threads   : 2
    Computer Name       : TOGR3PRD1
    User Name           : SAPServicePRD
    Number of Processors: 8
    Processor Type: x86 Family 15 Model 2 Stepping 6
    Windows Version     : 5.2 Current Build: 3790
    State Dump for Thread Id 14ac
    eax=00000000 ebx=00000000 ecx=00000000 edx=00000000 esi=003c61d4 edi=003c61a8
    eip=7c82ed54 esp=03fedfb4 ebp=03fedfc4 iopl=0         nv up ei pl nz ac po nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000216
    function : KiFastSystemCallRet
             7c82ed54 c3               ret
             7c82ed55 8da42400000000   lea     esp,[esp]              ss:03fedfb4=7c82ed5c
             7c82ed5c 8d642400         lea     esp,[esp]              ss:07fdb4c7=00000000
    FramePtr ReturnAd Param#1  Param#2  Param#3  Param#4  Function Name
    03fedfc4 003c61a8 00000000 00000001 01d40b84 000014ac ntdll!KiFastSystemCallRet
    00000000 00000000 00000000 00000000 00000000 00000000 <nosymbols>
    State Dump for Thread Id 168c
    eax=00000001 ebx=00000103 ecx=fffffffe edx=003c0000 esi=00000000 edi=00000000
    eip=7c82ed54 esp=05fefeb0 ebp=05fefef4 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:05fefeb0=7c821514
             7c82ed5c 8d642400         lea     esp,[esp]              ss:09fdd3c3=00000000
    FramePtr ReturnAd Param#1  Param#2  Param#3  Param#4  Function Name
    05fefef4 00fede51 00000eb0 00000000 00000000 003c7920 ntdll!KiFastSystemCallRet
    05feff84 7c349565 00000000 00000000 00000000 003c79b8 disp+work!SigIMsgFunc >
    > [signt.c (563)]
    05feffb8 77e6608b 003c79b8 00000000 00000000 003c79b8 MSVCR71!endthreadex
    05feffec 00000000 7c3494f6 003c79b8 00000000 00000000 kernel32!GetModuleFileNameA
    List of ABAP programs affected
    Type
    Program
    Gen. Date  Time
    Load Size
    Prg
    SAPLMIGO
    22.09.2005 21:54:56
    1226752
    Prg
    SAPMSSYD
    05.06.2002 17:09:33
    16384
    Prg
    SAPFSYSCALLS
    14.02.2002 14:22:47
    6144
    Prg
    CL_MMIM_USERDEFAULTS==========CP
    06.05.2002 10:42:38
    17408
    Typ
    ESDUS
    01.03.1999 13:36:04
    2048
    Typ
    GOHEAD
    08.01.2003 16:15:40
    9216
    Typ
    MKPF
    08.01.2002 15:13:52
    5120
    Typ
    KBEFU
    26.03.1999 14:46:02
    5120
    Typ
    LFA1
    11.05.2004 11:32:44
    19456
    Typ
    MIGO_CUST_ACTION
    30.11.1999 10:19:14
    2048
    Typ
    MIGO_CUST_REFDOC
    30.11.1999 10:19:14
    2048
    Typ
    X031L
    15.11.2000 18:03:28
    5120
    Prg
    SAPLSDIFRUNTIME
    22.09.2005 21:42:36
    81920
    Typ
    DFIES
    09.11.2000 14:07:05
    8192
    Prg
    SAPLSDNT
    22.09.2005 21:55:13
    201728
    Prg
    SAPLSUGS
    22.09.2005 21:42:36
    29696
    Prg
    SAPLV01D
    11.05.2004 11:59:11
    25600
    Typ
    IWRKZ
    04.04.1995 15:56:46
    1024
    Typ
    TCUCH
    07.01.2002 15:50:54
    3072
    Typ
    TCUBN
    07.01.2002 15:50:53
    2048
    Typ
    TCUWS
    13.08.1997 13:57:58
    2048
    Typ
    TCUDRV
    07.01.2002 15:50:54
    2048
    Prg
    CL_GUI_CFW====================CP
    22.09.2005 21:14:53
    154624
    Prg
    CL_GUI_PROPS_CONSUMER=========CP
    07.01.2003 18:26:56
    26624
    Prg
    %_CCNTL
    14.02.2002 14:22:46
    13312
    Prg
    SAPLTHFB
    22.09.2005 22:08:44
    304128
    Prg
    CL_EXITHANDLER================CP
    16.06.2004 11:34:41

    Hello,
    the problem is the following error:
    >> ORA-04030: out of process memory when trying to allocate 1332 bytes (callheap,qkkele)
    Take a look at sapnote #130140 and #335230 and follow the instructions.
    Regards
    Stefan

  • Runtime error in excise tax

    hi
    i am getting runtime error while doing googs receipt with tax code(without tax not getting error).please see this error.
    Runtime Errors         MESSAGE_TYPE_X
    Date and Time          27.08.2008 20:32:45
    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
    Long text of error message:
    Diagnosis
    A balance has occurred in transaction currency 'INR' with the
    following details:
    Exchange rate '00', amount '             8.00-' and currency key
    'INR'.
    The data in the transaction currency were transferred from the
    calling application.
    System Response
    Your data cannot be processed in FI.
    Procedure
    The error is probably in the calling application.
    Technical information about the message:
    Message class....... "F5"
    Number.............. 702
    Variable 1.......... 00
    Variable 2.......... " 8.00-"
    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
    Source Code Extract
    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.

    Hi,
    Please check the following notes
    Note 1242773 - Getting short dump when doing GR for combined requisitions
    Note 1047059 - Run time error in migo/Goods receipt
    Regards,
    Jigar

  • Run time error while saving migo

    Dear All,
    I am doing the subcontracting process. and while saving the MIGO it shows Runtime Error.
    Error analysis
        Short text of error message:
        No taxes on sales/purch.are allowed for account 428304 BS70, V0 is not a
        llowed
        Technical information about the message:
        Message classe...... "FS"
        Number.............. 217
        Variable 1.......... 428304
        Variable 2.......... "BS70"
        Variable 3.......... "V0"
        Variable 4.......... " "
    Trigger Location of Runtime Error
        Program                                 SAPLMBWL
        Include                                 LMBWLU21
        Row                                     59
        Module type                             (FUNCTION)
        Module Name                             MB_POST_GOODS_MOVEMENT
    BS70 is a company code.
    Please help me out.
    Thanks & Regards,
    Sandeep Patil.

    Dear All,
    i have done that but now another error is coming as
    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.......... " 5.000,000"
        Variable 3.......... "INR"
        Variable 4.......... " "
    5.000,000 is my po value.
    Thanks & Regards,
    Sandeep.

  • Runtime Error in PGI

    Hi Experts,
    This is with regarding Bonded warehouse scenario by which client get an option to keep the material at the warehouse for 90 days without paying the customs duties. After completion of 90 days, they would pay the duties & move the stock from one storage location(RM non duty paid) to another (RM duty paid).
    1. PO against import vendor - Bonded warehouse plant
    2. MIGO - Only Stock a/c and GR/IR accounted, no accounting of CVD & customs clearing happened. (Storage location - RM Non duty paid)
    3. MIRO against Import vendor - Only vendor a/c & GR/IR accounted.
    After completion of 90 days - payment of duties and moving from one storage to another.
    4. STO PO from one storage location to another - CVD & Customs conditions are loaded.
    5. MIRO against Commissioner of Customs - CVD & Customs clearing accounted here.
    6. VL10B and VL02N (PGI from one storage location (Non duty paid) to another storage location (Duty paid).
    In the PGI, all the duty values are getting added up to the inventory. All duties should be inventoried, only when the Material type is Trading goods. If the Material type is RM (or) PM (or) Semi finished, CVD values should not be added to the inventory as it is Set off u2013 Claimable.
    For the above purpose, ABAPer wrote a code and executed the PGI, system throws a runtime error as below
    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
    Any help?
    Regards,
    Vijay N

    as it is your Abapers coding that it causing the problem, you have to tell him about the issue so that he can fix is error.
    You cannot expect help from here.

Maybe you are looking for

  • SQL*Loader to load LOB files....

    Hi everybody, I've tried to insert LOB files (*.gif,*.doc,*.bmp) into database using SQL*Loader. create table media_tab2 ( clip_id NUMBER NOT NULL, text1_txt CLOB, image_gif BLOB This is the control file: LOAD DATA INFILE * INTO TABLE media_tab FIELD

  • Not show anythings in tab License Key in Central Management Console

    Dear All ! I have a DVD SAP Business Objects Edge Standard XI 3.1 include BOE Standard XI 3.1 and Add on Sap_Integration, PeopleSoft_Integration, JDE_Integration and EBS_Integration I have a temporary License Key Code which downloaded on Sap Market P

  • DNS nuisance on MBP OS X 10.6.4 (Snow Leopard)

    I have seen many posts regarding a potential bug with DNS on SL (OS X 10.6.x). Some users have a recurring problem but at least get to a working state after a reboot or flushing their DNS cache. I have upgraded to SL 10.6.4. DNS worked for a time and

  • Tool pane for selecting properties for app in SharePoint 2013(Something like webpart properties for apps)

    How to create a tool pane for apps in SharePoint using SharePoint hosted app model 2013..I mean i m looking for something like webpart propeties to be given to the user for selecting desired content.Can someone provide help code for this functionalit

  • Update os x

    I have imac with os x 10.5.8 How update to the latest os x? Which is the lastest? Os x mountain lion?