> 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/partner-information/system-architecture/transaction-tables.md).

# Transaction Tables

### **Golden EDI Base Application**

These table hold the transaction data during standard operations. Before going live with a system, ensure that these tables a cleared to avoid any issues. 

{% hint style="danger" %}
Manual clearing in a live system is discouraged; use the GEDIDELETE job queue for routine cleanups to prevent issues like duplicate imports or incorrect statuses.
{% endhint %}

<table data-full-width="true"><thead><tr><th>Table No.</th><th>Table Name</th><th>Description</th></tr></thead><tbody><tr><td>70019001</td><td>GEDI Message Line</td><td>Contents of a message in the queue.</td></tr><tr><td>70019002</td><td>GEDI Message Queue</td><td>Queue for all incoming and outgoing messages.</td></tr><tr><td>70019011</td><td>GEDI Message Log</td><td>Log of processed messages, used by the duplication check.</td></tr><tr><td>70019020</td><td>GEDI Status Ledger Entry</td><td>Holds all document statuses as created by Golden EDI. </td></tr><tr><td>70019021</td><td>GEDI Ship Advice Header</td><td>The header for a shipment advice.</td></tr><tr><td>70019022</td><td>GEDI Ship Advice Log Unit Line</td><td>Logistic units connected to a shipment advice.</td></tr><tr><td>70019023</td><td>GEDI Ship Advice Unit Line</td><td>Items on a logistic units.</td></tr><tr><td>70019033</td><td>GEDI Data Set Values</td><td>Temporary stored for query values.</td></tr></tbody></table>

### **Golden EDI Extended Platform**

It's advisable to clear them during testing phases or before system launch, while manual clearing during regular operations should be avoided. Single document deletions are permissible via the GUI, as configurations can be set to restrict deletions based on document statuses, thereby ensuring safe deletion practices.

{% hint style="info" %}
For automated clearing configurations, contact our support team.&#x20;
{% endhint %}

<table data-full-width="true"><thead><tr><th>Table No.</th><th>Table Name</th><th>Description</th></tr></thead><tbody><tr><td>70845581</td><td>GEDI Intermediate Header</td><td>Represents the header of an intermediate document.</td></tr><tr><td>70845582</td><td>GEDI Intermediate Line</td><td>Contains lines associated with a single header.</td></tr></tbody></table>


---

# 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 dynamically by asking a question.

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

```
GET https://docs.goldenedi.com/partner-information/system-architecture/transaction-tables.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.