Skip to Content

EDI using Seeburger BIC

Hi,

I am using the BIC module provided by Seeburger for EDI to XML conversion. The input EDI message is a 850 version 4010 message. I have configured the sender communication channel for Functional Acknowledgement and configured the message splitter which is working fine.

When I run this scenario for a few of the test files with a 850 4010 message, the classifier module does not recognise the EDI message as a 850 4010 message and hence the mapping(See_E2X_ANSIX12_850_V4010) is not called. There are no errors in the sender communication channel monitoring and I get only the functional acknowledgement message.

There is a warning message in the CC monitoring which says SEEBURGER/MSGSPLITTER: There is no attachment to split. So there is nothing to do

Am is missing anything here? If so could you please throw some light on this issue.

I have seen this thread seeburgermsgsplitter-there-is-no-attachment-to-spl, but could not get much info.

Thanks,

Chandra

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    avatar image
    Former Member
    Mar 18, 2009 at 07:51 AM

    You are using a Classifier -> BIC -> MessageSplitter module chain ? Have you set the split parameter of the BIC module to true ?

    If so, you should find the functionalacknowledgement being created by the bic module which will probably show a status "R" (=rejected). That means that the mapping of the edi message failed - the mapping error can be found in the attached bic log (if that is configured) or in the bic logs located on disk !

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi ALL,

      Can any one send me documents regarding Seeburger BIS.I am working on Seeburger BIS .can you tell how to design the workflow in Seeburger BIS and how to the mapping.

      Regards,

      Ramesh

  • avatar image
    Former Member
    Mar 19, 2009 at 09:05 AM

    Can you show us the biclog which should have been generated (and attached to the xi message if configured) ?

    Add comment
    10|10000 characters needed characters exceeded