Integration of Commitment Control with PeopleSoft Applications

Use the common instructions in the Commitment Control documentation and the detail instructions for the various PeopleSoft subsystem applications to set up control budgets and check source transactions.

In the following sections are discussed additional setup considerations because of dependencies between some applications that arise when one application is used with commitment control and the other is not or when one application is installed and the other is not.

Since some PeopleSoft applications depend on each other to perform key functions, you may have to do some additional setup if you enable Commitment Control for one but not for the other interdependent applications.  Some PeopleSoft application from different product line might rely on PeopleSoft Financials and Supply Chain Management applications to handle Commitment Control processing for them.

You can export budget and ledger data from Commitment Control to Budgeting and load budgets from Budgeting to Commitment Control.

If Budgeting is installed, reference the appropriate documentation for detail instructions about creating budgets and sending them to Commitment Control.

Once the data is staged in the financial database, you can create an allocation set to extract the budget data and create budget journals for posting to Commitment Control ledgers.

Use PeopleSoft Human Resources to define budgets for earnings and employer-paid deductions and taxes. You use the Commitment Control Budget Update Enterprise Integration Point to update and validate Commitment Control budgets with the budget journals received.

You run the Budget Export to GL process (BUD014.sqr) from Human Resources to publish budget data to General Ledger using the Commitment Control Budget Update IP. Upon receiving budget data at the Financial database, the IP automatically runs the Commitment Control Posting process (FS_BP) to edit and post the budget journal to the Commitment Control ledger.

After you import budget journals from the external system, COMMIT_CNTRL_BUDGET_UPDATE validates the fields of the budget header/line. You can log into the PeopleSoft FSCM Asynchronous service to check the status on the Asynchronous Details page. If errors exist during the import, an Error hyperlink is enabled. Clicking the link opens the Subscription Contract Error Messages page displaying the details of the error. Use the Resubmit button to resubmit the action after fixing the errors.

See the section Viewing Asynchronous Service Operation Instance Details under the Chapter Understanding Viewing Asynchronous Service Operation Details in the PeopleBook:PeopleTools: Integration Broker Service Operations Monitor

If you later need to adjust budgets in Human Resources, the system uses the same Commitment Control Budget Update IP to send data containing the new budget journal and the original budget journal ID. The Commitment Control Posting process reverses the original journal and creates the new journal in the Commitment Control ledger.

To use the Commitment Control Budget Update IP, you must activate the COMMIT_CNTRL_BUDGET_UPDATE application message and its related integration objects.

The Budget Export to GL process publishes human resources department budget data to the general ledger. The subscription process (COMMIT_CNTRL_BUDGET_UPDATE) creates and posts commitment control budget journals to the LEDGER_KK table.

You can interface payroll encumbrance data to Commitment Control by running the Encumbrance GL Interface process (PAYGL03.sqr) ).

Use the Actuals GL Interface process (PAYGL02.sqr) to send actual payroll expenditure transactions to General Ledger.

You budget check encumbrance and expenditure transactions in General Ledger after receiving them from Payroll.

The source transactions from the Actuals GL Interface process (PAYGL02.sqr) liquidate the transactions from the Encumbrance GL Interface process (PAYGL03.sqr).

After General Ledger and Commitment Control receive the source transactions, run the Budget Processor from the Budget Check HR Payroll page in Commitment Control to update the control budgets.

If there are any error exceptions when you budget check from Commitment Control, the Budget Processor automatically overrides the entire transaction and generates a warning exception. You can receive warning exceptions for payroll transactions using the HR Payroll Exceptions component.

Run the Journal Generator process after running the Budget Processor. You run Budget Processor directly against the payroll accounting table. Journal Generator creates journals out of the same payroll accounting table; however, it marks the journals with Skip Commitment Control so that the items are not budget checked again by the budget processor from the resulting journals.

To receive payroll transactions, activate the Payroll Accounting Transaction (PAYROLL_ACCTG_TRANSACTION) message and its related integration objects. This IP carries encumbrance and expenditure source transactions to update Commitment Control. The expenditure transactions from the same IP is also used by Journal Generator to create journals in General Ledger.

The Payroll Accounting Transaction message is sent from payroll when you have completed a payroll and are ready to send the ChartField distribution (general ledger accounts) to the Financials database using the general ledger interface PAYGL01.sqr (for non commitment accounting) and PAYGL02.sqr (for commitment accounting).

The PAYGL03.sqr process prepares encumbrance data. Before you can post encumbrance data, calculate it using either the Fiscal Year Encumbrances process (PSPENANN) or the Nightly Encumbrances process (PSPENNHT) in payroll. Use the Fiscal Year Encumbrances process to calculate encumbrances for the entire fiscal year. Use the Nightly Encumbrances process to update encumbrance data as you make changes to budgets or employees. After calculating encumbrance using these processes, run the Encumbrance GL Interface (PAYGL03.sqr) to post the results to the general ledger so that they can be budget checked and update the Commitment Control ledger.

The PAYGL02.sqr process prepares actuals transactions to be published to the general ledger. This process also liquidates encumbered amounts to reflect that the actuals for that pay period have been processed. All processed transactions are reflected on the Department Budget Actuals page.

After the subscription code populates the HR_ACCTG_LINE table, you can run the Journal Generator process against the table to create general ledger journals. These journals are marked to bypass budget checking. A second part of the subscription code populates the HR_KK_HDR table. The Budget Processor can then be run to update the Commitment Control ledger to reflect payroll activity.

You enable Commitment Control accounting in Human Resources by department in the Department Table component. You can enable Commitment Control for encumbrances only, actuals only, or both. The system uses the setting for the department and the settings on the Source Transactions - Selection Criteria page for the HR_PAYROLL source transaction definition to determine if it should process a payroll source transaction.