Project Team Definition
In this chapter we 'll discusses the functionality behind project team definition, including the definition of scheduled and nonscheduled team members and the definition of organization roles, and the definition and management of scheduled team roles.
Team members are people who have a specific project role on a project (such as a Project Manager, for example).
Note: Team members are also referred to as key members.
You can use team members and their associated roles when you set up project–based security in Oracle Projects.
You can designate team members at the project level only. Subject to the functions that are associated with their login responsibility, a project team member can view and update all project information except labor cost details. To permit viewing of labor cost details, you must assign a team member a project role that expressly allows query of labor cost
details.
Note: A user with cross–project update access does not need to be defined as a team member in order to view or update project information, or to view labor cost details. A user with cross–project view access does not need to be defined as a team member in order to view project–level information.
Oracle Projects comes seeded with a project manager role, and requires that you designate one project team member as a project manager. While you can have only one project manager at any point in time, you can change the project manager role assignment as necessary. You can also define users as team members in order to facilitate distribution of Projects reports to responsible parties.
Effective Dates
Oracle Projects uses effective dates to control team member and team member role assignments. You can inactivate a team member’s role at any time by specifying an ending effective date. You can reactivate the team member or redefine the team member with a new role by reentering the team member with a beginning effective date that is after the previous ending effective date. You can also associate a team member with more than one role on a project. You do not need to define each person who is doing work on the project as a team member–only those who need to maintain project data and/or view project expenditures.
When you enter a team member (key member), the system provides a default start date based on the following precedence order. At each precedence level, if there is no value for the date, the date at the next level is the default date:
1. Project Actual Start Date
2. Project Scheduled Start Date
3. Project Target Start Date
4. System date
Future–Dated Employees as Team Members
You can enter a future–dated employee as a project member. A future–dated employee is an employee who is starting employment on a future date.
You can also enter related setup for a future–dated employee, such as rate overrides and transaction controls. The start dates of those definitions must be on or later than the start date of the employee.
Organization Roles
Organization roles enable external organizations to participate and collaborate on your projects.
Adding External Organizations to Projects
Setup > Organizations
When you add an external organization to a project, you must select a customer or partner project role for the organization. If the organization has a customer role on the project, you can maintain a list of billing accounts from the organization that belong to the project. If you select customer for a customer organization, you can define billing terms and information for the customer.
Adding Team Members from External Organizations to Projects
Note: You can add only internal team members to your project as scheduled members, not external team members.
Associating Billing Accounts from Customer Organizations with a Project
You can associate billing accounts from customer organizations with a project. Billing accounts enable you to track billing information related to the participation of customer organizations in projects.