Month: September 2018

EDI stands for Electronic Data Interchange. In retail, EDI is used to automate orders, invoices and dispatch notes. EDI replaces order processes, transactions and communication that were previously done on paper or per fax machine. Simply put, EDI makes sure that all company systems of trading partners speak the same language so they can easily and quickly communicate with each other with a limited number of errors.

EDI consists of two main components: translation and communication. During the translation, a company document is changed into a standardized EDI format, such as EDIFACT, S@les in construction, HRXML, TEA{{S, SimplerInvoicing, RosettaNet or the standard Onetrail XML. Each trading partner has its own collection of EDI standards and specifications. The translated information is then safely sent to the receiver.

There are several required communication standards and protocols in order to do EDI with large trading partners. Due to the complexity, security risk and highly technical character of EDI, many trading partners choose to outsource these activities to a specialised EDI provider.

When a buyer wants to place an order with a supplier, he creates a digital purchase order. EDI software then turns this purchase order into an EDI standard version and sends it to the supplier.

The supplier returns an order confirmation via EDI, stating the order was received. When the order is ready to be dispatched, a digital packing slip (a DESADV) can be sent to the buyer . As soon as the order has been delivered, the supplier sends the buyer an invoice via EDI.

It is likely that the supplier uses different technology than the buyer, yet his system can receive the information because the message was translated into a universal standard format. There are many different types of EDI transactions. Because EDI is a standard data format, there are specifications for every type of transaction. Specifications and EDI requirements can vary per trading partner and industry.

By using a standard data format, EDI compatible companies can exchange electronic information without human interference. This way, EDI offers a technical basis for automation.

From an operational point of view, this is logical because it reduces human error and streamlines the order process. Trading partners are able to process orders more quickly, more affordably, and with less mistakes.

Onetrail builds a specific EDI connection for customers that can be used to digitally send messages directly from a company system to the Onetrail Trading Partner Network. It does not matter which message format is used: EDI, XML or flat file, each format is accepted. In addition, Onetrail has special solutions for PDF and Excel.

Onetrail translates the incoming messages into the Onetrail XML standard. The Onetrail XML standard is a universal format that can be transformed into and from all other standard formats. This way, messages can be exchanged with all trading partners that are connected to the Onetrail Trading Partner Network.

DESADV is the abbreviation for DESpatch ADVice. This is the electronic version of the paper packing slip. This EDI message contains all information relating to the delivery.

In the most concise format the DESADV only states who sends the order, who receives the order and at what time. An article code (EAN / GTIN / SKU) and quantity are also mentioned per order line. The extended version of the DESADV also contains the data per pallet with all products on the pallet and the associated batch codes. We call this batch code a SSCC.

The DESADV can also have an important role by automating the invoice check. By using the EDI notice ORDRSP (to confirm purchase price per piece), DESADV (actual receipt) and INVOIC (what is actually invoiced), the entire process from import and verification of the invoices can be automated.

The DESADV indicates for each SSCC which SKUs (EAN/GTIN) are on the pallet and in what quantity. The great advantage of an SSCC is that the moment an employee scans the SSCC, the data of all articles on the pallet are immediately imported and visible in the WMS.

On a daily bases large numbers of DESADV messages are sent from and to the trading partners connected to the Onetrail Trading Partner Network.

Payload agnostic means that the service is not aware of the content it is serving. In case of SOAP with XML it means the usage of, for example, a CDATA element or MIME message containing the actual XML message. Some examples within the standards community of payload agnostic services are: AS2/AS4 and ebMS.

In addition to AS2, the Onetrail Trading Partner Network REST ODE Service for Sellers is payload agnostic, meaning the service is generic for all order related message types and thus not aware of the content of the message. Message validation (schema validation in case of XML) needs to be performed outside of the service. The advantage here is that the connection can be set up easily, regardless of the order type.

The disadvantage of payload agnostic services is that the service is not validating against the schema of the message which can cause schema errors at the service provider.

The advantage of a payload agnostic service is that only one service is required to transfer all types of messages.

A namespace is a method to prevent element name conflicts in XML.

In XML, element names are defined by the developer. This sometimes results in a conflict when mixing XML documents with different XML applications. In XML schemas, the namespace is used to distinguish different template libraries from each other.

Name conflicts in XML can be avoided by distinguishing the different libraries by adding a prefix. We call this prefix a namespace in XML documents. This namespace can also be used to distinguish different types of messages (order, packing slip, etc.).

In its basis, the namespace is not intended to look up information. However, companies often use the namespace as a pointer to a library with underlying information.

A library is a scheme with common elements and works in the following way: you have an order, order response, packing slip and invoice. All these messages have elements in which the customer code (at Onetrail a GLN) and address data are listed. Without namespace you have to redefine these elements per message. By including a schema with a namespace in the XML document, you can use it in all messages. The schema with the common elements, the library, can then be included in XML documents by means of an include.

Namespaces in XML are often considered difficult and cumbersome. At Onetrail, we have a different opinion. We mainly see the advantages of the namespace, which serve as a powerful tool to keep our message traffic on the right track. Onetrail gladly helps you to apply namespaces in your process.

A good example is the UBL message set. There are different values with regard to amounts between the standard UBL and the Dutch taxonomy version. Here, the different versions are distinguished with the help of the namespace.

A Global Location Number is a number of 8, 12, 13 or 14 positions long (depending on the country), with which a physical location of, for example, an office, shop or warehouse is identified as a unique address. A GLN enables unique and unambiguous identification of physical or operational locations worldwide. In Germany, a GLN is also called an ILN.

GLNs ensure efficient communication and processing of names, addresses and other information about certain locations by not transmitting them with every transaction. This information is only communicated once, stored in the relevant system (e.g. ERP or CMS system) and then retrieved by referring to the unique GLN. It is possible to translate a GLN number into a GS1-128 barcode or EPC / RFID tag for scanning purposes.

Why use a GLN instead of an internal code? Each company can design its own internal code structure to identify locations. Although this may seem the easiest and fastest way, this may cause problems such as mentioned below.

A GLN is used to indicate a unique location. They are widely used for electronic data exchange (EDI) between trading partners.

The GLN standard is managed by GS1, a non-profit organization that develops worldwide standards and solutions for a more efficient and better visible supply chain in various industries. In the Netherlands this role is fulfilled by GS1 Netherlands.

Onetrail is an official GS1 GLN provider and uses a GLN number for all its customers to identify the location. When a company does not have its own GLN number, an official GLN number is assigned by Onetrail.

To enable the smart use of data, large quantities of ‘raw’ data from various sources must be securely connected, normalised, linked and made accessible. Converting this raw data into relevant and actionable data is what we call data logistics at Onetrail.

The amount of data and the speed with which data is growing, is becoming increasingly determinative for the extent to which the customer can be put and the centre and hence the success of companies.

Data is increasingly being retrieved real-time at the source, making the data chain increasingly sensitive. This also increases the complexity of data logistics and it is becoming more and more a task for specialists.

There is a growing number of companies that realise that the proper organisation and daily control of their data logistics is crucial for their success. Therefore, they enter into a partnership with a specialist in data logistics, such as Onetrail.

We have a connected economy with data as raw material. Digital is increasingly becoming the norm in which organisations place the customer more and more at the centre and use technology to achieve the ultimate customer focus. An important consequence of this development is that companies are increasingly connected to each other and are therefore dependent on each other’s processes and data.

The error-free exchange of data between companies is therefore a subject that cannot be ignored. To ensure continuity, scalability and reliability of processes, companies must get a grip on their data logistics, otherwise they will lose their relevance in the chain.

A growing number of companies realise that the right layout, availability and daily control of data is crucial for their success. How do I keep adding value in the new digital world and how can I continue to carry out my processes as well as possible?

For trading parties, suppliers and retailers, these questions are closely linked to the usability, correctness and topicality of the data in their systems. This data must increasingly be available digitally at any time, not only for their own processes, but also for suppliers and, above all, for their customers.

Extensive availability of data is no longer a unique added value, but a necessity for the existence of every company. In this way, in addition to the physical trade chain, a data logistic network of online connections is created in which the mutual dependencies are becoming ever greater. More and more business processes will become dependent on good and reliable data logistics in the future.

Onetrail is the only trading partner in the market where every company can connect its data logistics in the form of product and order data to all its partners, such as an advanced EDI system would do.

Onetrail does not stop at EDI but also resolves the differences in syntax and content. Normally, such a solution would be far out of reach for many parties, but Onetrail makes it accessible, easy and cost-effective for everyone through a user-friendly, stable and easily accessible online portal. More than a thousand parties are connected to the Onetrail Trading Partner Network.

Onetrail is the specialist in data-logistical challenges. We develop solutions that meet the latest technical requirements and help organisations with their data-logistic change.

Our way of working is pragmatic and realistic and is done in close cooperation with our customers. We take the responsibility for the key processes of our customers very seriously and put continuity and stability of the network and our customer’s wishes first. We are proactive and innovative in how we approach data-logistic processes can be improved continuously.