Previous	Next		Contents	Index	Navigation	Glossary	Library

• You must create at least one project template for every project type class that your company uses. All projects originate from a template. You cannot change the project type class when you copy a project from a template.

Suggestion: Oracle Projects allows you to change a project's project type, as long as the new type belongs to the project class assigned to the project (See: Changing the Project Type of a Project.) However, you may find it most efficient to create a project template for each project type that your company uses, so that you can set up the appropriate parameters for each project type in each template.

• Use a numbering and/or naming convention for your templates so it is easy to identify the purpose and definition of each one.

Note: Project templates are always numbered manually. The Project Numbering implementation option, which determines whether projects are numbered automatically or manually, does not affect numbering of project templates.

• Define typical work breakdown structures and task durations for common projects. Consider the task numbering, task names, task duration, service types, and managing organizations. See: Overview of Projects and Tasks

• If you are going to associate the project template with an agreement template, you must enter a customer in the customer project option.

• If you do not want the task organizations to change when you copy the project template, set the project organization to an organization that is not used as a task organization. See: Project and Task Organizations

• Use Quick Entry fields for Key Members and Classifications when these values usually change for each new project

• If you want to maintain key members and classifications in your templates, you must define enough templates for each combination of key member and classification, and for the rest of the project template definition. Consider the amount of maintenance required for each template before you create them

• Determine the appropriate project and task options for each template to simplify project entry and maintenance

• Determine who can create templates in your company. Any active template can be used throughout the company

Suggestion: If your company does not want to use predefined templates, you can set up one template for each project type that everyone can use. You should enable all project and task options that are appropriate to the project type for this skeleton template. Do not define default values, other than the minimum required fields. See: Specifying Project and Task Options for a Template.

See Also

Quick Entry

Using Project Templates and Quick Entry

Specifying Project and Task Options for a Template