Describing Validation Rules

Objective

After completing this lesson, you will be able to describe validation rules.

Validation Rules Overview

Validation rules compare values in expense report fields to a table of predefined values, imported by your company. You can configure the comparison to take place on entry save and submit, allocation save, and report save, submit, or post submission. If the comparison uncovers a mismatch, the validation rule can generate an exception, update the report field (except on allocation save), or both. Generally, most customers don’t need validation rules.

The image displays an Audit Rules screen on the Validation tab. A filter row says “Find validation rules where” with two drop-downs and a search field. Buttons show New, Modify, Copy, Activate, Deactivate, and Remove. A table lists columns for Name, Event, Rule Action, Editable By, Applies To, and Active. One rule, “Org Unit and Account Code Allocation Example,” uses event Allocation Save and action Exception only. Another rule, “Org Unit and Account Code Entry Save Example,” uses event Entry Save and action Exception only. Both rules show Editable By Global, Applies To Global, and Active set to No.

Summary

  • Compare expense data to predefined values.
  • Triggers at various stages of expense processing.
  • Can generate exceptions or update report fields.

Learning

SAP FacebookSAP YoutubeSAP LinkedIn