File to RFC/IDoc

Hi all
In any scenario suppose File system is sender system in that if the file is READ-ONLY file then how to process that file.

Hi,
Set the File adapter Processing Mode for "Set to Read-Only"
this will change the file property to read-only.
This will cause only new files to be processed.
This set to read only mode for sender file communication channel will process the fiels have write permission and change it to Read only to not to modify it later on.
this option is available for NFS only (Native file system)
Please reward points if it helps
Thanks
Vikranth

Similar Messages

File - XI/RFC - Idoc

My scenario is I get a file with multiple records. I need post these into R3 using Idoc. Since File doesn't have all the fields required, I have to get missing fields from R3 to which I'm ultimately posting.
I get StateCode from inpu file record. Based on this state code I will get plants. For each plant I need to post input file record onto Idoc. So for each file record there will be multiple Idocs ( one Idoc per plant ). What is the best possible solution for this kind of situation. Thanks for any suggestions..

Hi Bhavesh,
thanks for your reply. Why should I use RFC? I get StateCode from payload. If I use Statecode to get plants, for every call I will get same plants. Instead I want to maintain these State Code and Plant references in a static file on Xi server or Ztable on XI.
I will have 2 input messages. 1. Flat File . 2. State/Plant xreference File.
From these 2 files I can use Standard node function to map.
Example:
Flat File
FL,1234,4567
FL,8495,8975
2nd File
FL,100
FL,200
FL,300
and Outbound file from XI:
100,1234,4567
200,1234,4567
300,1234,4567
400,1234,4567
100,8495,8975
200,8495,8975
300,8495,8975
400,8495,8975
So for each occurance of StateCode from File 2, I need to create those many recs of file 1.
I hope I did not confused. Similarly I will have other states with some plants.
Would you please let me know what Node function and mapping I should use. Thanks a lot..

File to RFC/IDOC with a set of business rules applied on every record

Hi experts,
i have a scenario where the following happens
checks need to be performed
1. Technical validations on the file picked up (Can be done through java programs)
2. Business rules to be applied on every record (Am not sure if this can be done in PI) Sample business rules - record id already present in the SAP system, check if some manadatory fields are missing in the record etc..quite a lot to be applied
I assume we use the File>PI>IDOC/RFC scenario for this..
However am not sure on how we apply the complex business rules on every record in file using PI.
Any suggestions??
Regards,
Kalyan

Hi My requirement as follow,
ELEMICA(CIDX)--->sap xi->SAP ECC,i receive CIDX Ordechange document from source system,when it is order change , the similr Order Chnage document available in DATA BASE,i need to retrive it from data base using some key fileds, i need to compare some of the fileds like PO Number,Buyer sequence number..like many fileds.if there is any change while validating then i need to send it SAP ECC Orders IDOC,IF TEH Values are same then i need to exit the process with mail to admin .
How i done my requiremnet i already explained,if you looking for any info let me know,but i never faced any problems like perfromace issues ...but writing JAVA Maping code is bit tough.
Regards,
Raj

Guarantee EOIO Processing in File-RFC-RFC-IDoc Scenario

Looking for some opinions on the following set up we've got. We're trying to build QoS EOIO on a scenario that goes File Sender->RFC and then RFC->IDoc. My question is basically have we effectively ensured that our scenario will be EOIO from file to IDoc. We want the first record in the file to always be the first created IDoc, the 10th record in the file to always be the 10th IDoc created etc..... We also want to make sure that if we encounter an error at any point that all subsequent processing stops and waits until the problem is resolved. We've successfully completed some steps but my biggest concern is in the area between where XI sends the data to SAP1 via RFC and the resulting return RFC from SAP1. I'm thinking we may not be quite there yet and would be interested to hear what others thought.
We're on SP15. The scenario goes like this (no BPM):
1) We have a legacy system LEG1 that we pick files up from using the Sender File adapter. This step will take the file from LEG1 into XI and map it to an SAP remote function on SAP system SAP1. We set QoS on the file adapter to EOIO. Our interface determination for the File to RFC component is set to QoS of "Maintain Order at Runtime".
2) XI makes the RFC call to SAP1 (6.20) using an RFC receiver adapter. The called function then processes the data and returns the data back to XI using another remote function call. This function call is of type tRFC where we call the function "in background task" and issue a commit after the RFC call.
3) We receive the data into XI from SAP1 using the RFC sender adapter. XI maps it to our IDoc layout and sends it onto another SAP system called SAP2. Again here our interface determination QoS is set to "Maintain Order at Runtime".
4) XI passes the IDoc onto SAP2 (7.00) using a receiver IDoc adapter. The paramter Queue Processing is turned on.

