RFC-XI-File Adapter scenario

Hello SDN members,
We are about to start the configuring XI 3.0 for connecting the SRM Module as a source and Portal as a destination to transfer a file. We are planning to have a function module to generate the flat file from SRM.
We need to process the data file from SRM to a portal.
Could some body suggest me the process flow to accomomplish this ?
Appreciate your time.

Hi Steve,
If the SRM module is creating a file, and the file has to be transfered from SRM system to Portal system, then you need to look at configuring a 'File -> XI -> File' scenario.
To work with File-XI-File scenario, refer to this blog:
/people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2
If you are looking at a just <b>Flat file transfer</b> and no mapping in XI, then:
it is possible to create a scenario to transfer any sort of files : including binary files.
<b><u>Steps:</u></b>
In Repository:
Create a data type (say dtBlob) with one field (data) of any type (xsd:string)
Create a Message type (mtBlob)
Create Two Message Interfaces (miBlob_IN & miBlob_OUT) : Aysnchronous Inbound & Outbound interfaces.
Message mapping & interface mapping are not required.
In Directory:
Create a Sender Agreement with this interface (miBlob_OUT)
Create a Receiver Agreement with miBlob_IN
Create Receiver Determination: From SRM system to Portal.
Create Sender channel for SRM system - File/FTP Adapter
Create Receiver channel for SRM system - File/FTP Adapter
<b><u>Process flow:</u></b>
Input Flat File (from SRM) is read by File/FTP Adapter and passed as it is to Integration Engine. It can be archived after pickup.
The flat file is not parsed into XML here.
Since no interface mapping is specified in XI, the same data is passed onto the target message.
The same data is passed further passed to the Target File/FTP adapter of Receiver.
The receiver adapter creates the file in the target destination.
Flat File transfered.
Hope this answers your concern.
-- Pops V

Similar Messages

Rfc to File Adapter

Hi ,
I am using RFC to file adapter.i am facing this error in XML.
com.sap.aii.utilxi.misc.api.BaseRuntimeException
thrown during application mapping
com/sap/xi/tf/_MM_RFC2FILE_: RuntimeException in
Message-Mapping transformatio~
<SAP:Stack>com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_MM_RFC2FILE_: RuntimeException in Message-Mapping transformatio~</SAP:Stack>
for receiver CC chanel i am using File adapter.Is there nees to use file content conversion for this.

Test the mapping with the payload from MONI, check if your mapping logic works in teh test tab of MM adn do the neccessary correction.
18:46:42 Start of test
Compilation of MM_RFC2FILE successful Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 2d, 20, 3c(:main:, row:2, col:3) com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 2d, 20, 3c(:main:, row:2, col:3) 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:832) Root Cause: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 2d, 20, 3c(:main:, row:2, col:3)(:main:, row=2, col=3) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 2d, 20, 3c(:main:, row:2, col:3) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2787) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2832) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231) 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(Unknown Source) 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:832) -
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144) at javax.xml.parsers.SAXParser.parse(Unknown Source) 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:832) Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 2d, 20, 3c(:main:, row:2, col:3) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2787) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2832) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231) 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(Unknown Source) 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:832) Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 2d, 20, 3c(:main:, row:2, col:3)
18:46:43 End of test
are you sending a XML file or a flat file to the target.If flat file ,
what is the requirement/delimitor and the data format requested by the Receiver system.
i just passind data from R3 RFC to XI,so sujjest what is needded in receiver file adapter.

Data tuncated in file adapter scenario

Hi,
File adapter scenario - Sender systems passes a file (csv format) to PI which has one of field as 0001. This field is received at PI without the prefix 000. But, the target systems requires the data to be in the same format as the sender. How to solve this?
Thanks

