90301 / edi-utils Goto Github PK

add a button to upload a file

upload the file, display it in a text window, and process the file to provide information about what the different fields are. display that information in the super field finder.

The idea here is to keep searching until both an idocSegment and idocField are found.

tab to control various settings.
example settings:
format of input (x12/idoc)
format of output (x12/idoc)

identify loops in the file.

current best idea:

find field that occurs more then once, and look at fields between the field and the next occurrence, see if they are the same fields, if not look at the fields between the field and the Nth occurance.
EX:

H1 555 <-----------
data
H1 232 <(inner field with same name)
trailer
H1 556 <--------------
data
H1 232 <(inner field with same name)
trailer
H1 557 <---------------
....

L = letter (a-Z)
n = number (0-9)

if it's 2 or 3 characters in length, it may be a constant or a unit (Ex: USD, S1, ect)
[Constant or Unit detection]
LLL
LL

if it's 5 characters (all numbers), it's probably a zip code:
[Zip Code Detection]
nnnnn-nnnn
nnnnn

Just add extra information at the bottom that includes the entire psudo-delmitied line.

create a delimited file based on the idoc specification.

output missing segments
output missing fields
Output differences in fields
optional: output correct fields

set up a list of ways to attempt to find a field.

For example, try to match the whole field, then try to match the first X characters, then the last X characters, and so on, until a field is found or we run out of options.

create a file with the files currently being worked on saved, so the next time the program is launched, the files are opened.

if the files are not found, just start with defaults.

Found : .001 [1]
FieldName: E2EDK01005
Occurance: 1
Field Length: 10

Position: 183

Found on Line: 1

-SEGMENT-
NAME: E2EDK01005
LEVEL: 01
STATUS: MANDATORY
LOOP_MIN: 0000000001
LOOP_MAX: 0000000001
KNOWN FIELDS: 32

-FIELD-
NAME: ACTION <----------------------------------------
TEXT: Action code for the whole EDI message
TYPE: CHARACTER
FIELD_POS: 1
LENGTH: 3
CHAR_FIRST: 64
CHAR_LAST: 66 <------------------------------------

Skipped results: 4

IT1 2

simply output the smart field finer fields in order, with notes at the bottom.

(More text boxes?)

add a feature to match the first N characters if the field can not be found.
(default to 5?)