JDBC Scenario : Stored Procedure Call

[abhradeepbasu]

Dear Experts,

We are currently working on a Proxy to JDBC scenario where we need to call to a stored procedure. The stored procedure has an input parameter which is basically a table type. I have tried with many combinations to pass the records as table type but still no success. Please help.

_AB

[Former Member]

Hi Basu,

Is the table data  type defined only in Stored Procedure and what value it is expecting

[iaki_vila]

Hi Abhradeep,

I agree with Bhavesh, in your case i usually talk with the DB to wrap the stored procedure with another that works with longvarchar length 16,777,215 bytes (varchar is 65,535 bytes).

Regards.

[bhavesh_kantilal]

I am not much of a expert on how Table Parameters on JDBC Stored Procedures work but as per SAP Help the only supported types are as below.

Defining XML Documents for Message Protocol XML SQL Format - Advanced Adapter Engine - SAP Library

The following SQL data types are supported: INTEGER, BIT, TINYINT, SMALLINT, BIGINT, FLOAT, REAL, DOUBLE, NUMERIC, DECIMAL, CHAR, VARCHAR, STRING, LONGVARCHAR, DATE, TIME, TIMESTAMP, BINARY, VARBINARY, LONGVARBINARY, BLOB (output only),CLOB (output only).

To me it seems like this might not be supported and other alternates would need to be looked at!

Regards

Bhavesh

[former_member187587]

Which type of database vendor you are using?

Try to export an XSD of this sp and import it as an external definition.

[former_member190293]

Hi Abhradeep!

I think that the most preferable way in your case would be to create temporary table on DB side, store your table data in that table and than call stored procedure which will read the data from that table and remove it after reading.

Regards, Evgeniy.

[Harish]

Hi,

Please refer the below blog

regards,

Harish

[abhradeepbasu]

Hi Harish,

Our stored procedure is at receiver end where we need to pass the records as an input (table type) followed by it will execute the business logic.

Gone through the blog you mentioned where Michal commented as below:

We are using MySQL here.