Proxy- JDBC Scenario

On running Proxy-> JDBC Scenario
i found out that no data is being passed through the Communication channel for this scenario ( but for another scenario also i am using the same communication channel, there it is passing the data ) but i can see the data in SXMB_MONI of XI.
Don't know where is the issue..?
Regards,

Hi Guys,
Finally i resolved ..
Since for the sender data type(and hence msg type,and also i was using that for proxy generation) i was not using the namespace but was using the namespace for receiver side..
At the time of message mapping message types were also mapped..but since no namespace was coming from Sender Message ..so it was throwing the error in RWB..
Hope it will help others also..
Regards,

Similar Messages

ABAP Proxy - JDBC scenario - checking condition insert_count

Hello,
I'm still fresh to XI topics and I'm supposed to do the scenario that sends data using JDBC
My scenario mapping is as follows:
1) Delete tables A and B
2) Insert table A and B
3) if step 2 is sucessfull Insert table C
I know what to do till step 2) according to help: http://help.sap.com/saphelp_nwpi711/helpdata/en/44/7b7171fde93673e10000000a114a6b/frameset.htm
I have message mapping that triggers DELETE(1) and INSERT(2) but I do not know implement step 3
I know only that it is saved in <insert_count>count</insert_count> but have no idea how to use it?
Should I
1) do new mapping and integrate it in BPM Process
2) is it possible to solve all 3 points in one mapping?
Any ideas, any detailled steps?
Thank you very much in advance

you can use a bpm in which you can check the response message of step two for the insert_count value and then proceed with another step to do the further processing.

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.

PROXY TO JDBC scenario

Hi All,
I am working on PROXY to JDBC scenario upto yesterday its working fine.
Today I, am getting "Time limit exceeded" error in QRFC monitoring and message showing with GREEN COLOUR FLAG (RECORDE) in PI SXMB_MONI.
Please help me to salvoes this error.
Thanks and Regards,
MFH

Hi All,
First of all thanks for all your early replays....
"TIME LIMIT EXCEEDED" QRFC Problem is indicates that when we processing large volume of messages to external or internal systems in this case specified time limit in SM59 is not enough to process the message so that please increase TIMEOUTS...TIME LIMIT EXCEEDED error will be solved.
With Regards,
MFH

Two Receiver DB in Synchronous Proxy to JDBC Scenario?

Hey,
Is it possible to develop a synchronous proxy to JDBC Scenario that have two different DBs as Receiver?
The response Datas are insert_count and update_count.
Thank.

Park,
You can't have more than one receivers in Sychronous case. If you designed the scenario , then u will get the error as "TOO_MANY_RECEIVER CASE_BE".
-raj.

Proxy to JDBC scenario need dynamic sql query for sender .

Hi Experts,
I am developing proxy to jdbc scenario. in this i need to pass dynamic sql query whre we are passing classical method like below.
while we are passing select stmt in constant and mapped with access field and key field mapped with key field.
MY requirement is like instead of passing select stmt in constant where i can generate dynamically and passed in one field and mapped with access field.

Hi Ravinder,
A simple UDF or use of graphical mapping functions in most cases should provide you everything you need to construct a dynamic SQL statement for your requirement.
Regards,
Ryan Crosby

Synchronous Proxy to Synchronous JDBC scenario

Hi,
I have a scenario for a synchronous PROXY to a synchronous JDBC scenario. I have set 4 message types .
MT_PROXYOUT u2013 o/b synch with a response MT_PROXYIN
MT_JDBC - i/b synch with a response MT_JDBC_RESPONSE
I then set up an interface mapping for both the request and response message interfaces. The design looks good but I got stuck in the configuration part.
Since itu2019s a proxy sender, the sender agreement is not needed(Correct me if I am wrong). In the interface determination, there is provision for only the inbound interface which in case would be the JDBC (request/response) back to the proxy and the interface mapping is applied.
So do I need just one interface determination from the proxy as sender and jdbc as receiver and also one receiver determination again with the proxy as sender and the jdbc as receiver. I am confused here because when I try to create a receiver determination for the response back from JDBC to proxy receiver , the interface mapping comes blank. Is it taken in account by the single receiver determination in synchronous to synchronous scenarios??
Teresa

