> 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/acron-9.3/en/anlagenkonfiguration/jobs/auftragsmappe/exportauftrag.md).
# Export job
Report job with custom configuration options including time frame for output.
The report jobs can be moved within the [job folders](/acron-9.3/en/anlagenkonfiguration/jobs/auftragsmappe.md) by [drag & drop](/acron-9.3/en/erklaerung_zur_bedienung.md#drag-drop).
### Name
Name of the export job
### Active
Activated/deactivate the job. Deactivated jobs are not executed.
## General
### Export type
Selection from
* Process data
* Primary interval data
* Secondary interval data
* Daily data
* Weekly data
* Monthly data
* Annual data
* Messages
* Malfunctions
* Events
All events within the selected time frame are exported to one file; otherwise the events are exported to separate files.
* Local process data raw values daily basis
With this option the raw data of the external variables - that is, the untreated values, as they are stored in the database - are exported.
The data of a whole day are written to a file each time.
The files are named according to the following scheme: `ACRON_Raw_Data_yyyymmdd`\*
`yyyymmdd` is the date of the daily values in question.
Note
The time stamps in the export file are displayed in UTC (*Coordinated Universal Time*) format
Note
The scope of the selection options depends on the activated [compression levels](/acron-9.3/en/anlagenverwaltung/register-datenbank.md#verdichtungsstufen).
### Path
ACRON places exports in this folder by default. Click the button in the next dialog box to select an existing directory.
### File
Name of the export file
Note
If no file extension is given, ACRON creates a file with the [file extension preset](/acron-9.3/en/anlagenverwaltung/register-datenexport.md#dateiendung) in Plant Management for data export (normally .csv).
The name may be used only once in each job call, otherwise the file will be immediately overwritten.
### Compress file
Compression in Zip format
### Add date to file name
The current date is appended to the file name.
Note
If the date is generated automatically, you can start this job several times a day by a parameter call, generating different export files.
### One row / Multiple rows
Selection from
* One row per time stamp (single-line)
All process variables in one data line per time stamp
* One row per PV and time stamp (multi-line)
Separate data line per process variable and time stamp
### Export only data records with values
Exclusive export of data records with values
## Time frame
### Length of the report time frame
Length of the report time frame
### Unit
Unit of length of report time frame
### Time frame end
Selection of the time frame end
* Now
All data up to the current time.
* End of hour
At 12:31 hours, for example, includes all data up to 13:00 hours.
* End of day
All data until end of day.
* End of month
All data until end of month.
* End of year
All data up to December 31 of the selected year
Note
For shift reports the time frame end cannot be changed.
If a shift goes into the next day, e.g. 22:00 - 6:00, it is displayed correctly.
The postponement of the time frame end in this case relates to the day on which the shift begins.
### Time frame end moved back by
Number of hours, days, months or years by which the preset time frame for data output is to be moved back.
| | |
| ----------------------------- | ------------------------------------- |
| Current system time | 8/16/2014 |
| Time range | 1 month |
| Time frame end = End of month | 8/31/2014 |
| Moved back by = 3 | 5/31/2014 (corresponding to 3 months) |
The time frame extends from May 1, 2014 to May 31, 2014.
When the current date reaches September 1, 2014, the time frame switches from June 1, 2014 - June 30, 2014.
### Unit of time offset
Selection of the unit of the time offset
## Filter
### Filter for variables - Time reports
Display of an active or inactive filter
| Data | Auto variable | Manual variable | Calculation variable | Key figure |
| ---------- | ------------- | --------------- | -------------------- | ---------- |
| Process | x | x | | |
| Interval\* | x | x | x | x |
| Day\* | x | x | x | x |
| Week\* | x | x | x | x |
| Year\* | x | x | x | x |
\* The data are only available when a compression method is active.
### Filter for variables - Alerts
Display of an active or inactive filter
#### Alert variables and alert groups
Display of an active or inactive filter
#### Use only specific alert types
The nature and assignment of the alert types depend on the system delivering the alerts.
| | |
| ---- | --------------------------------------------------------------------------------- |
| HiHi | The alert is triggered when its start value is exceeded. |
| Hi | The alert is triggered when its start value is exceeded. |
| Lo | The alert is triggered when the value falls below its start value. |
| LoLo | The alert is triggered when the value falls below its start value. |
| Dev1 | The alert is triggered by a level 1 deviation. |
| Dev2 | The alert is triggered by a level 2 deviation. |
| Modf | The alert is triggered by a modification. |
| Disk | The alert is triggered by a discrete modification (change from 0 to 1 or 1 to 0). |
| Opr | The alert is triggered by a change of user (control system user). |
| Dde | The alert is triggered by the communication of the DDE interface. |
| Sys | The alert is triggered by the system. |
The nature and assignment of the alert types depend on the system delivering the alerts.
#### Character string in identification
Character string that must occur in the variable name as a means of filtering alert variables.
#### Control system user at alert onset
Name of the control system user as a means of filtering alerts that occurred for that user.
#### Acknowledged by control system user
Name of the control system user as a means of filtering alerts acknowledged by that user.
#### Priority from/to
If only a 'from' value is entered, all alerts greater than or equal to that value are displayed.
If only a 'to' value is entered, all alerts less than or equal to that value are displayed.
Note
If a 'from' and a 'to' value are entered, all alerts within the range are displayed.
#### Only alerts beginning in the time frame
Output only alerts starting in the selected export time range.
#### Active alerts only
Output only alerts active in the selected export time range.
### Filter for variables - events
Display of an active or inactive filter; Selection of groups and events.
#### Event data filter
Filter option on the status of events for export
* All event data
* Only completed events
* Only open events
* Only events starting in the time frame
* Only events ending in the time frame
#### Sort order of events/steps
Selection from
* According to the configuration in the ACRON Designer, chronologically ascending/descending order
The calculated events are displayed under the relevant group, according to their configuration, in ascending or descending chronological order
* Chronologically ascending / descending
The calculated events/steps are displayed under the relevant group, independently of their configuration, only based on the time stamps of the start time, in ascending or descending chronological order. Where the time stamps are identical, the output is based on the sequence in the database, with no further sorting.
#### Output deleted data records
Deleted event data records are also output.
---
# 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/acron-9.3/en/anlagenkonfiguration/jobs/auftragsmappe/exportauftrag.md?ask=
```
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.