> For the complete documentation index, see [llms.txt](https://docs.videc.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.videc.de/june5-3.5/datenquellenunterstuetzung-und-einbindung/june5-batch-connector/sql-tabelle-batch-header.md).

# SQL Tabelle Batch Header

Die Tabelle Batch enthält alle Batch-Headerdaten einer Datenquelle. Die folgende Tabelle zeigt eine mögliche Struktur einer SQL-Tabelle mit den Batch-Headerdaten in dem Quellserver.

| Customer | Location | DataSourceId | Namespace        | Start               | End                 | LotNumber      | DataSourceKeys                            |
| -------- | -------- | ------------ | ---------------- | ------------------- | ------------------- | -------------- | ----------------------------------------- |
| A        | BER      | SRCBER       | \ProductionLine1 | 01.01.2020 08:00:00 | 01.01.2020 09:00:00 | BER\_B200\_ABC | \["BER.TANK1\_TEMP1", "BER.TANK1\_TEMP2"] |
| B        | BER      | SRCBER       | \ProductionLine2 | 01.01.2020 08:10:00 | 01.01.2020 09:10:00 | BER\_B200\_BCE | \["BER.TANK2\_TEMP1", "BER.TANK2\_TEMP2"] |
| A        | BER      | SRCBER       | \ProductionLine1 | 01.01.2020 10:00:00 | 01.01.2020 11:00:00 | BER\_B202\_CDE | \["BER.TANK1\_TEMP1", "BER.TANK1\_TEMP2"] |
| B        | BER      | SRCBER       | \ProductionLine2 | 01.01.2020 10:10:00 | 01.01.2020 11:10:00 | BER\_B200\_DEF | \["BER.TANK2\_TEMP1", "BER.TANK2\_TEMP2"] |

Eine einzelne Tabelle mit den Batch-Headerdaten kann einer JUNE5 Datenquelle (hier Standort) zugeordnet werden. Die folgende Tabelle stellt die Zuordnung der Spalten einer SQL Tabelle zu denen von JUNE5 dar.

| Eindeutige Kennung in JUNE5 | Möglicher Name in der SQL Tabelle | Beschreibung                                                                                                                            |
| --------------------------- | --------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| Customer                    | Customer                          | Kunde, für den die Charge produziert wird.                                                                                              |
| Location                    | Location                          | Standort der Charge.                                                                                                                    |
| DataSourceId                | DataSourceId                      | Identifikation der Datenquelle, durch den die Charge in JUNE5 ermittelt wird.                                                           |
| Namespace                   | Namespace                         | Namensraum der Charge.                                                                                                                  |
| Start                       | Start                             | Startzeit der Charge.                                                                                                                   |
| End                         | End                               | Endzeit der Charge.                                                                                                                     |
| LotNumber                   | LotNumber                         | Chargennummer.                                                                                                                          |
| DataSourceKeys              | DataSourceKeys                    | Liste von Zeichenketten, welche die Messgrößen innerhalb eines JUNE5-Systems eindeutig identifizieren und einer Charge zugeordnet sind. |


---

# 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:

```
GET https://docs.videc.de/june5-3.5/datenquellenunterstuetzung-und-einbindung/june5-batch-connector/sql-tabelle-batch-header.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.