Hi Experts,
Right now, we are receiving inbound Edifact/EANCOM messages from our partners. When using seeburger we had no issues processing these messages as Edifact. However, when using B2B Add-on, we are getting errors since these are treated as EANCOM and EDIFACT separately. We would like to process EANCOM as EDIFACTto avoid creating 2 EDISeparator Sender channels for EANCOM and EDIFACT.
This should be possible if EANCOM tables were not uploaded into the B2B Cockpit. Unfortunately, we uploaded EANCOM tables early on. Are any of you familiar about this issue? We can’t seem to find a way to delete the EANCOM tables or a way around this.
Thanks in Advance!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.