About EOIO in qRFCs, actually this is quite a polemic topic.
There is something you could do, allright, but it is controversial whether you could properly call it "EOIO" or not.
Refer to this thread for further discussion: use EOIO on Sender RFC and outbound ABAP proxy calls
Supposing you call the other RFC before you commit work in the receiver RFC, and supposing you could have EOIO at 2nd RFC (sender RFC), all these assumptions could mean that you would guarantee EOIO end-to-end. But they are just assumptions.
You have to try it and stress test the scenario to guarantee the validity of this design.
One other approach would be a BPM with all steps in one single transaction (check BPM transaction handling). The steps would be:
File -> sync RFC -> Idoc
where the response of RFC should be the necessary information for triggering the IDoc, and all send steps would be in EOIO mode (set queue name in Send steps). Also, file sender adapter QoS should be set to EOIO.
But I'm also not sure that this will guarantee EOIO end-to-end (possibly not...)
Good luck.
Regards,
Henrique.

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

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

In IDoc to file example if IDoc has not generated?what might be the problem

In IDoc to file example if IDoc has not generated? what might be the problem? where we can find it?

Hi Sudhakar,
We need to check in sm58 of R/3 system for any errors..and according to the error message we have to fix the problem.
It can fail with many reasons for example error in RFC destination connection etc.
Regards,
Prasanthi.

Error in File to Custom IDoc

Hi All,
I am getting following error while doing File to Custom IDoc Scenario
No authorization to send IDocs with message type Z
Can any one tell how to resolve this error?
Regards,
Sai

Hi Krishna,
The RFC destination that you have put in IDoc communication channel must be present in your SAP XI system, transaction SM59 also.
Please check if the user id/Password that you have given has all the authorization.
Also check the User ID and passwrord in SM59 in R3 and see if a Remote Login is possible.
There is also some configuration by which the clients are allowed / blocked from receiving Idocs from XI. Basis guys can do it for you. Please approach your basis consultant. Hopefully that helps..
Regards,
Abhy
Message was edited by: Abhy Thomas

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

Error importing RFC / idoc despite following note 769356

