# EDI Destination File

### Overview

Astera’s *EDI Destination File* object provides the functionality to validate the data against the receiver’s trading partner profile and write the data to an EDI destination file.

In this document, we will learn how to configure an *EDI Destination File* object in Astera.

### Video

{% embed url="<https://youtu.be/diNOD67VQyI?si=qwp9tyw4LEW8zlYr>" %}

### Use Case

To understand how to write to an *EDI Destination* *File* object, we will utilize a use-case where an XML source containing an X12 834 message has been serialized with the help of an *EDI Message Serializer* object. We now want to write this serialized output to an EDI destination file.

![](/files/An6VPgLhIh14l32wTET5)

To perform this task, we will use the *EDI Destination File* object in Astera.

#### Using EDI Destination File Object

1. To access the *EDI Destination File* object, go to *Toolbox > EDI > EDI Destination File* and drag-and-drop the object onto the designer.

![](/files/JkMB32Cr06bTveccnuwQ)

2. Let’s auto-map the metadata fields along with the *Text* field onto it.

![](/files/Qsx5dInJwFw6PByqXgh1)

3. Right-click on the *EDI Destination File* object’s header and select *Properties* from the context menu.

<img src="/files/0FSbIzXhIni2548gOy1u" alt="" width="375">

A configuration window will open, as shown below.

<figure><img src="/files/Okr3iUKbu9dtVoLrNj5q" alt=""><figcaption></figcaption></figure>

4. Provide the *File Path*. This is where the EDI destination file will be saved.

![](/files/3tWvodjehz3i2szaq8uk)

The configuration window also includes other document settings options. Let’s go over them:

![](/files/nHpi7pX6aUsXAHijqjO8)

* *Partner Profile ­*– Fetches all outbound maps based on the partner profile provided.
* *Test Indicator* – Allows user to specify any testing/debugging/validation indicator that may be used in the header or control segment of the message.
* *Contains Multiple Transaction Types* – If selected, this indicates the message has multiple transaction types in a single message, with each message having its own Functional Group Header and Trailer. If not selected, the transactions will be grouped into a single chunk.
* *Omit Byte Order Mark* – If selected, this indicates that the destination file must exclude the byte order mark from the beginning of the EDI message.

After configuring the document settings options, click *Next.*

![](/files/CyK8P17dol2kYrZOCoUT)

5. The *Config Parameters* screen will open, where we can configure and define parameters for the *Destination File* and *Trade Partner Profile* file.

Use of Parameters eliminates the process of inserting hardcoded values and provides simplification in the deployment of flows. If the parameters are left empty, the default values defined in the *Properties* window are assigned for use.

![](/files/ZCdB18a2EAh8nzAhoRB5)

Click *Next*, and a new window, *General Options,* will open. In this window:

* *Comments* can be added.
* *General Options* are given, which relate to processing of records in the destination file.

![](/files/FQPpuU7Ai4eCKlGccFIm)

Click *OK.*

6. The *EDI Destination File* object is now configured, and the destination file can now be created by running the Dataflow.

![](/files/PdqyKjnRVlXe9iJ7jN6V)


---

# Agent Instructions: 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://documentation.astera.com/dataflows/edi/edi-destination-file.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.