Runtime error while doing FB08

while doing FB08 the system is creating a dump.
Runtime errors         SYNTAX_ERROR                                                      
       Occurred on     05.08.2008 at   12:43:14                                                                               
Syntax error in program "SAPLFMREAS ".                                                                               
What happened?                                                                               
The following syntax error occurred in the program SAPLFMREAS :                          
"The obligatory parameter "C_GSBER" had no value assigned to it."                        
Error in ABAP application program.                                                                               
The current ABAP program "SAPLFMRI_CORE" had to be terminated because one of             
the                                                                               
statements could not be executed.                                                                               
This is probably due to an error in the ABAP program.                                                                               
What can you do?                                                                               
Please eliminate the error by performing a syntax check                                  
(or an extended program check) on the program "SAPLFMREAS ".                             
You can also perform the syntax check from the ABAP/4 Editor.                            
If the problem persists, proceed as follows:                                             
Print out the error message (using the "Print" function)                                 
and make a note of the actions and input that 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
The following syntax error was found in the program SAPLFMREAS :
"The obligatory parameter "C_GSBER" had no value assigned to it."
How to correct the error
Probably the only way to eliminate the error is to correct the program.
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.

Hi,
Run time error occurs when certain info objects are activated or if the patches for a certain standard program or tcode has to be applied. Please refer to the SAP Notes for the error mentioned by you and apply the related support package for the same. You can co ordinate wiht your Basis as well as Abap consultant to implement the correction.
Hope this helps
regards,
radhika

