Payload issue in jdbc to proxy scenario

HI Experts,
We have designed a new interface from jdbc to proxy where in it went fine with the design part.
But while testing it the records are pulled by XI but were not posting to ECC.
So when collected the payload to test in mapping I see a red color to the fields in the structure. due to which am not able to get the output in mapping.
Can anyone help me out how to resolve this issue.
Appreciate the quick response.
Thanks and regards,
Ranganath.

Add those Extra fields in your Data type and dont map it with target.
or
In select stataement in sender JDBC adapter mention the fieldname you want to pick
Suppose employee table has 3 field
EmployeeeID,
Employeename
address
but you dont want address field then write the select query like this
Select EmployeeeID, Employeename from employee
mention the table fieldnames in select query which you have in your mapping source structure.
if you are write select * from employee
then address will come as extra field and create problem in mapping
Refer this
http://www.java2s.com/Code/SQLServer/Select-Query/Specificcolumnnamesaredefinedinthequery.htm

Similar Messages

JDBC To Proxy Scenario Problem

Dear All,
I am doing JDBC to Proxy scenario. In SXMB_MONI in XI Message is sucessful and JDBC Adaptor fetching records also. These records are seen in SXMB_MONI.
When I check in SXI_MONOTOR in R/3 , message is sucessful, but payload is Blank. The selected records in JDBC are not reaching R/3 . What may be the problem
Raghvendra

Check the mapping between the JDBC response and the Proxy response in XI?
Does the JDBC response have the valid rows? If yes, check what is the output mapping that is sent to the Proxy.
Regards
Bhavesh

Database error for JDBC to Proxy Scenario

Hello SAP PI Gurus,
I am having a JDBC to Proxy Scenario .And the interface is running at 10 min of duration.
However, my other interface are running fine with the same details.
But for this interface, it giving the belwo error :
Database-level error reported by JDBC driver
while executing statement 'call proc_dtdc_prod_summary'.
The JDBC driver returned the following error message: '
com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: Table
'dtdc_prod_summary_temp' already exists'. For details,
contact your database server vendor.
So increased the time from 10 min to 20 min to 30 min. But the erro remians.
So pls look into this and give your suggestion.
Regards,
Ravi

Hi Ravi,
Please check execution of your stored procedure is resulting with creation of Table : dtdc_prod_summary_temp.
Modify your stored procedure to just fetch records or insert records in the existing table. Or change the code to Create a table 'dtdc_prod_summary_temp only if it doesn't exits in the Table data base.
Regards
Praveen K

Issue in Iodc- abap proxy scenario

Hi all
I have a idoc to abap proxy scenario. The issue is ,
when we send the idoc to client A of target system, it works ifne.
But when we send the saem mesage to Client B, we find a error message in sxmb_moni of Target system. the mesage is Application_fault.
Is it because of any error in XI configuration or somethin else.

hi all
thanks for all your responses.
I forgot to mention that based on a particualr field value in the idoc , it will be routed to eihter Client 100 or 200 .
I gave the conditions in Receiver Determination.
Same Server Proxy is used in both the target business sytems.
I have done all the Configuration Steps ,( Created two separate business systems also )
Also I have checked wiht all the system settings to be made in the target system B.
When i trigger the idoc to Client 100, it goes to XI and then reaches Client 100 of System B
without any problem. I get the desired result from proxy code.
When i send the saem idoc to Client 200, it reaches the target system and routed to client 200. But getting this error message in
the Call Inbound PRoxy step. (from sxmb_moni)
<SAP:Category>Application</SAP:Category>
<SAP:Code area="ABAP">APPLICATION_ERROR</SAP:Code>
Since it reaches the target system correctly, i guess there is nothing wrong in the XI configuration side.
But if its Application fault, how come the same data is processed successfully in one client whereas it thorws error in another.

Mapping issue in jdbc to idoc scenario

Hi
we have a jdbc to idoc scenario , we need to repeat the segment given below which has only two fields FLDGRP and FLDVAL,
both filed_Group and fieldgroup1 is coming simultaneously . when field group =BATCH, batch=FLDVAL and fieldgroup1=CUST cust_code=FLDVAL
mapping is as follows :
E1WXX01 (segment name) occurance 0:9999999999
fieldgroup----
> FLDGRP
batch----
>FLDVAL
fieldgroup1----
>FLDGRP(same filed as above )
cust_code----
>FLDVAL(same filed as above)
pl sugggest how to map using graphical mapping
rgds
arun

