Cross references

In this table you can register rows for cross references to different transaction types. A transaction type (business document) consists of different data that can contain cross references.

You select a row with a transaction type in the table. In the box to the right, you select for which data you want to add the cross reference. Then you add a row in the table to the far right for the actual cross reference, between the code in Monitor ERP and the code used in EDI EDI is the acronym of Electronic Data Interchange. EDI is about exchanging electronic business documents with your business partners, e.g. customers and suppliers. The EDI concept can be wide and a bit unclear, and can many times be used about all types of documents which are sent electronically, even if it might be PDF files sent via e-mail or publishing business documents on a website. What we refer to as EDI – and what is traditionally meant by EDI – is structured business documents following given standards, electronically sent or received and which are compiled and interpreted automatically and that is integrated with the customer's/supplier's ERP system. message.

A cross reference is used when the code in the EDI messages differs from the corresponding code in Monitor ERP, even though it has the same meaning. For example, "pcs" is used as part unit in the EDI message while Monitor ERP uses "items" as part unit.

Name

Here you enter an optional name for the cross reference.

Transaction type

The transaction type to which the cross reference applies.

Module

Here you see to which module the selected transaction type belong.

Direction

Here you see the direction in the selected transaction type.

Log

By using the button Log you find a changelog for the cross reference. Here you see who modified the information as well as when. You also see what has been changed, with the value before and after the change.

Included in behavior

By using the button Included in behavior you see in which behaviors this cross reference is used.