Security Events

Commitment Control uses security events to enable you to specify the budgetary functions, or events, on which the system enforces security. There are seven event types for which you can enable security:

• Budget Entry or Adjustment

• Budget Transfer

• Budget Override

• Budget Date Override

• Bypass Budget

• Workflow Notification

• Budget Inquire

You enable security separately for each event on the Security Events page. This enables you to decide whether to implement security across all control-budgeting functions (events) or a limited set of functions. For example, you may want to enable security for budget journal entry and adjustments to limit this activity to a small set of users, but not enable security for inquiring on existing budgets so that all users can check on the status of a budgeted amount.

The following table shows how each security event restricts access to Commitment Control functions when you activate it. The table also provides links to detailed discussions of the functions themselves:

Security Event	Functions	Further Discussion
Budget Entry or Adjustment (ENT_ADJT)	Enables you to restrict budget journal (budget amount) entry to a limited set of users. You can also restrict users to specific budgets using ChartField values.	See Understanding Entering and Posting Commitment Control Budget Journals.
Budget Transfers (TRANSFER)	Enables you to restrict or add constraints to the ability of the user to transfer funds from one budget to another.	See Understanding Entering and Posting Commitment Control Budget Journals.
Budget Override (OVERRIDE)	Enables you to restrict or add constraints to the ability of the user to override budget checking. Budget-checking override enables users to override budget-checking exceptions for a new transaction or to pass a transaction that has failed budget checking. Note: If Commitment Control security is active for the budget override event, the commitment control security rules will supersede the override setting for the Source Transaction Definition. The override setting on the Source Transaction Definition is taken into consideration by the system only when the override event is inactive within Commitment Control security. Note: Override at the transaction level, or header level, as for a complete override of a journal entry, can be done by a super user only. Overrides at the individual budget level for source transactions can be established for other than a super user rule.	See Understanding Exception Handling and Notification.
Workflow Notification (NOTIFY)	The notification feature in Commitment Control enables users to be notified by workflow when budget exceptions occur or when a specified percentage of the budget has been used (Early Warning notification). Activating the Workflow Notification security event enables you to limit the budgets that a user can specify for notification.	See Understanding Exception Handling and Notification.
Budget Inquire (INQUIRE)	Enables you to limit the users who can view control budgets.	See Understanding Budget Inquiries. See Understanding Exception Handling and Notification.
Bypass Budget (BYPASS)	Enables you to limit the users who can create a General Ledger journal that bypasses budget checking entirely (as opposed to overriding a budget-checking exception). A journal that bypasses budget checking never updates the control budget ledger. This function is reserved for occasions such as when a user needs to correct a suspense journal that was generated from within a source application like Purchasing and whose accounting entries have already been budget-checked. Users may also want to bypass budget checking for journals that are created in the allocation process, when, for example: Source transactions are already budget-checked. The allocation process is being used to create a reporting ledger that uses a standard ledger template. Note: You can attach this event only to a super user security rule.	See PeopleSoft General Ledger: Create/Update Journal Entries - Header Page. See PeopleSoft General Ledger: Correcting Journal Errors.
Budget Date Override (BUDG_DT)	Enables you to limit the users who can override the system-defined budget date on a source transaction. Note: You can attach this event only to a super user security rule.	See Budget Processor.