Re^4: EDIFACT - edi

I have been researching EDI on the web.

What would constitute a proof of concept? That is, without investing a whole bunch of resources to a test, what would the input and the output look like? When I say input, I also mean the reference files or tables that the validator would read as it encountered each data segment and data element in the EDI input file.

I propose validating a simple purchase order. I further propose that we stick to X12 initially.

I have seen a validator on the web, so I have an idea what kind of error messages a validator would generate.

If the proof of concept works, then we can complicate it further.

Comment on Re^4: EDIFACT - edi - Validator

Replies are listed 'Best First'.
Re^5: EDIFACT - edi - Validator by GotToBTru (Prior) on Aug 18, 2016 at 12:41 UTC
The concept I have has two inputs: the written specification and the EDI file to be validated. No attempt is made to check the EDI file against any other external standard. I should also note I have no time at present to explore this concept. I am very willing to act as an adviser on somebody else's. But God demonstrates His own love toward us, in that while we were yet sinners, Christ died for us. Romans 5:8 (NASB)	[reply]

Replies are listed 'Best First'.

Re^5: EDIFACT - edi - Validator
by GotToBTru (Prior) on Aug 18, 2016 at 12:41 UTC

The concept I have has two inputs: the written specification and the EDI file to be validated. No attempt is made to check the EDI file against any other external standard.

I should also note I have no time at present to explore this concept. I am very willing to act as an adviser on somebody else's.

But God demonstrates His own love toward us, in that while we were yet sinners, Christ died for us. Romans 5:8 (NASB)

[reply]