cancel
Showing results for 
Search instead for 
Did you mean: 

DBIF_RSQL_INVALID_RSQL when creating a Purchase Order (ME21N)

Former Member
0 Kudos

Hi,

The system is generating a short dump DBIF_RSQL_INVALID_RSQL when a user tries to create a purchase order.

what could be the cause of this? i have analysed the short dump in st22 and looked at sm21 and st11 and they are giving very little detaill.

Error in the module RSQL accessing the database interface.

What happened?

Error in ABAP application program.

The current ABAP program "SAPLZMM_GET_ACT" 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

"ZMM_GET_ACT_PLN" "(FUNCTION)"

.

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

"ZMM_GET_ACT_PLN"

"(FUNCTION)", 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

"SAPLZMM_GET_ACT" or "LZMM_GET_ACTU01"

"ZMM_GET_ACT_PLN"

-


Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

Wherever you have used SQL statement please do check all the fields here as some of the fields are not in correct order as they are required per the actual table in dictonary, to just verify that you can use addition of "INTO CORRESPONDING FIELDS OF INTERNALTABLE" in your SQL statement as this will not require the fields to be in order but this may cause performance issue.

Thanks and Regards

Sudharshan

Former Member
0 Kudos

Check whether the Tablespace is full for the perticular table where its creating purchase order.