Seeburger EDI Text to EDI XML conversion failure should throw an error

[former_member841822]

Hi,

I am expecting an error message to be thrown when EDI Text to EDI XML conversion fails at Message splitter of Seeburger module. I am getting the following error in the log.

"2012-01-19T01:46:08.032-0800 ERROR [Error:ID=2150;LEVEL=3] counter value (41) of incoming field (UNB.UNH.UNT:0074) doesnt match the calculated value (39).

DESCRIPTION: Either the counter value is not filled in the source file or the counter field value is wrong. "

But my expectation is that the channel should show some error in Adapter Engine monitoring itself. As shown below, it is just showing some warning that because of above error, it is not creating the attachment. Now I am expecting the the following warning to be an error rather than just warning. Please let me know if any idea on the same.

19.01.2012 01:46:08 Information SEEBURGER/MESSAGESPLITTER: Trying to establish CCI Connection to Message Splitter Adapter

19.01.2012 01:46:08 Information SEEBURGER/MESSAGESPLITTER: Creating CCI Interaction

19.01.2012 01:46:08 Warning SEEBURGER/MESSAGESPLITTER: There is no attachment to split. So there is nothing to do.

19.01.2012 01:46:08 Information SEEBURGER/MESSAGESPLITTER: Finished splitting!

BR,

Aman

[prateek]

>> I am getting the following error in the log.

Which log is this?

[former_member841822]

Thanks you all for your inputs..

I got the solution for the same.

I need to set the mapping program name specifically rather than AUTO for bic mappingName parameter. This has turned my communication channel status in RWB into Red for errors.

Closing this thread ...

Regards,

Aman

[Former Member]

D0074 under UNT segment counts the number of segments in a message..by looking ur error it seems that ur EDI text file is not having correct counted values (which should be 39)...change the value under UNT segment and then test the edi mapping

[former_member841822]

Hi Amit,

I intentionally put this incorrect value. My requirement is to have the error in Communication channel. It is currently showing green for Adapter engine & Communication Channel even it is failed because of incorrect count.

Regards,

Aman

[Former Member]

Hi.

Always the CC will be in green, because is not problem of Adapter , the problem occurs when Seeburger try to parse the EDI to XML..however you catch the error by Functional Acknowlegment that sent when this error happens.

Regards.

Luis Ortiz.