# EDI Acknowledgement Task

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

![](https://750977703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqHxyVNGb7tSdIWecl6Ru%2Fuploads%2FcQauQ2I5e6tjIO1zZrwc%2F0.png?alt=media)

To use an *EDI acknowledgment* task:

1. 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://750977703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqHxyVNGb7tSdIWecl6Ru%2Fuploads%2F1A0MlyMUJi94WW74QEev%2F1.png?alt=media)

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

![](https://750977703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqHxyVNGb7tSdIWecl6Ru%2Fuploads%2FbqGTqhVyzpW2KMFrHTie%2F2.png?alt=media)

* *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.
* *Acknowledgment 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.

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