Attachments with RFC adapter ?

Dear Experts,
I have a SOAP 2 RFC Synchronous Interface in my project, from sender side i.e from SOAP i am receiving data of 20 fields and also the attachment(the format of the file can be JPEG, EXCEL, WORD DOC or VIDEO Files) and these needs to be transferred to SAP R/3 System using RFC Adapter.
1. can RFC adapter able receive and send these format of attachments to r/3 server ? can you please suggest me on this...

Hi Raj,
Thanks..
The attachment will not go to the file system in ECC, as i stated that sender is sending the Data & attachments, at the ECC system a INCIDENT(SAP HSE) will be created by using the RFC, when you open the Incident in ECC system you should able to see the data in the Incident along with the attachment attached.
Regards,
Ravi

Similar Messages

Problem with RFC adapter (JCO Exception RFC logon failure)

Hi ,
I have SOAP to RFC scenario.
Scenario with same configuration (RFC adapter) is working in QA system.but when I have transported to PRODUCTION system
it is showing
com.sap.aii.af.ra.ms.api.DeliveryException: RfcAdapter: receiver channel has static errors: can not instantiate RfcPool caused by: com.sap.aii.af.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.af.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE:
I have gievn max conn=10 ;Refresh the cache also
and checked Roles and authorization also but still I am getting the same error.
Regards

Hi ,
I have created all the objects manually. and it is working.
now it is showing other error when I am sending the messages from SOAP side it is showing
MAPPING">NO_MAPPINGPROGRAM_FOUND</SAP:Code>
<SAP:P1>Object ID DF2C6D6E40E935CB970DEE3A71049BF9 Software Component C3D5E1D1C75311DDB94DE33C0A1E01B6</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Interface mapping Object ID DF2C6D6E40E935CB970DEE3A71049BF9 Software Component C3D5E1D1C75311DDB94DE33C0A1E01B6 does not exist in runtime cache</SAP:Stack>
for this I checked the Interface determination step and receiver determination ,mapping program all looks correct.
I have refershed cache also both Complete and SLD.
but nothing is wroking
Please advice.
Regards

Problems with RFC Adapter, utf-8 encoding and special characters

Hi,
How can I change my enconding UTF-8 for ISO-8859-1 in my RFC ADAPTER SENDER?
Regards,
Sérgio

Hi,
To change encoding of xml you can either use this piesce of xslt after your mapping as a next step
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml" encoding="ISO-8859-1"/>
<xsl:template match="/">
<xsl:copy-of select="*" />
</xsl:template>
</xsl:stylesheet>
or use adapter module but now I can't remember name of it.
Best regards,
Wojciech

I receive a lot of attachments with RFC-822 format. How do I open thes?

Most of these RFC-822 attachments are asking which program would like to use to open. Most are from Google

RFC 822 is an MIME type created in 1982 and no longer in general use. See this Wikipedia article: http://en.wikipedia.org/wiki/List_of_RFCs
The Nimda worm is known to use that format to propagate itself without user intervention by copying email addresses from the user's address book. If you're receiving attachments but don't know the sender, then it could be an indication that their PC is infected by this virus. Even if you know the sender, it would be wise to check with them in order to determine whether they intentionally sent you an attachment or not.
More on the Nimda worm here: http://www.f-secure.com/v-descs/nimda.shtml 
For your own peace of mind, run a full system scan with your antivirus program. If you haven't got one, you can get Avast AV free from here: http://www.avast.com/free-antivirus-download (''I use this one myself'').
Also, download the free version of Malwarebytes as an added precaution: http://www.malwarebytes.org/products/malwarebytes_free
If this answers your question, please click the '''Solved it''' button next to this post after you log in into the forum. This will help others searching for a solution to the same thing.
Thanks.

RFC Adapter not getting data

