General Columns of the Activity Table

Activity ID field

The unique identifier of the activity.

In order to identify and track activities, P6 assigns each activity a unique Activity ID that is the result of joining the Activity ID Prefix with the Activity ID Suffix and then adding an Increment value.

For example, a prefix of PROJ-A# combined with a suffix of 2500 and an Increment of 5 will yield the following activity IDs: PROJ-A#2500, PROJ-A#2505, etc.

Activity Leveling Priority list

Determines the priority of the activity when performing resource leveling.

Activity Name field

The name of the activity.

The activity name does not have to be unique.

Activity Status list

Determines the status of the activity.

Valid values are Not Started, In Progress, and Completed.

Activity Type list

Determines how duration and schedule dates are calculated for an activity.

Task Dependent: Activities are scheduled using the activity's calendar rather than the calendars of the assigned resources. Choose task dependent when you want to control the duration of the activity yourself (that is, no resources are assigned), or when one or more resources assigned to the same activity can work according to the same calendar. For example, you might have an activity to cure concrete; you know how long the task takes and the addition of resources won't complete the task any earlier. You would designate this activity as task dependent.

Resource Dependent: Activities are scheduled using the calendars of the assigned resources. This type is used when several resources are assigned to the activity, but they might work separately. Choose resource dependent when you want to schedule each resource according to his/her own time schedule, or resource calendar, not the activity calendar. The assigned resource availability determines the start and finish dates of the activity. Typically, you use this type when multiple resources assigned to the same activity can work independently, or when availability can affect the activity's duration. For example, an activity that requires an Inspector might be delayed if that resource is assigned to multiple projects or is on vacation.

Level of Effort: Activities have a duration that is determined by its dependent activities and are typically administration type. Choose level of effort to indicate that the activity's duration depends on its predecessor and/or successor activities. A level of effort activity is usually one that is ongoing, such as clerical work, Change Management, or project management tasks. For example, site cleanup could be considered a level of effort activity; it occurs repeatedly and is dependent on the completion of a phase.

Start or Finish Milestone: Milestone activities are zero-duration without resources, marking a significant project event. Choose start milestone or finish milestone to indicate that the activity marks the beginning or end of a major stage in the project. Milestones have zero duration. A primary resource or an activity owner, and expenses can be assigned to a milestone. In an office building addition project, examples of milestones might include Project Definition Complete, Structure Complete, or End Bidding Process.

WBS Summary: Activities that are used to aggregate date, duration, and percent complete values for a group of activities that share a common WBS code level. Choose WBS Summary to indicate that the activity is a summary-level WBS activity. A WBS Summary activity represents a group of activities that share a common WBS level. The summary-level WBS activity enables roll-ups of dates for the activity group. The duration of a WBS Summary activity extends from the start of the earliest activity in a group to the finish of the latest activity. WBS codes control which activities are part of a WBS Summary activity; P6 incorporates any activities that share a component of the WBS Summary activity's WBS code into the WBS Summary activity. For example, all activities whose WBS codes begin with A (A.1, A.1.1, A.1.2, etc.) can be part of one WBS Summary activity whose WBS code is A. At a lower level, all activities whose WBS codes start with A.1 (A.1.1, A.1.2, etc.) can be part of a WBS Summary activity whose WBS code is A.1.

Added By field

The name of the user who added the activity to the project.

Added Date field

The date the activity was inserted into the project, showN in your timezone..

Auto Compute Actuals option

Determines whether the activity actual and remaining units, and start and finish dates for the resource are calculated automatically using the planned dates, planned units, and the activity's schedule percent complete.

If this option is selected, the actual/remaining units and actual dates are automatically updated when project actuals are applied. This assumes that all work by the resource proceeds according to plan.

Note: This option is not available if the Uses Timesheets option is selected.

BL Project Activity Status field

The status of the activity in the project baseline.

BL1 Activity Status field

The status of the activity in the primary baseline.

Calendar field

The calendar assigned to the activity.

CBS field

The Primavera Unifier Cost Breakdown Sheet to which you want to link an activity, assignment or expense.

Cost Account IDs field

The identifying codes of the cost accounts assigned to the activity.

Cost Account Names field

The name(s) of the cost accounts assigned to the activity.

Critical option

Determines whether the activity is critical.

An activity is critical when its total float is below the critical duration specified for the project. Delaying critical activities will delay the finish date of the project.

Duration Type list

