EDI EDI Testing and Validation 2

Question 1

What is the purpose of a control number in EDI transactions?

Accepted Answer

To uniquely identify each transaction and enable matching of acknowledgments and detecting duplicates

Answer

Control numbers at the ISA, GS, and ST levels uniquely identify each interchange, functional group, and transaction set, enabling acknowledgment matching and duplicate detection.

Question 2

In EDI validation, what is a 'mandatory element' error?

Accepted Answer

A required data element designated as 'M' in the EDI standard is missing or empty

Answer

When an element marked as mandatory (M) in the X12 standard or implementation guide is absent, it generates a mandatory element error that will typically cause the 997 to report an error.

Question 3

What is an EDI implementation guide (IG)?

Accepted Answer

A trading partner-specific document that specifies which elements, codes, and rules apply to their EDI transaction sets

Answer

An implementation guide customizes the base EDI standard for a specific trading partner, defining which elements are required, optional, or not used, along with valid code values.

Question 4

During EDI testing, a supplier receives a 997 with AK5*R. What does this indicate?

Accepted Answer

The transaction set was rejected due to errors

Answer

AK5*R in a 997 Functional Acknowledgment means the transaction set was Rejected, and the preceding AK3/AK4 segments will describe the specific errors found.

Question 5

What is parallel testing in an EDI go-live strategy?

Accepted Answer

Running EDI transactions alongside manual processes simultaneously to verify EDI output matches expected results

Answer

Parallel testing runs the new EDI process side-by-side with the existing manual or legacy process, comparing outputs to validate accuracy before cutting over fully to EDI.

(EDI) Practice Test

(EDI) Practice Test

EDI EDI Testing and Validation 2