ABAP/4 processor: POSTING_ILLEGAL_STATEMENT in WSM3

hi all,
i am getting dump while doing listing in WSM3 stating 'Update was terminated '.
the detailed message is as follows:
Transaction..   WSM3
Update key...   4BCEF56BE790016000000000C0A80054
Generated....   22.04.2010, 08:12:55
Completed....   22.04.2010, 08:14:04
Error Info...   00 671: ABAP/4 processor: POSTING_ILLEGAL_STATEMENT
i searched for SAP notes also but unable to find one.
Regards
Sunil

Hi Oilivia,
I have the same issue while using SO_DOCUMENT_REPOSITORY_MANAGER Function Module.
And I implemented the Note 1023041 as per your suggestion.
I'm still getting the same Update Termination 'POSTING_ILLEGAL_STATEMENT'.
(Invoice Emailing)
Any other suggestions?
Thanks,
Sowmya

Similar Messages

Error : 00 671: ABAP/4 processor: POSTING_ILLEGAL_STATEMENT

hi all
i am getting update termination while saving PO
when i goto SM13 an dble click on error get following
1 ME_CREATE_DOCUMENT             V1                   Initial
2 EINKBELEG_WRITE_DOCUMENT       V1                   Initial
3 MCE_STATISTICS_UPD_V1          V1                   Initial
4 MCE_STATISTICS_UPD_V2          V2                   Initial
5 ME_CREATE_MRPRECORD_PO         V1                   Initial
6 ME_UPDATE_QUOTA_DIALOG         V1                   Initial
7 RV_MESSAGE_UPDATE              V1                   Error
after clicking the 7 item getting following
Function Module        RV_MESSAGE_UPDATE
Status                 Update was terminated
Report                 LSYDBU27
Row                    7
Error details   Class:     00         Number:    671
00 671: ABAP/4 processor: POSTING_ILLEGAL_STATEMENT
plz help me out
regards
kunal

we just deleted and created the conditon records for printing in NACE for neu and then DB02 updated
Edited by: SAP Learner on Dec 22, 2009 1:20 PM

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

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 : ASSIGN_TYPE_CONFLICT

I am recieveing this error message ABAP/4 processor : ASSIGN_TYPE_CONFLICT when i ran a DTP from a flat file datasource
to the data source object (DSO) Can someone help me ?? please...

Hi,
if you have written some own code in transformation please make sure that you are using fields witch have the same data type...
ASSIGN_TYPE_CONFLICT
DTP -ASSIGN_TYPE_CONFLICT
DTP failure
Regards
Andreas

Error Info... 00 671: ABAP/4 processor: SAPSQL_ARRAY_INSERT_DUPREC

Dear experts,
     I got an error while creating a process order.System allowing to create a process order after saving througing an error
   " Express document "Update was terminated" received from author "GLP Developer"
*'Error Info...   00 671: ABAP/4 processor: SAPSQL_ARRAY_INSERT_DUPREC".*
    I did changed the number ranges for a particular order type.Created one order and prcessed.But again getting the same error while processing second order.
Thanks in advance,
Rambabu.K.
Edited by: RamPPQMPM on Nov 24, 2010 6:49 PM

The system is telling you that you have a duplicated key (record) in a table. You have to take a look into the userexits or enhancements applyied to your transactios in ordert to find a bad modifying of an stardard structure.

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: SAPSQL_ARRAY_INSERT_DUPREC on creation of a Purchase Req

Hi Gurus,
we are encountering an situation whereby, when a user creates and saves a PReq, the Preq number is displayed at the bottom, yet a termination message appears : '' ABAP/4 processor: SAPSQL_ARRAY_INSERT_DUPREC ''
have checked the number range and it doesnt seem to be that. May you please help
Regards
Nsovo

Hello Mahee
Normally there are two reasons for short dump SAPSQL_ARRAY_INSERT_DUPREC
1, commit work in user exit;
2. inconsistancy between the last number in the table and the current number in the number range;
please check the short dump happens where inserts entry in table XXXX. check the lastest number in this table and compare it with the current number in number range object. In this case, the current number in number range is no larger than the lastest number in DB.
The solution would be to manually adjust the current number in the number range object in SNRO.
I hope the information is helpful.
Regards,
Jane

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

Background jobs failing with ABAP/4 processor: RFC_CONVERSION_FIELD

Hi Guru's,
Below are the backgroud jobs failing with runtime Error " ABAP/4 processor: RFC_CONVERSION_FIELD" in solution manager system (solution manager 3.0,SR2). Not sure why all these jobs failing with this dump on of sudden. i haven't made any changes to the system in the recent past.
BTC_CMS_COLLECTOR
SAP_APPLICATION_STAT_COLLECTOR
SESS_Y000001806_COLL_TRANS
ABAp Dump says that
Conversion error between two character sets
What happened?
Conversion error "ab_rfccon" from character set 4103 to character set 1100.
When executing a remote function call a conversion error occurred. This
occurred when receiving or sending the data. The conversion error can
only appear, when the data is transferred from a Unicode system to a
non-Unicode system.
Could some one please share some information if any one experienced the issue. Please note that all of our ECC systems are uni-code systems.
Thanks & Regards,
Vinod.

Hi Vinod
Just try to understand the purpose of these jobs and may be these Notes will help you
Note 814707 - Troubleshooting for RFC connections Unicode/non-Unicode
Note 647495 - RFC for Unicode ./. non-Unicode Connections
Note 1361970 - Conversion problems during RFC communication

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

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.

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: POSTING_ILLEGAL_STATEMENT in WSM3

Similar Messages

Maybe you are looking for