Open cpotter1 opened 4 weeks ago
Hi @cpotter1 , the "END" events are currently signaled at the start of the following segment but the "START" events do provide the starting segment name in the position information.
E.g.
event: START_GROUP in segment GS at position 2
event: START_TRANSACTION in segment ST at position 3
I understand the confusion around the end event, but are you expecting something else for the start events?
There are two transactions here - ST and SE. Where are the SE transaction events? That is my question #1.
ST
is the start of a transaction, SE
is the end. One transaction per ST
/SE
pair.
Ok, so you see it part of the txn itself. Ok.
What about point 2 re: ELEMENT_DATA_ERROR ?
What about point 2 re: ELEMENT_DATA_ERROR ?
For this particular example, I suspect the reason for one of the errors was CONTROL_COUNT_DOES_NOT_MATCH_ACTUAL_COUNT
. The count in SE01 it validated to be the number of segments in the transaction (including ST
and SE
), which in this case is 2
. You can fetch the error type via EDIStreamReader#getErrorType()
when the ELEMENT_DATA_ERROR
occurs.
Consider this simple x12:
The stream of events I see is as follows:
There are a few concerns I have with this:
Please have a look.
Thanks!