Short dump when executing DTP

Dear Gurus,
I am loading 2lis_02_hdr and 2lis_02_itm data in to customized ODS.
it loaded sucessfully up to PSA level, when i am loading through DTP it shows the abap runtime error as "CREATE_DATA_UNKNOWN_TYPE"
let me know the solution for the above..urgent

Hi Ravindra,
As you said i have gone through transformations once again, I mapped the correct data type only.
Including the above error mentioned i am also facing runtime error message as MESSAGE_TYPE_X

Similar Messages

  • SHORT DUMP WHILE EXECUTING DTP.

    Hi Gurus,
    I have got a short dump while executing DTP the Error is as Follows.
    Runtime Error: MESSAGE_TYPE_X.
    Reasons for Error: 1.The installation of the SAP GUI on the present server is faulty or obselete
    2.There is a error in the application program
    And i have sent the sreen shot of the Short Dump to BASIS TEAM and they have replied me that they have to install some patches and it will take some time.
    But i have no much time and i have to someway or the other execute the DTP and load the data.
    Is there any shortcuts for this i mean to say without the involvement of Basis team that i can do in th BI System
    Regards
    Amar.

    Hi Amar,
    If the problem is with with System itself, how can we all have a short cut in that case. You may give it another trial, but you have to wait for the patches to be applied. Ask your basis team to get it done ASAP.
    Thanks..
    Shambhu

  • ABAP Dump when executing DTP

    Dear gurus:
           I just faced an annoying problem when executing DTP in t-code RSA1. It appears an  ABAP dump here. The ABAP dump is briefly shown below. And I found that it seems to be an authorization problem, because when I use a new account which has SAP_ALL authorization, then it works. So it may lack of some authorizations, but it's hard to figure it out. T-code su53 cannot check it properly. Need your help and thanks a lot.
    Runtime Errors         MESSAGE_TYPE_X
    Date and Time          2007.06.20 11:17:30
    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:
         Invalid program status
         Long text of error message:
         Technical information about the message:
         Message class....... "RSBK"
         Number.............. 299
         Variable 1.......... " "
         Variable 2.......... " "
         Variable 3.......... " "
         Variable 4.......... " "

    Hai Wei,
    This dump is due missing of OCX files while installing SAP GUI Front end just find out the exact files and copy and paste them in the Front end files files then ur prob will be solved.......
    If in case any issues let me know.
    Regards
    Madhavi

  • Short dump when executing the query

    Hello Friends,
                         I have a query from MM area which I have insalled from Business Content , and when I try to go to the edit mode or try to excute the query I get a short dump which says "Missing elements ..", I get the same dump when executing from query designer or RSRT . At this time I'm not able to do a "check" on the query also n query designer since it doesnot allow me to go to the edit mode also . Any inputs greatly appreciated .
    thanks ,

    Hi,
    While activating it from the Business Content, have you activated all the underlying objects also. Pls check that. It might help.

  • Getting Short dump When Executing MIGO:    SYNTAX_ERROR

    Please Help,
    I am getting this dump, when i hit MIGO transaction
    Runtime Errors         SYNTAX_ERROR
    Date and Time          10.12.2008 08:28:03
         Short text
              Syntax error in program "MB_MIGO_BADI==================CP ".
         What happened?
              Error in the ABAP Application Program
              The current ABAP program "CL_EX_MB_MIGO_BADI============CP" had to be
               terminated because it has
              come across a statement that unfortunately cannot be executed.
              The following syntax error occurred in program
               "MB_MIGO_BADI==================CP " in include
               "MB_MIGO_BADI==================CM000 " in
              line 0:
              "The specified type cannot be converted into the target variables."
              The include has been created and last changed by:
              Created by: "SAP "
              Last changed by: "SAP "
              Error in the ABAP Application Program
              The current ABAP program "CL_EX_MB_MIGO_BADI============CP" had to be
               terminated because it has
              come across a statement that unfortunately cannot be executed.
         What can you do?
              Please eliminate the error by performing a syntax check
              (or an extended program check) on the program "MB_MIGO_BADI==================CP
              You can also perform the syntax check from the ABAP Editor.
              If the problem persists, proceed as follows:
              Note down which actions and inputs caused the error.
              To process the problem further, contact you SAP system
              administrator.
              Using Transaction ST22 for ABAP Dump Analysis, you can look
              at and manage termination messages, and you can also
              keep them for a long time.
         Error analysis
              The following syntax error was found in the program
               MB_MIGO_BADI==================CP :
              "The specified type cannot be converted into the target variables."
         How to correct the error
              Probably the only way to eliminate the error is to correct the program.
              If you cannot solve the problem yourself and want to send an error
              notification to SAP, include the following information:
              1. The description of the current problem (short dump)
                 To save the description, choose "System->List->Save->Local File
              (Unconverted)".
              2. Corresponding system log
                 Display the system log by calling transaction SM21.
                 Restrict the time interval to 10 minutes before and five minutes
              after the short dump. Then choose "System->List->Save->Local File
              (Unconverted)".
              3. If the problem occurs in a problem of your own or a modified SAP
              program: The source code of the program
                 In the editor, choose "Utilities->More
              Utilities->Upload/Download->Download".
              4. Details about the conditions under which the error occurred or which
              actions and input led to the error.
         System environment
              SAP-Release 700
              Application server... "DMATE"
              Network address...... "140.1.1.141"
              Operating system..... "Windows NT"
              Release.............. "5.2"
              Hardware type........ "4x AMD64 Level"
              Character length.... 16 Bits
              Pointer length....... 64 Bits
              Work process number.. 1
              Shortdump setting.... "full"
              Database server... "dmate"
              Database type..... "ADABAS D"
              Database name..... "AD0"
              Database user ID.. "SAPAD0"
              Char.set.... "C"
              SAP kernel....... 700
              created (date)... "Jun 23 2008 00:09:46"
              create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
              Database version. "SQLDBC 7.6.0.018 CL 119055 "
              Patch level. 166
              Patch text.. " "
              Database............. "MaxDB 7.6, MaxDB 7.7"
              SAP database version. 700
              Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
               NT 6.0"
              Memory consumption
              Roll.... 16192
              EM...... 8379680
              Heap.... 0
              Page.... 40960
              MM Used. 1627776
              MM Free. 2559440
         User and Transaction
              Client.............. 040
              User................ "LAKSHMI"
              Language key........ "E"
              Transaction......... "MIGO "
              Transactions ID..... "EE72C6DDC96BF1F99FA4001143E563CA"
              Program............. "CL_EX_MB_MIGO_BADI============CP"
              Screen.............. "SAPLMIGO 0001"
              Screen line......... 2
         Information on where terminated
              Termination occurred in the ABAP program "CL_EX_MB_MIGO_BADI============CP" -
               in "IF_EX_MB_MIGO_BADI~INIT".
              The main program was "SAPLMIGO ".
              In the source code you have the termination point in line 1
              of the (Include) program "CL_EX_MB_MIGO_BADI============CM001".
         Source Code Extract
         Line     SourceCde
         >>>>>     method IF_EX_MB_MIGO_BADI~INIT.
             2       CLASS CL_EXIT_MASTER DEFINITION LOAD.
             3     
             4       DATA l_badi TYPE REF TO MB_MIGO_BADI.
             5     
             6     
             7     
             8     
             9     
            10       TRY.
            11     
            12         GET BADI l_badi
            13          CONTEXT me.
            14     
            15         CALL BADI l_badi->INIT
            16     
            17          CHANGING
            18            CT_INIT = CT_INIT.
            19     
            20     
         Contents of system fields
         Name     Val.
         SY-SUBRC     0
         SY-INDEX     0
         SY-TABIX     1
         SY-DBCNT     1
         SY-FDPOS     1
         SY-LSIND     0
         SY-PAGNO     0
         SY-LINNO     1
         SY-COLNO     1
         SY-PFKEY     
         SY-UCOMM     
         SY-TITLE     
         SY-MSGTY     S
         SY-MSGID     VBDOCUBATCH
         SY-MSGNO     001
         SY-MSGV1     
         SY-MSGV2     
         SY-MSGV3     
         SY-MSGV4     
         SY-MODNO     0
         SY-DATUM     20081210
         SY-UZEIT     082802
         SY-XPROG     
         SY-XFORM     
         Active Calls/Events
         No.   Ty.          Program                             Include                             Line
               Name
             4 METHOD       CL_EX_MB_MIGO_BADI============CP    CL_EX_MB_MIGO_BADI============CM001     1
               CL_EX_MB_MIGO_BADI=>IF_EX_MB_MIGO_BADI~INIT
             3 METHOD       SAPLMIGO                            LMIGOGL2                               54
               LCL_MIGO_GLOBALS=>CLASS_CONSTRUCTOR
             2 FORM         SAPLMIGO                            LMIGOIN1                               11
               INITIALIZATION
             1 MODULE (PBO) SAPLMIGO                            LMIGOPBO                               11
               PBO_INITILIZATION
         Chosen variables
         Name
             Val.
         No.          4     Ty.      METHOD
         Name      CL_EX_MB_MIGO_BADI=>IF_EX_MB_MIGO_BADI~INIT
         CT_INIT
              Table[initial]
         %_DUMMY$$
                 2222
                 0000
                 0000
                 0000
         SYST-REPID
              CL_EX_MB_MIGO_BADI============CP
                 4454554454444544443333333333334522222222
                 3CF58FD2FD97FF2149DDDDDDDDDDDD3000000000
                 0000000000000000000000000000000000000000
                 0000000000000000000000000000000000000000
         SY-SUBRC
              0
                 0000
                 0000
         No.          3     Ty.      METHOD
         Name      LCL_MIGO_GLOBALS=>CLASS_CONSTRUCTOR
         SY-REPID
              SAPLMIGO
                 5454444422222222222222222222222222222222
                 310CD97F00000000000000000000000000000000
                 0000000000000000000000000000000000000000
                 0000000000000000000000000000000000000000
         LCL_MIGO_GLOBALS=>CNTL_ERROR
                 2
                 0
                 0
                 0
         ABAP_FALSE
                 2
                 0
                 0
                 0
         SYST-REPID
              SAPLMIGO
                 5454444422222222222222222222222222222222
                 310CD97F00000000000000000000000000000000
                 0000000000000000000000000000000000000000
                 0000000000000000000000000000000000000000
         GOSEARCH_PO
                 2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
                 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
                 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
                 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
         TEXT-220
              Dest
                 46772222
                 45340000
                 00000000
                 00000000
         %_SPACE
                 2
                 0
                 0
                 0
         %_TAG*TS_GOITEM
              <initial>
                 <initial>
                 <initial>
         X
              X
                 5
                 8
                 0
                 0
         LCL_MIGO_GLOBALS=>IF_BADI
                 F0000000
                 70008000
         %_FL2*TV_GOFREIGHT
              <initial>
                 <initial>
                 <initial>
         %_PRINT
                  000                                                                                0###
                 2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223000
                 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
                 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
                 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
         LCL_MIGO_GLOBALS=>T_BADI
              Table[initial]
         /SPE/CL_INB_ACTION_INFO=>C_DIALOG_MIGO
         SCREEN
                 2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
                 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
                 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
                 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
         OREF_TITLEBAR
                 F0000000
                 F0000000
         L_BADIS_1
              0
                 0000
                 0000
         SY-MSGID
              VBDOCUBATCH
                 54444544544222222222
                 624F3521438000000000
                 00000000000000000000
                 00000000000000000000
         OREF_TIP
                 F0000000
                 F0000000
         TV_GOSERIAL-CX
              <initial>
                 <initial>
                 <initial>
         SPACE
                 2
                 0
                 0
                 0
         SY-MSGNO
              001
                 333
                 001
                 000
                 000
         No.          2     Ty.      FORM
         Name      INITIALIZATION
         OREF_ARCH
                 F0000000
                 F0000000
         LCL_MIGO_GLOBALS=>KERNEL
                 F0000000
                 D0002000
         %_CX_TABLEVIEW_VERSION
              0
                 3
                 0
                 0
                 0
         GODEFAULT-DEF_XBOM
                 2
                 0
                 0
                 0
         LCL_MIGO_GLOBALS=>KERNEL->C_REFDOCTYPE_MATDOC
              MAT
                 445
                 D14
                 000
                 000
         No.          1     Ty.      MODULE (PBO)
         Name      PBO_INITILIZATION
         GOITEM-UMWRK
                 2222
                 0000
                 0000
                 0000
         GOITEM-UMNAME1
                 222222222222222222222222222222
                 000000000000000000000000000000
                 000000000000000000000000000000
                 000000000000000000000000000000
         Internal notes
              The termination was triggered in function "ab_genprog"
              of the SAP kernel, in line 1551 of the module
               "//bas/700_REL/src/krn/runt/abgen.c#10".
              The internal operation just processed is "CPOP".
              Internal mode was started at 20081210082802.
              Program name.........: "MB_MIGO_BADI==================CP ".
              Error message........: "The specified type cannot be converted into the target
               variables.".
         Active Calls in SAP Kernel
         Lines of C Stack in Kernel (Structure Differs on Each Platform)
         SAP (R) - R/3(TM) Callstack, Version 1.0
         Copyright (C) SAP AG. All rights reserved.
         Callstack without Exception:
         App       : disp+work.EXE (pid=5776)
         When      : 12/10/2008 8:28:3.84
         Threads   : 2
         Computer Name       : DMATE
         User Name           : SAPServiceAD0
         Number of Processors: 4
         Processor Type: EM64T Family 15 Model 4 Stepping 1
         Windows Version     : 5.2 Current Build: 3790
         State Dump for Thread Id 14f0
         FramePtr         ReturnAd         Param#1          Function Name
         0000000007eb8800 0000000077d7047f 00000000411b4070 ntdll!NtWaitForSingleObject
         0000000007eb88a0 000000000173b1d1 000000000000042c kernel32!WaitForSingleObjectEx
         0000000007eb8af0 00000000006179c5 0000000000000001 disp+work!NTDebugProcess [ntstcdbg.c (501)]
         0000000007eb8b20 0000000000b05d9c 0000000000000001 disp+work!CTrcStack [dptstack.c (182)]
         0000000007eb8b70 0000000000b0afc0 0000000000000001 disp+work!rabax_CStackSave [abrabax.c (7093)]
         0000000007eb9550 0000000000a51c94 0000000001d12320 disp+work!ab_rabax [abrabax.c (1231)]
         0000000007ebc220 00000000007f753a 0000000000000001 disp+work!ab_genprog [abgen.c (1555)]
         0000000007ebc2f0 00000000007f7dc8 00000000ffffffff disp+work!newload [abload1.c (336)]
         0000000007ebc350 00000000007f7e8e 0000000000000056 disp+work!ab_LoadProgOrTrfo [abload1.c (160)]
         0000000007ebc380 00000000007bc84d 000007fe725a5f70 disp+work!ab_LoadProg [abload1.c (78)]
         0000000007ebc450 00000000007be91a 00002a441022f402 disp+work!LoadGlobalClass [abobject.c (943)]
         0000000007ebc4a0 00000000007c1bdd 0000000000000000 disp+work!ab_FillCfix [abobject.c (1603)]
         0000000007ebc580 000000000083ae52 0000000000000000 disp+work!ab_jaboo [abobject.c (2248)]
         0000000007ebc700 0000000000a1ccb7 000000000000000d disp+work!ab_extri [abextri.c (554)]
         0000000007ebc750 0000000000ad50ac 000000000000000d disp+work!ab_xevent [abrunt1.c (281)]
         0000000007ebc7e0 0000000000679328 000000000000000d disp+work!ab_dstep [abdynpro.c (492)]
         0000000007ebc960 000000000067d02d 000007fe725d6f20 disp+work!dynpmcal [dymainstp.c (2396)]
         0000000007ebc9f0 000000000067ca2a 0000000000000000 disp+work!dynppbo0 [dymainstp.c (543)]
         0000000007ebcaa0 00000000006395c5 0000000000000000 disp+work!dynprctl [dymainstp.c (360)]
         0000000007ebfc30 00000000004dbc4c 000000000000000c disp+work!dynpen00 [dymain.c (1646)]
         0000000007ebfeb0 000000000042f096 0000000007f62ff0 disp+work!TskhLoop [thxxhead.c (4538)]
         0000000007ebfee0 000000000040108d ffffffff00000003 disp+work!DpMain [dpxxdisp.c (1136)]
         0000000007ebff10 00000000019e84b1 0000000000000000 disp+work!nlsui_main [thxxanf.c (84)]
         0000000007ebff70 0000000077d5966c 0000000000000000 disp+work!wmainCRTStartup [crtexe.c (498)]
         0000000007ebffa0 0000000000000000 00000000019e8340 kernel32!BaseProcessStart
         State Dump for Thread Id b94
         FramePtr         ReturnAd         Param#1          Function Name
         000000000c9dfe40 0000000077d5f651 0000000000000000 ntdll!NtFsControlFile
         000000000c9dfeb0 00000000018ce23f fffffffffffffffe kernel32!ConnectNamedPipe
         000000000c9dff40 000007ff7fc411c4 0000000000000000 disp+work!SigIMsgFunc [signt.c (679)]
         000000000c9dff70 0000000077d6b69a 0000000077d6b660 msvcrt!endthreadex
         000000000c9dffa0 0000000000000000 0000000000000000 kernel32!BaseThreadStart
         List of ABAP programs affected
         Index     Typ     Program     Group     Date     Time     Size     Lang.
              0     Prg     SAPLMIGO          0     04.05.2008     12:54:34       1561600     E
              1     Prg     SAPMSSYD          0     25.02.2008     17:02:32         21504     E
              2     Prg     SAPFSYSCALLS          0     09.09.2004     14:18:32          7168     E
              3     Prg     CL_MMIM_USERDEFAULTS==========CP          3     06.05.2002     10:42:38         21504     E
              4     Typ     ESDUS          0     01.03.1999     13:36:04          2048     
              5     Typ     GOHEAD          0     07.02.2006     10:07:36         11264     
              6     Typ     MKPF          0     25.08.2005     22:02:19          7168     
              7     Typ     KBEFU          0     16.03.2008     17:46:49          6144     
              8     Typ     LFA1          0     16.03.2008     17:47:20         22528     
              9     Typ     MIGO_CUST_ACTION          0     30.11.1999     10:19:14          3072     
             10     Typ     MIGO_CUST_REFDOC          0     30.11.1999     10:19:14          2048     
             11     Typ     X031L          0     05.07.2005     13:10:15          6144     
             12     Prg     SAPLSDIFRUNTIME         12     19.11.2006     16:35:34         96256     E
             13     Typ     DFIES          0     28.12.2004     17:06:45         10240     
             14     Prg     SAPLSDNT         14     09.03.2008     19:02:04        219136     E
             15     Prg     SAPLSUGS         15     31.03.2006     11:23:11         47104     E
             16     Prg     SAPLV01D         16     24.03.2008     17:03:30         40960     E
             17     Typ     IWRKZ          0     04.04.1995     15:56:46          2048     
             18     Typ     TCUCH          0     07.01.2002     15:50:54          3072     
             19     Typ     TCUBN          0     07.01.2002     15:50:53          2048     
             20     Typ     TCUWS          0     13.08.1997     13:57:58          2048     
             21     Typ     TCUDRV          0     07.01.2002     15:50:54          2048     
             22     Prg     SAPLVBDOCUBATCH_BF         22     16.01.2004     14:28:56         10240     E
             23     Typ     TCUDB          0     14.01.2004     10:05:59          2048     
             24     Prg     CL_GUI_CFW====================CP         24     28.02.2005     21:03:09        168960     E
             25     Prg     CL_GUI_PROPS_CONSUMER=========CP         25     18.03.2008     13:25:33         29696     E
             26     Prg     %_CCNTL         25     18.02.2005     14:15:08         15360     E
             27     Prg     SAPLTHFB         27     18.03.2008     13:24:52        394240     E
             28     Typ     EUDB          0     06.11.2003     20:28:08          8192     
             29     Typ     TCURM          0     01.03.2005     10:56:26          5120     
             30     Prg     CL_EXITHANDLER================CP         30     18.03.2008     13:11:35         30720     E
             31     Prg     SAPLSEXV         31     18.03.2008     13:12:58        117760     E
             32     Typ     SXS_ATTR          0     07.02.2006     10:09:24          5120     
             33     Typ     BADIISIMPLED          0     19.05.2005     19:10:34          3072     
             34     Prg     CL_ENH_BADI_TOOL_UTILITIES====CP         34     17.03.2008     11:03:36         13312     E
             35     Typ     BADI_MAIN          0     08.12.2004     18:01:11          2048     
             36     Typ     BADI_IMPL          0     09.12.2004     19:05:43          3072     
             37     Typ     TADIR          0     07.02.2006     10:08:38          5120     
             38     Prg     CL_SWITCH=====================CP         38     17.03.2008     11:13:47         19456     E
             39     Typ     SFW_PACKAGE          0     07.03.2008     12:18:16          2048     
             40     Prg     CL_ABAP_SWITCH================CP         40     14.10.2006     15:40:30         33792     E
             41     Prg     SAPLPA_PACKAGE_SERVICES         41     18.03.2008     13:12:54        152576     E
             42     Typ     TDEVC          0     08.12.2004     18:02:41          6144     
             43     Prg     CL_EX_MB_MIGO_BADI============CP         43     05.12.2008     17:09:58         30720     E
             44     Prg     IF_EX_MB_MIGO_BADI============IP         30     19.05.2005     19:30:39         14336     E
             45     Typ     SYST          0     09.09.2004     14:18:12         31744     
             46     Typ     GOSEARCH_PO          0     20.07.2001     19:17:34          4096     
             47     Prg     /SPE/CL_INB_ACTION_INFO=======CP         47     24.03.2008     20:30:06         20480     E
             48     Prg     /SPE/IF_CONST=================IP         47     14.10.2006     18:49:02          7168     E
             49     Typ     GODEFAULT          0     14.01.2004     10:04:46          5120     
             50     Typ     GOITEM          0     07.02.2006     10:07:36         65536     
         Directory of Application Tables
         Name                                     Date       Time       Lngth
             Val.
         Program      SAPLMIGO
         SYST            .  .            :  :          00004612
              \0\0\0\0\x0001\0\x0370\0\0\0\0\0\0\0\0\0\0\0\0\0\x0001\0
         GOITEM            .  .            :  :          00005524
                        00000000000000000000
         GOSEARCH_PO            .  .            :  :          00000492
         GODEFAULT            .  .            :  :          00000220
         Program      SAPLV01D
         TCUCH            .  .            :  :          00000122
              0401100020061029095148ANOOPJ      00000000000000
         TCUWS            .  .            :  :          00000060
              040020061227101454CONSULTANT     
         TCUBN            .  .            :  :          00000060
              040020061227101454CONSULTANT     
         TCUDRV            .  .            :  :          00000064
                    00000000000000     
         Program      CL_GUI_PROPS_CONSUMER=========CP
         EUDB            .  .            :  :          00004068
              %CAA72C6DDAD55F1179FA4001143E563CA         \0\0\0
         ABAP Control Blocks (CONT)
         Index     Name     Fl     PAR0     PAR1     PAR2     PAR3     PAR4     PAR5     PAR6     Source Code     Line
            94     BRAX     01     FFEB                                   CL_EX_MB_MIGO_BADI============CM001           15
            95     CLEA     00     0020                                   CL_EX_MB_MIGO_BADI============CM001           15
            96     EXCP     08     0000                                   CL_EX_MB_MIGO_BADI============CM001           22
            97     BRAX     00     0005                                   CL_EX_MB_MIGO_BADI============CM001           22
            98     EXCP     00     0007                                   CL_EX_MB_MIGO_BADI============CM001           22
            99     BRAX     00     0003                                   CL_EX_MB_MIGO_BADI============CM001           22
           100     EXCP     07     0000                                   CL_EX_MB_MIGO_BADI============CM001           22
           101     BRAX     00     0001                                   CL_EX_MB_MIGO_BADI============CM001           23
           102     EXCP     0B     0000                                   CL_EX_MB_MIGO_BADI============CM001           23
           103     METH     01     0000     0000     0000     0000     0000     0000     0000     CL_EX_MB_MIGO_BADI============CM001           24
           107     -
         00     0000                                   CL_EX_MB_MIGO_BADI============CM001           24
           108     ABOO     02     0000     0005     0000                         CL_EX_MB_MIGO_BADI============CM001            1
         >>>>>     CPOP     00     0000                                   CL_EX_MB_MIGO_BADI============CM001            1
           111     -
         00     0000                                   CL_EX_MB_MIGO_BADI============CM001            1
           112     METH     04     0000     0005     0002     0000     0003     0000     0000     CL_EX_MB_MIGO_BADI============CM002            1
           116     PAR2     04     0000     C000     0000                         CL_EX_MB_MIGO_BADI============CM002            1
           118     PAR2     04     0000     C001     0000                         CL_EX_MB_MIGO_BADI============CM002            1
           120     PAR2     14     0000     C002     0000                         CL_EX_MB_MIGO_BADI============CM002            1
           122     PAR2     14     0000     C003     0000                         CL_EX_MB_MIGO_BADI============CM002            1
           124     PAR2     14     0000     C004     0000                         CL_EX_MB_MIGO_BADI============CM002            1

    Hai,
    Seems to be problem with the Program.
    Please check the point 'What Happened' in the dump for more details.
    What happened?
    Error in the ABAP Application Program
    The current ABAP program "CL_EX_MB_MIGO_BADI============CP" had to be
    terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program
    "MB_MIGO_BADI==================CP " in include
    "MB_MIGO_BADI==================CM000 " in
    line 0:
    "The specified type cannot be converted into the target variables."
    Error in the ABAP Application Program
    The current ABAP program "CL_EX_MB_MIGO_BADI============CP" had to be
    terminated because it has
    come across a statement that unfortunately cannot be executed.
    What can you do?
    Please eliminate the error by performing a syntax check
    (or an extended program check) on the program "MB_MIGO_BADI==================CP
    You can also perform the syntax check from the ABAP Editor.
    Take help from a ABAP consultant and try to check the syntax of the Program.
    If you have access even you can check the syntax of the specified program from SE38.
    Goto SE38 and put the program name and select 'Source code' and press F8, IN THE SOURCE CODE PAGE, press control+F2 and check whether there is any problem with the syntax or not.
    If you find any take help from ABAP consultants.
    Hope this helps.
    Regards,
    Yoganand.V

  • Dump when executing DTP right after infopackage in BI 7.0 SP 7

    Hello.
    whenever I try to execute DTP <b>right after</b> run infopackage (eg.master loading), exception error occurs like below.
    <b><u>"A RAISE statement in the program "SAPLRSSTATMAN" raised the exception"</u></b>
    can't find any notes related to this problem in SAP notes.
    that is okay when i try this job with intervals though.(10sec or so.)
    Is there any solution about this?
    Thanks in advance.

    This sounds like you need to create a customer message. You haven't sent the dump but from the process I would guess that some data is still stuck on the database. Anyway a RAISE where you don't find a note is always worth a customer message if you can reproduce it.
    Best regards
    Dirk

  • Short dump when executing report.

    Dear all,
    I’m running a web template report which is calling a multiprovider and within the multiprovider are 9 cubes. All cubes have aggregates and are optimize for performance. Lately, for the past 2 days, users have been complaining that they keep getting error 500, a time out error. This happens only to certain users and not all. Some users are able to query for data more the 5 years where as some not even 1 day. Below is the error which BW is throwing back to us. Can you please help me analyze the error?
    Error analysis
        After a certain length of time, the program is terminated. In the case
        of a work area, this means that
        - endless loops (DO, WHILE, ...),
        - database accesses producing an excessively large result set,
        - database accesses without a suitable index (full table scan)
        do not block the processing for too long.
    Trigger Location of Runtime Error
        Program                                 SAPLRSDRS
        Include                                 LRSDRSF04
        Row                                     116
        Module type                             (FORM)
        Module Name                             FETCH_DATA_OPENSQL
      103
      104     IF <l_s_data>      IS NOT ASSIGNED OR
      105        <l_s_data>      IS NOT ASSIGNED OR
      106        <l_s_data_olap> IS NOT ASSIGNED .
      107       RAISE EXCEPTION TYPE cx_rs_program_error
      108          EXPORTING
      109            method = 'FETCH_DATA_OPEN_SQL-2-'.
      110     ENDIF.
      111   ENDIF.
      112
      113
      114   IF i_pkgsize <= 0.
      115 *   Reading all data with one single fetch
    >>>>>     FETCH NEXT CURSOR i_cursor
      117       INTO CORRESPONDING FIELDS OF TABLE <l_t_data>.
      118     e_eof = rs_c_true.
      119   ELSE.
      120 *   Reading only one package
      121     FETCH NEXT CURSOR i_cursor
      122       INTO CORRESPONDING FIELDS OF TABLE <l_t_data>
      123       PACKAGE SIZE i_pkgsize.
      124
      125 *   If less than 'i_pkgsize' many tuples are read
      126 *   => end-of-data is reached
      127     DESCRIBE TABLE <l_t_data> LINES l_count.
      128     IF l_count <> i_pkgsize.
      129       e_eof = rs_c_true.
      130     ENDIF.
      131   ENDIF.

    Hi SCHT.
    Error itself says that
    <i>"database accesses producing an excessively large result set,
    - database accesses without a suitable index (full table scan)
    do not block the processing for too long."</i>
    I believe there should be some change in query which causes aggregates to be excluded from selection.
    Try running query from RSRT with option Execute + Debut ->Aggergates section select "Display aggregates found" and see the out put ..and watch whether aggregates are actually used.
    Also some time this error happens because of network traffic , try running query in Bex Analyzer and see the run time.
    Hope that helps.
    Regards
    Mr Kapadia
    Assigning points is the way to say thanks in SDN.

  • Short dump while executing info package in 3.5 data flow?

    Hi,
    i am getting short dump while executing info package while executing info package. it was working perfectly 2 days back suddenly it is giving this problem. it is a full load for info object text data and i have only 600 records. when i tried with " only info package" it is working perfectly n bringing the data into PSA. But when i use "PSA and the into data target" it is giving short dump.
    i replicated Data source and also i activated transfer rules, update rules still it is not working. When i check with another info objects it is working perfectly fine. i dont know what is wrong with only particular info object.
    Please find attached short dump.
    Thanks

    Hi,
    When you load transaction data I think there is a deadlock.
    Check in the process overview (transaction SM50) the waiting processes are in program SAPLSENA .
    The program SAPLSENA is the lock handler tool.
    Also check if  ACR is running on this target while your load is happening.
    Check in SM12 if there are any lock entries for the Infoobject to which you are loading data and on RSICCONT table .
    Try reloading after deleting the locks manually.
    Regards.

  • System Throws short dump while executing data source 2LIS_11_VASCL in RSA3.

    Hello Experts,
    I got short dump while executing data source 2LIS_11_VASCL in RSA3.
    The details are as follow.
    When importing object "MC11VA0SCL_TAB", the structure did not match the
    structure of the target object. The error occurred in component
    no. 567.
    This may be due to one of the following reasons:
    - the structure is actually different (the next field has, for
      example, a different data type) or
    - the same sequence of components were exported and imported,
      but the fields were from other include units.
    I have checked source and target fields and those are of same length and data type.
    Could you please give some points why this short dump occurs.
    Thanks
    Konda Reddy

    Hi,
    This error is not between BI and R/3.  It is within R/3.  You may have setup data and then modified the datasource.
    Delete setup data, generate your datasource again.  Setup data and try again.
    If you are on a live system with data setup after a downtime and you do not want to delete it, then bring your datasource to the original state when you setup data and pull data.
    Cheers....

  • Short dump while executing few queries , which has got created on Infoset.

    Hi,
    We went to BI7.0 upgrade from BW3.x now.
    We are getting short dump short dump while executing few queries and work book, which has got created on Infoset.
    When i was executing work book where i was geting popup message saying that "Erro ZSD_XST_F00121 is invalid".When i click that message it went to dump.
    I was getting this error while executing query on infoset.
    We are currently SP Stack 13(Patch level 15).
    I found some note 1067918 as per the shortdum,where it is saying that you need to apply SP Stack14(patch level16).
    Please some one who had earlier this kind of issue.
    I appreciate your answer.

    Dear Krish,
    Yes, It is the patch problem.
    We too faced the same issue on Infosets.
    Apply SP 15.
    Regards,
    Ram.

  • Facing short dumps when trying to open session in CSA

    Hi
    All am facing Short dump when i am trying to open session in CSA
    Error detials:
    go to System Administration workcenter  task management up CSA. Choose the Solution
    got short dump:
    Short text
        Length error occurred in IMPORT statement.
    What happened?
        Error in the ABAP Application Program
        The current ABAP program "SAPLDSVAS_PROC" had to be terminated because it has
        come across a statement that unfortunately cannot be executed.
    Error analysis
        An exception occurred that is explained in detail below.
        The exception, which is assigned to class 'CX_SY_IMPORT_MISMATCH_ERROR', was
         not caught in
        procedure "LOAD" "(METHOD)", nor was it propagated by a RAISING clause.
        Since the caller of the procedure could not have anticipated that the
        exception would occur, the current program is terminated.
        The reason for the exception is:
        During import the system discovered that the target object has
        a different length than the object to be imported.
    Missing RAISING Clause in Interface
        Program                                 SAPLDSVAS_PROC
        Include                                 LDSVAS_PROCTAI
        Row                                     1.431
        Module type                             (METHOD)
        Module Name                             LOAD
    Trigger Location of Exception
        Program                                 SAPLDSVAS_PROC
        Include                                 LDSVAS_PROCTAI
        Row                                     1.514
        Module type                             (METHOD)
        Module Name                             LOAD
    Please help me to solve this problem
    Regards,
    Neni

    Hello Neni
    According to the information I saw in that post it could be caused by a sort of inconsistency of the program code vs a structure.
    Wether that is a bug that is in your SAP Solution Manager release or something that is caused by administrative actions (perhaps solving SPAU entries after SP stack update or upgrade) I cannot tell.
    I would recommend you either try and find a relative SAP note (narrowing down result to only your SAP Solution Manager system) and searching using the dump keywords. If you cannot find anything I would recommend you to open a customer message so SAP can take a look at the specific error.
    If you give more information, perhaps someone on the forum can help you out abit better, which SAP Solution Manager version and so on.
    You also didn't answer my question, any recent changes you are aware of ?
    Kind regards
    Tom

  • ASSERTION_FAILED short dump when Transporting Transformation from Dev to QA

    Hi Experts,
    I' am getting a short Dump when transporting the transformations, DSO & DTPs from Dev server to QA.
    I got RC=12, Please have a look below....
    Transport log...
        BCQ        System BCQ
                   Selection for Import                     08.07.2010 15:28:59    (0) Successfully Completed
                   Import                                   08.07.2010 15:35:14    (0) Successfully Completed
                   Check Versions                           08.07.2010 15:35:14    (0) Successfully Completed
                   Method Execution                         08.07.2010 15:36:20   (12) Canceled
                   Import                                   08.07.2010 15:45:39    (0) Successfully Completed
                   Check Versions                           08.07.2010 15:45:39    (0) Successfully Completed
                   Method Execution                         08.07.2010 15:46:45   (12) Canceled
    and the Log detalis.....
    Date        Time      Message
    08.07.2010  15:35:15  Job started
    08.07.2010  15:35:15  Step 001 started (program RDDEXECL, variant , user ID DDIC)
    08.07.2010  15:35:15  All DB buffers of application server sxcat136 were synchronized
    08.07.2010  15:35:21  STDO: Log  could not be written on output device T
    08.07.2010  15:35:30  Replication completed successfully
    08.07.2010  15:35:31  Struttura di comunicazione /BIC/CS8ZFIZIASA activated
    08.07.2010  15:35:40  Regola(e) di trasm. 8ZFIZIASA_AA activated
    08.07.2010  15:35:47  ABAP/4 processor: ASSERTION_FAILED
    08.07.2010  15:35:47  Job cancelled
    Even I've checked the entries on the table RSTRANRULE for those Transpormations but there I got...all the entries with...
    RULEID = all numbers
    GROUPID = '1' or '2'
    GROUPTYPE = 'S' or 'T'
    REF_RULE ='0'
    we are in to SAP_BW Release 700, Level 0013, SP -SAPKW70013, SAP NetWeaver BI 7.0
    Pls help if any one know's the solution for this.
    Thanks in adv.
    BR,
    Ajay Kumar
    Edited by: sap.ajaykumar on Jul 9, 2010 12:48 PM

    Follow the steps mentioned in OSS note 998730.
    FYI.. Solution:
    Call transaction SE16 (Table Browser) and the 'RSTRANRULE' table with the following selection parameters:
    GROUPID = 'space'
    GROUPTYPE = 'space'
    REF_RULE 'space'
    If there are inconsistent entries in the RSTRANRULE table such as this:
    TRANID *
    OBJVERS *
    RULEID *
    SEQNR *
    GROUPID 00
    GROUPTYPE space
    RULETYPE space
    REF RULE *
    Delete these entries from the table.
    Activate the affected transformations.
    Also check the OSS note: 1006658.
    Follow the steps mentioned in OSS note 998730.
    FYI.. Solution:
    Call transaction SE16 (Table Browser) and the 'RSTRANRULE' table with the following selection parameters:
    GROUPID = 'space'
    GROUPTYPE = 'space'
    REF_RULE 'space'
    If there are inconsistent entries in the RSTRANRULE table such as this:
    TRANID *
    OBJVERS *
    RULEID *
    SEQNR *
    GROUPID 00
    GROUPTYPE space
    RULETYPE space
    REF RULE *
    Delete these entries from the table.
    Activate the affected transformations.
    Also check the OSS note: 1006658.
    Follow the steps mentioned in OSS note 998730.
    FYI.. Solution:
    Call transaction SE16 (Table Browser) and the 'RSTRANRULE' table with the following selection parameters:
    GROUPID = 'space'
    GROUPTYPE = 'space'
    REF_RULE 'space'
    If there are inconsistent entries in the RSTRANRULE table such as this:
    TRANID *
    OBJVERS *
    RULEID *
    SEQNR *
    GROUPID 00
    GROUPTYPE space
    RULETYPE space
    REF RULE *
    Delete these entries from the table.
    Activate the affected transformations.
    Also check the OSS note: 1006658.
    Also check the oSS note : Note 975675 - Transformation cannot be activated

  • Short Dump when the Bex-Report scheduled for Broadcast

    Hi Guru's
    I am getting the short dump when I am scheduling the Bex-Report for Broadcasting. Need your help to reslove this issue.
    Thanks
    Navin
    Note
    The following error text was processed in the system BDV : The current application triggered a termination with a short dump.
    The error occurred on the application server spdbwd01_BDV_05 and in the work process 0 .
    The termination type was: RABAX_STATE
    The ABAP call stack was:
    Form: INTERNAL_ERROR of program SAPLSDCL
    Form: PHIO_GET_CONTENT_ACCESS of program SAPLSDCI
    Function: SDOK_PHIO_GET_CONTENT_ACCESS of program SAPLSDCI
    Function: SKWF_PHIO_CONTENT_ACCESS_GET of program SAPLSKWF_CONTENT
    Method: COPY_MIME_TO_FOLDER of program CL_RSRA_KWF_UTILITIES=========CP
    Method: GET_STYLESHEET of program CL_RSRA_KWF_TMPL==============CP
    Method: CONSTRUCTOR of program CL_RSRA_KWF_TMPL==============CP
    Method: SET_TEMPLATE_FOLDER of program CL_RSRA_ENGINE_BC=============CP
    Method: CONSTRUCTOR of program CL_RSRA_ENGINE_BC=============CP
    Method: EXECUTE_SINGLE of program CL_RSRA_JOB===================CP

    HI Navin,
    Check the short dump analysis in T-code ST22.
    and also check the Information Broadcast Settings / Configuration
    Check the error for Emails in t-code SCOT. BASIS Consultants will help you on this issue.
    Regards
    Daya Sagar

  • Short Dump while executing New Hire (action type) in PA40

    Hi All,
    i am getting short dump while executing PA40 for new hire action type can anyone look into this and guide as i am new to HCM.
    Category               ABAP Programming Error                                                      
    Runtime Errors         SYNTAX_ERROR                                                                
    ABAP Program           /1PAPAXX/HDR_21000A                                                         
    Application Component  Not Assigned                                                                
    Date and Time          21.08.2014 14:07:03                                                         
    Short text                                                                                       
        Syntax error in program "/1PAPAXX/HDR_21000A ".                                              
    What happened?                                                                                   
        Error in the ABAP Application Program                                                        
        The current ABAP program "SAPFP50M" had to be terminated because it has                      
        come across a statement that unfortunately cannot be executed.                               
        The following syntax error occurred in program "/1PAPAXX/HDR_21000A " in                     
        include "/1PAPAXX/HDR_21000AO01 " in                                                        
        line 52:                                                                                     
        ""LV_LENGTH" has already been declared"                                                      
        The include has been created and last changed by:                                            
        Created by: "HCM04 "                                                                         
        Last changed by: "HCM03 "                                                                    
        Error in the ABAP Application Program                                                        
        The current ABAP program "SAPFP50M" had to be terminated because it has                      
        come across a statement that unfortunately cannot be executed.                               
    What can you do?                                                                                 
        Please eliminate the error by performing a syntax check                                      
        (or an extended program check) on the program "/1PAPAXX/HDR_21000A ".                        
        You can also perform the syntax check from the ABAP Editor.                                  
        If the problem persists, proceed as follows:                                                 
        Note down which actions and inputs caused the error.                                         
        To process the problem further, contact you SAP system                                       
        administrator.                                                                               
        Using Transaction ST22 for ABAP Dump Analysis, you can look                                  
        at and manage termination messages, and you can also                                         
        keep them for a long time.                                                                   
    Error analysis                                                                                   
        The following syntax error was found in the program /1PAPAXX/HDR_21000A :                    
        ""LV_LENGTH" has already been declared"                                                      
    How to correct the error                                                                         
        Probably the only way to eliminate the error is to correct the program.                      
        If you cannot solve the problem yourself and want to send an error                           
        notification to SAP, include the following information:                                      
        1. The description of the current problem (short dump)                                       
           To save the description, choose "System->List->Save->Local File                           
        (Unconverted)".                                                                              
        2. Corresponding system log                                                                  
           Display the system log by calling transaction SM21.                                       
           Restrict the time interval to 10 minutes before and five minutes                          
        after the short dump. Then choose "System->List->Save->Local File                            
        (Unconverted)".                                                                              
        3. If the problem occurs in a problem of your own or a modified SAP                          
        program: The source code of the program                                                      
           In the editor, choose "Utilities->More                                                    
        Utilities->Upload/Download->Download".                                                       
        4. Details about the conditions under which the error occurred or which                      
        actions and input led to the error.                                                          
    System environment                                                                               
        SAP Release..... 731                                                                         
        SAP Basis Level. 0007                                                                        
        Application server... "dc-ds-erp"                                                            
        Network address...... "172.16.23.111"                                                        
        Operating system..... "Linux"                                                                
        Release.............. "3.0.13-0.27-default"                                                  
        Hardware type........ "x86_64"                                                               
        Character length.... 16 Bits                                                                 
        Pointer length....... 64 Bits                                                                
        Work process number.. 1                                                                      
        Shortdump setting.... "full"                                                                 
        Database server... "dc-ds-erp"                                                               
        Database type..... "ORACLE"                                                                  
        Database name..... "ECD"                                                                     
        Database user ID.. "SAPSR3"                                                                  
        Terminal.......... "NLC-HP"                                                                  
        Char.set.... "C"                                                                             
        SAP kernel....... 720                                                                        
        created (date)... "Sep 14 2013 06:16:24"                                                     
        create on........ "Linux GNU SLES-11 x86_64 cc4.3.4 use-pr130820"                            
        Database version. "OCI_112, 11.2.0.3.0, V1, default"                                         
        Patch level. 500                                                                             
        Patch text.. " "                                                                             
        Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"              
        SAP database version. 720                                                                    
        Operating system..... "Linux 2.6, Linux 3"                                                   
        Memory consumption                                                                           
        Roll.... 0                                                                                   
        EM...... 37708200                                                                            
        Heap.... 0                                                                                   
        Page.... 106496                                                                              
        MM Used. 4666776                                                                             
        MM Free. 3709976                                                                             
    User and Transaction                                                                             
        Client.............. 210                                                                     
        User................ "HCM03"                                                                 
        Language key........ "E"                                                                     
        Transaction......... "PA40 "                                                                 
        Transaction ID...... "53EF470299AB5D67E1000000AC10176F"                                      
        EPP Whole Context ID.... "005056A301D11EE48A9D08B337F884E3"                                  
        EPP Connection ID....... 00000000000000000000000000000000                                    
        EPP Caller Counter...... 0                                                                   
        Program............. "SAPFP50M"                                                              
        Screen.............. "MP000000 1000"                                                         
        Screen Line......... 3                                                                       
        Debugger Active..... "none"                                                                  
    Information on where terminated                                                                  
        Termination occurred in the ABAP program "SAPFP50M" - in                                     
        "GET_HEADER_WITH_TCLAS".                                                                    
        The main program was "MP000000 ".                                                            
        In the source code you have the termination point in line 146                                
        of the (Include) program "FP50MDHD".                                                         
    Source Code Extract                                                                              
    Line
    SourceCde                                                                                  
      116
      CALL FUNCTION 'HR_HEADER_GET'                                                            
      117
          EXPORTING                                                                            
      118
               DHDID                    = FHD_HID                                              
      119
               BEGDA                    = BEGDA                                                
      120
               TCLAS                    = TCLAS                                                
      121
    * Es wird nur einer der folgenden 3 Parameter benutzt.                                     
      122
    * Ausgewertet wird zunaechst MOLGA, dann P0001 dann PERNR.                                 
      123
    * Der erste der nicht initial ist wird ausgewertet.                                        
      124
    *           MOLGA                   =                                                      
      125
               P0001                    = P0001                                                
      126
               PERNR                    = PSPAR-PERNR                                          
      127
          IMPORTING                                                                            
      128
               PROG                     = HEADER_PROG                                          
      129
               DNUM                     = HEADER_DYNNR                                         
      130
           EXCEPTIONS                                                                          
      131
                HEADER_DEACTIVATED          = 1                                                
      132
                HEADER_UNKNOWN              = 2                                                
      133
                HEADER_GENERATE_DEACTIVATED = 3                                                
      134
                HEADER_GENERATE_FAILED      = 4                                                
      135
                INTERNAL_ERROR              = 5                                                
      136
                OTHERS                      = 6.                                               
      137
      138
      IF NOT SY-SUBRC IS INITIAL.                                                              
      139
    * Bei Problemen gibt's eben ein leeres Dynpro.                                             
      140
        HEADER_PROG = 'SAPMP50A'.                                                              
      141
        HEADER_DYNNR = '0090'.                                                                 
      142
      ELSE.  " NOT sy-subrc IS INITIAL.                                   "                    
      143
    * Dann setzen wir jetzt auch noch das Datum fest.                                          
      144
        PERFORM HEADER_BEGDA_SET IN PROGRAM (HEADER_PROG) USING BEGDA.                         
      145
    * Und schalten auf Uebergabe der PERNR mit globalen Variablen.                             
    >>>>>
        PERFORM HEADER_LAZY_ON IN PROGRAM (HEADER_PROG).                                       
      147
      ENDIF.  " (ELSE) NOT sy-subrc IS INITIAL.                           "                    
      148
    * Merken wie der Header heisst. Damit MPPERS00 sich erinnern kann.                         

    Hi,
    Error Log: Syntax error
    ""LV_LENGTH" has already been declared"
    please check LV_LENGTH variable declaration.
    It may be declared more once!

  • Short Dump when trying to open C-project due to status

    Hi,
    We have a daily batch job in CRM that reports all the project ID's and
    sends e-mails out to recipients.
    As part of this report it retrieves the statuses for the project ID's,
    however the report short dumps when retrieving the status for one of
    the projects because it is not finding an active status.
    When we try and open the project in C-projects we get the same short
    dump error: CX_DPR_FATAL_ERROR so we cannot view or update the status.
    When we investigate this issue we find that in table CRM_JCDS there are
    3 entries for this project ID. One of the statuses is inactive (I1703)
    but there is another status that is active (I1701). The two status
    entries were created at exactly the same date and time and by the same
    user.
    In table CRM_JEST there is only one entry shown which shows an inactive
    status and we believe this to be the wrong status. Please can you
    advise if this status conflict is causing the problem and also how to
    resolve this issue?

    Hi Paul,
    generally, the project and its elements must have an active status in table CRM_JEST, however, at this point it is not clear how this inconsistency arised. There is no SAP standard report or a 'generally valid' solution that could solve this issue, however, I found a customer message that you have opened in September with exactly the same problem. A colleague from the development team already provided you with a correction report, but there was no feedback from your side if it helped or not.
    It is very difficult to provide help as inconsistencies can have several different causes, so the best would be to have this checked in a customer message with an example.
    Regards,
    Silvia

Maybe you are looking for