Hi Teressa,
Java Proxy to Synchronous JDBC scenario and SAP XI:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a068cf2f-0401-0010-2aa9-f5ae4b2096f9
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f272165e-0401-0010-b4a1-e7eb8903501d
ABAP proxies-
Client proxy:
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
Server Proxies
/people/siva.maranani/blog/2005/04/03/abap-server-proxies
Cheers
Sunil

MAPPING.NO_MAPPINGPROGRAM_FOUND in JDBC Scenario

I have the problem:.
The scenario I have is Abap Proxy -> JDBC asynchronous, configure everything you need and the system threw me no errors. But when running the interface the system tells me the following error:
System failure
<s:SystemError <detail> xmlns:s="http://sap.com/xi/WebService/xi2.0"> <context> </ context> <code> MAPPING.NO_MAPPINGPROGRAM_FOUND </ code> <text> Mapping program is not available in runtime cache: Software Component Object ID B860572FD3AB3E9DA790882F58DE9DB2 30EF63B07D6811DF9B05E70FC0A90D2F </ text> </ s: SystemError> </ detail>
I followed all the instructions and notes OSS forums and I could not solve the problem:
Refresh all the objects
Java cache refresh yourself
CPA Refresh cache
Refresh cache for that specific object
Server Restart
The most strange thing is that while SAP PI the message is marked as an error in the database data is updated correctly.
Regards,
Johnny

Hi,
I've completed all the checks you have recommended me. Delete everything and
create new objects and still get the same error.
Check SMX_MONI trx and saw two things that caught my attention:
The Request Message Mapping ProcessingMode says he is syncronous,
but the two services interfaces are asyncronous.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SOAP:Header>
- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>SystemError</SAP:MessageClass>
<SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
<SAP:MessageId>00505683-6B63-1DDF-A08C-F62E9AE3367A</SAP:MessageId>
<SAP:RefToMessageId>00505683-6B63-1DDF-A08C-F62E9AE1F67A</SAP:RefToMessageId>
<SAP:TimeSent>2010-06-25T14:41:13Z</SAP:TimeSent>
The trace section at the end of XML, mentions that "Interface
mapping has no response mapping, but not in the services interfaces
I have as a response set because, as mentioned above all
scenario is asyncronous.
<Trace level="1" type="B" name="PLSRV_MAPPING_RESPONSE" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV" />
- 
<Trace level="1" type="T">Interface mapping has no response mapping</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
</Trace>
<Trace level="1" type="T">An Exception has occured</Trace>
<Trace level="1" type="T">Error Text: Mapping program is not available in runtime cache: Object ID 7CDFBA22E91535FDAFBD39466BC4C3D4 Software Component E4E4CB0073F711DFA67BD407C0A90D2F</Trace>
<Trace level="1" type="T">SystemError message generated. Guid: 005056836B631DDFA08CF62E9AE3367A</Trace>
<Trace level="1" type="T">Error during execution of message : C780BD7A27F24B60024EB6BD2BF1AEF9</Trace>
<Trace level="1" type="T">ApplicationMessage was (=RefToMsgId): 005056836B631DDFA08CF62E9AE1F67A</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>
Regards,
Johnny

Jdbc scenario .. where to find the error msg

Hi,
I am working on a scenario,
abap proxy->jdbc adapter->MsSql server.
Whle testing,
i sent the payload xml from the sproxy test sceen.
After that, i checked the "Monitor for processed xml messages" screen (SXI_MONITOR).
There it shows the status "Processed successfully" for the message that i sent.
But when i checked the sqlserver database, the record is not inserted.
Where can i find, if anything gone wrong at Jdbc adapter, or there after.
Thanks in advance,
Ganesh

