on 09-27-2011 2:45 PM
Hi All,
My requirement is like this..
From ECC, a CSV file will be placed in AL11, from there PI need to pick it and place in a FTP server.
Can we do it without design and secondly pls help me with content conversion.
Regards,
Praveen
For File tranfer without design/mapping involved
refer this [link|http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/4383] [original link is broken] [original link is broken] [original link is broken];
For content conversion from CSV to xml file.
YOu need to know file sender content conversion
refer these links
[link1 |http://saptechnical.com/Tutorials/XI/Contentconversion/page2.htm]
[link2|http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/3228] [original link is broken] [original link is broken] [original link is broken];
[link3|http://help.sap.com/saphelp_nw04/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm]
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Bhaskar,
Thnx for quick reply.
I know file transfer can be poss without design where no content conversion required i.e. txt to txt or CSV to CSV transfer.
But my qs is this physical file transfer possible where content conversion required without mapping. Can i just create config objects and maintain FCC in sender channel to fulfill my requirement?
Regards,
Praveen.
Hi,
If you are looking at a scenario where you don't need to do any transformation to the existing file, you can use integrated configurations if you are using PI 7.1 or even 7.0 you can only create dummy interface to complete the integration scenario objects.
Read the source file in binary mode and in the receiver side use binary instead of text.
Regards,
Indranil
Yes..you can do that without mapping.
In the sender channel FCC, the document name, namespace and record structure should be given as required based on the target xml structure.
recordset.fieldNames - Name the fields as required in target xml
recordset.fieldSeparator - , (as you have csv file)
recordset.endSeparator - nl
Use dummy object names while creating interface determination, receiver determination etc.
Make sure you used the same names in FCC (document name, namespace etc).
User | Count |
---|---|
88 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.