Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 3 Managing EDIFACT Interchanges, Functional Groups, and Messages : Configuring Validation Profile (.apf) Files

Configuring Validation Profile (.apf) Files
By default, any validation error that occurs will cause a transaction to be rejected. When a transaction is rejected, the CONTRL generated will contain a UCM segment with a Transaction Set Acknowledgment Code of 4 for the transaction. When validating EDI transactions, it is desirable to be able to control whether a validation error should cause the rejection of the entire transaction or not.
Sometimes we may want the error reported and the transaction rejected. At other times we may want to report the error in the CONTRL but to accept the transaction anyway (for example, the generated CONTRL would have a Transaction Set Acknowledgment Code of accepted with errors). We might want validation errors ignored altogether or we might want only some validation errors ignored. In conjunction with EDISIM Validator, TIBCO BusinessConnect EDI Protocol powered by Instream now provides the ability to configure the severity errors which occur in EDI transactions.
Severity Level
When a transaction is rejected, error information is also sent to the private process on the subject AX.BC.<BC instance name>.EDIFACT.ERROR.VALIDATION. This error information contains the transaction ID of the transaction which had validation errors and descriptive information about the validation errors similar to the following:
Setting different error severity types to validation errors will affect the information about the validation errors that is contained in CONTRL acknowledgments and the error information reported to the private process. It will also affect whether the given transaction is converted from EDI to XML or from XML to EDI. When a transaction is rejected, no conversion takes place. Table 10 describes the four levels of severity which can be configured for validation errors and their affect on how error information is reported.
UCM or UCF segments report transaction/functional group status rejected. UCD segments might contain information about the location of the error in the transaction as appropriate.
UCM or UCF segments report transaction/functional group status accepted with errors. UCD segments might contain information about the location of the error in the transaction as appropriate.
Severity Scope
The scope of error severity setting is Message.
Normally an error severity setting is applied to all validation errors of the specified type within the entire transaction.
Validating Severity Levels
The steps for validating the error severity settings for a transaction are similar to configuring the guideline for the message. You first create a Validator Profile file for a message using EDISIM Validator and then upload this file in the Protocol Editor of the TIBCO BusinessConnect configuration GUI.
 
Task A Create A Validator Profile (.apf) File
The Validator Profile file is created using the EDISIM Validator.
1.
2.
Click Options > Validator Profile.
3.
Select a message in the Message tab, change the error severity and save it.
4.
5.
Select File> Open.
6.
This step should open an EDI data file, such as sample data Edifact_D93A_Orders.dat.
7.
Click Open.
An EDI compliance check will be automatically performed.
8.
Select the guideline to be used to validate the data file: it should be D93A that was imported from Edifact_D93A_Orders.sef (Figure 17).
Figure 18 shows the validation result.
Figure 17 Select Standard Dialog
Figure 18 EDI Compliance Check
9.
10.
Click OK. The Diagnostics window provides the Validator analysis of the selected guideline.
Task B Apply the Validator Profile file (.apf) for a Message
To associate a transaction with a Validator Profile in EDIFACT, perform the following steps:
1.
Using TIBCO Administrator, select BusinessConnect> Operations Editor.
2.
Select EDIFACT from the Protocol menu.
3.
4.
Select the Guideline tab.
Figure 19 Edit Notification Message
5.
Click change to upload the Validator Profile file (.apf).
6.
File Reference   When you select this option, enter the path to the file reference you want to use.
Uploaded File   When you select this option, browse to the location of the file you want to upload. In this case, look for the file you saved in Task A.
7.
8.
Click Save.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved