RFC to Jdbc Synch Scenario

Hi,
I have a scenario like RFC to JDBC synch scenario, so what would be the QOS for sending( RFC) communication channel and as well as JDBC communicaiton channel.
Thanks n Advance.,
Xeon

Hi,
Neither the Sender RFC adapter nir the Receiver JDBC adapter provide the option to select the QOS.
In your case if the report triggering the call to XI is making a Synch Call then the QOS in the SOAP header will be BE. If the Inbound Interface for the Receiver JDBC adapter is also a Synchronous Interface the QOS is taken as BE for the Receiver JDBC adapter.
You need not manually change the QOS anywhere as long as you are using Synch message interfaces.
Regards
Bhavesh

Similar Messages

Error in SAOP adapter : RFC to SOAP Synch Scenario

Hi Experts,
Scenario is "RFC to SOAP Synch".
For creating this following this link : **************** - Scenario on RFC to SOAP
Trying to send XML to SOAP receiver.
Using Below details for SOAP:
Website : http://www.webservicex.net/WS/WSDetails.aspx?WSID=59&CATID=4
Target URL : http://www.webservicex.net/SendSMS.asmx?WSDL
SOAP Action: http://www.webserviceX.NET/SendSMSToIndia
But when I try to send showing this error:
"Error in processing caused by: com.sap.aii.af.lib.mp.module.ModuleException: call to messaging system failed: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIAdapterFramework:GENERAL:com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: unable to create a socket".
Any one please suggest how resolve this issue?
Is there any setup necessary in PI server to send message through SOAP?
Thanks,
Arthita

Is there any setup necessary in PI server to send message through SOAP?
No
Solution
Check if there are any firewall rules in place which are restricitng the PI system to connect with the URL
: http://www.webservicex.net/SendSMS.asmx?WSDL
Suggestion
Copy paste this URL in browser and verify if it is accessible
Sourabh

RFC to JDBC Sync Scenario and get JDBC response

Hi All,
We need to create RFC to JDBC synchronous interface with update_insert action.
And we need to get the number of records updated or inserted as response and map the response and send it back to ECC as RFC response mesg.
I have gone through the help document on JDBC and it says :
The response document has the following format; one of the two values is always 0 because either an UPDATE or an INSERT action is always executed:
<update_count>count</update_count>
<insert_count>count</insert_count>
Now following is the question: Is this this the standard feature? Because in our case Database side they will not be sending any response back.
So with the synchronous receiver JDBC channel would we get this update and insert count as response by default?.
Please help with replies.
Thanks,
Jane

Hi Jane
No setting needs to be done by the Database team, it is a standard feature.
Whenever you insert or update records in DB using the JDBC Adapter, you will get the response with the count.
If insertion fails due to some reason in JDBC Adapter, then there will be no response.
Regards
Osman

RFC to JDBC Synchronous Scenario

Hi,
I have to configure a scenario in which by an RFC call we have to select records on a DB table and return them to the RFC as resultset. I'm not using any BPM.
So I've developed all the design objects like:
- MT : MT_Request; MT_Response
- MI : MI_Synch_Inbound with MT_Request, MT_Response end FM ; MI_Asynch_Outbound with MT_Response
- MM : MM_RFC_to_Request (from RFC to MT_Request ); MM_Response_To_RFC (from DB table response to RFC)
- IM : IM_RFC_to_JDBC (from RFC to MI_Synch_Inbound with the 2 MM in request/response tabs)
Also I have a JDBC CC Receiver Synch to perform the Select stm.
My doubt now is: which configuration objects I have to configure ?
The RFC Adapter needs 2 communication channels (Sender Asynch and Receiver Asynch) or only one Synch?
Thanks to all,
GB

Dear all,
I've created all the required configuration objects in ID:
RFC CC sender, JDBC CC receiver, sender agreement , reciever determination, interface determination, reciever agreement.
But when I run RFC called in background task by a report, I obtain only one message into SXMB_MONI, the one that contains the RFC output. In addition it's not visible into moni the Message Mapping execution.
Instead if I remove the background task mode I obtain no message in moni.
Any ideas?
Thanks,
Gianluca

Problem with Stored procedure in JDBC Synch scenario

