Dump while running Workflow

Hi Gurus,
I get the following dump whenever I execute my workflow :
The following syntax error occurred in the program                     
CL_SWF_RUN_WIM_LOCAL==========CP :                                    
"You can only define attributes in the PUBLIC, PROTECTED or PRIVATE section"
Error in ABAP application program.                                                                               
The current ABAP program "CL_SWF_RUN_WIM_FACTORY========CP" had to be  
terminated because one of the                                         
statements could not be executed.                                                                               
This is probably due to an error in the ABAP program.                  
I have checked the workflow config in SWU3 and find all green tick marks.
As suggested in the Dump I did the syntax check on the  Class Interface CL_SWF_RUN_WIM_LOCAL
I get the following  Syntax error.
Include <SWFCNTN01>
You can only define attributes in the PUBLIC,PROTECTED or PRIVATE section.
Can  anybody  advice me on how should I go ahead and  rectify this Syntax error.
I have checked that the  Include <SWFCNTN01> is defined in the Program SAPLSWUS and the Include
LSWUSTOP.
Any help is appreciated.
Thanks,
Bluesh

Include <SWFCNTN01>
Why are you using the above include? to use the macros for creating conatiner and passing teh elements.
Then instead of the above one try to use INCLUDE cntn01_swc

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

  • Short Dump While Running infopackage

    Hello All,
    While Running infopackae for Master data i am getting a dump MESSAGE_TYPE_X" C
    CL_RSDMD_UPDATE_MASTER_DATA===CP" or "CL_RSDMD_UPDATE_MASTER_DATA===CM00R"
    CHECKDATA_PACKET".
    Data is comming to PSA without any Errors,But while loading to Infoobject Table i am getting the Dump.
    What can be the problem?

    Hi,
    Force the request to red and reload to PSA first and then to target manually.
    When the load is not getiing processed due to huge volume of data, or more number of records per data packet, Please try the below option.
    1) Reduce the IDOC size to 8000 and number of data packets per IDOC as 10. This can be done in info package settings.
    2) Run the load only to PSA.
    3) Once the load is succesfull , then push the data to targets.
    In this way you can try to overcome this issue.
    Thanks,
    JituK

  • Short dump while running Alert Monitor

    Hi,
    I am getting a short dump while determining alert in Alert Monitor through T. Code /SAPAPO/AMON1. The error says as below:
    Runtime Errors         BCD_NO_SIGN
    Short text : A packed number contains no sign.
    What happened? : Error in the ABAP Application Program, The current ABAP program "SAPLKKBL" had to be terminated because it has come across a statement that unfortunately cannot be executed.       
    Information on where terminated : Termination occurred in the ABAP program "SAPLKKBL" - in "FB_OUTTAB_SORT2".

    Hi Axon Generic,
    Please checkon the following
    1) In the overall profile of alert monitor, check the relative
    time interval whether specified correctly
    2) Under the alert profile in Overall profile, check the
    threshold values are defined correctly
    3) Check the SAP Note 151709 , 189061
    Please confirm your findings.
    Regards
    R. Senthil Mareeswaran.

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

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

  • DUMP while running my import FM

    Hi ALL,
    I have import request and i got sucess .My 3 function modules are import to client system.2 FM are working properly but 1 function module is going for DUMP.
    I have gone dump analysis its saying
    An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assigned to the class 'CX_SY_IMPORT_MISMATCH_ERROR',
    was neither
    caught nor passed along using a RAISING clause, in the procedure
    "MO_IMPORT_MODIFICATIONS" "(METHOD)"
    "Length error occurred during the IMPORT statement."
    "The system found when importing that the target object was longer or
    shorter than the object to be imported."
    where did i mistake while import ? or while transport?
    That FM is working properly in our DEV.
    Thanks in Advance,
    Madhu.

    If you go from se37 and se80 same result ..its going for DUMP.
    it giving me error in this SAP std method   MO_IMPORT_MODIFICATIONS
    Length error occurred during the IMPORT statement.
    <<<<< IMPORT old_import    TO old_import
               old_export    TO old_export
               old_change    TO old_change
    Madhu

  • 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

  • Reg : Short Dump While Activating Workflow

    Hi All,
    This morning I added a condition step in my workflow and created two custom methods in the corresponding BO and used them in the task. Initially when i made the changes in the workflow and tested it, it was working fine. But after sometime, when I did the necessary binding and tried to activate the workflow, the workflow started resulting in short dump.
    Below is the dump analysis.
    SAPSQL_ARRAY_INSERT_DUPREC
    The ABAP/4 Open SQL array insert results in duplicate database records.
    000310        L_OTYPE EQ ORG_OBJTYPE_WORKFLOW.
    000320       LOOP AT ACT_LINES.
    000330         MOVE-CORRESPONDING ACT_WFDKEY TO ACT_LINES.
    000340         MOVE ACT_CLIENT TO ACT_LINES-CLIENT.
    000350         MODIFY ACT_LINES.
    000360       ENDLOOP.
    000370     ELSE.
    000380       MESSAGE E280 WITH L_OTYPE RAISING INVALID_OBJECT_TYPE.
    000390     ENDIF.
    000400
    000410   *- insert lines table
    ------>     INSERT SWD_LINES CLIENT SPECIFIED FROM TABLE ACT_LINES.
    000430     IF SY-SUBRC NE 0.
    000440       MESSAGE E281 WITH SY-SUBRC 'SWD_LINES'
    000450                    RAISING INTERNAL_DATABASE_ERROR.
    000460     ENDIF.
    000470
    000480   *- commit
    000490     IF DO_COMMIT NE ' '.
    000500       COMMIT WORK.
    000510     ENDIF.
    000520
    000530   ENDFUNCTION.
    I tried searching sdn. But all other posts were related to passing entries from internal table to DB. Also I'm not even sure if i can raise a OSS, because a few minutes back the system was working fine and all of sudden this started happening.
    So can you please guide me what I am missing and how can i fix this?
    Thanks & Regards,
    Raj

    Hi Rick,
    When I get acitvate the workflow, the workflow template is gettign active & saved and after that the system results into short dump. And also when i try creating a PR and test this workflow, in SWEL, i can see the below message in RFC status field.
    The ABAP/4 Open SQL array insert results in duplicate database records..
    I haven't done any duplicate binding. Also I checked what you suggested. Didn't work. Also checked my newly added code. But I'm not accessing database directly anywhere. All is done via SAP standard function module.
    Even if i try to display this workflow in PFTC, the system is resulting in the same short dump.
    What could be the reason?
    Regards,
    Raj
    Edited by: Raj  Karunanidhi on Feb 23, 2010 5:30 AM

  • SPOOL_INTERNAL_ERROR short dump while running RBDAPP01

    I recently encountered this run-time error when processing IDOCs.
    The IDOC message type was WMMBXY, if that helps.
    We have been using this message type and have been processing thousands of these transactions for years,
    and this just suddenly happened.  We got other IDOCs of the same message type to process successfully after
    this error occurred, so I think it is some sort of data issue.
    We were simply trying to process a simple PO Goods receipt (movement type 101), so this is nothing unique.
    Has anyone else out there experienced this issue before?
    I would appreciate any help you can give.
    Thanks.
    Mike

    Hi Michael,
    please check the SAP notes regarding SPOOL_INTERNAL_ERROR.
    I have found 15 notes, for example the newest ones:
    http://service.sap.com/sap/support/notes/1888199
    http://service.sap.com/sap/support/notes/1953355
    Regards,
    Klaus

Maybe you are looking for