How Budgets and Forecasts are Copied

You can create a project either based on a project template or an existing project and copy existing financial plan versions. You can select a financial plan version and copy to the new project.

Copy Financial Plan Versions

When you're creating a project, the following parameters determine what and how financial plan versions are copied.

Parameter	Impact
Calendar type	Calendar type: Whether financial plan types use the accounting calendar, project accounting calendar, or none
Creation source and version status	Whether the project is created from a project template or another project, and the status of the financial plan version in the source
Status	Whether the financial plan is in any of the following statuses: Current Working Current Baseline Current Approved Submitted

Parameter

Impact

Calendar type

Calendar type: Whether financial plan types use the accounting calendar, project accounting calendar, or none

Creation source and version status

Whether the project is created from a project template or another project, and the status of the financial plan version in the source

Status

Whether the financial plan is in any of the following statuses:

Current Working
Current Baseline
Current Approved
Submitted

Note: For financial plan types that support cost and revenue in separate plan versions, both cost and revenue versions are displayed and are available for selection separately, based on their status.

Status When Financial Plan Versions Are Copied

Let's see what happens when you create a project from another project. Irrespective of the version status in the source project, the financial plan versions are created in Current Working status.

When you create a project from a project template, then you use template as the source, then you can select one of the following options to copy a current baseline budget version:

Copy the selected version as the current working version.
Copy the selected version as current baseline version and as current working version. That is, create two versions in the new project.

Here are some more details about copied version information:

Aspect of Version	Details
Generation and copy sources	If the copied financial plan version was originally generated or copied from another source, those details are copied over to the new project. However, if the version was generated or copied from another financial plan version that you didn't select to copy, then source information is deleted even though the budget or forecast creation method remains unchanged.
Actual amounts	Actual amounts for forecast versions aren't copied to the new project. Estimate-at-completion (EAC) amounts are copied over as estimate-to-complete (ETC) and actual amounts are set to zero.
Period information	When you copy financial plan versions that use an accounting or a project accounting calendar, then periods for the versions created in the new project are based on the periods of the target project and task start dates. If the source project or template doesn't have a date or you haven't entered a start date for the target project, then periods are copied to the new financial plan version without adjustment. However, if both the source project or template, and target project have start dates, then Oracle Fusion Cloud Project Management performs the following actions: Calculates the number of periods between the following: The period that contains the start date of the source project template or project The period that contains the start date of the new project Derives the start period for each budget or forecast line in the new project by adding the number of periods determined above to the period of the new start date. For example, assume your projects have the following start dates: Source project or template: September 1, 2010 New project: December 15, 2010 If the financial plan version in the source project contains plan amounts for periods SEP-2010, OCT-2010, and DEC-2010 (assuming monthly periods), then the financial plan version in the new project will contain amounts in DEC-2010, JAN-2011, and MAR-2011. Oracle Fusion Cloud Project Management assumes that all periods are equal. If your periods are different lengths, then you must review plan amounts in the new financial plan version and update them as required.

Aspect of Version

Details

Generation and copy sources

If the copied financial plan version was originally generated or copied from another source, those details are copied over to the new project. However, if the version was generated or copied from another financial plan version that you didn't select to copy, then source information is deleted even though the budget or forecast creation method remains unchanged.

Actual amounts

Actual amounts for forecast versions aren't copied to the new project. Estimate-at-completion (EAC) amounts are copied over as estimate-to-complete (ETC) and actual amounts are set to zero.

Period information

When you copy financial plan versions that use an accounting or a project accounting calendar, then periods for the versions created in the new project are based on the periods of the target project and task start dates.

If the source project or template doesn't have a date or you haven't entered a start date for the target project, then periods are copied to the new financial plan version without adjustment.

However, if both the source project or template, and target project have start dates, then Oracle Fusion Cloud Project Management performs the following actions:

Calculates the number of periods between the following:
1. The period that contains the start date of the source project template or project
2. The period that contains the start date of the new project
Derives the start period for each budget or forecast line in the new project by adding the number of periods determined above to the period of the new start date.

For example, assume your projects have the following start dates:

Source project or template: September 1, 2010
New project: December 15, 2010

If the financial plan version in the source project contains plan amounts for periods SEP-2010, OCT-2010, and DEC-2010 (assuming monthly periods), then the financial plan version in the new project will contain amounts in DEC-2010, JAN-2011, and MAR-2011.

Oracle Fusion Cloud Project Management assumes that all periods are equal. If your periods are different lengths, then you must review plan amounts in the new financial plan version and update them as required.