Satish,
It is the behaviour of the CSV files that it trims leading zeros in the columns with numeric values, try this open the CSV file and select the column and right click it in the context menu you would find FORMAT CELLS and change the type of the column to TEXT so that whatever values you enter in that column remain as it is without truncating.
Also, the trick at following link would help
[http://www.howtogeek.com/howto/microsoft-office/how-to-import-a-csv-file-containing-a-column-with-a-leading-0-into-excel/]
Hope this resolves your issue!!
Regards,
Amit

File to RFC want to delay rfc or file adapter

Hi,
Ive got a problem with my file to RFC scenario.
XI picks up a file and puts it to an archive directory.
Then it makes a synchoon call to a RFC. Quality of Service is Best Effort
The problem is, that the function module does not execute properly, because it can not find the file, so the RFC acts to quick.
When I change the quality of service to Exactly One or Exactly One in Order it works properly but in that cause I can not see my return message in the payload from SXMB_MONI.
I guess it is not possible to delay the RFC with the help of additional parameters. The only way to handle this I think is to build a wait function into the function module but my opinion, that's not a correct solution.
Any expert an idea?
Thanks in advance for your answers!

Hi,
File adapter doesnot support Sychronous. It only supports Asynchronous. Even you specify as synchrounous it acts like asynchronous only. So that is the reason why you are not seeing the response message in SXMB_MONI.
---Satish

Syncronous RFC to File Server Scenario

Hello,
I have this requirement for the XI Scrnario.
SAP 4,6 (RFC) needs to pick up XML file placed on Remote File Server.
RFC need to be executed on SAP which should make a call to XI and in turn File server, pickup the XML file from the server, bring it back to XI , do mapping and send the structure back to RFC.
This is Syncronous scenario.
Can naybody tell me how to do it.
i have searched it, but got more confused.
Appriciate your help.
Thanks.
DK

there exist a way around for this,but there are few(may be lot) constraints on it.
first of all you should know all the directories before hand from which you can get files,secondly you should know about the filenames too
what you can do is give all the directory names in the sender file adapter,similarly give the corresponding fileanames as well,XI will pick all the files in all the directories which satisfy the criteria one thing you need to make sure here is that if you don't want a certain file to be picked by XI,then it must either not exist in the directory or it must have a different names.
even though this is not completely dynamic but it solves the prupose if all the constraints are fulfilled and sender file adapter has been configured properly
Thanx
Aamir

Converting .XSL file to RFC using File Adapter

Hi,
I need to convert .xsl file using XI and send an RFC. I am not sure how to do that. Do i need to write some JAVA API's for the same. Is File adapter capable of converting .xsl files.
Any pointers are most welcome.
Thanks in Advance
Regards,
Vikas

HI,
try in the following ways
Write a simple XSLT mapping or java mapping to change the value of the attribute "encoding" to "ISO-8859-1" in the output XML of message mapping . Include this XSLT or Java map as the second mapping step in your interface mapping.
An example of the XSL code might be as follow:
<?xml version='1.0'?>
<xsl:stylesheet 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
see the below links
/people/sap.user72/blog/2005/07/31/xi-read-data-from-pdf-file-in-sender-adapter
How to write ModuleData process exit bean in the sender file adapter
Adapter module for file renaming
Module processor usage in File ADapter
Regards
Chilla

Error during mapping service, RFC-XI-File Adapter

Hello,
I have the following problem: I am using RFC to send some data to XI and then to File Adapter, however I get a short dump with "5990 Error during mapping service in XI". Even though mappings works, I tested using the document that comes in XI in Repository without any errors.
       What does this error means and is there any way to get more detailed explanation of my error. Thank you in advance for your help,
               Dmitriy Mindich

Synchronous RFC
1. CALL FUNCTION func DESTINATION dest
                     parameter_list.
Asynchronous RFC
2. CALL FUNCTION func STARTING NEW TASK task
                [DESTINATION {dest|{IN GROUP {group|DEFAULT}}}]
                parameter_list
                [{PERFORMING subr}|{CALLING meth} ON END OF TASK].
Transactional RFC
3. CALL FUNCTION func IN BACKGROUND TASK
                     [DESTINATION dest]
                     parameter_list
                     [AS SEPARATE UNIT].
Use help function of your ABAP editor for more details.
Regards
Stefan

CSV to CSV (FILE to FILE Adapter)Scenario

Hi All,
Kindly provide an immediate response..
The error is as follows..
Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Parameter '.fieldFixedLengths' or '.fieldSeparator' is missing

Hi Dhayanadh.
First let me confirm if you are using a flat file with fixed field lengths. if that is the case, then you need to specify the length of each field in the content conversion parameters.. for example
record.fixedFieldLengths : 10,14,12
where in 10 is the length for the first, 14 for second and 12 for the third one.
in the other case if, the field lengths are not fixed, then we need to mention the field separator in the conversion parameters.
Just check if you have provided that....
Browse these links....these could be provide you with an idea about content conversion...
/people/michal.krawczyk2/blog/2004/12/15/how-to-send-a-flat-file-with-fixed-lengths-to-xi-30-using-a-central-file-adapter
/people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2
Let me know if it has helped you..
Regards,
Hari

Adding Namespace in Sender File Adapter Scenario.

Hi All
I have a scenario where XI has to Pick Up XML a file and process it. The structure of the file is as follows
<?xml version="1.0" encoding="UTF-8" ?>
<Header>
     <Seg1>
     </Seg1>
</Header>
This file does not contain any any namespace tag. I guess XI would not be able to pick up this file if there is no namespace in the XML file . The file expected by XI would be something like this.
<?xml version="1.0" encoding="UTF-8" ?>
<ns0:MessageTypeName xmlns:ns0="...namespace...">
<Header>
     <Seg1>
     </Seg1>
</Header>
</ns0:MessageTypeName>
Is there a way this can be handled at the File Sender adapter side . I am aware about adding adapter module. Is there any other way to add the missing two namespace tags at the top and bottom of the file .
any help would be appreciated.
regards
Nilesh .
Edited by: Nilesh Taunk on Apr 7, 2008 2:11 PM

Hi Nilesh,
Yes it is possible in File sender adapter to give the namespace. In FCC you can give inside Document Specification.
Under Document Name, enter the name of the XML document.
The document name is inserted in the message as the main XML tag. This is mandatory for the mapping.
Under Document Namespace, enter the namespace of the document.
The namespace is added to the name of the document. This is mandatory for the mapping
I hope this will help you.
Regards
Aashish Sinha

RFC-XI-FILE Asynch Scenario

Hi All,
i am working RfcXiFile Asynch. Scenario by using Proxy. i created ABAP proxy in R/3 system and exececuted in XI server. it's working fine. All design and Configuration in IR, ID over. i tested the configuration, it's fine. But the problem is file is not created in the receiver.
and no messages will be displayed in SXMB_Moni. Anybody came across this situation, Please let me know the solution asap.
Thanks & Regards,
Nagarjuna.

Hi Sarvesh,
What i have done exactly is:
After completeting the design part in IR, i created a proxy class in R/3 by using the SPROXY tcode. There, the following objects are generated, they are
Class ZSRCO_RFC_RESP_MI Proxy Class (Generated)
Structure ZSRRFC_RESP_DT1 Proxy Structure (Generated)
Structure ZSRRFC_RESP_MT1 Message type for RFC Response
then i create report in R/3 by using SE38,
there i called the function module and my internal table gets populated.
in the same report i created the object for my proxy class and called the proxy also.And i declared the data for proxy class & structure.
The same report i executed in XI server, the data is displayed.
but in SXMB_MONI, no messages are displayed.
i am sure that i configured receiver communication channel properly.
For this scenario, sender communication channel is not required, becuase instead of that we are using the Proxy right?
So, please try to under stand my scenario and get back to me with proper solution.
Thanks,
Nagarjuna.

Polling issue in File Adapter scenario

Hello Experts,
I have a scenario where in I am using a batch command to rename a file before processing it using "run operating system command before message processing". The command works fine and renames the file, but the issue is that it does not process the renamed file in the same polling interval.
In next polling interval the file is processed as expected.
Can you please let me know the reason why this might be happening?
Thanks.

Hi Ravi,
First the file is picked and then the pre-message processing OS command is executed and then the message is processed. Processing of the message is not dependent on whether the OS command gets executed successfully or not. Basically, PI issues the OS command and then processes the message.
So if you have renamed the file using OS command it should be picked up in the subsequent interval.
Hope it helps!
Cheers,
Anand

Extra Blank Line gets added at the Beginning of the file by File Adapter...

Hello All,
I have created an RFC to File Adapter scenario in PI 7,1 and I am using Content Conversion in the File Adapter to convert the payload structure to flat text file. The input Structure is simple as follows:
<File>
<FName>some file name</Fname>
<Record>
<Data>
      <Line>Text Lines</Line>
</Date>
</Record>
</File>
while using the following Content Conversion Parameters: While I have defined "Record" as Structure.
Record.addHeaderLine   = 0
Record.fieldSeparator      = 'nl'
Record.endSeparator      = 'nl'
Here everything is working fine except that the text file getting generated has a blank line at the beginning. I was thinking that by adding "Record.addHeaderLine   = 0" parameter, no header line will be added to the file but this seems to be not working. I tried to include the top element "File" with the same parameters and different combinations but was not able to achieve the result and it stopped the file creation altogether.
So, I'll appreciate if anyone can suggest something to get rid of the this blank line at the beginning of the file.
Regards,
Athar

Extra blank line is actually provided for the FNAME node, but not displayed because of it has different structure with Record node.
Change the structure for FNAME to :
<FName>
<Data>
<Line>some file name</Line>
</Data
</Fname>
this way "some file name" will be dispalyed in the text file at the first line of file. To remove it use this trick, define the following values in Content Conversion Parameters:
in the Recordset Structure : FName,Record
FName.fieldFixedLengths     = 0
FName.fixedLengthTooShortHandling =     Cut
FNamee.fieldSeparator = '0'
FName.endSeparator =     '0'
Record.fieldSeparator = 'nl'
Record.endSeparator = 'nl'
Rgds,
Triana

Issue in Sync-Async bridge(RFC to File) scenario

Hi All,
My scenario id RFC to file synchronous scenario.Following the below link, I configured everything and its working fine. I am working on SAP PI 7.31 Dual Stack.
http://scn.sap.com/blogs/henrique/2007/08/02/syncasync-scenarios-without-bpm
As mentioned in the above link, I created the file with Message Id as file name and correlating with the message id(Using WaitResponse and Notify beans).Its working fine. But I don't want the file name to be as Message Id. Then in that case, please suggest me how can I correlate the request and response messages.What are the possible ways of doing it.
Thanks,
Madhurima

there is not a best way, just what you need to archive, take the file name as you mentioned is not the best practice, so you can use another parameter provided by SAP.
To evaluate the following attributes in the PI message header, set the corresponding indicators:
○ File Name (technical name: FileName)
○ Directory (technical name: Directory)
○ File Type (technical name: FileType)
○ File Encoding (technical name: FileEncoding)
do any of them are good for you?
Rdgs

R/3(RFC)-----XI---------FILE scenario

Hi All,
I developed the scenario like RFC>XI->File Asynch Scenario by using ABAP Proxy(Client). Can i use business service for receiver in this scenario?
All http connections between R/3 and XI are configured. Could you please explain me how to test this scenario.
Thanks<
Nagarjuna.

Hi,
1) Check wether the Message Mapping is working correctly by testing with test data.
2) You can test ur complete scenario in Configuration from TOOLS -> Test Configuration.
There u can find whether Sender Agreement,Receiver Agreement,Interface Determination and Receiver Determination are correctly configured. By giving Payload.
3) Check your Communication Channel in RWB.
Because if u r using Content Conversion, there will be some problem. So check this.
Thanks,
Kish.

Error in RFC to FTP asynchronous scenario

Hi Experts,
I have created RFC to File(FTP) scenario in SAP PI 7.31 AEX(java only) server.
When I execute RFC in sender SAP server, it gives run-time error(dump) as "call to messaging system failed".
But it successfully creates text file in target FTP server.
In message monitoring I found 2 messages for this.
First has status 'Canceled' with below message log,
Second message has status as 'Log Version' with no message log and with below message details.
Please suggest/guide me how to rectify this run-time error.
Thanks,
Amit Patil

Hi Jens,
I tried your suggestion, but couldn't work.
But I found 1 doubtful thing which is Quality of Service. It is found as
Quality of Service
BE
in message details of 1st message.
Also in message content of 1st message it is as
9/18/2014 1:36:51.053 PM
Information
File adapter receiver: processing started; QoS required: BestEffort
I don't know from where is getting set as 'BE'. It should be 'EO' since my scenario is asysnchronous.
Please suggest.
Thanks,
Amit Patil

RFC-XI-File Adapter scenario

Similar Messages

Maybe you are looking for