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            

Similar Messages

  • SYNTAX_ERROR program RDDEXECL at XPRA_EXECUTION in Importing BI_CONT 703

    Hi,
    I need help. I encountered error in importing the OCS Package SAPKIBIIP4 (BI_CONT 703) in Solution Manager.
    Below are the following details of error:
    Error in phase: XPRA_EXECUTION
    Reason for error: TP_STEP_FAILURE
    Return code: 0012
    Error message: OCS Package SAPKIBIIP4, tp step R, return code 0012.
    I have re-imported the support package several times, unluckily; I still get stuck in the same error.
    I tried to do adjust the modification adjustment, as advised by sap note 822379, but unfortunately no objects were found to be adjusted.
    Can someone help me with this? All inputs are highly appreciated.
    Thanks in advance!

    Hi,
    Short text
    Syntax error in program "SAPLRSVERS ".
    What happened?
       Error in the ABAP Application Program
       The current ABAP program "SAPLSCTS_EXE_EXP" had to be terminated because
       come across a statement that unfortunately cannot be executed.
       The following syntax error occurred in program "SAPLRSVERS " in include
        "%_CRRO01 " in
       line 539:
       "The type "RRHIERACTTP" is unknown."
       The include has been created and last changed by:
       Created by: "SAP "
       Last changed by: "SAP "

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

  • 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

  • Error in Automatic Payment Program : ABAP/4 processor : GETWA_NOT_ASSIGNED

    Hi SAP gurus,
    I'm currently implementing automatic payment using DME to generate a text file, in a format that is specified by HSBC.
    I read some articles about this topic and I have done these steps:
    I created DME Format Tree (just a demo format tree).
    I created a new Payment Media Format
    Set up Payment Method and Assigned Payment Media Format.
    But finally it didn't work.
    After I run F110, the posting was okay but no Data Media File was created. The end of Job Log Entry look like below:
    "Step 002 started (program SAPFPAYM_SCHEDULE, variant &0000000001977, user ID DANGNH)
    ABAP/4 processor : GETWA_NOT_ASSIGNED
    Job cancelled"
    I don't understand why it won't work. Does anyone here have any suggestion for this problem.
    Thanks and regards.
    HaiDang.
    Edited by: Maxielight on Jun 28, 2010 2:14 PM

    Dear Madhu,
    I have followed your suggestion but It didn't work. I used transaction SE38 to run RGZZGLUX as yousuggested.
    I used ST12 to analyse runtime errors and the analysis information look like below:
    Short text
          Field symbol has not yet been assigned
    What happend?
          Error in the ABAP Application Program.
          The current ABAP program "SAPLDMEE2_ABA" had to be terminated because it has come across a statement
          that unfortunately cannot be executed.
    Error Analysis
          You attempted to access an unassigned field symbol (Data Segment 8)
    Any suggestion?
    Maxielight.

  • ABAP program fails  in process chain -'ABAP/4 processor: DBIF_NTAB_SQL_ER

    Hi Experts,
    I have an ABAP program in  process chain. It frequently fails in the chain .
    When i do repeat on it will run fine.
    Purpose of the program is to delete the content from open hub table.
    I can    'ABAP/4 processor: DBIF_NTAB_SQL_ERROR' .
    What could be the reason . How can i give permenant fix to it.
    Thanks in Advance

    Hi,
    It looks like database error, speak to your DBA/Basis to get it resolved.
    regards
    Vikash

  • ABAP/4 processor: ASSERTION_FAILED

    Hi BW Experts,
    When we transport one of our Billing DSO and update rules linked to it from Dev to Quality the transport is failing with the below error message.
    09/24/2007  18:35:02  Job started
    09/24/2007  18:35:02  Step 001 started (program RDDEXECL, variant , user ID DDIC)
    09/24/2007  18:35:02  All DB buffers of application server sisbiq02 were synchronized
    09/24/2007  18:35:07  SQL: 24.09.2007 18:35:07 DDIC
    09/24/2007  18:35:07   CREATE UNIQUE INDEX "/BIC/B0001090000~0" ON
    09/24/2007  18:35:07  "/BIC/B0001090000" ("REQUEST", "DATAPAKID",
    09/24/2007  18:35:07  "PARTNO", "RECORD") PCTFREE 10 LOCAL INITRANS 002
    09/24/2007  18:35:07  TABLESPACE PSAPSR3 STORAGE (INITIAL
    09/24/2007  18:35:07  0000000016 K NEXT        0000000160 K MINEXTENTS
    09/24/2007  18:35:07  0000000001 MAXEXTENTS  UNLIMITED PCTINCREASE 0000
    09/24/2007  18:35:07  FREELISTS   004
    09/24/2007  18:35:07  SQL-END: 24.09.2007 18:35:07 00:00:00
    09/24/2007  18:35:10  STDO: Log  could not be written on output device T
    09/24/2007  18:35:20  Replication completed successfully
    09/24/2007  18:35:25  Communication Structure /BIC/CS8ZD2C_O33 activated
    09/24/2007  18:35:36  Transfer Rule(s) 8ZD2C_O33_AA activated
    09/24/2007  18:36:55  ABAP/4 processor: ASSERTION_FAILED
    09/24/2007  18:36:55  Job cancelled
    =================
    When i checked the short dump this is analysis provided...
    What happened?
        In the running application program, the ASSERT statement recognized a
        situation that should not have occurred.
        The runtime error was triggered for one of these reasons:
        - For the checkpoint group specified with the ASSERT statement, the
          activation mode is set to "abort".
        - Via a system variant, the activation mode is globally set to "abort"
          for checkpoint groups in this system.
        - The activation mode is set to "abort" on program level.
        - The ASSERT statement is not assigned to any checkpoint group.
    ====================
    How to correct the error
        Probably the only way to eliminate the error is to correct the program.
        If the error occures in a non-modified SAP program, you may be able to
        find an interim solution in an SAP Note.
        If you have access to SAP Notes, carry out a search with the following
        keywords:
        "ASSERTION_FAILED" " "
        "CL_RSAR_PSA===================CP" or "CL_RSAR_PSA===================CM006"
        "_UPDATE_DIRECTORY_TABLES"
        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.
    Did any of you faced this problem
    Can you suggest how to solve the problem... Whether we have to raise SAP message... or any other solution.....
    We are in BI 7.0 with support pack 12.....
    Thanks a lot in advance
    Mahesh reddi

    Hi
    Already one post is there anyway
    If you have checked this message you would know that it got failed after transformation step...i guess its because of some formula in transformation which are causing this problem...you would need support pack 13.
    OSS -1025748
    Thanks
    Tripple k

  • Report giving error when scheduled in background (ABAP/4 processor:PERFORM)

    Dear Freinds,
               I have written a custom program and iam not able schedule in background, if check in SM37 the job getting canceleld and found as the error ABAP/4 processor: PERFORM_NOT_FOUND.
    Please could you let me know should i specify in my custom program for get sucessfully run in background . or could any one please let me know any setting should be done for my custom program
    regards
    madhuri

    Hi
         when i run in foreground it is working perfectly. The Spool is not getting created.
    regards
    madhuri
    Edited by: madhuri_2000 kumari on Nov 26, 2008 2:00 PM

  • Error Info...   ABAP/4 processor: SAPSQL_ARRAY_INSERT_DUPREC

    Update was terminated
    System ID....   ZDE
    Transaction..   ABUMN
    Update key...   4CA0A62864FF0068E1008000093FF453
    Generated....   28.09.2010, 09:39:14
    Completed....   28.09.2010, 09:39:15
    Error Info...   ABAP/4 processor: SAPSQL_ARRAY_INSERT_DUPREC
    While transferring asset using ABUMN transaction I am getting this error message
    I have implemented a implicit enhancement in    FM  AMBU_CALL_AC_DOCUMENT_POST  in which BAPI_EQUI_CHANGE is used to change the equipment with the new asset no.When I comment the BAPI there is no error .What might be the cause of this error in the BAPI_EQUI_CHANGE and is there an alternative to this BAPI
    I

    Hi Praveen,
    You can get the detailed error info for this error in SM13 transaction where we can check update error,which program/function module caused error in update task. You can also execute your code in bebugging mode from here.
    The Error you got occurs when transaction / program tries to commit database that would result in a duplicate entry in a
    table with primary key and hence the update failes,
    Regards,
    Pawan

  • ABAP/4 processor: UNCAUGHT_EXCEPTION while activation

    Hi All,
    I am getting this error "ABAP/4 processor: UNCAUGHT_EXCEPTION" while the activation of DSO. I am attaching the dump
    Runtime Errors         UNCAUGHT_EXCEPTION
    Exception              CX_SDB_ORA_PROGRAM_ERROR
    Date and Time          19.12.2008 03:02:53
    Short text
    An exception occurred that was not caught.
    What happened?
    The exception 'CX_SDB_ORA_PROGRAM_ERROR' was raised, but it was not caught
    anywhere along
    the call hierarchy.
    Since exceptions represent error situations and this error was not
    adequately responded to, the running ABAP program
    'CL_SDB_ORA_UPDATE_STATS=======CP' has to be
    terminated.
    What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
    Error analysis
    An exception occurred which is explained in detail below.
    The exception, which is assigned to class 'CX_SDB_ORA_PROGRAM_ERROR', was not
    caught and
    therefore caused a runtime error.
    The reason for the exception is:
    An error occurred in the program:
    The occurrence of the exception is closely related to the occurrence of
    a previous exception "CX_SQL_EXCEPTION", which was raised in the program
    "CL_SQL_STATEMENT==============CP",
    specifically in line 31 of the (include) program
    "CL_SQL_STATEMENT==============CM002".
    The cause of the exception was:
    ORA-04031: unable to allocate 62208 bytes of shared memory ("shared
    pool","DBMS_STATS","PL/SQL MPCODE","BAMIMA: Bam Buffer")
    ORA-06508: PL/SQL:
    could not find program unit being called: "SYS.DBMS_STATS"
    ORA-06512: at line 1
    How to correct the error
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "UNCAUGHT_EXCEPTION" "CX_SDB_ORA_PROGRAM_ERROR"
    "CL_SDB_ORA_UPDATE_STATS=======CP" or "CL_SDB_ORA_UPDATE_STATS=======CM00I"
    "UPDATE_STATS"
    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... "gwpsapci"
    Network address...... "10.220.136.60"
    Operating system..... "AIX"
    Release.............. "5.3"
    Hardware type........ "0005E935D600"
    Character length.... 8 Bits
    Pointer length....... 64 Bits
    Work process number.. 30
    Shortdump setting.... "full"
    Database server... "de08u1642"
    Database type..... "ORACLE"
    Database name..... "GWP"
    Database user ID.. "SAPR3"
    Char.set.... "en_US.ISO8859-1"
    SAP kernel....... 700
    created (date)... "Aug 24 2008 21:05:40"
    create on........ "AIX 2 5 005DD9CD4C00"
    Database version. "OCI_102 (10.2.0.2.0) "
    Patch level. 175
    Patch text.. " "
    Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
    SAP database version. 700
    Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"
    Memory consumption
    Roll.... 16128
    EM...... 25139520
    Heap.... 0
    Page.... 24576
    MM Used. 12500304
    MM Free. 4256248
    User and Transaction
    Client.............. 950
    User................ "ZZSUPPORT"
    Language key........ "E"
    Transaction......... " "
    Transactions ID..... "494AFB8FEB5A00D6E10080000ADC883C"
    Program............. "CL_SDB_ORA_UPDATE_STATS=======CP"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
    Information on where terminated
    Termination occurred in the ABAP program "CL_SDB_ORA_UPDATE_STATS=======CP" -
    in "UPDATE_STATS".
    The main program was "RSPROCESS ".
    In the source code you have the termination point in line 40
    of the (Include) program "CL_SDB_ORA_UPDATE_STATS=======CM00I".
    The program "CL_SDB_ORA_UPDATE_STATS=======CP" was started as a background job.
    Job Name....... "BI_PROCESS_ODSACTIVAT"
    Job Initiator.. "E442207"
    Job Number..... 03030600
    Source Code Extract
    Line
    SourceCde
    10
    i_tablnm      = i_tablnm
    11
    i_signi       = i_signi
    12
    i_thresh_mod  = i_thresh_mod
    13
    i_degree      = i_degree
    14
    i_histo       = i_histo
    15
    i_granularity = i_granularity
    16
    i_cascade     = i_cascade
    17
    i_force       = i_force
    18
    i_flush       = i_flush
    19
    i_connection  = i_connection.
    20
    21
        Update Statistics
    22
    IF l_r_upd_stats->p_skip_upd IS initial.
    23
    CASE l_r_upd_stats->p_granularity.
    24
    WHEN 0. " DEFT
    25
    IF l_r_upd_stats->global_update_stats( ) = 'NO'.
    26
    l_r_upd_stats->part_update_stats( ).
    27
    ENDIF.
    28
    WHEN 1. " ALL
    29
    l_r_upd_stats->global_update_stats( ).
    30
    WHEN 2. " GLOBAL
    31
    l_r_upd_stats->global_update_stats( ).
    32
    WHEN 3. " PART
    33
    l_r_upd_stats->part_update_stats( ).
    34
    WHEN OTHERS. " AUTO
    35
    l_r_upd_stats->global_update_stats( ).
    36
    ENDCASE.
    37
    ENDIF.
    38
    39
    CATCH cx_sql_exception INTO l_r_exception.
    >>>>>
    RAISE EXCEPTION TYPE cx_sdb_ora_program_error
    41
    EXPORTING previous = l_r_exception.
    42
    CLEANUP.
    43
    TRY.
    44
    CATCH cx_sql_exception INTO l_r_exception.
    45
    RAISE EXCEPTION TYPE cx_sdb_ora_program_error
    46
    EXPORTING previous = l_r_exception.
    47
    ENDTRY.
    48
    ENDTRY.
    49
    50
    ENDMETHOD.
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    0
    SY-INDEX
    0
    SY-TABIX
    0
    SY-DBCNT
    0
    SY-FDPOS
    0
    SY-LSIND
    0
    SY-PAGNO
    0
    SY-LINNO
    1
    SY-COLNO
    1
    SY-PFKEY
    SY-UCOMM
    SY-TITLE
    Process Variant Run
    SY-MSGTY
    E
    SY-MSGID
    DA
    SY-MSGNO
    300
    SY-MSGV1
    SY-MSGV2
    SY-MSGV3
    SY-MSGV4
    SY-MODNO
    0
    SY-DATUM
    20081219
    SY-UZEIT
    030252
    SY-XPROG
    SAPCNVE
    SY-XFORM
    CONVERSION_EXIT
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    6 METHOD       CL_SDB_ORA_UPDATE_STATS=======CP    CL_SDB_ORA_UPDATE_STATS=======CM00I    40
    CL_SDB_ORA_UPDATE_STATS=>UPDATE_STATS
    5 FUNCTION     SAPLRSDU_UTIL_ORA                   LRSDU_UTIL_ORAU01                      86
    RSDU_ANALYZE_TABLE_ORA
    4 FUNCTION     SAPLRSDU_UTIL                       LRSDU_UTILU01                          38
    RSDU_ANALYZE_TABLE
    3 FUNCTION     SAPLRSSM_PROCESS                    LRSSM_PROCESSU30                     1476
    RSSM_PROCESS_ODSACTIVATE
    2 METHOD       CL_RSSM_ODSACTIVATE===========CP    CL_RSSM_ODSACTIVATE===========CM007   117
    CL_RSSM_ODSACTIVATE=>IF_RSPC_EXECUTE~EXECUTE
    1 EVENT        RSPROCESS                           RSPROCESS                             144
    START-OF-SELECTION
    Chosen variables
    Name
    Val.
    No.       6 Ty.          METHOD
    Name  CL_SDB_ORA_UPDATE_STATS=>UPDATE_STATS
    I_TABLNM
    /BIC/AOD13ITM340
    244424443345433322222222222222
    F293F1F41394D34000000000000000
    I_SIGNI
    5775488
    0
    0
    I_THRESH_MOD
    0
    0000
    0000
    I_DEGREE
    3
    0000
    0003
    I_HISTO
    2
    0
    I_GRANULARITY
    0
    0000
    0000
    I_CASCADE
    0
    0000
    0000
    I_FORCE
    2
    0
    I_FLUSH
    X
    5
    8
    I_CONNECTION
    222222222222222222222222222222
    000000000000000000000000000000
    SPACE
    2
    0
    L_R_UPD_STATS
    |
    | 0000000F |
    | 80000027 |
    | %_DUMMY$$ |
    |  |
    | 2222 |
    | 0000 |
    | SY-REPID |
    | CL_SDB_ORA_UPDATE_STATS=======CP |
    | 4455445454555445455545533333334522222222 |
    | 3CF342FF21F504145F34143DDDDDDD3000000000 |
    | SY-XFORM |
    | CONVERSION_EXIT |
    | 444545544454545222222222222222 |
    | 3FE65239FEF5894000000000000000 |
    | L_R_EXCEPTION |
    |
    E0000001
    80000037
    SYST
    #######################################################A#######ÿ###############(##############
    000000000000000000000000000000000000000000000000000000040000000F000000000000000200000000000000
    000000000000000100000000000000000000000000000000000100010001000F000000000000000800000000000000
    SY
    #######################################################A#######ÿ###############(##############
    000000000000000000000000000000000000000000000000000000040000000F000000000000000200000000000000
    000000000000000100000000000000000000000000000000000100010001000F000000000000000800000000000000
    %_EXCP
    E0000001
    70000038
    %_SPACE
    2
    0
    SYST-REPID
    CL_SDB_ORA_UPDATE_STATS=======CP
    4455445454555445455545533333334522222222
    3CF342FF21F504145F34143DDDDDDD3000000000
    No.       5 Ty.          FUNCTION
    Name  RSDU_ANALYZE_TABLE_ORA
    I_ALL_COLUMNS
    2
    0
    I_FORCE_ESTIMATE
    X
    5
    8
    I_FORCE_STATISTICS
    2
    0
    I_PERCENTAGE
    1
    0000
    0001
    I_PERCENTAGE_SPECIFIED
    X
    5
    8
    I_TABLNM
    /BIC/AOD13ITM340
    244424443345433322222222222222
    F293F1F41394D34000000000000000
    I_TEMP_TABLE
    2
    0
    I_T_TABLNM
    Table[initial]
    C_PROCESSED
    2
    0
    SY-REPID
    SAPLRSDU_UTIL_ORA
    5454554555544545422222222222222222222222
    310C2345F549CFF2100000000000000000000000
    <L_TABLNM>
    /BIC/AOD13ITM340
    244424443345433322222222222222
    F293F1F41394D34000000000000000
    SYST-REPID
    SAPLRSDU_UTIL_ORA
    5454554555544545422222222222222222222222
    310C2345F549CFF2100000000000000000000000
    %_SPACE
    2
    0
    SY
    #######################################################A#######ÿ###############(##############
    000000000000000000000000000000000000000000000000000000040000000F000000000000000200000000000000
    000000000000000100000000000000000000000000000000000100010001000F000000000000000800000000000000
    %_DUMMY$$
    2222
    0000
    L_SIGNI
    5775488
    0
    0
    L_PARALLEL_DEGREE
    3
    0000
    0003
    L_HISTO
    2
    0
    L_FLUSH
    X
    5
    8
    SY-ONCOM
    S
    5
    3
    No.       4 Ty.          FUNCTION
    Name  RSDU_ANALYZE_TABLE
    I_FORCE_ESTIMATE
    X
    5
    8
    I_FORCE_STATISTICS
    2
    0
    I_PERCENTAGE
    1
    0000
    0001
    I_TABLNM
    /BIC/AOD13ITM340
    244424443345433322222222222222
    F293F1F41394D34000000000000000
    I_TEMP_TABLE
    2
    0
    I_T_TABLNM
    Table[initial]
    SYST-REPID
    SAPLRSDU_UTIL
    5454554555544222222222222222222222222222
    310C2345F549C000000000000000000000000000
    RSDU_C_OBJTYPE-VIEW
    VIEW
    5445
    6957
    L_DBFUNC
    RSDU_ANALYZE_TABLE_ORA
    554554444554554444545422222222
    2345F1E1C9A5F412C5FF2100000000
    SY-XFORM
    CONVERSION_EXIT
    444545544454545222222222222222
    3FE65239FEF5894000000000000000
    L_PERCENTAGE_SPECIFIED
    X
    5
    8
    %_VIASELSCR
    0
    4
    %_ARCHIVE
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    L_PROCESSED
    2
    0
    RS_C_FALSE
    2
    0
    SY-SUBRC
    0
    0000
    0000
    SCREEN
    %_17NNS0000194530_%_%_%_%_%_%_
    2533445333333333352525252525252222222222222222222222222222222222222222222222222222222222222222
    5F17EE30000194530F5F5F5F5F5F5F0000000000000000000000000000000000000000000000000000000000000000
    SY-REPID
    SAPLRSDU_UTIL
    5454554555544222222222222222222222222222
    310C2345F549C000000000000000000000000000
    L_MESSAGE
    222222222222222222222222222222222222222222222222222222222222222222222222
    000000000000000000000000000000000000000000000000000000000000000000000000
    No.       3 Ty.          FUNCTION
    Name  RSSM_PROCESS_ODSACTIVATE
    I_CRT_ACTIVATION
    2
    0
    I_DROP_CREA_SEC_IND
    2
    0
    I_INSTANCE
    ODSA_4C7HUKHW8WV06KLJFFYZP95BW
    445453434544535533444445553345
    F431F43785B8787606BCA669A09527
    I_JOBNAME
    BI_PROCESS_ODSACTIVAT
    44555444555445445454522222222222
    29F02F3533FF43134961400000000000
    I_LOG_ID
    4C7HSJQKN58AR2DG5NSOGNB5O
    3434545443345344345444434
    43783A1BE58122475E3F7E25F
    I_NO_CONDENSE
    2
    0
    I_ODSOBJECT
    OD13ITM3
    443345432222222222222222222222
    F41394D30000000000000000000000
    I_PARENT_BATCH_ID
    222222222222222222222222222222
    000000000000000000000000000000
    I_SERIALIZE
    2
    0
    I_T_REQUEST_SEL
    Table[initial]
    I_VARIANT
    OD13ITM3_ACTIVATE
    443345435445454542222222222222
    F41394D3F134961450000000000000
    I_WITH_COMMIT
    X
    5
    8
    E_ERROR
    2
    0
    E_RNR
    ODSR_4C7HULKAVPVJRPAS8MAP3IYWS
    445553434544455545545344534555
    F432F43785CB1606A20138D1039973
    E_T_ACTIVATE_RNR
    Table[initial]
    E_T_ERROR_RNR
    Table[initial]
    E_T_MSG
    Table IT_18345[3x704]
    CLASS=CL_RSSM_ODSACTIVATEMETHOD=IF_RSPC_EXECUTE~EXECUTEDATA=L_T_MSG_PROC
    Table reference: 123
    TABH+  0(20) = 07000000A05FD4B0000000000000000000000000
    TABH+ 20(20) = 0000007B000047A900000003000002C0FFFFFFFF
    TABH+ 40(16) = 0400012500000D40001024C401800000
    store        = 0x07000000A05FD4B0
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 123   (0x0000007B)
    label        = 18345 (0x000047A9)
    fill         = 3     (0x00000003)
    leng         = 704   (0x000002C0)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000050
    occu         = 16    (0x00000010)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 8     (cmpManyEq)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x07000000A05750F0
    pgHook       = 0x0000000000000000
    idxPtr       = 0x0000000000000000
    shmTabhSet   = 0x0000000000000000
    id           = 10517 (0x00002915)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x00000010)
    lineAlloc    = 16    (0x00000010)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x00000001)
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    collHook     = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    E_T_ODSR_RNR
    Table[initial]
    L_LINES
    0
    0000
    0000
    %_DUMMY$$
    2222
    0000
    SCREEN
    %_17NNS0000194530_%_%_%_%_%_%_
    2533445333333333352525252525252222222222222222222222222222222222222222222222222222222222222222
    5F17EE30000194530F5F5F5F5F5F5F0000000000000000000000000000000000000000000000000000000000000000
    SY-REPID
    SAPLRSSM_PROCESS
    5454555455544455222222222222222222222222
    310C233DF02F3533000000000000000000000000
    SY-MSGID
    DA
    44222222222222222222
    41000000000000000000
    G_CHANGED
    2
    0
    SPACE
    2
    0
    SY-MSGNO
    300
    333
    300
    SY-MSGV1
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    SY-MSGV2
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    SY-MSGV3
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    SY-MSGV4
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    L_PERFORMED_ANALYZE
    2
    0
    G_R_ALV_GRID
    F0000000
    F0000000
    RS_C_TRUE
    X
    5
    8
    L_S_ODSTABNAME-M_TAB
    /BIC/AOD13ITM340
    244424443345433322222222222222
    F293F1F41394D34000000000000000
    SYST
    #######################################################A#######ÿ###############(##############
    000000000000000000000000000000000000000000000000000000040000000F000000000000000200000000000000
    000000000000000100000000000000000000000000000000000100010001000F000000000000000800000000000000
    <%_TABLE_RSDS>
    RSAU_C_PROTCLASS
    1234
    3333
    1234
    SYST-REPID
    SAPLRSSM_PROCESS
    5454555455544455222222222222222222222222
    310C233DF02F3533000000000000000000000000
    G_BUTTON_REQUDEL
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    %_SPACE
    2
    0
    No.       2 Ty.          METHOD
    Name  CL_RSSM_ODSACTIVATE=>IF_RSPC_EXECUTE~EXECUTE
    I_VARIANT
    OD13ITM3_ACTIVATE
    443345435445454542222222222222
    F41394D3F134961450000000000000
    I_EVENT_START
    RSPROCESS
    55554445522222222222222222222222
    2302F353300000000000000000000000
    I_EVENTP_START
    4BO77YTX6F8UVLQ22AEHHYIPO
    3443355534355453344445454222222222222222222222222222222222222222
    42F7794866856C1221588990F000000000000000000000000000000000000000
    I_JOBCOUNT
    03030600
    33333333
    03030600
    I_BATCHDATE
    20081218
    33333333
    20081218
    I_BATCHTIME
    030306
    333333
    030306
    I_T_PROCESSLIST
    Table IT_123[18x528]
    PROGRAM=RSPROCESSDATA=G_T_PROCESSLIST
    Table reference: 37
    TABH+  0(20) = 07000000A02596D8000000000000000000000000
    TABH+ 20(20) = 000000250000007B0000001200000210FFFFFFFF
    TABH+ 40(16) = 040000740000116800102CC421800000
    store        = 0x07000000A02596D8
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 37    (0x00000025)
    label        = 123   (0x0000007B)
    fill         = 18    (0x00000012)
    leng         = 528   (0x00000210)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000069
    occu         = 16    (0x00000010)
    access       = 1     (ItAccessStandard)
    idxKind      = 1     (ItIndexLinear)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 8     (cmpManyEq)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 1
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x07000000A0262CF0
    pgHook       = 0x07000000A0258600
    idxPtr       = 0x07000000A0259788
    shmTabhSet   = 0x0000000000000000
    id           = 93    (0x0000005D)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 32    (0x00000020)
    lineAlloc    = 32    (0x00000020)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x00000001)
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    collHook     = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    I_LOGID
    4C7HSJQKN58AR2DG5NSOGNB5O
    3434545443345344345444434
    43783A1BE58122475E3F7E25F
    I_T_VARIABLES
    Table[initial]
    I_SYNCHRONOUS
    2
    0
    I_SIMULATE
    2
    0
    I_REPAIR
    222222222222222222222222222222
    000000000000000000000000000000
    I_BATCHID
    222222222222222222222222222222
    000000000000000000000000000000
    E_INSTANCE
    ODSA_4C7HUKHW8WV06KLJFFYZP95BW
    445453434544535533444445553345
    F431F43785B8787606BCA669A09527
    E_STATE
    2
    0
    E_EVENTNO
    00
    33
    00
    E_HOLD
    2
    0
    SY-REPID
    CL_RSSM_ODSACTIVATE===========CP
    4455554544544545454333333333334522222222
    3CF233DFF4313496145DDDDDDDDDDD3000000000
    <%_L003>-RNR
    L_T_REQUESTS
    Table[initial]
    L_S_REQUESTS
    222222222222222222222222222222
    000000000000000000000000000000
    SY-SUBRC
    0
    0000
    0000
    SYST-REPID
    CL_RSSM_ODSACTIVATE===========CP
    4455554544544545454333333333334522222222
    3CF233DFF4313496145DDDDDDDDDDD3000000000
    ICON_GREEN_LIGHT
    @08@
    4334
    0080
    L_JOBNAME
    BI_PROCESS_ODSACTIVAT
    44555444555445445454522222222222
    29F02F3533FF43134961400000000000
    L_S_SELE-NO_CONDENSE
    2
    0
    L_S_ODS-OBJECT
    OD13ITM3
    443345432222222222222222222222
    F41394D30000000000000000000000
    L_S_SELE-ODSACTSERIAL
    2
    0
    L_ERROR_PROC
    2
    0
    L_T_MSG_PROC
    Table IT_18345[3x704]
    L_T_MSG
    Table[initial]
    No.       1 Ty.          EVENT
    Name  START-OF-SELECTION
    G_VARIANT
    OD13ITM3_ACTIVATE
    443345435445454542222222222222
    F41394D3F134961450000000000000
    G_TYPE
    ODSACTIVAT
    4454454545
    F431349614
    %_DUMMY$$
    2222
    0000
    %_ARCHIVE
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    G_OBJECT
    CL_RSSM_ODSACTIVATE
    445555454454454545422222222222
    3CF233DFF431349614500000000000
    G_INSTANCE
    222222222222222222222222222222
    000000000000000000000000000000
    SY
    #######################################################A#######ÿ###############(##############
    000000000000000000000000000000000000000000000000000000040000000F000000000000000200000000000000
    000000000000000100000000000000000000000000000000000100010001000F000000000000000800000000000000
    %_SPACE
    2
    0
    %_REPAIR_%_APP_%
    222222222222222222222222222222
    000000000000000000000000000000
    G_STATE
    2
    0
    G_EVENTID
    RSPROCESS
    55554445522222222222222222222222
    2302F353300000000000000000000000
    G_HOLD
    2
    0
    G_EVENTPARM
    4BO77YTX6F8UVLQ22AEHHYIPO
    3443355534355453344445454222222222222222222222222222222222222222
    42F7794866856C1221588990F000000000000000000000000000000000000000
    G_JOBCOUNT
    03030600
    33333333
    03030600
    G_BATCHDATE
    20081218
    33333333
    20081218
    G_EVENTNO
    00
    33
    00
    G_BATCHTIME
    030306
    333333
    030306
    G_T_VARIABLES
    Table[initial]
    G_T_PROCESSLIST
    Table IT_123[18x528]
    %F007017_1000
    Log ID (Internal Use Only)
    46624422467676662576246672222222222222222222222222222222222222222222222222222222222
    CF7094089E452E1C05350FEC99000000000000000000000000000000000000000000000000000000000
    G_LOGID
    4C7HSJQKN58AR2DG5NSOGNB5O
    3434545443345344345444434
    43783A1BE58122475E3F7E25F
    G_CHAIN
    ZLIS_13_VDITM
    5445533554454222222222222
    AC93F13F6494D000000000000
    G_REPAIR
    222222222222222222222222222222
    000000000000000000000000000000
    G_BATCHID
    INFO_4C7HUKA7PY9ANY239LWNF76M4
    444453434544355344533345443343
    9E6FF43785B170991E9239C7E676D4
    Internal notes
    The termination was triggered in function "raiseExcp"
    of the SAP kernel, in line 2099 of the module
    "//bas/700_REL/src/krn/runt/abexcp.c#7".
    The internal operation just processed is "EXCP".
    Internal mode was started at 20081219030246.
    Active Calls in SAP Kernel
    Lines of C Stack in Kernel (Structure Differs on Each Platform)
    => 64 bit R/3 Kernel
    => 64 bit AIX Kernel
    => Heap limit      = unlimited
    => Stack limit     = unlimited
    => Core limit      = 1073741312
    => File size limit = unlimited
    => Heap address  = 0x1154fc6a0
    => Stack address = 0xfffffffffffb080
    => Stack low     =  0xfffffffffffb080
    => Stack high    =  0xffffffffffff880
    => Stack Trace:
         AixStack() at 0x1000a2474
         CTrcStack2() at 0x1000a256c
         rabax_CStackSave__Fv() at 0x1000d0e3c
         ab_rabax() at 0x1000cd81c
         raiseExcp__F6HeadId() at 0x100429ba0
         ab_jexcp__Fv() at 0x100428d30
         ab_extri__Fv() at 0x10038e6dc
         ab_xevent__FPCc() at 0x100ab5cc4
         ab_trigg__Fv() at 0x100ab59b0
         ab_run() at 0x1014d42dc
         N_ab_run() at 0x100ed3f4c
         dynpmcal() at 0x100ed2d40

    HI karthik..
    The Error Msg is due to insufficient memory while storing the Data in Database(i,e ODS) and this error UNCAUGH EXCEPTION will come due to " like there is an exception raised but no code to catch it(to activate the ODS)".
    so chk the problem with the Basis People... those guys can give clear info pertaining to this kind of  problems...
    Genereally in our case we raise ticket to Basis people..
    hope useful....
    cheers
    Sukhai..

  • ABAP/4 processor: TSV_TNEW_PAGE_ALLOC_FAILED

    Hi,
    Please help me. I'm having ABAP/4 processor: TSV_TNEW_PAGE_ALLOC_FAILED job cancelled for my payment run F110.
    Before this we having performance issue for the payment run F110. We implemented notes (SNOTE 1343823) to solve the performance issue. And today when we wanted to do payment run some of the payment run is automatically cancelled by system.
    Tq

    hi,
    Try this Note 1250607 - Long runtime and high memory reqmt for payment program
    thanks and regards
    Praveen.J

  • Message-ABAP/4 processor: DYNPRO_SEND_IN_BACKGROUND in BDC

    Hi all,
    BDC is written for MM02 and when execcuted from z report the inspection data bdc (mm02) BDC is getting executed successfully.
    Later a badi is written to block mm02 from command prompt but allow from called programs(call transaction) in BADI
    MATN1_OUTPUT_001 implmentation of BADI-MATN1.
    DATA: it_zemail_mdm TYPE STANDARD TABLE OF zemail_mdm,
             wa_zemail_mdm TYPE zemail_mdm.
      DATA: v_x1,v_c,v_x.
      IF sy-tcode = 'MM06' OR sy-tcode = 'MM02' OR sy-tcode = 'MM01'
      OR sy-tcode = 'MMAM' OR sy-tcode = 'CL20N' OR sy-tcode = 'C223'
      OR sy-tcode = 'MM17'.
        CONSTANTS : c_msg1(45) TYPE c VALUE 'You are not authorised for this transaction.'.
        DATA: c_err TYPE c VALUE 'S'.
        IF ( ( sy-uname NE 'MDCC'  ) AND ( sy-uname NE 'MDT_01'  ) AND ( sy-uname NE '150891' ) AND ( sy-uname NE 'DESIGN' ) ).
          IF syst-calld  = ''.
            MESSAGE c_msg1 TYPE c_err.
            LEAVE TO SCREEN 0.
          ENDIF.
        ENDIF.
      ENDIF.
    But now when i execute BDC i get following  message-
    Message-ABAP/4 processor: DYNPRO_SEND_IN_BACKGROUND
    Th message is success meassage but data is not getting created in database now.
    Please guide to resolve the issue.
    Thnaks.
    Edited by: sanjivrd on Dec 12, 2009 12:36 PM

    Hi sanjivrd,
    in Batch-Input, just leave the BADI, put this at begin of BADI methold:
    IF SY-BINPT IS NOT IITIAL.
      RETURN.
    ENDIF.
    Regards,
    Clemens

  • ABAP/4 processor: OBJECTS_OBJREF_NOT_ASSIGNED

    DEar All,
    I m getting abap dump in Solution manager and background job Job 'Landscape Fetch' is getting cancelled. In error log i m getting
    07.06.2010 00:36:32 ABAP/4 processor: OBJECTS_OBJREF_NOT_ASSIGNED
    07.06.2010 00:36:32 Job cancelled
    ON checking abap dump i m getting error with detail :-
    Runtime Errors         OBJECTS_OBJREF_NOT_ASSIGNED
    Exception              CX_SY_REF_IS_INITIAL
    Date and Time          07.06.2010 13:00:37
    Short text                                                                               
    Access via 'NULL' object reference not possible.
    Error in the ABAP Application Program
    The current ABAP program "SAPLSMSY_ACTUALIZE_DATA" had to be terminated because
    come across a statement that unfortunately cannot be executed.
    What happened?
    Error analysis
    Error analysis                                                                               
    An exception occurred that is explained in detail below.                                     
        The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not                    
         caught in                                                                               
    procedure "SMSYAD_GET_DATA_FROM_LCR" "(FUNCTION)", nor was it propagated by a                
        RAISING clause.                                                                               
    Since the caller of the procedure could not have anticipated that the                        
        exception would occur, the current program is terminated.                                    
        The reason for the exception is:                                                             
        You attempted to use a 'NULL' object reference (points to 'nothing')                         
        access a component (variable: "ACCESSOR").                                                   
        An object reference must point to an object (an instance of a class)                         
        before it can be used to access components.                                                  
        Either the reference was never set or it was set to 'NULL' using the                         
        CLEAR statement.   
    Kindly suggest me how to resolve this isuue.
    Regards
    Adil

    Hi Paul / Raguram,
    Thnx for your reply.Curent SP Level of solman
    SAP_ABA    700                      0016    SAPKA70016   Cross-Application Component
    SAP_BASIS  700                     0016    SAPKB70016   SAP Basis Component
    PI_BASIS   2005_1_700          0018    SAPKIPYJ7I   PI_BASIS 2005_1_700
    ST-PI      2008_1_700 0000
    SAP_BW     700                      0017    SAPKW70017   SAP NetWeaver BI 7.0
    SAP_AP     700          0011    SAPKNA7011   SAP Application Platform
    BBPCRM     500                       0012    SAPKU50012   BBPDRM
    when i run SLDCHECK T-code all are in red.
    RFC destination SAPSLDAPI does not exist
    Create the RFC destination by using transaction SM59!
    Summary: Connection to SLD does not work
    Check SLD function and configurations
    Now checking access to the XI Profile
    FC destination LCRSAPRFC does not exist
    Create the RFC destination by using transaction SM59!
    Please tell note number me  hoe to create SLD ?
    Regards
    AShok

  • Info spoke error : ABAP/4 processor: DATASET_NOT_OPEN

    HI all,
    We have Infospoke with
    Data source: 0MATERIAL and
    Destination : BW_MAT
    In process chain after this infospoke is filled we have ABAP Program
    to Transfer Material Data.
    In process chian the load is successfull till infospoke but failed at the ABAP Program with error
    Error Mesg : ABAP/4 processor: DATASET_NOT_OPEN
    Job shows cancelled in Batch monitor.
    HOw to sole this problem ? I can learn more from your responses.

    I think there is some problem with your ABAP program.
    Have you used OPEN DATASET statement, if so check if you have mentioned file path etc correctly.
    Can you try debugging the code.
    Hope this helps.

  • ABAP/4 processor: DBIF_DSQL2_SQL_ERROR

    Hi All,
    I get an error when running a Job for deactivating aggregates (Program:-SAP_AGGREGATES_DEACTIVATE)
    Error:-- ABAP/4 processor: DBIF_DSQL2_SQL_ERROR
    This deactivation job fails on some occasion with this error and other time it is executed successfully.
    Can anyone give me the reason for this error
    Thanking You
    Sandeep

    Hi All,
    I get an error when running a Job for deactivating aggregates (Program:-SAP_AGGREGATES_DEACTIVATE)
    Error:-- ABAP/4 processor: DBIF_DSQL2_SQL_ERROR
    This deactivation job fails on some occasion with this error and other time it is executed successfully.
    Can anyone give me the reason for this error
    Thanking You
    Sandeep

