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

(ASN 856) Some data related problems are throwing X12ParsingException making 824 difficult to generate #115

Closed
CodeSmell opened this issue May 4, 2021 · 0 comments · Fixed by #118
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@CodeSmell
Copy link
Collaborator

The X12Parser and StandardX12Parser will throw an X12ParserException when the sourceData it gets is not correct.
That breaks down into the following

  1. Invalid Envelope (ISA...ISE)
  2. Unexpected segment (ISA, GS, ST, SE, GE, ISE)
  3. Unexpected exception (wrapped)

These are reasonable errors to abort any further parsing and return an exception.

The DefaultAsn856TransactionSetParser will also throw an exception for the following:

  1. When the BSN line is missing
  2. When a segment other than DTM is found between the BSN and the first loop
  3. When the HL loops are incorrect (missing, orphans, out of order etc)

The 2nd and 3rd set of errors should make is easier to generate an 824 response as the envelope, group and BSN line were are parsable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

Successfully merging a pull request may close this issue.

1 participant