You define work types to represent a classification of work. You use work types to classify both actual and scheduled work. For example, a professional services enterprise could define the following work types:
- External Training
- Non-Worked Time
You can use work types to classify work for the following purposes:
- Determining the billability of expenditure items
- Classifying cross charge amounts into cost and revenue for cross-charged work
- Assigning attributes for utilization reporting
You assign work types when you define project types, project templates, projects, financial tasks, team roles, project requirements, and project assignments. You also assign a work types to expenditure items when you enter transactions.
You must define work types before you can create any of the following items in Oracle Projects:
- Team roles
- Project requirements
- Project assignments
If no work types exist, then you receive errors when you attempt to create these items.
A role list specifies which roles are available on a project. You can specify a role list when you create a project.
- If you do not select a role list for a project, any role can be used on the project. The list of values of roles on the project displays all roles defined in the system.
- If you associate a role list with a project, you limit the roles that can be used on the project. The list of values displayed for roles is shorter and project–specific.
You can associate a calendar with a project, to specify the project’s primary work pattern for open and staffed assignments. The calendar is also used in workplans to determine the duration of tasks
User–Defined Project Attributes
In addition to the project–level attributes that are delivered with the application, you can also define project attributes that fit the unique needs of your enterprise. For example, an automobile manufacturer can use this functionality to create a set of attributes that associate vehicle specifications with specific manufacturing projects. An architectural
firm could create attributes that track the blueprints for different construction projects.
Using the Projects Super User responsibility, you can create groups of attributes and associate them with attribute contexts. The system uses attribute contexts to determine how it associates attribute groups with projects and tasks.
You can access project–level attribute groups through links on the Project Setup page.
You can also arrange for user–defined attributes to display in page regions. Project–level attributes can display in page regions on the Project Home, Project Overview, and Project Status Report pages. You can control at the template level whether the system displays user–defined attributes for projects.
Use this option enable the workplan structure for the project or template, to indicate whether workplan and financial structures are shared on the project, and to configure structures.
You can use work quantity to plan and measure task progress in quantitative terms rather than in terms of completed effort, such as number of items manufactured or number of processes performed. The actual value can compared to a planned value to derive the base task percent complete.
For example, a construction company could have a task for the installation of windows on a new building. The task is complete when 50 windows are installed. When progress is taken on the task and 25 windows have installed, the task is 50% complete. This allows companies to track progress according to quantitative values.
You can enter work quantity either as an incremental value (the amount of work complete for a task since the last time progress was recorded for the task) or a cumulative value (the total amount of work complete for the task since the task began). This option is set at the workplan, task, and task type level.
You enable work quantity at the workplan level. You must also enable work quantity for each task that will measure progress using that method. A workplan can include tasks that measure progress in terms of effort as well as work quantity.
This check box controls whether to allow new expenditure items to be charged to a task. You can only enter expenditure items at the lowest task. The default is to allow charges for all new tasks. You can only allow charges for lowest tasks. Parent tasks are not chargeable. Uncheck this check box if you want to prevent new charges to this task. Oracle Projects automatically unchecks the check box for a task when you create a child task for it.
This check box controls whether the expenditure items you charge to the task are eligible for capitalization. The capitalizable indicator is applicable for capital projects only.
You can select this check box for a task on a capital project to indicate that the task is for retirement cost processing. When this option is enabled, all expenditure items charged to a task are designated as cost of removal or proceeds of sale amounts that pertain to retirement adjustment assets.
This check box controls whether the expenditure items you charge to the task are eligible for revenue accrual and billing. The billable indicator is applicable for contract projects only.