Expenditure Type Classes: Oracle Projects pre-defines all expenditure type classes. Indicates how Oracle Projects processes the expenditure types.
Multiple Expenditure Type Classes Per Expenditure Type
| Expenditure Type | Module Where Expenditure Originated | Expenditure Type Class |
| Materials | Oracle Payables | Supplier Invoice |
| Materials | Oracle Inventory | Inventory |
Expenditure Categories: Expenditure categories are used for grouping expenditure types for costing.
Revenue Categories: Revenue categories are used to group expenditure types for revenue and billing.
Expenditure Types: a classification of cost that you assign to each expenditure item you enter in Oracle Projects. An expenditure type is made up of four elements:
- An expenditure category
- A revenue category
- A unit of measure
- One or more expenditure type classes
Service Types: Assigned to each task. Use in AA to derive accounts. Also reporting on Service types such as billable work, non-billable work, vacation, or whatever fits.
Work Types:
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:
- Analysis
- Design
- External Training
- Implementation
- Non-Worked Time
- Support
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.
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 type to expenditure items when you enter transactions.
Note: The default work type for a project or project template comes from its project type. 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 project types, project templates, projects, and financial tasks.
Important: 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 work type is distinct from an expenditure type. Expenditure types classify the type of cost incurred on a transaction, whereas a work type classifies the type of work to be performed or actually performed. For example, you can enter and expenditure item for a task with an expenditure type of Clerical Labor to represent the type of cost incurred, and assign the expenditure item a work type such as Analysis to identify the type of work performed.
Resource Lists
You attach resource lists to projects to effectively budget project cost and revenue, to track resource usage, and to view cross-project reporting. Oracle Projects summarizes actual costs and commitments for resources, and rolls up the amounts for a project based on the attached resource list. Oracle Projects requires that every project have at least one resource list assignment; this is to ensure that you can view actuals information in the Project Status windows and project status reports if no budget or forecast was created for the project.
Project Classifications (Class Categories and Class Codes)
You define project classifications to group your projects according to categories you define. A project classification includes a class category and a class code. The category is a broad subject within which you can classify projects. The code is a specific value of the category.
For example, if you want to know the market sector to which a project belongs, you can define a class category with a name such asMarketSector. You can define class codes for this category such as WasteCleanup, Risk Analysis, andEnvironmental Engineering.
You can create a report that displays projects classified by a particular category. For example, if you classify your projects by market sector, you can create reports showing which market sectors generate the most revenue. Or, your marketing department could run a report to determine which markets need to be pursued more aggressively.
Oracle Projects does not predefine any class categories or class codes.
User-Defined Attribute Sections
User-defined attributes enable you to define, enter, and maintain information unique for your organization at the project and task level. For example, as an aircraft manufacturer you can use this functionality to create a set of attributes that associate aircraft specifications with specific manufacturing projects. The attributes are grouped together to form attribute groups. For example, you can have attribute group of Engine Specifications containing attributes of weight, length, size and color of the engine. The attribute groups are linked to project and tasks by attribute contexts.
User-defined attributes groups are associated with attribute contexts. The association can be either at the project level or task level not both. Attribute contexts are defined by their context type. The context type identifies the projects or tasks with which an attribute context is associated. For information on setting attribute contexts and associating attribute contexts with projects and tasks, see Setting Up User-Defined Attributes, Oracle Projects Implementation Guide. For information on creating attribute groups, attributes, and attribute functions, see the online help for Product Lifecycle Management.
There are four context types: Project Type, Task Type, Class Category, and Class Code. For example, you can have the following context types associated with attribute groups of Engine Specifications and Engine Prototypes:
- Project Type: Time and Materials
- Task Type: Design
- Class Category: Aircraft Engines
- Class Code: Commercial and Government
You create and maintain page regions for an attribute context. The page regions display the attribute groups associated with the attribute context. For example. you can create a page region called Engine Information that displays the attribute groups of Engine Specification and Engine Prototype.
When you define page layouts, you can add the available user-defined attribute page regions to your page layouts. Project level user-defined attribute page regions are available for Project Overview, Project Home, and Project Status Report page layouts. Task level user-defined attribute page regions are available for Task Overview, and Task Progress Additional Information page layouts.
Note: Like the pre-defined page layout sections, User-Defined page regions can also be displayed as sections or links.
Attribute contexts for user-defined page region determine whether the page region can be displayed as a section for a page layout. For example, you have a Project Type attribute context of Time and Materials added to a page region (A), and a Project Type attribute context of Fixed Cost added to a page region (B). If you create a page region (A) and associate it with a page layout, you can only display the page layout for a project with a Project Type Time and Materials. You cannot display the page layout for a project type Fixed Cost.
Note: You can control the display of user-defined attribute information for each project at the project template level using a new project setup option called Project Attributes. See Project Definition and Information, Oracle Projects Fundamentals.