Hi
apart from this communication channel you can see the message in adapter engine
to do this take the id of the message fromSXI_MONITOR
then go to transaction sxmb_ifr
inside this go to message Monitoring
under drop down select adapter engine and inside the window give the iD of your message which you have taken from MONI
if you are not getting the filter for message ID then click on additional filter and give the iD
after this you can see your message
select the radio butten inside your message and click on details
here you will get the log of each and every step which have been followed in processing the message and you can find the error exactly
regards
sandeep
If helpful reward points

Proxies to jdbc scenario help...!

Dear All,
I am very new to XI , can anyone guide me step by step process for
1. File to webservice scenario via xi
2. Proxies to jdbc scenario via xi
3.IDOC to JDBC scenario via xi
will be much helpful as i need to complete these processes very soon.
Thanks in Advance.

HI,
Here are the documents:
Webservice scenario:
these 3 documents should explain it all,
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/befdeb90-0201-0010-059b-f222711d10c0
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5f3ee9d7-0901-0010-1096-f5b548ac1555
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d23cbe11-0d01-0010-5287-873a22024f79
troubleshooting SOAP:
/people/varadharajan.krishnasamy/blog/2007/01/09/troubleshooting-soap-message--xi
IDOC and JDBC Scenarios:
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters --> For Idoc sender: IDOC -file
/people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30 --> for jdbc receiver: file -JDBC
IDOC configuration :
Refer the help:
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi - ALE settings for R3-XI
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd1539
Idoc to File:
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
This is expalined both the scenarios:
Please follow the below process for configuration:
Pre-requisites for Inbound IDoc to R/3 from PI:
Configuration required at Xi side:
Go to IDX1: configure the port.
Go to IDX2: load the DOC metadata.
Go to SM59: Create RFC destination which points to R3 system this is require in the case where your IDOC is sent to R 3 system,
Configiration required at R3 side:
Maintain Logical System for PI (SALE transaction):
Maintain Partner Profile for XI system(WE20):
Pre-requisites for Outbound IDoc from R/3 to PI:
Configurations required in R/3:
Maintain Logical System (SALE)
Define RFC Destination (SM59) which points to PI system
Maintain Port (WE21)
Maintain partner profile. (WE20):
Maintain Distribution Model (BD64):
JDBC:
Receiver JDBC scenario MS access - /people/sameer.shadab/blog/2005/10/24/connecting-to-ms-access-using-receiver-jdbc-adapter-without-dsn
Writing Stored Procedures-
/people/siva.maranani/blog/2005/05/21/jdbc-stored-procedures
http://www.ics.com/support/docs/dx/1.5/tut6.html
/people/sriram.vasudevan3/blog/2005/02/14/calling-stored-procs-in-maxdb-using-sap-xi
http://www.ics.com/support/docs/dx/1.5/tut6.html
http://java.sun.com/docs/books/tutorial/jdbc/basics/sql.html
http://www.sqlteam.com/article/stored-procedures-an-overview
Proxy:
Client Proxy:
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
Server Proxy:
/people/siva.maranani/blog/2005/04/03/abap-server-proxies
Smarter Approach for coding ABAP Proxies
/people/sravya.talanki2/blog/2006/07/28/smarter-approach-for-coding-abap-proxies
File to Inbound Proxy:
/people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy
How do you activate ABAP Proxies?
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
Debugging Inbound Proxy:
/people/stefan.grube/blog/2006/07/28/xi-debug-your-inbound-abap-proxy-implementation
Thanks and Regards,
Chirag Gohil

Proxy -jdbc

Have a sync proxy to jdbc scenario. Wanted to understand , if in database a table is created ,can pi pull a table via a stored procedure in one shot and pass to a proxy as a table ?
basically a request will go as a proxy request for some records which stored procedure computes. but these records can be of thousands of line items,so was wondering how to pull this data in one shot via pi and send to proxy as response.i thought passing table would be easier although am not sure.
If someone could post some suggestions ,would be appreciated.
thanks
Edited by: xi project on Jul 14, 2010 5:01 AM

