File to RFC to 3 IDocs

Hi Experts,
I am configuring a scenario where a File is sent to RFC if data is fine then its response is mapped to 3 IDocs else the error response needs to be mapped to a file and sent it back.
Previously I have worked on File to RFC to File scenario with out using BPM.
https://wiki.sdn.sap.com/wiki/display/XI/File-RFC-File%28Without%20BPM%29
Can I follow same approach in this scenario to avoid BPM?
Do I need to go for Multi mapping here for mapping RFC response to 3 IDocs?
Can I create 4 message mappings, 3 for IDocs and one for error response and apply condition in Interface Determination in ID?
Please advice. Thanks in Advanceu2026

>
PhaniKumar Akella wrote:
> Hi Experts,
>
> I am configuring a scenario where a File is sent to RFC if data is fine then its response is mapped to 3 IDocs else the error response needs to be mapped to a file and sent it back.
>
> Previously I have worked on File to RFC to File scenario with out using BPM.
> https://wiki.sdn.sap.com/wiki/display/XI/File-RFC-File%28Without%20BPM%29
>
> Can I follow same approach in this scenario to avoid BPM?
> Do I need to go for Multi mapping here for mapping RFC response to 3 IDocs?
> Can I create 4 message mappings, 3 for IDocs and one for error response and apply condition in Interface Determination in ID?
>
> Please advice. Thanks in Advanceu2026
my suggestion is to go for a bpm.
it will give you the flexibility to handle the error message in case the RFC fails. You can easily catch exceptions and raise alerts plus also map the error to a file and send it as per your requirement.
You can also easily do the response mapping to the Idocs

Similar Messages

Error in File to RFC scenario: ATTRIBUTE_WRONG_INTF

Hello,
My scenario is going from File to RFC which is simply writing to an SAP table.
My mapping seems OK and tests OK but in SXMB_MONI I get red flag and error below:
<?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="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
<SAP:P1>ZDWM_POS_UPDATE</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to interpret IDoc interface ZDWM_POS_UPDATE</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
The posts I see in the forums with this text have to do with an external deffinition being incorrect. I don't have an ED, it is mapping right to our custom RFC interface ZDWM_POS_UPDATE.
Does anyone have any ideas or pointers for troubleshooting this?
Many thanks,
Aaron

Hi Aron,
You should not create any message interfaces refering to RFC.Infact RFC acts both like Message type and Messge interface.
In interface determination choose ALL radio button and choose Idoc itself instead of interface.
Also the interface mapping should be b/w Fileinterface<-->RFC directly (no need of interface)
Hope this helps.
Regards,
Divya

How to explain the business requirement of a file to rfc scenario

Hello Experts,
 How do i explain the business requirement of
 1. FILE TO IDOC.
 2. FILE TO RFC.
 3. FILE TO JDBC scenarios?
 Cud anybody explain me how to explain the requirement of these scenarios in an interview?Cud u pls send me the example for these and the systems involved and the documents involved...helpful answers will be rewarded...
 cheers
 Jay.
my mail : [email protected]

1. FILE TO IDOC.
When u have ur master data stored in a file thru a legacy system say in some xml format then u may need to have this scenario configured.
2. FILE TO RFC.
Consider pt1 but here for example consider delete scenario. when u have deleted the mater/transaction u may need to update another file...so in this case u will need to config this scenario...y we cannot use idoc is becoz sync scneario is not possible with idoc but yes with rfc
3. FILE TO JDBC scenarios?
u have some business data extracted from a file and before u update a r3 transaction u may need to refer a datbase table to read some data baed on keyfield...so u will take a jdbc response and based on that u may validate with the data for r3 updation.
the scenario keeps varying in real life and the above are very few examples of the kind of scenario that would exists in the business world

Doubt on FILE to RFC & PROXYS

Hi everybody,
 I'm able to solve most of my doubts by this forum, thankz to everybody who assisted me.Here are some simple doubts plz give solutions to them as many as possible
 1.In my FILE to RFC scenario I'm using BPM & i should send response back to SENDER so what steps should i include in it ? I'm using BAPI_GOODS_MVT_CREATE bapi?
 2.In my FILE to RFC scenario I'm maintaining single SLD for DEV,CONS,PROD ,so can i configure my file sender service directly in ID as a BUSSINESS SERVICE?
 3.Can any one give some information In which case we have to go for
PROXY & in which case for IDOC?exluding this reason " if syst config is >6.20 or else go for IDOC or RFC for an sap system?
 Plz kindly answer to this questions & valuable answers are rewarded.
 Regards,
 Vinod.

