Budget Plan Versions

You can retain a historical version of the budget plan transaction rows each time that you finalize a budget. Historical budget plan versions are stored in the Project Transaction table along with the current, finalized budget rows. Each historical budget version is uniquely distinguished by analysis type, and can be used for analysis and reporting. You can control budget plan versions by business unit.

By using budget row versioning, the first time that you finalize a project's budget plan, the system creates a copy of the plan and assigns a unique analysis type to budget rows in the plan copy. The new analysis type distinguishes these rows as historical budget plan version sequence one. The original analysis type remains unchanged on the current, finalized budget rows.

If you modify and refinalize the existing budget plan, or activate and finalize a different plan for the project, the system again creates a copy of the new plan and assigns a unique analysis type to budget rows in the plan copy. The new analysis type distinguishes these rows as historical budget plan version sequence two.

You configure the budget version analysis types, and the sequence in which they are used, by business unit. PeopleSoft delivers the following sequence of analysis types and analysis groups that you can use to distinguish historical cost and revenue budget versions:

Version Sequence Cost Budget Version Analysis Type Revenue Budget Version Analysis Type Version Analysis Group

1

CV1 (Historical Cost Budget Version 1)

RV1 (Historical Revenue Budget Version 1)

HBPV1 (Historical Budget Version 1)

2

CV2 (Historical Cost Budget Version 2)

RV2 (Historical Revenue Budget Version 2)

HBPV2 (Historical Budget Version 2)

3

CV3 (Historical Cost Budget Version 3)

RV3 (Historical Revenue Budget Version 3)

HBPV3 (Historical Budget Version 3)

4

CV4 (Historical Cost Budget Version 4)

RV4 (Historical Revenue Budget Version 4)

HBPV4 (Historical Budget Version 4)

You define these sequences at the business unit level, and use them at the project level. Each project independently uses the analysis type sequence for budget plan versions. The last analysis type used in the sequence is stored in the Project Header table (PS_PROJECT).

For example, assume that you finalize a new cost budget plan using the analysis type BUD. The system:

  • Saves the budget detail rows with analysis type BUD in the Project Transaction table.

  • Creates a copy of the finalized budget detail rows and updates the analysis type to CV1 (Historical Cost Budget Version 1).

  • Stores the copy of the budget detail rows with analysis type CV1 in the Project Transaction table.

Next, assume that you refinalize the cost budget plan for the project. The system:

  • Deletes the previously finalized budget detail rows with analysis type BUD from the Project Transaction table.

  • Saves the new refinalized budget detail rows with analysis type BUD in the Project Transaction table.

  • Creates a new copy of the refinalized budget detail rows and updates the analysis type to CV2 (Historical Cost Budget Version 2).

  • Stores the copy of the budget detail rows with analysis type CV2 in the Project Transaction table.

The system does not retain a historical budget version in the Project Transaction table if:

  • The project is commitment-controlled.

  • The Enable Budget Row Versioning check box is not activated for the business unit on the Budget Row Versioning page at the time you finalize the budget.

  • No budget analysis type sequence is defined on this page for the business unit.

  • All of the analysis types in the budget analysis type sequence have been assigned to a budget version for the business unit.

By using budget row versioning you have the ability to preserve detailed budget rows in the Budgeting tables that match rows in the Project Transaction table. For example, assume that Budget Plan A is the active, finalized cost budget plan. The Project Transaction table contains budget rows with an analysis type of BUD for Budget Plan A, and a copy of Budget Plan A budget rows with an analysis type of CV1. Now you want to modify the budget plan. Instead of modifying and refinalizing Budget Plan A, you inactivate Budget Plan A and activate a new plan—Budget Plan B. When you finalize Budget Plan B, the system deletes the previous BUD rows for Budget Plan A from the Project Transaction table, creates new BUD rows for Budget Plan B, and creates a copy of the new Budget Plan B budget rows with an analysis type of CV2. Then if you want to view the detail rows in the Project Transaction table for analysis type CV1, you simply view Budget Plan A that contains identical rows.

You cannot use budget row versioning if you use Commitment Control.

See Budget Row Versioning Page.