Dump by running 0Orgunit_attr Datasource in R/3

Hi Gurus,
i am facing a problem by executing 0Orgunit_attr in the quality system. In D System evry thing is ok.
By executing the 0Orgunit_ATTR extractor in RSA3 in R/3, i had a dump.
The Error is as follow:
Runtime Errors ITAB_DUPLICATE_KEY
Date and Time 14/01/2011 11:10:12
Short dump has not been completely stored
Short text
A row with the same key already exists.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLHRMS_BW_PA_OS" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
An entry was to be entered into the table
"\FUNCTION=HR_BW_EXTRACT_IO_0Orgunit\DATA=MAIN_COSTCENTERS[]" (which should have
had a unique table key (UNIQUE KEY) table).
After some researches by SDN i proceed as follow:
1.I used program: RSAR_RSISOSMAP_REPAIR in SE38 to identify the objects in R/3. But no object were found.
2.I checked table RSISOSMAP in SE16. It was empty.
What can be the cause of that?
Could you please help?
Man Thanks in advance

Hi,
I think you are getting the dump in FM HR_BW_EXTRACT_IO_ORGUNIT which is triggered by the Orgunit extractor. It could be at the code I pasted below. May be...you could try to insert a break point here in the code and run the extractor from RSA3 in debug mode. See what values you have here in main_costcenters.
CALL FUNCTION 'RH_GET_COSTCENTER_OF_OBJECT'
           EXPORTING
               plvar              = last_plvar
               begda              = p_begda
               endda              = p_endda
           svect             = '1'
           active            = ' '
           dist               = ' '
               object_only        = only_direct
               buffered_access    = 'X'
               read_it0001        = 'X'
               i0027_flag         = ' '
               ombuffer_mode      = ' '
           TABLES
               in_objects         = in_objects
               main_costcenters   = main_co
           EXCEPTIONS
               OTHERS             = 0.
        INSERT lines of main_co INTO TABLE main_costcenters.

