Oracle Projects summarizes actuals and commitments by resource when you update project summary amounts.
Oracle Projects automatically maps each transaction to one resource in each resource list assigned to the project to which the transaction is charged. This mapping is based on the following: employee or supplier, expenditure organization, and expenditure type of the transaction; you do not have to specify the resource when you enter the transaction.
Oracle Projects maps each transaction to a resource based on the combination of the resource and its resource group. For example, you can enter an organization resource of Risk Analysis under both the resource groups of Labor and Other Expenses in one resource list. Timecards for the Risk Analysis organization map to the resource of Risk Analysis under the Labor resource group, and expense reports for the Risk Analysis organization map to the Risk Analysis resource under the Other Expenses resource group.
There are cases in which one transaction could map to more than one resource in a resource list. For example, you may have entered both an employee resource for Marlin and a job resource of Senior Consultant under the Resource Group of labor. Amy Marlin, a senior consultant, charges labor to the project using this resource list. Marlin's labor transaction can be mapped to both resources. However, Oracle Projects ensures that each transaction maps to only one resource in a resource list by utilizing a precedence-based mapping to determine which resource in the resource list is mapped to each transaction. Oracle Projects predefines the precedence of each resource type for each expenditure type class. The resource types that are more specific are ranked higher and thus are used to summarize the transaction amounts.
The precedence by resource type is as follows:
Employee and Supplier
Job
Organization
Expenditure Type and Event Type
Expenditure Category and Revenue Category
For example, an employee resource is used before a job resource is used.
It is possible that a transaction cannot be mapped to any resource defined in the resource list. Oracle Projects maps such transactions to an Unclassified resource.
If you discover that transactions are mapped to an Unclassified resource, and you subsequently want to change the resource list to ensure that all transactions are mapped to a resource, you can add the appropriate resource to the resource list and then update the project summary amounts after a resource list change.
You may need to change your resource list after you have used it for summarization for status reporting. Some reasons for this may be due to new employees or organizations defined for your company, if you use employees and organizations as resources, or because your company has decided to classify expenses in a different way, thus disabling use of an expenditure type.
When you change a resource list, the new resource may change the way a transaction is mapped to a resource. In such a case, you need to decide how to handle the transactions that have already been summarized using the resource list precedence that existed before you made the change. You may choose to leave the historical transactions summarized as they are and have new transactions summarized using the new precedence. For more consistency in the summarization, you can summarize all historical transactions mapped to resources in that resource list again so that they use the new resource precedence by running the PRC: Update Project Summary Amounts after a Resource List Change process.