Determines how remaining duration, units, and units/time are calculated when you update an activity that has resources assigned. The activity's duration type should correspond to the dominant factor, that is, the least flexible factor in the project: schedule, costs/work effort, or resource availability.

Fixed Units/Time: The resource units per time are constant when the activity duration or units are changed. Use this duration type when an activity has fixed resources with fixed productivity output per time period.

Fixed Duration & Units/Time: The activity duration is constant as the units or resource units per time are changed. Use this duration type when the activity must be completed within a fixed time period regardless of the resources assigned.

Fixed Units: The activity units are constant when the duration or resource units per time are changed. Use this duration type when the total amount of work is fixed, and increasing the resources can decrease the activity duration.

Fixed Duration & Units: The duration and units remain constant as the units/time are changed. Use this duration type when the activity must be completed within a fixed time period and the total amount of work is fixed.

Financial Period Calendar field

The name of the financial period calendar assigned to the project.

Last Modified By field

The name of the user who last modified the activity.

Last Modified Date field

The date the activity was last updated.

Location field

The geographical location.

Longest Path option

Determines critical activities base on the sequence of driving activities that determine the project end date.

Owner field

The user responsible for the activity.

Post-Response Criticality Index field

Shows the percentage of time the activity in Oracle Primavera Cloud was on the critical path during quantitative post-response risk analysis.

Pre-Response Criticality Index field

Shows the percentage of time the activity in Oracle Primavera Cloud was on the critical path during quantitative pre-response risk analysis.

Primary Constraint list

The primary constraint type for the selected activity.

Primary Resource field

The person primarily responsible for performing or overseeing work related to a specific activity.

The first resource you assign to an activity is automatically identified as the activity's primary resource.

Project ID field

The unique identifying code for the project associated with the activity.

Project Name field

The name of the project associated with the activity.

Project Status list

The current state of the project or WBS element. For activities, this field reflects the current state of its parent WBS or project. The status type determines how project, WBS, activity, and resource assignment data are handled by applications within P6 EPPM.

The status you assign to a project automatically applies to all its WBS elements and their activities. By default, when you create and save a new WBS, it automatically inherits the Project Status value of its parent WBS or project; however, subject to certain logical constraints, you can change the individual status of a WBS. For example, within an Active project you can designate WBS elements that are Active, Inactive, and Planned. The following status values can appear in this field:

Active: This is the default setting for new projects. Use this status to reflect actual authorized WBS or project work at your organization. When you designate a project as Active, P6 Team Member Web timesheet users can view all activities included in its active WBS elements. Depending on their timesheet privileges, users may also be able to assign themselves to and perform work on activities that are included in an active WBS element.

Inactive: Use this status to designate a WBS or project that is on hold, terminated, or no longer active. Select the Resources can view activities from an inactive project option on the Team Member page of the Project Preferences dialog box to allow P6 Team Member Web timesheet users to view, but not edit, activities that are included in an inactive WBS element or project.

Planned: Use this status to designate a project or WBS that is in its planning phase. If a WBS element's status is Planned, P6 Team Member Web timesheet users cannot view any of its activities. This prevents P6 Team Member Web timesheet users from assigning themselves to and performing work on unauthorized activities not yet officially designated Active.

What If: This status can only be designated at the project level. Use this status to designate a project is only being considered or is undergoing analysis before establishing a more defined project schedule. When a project's status is What If, P6 Team Member Web timesheet users cannot view any of its activities. This prevents P6 Team Member Web timesheet users from assigning themselves to and performing work on unauthorized activities not yet officially designated Active.

Reflection projects created in P6 Professional appear in P6 as What If projects.

Requested: This status is set automatically for projects associated with certain types of project initiation and project request workflows.

Template: This status appears in this field only for template projects or for a WBS element that belongs to a template project. This status is set by P6; you cannot directly set this value.

Review Required option

Determines whether activity updates made in P6 Team Member interfaces require review.

Secondary Constraint field

The secondary constraint type for the selected activity.

This field is only available if a primary constraint has been selected.

Unread Comments field

The number of comments posted to the activity since you last reviewed the comments in the Discussion detail window.

WBS field

The name of the WBS element.

WBS Category field

The category of the selected WBS.

Use this category to organize, filter, and report WBS information in all projects. The category applies to this WBS in all projects to which the WBS item is assigned.

WBS Code field

The unique identifier of the WBS for the associated activity.

Work Package ID field

The ID of the work package in Oracle Primavera Cloud.

Work Package Name field

The name of the work package in Oracle Primavera Cloud.



Last Published Wednesday, July 10, 2024