Runtime Errors Raise Exception in Solution Manager

Hi Guru's,
While I try to excute the transaction solman_issue_mgnt in solution manager for issue tracking, runtime errors occurs.
Error analysis
    A RAISE statement in the program "CL_GUI_HTML_VIEWER============CP" raised the
     exception
    condition "CNHT_ERROR_PARAMETER".
    Since the exception was not intercepted by a superior
    program, processing was terminated.
Could anyone suggest me on this issue.
regards,
Guna

Hi Juan,
As per the note, everything was fine there. We have SAP_Basis 700 with SP16.
Earlier it was worked fine. Now only we are facing this issue while excuting the t-code solman_issue_mgmt.
regards,
Guna

Similar Messages

Dump (Raise exception) in Solution Manager

Hi experts ,
We are getting dumps from Satellite system into the Solution manager system. And the user respossible for the dump
is ALERT_<SID of Satellite System>. All the RFC have been checked . Central Auto reaction methods are assigned from
Solution manager to Satellite system. And checked that Auto reaction methods are not responsible for dump
SOLMAN_CEN_ALERT Destination is also checked in Satellite system.
Please assist
DUMP Details :
A RAISE statement in the program "CL_ABAP_TYPEDESCR=============CP" raised the
| exception
| condition "TYPE_NOT_FOUND".
| Since the exception was not intercepted by a superior
| program, processing was terminated.
User and Transaction
| Client.............. 100
| User................ "ALERT_SID"
| Language Key........ "E"
| Transaction......... " "
| Transactions ID..... "XXXXXXXXXXXXXXXXXXXXXXX"
| Program............. "CL_ABAP_TYPEDESCR=============CP"
| Screen.............. "SAPMSSY1 3004"
| ScreenLine.........2
| Information on caller of Remote Function Call (RFC):
| System.............. "SID"
| Database Release.... 700
| Kernel Release...... 700
| Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
| Call Type........... "synchron and transactional (emode 0, imode 0)"
| Inbound TID.........." "
| Inbound Queue Name..." "
| Outbound TID........." "
| Outbound Queue Name.." "
| Client.............. 100
| User................ "WF-BATCH"
| Transaction......... " "
| Call Program........."SAPLSALRT_CREATE_LOCAL"
| Function Module..... "SALERT_CREATE"
| Call Destination.... "SOLMAN_CEN_ALERT"
| Source Server....... "Satellite System hostname"
| Source IP Address... "XX.XX.XX.XX"
Source Code Extract
|Line |SourceCde
| 53| read table admin_tab from admin_tab_line into admin_tab_line.
| 54| if sy-subrc = 0.
| 55| p_descr_ref ?= admin_tab_line-ref->get( ).
| 56| if p_descr_ref is bound.
| 57| return.
| 58| endif.
| 59| delete table admin_tab from admin_tab_line.
| 60| endif.
| 61|* create new descr object
| 62| case admin_tab_line-kind.
| 63| when kind_elem.
| 64| raise event create_elemdescr
| 65| exporting xtype = admin_tab_line-xtype.
| 66| when kind_ref.
| 67| raise event create_refdescr
| 68| exporting xtype = admin_tab_line-xtype.
| 69| when kind_struct.
| 70| raise event create_structdescr
| 71| exporting xtype = admin_tab_line-xtype.
| 72| when kind_table.
| 73| raise event create_tabledescr
| 74| exporting xtype = admin_tab_line-xtype.
| 75| when kind_class.
| 76| raise event create_classdescr
| 77| exporting xtype = admin_tab_line-xtype.
| 78| when kind_intf.
| 79| raise event create_intfdescr
| 80| exporting xtype = admin_tab_line-xtype.
| 81| when others.
| 82|* all others are erros
|>>>>>| raise type_not_found.
| 84| endcase.
| 85| endcase.
86
| 87| create object admin_tab_line-ref exporting oref = returning_ref.
| 88| insert admin_tab_line into table admin_tab.
| 89| p_descr_ref = returning_ref.
| 90| clear returning_ref.
91
| 92|endmethod.
Kamal

Hi Kamal,
I recommend to open a ticket for SAP with the runtime error attached.
Best regards,
Andreas

Runtime Errors SYNTAX_ERROR in SAP Solution Manager 4.0

Hi every body,
     After in install of support packages SAP_BASIS SAP_ABA and ST. When I logon in the SAPGui I received this error:
Runtime Errors         SYNTAX_ERROR
Short text
    Syntax error in program "SAPLSCP2 ".
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLOLEA" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program "SAPLSCP2 " in include "LSCP2U09
     " in
    line 66:
    "The field "ZCSA_SYSTEM_LANGUAGE" is unknown, but there is a field with"
    " the similar name "ZCSA_INSTALLED_LANGUAGES". "ZCSA_INSTALLED_LANGUAGE"
    "S"."
    The include has been created and last changed by:
    Created by: "SAP "
    Last changed by: "SAP "
Error analysis
    The following syntax error was found in the program SAPLSCP2 :
    "The field "ZCSA_SYSTEM_LANGUAGE" is unknown, but there is a field with"
    " the similar name "ZCSA_INSTALLED_LANGUAGES". "ZCSA_INSTALLED_LANGUAGE"
    "S"."
Trigger Location of Runtime Error
    Program                                 SAPLOLEA
    Include                                 LOLEAU13
    Row                                     71
    Module type                             (FUNCTION)
    Module Name                             AC_CALL_METHOD
Please help me
Regards.

Hi,
Have upgrade kernel?
Regards
Ben

Runtime error Raise Exception Initial Product Catalog Replication

Dear All,
We are on CRM ISA MSA 5.0 SP8 & Trex 7 SP 30. Ours is a 3 system landscape. CRM Dev, Q, & P. Recently we added a new system in the landscape for Intergration Testing purpose. and its called as CRI which is a copy of the production Crm box.
I did all the post installation activitiese and did all Connections (sm59, srmo) between Trex and CRM. After the connection was made, the RFC, SSR are all working fine.
I did the settings in spro for the product catalog replication, created the ssr and then did a initial replication without document and it worked fine. I then did a replication with documents, I am getting a runtime error, RAISE_EXCEPTION. All the connections between the crm and trex box are working fine. everything is pinging, the FTP user has all the access on the IMS_DOCS_A5C folder.
Can someone please let me know what the issue could be?
Awaiting a postive response.
Thanks in advance.
Warm Regards,
Rajeet Mathur

