PA30, PA40 Showing dump error

Hi Experts,
When i run the tcode PA30 and PA40  getting short dump attached here with.
Kindly suggest how to overcome from this issue.
Our current SAP_HR support pack level is SAPKE60429
Thanks,
Narasimhan Krishna

Category               ABAP Programming Error
Runtime Errors         SYNTAX_ERROR
ABAP Program           /1PAPAXX/HDR_80004A
Application Component  Not Assigned
Date and Time          06.04.2014 19:11:29
|Short text                                                                                        |
|    Syntax error in program "/1PAPAXX/HDR_80004A ".                                               |
|What happened?                                                                                    |
|    Error in the ABAP Application Program                                                         |
|                                                                                                  |
|    The current ABAP program "SAPFP50M" had to be terminated because it has                       |
|    come across a statement that unfortunately cannot be executed.                                |
|                                                                                                  |
|    The following syntax error occurred in program "/1PAPAXX/HDR_80004A " in                      |
|     include "/1PAPAXX/HDR_80004AO01 " in                                                         |
|    line 44:                                                                                      |
|    ""LV_LENGTH" has already been declared"                                                       |
|    " "                                                                                           |
|    " "                                                                                           |
|    " "                                                                                           |
|                                                                                                  |
|    The include has been created and last changed by:                                             |
|    Created by: "BONIN "                                                                          |
|    Last changed by: "SAPUSER "                                                                   |
|    Error in the ABAP Application Program                                                         |
|                                                                                                  |
|    The current ABAP program "SAPFP50M" had to be terminated because it has                       |
|    come across a statement that unfortunately cannot be executed.                                |
|What can you do?                                                                                  |
|    Please eliminate the error by performing a syntax check                                       |
|    (or an extended program check) on the program "/1PAPAXX/HDR_80004A ".                         |
|    You can also perform the syntax check from the ABAP Editor.                                   |
|                                                                                                  |
|    If the problem persists, proceed as follows:                                                  |
|    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                                                                                    |
|    The following syntax error was found in the program /1PAPAXX/HDR_80004A :                     |
|    ""LV_LENGTH" has already been declared"                                                       |
|    " "                                                                                           |
|    " "                                                                                           |
|    " "                                                                                           |
|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 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..... 702                                                                          |
|    SAP Basis Level. 0011                                                                         |
|                                                                                                  |
|    Application server... "JKTSAPBLR2"                                                            |
|    Network address...... "192.168.10.181"                                                        |
|    Operating system..... "Windows NT"                                                            |
|    Release.............. "6.1"                                                                   |
|    Hardware type........ "4x AMD64 Level"                                                        |
|    Character length.... 16 Bits                                                                  |
|    Pointer length....... 64 Bits                                                                 |
|    Work process number.. 1                                                                       |
|    Shortdump setting.... "full"                                                                  |
|                                                                                                  |
|    Database server... "JKTSAPBLR2"                                                               |
|    Database type..... "MSSQL"                                                                    |
|    Database name..... "JED"                                                                      |
|    Database user ID.. "jed"                                                                      |
|                                                                                                  |
|    Terminal.......... "BLR-FNTT8R1"                                                              |
|                                                                                                  |
|    Char.set.... "C"                                                                              |
|                                                                                                  |
|    SAP kernel....... 721                                                                         |
|    created (date)... "Dec 4 2013 15:53:05"                                                       |
|    create on........ "NT 5.2 3790 S x86 MS VC++ 14.00"                                           |
|    Database version. "SQL_Server_9.00 "                                                          |
|                                                                                                  |
|    Patch level. 201                                                                              |
|    Patch text.. " "                                                                              |
|                                                                                                  |
|    Database............. "MSSQL 9.00.2047 or higher"                                             |
|    SAP database version. 721                                                                     |
|    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows                |
|     NT 6.0, Windows NT 6.1, Windows NT 6.2, Windows NT 6.3"                                      |
|                                                                                                  |
|    Memory consumption                                                                            |
|    Roll.... 0                                                                                    |
|    EM...... 25138752                                                                             |
|    Heap.... 0                                                                                    |
|    Page.... 311296                                                                               |
|    MM Used. 7058688                                                                              |
|    MM Free. 5507568                                                                              |
|User and Transaction                                                                              |
|    Client.............. 800                                                                      |
|    User................ "SAPUSER"                                                                |
|    Language key........ "E"                                                                      |
|    Transaction......... "PA30 "                                                                  |
|    Transaction ID...... "0791BDE33448F14DA9F5005056AF3C2B"                                       |
|                                                                                                  |
|    EPP Whole Context ID.... "005056AF3C2B1EE3AFB21F7FE7D409F5"                                   |
|    EPP Connection ID....... 00000000000000000000000000000000                                     |
|    EPP Caller Counter...... 0                                                                    |
|                                                                                                  |
|    Program............. "SAPFP50M"                                                               |
|    Screen.............. "MP000700 1000"                                                          |
|    Screen Line......... 3                                                                        |
|    Debugger Active..... "none"                                                                   |
|Information on where terminated                                                                   |
|    Termination occurred in the ABAP program "SAPFP50M" - in                                      |
|     "GET_HEADER_WITH_TCLAS".                                                                     |
|    The main program was "MP000700 ".                                                             |
|                                                                                                  |
|    In the source code you have the termination point in line 146                                 |
|    of the (Include) program "FP50MDHD".                                                          |
|Source Code Extract                                                                               |
|Line |SourceCde                                                                                   |
|  116|  CALL FUNCTION 'HR_HEADER_GET'                                                             |
|  117|      EXPORTING                                                                             |
|  118|           DHDID                    = FHD_HID                                               |
|  119|           BEGDA                    = BEGDA                                                 |
|  120|           TCLAS                    = TCLAS                                                 |
|  121|* Es wird nur einer der folgenden 3 Parameter benutzt.                                      |
|  122|* Ausgewertet wird zunaechst MOLGA, dann P0001 dann PERNR.                                  |
|  123|* Der erste der nicht initial ist wird ausgewertet.                                         |
|  124|*           MOLGA                   =                                                       |
|  125|           P0001                    = P0001                                                 |
|  126|           PERNR                    = PSPAR-PERNR                                           |
|  127|      IMPORTING                                                                             |
|  128|           PROG                     = HEADER_PROG                                           |
|  129|           DNUM                     = HEADER_DYNNR                                          |
|  130|       EXCEPTIONS                                                                           |
|  131|            HEADER_DEACTIVATED          = 1                                                 |
|  132|            HEADER_UNKNOWN              = 2                                                 |
|  133|            HEADER_GENERATE_DEACTIVATED = 3                                                 |
|  134|            HEADER_GENERATE_FAILED      = 4                                                 |
|  135|            INTERNAL_ERROR              = 5                                                 |
|  136|            OTHERS                      = 6.                                                |
|  137|                                                                                            |
|  138|  IF NOT SY-SUBRC IS INITIAL.                                                               |
|  139|* Bei Problemen gibt's eben ein leeres Dynpro.                                              |
|  140|    HEADER_PROG = 'SAPMP50A'.                                                               |
|  141|    HEADER_DYNNR = '0090'.                                                                  |
|  142|  ELSE.  " NOT sy-subrc IS INITIAL.                                   "                     |
|  143|* Dann setzen wir jetzt auch noch das Datum fest.                                           |
|  144|    PERFORM HEADER_BEGDA_SET IN PROGRAM (HEADER_PROG) USING BEGDA.                          |
|  145|* Und schalten auf Uebergabe der PERNR mit globalen Variablen.                              |
|>>>>>|    PERFORM HEADER_LAZY_ON IN PROGRAM (HEADER_PROG).                                        |
|  147|  ENDIF.  " (ELSE) NOT sy-subrc IS INITIAL.                           "                     |
|  148|* Merken wie der Header heisst. Damit MPPERS00 sich erinnern kann.                          |
|  149|* Wird mit Einfuehrung des Headerobjekts obsolet.                                           |
|  150|  PERFORM REMEMBER_HEADER  "                             "XYVPH4K015649                     |
|  151|    USING HEADER_PROG HEADER_DYNNR 'S'.  "               "XYVPH4K015649                     |
|  152|ENDFORM.                                                                                    |
|  153|*---------------------------------------------------------------------*                     |
|  154|*       FORM RE588I                                                   *                     |
|  155|*---------------------------------------------------------------------*                     |
|  156|*       ........                                                      *                     |
|  157|*---------------------------------------------------------------------*                     |
|  158|*  -->  T588I_DHDID                                                   *                     |
|  159|*  -->  T588I_MOLGA                                                   *                     |
|  160|*  -->  T588I_TCLAS                                                   *                     |
|  161|*---------------------------------------------------------------------*                     |
|  162|FORM RE588I USING T588I_DHDID T588I_MOLGA T588I_TCLAS.      "QNUR3                          |
|  163|  CLEAR SY-SUBRC.                                           "QNUK64192                      |
|  164|  CHECK T588I-DHDID NE T588I_DHDID OR T588I-MOLGA NE T588I_MOLGA                            |
|  165|     OR T588I-TCLAS NE T588I_TCLAS.                                                         |
|Contents of system fields                                                                         |
|Name    |Val.                                                                                     |
|SY-SUBRC|0                                                                                        |
|SY-INDEX|0                                                                                        |
|SY-TABIX|1                                                                                        |
|SY-DBCNT|1                                                                                        |
|SY-FDPOS|0                                                                                        |
|SY-LSIND|0                                                                                        |
|SY-PAGNO|0                                                                                        |
|SY-LINNO|1                                                                                        |
|SY-COLNO|1                                                                                        |
|SY-PFKEY|                                                                                         |
|SY-UCOMM|                                                                                         |
|SY-TITLE|Planned Working Time Infotype (0007)                                                     |
|SY-MSGTY|                                                                                         |
|SY-MSGID|                                                                                         |
|SY-MSGNO|000                                                                                      |
|SY-MSGV1|                                                                                         |
|SY-MSGV2|                                                                                         |
|SY-MSGV3|                                                                                         |
|SY-MSGV4|                                                                                         |
|SY-MODNO|0                                                                                        |
|SY-DATUM|20140406                                                                                 |
|SY-UZEIT|191129                                                                                   |
|SY-XPROG|SAPMSSY1                                                                                 |
|SY-XFORM|XAB_READ                                                                                 |
|Active Calls/Events                                                                               |
|No.   Ty.          Program                             Include                             Line   |
|      Name                                                                                        |
|    6 FORM         SAPFP50M                            FP50MDHD                              146  |
|      GET_HEADER_WITH_TCLAS                                                                       |
|    5 FORM         SAPFP50M                            FP50MDHD                              144  |
|      GET_HEADER_WITH_TCLAS                                                                       |
|    4 FORM         SAPFP50M                            FP50MDHD                               96  |
|      GET_HEADER                                                                                  |
|    3 FORM         SAPFP50M                            FP50MDHD                               61  |
|      FILL_HEADER                                                                                 |
|    2 FORM         SAPFP50M                            FP50ME00                              417  |
|      INIT_DIALOG                                                                                 |
|    1 MODULE (PBO) MP000700                            MPPERS00                              575  |
|      INIT_DIALOG                                                                                 |
|Chosen variables                                                                                  |
|Name                                                                                              |
|    Val.                                                                                          |
|No.       6 Ty.          FORM                                                                     |
|Name  GET_HEADER_WITH_TCLAS                                                                       |
|SY-REPID                                                                                          |
|    SAPFP50M                                                                                      |
|    5454533422222222222222222222222222222222                                                      |
|    3106050D00000000000000000000000000000000                                                      |
|    0000000000000000000000000000000000000000                                                      |
|    0000000000000000000000000000000000000000                                                      |
|    53004100500046005000350030004D0020002000200020002000200020002000200020002000200020002000200020|
|T582A-DAVO                                                                                        |
|    1                                                                                             |
|    3                                                                                             |
|    1                                                                                             |
|    0                                                                                             |
|    0                                                                                             |
|    3100                                                                                          |
|SYST-REPID                                                                                        |
|    SAPFP50M                                                                                      |
|    5454533422222222222222222222222222222222                                                      |
|    3106050D00000000000000000000000000000000                                                      |
|    0000000000000000000000000000000000000000                                                      |
|    0000000000000000000000000000000000000000                                                      |
|    53004100500046005000350030004D0020002000200020002000200020002000200020002000200020002000200020|
|PSHDR-PSKEY-PERNR                                                                                 |
|    00000000                                                                                      |
|    33333333                                                                                      |
|    00000000                                                                                      |
|    00000000                                                                                      |
|    00000000                                                                                      |
|    30003000300030003000300030003000                                                              |
|%_SPACE                                                                                           |
|                                                                                                  |
|    2                                                                                             |
|    0                                                                                             |
|    0                                                                                             |
|    0                                                                                             |
|    2000                                                                                          |
|PSYST-BEGDA                                                                                       |
|    20140406                                                                                      |
|    33333333                                                                                      |
|    20140406                                                                                      |
|    00000000                                                                                      |
|    00000000                                                                                      |
|    32003000310034003000340030003600                                                              |
|DELETE                                                                                            |
|    DEL                                                                                           |
|    44422222222222222222                                                                          |
|    45C00000000000000000                                                                          |
|    00000000000000000000                                                                          |
|    00000000000000000000                                                                          |
|    440045004C0020002000200020002000200020002000200020002000200020002000200020002000              |
|PSINFO[]                                                                                          |
|    Table IT_0[6x80]                                                                              |
|    \PROGRAM=SAPFP50M\DATA=PSINFO[]                                                               |
|    Table reference: 0                                                                            |
|    TABH+  0(20) = 50240D00DF070000000000000000000000000000                                       |
|    TABH+ 20(20) = 00000000000000000600000050000000FFFFFFFF                                       |
|    TABH+ 40(16) = 04000000709C020005000000C104C000                                               |
|    store        = 0x50240D00DF070000                                                             |
|    ext1         = 0x0000000000000000                                                             |
|    shmId        = 0     (0x00000000)                                                             |
|    id           = 0     (0x00000000)                                                             |
|    label        = 0     (0x00000000)                                                             |
|    fill         = 6     (0x06000000)                                                             |
|    leng         = 80    (0x50000000)                                                             |
|    loop         = -1    (0xFFFFFFFF)                                                             |
|    xtyp         = TYPE#000105                                                                    |
|    occu         = 5     (0x05000000)                                                             |
|    accKind      = 1     (ItAccessStandard)                                                       |
|    idxKind      = 0     (ItIndexNone)                                                            |
|    uniKind      = 2     (ItUniNo)                                                                |
|    keyKind      = 1     (default)                                                                |
|    cmpMode      = 2     (cmpSingleMcmpR)                                                         |
|    occu0        = 0                                                                              |
|    stMode       = 0                                                                              |
|    groupCntl    = 0                                                                              |
|    rfc          = 0                                                                              |
|    unShareable  = 0                                                                              |
|    mightBeShared = 0                                                                             |
|    sharedWithShmTab = 0                                                                          |
|    isShmLockId  = 0                                                                              |
|    isUsed       = 1                                                                              |
|    isCtfyAble   = 1                                                                              |
|    hasScndKeys  = 0                                                                              |
|    hasRowId     = 0                                                                              |
|    scndKeysOutdated = 0                                                                          |
|    scndUniKeysOutdated = 0                                                                       |
|    ----- Shareable Table Header Data -----                                                       |
|    tabi         = 0xA0220D00DF070000                                                             |
|    pgHook       = 0xE0631100DF070000                                                             |
|    idxPtr       = 0x0000000000000000                                                             |
|    id           = 2     (0x02000000)                                                             |
|    shmTabhSet   = 0x0000000000000000                                                             |
|    refCount     = 0     (0x00000000)                                                             |
|    tstRefCount  = 0     (0x00000000)                                                             |
|    lineAdmin    = 125   (0x7D000000)                                                             |
|    lineAlloc    = 13    (0x0D000000)                                                             |
|    shmVersId    = 0     (0x00000000)                                                             |
|    shmRefCount  = 1     (0x01000000)                                                             |
|    rowId        = 18446744073709551615                                                           |
|    scndKeyAdmin = 0x0000000000000000                                                             |
|                                                                                                  |
|    0000002000011800010199991231A    1    ##                                                      |
|    3333333333333333333333333333422223222201                                                      |
|    000000200001180001019999123110000100000C                                                      |
|    0000000000000000000000000000000000000000                                   