Hi experts!
I am developing a RFC to File scenario on PI 7.1 EHP1 and ECC 6.0 which is synchronous. Following the Help page Setting Up an RFC Destination for the RFC Adapter I created two destinations. The fist one is a TCP/IP, name RFCDE1COMPANY2, program id BAPI_COMPANY_GETLIST and corresponding gateway host and service I found at SMGW (Parameters). The second one is a Logical with name RFCDE1and reference entry RFCDE1COMPANY2.
At my RFC Sender Adapter I configured the same gateway info and the same program id. After that I tested both destinations and it worked. I created the following report to call the bapi on that destinations::
REPORT ZREP_BAPI_COMPANY_GETLIST.
DATA: company_list TYPE STANDARD TABLE OF BAPI0014_1.
CALL FUNCTION 'BAPI_COMPANY_GETLIST'
IN BACKGROUND TASK
DESTINATION 'RFCDE1'
TABLES
COMPANY_LIST = company_list.
COMMIT WORK.
At SXMB_MONI the request message was processed and the output file generated, but it has only the root tag. At moni the inbound message has no data (company data).
I tested the BAPI_COMPANY_GETLIST at SE37 and there are 149 entries. When I executed this same BAPI with RFC target sys configured to my destination, it didn´t show any data and has an exception called SYSTEM_FAILURE. I think probably the error is on RFC destinations but I can´t figure it out what is wrong.
Best Regards,
Gabriela

Hi experts,
Thank you all for your quick response.
At the TCP/IP Destination there is a button "Unicode Test", according to this test my target system is unicode (character size 2). I changed the option at MDPM&Unicode on that TCP/IP Destination like Madhusudana described. I also selected the checkbutton "Unicode" on sender RFC communication channel.
About the sync/async, I will not use sync async bridge because this scenario can be async. One think that I realized is that when I call my report, I am implicitly calling PI asynchronously and when I call the BAPI directly by the test tool, I am implicitly calling PI synchronously. That is why most part of my tests did not work before.
Now I can see on SXMB_MONI that the scenario worked and the file was generated. But the data are still not being showed on inbound payload. I think something is wrong with my destinations but I can´t figure it out what is.
Ps.: I would prefer to use XI proxies, but this scenario will be configured (not now) on a XI 3.0 with ERP 4.6 C. Now I´m just learning how to handle with RFC Adapter.
Any ideia?
(Points granted)
Thank you and best regards,
Gabriela

RFC Adapter : JCO_ERROR_CONVERSION : Unparseable date

Hi all,
We are working with RFC Adapter .
We are getting the following error in RWB -->
Component Monitoring --> Adapter Engine --> RFC
Adapter
" JCO_ERROR_CONVERSION: Date '01.12.2005' has a wrong format at field VALIDITYBEGIN: Unparseable date: "01.12.2005" "
- Error: 2006-02-03 11:17:13 IST: Message processed for interface BAPI_BANKDETAIL_CREATE: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: could not convert request from XML to RFC:com.sap.mw.jco.JCO$ConversionException: (122)
Can anyone please suggest how to resolve it .
Regards,
Shikha

Hi,
In which format the date is passed from XI?
If, it is of type Java Date there will be No conversion issue else if the it of Type String then the date should be in the format YYYYMMDD.
Hope this helps you.

RFC adapter commit

Hi,
I have a scenario with RFC adapter using BPM. This scenario working and live but now we find out that 1 material document not posted but we able to get the mat doc number. This is only happen for 1 time and others material was posted successful. Anyone have idea?
Thanks.

Hi,
Thanks for reply. I am able to get the material document but the problem is it not get posted in SAP R3. In sxmb_moni it show that process successful.
Thanks.

RFC adapter in XI 3.0 not working properly with BAPI in R/3 4.6C

Here is the scenario.
An XML file is received from our customer. This file contains purchase order information that is used to create a sales order in our SAP 4.6C system. Once the sales order is created an acknowledgement is generated and this is returned back to our customer in an XML format. This scenario is working perfectly fine in our XI 2.0 system but is not working properly in our XI 3.0 test environment. Our custom function module in R/3 is a wrapper function that uses a standard SAP BAPI to create the sales order. Part of the function module does use the statement
call function 'BAPI_TRANSACTION_COMMIT'
The last thing the BAPI does is call another function module that using an RFC destination that will return and order acknowledgement.
Here is what happens within XI and our SAP system.
The XML file is received and mapped to our imported RFC. The RFC adapter is called and the information is passed onto SAP where our customer function module executed. The sales order is created within SAP without any problems and the second function module is called which references an RFC destination assigned to our XI 3.0 system. The information is sent back to XI and an appropriate file is created for our customer. All seems to be working properly except that when the original RFC is sent from XI to SAP, SAP creates a short dump stating
"call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException:" Then it is put back into the que where 5 minutes later it executes again and trys to recreate the sales order in SAP. (again, this same function module executing from XI 2.0 works fine)
I believe I have everything configured properly because the SAP side is being executed and I am successfully passing information back from SAP to XI. However the original function module in SAP is failing with the above error message. It appears that the original function module cannot communicate back with XI. I have had SAP looking at this issue and they have not been successful yet in solving this problem.
Any ideas.
Thanks,
Jim d'Hulst

