PROBLEM .beginSeparator and .endSeparator SAME !!!

[Former Member]

Hii I am doing a file sender config and my message is something like this

010TN4028260000PP345700210 2620582 005 0000000000000072020061802 000000000000000000

020TN402826000000001037331742557076 0000071641086338975600000110230000394007

025TN4028260000000010000071641086338975600097BP 0005 00000000030000000000

This is <b>only a part of the Payload</b>............

my Datatype format is

<b>OCCURANCES</b>

<Data_DT>

<Record> 1

<Header> 0..1

There are many fields....

</Header>

<Control_1> 0...unbounded

There are many fields....

</Control_1>

<Control_2> 0...unbounded

There are many fields....

</Control_2>

<Control_3> 0...unbounded

There are many fields....

</Control_3>

<Line> 0..1

There are many fields....

</Line>

</Record>

my problem is that in the payload the Start and end separator is the SAME which is |

I am having error loading files. Can some1 help me in content conversion

My Content Conversion is like this

Header.fieldNames VERTBAR1,...........

Header.fieldFixedLengths 1,.........

Header.keyFieldValue 000

Header.fieldContentFormatting trim

Header.lastFieldsOptional Yes

Header.beginSeparator |

Control_1.fieldNames VERTBAR2,.....

Control_1.fieldFixedLengths 1,..........

Control_1.keyFieldValue 010

Control_1.fieldContentFormatting trim

Control_1.lastFieldsOptional Yes

Control_1.beginSeparator |

Control_2.fieldNames VERTBAR3,........

Control_2.fieldFixedLengths 1,............

Control_2.keyFieldValue 011

Control_1.beginSeparator |

..............................

.........................

........................

ignoreRecordsetName true

[moorthy]

Hi,

WHat is the error in the Adapter Monitoring/Message Monitoring->Audit Log?

Problem may be because of key field value etc.

btw, this blog may help you.

/people/shabarish.vijayakumar/blog/2006/02/27/content-conversion-the-key-field-problem

Regards,

moorthy