Hi Rajeet,
The intitial replication transports product catalog data (for example, product items or text) to the index server. You can replicate all or individual product catalog variants. The replicated product catalog contents are transferred from the index server to the Web server. The product catalog contents are then available in the E-Commerce application. Multimedia objects are transferred from the product catalog to the Knowledge Provider Content Server and are subsequently published on the Web server.
As you said that after you put in the documents the repliaction gives a runitme error, I beleive the replication to the contect server is giving problems.
1. Have you created templates for folder and assigned them to the catalog types for the attachement of documents.
2. While replication are you specifying the Publishing computer ID with the checkbox transfer Document content ticked.
Check in these details.
Regards,
Shalini Chauhan

Runtime error RAISE_EXCEPTION Exception condition "METADATA_MISSING" raised

Hi All,
I am facing a runtime error, while using transaction DSWP --> Set-up System Monitoring --> Copy Customizing -->
At that time we are getting "Runtime error RAISE_EXCEPTION Exception condition "METADATA_MISSING" raised
===========================================
Runtime Errors RAISE_EXCEPTION
Date and Time 25.07.2008 08:31:11
Short text
Exception condition "METADATA_MISSING" raised.
What happened?
The current ABAP/4 program encountered an unexpected
situation.
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
A RAISE statement in the program "SAPLDSVAS_SERV" raised the exception
condition "METADATA_MISSING".
Since the exception was not intercepted by a superior
program, processing was terminated.
Short description of exception condition:
For detailed documentation of the exception condition, use
Transaction SE37 (Function Library). You can take the called
function module from the display of active calls.
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:
"RAISE_EXCEPTION" " "
"SAPLDSVAS_SERV" or "LDSVAS_SERVC7I"
"MAP_DSVAS_TT_DATA_TO_TT_25"
or
"SAPLDSVAS_SERV" "METADATA_MISSING"
or
"RDSMOP_MAIN " "METADATA_MISSING"
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... "terra"
Network address...... "172.16.1.198"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "4x Intel 801586"
Character length.... 16 Bits
Pointer length....... 32 Bits
Work process number.. 2
Shortdump setting.... "full"
Database server... "TERRA"
Database type..... "ORACLE"
Database name..... "DSM"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Oct 23 2007 01:07:18"
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. 133
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.... 8176
EM...... 37628064
Heap.... 0
Page.... 65536
MM Used. 31785376
| MM Free. 1656912
=============================================
Configuration:
OS :Windows 2003 server.
Solution Manager 7.0 SP15
Oracle 10.2
RAM - 2 GB
Its bit urgent, Please help out us.
Thanks in advance.
Best Regards,
Pratyusha

Hi
Check the SP level for ABAP and Basis. Download the latest SP level from SWDC and apply it on the system
This error is related to ABAP program.
Currently the latest available patch level is 16. Please download both ABAP and BASIS SP 16 and apply them on the system.

In SCM 5.0 Runtime Errors: DBIF_DSQL2_SQL_ERROR Exception: CX_SY_NATIVE_SQ

