Use this option to create and update tasks and task details for the financial structure. Tasks are elements of the project that are contained in the project structures. For information about project structures, see: Project Structures.
As you create tasks, Oracle Projects defaults values from the project or the parent task to the new task. A top task accepts default values from its owning project. In addition, a new subtask accepts default values from its owning parent task.
If you modify project attributes, Oracle Projects does not change the default task information for existing tasks. In addition, if you modify task attributes, Oracle Projects does not change the default task information for lowest tasks. However, new top or lowest tasks you subsequently create inherit the new default information.
The following task details default from the project to any new top or child tasks:
Organization
Start date
Finish date
Service type
For top tasks, this defaults from project type
For sub tasks, this defaults from the parent task
Task manager
No default for top tasks
Work Site
For top tasks, this defaults to the customer work site if only one customer
For sub tasks, this defaults from the parent task
Cost burden schedule
Capitalizable indicator (for capital projects only)
For top tasks, this defaults to capitalizable
For sub tasks, this defaults from the parent task
Billable indicator (for contract projects only)
For top tasks, this defaults to billable
For sub tasks, this defaults from the parent task
Billing schedules and discounts (for contract projects only)
Unique identification number of the task within the project. You can enter a numeric or alphanumeric value.
For audit trail purposes, you cannot modify a task number after you create customer invoices for the project, or charge expenditure items, requisitions, purchase orders, or supplier invoices to the project.
Suggestion: Oracle Projects sorts your project structure by the task number within a structure level, so ensure that your numbering methods reflect an organized project structure. See: Defining Your Financial Structure
A short, descriptive name of the task. You can use the same task name many times within a project.
A longer, descriptive name for the task. Can be up to 240 characters long. The default value is the task short name (Task Name).
This is a required field. The Task Long Name does not have to be unique within the project.
You use the Task Status to indicate the status of individual tasks and to control system processing for tasks based on their status. Every task must have a valid status. The system statuses are:
Not Started
In Progress
Completed
On Hold
Cancelled
You can change task status for published tasks manually when you update tasks or create progress. Tasks that are marked 100% complete are automatically updated to Completed status. Similarly, if a task's status is changed to Completed, it is automatically marked 100% complete.
The system changes a task's status automatically if the status of a parent or child task is changed. For example, if all the child tasks of a task are set to Completed, the task's status is automatically set to Completed. If a task's status is changed to On Hold or Cancelled, all of the task's subtasks are also changed to match the parent task's status.
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. Oracle Projects can divide the actual value by the planned value to derive the task physical percent complete for the task.
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. See: Managing Progress.
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 task type level and can be overridden at the task level. Selecting Progress Options for Tasks.
You can define work quantity for lowest-level tasks only if the following are true:
The task type associated with the task has work quantity enabled
Work quantity is enabled at the workplan level for the project
While defining work quantity for a task, Oracle Projects allows you to specify a Unit of Measure and Work Item. If you enable work quantity planning for a task, you can also measure progress using work quantity.
For information on defining work items, see: Defining Work Items, Oracle Projects Implementation Guide.
Task types assign default attributes to tasks and control how Oracle Projects processes tasks. Task types specify basic task attributes. For example:
The task type determines the initial status of a task.
The task type determines whether to associate Task Execution Workflow with a task.
The task type also controls whether progress can be collected for a task, and how progress is measured.
See:
Task Types, Oracle Projects Implementation Guide
Task Execution Workflow, Oracle Projects Implementation Guide
Task start and finish dates must be within the corresponding project dates and within the dates of the parent task.
The start and finish dates at the task level are:
Actual: Actual dates when work on the task started and finished. You can use these dates to drive future timecard and earned value functionality.
Scheduled: Scheduled to start and finish dates for the task.
Estimated: A resource's estimate of when work on the task will be started and finished.
Baseline: The baselined schedule for the task
Transaction: The transaction start and finish dates control the transactions that can be charged to the task.
You cannot charge an expenditure item to a task if the expenditure item date falls outside the task dates. The lowest level task must be equal to or greater than the maximum of all expenditure item dates for that task. Default values for task start and finish dates are the project transaction dates (top tasks) or the parent task's transaction dates (subtasks). When you apply an end date to a top task with subtasks that do not have end dates, the system applies that top task end date to those subtasks.
See: Project Start and Finish Date.
The person responsible for managing this task.
Note: The task manager is used for reporting purposes only (see: Task-Revenue, Cost, Budgets by Resources) and is not the same as the team member.
The organization that manages the task. You can use the organization for reporting and AutoAccounting. This value is defaulted from the project organization; the task organization can be different from the project organization. You can choose any organization that is identified as a project or task owning organization based on the Project/Task Organization Type you set up in the Implementation Options form.
For audit trail purposes, there are controls over when you can change a task organization. See: Changing the Owning Organization.
You define service types to represent activities that you want to track for financial purposes. You assign a service type to each financial task. You can use service types in your AutoAccounting setup and to group tasks for custom reporting. The default service type for each top-level financial task comes from the project type that you assign to its project or project template. The default service type for each subtask comes from its parent task.
Work types represent a classification of work. You use work types to classify both actual and scheduled work. 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
Note: Work types roll up to resource and organization utilization categories. You define this roll up when you define work types.
The default work type for each top-level financial task comes from the project-level work type. The default work type for each subtask comes from its parent task. The work type that you assign to a lowest-level financial task is the default work type when you enter or import an expenditure item for that task. If you set the profile option PA: Require Work Type Entry for Expenditures to Yes, then work type is a required value for financial tasks
See: Defining Work Types.
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. Deselect this check box if you want to prevent new charges to this task. Oracle Projects automatically disables the check box for a task when you create a child task for it. See: Determining if an Item is Chargeable.
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. See: Specifying Capitalizability of Capital Project Structure Levels.
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. For more information, see: Overview of Asset Capitalization.
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. See: Overview of Contract Projects and Determining if an Item is Billable.
The customer work site address where you perform a task. You can select any active, ship-to site defined for a project customer.
In addition to the task-level attributes that are delivered with the application, you can also define task attributes that fit the unique needs of your enterprise.
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. For more information on setting up user-defined attributes, see: Setting Up User-Defined Attributes: Oracle Projects Implementation Guide.
You can access task-level attribute groups through links on the Task Details page.
You can also configure the page layouts of the Task Overview and Task Progress Additional Information pages to display task-level user-defined attributes as page regions.
You can control at the template level whether the system displays user-defined attributes for tasks in your projects. For more information see: Enabling User-Defined Attributes in Project Templates.
You can specify the revenue and billing contribution of a paying customer for project work, define the relationship of a customer to this project, and enter other information about this project's customer. The customer you choose must be an active customer in Oracle Receivables.
You must enter at least one customer on a contract project to fund the project, accrue revenue, invoice the customer. The contribution percentage must sum to 100%, unless you have enabled the Date-Effective Funds Consumption option for the project. If Date-Effective Funds Consumption is enabled, then you cannot enter a contribution percentage.
You enter project customer and contact information at the project level only.
You enter the following customer and contact information in the Project Customers window:
Name/Number: Choose a project customer. You can choose any active customer in the Oracle Receivables customer database.
Relationship: The relationship between this customer and your project, such as Primary, or Non-Paying.
Contribution: The percentage of this project's revenue and billing you expect this customer to contribute. If you enter more than one customer for this project, the total customer contributions towards revenue and billing must sum to 100% before you can accrue revenue or bill invoices against this project.
If you enable Customer at Top Task option at the project level, the contribution is disabled and the customer is billed 100% for the associated tasks.
Note: Oracle Projects supports only one percentage split between customers over the life of a project. You cannot change an existing percentage split.
Bill To Name: Enter the name of the customer who will receive the project invoices. Depending on the Customer Relationships setting in the Implementation Options window, you can choose the project customer, a related customer, or any customer defined in Oracle Receivables. If the Customer Relationships option is set to No, the project customer is copied to the Bill To Name field. See also: Implementing Oracle Project Foundation, Oracle Projects Implementation Guide.
Bill To Number: You can enter either a Bill To Number or Bill To Name. When you enter a value in one of these fields, the other field is populated automatically.
Billing Address: The address where you want to send this customer's invoices. You can choose any active billing address defined for the Bill To customer in Oracle Receivables.
Default Top Task Customer: Check this box if you want the customer to be the default customer for all the top tasks. The default customer at top task is used as the primary customer when you copy a project.
You must enable this functionality for one of the customers if the Customer at Top Task option is enabled at the project level.
Only one customer can be enabled to be the default customer at the top task. You can change the default top task customer, but it will be applicable only for new tasks
Additional Information: You can override the default customer at the top task level, in the Billing Information window.
Ship To Name: Enter the name of the customer who will receive shipment of the items. Depending on the Customer Relationships setting in the Implementation Options window, you can choose the project customer, a related customer, or any customer defined in Oracle Receivables. If the Customer Relationships option is set to No, the project customer is copied to the Ship To Name field. See also: Implementing Oracle Project Foundation, Oracle Projects Implementation Guide.
Ship to Number: You can enter a Ship To Name or Ship To Number. When you enter a value in one of these fields, the other field is populated automatically.
Shipping Address: The address where work will be performed for this project. You can choose any active Ship To address defined for the Ship To customer in the Oracle Receivables database.
Bill another Project: Select if you want to identify a project as a provider project for purposes of inter-project billing. The check box is available only if the current operating unit is a provider operating unit and the project customer is associated with a receiver operating unit.
Receiver Project / Receiver Task: Enter the numbers of the projects and tasks that will receive the work performed on this project. Valid receiver projects and tasks belong to receiver operating units that have identified the current operating unit as a provider operating unit. You can change the receiver project and task information at any time before you create billing transactions for this project.
If you want to invoice the project customer in a currency different from the project currency, you can enter the following invoice currency information (currency attributes):
Note: You can override these currency attributes in the Invoice Review windows before releasing an invoice.
Allow Rate Type "User": Enable this option if you want to allow the rate type "User" for invoicing this project customer.
Code: The default invoice currency code for the customer.
Rate Date: The default exchange rate date. If this field is left blank, the system will use the Bill Through date for the exchange rate date.
Rate Type: The default rate type.
Exchange Rate: The default currency exchange rate. You can enter a value only if the Rate Type is User.
Type: A contact type, such as Billing or Shipping, to identify a contact. The billing contacts are limited to the contacts defined for the Bill To customer and billing address. The shipping contacts are limited to the contacts defined for the Ship To customer and shipping address.
You can enter only one billing contact for each customer associated with this project. When invoices are interfaced to Oracle Receivables, this billing contact is used as the billing contact in Oracle Receivables.
Name: You can choose any active contact name defined for the Bill To customer and billing address or the Ship To customer and shipping address in the Oracle Receivables database.
Job Title: The job title of the contact.