Hi,
In the sender JDBC comm. channel under the processing tab you have to specify the Query SQL statement to retrieve the data from the database based on some condition depending upon your requirement
Example
Select * from tableName where ..some condition.
along with other mandatory details in the processing tab.
and As your scenario is Synchronous JDBC to Proxy ,you have to use BPM.
refer my reply in this thread XML file to Proxy Scenario with BPM - ID Steps
where I have specified the steps that I have followed for JDBC to Proxy sync scenario.

XI idoc-jdbc scenario in details

Hi Experts,
Please provide me this scenario pn detail.
Cheers
Aman

Hi,
For IDOC to JDBC scenario:
Refer the below weblog for help:
/people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30 --> for jdbc receiver: file -JDBC
1) First you need to install the JDBC drivers on XI server refer the below link for installation process.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3867a582-0401-0010-6cbf-9644e49f1a10
2) You need to do the IDOC configuration at R3 as well as at Xi end:
Refer the below configuration steps:
ALE configuration for pushing idocs from SAP to XI
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
IDOC testing using WE19
/people/sameer.shadab/blog/2005/07/25/reposting-idocs-instead-of-recreating--for-testing-purpose-xi
Pre-requisites for Outbound IDoc from R/3 to PI:
Configurations required in R/3:
Maintain Logical System (SALE)
Define RFC Destination (SM59) which points to PI system
Maintain Port (WE21)
Maintain partner profile. (WE20):
Maintain Distribution Model (BD64):
Configuration required at Xi side:
Go to IDX2: load the DOC metadata.
3) For updating the table you need to write the stored procedure:
Refer the below link for stored prcedure.
JDBC:
Receiver JDBC scenario MS access - /people/sameer.shadab/blog/2005/10/24/connecting-to-ms-access-using-receiver-jdbc-adapter-without-dsn
Stored Procedures-
/people/siva.maranani/blog/2005/05/21/jdbc-stored-procedures
http://www.ics.com/support/docs/dx/1.5/tut6.html
/people/sriram.vasudevan3/blog/2005/02/14/calling-stored-procs-in-maxdb-using-sap-xi
http://www.ics.com/support/docs/dx/1.5/tut6.html
http://java.sun.com/docs/books/tutorial/jdbc/basics/sql.html
http://www.sqlteam.com/article/stored-procedures-an-overview
Thnx
Chirag
Reward points if it helps and close the threads.

Pass system ack of JDBC adapter to ERP in IDoc - XI - JDBC scenario

Dear all,
i have an IDoc -> XI -> JDBC scenario (without using ccBPM). In the standard way the ERP system, sending the IDoc waits for an application acknowledgement. However the JDBC adapter is only capeable to send system acknowledgements.
Is there a way to pass these acknowledgements to the IDoc status record?
In help.sap.com (http://help.sap.com/saphelp_nwpi71/helpdata/en/ab/bdb13b00ae793be10000000a11402f/frameset.htm) under "IDoc Processing with the IDoc Adapter " there is a table that maps XI system/applic acknowledgement to IDoc status. So in my opinion the status record of my IDoc should at least chenge to the corresponding status for the system ack.
Can anyone tell, if this is really working? What if I deactivate the acknowledgement request in the NOALE programm?
In any case, can I achieve to transfer the system ack to the IDoc status without using a ccBPM?
Many thanks and best regards
Florian

Is there a way to pass these acknowledgements to the IDoc status record?
Without BPM, No.
So in my opinion the status record of my IDoc should at least chenge to the corresponding status for the system ack.
The ack referred here is related to idoc status whether it is properly reached till XI or not and not related to the JDBC ack.
What if I deactivate the acknowledgement request in the NOALE programm?
Then u won't have any ALEAUD message at sender R3.
In any case, can I achieve to transfer the system ack to the IDoc status without using a ccBPM?
No
Regards,
Prateek

Problem in JDBC to JDBC scenario

Hello all,
I am working on a JDBC 2 JDBC Scenario.
Everything gone fine, data is picked from source, but it is not updated in the destination.
I could not see any message related to this in SXMB_MONI it shows only messages related to IDOC, on search I fould, we need to add trace level,etc in SXMB_ADM but still couldnot found any message (I restarted the system, cleared cache also).
In RWB(communication channel monitoring) I could find that sender is sucessful, but no message for receiver.
In RWB (message monitoring) I checked my business system, i could see sender entries but no receiver entries, there is only one error message as :
<b> transmitting the message to endpoint http://xisystem:50100/sap/xi/engine?type=entry using connectio</b>
For which I found we need to change XI businesssystem's pipeline port no from some 54+++ to 4+++ (but I could see only 50100 in the pipeline so i did'nt)
we are using R/3, was7.0 sp11,XI3.0,
Can any body help me in this regard
Thanks,
Sai.k.k

