Issue while testing Inbound Client Proxy to JDBC using SP

[Former Member]

Hi All,

I am working on Proxy to JDBC using Stored Procedure scenario.

When i am sending proxy data to the data base,its showing successful in the adapter engine and reciver channel but the data is not getting populated in the target structure.Rather its taking default blank values...

Source side :

<ZDT_CUST_HIER_ECC_4283_REQ_ITE>

<CONTROLLER />

<CUST_LIFE_NO>112244</CUST_LIFE_NO>

<UPDATE_TMS>2012-02-29 22:11:48</UPDATE_TMS>

<ACTION_CODE>A</ACTION_CODE>

<SALES_ORG>CA01</SALES_ORG>

<DIST_CHAN>45</DIST_CHAN>

Target Side:

<Statement>

- <Customer_Hierarchy_TypeG action="EXECUTE">

<table>W2W_sp_InboundTypeGCustHier_CAN</table>

<cust_life_num type="VARCHAR" />

<last_updated_tms type="VARCHAR">1900-01-01</last_updated_tms>

<action_code type="VARCHAR" />

<sales_org type="VARCHAR" />

<dist_channel type="VARCHAR" />

<division type="VARCHAR" />

I think Statement is not mapped to right field...but i dnt know thw right field...

Please help urgently !!!!

[Former Member]

Hi,

Extract the source payload from sxmb_moni and use this XML in the test tool of ESR to check your message mappingIs the result xml correct in this test?

If not, check your message mapping.

REgards,

Carme

[Former Member]

No..its giving error as Cannot create target element - Statement.

[Former Member]

This means your mapping has issues, please check

[Former Member]

Hi,

I am getting the below error:

Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'W2W_sp_InboundTypeGCustHier_CAN' (structure 'Statement'): java.lang.IllegalArgumentException

CAn some one tell what could be the problem???

[rajasekhar_reddy14]

Check your JDBC Receiver structure and compare your table SP input paremeter with receiver strcure and fprovide identical input paramater names in Receiver structure

[Former Member]

there are few things that u can cross check in adition to above suggestions:

1) check whether the order of fields in SP is matching with that mentioned in PI..(AFAIK the sequence should be same)

2) check the date format....i would suggest that execute ur SP standalone and then chk

<UPDATE_TMS>2012-02-29 22:11:48</UPDATE_TMS>