# EDI Acknowledgment

An *EDI Acknowledgement* task issues an acknowledgment notification to the sender when an EDI message is received.

<figure><img src="https://3083465318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsR50Wa7EwZGlmPSAMkkf%2Fuploads%2FQ9BRRwWyA7mnD9J1fUH6%2F01-EDI-Ack-Object.PNG?alt=media&#x26;token=cc87b355-b42b-4eea-b2b3-38ba8f84b7ff" alt=""><figcaption></figcaption></figure>

To use an *EDI acknowledgment* task, drag-and-drop the *EDI Acknowledgement* object onto the workflow designer. Configure the object by right-clicking on the object’s header and selecting *Properties* from the context menu.

![](https://3083465318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsR50Wa7EwZGlmPSAMkkf%2Fuploads%2FShb9jrGEM9toepuJ4vPX%2F02-EDI-Click.PNG?alt=media\&token=04648ba4-3bb6-42f6-b47c-2987c2c1c2cd)

An *EDI Acknowledgement* *Properties* window will open, as shown below. Here, we need to provide the following information:

![](https://3083465318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsR50Wa7EwZGlmPSAMkkf%2Fuploads%2FQuszRl8DH9KoLBfSaZoS%2F03-EDI-Ack-Properties.PNG?alt=media\&token=4cab66e2-d2ff-4f98-b7ae-e94330e623f3)

* *Partner Profile*: This is the path to the .tpp extension file that governs the EDI exchange with a specific customer or vendor.
* *Input File*: This is the path to the .edi extension file that contains the EDI source file reader.
* *Acknowledgement Settings*:
  * *File Path*: This is the output file path.
  * *Transaction Set*: This is the acknowledgment that is being created, i.e.., a 997 or a 999, etc..
  * *Pretty Print*: This adds a line break after each segment.
  * *Omit Byte Order Mark*: Leaves out the first two bytes for UTF indicating the actual encoding for the rest of the file.&#x20;

{% hint style="info" %}
**Note:** Windows makes use of this, other systems might get confused by these two extra bytes.
{% endhint %}

This concludes our discussion on the *EDI Acknowledgement* workflow task in Astera.