Hi,
Error in SXMB_MONI :
com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_JDBC2JDBC_MM_: RuntimeException in Message-Mapping transformatio~
Error in Integration repository when I test with the payload :
<pre>
13:01:52 Start of test
Document start
Start tag [ns0:Receiver_JDBC_MT]
Add raw attribute [ xmlns:ns0="http://xyz.com/JDBC2JDBC_NMSP"]
Start tag [Statement]
Start tag [dbTable]
Add attribute: [action]=[INSERT]
Start tag [table]
Put value [Example]
Close tag [table]
Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)com.sap.aii.utilxi.misc.api.
BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException:XML Declaration not allowed here.(:main:, row:1, col:8)
at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:157)
at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73)
at java.lang.Thread.run(Thread.java:534) Root Cause: com.sap.engine.lib.xml.parser.NestedSAXParserException:Fatal
Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)(:main:, row=1, col=8) ->
com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)
at com.sap.engine.lib.xml.parser.XMLParser.scanPI(XMLParser.java:2126)
at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2774)
at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830)
at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261)
at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)
at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155)
at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73)
at java.lang.Thread.run(Thread.java:534) -
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155)
at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73)
at java.lang.Thread.run(Thread.java:534) Caused by: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)
at com.sap.engine.lib.xml.parser.XMLParser.scanPI(XMLParser.java:2126)
at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2774)
at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830)
at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261)
at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)
at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) ... 4 more Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)
13:01:52 End of test
</pre>
Query : Select * from Employee fetches all the fields
Payload :
<pre> <?xml version="1.0" encoding="utf-8" ?>
- <resultset>
- <row>
<PerNer>t</PerNer>
<Initials>t</Initials>
<Name>t</Name>
<DOB>t</DOB>
<State>t</State>
<Country>t</Country>
</row>
</resultset>
</pre>
Regards,
Sai.k.k

Error"SYSTEM Failure" while testing the RFC in SE37 : RFC to JDBC Scenario

Hi All,
I am doing RFC to JDBC scenario. When I am testing the RFC in SE37 using the RFC destination created in SM59, I get an error "SYSTEM FAILURE".
Please suggest.
Thanks,
Shyam
Edited by: Shyam Sreepada on Dec 18, 2007 5:46 PM

Hi,
You must run RFC with RFC destination in background mode, I suggest to read following post in order to understand it better.
Syntax would be:
CALL FUNCTION func IN BACKGROUND TASK
[DESTINATION <your RFC destination>]
parameter list
http://help.sap.com/saphelp_nw04/helpdata/en/8f/53b67ad30be445b0ccc968d69bc6ff/frameset.htm
If you read it you will find that you can't test it directly from SE37, for this either you need to create dummy ABAP program or another RFC where you will call this RFC with background syntax.
Regards,
Gourav
Reward points if it helps you
Edited by: Gourav Khare on Dec 18, 2007 6:07 PM

Proxy- JDBC Scenario

Similar Messages

Maybe you are looking for