Enabling Commitment Control

You must enable Commitment Control for the PeopleSoft applications whose transactions you want to check against control budgets.

You use the Installed Products page in Installation Options. When you enable Commitment Control for an application, all transactions initiated from that application are presented to the Budget Processor Application Engine (FS_BP) process; however, the transactions that actually undergo budget checking depend on your control budget definitions, source transaction type definitions, and other setup options.

If you disable Commitment Control for an application by deselecting the check box for that application on the Installed Products page, the Budget Processor bypasses all transactions initiated from the application as well as all transactions sent from the application directly to PeopleSoft General Ledger to be processed as journal entries, even if General Ledger is enabled for Commitment Control. The only exception occurs when the transactions from a Commitment Control-disabled application are sent to a Commitment Control-enabled application other than General Ledger. In that case, the transactions can be budget-checked in the Commitment Control-enabled application or when they are sent from that enabled application to a Commitment Control-enabled General Ledger.

You can enable and disable Commitment Control for specific PeopleSoft applications at any time, but disabling Commitment Control for an application during a budget period might corrupt the consistency and integrity of your data.

Carefully consider document processing relationships when you determine which applications to enable or disable for Commitment Control. For example, it is impractical to enable Commitment Control for PeopleSoft Purchasing and not enable Commitment Control for PeopleSoft Payables. This is because encumbrances in your ledgers are never liquidated in that situation unless you perform a manual journal adjustment in PeopleSoft General Ledger.

Some PeopleSoft applications are automatically enabled for Commitment Control when you install them. These include:

  • PeopleSoft Payroll for North America.

  • PeopleSoft Time and Labor when the PeopleSoft Project Costing application is enabled for Commitment Control and the standard PeopleSoft Project Costing/Time and Labor interface is in place.

Enabling Commitment Control for Third-Party Applications

You enable or disable budget checking for the journals that are generated from third-party (non-PeopleSoft) applications on the Accounting Entry Definition page in General Ledger. If you select Skip Commitment Control In GL, the Budget Processor skips journals that are generated through the Journal Generator (FS_JGEN) from outside source transactions. If you select the Skip Commitment Control In GL check box, journals that are generated from outside source transactions have to be budget-checked in General Ledger before the journals can be posted.

WARNING:

Just enabling applications and business units for Commitment Control is not necessarily enough to use the functionality, because many applications have dependencies with other applications that require you to maintain integration points between those applications for valid budget checking and notification.

Related Topics