Compliance check logs
The compliance check logs are written for any EDI interchanges that fail validation, and include information about any errors that were found. If there are no errors, then no compliance check logs are written.
- File output – The x12/reject, rail/reject, or edifact/reject directory under the directory that is specified by the <FileDirectory> element in the configuration.
- Queue output – The queue that is specified by the <X12_RejectLogQueue>, <RAIL_RejectLogQueue>, or <EDIFACT_RejectLogQueue> element in the configuration.
- Wire output – The wire terminal that is specified by the <X12_RejectLogTerminal>, <RAIL_RejectLogTerminal>, or the <EDIFACT_RejectLogTerminal>.
The compliance check logs are intended to be read by humans. However, the format is also defined in the ccx12.mtt and ccedf.mtt schemas (type ErrorLog ErrorHandling EDI). You can use these schemas to create maps that convert the logs to other formats such as XML or HTML, or to do other automated processing with the logs.
If you do not want the compliance check log to be generated, you can set the configuration parameters to disable it. If the log is disabled, you must look at any generated acknowledgements to determine the errors. If the log is disabled, it can make it difficult to determine problems. For example, in cases where no acknowledgement is generated, no acknowledgement is requested or if the EDI data cannot be parsed.
Also, the compliance check log often includes additional information that is not included the functional acknowledgement. To disable the creation of the compliance check log, set the CreateRejectLog element in the configuration to F (False). See CreateRejectLog.