I see the problem here... hmmm.. It is simple
You need to just duplicate the E1WXX01 segment by right clicking and pressing Duplicate Subtree.
Once you do duplication of segment then you will have two segments of E1WXX01.
In first segment map
> fieldgroup----
> FLDGRP
> batch----
>FLDVAL
and in second segment of E1WXX0, map
> fieldgroup1----
>FLDGRP
> cust_code----
>FLDVAL
Regards,
sarvesh

JDBC to Proxy scenario

Hi,
Hope you are doing well.
I have a scenario where I need to fetch the data from an Oracle table and pass them on to SAP via proxy. Since, the data to be extracted from the Oracle db is huge, I want to call a stored procedure to fetch the data, and then pass them on in batches of say 100 records at a time to XI. To do this,I believe the stored procedure has to trigger the interface in XI.
I have seen a few blogs stating that a sender JDBC adapter cannot interact with a stored procedure since the latter provides the data in a cursor whereas XI needs the data in record sets.
Then how can I achive my objective? Please provide me some ideas.
regards
Debansu

Bhaskar,
Thanks.
A huge amount of data needs to be fetched from the database (for example say 100000 records). My plan was to use the stored procedure to trigger the XI interface and send the fetched data in batches (say 100 records per batch). How am I going to do this without using a stored procedure? Am I going to use fetch all the data using select statements in XI and then chunk it into messages using UDF in XI? Is there a better way to achieve this? Please suggest.
regards
Debansu

ALE Configurations for JDBC to PROXY scenario

Can some body tell me what are the ALE configurations that needs to be done in both the systems and also in XI system.

Hi there
No need for ALE confihuration unless you are using IDocs in your scenario.
You need to configure the integration engine in the Proxy system using SXMB_ADM and create an RFC for the Integration server.
on the JDBC side you'll need the database bridge configured in the communication chanell...
what is your scenario specific...which system types and versions?
Nimrod

Inbound Proxy Error - JDBC to PROXY Scenario

Hi experts,
I am getting the following error while activating Inbound Proxy.
Error when creating service node. [unknown]You are not authorized to use function Netzwerkadministration
Exception of class CX_SRT_WSP_ICF
Regards,
Sudheer

Hi Experts,
Thank you for your replys.....Problem got solved......:)
Some authorisation was missing...Now it was fine and I can activate Inbound proxy......:)
Once again Thank you for your replys.....:)
Regards,
Sudheer

Issue in Soap to Proxy scenario

I am unable to generate wsdl file in sender agreement in pi 7.1v? If I try to generate, getting error.
How to generate wsdl?

hi,
If we are using sender interface in multiple scenarios at that case we are not providing Software Component version in sender agreement.
u2026u2026u2026u2026u2026u2026.
How to generate wsdl?
Tools -> display wsdl -> provide specified parameters
thanks

SOAP- Proxy scenario, issue with WS adapter