Hello Experts,
I am working on the scenario which is from HTTP <-> to <-> JDBC. It is a synchronouse scenario. We are using Stored procedure in this scenario.
1) Please send the response structure for it.
2) here when i am sending request to the Database it is giving me below error :
Delivery of the message to the application using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'TCS.PKG_BMF_MANAGE_SERVICE_DATA.PROC_GET_ACTIVE_MF_ESIIDS' (structure 'statement'): java.sql.SQLException: Oracle CLOB Helper: java.lang.AbstractMethodError: java/sql/Clob.setString(JLjava/lang/String;)I. Setting message to status failed.
One of the field in Database stored procedure is of type CLOB. So can you ppl guide me that what might be the solution for this.
Any help appriciated.
Thanks,
Hetal

I am using Stored procedure and that is working fine in Oracle
This is my XI Request structure :
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:read_PROC_GET_ACTIVE_ESIIDS xmlns:ns0="http://reliant.com/xi/BMFR2">
- <statement>
- <PROC_GET_ACTIVE_ESIIDS action="EXECUTE">
<table>TCS.PKG_BMF_MANAGE_SERVICE_DATA.PROC_GET_ACTIVE_MF_ESIIDS</table>
<in_bmf_partner_id isInput="true" type="VARCHAR">994</in_bmf_partner_id>
<in_esids isInput="true" type="CLOB">1008901001155950587100:1008901001155950545100:1008901001155950671100:1008901001155950114100</in_esids>
</PROC_GET_ACTIVE_ESIIDS>
</statement>
</ns0:read_PROC_GET_ACTIVE_ESIIDS>
This is oracle Stored procedure signature :
PROCEDURE PROC_GET_ACTIVE_ESIIDS
in_bmf_partner_id           IN   kss_activity_stg_curr_stat.BMF_PARTNER_ID%TYPE,
in_esids                    IN   CLOB,
out_recordset               OUT sys_refcursor
Let me know if you need any further information.
Thanks,
Hetal

Error while executing the SOAP-XI-JDBC(syn) scenario

Dear Forum,
We have done SOAP-XI-JDBC(synch) scenario with out BPM.
When we sent the request data from EP to Oracle database through XI, we got an error,Runtime in Message-Mapping transformation~.
com.sap.aii.utilxi.misc.api.BaseRuntimeException: Runtime in Message-Mapping transformation: Cannot produce target element /ns:Customer/customers. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:291)
Exception message says that it is a mapping issue. But we got the responce data from database along with this message.In message monitoring we got the message processed successfully.
Now i am not able to understanding why it throughs an error Runtime in Message-Mapping transformatio~ first time ?
Pls revert me to fulfill this task successfully.
Points will be rewarded.
Regards,
Naresh

Dear Friends,
Sorry for the delay,and Thank you for your quick responce.
Yes I got that message under trace option in SXMB_MONI,
Pls find the following msg structures and if any error please let me know status...
Soap request structure:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://soap2dbns" targetNamespace="http://soap2dbns">
<xsd:element name="soap_reqmt" type="soap_reqdt" />
<xsd:complexType name="soap_reqdt">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
5b474a34c8a511dc8d8e001a4bf038d4
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="Request" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
49b1ae20c81211dcce03001b78afb958
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ORDERID" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
49b1ae21c81211dcc20d001b78afb958
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Operation" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
49b1ae22c81211dc858a001b78afb958
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
Data base request structure:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://soap2dbns" targetNamespace="http://soap2dbns">
<xsd:element name="db_reqmt" type="db_reqdt" />
<xsd:complexType name="db_reqdt">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
5b4e7620c8a511dcc4fe001a4bf038d4
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="STATEMENTNAME" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
fa204eb0bceb11dcbb54001b78b0798a
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="FETCHDATA">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
fa204eb1bceb11dc9750001b78b0798a
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="TABLE" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
fa204eb3bceb11dccc94001b78b0798a
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="access">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
fa204eb4bceb11dc9b35001b78b0798a
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ORDERID" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
fa204eb5bceb11dca20a001b78b0798a
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ITEM" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
d0279840c81011dc8e4e001b78afb958
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="QUANTITY" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
d0279841c81011dcb8f4001b78afb958
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="PRICE" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
d0279842c81011dc832f001b78afb958
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="key">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
89f43170c81611dcc8fa001b78afb958
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ORDERID">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
89f43171c81611dcb6e3001b78afb958
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base="xsd:string">
<xsd:attribute name="compareOperation" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
89f43172c81611dccba5001b78afb958
</xsd:appinfo>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="action" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
fa204eb2bceb11dca298001b78b0798a
</xsd:appinfo>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
Soap Responce Structure:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://soap2dbns" targetNamespace="http://soap2dbns">
<xsd:element name="soap_resmt" type="soap_resdt" />
<xsd:complexType name="soap_resdt">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
8d49d494c8a411dc81f5001a4bf038d4
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="response" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
491ccd30bd0611dcb29d001b78b0798a
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="row" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
491ccd31bd0611dca3d7001b78b0798a
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ORDERID" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
491ccd32bd0611dcc7d1001b78b0798a
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ITEM" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
491ccd33bd0611dca6ad001b78b0798a
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="QUANTITY" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
491ccd34bd0611dc95a8001b78b0798a
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="PRICE" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
491ccd35bd0611dcc034001b78b0798a
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
Database responce Structure:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://soap2dbns" targetNamespace="http://soap2dbns">
<xsd:element name="db_resmt" type="db_resdt" />
<xsd:complexType name="db_resdt">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
8d3b7cb1c8a411dcb1d6001a4bf038d4
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="STATEMENTNAME_response" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
adca3410bcfd11dcaf4c001b78b0798a
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="row" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
adca3411bcfd11dc92d6001b78b0798a
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ORDERID" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
adca3412bcfd11dc92e8001b78b0798a
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ITEM" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
adca3413bcfd11dc9f7a001b78b0798a
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="QUANTITY" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
adca3414bcfd11dcc6c4001b78b0798a
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="PRICE" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
adca3415bcfd11dca54c001b78b0798a
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
Regards,
Naresh

