Validate EDI against mapping

[carlosgoce]

Validate EDI against mapping

[sabas]

If you're trying to validate an existing EDI you need the Parser (errors here are basic on the syntax)

$c = new EDI\Parser($file);
var_dump($c->errors());

Then you can use Analyser to get a string representation of the EDI, Interpreter to process it according to a xml mapping you load from the other package (Interpreter gives the error according to the message "semantic")

[sabas]

@carlosgoce it's clear now or you need some more insight?

[carlosgoce]

I am going to try it today! But I think so. Thank you

[itg-dave]

Hi,

I tried to follow the recommendations but even if I force the wrong mapping, I still get no errors.

What I did:

use EDI\Parser;
use EDI\Analyser;
use EDI\Mapping\MappingProvider;

require_once __DIR__ . '/vendor/autoload.php';

$parser = new Parser();
$parser->load(__DIR__ . '/files/test1.edi');
var_dump($parser->get());
var_dump($parser->errors());

$mapping = new MappingProvider('D01B');

$analyser = new Analyser();
$segments = $analyser->loadSegmentsXml($mapping->getSegments());
$serviceSegments = $analyser->loadSegmentsXml($mapping->getServiceSegments(3));

$interpreter = new EDI\Interpreter($mapping->getMessage('INVOIC'), $segments, $serviceSegments);
$prep = $interpreter->prepare($parser->get());
var_dump($interpreter->getErrors());

The test file (INVOIC) uses the D96A specification so I should get some errors here.

Edit:
It works with a wrong set message type (p.e. DESADV instead of INVOIC).

[sabas]

@Dave3o3 in theory a later version of the same message could/should be compatible (it should have at least the same segments), so you can get no errors if it's well formed...
What kind of errors did you expect?