Seeburger Inbound - Classifer and Splitter

[silentbull]

Hello

I have a weird issue where all inbound EDI messages related to EDIFACT is splitting nice, but any Tradacom message is giving the following error.

  <Text>InhouseDocReader doSyntaxCheck() Offset[7309]: Could only identify segment ''END'' as dirty! (Counter exceeds) DESCRIPTION: InhouseDocReader: Syntax check of replacement file with some errors could not properly check the syntax. DocReader given up after several tries.</Text>

It seems like in any Tradacom file, it can identify only the END segment and nothing more than that. But it has correctly identifed the sender,receiver,messagetype .

We have individually tested the same file by directly giving the mapping name in the channel without any splitter or classifer which is also working fine.

Regards

Sam

[S0003485845]

Hello Sam,

can you let me know which Tradacom-Messages you try to split ?

Are you using Tradacom-Mapping that was part of the original delivered Mapping_Sys - Mappings or is this a Mapping that has been created by yourself ?

Which Version of the Adapters are you using ?

Kind Regards

Stefan

[silentbull]

Hello Stefan

We are trying both the maps delivered by seeburger and the one we created.

When we directly specify the mapping name without split, it works fine, but when we specify the classifer/mapping = auto and split = true, it gives with this error.

But we tested edifact messages which  are delivered by seeburger as well as custom ones and are fine.

We are using 2.2.2 with PI 7.4 dual stack.

Regards

Sam

[S0003485845]

Is there a possibility to provide an example message ?

And is this error only occuring after an update to the PO74 with 2.2.2. ?

Kind Regards

Stefan

[silentbull]

Hi Stefan

When we upgraded to PI7.4 dual stack with 2.2.2, we just tested one inbound and one outbound.

For the inbound we tested edifact which was fine, but later we found out it was not working for tradacoms.

We recompiled all mappings with version 2.2.2 bic compiler and loaded it and tested.

For eg., See_E2X_ORDHDR_V9 is not working as an example .

Regards

Sam