Discovering Company Administration
Managing the Processor Queues
Introducing Company Tools
Managing Expense Types and Account Codes
Creating Audit Rules
Maintaining Car Mileage
Maintaining Delegate Configuration
Configuring Email Reminders
Configuring List Management
Configuring Attendees
Configuring Receipt Handling
Working with Locations
Modifying Printed Reports
Maintaining Tax Administration
Maintaining Shared Configuration Administration
Maintaining Workflows
Maintaining Cognos Settings
Creating Test Users
Maintaining Training Documentation
Configuring Travel Allowance
Configuring Site Settings
Managing Control Center

Creating an Exception Message

Objective

After completing this lesson, you will be able to configure an exception message and describe its impact on users.

Exception Messages Overview

The exception is the then portion of the if/then statement and it is triggered when audit rule conditions are met.

The exception is made up of three components: the Exception Code, the Exception Level, and the Exception Message. Review the following terms and definitions to learn more.

Exception Code
This is the company-defined code for the exception, up to eight alphanumeric characters and all uppercase.
Exception Level
The company decides which exception levels to use. Levels 1- 98 produce a yellow warning message. Level 99 and above are hard stops and will prevent the user from submitting their report. The company also determines the point at which the severity of the exception prevents the user from submitting the expense report. This is established in the Workflow settings. Levels 1-98 will display a yellow message which is a warning to the user. Meaning the message will appear but the user can till submit their report. Levels 99 and above will display a red message which is a hard stop and will prevent the user from submitting the report.​
Exception Message
The message that appears to the user on their expense report.
The image displays an Exceptions administration page in an expense system with a “Modify Exception” dialog open. The dialog shows Exception Code: 60DAYS, Exception Level: 1, and Message: “The Transaction Date is Greater than 60 days. Please be more timely in your expense submissions.” Editable By is set to Global. Save and Cancel buttons appear at the bottom, and the background lists other exception codes.

Note

Exception messages can also be shared with Workflows.

Configure an Exception Message

To configure an exception message:

Steps

  1. From the Exceptions page, select the New button.

    The image displays the same Exceptions list screen. The New button is highlighted above the table. The grid lists exception codes with columns for Code, Level, Editable By, Product Code, and Message, including entries such as 60DAYS with a warning about transaction dates.

  2. Enter a unique Exception Code and the appropriate Exception Level. Then, enter the Exception Message and select which administrative Group can edit the exception message. It's recommended to leave configuration items as Editable by: Global. Select the Save button once all of the details are entered.

    Note

    By default, exception levels 1-98 will display as a yellow message allowing the user to submit their report, and level 99+ will display a red message preventing the user from submitting their report.
    The image displays an Exceptions administration page in an expense system with a “Modify Exception” dialog open. The dialog shows Exception Code: 60DAYS, Exception Level: 1, and Message: “The Transaction Date is Greater than 60 days. Please be more timely in your expense submissions.” Editable By is set to Global. Save and Cancel buttons appear at the bottom, and the background lists other exception codes.

Summary

  • Define an exception code (alphanumeric, uppercase, up to 8 Characters).
  • Set exception level (warning or hard stop).
  • Craft a clear exception message for users.
  • Save changes to activate the exception.

Reference

TopicLink
ExceptionsSAP Help Portal
Learning

SAP FacebookSAP YoutubeSAP LinkedIn