ABAP/4 processor:DBIF_RSQL_SQL_ERROR receives after saving an article MM42
Hi,
We are getting "Express document "Update was terminated" received from author "XXXX" error while saving an article using MM42. We executed listing in "Listing" view in MM42 and saved the article.
Then the error "Express document" comes
The error message in the "express document " is given below:-
Update was terminated
Error info... 00 671: ABAP/4 processor: DBIF_RSQL_SQL_ERROR
Exception :-CX_SY_OPEN_SQL_DB
Thanks in advance
Hi,
See in transaction SM13
Normally you foind your update task and you can repeat it in foreground debug mode
Rgds
Similar Messages
-
ABAP/4 processor: DBIF_RSQL_SQL_ERROR
We are running the below on an AS/400 model 840 with v5r2:
Module Version Patch Service Pack
SAP_BASIS 620 54 SAPKB62054
SAP_ABA 620 54 SAPKB62054
SAP_BW 30B 25 SAPKW30B25
PI_BASIS 2003_1_6201 7 SAPKIPYH57
When activating standard content ODS (0SD_O01, 0SD_O02, and 0SD_O03) and 1 custom ODS (ZSD_O01) we receive the above error. Everything shows that the extract was loaded correctly and their is a PSA request id; however, the lights are red.
You can't change the the status to green. The display messages for loading the extract indicate that everything went well. You can't delete the request.
The extracts that can't be activated in the ODS (2LIS_11-VAHDR, 2LIS_11-VAITM, and 2LIS_11_VASTH) are activated in the infocubes where they are used.
I have sent a note to SAP for assistance and it has bounced around and is now in the hands of the BC-DB-DB4 team.
Does anyone have any idea as to what is going on?
Thanks,
Bill CooperLooking at SM50 didn't provide any information. SM21 echos what is in the ABAP dump.
The error occurs at
001260 * check previous operations in odsobject for all requests
> SELECT *
001280 INTO TABLE l_t_reqstate
001290 FROM rsodsactreq
001300 FOR ALL ENTRIES IN i_t_actreq
001310 WHERE
001320 odsobject = i_odsobject
001330 AND request = i_t_actreq-request
001340 AND operation <> rsdro_c_operation-activate
001350 AND status <> rsdro_c_reqstate-finished.
The data in table RSODSACTREQ has errors in it. There are datapakid type 1 and type 0 records for the same request. It seems that there should only be type 0 records for a successful activation. The type 0 record exists but the not all of the required data is there.
In table RSREQICODS there are type "I" records for the request but no type "C" records for the ODSR. If the missing records are added and missing data values added to RSODSACTREQ, the status lights turn green, everything looks correct in RSA1 but you can't delete the request nor can you access the data via a query.
Any ideas?
Bill -
Hi Gurus ,
I am creating material with class and characters. class type is 001
While creating material through MM01, in classification view I am giving class and after that characteristics value of that class and after that material is saved but system is not taking the characteristic value and message is coming as --u201CExpress document "Update was terminated" received from author u2026.u201D
In SAP inbox message is coming as -- u201CError Info... 00 671: ABAP/4 processor: DBIF_RSQL_SQL_ERRORu201D
And in SM14 error message is--u201CCLVF_VB_INSERT_CLASSIFICATIONu201D
Function Module CLVF_VB_INSERT_CLASSIFICATION
Status Update was terminated
Report LCLVFF40
Row 124
Error details Class: 00 Number: 671
00 671: ABAP/4 processor: DBIF_RSQL_SQL_ERROR
Same type of error is coming while adding characteristics value for release strategy class type
032 following error is coming for that.
Function Module CLVF_VB_INSERT_CLASSIFICATION
Status Update was terminated
Report LCLVFF40
Row 85
Error details Class: 00 Number: 671
00 671: ABAP/4 processor: DBIF_RSQL_SQL_ERROR
Please replyClose
-
Hi,
I am getting Message having CALL_FUNCTION_NOT_FOUND after saving my document in ME22N Tcode.
Message i am getting in my inbox:
Transaction.. ME22N
Update key... 80234FDE6D51F11C9004001A6435E8C6
Generated.... 02.06.2009, 05:15:29
Completed.... 02.06.2009, 05:15:31
Error Info... 00 671: ABAP/4 processor: CALL_FUNCTION_NOT_FOUND
Can any one please tell what will be the problem?
My out type also configured correctly with function module routine and program name.
Please reply.
Regards,
Kusuma.Hi Karthik,
Thank you for ur reply.
I did not implement any user exit/ badi. Dump is saying that my smarform function module does not exist in the se37 library.
I have excuted my form through se38, that time is working fine. When i tried through output type it is going to dump.
Regards,
Kusuma. -
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 PMThe 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.
-
Hi
While uploading duty rate files provided by the data provider customs info ,at the time of saving , its throwing the below error .
00 671: ABAP/4 processor: SAPSQL_ARRAY_INSERT_DUPREC .
There is no duplicate data in the XML file and data provider has also confirmed the same. Let me know if anybody has come across the same issue .
Thanks in advance.
Regards,
VaniHi Jasmit
Yes , as you have mentioned ,
After HTS data upload for 2012 through XML file ,system had 2 validity periods 2012-01-01 9999-12-30 and 2012-01-01 2012-12-31 . Hence now there is a issue of duplicate record ,since both periods are valid .
But the data provider customs info has confirmed they have sent only one record with validity period 2012-01-01 2012-12-31 .in the XML file .
How the record with validity period 2012-01-01 9999-12-30 is now there in the system
Is there a chance that the XML upload pgm in our system has generated this record ? How the upload pgm works ?
Regards,
Vanathi -
Error after saving co11n document
Hi
While Entering Confirmation of Production order using tcode CO11N, at the time of saving, it showing the message ( Confirmation Saved (Goods movement 2, Failed 0) )
afterwards showing below message
Express Document u201CUpdate was terminatedu201D received from author u201DUserNameu201D
Message detail in INBOX
Update was terminated
System ID.... PRD
Client....... 444
User..... CEO
Transaction.. CO11N
Update key... 51817DDDDE72F1F09150001A64484A38
Generated.... 08.09.2008, 14:07:45
Completed.... 08.09.2008, 14:07:45
Error Info... F1 109: Line item 001
============----
Here we are started to capture Personnel ID
Pls. help in this.
PrakashHi Prakash,
As per your error message the problem is the document updation is not happening in the system according to your data, you tell ABAP or Basis people they will help you in that it may realeted to technical or configuration.The technical people can tell what is excatly happening.
Please change the number range define for confirmation then try again.
Please check T. Code SM21, SM22 and SM13
Check the link below:
Re: Me21n after saving Update Terminate Error Coming
Check the 'Update debuggiing ' option from menu
Regards,
R.Brahmankar -
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
kunalwe 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 -
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 0x100ed2d40HI 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.. -
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 PMDear 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. -
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 reddiHi
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 -
Signature Scribble field not retaining image file after saving
I have 2 issues with my PDF dynamic file I sent out
1) The add/remove controls is adding a random amount of extra blank rows upon saving the PDF
2) The image files selected for the Signature Scribble field is not retaining the image file after saving. It also doesn't give an opportunity to actually draw in a signature.
I even tried to use the Subform Instance Controls Insert/Remove/Move in my table, but I keep receiving the error "You have reached the maximum number of items allowed"
I would appreciate any help you can give me! I have been farting around with this for too long.
Thanks!
RhondaThanks Pat. Tried each, restarted computer each time; tried the "Accept" routine several days ago - it worked briefly and then stopped. Uninstalled Reader and Flash as well. Strange thing with Flash, one of my online broker programs provides streaming of CNBC. When I clicked on the CNBC option to initiate CNBC, I got a message saying that I needed to load Flash. I did, and it loaded again with no mention of Flash having already been installed.
Using Internet Explorer works, as well as, clicking on the .pdf file within Windows Explorer (WE). Expanding the window in WE makes it large enough to read. I would still like to find a way to open the files as they are designed to open.
I have done all of the Adobe updates as they have been presented. Microsoft updates load automatically, and restart my computer in the process. I do not look to see what the updates have been. I figure if there was not a need, Microsoft would not make the updates.
[private data removed] -
Invoice outputs are not printing after saving the document..!
Invoice outputs are not printing after saving the document. Eventhough we maintain all condition records not only that Processing log also it showed that it has been processed on some date. but customer not received the printout
AmarhI,
GO TO IMG, SD, BF, OUTPUT CONTROL, OUTPUT TYPES, SELECT UR OUTPUT TYPE, GO TO DETAILS ICON AND ASSIGN THE VALUE "ISSUE OUTPUT IMMEDIATELY SAVING THE APPLICATION" FROM DROP DOWN DOWN LIST IN THE DEFAULT VALUES
AND ASSIGN THE RELEVENT PRINTER TO USER ID IN SU01 AND IN CONDITION RECORDS
REGARDS,
SK
Edited by: Sadanandam Kasarla on Mar 16, 2009 12:07 PM
Edited by: Sadanandam Kasarla on Mar 16, 2009 12:08 PM
Edited by: Sadanandam Kasarla on Mar 16, 2009 12:10 PM -
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 cancelledSee the dump in ST22 for details.
Maybe you are looking for
-
Printer Problem In Oracle Forms And Reports server
Hi, I am facing a problem regarding installation of printer drivers in my Reports Server (10.1.2.0.2 on Windows 2003). Unless the printer driver is installed locally on the Report Server Reports are not printing. The problem is with the USB printers
-
Custom XSLT Functions Throw Exception
Hi, I have following requirement- 1. I have defined and configured some custom XSLT functions in Jdev and BPEL, which throw exception in case of an error. 2. Now I want to catch that exception in my BPEL process 3. In My BPEL process I have defined t
-
Hi all, I am not able to see the Excise details in My GR in MIGO transaction. Kindly explain me how the value of BED, SED etc flows to the GR document in SAP . That is exactly where should i check so that values of excise duties will flow to the MIGO
-
I usually had a homepage with the firefox banner at the top. This provided printer access, google, file, etc.. I cannot navigate out of my home page since this info is no longer at the top.
-
Most popular iPhone to stereo speaker systems adapter/interface
new to iPhone and I wonder what folks say about interfaces to use the iPhone for home audio and possibly video