Xml to flat file scenario

hi guys,
I am new to XI.am tryin to configure xml to flat file scenario.i have configured the scenario but the problem is am getting the flat file into my receiver system with no content..what might be the problem.pls do help me out

Hi,
Please find here with the required parameters for receiver end file to get it as flat file
Please refer below scenarios, this could be used as reference for your scenario
IDOC-XML to flat file
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a
XML to Flat file conversion
XML to flat file conversion
File Receiver with Content Conversion
/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
Configuring the Receiver File/FTP Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/95/bb623c6369f454e10000000a114084/frameset.htm
Please see the below links for file 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 - FCC
/people/michal.krawczyk2/blog/2004/12/15/how-to-send-a-flat-file-with-fixed-lengths-to-xi-30-using-a-central-file-adapter - FCC
File Content Conversion for Unequal Number of Columns
/people/jeyakumar.muthu2/blog/2005/11/29/file-content-conversion-for-unequal-number-of-columns - FCC
Content Conversion (Pattern/Random content in input file)
/people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file - FCC
Thanks
Swarup

Similar Messages

XML File to Flat File scenario: Reciver file adaptor content conversion

Hello Friends,
Currently I am working on XML File to Flat File Scenario.
I used receiver side File adaptor with content conversion.
My receiver side adaptor is giving error. Error is given below.
Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Parameter '.fieldFixedLengths' or '.fieldSeparator' is missing
My content conversion parameters are as:
row.fieldNames                           Customer_ID,Name,Address,Phone
row.fieldSeparator                      ,
row.processConfiguration          FromConfiguration
row.endSeparator                       'nl'
Can you please suggest me what kind of error is this?
Regards,
Narendra

Still I am facing below given issue.
2010-06-08 15:34:25     Error     File adapter receiver channel CC_Customer_FlatFile_Distination is not initialized. Unable to proceed: null
2010-06-08 15:34:25     Error     Exception caught by adapter framework: Channel has not been correctly initialized and cannot process messages

Urgent, Help on conversion: xml to flat file

Dear experts,
Here is the scenario, XML FILE ->XI-> JMS
In JMS recevier side, we use localejbs/AF_Modules/MessageTransformBean to convert xml to flat file.
Transform.Class: com.sap.aii.messaging.adapter.Conversion
Transform.ContentType: text/plain;charset=utf-8
xml.conversionType: SimpleXML2Plain
xml.fieldFixedLengths: 5,20,5,8
When input source xml file contents are non-unicode, it works fine.
But when the contents contain unicode characters such as Chinese word, it works but with wrong length in the output flat file. It seems xi treat one Chinese word length is 1. Actually, one chinese word should take 2 bytes.
My question is how to make XI handle unicode characters with correct lengths while conversing to flat file.
Thanks in advance.

Jai Shankar
Thanks for your response.
I am already using the standard adapter modules provided by SAP:
localejbs/AF_Modules/MessageTransformBean
Transform.Class: com.sap.aii.messaging.adapter.Conversion
My input file's encoding is UTF-8
"You need to change the encoding scheme according to your input file" , do you mean change the output file's encoding or else?
I can't find the article you mentioned: "Encoding schemes in XI", Would you please give me the link?
Thanks a lot.

Reg error in flat file to flat file scenario

Hi techies,
Iam just starting working with XI scenarios.
In base flat file to flat file scenario which is mentioned in wiki.sdn
http://wiki.sdn.sap.com/wiki/display/XI/FLATFILETOFLATFILE
I had completed entire scenario. After generating sender file. Iam getting this error in runtime work bench.
Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Parameter 'CONTACTS.EMP.fieldFixedLengths' or 'CONTACTS.EMP.fieldSeparator' is missing
Please suggest how to resolve this error.
Thanks in advance,
Regards,
Kiran

