Field validation business rules are supported for all fields. The business rules are internally registered as user exits via the SetFieldValidate user exit.

Validation business rules must support the following input and output variables:

For example, you can create a business rule to check if an invoice number already exists for a vendor, based on values from a custom table or service. If the invoice number does exist then the field is marked as invalid and an error message is displayed.

To reduce complexity and effort, a business unit template is available for field validation so you can copy it and modify it for your own business needs.

Related topics:

• Custom user exits for Invoice Processing

• User exits in all environments including OPMT and Azure

• Before and after validation

• Purchase order vendor validation