Webservice - XI - JDBC BPM scenario

Hi Experts,
Could you please provide the steps to do the Webserive -> XI -> JDBC scenario, using BPM?
Regards
Sara

Hi Jai,
Actually, I have to do multiple orchestrations scenarios.
I came to know from some of the XI experts that I have to use BPM to do multiple orchestration scenarios.
If you have any idea, could you please provide the BPM steps for the (Webservice to JDBC synch scenario)
Regards
Sara

Synch Scenario ( RFC to JDBC)

Hi,
I have a synch scenario like RFC to JDBC.
1. I have a qurey regarding JDBC receiver side structure. What would be the structure I have to create on receiver side ( JDBC) for the same.
2. Mainly, what would be the constants I have to map for the action, table, statement fileds??!! If possible try to explain for each and every scenario.( synch/asynch)
Cheers.,
Stallin

Hi Stallin,
Check these links:
/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
/people/siva.maranani/blog/2005/09/16/xi-how-to-on-jdbc-receiver-response
http://help.sap.com/saphelp_nw04s/helpdata/en/33/c6e63b60c25767e10000000a11402f/frameset.htm
Regards,
Subhasha Ranjan

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

Reg error in interface mapping in RFC to JDBC scenario

Hi Techies,
Iam trying to map the scenario RFC to JDBC.
In configuration window Iam testing the configuration.
when Iam testing it is giving the error.
" com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_mm_mapping_: Parsing an empty source. Root element expected! "
My mapping is as follows
                   mt_receiver
                                                        statement
                                                            ROW
                                                 action---insert
             ZHRT002----
     Table
     Item----
access
          MANDT
          PERNR                                     PERNR
          PERID                            PERID
          SHOPN                           SHOPN
Sender
<?xml version="1.0" encoding="UTF-8"?>
<ns0:ZTEST_PI_ZHRT002 xmlns:ns0="urn:sap-com:document:sap:rfc:functions">
   <ZHRT002>
      <item>
         <MANDT/>
         <PERNR/>
         <PERID/>
</item>
   </ZHRT002>
</ns0:ZTEST_PI_ZHRT002>
Reciver
<?xml version="1.0" encoding="UTF-8"?>
<ns1:mt_receiver xmlns:ns1="urn:sap-com:RFC2JDBC"><Statement1><ROW action="INSERT"><TABLE>ZHRT002</TABLE><access><PERNR></PERNR><PERID></PERID></access></ROW></Statement1></ns1:mt_receiver>
Please give suggestion how to go about this.
Thanks in advance,
Regards,
Kiran

Hi,
Please check the payload you are using to test the configuration.
The structure seems to be Incorrect.
Regards,
Deepak

Can we able to create a scenario in XI like, RFC to JDBC

Hello,
I want to know whether there is any way to create a scenarion like RFC to JDBC.
RFC sends a rfc call with some parameters on sender side.
JDBC stores the data in the receiver side.
Thanks ,
Prakash

Hi Prakash,
Step-by-step RFC to JDBC scenario:
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/step%2bby%2bstep%2brfc%2bto%2bjdbc%2bscenario
XI: How-to on JDBC receiver response:
/people/siva.maranani/blog/2005/09/16/xi-how-to-on-jdbc-receiver-response
-Pinkle

