on 09-10-2013 8:37 PM
Hello All,
I have a problem with the receiver FCC . I have the following text file attached. All i require is to convert it to xml and convert it back to text. I need this as I require the file name of the text file . This is a file to file scenario
The Message type is below.
MT_FILE
LINE (0..UNBOUNDED)
FileName - - ( Mapped to a UDF to get the file name )
Below is the Sender FCC parameters:
Recordset Structure : Line
Recordset Sequence: Ascending
Line.fieldSeparator :'nl'
Line.fieldSeperator: fromConfiguration
Line.fieldNames :Line
ignoreRecordsetName: true
The xml file before message mapping after the sender file content conversion looks like below.
<?xml version="1.0" encoding="utf-8" ?>
</Line>
</Line>
</Line>
</Line>
</Line>
</Line>
Are the above parameters for sender FCC correct ?
Now in the receiver what parameters i need to pass to get back the txt file before the sender FCC .
Please advise .
Thank you,
Teresa
Hi there,
if your anser to Baskar's question a) is "yes" (structure between sender and receiver different), please provide input file before sender FCC.
Thanks
Cheers
Jens
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jen,
The sender flat file structure and receiver flat file structure are the same.
I have an extra field in the target Message type called FileName as below. I am dong this as I need the file name for variable substitution.
MT_FILE
LINE (0..UNBOUNDED)
FileName - - ( Mapped to a UDF to get the file name )
The scenario is source 1 [file] to target1 [file]
source 1 [file] to target2 [Proxy]
I am attached the sample input file in my first post.
Thanks,
Teresa
Hi Teresa
If you are getting flat file and want to convert to xml, you need sender side fcc. Similarly if you have xml and want to convert to flat file then you need receiver side fcc. If you have sender side flat file and receiver side sending same flat file then you dont need file content conversion.
Question:
a) Is your sender flat file structure and receiver flat file structure different? If not, just use the simple file to file scenario without ESR objects. Just pass through scenario using configuration objects.
http://wiki.scn.sap.com/wiki/display/XI/Dynamic+file+name+for+pass-through+scenario
b) If sender side flat file strucure and receiver side structure are different then you need to do fcc sender and reciever. Please go through sap help document and below links
http://www.riyaz.net/sap/xipi-file-content-conversion-for-simple-structure/75/
http://www.riyaz.net/sap/xipi-file-content-conversion-for-complex-structures/79/
useful links
http://scn.sap.com/docs/DOC-3716
http://help.sap.com/saphelp_nw04/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm
http://scn.sap.com/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for your reply.
The sender FCC parameters are
Below is the Sender FCC parameters:
Recordset Structure : Line,*
Recordset Sequence: Ascending
Line.fieldSeparator :'nl'
Line.fieldSeperator: fromConfiguration
Line.fieldNames :Line
ignoreRecordsetName: true
I have attached the sender file in the original post. The sender file name would be ACH_BOA and receiver file name would be ACH_BOA.
The scenario is source 1 [file] to target1 [file]
source 1 [file] to target2 [Proxy]
Thanks,
Teresa
User | Count |
---|---|
70 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.