1.In my FILE to RFC scenario I'm using BPM & i should send response back to SENDER so what steps should i include in it ? I'm using BAPI_GOODS_MVT_CREATE bapi?
>>>
Ref: /people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
Else in case you have SP19 then ref this abstract from an earlier post !!
All,
Just thought I'd add a quick note here.
From SP 19 on XI 3.0 and SP 10 on PI 7.0, a File - RFC - File ( Asynch - Synch ) scenario can be done without a BPM.
Steps:
Integration Repository
The Integration Repository will be similar to any Synchronous Scenario ( say HTTP - RFC ) . 1 Outbound Synch message Interface and 1 Inbound Synch Message Interface.
Integration Directory
This is where a few differences lie, so let me take some time.
1. The Receiver Determination , Interface Determination will be the same as in HTTP - RFC synch scenario. Create the Sender File Adapter, Receiver RFC Adapter and Receiver File Adapter.
2. Sender Agreement will be for the Sender File Adapter. Sender Agreement uses the Synch Outbound Message Interface.
3. Receiver Agreement will be for the Receiver RFC adapter. Receievr Agreement will use the RFC as thge Inbound Message Interface.
4. We need to add a few modules in the Sender File Adapter.
Go to the Modules Tab of the Sender File Adater, and add the following modules in the same sequence,
Number - ModuleName - Type - ModuleKey
1- AF_Modules/RequestResponseBean - Local Enterprise Bean - 1
2- CallSapAdapter-Local Enterprise Bean - 2
3-AF_Modules/ResponseOnewayBean-3
Parameters
ModuleKey - ParameterName - ParameterValue
1 - passThrough - true
3-receiverChannel - Receiver File Adapter Name
3-receiverService - Receiver Business Service/ System
With this configuration, you can now handle the requirement without a BPM
This feature been already blogged for JMS Adapters in these blogs ,
Sync/Async communication in JMS adapter without BPM (SP19)
Async/Sync Communication using JMS adapter without BPM (SP 19)
Dynamic Configuration is also possible,and this as well as many other options are discussed in the How To guide - "How To Realize a sync-async and async-sync
bridge within the Adapter Framework" available on the Service Market Place.

In my FILE to RFC scenario I'm maintaining single SLD for DEV,CONS,PROD ,so can i configure my file sender service directly in ID as a BUSSINESS SERVICE?
>>
you can use Business service !!!
3.Can any one give some information In which case we have to go for
PROXY & in which case for IDOC?exluding this reason " if syst config is >6.20 or else go for IDOC or RFC for an sap system?
>>>
Advantage of Proxy over RFC, IDOC
/people/ravikumar.allampallam/blog/2005/08/14/choose-the-right-adapter-to-integrate-with-sap-systems

Business service for file to rfc

hi
can someone tell me the business services used for each of the communication channels and their inbound outbound interfaces for Arpit Seth's blog file to rfc synchronous scenario
this is the url
RFC Scenario using BPM --Starter Kit
Edited by: pratichi chauhan on Aug 19, 2008 9:12 AM

Hi,
In the RFC Service, Add the Standard Idoc's Message Inetrface name at Receiver TAB only
that all
You can Implement the same Scenario with out BPM also
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/file-rfc-file%28without+bpm%29&
Regards
Seshagiri
Edited by: N V Seshagiri on Aug 19, 2008 10:11 AM

File-to-file or File-to-RFC for Automatic PO creation and GR creation

Hi,
We are on XI 3.0 and the following has been put to me:
We will receive a .CSV file from FTP server, into XI and then need to create Purchase Orders followed by the Goods Receipt documents in R/3 based on the incoming data.
Further to this, the requirement is to give a log of the successfule and failed PO + GR document summary to the business.
The programme in R/3 will compare the incoming file nmame with archived files already processed and will reject any files with duplicate names.
I was suggesting to go with the file to RFC in R/3 whereby we can have a Z shell BAPI to include the standard BAPI for PO creation and GR creation. This Z code can then be extended to email the log to the business of which records were successfully created and which failed.
However, I am stumped as to how can I make the file duplication comparison on R/3 as the incoming file will also be stored on R/3 archive somewhere.
Can this be made when the BAPI is called in XI?
I can configure alerts when the BAPI is mapped from incoming file for that interface.
What was suggested also was to pick up the CSV file and thow it as it is in R/3 and then the Z code can go through it and create the PO and GR objects. However, then it does not make much sense to use XI as the middleware platform.
Please advice.
Regards,
Arcahna