Similar Messages

  • Short dump while running Payroll

    Dear Experts,
    I am getting short dump while running the payroll for around 150 employees, but am not able to see the short dump also as it says that "process terminated".
    please help me in this regard and also let me know if there could be any configuration errors.
    Regards
    Shansar

    Thank you all for the response.
    The issue has been resolved.  i have learnt that log field should not be flagged when you are executing payroll for more than 50 employees.
    Regards
    Shansar

  • ABAP dump while running the tcode MIGO

    Hi All,
    I am getting the abap dump while running the tcode MIGO when I searched I got two relevant sap notes but our functional team said that its not applicable in our case.
    Please find the details of ST22 analysis-:
    Runtime Errors         MESSAGE_TYPE_X
    Date and Time          17.04.2009 13:18:45
    Short text
         The current application triggered a termination with a short dump.
    What happened?
         The current application program detected a situation which really
         should not occur. Therefore, a termination with a short dump was
         triggered on purpose by the key word MESSAGE (type X).
    Error analysis
        Short text of error message:
        No RFC destination is defined for SAP Global Trade Services
        Long text of error message:
        Technical information about the message:
        Message class....... "/SAPSLL/PLUGINR3"
        Number.............. 002
        Variable 1.......... " "
        Variable 2.......... " "
        Variable 3.......... " "
        Variable 4.......... " "
    How to correct the error
        Probably the only way to eliminate the error is to correct the program.
        If the error occures in a non-modified SAP program, you may be able to
        find an interim solution in an SAP Note.
        If you have access to SAP Notes, carry out a search with the following
        keywords:
        "MESSAGE_TYPE_X" " "
        "SAPLMBWL" or "LMBWLU21"
        "MB_POST_GOODS_MOVEMENT"
    SAP Notes i have reffered 1098491, 1041122
    Currently we are running on SAP_APPL     600     0007     SAPKH60007     
    Regards,
    Prashant

    Hi Rohit,
    This particular note is valid for
    Support
    Packages Release Package
    Name
    PI 2004_1_46B SAPKIPZI38
    PI 2004_1_46C SAPKIPZI48
    PI 2004_1_470 SAPKIPZI58
    PI 2004_1_500 SAPKIPZI68
    Our system is running on PI_BASIS     2006_1_700     0005     SAPKIPYM05
    Pls suggest.
    Regards,
    Prashant

  • Core dump while running jmf application

    I am running a bit customised version of Transcode & Concat from JMF samples as a single application on Solaris 10.
    I got core dump while running the application.
    Any clue ?
    Below are the content from hs_err_pid#.out file.
    +#+
    +# An unexpected error has been detected by HotSpot Virtual Machine:+
    +#+
    +# SIGSEGV (0xb) at pc=0xfecaa04c, pid=23754, tid=97822+
    +#+
    +# Java VM: Java HotSpot(TM) Server VM (1.5.0_11-b03 mixed mode)+
    +# Problematic frame:+
    +# V [libjvm.so+0x4aa04c]+
    +#+
    ---------------  T H R E A D  ---------------
    +Current thread (0x05b62e40):  JavaThread "Loop thread: com.sun.media.parser.audio.WavParser$WavTrack@8d6f11" [_thread_in_vm, id=97822]+
    siginfo:si_signo=11, si_errno=0, si_code=1, si_addr=0x00000000
    Registers:
    O0=0x00008000 O1=0x00000b90 O2=0x016d8b90 O3=0xff02d024
    O4=0x0000942c O5=0x00009400 O6=0xbfa7f1e0 O7=0x00009400
    G1=0x00000000 G2=0x000077bc G3=0x00000000 G4=0x80000000
    G5=0x00000006 G6=0x00000000 G7=0xae787200 Y=0x00000000
    PC=0xfecaa04c nPC=0xfecaa050
    Top of Stack: (sp=0xbfa7f1e0)
    +0xbfa7f1e0: ff02d02c 00000002 00001ffc 00000001+
    +0xbfa7f1f0: fefd8000 ff02d028 00008800 ff03106c+
    +0xbfa7f200: ff02d9e4 00000000 00000000 05b62e40+
    +0xbfa7f210: 00008374 00009638 bfa7f240 bfd04dc4+
    +0xbfa7f220: 00000000 00000000 00000000 00000000+
    +0xbfa7f230: 00000000 00000000 00000000 00000000+
    +0xbfa7f240: feca9f1c 00007fec 00000006 00034cb8+
    +0xbfa7f250: 00000005 00000002 01000000 006d81a8+
    Instructions: (pc=0xfecaa04c)
    +0xfecaa03c: 7f f8 86 38 90 10 00 1b 8a 10 20 06 ca 26 e0 e4+
    +0xfecaa04c: ec 06 60 00 fa 05 a0 08 80 a7 60 00 02 40 00 11+
    Stack: [0xbfa00000,0xbfa80000),  sp=0xbfa7f1e0,  free space=508k
    Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
    +V  [libjvm.so+0x4aa04c]+
    +C  [libjmmpa.so+0x4dcc] Java_com_sun_media_codec_audio_mpa_NativeEncoder_nFlush+0x1c+
    +j  com.sun.media.codec.audio.mpa.NativeEncoder.nFlush(I[B)I+0+
    +j  com.sun.media.codec.audio.mpa.NativeEncoder.nFlush(I[B)I+0+
    j  com.sun.media.codec.audio.mpa.NativeEncoder.process(Ljavax/media/Buffer;Ljavax/media/Buffer;)I20+
    v  ~C2IAdapter
    J  com.sun.media.BasicFilterModule.process()V
    J  com.sun.media.BasicFilterModule.process()V
    J  com.sun.media.BasicFilterModule.process()V
    J  com.sun.media.BasicFilterModule.process()V
    J  com.sun.media.BasicFilterModule.process()V
    J  com.sun.media.BasicFilterModule.process()V
    J  com.sun.media.SourceThread.process()Z
    J  com.sun.media.util.LoopThread.run()V
    v  ~I2CAdapter
    v  ~StubRoutines::call_stub
    +V  [libjvm.so+0x19b95c]+
    +V  [libjvm.so+0x2c1a24]+
    +V  [libjvm.so+0x2e1010]+
    +V  [libjvm.so+0x2dcbac]+
    +V  [libjvm.so+0x67a7e0]+
    Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
    +j  com.sun.media.codec.audio.mpa.NativeEncoder.nFlush(I[B)I+0+
    j  com.sun.media.codec.audio.mpa.NativeEncoder.process(Ljavax/media/Buffer;Ljavax/media/Buffer;)I20+
    v  ~C2IAdapter
    J  com.sun.media.BasicFilterModule.process()V
    J  com.sun.media.BasicFilterModule.process()V
    J  com.sun.media.BasicFilterModule.process()V
    J  com.sun.media.BasicFilterModule.process()V
    J  com.sun.media.BasicFilterModule.process()V
    J  com.sun.media.BasicFilterModule.process()V
    J  com.sun.media.SourceThread.process()Z
    J  com.sun.media.util.LoopThread.run()V
    v  ~I2CAdapter
    v  ~StubRoutines::call_stub
    ---------------  P R O C E S S  ---------------
    Java Threads: ( => current thread )
    +0x0557db38 JavaThread "Thread-3024" [_thread_blocked, id=97827]+
    +0x05390a28 JavaThread "Loop thread" [_thread_blocked, id=97823]+
    +=>0x05b62e40 JavaThread "Loop thread: com.sun.media.parser.audio.WavParser$WavTrack@8d6f11" [_thread_in_vm, id=97822]+
    +0x05725a68 JavaThread "JMF thread: SendEventQueue: com.sun.media.ProcessEngine" [_thread_blocked, id=97814]+
    +0x05303e38 JavaThread "JMF thread: SendEventQueue: com.sun.media.processor.unknown.Handler" [_thread_blocked, id=97813]+
    +0x053d6848 JavaThread "Loop thread" [_thread_blocked, id=97812]+
    +0x05b8d508 JavaThread "RawBufferStream Thread" [_thread_blocked, id=97811]+
    +0x04a957b8 JavaThread "JMF thread: SendEventQueue: com.sun.media.ProcessEngine" [_thread_blocked, id=97806]+
    +0x0573c8a0 JavaThread "JMF thread: SendEventQueue: com.sun.media.processor.unknown.Handler" [_thread_blocked, id=97805]+
    +0x04be2248 JavaThread "Keep-Alive-Timer" daemon [_thread_blocked, id=97804]+
    +0x00189ea0 JavaThread "Timer-1" daemon [_thread_blocked, id=38]+
    +0x00e2d5f8 JavaThread "OamBus" daemon [_thread_in_native, id=26]+
    +0x00e5d168 JavaThread "Dispatcher-Thread-3" daemon [_thread_blocked, id=25]+
    +0x00c972b8 JavaThread "Thread-2" [_thread_blocked, id=20]+
    +0x00c4e9b0 JavaThread "RMI TCP Accept-19912" daemon [_thread_in_native, id=18]+
    +0x00c56c90 JavaThread "RMI TCP Accept-0" daemon [_thread_in_native, id=17]+
    +0x00c51da0 JavaThread "Timer-0" daemon [_thread_blocked, id=16]+
    +0x001ae158 JavaThread "Low Memory Detector" daemon [_thread_blocked, id=15]+
    +0x001ac898 JavaThread "CompilerThread1" daemon [_thread_blocked, id=14]+
    +0x001aba20 JavaThread "CompilerThread0" daemon [_thread_blocked, id=13]+
    +0x001aab08 JavaThread "AdapterThread" daemon [_thread_blocked, id=12]+
    +0x001a9d68 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=11]+
    +0x001a90d8 JavaThread "Surrogate Locker Thread (CMS)" daemon [_thread_blocked, id=10]+
    +0x0019c718 JavaThread "Finalizer" daemon [_thread_blocked, id=9]+
    +0x0019c1d8 JavaThread "Reference Handler" daemon [_thread_blocked, id=8]+
    +0x0003b260 JavaThread "main" [_thread_blocked, id=1]+
    Other Threads:
    +0x0019a0f8 VMThread [id=7]+
    +0x00c55fe0 WatcherThread [id=19]+
    VM state:not at safepoint (normal execution)
    VM Mutex/Monitor currently owned by a thread: None
    Heap
    par new generation   total 24512K, used 3242K [0xd4800000, 0xd6000000, 0xd6000000)
    eden space 24448K,  13% used [0xd4800000, 0xd4b2aa50, 0xd5fe0000)
    from space 64K,   0% used [0xd5fe0000, 0xd5fe0000, 0xd5ff0000)
    to   space 64K,   0% used [0xd5ff0000, 0xd5ff0000, 0xd6000000)
    concurrent mark-sweep generation total 499712K, used 263197K [0xd6000000, 0xf4800000, 0xf4800000)
    concurrent-mark-sweep perm gen total 50712K, used 30431K [0xf4800000, 0xf7986000, 0xf8800000)
    Dynamic libraries:
    +0x00010000      /usr/jdk/instances/jdk1.5.0/bin/java+
    +0xff390000      /usr/lib/libthread.so.1+
    +0xff360000      /usr/lib/libdl.so.1+
    +0xff200000      /usr/lib/libc.so.1+
    +0xff380000      /platform/SUNW,Netra-440/lib/libc_psr.so.1+
    +0xfe800000      /usr/jdk/instances/jdk1.5.0/jre/lib/sparc/server/libjvm.so+
    +0xff300000      /usr/lib/libsocket.so.1+
    +0xff330000      /usr/lib/libsched.so.1+
    +0xff1c0000      /usr/lib/libCrun.so.1+
    +0xff190000      /usr/lib/libm.so.1+
    +0xff080000      /usr/lib/libnsl.so.1+
    +0xfe700000      /usr/lib/libm.so.2+
    +0xff160000      /usr/lib/libscf.so.1+
    +0xff140000      /usr/lib/libdoor.so.1+
    +0xff060000      /usr/lib/libuutil.so.1+
    +0xfe7d0000      /usr/lib/libgen.so.1+
    +0xfe6d0000      /usr/lib/libmd.so.1+
    +0xfe6b0000      /platform/SUNW,Netra-440/lib/libmd_psr.so.1+
    +0xfe690000      /usr/lib/libmp.so.2+
    +0xfe650000      /usr/jdk/instances/jdk1.5.0/jre/lib/sparc/native_threads/libhpi.so+
    +0xfe5c0000      /usr/jdk/instances/jdk1.5.0/jre/lib/sparc/libverify.so+
    +0xfe580000      /usr/jdk/instances/jdk1.5.0/jre/lib/sparc/libjava.so+
    +0xfe560000      /usr/jdk/instances/jdk1.5.0/jre/lib/sparc/libzip.so+
    +0xfe410000      /usr/lib/locale/en_US/en_US.so.3+
    +0xfe310000      /usr/jdk/instances/jdk1.5.0/jre/lib/sparc/libmanagement.so+
    +0xfe250000      /usr/jdk/instances/jdk1.5.0/jre/lib/sparc/libnet.so+
    +0xcc450000      /usr/jdk/instances/jdk1.5.0/jre/lib/sparc/libj2pkcs11.so+
    +0xcc410000      /usr/lib/libpkcs11.so+
    +0xcc3f0000      /usr/lib/libcryptoutil.so.1+
    +0xcc340000      /usr/lib/security/pkcs11_softtoken.so+
    +0xcc3d0000      /opt/tib/EAG/tibrv/lib/libtibrvj.so+
    +0xcc310000      /opt/tib/EAG/tibrv/lib/libtibrvcmq.so+
    +0xcc250000      /opt/tib/EAG/tibrv/lib/libtibrvcm.so+
    +0xcc230000      /opt/tib/EAG/tibrv/lib/libtibrvft.so+
    +0xcc110000      /opt/tib/EAG/tibrv/lib/libtibrv.so+
    +0xccbf0000      /usr/lib/libpthread.so.1+
    +0xcc210000      /usr/lib/libkstat.so.1+
    +0xcc050000      /usr/jdk/instances/jdk1.5.0/jre/lib/sparc/libnio.so+
    +0xcc030000      /usr/lib/librt.so.1+
    +0xcc010000      /usr/lib/libaio.so.1+
    +0xc0680000      /usr/jdk/instances/jdk1.5.0/jre/lib/sparc/libawt.so+
    +0xc0500000      /usr/jdk/instances/jdk1.5.0/jre/lib/sparc/libmlib_image.so+
    +0xcb920000      /usr/jdk/instances/jdk1.5.0/jre/lib/sparc/headless/libmawt.so+
    +0xcb850000      /usr/jdk/instances/jdk1.5.0/jre/lib/sparc/libjmutil.so+
    +0xbfd80000      /usr/lib/libX11.so.4+
    +0xcb810000      /usr/openwin/lib/libXext.so.0+
    +0xbfd00000      /usr/jdk/instances/jdk1.5.0/jre/lib/sparc/libjmmpa.so+
    VM Arguments:
    jvm_args: -DappInstanceId=19912 -DsocketCountPorts= -Dlog4j.configuration=DCL_BusListener-19912-5.1.2-log4j.xml -Dcfg.uri=/u01/home/ihome/ops/Server/cfg/dcl_bus_responder.xml -Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0 -Dcom.sun.management.jmxremote.port=19912 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Djava.awt.headless=true -Dargos.group=VMABusListener -Dspring.bootstrap=spring/VoiceMailAdapter/dcl/DCLSpringBootstrapContext.xml -Xmx512m -Xms512m -verbose:gc -XX:PrintGCDetails -XX:+PrintGCApplicationConcurrentTime -XX:+PrintGCApplicationStoppedTime -XX:MaxNewSize=24m -XX:NewSize=24m -XX:+UseParNewGC -XX:+CMSParallelRemarkEnabled -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=60+
    Launcher Type: SUN_STANDARD
    Environment Variables:
    JAVA_HOME=/usr/jdk/latest
    PATH=/usr/jdk/latest/bin:/usr/local/bin:/usr/jdk/latest/bin:/usr/local/bin:/usr/sbin:/usr/bin:/usr/sfw/bin:/opt/sfw/bin:/usr/ccs/bin:/usr/openwin/bin:/usr/dt/bin:/usr/sadm/bin:/usr/proc/bin:/opt/tib/EAG/tibrv:.:/u01/home/ihome/.bin:/usr/sfw/bin:/opt/tib/EAG/tibrv/bin:/u01/app/oracle/product/10.2.0/db10g/bin:/opt/tib/EAG/tibrv:.:/u01/home/ihome/.bin:/usr/sfw/bin:/opt/tib/EAG/tibrv/bin:/u01/app/oracle/product/10.2.0/db10g/bin
    LD_LIBRARY_PATH=/usr/jdk/instances/jdk1.5.0/jre/lib/sparc/server:/usr/jdk/instances/jdk1.5.0/jre/lib/sparc:/usr/jdk/instances/jdk1.5.0/jre/../lib/sparc:/opt/tib/EAG/tibrv/lib:/opt/tib/EAG/tibrv/lib
    SHELL=/usr/bin/bash
    Signal Handlers:
    +SIGSEGV: [libjvm.so+0x709bb4], sa_mask[0]=0xffbffeff, sa_flags=0x00000004+
    +SIGBUS: [libjvm.so+0x709bb4], sa_mask[0]=0xffbffeff, sa_flags=0x00000004+
    +SIGFPE: [libjvm.so+0x274474], sa_mask[0]=0xffbffeff, sa_flags=0x0000000c+
    SIGPIPE: SIG_IGN, sa_mask[0]=0x00000000, sa_flags=0x00000000
    +SIGILL: [libjvm.so+0x274474], sa_mask[0]=0xffbffeff, sa_flags=0x0000000c+
    SIGUSR1: SIG_DFL, sa_mask[0]=0x00000000, sa_flags=0x00000000
    SIGUSR2: SIG_DFL, sa_mask[0]=0x00000000, sa_flags=0x00000000
    SIGHUP: SIG_IGN, sa_mask[0]=0x00000000, sa_flags=0x00000000
    SIGINT: SIG_IGN, sa_mask[0]=0x00000000, sa_flags=0x00000000
    +SIGQUIT: [libjvm.so+0x67bb74], sa_mask[0]=0xffbffeff, sa_flags=0x00000004+
    +SIGTERM: [libjvm.so+0x67bb74], sa_mask[0]=0xffbffeff, sa_flags=0x00000004+
    ---------------  S Y S T E M  ---------------
    OS:                       Solaris 10 11/06 s10s_u3wos_10 SPARC
    Copyright 2006 Sun Microsystems, Inc.  All Rights Reserved.
    Use is subject to license terms.
    Assembled 14 November 2006
    uname:SunOS 5.10 Generic_127111-11 sun4u  (T2 libthread)
    rlimit: STACK 8192k, CORE infinity, NOFILE 65536, AS infinity
    load average:9.45 9.59 9.62
    CPU:total 4 has_v8, has_v9, has_vis1, has_vis2, is_ultra3
    Memory: 8k page, physical 16777216k(6702928k free)
    vm_info: Java HotSpot(TM) Server VM (1.5.0_11-b03) for solaris-sparc, built on Dec 15 2006 01:18:11 by unknown with unknown Workshop:0x550

    Hello captfoss!
    The Linux video drivers are buggy. If you give them video they don't like, they crash.You seem to repeat this statement quite often......but I don't think s/he is using Linux. S/He is using Solaris10 !!!
    I don't know if Linux and Solaris are same OS.............
    Thanks! And please don't take it as a comment! :-)

  • Dump in master data datasource

    Hi all,
    When I execute an extraction through a master data datasource (e.g. 0CUSTOMER:ATTR, 0VENDOR), I'm getting the following error:
    Job cancelled in source system (RSM078)
    The job in the source system is cancelled because a dump,
    DBIF_RSQL_SQL_ERROR
    Database error text........: "Cursor HCACHEDCSRN00445 not open. MSGID=
      Job=067810/PRE00/WP27"
    Internal call code.........: "\[RSQL/FTCH/KNA1 ]"
    I'm running on BW 7.01 SP 07
    Regards

    Hi Raghavendra, thanks for your reply
    Here is the content of the dump
    Runtime Errors         DBIF_RSQL_SQL_ERROR
    Exception              CX_SY_OPEN_SQL_DB
    Date and Time          19.11.2010 11:19:45
    Short text
    SQL error in the database when accessing a table.
    What can you do?
    Note which actions and input led to the error.
    For further help in handling the problem, contact your SAP administrator
    You can use the ABAP dump analysis transaction ST22 to view and manage
    termination messages, in particular for long term reference.
    How to correct the error
    Database error text........: "Cursor HCACHEDCSRN00339 not open. MSGID=
    Job=067809/PRE00/WP26"
    Internal call code.........: "[RSQL/FTCH/LFA1 ]"
    Please check the entries in the system log (Transaction SM21).
    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:
    "DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
    "SAPLWYSE" or "LWYSEF02"
    "LFA1_DATEN_LESEN_CURSOR"
    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
    "LFA1_DATEN_LESEN_CURSOR" "(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 701
    Application server... "ERPPRD"
    Network address...... "10.16.40.23"
    Operating system..... "OS400"
    Release.............. "6.1"
    Hardware type........ "00100007B87A"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 26
    Shortdump setting.... "full"
    Database server... "ERPPRD"
    Database type..... "DB400"
    Database name..... "PRE"
    Database user ID.. "R3PREDATA"
    Terminal.......... " "
    Char.set.... "C"
    SAP kernel....... 701
    created (date)... "May 23 2010 21:51:44"
    create on........ "AIX 2 5 00CB5A5B4C00 (IBM iSeries with OS400)"
    Database version. "DB4_53"
    Patch level. 94
    Patch text.. " "
    Database............. "V5R3, V5R4, V6R1, V7R1"
    SAP database version. 701
    Operating system..... "OS400 3 5, OS400 4 5, OS400 1 6, OS400 1 7"
    Memory consumption
    Roll.... 16192
    EM...... 29328936
    Heap.... 0
    Page.... 32768
    MM Used. 2610000
    MM Free. 18335840
    User and Transaction
    Client.............. 300
    User................ "ALEREMOTE"
    Language key........ "S"
    Transaction......... " "
    Transactions ID..... "4CE5FF2B4DA21FDDE10080030A102817"
    Program............. "SAPLWYSE"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
    Information on where terminated
    Termination occurred in the ABAP program "SAPLWYSE" - in
    "LFA1_DATEN_LESEN_CURSOR".
    The main program was "SBIE0001 ".
    In the source code you have the termination point in line 620
    of the (Include) program "LWYSEF02".
    The program "SAPLWYSE" was started as a background job.
    Job Name....... "BIREQU_4JVYLR3Y1HW25Z7MZZK6TJRQ1"
    Job Initiator.. "ALEREMOTE"
    Job Number..... 11194000
    The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
    procedure "LFA1_DATEN_LESEN_CURSOR" "(FORM)", but it was neither handled
    locally nor declared
    in the RAISING clause of its signature.
    The procedure is in program "SAPLWYSE "; its source code begins in line
    616 of the (Include program "LWYSEF02 ".

  • Dump when run in background

    Hi All,
    I have a z-report which displays a ALV report. when I run this in background it gets canceled. when i see the log , it has dump and dump is as shown below.
    A RAISE statement in the program "CL_GUI_CONTROL================CP" raised the exception condition "CNTL_ERROR".
    Since the exception was not intercepted by a superior
    program, processing was terminated.
    What could be the problem, suggest me a solution if i have to add some code into my program or is it an application error which can be solved by SAP Notes.
    Regards
    Divakar Goud,

    Are you using GUI_UPLOAD or GUI_DOWNLOAD in the report then they will not work there.
    Use OPEN DATASET instead to read or write.
    Also, check weather there is a Container for OO ALV on the Report then use Docking Containe when SY_BATCH = 'X'.
    If its an normal ALV then Change the GRID to LIST layout for Backgroud. Its not that we cannot display grid in background we can do that but we require some layout handling there.
    ALV Grid in background job?
    Regards,
    Amit
    Reward all helpful replies.

  • Program giving dump when run in background

    Hi All,
    I have an ALV report in which I am using REUSE_ALV_GRID_DISPLAY.
    The report works perfectly in foreground. But when I execute in background I am getting dump.
    Dump details are given below.
    ShrtText
        Unable to fulfil request for 134217728 bytes of memory space.
    What happened?
        Each transaction requires some main memory space to process
        application data. If the operating system cannot provide any more
        space, the transaction is terminated.
    What can you do?
        Try to find out (e.g. by targetted data selection) whether the
        transaction will run with less main memory.
        If there is a temporary bottleneck, execute the transaction again
        If the error persists, ask your system administrator to check the
        following profile parameters:
        o  ztta/roll_area            (1.000.000 - 15.000.000)
               Classic roll area per user and internal mode
               usual amount of roll area per user and internal mode
        o  ztta/roll_extension       (10.000.000 - 500.000.000)
               Amount of memory per user in extended memory (EM)
        o  abap/heap_area_total      (100.000.000 - 1.500.000.000)
               Amount of memory (malloc) for all users of an application
               server. If several background processes are running on
               one server, temporary bottlenecks may occur.
               Of course, the amount of memory (in bytes) must also be
               available on the machine (main memory or file system swap).
               Caution:
               The operating system must be set up so that there is also
               enough memory for each process. Usually, the maximum address
               space is too small.
               Ask your hardware manufacturer or your competence center
               about this.
               In this case, consult your hardware vendor
        abap/heap_area_dia:        (10.000.000 - 1.000.000.000)
               Restriction of memory allocated to the heap with malloc
               for each dialog process.
        Parameters for background processes:
        abap/heap_area_nondia:        (10.000.000 - 1.000.000.000)
               Restriction of memory allocated to the heap with malloc
               for each background process.
        Other memory-relevant parameters are:
        em/initial_size_MB:         (35-1200)
               Extended memory area from which all users of an
               application server can satisfy their memory requirement.
        Make a note of the actions and input which caused the error.
        To resolve the problem, contact your SAP system administrator.
        You can use transaction ST22 (ABAP Dump Analysis) to view and administer
        termination messages, especially those beyond their normal deletion
        date.
    Error analysis
        More main memory area was requested.
        However, all the available space has been used up.
        Possible reasons:
        - Many (large) internal tables.
        - Many (large) programs active.
        - Deep nesting of subroutines with a lot of local data.
    Can you please help on this ?

    Hi,
    Check you code properly.
    The dump is because of an infinite loop which is running when you run the program in background and it is keeping appending or inserting the same table.
    Check teh same.
    regards,
    Ankur Parab

  • Dump while running report in background

    Hi Experts,
    I have created one report to create the conditions record by using BDC. The program is uploading the data from file which is located at local server and at selection screen, path of file is defined.
    When i run the report in foreground it works fine, first it uploaded that data and then created BDC and record saved successfully.  But if i run the program in background and check the job status through SM37 , job get canceled due to the dump. The dump message is "Exception condition "NO_BATCH" raised."
    The FM which i am using currently in my code to upload the data is "GUI_UPLOAD", i tried the same thing with FM "ALSM_EXCEL_TO_INTERNAL_TABLE" as well, but same dump is coming.
    Please advice if anyone have some solution.
    Thanks & Regards,
    Swati

    Hi,
    The FM GUI_UPLOAD, wont work in the background jobs. This is the reason for the dump.
    As the backround job runs at the application server, the program cannot identidy the presentation server (local system) file path.
    To avoid this store and read file from application server.
    Thanks & Regards,
    Navneeth K.

  • Short dump GETWA_NOT_ASSIGNED while transporting Datasource in BI 7.0

    Hi Friends,
    I am getting an error, while trying to transport Datasource into quality system. The Transport request log says that "Program terminated (job: RDDEXECL, no.: 11372100)"
    If I check the log in SM37 of target system it gives following steps
    29.06.2007 11:37:21 Job started
    29.06.2007 11:37:21 Step 001 started (program RDDEXECL, variant , user ID DDIC)
    29.06.2007 11:37:21 All DB buffers of application server bdhp4488 were synchronized
    29.06.2007 11:37:30 SQL: 29.06.2007 11:37:30 DDIC
    29.06.2007 11:37:30  CREATE UNIQUE INDEX "/BIC/B0000566001~0" ON
    29.06.2007 11:37:30 "/BIC/B0000566001" ("REQUEST", "DATAPAKID",
    29.06.2007 11:37:30 "PARTNO", "RECORD") PCTFREE 10 LOCAL INITRANS 002
    29.06.2007 11:37:30 TABLESPACE PSAPSR3 STORAGE (INITIAL
    29.06.2007 11:37:30 0000000016 K NEXT        0000000160 K MINEXTENTS
    29.06.2007 11:37:30 0000000001
    If I see the short dump in ST22 in target system (quality) The I get error
    "Runtime Errors         GETWA_NOT_ASSIGNED"
    Could somebody help me in resolving this?
    Thanks and regards,
    Balaraj

    Thanks Edwin,
    My issue is still not resolved.
    Now the error that I am getting while transporting the Transformation is
    Program terminated (job: RDDEXECL, no.: 12091300)
    The SM37 job log says that
    "Job started
    Step 001 started (program RDDEXECL, variant , user ID DDIC)
    All DB buffers of application server bdhp4488 were synchronized
    ABAP/4 processor: GETWA_NOT_ASSIGNED
    Job cancelled"
    When i see the dump in ST22. It says that it could not find entry in one of the tables
    "   READ TABLE p_t_mapping ASSIGNING <fs_map>
       WITH KEY target_stepid = 0
                targetsegid   = <fs_posit>-rulesegid
                targetposit   = <fs_posit>-ruleposit
                targetid      = 0.
    Sy-subrc <> 0 for this read.
    Could you please advise?
    Thanks and regards,
    Balaraj

  • Dump while running a stock report for one year

    hi experts,
                        i'm getting  dump error while running a stock summary report for one year
            the error is as follows:
      A RAISE statement in the program "CL_GUI_CUSTOM_CONTAINER=======CP" raised the
       exception
      condition "CNTL_ERROR".
    regards,
    andrews.

    Hi Andrew,
    Did you try running the report for a smaller period of maybe a month. Check for any authorisation related issues.
    The dump has a lot of detailed and valuable information about the error. If feasible, post the dump data for further analysis.
    Regards,
    Pranav.
    Edited by: Pranav Mandelia on Sep 6, 2011 2:07 PM

  • Dump while running MRP: MD03:   PERFORM_CONFLICT_TAB_TYPE CX_SY_DYN_CALL_IL

    Dear All,
    I am trying to run MRP for a single item at a single level. The program is giving a dump.
    If anyone knows a way around kindly tell me.
    Thanks. Anu.
    SHORT DUMP:
    Runtime errors         PERFORM_CONFLICT_TAB_TYPE                                         
    Exception              CX_SY_DYN_CALL_ILLEGAL_TYPE                                       
           Occurred on     28.02.2008 at   12:19:49                                                                               
    Illegal type when passing an internal table to a FORM                                                                               
    What happened?                                                                               
    Error in ABAP application program.                                                                               
    The current ABAP program "SAPLEINU" had to be terminated because one of the              
    statements could not be executed.                                                                               
    This is probably due to an error in the ABAP program.                                    
    A FORM was called incorrectly.                                                                               
    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.                                                                               
    Error analysis                                                                               
    An exception occurred. This exception is dealt with in more detail below                 
    . The exception, which is assigned to the class 'CX_SY_DYN_CALL_ILLEGAL_TYPE',           
    was neither                                                                             
    caught nor passed along using a RAISING clause, in the procedure                         
    "ME_UPDATE_AGREEMENT_PO" "(FUNCTION)"                                                   
    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:                                                         
    Incorrect FORM call.                                                                     
    The FORM call is incorrect for parameter number 1.                                       
    The current internal table passed to the formal table parameter has                      
    a type that is not compatible with the type of the formal parameter.                     
    The condition selected below has been violated:                                                                               
    (" ") The access types defined for the tables are incompatible.                          
          The following hierarchy shows the compatibility rules:                                                                               
    ANY_TABLE                                                                               
                        INDEX_TABLE   HASHED_TABLE                                           
                STANDARD_TABLE    SORTED_TABLE                                                                               
    A concrete access type is only compatible with types higher                        
          in the hierarchy. For example, STANDARD_TABLE is compatible                        
          with INDEX_TABLE and ANY_TABLE, but not with HASHED_TABLE.                                                                               
    ("X") The line types of the tables are incompatible.                                                                               
    (" ") The table keys of the tables are not identical.                                                                               
    (" ") One of the tables has a UNIQUE key, but the other has a                            
          NON-UNIQUE key.                                                                               
    How to correct the error                                                                               
    The exception must either be prevented, caught within the procedure                      
    "ME_UPDATE_AGREEMENT_PO"                                                                
    "(FUNCTION)", or declared in the procedure's RAISING clause.                             
    To prevent the exception, note the following:                                                                               
    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:                                                                               
    "PERFORM_CONFLICT_TAB_TYPE" CX_SY_DYN_CALL_ILLEGAL_TYPEC                                 
    "SAPLEINU" or "LEINUU04"                                                                 
    "ME_UPDATE_AGREEMENT_PO"                                                                 
    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.

    Dear All,
    I am trying to run MRP for a single item at a single level. The program is giving a dump.
    If anyone knows a way around kindly tell me.
    Thanks. Anu.
    SHORT DUMP:
    Runtime errors         PERFORM_CONFLICT_TAB_TYPE                                         
    Exception              CX_SY_DYN_CALL_ILLEGAL_TYPE                                       
           Occurred on     28.02.2008 at   12:19:49                                                                               
    Illegal type when passing an internal table to a FORM                                                                               
    What happened?                                                                               
    Error in ABAP application program.                                                                               
    The current ABAP program "SAPLEINU" had to be terminated because one of the              
    statements could not be executed.                                                                               
    This is probably due to an error in the ABAP program.                                    
    A FORM was called incorrectly.                                                                               
    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.                                                                               
    Error analysis                                                                               
    An exception occurred. This exception is dealt with in more detail below                 
    . The exception, which is assigned to the class 'CX_SY_DYN_CALL_ILLEGAL_TYPE',           
    was neither                                                                             
    caught nor passed along using a RAISING clause, in the procedure                         
    "ME_UPDATE_AGREEMENT_PO" "(FUNCTION)"                                                   
    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:                                                         
    Incorrect FORM call.                                                                     
    The FORM call is incorrect for parameter number 1.                                       
    The current internal table passed to the formal table parameter has                      
    a type that is not compatible with the type of the formal parameter.                     
    The condition selected below has been violated:                                                                               
    (" ") The access types defined for the tables are incompatible.                          
          The following hierarchy shows the compatibility rules:                                                                               
    ANY_TABLE                                                                               
                        INDEX_TABLE   HASHED_TABLE                                           
                STANDARD_TABLE    SORTED_TABLE                                                                               
    A concrete access type is only compatible with types higher                        
          in the hierarchy. For example, STANDARD_TABLE is compatible                        
          with INDEX_TABLE and ANY_TABLE, but not with HASHED_TABLE.                                                                               
    ("X") The line types of the tables are incompatible.                                                                               
    (" ") The table keys of the tables are not identical.                                                                               
    (" ") One of the tables has a UNIQUE key, but the other has a                            
          NON-UNIQUE key.                                                                               
    How to correct the error                                                                               
    The exception must either be prevented, caught within the procedure                      
    "ME_UPDATE_AGREEMENT_PO"                                                                
    "(FUNCTION)", or declared in the procedure's RAISING clause.                             
    To prevent the exception, note the following:                                                                               
    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:                                                                               
    "PERFORM_CONFLICT_TAB_TYPE" CX_SY_DYN_CALL_ILLEGAL_TYPEC                                 
    "SAPLEINU" or "LEINUU04"                                                                 
    "ME_UPDATE_AGREEMENT_PO"                                                                 
    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.

  • ABAP dump when running an ALV report in a portal

    Hi,
      I have an ABAP report created in SAP R/3 4.7. Am using the ALV function module REUSE_ALV_GRID_DISPLAY to display the output. The programs runs correctly when run in R/3 using the SAP GUI.
      When the report is run in the portal, I get a runtime error 'MESSAGE_TYPE_X'.
      Please let me know if anybody has faced such issues.
    I checked the OSS note 702732 which talks about increasing the threshold value of the start parameter. But this is not agreed by the BASIS team.
    Thanks,
    Best regards,
    Ajith
    The ST22 error log is as follows:
    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?
    Print out the error message (using the "Print" function)
    and make a note of the actions and input that caused the
    error.
    To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
    termination messages, especially those beyond their normal deletion
    date.
    Error analysis
    Short text of error message:
    Data volume (84.550.400 bytes) is too large. (abap/alvgrid/size_nodod_mb
    Technical information about the message:
    Diagnosis
         You tried to send a data record to the front-end that contains
         84.550.400 bytes. However, the data volume is restricted to
         52.428.800 bytes.
    System Response
         The running application program was terminated with a runtime
         error.
    Procedure
         Restrict the data selection if possible or contact your system
         administrator.
    Procedure for System Administration
         You can set the maximum size of these data volumes using the kernel
         parameter 'abap/alvgrid/size_nodod_mb'  (in megabytes).
    Message classe...... "S>"
    Number.............. 890
    Variable 1.......... "84.550.400"
    Variable 2.......... "52.428.800"
    Variable 3.......... " "
    Variable 4.......... " "
    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:
    "MESSAGE_TYPE_X" C
    "SAPLAWRT" or "LAWRTU22"
    "ITS_CHECK_ALV_DATA_SIZE"
    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.
    Information on where terminated
    The termination occurred in the ABAP program "SAPLAWRT" in
    "ITS_CHECK_ALV_DATA_SIZE".
    The main program was "Z_BW_RECON_INV_RPT ".
    The termination occurred in line 25 of the source code of the (Include)
    program "LAWRTU22"
    of the source code of program "LAWRTU22" (when calling the editor 250).
    Source code extract
    000010   FUNCTION ITS_CHECK_ALV_DATA_SIZE.
    000020   *"
    000030   ""Lokale Schnittstelle:
    000040   *"  IMPORTING
    000050   *"     REFERENCE(DATA_TABLE) TYPE  TABLE
    000060   *"
    000070
    000080     data n type i.
    000090     data currsize type i.
    000100     statics maxsize type i.
    000110     data par_value(56).
    000120     if maxsize is initial.
    000130       sy-subrc = 0.
    000140       CALL 'C_SAPGPARAM'  ID 'NAME' FIELD 'abap/alvgrid/size_nodod_MB'
    000150                           id 'VALUE' field par_value.
    000160       if sy-subrc ne 0.
    000170         maxsize = 52428800.       " Default 50 MB
    000180       else.
    000190         maxsize = 1048576 * par_value.
    000200       endif.
    000210     endif.
    000220     describe table data_table lines n.
    000230     currsize = sy-tfill * sy-tleng.
    000240     if currsize gt maxsize.
         >       message x890(s>) with currsize maxsize.
    000260     endif.
    000270   ENDFUNCTION.

    HI,
    This is a Memory problem.
    System is allocated with a Max Memory of 50 MB,(see the dump code, in the last it is hardcoded in the std code)
    The data of your report is coming around 83 MB.
    Restrict your selection criteria of the Object and run the same report and see. it will work.
    Regards,
    Anji

  • Dump while running payroll

    Dear Expert,
    Please correct if i am wrong.
    We always run payroll with Log only.It does not matter,we are running in test mode or in live run.
    Now in my current situation,, when i am running payroll for 2500 emp, system is giving dump stating that no memory location.
    Then basis guy increase the memory allocation, but still giving the error.
    Now my basis guy said that, you have to run payroll in background.
    SO how should i go now.
    Request to all experts, please share some information on this.
    Regards,
    sharma

    Dear Remi,
    Thanks a lot for reply on the same.
    Yes i run payroll without log.and also that time its working fine.
    I request to you,, please advice me we should run payroll with log or without log in simulation as well in Live run.
    Accordingly i update you by checking all the things.
    Regards,
    sharma

  • Dump while running in FG mode at different places

    We are running a Z transaction which is related to some trading of shares.
    It is handling huge data.
    when run in fore ground, its throwing dump at different places each time, its run.
    For ex: CL_OS_CA_COMMON->Method SM_UPDATE_SUBSCRIPTIONS
    In a different run, it failed at class CA_COL_POSITION_TRQ -> Method MAP_LOAD_FROM_DATABASE_GUID.
    But the reason it states in both the cases is Maximum permitted time is reached.
    We tried to improve the performance of the program technically and still getting dump.
    So we want to post a message to SAP. For this, I need to know the module am dealing with. How Do I find that exactly.
    As I was extracting my main data from table FMFINCODE, I thought its FUND MANAGEMENT.
    Please help me in both the cases.
    I also want to know, if a class is released for customer re-use or not?
    Thanks
    Kiran

    Hi Rob,
    Do you mean to say, SAP doesnt support custom transactions?
    I did try se30 but I tried to reduce to the extent I could.
    Any thoughts on the last question? If a class is for Customer re-use.
    Thanks
    Kiran

  • DUMP while running the program RSAR_RSISOSMAP_REPAIR

    Hi Experts,
    I am facing the dump while executing the DTP. the dump is ITAB_DUPLICATE_KEY.to fix the error  ITAB_DUPLICATE_KEY I am referring to the below link :
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/a04c82eb-ec7c-2c10-7fae-ca6e764c483a&overridelayout=true
    i have run the program RSAR_RSISOSMAP_REPAIR with the repair indicator set.
    the issue is its not executing successfully.kinldy help me in this.
    the abap errror i m getting while execution of program RSAR_RSISOSMAP_REPAIR is as :
    TSPREFIX for TCD500-1 not found.
    Kindly help me in resolving the above error TSPREFIX for TCD500-1 not found, where TCD500-1 is my development R/3 system .
    Kindly advise.
    thanks & regards ,
    M.S
    Edited by: M.S on Dec 9, 2009 6:41 AM

    Hi,
    1) TCD for testing transactions, especially those that do not use controls
    2)TCD has the following advantages
    3)It has a built in screen simulation for standard screen element
    4) No GUI is required for playback
    5)  It is suitable for load testing
    6) The TCD command has the same limitations as the CATT function of the same name. The flow of data to and from controls, as well as screen input values, are recorded. When the test script runs, the controls are deactivated and the user's actions are simulated by reading the recorded data flows
    For more info on TCD go through the below link
    http://help.sap.com/saphelp_sm32/helpdata/en/83/77cd3b4261706fe10000000a11402f/content.htm
    Regards,
    Marasa.

Maybe you are looking for