Hi,
From your error description,
Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Parameter 'CONTACTS.EMP.fieldFixedLengths' or 'CONTACTS.EMP.fieldSeparator' is missing
it is clear that you have missed out either or both the 2 parameters in receiver file adapter content conversion, namely EMP.fieldFixedLengths and EMP.fieldSeparator.
From the example that you followed, use the following values for the 2 parameteres is the output file is a comma separated file:
EMP.fieldFixedLengths: 8,10,10
EMP.fieldSeparator: ,
I have assumed that the lengths of the fields NAME,ADD,MOBILE are 8,10 and 10 respectively. Change them according to your requirement.
Use any other value in place of comma(,) in EMP.fieldSeparator according to the requirement.
Hope it helps you buddy!!!
Thanks
Biswajit
Edited by: 007biswa on Feb 22, 2011 9:25 AM
Edited by: 007biswa on Feb 22, 2011 9:28 AM

Flat File to Flat File scenario

Hi all,
I have a flat file to flat file scenario. I pick up a file in a specific format and produce a flat file in tab delimited format after some mapping.
Everything is ok. All the functionality is working perfectly. However, there is one small error. In case the source file is empty, there is an error message in SXMB_MONI (which is correct as there is no XML content) but I still need to generate an empty output file.
Is this possible ? Can I change something at the 'File Content Conversion' level ?
Any advise will be highly appreciated.
Thanks,
Freddy.

Hi Freddy,
>>>Problem while determining receivers using interface mapping: Error while determining root tag of XML: BOM / charset detection failed.
The charset of the XML cannot be determined. That is written clearly in the message.
Is your XML belongs to UTF-16 or UTF-32? Then it needs a BOM which is missing.
Have a look at below link.
http://en.wikipedia.org/wiki/Byte-order_mark
Check, if there is an XML header and which charset is mentioned.
Regards,
P.Rajesh

R/3 46C(IDOC) -- XI -- Flat file scenario

Hi
Is there anyone who could give me information on a R/3 46C(IDOC) --> XI --> Flat file scenario?
Many thanks!
br
Göran

Hi Manish
We are using a standard IDOC called PROACT.PROACT01
(We are using transaction sa38(Report RSMIPROACT) in R/3 to send our IDOC.)
First we create the technical and business systems in SLD
Second we transfer these to the repository.(I think the only thing you need to do is to update the SLD cache to get them there - Design : Integration builder --> Environment --> clear SLD cache)
Then we just use the configuration wizard(Configuration : Integration builder --> Tools --> configuration wizard) to map everything together - defining sender and receiver etc(You get the configuration wizard tool by patching XI to patch level 4 or 5).
I assume that you have made all the configurations accordingly to the XI configuration guide which you can download from the service marketplace.
This is just a hint but maybe it can give you a start.
br
Göran

IDoc to Flat file scenario - abap mapping

Hi All,
I have to do some IDOC to Flat file scenarios. In Order to generate the file in required format I will have to add all segments(Nodes) of Idoc in FCC receiver. We also have other option of doing it through ABAP Mapping which I found in one blog.
Now my question is : Is it better way of doing it through FCC or ABAP Mapping?
Ofcourse from development point of view ABAP Mapping looks easier as FCC is very time consuming task.
Is there and performance issues in either of the approach?
Thanks and Regards,
Atul

Hi VJ and Harald,
Thanks for your replies.
I am not having PI7.1 however the given blog was very informative.
I will try using file port approach as suggested.
Thanks and Regards,
Atul

Call Pipeline in orchestration for converting XML to flat file

Hi ,
Can we call Pipeline in orchestration for converting XML to flat file ?
Or we have some another option for this task ?
Prakash

Hi,
You can refer this article from Abdul Rafay on how to work with Flat files and how to call receive and send pipelines within your orchestration. He
has provided detailed step by step explanation of the process.
Calling Send and Receive Pipelines
from the orchestration expression shapes
The code shared by Abdul at http://abdulrafaysbiztalk.wordpress.com/files/2009/06/processingflatfiles.doc (Change the extention to rar) and try it.
One common mistake I have seen people doing will working with Flat File Assembler is that they miss to set the Document schema property in the Properties
window to the flat file schema.
If the Document schema property is not specified, runtime schema discovery will be attempted. During schema discovery, BizTalk Server attempts
to determine the correct flat file schema to assemble the message with, based on the namespace and root node of the message, its added performance hit.
Rachit

OSB XML to Flat file(write)- MFL?