Similar Messages

  • PCUI showing dump errors after EEWB enhancement

    Hi Experts,
    I'm using CRM5.0.
    After adding some fields by EEWB(Easy Enhancement Workbench) the PCUI application showing several dump errors in several places. How to correct this problem, should I regenerate all the layout by CRMC_BLUEPRINT or any other way is there to correct these errors. Please suggest a solution for that.This is very urgent.
    Thanks In Advance
    Rana

    Hi Fred,
    1>
    Whenever I'm clicking  F4 help button beside service prospect,contact person etc the following dump is coming as in opportunity transaction (CRMD_BUS2000111) likewise other transactions also.
    Note
         The following error text was processed in the system CS1 : CRM_BSP_LIBRARY:structureEdit: Act. table parameter gt_layout is empty
         The error occurred on the application server nmpcsssb1_CS1_01 and in the work process 0 .
         The termination type was: ERROR_MESSAGE_STATE
         The ABAP call stack was:
    Method: IF_BSP_ELEMENT~DO_AT_BEGINNING of program CL_CRM_BSP_STRUCTUREEDIT======CP
    What can I do?
         If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system CS1 in transaction ST22.
         If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server nmpcsssb1_CS1_01 in transaction SM21.
         If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server nmpcsssb1_CS1_01 . In some situations, you may also need to analyze the trace files of other work processes.
         If you do not yet have a user ID, contact your system administrator.
    Error code: ICF-IE-http -c: 500 -u: ABAP1 -l: E -s: CS1 -i: nmpcsssb1_CS1_01 -w: 0 -d: 20070521 -t: 115438 -v: ERROR_MESSAGE_STATE -e: CRM_BSP_LIBRARY:structureEdit: Act. table parameter gt_layout is empty
    HTTP 500 - Internal Server Error
    Your SAP Internet Communication Framework Team
    second error:
    2>
    Whenever any business partner is selected in partner id of  partner tab ,partner fn(sold-to-party) then it is showing the following dump error.
    SAP Note
         The following error text was processed in the system:
    An exception with the type CX_SY_DYN_CALL_PARAM_NOT_FOUND occurred, but was neither handled locally, nor declared in a RAISING clause
    Exception Class     CX_SY_DYN_CALL_PARAM_NOT_FOUND
    Error Name     
    Program     CL_CRM_BSP_INTLAY_PARTNER=====CP
    Include     CL_CRM_BSP_INTLAY_PARTNER=====CM002
    ABAP Class     CL_CRM_BSP_INTLAY_PARTNER
    Method     PUT_DATA
    Line     1269
    Long text     Call of the function CRM_PARTNER_GET_COM_BY_STRUCT failed: The formal parameter ET_RETURN_VALUES does not exist.
    EEWB used to add a field Account No in Service order transaction.
    which is now reflecting to all the transaction as a customer field.
    Thanks
    Koustav

  • Regarding dump error in smartforms

    hi experts,
                   my one driver program along with smartforms is working fine in the development server after transportation to production server it is showing dump error :::
    the error is:
    Function module " " not found.                                                                
    What happened?                                                                               
    The function module " " was called, but cannot be                                             
        found in the Function Library.                                                                               
    Error in ABAP application program.                                                                               
    The current ABAP program "ZSD_DELIVERY_ORDER_DRIVER_PREP" 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?                                                                               
    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.                                                                               
    is especially useful if you want to keep a particular message.                                
    Error analysis                                                                               
    An exception occurred. This exception will be dealt with in more detail                       
        below. The exception, assigned to the class 'CX_SY_DYN_CALL_ILLEGAL_FUNC', was                
         not caught, which                                                                               
    led to a runtime error. The reason for this exception is:                                    
        The program "ZSD_DELIVERY_ORDER_DRIVER_PREP" contains a CALL FUNCTION                         
         statement. The name                                                                               
    of the function module to be called is " ".                                                                               
    No function module exists with the name " ".                                                  
        All function modules are stored in the Function Library (SE37).                                                                               
    Possible reasons:                                                                               
    a) Wrong name specified. Particular attention should be paid                                  
           to upper/lower case and underscores ("_")                                                  
        b) Transport error                                                                               
    c) If an enqueue/dequeue module has been used, the lock object                                
           may not have been activated (ABAP Dictionary)                                              
           may not have been activated (ABAP Dictionary).                                             
    i have checked in the production server but i m not finding <b>" "</b> this thing in the program ..plz help me to solve this.

    Hi Ravi,
    Can you show me the code where you have called the smart form in driver program.Becaus the FM generated in Development server may differ from the FM generated in Production server.Make sure u r passing the FM  which is generated from the function module SSF_FUNCTION_MODULE_NAME.

  • Regarding dump error in MMBE

    hi experts good morning,
                      when i execute tc mmbe it is showing dump error sometimes back it worked fine and now it is showing dump error ,,i m giving the error below plz have a look and help me.....
    ShrtText
        Syntax error in program "SAPLMBBS ".
    What happened?
        Error in ABAP application program.
        The current ABAP program "RMMMBESTN" 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 "SAPLMBBS ", the following syntax error occurred
        in the Include "LMBBSU07 " in line 75:
        "The column name "WAERS" has two meanings. ABAP/4 Open SQL statement."
        Author and last person to change the Include are:
        Author "SAP "
        Last changed by "SAP "
    Error analysis
        In program "SAPLMBBS ", the following syntax error occurred:
        "The column name "WAERS" has two meanings. ABAP/4 Open SQL statement."
    Trigger Location of Runtime Error
        Program                                 RMMMBESTN
        Module type                             (FORM)
        Module Name                             EKPO_LESEN

    Hi,
    Please find the SAP notes. There are several notes for this.
    Regards,

  • While saving the delivery no in VA02 dump error showing (Arithmatic overflo

    Hi,
    while saving the delivery no in VA02, one dump error getting displayed.
    Arithmatic over flow occurs.
    Can any one can say how to rectify the program to avoid dump error
    The below lines are showing in dump.
    Waiting for quick response.
    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 "USEREXIT_SAVE_DOCUMENT_PREPARE" "(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:                                                       
                   An overflow was discovered in an ongoing arithmetical operation with                                                       
                   operands of type P. Possible causes are:                                                       
                   1. The result field of type P is too small for the result.                                                       
                   2. The result or a intermediate result has more than 31 decimal places.                                                       
         How to correct the error                                                                 
                   The result field must be enlarged, if this is still possible. It may                                                       
                   also be possible to break up the current process into subprocesses so                                                       
                   that only smaller values occur.                                                       
                   There may already be a solution to the error in the SAP notes system.                                                       
                   If you have access to the SAP notes system first try searching with the                                                       
                   following keywords:                                                       
                    "COMPUTE_BCD_OVERFLOW"                                                       
                    "BCD_FIELD_OVERFLOW" (Until release 4.0a, this runtime error occurred at this                                                       
                    position)                                                       
                    "SAPMV50A" or "ZSDI_MV50AFZ1_CRPC_CALC_4QA"                                                       
                    "USEREXIT_SAVE_DOCUMENT_PREPARE"               ***----
         Information on where terminated                                                                 
                   Termination occurred in the ABAP program "SAPMV50A" - in                                                       
                    "USEREXIT_SAVE_DOCUMENT_PREPARE".                                                       
                   The main program was "SAPMV50A ".                                                       
                   In the source code you have the termination point in line 666                                                       
                   of the (Include) program "ZSDI_MV50AFZ1_CRPC_CALC_4QA".                                                       
                   The termination is caused because exception "CX_SY_ARITHMETIC_OVERFLOW"                                                       
                    occurred in                                                       
                   procedure "USEREXIT_SAVE_DOCUMENT_PREPARE" "(FORM)", but it was neither handled                                                       
                    locally nor declared                                                       
                   in the RAISING clause of its signature.                                                       
                   The procedure is in program "SAPMV50A "; its source code begins in line                                                       
                   208 of the (Include program "MV50AFZ1 ".
    657                           ADD: xvbap-brgew TO l_w_tot_list_vals-brgew,                                                  
         658                                xvbap-zzlogpoint TO l_w_tot_list_vals-zlogpoint,                                                  
         659                               xvbap-zztotgrossvalue TO                                                  
         660                               l_w_tot_list_vals-totgrossvalue.                                                  
         661                                                                 
         662                                                                 
         663                           l_w_tot_list_vals-gewei = xvbap-gewei.                                                  
         664                                                                 
         665                           IF NOT xvbap-pstyv IN zzt_free.                                                  
         >>>>>                             ADD xvbap-volum TO l_w_tot_list_vals-volum.                                                  
         667                           ELSE.                                                  
         668                             ADD xvbap-volum TO l_w_tot_list_vals-volum_f.                                                  
         669                           ENDIF.                                                  
         670                           ADD 1 TO l_w_tot_list_vals-zw_nbitem.
    Best Regards,
    BDP
    Edited by: Bansidhar Padhy on Jan 26, 2010 8:24 AM

    ADD xvbap-volum TO l_w_tot_list_vals-volum.
    Declare l_w_tot_list_vals-volum as  "like vbap-volum" or (preferably) "type volum_ap".
    If you're using a packed decimal, you've done something like....  volum(5) type p decimals 2, which is a great way to get an overflow...if you use packed decimals in a program...declare <field> type p decimals <n> without a length attribute, so that SAP can use the full 8 bytes for the calculation.....the put it into a alpha field for display, if needed....

  • Error in creating Table Maintenance for TABLES: J_2IRG1BAL ,Dump error show

    Dear Gurus
    I have Created one Table Maintenance for TABLES: J_2IRG1BAL ,
    1) I have take function group as same as table name like J_2IRG1BAL
    3) Authorization Group  &NC&
    4) Authorization object S_TABU_DIS
    5) Function group  J_2IRG1BAL
    6) Package J1I5
    7) Maintenance type one step.
    8) Maint. Screen No.    Overview screen 2009.
    9) Recording routine STD recording routines .
    I have assign screen single screen 1 but it will not take the screen so ill put screen 2009 ,the system will not not accept the screen but I proposed to Save and activate the table maintenance generator  and created and save the function group ,the table is ready to save the entries
    We have to go to SM30 then put 4-5 entries ,after that a dump error shows
    Which i have attachéd in this mail kindly help me out
    Its effect in production server.
    I have found that the error is given below I have mentioned all the details
    Kindly read this 
    I have created function group J_2IRG1BAL and  assign Package J1I5 and function group,J1I5 is already a Function group so problem occurs a dump error message displays
    Kindly give me the right solution all the Clients are effected
    110,100 150,250 these all are effected development clients
    300 is prod client this is also affected  because I have created a table maintenance generator and send the req to production .
    *Dump Error Shows in Production*
    Runtime Errors         SYNTAX_ERROR
    Date and Time          11.12.2008 09:26:30
    What happened?                                                                               
    |    Error in ABAP application program.                                                                               
    Error analysis
    In program "SAPLJ1I5 ", the following syntax error occurred:
    "The program "SAPLJ1I5" is not Unicode-compatible, according to its pro"
    "gram attributes."
    The current ABAP program "SAPLSVIM" 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 "SAPLJ1I5 ", the following syntax error occurred
    in the Include "SAPLJ1I5 " in line 0:
    "The program "SAPLJ1I5" is not Unicode-compatible, according to its pro"
    "gram attributes."
    rigger Location of Runtime Error                                                                 |
    Program                                 SAPLSVIM
    Include                                 LSVIMU01
    Row                                     107
    Module type                             (FUNCTION)
    |    Module Name                             VIEW_MAINTENANCE 
    Author and last person to change the Include are:
    Author "TTLABAP2 "
    Last changed by "TTLABAP2 "                 
    105
    Initialisierung des Abgleichsmandanten zum View                     *
    106
    >>>>>
    vim_default_upgr_clnt-viewname = x_header-viewname.
    108
    vim_default_upgr_clnt-client   = client_for_upgrade.
    109
    PERFORM vim_set_global_field_value IN PROGRAM (fpool)
    |  110|            USING 'VIM_DEFAULT_UPGR_CLNT' 'C' vim_default_upgr_clnt rc.

    I have send you all the details regarding the table maintenance generator
    error is shown below
                                           I have Created one Table Maintenance for TABLES: J_2IRG1BAL ,
    1) I have take function group as same as table name like J_2IRG1BAL
    3) Authorization Group  &NC&
    4) Authorization object S_TABU_DIS
    5) Function group  J_2IRG1BAL
    6) Package J1I5
    7) Maintenance type one step.
    8) Maint. Screen No.    Overview screen 2009.
    9) Recording routine STD recording routines .
    I have assign screen single screen 1 but it will not take the screen so ill put screen 2009 ,the system will not not accept the screen but I proposed to Save and activate the table maintenance generator  and created and save the function group ,the table is ready to save the entries
    We have to go to SM30 then put 4-5 entries ,after that a dump error shows
    Which i have attachéd in this mail kindly help me out
    Its effect in production server.
    I have found that the error is given below I have mentioned all the details
    Kindly read this 
    I have created function group J_2IRG1BAL and  assign Package J1I5 and function group,J1I5 is already a Function group so problem occurs a dump error message displays
    Kindly give me the right solution all the Clients are effected
    110,100 150,250 these all are effected development clients
    300 is prod client this is also affected  because I have created a table maintenance generator and send the req to production .
                                                                                    Runtime Errors         SYNTAX_ERROR
    Date and Time          11.12.2008 09:26:30
    ShrtText
    Syntax error in program "SAPLJ1I5 ".
    What happened?
    Error in ABAP application program.
    The current ABAP program "SAPLSVIM" 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 "SAPLJ1I5 ", the following syntax error occurred
    in the Include "SAPLJ1I5 " in line 0:
    "The program "SAPLJ1I5" is not Unicode-compatible, according to its pro"
    "gram attributes."
    Author and last person to change the Include are:
    Author "TTLABAP2 "
    Last changed by "TTLABAP2 "
    Error analysis
    In program "SAPLJ1I5 ", the following syntax error occurred:
    "The program "SAPLJ1I5" is not Unicode-compatible, according to its pro"
    "gram attributes."
    Trigger Location of Runtime Error
    Program                                 SAPLSVIM
    Include                                 LSVIMU01
    Row                                     107
    Module type                             (FUNCTION)
    Module Name                             VIEW_MAINTENANCE
    Source Code Extract
    Line
    SourceCde
    77
    TRANSPORTING NO FIELDS.
    78
    IF sy-subrc NE 0.
    79
    SELECT SINGLE * FROM tfdir WHERE funcname EQ <function_name>.
    80
    IF sy-subrc NE 0.
    81
    RAISE no_editor_function.
    82
    ELSE.
    83
    length = strlen( function_name1 ).
    84
    ASSIGN function_name1(length) TO <function_name>.
    85
    SELECT SINGLE * FROM tfdir WHERE funcname EQ <function_name>.
    86
    IF sy-subrc NE 0.
    87
    RAISE no_database_function.
    88
    ENDIF.
    89
    ENDIF.
    90
    INSERT x_header-viewname INTO alr_checked_views INDEX sy-tabix.
    91
    ELSE.
    92
    length = strlen( function_name1 ).
    93
    ASSIGN function_name1(length) TO <function_name>.
    94
    ENDIF.
    95
    96
    Initialisierung der RFC-Destination zum View                        *
    97
    98
    FPOOL+4 = X_HEADER-AREA.
    99
    fpool   = x_header-fpoolname.
    100
    vim_default_rfc_dest-viewname = x_header-viewname.
    101
    vim_default_rfc_dest-rfcdest  = rfc_destination_for_upgrade.
    102
    PERFORM vim_set_global_field_value IN PROGRAM (fpool)
    103
    USING 'VIM_DEFAULT_RFC_DEST' 'C' vim_default_rfc_dest rc.
    104
    105
    Initialisierung des Abgleichsmandanten zum View                     *
    106
    >>>>>
    vim_default_upgr_clnt-viewname = x_header-viewname.
    108
    vim_default_upgr_clnt-client   = client_for_upgrade.
    109
    PERFORM vim_set_global_field_value IN PROGRAM (fpool)
    110
    USING 'VIM_DEFAULT_UPGR_CLNT' 'C' vim_default_upgr_clnt rc.
    111
    112
    set flag if complex selection conditions in sellist                  *
    113
    114
    IF complex_selconds_used NE space.
    115
    READ TABLE dba_sellist INDEX 1.
    116
    IF sy-subrc EQ 0 AND dba_sellist-cond_kind EQ space.
    117
    dba_sellist-cond_kind = 'C'. MODIFY dba_sellist INDEX 1.
    118
    ENDIF.
    119
    ENDIF.
    120
    121
    direkter Vergleich: Flagge setzen usw.                              *
    122
    123
    IF view_action EQ vim_direct_upgrade.
    124
    view_action = aendern.
    125
    PERFORM vim_set_global_field_value IN PROGRAM (fpool)
    126
    USING 'VIM_SPECIAL_MODE' 'C' vim_direct_upgrade rc.

  • When  i executed program , it go to dump, show this error

    Hi Gurs
    when  i executed program , it go to dump, show this error .
    Short text                                                   
         The ABAP program lines are wider than the internal table.
    Error in the ABAP Application Program                                                                               
    The current ABAP program "SAPLSKBH" had to be terminated because it has 
    come across a statement that unfortunately cannot be executed.          
    it show this lines.
        read report l_prog_tab_local into l_abap_source.          
      366 *      catch cx_sy_read_src_line_too_long into ex_too_long.   
      367 *    endtry.                                                  
      368     check sy-subrc eq 0.
    Edited by: Rob Burbank on Feb 17, 2010 2:54 PM

    d022s length is only 72 char
    so u have to copy D022S Structure  to ZD022S Structure and
    and define  like  LINE  CHAR(data type)  1500(length)
    then u define internal table like
    data: begin of itab occurs 0.
            include structure  Zd022s.
    data: end of itab.

  • Authorisation error with PA30/PA40 transaction

    Hi Experts,
    In our system, the transactions PA30/PA40 are giving some authorisation error
    (No read/maintain authorisation for Personal Data) for all operations
    create/change/display of data. (even though in su01 transaction,
    we have given all authorisations SAP_ALL under profiles and also removed all roles)
    Also checked the possibility of any custom BADI getting called, but none exists.
    Any solutions / suggestions are appreciated.
    Thanks in Advance,
    Mirza.

    Hi!
    Right after you have the authority error, enter the following transaction code /NSU53.
    SU53 trasnaction will collect the missing autority objects.
    Regards
    Tamá

  • Dump error while creating a new page in smartforms URGENT pls!!!

    while creating a new page it is showing me a dump error , that the superior program execption was not intercepted , i have even given the next page field also correctly, i have attached a mainwindow to that page and a text element to that . .
    thanks
    sridhar

    Hi Deena,
    This error:
    "[2012-07-10T14:50:30.005+05:30] [wls_ods1] [ERROR] [] [oracle.adfinternal.view.faces.config.rich.RegistrationConfigurator] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000JXkC9dU3FClqwsJb6G1FyhO000003D,0] [APP: odsm#11.1.1.2.0] Server Exception during PPR, #7[[
    javax.servlet.ServletException: Could not initialize class com.octetstring.vde.admin.services.client.VDEAdminServiceSoapBindingStub"
    is known issue
    Go to metalink, article: Unable To Connect To OVD 11g Webinterface Using ODSM. [ID 1282757.1]
    You need to apply that patch.
    I hope this helps,
    Thiago Leoncio.

  • Short dump error report

    What is the purpose of short dump error report generated by the system? What r the major parts/section of this report?

    hi please look through this:
    Whenever any transaction or any process is executed it hits an ABAP code.
    If there is any issue in executing the code the situation is called "ABAP DUMP" or 'Short Dump'
    Transaction ST22 is used to check any ABAP Dump within a given duration.
    U can also fix the issue with the help of ABAP editor (Transaction Code SE38) if u r good with ABAP.
    you can select back to the last 14 days if you are
    running the SAP_REORG_ABAPDUMPS job (program RSSNAPDL) which deletes te
    old ABAP dumps every day, possibly further if you run it weekly or
    monthly.
    sap-basis   sap-basisAll Groups  Ignore this text box. It is used to detect spammers.If you enter anything into this text box, no search results will be displayed.
    SAP Groups > Technical-functional > sap-basis > Message
    About This Group | Invite peers to join this group 
    << Prev thread  < Prev msg  Next msg >  Next thread >> 
    short dump----urgent
    Reply from Keith Lewis on 5/2/2003 3:22:00 AM 
    Good explanation Joy, but it is not only limited to the current day and
    yesterday. If you click on the Selection button you can select previous
    days as well. In fact you can select back to the last 14 days if you are
    running the SAP_REORG_ABAPDUMPS job (program RSSNAPDL) which deletes te
    old ABAP dumps every day, possibly further if you run it weekly or
    monthly.
    Cheers
    Keith
    SAP R/3 Support Specialist
    Information Services International
    Tel +44 1664 41 6178 Mobile +44 7887 627818
    E-mail email@removed
    Archive Page - http://www.ittoolbox.com//I/sap-r3-basis.asp
    Dear sreenivas
    If you receive an error message in the R/3 System log (SM21), or if you
    see
    a terminated update in the update service analysis transaction (SM13), or
    DB
    realated error ,check for dumps using the dump analysis transaction
    (transaction ST22), or choose Tools -> Administration -> Monitoring ->
    Dump
    analysis.
    Transaction ST22 enables you to analyze short dumps from the current and
    previous day.
    The dump analysis function shows you:
    What happened
    What you can do
    How to correct the error
    The dump analysis function also provides an error ID and keywords that you
    can use to search in SAPNet, as well as information about:
    The system environment
    Users and transactions
    Transaction ST22 enables you to analyze the following data:
    Date, time, user, client
    Contents of system and data fields
    Contents of internal tables and application tables
    ST22 is a very nice feature in SAP. This is where all the system errors
    and users mistakes showed up. If there is a problem that you cannot
    solve and you contact SAP support, they look at this area to analyze it.
    This gives us lead where to handle the problems.
    Error analysis
    How to correct the error
    System environment
    User, transaction...
    Information on where termination occurred
    Contents of system fields
    Chosen variables
    Active calls / events
    Internal notes
    Active calls in SAP kernel
    List of ABAP programs affected
    List of internal tables
    Directory of application tables (contents)
    Directory of data areas (administration information)
    Directory of data areas (contents)
    ABAP control blocks CONT
    End of runtime analysis
    i think this would be helpful
    regards
    sravani

  • Short dump error when using count(*)

    Hi Experts
    I am getting a short dump error when selecting the records >= current date - 30 see the coding and comment please correct the coding I want to know the ztable records it is important for command interface.
    I have 1402345 records available after deleting the records but as the memory is not enough it is giving short dump error
    select count(*) from ZINT_TABLE
    select count(*) from ZINT_MSGS
       select * from zint_data
                 nto table izint_d2 . "PACKAGE SIZE 20000
       where STATUS = 'OK' AND CREATED_ON >= w_date1.          " VALUE
    endselect.**
    report z_eslp_command_records.
    data: cnt type i.
    data: cnt2 type i.
    data: cnt3 type i.
    data: cnt4 type i.
    DATA:
         w_date1 like sy-datum .
    DATA:
         w_date2 like sy-datum.
    data: izint_msgs type table of zint_msgs.
    data: izint_data type table of zint_data.
    data: izint_m2 type table of zint_msgs.
    data: izint_d2 type table of zint_data.
    INITIALIZATION.
    w_date1 = sy-datum -  30.
    w_date2 = sy-datum -  30.
    select * from zint_data
                 into table izint_data PACKAGE SIZE 3000
                 where STATUS = 'OK' AND CREATED_ON <= w_date1.   " ZERO
    endselect.
    select * from zint_msgs
                 into table izint_msgs  PACKAGE SIZE 3000
                  where  CREATED_ON <= w_date2.              " ZERO
    endselect.
      select * from zint_data
                 into table izint_d2 PACKAGE SIZE 20000
       where STATUS = 'OK' AND CREATED_ON >= w_date1.          " VALUE
    endselect.
    select * from zint_msgs
                 into table izint_m2 PACKAGE SIZE 20000
      where CREATED_ON >= w_date2.                            " VALUE
      endselect.
    select * from zint_data
                into table izint_data2
    where STATUS = 'OK' AND CREATED_ON >= CONVERT(CHAR(8), GETDATE() - 30, 112)).
    ENDSELECT.
      select * from zint_msgs
                into table izint_msgs2
    where CREATED_ON >= CONVERT(CHAR(8), GETDATE() - 30, 112)).
    ENDSELECT.
    sort izint_data by created_on ascending.
    sort izint_msgs by created_on ascending.
    sort izint_d2 by created_on ascending.
    sort izint_m2 by created_on ascending.
    describe table izint_data lines cnt.
    describe table izint_msgs lines cnt2.
    describe table izint_d2 lines cnt3.
    describe table izint_m2 lines cnt4.
    write:/ ' Note: THE RECORDS COUNTED SHOULD SHOW ZERO ELSE THE SCRIPT FAILED TO RUN' color 3.
    skip.
    write:/ '1. Records counted in ZINT_DATA   <=current date - 30                   :' color 2,                        cnt color 4.
    write:/ '2. Records available in ZINT_DATA >=current date - 30                   'color 4,                   cnt3 color 4 .
    skip.
    write:/ '2. Records counted in ZINT_MSGS   <=current date - 30                   :' color 2                 ,                      cnt2 color 4.
    write:/ '4. Records available in ZINT_MSGS >=current date - 30                   'color 4  ,            cnt4 color 4 .
    TOP-OF-PAGE.
    WRITE:/55(60) ' WAGNERS INVESTMENT LIMITED  '.
    WRITE:/50(40) ' Command Interface Data' CENTERED .
      WRITE:/50(40) '----
    ' CENTERED .
      FORMAT INTENSIFIED ON.
      SKIP.
      "FORMAT COLOR COL_HEADING.
      ULINE.
      FORMAT COLOR 1.
    END-OF-PAGE.

    Answer

  • Dump error while filling the Setup table

    Hi All,
    I am trying to fill the setup table.While filling the stup table for 2lis_03_BF datasource, i got the Dump error after some time. I have checked the data in Setup table and found 9000 records.
    Shall i proceed further by pulling the data from R/3 to BW.I have checked the data in RSA3 and got some data.
    Shall i schedule the data from BW side.
    Pls help on this issue.
    Thanks,
    Siva.

    Thanks Reddy and JS.
    I have checked the TCODE SM37 and found no jobs are available. I have checked the TCODE : NPRT and found some logs.In this, it is not showing any errors.
    I have checked in SM21 and found some errors.
    Time_______________Text
    17:08:10____________Transaction Canceled M2 630 ( )
    17:23:47____________Run-time error "TIME_OUT" occurred
    17:23:47____________> Short dump "090302 172347 sand1_W2 2_00 " generated
    17:30:08____________Status: 80% of IL00.DAT is in use
    17:30:17____________Status: 90% of IL00.DAT is in use
    17:30:18____________Overflow of Paging File (032768 Blocks)
    17:30:18____________Run-time error "MEMORY_NO_MORE_PAGING" occurred
    17:30:19____________> Short dump "090302 173018 sand1_W2 2_00 " generated
    Shall i execute filling the setup table again. Do i need to give termination time More ( 2 Hrs difference)
    Any issue on refilling the setup table again.
    Pls suggest.
    Thanks,
    Siva.

  • Dump error while running termination action

    I'm facing a dump error while running termination action, please, if some one wud help me out of this error. here when im termination action the system is opening action infotype when given the date of termination and try to save, system shows a warning message that "Record valid from 08.08.1995 to 31.12.9999 delimited at end" then I press enter and system is asking me to save. when I do so, rather than it taking me to another screen its throwing a dump error.
    Runtime Errors         SYNTAX_ERROR
    Date and Time          21.10.2008 18:54:05
    Short dump has not been completely stored (too big)
    Short text
         Syntax error in program "SAPLCACS_BU_PARTNER ".
    What happened?
         Error in the ABAP Application Program
         The current ABAP program "SAPLBUD_CHECK" had to be terminated because it has
         come across a statement that unfortunately cannot be executed.
         The following syntax error occurred in program "SAPLCACS_BU_PARTNER " in
          include "LCACS_BU_PARTNERU44 " in
         line 19:
         "The key of internal table "LT_BUT0BK" contains components of type "X" "
         "or "XSTRING". The "READ TABLE LT_BUT0BK" statement is not permitted fo"
         "r such tables in a Unicode context."
         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 "SAPLBUD_CHECK" 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 SAPLCACS_BU_PARTNER :
         "The key of internal table "LT_BUT0BK" contains components of type "X" "
         "or "XSTRING". The "READ TABLE LT_BUT0BK" statement is not permitted for
    "r such tables in a Unicode context."
    ger Location of Runtime Error
    Program                                 SAPLBUD_CHECK
    Include                                 LBUD_CHECKF01
    Row                                     1.129
    Module type                             (FORM)
    Module Name                             RLDEL_CHECK
    ce Code Extract
      SourceCde
    9
    0 *------ ... Funktionsbausteine ermitteln -
    1   CALL FUNCTION 'BDT_TBZ1F_GET'
    2     EXPORTING
    3       iv_objcn  = gc_objcn_bupa
    4       iv_objap  = gc_objap_bupa
    5     TABLES
    6       et_tbz1f  = lt_tbz1f
    7     EXCEPTIONS
    8       not_found = 1
    9       OTHERS    = 2.
    0   READ TABLE lt_tbz1f INDEX 1.
    1   IF sy-subrc = 0.
    2     CALL FUNCTION 'BUP_PARTNER_GET'
    3       EXPORTING
    4         i_partner    = is_but100-partner
    5         i_cp_exclude = gc_x
    i_is_exclude = gc_x
    PORTING
    e_but000_int = ls_but000_int
    CEPTIONS
    OTHERS       = 1.
    ... Funktionsbausteine aufrufen -
    T lt_tbz1f WHERE     ztpkt =  'RLDEL'
                 AND NOT fname IS INITIAL.
    Datümer alt = neu = SPACE => Löschung, sonst Update -
    (Einschränkung der Gültigkeit)
    FUNCTION lt_tbz1f-fname
    PORTING
    i_partner        = is_but100-partner
    i_partnerguid    = ls_but000_int-partner_guid
    i_role           = is_but100-rltyp
    i_dfval          = is_but100-dfval
    i_calltp         = iv_calltp
    i_valid_from     = is_but100-valid_from_dats
    i_valid_from_old = iv_valid_from_old
    i_valid_to       = is_but100-valid_to_dats
    i_valid_to_old   = iv_valid_to_old
    PORTING
    e_result         = lv_result.
    ... Ergebnis merken, wenn höher als bisheriges Zwischenergebnis-
    v_result > gv_wu_result.                          "#EC PORTABLE
    wuresult = lv_result.
    F.
    ... Ergebnis ist 'Nicht löschen': Zeitpunkt abbrechen -

    HI Mallik,
    for termination action the operation that i've set is
    lis9  0001
    cop  0002
    lis9  0007
    cop  0008
    lis9  0014
    lis9  0015
    lis9  0587
    so just want to know if the set format for termination action is right
    and other option is that if there is some change to settings of infotype charateristics in table v_t582A this may cause change in the date that is cause of error.
    can u please suggest the above alignment of operations and infotype is right and provide me the idle settings for infotype characteristics which may solve my query.
    thanks mallik.

  • At the time of RFQ creation dump error

    Dear All,
                        At the time of RFQ creation one Dump error is coiming... please advise to solve this issue...
    the error message is :
    Runtime errors         SYNTAX_ERROR
           Occurred on     09.09.2009 at   12:10:27
    Syntax error in program "SAPLV61A ".
    What happened?
    The following syntax error occurred in the program SAPLV61A :
    "Incorrect logical expression: Instead of "X" a field, a function or "("
    Error in ABAP application program.
    The current ABAP program "SAPLMEVA" 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 "SAPLV61A ".
    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 SAPLV61A :
    "Incorrect logical expression: Instead of "X" a field, a function or "("
    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.
    System environment
    SAP Release.............. "620"
    Application server....... "ARCHIVAL"
    Network address.......... "172.26.2.145"
    Operating system......... "Windows NT"
    Release.................. "5.2"
    Hardware type............ "4x Intel 80686"
    Character length......... 8 Bits
    Pointer length........... 32 Bits
    Work process number...... 0
    Short dump setting....... "full"
    Database server.......... "ARCHIVAL"
    Database type............ "MSSQL"
    Database name............ "EDP"
    Database owner........... "dbo"
    Terminal................. "cheeid92corit"
    Character set............ "English_United State"
    SAP kernel............... "640"
    Created on............... "Mar 9 2009 22:54:07"
    Created in............... "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
    Database version......... "SQL_Server_9.00 "
    Patch level.............. "274"
    Patch text............... " "
    Supported environment....
    Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
    SAP database version..... "640"
    Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2,
    Windows NT 6.0"
    User, transaction...
    Client.............. 777
    User................ "MMCORE"
    Language key........ "E"
    Transaction......... "ME47 "
    Program............. "SAPLMEVA"
    Screen.............. "SAPMM06E 0311"
    Screen line......... 54
    Information on where terminated
    The termination occurred in the ABAP program "SAPLMEVA" in
    "ME_LOAD_VARIANTS_PRICING".
    The main program was "SAPMM06E ".
    The termination occurred in line 55 of the source code of the (Include)
    program "LMEVAU08"
    of the source code of program "LMEVAU08" (when calling the editor 550).
    Source code extract
    000250       ENDIF.
    000260   *--> Initialisieren
    000270   *--> not necessary anymore (Raimond Buchholz)
    000280   *   CALL FUNCTION 'CUD0_CONFIGURATION_INITIALIZER'.
    000290   *--> Preisteile der Varianten besorgen
    000300       CALL FUNCTION 'CEI0_GET_CONDITIONS'
    000310            EXPORTING
    000320                 INSTANCE    = I_CUOBJ
    000330                 APPLICATION = 'MM'
    000340            TABLES
    000350   *              CONDITIONS  = T_VCKEY.                 "del 194053
    000360                 CONDITIONS  = T_VCKEY                   "ins 194053
    000370            exceptions                                   "ins 194053
    000380                 error_message  = 01                     "ins 194053
    000390                 others         = 02.                    "ins 194053
    000400   *--> Preisteile der Varianten mit Belegnummer versorgen
    000410       LOOP AT T_VCKEY.
    000420         T_VCKEY-KAPPL = 'M '.
    000430         T_VCKEY-VBELN = I_EBELN.
    000440         T_VCKEY-POSNR = I_EBELP.
    000450         MODIFY T_VCKEY.
    000460       ENDLOOP.
    000470     ENDIF.
    000480
    000490   *--> Preisteile der Varianten an Preisfindung übergeben
    000500   *- pricing_load_variant_key muß auch bei Positionen ohne Konfiguration
    000510   *- laufen, da die Logik im PRICING zu 4.0 umgestellt wurde
    000520     IF I_NO_LOAD IS INITIAL.
    000530       DATA: I_POSNR LIKE VBAP-POSNR.
    000540       I_POSNR = I_EBELP.
          CALL FUNCTION 'PRICING_LOAD_VARIANT_KEYS'
    000560            EXPORTING
    000570                 APPLICATION = 'M '
    000580                 VBELN       = I_EBELN
    000590                 POSNR       = I_POSNR
    000600            TABLES
    000610                 TVCKEY      = T_VCKEY
    000620            EXCEPTIONS
    000630                 OTHERS      = 1.
    000640     ENDIF.
    000650
    000660   ENDFUNCTION.
    Contents of system fields
    SY field contents..................... SY field contents.....................
    SY-SUBRC 0                             SY-INDEX 0
    SY-TABIX 1                             SY-DBCNT 1
    SY-FDPOS 1                             SY-LSIND 0
    SY-PAGNO 0                             SY-LINNO 1
    SY-COLNO 1                             SY-PFKEY GVP
    SY-UCOMM
    SY-TITLE Maintain Quotation : Item 00001
    SY-MSGTY E                             SY-MSGID AIPLOC
    SY-MSGNO 002                           SY-MSGV1 303632
    SY-MSGV2                               SY-MSGV3
    SY-MSGV4
    Kind regards
    P.Anandhakumar

    Hi Anandhakumar,
    Debugg the transaction with help of ABAPER.
    System will show you the reason for the above error.
    Hope this should solve your problem.
    Thanks and regards 
    Gitesh

  • I purchased bioshock 2 on the app store on my macbook pro (running lion) and it shows 'an error has occured' every time I try to download the app. How do I install it properly, I have restarted my mac and reset the app on the debug menu?

    I purchased bioshock 2 on the app store on my macbook pro (running lion) and it shows 'an error has occured' every time I try to download the app. How do I install it properly, I have restarted my mac and reset the app on the debug menu?

    If you have more than one user account, these instructions must be carried out as an administrator.
    Launch the Console application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
    Select "/var/log/install.log" from the file list on the left. If you don't see that list, select
    View ▹ Show Log List
    from the menu bar. Then select the messages from the last installation or update attempt, starting from the time when you initiated it. If you're not sure when that was, start over and note the time. Copy them to the Clipboard (command-C). Paste into a reply to this message (command-V).
    If there are runs of repeated messages, post only one example of each. Don’t post many repetitions of the same message.
    When posting a log extract, be selective. Don't post more than is requested.
    Please do not indiscriminately dump thousands of lines from the log into this discussion.
    Important: Some private information, such as your name, may appear in the log. Edit it out by search-and-replace in a text editor before posting.

Maybe you are looking for

  • Print Html page Using Java

    I need to print Html Page into my printer, how can I do this. Any help will be appreciated. Wil

  • 10.5.2 and Windows 2003 Domain and Home Folders

    Hello, This has probably been beaten to death but cant seem to find the answer that I'm looking for. I can add the mac to the 2003 domain fine with no problems and can get the user authentication fine, access to the network shares and printers. The q

  • CFFORM onSubmit script works in FF but not in IE

    I've got a CFFORM that has an onSubmit additional javascript for  form validation, and while it works in FF, it passes right through in IE and ends up erroring because the mandatory fields aren't there... the CFFORM call looks like this <cfform name=

  • How to change the disabled value color of messageTextInput

    Hi, I have a requirement to change the value color of messageTextInput. And I had apply custom look and feel. For normal messageTextInput, I can change its color, but for disabled messageTextInput, the value is always gray out. I can't change its col

  • Problem in Calling a smartform in a driver program(SE38)

    Hi,       I created a report in SE38 and i have a 5 CHECK Boxes. i called a smartformsin that program. My problem is if i check the 5 check boxes the layout should show 5 copies. if i check 3 check boxes the layout should show 3 copies. e.t.c. Edited