cancel
Showing results for 
Search instead for 
Did you mean: 

RFC to JDBC Sync. Scenario

Former Member
0 Kudos

Hello Guys,

I'm trying to set up a RFC - XI - JDBC Scenario. Where the RFC sends some parameters and the JDBC performs a SELECT Query.

I have a RFC that already was imported with the following definition:

IMPORTING

VALUE(LOGIN) TYPE STRING

VALUE(VIGENCIA) TYPE STRING

EXPORTING

VALUE(LOGIN_RES) TYPE STRING

VALUE(ID_USUARIO) TYPE STRING

VALUE(FECHA_CREACION) TYPE STRING

VALUE(VIGENCIA_RES) TYPE STRING

VALUE(PERFIL) TYPE STRING

I already define the JDBC Request Structure as:

<Statement_Select>

<TableName Action="SELECT">

<Table>USUARIO_WEB2</Table>

<Access>

<ID_USUARIO_WEB/>

<LOGIN/>

<FECHA_CREACION/>

<VIGENCIA/>

<PERFIL/>

</Access>

<Key>

<LOGIN>value1</LOGIN>

<VIGENCIA>value2</VIGENCIA>

</Key>

</TableName>

</Statement_Select>

After testing the RFC I'm getting the following error in the CC monitor:

Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'null' (structure 'LOGIN'): java.lang.IndexOutOfBoundsException: Index: 1, Size: 1

Can anyone please help me with this? I'm not sure where the error migth be.

Thanks!

Felipe

Accepted Solutions (1)

Accepted Solutions (1)

agasthuri_doss
Active Contributor
0 Kudos

Hi,

<LOGIN/> are you passing Null value and check whether you are passing null value to any of the element.

Regards

Agasthuri Doss

Former Member
0 Kudos

Hi Agasthuri,

Yes I'm not passing any value to <LOGIN/> because is a SELECT statement. This is the Request "SELECT" Structure that I'm using. Is there any problem there?

<Statement_Select>

<TableName Action="SELECT">

<Table>USUARIO_WEB2</Table>

<Access>

<ID_USUARIO_WEB/>

<LOGIN/>

<FECHA_CREACION/>

<VIGENCIA/>

<PERFIL/>

</Access>

<Key>

<LOGIN>value1</LOGIN>

<VIGENCIA>value2</VIGENCIA>

</Key>

</TableName>

</Statement_Select>

I'm still with the problem, please help.

Felipe

Answers (3)

Answers (3)

Former Member
0 Kudos

Just check the JDBC request structure...

you should be good

VijayKonam
Active Contributor
0 Kudos

Did you selct replace NULL by empty string in advanced JDBC adapter settings? It looks like the SQL side, the field login is going out of the array limit.

VJ

Former Member
0 Kudos

Hi,

Pls check the column names of your table. Make sure they are spelled correctly and case-sensitive.

All table and column names are case-sensitive.

Regards,

Bill