Maybe you are looking for

  • Install Oracel 9.2.0.1 Client on Win XP Pro SP 2, Pentium 4 machine

    Hello, Please help me solve problem in installing Oracel client. I install Oracel 9.2.0.1 client on PC has following configure: Win XP Profesional SP 2 Intel Pentium 4 RAM 256 KB Disk space >10 GB At step : choose Install Type: Administrator, Runtime

  • Java.lang.NullPointerException while creating virtual classroom via Adobe Connect 9 Web Services

    Hello all, I am trying to create a virtual classroom via Adobe Connect 9 Web Services with the code below. https://XXXXXXXX.adobeconnect.com/api/xml?action=sco-update&type=virtual-classroom&name=My Virtual Classroom&folder-id=1358451232&date-begin=20

  • D800 tethered in LR 4.3 - .nef vs .NEF

    Hello, I have been shooting nikon for a few bodies now and my library consists of .NEF files. I have recently upgraded to the d800 and I have began experimenting with tethered shooting. It seems that while doing this the RAW files get written out wit

  • Backing up

    Hi, I do a lot of graphic project work and as a result have many psd and jpegs on my mac. I really need to back the files up regularly as recently i suffered a corruption and lost a lot of work (corruption when working with a windows OS pc) I also ha

  • Texts in F.14 & F110

    Hi All, We have one best retail company and user to pay rent through F.14 (Recurring) & Also make payments through F110. Now business requirements as follows. While execute the F.14 system automatically pick the text & update in all recurring invoice