> For the complete documentation index, see [llms.txt](https://docs.goldenedi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.goldenedi.com/standard-app-core-concepts/concepts/gedi-conversion-lists.md).

# GEDI Conversion Lists

"A 'GEDI Conversion Document', is a table used for converting specific values"

![GEDI Conversion Lists](https://4116199904-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4Q6J1fzsyYoa0sjFct%2Fuploads%2FzTpA6Ms9t7r7xXXTq6jJ%2FCC%20Conversion%20Lists.png?alt=media\&token=2d5485af-a027-44b1-b743-c26f0d2e9478)

## Introduction

In the 'GEDI Conversion List' page view in Business Central you will find 'GEDI Conversion Documents'. A 'GEDI Conversion Document', or short 'GEDI Conversion', is a table were you can input values to be converted and used in 'GEDI Mappings' or in Code Units.

This means that code identifiers inside Business Central can be different from the code identifiers in the EDI.

## Conversion Concepts

In general you can divide 'GEDI Conversions' into some different concepts;

* **Identifier:** Convert internal Business Central identifiers to or from standard EDI codes used by the 'CIP translators'. 

  For example, maybe in Business Central a unit of measure is "BX" but the corresponding EDI standard code is "BOX". Then a 'GEDI Conversion' is used to convert the values.
* **Add Info:** Can be used to add information that has no field in Business Central. 

  For example, A customer has a fixed invoice reference they require in EDI. Then a 'GEDI Conversion' could be used to convert the customer nr into the fixed invoice reference and include in the EDI message.
* **Logical:** Can be used to convert fields in Business Central to a integer. The integer can then be used in 'GEDI Mapping' rules or in the 'CIP Translator' to flag certain scenarios. 

  For example, some order rows are articles and some are not. If we convert ARTICLES to 1, RESOURCES to 0 and G/L ACCOUNTS to 0; then we can tell the 'CIP Translator' that some rows are item related (1) and some rows are are not (0).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.goldenedi.com/standard-app-core-concepts/concepts/gedi-conversion-lists.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.