Altova MapForce 2024 Enterprise Edition

Navigation: Composants de structure > EDI > Validation EDI

Message-Level Validation (Local)

You can perform validation globally for all messages in which a field is used or locally for a particular message. For information about global validation, see Full Field Validation. To set local validation that will apply only to a specific message, follow the steps below:

1.Create a custom EDI collection if you have not done this yet.

2.In the directory of your custom EDI collection, find the relevant .config file and open it in an XML editor.

3.Find the <Data> element under the required <Segment> and add the custom code values as children of <Values> (see code listing below):

</Values>
</Data>
<Data ref="F329" info="Transaction Set Control Number" />
<Data ref="F1705" info="Implementation Convention Reference" />
</Segment>

When a field has both locally-defined values (such as those in the code listing above) and globally-defined code values (in a .codelist file, as shown in Full Field Validation), then make sure that local code values are also defined as global code values. Otherwise, a validation error will occur. Note that the actual validation outcome takes into account the settings configured for the rule Invalid code list value in the EDI Validation Settings dialog box.

Local validation can be used if you require validation at field level (that is, the possible values that a field can take can be expressed as a list). Local validation cannot be used for fields that require complex validation rules at character level. When the field needs to be validated at character level (such as those defined in ISO 6346 applicable to Data Element 8155 of the UN/EDIFACT standard), add the code values globally, as shown in Full Field Validation. You can then configure validation as shown in Character-Level Validation.