When you create a project from a template or another project, Oracle Projects copies the project, its project structure, and all of the project and task options to the new project. You can only copy from templates that are effective as of the current date. The following table describes how project features are handled when you create a new project.
| Project Feature | Description |
|---|---|
| Agreements | When you copy from a template with an agreement, funding, and baseline revenue and cost budgets, Oracle Projects copies the agreement, funding, and baseline revenue and cost budgets to the new project. |
| Attachments | When you copy a project from an existing project that has attachments, Oracle Projects copies the attachments to the new project. When you copy an existing capital project with assets, attachments associated with the assets are copied to the new capital project. |
| Budgets | Budgets are copied. |
| Capital Projects | When you copy a capital project, Oracle Projects copies the asset assignments and most asset information to the new capital project. Oracle Projects does not copy the following asset information: Asset Number, Employee Asset Assigned to, and Actual Date Placed in Service. The Asset Location is copied to the new project only if you are copying from a project template. The Estimated In Service Date is shifted by the number of days between the start date in the project template and the start date that you enter. |
| Customer | If the Customer option is enabled at the top task level is enabled, then the default top task customer is copied as the default primary customer. |
| Deliverables | Deliverables are copied. |
| Task Assignments | When you copy a project from a template or project that includes task assignments, the task assignments are copied to the new project, but the planning resources associated with the assignments are not copied. You can associate new planning resources with the task assignments using the bottom-up resource planning method. |
| Transactions | Transactions charged to the source project are not copied to the new project. This includes expenditure items, requisitions, purchase orders, supplier invoices, and billing events (contract projects). |
| Workplan Versions | When you create a project by copying another project that includes several versions of a workplan, Oracle Projects copies all workplan versions with a status of Working to the new project. Workplan versions with a status of Submitted, Approved, Rejected, or Published are not copied to the new project. In addition, Oracle Projects enables you to choose which working workplan versions to copy to the new project and identify a workplan version to be submitted for publication.
Note: If the source project has a workplan structure that is fully or partially shared with a financial structure, the system enables you to copy over only one workplan version. Projects with shared structures cannot have multiple workplan versions. |
Set up your Project Templates. See: Creating a Project Template.
Note: When you disable a setup option in a template, that setup option is also disabled for all projects created using that template. For example, say you disable the Structures setup option for a template you name Engineering-Project. When you create a project using the Engineering-Project template and go to the Project Setup page for that project, you will find that you do not have access to the Structures setup page for that project.
When you create a project from a template or another project, the status of the new project you create is determined as follows:
If the status of the existing project or template is a valid starting status, then its project status is copied to the new project.
If the status of the existing project or template is not a valid starting status, then the default starting status for the project's project type is the starting status of the new project.
See: Project Types, Oracle Projects Implementation Guide.
You can change the project type of a project if the following requirements are met:
The new project type belongs to the same project type class as the current project type.
The project does not have any cost distribution lines.
The project does not have any draft revenue or draft invoice items.
If the new project type's cost burden schedule differs from that of the project type you are changing from, the following update will take place:
Note: If any tasks exist with a cost burden schedule matching the cost burden schedule of the project type before the change, those tasks will be updated to use the cost burden schedule of the new project type.
When a project was originally entered in a system outside of Oracle Projects, two fields are displayed to give you information about the project and its tasks:
Product Source : The name of the external system where the project or task was originally entered.
Source Reference: The unique identifier of the project or task in the external system.
These fields are displayed in the following windows:
Projects
Tasks
Find Projects
Find Tasks
Project Status Inquiry
See: Implementing APIs for Oracle Projects Integration: Oracle Projects Implementation Guide.