Short run time

Hi all,
I have wrote and modified this code. There's no error in the code, but I am having hard time of fixing the run time. It runs only up to maximum of 350 iteration. I wanted to run until I receive a true value; before it gets there it just says PASS which is my true value. But the computation is not true. Below is an attachment of my code. If you have any idea how to fix this please make suggestion.
Thank you in advance
Solved!
Go to Solution.
Attachments:
tachounter.vi ‏45 KB

I went ahead and cleaned up your code so that there is only 1 error path, removed locals, only close the serial port once, and (best of all) removed the sequence structures.  Yes, the VI looks long, but that's fine.  I would highly recommend making subVIs for each of your tasks (what you used to have as sequence steps).  See if this works for you.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
Attachments:
tachounter.vi ‏25 KB

Similar Messages

  • In  iTunes: why different run times for same track?

    I have occasional repeats of the same given track stored in iTunes. Sometimes, the 2 identical tracks show different running times. This happens when one track came from the Net (downloaded before I started using iTunes, then imported into iTunes) and the other comes from a commercial CD. Do you know why the differing times? FYI: In each case, I have checked the endings of both tracks; they are identical, so the music is the same even though one track is rated to run [much] longer than the other. Also, in "Get Info" there's a way to change the running time of a track, but this is no solution: if I enter a shorter run time, the track will truncate itself, and finish playing before the proper end of the song -- if I enter a longer time, I get dead air after the end of the recording. Any ideas?
      Windows XP  
      Windows XP Pro  
      Windows XP Pro  

    "will iphone users in Singapore have access to application from other countries? "
    No. You can buy from the itunes store in the country in which you reside.
    Each country has the same rules:
    "SINGAPORE ONLY. The Service is available to you only in Singapore and is not available in any other location. You agree not to use or attempt to use the Service from outside of the available territory. iTunes may use technologies to verify such compliance."
    http://www.apple.com/legal/itunes/appstore/sg/terms.html#APPS

  • Run time error (short dump) executing program SCAN_BW_REFERENCES in SE80

    Hi experts,
    I am not an ABAPer, or Basis person, rather a hybrid functional/technical Key User for our Business Warehouse system (BW 3.5, Netweaver 2004).  We have a user who cannot save BW reports to his favorites and he is getting a number of error messages.  OSS note 887002 seems to address this and indicates that I should run program SCAN_BW_REFERENCES from transaction SE80.  The program is supposed to perform the checks for BW objects assigned to the Favorites and identify situations causing terminations in BW frontend applications.  I have attempted to execute this program on several occassions and always get run-time errors (short dumps).  Here is the error:
    Runtime Errors         TSV_TNEW_PAGE_ALLOC_FAILED
    Date and Time          2008.09.17 19:00:49
    ShrtText
         No storage space available for extending an internal table.
    What happened?
         You attempted to extend an internal table, but the required space was
         not available.
    I have been informed by our Basis group that I have reached a memory limit, but they will not extend the memory paramters.  Any ideas on a work-a-round or a way to minimize the number of records this program is pulling in, in an attempt to get it to run?
    Thanks,
    HC

    Hi,
    The only response I got from Basis was that they would not extend the memory parameters because they are for all users in the system.  Not sure what that means. 
    The full dump is too large to paste here.  I think what I will do is to see if our ABAPers can create a modified version of this program to include selection by user.  Typically it is for only one user that I need to run the program, and that surely would fall within the space requirements.
    Thanks for your answer.
    //HC

  • Error run time  DYNPRO_FIELD_CONVERSION

    I have a dump:
    Errore run-time        DYNPRO_FIELD_CONVERSION
           Verific. il     28.11.2007 h  02:12:16
    A conversion error occurred.
    Causa dell'errore
    The current screen processing was terminated, since a situation
    occurred from which it could not continue processing.
    This is probably due to an error in the current screen of the ABAP
    program.
    Possibili soluzioni
    Make a note of the actions and input which caused the error.
    To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
    termination messages, especially those beyond their normal deletion
    date.
    Analisi errori
    The program flow was interrupted and could not be resumed.
    Program "SAPMM06B" tried to display fields on screen 0106. However, an
    error occurred while this data was being converted.
    Indic. per la correzione
    A conversion error occurred while the program was trying to
    display data on the screen.
    The ABAP output field and the screen field may not have the
    same format.
    Some field types require more characters on the screen than
    in the ABAP program. For example, a date field on a screen needs
    two characters more than it would in the program. When attempting to
    display the date on the screen, an error will occur that triggers the
    error message.
                  Screen name.............. "SAPMM06B"
                  Screen number............ 0106
                  Screen field............. "EBAN-MENGE"
                  Error text............... "FX015: Sign lost."
    Further data:
    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.
    It is probably not possible to eliminate the system error
    with ABAP alone.
    If you have access to SAPnet, you can search for a relevant note
    using the following keywords:
    "DYNPRO_FIELD_CONVERSION" " "
    "SAPMM06B" bzw. "MM06BO0R_RM06B-EPSTP"
    "RM06B-EPSTP"
    Ambiente sistema
    SAP Release.............. "620"
    Application server....... "assapoa"
    Network address.......... "10.58.19.23"
    Operating system......... "AIX"
    Release.................. "5.2"
    Hardware type............ "00CB585E4C00"
    Character length......... 8 Bits
    Pointer length........... 64 Bits
    Work process number...... 26
    Short dump setting....... "full"
    Database server.......... "ars005sapdb"
    Database type............ "ORACLE"
    Database name............ "PRD"
    Database owner........... "SAPR3"
    Character set............ "it_IT.ISO8859-1"
    SAP kernel............... "640"
    Created on............... "Jul 16 2006 20:40:53"
    Created in............... "AIX 1 5 00538A4A4C00"
    Database version......... "OCI_920 "
    Patch level.............. "139"
    Patch text............... " "
    Supported environment....
    Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
    10.2.0.."
    SAP database version..... "640"
    Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"
    Utente, transazione.....
    Client.............. 300
    User................ "CONSULENTI"
    Language key........ "I"
    Transaction......... "ME52 "
    Program............. "SAPMM06B"
    Screen.............. "SAPMM06B 0106"
    Screen line......... 26
    Informazioni punto di interr.
    The termination occurred in the ABAP program "SAPMM06B" in "RM06B-EPSTP".
    The main program was "SAPMM06B ".
    The termination occurred in line 14 of the source code of the (Include)
    program "MM06BO0R_RM06B-EPSTP"
    of the source code of program "MM06BO0R_RM06B-EPSTP" (when calling the editor
    140).
    The program "SAPMM06B" was started as a background job.
    Errore verificatosi durante un'elaborazione Batch-Input
    Dettaglio cd. sorgente
    000010   *eject
    000020   *----
    000030   * Positionstyp aufbereiten                                             *
    000040   *----
    000050   MODULE RM06B-EPSTP OUTPUT.
    000060
    000070   CALL FUNCTION 'ME_ITEM_CATEGORY_OUTPUT'
    000080        EXPORTING
    000090             PSTYP = EBAN-PSTYP
    000100        IMPORTING
    000110             EPSTP = RM06B-EPSTP
    000120             PTEXT = T163Y-PTEXT.
    000130
      ENDMODULE.
    Contenuto campi sistema
    Cmpo SY  Contenuto.................... Cmpo SY  Contenuto....................
    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 VU
    SY-UCOMM
    SY-TITLE Richiesta d'acquisto mod.: Riepilogo pos.
    SY-MSGTY                               SY-MSGID
    SY-MSGNO 000                           SY-MSGV1
    SY-MSGV2                               SY-MSGV3
    SY-MSGV4
    Richiami/eventi attivi
    N..... Tipo........ Nome..........................
           Programma
           Include                                  Riga
           Classe
         1 MODULE (PBO) RM06B-EPSTP
           SAPMM06B
           MM06BO0R_RM06B-EPSTP                        14
    Variabili selezionate
         1 MODULE (PBO) RM06B-EPSTP
           SAPMM06B
           MM06BO0R_RM06B-EPSTP                        14
    DIEN                           DIEN
                                   4444
                                   495E
    EBAN-PSTYP                     0
                                   3
                                   0
    LIM                            LIM
                                   4442
                                   C9D0
    RM06B-EPSTP
                                   2
                                   0
    POTE                           TXP
                                   5552
                                   4800
    T163Y-PTEXT                    Standard
                                   57666676222222222222
                                   341E4124000000000000
    Chiamate applicazione
    Il dump non riporta informazioni relative
    Informazioni applicazione
    Il dump non riporta informazioni relative
    Note interne
    The termination occurred in the function "dynpconv.c" of the SAP
    Basis System, specifically in line 701 of the module
    "//bas/640_REL/src/krn/dynp/dybas.c#4".
    The internal operation just processed is "ENDM".
    The internal session was started at 20071128021215.
    Application server....... "assapoa"
    Network address.......... "10.58.19.23"
    Operating system ........ "AIX"
    Release.................. "5.2"
    Hardware type............ "00CB585E4C00"
    Database server.......... "ars005sapdb"
    Database type............ "ORACLE"
    Database name............ "PRD"
    Database user ID......... "SAPR3"
    Rich. attivi nel nucleo SAP
    => 64 bit R/3 Kernel
    => 64 bit AIX Kernel
    => Heap limit      = unlimited
    => Stack limit     = unlimited
    => Core limit      = 1073741312
    => File size limit = unlimited
    => Heap address  = 0x11dd952a0
    => Stack address = 0xfffffffffffa920
    => Stack low     =  0xfffffffffffa920
    => Stack high    =  0xffffffffffff910
    => Stack Trace:
         AixStack() at 0x1000206bc
         CTrcStack2() at 0x1000207b4
         rabax_CStackSave__Fv() at 0x1001520d4
         ab_rabax() at 0x10014ef04
         dyHandleError() at 0x1005a6850
         dypcnvoXt() at 0x100cbd6cc
         dynplend() at 0x1010cf268
         dynpmcal() at 0x1010c6f60
         dynppbo0() at 0x1010c5134
         dynprctl() at 0x1010ce40c
         dynpen00() at 0x100bd0c30
         Thdynpen00() at 0x1000a1f7c
         TskhLoop() at 0x1000a5298
         tskhstart() at 0x1000bb0d8
         DpMain() at 0x101579ca0
         nlsui_main() at 0x10154d428
         __start() at 0x1000002fc
    !!! Invalid stack address encountered: 0x0
    !!! Stack corrupted.
    Lista dei programmi ABAP in oggetto
    Tipo
    Programma
    DataGen   Ora
    Dim.car.
    Prg
    SAPMM06B
    25.09.2007 16:07:55
    514048
    Prg
    SAPMSSYD
    05.06.2002 17:09:33
    16384
    Prg
    SAPFSYSCALLS
    14.02.2002 14:22:47
    6144
    Typ
    T160
    12.05.1997 15:22:15
    2048
    Prg
    SAPFMMEX
    18.11.2007 09:34:59
    177152
    Typ
    TSTCT
    14.02.1998 14:31:34
    2048
    Typ
    TMED
    27.08.1994 21:59:16
    2048
    Typ
    TPRG
    14.02.1998 14:06:12
    2048
    Typ
    T160D
    11.02.2000 14:20:36
    5120
    Typ
    T160V
    14.05.1998 22:44:11
    6144
    Typ
    T168T
    28.08.1997 09:05:04
    2048
    Prg
    SAPLMEXF
    18.11.2007 09:35:00
    166912
    Typ
    T162
    02.10.2001 13:56:13
    2048
    Prg
    SAPLSTUP
    17.06.2004 12:05:43
    65536
    Prg
    SAPLCNDP
    17.06.2004 15:06:47
    163840
    Prg
    SAPFGUICNTL
    09.01.2003 17:18:52
    20480
    Prg
    SAPLOLEA
    17.06.2004 15:12:42
    78848
    Prg
    SAPLSGUI
    09.01.2003 17:15:12
    31744
    Prg
    SAPLSTTM
    17.06.2004 15:08:30
    75776
    Prg
    SAPLSBDC
    07.01.2003 18:31:25
    38912
    Prg
    SAPLSFES
    17.06.2004 15:15:58
    174080
    Prg
    SAPLURFC
    17.06.2004 14:25:28
    16384
    Prg
    SAPLSPLUGIN
    14.02.2002 14:22:48
    6144
    Typ
    SWCBCONT
    15.11.2000 17:55:11
    3072
    Typ
    OLE_VERBS
    04.04.1995 16:02:20
    2048
    Typ
    OLE_PA
    04.04.1995 16:02:19
    2048
    Prg
    SAPLSCNT
    14.02.2002 14:22:47
    24576
    Prg
    SAPSHDTV
    17.06.2004 11:46:16
    28672
    Typ
    EBANW
    17.06.2004 15:55:16
    21504
    Prg
    CL_CONTEXTFIELD_MM============CP
    25.09.2007 16:07:49
    9216
    Prg
    /1BCDWBEN/SAPLMEN0000
    18.11.2007 09:35:16
    237568
    Prg
    SAPLSENA
    17.06.2004 14:19:40
    28672
    Typ
    EBAN
    13.11.2006 11:19:59
    20480
    Prg
    CL_PROCESS_STATE_MM===========CP
    25.09.2007 16:07:50
    16384
    Prg
    SAPLSWUG
    17.06.2004 14:22:25
    53248
    Typ
    SWCONT
    04.04.1995 16:18:01
    2048
    Typ
    OBJ_RECORD
    14.02.1998 08:30:43
    2048
    Typ
    SWOTOBJID
    04.05.1995 15:20:52
    2048
    Typ
    SWHACTOR
    04.04.1995 16:18:07
    2048
    Prg
    CL_GOS_MANAGER================CP
    11.04.2001 13:02:00
    17408
    Prg
    CL_GOS_VIEW_MANAGER===========CP
    24.01.2002 20:31:22
    22528
    Typ
    SIBFLPOR
    15.11.2000 17:53:54
    2048
    Typ
    SGOS_MVOBJ
    24.07.2001 09:18:06
    3072
    Typ
    BORIDENT
    28.08.1997 08:38:50
    2048
    Prg
    SAPLSUU1
    17.06.2004 15:13:06
    165888
    Typ
    USR02
    17.06.2004 15:05:37
    7168
    Typ
    USREFUS
    07.01.2003 18:24:17
    2048
    Typ
    SIBFLPORB
    15.11.2000 17:53:55
    2048
    Prg
    CL_GOS_TOOLBOX_MODEL==========CP
    17.06.2004 15:04:37
    38912
    Typ
    SGOS_MODL
    24.07.2001 09:18:05
    4096
    Typ
    OBJ_RECORD
    14.02.1998 08:30:43
    2048
    Prg
    SAPLSWOR
    17.06.2004 15:08:55
    270336
    Typ
    SWOTRI
    03.01.1996 15:29:13
    2048
    Typ
    SWOTRETURN
    20.08.1998 10:59:29
    3072
    Prg
    SAPLSWOH
    14.02.2002 14:22:48
    7168
    Typ
    SWOTENV
    11.02.2000 14:20:34
    4096
    Typ
    TOJTD
    15.11.1995 03:08:46
    2048
    Prg
    SAPLRHS0
    14.02.2002 14:22:47
    11264
    Prg
    SAPLSDIFRUNTIME
    17.06.2004 14:20:44
    82944
    Typ
    DFIES
    09.11.2000 14:07:05
    8192
    Typ
    X031L
    15.11.2000 18:03:28
    5120
    Prg
    SAPLSDNT
    17.06.2004 12:06:43
    199680
    Prg
    SAPLSUGS
    21.11.2002 10:20:02
    29696
    Typ
    TOJTD
    15.11.1995 03:08:46
    2048
    Typ
    TOJTB
    14.02.1998 14:02:55
    8192
    Typ
    SWOTLI
    04.04.1995 17:30:59
    2048
    Typ
    T100
    28.08.1997 09:04:45
    2048
    Prg
    CL_EXITHANDLER================CP
    17.06.2004 15:04:37
    26624
    Prg
    CL_ABAP_TYPEDESCR=============CP
    17.06.2004 14:19:33
    21504
    Prg
    CL_ABAP_ELEMDESCR=============CP
    17.06.2004 14:19:13
    18432
    Prg
    CL_ABAP_DATADESCR=============CP
    17.06.2004 14:19:13
    14336
    Prg
    CL_ABAP_REFDESCR==============CP
    17.06.2004 14:19:33
    16384
    Prg
    CL_ABAP_STRUCTDESCR===========CP
    17.06.2004 14:19:33
    19456
    Prg
    CL_ABAP_COMPLEXDESCR==========CP
    17.06.2004 14:19:13
    13312
    Prg
    CL_ABAP_TABLEDESCR============CP
    17.06.2004 14:19:33
    17408
    Prg
    CL_ABAP_CLASSDESCR============CP
    17.06.2004 14:19:33
    23552
    Prg
    CL_ABAP_OBJECTDESCR===========CP
    17.06.2004 14:19:33
    25600
    Prg
    CL_ABAP_INTFDESCR=============CP
    17.06.2004 14:19:13
    19456
    Prg
    CL_ABAP_SOFT_REFERENCE========CP
    29.03.2001 16:42:12
    7168
    Prg
    CL_ABAP_REFERENCE=============CP
    14.02.2002 14:22:46
    6144
    Prg
    IF_EX_GOS_SRV_SELECT==========IP
    04.12.2000 16:22:18
    4096
    Prg
    %_CABAP
    07.01.2003 18:31:23
    23552
    Typ
    SXS_INTER
    30.11.1998 15:55:16
    2048
    Prg
    SAPLSEXV
    17.06.2004 15:04:40
    106496
    Prg
    CL_BADI_FLT_DATA_TRANS_AND_DB=CP
    17.06.2004 15:04:37
    33792
    Typ
    SXS_ATTR
    20.08.2001 12:23:27
    4096
    Typ
    V_EXT_ACT
    09.11.2000 14:27:05
    2048
    Typ
    SXC_EXIT
    09.11.2000 14:23:43
    2048
    Prg
    CL_EX_GOS_SRV_SELECT==========CP
    17.06.2004 15:04:37
    13312
    Prg
    %_CSXRT
    17.06.2004 15:04:37
    11264
    Prg
    CL_EXIT_MASTER================CP
    17.06.2004 15:04:37
    13312
    Typ
    V_EXT_IMP
    09.11.2000 14:27:05
    2048
    Typ
    V_EXT_IMP
    09.11.2000 14:27:05
    2048
    Prg
    SAPLBDLS
    17.06.2004 11:45:48
    176128
    Typ
    T000
    11.09.1997 10:17:18
    4096
    Typ
    SWOTRTIME
    14.02.1998 10:19:46
    3072
    Prg
    %_CSWOB
    14.02.2002 14:22:46
    13312
    Typ
    SWOTINVOKE
    14.02.1998 10:18:40
    6144
    Typ
    SWOTLV
    04.12.2000 14:59:45
    10240
    Prg
    SAPLSWCD
    17.06.2004 15:06:55
    78848
    Prg
    RBUS2105
    13.11.2006 11:20:02
    57344
    Prg
    CL_GOS_PUBLICATION============CP
    13.11.2000 16:31:37
    15360
    Prg
    SAPLSGOSHIST
    17.06.2004 14:23:50
    46080
    Typ
    EBKN
    16.06.2004 13:09:57
    9216
    Typ
    T161
    16.06.2004 13:14:35
    5120
    Typ
    T161T
    14.02.1998 10:55:58
    2048
    Typ
    CMMDA
    18.09.2001 10:02:31
    4096
    Prg
    SAPLMMDA
    04.09.2006 11:00:54
    65536
    Typ
    TWLAD
    13.08.1997 14:04:45
    2048
    Typ
    TTXID
    27.08.1999 17:40:33
    3072
    Prg
    SAPLSTXD
    17.06.2004 15:06:22
    347136
    Typ
    STEXTNAME
    18.09.2001 10:03:52
    1024
    Typ
    STXDRID
    26.02.1999 14:48:42
    2048
    Typ
    STXDRLANG
    26.02.1999 14:48:42
    2048
    Typ
    STXDRNAME
    26.02.1999 14:48:42
    2048
    Typ
    STXDROBJ
    26.02.1999 14:48:42
    2048
    Typ
    THEAD
    09.11.2000 14:15:08
    6144
    Prg
    CL_ABAP_CHAR_UTILITIES========CP
    07.01.2003 18:31:23
    11264
    Typ
    STXH
    17.06.2004 14:15:46
    6144
    Typ
    TCATALOG
    25.05.1998 12:19:20
    3072
    Typ
    T168F
    27.05.1992 20:16:27
    3072
    Typ
    T168
    27.05.1992 17:53:38
    3072
    Prg
    SAPLMECCP
    25.09.2007 16:07:53
    39936
    Prg
    CL_BADI_MM====================CP
    08.01.2003 16:43:11
    9216
    Prg
    %_CCXTAB
    14.02.2002 14:22:46
    6144
    Prg
    SAPLEINH
    25.09.2007 16:07:53
    56320
    Typ
    T001W
    16.06.2004 13:14:17
    9216
    Prg
    SAPLVDAT
    19.02.2002 12:59:51
    25600
    Typ
    T163Y
    28.08.1997 09:05:01
    2048
    Prg
    SAPCNVE
    14.02.2002 14:22:47
    6144
    Prg
    SAPLOMCV
    17.06.2004 10:54:26
    16384
    Prg
    CL_EX_BADI_MATN1==============CP
    17.06.2004 10:27:52
    22528
    Prg
    IF_EX_BADI_MATN1==============IP
    17.06.2004 10:53:59
    4096
    Typ
    TMCNV
    24.02.1999 03:33:25
    3072
    Typ
    RM06B
    17.06.1998 03:23:02
    10240
    Lista tabelle interne
    Il dump non riporta informazioni relative
    Indice delle tabelle applicative
    Programma
      Nome................ Contenuto..1.......2........3........4........5....+....
    SAPMM06B
      SYST                 |00000000000x010000000000000000
      EBAN                 |300001100895000010NB  B  NB           1  Elena Varett20071
      *EBAN                |             00000                                   00000
      EBKN                 |             0000000 00000000            000000x0C
      AEBAN                |3000011008950NB     BBEUR  |
      EBANW                |300001100895000010NB  B  NB           1  Elena Varett20071
      RM06B                |                           00000000000000000010       00
      *RM06B               |                           00000000000000000000       00
      RM06E                |          000000000000000    00000000          00000
      TPRG                 |300IW2Formato settimana   Sett. |
      T001W                |3006   PIATTAFORMA DI LEINI'         6   CEDI6     0000000
      T023                 |
      T024                 |
      T160                 |300ME52                VB        B |
      T160V                |300C1XX A              XX X                   X   |
      T161                 |300BNB   000100102NBB                 NB         00000
      T161T                |300INB  BRichiesta d'acquisto|
      T168                 |300B AB  ***   1 106       0x0C0x0C0x0C0x0C|
      T168F                |300B AB  XXX                                |
      T168T                |300IB0106002 |
      TTXID                |EBAN      B04        X
      T163K                |                       |
      T163Y                |     Standard             |
      T001L                |
      T160D                |     XXXXXXXXXXXXXXXXXXXXXX
      T161E                |                         |
    SAPFMMEX
      TMED                 |300BB     |
    SAPLMEXF
      T161                 |300BNB   000100102NBB                 NB         00000
      T162                 |300PT0B                ...................................
    SAPLSUU1
      USR02                |300CONSULENTI  ÷x9Fw'x97[æÆ0000000000000000A
      USREFUS              |300CONSULENTI
    SAPLSWOR
      TOJTB                |BUS2105   XI          RBUS2105
      SWOTLV               |BUS2105   EXISTENCECHECK                  M
      TOJTD                |                                 |
    SAPLBDLS
      T000                 |300Mandante produzione      Arenzano                 EUR
    SAPMM06B
      *RM06E               |          000000000000000    00000000          00000
      MARA                 |                      00000000            00000000
      T006                 |        00          00000000000000x0C 0
    SAPLVDAT
      TPRG                 |300IW2Formato settimana   Sett. |
    SAPLOMCV
      TMCNV                |300MATCONV  0x120000000x12
    Directory delle tabelle applicative (inf. di gestione)
    Programma
      Nome.......................... tempo..........lungh....
    SAPLOMCV
      SYST                           20010612125650 00002404
      EBAN                           20061113111959 00000892
      *EBAN                          20061113111959 00000892
      EBKN                                          00000421
      AEBAN                          20000323224119 00000027
      EBANW                                         00000896
      RM06B                          20000323224119 00000529
      *RM06B                         20000323224119 00000529
      RM06E                          20020124202505 00001154
      TPRG                           20000323231030 00000032
      T001W                          20040617141548 00000338
      T023                           20040616131428 00000102
      T024                           20040616131429 00000352
      T160                                          00000035
      T160V                                         00000050
      T161                           20040616131435 00000095
      T161T                                         00000029
      T168                                          00000035
      T168F                                         00000044
      T168T                                         00000013
      TTXID                                         00000058
      T163K                          20000323230840 00000023
      T163Y                                         00000026
      T001L                          20000323230832 00000069
      T160D                                         00000069
      T161E                          20000323230840 00000025
    SAPFMMEX
      TMED                                          00000010
    SAPLMEXF
      T161                                          00000095
      T162                                          00000234
    SAPLSUU1
      USR02                                         00000226
      USREFUS                                       00000067
    SAPLSWOR
      TOJTB                                         00000453
      SWOTLV                                        00000701
      TOJTD                                         00000033
    SAPLBDLS
      T000                                          00000107
    SAPMM06B
      *RM06E                         20020124202505 00001154
      MARA                           20071118093457 00001118
      T006                           20001109142345 00000080
    SAPLVDAT
      TPRG                                          00000032
    SAPLOMCV
      TMCNV                                         00000062
    Blocchi di contr. CONT ABAP
    Include                                 Riga  Codice sorg.
    Ind.  Nome FI Co Par01 Par2. Par3. Par4. Tab.
    MM06BO0R_RM06B-EEIND                       25 EXIT.
    2502 BRAX 00
    MM06BO0R_RM06B-EEIND                       27 ENDSELECT.
    2503 BRAX 00
    2504 SQLS 08
    MM06BO0R_RM06B-EEIND                       31 ENDMODULE.
    2505 ENDM 00
    2506 -
    MM06BO0R_RM06B-EPSTP                        7 CALL FUNCTION 'ME_ITEM_CATEGOR
    2507 FUNC 00
    2508 FUNC 00
    2509 PAR2 02     0336
    2511 FUNC 10
    2512 PAR2 01     03B9
    2514 PAR2 01     03BA
    2516 FUNC FF
    MM06BO0R_RM06B-EPSTP                       14 ENDMODULE.
    >>>>> ENDM 00
    2518 -
    MM06BO0V_VRTKZ                              6 CASE EBAN-VRTKZ.
    2519 BREL 04
    MM06BO0V_VRTKZ                              7 WHEN '1'.
    2520 when 00 02  0090
    2522 BRAN 02
    2523 BRAX 00
    MM06BO0V_VRTKZ                              8 RM06B-MKNTW = '3 '. "3 Nachkom
    2524 MOVL 00 02  0136
    MM06BO0V_VRTKZ                              9 WHEN '2'.
    2526 BRAX 00
    Fine dell'analisi err. run-time
    Help me.
    Thank you

    Hello Maurizio,
    Thre screen field EBAN-MENGE is unable to handle a sign along with the value.
    Regards,
    Ammey Kesarkar

  • Run time error

    Dear All,
    During the transaction /n/sapapo/ccr (Reconsilation of transaction data) in client SCP 950, system displays the run time error which are attached herewith.
    This is the activity a used to execute regularly (Daily) and first time i recieved this message - -
    Runtime Errors         ASSERTION_FAILED                                                            
    Date and Time          13.07.2007 10:13:37                                                         
    ShrtText                                                                               
    The ASSERT condition has been violated.                                                       
    What happened?                                                                               
    In the current application program, the system recognized a situation                         
        involving the ASSERT statement that should not occur. A runtime error                         
        occurred, either because there was no activation ID entered or because                        
        the ID of the activation mode used was set to "Cancel.                                        
    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                                                                               
    The following activation ID was used: "No checkpoint group specified"                                                                               
    If the FIELDS addition was used with this ASSERT statement, the content                       
        of the first 8 fields is as follows:                                                          
        " (not used) "                                                                               
    " (not used) "                                                                               
    " (not used) "                                                                               
    " (not used) "                                                                               
    " (not used) "                                                                               
    " (not used) "                                                                               
    " (not used) "                                                                               
    " (not used) "                                                                               
    How to correct the error                                                                               
    Probably the only way to eliminate the error is to correct the program.                                                                               
    You may able to find an interim solution to the problem                                       
        in the SAP note system. If you have access to the note system yourself,                       
        use the following search criteria:                                                                               
    "ASSERTION_FAILED" C                                                                               
    "/SAPAPO/SAPLTIMESTAMP" or "/SAPAPO/LTIMESTAMPU08"                                            
        "/SAPAPO/TIMESTAMP_DIFFERENCE"                                                                
        If you cannot solve the problem yourself and you wish to send                                 
        an error message to SAP, include the following documents:                                                                               
    1. A printout of the problem description (short dump)                                         
           To obtain this, select in the current display "System->List->                              
           Save->Local File (unconverted)".                                                                               
    2. A suitable printout of the system log                                                      
           To obtain this, call the system log through transaction SM21.                              
           Limit the time interval to 10 minutes before and 5 minutes                                 
           after the short dump. In the display, then select the function                             
           "System->List->Save->Local File (unconverted)".                                                                               
    3. If the programs are your own programs or modified SAP programs,                            
           supply the source code.                                                                    
           To do this, select the Editor function "Further Utilities->                                
           Upload/Download->Download".                                                                               
    4. Details regarding the conditions under which the error occurred                            
           or which actions and input led to the error.                                               
    System environment                                                                               
    SAP Release.............. "640"                                                                               
    Application server....... "scmprd"                                                            
        Network address.......... "172.16.10.47"                                                      
        Operating system......... "AIX"                                                               
        Release.................. "5.3"                                                               
        Hardware type............ "0002BFAAD700"                                                      
        Character length......... 16 Bits                                                             
        Pointer length........... 64 Bits                                                             
        Work process number...... 0                                                                   
        Short dump setting....... "full"                                                                               
    Database server.......... "scmprd"                                                            
        Database type............ "ORACLE"                                                            
        Database name............ "SCP"                                                               
        Database owner........... "SAPSCP"                                                                               
    Character set............ "C"                                                                               
    SAP kernel............... "640"                                                               
        Created on............... "Jan 18 2006 20:47:39"                                              
        Created in............... "AIX 1 5 00538A4A4C00"                                              
        Database version......... "OCI_920 "                                                                               
    Patch level.............. "109"                                                               
        Patch text............... " "                                                                               
    Supported environment....                                                                     
        Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE                        
         10.2.0.."                                                                               
    SAP database version..... "640"                                                               
        Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"                                                                               
    Memory usage.............                                                                     
        Roll..................... 16192                                                               
        EM....................... 196923232                                                           
        Heap..................... 0                                                                   
        Page..................... 98304                                                               
        MM Used.................. 186636840                                                           
        MM Free.................. 1895288                                                             
        SAP Release.............. "640"                                                                               
    User and Transaction                                                                               
    Client.............. 950                                                                      
        User................ "SCMATP"                                                                 
        Language key........ "E"                                                                      
        Transaction......... "/SAPAPO/CCR "                                                           
        Program............. "/SAPAPO/SAPLTIMESTAMP"                                                  
        Screen.............. "SAPMSSY0 1000"                                                          
        Screen line......... 6                                                                        
    Information on where terminated                                                                   
        The termination occurred in the ABAP program "/SAPAPO/SAPLTIMESTAMP" in                       
         "/SAPAPO/TIMESTAMP_DIFFERENCE".                                                              
        The main program was "/SAPAPO/CIF_DELTAREPORT3 ".                                                                               
    The termination occurred in line 61 of the source code of the (Include)                       
         program "/SAPAPO/LTIMESTAMPU08"                                                              
        of the source code of program "/SAPAPO/LTIMESTAMPU08" (when calling the editor                
         610).                                                                               
    Source Code Extract                                                                               
    Line  SourceCde                                                                               
    31     lv_time_int_low      TYPE i,                                                            
       32     lv_timediff_int      TYPE i,                                                            
       33     lv_datediff_int      TYPE i,                                                            
       34     lv_time              TYPE t,                                                            
       35     ls_time              TYPE tstr_timestr.                                                 
       36                                                                               
    37 * check timestamp parameter                                                                 
       38 * ASSERT NOT iv_timestamp_high IS INITIAL.                                                  
       39 * ASSERT NOT iv_timestamp_low  IS INITIAL.                                                  
       40 * ASSERT iv_timestamp_low <= iv_timestamp_high.                                             
       41   IF iv_timestamp_high IS INITIAL                                                           
       42   OR iv_timestamp_low  IS INITIAL.                                                          
       43     RAISE invalid_parameter.                                                                
       44   ENDIF.                                                                               
    45   IF iv_timestamp_high < iv_timestamp_low.                                                  
       46     RAISE invalid_parameter.                                                                
       47   ENDIF.                                                                               
    48                                                                               
    49 * prepare timestamps                                                                        
       50 * .. split into date and time integers                                                      
       51   ls_timestamp_high = iv_timestamp_high.                                                    
       52   lv_date_int_high  = ls_timestamp_high-date.                                               
       53   lv_time_int_high  = ls_timestamp_high-time.                                               
       54   ls_timestamp_low  = iv_timestamp_low.                                                     
       55   lv_date_int_low   = ls_timestamp_low-date.                                                
       56   lv_time_int_low   = ls_timestamp_low-time.                                                
       57                                                                               
    58 * .. calc date diff                                                                         
       59 * .. check against max. allowed integer difference                                          
       60   lv_datediff_int = lv_date_int_high - lv_date_int_low.                                     
    >>>>>   ASSERT lv_datediff_int <= lc_datediff_intmax.                                             
       62                                                                               
    63 * calc time diff                                                                               
    64   lv_timediff_int = lv_time_int_high - lv_time_int_low.                                     
       65   IF lv_timediff_int < 0.                                                                   
       66     ADD 86400 TO lv_timediff_int.                                                           
       67     SUBTRACT 1 FROM lv_datediff_int.                                                        
       68   ENDIF.                                                                               
    69                                                                               
    70 * calc total duration                                                                       
       71   lv_duration_int = lv_datediff_int * 86400 + lv_timediff_int.                              
       72   lv_time = lv_timediff_int.                                                                
       73   ls_time = lv_time.                                                                        
       74   ls_duration-hours   = lv_duration_int DIV 3600.                                           
       75   ls_duration-minutes = ls_time-minute.                                                     
       76   ls_duration-seconds = ls_time-second.                                                     
       77                                                                               
    78   ev_duration_packed  = ls_duration.                                                        
       79   ev_duration_integer = lv_duration_int.                                                    
       80 ENDFUNCTION.                                                                               
    Contents of system fields                                                                         
    Name     Val.                                                                               
    SY-SUBRC 0                                                                               
    SY-INDEX 0                                                                               
    SY-TABIX 1                                                                               
    SY-DBCNT 1                                                                               
    SY-FDPOS 6                                                                               
    SY-LSIND 0                                                                               
    SY-PAGNO 0                                                                               
    SY-LINNO 1                                                                               
    SY-COLNO 1                                                                               
    SY-PFKEY                                                                               
    SY-UCOMM                                                                               
    SY-TITLE CIF - Comparison/Reconciliation of Transaction Data                                      
    SY-MSGTY                                                                               
    SY-MSGID                                                                               
    SY-MSGNO 000                                                                               
    SY-MSGV1                                                                               
    SY-MSGV2                                                                               
    SY-MSGV3                                                                               
    SY-MSGV4                                                                               
    Active Calls/Events                                                                               
    No.   Ty.          Program                             Include                             Line   
          Name                                                                               
    5 FUNCTION     /SAPAPO/SAPLTIMESTAMP               /SAPAPO/LTIMESTAMPU08                  61  
          /SAPAPO/TIMESTAMP_DIFFERENCE                                                                
        4 FORM         /SAPAPO/SAPLCIF_DELTA3              /SAPAPO/LCIF_DELTA3F17                349  
          COMPARE_ORDER_HEADER                                                                        
        3 FUNCTION     /SAPAPO/SAPLCIF_DELTA3              /SAPAPO/LCIF_DELTA3U03                125  
          /SAPAPO/CIF_DELTA3_COMP_ORDER                                                               
        2 FUNCTION     /SAPAPO/SAPLCIF_DELTA3              /SAPAPO/LCIF_DELTA3U01                871  
          /SAPAPO/CIF_DELTA3_COMP                                                                     
        1 EVENT        /SAPAPO/CIF_DELTAREPORT3            /SAPAPO/CIF_DELTAREPORT3              189  
          START-OF-SELECTION                                                                          
    Chosen variables                                                                               
    Name                                                                               
    Val.                                                                               
    No.       5 Ty.          FUNCTION                                                                 
    Name  /SAPAPO/TIMESTAMP_DIFFERENCE                                                                
    IV_TIMESTAMP_HIGH                                                                               
    #q1###                                                                               
    02073899                                                                               
    2001125C                                                                               
    IV_TIMESTAMP_LOW                                                                               
    ##q!####                                                                               
    00720899                                                                               
    2011125C                                                                               
    EV_DURATION_INTEGER                                                                               
    0                                                                               
    0000                                                                               
    0000                                                                               
    EV_DURATION_PACKED                                                                               
    000000                                                                               
    00000C                                                                               
    SYST-REPID                                                                               
    /SAPAPO/SAPLTIMESTAMP                                                                         
        0000000000000000000000000000000000000000                                                      
        0000000000000000000000000000000000000000                                                      
        2545454254545444554452222222222222222222                                                      
        F31010FF310C49D5341D00000000000000000000                                                      
    %_SPACE                                                                               
    0                                                                               
    0                                                                               
    2                                                                               
    0                                                                               
    LS_TIMESTAMP_HIGH                                                                               
    22000713182959                                                                               
    00000000000000                                                                               
    00000000000000                                                                               
    33333333333333                                                                               
    22000713182959                                                                               
    LV_DATE_INT_HIGH                                                                               
    803363                                                                               
    0042                                                                               
    0C23                                                                               
    LS_TIMESTAMP_HIGH-DATE                                                                               
    22000713                                                                               
    00000000                                                                               
    00000000                                                                               
    33333333                                                                               
    22000713                                                                               
    LV_TIME_INT_HIGH                                                                               
    66599                                                                               
    0002                                                                               
    0147                                                                               
    LS_TIMESTAMP_HIGH-TIME                                                                               
    182959                                                                               
    000000                                                                               
    000000                                                                               
    333333                                                                               
    182959                                                                               
    LS_TIMESTAMP_LOW                                                                               
    20071210182959                                                                               
    00000000000000                                                                               
    00000000000000                                                                               
    33333333333333                                                                               
    20071210182959                                                                               
    LV_DATE_INT_LOW                                                                               
    733021                                                                               
    0025                                                                               
    0BFD                                                                               
    LS_TIMESTAMP_LOW-DATE                                                                               
    20071210                                                                               
    00000000                                                                               
    00000000                                                                               
    33333333                                                                               
    20071210                                                                               
    LV_TIME_INT_LOW                                                                               
    66599                                                                               
    0002                                                                               
    0147                                                                               
    LS_TIMESTAMP_LOW-TIME                                                                               
    182959                                                                               
    000000                                                                               
    000000                                                                               
    333333                                                                               
    182959                                                                               
    SY-UNAME                                                                               
    SCMATP                                                                               
    000000000000                                                                               
    000000000000                                                                               
    544455222222                                                                               
    33D140000000                                                                               
    SCREEN-INPUT                                                                               
    1                                                                               
    0                                                                               
    0                                                                               
    3                                                                               
    1                                                                               
    LV_DATEDIFF_INT                                                                               
    70342                                                                               
    001C                                                                               
    0126                                                                               
    LV_TIMEDIFF_INT                                                                               
    0                                                                               
    0000                                                                               
    0000                                                                               
    SYST                                                                               
    #######################################&#332;###############################################&#19800; C#&#1280;##
        0000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000
        000000000000000000000000000000000000000100000000000000000000000000000000000000000000000D000500
        0000000000000000000000000000000800000004000000000000000000000000000000000000010900000005240000
        0000010200000000000001060100010C0000000C0000000002000000000000000000000000000B000001000803000C
    SY-REPID                                                                               
    /SAPAPO/SAPLTIMESTAMP                                                                         
        0000000000000000000000000000000000000000                                                      
        0000000000000000000000000000000000000000                                                      
        2545454254545444554452222222222222222222                                                      
        F31010FF310C49D5341D00000000000000000000                                                      
    %_DUMMY$$                                                                               
    0000                                                                               
    0000                                                                               
    2222                                                                               
    0000                                                                               
    No.       4 Ty.          FORM                                                                     
    Name  COMPARE_ORDER_HEADER                                                                        
    SYST-REPID                                                                               
    /SAPAPO/SAPLCIF_DELTA3                                                                        
        0000000000000000000000000000000000000000                                                      
        0000000000000000000000000000000000000000                                                      
        2545454254544445444543222222222222222222                                                      
        F31010FF310C396F45C413000000000000000000                                                      
    GC_APPEND_MODE                                                                               
    3                                                                               
    0                                                                               
    0                                                                               
    3                                                                               
    3                                                                               
    LS_FIELDS_TO_COMPARE-DUEDATE                                                                      
        X                                                                               
    0                                                                               
    0                                                                               
    5                                                                               
    8                                                                               
    SYST                                                                               
    #######################################&#332;###############################################&#19800; C#&#1280;##
        0000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000
        000000000000000000000000000000000000000100000000000000000000000000000000000000000000000D000500
        0000000000000000000000000000000800000004000000000000000000000000000000000000010900000005240000
        0000010200000000000001060100010C0000000C0000000002000000000000000000000000000B000001000803000C
    LS_APO_ORDER-ORDTYPE                                                                               
    5                                                                               
    0                                                                               
    0                                                                               
    3                                                                               
    5                                                                               
    GC_PLANNED_ORDER                                                                               
    5                                                                               
    0                                                                               
    0                                                                               
    3                                                                               
    5                                                                               
    LS_R3_ORDER-STATUSCNF                                                                               
    0                                                                               
    0                                                                               
    2                                                                               
    0                                                                               
    GC_ORDER_STATUS_NO_CONF                                                                               
    1                                                                               
    0                                                                               
    0                                                                               
    3                                                                               
    1                                                                               
    LS_APO_ORDER-STATUSCNF                                                                               
    0                                                                               
    0                                                                               
    2                                                                               
    0                                                                               
    GC_PRED_OUT_DEL                                                                               
    A                                                                               
    0                                                                               
    0                                                                               
    4                                                                               
    1                                                                               
    GC_TND_DELETE                                                                               
    CN                                                                               
    00                                                                               
    00                                                                               
    44                                                                               
    3E                                                

    Dear Sajit,
    Go through the following OSS Notes:
    <a href="https://websmp110.sap-ag.de/form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=901957&_NLANG=E">901957</a>, <a href="https://websmp110.sap-ag.de/form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1036880&_NLANG=E">1036880</a>, <a href="https://websmp110.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1067414&_NLANG=E">1067414</a>
    Regards,
    Naveen.

  • How to choose RT System at Run Time

    Variations of this question have been asked, but I'm not sure if they've been answered.
    We use LabVIEW RT to do a variety of behavior tests.  We have multiple experimenters using the same hardware, and each has his/her own set of "What I want to do" requirements.
    Originally, we used LabVIEW 7.0 (i.e. Before Project) to develop a Host and Remote (PXI) application.  The Host application was built as an .EXE, while the Remote was saved as an .LLB, copied to the PXI, and "invoked" at Run Time by calls to VI Server.  Note that this means that the code on the Remote might (is?) not be as compact, efficient, or optimized as if we had built an .EXE.  But we definitely can have Bob's Experiment, Jane's Experiment, and Joe's Experiment on the PC (as separate executables), and each could respectively call Bob's RT, Jane's RT, or Joe's RT on the PXI at run time.  No need to have LabVIEW (or LabVIEW expertise) on this system, and Bob, Jane, and Joe can be "ordinary users".
    "Modern LabVIEW" takes a slightly different (and probably better) view towards Real-Time -- both the Host and Remote programs are built as Executables (the RT is built as an .RTEXE).  We can "pre-deploy" the RT code to the PXI, and set it to run at Startup.  This makes getting the RT side "running" semi-automatic -- all you need to do (if it isn't running) is reboot the PXI.
    But what if you want Bob, Jane, and Joe's version, selectable by running (on the Host) Bob, Jane, or Joe's Host application?
    I'm playing with the following algorithm, which seems to work.  I'm presenting it here to get feedback, especially if there is a "better way" to do this.
    The key to this method is that there is an .INI file on the Remote, C:\ni-rt.ini, that contains, among other things, the RT Target's Startup Application path (by default, this is C:\ni-rt\startup\startup.rtexe).
    Consider three Projects, Project Bob, Project Jane, and Project Joe.  Within each Project, a Host executable is built having a name like "UI Bob" (or "Jane" or "Joe"), while the Target executable is given the name "RT Bob" (or "Jane" or "Joe").  The three .RTEXE files are copied to the Target and placed in the Startup folder, C:\ni-rt\startup.
    Now run one of the Host executables.  It does the following:
    FTP a copy of C:\ni-rt.ini from the Target to itself.
    Get the name of the Startup .RTEXE.
    If it is the "appropriate" name (i.e. if the Host program is UI Bob.exe, the Remote should be RT Bob.rtexe), do nothing, as the Target is already running the right code.
    Otherwise, we need to force the Target to run the correct Target code.  We can do this by changing the Startup entry in the .INI file to the Remote code we need (for example, RT Bob.rtexe), then tell the Remote to Reboot.  When it comes back, it will be running the appropriate RT code.
    The Host now goes ahead and tries to connect to the Remote.  If a connection cannot be established (for example, the Remote code might have stopped), a Reboot of the Remote might fix things up.
    Short of trying to write a single enormous program that encompasses every experimental scenario and situation (i.e. have a big Case Statement with a Bob, Jane, or Joe "choice", and a single executable that had everyone's code in it), this seemed to be a fairly simple way to have the robustness of compiled executables on both the Host and Remote machines, yet maintain the flexibility to let the (non-LabVIEW-guru) User choose which executable to run.
    I haven't fully deployed this system -- I'm currently at "Proof-of-Concept" stage, but I've got the various "pieces" working.  Does this seem like a sensible appropach?  Are there other, simpler, ways to accomplish this?
    Bob Schor

    Hey Bob.
    So I assume you're -completely- working with built executables?  You're not going to work in the editor environment to modify your projects at all?
    If this is the case, then having a generic deployment phase at the beginning of the executable (with a "setting up hardware for your app" splash screen) isn't a bad idea -
    Check the binary on the target, ensure it matches the binary you have on the host machine (in case you ever decide to update).
    If they don't match, FTP the new file down to replace the old one.
    FTP the ni-rt.ini file, ensure the startup exe is enabled and is pointing to the correct location.  
    If it's not enabled or not pointing to the correct startup file, modify the .INI file and FTP back to the target.
    If you had to update the INI file, ask target to reboot itself.  Wait 30 seconds, and wait for target to become available again.
    Connect to the target. If you cannot connect, reboot target.  If the target comes back and you still cannot connect to the app, notify user.
    That's almost exactly how we handle installation and deployment via MAX.  
    The big assumption here is that the built executables were all built with the same version of LabVIEW Real-Time.  If not, you'd need a system replication step in there to make sure the proper version of LabVIEW is on the target before launching the built .rtexe.  
    -Danny

  • Run-time error in alv

    Hi guys,
    I am executing an alv grid report.i m getting a run time error and i m gettig a dump.In the below i pasted the error.any suggestions where i m going wrong in the code.
    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).          
    Information on where terminated?                                              
    Termination occurred in the ABAP program "SAPLSLVC" - in "FILL_DATA_TABLE"
        The main program was "ZRPP1353 ".                                                                               
    In the source code you have the termination point in line 2735           
        of the (Include) program "LSLVCF36".    
    Source code where the error occured?
    Column per Fieldcat Entry                                          
            ls_lvc_data-value = space.                                   
            clear ls_lvc_data-style.                                     
            loop at it_fcat_local assigning <ls_fcat>                    
                    where tech ne 'X' and no_out ne 'X'.                 
              if l_invisible eq 'X'.                                     
                clear l_invisible.                                       
                if <ls_fcat>-do_sum is initial.                          
                  continue.                                              
                else.                                                    
                  clear ls_lvc_data-col_pos.                             
                endif.                                                   
              endif.                                                                               
    add 1 to ls_lvc_data-col_pos.                                                                               
    assign component <ls_fcat>-fieldname                       
                               of structure <ls_data> to <l_field_value>.
              if sy-subrc ne 0.                                          
                message x000(0k).                                        
              endif.

    Hi Dinesh,
    This is because of some problem with the field catalog you have defined. Please give the field catalog so that we can identify the problem easily.

  • Run time Error while Creating Expense request

    Dear Friends ,
    In   E-Payment ( Expense  Claim )   creation , While clicking on Enter Receipts application is going to run time error for only one user.    
    Run time Error Info :
    Runtime Errors         OBJECTS_OBJREF_NOT_ASSIGNED
    Exception              CX_SY_REF_IS_INITIAL
    Short text
         Access via 'NULL' object reference not possible.
    What happened?
         Error in the ABAP Application Program
         The current ABAP program "CL_WDR_P13N_UTILITIES=========CP" had to be
          terminated because it has
         come across a statement that unfortunately cannot be executed.
    Error analysis  
        An exception occurred that is explained in detail below.
       The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
        caught in
       procedure "PRESET" "(METHOD)", nor was it propagated by a RAISING clause.
       Since the caller of the procedure could not have anticipated that the
       exception would occur, the current program is terminated.
       The reason for the exception is:
       You attempted to use a 'NULL' object reference (points to 'nothing')
       access a component (variable: "LR_CONTEXT_ELEMENT").
       An object reference must point to an object (an instance of a class)
       before it can be used to access components.
       Either the reference was never set or it was set to 'NULL' using the
       CLEAR statement.
    How to correct the error 
         Probably the only way to eliminate the error is to correct the program.
       If the error occures in a non-modified SAP program, you may be able to
       find an interim solution in an SAP Note.
       If you have access to SAP Notes, carry out a search with the following
       keywords:
       "OBJECTS_OBJREF_NOT_ASSIGNED" "CX_SY_REF_IS_INITIAL"
       "CL_WDR_P13N_UTILITIES=========CP" or "CL_WDR_P13N_UTILITIES=========CM002"
       "PRESET"
    Information on where terminated
        Termination occurred in the ABAP program "CL_WDR_P13N_UTILITIES=========CP" -
         in "PRESET".
        The main program was "SAPMHTTP ".
        In the source code you have the termination point in line 60
        of the (Include) program "CL_WDR_P13N_UTILITIES=========CM002".
        The termination is caused because exception "CX_SY_REF_IS_INITIAL" occurred in
        procedure "PRESET" "(METHOD)", but it was neither handled locally nor declared
        in the RAISING clause of its signature.
        The procedure is in program "CL_WDR_P13N_UTILITIES=========CP "; its source
         code begins in line
        1 of the (Include program "CL_WDR_P13N_UTILITIES=========CM002 ".
    Regards,
    Suresh .

    Hi Agrawal
    As you are getting run-time error after entering the sold to party and material and the error is in SAPLV61Z ,
    close the session for sometime and open again and then create sales order and then enter sold to party and material and then check wheather you are getting or not. If you are still facing the problem then take the help of the ABAP & BASIS consultant's.
    Regards
    Srinath

  • Run time error while running BDC for production order creation and confirmation:

    Dear Gurus,
    We have a situation, where the users are trying to do the entries creation of order or confirmation (through manual and BDC). But, if there is any kind of a deficit quantities in consumption or GR quantity, then it is going to run time error and Dumps are coming in program SAPLCORB
    and the transaction code is coming for CO11N.
    How to avoid this error to run the production system in smoothing way...Any flash lights on this will be great full
    Regards,
    Madhu.G

    Hi Madhu,
    Expert Caetano has rightly point out. Refer Note 1840705 - RAISE_EXCEPTION short dump if running CO11N in background
    Cause
    The short dump is triggered because SAP transaction CO11N contains new GUI elements that cannot always be dealt with in a background process,
    such as the confirmation texts.
    Resolution
    SAP recommends that the standard production order BAPIs, such as BAPI_PRODORDCONF_CREATE_TT, should be used to post a confirmation in background.
    If this is not feasible, the following workaround may be uses:
    Define a confirmation profile in transaction OPK0; 
    In the detail areas, remove the area "Confirmation text"; 
    Set this profile as standard, so that it is chosen automatically by the system when a batch-job
    is started; 
    Assign this confirmation profile to the batch user with transaction SU3 using parameter CORUPROF.
    Also see Note 429432 - CO11N: Batch input in background dumps if long text is maintained
    Refer to note 1154692 - Endless loop during confirmation in background if you doing Auto GR during confirmations
    Thanks & Regards,
    Ramagiri

  • Run-time error SAPSQL_ARRAY_INSERT_DUPREC occurred

    When creating a new SyncBo (T51) instance after syncing eventually MI Clients shows the following message:
    [20070315 01:28:14:343] E [MI/Sync ] Received exception info code 10 and detailed message "Exception while callSync: The ABAP/4 Open SQL arrayinsert results in duplicate database records. records in the data base."
    In sm21 shows message:
    AB0 Run-time error "SAPSQL_ARRAY_INSERT_DUPREC" occurred
    AB1 > Short dump "070316 205056 sapnw ELDA " generated
    Looking for SAPSQL_ARRAY_INSERT_DUPREC error in SAP Note we found the note 817849 (Runtime error SAPSQL_ARRAY_INSERT_DUPREC occurs during sync).
    We have downloaded and applied this note in Backend as note requires and ALL prerequisites of this note. Also we have upgraded to SP19 and Kernel to 155 (part 1 and 2). But problem continues and the client that happened this problem does not work any more, all new SyncBO instances created goes to MEREP_MON as Waiting status.
    The dump on duplicate record is happening when the user is synchronizing and when a record is getting inserted to table merep_10100.
    The solution /workaround could be to do a client reset for those devicesand test again and see if it is happening, but error returns happening after this.
    When this happen SyncBo instance keeps on Waiting status (MEREP_MON). We couldn't understand why this happen suddenly and then no more new SyncBo could be created, all goes to Waiting status. Reprocess (ShiftF5) or start handler (Shift10) does not take any effect.
    Best Regards,
    Rogério

    Hi Ajith
    I am getting the same error and below is the error message from ST22. The only change is I am using for MTR application and the sync fails for the 2nd time when synched for patches for the MTR application. As it is generic sync, could you please advice to get rid of the problem.
    An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
      neither
    caught nor passed along using a RAISING clause, in the procedure
      "LOG_INSERT_DB" "(FORM)"
    Since the caller of the procedure could not have expected this exception
      to occur, the running program was terminated.
    The reason for the exception is:
    If you use an ABAP/4 Open SQL array insert to insert a record in
    the database and that record already exists with the same key,
    this results in a termination.
    (With an ABAP/4 Open SQL single record insert in the same error
    situation, processing does not terminate, but SY-SUBRC is set to 4.)
    Thanks, Raj

  • Run time error while saving sales order

    Hi all,
    i am working on IDES ECC 6.0, when i am saving an sales order(OR) i am getting run time error in the table CRMPAROLTP, program SAPMV45A.
    i am using 4 GB RAM, still having a space of 30 GB for only IDES to save the data.
    so, how to solve it.

    Hello,
    I doubt the runtime error (I am assuming you mean that you got a short dump) you mentioned in your original post has anything to do with the warning messages you see when doing a check (Ctrl+F2) on table CRMPAROLTP and program SAPMV45A.  These warnings should not cause a short dump or runtime error.
    The warning message for the table has the following long text:
    Table CRMPAROLTP: Key length > 120 (Restricted functionality)
    Message no. DT214
    Diagnosis
    The key length, i.e. the sum of the field lengths of all the key fields of the table, is more than 120 bytes.
    System response
    This is a warning.
    Procedure
    Note the following restricted fuctionality for this table:
    - Table contents cannot be transported by specifying key values, at
      best by specifying generic key values with a maximum length of 120
      bytes.
    - The table may not be used as the base table of a lock object.
    The warnings in SE38 for program SAPMV45A are mostly related to Unicode and have no reference to the table CRMPAROLTP.
    If you haven't already done so, please check the SAP Note referenced in my first reply since this does provide a solution for short dumps related to table CRMPAROLTP.
    Of course, since I don't know specifically what the short dump message is that you received, I could be basing my assessment on false assumptions.  If you have those details it is better for the SDN community as a whole if you include the information in this thread instead of sending it to me offline.
    Best Regards,
    Jamie

  • While doing SO, im getting run time error - reg;

    Hi,
    While doing sales order and whenever im doing save its  getting runtime error.
    Runtime Errors         MESSAGE_TYPE_X
    Date and Time          14.12.2011 10:55:26
    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:
        Maintain the current CRM release (table CRMPAROLTP)
        Long text of error message:
         Diagnosis
             Various transfer errors occur when transferring SAP sales orders to
             CRM or there is no status update or the status update has errors
             when transferring from CRM to the SAP system. This is caused by an
             incorrect entry for the CRM release in the SAP table CRMPAROLTP, or
             no entry is maintained at all.
         System Response
             To avoid data inconsistencies, this message causes a short dump.
         Procedure
             Maintain table CRMPAROLTP in your SAP system as is described in SAP
             Note 691710 and then repeat the process again.
         Procedure for System Administration
        Technical information about the message:
        Message class....... "V3"
        Number.............. 302
        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.
    Runtime Errors         MESSAGE_TYPE_X
    Date and Time          14.12.2011 10:55:26
    hort dump has not been completely stored (too big)
        If you have access to SAP Notes, carry out a search with the following
        keywords:
        "MESSAGE_TYPE_X" " "
        "SAPMV45A" or "MV45AF0B_BAPIDATEN_ERMITTELN"
        "BAPIDATEN_ERMITTELN"
        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 700
        Application server... "personal"
        Network address...... "192.168.2.11"
        Operating system..... "Windows NT"
        Release.............. "5.2"
        Hardware type........ "4x Intel 80686"
        Character length.... 16 Bits
        Pointer length....... 32 Bits
        Work process number.. 1
        Shortdump setting.... "full"
        Database server... "PERSONAL"
        Database type..... "ORACLE"
        Database name..... "GCU"
        Database user ID.. "SAPSR3"
        Char.set.... "C"
        SAP kernel....... 700
        created (date)... "Aug 29 2006 00:18:21"
        create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
        Database version. "OCI_10201_SHARE (10.2.0.1.0) "
        Patch level. 75
        Patch text.. " "
    Runtime Errors         MESSAGE_TYPE_X
    Date and Time          14.12.2011 10:55:26
    hort dump has not been completely stored (too big)
        Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
        SAP database version. 700
        Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
        Memory consumption
        Roll.... 8176
        EM...... 30311496
        Heap.... 0
        Page.... 139264
        MM Used. 14538320
        MM Free. 91952
    User and Transaction
        Client.............. 100
        User................ "INFO_SD"
        Language key........ "E"
        Transaction......... "VA01 "
        Program............. "SAPMV45A"
        Screen.............. "SAPMV45A 4001"
        Screen line......... 65
    Information on where terminated
        Termination occurred in the ABAP program "SAPMV45A" - in "BAPIDATEN_ERMITTELN".
        The main program was "SAPMV45A ".
        In the source code you have the termination point in line 338
        of the (Include) program "MV45AF0B_BAPIDATEN_ERMITTELN".
    Edited by: kiran35086 on Dec 14, 2011 6:30 AM

    Dear  kiran,
    This might be many reasons.If you have not done  configuration properly system will take you to dump(Run time error).
    Try read the diagnosis possibly you may understand the problem.
    If not You coordinate with your technical team.
    Thanks&Regards
    Raghu.k

  • Run time error while create Vendor master via MK01

    Dear Experts,
    when i try to create vendor master by MK01.....system throws run time error as below:
    "The exception 'CX_BADI_MULTIPLY_IMPLEMENTED' was raised, but it was not caught
    anywhere along
    the call hierarchy.
    Since exceptions represent error situations and this error was not
    adequately responded to, the running ABAP program
    'CVI_MAP_TITLE=================CP' has to be
    terminated."
    My current system is ECC 6 along with DBM. Business partner configuration is activated in the current system. I am getting this error after BP configuration. Could you please help me to fix this issue?.......Is it due to configuration or a dump from abap program?
    Regards
    Vetrivelan

    Hii,
       please search sdn before posting the threads.
    check these  links, it may help u............
    Short Dump - CX_BADI_MULTIPLY_IMPLEMENTED - BADI Q1SR1
    Short Dump - CX_BADI_MULTIPLY_IMPLEMENTED - BADI Q1SR1
    CX_BADI_NOT_IMPLEMENTED
    thanks.

  • Run Time Error  while Transferring data to Application server

    Hello Abaper's,
    I have generated a XML data using the FM : "  SAP_CONVERT_TO_XML_FORMAT ".
    While transferring the data to a File on Application Server using the statement
    DATA : wa_xmltab TYPE truxs_xml_line,
                 it_xmltab TYPE truxs_xml_table.
    OPEN DATASET FNAME FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
    IF sy-subrc EQ 0.
      LOOP AT it_xmltab INTO wa_xmltab.
        TRANSFER wa_xmltab TO FNAME.    <<<<<<<<<<<<<<  Getting Error here
      ENDLOOP.
    ELSE.
      MESSAGE e004(zmsg5) WITH 'File FNAME not opened'.
    ENDIF.
    CLOSE DATASET FNAME.
    The Run Time Error i am Facing is  
    Short text
        The current statement is only defined for character-type data objects.
    Error analysis
        For the statement
           "TRANSFER f TO ..."
        only character-type data objects are supported at the argument position
        "f".
        In this case. the operand "f" has the non-character-type "TRUXS_XML_LINE". The
        current program is a Unicode program. In the Unicode context, the type
        'X' or structures containing not only character-type components are
        regarded as non-character-type.
    Regards
    jv

    Hello  Volker Binder ,
    Thank you . it's now transferring the data to Application sercver. I forgot to try using Binay mode,
    Thers is one more problem. There are 10 Records in that internal table that is being converted to XML format,
    but the XML data is showing only first 4 records.... the XML data format for the remaining data is not seen.
    Actual  No. of Records  in Internal table :
    matnr            matkl          meins
    0-BUY1               012         PC
    0-BUY2               012         PC
    1                                EA
    2                    012         L
    3                    01          EA
    12                               EA
    23                   001         ST
    24                   015`        EA
    28                   010         EA
    29                   015`        AU
    XML Format for the above 10 fields is :
    <?xml version="1.0"?><TY_MARA><TY_MARA><MATNR Datatype="C" Length="36">0-BUY1</MATNR><MATKL Datatype="C" Length="18">012</MATKL><MEINS Datatype="C" Length="6">PC
    </MEINS>
    </TY_MARA><TY_MARA><MATNR Datatype="C" Length="36">0-BUY2</MATNR><MATKL Datatype="C" Length="18">012</MATKL><MEINS Datatype="C" Length="6">
    PC </MEINS>
    </TY_MARA><TY_MARA><MATNR Datatype="C" Length="36">000000000000000001</MATNR><MEINS Datatype="C" Length="6">EA</MEINS>
    </TY_MARA><TY_MARA><MATNR Datatype="C" Length="36">000000000000000002</MATNR
    This 4th record data in XML is also incomplete..
    The above XML format is generated only for 4 records  out of 10 Records.
    Please let me know , how can i increase the Size / Memory of the Application server file to accomodate for the reamining Records
    Regards
    Jv

  • ABAP run time error

    Dear ALL,
    When we are creating sales order after entering sold-to-party, Material & Quantity when we press ENTER key That time
    we are getting following run time error
    Hoe to resolve this?
    Runtime Errors         SAPSQL_INVALID_FIELDNAME                                                    
    Except.                CX_SY_DYNAMIC_OSQL_SEMANTICS                                                
    Date and Time          15.01.2009 16:04:19                                                         
    Short dump has not been completely stored (too big)                                                                               
    Short text                                                                               
    A dynamically specified column name is unknown.                                               
    What happened?                                                                               
    Error in the ABAP Application Program                                                                               
    The current ABAP program "SAPLV61Z" 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_DYNAMIC_OSQL_SEMANTICS', was                 
         not caught in                                                                               
    procedure "SEL_KONDTAB" "(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 Open SQL clause was specified dynamically. The contained field name                        
        "ALAND" does not exist in any of the database tables from the FROM clause.                    
    How to correct the error                                                                               
    Check the field name in the SELECT clause.                                                                               
    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:                                                                               
    "SAPSQL_INVALID_FIELDNAME" "CX_SY_DYNAMIC_OSQL_SEMANTICS"                                     
        "SAPLV61Z" or "LV61ZU01"                                                                      
        "SEL_KONDTAB"                                                                               
    If you cannot solve the problem yourself and want to send an error                            
        notification to SAP, include the following information:                                                                               
    1. The description of the current problem (short dump)                                                                               
    To save the description, choose "System->List->Save->Local File                            
        (Unconverted)".                                                                               
    2. Corresponding system log                                                                               
    Display the system log by calling transaction SM21.                                        
           Restrict the time interval to 10 minutes before and five minutes                           
        after the short dump. Then choose "System->List->Save->Local File                             
        (Unconverted)".                                                                               
    3. If the problem occurs in a problem of your own or a modified SAP                           
        program: The source code of the program                                                       
           In the editor, choose "Utilities->More                                                     
        Utilities->Upload/Download->Download".                                                                               
    4. Details about the conditions under which the error occurred or which                       
        actions and input led to the error.                                                                               
    The exception must either be prevented, caught within proedure                                
        "SEL_KONDTAB" "(FORM)", or its possible occurrence must be declared in the                    
        RAISING clause of the procedure.                                                              
        To prevent the exception, note the following:                                                 
    System environment                                                                               
    SAP-Release 700                                                                               
    Application server... "slgsap-prd"                                                            
        Network address...... "10.140.1.11"                                                           
        Operating system..... "Windows NT"                                                            
        Release.............. "5.2"                                                                   
        Hardware type........ "8x AMD64 Level"                                                        
        Character length.... 16 Bits                                                                  
        Pointer length....... 64 Bits                                                                 
        Work process number.. 0                                                                       
        Shortdump setting.... "full"                                                                               
    Database server... "SLGSAP-PRD"                                                               
        Database type..... "MSSQL"                                                                    
        Database name..... "PRD"                                                                      
        Database user ID.. "prd"                                                                               
    Terminal................. "SD0123l"                                                                               
    Char.set.... "C"                                                                               
    SAP kernel....... 700                                                                         
        created (date)... "May 6 2008 00:13:21"                                                       
        create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"                              
        Database version. "SQL_Server_8.00 "                                                                               
    Patch level. 159                                                                               
    Patch text.. " "                                                                               
    Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"                              
        SAP database version. 700                                                                     
        Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows                
         NT 6.0"                                                                               
    Memory consumption                                                                               
    Roll.... 16192                                                                               
    EM...... 20949200                                                                               
    Heap.... 0                                                                               
    Page.... 196608                                                                               
    MM Used. 15928048                                                                               
    MM Free. 828016                                                                               
    User and Transaction                                                                               
    Client.............. 900                                                                      
        User................ "ADMIN"                                                                  
        Language key........ "E"                                                                      
        Transaction......... "VA01 "                                                                  
        Transactions ID..... "03F0E2DD6B35F16CBBFF002219897F24"                                                                               
    Program............. "SAPLV61Z"                                                               
        Screen.............. "SAPMV45A 4900"                                                          
        Screen line......... 930                                                                      
    Information on where terminated                                                                   
        Termination occurred in the ABAP program "SAPLV61Z" - in "SEL_KONDTAB".                       
        The main program was "SAPMV45A ".                                                                               
    In the source code you have the termination point in line 672                                 
        of the (Include) program "LV61ZU01".                                                          
        The termination is caused because exception "CX_SY_DYNAMIC_OSQL_SEMANTICS"                    
         occurred in                                                                               
    procedure "SEL_KONDTAB" "(FORM)", but it was neither handled locally nor                      
         declared                                                                               
    in the RAISING clause of its signature.                                                                               
    The procedure is in program "SAPLV61Z "; its source code begins in line                       
        260 of the (Include program "LV61ZU01 ".                                                      
    Source Code Extract                                                                               
    Line  SourceCde                                                                               
    642     if se_prestep              = yes or                                                     
      643        se_read_only_one_record = yes.                                                       
      644       if t681-ksdat is initial.                                                             
      645         if se_read_all_prestep is initial.                                                  
      646           select * from (t681-kotab) appending table <cond_tab>                             
      647                  up to 1 rows                                                               
      648                  where kappl  = se_kappl                                                    
      649                  and   kschl  = se_kschl                                                    
      650                  and   (coding_tab).                                                        
      651           h_subrc = sy-subrc.                                                               
      652         else.                                                                               
    653           select * from (t681-kotab) appending table <cond_tab>                             
      654                  where kappl  = se_kappl                                                    
      655                  and   kschl  = se_kschl                                                    
      656                  and   (coding_tab).                                                        
      657         endif.                                                                               
    658                                                                               
    659 * it is enough to find one record in prestep                                                
      660 * (care must be taken with pool tables - depending on database this                         
      661 *  will cost performance instead of saving)                                                 
      662         if select_split ne 0 and h_subrc ne 0.                                              
      663           modify coding_tab from coding_alter index select_split.                           
      664           select * from (t681-kotab) appending table <cond_tab>                             
      665                  up to 1 rows                                                               
      666                  where kappl  = se_kappl                                                    
      667                  and   kschl  = se_kschl                                                    
      668                  and   (coding_tab).                                                        
      669         endif.                                                                               
    670       else.                                                                               
    671         if se_read_all_prestep is initial.                                                  
    >>>>>           select * from (t681-kotab) appending table <cond_tab>                             
      673                  up to 1 rows                                                               
      674                  where kappl  = se_kappl     
    Regards,
    Akshay
    Edited by: Akshay Dalal on Jan 17, 2009 6:25 AM
    Edited by: Akshay Dalal on Jan 17, 2009 6:30 AM

    Dear Akshay,
    We will NOT be able to provide you with a solution on this forum, because we have no clue what configuration do you have in your system and what user exits or other custom development may have been done in your specific system.
    Lakshmipathi has already correctly pointed to a similar post. You might want to get an ABAPer to set a breakpoint just before the error occurs, then he/she might provide you with more information, which may (or may not) be helpful.
    There is obviously something wrong in the pricing condition either on configuration level or in a user exit. If you write to SAP (which you should, because it's a standard program), they will ask to connect to your system, because they don't have any chrystal balls over there either.
    Just in case - before going any further, try running the program RV80HGEN (in the test system, of course), which re-generates requirements and formulas. Sometimes it helps, although I doubt that it is the case here.
    Also if you've used some custom (Z...) fields in the pricing configuration, that's where the problem is most likely.

Maybe you are looking for

  • How can I tell if time machine is backing up my user folder?

    I use time machine, but I'm worried that my user library folder (containing my Mail folders) isn't being backed up. I can't see it when I browse the time machine folders, but then again, I can't see my user library on my dard drive without using the

  • Is there a generic way to get sequence

    Hey, I need a counter that will not initialized when my sever restarted, so i decide to write sequence in the data base for this. My question is there a generic (for any vendor) way to get next id? Thank you

  • Can change work-space background color without effect on HTML?

    I'd like to have a dark work-space background-color (for the design part of the interface) when I work in my included files, instead of the default white. Can I have it without setting a true CSS that affects the real appearance of the page?

  • Migrating from WebSphere 5.1

    Does the tool support WebSphere 5.1? I tried running it anyway over a J2EE application in WebSphere 5.1 and it worked fine except it did not create the EJB jar file in the EAR file at all. Are there any recommendations on a work around? Thanks.

  • IPod as back up device

    Can I use my iPod (30GB) as a device to store MS Word en Excel documents? Thanks!