Hi guys,
i've set up a soap->abap proxy scenario (on 7.1) and want to use the new WS adapter. unfortunately I'm facing some issues. The proxy has been generated properly and I also set it up in soamanager. I tested it from XML Spy and it works fine. So there shouldn't be any problem with it.
But when I try to run the scenario, I get following error:
WS_ADAPTER_SYS_ERROR
<sap:ExceptionChain xmlns:sap="http://www.sap.com/webas/710/soap/runtime/abap/fault/system/SystemFault"><sap:ChainedException><Exception_Name>CX_SOAP_FAILURE</Exception_Name><Exception_Text>SRT: Processing error in Internet Communication Framework: ("ICF Error when receiving the response: ICM_HTTP_CONNECTION_FAILED")</Exception_Text></sap:ChainedException><sap:ChainedException><Exception_Name>CX_SOAP_CORE</Exception_Name><Exception_Text>SRT: Processing error in Internet Communication Framework: ("ICF Error when receiving the response: ICM_HTTP_CONNECTION_FAILED")</Exception_Text></sap:ChainedException></sap:ExceptionChain>
System error while calling Web service adapter: <sap:ExceptionChain xmlns:sap="http://www.sap.com/webas/710/soap/runtime/abap/fault/system/SystemFault"><sap:ChainedException><Exception_Name>CX_SOAP_FAILURE</Exception_Name><Exception_Text>SRT: Processing error in Internet Communication Framework: ("ICF Error when processing Web service
I checked the /sap/xi/engine service on both - PI & ECC and it is activated.
Any hint, what could be wrong?
Thanks a lot,
Olian

Hi,
"ICM_HTTP_CONNECTION_FAILED" this error is relaed to ICM. Does your Type H connection "INTEGRATION_SERVER_HMI" works fine.And check integration engine configuration in SXMB_ADM.
And here is a similar thread.
Re: HTTP to Enterprise Services.
Regards,
Reyaz

IS Mapping required in JDBC to PROXY asynchronous scenario?

Hi,
I am working on JDBC to PROXY asynchronous scenario. The scheduled stored procedure fetches the data from database tables and stores them in staging table in the same database. XI will fetch the records via JDBC adapter. Now these records are to be posted into SAP custom table via proxy without any transformation. Now is Message mapping and Interface mapping required in this case?

Hi
I assume that your source and traget structure will be different as you are using JDBC.
SO you will need to create message mapping and operation mapping.
-Deepak.

SOAP - Proxy Scenario

In my SOAP to Proxy scenario I have a proxy that will return "true" or "false" depending on the logic in my method. When I execute the proxy it returns the false value for cases that are false in SAP. The scenario does not return the "true" value when the logic is true in SAP. If I go into SAP and run the method, both the true and the false logic paths work and the method returns the correct value. If I hard code the variable in the method to "test" and execute the XI scenario it will return the word "test" for both cases, true and false. I have the same scenario in my XIQ system and it works fine.
So, what I have done...
I have flushed the cache, that did not work.
I have rebooted my XI system that has the problem.
I have compared my XI broken system with the one that is working and there are no differences.
Does anyone know how I can see what is truely being sent back to the SOAP side? Is there a way to debug the ABAP code from the XI / SOAP side?
Any help would be greatly appreciated.
Thanks
Skip Ford

Hi Ford
When you try with SAP its working right. Did you see that response in XI. If not then no need to touch XI.
Take the payload and try to debug the proxy. You will come to know if it really returns the true value or there is a data issue itself and no problem with XI and SAP.
Check in XI mapping as well. if the value from source is moving to target or not. If you make any changes or found problem do regenerate and activate proxy.
Thanks
Gaurav

SET_PAYLOAD_FAILED error in SOAP to Proxy scenario

Hi PI Experts,
We have an inbound syncronus interface (Non sap system to SAP) using the SOAP to Proxy scenario.
When we test the interface using any soap tool like soapui it is working fine but when the interface is triggered end to end from source system then the below error is getting dispalyed on source system.
500 Internal Server Error
In XI below is the error message -
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">SET_PAYLOAD_FAILED</SAP:Code>
<SAP:P1>IN</SAP:P1>
<SAP:P2>REQUEST</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Internal error when completing the message object (setting the payload, direction: IN message: REQUEST)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can any please let me know what is the issue here?
Appreciate your help.
Regards,
Jitender

We had a similar issue with a Synchronous Interface
The interface worked perfectly when sending the request directly to the integration server, but when sending it using SOAP the issue appeared.
It was very tricky to solve it because we had similar interfaces that worked without any issues.
SOLUTION: Create a new Service interface with a new name different from the one failing. And make sure The Message Types are in the same namespace as the service interface.
Why?:
The issue turned out to be in the sender agreement, and name-spacing issues.
Our Outbound Service Interface belonged to one SWCV and ns, We will call it "ns1:SI_A_OUT".
In PI 7.3, and I believe 7.11 also, the you no longer assign a default interface in the to the SOAP communication channel sender agreement pair.
Therefore the SOAP adapter determines the soap method from the payload. If The internal message type in the soap message belong to different namespace, the the java method getMessage() does not find the correct XML node, therefore does not find the payload.
<"ns1:SI_A_OUT">
...<ns2:MT_element>
getMessage( ns1:MT_element)
We are not sure if the issue is the implementation of the SOAP protocol or in the WSDL generation. But this issues seem to create orphan object during runtime, and even if you re-implement the complete interface, the sender agreement seems to be corrupt.
Therefore the only was we could solve this, was to move our MT to the same namespace as the service interface and rename the interface "ns1:SI_A2_OUT"
Hope this helps someone.
Juan Francisco Zurita Duque
NNIT A/S

Error while executing a JDBC to Idoc scenario : No standard agreement found

Hello SAP PI Gurus,
I am having a JDBC to idoc Scenario .And the interface is running at 10 min of duration.
<SAP:AdditionalText>No standard agreement found for ,
BS_EXT_CTBSREPDB, , BS_ERPQAS_QE1_320, http://XYZ.com/FI/FI_FI_01/Charges, FIDCC2</SAP:AdditionalText>.
While i test the configuration...i get an error in reciever agreement as mentioned above.
Can you pls help me in resolving this issue.
Regards,
Ravi

Hi,
I think the problem is with namespace....for IDOC the namespace will be "urn:sap-com:document:sap:idoc:messages"...but in your case it is different.....i.e http:....etc.....please check whether you 've used the same IDOC withe above mentioned namespace in all the configuration objects like interface determination, receiveragreement etc.....
Thanks
Priyanka

JDBC to Mail scenario with XSLT mapping

Hi all,
I am working on JDBC to Mail scenario. We have to pick the data from Oracle system and mail has to be sent with an attached Excel file.
I am doing this scenario by using of following blog.
eMail Report as Attachment (Excel/Word)
I am getting the output as an attachment but iam not getting the data.
the same xslt coding iam using which has given in blog.
any idea........
Thanks,
Sreedhar Goud.

Hi Gaurav,
JDBC is picking the data.In SXMB_MONI outbound payload iam able to see the data but in inbound payload there is no data.i think the problem is in XSLT code only.
My source structure:
<?xml version="1.0" encoding="utf-8" ?>
<ns:MT_ORMS_Errors xmlns:ns="http://mg.adityabirla.com/mg/orms/mail">
    <row>
        <INTERFACE_NAME>MG_SAP_RMS_ITEM_PKG</INTERFACE_NAME>
        <RECORD_DETAIL>Item</RECORD_DETAIL>
        <ERROR>item</ERROR>
        <CREATE_DATE>2008-11-03 00:00:00.0</CREATE_DATE>
        <MAIL_SENT>N</MAIL_SENT>
    </row>
</ns:MT_ORMS_Errors>
XSLT code:
<?xml version='1.0'?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/>
<xsl:variable name="break"><br></xsl:variable>
<xsl:variable name="tableB"><table></xsl:variable>
<xsl:variable name="tableE"></table></xsl:variable>
<xsl:variable name="trB"><tr></xsl:variable>
<xsl:variable name="trE"></tr></xsl:variable>
<xsl:variable name="tdB"><td></xsl:variable>
<xsl:variable name="tdE"></td></xsl:variable>
<xsl:variable name="nbsp">&nbsp;</xsl:variable>
<xsl:variable name="thB"><tr BGCOLOR="#CCCC99"></xsl:variable>
<xsl:template match="/">
   <ns1:Mail xmlns:ns1="http://sap.com/xi/XI/Mail/30">
    <Subject>Deliveries from XI</Subject>
    <From></From>
    <To></To>
    <Content_Type>application/vnd.ms-excel</Content_Type>
    <Content>
     <xsl:text xsl:space="preserve">These deliveries has been completed:</xsl:text>
     <xsl:value-of select="$break"/>
     <xsl:value-of select="$break"/>
     <xsl:value-of select="$tableB"/>
     <xsl:value-of select="$thB"/>
     <xsl:value-of select="$tdB"/>
     <xsl:text xsl:space="preserve">INTERFACE_NAME</xsl:text>
     <xsl:value-of select="$nbsp"/>
     <xsl:value-of select="$tdE"/>
     <xsl:value-of select="$tdB"/>
     <xsl:text xsl:space="preserve">RECORD_DETAIL</xsl:text>
     <xsl:value-of select="$nbsp"/>
     <xsl:value-of select="$tdE"/>
     <xsl:value-of select="$tdB"/>
     <xsl:text xsl:space="preserve">ERROR</xsl:text>
     <xsl:value-of select="$nbsp"/>
     <xsl:value-of select="$tdE"/>
     <xsl:value-of select="$tdB"/>
     <xsl:text xsl:space="preserve">CREATE_DATE</xsl:text>
     <xsl:value-of select="$nbsp"/>
     <xsl:value-of select="$tdE"/>
     <xsl:value-of select="$trE"/>
    <xsl:for-each select="MT_ORMS_Errors/row">
      <xsl:value-of select="$trB"/>
      <xsl:value-of select="$tdB"/>
      <xsl:value-of select="INTERFACE_NAME"/>
      <xsl:value-of select="$nbsp"/>
      <xsl:value-of select="$tdE"/>
      <xsl:value-of select="$tdB"/>
      <xsl:value-of select="RECORD_DETAIL"/>
      <xsl:value-of select="$nbsp"/>
      <xsl:value-of select="$tdE"/>
      <xsl:value-of select="$tdB"/>
      <xsl:value-of select="ERROR"/>
      <xsl:value-of select="$nbsp"/>
      <xsl:value-of select="$tdE"/>
      <xsl:value-of select="$tdB"/>
      <xsl:value-of select="CREATE_DATE"/>
      <xsl:value-of select="$nbsp"/>
      <xsl:value-of select="$tdE"/>
      <xsl:value-of select="$trE"/>
     </xsl:for-each>
     <xsl:value-of select="$tableE"/>
    </Content>
   </ns1:Mail>
</xsl:template>
</xsl:stylesheet>
Thanks,
Sreedhar Goud.

Payload issue in jdbc to proxy scenario

Similar Messages

Maybe you are looking for