Hi,
OSB 11G
I will be invoking the db to get XML data and I have to write to a text file(pipe delimiter).
I saw below forum, but I am not sure how to create MFL .Can you anyone pls mention the steps. (MFL ->XML to flat file )
Do I have import xsd in Native Builder and convert to a flat file with pipe delimiter ?
How to write a CSV file in OSB
Thanks
Edited by: soauser on Jul 7, 2011 8:07 PM

truth must be said, MFL is very sensitive to input data, any deviation from the contract is punished with a NullPointerException, especially when the input is in binary format. One would expect a better error message, but what can we do.
Make sure your input data complies with the Schema, for instance do a xsd validation...

How to test the RFC to Flat File scenario

Hi,
How to test the RFC to Flat File scenario
regards,
kiran

Hi,
After running the RFC it's going Dump.
this is the error message i got.
"Error analysis
An error occurred when executing a Remote Function Call.
"CPI-C error CM_RESOURCE_FAILURE_NO_RETRY"
Status of connection.... "CODE=CM_RESOURCE_FAILURE_NO_RETRY -1 -1 SAPCODE=666
CONV="
Internal error code.... "RFC_IO5"
There is an error in the communication system. To clarify
and resolve the error, contact your system administrator.                     "

J2SE XML to Flat File Content Conversion

Hi
I've currently got a scenario which sends a flat file to the integration server, it gets mapped and sent to a receiver adapter on a deployed j2se engine.
I'm now trying to convert the xi-xml structured file to a flat file again on the j2se side (the same flat file format it originally had).
My original flat file looks like this -
477
477=AA1
My xml file looks like this -
<?xml version="1.0" encoding="UTF-8"?>
<ns0:ResultMessage xmlns:ns0="urn:xxxx-com:a_test_j2se_filetofile">
<Item>
          <field1>477</field1>
</Item>
<Item>
          <field1>477</field1>
          <field2>AA1</field2>
</Item>
</ns0:ResultMessage>
I am using these content conversion parameters:
xml.addHeaderLine=0
xml.fieldSeparator==
xml.endSeparator='nl'
I get this error on the integration engine (sxmb_moni):
Error while sending by HTTP (error code: 500, error text: Internal Server Error:java.lang.NullPointerException) (See attachment HTMLError for details)
and the j2se adpater log says this:
17:16:32 (4120): Message "13b9d644-54c9-4ffb-0c40-db4c14458d77" of type "application/xml", kind "B" received
17:16:32 (4124): Parsing XML message
17:16:32 (4131): ERROR: Message processing failed with "java.lang.NullPointerException"
What am i missing?

So, now... I did a test configuration in XI and sent your test-payload...it worked.
The J2SE adapter configuration:
File adapter java class
classname=com.sap.aii.messaging.adapter.ModuleXMB2File
version=30
mode=XMB2FILEWITHCONVERSION
#Adress for XMB endpoint -
XI.httpPort=8111
XI.httpService=/file/receiver
#File Adapter specific parameters -
file.createDir=1
file.targetDir=c:/transfer/inbound
file.targetFilename=xmboutput.txt
#file.writeMode=append
#file.writeMode=overwrite
file.writeMode=addCounter
file.counterMode=immediately
#file.counterMode=afterFirst
file.counterSeparator=_
file.counterFormat=00000
file.counterStep=1
#File Content Conversion specific parameters -
xml.addHeaderLine=0
xml.fieldSeparator==
xml.endSeparator='nl'
And here the configuration of the receiver communication channel in the integration directory:
Adapter Type: XI
Receiver
Transport-Protocol: HTTP 1.0
Message-Protocol: XI 3.0
Adapter-Engine: Integration Server
Adressing-Type: URL Address
Target Host: <yourJ2SEip>
Service Number: 8111
Path Prefix:http://<yourJ2SEip>:8111/file/receiver
Authentication Data
Logon data for non-SAP systems
User
Password
That's it... sent your payload and got the wished result:
477
477=AA1
Regards,
Heinrich

Doubts in SAP(Idoc)-XI-Flat file scenario

Dear All,
I am sending Delivery Idoc from R/3 and I am able to view the Idoc in XI in transaction IDX5. Also i m able to see the XML structure with the data of the idoc in SXMB_MONI.
Now as per my scenario I have to download this to a flat file from XI.
My question is, should I have to do the creation of Data types, message types, mapping interface & interface mapping in IR or should I directly do the designing in the ID.
waiting for your reply.
Warm regards,
N.Jain