Similar Messages

  • Getting runtime error while doing sales order

    Hi,
    I am getting a runtime error while doing sales order.
    Error : SAPSQL_INVALID_FIELDNAME
    Kindly suggets....stuck up badly.
    cant do any transaction.
    Regards
    Kishan

    Hello,
    Check OSS Note#209847 and 310304
    Regards,
    Gauravjit.
    Reward points if the notes are helpful

  • ABAP runtime error while doing ME21N, ME22N, ME23N, ME51N,ME52N, ME53N

    Dear All Expert,
    I am facing problem while doing ME21N, ME22N, ME23N, ME51N,ME52N, ME53N,
    Please find the below ABAP Runtime Error.
    Runtime Errors         LOAD_TYPE_VERSION_MISMATCH
    Date and Time          10.02.2011 11:13:07
    Short text
         Change of a Dictionary structure at runtime of a program.
    What happened?
         Runtime error
         The current ABAP program "CL_IM_WRF_MM_PROC_PO==========CP" had to be
          terminated because one
         of the statements could not be executed at runtime.
    What can you do?
         Restart the program.
         If the error persists, contact your SAP administrator.
         You can use the ABAP dump analysis transaction ST22 to view and manage
         termination messages, in particular for long term reference.
    Error analysis
         The ABAP runtime system detected that the Dictionary-type "WRF_POHF_KOMP_STY"
          changed
         during the flow of the transaction.
         As the type was already used in the old version
         and in the new type should be used in the same transaction in the new
          version, the transaction had to be cancelled to avoid inconsistencies.
    How to correct the error
        Try to restart the program.
    System environment
        SAP-Release 700
        Application server... "iqe"
        Network address...... "172.25.0.85"
        Operating system..... "Linux"
        Release.............. "2.6.9-55.ELsmp"
        Hardware type........ "x86_64"
        Character length.... 16 Bits
        Pointer length....... 64 Bits
        Work process number.. 0
        Shortdump setting.... "full"
        Database server... "iqe"
        Database type..... "ORACLE"
        Database name..... "IQE"
        Database user ID.. "SAPSR3"
        Terminal................. "MUMJML5727"
        Char.set.... "C"
        SAP kernel....... 700
        created (date)... "Dec 26 2010 20:17:07"
        create on........ "Linux GNU SLES-9 x86_64 cc3.3.3"
        Database version. "OCI_102 (10.2.0.2.0) "
    Patch level. 285
    Patch text.. " "
    Database............. "ORACLE 10.1.0.., ORACLE 10.2.0.., ORACLE 11.2...*"
    SAP database version. 700
    Operating system..... "Linux 2.6"
    Memory consumption
    Roll.... 16192
    EM...... 25139088
    Heap.... 0
    Page.... 40960
    MM Used. 8038136
    MM Free. 4528408
    User and Transaction
    Client.............. 600
    User................ "JKMM"
    Language key........ "E"
    Transaction......... " "
    Transactions ID..... "4D524AD1FD7A42F9E1000000AC190055"
    Program............. "CL_IM_WRF_MM_PROC_PO==========CP"
    Screen.............. " "
    Screen line......... " "
    Information on where terminated
        The termination occurred during generation of the ABAP/4 program
         "CL_IM_WRF_MM_PROC_PO==========CP".
        The termination occurred in line 213
        of the source code of program "CL_IM_WRF_MM_PROC_PO==========CM007" (when
         calling the editor 2130).
    Source Code Extract
    Line  SourceCde
      183   DATA: l_flag TYPE wrf_pbas_boolean.
      184
      185   CALL FUNCTION 'WRF_POHF_MSG_READ_PREVIEW_FLAG'
      186     IMPORTING
      187       e_preview_flag = l_flag.
      188
      189   IF NOT l_flag IS INITIAL.
      190
      191     DATA: l_header TYPE REF TO cl_po_header_handle_mm.
      192
      193     MOVE im_header ?TO l_header.
      194
      195     CALL METHOD l_header->if_output_mm~preview( ).
      196
      197     CALL FUNCTION 'WRF_POHF_MSG_RESET_PREV_FLAG'.
      198
      199 ***$ Widening Cast for printing information.
      200 **    CALL FUNCTION 'WRF_POHF_STORE_PRINT_INFO_SET'
      201 **      EXPORTING
      202 **        im_header = l_header.
      203
      204 * Printing Preview
      205 * IF NOT gv_preview IS INITIAL.
      206 *    CALL METHOD l_header->if_output_mm~overview( ).
      207 *    CALL METHOD l_header->if_output_mm~preview( ).
      208 * clear gv_preview.
      209   ENDIF.
      210
      211 *  ENDIF.
      212
    >>>>> ENDMETHOD.
    Internal notes
        The termination was triggered in function "ab_RxDdicStruShareFailed"
        of the SAP kernel, in line 2539 of the module
         "//bas/700_REL/src/krn/runt/abtypload.c#11".
        The internal operation just processed is " ".
        Internal mode was started at 20110210111306.
        Name of the changed type......: "WRF_POHF_KOMP_STY"
        New version of the type.......: 20070508193207
        Old version of the type.......: 20070508193207
        New user......................: "Type" "WRF_POHF_KOMP_STY"
        Version of the new user.......: 20070508193207
        Old user......................: "???" "???"
        Version of the old user.......: "???"
    Active Calls in SAP Kernel
    Lines of C Stack in Kernel (Structure Differs on Each Platform)
    (CTrcStack2+0x78)[0x6cbb78]
    (CTrcStack+0xb)[0x6cc17b]
    (ab_rabax+0x3be5)[0xb8d985]
    (_Z24ab_RxDdicStruShareFailedPKtm4RUDIS0_S1_S0_+0x163)[0xb16823]
    (_Z19ab_GetDdicTypeIndexPKtm4RUDI+0x1f6)[0xb0dbb6]
    (_Z11ab_LoadViewPtjPKtPK11PROGRAMHEADPj+0x27e)[0xb16ede]
    (_Z18ab_GetDdicTypeLoad4RUDI+0x6e)[0xb1705e]
    (ab_GetView+0xc1d)[0xb0ee1d]
    (_Z20CompressInitRcByDatajPK6CG_DIRjjS1_jj4RUDIPKhj+0x60d)[0xe32b2d]
    (_Z21cg_CompressStackFrameP4TRIGjj+0x169)[0xe33399]
    (_Z8cg_blkleP3ENV+0x75f)[0xe4779f]
    (_Z9sc_cblklePKt8ENV_KINDP7SC_INFO+0x394)[0xe90024]
    (sc_blkle+0xdd)[0xec6e4d]
    (rs_oper_abap1729+0x37)[0x10eb237]
    (rs_expan_abap+0xa1996)[0xfd7a2a]
    (_Z8sc_expanj+0x76d)[0xe1d55d]
    (_Z5parsejPi+0x258)[0xe19998]
    (sc_check+0xb9c)[0xe1857c]
    (sc_inclu+0x5fa)[0xe0d50a]
    (rs_oper_abap2160+0x3a)[0x1115d6a]
    (rs_expan_abap+0xcd41d)[0x10034b1]
    (_Z8sc_expanj+0x76d)[0xe1d55d]
    (_Z5parsejPi+0x258)[0xe19998]
    (sc_check+0xb9c)[0xe1857c]
    (sc_checkStart+0x41)[0xe1ac51]
    (cg_generate+0xb65)[0xe57755]
    (ab_gabap+0x14a)[0xb01a5a]
    (dy_gen_abap+0x63c)[0x74428c]
    (ab_genprog+0x13d3)[0xb03d13]
    (_Z17ab_LoadProgOrTrfoPKtjPj+0xb56)[0x8f9ab6]
    (_Z11ab_LoadProgPKtj+0x11)[0x8f9ca1]
    (_Z15LoadGlobalClassPKtjjj9ClasState+0x24c)[0x958c2c]
    (_Z11FillCfixIntPK4CREFP4CFIXjj9ClasState+0x214)[0x957404]
    (_Z11ab_FillCfixtj+0x65)[0x957ae5]
    (_Z26ab_CrefToCladId_ActivateOKtPh+0x7d)[0x957b6d]
    (_Z8ab_jaboov+0x623)[0x959793]
    (_Z8ab_extriv+0x607)[0x8ba9c7]
    (_Z9ab_xeventPKt+0x1c1)[0xa1c021]
    (_Z8ab_triggv+0x9c)[0xa1c77c]
    (ab_run+0x97)[0xbde5c7]
    (N_ab_run+0x9)[0x736359]
    (dynpmcal+0x669)[0x7333b9]
    (dynppai0+0x8eb)[0x734d9b]
    (dynprctl+0x3e9)[0x733db9]
    (dynpen00+0x4a5)[0x726eb5]
    (Thdynpen00+0x359)[0x541bd9]
    (TskhLoop+0xc49)[0x54d999]
    (ThStart+0x20f)[0x55b29f]
    (DpMain+0x2da)[0x4bd49a]
    (nlsui_main+0x9)[0x4910c9]
    (main+0x33)[0x491103]
    /lib64/tls/libc.so.6(__libc_start_main+0xdb)[0x3cde51c3fb]
    Please help me to resolve the issue.
    Thanks & Regards
    SKK

    read this part again:  The ABAP runtime system detected that the Dictionary-type "WRF_POHF_KOMP_STY" changed during the flow of the transaction. As the type was already used in the old version and in the new type should be used in the same transaction in the new version, the transaction had to be cancelled to avoid inconsistencies. How to correct the error Try to restart the program
    how often had you restarted ME21N before you posted this message?
    In best case this message appears only once, because the program / or dictionary was changed while you executed ME21N
    If many times, then contact your ABAPer, because then he probably did not transport all objects that were changed, or the objects have to be regenerated in your system.

  • 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

  • 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

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

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

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

  • Runtime error while executing rule - see long text RSTRAN 301

    Hi BW Gurus,
    When I executing the DTP, the following error occured.
    Runtime error while executing rule -> see long text     RSTRAN     301
    Diagnosis
        An error occurred while executing a transformation rule:
        The exact error message is:
        The argument 'GBP' cannot be interpreted as a number
        The error was triggered at the following point in the program:
        GP46DQFOYRZTUS0QITMO07IFTS0 1137
    Appreciate any useful suggestions.
    Thanks in advance.
    Maruthi

    Guess you are doing some calculation in your routines ..based on Currency Key i.e USD or INR , GBP..etc ..it should be currency value..rather than currency key. Check your field caluclation

  • Termination error while doing me31k

    HI Experts,
    This is the sincere apology for the previous thread which was in capital letter subject" termination error while doing me31k 
    Posted: Mar 6, 2012 2:56 AM          
    HI while performing transaction ME31K I'm getting follow error
    Runtime error: DYNPRO_NOT_FOUND
    What Happened?
    Error in the ABAP application Program
    The current ABAp program "SAPLXM06" had to be terminated because it has come across a statement that unfortunately canont be executed.
    Error Analysis
    The system attempted to use dynpro 0201 in program "SAPLXM06".
    This dynpro does not exist.
    Trigger Location of Run TIme Error
    Program: SAPLXM06
    Include: MM06E00C_CUSTSCR1_HEAD_SET_DAT
    ROW: 10
    There is a Edit button, that allows you to change the subject
    Edited by: Jürgen L. on Mar 6, 2012 8:41 AM

    Dear MM user,
    Follow the documentation of this enhancement (see transaction SMOD):
    Within the documentation of enhancement MM06E005, via TA SMOD, it specifically states that if you use the enhancement you must generate six listed dynpros (screens), even if you are not using them.
    So you may goto transaction CMOD and enhance the same.
    For example, the dynpro area should be like the following:
    Calling screen No. Area Called screen No. ShortTxt
    SAPMM06E 0101 CUSTSCR1 SAPLXM06 0101 Subscreen: PO header
    SAPMM06E 0111 CUSTSCR1 SAPLXM06 0111 Subscreen: PO item
    SAPMM06E 0201 CUSTSCR1 SAPLXM06 0201 Subscreen: agreement
    Regards,
    ian Wong Loke Foong

  • Getting error while doing pgi

    i am getting an error while doing pgi, the error is 'runtime error - description of exception'
    how could i overcome this problem
    pls help me to solve this problem

    Hi,
    Consult your abaper he can give you a solution.
    Thank you,

  • Error while doing ABGL Asset Credit Memo

    Hi Friends,
    I am getting the below error while doing Asset Credit Memo in ABGL. Please help me in fix this issue.
    Balance for transaction type group 10 negative for the area 01
    Note:In Asset Explorer Fiscal year start Asset value is 98,425.45 and Change is 4768.19. So total Asset value as of now is 1,03,193.64.
    Now we are trying to do ABGL with 12,790.23 value (Transaction type is 105). System is giving the above highlighted error.
    If we give the amount 4768.19 in ABGL transaction, system is not giving any error. If we give more that that system is giving error.
    Why system is giving error even the asset has balance of 1,03,193.64? Please help me on this..
    Thanks
    Sunil

    Hi,
    If the asset has been capitalized during earlier years, use ABGF to post credit memo.  ABGL is meant for assets capitalized during the year.
    Best Regards,
    Madhu

  • Error while doing "Visulaize Plan"

    Hi,
    Before i did Visualize plan many times without any problem.Now I am getting error while doing so.
    I was able to run "Explain Plan" successfully.
    I am on HANA revision 60.
    I saved above error log and the log information is given below:
    I can identify invalid XML tag <TablesInvolved><![CDATA[raj/AN_VIZ]]></TablesInvolved> but how to fix this issue?
    I gone through various blogs related to Visulaization Plan but not found related to this issue.
    <Plan xmlns="http://www.sap.com/ndb/planviz" ID="ID_0" Type="Estimated">
    <SQL><![CDATA[SELECT KOKRS, BELNR, PERIO, SUM(MEGBTR)
    FROM "_SYS_BIC"."raj/AN_VIZ"
    GROUP BY KOKRS, BELNR, PERIO]]></SQL>
    <CompileTime>
      <Start Unit="us">1401281467643661</Start>
      <End Unit="us">1401281467658329</End>
    </CompileTime>
    <RootRelation ID="ID_0" TypeName="PROJECT" Status="Finished">
      <Name>Project</Name>
      <ExecutionType>Row Search</ExecutionType>
      <Summary><![CDATA[raj/AN_VIZ.KOKRS, raj/AN_VIZ.BELNR, raj/AN_VIZ.PERIO, SUM(raj/AN_VIZ.MEGBTR)]]></Summary>
      <Location>hanasp7:30003</Location>
      <EstimatedCost>
       <Exclusive Unit="us">2.12902e+06</Exclusive>
       <Inclusive Unit="us">2.64021e+06</Inclusive>
      </EstimatedCost>
      <EstimatedOutputCardinality>648284</EstimatedOutputCardinality>
      <Details><![CDATA[{"Projected Cols":"raj/AN_VIZ.KOKRS, raj/AN_VIZ.BELNR, raj/AN_VIZ.PERIO, SUM(raj/AN_VIZ.MEGBTR)","Project column0":"NString(4, 0)  __trex_field_NVarchar3__() ....... [3]:040:<5/7 (16B)>:
      /1/ void*  \"__rids__\" ....... [0]:NOP:<0/1 (8B)>:
      /2/ int32_t(10, 0) const := 0 ....... [1]:LOAD:<3/4 (4B)>:
      /3/ int32_t(10, 0) const := 0 ....... [2]:LOAD:<4/5 (4B)>:","Project column1":"NString(10, 0)  __trex_field_NVarchar3__() ....... [8]:040:<5/7 (16B)>:
      /1/ void*  \"__rids__\" ....... [5]:NOP:<0/1 (8B)>:
      /2/ int32_t(10, 0) const := 0 ....... [6]:LOAD:<3/4 (4B)>:
      /3/ int32_t(10, 0) const := 1 ....... [7]:LOAD:<4/5 (4B)>:","Project column2":"NString(3, 0)  __trex_field_NVarchar3__() ....... [13]:040:<5/7 (16B)>:
      /1/ void*  \"__rids__\" ....... [10]:NOP:<0/1 (8B)>:
      /2/ int32_t(10, 0) const := 0 ....... [11]:LOAD:<3/4 (4B)>:
      /3/ int32_t(10, 0) const := 2 ....... [12]:LOAD:<4/5 (4B)>:","Project column3":"Decimal(18, 3)  __typecast__() ....... [23]:076:<10/12 (16B)>:
      /1/ Fixed16(18, 3)  __trex_field_Fixed16__() ....... [19]:043:<6/8 (16B)>: 
         /1/ void*  \"__rids__\" ....... [15]:NOP:<0/1 (8B)>:
         /2/ int32_t(10, 0) const := 0 ....... [16]:LOAD:<3/4 (4B)>:
         /3/ int32_t(10, 0) const := 3 ....... [17]:LOAD:<4/5 (4B)>:
         /4/ int32_t(10, 0) const := 3 ....... [18]:LOAD:<5/6 (4B)>: 
      /2/ int32_t(10, 0) const := 18 ....... [21]:LOAD:<8/9 (4B)>:
      /3/ int32_t(10, 0) const := 3 ....... [22]:LOAD:<9/10 (4B)>:"}]]></Details>
      <Child ID="ID_8" >
      </Child>
    </RootRelation>
    <Relation ID="ID_8" TypeName="TREX_SEARCH" Status="Finished">
      <Name>Column Search</Name>
      <ExecutionType>Column Search</ExecutionType>
      <Summary><![CDATA[Aggregation on a single table]]></Summary>
      <Location>hanasp7:30003</Location>
      <EstimatedCost>
       <Exclusive Unit="us">511194</Exclusive>
       <Inclusive Unit="us">511194</Inclusive>
      </EstimatedCost>
      <EstimatedOutputCardinality>648284</EstimatedOutputCardinality>
      <TablesInvolved><![CDATA[raj/AN_VIZ]]></TablesInvolved>
      <LogicalPlan ID="ID_11" Type="Estimated">
       <RootRelation ID="ID_11" TypeName="PROJECT" Status="Finished">
        <Name>Project</Name>
        <EstimatedCost>
         <Exclusive Unit="us">0</Exclusive>
         <Inclusive Unit="us">0</Inclusive>
        </EstimatedCost>
        <EstimatedOutputCardinality>648284</EstimatedOutputCardinality>
        <Child ID="ID_12" >
        </Child>
       </RootRelation>
       <Relation ID="ID_12" TypeName="GROUP_BY" Status="Finished">
        <Name>Aggregation</Name>
        <Summary><![CDATA[raj/AN_VIZ.KOKRS, raj/AN_VIZ.BELNR, raj/AN_VIZ.PERIO\nSUM(raj/AN_VIZ.MEGBTR)]]></Summary>
        <EstimatedCost>
         <Exclusive Unit="us">0</Exclusive>
         <Inclusive Unit="us">0</Inclusive>
        </EstimatedCost>
        <EstimatedOutputCardinality>648284</EstimatedOutputCardinality>
        <Details><![CDATA[{"Grouping Cols":"raj/AN_VIZ.KOKRS, raj/AN_VIZ.BELNR, raj/AN_VIZ.PERIO","Aggregation Cols":"SUM(raj/AN_VIZ.MEGBTR)"}]]></Details>
        <Child ID="ID_13" >
        </Child>
       </Relation>
       <Relation ID="ID_13" TypeName="TABLE" Status="Finished">
        <Name>Column View</Name>
        <Schema><![CDATA[_SYS_BIC]]></Schema>
        <ObjectName><![CDATA[raj/AN_VIZ]]></ObjectName>
        <Location>hanasp7:30003</Location>
        <EstimatedCost>
         <Exclusive Unit="us">0</Exclusive>
         <Inclusive Unit="us">0</Inclusive>
        </EstimatedCost>
        <EstimatedOutputCardinality>682404</EstimatedOutputCardinality>
       </Relation>
      </LogicalPlan>
    </Relation>
    </Plan>
    Regards
    Raj

    Hi,
    To solve this you must update your studio. In lower studio versions (PlanViz) does not allow "unknown" XML tags sent by higher version servers. A fix for this issue was made so that PlanViz parser can simply skip unknown tags.
    Please go to version 74, if possible.
    Regards,
    Michael

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

  • Error while doing EHP4 upgrade in downtime phase

    HI .
    Iam facing the below error while doing the EHP4 upgrade , in downtime phase.
    Checks after phase MAIN_SWITCH/STARTSAP_TRANS were negative!
    Last error code set: RFC call to subst_get_uvers failed with key RFC_ERROR_COMMUNICATION (open): SAP_CMINIT3 : rc=20 >
    Connect to SAP gateway failed Connect_PM GWHOST=Hydhtc4526D, GWSERV=sapgw04, SYSNR=04  LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.136.162.30:3304' not reached TIME Mon Jun 06 18:17:46 2011 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.136.162.30:3304 SYSTEM CALL connect ERRNO 10061 ERRNO TEXT WSAECONNREFUSED: Connection refused COUNTER System start failed
    Please help me in resolving this error.
    Sanketh.

    Hi,
    Upgrade tool is trying to start the system but system is not coming up. Try to start system manually and see if system comes up or not. If not then check logs in work directory for why system is not coming up.
    Thanks
    Sunny

  • Runtime error while trying to convert script to pdf and sending in mail

    Hi all,
    I m trying to convert the standard script into pdf using convert_otf fm and trying to send it as an attachment using 'SO_NEW_DOCUMENT_ATT_SEND_API1'.
    I m using fm 'SSF_FUNCTION_MODULE_NAME' to get the function module name.
    But i m getting a runtime error while executing the program..
    Can anyone help me in this issue please.
    Thanks in advance,
    Ashok

    Hi Ramesh,
    I m getting an runtime error function module not found. I ll paste the code here.
    CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
        EXPORTING
          formname           = lf_formname
        IMPORTING
          fm_name            = lf_fm_name
        EXCEPTIONS
          no_form            = 1
          no_function_module = 2
          OTHERS             = 3.
      IF sy-subrc = 0.
    error handling ent_retco = sy-subrc.
    perform protocol_update_i.
      ENDIF.
      ls_control_param-getotf = 'X'.
      DATA: l_document_output_info TYPE ssfcrespd,
            l_job_output_info TYPE ssfcrescl,
            l_job_output_options TYPE ssfcresop.
    check ent_retco eq 0.
      CALL FUNCTION 'lf_fm_name'
      EXPORTING
        archive_index = toa_dara
        archive_parameters = arc_params
        control_parameters = ls_control_param
        mail_recipient = ls_recipient
        mail_sender = ls_sender
        output_options = ls_composer_param
        user_settings = ' '
        zxekko = l_doc-xekko
        zxpekko = l_doc-xpekko
    zxaend = l_doc-xaend
        IMPORTING
          document_output_info = l_document_output_info
          job_output_info = l_job_output_info
          job_output_options = l_job_output_options
          TABLES
            l_xekpo = l_doc-xekpo[]
            l_xekpa = l_doc-xekpa[]
            l_xpekpo = l_doc-xpekpo[]
            l_xeket = l_doc-xeket[]
            l_xtkomv = l_doc-xtkomv[]
            l_xekkn = l_doc-xekkn[]
            l_xekek = l_doc-xekek[]
            l_xaend = l_doc-xaend[]
            l_xkomk = l_xkomk
            EXCEPTIONS
              formatting_error = 1
              internal_error = 2
              send_error = 3
              user_canceled = 4
              OTHERS = 5.
    CALL FUNCTION 'CONVERT_OTF'
        EXPORTING
          format                = 'PDF'
          max_linewidth         = 132
        IMPORTING
          bin_filesize          = v_len_in
        TABLES
          otf                   = l_job_output_info-otfdata
          lines                 = tb_pdf
        EXCEPTIONS
          err_max_linewidth     = 0
          err_format            = 1
          err_conv_not_possible = 2
          OTHERS                = 3.

  • Error while doing  GR for scheduling aggrement

    Dear Experts,
    We are facing error while doing GR for scheduling aggrement.
    we have done the following steps.
    1) Scheduling aggreement in ME31L
    2) Released in ME35L
    3) Mainatined Sch.Agmt Schdule in ME38 for todays and date 200 qty and other line is 800 qty.
    When we are trying to do GR in MIGO system is giving the following message.
    Document 5500000152 does not contain any selectable items
    can I know what I have missed in the above steps.
    Please guide me to resolve this.
    Regards,
    Prasad

    Hi,
    Please check Please check if Gr is already done against this document.  Also please check whether you have attached SA in the source list with line items.
    T-code:ME01
    Enter Mat.code & Plant.
    In the next screen pl.do the following:
    Valid from - commencement date of the SA
    Valid to - End date of the SA
    Vendor - Vendor on whom the SA is released
    POrg - Your purchase organisation
    PPL - Leave it blank(This is only for interplant)
    OUn - Ordering unit
    Agreement - SA number
    Item - 1
    I hope this will resolve your issue. Thanking you

