OpenText Active Catalogue performs the following validations of your EDI data:
|
1
|
EDI validation - Catalogue first checks your data to ensure that it is EDI data. Typical errors at this stage are unknown Catalogue account number, unknown batch password and unknown proxy account. These types of errors appear on the EMC page. See “Using the EDI Management Console� to identify these types of errors.
|
|
2
|
EDI standards validation - Catalogue validates the EDI data to ensure that the EDI conforms to published EDI standards. The EDI data is validated for EDI qualifiers, mandatory segments and elements, field lengths, and so on. These types of errors appear on the EMC page. See “Using the EDI Management Console� to identify these types of errors.
|
|
3
|
Translation validation - If an ST group in your EDI data contains a translation error, the entire group is sent to Error Processing (EP). Subsequent ST groups will continue to be processed. You can use EP to locate the error in the EDI data. See “Viewing Translation Errors in an EDI Document� to identify these types of errors.
|
You must fix all translation errors and resend the EDI data before Catalogue can process the file.
|
4
|
Data validation - Catalogue validates the EDI data to ensure that it conforms to Catalogue specifications such as business rules, data validations, and compliance checks. These rules are documented in the following guides, depending on the type of EDI document you are submitting:
|
Examples of errors at this stage include invalid batch password and error for action “00� when the G53 segment is not correct. These types of errors appear in Error Processing (EP). See Section 14 "Online Correction of Errors," to identify these types of errors.
OpenText Active Catalogue Browser Interface User Guide for Vendors PDF
