# GEDI Message Log

![GEDI Message Log](/files/rpdoru0hAil5WNfSd0q0)

## Introduction

In the 'GEDI Message Log' page view in Business Central you will find an overview of all 'GEDI Message Logs'. A 'GEDI Message Log', contains information about when 'GEDI Message' has been processed. Also some other context information regarding the processing is saved in the 'GEDI Message Log'.

Not all processed 'GEDI Messages' will create a 'GEDI Message Log'. How and when a 'GEDI Message Log' is created is determined by the 'GEDI Mapping' rules.

Creating a 'GEDI Message Log' connected to a record will allow for the 'GEDI Status' to be updated after processing. Therefore it is recomended to create a 'GEDI Message Log' for the 'GEDI Mappings' where a 'GEDI Status' update is relevant.  

## Duplicate protection

One of the purposes of the 'GEDI Message Log' is to track which key references are already used by other 'GEDI Messages'. It is very common in a EDI process that updates are not allowed against the same key reference. This is prevented by setting the 'GEDI mapping' to "not allow updates", and by creating a 'GEDI Message Log' on the key reference.

For example, you have received the same sales order twice from a customer by mistake. The first time the order gets imported and the customer purchase order number is stored into External Document Number field and saved as a 'GEDI Message Log'. The second time you receive an order with that same customer purchase order number, the import will be stopped automatically and an error e-mail sent out.

## **Processing protection**

Another purpose of the 'GEDI Message Log' is to track if a request is executed or not. This can be useful to prevent certain events to create a second request before the first is executed.

For example, a sales order is released and the event creates a request for an order confirmation to be processed. If the user want to reopen the sales order again, they have to wait for the first order confirmation to be executed, before reopening the order is allowed. This is to make sure that the sent order confirmation correspond to the sales order at the time it was released.

The processing protection can be disabled in the corresponding 'GEDI Mapping Document'.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.goldenedi.com/standard-app-core-concepts/concepts/gedi-message-log.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.