Previous  Next          Contents  Index  Navigation  Glossary  Library

Project and Labor Cost Security in Oracle Projects

Oracle Projects provides three levels of project-based security to protect data ownership and sensitivity in relation to a given project or project template. For each level of security, Oracle Projects enforces default business rules depending on an employee's relationship to a project, as illustrated below:

Action Key Member Cross- Project Other Users
Query project information
Update project information and perform functions on a project  
View labor costs of detail expenditure items *  
* Only if the user's project role type is configured to view labor costs.
Table A - 1. (Page 1 of 1) Security for Enter Projects Window

You can override the default logic or add additional security criteria via the Project Security Client Extension. For a detailed description of the project security extension, see: Project Security Extension.

Key members are responsible for the management and administration of the project to which they are assigned. Each key member is assigned a project role type, which describes the type of role that the employee has on the project. Project role types include Project Manager and Project Administrator. You define whether each role type can view labor costs online and in reports.

Cross-project users can view expenditure details and update information for any project, even if they are not assigned as a key member to the project. Cross-project users log in to Oracle Projects under a cross-project responsibility. You define an Oracle Projects responsibility as a cross-project responsibility by setting the PA: Cross-Project Responsibility profile option value to Yes.

View Labor Cost Allowed

This level of security determines whether or not you can view labor costs (both raw and burdened). The default business rule in Oracle Projects is that you may view labor costs if you are:

If you are not permitted to view labor costs, the amount is not shown in the form field; that is, the field will be blank.

How project security and function security work together

Project security controls what projects you can view and update. Function security controls what functions you can perform. Together these two types of security allow you to control the which functions you can perform on which projects. You can perform the functions that are available to you for any projects for which you have access to update the project.

For example, assume you can have access to the function to generate asset lines in the Capital Projects workbench. You can perform this function only on the projects for which you have update access.

You will be able to view labor costs in reports and windows where only summary amounts are shown. Labor cost security applies only at the most detailed level where it can be determined that the entire amount displayed is labor only.

See Also

Function Security in Oracle Projects

         Previous  Next          Contents  Index  Navigation  Glossary  Library