Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The EDI specifications allow one or more DTM segments between the BSN and the first HL loop #107

Closed
CodeSmell opened this issue Mar 25, 2021 · 1 comment · Fixed by #108
Assignees
Labels
bug Something isn't working
Milestone

Comments

@CodeSmell
Copy link
Collaborator

The Standard Parser currently throws an X12ParserException noting that it "expected HL segment but found DTM"
However, EDI guidance allows one or more DTM segments to be added to the EDI transaction set before the first HL loop.

ST*856*368090001
BSN*00*05755986*20190523*171543*0002
DTM*011*20210323
DTM*067*20210323
HL*1**S
...
SE*296*368090001
@CodeSmell CodeSmell added the bug Something isn't working label Mar 25, 2021
@CodeSmell CodeSmell added this to the 0.3.0 Release milestone Mar 25, 2021
@CodeSmell CodeSmell self-assigned this Mar 25, 2021
@CodeSmell
Copy link
Collaborator Author

The fix will allow any DTM segment found between the BSN and the HL to be added to the Asn Transaction Set.
Any other segment id that is added between the BSN and the HL will result in an X12ParserException

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Development

Successfully merging a pull request may close this issue.

1 participant