Hi Archana,
Take a look to this blog:
https://wiki.sdn.sap.com/wiki/display/XI/Different%20ways%20to%20keep%20your%20Interface%20from%20processing%20duplicate%20files
Maybe it could help you for the duplicate files.
Regards,
Juan

File to RFC/BAPI - Async- How to capture response field value

Hi,
I am doing File to RFC/BAPI Scenario. I have Two BAPI's. THe same source xml file is mapped to the Two Target BAPI's.
For the first flow i.e File to BAPI1, I need to capture BAPI Response, field value and pass this value as Input to the BAPI2.
How do I proceed with the Mapping. I am working on PI 7.1
Any input would be Appreciated.
Thanks & Regards,
Varun

Hi Varun,
apparently you need a Business Process:
XML -> BP (asynchronous), Map to Bapi1 request structure
BP -> BAPI 1 (synchronous)
Transformations step with multi mapping merging XML and Bapi1 response to Bapi2 request structure
BP-> BAPI2
Regards,
Udo

Step by Step Guide Details for RFC to File and File to RFC scenario

Hi Guru's
Good day to you. I am tyring to develop some scenarios based on RFC adaptor. so i want to start up with basic scenarios like RFC to File scenario(Here i just want to pull some data from SAP using RFC and put it in destination folder as an text file) and FILE to RFC scenario (Here i just want to take some data from the file and update into SAP).
For doing these scenarios i would like to request you people to send me the step by step guide which explains me about the complete steps of configurations required to do the RFC to FILE scenario and FILE to RFC scenario.
I found some scenarios and i am in confused state. so i request you to please put your experience to help me out.
thanks in advance.
Regards
Raj

Hi Aaron,
I don't know your scenario and your ECC and PI versions but I learned how to use ABAP Proxy more than 1 year ago with the following tutorial:
Edit--> The forum doesn't allow me to post external link, just search "ABAP Proxy Communication Scenario" in google and visit the 1st result
The way to develop ABAP Proxys has changed a little if your PI is 7.1. In the ECC side, the transaction SPROXY looks much better too if you have a recent version of the ECC.
Edited by: Marshal on Oct 8, 2009 5:08 PM
I've found that SDN Document. Maybe the scenario is not the most simple to start with ABAP Proxy but is very well documented and is for PI 7.1. The document also handles the inbound and outbound proxys
[http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/c00ca32e-f991-2b10-f5be-97114bd2b08f&overridelayout=true]
Edited by: Marshal on Oct 8, 2009 5:22 PM

File to RFC problem

Hi Friends,
I am doing a scenario CSV File to RFC. This is for SO creation in R/3 thru RFC.
I was provided with a wrapper RFC which internally calls the Sales order create BAPI.
Now my problem is When I go to SE37 and test the function module the SO is getting created but with the same data when I pass thru XI the so is not getting created. What can be the problem. Is there any authorization issue, if so tell me what auth should be given.
Vijay

Vijay,
Did you check the BAPI return parameter and what is the message you are getting. I think the problem is because of the conversion exit. I this this should be the problem R/3 expects leading zeros for vendor/customer numbers ans this is quite common error. Either change the wrapper RFC to handle this kind of values like calling the conversion routin before passing to the BAPI. This conversion routin can be foung in the domain.
Or add the leading zeros in XI mapping.
use this code in udf while mapping
int intDif, i;
String strDiff = new String();
intDif = 10 - Par_Input.length();
if(intDif > 0)
strDiff = "0";
for(i=1; i<intDif; i++)
strDiff = strDiff.concat("0");
strDiff = strDiff.concat(Par_Input);
return strDiff;
else return Par_Input;
Thanks,
Prakash

File to RFC - error while processing message to remote system:com.sap.aii.

