Change documents include change requests and change orders.
A change request is initiated when one or more parties to a project encounters an event or condition that they believe may result in a change to any aspect of the project (for example, the project scope, value, or duration). One or more approved change requests may be grouped or included in a change order.
A change order is a formal document that, when approved and implemented, will result in a change to a project.
Change requests and change orders may or may not have a financial impact on a project. A financial impact can affect cost only, revenue only, or both cost and revenue. Cost implementation can occur separately from revenue implementation, based on the status of the change document. In addition, you can implement part of the change document revenue impact into approved revenue budgets. Oracle Projects can automatically update a budget or forecast for the financial impact of a change document based on the following rules:
You can only include the financial impact of a change order or change request in a plan version once.
You can only include the financial impact of approved change orders in plan versions designated as approved cost budgets or approved revenue budgets.
You can include the financial impact of a change order or change request of any status in plan versions (including forecasts) that are not approved cost or revenue budgets. In the case of a forecast that is time-phased, you can include the financial impact of an approved change order into a forecast only in the periods after the actuals amounts through date. The amounts included depend on whether the change order is time-phased, as described below:
If the change order is time-phased, Oracle Projects ignores amounts for periods before the actuals amounts through date.
If the change order is not time-phased, Oracle Projects includes the entire financial impact of the change order after the actuals amounts through date.
You can create a baseline for your budgets and forecasts while implementing financial impact.
The change document types and change document statuses that you can implement and include in a budget or forecast version are determined by the financial plan type. For more information, see: Financial Plan Types.
For more information on change documents, see: Overview of Change Management.
Oracle Projects cannot automatically include the financial impact of a change document in a plan version if the following conditions are true:
The time phase of the plan version and the change document differ in the following scenarios:
The plan version is time phased by GL period and the change document is time phased by PA period.
The plan version is time phased by PA period and the change document is time phased by GL period.
When Oracle Projects cannot automatically include the financial impact of a change document in a plan version, the system will display the View Financial Impact page for the change document. To include the financial impact of the change document in a plan version in this instance, choose Printable Page on the View Financial Impact page to print the document information. Use the printed information to manually update the plan version.
If you manually update a plan version to include the financial impact of a change document, then use the Mark as Included option on the View Financial Impact page. This option prevents the change document from being included in a plan version more than once, and enables the change document information to be displayed in the View Included Change Documents page for a plan version.