Exception Notification

Oracle recommends that you set up security using the notification process, so that only users with Notify security access receive exception notifications, and only for the budgets to which they have access. However, this is not required. You can use notification without implementing related commitment control security.

You can be notified of exceptions by the commitment control workflow process, by email, or through the work list. You can also view exceptions online using the Exception Inquiry pages without using the Commitment Control Notification feature.

Online Exception Notification

In an online situation, you receive a message regarding status of a transaction when the budget-checking process finishes. The message indicates what type of exception the transaction created and enables you to transfer directly to the appropriate transaction exception header page, where you can either view the warnings generated or view and override the errors.

Note:

An override is applicable only to the original entry. After the override, any change or additions to the original journal lines causes the system to cancel the override and reset the header status to (N) not checked. This is to prevent the adding of lines using the same overridden ChartField combination to create unauthorized overrides for different or larger amounts.

Workflow Exception Notification

In a batch budget-checking situation, users are notified of exceptions through workflow. You grant access to exception notification workflow to the appropriate individuals when you set up Commitment Control security. The system generates a worklist containing budget exceptions for each user responsible for budgetary oversight. The budgets, source transactions, and exception types included in the worklist depend on the security you have set up for the individual and the notification preferences for the individual. You can also have the system provide email notification.

From the worklist entry or the email, you can select a budget with exceptions and transfer to the Budget Details page, where you can open the Budget Exceptions page to see a list of all transactions that have failed for that budget. You can also link to the transaction exception page for each transaction to view a list of all budgets that have caused exceptions for that transaction. The Budget Exceptions and transaction exceptions pages enable you to inquire about exceptions and to perform overrides, if you have security access.

The Budget Exceptions page and transaction exception pages for each source transaction type are also available directly through the PeopleSoft menus.

Early Warning Notification

You can use workflow to provide early warning notifications when a predefined percentage of a budget has been spent.

Commitment Control Notify Process

After you have set up security and notification preferences for all appropriate users, you use the Commitment Control Notify Application Engine process (KK_NTFY_WF) to scan the exception table and notification preferences and route the notification to the email and worklists for the user.