Maybe you are looking for

  • Is it possible to only submit/email a one page form embedded in a large document?

    Hello. I have a catalogue with numerous product enquiry forms embedded (designed in ID CS6). When one submits an enquiry form, the entire massive pdf is put into an email for sending. Is it possible to define that only the form page is emailed? Thank

  • 10.6.5 Problems with external Display

    Hi, I'm getting crazy... Yesterday Night I update my MBP to the Os 10.6.5 and this morning i try to connect my MBP to the LCD and nothing just for a few second the display change to blue trying to recognize the lcd and then nothing, can anyone tell m

  • Dock + Remote apple in the ipod 3g reset while viewing videos

    Hello. I have the following problem is my ipod nano 3g 1.1.3 connected to the dock of apple and driving with the remote apple. The problem is that the iPod is reset when you press forward or play / pause while playing videos, I have tested with the p

  • 0 fiscper3 (posting period)and 0fiscyear (fiscal year) in bw report

    Hi I need a quick help, please resolve my issue in step by step. Report is required to display the 0 fiscper3 (posting period)and 0fiscyear (fiscal year) in bw report. I have a 0fiscper Fiscal Yr / Period in my datasource and infosource but not 0fisc

  • Printing duplex from template - won't flip

    When I use the Birthday Card template and wish to print it using the duplex feature of my printer, the second page does not print upside down (or whatever that orientation should be). When printed, the card when folded would have page 2 - with the me