Hi,
I am getting following shortdump in my SCM 5.0 system with LiveCache 7.6.03 on AIX 5.3.
Please help me.
Runtime Errors DBIF_DSQL2_SQL_ERROR
Exception CX_SY_NATIVE_SQL_ERROR
Date and Time 01.07.2008 09:20:09
Short text
An SQL error occurred when executing Native SQL.
What happened?
The error "-4016" occurred in the current database connection "LCA".
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.
How to correct the error
Database error text........: "POS(1) Unknown procedure
name:SIM_SIMSESSION_GET_ACTIVE"
Database error code........: "-4016"
Triggering SQL statement...: "EXECUTE PROCEDURE "SIM_SIMSESSION_GET_ACTIVE""
Internal call code.........: "[DBDS/NEW DSQL]"
Please check the entries in the system log (Transaction SM21).
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:
"DBIF_DSQL2_SQL_ERROR" "CX_SY_NATIVE_SQL_ERROR"
"/SAPAPO/SAPLOM_CORE" or "/SAPAPO/LOM_COREU23"
"/SAPAPO/OM_SIMSESSION_GET_ALL"
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.
The exception must either be prevented, caught within proedure
"/SAPAPO/OM_SIMSESSION_GET_ALL" "(FUNCTION)", or its possible occurrence must
be declared in the
RAISING clause of the procedure.
To prevent the exception, note the following:
System environment
SAP-Release 700
Application server... "dewall43"
Network address...... "10.40.16.43"
Operating system..... "AIX"
Release.............. "5.3"
Hardware type........ "00C912FC4C00"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 14
Shortdump setting.... "full"
Database server... "dewall43"
Database type..... "ORACLE"
Database name..... "APO"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Jan 23 2008 21:25:00"
create on........ "AIX 2 5 005DD9CD4C00"
Database version. "OCI_102 (10.2.0.2.0) "
Patch level. 144
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.... 1117168
EM...... 0
Heap.... 0
Page.... 24576
MM Used. 720672
MM Free. 376056
User and Transaction
Client.............. 100
User................ "DDIC"
Language key........ "E"
Transaction......... " "
Transactions ID..... "48692ABF23D6012AE10080000A28102B"
Program............. "/SAPAPO/SAPLOM_CORE"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "/SAPAPO/SAPLOM_CORE" - in
"/SAPAPO/OM_SIMSESSION_GET_ALL".
The main program was "/SAPAPO/OM_DELETE_OLD_SIMS ".
In the source code you have the termination point in line 39
of the (Include) program "/SAPAPO/LOM_COREU23".
The program "/SAPAPO/SAPLOM_CORE" was started as a background job.
Job Name....... "/SAPAPO/OM_DELETE_OLD_SIMSESS"
Job Initiator.. "DDIC"
Job Number..... 08200801
The termination is caused because exception "CX_SY_NATIVE_SQL_ERROR" occurred
in
procedure "/SAPAPO/OM_SIMSESSION_GET_ALL" "(FUNCTION)", but it was neither
handled locally nor declared
in the RAISING clause of its signature.
The procedure is in program "/SAPAPO/SAPLOM_CORE "; its source code begins in
line
1 of the (Include program "/SAPAPO/LOM_COREU23 ".
Source Code Extract
Line
SourceCde
9
*" REFERENCE(ET_ACTIVE_SIMSESSION) TYPE /SAPAPO/OM_SIMSESSION_TAB
10
*" REFERENCE(ET_RC) TYPE /SAPAPO/OM_LC_RC_TAB
11
*" EXCEPTIONS
12
*" LC_CONNECT_FAILED
13
*" LC_COM_ERROR
14
*" LC_APPL_ERROR
15
16
17
data_def.
18
create_gen_com_params_default.
19
CLEAR ls_gen_com_params-client.
20
21
Verbindung zum liveCache aufbauen
22
start_function 'OM_SIMSESSION_GET_ALL'. "#EC *
23
check_server.
24
connect_to_livecache.
25
IF et_simsession IS REQUESTED.
26
COM-Routine zum Auslesen aller trans. Sim.
27
EXEC SQL.
28
EXECUTE PROCEDURE "SIM_SIMSESSION_GET_ALL" (
29
IN :LS_GEN_COM_PARAMS,
30
OUT :LV_RC,
31
OUT :ET_SIMSESSION)
32
ENDEXEC.
33
Returncodes pruefen und evtl. Exception raisen
34
lv_subrc_sav = sy-subrc.
35
ENDIF.
36
IF et_active_simsession IS REQUESTED.
37
COM-Routine zum Auslesen aller aktiven trans. Sim.
38
EXEC SQL.
>>>>>
EXECUTE PROCEDURE "SIM_SIMSESSION_GET_ACTIVE" (
40
IN :LS_GEN_COM_PARAMS,
41
OUT :LV_RC,
42
OUT :ET_ACTIVE_SIMSESSION)
43
ENDEXEC.
44
Returncodes pruefen und evtl. Exception raisen
45
lv_subrc_sav = sy-subrc.
46
ENDIF.
47
48
end_performance_measure.
49
end_function_no_main om_simsession_get_all.
50
check_returncodes.
51
if iv_get_testguids = gc_false.
52
delete ET_ACTIVE_SIMSESSION where table_line cs '~'.
53
delete ET_SIMSESSION where table_line cs '~'.
54
endif.
55
ENDFUNCTION.
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
0
SY-TABIX
1
SY-DBCNT
0
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
Periodic Deletion of Hanging Simulation Versions
SY-MSGTY
SY-MSGID
SY-MSGNO
000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20080701
SY-UZEIT
092008
SY-XPROG
RSDBRUNT
SY-XFORM
%_INIT_PBO_FIRST
Active Calls/Events
No. Ty. Program Include Line
Name
3 FUNCTION /SAPAPO/SAPLOM_CORE /SAPAPO/LOM_COREU23 39
/SAPAPO/OM_SIMSESSION_GET_ALL
2 FUNCTION /SAPAPO/SAPLOM_CORE /SAPAPO/LOM_COREU12 52
/SAPAPO/OM_SIMSESSION_SELECT
1 EVENT /SAPAPO/OM_DELETE_OLD_SIMS /SAPAPO/OM_DELETE_OLD_SIMS 67
START-OF-SELECTION
Chosen variables
Name
Val.
No. 3 Ty. FUNCTION
Name /SAPAPO/OM_SIMSESSION_GET_ALL
IV_GET_TESTGUIDS
X
0
0
5
8
ET_ACTIVE_SIMSESSION
Table IT_9[0x44]
\FUNCTION=/SAPAPO/OM_SIMSESSION_SELECT\DATA=LT_SIMSESSION
Table reference: 2
TABH+ 0(20) = 0000000000000000000000000000000000000000
TABH+ 20(20) = 0000000200000009000000000000002CFFFFFFFF
TABH+ 40(16) = 04000021000026C00010249401800000
store = 0x0000000000000000
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 2 (0x00000002)
label = 9 (0x00000009)
fill = 0 (0x00000000)
leng = 44 (0x0000002C)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000192
occu = 16 (0x00000010)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
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 = Not allocated
pghook = Not allocated
idxPtr = Not allocated
shmTabhSet = Not allocated
id = Not allocated
refCount = Not allocated
tstRefCount = Not allocated
lineAdmin = Not allocated
lineAlloc = Not allocated
shmVersId = Not allocated
shmRefCount = Not allocated
shmIsReadOnly = Not allocated
>>>>> 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
ET_RC
Table[initial]
ET_SIMSESSION
Table[initial]
OM_LC_NAME
LCA
000000000000000000000000000000
000000000000000000000000000000
444222222222222222222222222222
C31000000000000000000000000000
GC_OM_SYSUBRC
-16842752
F
E
SY-SUBRC
0
0000
0000
%_SPACE
0
0
2
0
%_VIASELSCR
0
4
OM_LC_APPL_NAME
000000000000000000000000000000
000000000000000000000000000000
222222222222222222222222222222
000000000000000000000000000000
SPACE
0
0
2
0
LS_GEN_COM_PARAMS
DDIC # /SAPAPO/OM_DELETE_OLD_SIMS
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222444422222222222222222222222222222222202254545424454444545444554452222222
0000000000000000000000449300000000000000000000000000000000000F31010FFFDF45C545FFC4F39D30000000
LV_RC
00
00
00
00
GC_OM_SPP_FORECAST_EXT
K
4
B
GC_IMMEDIATE_TRANSFER
65537
0
0
GC_RESOURCE_MULTI
16909060
0
1
GV_SIMSESSION_TYPE
0
0
2
0
OM_MEASURE_PERFORMANCE
0
0
2
0
GC_OM_OBJECT_OUTPUT_NODE
454827294
1
B
OM_AS_KEY
000000000000000000000000000000
000000000000000000000000000000
222222222222222222222222222222
000000000000000000000000000000
%_DUMMY$$
0000
0000
2222
0000
No. 2 Ty. FUNCTION
Name /SAPAPO/OM_SIMSESSION_SELECT
IV_MIN_AGE_IN_HOURS
1
0000
0001
IV_SAVED_INCLUSIVE
0
0
2
0
ET_OMS_VERSION
Table[initial]
ET_SIMSESSION_DELTA
Table[initial]
SCREEN
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
GC_OM_RPM_PORD_DEL
2004
000D
0074
GC_OM_OBJECT_UNKNOWN
66051
0
0
GC_OM_OBJECT_ORDER
16909060
0
1
GS_OMS_VERSION
00000000 ########
000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000C
222222222222222222222233333333222222222222222222222200000000
000000000000000000000000000000000000000000000000000000000000
GC_MINTIME
09011000
1700002C
GT_OMS_VERSION
Table[initial]
GC_APPLICATION_BLRG
235868177
0
E
GC_OM_OBJECT_MODE
50595078
0
3
GC_TRUE
X
0
0
5
8
RSJOBINFO
00000000000000 ##
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222233333333333333222222222222222222222222222222222200
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
GC_OM_OBJECT_RESOURCE
67438087
0
4
LT_SIMSESSION
Table IT_9[0x44]
GC_APPLICATION_CTPE
168496141
0
A
SY-REPID
/SAPAPO/SAPLOM_CORE
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2545454254544454454222222222222222222222
F31010FF310CFDF3F25000000000000000000000
GC_APPLICATION_MATP
185339150
0
B
SYST-REPID
/SAPAPO/SAPLOM_CORE
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2545454254544454454222222222222222222222
F31010FF310CFDF3F25000000000000000000000
GC_ATP_UPD_RPM
R
0
0
5
2
No. 1 Ty. EVENT
Name START-OF-SELECTION
VARI
###00000000000000 ############
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222222222222222222222222222222200033333333333333222222000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SYST-REPID
/SAPAPO/OM_DELETE_OLD_SIMS
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2545454244544445454445544522222222222222
F31010FFFDF45C545FFC4F39D300000000000000
GC_OM_OBJECT_RPM_GENERIC
791687475
2
F
SY-SUBRC
0
0000
0000
%_VIASELSCR
0
4
SY-REPID
/SAPAPO/OM_DELETE_OLD_SIMS
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2545454244544445454445544522222222222222
F31010FFFDF45C545FFC4F39D300000000000000
SY-MSGID
00000000000000000000
00000000000000000000
22222222222222222222
00000000000000000000
GC_TRANSPORT
y
0
0
7
9
SPACE
0
0
2
0
SY-MSGNO
000
000
000
333
000
SY-MSGV1
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
SY-MSGV2
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
SY-MSGV3
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
SY-MSGV4
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
GC_ITRUE
16777623
0
1
GC_FALSE
0
0
2
0
SYST
###############################################################################T########X ####
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000100000000000000000000000000000000000000000000000E000200
0000000000000000000000000000000000000006000000000000000000000000000000000000010500000001520000
000001010000010000000000010001000000000A00000000000000000000000000000000000006040000000080000C
GC_IFALSE
104192
0
0
GT_OMS_VERSION
Table[initial]
GC_MINTIME
09011000
1700002C
GT_SIMS_DELTA
Table[initial]
SY-XFORM
%_INIT_PBO_FIRST
000000000000000000000000000000
000000000000000000000000000000
254445554454455522222222222222
5F9E94F02FF6923400000000000000
%_DUMMY$$
0000
0000
2222
0000
SCREEN
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Internal notes
The termination was triggered in function "DsqlErrorHandler"
of the SAP kernel, in line 2062 of the module
"//bas/700_REL/src/krn/runt/abexsql.c#2".
The internal operation just processed is "DSQL".
Internal mode was started at 20080701092008.
Internal call code.........: "[DBDS/NEW DSQL]"
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 = 4294965248
=> File size limit = unlimited
=> Heap address = 0x0x1152ede20
=> Stack address = 0xfffffffffff84a0
=> Stack low = 0xfffffffffff84a0
=> Stack high = 0xffffffffffff7a0
=> Stack Trace:
 AixStack() at 0x1000c7d94
 CTrcStack2() at 0x1000c7e8c
 rabax_CStackSave__Fv() at 0x1000b2d70
 ab_rabax() at 0x1000af728
 ab_dbdserr__FiPCUsT1T2P9DS_HEADERT2T1Pv() at 0x10057efbc
 DsqlErrorHandler__Fi() at 0x10135b8e8
 ExecuteCall__Fv() at 0x10135b454
 ab_jdsql__Fv() at 0x101356b40
 ab_extri__Fv() at 0x10040d93c
 ab_xevent__FPCUs() at 0x100a9d170
 ab_trigg__Fv() at 0x100a9ce5c
 ab_run() at 0x1014bee48
 N_ab_run() at 0x100d5bca8
 dynpmcal() at 0x100d5aa74
 dynppai0() at 0x100d58a08
 dynprctl() at 0x100d6047c
 dynpen00() at 0x100d52364
 Thdynpen00() at 0x1000e2410
 TskhLoop() at 0x1000e4254
 ThStart() at 0x1000fe324
 DpMain() at 0x10156c770
 nlsui_main() at 0x101a99998
List of ABAP programs affected
Index
Typ
Program
Group
Date
Time
Size
Lang.
0
Prg
/SAPAPO/OM_DELETE_OLD_SIMS
0
28.09.2006
17:13:54
115712
E
1
Prg
SAPMSSY0
1
07.01.2008
17:16:23
92160
E
2
Prg
SAPMSSYD
1
27.09.2006
18:38:20
21504
E
3
Prg
SAPFSYSCALLS
1
03.12.2004
17:45:45
8192
E
4
Prg
RSDBRUNT
0
07.01.2008
17:27:13
254976
E
5
Typ
RSSCR
0
12.10.1999
15:50:05
5120
6
Prg
RSDBSPBL
0
22.02.2005
08:58:45
72704
E
7
Prg
SAPDB__S
0
03.12.2004
17:45:45
19456
E
8
Prg
RSDBSPMC
0
27.09.2006
18:23:16
79872
E
9
Typ
DDSHDESCR
0
28.11.1997
16:26:30
4096
10
Typ
SPPARAMS
0
07.03.1997
14:48:48
2048
11
Prg
SAPLSABE
11
03.12.2004
17:45:46
13312
E
12
Prg
SAPLSECU
12
07.01.2008
17:09:46
87040
E
13
Typ
RSSUBINFO
0
25.02.2000
15:47:23
3072
14
Prg
SAPLSTUP
14
07.01.2008
17:08:20
74752
E
15
Prg
SAPLCNDP
15
13.12.2007
16:41:21
195584
E
16
Prg
SAPLSCNT
16
22.02.2005
08:58:56
30720
E
17
Prg
SAPSHDTV
16
31.01.2005
15:41:11
33792
E
18
Prg
SAPFGUICNTL
1
22.02.2005
08:58:14
24576
E
19
Prg
SAPLOLEA
19
12.12.2007
14:16:36
96256
E
20
Prg
SAPLSGUI
20
07.01.2008
17:16:23
84992
E
21
Prg
SAPLSTTM
21
28.07.2005
11:12:25
69632
E
22
Prg
SAPLSBDC
22
07.01.2008
17:09:02
44032
E
23
Prg
SAPLSFES
23
07.01.2008
17:27:14
260096
E
24
Prg
SAPLTHFB
24
07.01.2008
17:16:23
394240
E
25
Typ
WPINFO
0
08.02.1999
14:18:32
6144
26
Prg
SAPLURFC
26
07.01.2008
17:13:39
22528
E
27
Prg
SAPLSPLUGIN
27
03.12.2004
17:45:46
8192
E
28
Typ
SWCBCONT
0
07.10.1997
12:13:50
3072
29
Typ
OLE_VERBS
0
09.02.1995
13:23:37
2048
30
Typ
OLE_PA
0
13.01.1995
11:06:59
2048
31
Prg
/1BCDWBEN/SAPL/SAPAPO/EN0001
31
08.06.2001
20:33:24
233472
E
32
Prg
SAPLSENA
32
12.12.2007
14:18:37
33792
E
33
Prg
/SAPAPO/SAPLOM_CORE
33
28.07.2005
16:02:32
502784
E
34
Prg
SAPLSAL2
34
07.01.2008
17:15:35
81920
E
35
Typ
/SAPAPO/OM_OMS_VERSIONS_STR
0
16.02.2006
18:01:55
3072
36
Prg
CL_ABAP_CHAR_UTILITIES========CP
36
28.07.2005
11:12:24
13312
E
37
Prg
CX_SY_NATIVE_SQL_ERROR========CP
37
12.12.2007
12:39:14
13312
E
38
Typ
SCX_SRCPOS
0
08.07.2004
09:59:00
2048
39
Prg
CX_SY_SQL_ERROR===============CP
39
28.07.2005
11:12:24
10240
E
40
Prg
CX_DYNAMIC_CHECK==============CP
40
28.07.2005
11:12:24
10240
E
41
Prg
CX_ROOT=======================CP
41
12.12.2007
17:18:15
11264
E
42
Prg
CX_NO_CHECK===================CP
42
28.07.2005
11:12:24
10240
E
43
Prg
CX_SY_NO_HANDLER==============CP
43
28.07.2005
11:12:24
10240
E
44
Prg
%_CSYDES
0
22.02.2005
08:58:46
8192
E
45
Prg
%_CSYDB0
0
22.02.2005
08:58:45
36864
E
46
Typ
RSVAMEMKEY
0
16.12.1996
19:31:50
2048
47
Prg
%_CRSDS
0
22.02.2005
08:58:21
10240
E
48
Prg
%_CSLIS
12
17.02.2006
08:58:39
89088
E
49
Typ
DTC_S_LAYO
0
08.06.2001
15:59:56
6144
50
Typ
CAT_SVARS
0
19.05.2004
16:00:08
3072
51
Typ
SYST
0
03.12.2004
17:45:35
31744
52
Typ
RSJOBINFO
0
09.02.1995
13:25:17
3072
53
Typ
VARI
0
16.12.1996
19:38:11
6144
Directory of Application Tables
Name Date Time Lngth
Val.
Program /SAPAPO/OM_DELETE_OLD_SIMS
SYST 03.12.2004 17:45:35 00004612
\0\0\0\0\0\x0001\0\x0001\0\0\0\0\0\x0001\0\0\0\0\0\0\0\0\0
VARI . . : : 00003052
Program /SAPAPO/SAPLOM_CORE
RSJOBINFO . . : : 00000164

As per note 1619720, drop following two tables and then validate by running t-code lca03.
drop table APPSYSNAME
drop table APPSYSPARAM
dbmcli -d LCSID -n hostname -u superdba,sdbapassword -uSQL SAPSID,password
dbmcli on hostname : SID>sql_execute drop table APPSYSPARAM
OK

Runtime Errors DATA_LENGTH_0    Exception   CX_SY_RANGE_OUT_OF_BO

Hi All,
While using leave request service we are getting following dump in abap code , please advice
Runtime Errors         DATA_LENGTH_0
Exception              CX_SY_RANGE_OUT_OF_BOUNDS
Date and Time          13.01.2012 10:17:48
     Invalid partial field access: Length 0
What happened?
     Error in the ABAP Application Program
     The current ABAP program "ZCL_PT_GEN_REQ================CP" had to be
      terminated because it has
     come across a statement that unfortunately cannot be executed.
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 that is explained in detail below.
     The exception, which is assigned to class 'CX_SY_RANGE_OUT_OF_BOUNDS', was not
      caught in
     procedure "IF_EX_PT_GEN_REQ~SEARCH_FOR_NEXT_PROCESSOR" "(METHOD)", nor was it
      propagated by a RAISING clause.
     Since the caller of the procedure could not have anticipated that the
     exception would occur, the current program is terminated.
     The reason for the exception is:
     In the executed program "ZCL_PT_GEN_REQ================CP", the system
attempted to access the field
"IM_SEARCHSTRING" using the length 0.
However, a partial field access with the length specification 0 is not
allowed.
How to correct the error
Use a positive length specification if a part of the field "IM_SEARCHSTRING" is
to be
accessed.
If the error occurred in your own ABAP program or in an SAP
program you modified, try to remove 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:
"DATA_LENGTH_0" "CX_SY_RANGE_OUT_OF_BOUNDS"
"ZCL_PT_GEN_REQ================CP" or "ZCL_PT_GEN_REQ================CM002"
"IF_EX_PT_GEN_REQ~SEARCH_FOR_NEXT_PROCESSOR"
Dump At source code shows as following
LOOP AT ex_persdata_tab INTO wa_ex_perdata.
        w_str3 = wa_ex_perdata-user.
        IF w_str3 CO im_searchstring.
          w_len2 = sy-fdpos.
          w_len1 = sy-fdpos + 1.
**Get First name
          w_str2 = im_searchstring+w_len1.
**Get last name
---->>>       w_str1 = im_searchstring(w_len2).       (Point of dump) (Data type String = char25)
          IF w_str2 EQ wa_ex_perdata-name.
            APPEND wa_ex_perdata TO lt_ex_perdata.
            EXIT.
          ENDIF.
          CLEAR:w_str2,w_str1,w_len2,w_len1.
        ENDIF.
      ENDLOOP.
      CLEAR:wa_ex_perdata.

attempted to access the field
"IM_SEARCHSTRING" using the length 0.
However, a partial field access with the length specification 0 is not
allowed.
that w_len2 of yours is having a value 0. you cant access a field with length 0. thats the error

Runtime Error DBIF_RSQL_SQL_ERROR exception CX_SY_OPEN_SQL_DB

Hi,
i need some guides to solve this problem.
The program works fine in client DEV. However, when it's in QAS, we encounter short dump: Runtime Error DBIF_RSQL_SQL_ERROR exception CX_SY_OPEN_SQL_DB
info from short dump:
An SQL error occurred when accessing a table.
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
neither
caught nor passed along using a RAISING clause, in the procedure
"FILL_T_DATA_TABLE" "(FORM)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
How to correct the error
The exception must either be prevented, caught within the procedure
"FILL_T_DATA_TABLE"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
Database error text........: "ORA-24371: data would not fit in current prefe
buffer"
Internal call code.........: "[RSQL/FTCH/VBUK ]"
Please check the entries in the system log (Transaction SM21).
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC
"ZSDR_SHIPPING_REPORT" or "ZSDR_SHIPPING_REPORT"
"FILL_T_DATA_TABLE"
If you cannot solve the problem yourself, please send the...
Information on where terminated
The termination occurred in the ABAP program "ZSDR_SHIPPING_REPORT" in
"FILL_T_DATA_TABLE".
The main program was "ZSDR_SHIPPING_REPORT ".
The termination occurred in line 3561 of the source code of the (Include)
program "ZSDR_SHIPPING_REPORT"
of the source code of program "ZSDR_SHIPPING_REPORT" (when calling the editor
35610).
Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
the
procedure "FILL_T_DATA_TABLE" "(FORM)" but was not handled locally, not
declared in the
RAISING clause of the procedure.
The procedure is in the program "ZSDR_SHIPPING_REPORT ". Its source code starts
in line 3468
of the (Include) program "ZSDR_SHIPPING_REPORT ".
source code:
035490
035500   *get all open sales orders (those that are deemed open at the Sales
035510   *Order "Header" level)
035520     clear open_orders.
035530     refresh open_orders.
035540     select * into corresponding fields of table open_orders
035550       from vbuk
035560       where ( vbtyp = 'C' or vbtyp = 'I' )
035570         and ( gbstk = 'A' or gbstk = 'B' ).
035580
035590   *get all open deliveries(some sales orders may be closed yet the
035600   *associated Delivery is not yet PGI'd)
     >     clear open_deliveries.
035620     refresh open_deliveries.
035630     select * into corresponding fields of table open_deliveries
035640       from vbuk
035650       where vbtyp = 'J'
035660         and ( wbstk = 'A' or wbstk = 'B' ).
035670
035680   *get sales orders associated with the Open deliveries
Please advice.
Thanks.

Thanks for the response.
Hi Renga,
The error happens in second selection.
this is the souce code:
data: begin of open_orders occurs 0,
        vbeln like vbuk-vbeln,
        gbstk like vbuk-gbstk,
        vbtyp like vbuk-vbtyp,
      end of open_orders.
data: begin of open_deliveries occurs 0,
        vbeln like vbuk-vbeln,
        wbstk like vbuk-wbstk,
        vbtyp like vbuk-vbtyp,
      end of open_deliveries.
*get all open sales orders (those that are deemed open at the Sales
*Order "Header" level)
clear open_orders.
refresh open_orders.
select * into corresponding fields of table open_orders
    from vbuk
    where ( vbtyp = 'C' or vbtyp = 'I' )
      and ( gbstk = 'A' or gbstk = 'B' ).
*get all open deliveries(some sales orders may be closed yet the
*associated Delivery is not yet PGI'd)
clear open_deliveries.
refresh open_deliveries.
select * into corresponding fields of table open_deliveries
    from vbuk
    where vbtyp = 'J'
      and ( wbstk = 'A' or wbstk = 'B' ).
Hi Prabhu,
how to identify the problem in DB02?
Please advice.
Thanks.
regards.

Runtime error - DBIF_RSQL_INVALID_RSQL, Exception - CX_SY_OPEN_SQL_DB

Hi,
Following code is working fine in Development system and in Production system I am getting a runtime error. Only difference I am finding is in r_lifnr value. In development system I have few lifnr and in Production system it's not so... am I getting error because of it? Is there any restriction to no. of items populated in a range? Or Basis person need to change any parameter? Enclosed the detail dump below the code...
Advance thanks.
Regards,
Balaji Viswanath.
Code:
SELECT bukrs
 lifnr
 augdt
 augbl
 zuonr
 gjahr
 belnr
 buzei
 waers
 dmbtr
 wrbtr
 zlsch
 shkzg
 blart
 gsber
 sgtxt
INTO TABLE t_bsak_tmp
FROM bsak CLIENT SPECIFIED
WHERE mandt = sy-mandt AND
 lifnr IN r_lifnr AND
 bukrs IN s_bukrs AND
 augdt IN s_augdt AND
 blart IN s_blart.
IF sy-subrc <> 0.
No data found for selection criteria
 MESSAGE i018.
 LEAVE LIST-PROCESSING.
ENDIF.
Dump:
Runtime Errors DBIF_RSQL_INVALID_RSQL
Exception CX_SY_OPEN_SQL_DB
 Occurred on 14.11.2005 at 14:35:22
Error in the module RSQL accessing the database interface.
What happened?
Error in ABAP application program.
The current ABAP program "/DS1/FI_CR_REPT_PGSR802_VEND_P" had to be terminated
because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
neither
caught nor passed along using a RAISING clause, in the procedure
"GET_CLRD_VEN_DATA" "(FORM)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
The SQL statement generated from the SAP Open SQL Statement violates a
restriction imposed by the database system used in R/3.
Possible errors:
o The maximum size of an SQL statement has been exceeded.
o The statement contains too many input variables.
o The space needed for the input data exceeds the available memory.
o ...
You can usually find details in the system log (SM21) and in the
developer trace of the work process (ST11).
If an error occurs the developer trace often informs you about the
current restrictions.
How to correct the error
The exception must either be prevented, caught within the procedure
"GET_CLRD_VEN_DATA"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
The SAP Open SQL statement must be divided into several smaller units.
If the problem occurred due to the use of an excessively large table
in an IN itab construct, you can use the addition FOR ALL ENTRIES
instead.
When you use this addition, the statement is split into smaller units
according to the restrictions of the database system used.
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"DBIF_RSQL_INVALID_RSQL" CX_SY_OPEN_SQL_DBC
"/DS1/FI_CR_REPT_PGSR802_VEND_P" or "/DS1/FI_CR_REPT_PGSR802_VEND_P"
"GET_CLRD_VEN_DATA"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
 To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
 To obtain this, call the system log with Transaction SM21
 and select the "Print" function to print out the relevant
 part.
3. If the programs are your own programs or modified SAP programs,
 supply the source code.
 To do this, you can either use the "PRINT" command in the editor or
 print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
 or which actions and input led to the error.
System environment
SAP Release.............. "620"
Application server....... "ztm1003"
Network address.......... "145.26.160.103"
Operating system......... "AIX"
Release.................. "5.3"
Hardware type............ "00C004DC4C00"
Character length......... 16 Bits
Pointer length........... 64 Bits
Work process number...... 6
Short dump setting....... "full"
Database server.......... "ztm1003"
Database type............ "ORACLE"
Database name............ "A94"
Database owner........... "SAPR3K"
Character set............ "C"
SAP kernel............... "640"
Created on............... "Aug 7 2005 20:44:35"
Created in............... "AIX 1 5 00538A4A4C00"
Database version......... "OCI_920 "
Patch level.............. "85"
Patch text............... " "
Supported environment....
Database................. "ORACLE 8.1.7.., ORACLE 9.2.0.., ORACLE
10.1.0.."
SAP database version..... "640"
Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"
User, transaction...
Client.............. 110
User................ "INBVI0"
Language key........ "E"
Transaction......... "SE38 "
Program............. "/DS1/FI_CR_REPT_PGSR802_VEND_P"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
The termination occurred in the ABAP program "/DS1/FI_CR_REPT_PGSR802_VEND_P"
in "GET_CLRD_VEN_DATA".
The main program was "/DS1/FI_CR_REPT_PGSR802_VEND_P ".
The termination occurred in line 503 of the source code of the (Include)
program "/DS1/FI_CR_REPT_PGSR802_VEND_P"
of the source code of program "/DS1/FI_CR_REPT_PGSR802_VEND_P" (when calling
the editor 5030).
Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
the
procedure "GET_CLRD_VEN_DATA" "(FORM)" but was not handled locally, not
declared in the
RAISING clause of the procedure.
The procedure is in the program "/DS1/FI_CR_REPT_PGSR802_VEND_P ". Its source
code starts in line 501
of the (Include) program "/DS1/FI_CR_REPT_PGSR802_VEND_P ".
Source code extract
004730 &----
004740 * get country names from t005t
004750 ----
004760 FORM get_country_names.
004770
004780 t_lfa1_land[] = t_lfa1[].
004790 SORT t_lfa1_land BY land1.
004800 DELETE ADJACENT DUPLICATES FROM t_lfa1_land COMPARING land1.
004810
004820 IF NOT t_lfa1_land[] IS INITIAL.
004830 SELECT land1
004840 landx
004850 INTO TABLE t_t005t
004860 FROM t005t
004870 FOR ALL ENTRIES IN t_lfa1_land
004880 WHERE spras = sy-langu AND
004890 land1 = t_lfa1_land-land1.
004900 REFRESH t_lfa1_land.
004910 SORT t_t005t BY land1.
004920 ELSE.
004930 MESSAGE i014 WITH 'No vendor data fetched'(001).
004940 ENDIF.
004950 ENDFORM. " get_country_names
004960 &----
004970 *& Form get_clrd_ven_data
004980 &----
004990 * Cleared vendor data
005000 ----
005010 FORM get_clrd_ven_data .
005020
> SELECT bukrs
005040 lifnr
005050 augdt
005060 augbl
005070 zuonr
005080 gjahr
005090 belnr
005100 buzei
005110 waers
005120 dmbtr
005130 wrbtr
005140 zlsch
005150 shkzg
005160 blart
005170 gsber
005180 sgtxt
005190 INTO TABLE t_bsak_tmp
005200 FROM bsak CLIENT SPECIFIED
005210 * the order of the fields are as in the secondary Index.
005220 WHERE mandt = sy-mandt AND
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 0 SY-INDEX 0
SY-TABIX 1 SY-DBCNT 59
SY-FDPOS 0 SY-LSIND 0
SY-PAGNO 0 SY-LINNO 1
SY-COLNO 1 SY-PFKEY
SY-UCOMM
SY-TITLE Vendor Payment Details for IRD
SY-MSGTY I SY-MSGID SF
SY-MSGNO 616 SY-MSGV1 /DS1/FI_CR_REPT_PGSR802_VEND_P
SY-MSGV2 RE SY-MSGV3 EN
SY-MSGV4
Active calls / events
No.... Type........ Name..........................
 Program
 Include Line
 Class
 2 FORM GET_CLRD_VEN_DATA
 /DS1/FI_CR_REPT_PGSR802_VEND_P
 /DS1/FI_CR_REPT_PGSR802_VEND_P 503
 1 EVENT START-OF-SELECTION
 /DS1/FI_CR_REPT_PGSR802_VEND_P
 /DS1/FI_CR_REPT_PGSR802_VEND_P 135

Hi Balaji,
Here is what the dump said and my answers are right below them.
Possible errors:
o The maximum size of an SQL statement has been exceeded.
This may not be the reason in your case. This usually happens when you use the option FOR ALL ENTRIES
o The statement contains too many input variables.
Most likely this is your issue. I think your r_lifnr is filled with all the vendors in your system and filled as single values. In that case you may be exceeding a limit set on the system. Instead of trying to remove this setting, what I would suggest is to do the following.
Define a select-option for LIFNR on your selection screen. This way users can have the flexibility of specifying certain vendors. If they don't enter anything, it is still ok. Don't fill it with single values.
Use this select-option in your select statement. After the select statement, do a delete from itab where the vendors are not in your r_lifnr as below.
DELETE t_bsak_tmp WHERE NOT lifnr IN r_lifnr.
Also, avoid using client. You don't need that unless you really want to select from a different client other than your logon client. Your select statement is using logon client anyway, so you don't need to specify that.
o The space needed for the input data exceeds the available memory.
If the above changes are made and the problem is still there, then this is the next thing to look at.
Srinivas

Runtime Errors    BCD_FIELD_OVERFLOW Exception CX_SY_CONVERSION_OVERFLOW

Dear All,
I am getting below error in PRD system. We are using ecc6, oracle 10g and windows 2003. The error coming after we have restarted the server. Please suggest how to solve the issues.
SM21 log
09:30:21 DIA 000 000 DDIC                               AB 0 Run-time error "BCD_FIELD_OVERFLOW" occurred
09:30:21 DIA 000 000 DDIC                               AB 1 > Short dump "100913 093034 nodeA " generated
ST22
Runtime Errors         BCD_FIELD_OVERFLOW
Exception              CX_SY_CONVERSION_OVERFLOW
Date and Time          13.09.2010 00:30:19
Short text
     A calculation field is defined too small.
What happened?
     Error in the ABAP Application Program
     The current ABAP program "CL_SWNC_RECORD================CP" had to be
      terminated because it has
     come across a statement that unfortunately cannot be executed.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_CONVERSION_OVERFLOW', was not
     caught in
    procedure "DO_TRANSFORMATIONS" "(METHOD)", nor was it propagated by a RAISING
     clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    A value generated during processing is too large for the
    field "ME->MAIN_RECORD_STR+1020(7)" of the program
     "CL_SWNC_RECORD================CP".
Regards,
Kumar

Dear Friends,
We even got same dump "BCD_FIELD_OVERFLOW" just after system restart. But error was slightly different. Please find below error details and solution:
Error Details:
The current ABAP program "CL_SWNC_RECORD================CP" had to be terminated because it has come across a statement that unfortunately cannot be executed.
Error Analysis:
An exception occurred that is explained in detail below. This exception cannot be caught in the context of the current statement.
The reason for the exception is: A value generated during processing is too large for the field " " of the program "CL_SWNC_RECORD================CP".
"BCD_FIELD_OVERFLOW" " "
"CL_SWNC_RECORD================CP" or "CL_SWNC_RECORD================CM002"
"CALCULATE_PROCESSING_TIME"
SOLUTION:
An OSS Note:
Note 1103295 - BCD_FIELD_OVERFLOW in CALCULATE_PROCESSING_TIME (It solves the problem)

Runtime Error...Any Solution

Hi all,
I am trying to laod a flat file in BI 7.0 with the following short dump.
Runtime Errors         UNCAUGHT_EXCEPTION
Except.                CX_RSR_X_MESSAGE
Date and Time          04.02.2007 01:13:2
What happened?
    The exception 'CX_RSR_X_MESSAGE' 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 'SAPLRRMS' has to be
    terminated.
Error analysis
    An exception occurred which is explained in detail below.
    The exception, which is assigned to class 'CX_RSR_X_MESSAGE', was not caught and
    therefore caused a runtime error.
    The reason for the exception is:
    No text available for this exception
Missing Handling of Application Exception
    Program                                 RSAWBN_START
Any solution.
Thanks

Hi,
But I dont have any access to get hold of that note.
Thanks
Message was edited by:
        J B

Error in RFC & to Solution Manager System

Hi,
Error in RFC & to Solution Manager System
can anyone tells me why this error occurs???
With regards
kulwinder

FYI
We have just had same issue thaat in certain scenarios with RFC communication BACK to Solution Manager from Satellite system we got the error. We resolved this by looking at the RFC user used in the BACK connection (i.e. SOLMAN<SID>) on the Solution Manager and changing the user type from communications.
Hope this helps someone else, I spent ages digging around for an answer to such a simple fix
Paul

Portal Runtime Error : An exception occurred while processing a request

Hello friends,
After upgradation of my portal to the following patch level, SAP J2EE 6.20:
Portal Version : EP 6 SP 2 patch 29 hotfix 0
Content Mgmt and Collaboration version : 6 SP2 patch 5
i faced many performance related issues. Portal seems to be very slow. After logging in, most of the time I get 2 errors:
Either
1> Iview remains blank.
Or
2> Portal Runtime Error : An exception occurred while processing a request. Portal Runtime exception occured. Please check the System Log.
But when I refresh that particular iview, it works fine.
I went through the portal.log file (/usr/sap/PEP6/j2ee/j2ee_00/cluster/server/managers/log/portal/logs). And found the root cause of most of the exceptions as "com.inqmy.services.servlets_jsp.server.ServletNotFoundException: The requested servlet ( portal ) not found."Aug 18, 2005 6:07:42 PM # PRT-Async 2 Fatal Exception ID:06:07_18/08/05_0669
com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Component : pcd:portal_content/ACCContent/ACCContent.Roles/Company/R.Employee/W.MyWork/P.MyWork.DesktopTools/I.Contacts
Component class : com.sapportals.portal.prt.pom.RootComponentNode
User : tempuser
 at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:853)
 at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:311)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
 at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:363)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:376)
 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
 at java.lang.Thread.run(Thread.java:479)
