Dump on DBIF_RSQL_INVALID_RSQL
Hi,
I am getting a dump on execution of a SQL statement, where the data is huge.
The error description...
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.
The Statement raising the error ...
LOOP AT pp_agreement.
TRANSLATE pp_agreement-fname TO UPPER CASE.
CONDENSE pp_agreement-fname NO-GAPS.
CASE pp_agreement-fname.
WHEN 'AGREEMENT'.
MOVE-CORRESPONDING pp_agreement TO r_agreement.
APPEND r_agreement.
WHEN OTHERS.
CLEAR pp_error.
pp_error-type = 'W'.
CONCATENATE 'Invalid Agreement --' pp_agreement-fname
INTO pp_error-message_v1.
APPEND pp_error.
ENDCASE.
CLEAR : r_agreement.
ENDLOOP.
IF pp_error IS INITIAL.
Get agreements effective as of validity date or in the future.
Inclue the customer related agreements.
SELECT * FROM z9ars_agreement
INTO CORRESPONDING FIELDS OF TABLE pp_z9p_generic_agreement
WHERE agreement IN r_agreement
AND customer = space
and orderbegindate le pp_validity_date "v003
and orderenddate ge pp_validity_date "v003
AND orderbegindate LE l_to_date "v003
AND orderenddate GE l_from_date. "v003
DESCRIBE TABLE pp_z9p_generic_agreement LINES g_line_count.
IF g_line_count = 0.
CLEAR pp_error.
pp_error-type = 'W'.
MOVE 'No agreements retrieved --'
TO pp_error-message_v1.
APPEND pp_error.
ENDIF.
ENDIF.
REFRESH: r_agreement.
The data in the IT r_agreement is Huge causing the dump.
The Z program is calling a Function Module where this select statement is executed.
This FM is being used by lots of other programs.
Kindly let know how to rectify the Error.
Do let know if any other details are required.
Thanks in advance.
Regards,
Syed
This is what we did for a similar issue.
Here we kept a limit of 5000 records in ranges. Hope it helps
SORT ra_objnr BY low.
DELETE ADJACENT DUPLICATES FROM ra_objnr COMPARING low.
DO.
APPEND LINES OF ra_objnr FROM l_count_start TO l_count_end TO ra_objnr2 .
l_last = sy-tabix.
l_count_start = l_count_end + 1.
l_count_end = l_count_end + 5000.
IF ra_objnr2[] IS NOT INITIAL.
SELECT kokrs
belnr
buzei
kstar
wkgbtr
objnr
vrgng
beknz FROM coep
APPENDING TABLE it_coep_over
WHERE kokrs EQ p_kokrs
AND perio EQ p_perio
AND gjahr EQ p_gjahr
AND objnr IN ra_objnr2.
ENDIF.
REFRESH ra_objnr2.
IF l_last NE 5000.
EXIT.
ENDIF.
ENDDO.
Edited by: Romit Kewalramani on Jul 24, 2008 7:33 PM
Similar Messages
-
Dump on DBIF_RSQL_INVALID_RSQL se14 pooled table adjustment
I have been trying to adjust table T157T in SE14 and I get a short dump that says:
Runtime Error DBIF_RSQL_INVALID_RSQL
Exception CX_SY_OPEN_SQL_DB
Occurred on 08.03.2008 at 15:06:58
Error in the module RSQL accessing the database interface.
What happened?
Error in ABAP application program.
The current ABAP program "%_T002S0" 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 "DATA_COPY" "(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 data read during a SELECT access could not be inserted into the target field. Either conversion is not supported for the target field's type or the
target field is too short to accept the value or the data are not in a form that the target field can accept
How to correct the error
The exception must either be prevented, caught within the procedure "DATA_COPY"
"(FORM)", or declared in the procedure's RAISING clause. To prevent the exception, note the following:
Check the entries in the developer trace (Transaction ST11) This contains details about the type and length of the database field, and the field in ABAP in which the database field should
have been placed.
Assistance will be greatly appreciated and rewarded.
Regards.DURING ADJUST THERE ARE PRIMARLY MANY STEPS INVOLVED
LOCKING THE TABLE
1.CREATING A TABLE WITH SAME NAME SPACE Q*
2.CREATING THE STRCUTRE OF THE TABLE
3.DELETING INDEXES
4.MOVING THE DATA FROM TABLE ORIGINAL TO TEMP TABLE.
5.DELETING THE TABLE OLD
6.CREATING NEW STRUCTURE WITH ORGINAL NAME.
7.MOVING THE DATA.
8.DELETING ALL THE TEMP TABLE & STRUCTURES.
UNLOCKING THE TABLE
U R ERROR PRETAINS TO EITHER DURING THE DATA_COPY U R SELECT QUERIE RUNS IN LOOPS
SO THE AUM-->> AUTOMATIC UNDO MANAGEMENT IS NOT SO ADEQUATELY SUPPORTED
SO IT TRIES TO RETAIN THE RECORD BUT IT COULDNT RETAIN BECAUSE OF IT NON AVAILBILITY OF BUFFERS SO SEE THE AUM-->> REDO PARAMETERS ARE AT HIGHEST AND THEN TRY YOUR ACIVITY U CAN ALSO GET THE LOG PARAMETERS IN ALERT.LOG FILE IN THE BACKEND ASK UR BASIS CONSULTANT TO LOOK INTO IT.
REGARDS
DEVANAND -
Dump DBIF_RSQL_INVALID_RSQL inserting the entry in bbp_pdisc
Hi Experts,
In our SRM senario, we are haing differnt backend system which are connected to SRM portal. Each system send the PO to SRM. I am currently facing a ssue with SRM system. When i create the PO in some backend system i am able to see the PO in SRM box. but for other systems PO it is giving the short dump as DBIF_RSQL_INVALID_RSQL.
On analysis of the dump i found that the error is occuring in the inesrt statemnt while iinserting the data in table bbp_pdisc. in standard program.
I am not sure while this is happing only for few system , Can any one let me know why this is happening ,any inputs on this are really helpful.hi ,
Please check table bbp_pdisc format and pass data according
if there is data type mismatch then it will give dump .
regards
Deepak. -
ODS activation error after the structure change
Hi all,
I am getting a short dump with " "DBIF_RSQL_INVALID_RSQL" CX_SY_OPEN_SQL_DBC " error when I am trying to activate an ODS after changing its structure. Do I need to change any setting before loading the data in to the ODS after adding few more fields to it. Exact error says
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
"ACTIVATE_SIDS" "(FORM)"
ThanksThe above-described symptom is due to a program error during the transfer of error messages. The problem can occur, for example, if a hierarchy is activated during the activation of an ODS object.
If the indicator 'BEx Reporting' is set for the ODS object, entries are created in the SID tables of characteristics involved during the activation of requests for this ODS object. Newly-created SID values must then be inserted into hierarchy tables. This is not possible for reasons of consistency if a hierarchy is activated at this time. The RRHI_CHAVLS_REQUEST_TO_HIERA function module is used for inserting newly-created SID values in hierarchies.
To simplify the search for the cause of the problem, additional error messages are now displayed in the monitor. If the problem is triggered, for example, by the simultaneous activation of a hierarchy, the error message RH 14 is issued. As described in note 717967, this error message contains the name of the affected hierarchy. If the activation of an ODS object is cancelled due to a serious error, this now also causes additional entries in the log of transaction SM21 (Syslog). These entries start with the character string '> RSDRO':.
Solution
BW 3.0B
Import Support Package 21 for 3.0B (BW3.0B Patch21 or SAPKW30B21) into your BW system. The Support Package is available whennote 0679665 with the short text "SAPBWNews BW3.0B Support Package 21", which describes this Support Package in more detail, is released for customers.
BW 3.10 Content
Import Support Package 15 for 3.10 (BW3. 10 Patch15 or SAPKW31015) into your BW system. The Support Package is available when note 0601055 with the short text "SAPBWNews BW 3.1 Content Support Package 15" is released for customers.
BW3.50
Import Support Package 03 for 3.5 (BW3.50 Patch03 or SAPKW35003) into your BW system. The Support Package is available when note 0693363 with the short text "SAPBWNews BW 3.5 Support Package 03", which describes this Support Package in more detail, is released for customers. -
Hi Experts,
I am facing the problem in the select statement where it giving the short dump
DBIF_RSQL_INVALID_RSQL CX_SY_OPEN_S.
i have searched many forms, but i found that the select option s_matnr have the limitaion 2000 entreis, but i am passing same s_matnr to other select statement with more than 2000 entries but it is not giving me any short dump.
but i am facing problem with only one select statement where if i pass select option s_matnr more than 1500 entris also giving short dump.
my select statement is
SELECT * FROM bsim
INTO CORRESPONDING FIELDS OF TABLE g_t_bsim_lean
FOR ALL ENTRIES IN t_bwkey WHERE bwkey = t_bwkey-bwkey
AND matnr IN matnr
AND bwtar IN bwtar
AND budat >= datum-low.
in the internal table g_t_bsim_lean internal table contain all the fields of the table bsim with 2 fields from other table.
Please let me know whether i need to change the select statement or any other solution for this.
Regards,
udupimy select query is like this:
DATA: BEGIN OF t_bwkey OCCURS 0, "184465
bwkey LIKE bsim-bwkey, "184465
END OF t_bwkey. "184465
LOOP AT g_t_organ WHERE keytype = c_bwkey.
MOVE g_t_organ-bwkey TO t_bwkey-bwkey.
COLLECT t_bwkey. "184465
ENDLOOP. "184465
READ TABLE t_bwkey INDEX 1. "184465
CHECK sy-subrc = 0. "184465
SELECT * FROM bsim "n443935
INTO CORRESPONDING FIELDS OF TABLE g_t_bsim_lean "n443935
FOR ALL ENTRIES IN t_bwkey WHERE bwkey = t_bwkey-bwkey
AND matnr IN matnr
AND bwtar IN bwtar
AND budat >= datum-low. -
'DBIF_RSQL_INVALID_RSQL' short dump
Hello All,
I have a dynamic where_clause in a select query. ie its created at runtime. I get a short dump 'DBIF_RSQL_INVALID_RSQL' at the select statement. The reason shown in ST22 is:
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.
Could you please suggest a solution to the problem, since the data to be fetched is large I would not want to use select-endselect loop as that would make it slower.
Thanks in advance,
AnjuHi Anju,
Check the link
[ Perfect link|
DBIF_RSQL_INVALID_RSQL;
Regards,
Sandeep -
Dump DBIF_RSQL_INVALID_RSQL
Dear all
I am facing a problem related to abap program, when I run the program like zmatlist
When I give Material Number in selection option ( for example 20000 Material Number )
In one go then abap report give me the following DUMP
DBIF_RSQL_INVALID_RSQL
CX_SY_OPEN_SQL_DB
And when in give selection option in chunk the that report run fine
After the dump I check dev_w0 file it shows like that
*C *** ERROR => max. statement length (65536) exceeded*
http://dbsloci.c 5759
C Dumping statement ...
C 0 | TEXT | 6 | SELECT
C 1 | TEXT | 4 | T_00
C 2 | TEXT | 1 | .
C 3 | IDENTIFIER | 5 | BISMT
So on
C 17481 | TEXT | 3 | AND
C 17482 | TEXT | 4 | T_02
C 17483 | TEXT | 1 | .
C 17484 | IDENTIFIER | 5 | WERKS
C 17485 | TEXT | 1 | =
C 17486 | MARKER(8588)| 0 | NULL
C token_cnt=17487, input_cnt=8589, marker_cnt=8589, stmt_length=86128
B ***LOG BYK=> current SQL statement exceeds a database limit dbtran#5 @ 7261 dbtran 7261
B dbtran ERROR LOG (hdl_dbsl_error): DbSl 'PRE'
thankx
RayyanHi Shahid,
Please refer OSS note:
Note 48230 - Parameters for the SELECT ... FOR ALL ENTRIES statement
which explains the various option to solve your problem.
The dump is occuring because of too many inputs(20000 material number) in the select option.
Please let me know if this helpful, by rating.
Regards
Prashanth -
Customer Analysis Dump - DBIF_RSQL_INVALID_RSQL
Hi all,
when I try to comparison previous period with tcode MCTA (Customer Analysis) the system generate the following dump.
It occurs when I select 2092 Sold-to-party for 1 Sales Office and for 1 month. Since last week it has been working.
The SAP release is ECC 5.0 on SQL 2005.
Runtime Error DBIF_RSQL_INVALID_RSQL
Except. CX_SY_OPEN_SQL_DB
ShrtText
Error in RSQL module of database interface.
What happened?
Error in ABAP application program.
The current ABAP program "RMCV0100" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
Any idea?
Thanks
M.Hi Shahid,
Please refer OSS note:
Note 48230 - Parameters for the SELECT ... FOR ALL ENTRIES statement
which explains the various option to solve your problem.
The dump is occuring because of too many inputs(20000 material number) in the select option.
Please let me know if this helpful, by rating.
Regards
Prashanth -
Short dump (DBIF_RSQL_INVALID_RSQL) during activating ODS
Hello Experts,
I found short dump during activating ODS.
The error message in short dump:
Runtime Error: DBIF_RSQL_INVALID_RSQL
Except.: CX_SY_OPEN_SQL_DB
The termination occurred in the ABAP program "GP7WIVS2MDWGSTMN3ICFDKNAH65" in "ACTIVATE_SIDS".
The main program was "RSODSACT1 ".
I add one InfoObject in the ODS. After activating related objects, I loaded data into the data target.
Data seemed to be loaded correctly, but couldn't be activated.
Any suggestion on this?
-WJ-Hi,
Please chekc the following SAP Notes you will find solution
Note 908599 - Runtime error SAPSQL_INVALID_FIELDNAME during activation
Note 612995 - P13:ODS:Data activation in bckgrnd always ends 'successfully
Note 1175860 - P19: DSO: SDL: Automatic update after activation
Note 1113603 - P17:DSO:Postprocessing ODS - activating and updating
Note 378447 - Correction: hierarchies do not become green
Note 1272738 - P21:DSO: Activation and automatic updating
Note 794584 - P26:Timestamp field empty in RS2NDPROCPROT after ODSACTIVATE
Note 800086 - P26: ODS activation: Status field in table RS2NDPROCPROT
Note 856292 - P28: Automatic functions: No lock obtained for ERSICENQ
Thanks
Reddy -
Dump DBIF_RSQL_INVALID_RSQL using pnp
Hi guys, i have a report which use the logical data base pnp but when it runs on productive enviroment with all personnel numbers it send me this dump: Run-time error "DBIF_RSQL_INVALID_RSQL" occurred, a tried to use a TRY ENDTRY befor the get event but does not accept it before the event....
What can i do to avoid this dump???
Thnks a lot.Thx a lot for reply, i checked the note but it is for release 30 and we are in release higher so basis said that this note is not available any more.... we find this one 1298550 do u think it could solved the problem????
Or do u know another solution???
Edited by: Sandra Torres on Dec 22, 2009 7:56 PM -
RV60SBAT DBIF_RSQL_INVALID_RSQL - ST22 dump using VF06
Hello
We are trying in test system to run a test in VF06 selecting approx
13000 DMR. When we try to run the program, we recieve a dump . Is there a limitation for number of selected DMR, and if so what is the max amount?
Kind regardsCheck these threads
[Error DBIF_RSQL_INVALID_RSQL in R/3|Error DBIF_RSQL_INVALID_RSQL in R/3]
[Reg Blocked Export Documents Runtime Error |Re: Reg Blocked Export Documents Runtime Error]
thanks
G. Lakshmipathi -
GRC 10.1 SP06 - Role sync fails with dump DBIF_RSQL_INVALID_RSQL
Hi!
We're experiencing an issue with the repository sync job for one connector. When selecting the full option, the sync for users and profiles report success but for the role sync we get the error "Error in RFC; 'Error in module RSQL of the database interface'" and a dump is generated in the back-end ( DBIF_RSQL_INVALID_RSQL) with the program /GRCPI/CL_GRIA_ROLE===========CP
The problem occurs in the sentence:
>>>>>
SELECT agr_name parent_agr FROM agr_define
"#EC CI_SGLSELECT
84
INTO TABLE lt_derived
85 *
WHERE agr_name IN it_incl_role
86
WHERE agr_name IN lt_incl_role
87
AND ( change_dat GE iv_update_date OR
88
( create_dat GE iv_update_date AND change_dat = '00000000' ) ).
We've tried working with the parameter 1122 (Batch size for Role sync) switching it to different values like 500, 100, 50, 10 and even 1 but the error still persists.
Synch for another connector with the same GRC System works fine.
any idea?
Thanks,
Diego.Sounds like an old foe from 10.0
http://service.sap.com/sap/support/notes/1632421
You may have to ask SAP to make a 10.1 version of this fix for you to apply to the plug-in system.
There is a specific note for this issue in both 10.0 and 10.1, but it is part of 10.1 SP01 (you are on SP06)
http://service.sap.com/sap/support/notes/1803121 -
Dump : Runtime Errors DBIF_RSQL_INVALID_RSQL
Hi Experts,
I got a dump at the select statement in the production during the excution.The Details of the program are :
DATA : BEGIN OF it_ekko OCCURS 0.
INCLUDE STRUCTURE ekko.
DATA : END OF it_ekko.
START-OF-SELECTION.
SELECT * FROM ekko
INTO TABLE it_ekko
WHERE ebeln IN p_ebeln
AND aedat IN p_aedat
AND bsart IN p_bsart
AND lifnr IN p_lifnr.
In ST22, the description of dump details is as follows.
<b><u>What happened?</u></b>
Error in ABAP application program.
The current ABAP program "ZMMRP126_1" had to be terminated because one of the statements could not be executed.
This is probably due to an error in the ABAP program.
<b><u>Error analysis</u></b>
An exception occurred. This exception will be dealt with in more detail
below. The exception, assigned to the class 'CX_SY_OPEN_SQL_DB', was not
caught, which
led to a runtime error. The reason for this 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.
<b><u>Source Code Extract</u></b>
001830
> SELECT * FROM ekko "read through purchase orders
001850 INTO TABLE it_ekko
001860 WHERE ebeln IN p_ebeln "for order number
001870 AND aedat IN p_aedat "created date
001880 AND bsart IN p_bsart "document type
001890 AND lifnr IN p_lifnr.
001900
001910 LOOP AT it_ekko INTO ekko.
001920 PERFORM process_items. "read, check and save line items
001930 ENDLOOP.
<b><u>Contents of system fields</u></b>
SY field contents..................... SY field contents.....................
SY-SUBRC 0 SY-INDEX 0
SY-TABIX 1 <b>SY-DBCNT 69682</b>
SY-FDPOS 0 SY-LSIND 0
SY-PAGNO 0 SY-LINNO 1
SY-COLNO 1 SY-PFKEY
SY-UCOMM SY-TITLE Purchase Order Receipt Status
SY-MSGTY I SY-MSGID SF
SY-MSGNO 616 SY-MSGV1 5000098347
SY-MSGV2 SY-MSGV3
SY-MSGV4
Kindly help me to solve out this issue.
Thanks & Regards,
Krishna Kishore .Khi,
I think you declared p_ebeln as parameter and used in where condition with IN operator.
Could you change with EQ operator.
Or If p_ebeln is select-oprions means check you are giving high range in the selection screen for the input values.
try to check by giving 1 purchase order i.e p_ebeln = 'XXXX' only.
dont give range.
If output is big range means program goes to dump.
are you trying to modify EKKO table in the program?
Please reward if its useful.
Thanks
Sivaparvathi
Or -
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 135Hi Balaji,
Here is what the dump said and my answers are right below them.
<i>Possible errors:</i>
o The maximum size of an SQL statement has been exceeded.</i>
This may not be the reason in your case. This usually happens when you use the option FOR ALL ENTRIES
<i>o The statement contains too many input variables.</i>
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.
<i>o The space needed for the input data exceeds the available memory.</i>
If the above changes are made and the problem is still there, then this is the next thing to look at.
Srinivas -
DBIF_RSQL_INVALID_RSQL Error while activating the ODS Object
Hello BW Friends,
We have used the Extractor 2LIS_11_VAHDR and enhanced and coded the user exit to extract the data to the required field. Extractor is working fine and able to get the records but when we tried to schedule a data load in BW the request was shown green in the ODS and when saw it in monitor it is still yellow and zero in PSA and the processing hasn't completed. When i tried to activate it manually there is a short dump generated with this error, DBIF_RSQL_INVALID_RSQL. If any one of you has encountered same problem please let us know. Appreciate your prompt response on this.
Regards,
RajeshRaj,
I misunderstood your question.... check whether source system job is processing or not? what about any blocked TRFC'sin SM58.
try to find root cause... ODS activation is not a problem... load is not finished you tried to acivate the request still in the process Yellow.
try to check in Monitor details tab page messages...
All the best.
Regards,
Nagesh Ganisetti.
Message was edited by: Nagesh Ganisetti
Message was edited by: Nagesh Ganisetti
Maybe you are looking for
-
Error message in ME22n transaction
Hi All, We want to display error message at status bar of me22n transaction for some certain conditon.I am using a user exit where actually i am writing a code.I tried to write like this 'Message E101(ZE) ' but message is not displaying at status
-
What is a 'Library Unit'?
Can somebody point me at a definition please? this is in the context of DBMS_PROFILER. If only captures Library Units which a procedure is. But I want to capture SQL built and executed via a client application (we are using ODP.Net). Basically do wha
-
Pre ordered album is available, but can't find it in the downloads section on ipad 2
The new album by coldplay is released and I received an e-mail with a download link. If Infollow the link on my ipad, it says to check the downloads section, but the album isn't there...
-
for many years i developed using ASP, and for several years now have been developing in PHP exclusively, leaving the days of ASP behind. PHP is great, however, it seems most well payinig jobs are either java or asp.net based. I was looking for opinio
-
How can I reset my phone all setting and data off iphone 4without passward
how can I reset my phone all setting and data off iphone 4without passward