MIRO runtime error

Dear Experts,
I am facing a problem in MIRO t.code.  While doing MIRO, when i click on details tab its going to dump.  the error as below.
ABAP runtime errors    DYNPRO_NOT_FOUND
DYNPRO_NOT_FOUND"
SAPLFDCB " or "LFDCBO01 "
CUST_SCREEN_SET_HEADER_DATA"
Error analysis
Program "SAPLXM08" tried to use screen 0400.
The screen does not exist.
kindly help me how to solve the issue.
regards,
Gopi.P

Hi,
Please check the below OSS note:-
[https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=135656]
It should solve your issue.
Regards,
SDNer

Similar Messages

  • Runtime error in MIRO while using User/Screen exit

    Hello,
    I have implemented an exit in ABAP for MIRO which when transported to Quality server through runtime error.
    I have used EXIT (SMOD) : LFDCB001 which contains FM -> EXIT_SAPLFDCB_001 and include -> ZXM08U31. In this exit I have written my code to disable Inv. Party field. This field exist in Details Tab in Miro Transaction.
    Location of the field: MIRO -> Details (tab) -> Inv. Party (Field)
    Code written in include ZXM08U31 is:
    LOOP AT SCREEN.
      IF screen-name = 'INVFO-LIFRE'.
        screen-input = 0.
        MODIFY SCREEN.
      ENDIF.
    ENDLOOP.
    This exit is assigned to a project in CMOD and I tested the same in Development system. It is working perfectly.
    Now I transported the TR (Includes program ZXM08U31 and Customer enhancement projects ZMIRO). Now when I run MIRO in quality server it triggers the my logic and then through runtime error.
    Runtime error says:
    Short text
        Dynpro does not exist
    Error analysis
        The system attempted to use dynpro 0400 in program "SAPLXM08".
        This dynpro does not exist.
    I agree that screen 400 does not exists in program for MIRO but it does not exists in development system as well. So if the runtime error is valid in QEC server then why not in DEV server. And when it can run successfully in DEV server why cant it run in QEC server.
    Hope I have explained all the things in detail.
    Please provide me the solution since user can bombard anytime for the MIRO dump everytime in QEC.
    Regards,
    Harjeet Grover

    Hi Harjeet,
    Reason of your Dump is that the enhancement "LFDCB001" which you used contains one Function module exit "EXIT_SAPLFDCB_001" and another one screen exit in calling screen  "SAPLFDCB" number 0150.
    So when you activate your project these above mentioned both components were activated.
    So when you execute transaction SAP looks for called screen "SAPLXM08" No-0400 but as you havn't created and program go for DUMP.
    Solution - Just Create called screen  "SAPLXM08" No-0400 and activate.
    Thanks,
    Vijay

  • 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

  • Runtime Error when Posting Invoice with text added (MIRO)

    Hi Gurus,
    We are getting a shortdump (runtime error) when we post certain invoices in MIRO. This happens when we input some text in the text field or add some text to the NOTE tab.
    We are having exception ERROR_DP raised in the program c_textedit_control.
    If the text field is blank and nothing is writing in the NOTE tab, the invoice gets posted with no problem.
    Has anyone come accross this issue before and how did you solve it please.
    Thanks.

    are u processing thru BADI, then it is very easy there are interfaces and methods for handling texts. u sud not get any error and plz never write commit work in BADI.
    May be i cud provide more help if u share more details but let me tell more but let me share one recent development that i did.
    In ME59n when we do PR TO PO then texdts sud be copied to header text in PO and get reflected in PO. the coding is like below may be can give some clues wid ur MIRO stuff.
    METHOD if_ex_me_process_po_cust~process_header.
    *  Author        : Prasenjit Bist                                          *
    *  ID            : PRBIST                                                  *
    *  Date          : 04.08.2011                                              *
    *  Changes       : New Devlopment                                          *
    *  Change Request:                                                         *
    *  Description: To copy LSP information in PO                               *
    TYPES:
            BEGIN OF ty_text,
              auto_pr_po TYPE zman_auto_pr_po,
              plant TYPE zman_plant,
              vendor TYPE zman_vendor,
              lsp_vendor TYPE zman_lsp_name,
              contract_no_text TYPE zman_contract_no_text,
            END OF ty_text.
      TYPES:
           BEGIN OF ty_address,
             ort01      TYPE ort01_gp,  " city
             ort02      TYPE ort02_gp,  " district
             pfach      TYPE pfach,     " PO Box
             pstlz      TYPE pstlz,     " Postal code
             region     TYPE regio,     "Region (State, Province, County)
             telf1      TYPE telf1,     "1st telephone number
             telf2      TYPE telf2,     "2nd telephone number
             telfx      TYPE telfx,     "Fax number
             land1      TYPE land1,
           END OF ty_address.
      DATA:
       get the header level details
            ls_mepoheader TYPE mepoheader,
            lt_purchase_order_items TYPE purchase_order_items,
            ls_purchase_order_items LIKE LINE OF lt_purchase_order_items,
       get the line item details
            lt_mepoitem TYPE STANDARD TABLE OF mepoitem,
            ls_mepoitem TYPE mepoitem,
            lt_textlines TYPE mmpur_t_textlines,
            ls_textlines LIKE LINE OF lt_textlines,
    TEXT TYPES
            lt_texttypes TYPE mmpur_t_texttypes,
            ls_texttypes LIKE LINE OF lt_texttypes.
      DATA: l_name TYPE thead-tdname,
            ls_header TYPE thead,
            lt_lines TYPE STANDARD TABLE OF tline,
            ls_lines TYPE tline,
            l_tdobject TYPE thead-tdobject,
            l_metafield TYPE mmpur_metafield.
      DATA: ls_text TYPE ty_text,
            l_text(50).
      DATA: l_continue(1).
      DATA: l_pass_vendor TYPE lifnr,
            l_pass_plant TYPE werks,
            l_name1(35).
    fetch the address
      DATA: ls_address TYPE ty_address,
            l_landx    TYPE landx.
      CONSTANTS: lc_id TYPE thead-tdid     VALUE 'F01',
                 lc_langu TYPE thead-tdspras  VALUE 'E',
                 lc_object TYPE thead-tdobject VALUE 'EKKO'.
      CONSTANTS: lc_set(1) VALUE 'X',
                 lc_vendor(11) VALUE 'Vendor:    ',
                 lc_lsp_vendor(11) VALUE 'LSP Vendor:',
                 lc_contract_no_text(14) VALUE 'Contract Text:'.
      CLEAR: l_continue.
      IF sy-uname EQ 'PRBIST'.
    Read the header data
        ls_mepoheader = im_header->get_data( ).
    read teh item level data.
       break prbist.
        lt_purchase_order_items = im_header->get_items( ).
        LOOP AT lt_purchase_order_items INTO ls_purchase_order_items.
    The item attribute of the structure is reference to line item
          ls_mepoitem = ls_purchase_order_items-item->get_data( ).
          APPEND ls_mepoitem TO lt_mepoitem.
        ENDLOOP.
    CHECK VENDOR IS THE ONE WE WANT.
        SELECT SINGLE name1 FROM lfa1 INTO l_name1 WHERE lifnr = ls_mepoheader-lifnr.
    First read the vebdor name based on LIFNR.
        TRANSLATE l_name1 TO UPPER CASE.
        IF ( l_name1 EQ 'LSP1' ) OR ( l_name1 EQ 'LSP2' ).
          LOOP AT lt_mepoitem INTO ls_mepoitem.
            TRANSLATE ls_mepoitem-werks TO UPPER CASE.
            IF ls_mepoitem-werks EQ 'FI01'.
              l_continue = lc_set.
              l_pass_vendor = ls_mepoheader-lifnr.
              l_pass_plant = ls_mepoitem-werks.
              EXIT.
            ENDIF.
          ENDLOOP.
        ENDIF.
        IF l_continue EQ lc_set AND sy-tcode EQ 'ME21N'.
    Call the POP UP screen to display LPS information.
          CALL FUNCTION 'ZMAN_LSP_POP_UP'
            EXPORTING
              im_vendor = l_pass_vendor
              im_plant  = l_pass_plant
            IMPORTING
              ex_text   = l_text.
    GET Text Object (TTXOB)
          im_header->if_longtexts_mm~get_textobject(
                        IMPORTING ex_tdobject = l_tdobject
                                  ex_metafield = l_metafield ).
    GET TEXT IDS
          im_header->if_longtexts_mm~get_types(
                        IMPORTING ex_texttypes = lt_texttypes ).
    CHECK TEXT TYPE 'F01' EXISTS.
          READ TABLE lt_texttypes INTO ls_texttypes WITH  KEY tdid = lc_id.
          IF sy-subrc EQ 0.
    UPDATING ITEM TEXT.
            MOVE: l_tdobject TO ls_textlines-tdobject,
                  ls_texttypes-tdid TO ls_textlines-tdid,
                  '*' TO ls_textlines-tdformat.
         break prbist.
            ls_text = l_text.
         CONCATENATE l_text ls_texttypes-tdtext INTO ls_textlines-tdline.
           CONCATENATE ls_text-vendor
                       ls_text-plant
                       ls_text-lsp_vendor
                       ls_text-contract_no_text
                                               INTO ls_textlines-tdline SEPARATED BY space.
           APPEND ls_textlines TO lt_textlines.
          INSERT VENDOR
           CLEAR ls_textlines-tdline.
           CONCATENATE lc_vendor ls_text-vendor INTO ls_textlines-tdline SEPARATED BY space.
           APPEND ls_textlines TO lt_textlines.
          INSERT LSP VENDOR
            CLEAR ls_textlines-tdline.
            CONCATENATE lc_lsp_vendor ls_text-lsp_vendor INTO ls_textlines-tdline SEPARATED BY space.
            APPEND ls_textlines TO lt_textlines.
          INSERT CONTRACT TEXT.
            CLEAR ls_textlines-tdline.
            CONCATENATE lc_contract_no_text ls_text-contract_no_text INTO ls_textlines-tdline SEPARATED BY space.
            APPEND ls_textlines TO lt_textlines.
         INSERT A BLANK LINE.
            CLEAR ls_textlines-tdline.
            APPEND ls_textlines TO lt_textlines.
    INSERT addreSS CAPTION.
            CLEAR ls_textlines-tdline.
            MOVE 'Address:' TO ls_textlines-tdline.
            APPEND ls_textlines TO lt_textlines.
            break prbist.
    READ THE ADDRESS
            SELECT SINGLE   ort01      " city
                            ort02      " district
                            pfach      " PO Box
                            pstlz      " Postal code
                            regio      "Region (State, Province, County)
                            telf1      "1st telephone number
                            telf2      "2nd telephone number
                            telfx      "Fax number
                            land1      "COUNTRY
            FROM lfa1 INTO ls_address WHERE lifnr = ls_mepoheader-lifnr.
    GET COUNTRY
            SELECT SINGLE landx FROM t005t INTO l_landx WHERE spras = 'E' AND land1 = ls_address-land1.
    INSERT ADDRESS DETAILS.
            CLEAR ls_textlines-tdline.
            CONCATENATE ls_address-ort01 ls_address-ort01 INTO ls_textlines-tdline SEPARATED BY space.
            APPEND ls_textlines TO lt_textlines.
    INSERT COUNTRY.
            CLEAR ls_textlines-tdline.
            MOVE l_landx TO ls_textlines-tdline.
            APPEND ls_textlines TO lt_textlines.
    TELEPHONE DETAILS
            CLEAR ls_textlines-tdline.
            CONCATENATE 'Tel:' ls_address-telf1 '/' ls_address-telf2 INTO ls_textlines-tdline.
            APPEND ls_textlines TO lt_textlines.
    FAX DETAILS.
            CLEAR ls_textlines-tdline.
            CONCATENATE 'Fax:' ls_address-telfx INTO ls_textlines-tdline.
            APPEND ls_textlines TO lt_textlines.
          SAVE THE HEADER LONG TEXT.
            im_header->if_longtexts_mm~set_text(
                          EXPORTING im_tdid = ls_texttypes-tdid
                                    im_textlines = lt_textlines ).
          ENDIF.
        ELSEIF l_continue EQ lc_set AND sy-tcode EQ 'ME59N'.
    No need to display POPUP simply read the values and show.
    if not
        ENDIF. "(l_continue = 'X' and transaction code is ME21N or ME59N)
        CLEAR l_continue.
      ENDIF. "(sy-uname)
    ENDMETHOD.
    Edited by: Prasenjit Singh Bist on Aug 14, 2011 10:15 AM
    Edited by: Prasenjit Singh Bist on Aug 14, 2011 10:21 AM

  • Runtime error in MIRO posting invoice for SES's created in CATS

    Hi Gurus,
    We are having an issue when posting invoices in MIRO referred to SES created in CATS.
    It always took much longer the system to process those SES created via CATS than those from the standard MM (ML81...) but the situation today is so critical that we can not pay the vendors for which SES are created via CATS. Runtime error is obtained when trying to post a SES for 900$ value.
    This problem does not happen in our integrating/testing system.
    Do you have any idea why this is happening?
    thanks to everyone in advance,
    VL

    Hi,
    have you searched for notes with the runtime error details?
    Has also a short dump occured (transaction ST22) ? Please give more detail information.
    Regards,
    Edit

  • ABAP Runtime error at simulating MIRO

    Hello SAPians,
    My user is getting the "ABAP Runtime Error" when simulating the MIRO. My technical consultant has given the below results. Please let me know how to handle this. As this is a standard program we don't want to change. Please find the below things:
    The code is in include LGLT0F61 and the internal table is item_l.
    Code :
       LOOP AT difference WHERE wrbtr <> 0.
       IF difference-curtp = qm.
         ADD difference-wrbtr TO item_l-accit-pswbt.
       ELSE.
         READ TABLE item_l-acccr INTO acccr_l
                                 WITH KEY curtp = difference-curtp. " This condition fails
         ADD difference-wrbtr TO acccr_l-wrbtr.
         MODIFY item_l-acccr FROM acccr_l INDEX sy-tabix. "Table cannot be modified with zero entries in it
       ENDIF.
    ENDLOOP.
    Thanks,
    JK

    Hi,
    We are also getting TABLE_INVALID_INDEX  Dump in LGLT0F61.
    Delete rounding differences
    LOOP AT difference WHERE wrbtr <> 0.
      IF difference-curtp = qm.
        ADD difference-wrbtr TO item_l-accit-pswbt.
      ELSE.
        READ TABLE item_l-acccr INTO acccr_l
                                WITH KEY curtp = difference-curtp.
        ADD difference-wrbtr TO acccr_l-wrbtr.
        MODIFY item_l-acccr FROM acccr_l INDEX sy-tabix.
      ENDIF.
    ENDLOOP.
    Could you please suggest me how to solve this.
    Thanks
    Bhuvana

  • Runtime error in MIRO

    Hi friends,
    while doing MIGO i am getting a runtime error as shown below
    Syntax error in program "SAPLF042 ".
    WHAT HAPPENED:
    Error in ABAP application program.
    The current ABAP program "SAPLFDCB" had to be terminated because one of the
    statements could not be executed.
    This is probably due to an error in the ABAP program.
    In program "SAPLF042 ", the following syntax error occurred
    in the Include "LF042U14 " in line 203:
    "The data object "E_BSEG" does not have a component called "ZZSPREG"."
    ERROR ANALYSIS
    In program "SAPLF042 ", the following syntax error occurred:
    "The data object "E_BSEG" does not have a component called "ZZSPREG"."
    How to proceed...........?

    Hi
    Please get in touch with your ABAPER as some one has performed an enhancement & it is incomplete.
    Please check.
    Thanks & Regards
    Kishore

  • 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.

  • MIR4 transaction is giving ABAP Runtime Error

    Hi Experts,
    When I am trying to display the invoice in MIR4 and/or MIRO the system is generating ABAP runtime error.  DYNPRO_FIELD_CONVERSION.  This is in Version ECC 6.0.
    Short text
        Conversion error
    What happened?
        The current screen processing action was terminated since a situation
        occurred where the application could not continue.
        This is probably due to an error in the ABAP program or in the curren
        screen.
    What can you do?
        Note which actions and input led to the error.
        For further help in handling the problem, contact your SAP administrator
        You can use the ABAP dump analysis transaction ST22 to view and manag
        termination messages, in particular for long term reference.
    Error analysis
        The program has been interrupted and cannot resume.
        Program "SAPLMR1M" attempted to display fields on screen 6310.
        An error occurred during the conversion of this data.
    How to correct the error
        There was a conversion error in the output of fields to the screen.
        The formats of the ABAP output field and the screen field may not match.
        Some field types require more space on the screen than in the ABAP
        program. For example, a date output field on the screen requires two
        more characters than the corresponding field in the ABAP program. When
        the date is displayed on the screen, an error occurs resulting in this
        error message.
                      Screen name.............. "SAPLMR1M"
                      Screen number............ 6310
                      Screen field............. "DRSEG-REMNG"
                      Error text............... "FX015: Sign lost."
        Other data:
        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.
    Please help us to solve this issue.
    Thanks and Regards,
    Havina
    Edited by: Havina Kutty on May 19, 2009 11:54 AM

    Hello,
    Please refer
    Note 503934 - MIRO: Dump DYNPRO_FIELD_CONVERSION -> field 'REMNG'
    Note 445853 - MIR4:more credit memos than invoices for service
    Note 393189 - MIRO: Incorrect update of BPMNG -> DYNPRO_FIELD_CONVERSION
    Regards,
    Ravi

  • A Runtime error: Generation successful, but you must call up the function

    I used Professor Jim Menching's AIS materials in fall 2009 before ECC 6.04 was installed and everything worked plug-n-play without too many problems.  I tested assigned client after my client provider migrated SAP from ECC 6.0 to 6.04. 
    I tried to proceeded "receive the product from the vendor" on page 13u2019s step 11 after creating an purchase order, as following:
    Logistics> Materials Management > Purchasing > Purchase Order > Follow-on Functions > Logistics Invoice Verification  (MIRO)
    I tried to save it.  However, I got an error message: "Generation successful, but you must call up the function".  After I did it one more time, it becomes a runtime error!  I am not savvy for dealing with unknown technical problem.  Can anyone provide me with a solution to fix problem?
    Thanks in advance.

    Picheng,
    Thanks for the post.  I forwarded your question to your hosting site for resolution since this is a technical issue ... and the technical team informed me the issue was already resolved.  If you have further issues related to this specific issue please contact the UCC directly.
    Best Regards,
    Heather

  • Runtime error in starting Lightroom

    I receive the following message when I try to start Lightroom:
    Microsoft Visual C++ Runtime Library
    Runtime Error!
    Program:...Files\Adobe\Adobe Photoshop Lightroom 1.2\lightroom.exe
    This application has requested the Runtime to terminate it in an unusual way.
    Please contact the application's support team for more information.
    Lightroom ran well for several days and then failed to open with the above message.
    I have tried everything I know to do (uninstalled and reinstalled the application, restored the computer to a restore point before Lightroom was originally installed, etc.) and do not know were to go from here. Suggestions would be appreciated.
    I am using Windows XP sp2 and have 4 GB of ram and 250 GB of hard disk space.
    Thanks,
    Cliff Culp

    Aha! A fix! Please look at this...
    http://www.adobeforums.com/cgi-bin
    bob frost, "Help! Runtime error after Lightroom 1.1 install!" #10, 27 Jun 2007 6:54 am

  • Runtime error while executing rule

    Hello All,
      While executing the DTP for a cube, im facing the error as Runtime error while executing rule -> see long text .
      For this source is another Cube, where im loading the data from Cube to Cube.
    Error Description are as follows:-
    Error Location: Object Type    TRFN
    Error Location: Object Name    0T9SCR6Q4VWS1SOPNRRBOY1YD51XJ7PX
    Error Location: Operation Type ROUTINE
    Error Location: Operation Name
    Error Location: Operation ID   00034 0000
    Error Severity                 100
    Original Record: Segment       0001
    Original Record: Number        557
    and Also descripton is :-
    Diagnosis
        An error occurred while executing a transformation rule:
        The exact error message is:
        Division by zero
        The error was triggered at the following point in the program
        GP4H0CW3MLPOTR3E8Y93QZT2YHA 4476
    System Response
        Processing the data record has been terminated.
    Procedure
    The following additional information is included in the higher-level
    node of the monitor:
       Transformation ID
       Data record number of the source record
       Number and name of the rule which produced the error
    Let me know ur valuable suggestions on these error...
    thanks.

    Hello,
    I have checked all the transformation and End Routines.All are working fine.Yesterday i have loaded some data into it, but today its gettting errored out.
    Checked completely in the forum for threads related to this, but couldnt find proper thread which had solutions....
    thanks,
    srinivas.

  • Could someone help me with a Runtime Error while saving a PDF file?

    While saving a 28 page PDF file in Illustrator today, I got a window saying, "This application has requested the "Runtime" to terminate it in a unusual way." It said to contact the applications support team for more information. I keep getting the same thing each time I try it. Does anyone know how to fix this issue or how I contact the applications support team ?
    Thank you for any insight.
    Pam

    It is a 13.5x11 inch calendar. There are 14 pages with images on them and
    some text. The other pages have text, a grid and a colored background with a
    gaussian blur. I saved each page as an "outline".
    The printer I am using requested I save all pages in a pdf file. I was
    successful in saving all but about six pages, now I can't even open the
    file.
    What happens is... I open Illustrator
                                   I open the pdf file
                                   A window appears that says... Runtime Error,
    This application has requested the Runtime to terminate it in an unusual
    way. Please contact the application's support team for more information.
                                   I select ok
                                   then a window appears that says... Adobe
    Illustrator CS5 has stopped working. A problem caused the program to stop
    working correctly. Windows will close the program and notify you if a
    solution is available.
                                   Then the program closes.
    So far I have not been notified of anything.
    Please let me know if you need more details.
    Thank you so much for helping me with this.
    Pam

  • RunTime Error while saving a Sales Order

    Hi All,
    When i am saving a Sales Order, the system is throwing a Runtime Error.
    The ABAP Code in the Runtime Error screen as follows.
              select * from (t681-kotab) appending table <cond_tab>
                     up to 1 rows
                     where kappl  = se_kappl
                     and   kschl  = se_kschl
                     and   datbi >= se_date
                     and   datab <= se_date
                     and   (coding_tab).
    Till these days, there was no such error while saving a Sales Order.
    How to resolve this issue?
    Regards
    Pavan

    Hi,
    The below piece of code is trying to get the contents of the table mentioned in T681-KOTAB.
    select * from (t681-kotab) appending table <cond_tab>
    up to 1 rows
    where kappl = se_kappl
    and kschl = se_kschl
    and datbi >= se_date
    and datab <= se_date
    and (coding_tab).
    The reason could be is someone has screwed up the entries in T681 table. Check that out.
    Try to put a break point on this SELECT query and see what the value of T681-KOTAB holds before the SELECT query. Check whether such a table entry exists in DB.
    Let me know if you are still stuck up.
    If you can send me the ST22 dump of the run time error, i might be able to help you more  on this.
    Hope this helps.
    Thanks,
    Balaji

  • WHILE DELETING A SALE ORDER GETTING A RUNTIME ERROR

    hi to all experts,
    whenever i try to delete a particular sale order im getting a runtime error
    stating that
    Short text
        Screen: Illegal message
    What happened?
        The current screen processing action was terminated since a situat
        occurred where the application could not continue.
        This is probably due to an error in the ABAP program or in the cur
        screen.
    Error analysis
        The program attempted to issue a " " message during "Exit Command" processing.
        This is an illegal operation.
        The program was terminated.
        Screen name.............. "SAPMV45A"
        Screen number............ 4001
    Trigger Location of Runtime Error
        Program                                 SAPMV45A
        Include                                 MV45AFZZ
        Row                                     370
        Module type                             (FORM)
        Module Name                             USEREXIT_SAVE_DOCUMENT
    SourceCde
                  message e001(zm) WITH text-335 ltab-kunnr text-334.
                else.
                  if ktab-jkunnr <> ltab-kunnr.
                    ktab-jkunnr = ltab-kunnr.
                    jobsitecode = ltab-kunnr.
                    CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
                    EXPORTING
                      input  = jobsitecode
                      IMPORTING
                      output = jobsitecode.
                    SELECT SINGLE * FROM kna1 WHERE kunnr = jobsitecode.
                    IF sy-subrc = 0.
                      ktab-jname1 = kna1-name1.
                      ktab-jstras = kna1-stras.
                    ENDIF.
                    chg_flg = 'X'.
                  endif.
                endif.
              else.
                message e001(zm) WITH text-336.
    * Validation for relationship between Sold-to Party and Ship-to Party
    *          if ktab-ckunnr+0(4) NE ktab-jkunnr+0(4).
    *            message e001(zm) WITH text-335 ktab-jkunnr text-337 ktab-ckunnr.
    *          endif.
              custcode1 = ktab-ckunnr.
              CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
                EXPORTING
                  input  = custcode1
                IMPORTING
                  output = custcode1.
              jobsitecode1 = ktab-jkunnr.
              CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
                EXPORTING
                  input  = jobsitecode1
                IMPORTING
                  output = jobsitecode1.
              SELECT SINGLE * FROM knvp
              WHERE kunnr = custcode1
                AND vkorg = vbak-vkorg
                AND vtweg = vbak-vtweg
                AND spart = vbak-spart
                AND parvw = 'WE'
    Error analysis
        The program attempted to issue a " " message during "Exit Command"
        This is an illegal operation.
        The program was terminated.
        Screen name.............. "SAPMV45A"
        Screen number............ 4001
    Trigger Location of Runtime Error
        Program                                 SAPMV45A
        Include                                 MV45AFZZ
        Row                                     370
        Module type                             (FORM)
        Module Name                             USEREXIT_SAVE_DOCUMENT

    Hi,
    Seems there is some problem with the user exit USEREXIT_SAVE_DOCUMENT..
    Put a breakpoint and see.
    Regards,
    Nagaraj

Maybe you are looking for