on 12-19-2007 1:05 PM
HI,
I am doing a mail(attachment)-xi-file scenario.
The message structure on the source side is :
Lead code:12929
Order ref: sp/jaksd/1212
order type: S
Item code Qty
1221231 123
1212232 78
........... ...
Please help me and tell what will be the File content conversion parameters on the file receiver side of the scenario.
Threads indeed helped.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Priya ,
If you have selected File Content Conversion as the message protocol, you can convert a text file that contains complex structures into an XML source format in this mode. The file contains various row formats in logical structures.
Please have a look upon the link:
http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/44/748d595dab6fb5e10000000a155369/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm
*Pls: Reward points if helpful*
Regards,
Jyoti
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
you first receive the xml message coming out.
read that message and make the parameters in the Receiver FCC.
RecordStructure : your root elements ( if more than one, you can specify all separated by comma)
you have to specify min 3 fields
all are prefixed with your record structure name
i.e.
structure.fieldNames : list all field names separated by comma
structure.fieldSeparator : , " comma separation
structure.endSeparator: '/n' " for new line
be sure that there is no internal spaces left.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi !
The file content conversion on the RECEIVER, depends on which output format you expect. The one you included in your post, as far as I understand is an input/source code.
Please give a sample of the expected output format.
Regards,
Matias.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Could you please let me see the actual flatfile itself?
and then show me the xml structure and with this information I will let you know all the exact parameters you need.
So the best way to do this is go to your message mapping --> Test --> Take the source xml
Also dont forget the flat file itself and if it is fixed length or not.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi priya,
.......<?xml version="1.0" encoding="UTF-8"?>
.......<ns0:MT_File_1 xmlns:ns0="http://bajaj.com/mailtofile"><dealerCode>10424</dealerCode><orderRef>SP/174 DT.18/12/2007</orderRef><orderType>R</orderType><itemdetails><itemCode>30151106</itemCode><qty>40</qty></itemdetails></ns0:MT_File_1>
by looking at your structure I feel record name is missing.
in general record structure should be as follows...
<root>
<recordset>
<field1>
<field2>...
....
</recordset>
</root>
<root> is message type and <recordset> is a row. Here in your structure recordset is missing.
if you mensioned this record set in your structure the following can be your content conversion parameters.
Record structure : recordset
dealerCode.fieldFixedLengths
orderRef.fieldFixedLengths
orderType.fieldFixedLengths
itemdetails.itemCode.fieldFixedLengths
itemdetails.qty.fieldFixedLengths
I am not sure about the last two but try
regards,
Pavani
You can use
RecordSetStructure Record, Row
Row.fieldNames=Lead code,Order ref, Order type,item code, qty
Row.fieldFixedLengths=5,15,1,7,3
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
95 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
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.