cancel
Showing results for 
Search instead for 
Did you mean: 

JDBC --- >XI --->RFC

Former Member
0 Kudos

Hi,

I have a problem Message mapping of sending the response from Jdbc to RFc

JDBC Sending Back

<StatementName_Response>

<response_1>

<row>

<IPARTID></IPARTID>

<POOLSTATUS/>

<SERIALNUMBER/>

<QUANTITY/>

<LOCATION/>

<ENGINETYPE/>

<CONDITION/>

<ICLASS/>

<TAG/>

<CAVITY/>

<STATUS/>

<ADDITIONALCLASS/>

<ENGINESERIALNUMBER/>

<PERMANENTID/>

<TAGCERTIFICATION/>

<TAGCERTIFICATIONDATE/>

<CYCLESN/>

<TSN/>

<CSO/>

<TSO/>

<CR/>

<WARRANTEEID/>

<CAMPAIGNID/>

<DESCRIPTION/>

<MINIMUM/>

<MAXIMUM/>

<STATIC/>

</row>

</response_1>

</StatementName_Response>

to RFc

xmlns:ns1="urn:sap-com:document:sap:rfc:functions">

<TE_SAP2EAGLE_PART_INVENT>

<item>

<MATNR>fdfdfdf</MATNR>

<ZPOOL/>

<ZLOC/>

<ZQTY/>

<ZMIN/>

<ZMAX/>

<ZSTATIC/>

</item>

</TE_SAP2EAGLE_PART_INVENT>

</ns1:Z_SAP2EAGLE_XMIT.Response>

I have problems with node mapping and i doubt in defining the datatypes.

Can any one help me how to map the response back,if possible any weblog,so that it would be an easy reference for me.

Thank you,

KishoreJ.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

HI Kishore,

You can use the request and response of RFC for the Data types.

For JDBC, use this weblog

/people/siva.maranani/blog/2005/09/16/xi-how-to-on-jdbc-receiver-response

Regards

Vijaya

bhavesh_kantilal
Active Contributor
0 Kudos

Kishore,

Can you explain what you are doing? Are you using a Sender JDBC adapter or are you using a Receiver JDBC adapter in a Synchronous call?

Regards,

Bhavesh

bhavesh_kantilal
Active Contributor
0 Kudos

Kishore,

As you are using a STORED PROCEDURE that returns a response, you will have to mention which of the paramters passed are input parameters and which of the parameters are output parameters. Also, you will have to define the TYPE attribute for each of the fields mentioning the DATATYPE of the field being passed to the Stored Procedure.

From the online help,

<i>The elements within the stored procedure are interpreted as parameters. They can optionally have the attribute isInput=“1“ (input parameter) or isOutput=“1“ (output parameter) or both (INOUT parameter). If both attributes are missing, the element is interpreted as an input parameter. The parameter names must be identical to those of the stored procedure definition.

The attribute type=<SQL-Datatype> , which describes the valid SQL data type, is mandatory for all parameter types (IN, OUT, INOUT).

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 (input and output),CLOB (input and output), CURSOR (output; only in conjunction with the Oracle JDBC driver).</i>

Regards,

Bhavesh