EDI Error Handling and Exception Management 2

Question 1

What is the purpose of the ISA14 (Acknowledgment Requested) element in an EDI interchange?

Accepted Answer

It signals the receiver that a TA1 interchange acknowledgment is expected in return

Answer

ISA14 set to '1' requests that the receiving party send back a TA1 Interchange Acknowledgment, allowing the sender to confirm delivery at the envelope level.

Question 2

In EDI exception management, what does a 'duplicate document' error typically trigger?

Accepted Answer

Rejection of the transaction set with an error logged in the 997/999 or trading partner notification

Answer

Duplicate documents are flagged and rejected to prevent double-processing (e.g., duplicate payments or shipments), with the error captured in the functional acknowledgment or a separate alert.

Question 3

What does GS06 (Group Control Number) mismatch between GS and GE segments indicate?

Accepted Answer

The functional group envelope is structurally invalid and should be rejected

Answer

GS06 must match GE02 within the same functional group; a mismatch is a structural error that invalidates the envelope and should result in rejection.

Question 4

Which EDI error-handling strategy involves holding inbound transactions in a suspense queue pending manual correction?

Accepted Answer

Exception-based queuing

Answer

Exception-based queuing places errored transactions in a suspense or error queue where human operators can review, correct, and reprocess them without blocking other transactions.

Question 5

What is the maximum number of days most EDI trading partner agreements (TPAs) allow for sending a 997/999 acknowledgment after receiving a transaction set?

Accepted Answer

1–2 business days, per typical SLA agreements

Answer

Most EDI TPAs specify a 997/999 must be returned within 1–2 business days (often 24 hours), though the exact window is defined in each trading partner agreement.

(EDI) Practice Test

(EDI) Practice Test

EDI Error Handling and Exception Management 2