F PeopleSoft Commitment Control

PeopleSoft's Commitment Control is a budgetary control feature in the PeopleSoft General Ledger product, which supports the posting of budgets and tests transactions against budgetary balances according to the rules configured by users. Using Commitment Control, you can define an alternate structure from the General Ledger to manage budgets based on the Chartfield (account segments) and calendars. For example, you can choose to control budgets at a Division level by Quarter whereas actual expenses are recorded at the Cost Center level by month.

Additionally, you can make large scale changes to budgets, and write revisions as journals back to source systems for posting while maintaining distinctions in PeopleSoft budgets between original proposals, adjustments, revisions, and adjusted budgets. Oracle Hyperion Planning, for example, can be used to prepare the initial budget at the start of the fiscal year. It can also be used to make revisions to the budgets throughout the fiscal year. As budgets are prepared and revised, they have to be validated and posted to Commitment Control, which manages and controls the actual revenue and expenses.

Oracle Hyperion Financial Data Quality Management, Enterprise Edition integrates with Commitment Control by enabling you to use Hyperion Planning to prepare and maintain the budgets. The integration involves:

• loading the Actual from Commitment Control

• validating budgets during preparation and revision against Commitment Control budget definitions

• posting the initial budget to Commitment Control

• posting ongoing budget revisions to Commitment Control

To use Commitment Control within the context of FDMEE, complete the following:

1. In Source System, register your General Ledger and HRMS source systems.

2. In Source System, to use PeopleSoft Commitment Control, select Enable Commitment Control.

3. In Target Application, register the target application.

4. In Import Format, define an import format that specifies how to map PeopleSoft chart fields to dimensions in the Public Sector Planning and Budgeting applications.

5. In Data Load Rule, define a location that identifies the PeopleSoft accounting entity (business unit) from which to load data.

6. In Data Load Rule, specify a period mapping type of "Budget."

7. In Data Load Rule define global, application, and source mappings that specify how period keys in the PeopleSoft calendar and time periods correspond to periods in your Public Sector Planning and Budgeting budget application such as months, quarters, and years. Options include:

   • Select an "As of Date."

     The "As of Date" to determine effective dated records, for example, Budget Definition.

   • Select a "Target for Blank Period" if the budget is based on a project period.

   • Optionally, in Period Mappings, map a budget period by mapping a calendar and period to an FDMEE period.

     Commitment Control enables different calendars to be used for different rules. The calendar can be of different granularity and duration. For example, you can map the Chartfield used for rule ranges to the Hyperion Planning Entity dimension. When you specify an explicit period mapping, you can map a Budget period by pointing to a calendar and period to an FDMEE period. The same FDMEE period can be mapped to multiple source periods from different calendars.

8. Run the data load rules.

9. In Import Format define an import format that contains write back mappings that identify the Public Sector Planning and Budgeting data to write to the PeopleSoft accounting entity chart fields.

10. In Data Load Rule, define a data load rule to write back.

    Write-back period mapping is based on explicit period maps. Every Entity is associated with a different Budget Calendar.

11. Run the data load rule to write.