Caused by: com.sapportals.portal.prt.component.PortalComponentException: PortalComponentException
 at com.sapportals.portal.prt.pom.RootComponentNode.service(RootComponentNode.java:153)
 at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:301)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
 at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:363)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:376)
 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
 at java.lang.Thread.run(Thread.java:479)
Caused by: com.inqmy.services.servlets_jsp.server.ServletNotFoundException: The requested servlet ( portal ) not found.
 at com.inqmy.services.servlets_jsp.server.ServletContextFacade.loadServletLocal(ServletContextFacade.java:3660)
 at com.inqmy.services.servlets_jsp.server.InvokerServlet.service(InvokerServlet.java:81)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.inqmy.services.servlets_jsp.server.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:275)
 at com.inqmy.services.servlets_jsp.server.RequestDispatcherImpl.include(RequestDispatcherImpl.java:384)
 at com.sapportals.portal.prt.pom.RootComponentNode.service(RootComponentNode.java:144)
 at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:301)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
 at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:363)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:376)
 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
 at java.lang.Thread.run(Thread.java:479)
Help needed.(as i am helpless now.)
Regards,
Nilz

Anthony,
I had check it. It was correct. But the thing when I saw in the component Inspector of portal, my iview did not appear.
I created like this
 project-> rightclick-> export-> par ->selecting project-> givint protal password-> and finish.
