> 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-class-setup.md).

# GEDI Class Setup

"A 'GEDI Class Setup', is a definition of which 'GEDI Message Code' should be used by the CIP."

![GEDI Class Setup](https://4116199904-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4Q6J1fzsyYoa0sjFct%2Fuploads%2Fwds2tiMMtffqrLd20BzK%2FCC%20Class%20Setup.png?alt=media\&token=f7b05036-a9e7-4286-8f50-91e509980396)

## Introduction

In the 'GEDI Class Setup' page view in Business Central you will find 'GEDI Class Setups'. A 'GEDI Class Setup', is a definition of which 'GEDI Message Code' should be used by the CIP when writing 'GEDI Messages' to the 'GEDI Message Queue'. This is defined per 'GEDI Class name' used for the header of the 'Message Document Type'.

For example, the CIP wants to write a new Order 'Message Document Type' into the 'GEDI Message Queue'. ORDER is the header 'GEDI Class name' for Order 'Message Document Type'. ORDER can then be defined in the 'GEDI Class Setup' with 'GEDI Message Code' "SO-01-IM". The CIP can now create a 'GEDI Message' with 'GEDI Message Code' "SO-01-IM".

It is possible for the CIP translator to have rules for fallback or override 'GEDI Message Code' as well.

In 'Reference Property names' field it is possible to determine which 'GEDI Property name' should be used as the 'Message ID' for the 'GEDI Message' that the CIP creates.

![Example of what the 'GEDI Class Setup' table can look like](https://4116199904-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCnajZpb6jyP8d1VA5elK%2Fuploads%2FH0YsW4KsjMzyxKDlVqnu%2Fbild.png?alt=media\&token=ffb9de57-ad28-46de-8060-deff464fc3a0)


---

# 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-class-setup.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.