Hi,
DT, MT, MI : you will create these things for receiver flat file only.
First create
In Integration Repository :
1.     Import structure of IDOC in your scenario, In imported objects  IDOCs
              a.     In Interface Objects
1.     Create Data type for your flat file
2.     Create Message Type
3.     Create Message Interface (inbound Asy.)
              b.     In Mapping Objects
1.     Message Mapping : IDOC to Message Type of Flat File.
2.     Create Interface Mapping : IDOC to Flat file by using Message Mapping which you have created.
Make activate all these things.
In Integration Directory :
1.     Create Communication channel for File Receiver.
2.     Sender Communication channel is not required.
3.     Create Receiver Agreement.
4.     Sender Agreement is not required.
5.     Interface Determination
6.     Receiver Determination
At sender side you will take your IDoc and at receiver side you will take your flat file.
It can help you,
Regards,
Sandeep Kaushik

XML to flat file

Hi all,
Scenario:
R/3 -> Proxy -> XI -> JMS -> MQ
Is it possible to deliver a FLAT FILE to MQ via the JMS adaptor?
I need to get reed of all the XML tags, since the receiving system is expecting a flat structure.
Thanks - /Thomas

hi,
you can use the following module to remove xml tags and namespaces
the module is XMLAnonymizerBean
the url:
http://help.sap.com/saphelp_nw04/helpdata/en/45/d169186a29570ae10000000a114a6b/frameset.htm
regards,
ujjwal

Flat File scenario-error

Hi All,
I am trying a Flat File 2 File Scenario ...
my input file is..
<?xml version="1.0" encoding="UTF-8" ?>
<ns0:MTYP_name xmlns:ns0="File_File">Mustafa</ns0:MTYP_name>
I am just doing simple mapping of single field, but I am getting the following error..
<SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>internal server error: com.sap.aii.messaging.mo.MalformedMessageException: Cannot find Main Header in XMBMessage - check the message version</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText><html> <head> <title>Transport Service Error</title> </head> <body> <h1>HTTP/1.0 500</h1> <h3>internal server error: com.sap.aii.messaging.mo.MalformedMessageException: Cannot find Main Header in XMBMessage - check the message version</h3> </body> </html></SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP response contains status code 500 with the description internal server error: com.sap.aii.messaging.mo.MalformedMessageException: Cannot find Main Header in XMBMessage - check the message version XML tag Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
What is the cause of this error and also how do I change the trace logging levels?
regards,
Mustafa

Hi Raj,
Iam sending the Inbound payload
<?xml version="1.0" encoding="utf-8" ?>
- <ns:MT_DB2_S_FF xmlns:ns="http://gsll.com/DB2">
- <RSETSTRUCT>
<S1>A</S1>
<S2>A</S2>
<S3>A</S3>
</RSETSTRUCT>
- <RSETSTRUCT>
<S1>B</S1>
<S2>B</S2>
<S3>B</S3>
</RSETSTRUCT>
</ns:MT_DB2_S_FF>
regads,
Jeevan

Flat File to Flat File Scenario using File Adapter

Hi Experts,
In my scenario, requirement is Flat File to Flat file through File Adapter in PI. At sender end, we would need to use Sender File Adapter (NFS) and receiver end we would need to use Receiver File Adapter (FTP). File would be coming as a encrypted format, and the file needs to be sent in encrypted format.
Any idea how to proceed with this requirement would be helpful.
Thanks and Regards
Soumya

Hi Soumya,
You need to choose the FTP in the "transport protocol" option. Then in the FTP connection parameters choose the option Connection Security and assign the value "FTPS for control and Data Connection". Then the "Command Order" will show up below that option and you could leave the default value itself. If you are using Public private key certificates of X.509 then you could choose the option "Use x.509 certificate for client authentication" and assign the values to the "keystore" and "certificate & private key" fields.
Note: To use the FTP with SSL you need to add the CA certificate to the TrustedCAs keystore view.
Regards,
Vishnu.

Xml to flat file scenario

Similar Messages

Maybe you are looking for