The NW didn't give any error, but the par file didn't appear in the portal componet Inspect.
but the par file is created in the NW studio Navigation bar.
Let me know any help regarding this
thanks
venkat

Error in Installation of Solution Manager on Virtualbox centOS

Error in Installation of Solution Manager on Virtualbox centOS .
I tried as per the solution given in the error.
Please go through attachment for error and my /etc/hosts file.

Hi,
I guess you added the entry in /etc/hosts after you got the error.
That being true, stop and start your sapinst again. This will allow you to continue. The information is cached and the only way is to stop and start sapinst.
Cheers,
Amerjit

I got errors while installation of solution manager 4.0 sr2

I faced the errors below while installing Solution Manager 4.0 sr2.
How can I solve these problems?
Thanks.
ERROR 2007-03-13 17:30:12
FSL-00001 System call failed. Error 13 (Permission denied) in execution of system call 'openU' with parameter (/opt/cdler/CD2/IM_HPUX_PARISC/COMMON/INSTALL/JDBCCONNECT.JAR, O_RDONLY), line (368) in file (syuxcfile.cpp).
ERROR 2007-03-13 17:30:12
FSL-02015 Node /opt/cdler/CD2/IM_HPUX_PARISC/COMMON/INSTALL/JDBCCONNECT.JAR does not exist.
ERROR 2007-03-13 17:30:12
MUT-03025 Caught ESyException in Modulecall: ESAPinstException: error text undefined.
ERROR 2007-03-13 17:30:12
FCO-00011 The step copyScripts with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_Unpack|ind|ind|ind|ind|8|0|copyScripts was executed with status ERROR .

Hello Cemil,
The errors you are recieving are most likely user or permissions
related.
Can you please verify that there are 777 permissions on the
installation directories? Also are you installing as User Root?
Are you installing from an NFS Mount or network drive? If so it could be
possible that the user does not have enough permissions on this. If
so I recommend copying the installation files to a local directory and
retrying the installation from there.
Best regards,
Dolores

Runtime Errors Raise Exception in Solution Manager

Similar Messages

Maybe you are looking for