Czech letters in RFC- XI-JDBC scenario

Hello experts,
we want to transfer data to a database in a RFC->XI->JDBC scenario. Everything works fine, but when we transfer czech characters, we only see "?" in the database where a "Č" is expected. In the XI system the letters are displayed correctly (before and after mapping).
How can we solve this problem? Is there any setting for this in the receiver CC?
Best regards,
David

hi David,
try using ![CDATA[]] in your mapping, i mean send value in to the target field as ![CDATA[ Č ]].
Regards,
Karna...

RFC-XI-JDBC Scenario: Help with RFC code

HI,
I am doing RFC-XI-JDBC Scenario, where I have to poll the contents of my Ztable in SAP to Oracle.
The appraoach i am using here is :
1. Created a FM with import parameters as the fields of my Ztable and without any export parameter or source code.
2. Created a report to call that FM in background. The code of my report is as follows :
************************REPORT***********************************************************
Data:       it_zrfc_read_table type table of zrfc_read_table,
            wa_zrfc_read_table like line of it_zrfc_read_table.
PARAMETERS: tab_name like DD02L-TABNAME.
Data:       l_tabname type DD02L-TABNAME.
At selection-screen.
select single tabname from DD02L into l_tabname where tabname = tab_name.
if sy-subrc <> 0.
message 'incorrect table name' type 'E'.
endif.
start-of-selection.
select * from (tab_name) into corresponding fields of table it_zrfc_read_table.
loop at it_zrfc_read_table into wa_zrfc_read_table.
CALL FUNCTION 'ZRFC_READ_TABLE2XI'
IN BACKGROUND TASK DESTINATION 'ORACLEGIS_RFC_SENDER'
EXPORTING
    valve_id       = wa_zrfc_read_table-valve_id
    equnr          = wa_zrfc_read_table-equnr
    ernam          = wa_zrfc_read_table-ernam
    invnr          = wa_zrfc_read_table-invnr
    groes          = wa_zrfc_read_table-groes
    elief          = wa_zrfc_read_table-elief
    gwlen          = wa_zrfc_read_table-gwlen
    gwldt          = wa_zrfc_read_table-gwldt
    serge          = wa_zrfc_read_table-serge
    typbz          = wa_zrfc_read_table-typbz.
    endloop.
    commit work.
NOw my problem is that although I am able to send a table with a single record, but when my records > 1, it is not able to poll.
Please guide me what can be altered in the code or any other suggestion.
Thanks,
Puneet

Hi,
Instead of calling RFC many times I would:
1) create RFM with only one import parameter
TYPE your_table type
2) call only once RFM in the report:
CALL FUNCTION 'ZRFCNAME'
    IN BACKGROUND TASK
    DESTINATION 'RFCDEST'
    EXPORTING
      pt_table = i_table.
COMMIT WORK AND WAIT.
This will also improve the performance.
Regards,
Jakub

** RFC to JDBC scenario - Need not source code - Correct ?

Hi Friends,
I am doing RFC to JDBC scenario. It is a synchronous scenario. I think it is need not required to write any code in the source code tab of RFC. Is it correct ...? (Only Import and Export parameters are enough.)
Kindly reply, friends.
Kind Regards,
Jeg P.

Hi,
RFC needs only configuration and we will call remote method in R/3. Actual logic present in R/3.
Thanks,
RamuV

RFC to JDBC Scenario, Date Transformation error

HI All,
I am trying a RFC to JDBC scenario where I am taking date from SAP in SAP Format i.e. 'yyyy-MM-dd' & sending this to oracle DB Where the format is 'MM/dd/yyyy'.
In Runtime Workbench I am getting Following error: 'java.sql.SQLException: ORA-01843: not a valid month'.
Can anybody help me on this.
Thanks & Regards,
Ruchi Agrawal

Hi Bhavesh,
The Date Problem is Solved. It is Working fine with your UDF code. There were some small changes in your UDF.
Here is the modified code:
String b="";
try
java.text.SimpleDateFormat sdf= new java.text.SimpleDateFormat("yyyy-MM-dd");
java.util.Date date = sdf.parse(a, new java.text.ParsePosition(0));
java.text.SimpleDateFormat sdf1= new java.text.SimpleDateFormat("dd-MMM-yy");
StringBuffer sb = new StringBuffer();
sdf1.format(date, sb, new java.text.FieldPosition(0));
b=sb.toString();
catch(Exception e)
e.printStackTrace();
return b;
Thanks,
Ruchi

RFC to Jdbc Synch Scenario

Similar Messages

Maybe you are looking for