Error Message DBIF_RSQL_INVALID_RSQL

[Former Member]

Hi,

I am enhancing a datasource in BW with some new fields and i have written a select statement for populating the data into the added fields.

SELECT SINGLE PARVW COUNTER PARNR INTO (I_MC18I30HDR-ZZPARVW,

I_MC18I30HDR-ZZCOUNTER,I_MC18I30HDR-ZZPARNR)

from IHPA where OBJNR = I_MC18I30HDR-OBJNR.

when i am checking the syntax check it says no syntax errors found.

when i am trying to execute the datasource in BW it is giving an error DBIF_RSQL_INVALID_RSQL.

I have checked the OSS Notes(35765) for the above error and the solution given in OSS Notes is "With the profile parameter 'rsdb/max_blocking_factor', you can break up the "SELECT FOR ALL ENTRIES IN itab" statement into several smaller statements. The default value for this parameter is 60, i.e. for each set of 60 entries in the 'itab', one SQL statement is generated. To avoid the abend, lower the value of this profile parameter to 30 (or even smaller, if necessary)."

can anybody help me in changing the select statement according to the OSS Notes solution.Where can i find the profile parameter to break the select statements.

Thanks in Advance

Bobby

[Former Member]

Please take a complete look at the dump. There will be other clues in there that will help identify the root cause. Are your source fields and target fields of same length and type?

[Former Member]

Hi Srinivas,

The source fields and target fields are of the same length and the error message in the dump says

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

Thanks,

Bobby

[Former Member]

Can you please post the declaration of your source fields and target fields? You dump information is definitely pointing to the fact that it was not able to move values from the source fields to the target fields. Try the process of elimination to check which of the three fields is causing it. My guess is that it is the counter field, but check it out.

[Former Member]

Data definitions for these fields

PARVW COUNTER PARNR

I_MC18I30HDR-ZZPARVW, I_MC18I30HDR-ZZCOUNTER,I_MC18I30HDR-ZZPARNR