This section describes the regions of the Project Types window.
Name: The name of the project type.
Class: The project type class (Indirect, Capital, or Contract) for the project type. See: Project Types, Oracle Projects Fundamentals.
Note: You can define contract projects only if you have installed Oracle Project Billing.
Effective: The date range within which the project is valid.
Category: Select a class category. See: Project Classifications.
Note: Only categories that you have defined as valid for this project type on the Class Categories and Codes window are displayed in the Category list.
Mandatory: Enable the Mandatory check box if you want the system to require all projects of the project type to be associated with the selected class category.
You can also enable the Mandatory option in the Class Categories and Codes window.
Note: You cannot select Mandatory for class categories that are already associated with one or more projects of the project type.
Service Type: A service type is a custom reporting attribute that you assign to each financial task to represent activities that you want to track for financial purposes. You can use service types to group tasks for custom reporting. You can also use service types in your AutoAccounting setup. 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.
Role List: 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.
Work Type: You define work types to represent a classification of work. You use work types to classify both actual and scheduled work. The default work type for a project or project template comes from its project type. See: Defining Work Types.
Probability List: (optional) Enter a probability list. The probability list you enter provides the list of values for the Probability field for projects.
Administrative: Use this box to identify administrative indirect projects on which that you can create administrative assignments in Oracle Project Resource Management.
Unassigned Time: Enable this option if you want to track available resource time in utilization reporting.
Intercompany Billing: Choose this box if you want to use this project type for intercompany billing projects.
Organization Planning: You must define a unique project type to identify the organization projects that are used in organization forecasting. Define the project type for organization forecasting projects with a class of indirect and then enable the Organization Planning check box.
Sponsored: Enable this check box if you want to fund projects with awards in Oracle Grants Accounting. For additional information, see the Oracle Grants Accounting User Guide.
Contingent Worker Enabled: Enable this check box to include all purchase orders associated with contingent worker enabled projects available for selection when a contingent worker enters a timecard. If you do not enable this, only purchase orders associated with the project that the contingent worker entered on the timecard, are available for selection.
Burdened: Indicates whether to burden raw costs charged to projects using this project type for internal costing purposes.
Schedule: The burden schedule to use as the default cost burden schedule. You enter a schedule only if the project type is burdened. If the project type is burdened, this field is required.
Allow Schedule Override: Indicates whether you can override the default cost burden schedule when entering and maintaining projects and tasks. Deselect the check box if you want to ensure that all projects of a project type use the same schedule for internal costing. Check the box to allow updates to the cost burden schedule on the projects and tasks. You can enter this only if you enabled the Burdened check box.
Burdening Options: If you select the Burdened check box, additional fields are displayed:
Burden cost on same expenditure item: Select if you want to store burden amount in the same expenditure item.
Account for Burden Cost components: Select this option to store the burden amount in the same expenditure item, and additionally to show the burden cost on separate, summarized expenditures on a separate project. Select a project and (optional) task that accounts for the expenditure item.
Note: This option works best if used with indirect projects. With other project types, the system may post duplicate amounts.
Burden Cost as separate expenditure item: Select this option if you want to account for burden amounts as a separate expenditure item.
Enable Accounting for Total Burdened Cost: Select if you want to generate accounting for the total burdened cost.
You can use the Project Status Inquiry Burdening Commitments Extension to override the setup for displaying burden costs of commitments. For more information, use the Integration SOA Gateway responsibility to access the Oracle Integration Repository and navigate to the Projects Suite to find Project Status Inquiry Burdening Commitments Extension.
Allow Cost Budget Entry: Indicates if you allow entry of cost budget types.
Entry Method: The default budget entry method for cost budgets.
Resource List: The default resource list for cost budgets.
Allow Revenue Budget Entry: Indicates if you allow entry of revenue budget types. For contract projects, you must enter a revenue budget for a contract project before it can accrue revenue and be billed. For indirect and capital projects, you can choose to not allow entry of revenue budgets.
Entry Method: The default budget entry method for revenue budgets.
Resource List: The default resource list for revenue budgets.
Resource List for Status Reporting: The default resource list to use for summarizing project amounts for status reporting. You must enter a value to ensure that you can view information in the Project Status windows and project status reports, even when you have not baselined a budget for the project. You typically select the same resource list as one of the resource lists you use for budgeting. When you create a new project template from scratch, Oracle Projects automatically creates a resource list assignment using this resource list.
Enter values in this tabbed region if you want to set up budgetary controls and/or budget integration for the project type.
Allow Override at Project Level. Check this check box if you want to allow users to modify the default budgetary control settings that you enter for the project type.
The budgetary control settings for the project type are used when a project template or project is created. If this check box is not checked, the user cannot change the values at the project template or project level.
Budget Type.
For Budgetary Controls: Select a project cost budget type. (Budgetary controls can be enabled for cost budgets only.)
For Bottom-Up Budget Integration: Select a project budget type to be integrated. You can select any active budget type.
Control Flag. Check this check box to enable budgetary controls for the corresponding budget type. (Budgetary controls can be enabled for only one budget type per project type.)
Balance Type. This field is used to define top-down and bottom-up budget integration.
For Bottom-Up Budget Integration: Select Budget.
For Top-Down Budget Integration: Select Encumbrance.
For No Integration (Independent Budgetary Controls): Leave field blank.
Non-Project Budget. This field is used to define top-down and bottom-up budget integration.
For Bottom-Up Budget Integration: Select a General Ledger budget from the list of values. The list of values displays budgets with a status of Open or Current.
For Top-Down Budget Integration: Select the General Ledger Funding Budget from the list of values.
For No Integration (Independent Budgetary Controls): Leave field blank.
Levels. Select a default control level for each budget level:
Project
Tasks
Resource Groups. Select Default from Resource List if you have defined default control levels for your resource list.
Resources. Select Default from Resource List if you have defined default control levels for your resource list.
Time Phase. The system uses these values to calculate available funds.
Amount Type. Select an Amount Type to determine the beginning budget period.
Boundary Code. Select a Boundary Code to determine the ending budget period.
For more information about these settings, see: Budgetary Control Settings, Oracle Project Management User Guide.
Starting Project Status: Enter a starting project status for each project type you create. The starting project status used as the default when:
A project template is created.
A project is created by copying an existing project or project template. The project status of the new project is the same as the current status of the existing project or project template, unless that starting project status is invalid for the project type. In that case, the starting project status set in the Starting Project Status field for the project type.
Use Workflow for Project Status changes: Select to initiate Workflow for all workflow-eligible project statuses in projects with this project type. See: Project Statuses.
Use Workflow for Budget Status changes: Select to initiate Workflow for all eligible project budgets in projects with this project type. See: Budget Types.
Cost Type: For the project type, specifies whether to capitalize costs at their burdened or raw cost amount.
Require Complete Asset Definition: Specifies whether an asset definition in Oracle Projects must be complete before you can interface costs to Oracle Assets. If you select this option, you do not need to enter information for the imported asset line in the Prepare Mass Additions window in Oracle Assets. The Asset Interface process places asset lines with complete definitions directly into the Post queue in Oracle Assets.
Override Asset Assignment: This field interacts with the assignment status of the asset to either call or disregard the Asset Assignment client extension, as shown in the following table:
| Is Override Asset Assignment selected? | Asset assignment of asset lines is... | Does the system call the client extension? |
|---|---|---|
| No | Unassigned | Yes |
| No | Assigned | No |
| Yes | Unassigned | Yes |
| Yes | Assigned | Yes |
You can set up the Asset Assignment extension to assign any unassigned asset lines that result from the Generate Asset Lines process, or (as described above) to override the current asset assignment for specified lines. See: Asset Assignment Extension, Oracle Projects APIs, Client Extensions, and Open Interfaces Reference.
Asset Cost Allocation Method: You can select one of several predefined allocation methods to automatically distribute indirect and common costs across multiple assets. See: Allocating Asset Costs, Oracle Project Costing User Guide.
Event Processing Method: You can specify a capital event processing method to control how assets and costs are grouped over time. You can choose to use either periodic or manual events. See: Creating Capital Events, Oracle Project Costing User Guide.
Grouping Method: Specify how to summarize asset lines. You can choose from the following options:
All (highest level of summarization)
CIP Grouped by Client Extension
Expenditure Category
Expenditure Category, Nonlabor Resource
Expenditure Type
Expenditure Type, Nonlabor Resource
Group Supplier Invoices: Select to consolidate the expenditure items on a supplier invoice into one asset line according to the method specified in the Grouping Method field. Deselect to interface the lines to Oracle Assets as separate mass addition lines:
As New Mass Additions: Interfaces each expenditure item on a supplier invoice line to Oracle Assets as a separate Mass Addition line. Each line has the status NEW.
As Merged Mass Additions: Interfaces each supplier invoice line to Oracle Assets as a separate Mass Addition line with the status MERGED.
Note: After lines are interfaced to Oracle Assets, you can use the Prepare Mass Additions window in Oracle Assets to split, merge, or unmerge the lines manually.
Capitalized Interest Default Schedule: Use this field to specify a default interest rate schedule for capitalized interest. See: Defining Capitalized Interest Rate Schedules, Oracle Project Costing User Guide.
Capitalized Interest Allow Override: Select this check box to allow override of the default capitalized interest rate schedule at the project level.
Funding Level: The level at which you allow funding for contract projects of this project type. You can choose from the values of Project, Top Task, or Both.
Billing Job Group: Enter a default job group for billing purposes. The job group you enter serves as the default Billing Job Group when you define a contract project with this project type.
Date-Effective Funds Consumption: Select this option to instruct the system to use the agreement billing sequence and effective dates when it processes expenditure items and events. When you enable this option, Oracle Project Billing bills Expenditure items and events are billed against the agreement with the lowest sequence and expiration date that has funding available greater than or equal to the amount of the expenditure item or event. If you enable this option, then you do not specify contribution percentages for the customers.
You can modify this field at any time. The check box is disabled if Intercompany Billing is selected.
AR Receipt Notification: Select this check box to receive workflow notifications on payment receipts applied in Oracle Receivables to invoices for projects created from this project type that are enabled for supplier payment control. For more information, see Send AR Notification Workflow, Oracle Projects Implementation Guide. See also, Revenue and Billing Information .
Automatic Release of Pay When Paid Invoices: Select this check box to ensure that the Release Pay When Paid Holds concurrent program considers all supplier invoices linked to customer invoices of all projects created from this project type. For more information, see Release Pay When Paid Holds.
Leave this check box deselected, if you would like to manually review and release pay when paid holds on supplier invoices for projects created from this project type. For example, if you receive 90% of the payment due on a customer invoice from a customer with a good payment record, you, as the project manager, can review the linked supplier invoices on the Supplier Summary page for your project and manually release all linked supplier invoices for payment. For more information on releasing holds, see Payment Control.
Labor: Select Bill Rate Schedule or Burden Schedule for labor billing.
When calculating labor revenue and invoicing, the system looks first for the employee-based bill rate schedule. If no employee-based rate is specified, or if none is available, the system uses the job-based bill rate.
Employee: Select the employee-based bill rate schedule to be used to calculate labor revenue and invoicing.
Job: Select the job-based bill rate schedule to be used to calculate labor revenue and invoicing.
Non-Labor: Select Bill Rate Schedule or Burden Schedule for non-labor billing.
Organization: Select the default organization that owns the labor and non-labor bill rate schedules.
Schedule: The default burden schedule for non-labor revenue and invoicing.
The list of values for labor and non-labor schedules are restricted as follows:
If the operating unit does not have multi-currency enabled, then only schedules with the same currency as the project functional currency are listed.
If the operating unit does not allow rate schedules to be shared across operating units, then schedules from other operating units are not included.
If the operating unit of the organization allows rate schedules to be shared across operating units, schedules from other operating units that do not allow other operating units to use the schedule, are excluded.
Labor: Select the default labor invoice format.
Non-Labor: Select the default non-labor invoice format.
Billing Cycle: The default billing cycle for projects of this type. See: Defining Cycles.
First Bill Offset Days: The default number of days that elapse between the project start date and the date of the project's first invoice.
Baseline Funding without Budget: Check this box if you want to automatically create a revenue budget when you baseline your funding.
Revaluate Funding: Check this box if you want to revaluate funding for the project type. This option cannot be unchecked if the Revaluate Funding option is enabled at the Project level.
Funding Revaluation includes Gains and Losses: This option can be enabled only if the Funding Revaluation includes Gains and Losses option is enabled in the Implementation Options window and Revaluate Funding is enabled for the project type. Check this box if you want funding revaluation to include gains and losses. If you enable this functionality you should define the project revenue realized gains and losses event types for account reclassifications.
If this functionality is not enabled, the revaluation process only considers the funding backlog amount.
Realized Gains and Losses Event Types: If the Funding Revaluation Includes Gains and Losses functionality is enabled at the Project Types level, define new gains and losses event types. These event types record the realized gains and losses events while processing funding revaluation.
Name: Select billing extensions to be used in revenue accrual or invoicing, or both.
Amount and Percentage: Enter an amount or percentage to used in the billing extension calculation.
Active: Deselect to disable the billing assignment.
Name: You select the distribution rules that can be allowed for any project of this project type. You can choose any predefined distribution rule:
| Cost/Cost | Accrue revenue and bill using the ratio of actual cost to budgeted cost (percent spent) |
| Cost/Event | Accrue revenue using the ratio of actual cost to budgeted cost (percent spent), bill based on events |
| Cost/Work | Accrue revenue using the ratio of actual cost to budgeted cost (percent spent), bill as work occurs |
| Event/Event | Accrue revenue and bill based on events |
| Event/Work | Accrue revenue based on events, bill as work occurs |
| Work/Event | Accrue revenue as work occurs, bill based on events |
| Work/Work | Accrue revenue and bill as work occurs |
Default: Check the box if you want to use the distribution rule as the default value for projects of this project type. You can only have one default distribution rule for each project type.