Short Dump : ABAP/4 Processor:Syntax_Error

Hello All,
I scheduled one chain and while activating the ODS it gave the Short Dump
ABAP/4 Processor:Syntax_Error.
Then i tried to change the delete the request freom ODS after changing its status to RED.
But while deleting also it is giving the same dump.
I am unable to delete the request also.
In sm37 following messeges were there in logs.
Job started
Step 001 started (program RSODSACT1, variant &0000000005515, us
Activation is running: Data target MPU09O74, from 19.886 to 19.
Data to be activated successfully checked against archiving obj
SQL: 20.11.2007 09:02:49 PJAIN
ANALYZE TABLE "/BIC/AMPU09O7440" DELETE
STATISTICS
SQL-END: 20.11.2007 09:02:49 00:00:00
SQL: 20.11.2007 09:02:49 PJAIN
BEGIN DBMS_STATS.GATHER_TABLE_STATS ( OWNNAME =>
'SAPEBF', TABNAME => '"/BIC/AMPU09O7440"',
ESTIMATE_PERCENT => 1 , METHOD_OPT => 'FOR ALL
INDEXED COLUMNS SIZE 75', DEGREE => 1 ,
GRANULARITY => 'ALL', CASCADE => TRUE ); END;
SQL-END: 20.11.2007 09:02:51 00:00:02
SQL: 20.11.2007 09:02:51 PJAIN
ANALYZE TABLE "/BIC/AMPU09O7400" DELETE
STATISTICS
SQL-END: 20.11.2007 09:02:51 00:00:00
SQL: 20.11.2007 09:02:51 PJAIN
BEGIN DBMS_STATS.GATHER_TABLE_STATS ( OWNNAME =>
'SAPEBF', TABNAME => '"/BIC/AMPU09O7400"',
ESTIMATE_PERCENT => 1 , METHOD_OPT => 'FOR ALL
INDEXED COLUMNS SIZE 75', DEGREE => 1 ,
GRANULARITY => 'ALL', CASCADE => TRUE ); END;
SQL-END: 20.11.2007 09:02:51 00:00:00
ABAP/4 processor: SYNTAX_ERROR
Job cancelled

See the dump in ST22 for details.

Similar Messages

  • Data Load Short Dump (ABAP/4 processor: ASSIGN_TYPE_CONFLICT)

    Hi Experts,
      I made few changes to the exisisting data target and transported it to Test system...
    Today when i loaded test data i got Dump: ABAP/4 processor: ASSIGN_TYPE_CONFLICT error
    Now i need to reactivate the Transformations and DTP's that will fix the error
    What is the reason for this error
    Thanks

    Yes, you are correct, you need to activate your transformation and then DTP to get rid of this error.
    The reason for this error is inconsistency b/w transformation and DTP.If you have made any changes to trasforamtion and activated it, then you need to activate the DTP also. If you are loading the data without DTP activation, you will get this error. This is because the DTP is build on transformation.
    Thanks...
    Shambhu

  • ABAP/4 processor: SYNTAX_ERROR  program RDDEXECL  at XPRA_EXECUTION

    Hi All,
    Following is the error message I am getting in spam-> goto->import log-> queue. I am applying support package SAPKB70013 and is stucked at XPRA_EXECUTION on my ecc6
    Execution of programs after import ()
    Transport request : SAPKB70013
    System : C27
    tp path : tp
    Version and release: 372.03.35 700
    Job started
    Step 001 started (program RDDEXECL, variant , user ID DDIC)
    All DB buffers of application server wicomp06 were synchronized
    ABAP/4 processor: SYNTAX_ERROR
    Job cancelled
    I found a reply in sdn to regenerate the existing objects using sgen and is running it now.
    Can any one tell why RDDEXECL program cannot be run by abap/4
    processor as well as the step to fix this issue.

    Hi All
    I have removed the old buffer again and restarted the spam again.It got stuck in the old place it self.
    As I said earlier RDDEXECL job  is getting canceled. In sm37 I checked the wp it used and here is the log of dev_w13 which it used
    trc file: "dev_w13", trc level: 1, release: "700"
    ACTIVE TRACE LEVEL           1
    ACTIVE TRACE COMPONENTS      all, MJ

    B Mon Jun 11 17:49:46 2007
    B  create_con (con_name=R/3)
    B  Loading DB library 'F:\usr\sap\C27\DVEBMGS00\exe\dboraslib.dll' ...
    B  Library 'F:\usr\sap\C27\DVEBMGS00\exe\dboraslib.dll' loaded
    B  Version of 'F:\usr\sap\C27\DVEBMGS00\exe\dboraslib.dll' is "700.08", patchlevel (0.144)
    B  New connection 0 created
    M sysno      00
    M sid        C27
    M systemid   561 (PC with Windows NT)
    M relno      7000
    M patchlevel 0
    M patchno    146
    M intno      20050900
    M make:      multithreaded, Unicode, 64 bit, optimized
    M pid        2932
    M
    M  kernel runs with dp version 232000(ext=109000) (@(#) DPLIB-INT-VERSION-232000-UC)
    M  length of sys_adm_ext is 576 bytes
    M  ***LOG Q0Q=> tskh_init, WPStart (Workproc13 2932) [dpxxdisp.c   1305]

    I Mon Jun 11 17:49:47 2007
    I  MtxInit: 30000 0 0
    M  DpSysAdmExtCreate: ABAP is active
    M  DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active
    M  DpShMCreate: sizeof(wp_adm)          25168     (1480)
    M  DpShMCreate: sizeof(tm_adm)          5652128     (28120)
    M  DpShMCreate: sizeof(wp_ca_adm)          24000     (80)
    M  DpShMCreate: sizeof(appc_ca_adm)     8000     (80)
    M  DpCommTableSize: max/headSize/ftSize/tableSize=500/16/552064/552080
    M  DpShMCreate: sizeof(comm_adm)          552080     (1088)
    M  DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
    M  DpShMCreate: sizeof(slock_adm)          0     (104)
    M  DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
    M  DpShMCreate: sizeof(file_adm)          0     (72)
    M  DpShMCreate: sizeof(vmc_adm)          0     (1864)
    M  DpShMCreate: sizeof(wall_adm)          (41664/36752/64/192)
    M  DpShMCreate: sizeof(gw_adm)     48
    M  DpShMCreate: SHM_DP_ADM_KEY          (addr: 000000001C430050, size: 6348592)
    M  DpShMCreate: allocated sys_adm at 000000001C430050
    M  DpShMCreate: allocated wp_adm at 000000001C432150
    M  DpShMCreate: allocated tm_adm_list at 000000001C4383A0
    M  DpShMCreate: allocated tm_adm at 000000001C438400
    M  DpShMCreate: allocated wp_ca_adm at 000000001C99C2A0
    M  DpShMCreate: allocated appc_ca_adm at 000000001C9A2060
    M  DpShMCreate: allocated comm_adm at 000000001C9A3FA0
    M  DpShMCreate: system runs without slock table
    M  DpShMCreate: system runs without file table
    M  DpShMCreate: allocated vmc_adm_list at 000000001CA2AC30
    M  DpShMCreate: allocated gw_adm at 000000001CA2ACB0
    M  DpShMCreate: system runs without vmc_adm
    M  DpShMCreate: allocated ca_info at 000000001CA2ACE0
    M  DpShMCreate: allocated wall_adm at 000000001CA2ACF0

    M Mon Jun 11 17:49:48 2007
    M  ThTaskStatus: rdisp/reset_online_during_debug 0
    X  EmInit: MmSetImplementation( 2 ).
    X  MM global diagnostic options set: 0
    X  <ES> client 13 initializing ....

    X Mon Jun 11 17:49:49 2007
    X  Using implementation view
    X  <EsNT> Using memory model view.
    M  <EsNT> Memory Reset disabled as NT default
    X  ES initialized.
    M  ThInit: running on host wicomp06

    M Mon Jun 11 17:49:50 2007
    M  calling db_connect ...
    C  Prepending F:\usr\sap\C27\DVEBMGS00\exe to Path.
    C  Oracle Client Version: '10.2.0.1.0'
    C  Client NLS settings: AMERICAN_AMERICA.UTF8
    C  Logon as OPS$-user to get SAPSR3's password
    C  Connecting as /@C27 on connection 0 (nls_hdl 0) ... (dbsl 700 250407)
    C  Nls CharacterSet                 NationalCharSet              C      EnvHp      ErrHp ErrHpBatch
    C    0 UTF8                                                      1 000000001F1E66C0 000000001F1EE8F0 000000001F20C118
    C  Attaching to DB Server C27 (con_hdl=0,svchp=000000001F20BFD8,srvhp=000000001F20E408)
    C  Starting user session (con_hdl=0,svchp=000000001F20BFD8,srvhp=000000001F20E408,usrhp=000000001F1EF108)
    C  Now '/@C27' is connected (con_hdl 0, nls_hdl 0).
    C  Got SAPSR3's password from OPS$-user
    C  Disconnecting from connection 0 ...
    C  Closing user session (con_hdl=0,svchp=000000001F20BFD8,usrhp=000000001F1EF108)
    C  Now I'm disconnected from ORACLE
    C  Connecting as SAPSR3/<pwd>@C27 on connection 0 (nls_hdl 0) ... (dbsl 700 250407)
    C  Nls CharacterSet                 NationalCharSet              C      EnvHp      ErrHp ErrHpBatch
    C    0 UTF8                                                      1 000000001F1E66C0 000000001F1EE8F0 000000001F20C118
    C  Starting user session (con_hdl=0,svchp=000000001F20BFD8,srvhp=000000001F20E408,usrhp=000000001F1EF108)
    C  Now 'SAPSR3/<pwd>@C27' is connected (con_hdl 0, nls_hdl 0).
    C  Database NLS settings: AMERICAN_AMERICA.UTF8
    C  DB instance C27 is running on WICOMP06 with ORACLE version 10.2.0.2.0 since JUN 11, 2007, 15:42:12

    B Mon Jun 11 17:49:51 2007
    B  Connection 0 opened (DBSL handle 0)
    B  Wp  Hdl ConName          ConId     ConState     TX  PRM RCT TIM MAX OPT Date     Time   DBHost         
    B  000 000 R/3              000000000 ACTIVE       NO  YES NO  000 255 255 20070611 174950 WICOMP06       
    M  db_connect o.k.
    M  ICT: exclude compression: .zip,.cs,.rar,.arj,.z,.gz,.tar,.lzh,.cab,.hqx,.ace,.jar,.ear,.war,.css,.pdf,.js,.gzip,.uue,.bz2,.iso,.sda,.sar,.gif

    I Mon Jun 11 17:50:05 2007
    I  MtxInit: 13 0 0
    M  SHM_PRES_BUF               (addr: 0000000022240050, size: 4400000)
    M  SHM_ROLL_AREA          (addr: 000006FBEA010050, size: 61440000)
    M  SHM_PAGING_AREA          (addr: 0000000022680050, size: 32768000)
    M  SHM_ROLL_ADM               (addr: 00000000245D0050, size: 615040)
    M  SHM_PAGING_ADM          (addr: 0000000024670050, size: 525344)
    M  ThCreateNoBuffer          allocated 544152 bytes for 1000 entries at 0000000024700050
    M  ThCreateNoBuffer          index size: 3000 elems
    M  ThCreateVBAdm          allocated 12176 bytes (50 server) at 0000000024790050
    X  EmInit: MmSetImplementation( 2 ).
    X  MM global diagnostic options set: 0
    X  <ES> client 13 initializing ....
    X  Using implementation view
    X  ES initialized.
    B  db_con_shm_ini:  WP_ID = 13, WP_CNT = 17, CON_ID = -1
    B  dbtbxbuf: Buffer TABL  (addr: 0000000029D00160, size: 30000000, end: 000000002B99C4E0)
    B  dbtbxbuf: Buffer TABLP (addr: 000000002B9A0160, size: 10240000, end: 000000002C364160)
    B  dbexpbuf: Buffer EIBUF (addr: 000000002C380170, size: 4194304, end: 000000002C780170)
    B  dbexpbuf: Buffer ESM   (addr: 000000002C790170, size: 4194304, end: 000000002CB90170)
    B  dbexpbuf: Buffer CUA   (addr: 000000002CBA0170, size: 3072000, end: 000000002CE8E170)
    B  dbexpbuf: Buffer OTR   (addr: 000000002CE90170, size: 4194304, end: 000000002D290170)
    M  CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.

    S Mon Jun 11 17:50:06 2007
    S  *** init spool environment
    S  initialize debug system
    T  Stack direction is downwards.
    T  debug control: prepare exclude for printer trace
    T  new memory block 000000001F3C5610
    S  spool kernel/ddic check: Ok
    S  using table TSP02FX for frontend printing
    S  1 spool work process(es) found
    S  frontend print via spool service enabled
    S  printer list size is 150
    S  printer type list size is 50
    S  queue size (profile)   = 300
    S  hostspool list size = 3000
    S  option list size is 30
    S      found processing queue enabled
    S  found spool memory service RSPO-RCLOCKS at 00000000365B00D0
    S  doing lock recovery
    S  setting server cache root
    S  found spool memory service RSPO-SERVERCACHE at 00000000365B0610
    S    using messages for server info
    S  size of spec char cache entry: 297032 bytes (timeout 100 sec)
    S  size of open spool request entry: 2272 bytes
    S  immediate print option for implicitely closed spool requests is disabled

    A  -PXA--
    A  PXA INITIALIZATION

    A Mon Jun 11 17:50:17 2007
    A  PXA: Locked PXA-Semaphore.
    A  System page size: 8kb, total admin_size: 11464kb, dir_size: 11392kb.
    A  Attached to PXA (address 000006FBEDAB0050, size 300000K)
    A  abap/pxa = shared protect gen_remote
    A  PXA INITIALIZATION FINISHED
    A  -PXA--


    A Mon Jun 11 17:50:18 2007
    A  ABAP ShmAdm attached (addr=000006FAEA83C000 leng=20938752 end=000006FAEBC34000)
    A  >> Shm MMADM area (addr=000006FAEAAD0B10 leng=141312 end=000006FAEAAF3310)
    A  >> Shm MMDAT area (addr=000006FAEAAF4000 leng=18087936 end=000006FAEBC34000)
    A  RFC rfc/signon_error_log = -1
    A  RFC rfc/dump_connection_info = 0
    A  RFC rfc/dump_client_info = 0
    A  RFC rfc/cp_convert/ignore_error = 1
    A  RFC rfc/cp_convert/conversion_char = 23
    A  RFC rfc/wan_compress/threshold = 251
    A  RFC rfc/recorder_pcs not set, use defaule value: 2
    A  RFC rfc/delta_trc_level not set, use default value: 0
    A  RFC rfc/no_uuid_check not set, use default value: 0
    A  RFC rfc/bc_ignore_thcmaccp_retcode not set, use default value: 0
    A  RFC Method> initialize RemObjDriver for ABAP Objects
    M  ThrCreateShObjects          allocated 35354 bytes at 0000000036F20050

    N Mon Jun 11 17:50:19 2007
    N  SsfSapSecin: putenv(SECUDIR=F:\usr\sap\C27\DVEBMGS00\sec): ok

    N  =================================================
    N  === SSF INITIALIZATION:
    N  ===...SSF Security Toolkit name SAPSECULIB .
    N  ===...SSF trace level is 0 .
    N  ===...SSF library is F:\usr\sap\C27\DVEBMGS00\exe\sapsecu.dll .
    N  ===...SSF hash algorithm is SHA1 .
    N  ===...SSF symmetric encryption algorithm is DES-CBC .

    N Mon Jun 11 17:50:20 2007
    N  ===...completed with return code 5.
    N  =================================================

    N Mon Jun 11 17:50:21 2007
    N  MskiInitLogonTicketCacheHandle: Logon Ticket cache pointer retrieved from shared memory.
    N  MskiInitLogonTicketCacheHandle: Workprocess runs with Logon Ticket cache.
    M  JrfcVmcRegisterNativesDriver o.k.
    W  =================================================
    W  === ipl_Init() called
    W    ipl_Init(): wp task type is 4:BTC, skip initialization
    W  === ipl_Init() returns 0, ITSPE_OK: OK
    W  =================================================
    E  Enqueue Info: rdisp/wp_no_enq=1, rdisp/enqname=<empty>, assume wicomp06_C27_00

    E Mon Jun 11 17:50:23 2007
    E  Replication is disabled
    E  EnqCcInitialize: local lock table initialization o.k.
    E  EnqId_SuppressIpc: local EnqId initialization o.k.
    E  EnqCcInitialize: local enqueue client init o.k.

    B Mon Jun 11 17:50:36 2007
    B  dbtran INFO (init_connection '<DEFAULT>' [ORACLE:700.08]):
    B   max_blocking_factor =   5,  max_in_blocking_factor      =   5,
    B   min_blocking_factor =   5,  min_in_blocking_factor      =   5,
    B   prefer_union_all    =   0,  prefer_join                 =   0,
    B   prefer_fix_blocking =   0,  prefer_in_itab_opt          =   1,
    B   convert AVG         =   0,  alias table FUPD            =   0,
    B   escape_as_literal   =   1,  opt GE LE to BETWEEN        =   0,
    B   select *            =0x0f,  character encoding          = STD / <none>:-,
    B   use_hints           = abap->1, dbif->0x1, upto->2147483647, rule_in->0,
    B                         rule_fae->0, concat_fae->0, concat_fae_or->0

    M Mon Jun 11 17:50:37 2007
    M  SecAudit(RsauShmInit): WP attached to existing shared memory.
    M  SecAudit(RsauShmInit): addr of SCSA........... = 0000000010410050
    M  SecAudit(RsauShmInit): addr of RSAUSHM........ = 00000000104107C0
    M  SecAudit(RsauShmInit): addr of RSAUSLOTINFO... = 0000000010410800
    M  SecAudit(RsauShmInit): addr of RSAUSLOTS...... = 000000001041080C

    M Mon Jun 11 17:51:02 2007

    M  *****************************************************************************
    M  *
    M  *  LOCATION    SAP-Gateway on host wicomp06 / sapgw00
    M  *  ERROR       program SLD_UC not registered
    M  *
    M  *  TIME        Mon Jun 11 17:51:02 2007
    M  *  RELEASE     700
    M  *  COMPONENT   SAP-Gateway
    M  *  VERSION     2
    M  *  RC          679
    M  *  MODULE      gwr3cpic.c
    M  *  LINE        1778
    M  *  DETAIL      TP SLD_UC not registered
    M  *  COUNTER     9
    M  *
    M  *****************************************************************************

    A  RFC 1485  CONVID 12820230
    A   * CMRC=2 DATA=0 STATUS=0 SAPRC=679 ThSAPOCMINIT
    A  RFC> ABAP Programm: RSLDAGDS (Transaction: )
    A  RFC> User: ADMIN (Client: 000)
    A  RFC> Destination: SLD_UC (handle: 1, , )
    A  TH VERBOSE LEVEL FULL
    A  ** RABAX: end RX_GET_MESSAGE
    B  table logging switched off for all clients
    S  handle memory type is RSTSPROMMM

    M Tue Jun 12 05:51:15 2007

    M  *****************************************************************************
    M  *
    M  *  LOCATION    SAP-Gateway on host wicomp06 / sapgw00
    M  *  ERROR       program SLD_UC not registered
    M  *
    M  *  TIME        Tue Jun 12 05:51:15 2007
    M  *  RELEASE     700
    M  *  COMPONENT   SAP-Gateway
    M  *  VERSION     2
    M  *  RC          679
    M  *  MODULE      gwr3cpic.c
    M  *  LINE        1778
    M  *  DETAIL      TP SLD_UC not registered
    M  *  COUNTER     711
    M  *
    M  *****************************************************************************

    A  RFC 1485  CONVID 56082020
    A   * CMRC=2 DATA=0 STATUS=0 SAPRC=679 ThSAPOCMINIT
    A  RFC> ABAP Programm: RSLDAGDS (Transaction: )
    A  RFC> User: ADMIN (Client: 000)
    A  RFC> Destination: SLD_UC (handle: 1, , )
    A  TH VERBOSE LEVEL FULL
    A  ** RABAX: end RX_GET_MESSAGE

    A Tue Jun 12 12:12:25 2007
    A  GENER request remote generation: SAPLSLOG.

    A Tue Jun 12 12:12:27 2007
    A  GENER request remote generation: SAPLSTRF.

    A Tue Jun 12 12:12:28 2007
    A  GENER request remote generation: CL_FDT_MAINTENANCE============CP.

    A Tue Jun 12 12:12:31 2007
    A  *** ERROR => Syntax error in program CL_FDT_MAINTENANCE============CP         [abgen.c      1517]
    A  *** ERROR => > Include CL_FDT_MAINTENANCE============CM01D      line 1 [abgen.c      1519]
    A  *** ERROR => > Method "DELETE_OBJECT_PERMANENTLY" does not exist. There is, however a method wi [abgen.c      1521]
    A  *** ERROR => > th the similar name "DELETE_PERMANENTLY". [abgen.c      1523]
    A  TH VERBOSE LEVEL FULL
    A  ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.
    A  ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.
    A  ** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.
    A  ** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.
    A  ** RABAX: level LEV_RX_ROLLBACK entered.
    A  ** RABAX: level LEV_RX_ROLLBACK completed.
    A  ** RABAX: level LEV_RX_DB_ALIVE entered.
    A  ** RABAX: level LEV_RX_DB_ALIVE completed.
    A  ** RABAX: level LEV_RX_HOOKS entered.
    A  ** RABAX: level LEV_RX_HOOKS completed.
    A  ** RABAX: level LEV_RX_STANDARD entered.
    A  ** RABAX: level LEV_RX_STANDARD completed.
    A  ** RABAX: level LEV_RX_STOR_VALUES entered.
    A  ** RABAX: level LEV_RX_STOR_VALUES completed.
    A  ** RABAX: level LEV_RX_C_STACK entered.

    A Tue Jun 12 12:12:34 2007
    A  ** RABAX: level LEV_RX_C_STACK completed.
    A  ** RABAX: level LEV_RX_MEMO_CHECK entered.
    A  ** RABAX: level LEV_RX_MEMO_CHECK completed.
    A  ** RABAX: level LEV_RX_AFTER_MEMO_CHECK entered.
    A  ** RABAX: level LEV_RX_AFTER_MEMO_CHECK completed.
    A  ** RABAX: level LEV_RX_INTERFACES entered.
    A  ** RABAX: level LEV_RX_INTERFACES completed.
    A  ** RABAX: level LEV_RX_GET_MESS entered.
    A  ** RABAX: level LEV_RX_GET_MESS completed.
    A  ** RABAX: level LEV_RX_INIT_SNAP entered.
    A  ** RABAX: level LEV_RX_INIT_SNAP completed.
    A  ** RABAX: level LEV_RX_WRITE_SYSLOG entered.
    A  ** RABAX: level LEV_RX_WRITE_SYSLOG completed.
    A  ** RABAX: level LEV_RX_WRITE_SNAP entered.

    A Tue Jun 12 12:12:35 2007
    A  GENER request remote generation: CL_FDT_MAINTENANCE============CP.
    A  *** ERROR => Syntax error in program CL_FDT_MAINTENANCE============CP         [abgen.c      1517]
    A  *** ERROR => > Include CL_FDT_MAINTENANCE============CM01D      line 1 [abgen.c      1519]
    A  *** ERROR => > Method "DELETE_OBJECT_PERMANENTLY" does not exist. There is, however a method wi [abgen.c      1521]
    A  *** ERROR => > th the similar name "DELETE_PERMANENTLY". [abgen.c      1523]
    A  ** RABAX:  level LEV_SN_EVENTS failed.
    A  ** RABAX: level LEV_RX_WRITE_SNAP entered.
    A  ** RABAX: level LEV_SN_END completed.
    A  ** RABAX: level LEV_RX_SET_ALERT entered.
    A  ** RABAX: level LEV_RX_SET_ALERT completed.
    A  ** RABAX: level LEV_RX_COMMIT entered.
    A  ** RABAX: level LEV_RX_COMMIT completed.
    A  ** RABAX: level LEV_RX_SNAP_SYSLOG entered.
    A  ** RABAX: level LEV_RX_SNAP_SYSLOG completed.
    A  ** RABAX: level LEV_RX_RESET_PROGS entered.
    A  ** RABAX: level LEV_RX_RESET_PROGS completed.
    A  ** RABAX: level LEV_RX_STDERR entered.
    A  Tue Jun 12 12:12:35 2007

    A  ABAP Program CL_FDT_TRANS==================CP        .
    A  Source CL_FDT_TRANS==================CM001      Line 1.
    A  Error Code SYNTAX_ERROR.
    A  Module  $Id: //bas/700_REL/src/krn/runt/abgen.c#10 $ SAP.
    A  Function ab_genprog Line 1551.
    A  ** RABAX: level LEV_RX_STDERR completed.
    A  ** RABAX: level LEV_RX_RFC_ERROR entered.
    A  ** RABAX: level LEV_RX_RFC_ERROR completed.
    A  ** RABAX: level LEV_RX_RFC_CLOSE entered.
    A  ** RABAX: level LEV_RX_RFC_CLOSE completed.
    A  ** RABAX: level LEV_RX_IMC_ERROR entered.
    A  ** RABAX: level LEV_RX_IMC_ERROR completed.
    A  ** RABAX: level LEV_RX_DATASET_CLOSE entered.
    A  ** RABAX: level LEV_RX_DATASET_CLOSE completed.
    A  ** RABAX: level LEV_RX_RESET_SHMLOCKS entered.
    A  ** RABAX: level LEV_RX_RESET_SHMLOCKS completed.
    A  ** RABAX: level LEV_RX_ERROR_SAVE entered.
    A  ** RABAX: level LEV_RX_ERROR_SAVE completed.
    A  ** RABAX: level LEV_RX_ERROR_TPDA entered.
    A  ** RABAX: level LEV_RX_ERROR_TPDA completed.
    A  ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.
    A  ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.
    A  ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.
    A  ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.
    A  ** RABAX: level LEV_RX_END entered.
    A  ** RABAX: level LEV_RX_END completed.
    A  ** RABAX: end no http/smtp
    A  ** RABAX: end RX_BTCHLOG|RX_VBLOG
    A  Syntax error in program CL_FDT_MAINTENANCE============CP        ..


    A Tue Jun 12 12:54:48 2007
    A  GENER request remote generation: CL_FDT_MAINTENANCE============CP.

    A Tue Jun 12 12:54:49 2007
    A  *** ERROR => Syntax error in program CL_FDT_MAINTENANCE============CP         [abgen.c      1517]
    A  *** ERROR => > Include CL_FDT_MAINTENANCE============CM01D      line 1 [abgen.c      1519]
    A  *** ERROR => > Method "DELETE_OBJECT_PERMANENTLY" does not exist. There is, however a method wi [abgen.c      1521]
    A  *** ERROR => > th the similar name "DELETE_PERMANENTLY". [abgen.c      1523]
    A  TH VERBOSE LEVEL FULL
    A  ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.
    A  ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.
    A  ** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.
    A  ** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.
    A  ** RABAX: level LEV_RX_ROLLBACK entered.
    A  ** RABAX: level LEV_RX_ROLLBACK completed.
    A  ** RABAX: level LEV_RX_DB_ALIVE entered.
    A  ** RABAX: level LEV_RX_DB_ALIVE completed.
    A  ** RABAX: level LEV_RX_HOOKS entered.
    A  ** RABAX: level LEV_RX_HOOKS completed.
    A  ** RABAX: level LEV_RX_STANDARD entered.
    A  ** RABAX: level LEV_RX_STANDARD completed.
    A  ** RABAX: level LEV_RX_STOR_VALUES entered.
    A  ** RABAX: level LEV_RX_STOR_VALUES completed.
    A  ** RABAX: level LEV_RX_C_STACK entered.
    A  ** RABAX: level LEV_RX_C_STACK completed.
    A  ** RABAX: level LEV_RX_MEMO_CHECK entered.
    A  ** RABAX: level LEV_RX_MEMO_CHECK completed.
    A  ** RABAX: level LEV_RX_AFTER_MEMO_CHECK entered.
    A  ** RABAX: level LEV_RX_AFTER_MEMO_CHECK completed.
    A  ** RABAX: level LEV_RX_INTERFACES entered.
    A  ** RABAX: level LEV_RX_INTERFACES completed.
    A  ** RABAX: level LEV_RX_GET_MESS entered.
    A  ** RABAX: level LEV_RX_GET_MESS completed.
    A  ** RABAX: level LEV_RX_INIT_SNAP entered.
    A  ** RABAX: level LEV_RX_INIT_SNAP completed.
    A  ** RABAX: level LEV_RX_WRITE_SYSLOG entered.
    A  ** RABAX: level LEV_RX_WRITE_SYSLOG completed.
    A  ** RABAX: level LEV_RX_WRITE_SNAP entered.
    A  GENER request remote generation: CL_FDT_MAINTENANCE============CP.

    A Tue Jun 12 12:54:50 2007
    A  *** ERROR => Syntax error in program CL_FDT_MAINTENANCE============CP         [abgen.c      1517]
    A  *** ERROR => > Include CL_FDT_MAINTENANCE============CM01D      line 1 [abgen.c      1519]
    A  *** ERROR => > Method "DELETE_OBJECT_PERMANENTLY" does not exist. There is, however a method wi [abgen.c      1521]
    A  *** ERROR => > th the similar name "DELETE_PERMANENTLY". [abgen.c      1523]
    A  ** RABAX:  level LEV_SN_EVENTS failed.
    A  ** RABAX: level LEV_RX_WRITE_SNAP entered.
    A  ** RABAX: level LEV_SN_END completed.
    A  ** RABAX: level LEV_RX_SET_ALERT entered.
    A  ** RABAX: level LEV_RX_SET_ALERT completed.
    A  ** RABAX: level LEV_RX_COMMIT entered.
    A  ** RABAX: level LEV_RX_COMMIT completed.
    A  ** RABAX: level LEV_RX_SNAP_SYSLOG entered.
    A  ** RABAX: level LEV_RX_SNAP_SYSLOG completed.
    A  ** RABAX: level LEV_RX_RESET_PROGS entered.
    A  ** RABAX: level LEV_RX_RESET_PROGS completed.
    A  ** RABAX: level LEV_RX_STDERR entered.
    A  Tue Jun 12 12:54:50 2007

    A  ABAP Program CL_FDT_TRANS==================CP        .
    A  Source CL_FDT_TRANS==================CM001      Line 1.
    A  Error Code SYNTAX_ERROR.
    A  Module  $Id: //bas/700_REL/src/krn/runt/abgen.c#10 $ SAP.
    A  Function ab_genprog Line 1551.
    A  ** RABAX: level LEV_RX_STDERR completed.
    A  ** RABAX: level LEV_RX_RFC_ERROR entered.
    A  ** RABAX: level LEV_RX_RFC_ERROR completed.
    A  ** RABAX: level LEV_RX_RFC_CLOSE entered.
    A  ** RABAX: level LEV_RX_RFC_CLOSE completed.
    A  ** RABAX: level LEV_RX_IMC_ERROR entered.
    A  ** RABAX: level LEV_RX_IMC_ERROR completed.
    A  ** RABAX: level LEV_RX_DATASET_CLOSE entered.
    A  ** RABAX: level LEV_RX_DATASET_CLOSE completed.
    A  ** RABAX: level LEV_RX_RESET_SHMLOCKS entered.
    A  ** RABAX: level LEV_RX_RESET_SHMLOCKS completed.
    A  ** RABAX: level LEV_RX_ERROR_SAVE entered.
    A  ** RABAX: level LEV_RX_ERROR_SAVE completed.
    A  ** RABAX: level LEV_RX_ERROR_TPDA entered.
    A  ** RABAX: level LEV_RX_ERROR_TPDA completed.
    A  ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.
    A  ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.
    A  ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.
    A  ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.
    A  ** RABAX: level LEV_RX_END entered.
    A  ** RABAX: level LEV_RX_END completed.
    A  ** RABAX: end no http/smtp
    A  ** RABAX: end RX_BTCHLOG|RX_VBLOG
    A  Syntax error in program CL_FDT_MAINTENANCE============CP        ..

    Also in st22 it is showing abap dumps. I am copying that result too
    Runtime Errors         SYNTAX_ERRORDate and Time          12.06.2007 12:54:49--|Short text                                                                                ||    Syntax error in program "CL_FDT_MAINTENANCE============CP ".                                  ||What happened?                                                                                ||    Error in the ABAP Application Program                                                         ||                                                                                ||    The current ABAP program "CL_FDT_TRANS==================CP" had to be                         ||     terminated because it has                                                                    ||    come across a statement that unfortunately cannot be executed.                                ||                                                                                ||    The following syntax error occurred in program                                                ||     "CL_FDT_MAINTENANCE============CP " in include                                               ||     "CL_FDT_MAINTENANCE============CM01D " in                                                    ||    line 1:                                                                                ||    "Method "DELETE_OBJECT_PERMANENTLY" does not exist. There is, however a"                      ||    " method with the similar name "DELETE_PERMANENTLY"."                                         ||    " "                                                                                ||    " "                                                                                ||                                                                                ||    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_FDT_TRANS==================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 "CL_FDT_MAINTENANCE============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                                           ||     CL_FDT_MAINTENANCE============CP :                                                           ||    "Method "DELETE_OBJECT_PERMANENTLY" does not exist. There is, however a"                      ||    " method with the similar name "DELETE_PERMANENTLY"."                                         ||    " "                                                                                ||    " "                                                                                ||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... "wicomp06"                                                              ||    Network address...... "10.201.52.95"                                                          ||    Operating system..... "Windows NT"                                                            ||    Release.............. "5.2"                                                                   ||    Hardware type........ "IA64 Level 32 ("                                                       ||    Character length.... 16 Bits                                                                  ||    Pointer length....... 64 Bits                                                                 ||    Work process number.. 13                                                                      ||    Shortdump setting.... "full"                                                                  ||                                                                                ||    Database server... "WICOMP06"                                                                 ||    Database type..... "ORACLE"                                                                   ||    Database name..... "C27"                                                                      ||    Database user ID.. "SAPSR3"                                                                   ||                                                                                ||    Char.set.... "C"                                                                              ||                                                                                ||    SAP kernel....... 700                                                                         ||    created (date)... "Feb 4 2008 04:41:16"                                                       ||    create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"                              ||    Database version. "OCI_10201_SHARE (10.2.0.1.0) "                                             ||                                                                                ||    Patch level. 146                                                                              ||    Patch text.. " "                                                                              ||                                                                                ||    Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."                ||    SAP database version. 700                                                                     ||    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows                ||     NT 6.0"                                                                                ||                                                                                ||    Memory consumption                                                                            ||    Roll.... 16192                                                                                ||    EM...... 25139040                                                                             ||    Heap.... 0                                                                                ||    Page.... 40960                                                                                ||    MM Used. 11416832                                                                             ||    MM Free. 1149616                                                                              ||User and Transaction                                                                              ||                                                                                ||    Client.............. 000                                                                      ||    User................ "DDIC"                                                                   ||    Language key........ "E"                                                                      ||    Transaction......... " "                                                                      ||    Transactions ID..... "C51E19DCC70DF112931E000087122C61"                                       ||                                                                                ||    Program............. "CL_FDT_TRANS==================CP"                                       ||    Screen.............. "SAPMSSY0 1000"                                                          ||    Screen line......... 6                                                                        ||Information on where terminated                                                                   ||    Termination occurred in the ABAP program "CL_FDT_TRANS==================CP" -                 ||     in "DEPLOY_DB_OBJECT_LIST".                                                                  ||    The main program was "RDDEXECU ".                                                             ||                                                                                ||    In the source code you have the termination point in line 1                                   ||    of the (Include) program "CL_FDT_TRANS==================CM001".                               ||    The program "CL_FDT_TRANS==================CP" was started as a background job.               ||    Job Name....... "RDDEXECL"                                                                    ||    Job Initiator.. "DDIC"                                                                        ||    Job Number..... 12544600                                                                      ||Source Code Extract                                                                               ||Line |SourceCde                                                                                ||>>>>>|METHOD deploy_db_object_list.                                                               ||    2|                                                                                ||    3|  REFRESH et_message.                                                                       ||    4|                                                                                ||    5|  DATA: lt_message TYPE if_fdt_types=>t_message,                                            ||    6|        lv_failed  TYPE abap_bool,                                                          ||    7|        lts_object_id_activate   TYPE if_fdt_types=>ts_object_id,                           ||    8|        lts_object_id_delete     TYPE if_fdt_types=>ts_object_id,                           ||    9|        lts_object_id_delete_phy TYPE if_fdt_types=>ts_object_id,                           ||   10|        lv_lock_scope_option     TYPE cl_fdt_locking=>scope_option.                         ||   11|                                                                                ||   12|************************************************************************                    ||   13|* A) DB Copy of the specified versions.                                                     ||   14|************************************************************************                    ||   15|  CALL METHOD cl_fdt_trans_db=>copy_for_db_object_list                                      ||   16|    EXPORTING                                                                               ||   17|      iv_target_client         = iv_target_client                                           ||   18|      iv_trrequest             = iv_trrequest                                               ||   19|      iv_force_overwrite       = iv_force_overwrite     "message0000391286                  ||   20|      iv_table_type_from       = iv_table_type_from                                         ||Contents of system fields                                                                         ||Name    |Val.                                                                                ||SY-SUBRC|0                                                                                ||SY-INDEX|0                                                                                ||SY-TABIX|1                                                                                ||SY-DBCNT|1                                                                                ||SY-FDPOS|2                                                                                ||SY-LSIND|0                                                                                ||SY-PAGNO|0                                                                                ||SY-LINNO|1                                                                                ||SY-COLNO|1                                                                                ||SY-PFKEY|                                                                                ||SY-UCOMM|                                                                                ||SY-TITLE|Execute Post-Import Methods and XPRAs for Transport Request                              ||SY-MSGTY|                                                                                ||SY-MSGID|                                                                                ||SY-MSGNO|000                                                                                ||SY-MSGV1|LIMU                                                                                ||SY-MSGV2|WDYV                                                                                ||SY-MSGV3|                                                                                ||SY-MSGV4|                                                                                ||SY-MODNO|0                                                                                ||SY-DATUM|20070612                                                                                ||SY-UZEIT|125447                                                                                ||SY-XPROG|SAPLSYST                                                                                ||SY-XFORM|SYSTEM_HOOK_OPEN_DATASET                                                                 ||Active Calls/Events                                                                               ||No.   Ty.          Program                             Include                             Line   ||      Name                                                                                ||    7 METHOD       CL_FDT_TRANS==================CP    CL_FDT_TRANS==================CM001     1  ||      CL_FDT_TRANS=>DEPLOY_DB_OBJECT_LIST                                                         ||    6 METHOD       CL_FDT_TRANS_CONNECTOR========CP    CL_FDT_TRANS_CONNECTOR========CM001    56  ||      CL_FDT_TRANS_CONNECTOR=>R3TRANS                                                             ||    5 FUNCTION     SAPLFDT_TRANS_IMP_EXP_PHASE         LFDT_TRANS_IMP_EXP_PHASEU04            57  ||      FDT_AFTER_IMPORT                                                                            ||    4 FORM         SAPLSCTS_EXE_EXP                    LSCTS_EXE_EXPF02                      351  ||      CALL_IMP_METHODS_IN_CLIENT                                                                  ||    3 FORM         SAPLSCTS_EXE_EXP                    LSCTS_EXE_EXPF02                       87  ||      CALL_IMP_METHODS                                                                            ||    2 FUNCTION     SAPLSCTS_EXE_EXP                    LSCTS_EXE_EXPU02                      103  ||      TRINT_CALL_AFTER_IMP_METHOD                                                                 ||    1 EVENT        RDDEXECU                            RDDEXECU                              168  ||      START-OF-SELECTION                                                                          ||Chosen variables                                                                                ||Name                                                                                ||    Val.                                                                                ||No.       7 Ty.          METHOD                                                                   ||Name  CL_FDT_TRANS=>DEPLOY_DB_OBJECT_LIST                                                         ||IV_TARGET_CLIENT                                                                                ||                                                                                ||    222            

  • 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

  • ABAP /4 processor: SYNTAX_ERROR

    Hi experts,
    I am basis engineer and I noticed one job fails in only one particular app server with ABAP dump.
    ABAP runime errors: SYNTAX_ERROR
    but the same job run well on other application servers.
    When i check the dump it say
    What happened?
    The following syntax error occurred in the program SAPLYBBP" include report "lybbpu16" not found
    Please help?
    Thanks
    Vijay

    The "lybbpu16" does not exist on any app server when i check from SE38.
    but this is avilable from calling system.
    Called system is XX1
    Calling system is XX2, lybbpu16 is existing on XX2 but the dump is created on XX1 with SYNTAX_ERROR and dump created on XX2 with CALL_FUNCTION_REMOTE_ERROR with
    "Syntax error in program SAPLYBBP
    Thanks
    Vijay

  • Dump: ABAP/4 processor: ASSIGN_TYPE_CONFLICT

    Hi SAP gurus
    Load fails with shortdump
    Tried again 2 times.
    Very high priority please solve.
    Fulls points will be assigned if no dump.
    Greetings

    Hi George,
    Activate the Transformationa nd try to load again.
    If you change the Data target and you have noit activated the transformation, you will get this type of Dump.
    Regards
    Gopal

  • BI 7.0 Dump: ABAP/4 processor: ASSIGN_TYPE_CONFLICT

    Dear Friends,
    Could any of u pl. provide me solution to above error. I am trying to load transaction data from flat file into BI 7.0
    the problem is specific to unit characteristics 0unit & 0currency.
    Data Source has following fields.
    Production qty
    0unit
    production value
    0currency.
    I have created the said objects in cube as well, mapped IS to DS, then created transformation. everything works fine. But the loading fails.
    could you pl. give ur inputs.
    Regards
    Paddy

    Thanks to all.
    I checked in SAP Service.com
    Pack 14 had to be updated, this was released on 27th June'07.
    Regards
    Paddy

  • Short dump ODS Syntax_Error- Urgent

    My chain steps,
    Load data (only PSA and Update Subsequently in data target)
    Update from PSA
    Delete PSA Request
    Activate ODS..
    While performing these steps, am getting the short Dump in ODS activation and   deleting the red request "ABAP/4 Processor: Syntax_Error".

    Job started
    Step 001 started (program RSODSACT1, variant &0000000005515, us
    Activation is running: Data target MPU09O74, from 19.886 to 19.
    Data to be activated successfully checked against archiving obj
    SQL: 20.11.2007 09:02:49 PJAIN
    ANALYZE TABLE "/BIC/AMPU09O7440" DELETE
    STATISTICS
    SQL-END: 20.11.2007 09:02:49 00:00:00
    SQL: 20.11.2007 09:02:49 PJAIN
    BEGIN DBMS_STATS.GATHER_TABLE_STATS ( OWNNAME =>
    'SAPEBF', TABNAME => '"/BIC/AMPU09O7440"',
    ESTIMATE_PERCENT => 1 , METHOD_OPT => 'FOR ALL
    INDEXED COLUMNS SIZE 75', DEGREE => 1 ,
    GRANULARITY => 'ALL', CASCADE => TRUE ); END;
    SQL-END: 20.11.2007 09:02:51 00:00:02
    SQL: 20.11.2007 09:02:51 PJAIN
    ANALYZE TABLE "/BIC/AMPU09O7400" DELETE
    STATISTICS
    SQL-END: 20.11.2007 09:02:51 00:00:00
    SQL: 20.11.2007 09:02:51 PJAIN
    BEGIN DBMS_STATS.GATHER_TABLE_STATS ( OWNNAME =>
    'SAPEBF', TABNAME => '"/BIC/AMPU09O7400"',
    ESTIMATE_PERCENT => 1 , METHOD_OPT => 'FOR ALL
    INDEXED COLUMNS SIZE 75', DEGREE => 1 ,
    GRANULARITY => 'ALL', CASCADE => TRUE ); END;
    SQL-END: 20.11.2007 09:02:51 00:00:00
    ABAP/4 processor: SYNTAX_ERROR
    Job cancelled

  • Short dump Error-ABAP/4 Run time Error

    Hi Expert,
    Dump:ABAP/4 Processor:MESSAGE_TYPE_X Why this error came,I would like to Investigation on Perticular error,Please Some body give me an Exact answer,so that i closed the ticket.
    Regards,
    Raju.

    Hi Suresh,
    What is the actual issue?
    When did you get this error.
    To know about this type of error, check below link...
    https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=dump%3aABAP%2F4Processor%3A+MESSAGE_TYPE_X&adv=false&sortby=cm_rnd_rankvalue
    Also check this:
    Note 1016317 - SP13:PC: Start type 'Date & time' gets scheduled wrong
    "Process chain scheduling results in dump- ABAP/4 processor: MESSAGE_TYPE_X"
    Solution:
    In the short dump analysis, the process fails at function module
    RSS2_PSA_NEW_OLD_DS
    call function 'RSDS_DATASOURCE_SINGLE_GET'
    Regards,
    KK.

  • DSWP short dump problem

    Hello
    I have installed new SP 25 with ABAP and JAVA on my client SOLMAN sistem. After that i have reconfigured solman_setup . When i enteren DSWP screen and click Sap solution it shows me up and short dump screen;
    Runtime Errors         SYNTAX_ERROR
    Date and Time          10.03.2011 14:55:55
    Short text
         Syntax error in program "SAPLCRM_ORDER_OW ".
    What happened?
         Error in the ABAP Application Program
         The current ABAP program "SAPLCRM_ORDER_API" had to be terminated because it
          has
         come across a statement that unfortunately cannot be executed.
         The following syntax error occurred in program "SAPLCRM_ORDER_OW " in include
          "LCRM_ORDER_OWU08 " in
         line 1359:
         "Different number of parameters in FORM and PERFORM (routine: READ_ITEM"
         "_EXT, number of formal parameters: 32, number of actual parameters: 31"
         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 "SAPLCRM_ORDER_API" had to be terminated because it
          has
         come across a statement that unfortunately cannot be executed.
    Error analysis
        The following syntax error was found in the program SAPLCRM_ORDER_OW :
        "Different number of parameters in FORM and PERFORM (routine: READ_ITEM"
        "_EXT, number of formal parameters: 32, number of actual parameters: 31"
    Trigger Location of Runtime Error
        Program                                 SAPLCRM_ORDER_API
        Include                                 LCRM_ORDER_APIU01
        Row                                     21
        Module type                             (FUNCTION)
        Module Name                             CRM_ORDER_INITIALIZE
    Source Code Extract
    Line  SourceCde
        1 FUNCTION crm_order_initialize.
        2 *"----
        3 ""Lokale Schnittstelle:
        4 *"  IMPORTING
        5 *"     REFERENCE(IT_GUIDS_TO_INIT) TYPE  CRMT_OBJECT_GUID_TAB OPTIONAL
        6 *"     REFERENCE(IV_INITIALIZE_WHOLE_BUFFER) TYPE  CRMT_BOOLEAN
        7 *"       OPTIONAL
        8 *"     REFERENCE(IV_INIT_FRAME_LOG) TYPE  CRMT_BOOLEAN OPTIONAL
        9 *"     REFERENCE(IV_LOG_HANDLE) TYPE  BALLOGHNDL OPTIONAL
       10 *"     REFERENCE(IV_KEEP_LOCK) TYPE  CRMT_BOOLEAN DEFAULT FALSE
       11 *"  EXCEPTIONS
       12 *"      ERROR_OCCURRED
       13 *"----
       14
       15 * Debug functionality for external calls of One Order APIs
       16   include crm_trace_initialize.
       17
       18 * Initialize business partner buffer
       19   CALL FUNCTION 'BUP_BUFFER_INIT'.
       20
    >>>>>   CALL FUNCTION 'CRM_ORDER_INIT_OW'
       22        EXPORTING
       23             it_guids_to_init           = it_guids_to_init
       24             iv_initialize_whole_buffer = iv_initialize_whole_buffer
       25             iv_init_frame_log          = iv_init_frame_log
       26             iv_log_handle              = iv_log_handle
       27             iv_keep_lock               = iv_keep_lock
       28        EXCEPTIONS
       29             OTHERS                    = 1.
       30
       31   IF sy-subrc NE 0.
       32     MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
       33             WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4
       34             RAISING error_occurred.
       35   ENDIF.
       36
       37 ENDFUNCTION.
    Whats is the problem?
    Thank you
    Fatih

    Hello,
    Have you checked SAP Note 1168593 - Short dumps in 'CRM_ORDER_READ_OW' for multiple
    pricing cond" to see if it is applicable to your Release and SP levels?
    Regards,
    Paul

  • ABAP/4 processor: UNCAUGHT_EXCEPTION - Activation job cancelled short dump

    Hi All,
    I loaded data to the new table of ODS successfully. But the data is not available for reporting.
    When i try to activate the request,it shows no error bt neither does data *** to active table .I checkd in sm37 for logs, it shows ABAP/4 processor: UNCAUGHT_EXCEPTION error. It shows that CX_SDB_ORA_PROGRAM_ERROR exception was raised.
    I also checked in table RSODSACTREQ in SE16 and found that status was 0 (means activation successful) n operation was U (means updating) .........
    The same problem persists for activation job for any ODS.......The support package has been upgraded from 11 to 14 recently.......
    Please help me resolve this issue.
    Regards,

    Prithi,
    Check out for invalid char's in the PSA.....
    Check monitoring  for invalid char's .. some time it will reach up to New data table and while activation it may get struc...
    hope there is some prob with invalid char's aor length of char.... Special char..like @__ in PSA .
    Cheer's
    HVR.

  • Zci type ADOBE Interactive Form in ABAP Webdynpro short dump

    Adobe Reader version 8.1.2
    Life Cycle Designer version 7.1.4270.1.421766
    ECC 6.0 patch 13
    When I ran the 'FP_PDF_TEST_00' , it shows
    Version Information: 710.20061024154505.342190
    In my ABAP Webdynpro app., it has 3 inputfields.
    In the Form layout, I changed the form layout type to 'ZCI' for interactive form, and Insert the WebDynpro Script.
    And in the ABAP Webdynpro view layput designer, I enabled the pdf form element.
    All objects compiled without any problem.
    During the runtime, it got the following short dump:
    21 METHOD       CX_WD_GENERAL=================CP    CX_WD_GENERAL=================CM003     5
        CX_WD_GENERAL=>RAISE                                                                     
    20 METHOD       CL_WD_ADOBE_SERVICES==========CP    CL_WD_ADOBE_SERVICES==========CM008   193
        CL_WD_ADOBE_SERVICES=>CREATE_PDF                                                         
    19 METHOD       /1WDA/LADOBE==================CP    /1WDA/LADOBE==================CCIMP  1955
        CL_INTERACTIVE_FORM_ZCI=>IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT                         
    Our BASIS sent me the ADS trace:
    SAP Interactive Forms by Adobe
    Render Error Report
    'pdf' Log Entries
    restoreState is not a valid attribute of subform, Attribute not loaded. Line 5.
    Invalid node type: dataGroup
    The fault occurred on line 0.
    The SOM expression '$record.BAPIBNAME' for the dataRef specified on field 'BAPIBNAME', resolved to an incompatible node type of 'dataGroup'.
    Any comment or advise?

    Hi,
    As far as i know when you use Adobe forms in a WD4A application, language is your "web" connection language.
    You can have a look at standard class CL_WD_ADOBE_SERVICE, it's used when generating an adobe forms from WD4A. , more particulary look at method DETERMINE_DOCPARAMS.
    regards

  • Short Dump While selecting Variant for ABAP query

    Hi,
    ABAP query is going to short dump (CONNE_IMPORT_WRONG_COMP_LENG) while selecting a Variant. If i create and use variant then i am able to see Output of Variant.But not able to use Earlier created variants .
    I think some mismatch between variant values and selection screen fields.Can anyone tell me how to rectify this ?
    I am not able to debug the code as dump is coming in a System program(RSDBSPVD).Can anyone tell me which database table i can use to get values of the Variant.
    Thanks in Advance.
    Nirmala K

    Hi nirmala,
    chk the links:
    http://help.sap.com/saphelp_webas620/helpdata/en/c0/980398e58611d194cc00a0c94260a5/content.htm
    http://help.sap.com/saphelp_webas620/helpdata/en/c0/9803a7e58611d194cc00a0c94260a5/content.htm
    regards,
    keerthi.

  • What are the major situations  to go to the short dump in abap programming?

    What are the major situations  to go to the short dump in abap programming?

    Hi,
    The major situations that an ABAP Program can result a dumb are as follows...
    1) Poor coding i.e., if the data in the data base is less, then even a poor code can give you the result.  But when you transport the program into Production, then there the same program will give you a dump, resulting 'TIMED OUT' error.  So performance tunning is required for each and every program.
    2) while calling a function module.
    3) extracting of data into fields which are not type casted.
    4) in case of x/y value, one should check the value of 'y' should not be zero, else a dump will result.
    these are few which i can give for time being........

  • ABAP short dump with "CNTL_ERROR"

    Hi,
    I am getting an ABAP short dump with "CNTL_ERROR" while using an input script. What do I do?
    Thanks,
    Sreekar.

    Hi,
    Newer versions of SAP GUI and R/3 include external controls called as ActiveX (OCXs). ABAP code internally issues some commands to flush and refresh these controls. Since, when using GuiXT and input scripting, these controls are not created, and ABAP dumps. Use keyword "Enable controls" (without quotes on a separate line) in a screen block that has an ActiveX control.
    Example:
    Screen SAPLCOIH.3000
      Enter "/Menu=4,1,5"
    Screen SAPLSP01.0100
      Enter "=No"
    Screen RIPLKO10.1000
      Enable controls
      Set F[Group] "UG"
      Enter "/8"
    Reward Points if found helpfull..
    Cheers,
    Chandra Sekhar.

Maybe you are looking for