Skip to Content
avatar image
Former Member

Handling BIC adapter errors


I have a scenario where my sender AS2 comm channel has a BIC module working in auto mapping mode.

The partner is expected to send only two types of EDI messages(for which he BIC module dynamically determines the map name from the EDI content)

If the partner sends any invalid document, the adapter fails as expected with unknown BIC map name exception.

As we have configured alerts for any Adapter engine failures, we receive too many alerts everyday.

Is there a way, this exception can be handled without an Adapter engine faialure?


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • May 24, 2013 at 12:45 PM

    Hi Senthil,

    Is that an Invalid EDI message among the 2 EDI types that you have configured? If this is the case, then you need to ask the Sender to send only valid EDI files. If this failure is happening due to some other EDI type which you haven't configured, then you may follow one of the below

    1) Try to use a different AS2 receiver name for 2 EDI types (that you have configured) and a different AS2 receiver for any EDI types apart from that 2. For the EDI files that are not valid to your business, you can simply receive them in the 2nd AS2 receiver and you can simply archive them.

    2) Try using AUTO as the BIC mapping parameter in your AS2 sender channel. This way even if you receive any EDI type that is not in use, the BIC mapping will still convert the data and you can archive the same.

    Hope this helps! If not provide some more details on the AS2 sender configuration that you have.


    Add comment
    10|10000 characters needed characters exceeded

    • Hi Senthil,

      Unfortunately there is no such option in the BIC Module.

      This is an unusual business scenario. If they can't stop sending the Invalid (or non-EDI messages), then you shouldn't use the BIC module parameters in the AS2 sender. Instead you can just use your AS2 sender CC only to receive the EDI/non-EDI files from your sender (by using a dummy sender & receiver interface) and you can use a java mapping where you can check for the first 3 characters.

      If they start with ISA, then put the data in to one folder and for non-EDI/invalid files assign a different directory. The you need to have a separate configuration to pick & process the EDI files.

      Hope this helps!