> 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.7/en/datenquellenunterstuetzung-und-einbindung/june5-batch-connector/sql-tabelle-batch-header.md).

# SQL Table Batch Header

The Batch table contains all batch header data from a data source. The following table shows a possible structure of a SQL table with batch header data on the source server.

| 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"] |

A single table with batch header data can be assigned to a JUNE5 data source (here location). The following table shows the mapping of columns from a SQL table to those in JUNE5.

| Unique Identifier in JUNE5 | Possible Name in SQL Table | Description                                                                                                  |
| -------------------------- | -------------------------- | ------------------------------------------------------------------------------------------------------------ |
| Customer                   | Customer                   | Customer for whom the batch is produced.                                                                     |
| Location                   | Location                   | Location of the batch.                                                                                       |
| DataSourceId               | DataSourceId               | Identification of the data source through which the batch is retrieved in JUNE5.                             |
| Namespace                  | Namespace                  | Namespace of the batch.                                                                                      |
| Start                      | Start                      | Start time of the batch.                                                                                     |
| End                        | End                        | End time of the batch.                                                                                       |
| LotNumber                  | LotNumber                  | Batch number.                                                                                                |
| DataSourceKeys             | DataSourceKeys             | List of strings that uniquely identify measurement values within a JUNE5 system and are assigned to a batch. |


---

# 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.7/en/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.