Oracle® Fusion
Applications Project Management Implementation Guide 11g Release 1 (11.1.3) Part Number E20384-03 |
Contents |
Previous |
Next |
This chapter contains the following:
Project Roles in Budgeting and Forecasting: Explained
Default project roles, including project application administrator, project manager, and project administrator can perform specific budgeting and forecasting tasks.
The following table describes the default access for each role.
Entitlement Area |
Project Application Administrator |
Project Manager |
Project Administrator |
Notes |
---|---|---|---|---|
Edit budget and forecast planning options |
Yes |
No |
No |
Project application administrators set planning options for financial plan types. Project managers and accountants can view planning options at the version level. |
Create versions |
No |
Yes |
Yes |
None |
Generate versions |
No |
Yes |
Yes |
Applies to budgets generated when setting a baseline for the project plan. Project administrators cannot generate forecasts from progress (they do not have access to publish progress.) |
Edit versions in Excel |
No |
Yes |
Yes |
None |
Submit versions |
No |
Yes |
Yes |
None |
Approve versions |
No |
Yes |
No |
A team member with project manager security role access must be manually designated as the project manager for the project. Note Project creators are not automatically designated as project managers for their projects. If workflow is enabled, then approval takes place through a notification. Menu actions are not available on the budgeting and forecasting pages. |
Review versions |
No |
Yes |
Yes |
None |
Project roles represent either a requirement or an assignment on a project, such as a project manager or project team member.
You associate an enterprise role with each project role. When you assign a project role to a project team member, the associated enterprise role determines the type of access the team member has to project information. For example, project managers can manage project progress or create budgets and forecasts. Project team members may only have access to view progress or financial plans.
When you create a project role, you assign it to one or more reference data sets so that only project roles that are relevant to the project unit are available to assign to project team members.
Important
Persons who are directly assigned enterprise roles such as Project Manager or Project Application Administrator may have access to certain project information even if they are not project team members or do not have a specific project role assignment.
Job titles represent the function persons fulfill within an organization and their position within a reporting hierarchy. For example, your organization may have designations or job titles such as software developer, sales representative, or accounts manager.
Project roles represent either a requirement or an assignment on a particular project, for example, project manager. Project roles may differ from project to project.