Some of the EDI inbound documents I receive from my trading Partners contain too many informative validation notes, warnings and errors. How can I control the maximum number of validation errors my BC-EDI XEngine should stop validating the document at?
Article ID: KB0089694
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessConnect EDI Protocol Powered by Instream | - |
| Not Applicable | - |
Description
Resolution:
. For BC-EDI 2.7.1 and earlier the errorLimit scope can be set at a particular level (for e.g. Transaction, Group, Interchange or File ) level. BC-EDI defaulted to 10 at a transaction level. This meant that the error reporting would stop at 10 if there are more than 10 errors in a transaction. Thereafter, we would inform by an error stating that the errorlimit was reached for this transaction, and the processing would continue to the next transaction.
Here is an example of such configuration for EDI-X12:
<ValidatorOptions ErrorLimit="10" ErrorLimitScope="Transaction">
within <BC_install_dir>/EDI/Validator/Docs/Settings/Production/validator-options-v18-x12.xml
. In BC-EDI 2.8.0 (XEngine 5.5), the errorLimit can be defined at different levels (default being 100 for File/Interchange/Group and 10 for Transaction). This is done within the registryValidator.xml. Note that the XEngine has the following order of precedence: file, interchange, group and then transaction.
For example, consider
- you configured File/Interchange/Group errorLimit to 100 and transaction to 10
- an inbound EDI document comes with one interchange, one group and 10 transactions with 20 errors each,
then
- the error collection would stop after the 10th error in each transaction,
- the total reporting would include 100 errors (10 errors * 10 transactions)
- AK3 segment after the 10th error would not be reported, but the AK5 would be marked as R(Rejected).
Please note that informational and warning validation events are not counted against the errorLimit when you configure BC-EDI to IGNORE info/warning property in EDI.cfg. AK3 segment for Info and Warning are reported in the 997.
Here is an example such configuration, within the <BC_install_dir>/EDI/config/registryValidator.xml file
[...]
<Category Name="ErrorLimit">
<Item Name="File">100</Item>
<Item Name="Interchange">100</Item>
<Item Name="Group">100</Item>
<Item Name="Transaction">10</Item>
</Category>
[...]
Note that file and interchange scope are the same in the context of BC-EDI, since we feed only one interchange at a time to the XEngine.
. For BC-EDI 2.7.1 and earlier the errorLimit scope can be set at a particular level (for e.g. Transaction, Group, Interchange or File ) level. BC-EDI defaulted to 10 at a transaction level. This meant that the error reporting would stop at 10 if there are more than 10 errors in a transaction. Thereafter, we would inform by an error stating that the errorlimit was reached for this transaction, and the processing would continue to the next transaction.
Here is an example of such configuration for EDI-X12:
<ValidatorOptions ErrorLimit="10" ErrorLimitScope="Transaction">
within <BC_install_dir>/EDI/Validator/Docs/Settings/Production/validator-options-v18-x12.xml
. In BC-EDI 2.8.0 (XEngine 5.5), the errorLimit can be defined at different levels (default being 100 for File/Interchange/Group and 10 for Transaction). This is done within the registryValidator.xml. Note that the XEngine has the following order of precedence: file, interchange, group and then transaction.
For example, consider
- you configured File/Interchange/Group errorLimit to 100 and transaction to 10
- an inbound EDI document comes with one interchange, one group and 10 transactions with 20 errors each,
then
- the error collection would stop after the 10th error in each transaction,
- the total reporting would include 100 errors (10 errors * 10 transactions)
- AK3 segment after the 10th error would not be reported, but the AK5 would be marked as R(Rejected).
Please note that informational and warning validation events are not counted against the errorLimit when you configure BC-EDI to IGNORE info/warning property in EDI.cfg. AK3 segment for Info and Warning are reported in the 997.
Here is an example such configuration, within the <BC_install_dir>/EDI/config/registryValidator.xml file
[...]
<Category Name="ErrorLimit">
<Item Name="File">100</Item>
<Item Name="Interchange">100</Item>
<Item Name="Group">100</Item>
<Item Name="Transaction">10</Item>
</Category>
[...]
Note that file and interchange scope are the same in the context of BC-EDI, since we feed only one interchange at a time to the XEngine.
Issue/Introduction
Some of the EDI inbound documents I receive from my trading Partners contain too many informative validation notes, warnings and errors. How can I control the maximum number of validation errors my BC-EDI XEngine should stop validating the document at?
Feedback
Yes
No
Powered by