Hi,
I think the problem is with the send back of acknowledgement to XI. Does the DeliveryException state something about the sender agreement? I guess you are using a statement like below:
CALL FUNCTION 'ZABCD'
destination <tcp/ip destination>
exporting
input = ack.
In that case, check whether the TCP/IP destination is working fine. Also, to be able to exchange message, the structure of the Function Module ZABCD needs to be identified as the sender in XI Configuration (Integration Directory).
Also, check your config with the blog mentioned below:
<a href="/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit">/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit</a>
Regards,
Amitabha

Problem with sender RFC adapter

Hi All
I have created one RFC adapter for which i have created wrong business system and all then i have deleted that and i have created on more RFC adapter but when i am testing my scenario its taking the old one which i have deleted from the Integration directory. I have refreshed the cache using sxi_cache and also in RWB. But still i m getting the same error...
Could you please tell me how to resolve this error

Hi
Yes i have configured RFC as sender communication channel. I have deleted the old one including the business system. but still in adapter monitoring i m getting the error "com.sap.aii.af.rfc.afcommunication.RfcAFWException: alternativeServiceIdentifier: party/service from channel configuration are not equal to party/service from lookup of alternativeServiceIdentifier (CPA party/service/channel ''/'Whirlpool_BS1'/'RFC_Source_CC', lookup of alternativeServiceIdentifier for party '', schema 'TechnicalSystem' with 'QN9#800' returned party/service of ''/'QN9')"
but i have deleted the whirlpool_bs1 business system.
Why still i m getting this error.
Thanks & Regards
SUN

Polling with RFC Sender Adapter

Hi,
i am facing a general problem with the rfc sender adapter.
I have to design a scenario where periodically pi has to call a rfc fuba/bapi in R3 and insert the response into a database or create a file.
I looked for some possibilities to impelement this scenario and desided to use ABAP Proxies to transfer the data from R3 to pi.
The problem is that the wish of the department for R3 is not to plan a job to send the files. They want that pi itself call periodically the fuba in R3. I found out that the rfc sender adapter is not able to poll like jdbc oder file adapter.
I thought i could write a litte abap program in pi to be planned in a job or to create a dummy file and poll with the file adapter. But i mean that these solutions are not good. They feel like workarounds and not like a real good solution.
Beside this there is also the problem that we could use the inubit integration system. inubit is able to poll periodically the rfc adapter and is it hard to argument against this.
Are there any good solutions known for the problem?
Does anyone know what the official SAP meaning is for a process like the described above?
many thanks
Michael Eckstein
Edited by: Michael Eckstein on Dec 16, 2011 12:55 PM

hi,
1st: your R3 department is stupid (!).
As your flow is ECC -> PI -> Database. you could easily create a litle extraction program with a selection screen (and a variant which could be easily updated !!) (1) to send data to PI (by using a proxy or an idoc), with a log (at end of your program) and to create easily (!!) a sap job (ecc) based on a country calendar (2).
2nd: If you really need to have "PI -> ECC (proxy)-> PI -> JDBC", you have to use the standard PI scheduler tool, called "Availibility time planning" (ATP). see this option in CC monitoring (RWB). you could trigger your sender CC (proxy)
And if you want, another possibility could be to trigger your sender CC by an external tools (to buy), or by creating an abap program....
(1) how you will pass the value to extract data with your solution (my 2nd point).
(2) in ATP of PI, the scheduling will be NOT based on a country calendar (holiday, religious/bank holiday), but just daily, weekly, inside a range, etc...
Mickael
Edited by: Mickael Huchet on Dec 16, 2011 12:53 PM

SAP PI Issue with RFC Receiver Adapter

Hello,
Iam using File-RFC scenario, where every thing executed fine, but in ECC iam unable to get the DATA coming from PI, Iam using Z RFC to insert data to a Z table.
I did'nt any errors in PI, is there any option to find the output data at receiver adapter where iam using RFC adapter.
Kindly Help,
Thanks in Advance,
Ravi.

Yes. If you enable the logging you should be able to see the post mapping xml.
Message Staging and Logging Options in Advanced Adapter Engine of PI 7.3x
Scenario specific message staging and logging in PI 7.31 AAE
Did you debug the RFC with test data? were you able to insert something?