We have been experiencing a number of problems where we cannot import RFC / idocs in the integration repository. The BASIS team have followed note 769356 and originally this solved the problem but meant that we reverted back to old screens in the Integration Builder and some German texts in the Integration Repository.
Current patch version is Support Stack 4
To get to this point the following steps were followed:
Undeployed com.sap.xi.repository
Deployed the install version of com.sap.xi.repository.
In order to correct the problems with the incorrect screens etc.. The following steps were carried out:
Undeployed com.sap.xi.repository
Deployed the Support Stack 4 version of XITOOLS (includes com.sap.xi.repository)
Applied Support Stack 5 for the Abap kernel
Applied SAPXIAFC04P_1-20000272 and SAPXITOOL04P_1-20000274 via SDM
This fixed all of the problems with German texts etc.. but now we cannot import RFC / idocs again. In the Java Web Start Log (attached) we still get the error message
mentioned in note 769356. We have deleted the Web Start Cache on the client hosts (several restarts of the machine and deletions of the cache). The BASIS guys are going to undeploy and redeploy the repository again but failing that we are running out of ideas.
Does anyone have any suggestions?
Here is the entry in the log file:
java.lang.AbstractMethodError: com.sap.aii.ibrep.sbeans.upload.UploadServiceRemote_Stub.openSAPSource(Lcom/sap/aii/utilxi/misc/r3Connect/SAPConnectionData;Lcom/sap/aii/utilxi/misc/r3Connect/SAPLoginData;Lcom/sap/aii/ib/bom/gen/VersionContext;)Lcom/sap/aii/ibrep/sbeans/upload/SourceID;at com.sap.aii.ibrep.clsif.upload.RemoteUploadClient$ConnectionImpl.connectBean(RemoteUploadClient.java:107)at com.sap.aii.ibrep.clsif.upload.RemoteUploadClient$ConnectionImpl.<init>(RemoteUploadClient.java:91)at com.sap.aii.ibrep.clsif.upload.RemoteUploadClient.getSAPUploadConnection(RemoteUploadClient.java:66)at com.sap.aii.ibrep.gui.tools.r3import.wizard.SAPLogonPage.connect(SAPLogonPage.java:94)at com.sap.aii.ibrep.gui.tools.r3import.wizard.R3ImportWizard$LoginTask.run(R3ImportWizard.java:456)at com.sap.aii.utilxi.misc.thread.ThreadPool$ThreadPoolThread.run(ThreadPool.java:321)

Dan,
you are almost there!
If you religiously follow note 769356, you should not have this problem.
Just do the following as the note suggests:
- From SDM, undeploy only the com.sap.xi.repository
- Unzip SAPXITOOL04P_1-20000274.SCA.zip
- The file ExchangeRepository.sda will be one of the extracted files
- Only import the ExchangeRepository.sda. Do not import the entire ZIP package.
- Restart the J2EE engine.
- Delete Webstart Cache
- From the XI admin page:
http://XIhost:50000/rep/support/admin/status.html
Re-Initialize the Jars for resigning.
- Wait for 5 minutes for the jar signing to finish. Sometimes, the jar signing gets interrupted, you have to let it finish.
The above steps worked for me.
thanks,
Manish

RFC, IDOC, ALE, BAPI

HI everybody,
anybody can tell me
1.what is RFC and its use?
2.What is IDOC and its purpose?
3.What ie ALE and BAPI? please tell me their functions.
points will be rewared.

IDocs are simple ASCII data streams. When they are stored to a disk file, the IDocs
are simple flat files with lines of text, where the lines are structured into data fields.
The typical structured file has records, each record starting with a leading string that
identifies the record type. Their specification is stored in the data dictionary.
IDocs is the acronym for Interchange Document. This indicates a set of (electronic)
information which builds a logical entity. An IDoc is e.g. all the data of a single
customer in your customer master data file, or the IDoc is all the data of a single
invoice.
IDoc data is usually exchanged between systems and partners that are completely
independent. Therefore, the data should be transmitted in a format that can easily be
corrected by the computer operators. It is therefore mandatory to post the data in a
human readable form.
Nowadays, this means that data is coded in ASCII format, including numbers which
are sent as a string of figures 0 to 9. Such data can easily be read with any text editor
on any computer, be it a PC, Macintosh, UNIX System, S/390 or any internet
browser.
The information which is exchanged by IDocs is called a message and the IDoc is
the physical representation of such a message. The name messages for the
information sent via IDocs is used in the same ways as other EDI standards. .
Everybody who has ever dealt with interface programming, will find IDocs very
much like the hierarchical data files used in traditional data exchange.
International standards like the ODETTE or VDA formats are designed in the same
way as IDocs are.
Other EDI standards like XML, ANSI X.12 or EDIFACT/UN are based on a data
description language. They differ principally from the IDocs concept, because they
use a programming language syntax (e.g. like Postscript or HTML) to embed the
data.

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

File to RFC/IDoc

Similar Messages

Maybe you are looking for