on 01-20-2007 1:41 AM
My Scenario is File-XI-File in csv:
Input Data is a stream of data as follows:
12Records11234
23Records78663
45Records73737
I like to have Data type as follows:
InFile ComplexType
InRec 0..1
Record 0..unbounded
When file is leaving XI I would convert back to
12Records11234
23Records78663
45Records737
File Content conversion on the inbound side to XI:
Document Name: InFile
Recordset Name: InRec
Recordset Structure: Record,*
It throws me error:
<i>Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Parameter 'Record.fieldFixedLengths' or 'Record.fieldSeparator' is missing Mandatory parameter 'Record.fieldNames': no value found</i>
As you can see my input there are no field names.
How can you do content conversion in my case ?
Thanks for any suggestions.
Ram,
I dont find any difference between the two files. Can you tell us a bit more specific?
---Satish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ram,
You input file looks like fixed length, then supply 'Record.fieldFixedLengths' in the sender channel configuration
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ram,
If you dont want RECORDSET then please specify ignoreRecordsetName as true in sender communication channel.
Please see this help:
http://help.sap.com/saphelp_nw04/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm
---Satish
After spending full couple of hours I suspected about the Blog /people/sravya.talanki2/blog/2005/08/16/configuring-generic-sender-file-cc-adapter with the given parameters can not produce as expected. She missed other parameters it seems.
I gave exactly as given in the blog which is producing
<b> <?xml version="1.0" encoding="utf-8" ?>
- <ns:MT_MET_GEN xmlns:ns="urn:horizon:genericmet">
- <RECORDSET>
- <DATA>
<ROW>1234</ROW>
</DATA>
</RECORDSET>
- <RECORDSET>
- <DATA>
<ROW>4567</ROW>
</DATA>
</RECORDSET>
- <RECORDSET>
- <DATA>
<ROW>8901</ROW>
</DATA>
</RECORDSET>
- <RECORDSET>
- <DATA>
<ROW>3478346348930dskjhdkc,mcvndkjfhd</ROW>
</DATA>
</RECORDSET>
- <RECORDSET>
- <DATA>
<ROW>jhvcbmnvbksdjfhkfljd;lfjdf;ldjf</ROW>
</DATA>
</RECORDSET>
</ns:MT_MET_GEN></b>
As you can see all ROWs are not together as was described. What other parameters required here?. Any help to resolve this is appreciated.
> How did you do the content conversion?
>
> <b>DATA.fieldNames - ROW
> DATA.fieldSeparator-'nl'
> DATA.endSeparator -'nl'.</b>> Cross verify with the message type you created and
> whatever is there in the blog.
>
Moorthy,
how I'm testing this content conversion is very simple. I configured Sender Adapter channel as per parameters given. When I look at Message Monitoring with Adapter Engine I get a snap shot of how the input message has been converted. This is the first time you can see converted XML right?. Which is well before message mapping. I'm trying to find why the content conversion is different from the weblog. I even used same field names. You can try this very easy with just configuring sender communication channel.
Hi,
Refer this blog-
/people/sravya.talanki2/blog/2005/08/16/configuring-generic-sender-file-cc-adapter
In the receiver side also similar way
Hope this helps,
Regards,
moorthy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.