Hi
i m working on File to RFC scenario. the records are getting displayed in sender CC and receiver CC. But in receiver CC i m also getting the following error:
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: JCO.Exception while calling ZRFC in remote system (RfcClient[CC_RIS_STC_PIMASTER_RECEIVER]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Screen output without connection to user.
Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: JCO.Exception while calling ZRFC in remote system (RfcClient[CC_RIS_STC_PIMASTER_RECEIVER]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Screen output without connection to user.
It was working fine few hours earlier but showing this error now. i was giving a SUBMIT program , but stopped that now.
But still facing the same problem. and in SXMB_MONI its showing recorded for Outbound processing.
could anyone help.

Hi
I am Facing Following Error When I am trying to call SAP Screen through JCO.jar
com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Screen output without connection to user
Please Guide Whethere it is possible to call SAP screen Through JCO.jar ot NOT
Please HELP if it is possible to Call SAP screen through JCO.jar with step and Code
Thanks
Vivek

Error while calling RFC adapter(FILE-XI-RFC scenario)

Hi,
I am trying for FILE-XI-RFC scenario. I am getting the following error. I have checked in message monitoring. The error is coming while calling the RFC adapter. Can any body tell what problem is this?
Regards,
Dhana
<?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="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>
<SAP:P1>af.f23.sofd00001530a</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>2: Unable to find URL for Adapter Engine af.u7a.us4296</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while reading access data (URL, user, password) for the Adapter Engine af.f23.sofd00001530a</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Hi,
I did SLD check.
The status says 'Summary: Connection to SLD works correctly'.
But it fails while checking the access to XI profile.
Here is the status
Summary: Connection to SLD works correctly
Now checking access to the XI Profile
Properties of RFC destination LCRSAPRFC
RFC host:
%%RFCSERVER%%
program id: LCRSAPRFC_DZ1
gateway host:
gateway service:
Testing the RFC connection to the SLD java client...
RFC ping returned exception with message:
/ CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679#Transaction program not registere

XML file to RFC

Hi,
i have scenario (XML file to RFC), it's by BPM, I can see XML content by file sender adapter but can't get detail field data into my data type of interface. what's wrong, please advise! Thanks!
my data type as follows,
 EXPORT Complex type
 SHIP element
 INVOICE element
and file content as follow
<?xml version="1.0" ?>
- <EXPORT>
<SHIP>A</SHIP>
<INVOICE>ZZ12387379</INVOICE>
<?xml version="1.0" ?>
</EXPORT>

>
robert yu wrote:
> I still can't understand, Could you give me more information? Thanks!
when you receive/ process an XML....this XML has a namespace associated to it.....which in your case should be http://aaa.bbb.com/SVRFIS/Forwarder_File.....
However looking at your Payload ther is no namespace in it....so what you do is...open the Interface/Message mapping--- go to the Test tab and click on the SRC tab and then check what/ how the namespace should be or rather how the XML should be while testing...it would be something like:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_Name xmlns:ns0="http://aaa.bbb.com/SVRFIS/Forwarder_File">

XML file to RFC (BAPI)

hi
can you please give the configuration steps that i have to follow while doing xml file to RFC,
1)configurations in XI part
2)configurations in R/3 part
and i am using bpm in this scenario, is there any need of "program id " while doing configurations in ID part, from where we get this programid. if you have some screnshots of this scenario, can you please forward it to me.
mailid:[email protected]
regards
Pradeep P N

hi pradeep,
no need of defining programid here...because u r using RFC as receiver...
dont define the RFC as sender....if u do so it will ask u the programid..
in u r case RFC is a receiver,so no need to define programid....
watch this
/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
thanx,
krish..

Issue in File to RFC to File Scenario with BPM using Block Step

Hi Everybody,
                       I am doing File to RFC to File Scenario for multiple records using BPM using Block Step. The File Message is getting posted and after that, the message is getting stuck up in the qRFC Monitor (Inbound Queue).
                    After seeing the message in Inbound Queue, I am trying to execute and release the message. But when i execute the LUW, it says " Function module doesnt exist or EXCEPTION raised" in Inbound queue.
Could somebody suggest me the outcome of this? What does this mean and how to
release the stuck up message in Queue.
Thanks and Regards,
N.Jayanth Kumar

Hi Rajesh,
                       After going through the blog, i saw the trace messages. It says
" The   exception occurred (program: CL_SWF_XI_INBOUND=============CP, include CL_SWF_XI_INBOUND=============CM00F, line: 19)"
Regards,
N.Jayanth Kumar

Issue in File-PI-RFC scenario

Dear All,
I am working on File-PI-RFC interface in which contents of file are updated in SAP ztable.
The interface was working fine but yesterday i changed the length of one of the fields of the table. From then onwards, table contents are getting updated with some dummy/junk values which we are not sending thru PI.
I have checked the payload at the receiver end and it is not showing any junk values but in the table it shows junk values in the filed whose length is changed.
I have reimported the RFC metadata in ESR but still it shows wrong values in ECC.
Please guide me where I need to referesh the RFC metadata to resolve this as this problem I am facing in PRD environment.
Regards,
NJ

Hi,
Pls check if the length of the field in table and the length of the field in internal table in the RFC function matches. If not pls do the same and then send data agn.
Edited by: Debaprasad Narendra on Nov 3, 2010 7:23 AM

File to RFC to 3 IDocs

Similar Messages

Maybe you are looking for