Edits/Validations

Manifest data (entered through the web or sent through the Paper route or FTP process) passes through a series of business rules before the data is finally accepted into the datamart.

The business rules have been classified into two categories:

Pre-Processing Edits: are checks to see if the data in a particular field exists or not. In other words, these fields are classified as mandatory fields and data must exist in these fields for the manifest data to be accepted into the operations database. For the manifest data entered through the web, the pre-processing business rules are executed online and error messages (if any) are reported directly to the user. For the FTP and paper route, the pre-processing business rule checks are executed as a nightly batch process.

The pre-processing edit business rules are different for each document type.

Data Validation Edits: are the more rigorous checks on the quality of the data. All data, which pass the pre-processing business rules, are marked for data validation. Data Validation rules check for existence of data against code tables or facility and transporter tables.

The outcome of the data validation can be either:

• Move the data to the datamart with errors.
• Move the data to the datamart with no errors.
• Move the data to the Work Queue for error resolution.

Again, like the pre-processing business rules, the data validation business rules are different for each document types.