Most forms throughout the software have some type of validation applied to one or more fields on the form. Depending on the field, validation may require an entry and/or that the entry meets specific requirements.
For example, validation for a Job field on one form may require that an entry is made, that the job is valid (i.e., exists in JC Jobs), and that the job status is ‘Open’. On another form, validation may not require entry of a job, but if an entry is made, that the job is valid. In some cases, validation may be controlled by a flag setting in a company file. For example, if the Validate Material flag is unchecked in JC Company Parameters, validation will allow entering non-HQ materials in JC Material Use, but only for ‘MI-Miscellaneous’ type transactions. If the flag is checked, all materials entered in JC Material Use must be valid.
For non-validated fields, you have the option to apply validation via the Field Properties (F3) form. If applying user-specific validation (the User Overrides tab), you can only define whether a value is required on a non-validated field. However, if you are applying validation at the system level (the System Overrides tab), you have the option to assign a custom validation procedure and define how it operates.
You cannot remove or override the standard validation defined for a field; however, you can apply a secondary validation procedure to supplement existing validation. Secondary validations allow you to implement a more restrictive validation process than what is standardly applied.
Your company requires that haul charge and haul vendor payment amounts be equal when entering tickets (in MS Ticket Entry). You could apply a secondary validation to the Haul Charge and/or pay Total fields to warn when this condition is not met.
Your company requires that purchase orders be posted to a specific cost type (e.g. cost type ‘2’). You could apply a secondary validation to the Cost Type field (in PO Purchase Order Entry) that restricts entry to only that cost type.
The system initiates standard validation first; secondary validation occurs only if the required standard validation conditions are met. If the validation level (specified in the Level field) differs between the standard and secondary validation procedures, the system uses the more restrictive level. For example, if the validation level for one procedure is set to ‘1-Warning, allow save’ and the other is set to ‘3-Show error, stay on input’, both procedures will use ‘3-Show error, stay on input’.
Once validation is complete, the standard and secondary validation messages display in a single window, with the standard validation messages appearing first.