How does RFC adapter with EO/EOIO work? Kindly help!

Hi Experts,
How does a sender or receiver RFC adapter works when QOS is EO or EOIO (Async)? In other words, for EOIO, are the messages are queued? How does this queueing work? Does it use FIFO logic? where do we specify the max limit of messages that can be queued?
Also what is the significance of 'Initial connection' and 'maximum connections' in communication channel? I have given the default value 1 for both. What should be the ideal value and why?
In my Async RFC - XI scenario sometimes XI is able to receive the messages but sometimes it doesnot even though the sender system is UP and running.
I cannot see any messages in SXMB_MONI even though the sender has sent the messade.
Why RFC adapter is behaving like this? What could be the issue?
Kindly help!

EOIO: How does this queueing work? Does it use FIFO logic?
>> yes it uses FIFO logic in EOIO.
Also what is the significance of 'Initial connection' and 'maximum connections' in communication channel? I have given the default value 1 for both. What should be the ideal value and why?
>>>noof rfc connections we are using for connecting to XI to RFC minmum is 1 maximum is 50 bydefault. you increase this value by changing the default setting.
How does RFC adapter with EO/EOIO work? Kindly help!
Posted: Mar 21, 2007 4:15 AM
Hi Experts,
How does a sender or receiver RFC adapter works when QOS is EO or EOIO (Async)? In other words, for EOIO, are the messages are queued? How does this queueing work? Does it use FIFO logic? where do we specify the max limit of messages that can be queued?
Also what is the significance of 'Initial connection' and 'maximum connections' in communication channel? I have given the default value 1 for both. What should be the ideal value and why?
Why RFC adapter is behaving like this? What could be the issue?
>>check ur sender RFC adapter. chekc whether data is sent from RFC . see logs in R/3.

Is this possible: SAP Java Connector - XI - R3 with XI RFC Adapter?

Hi,
I try to call a RFC on a remote R/3 System over the XI Server in a Java Application with SAP Java Connector.
I have configured a RFC Sender Adapter in XI. I get the
following Exception:
"lookup of alternativeServiceIdentifier via CPA-cache failed for channel 'SenderChannel_RFC"!
Is this scenario possible? Or do the connection from
a SAP Java Connector App to the XI RFC Adapter not work?
You can't set the Client and System ID of a Third-Party or
Standalone Java system in the SLD.
Thanks for any help!
Regards
Wolfgang

Hi,
We use a JCO for directly connecting to sap systems.
In that case we need not use any XI also.
But if you want to use RFC adapter and java application the best way is to use java proxies as sender and reciever as RFC adapter.
I donot think there is any architectural significance in using rfc adapter of XI while using JCO.
Let me know if I mis-understood the context.

Can we process files with attachments using File Adapter

Hi All,
I want to process files which have attachments using File Adapter.
Is it possible to process such files?
May be using standard modules?
Regards,
CBKLP

Assuming you are talking about sender FILE channel....you can make use of PayloadSwapbean provided by SAP (standard module)...to read data from attachment.
Regards,
Abhishek.

Problem with RFC sendder adapter.

Hello All, Any help will be greatly appreciated. I am creating interface from CRM to XI using RFC adapter and XI to Forums using SOAP adapter. I configured in IR and ID and trying to push the RFC in CRM and I am getting the following error.
lookup of binding via CPA-cache failed for AdapterType RFC, AdapterNS
I went through the previous forums and I got no luck following those recommendations.
Thank you very much for your help.

Hi ,
Check these-
1) Sender Agreement and Program Id for the RFC is correct or not
Sender RFC Adapter
Refresh the cache of the Adapter Engine.
1) sxi_cache->goto-->AE Cache
2) check for CPA Cache also
Just go thru following link from service.sap.com
https://websmp103.sap-ag.de/~sapdownload/011000358700002757652005E/HowtoMintorAF.pdf
http://help.sap.com/saphelp_nw2004s/helpdata/en/0d/28e1c20a9d374cbb71875c5f89093b/frameset.htm
Did you refresh Adapter Metadata in the SLD ? This is mentioned in the Adapter Monitor document.
Change the RFC adapter once again and activate the same. and then run the scenario. Did you change the RFC after importing..If so again import it.
Hope this helps,
Regards,
Moorthy
Message was edited by: Krishna Moorthy P

Attachments with RFC adapter ?

Similar Messages

Maybe you are looking for