In developing business with partners who have worked for a longer period of time with EDI (Electronic Data Interchange), there is likely to be a desire for communication through an EDIFACT standard, such as EDIFACT D96A.
The most common uses are edi-invoices and edi-orders, but there are also other messages that are frequent. This may include delivery notification, article lists / price lists / quotes and order confirmation.
When newer integrations are going to be set up, EDIFACT standards have often given room to more modern EDI formats based on xml, for example UBL (Univseral Business Language), or the newest Swebase variant. If you think about starting to use EDI, it’s important to make sure to use a product that converts the internal formats into real EDI formats. If you let someone “encode” the message, the likelihood is imminent that you incur unnecessary administrative costs and errors even in the future.
To be well-equipped for the future, it is important to ensure that you can receive different messages and formats from different customers. It is likely that one customer will use an XML schema such as EDI funds and another maybe EDIFACT D96A order to leave his order. It’s also common for customers to mix their messages. For order and delivery report, D96A may be used while the price list is in, for example, UBL.
Integration needs to be planned well – for example, it is important not to build an integration per customer without finding a method of exporting the area’s data, whether it’s article information, order confirmation, delivery notification or invoices. Under our solution examples, you’ll find several examples where our customers managed to use a method of exporting output and avoiding customer-unique integrations. Once the information has been exported, BlueIntegrator’s job is to filter and convert the information to the different customers’ formats.