1. P6 EPPM Rest API
  2. Tasks
  3. ResourceAssignment

Read ResourceAssignments

get

/resourceAssignment

Reads ResourceAssignment objects from the database.

Request

Query Parameters
Header Parameters

There's no request body for this operation.

Back to Top

Response

Supported Media Types

200 Response

OK.
Body ()
Root Schema : List<ResourceAssignment>
Type: array
Title: List<ResourceAssignment>
Show Source
Nested Schema : ResourceAssignment
Type: object
Title: ResourceAssignment
ResourceAssignment Entity
Show Source
  • The date on which the activity was completed.
  • The short ID that uniquely identifies the activity within the project.
  • The name of the activity. The activity name does not have to be unique.
  • The unique ID of the activity to which the resource is assigned.
  • Determines how duration and schedule dates are calculated for an activity.
  • The actual non-overtime plus overtime cost for the resource assignment on the activity. Computed as actual cost = actual regular cost + actual overtime cost.
  • The actual duration for the resource assignment on the activity.
  • The date the resource actually finished working on the activity.
  • The actual overtime cost for the resource assignment on the activity. Computed as actual overtime cost = actual overtime units * cost per time * overtime factor.
  • The actual overtime units worked by the resource on this activity. This value is computed from timesheets when project actuals are applied or may be entered directly by the project manager.
  • The actual non-overtime cost for the resource assignment on the activity. Computed as actual regular cost = actual regular units * cost per time.
  • The actual non-overtime units worked by the resource on this activity. This value is computed from timesheets when project actuals are applied or may be entered directly by the project manager.
  • The date the resource actually started working on the activity.
  • The actual this period cost (will be labor or nonlabor).
  • The actual this period units (hours) (will be labor or nonlabor).
  • The actual non-overtime plus overtime units worked by the resource on this activity. This value is computed from timesheets when project actuals are applied or may be entered directly by the project manager. Computed as actual units = actual regular units + actual overtime units.
  • The sum of the actual plus remaining costs for the resource assignment on the activity.
  • The total working time from the activity's current start date to the current finish date. The current start date is the planned start date until the activity is started, then it is the actual start date. The current finish date is the activity planned finish date while the activity is not started, the remaining finish date while the activity is in progress, and the actual finish date once the activity is completed. The total working time is computed using the activity's calendar.
  • The sum of the actual plus remaining units for the resource assignment on the activity.
  • The option that determines whether the activity's actual and remaining units, start date, finish date, and percent complete are computed automatically using the planned dates, planned units and the schedule percent complete. If this option is selected, the actual/remaining units and actual dates are automatically updated when project actuals are applied. Use this option to assume that all work for the activity proceeds according to plan.
  • The name of the calendar.
  • The unique ID generated by the system for the calendar associated with the resource assignment.
  • CBS Code.
  • The unique Id of CBS.
  • The id of associated cost account.
  • The name of the associated cost account.
  • The unique ID of the cost account associated with this resource assignment.
  • The date this assignment was created.
  • The name of the user that created this assignment.
  • The flag indicating whether new resource/role assignments drive activity dates, by default.
  • The finish date of the resource assignment on the activity. Set to the remaining finish date until the activity is completed, then set to the actual finish date.
  • The globally unique ID generated by the system.
  • The flag that indicates whether the assignment has future bucket data.
  • The flag that indicates whether this resource assignment is active.
  • The flag that indicates whether the resource who is assigned to the activity assignment has flagged the activity as important to the resource.
  • The boolean value indicating if this business object is related to a Project or Baseline.
  • The flag that determines whether or not cost should be calculated based on units.
  • The flag that indicates whether the resource is allowed to log overtime hours.
  • The flag that indicates whether this resource is the activity's primary resource.
  • The boolean value indicating if this business object is related to a template Project.
  • The date this assignment was last updated.
  • The name of the user that last updated this assignment.
  • The unique ID generated by the system.
  • The overtime factor used to compute the overtime price for the resource assignment on this activity. Overtime price = standard price * overtime factor. When the resource is assigned to the activity, the resource's overtime factor is copied to the assignment. The assignment overtime factor is refreshed from the resource value when resource prices are synchronized for the project.
  • The actual overtime units worked by the resource on this activity. This value is computed from values entered by a user in the Progress Reporter application and is applied to the resource assignment when the Apply Actuals service is invoked.
  • The actual nonovertime units worked by the resource on this activity. This value is computed from values entered by a user in the Progress Reporter application and is applied to the resource assignment when the Apply Actuals service is invoked.
  • The estimate of the percentage of the resource's units of work completed on this activity. The pending percent complete is entered by each resource using Timesheets. This value is used to compute the resource's remaining units for the activity when project actuals are applied. The project manager specifies whether resources update their percent complete or remaining units for each project.
  • The estimate of the resource's remaining units on this activity. The pending remaining units is entered by each resource using Timesheets. This value is copied to the resource's remaining units for the activity when project actuals are applied. The project manager specifies whether resources update their percent complete or remaining units for each project.
  • The planned cost for the resource assignment on the activity. Computed as planned cost = planned units * price per time. This field is named BudgetedCost in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.
  • The planned working time for the resource assignment on the activity, from the resource's planned start date to the planned finish date. This field is named BudgetedDuration in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.
  • The date the resource is scheduled to finish working on the activity. This date is computed by the project scheduler but can be updated manually by the project manager. This date is not changed by the project scheduler after the activity has been started. This is the finish date that Timesheets users follow and schedule variance is measured against.
  • The planned time lag between the activity's planned start date and the resource's planned start date on the activity. If the resource is planned to start work when the activity is planned to start, the planned lag is zero. This field is named BudgetedLag in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.
  • The date the resource is scheduled to begin working on the activity. This date is computed by the project scheduler but can be updated manually by the project manager. This date is not changed by the project scheduler after the activity has been started. This is the start date that Timesheets users follow and schedule variance is measured against.
  • The planned units of work for the resource assignment on the activity. This field is named BudgetedUnits in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.
  • The planned units per time at which the resource is to perform work on this activity. For example, a person assigned full time would perform 8 hours of work per day. A department of five people may perform at 5 days per day. This field is named BudgetedUnitsPerTime in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.
  • The price per time for the resource on this activity. This price is used to compute the resource's cost for the activity. When the resource is assigned to the activity, the resource's price is copied to the assignment based on the effective date of the price and the activity start date. The assignment price is refreshed whenever resource prices are synchronized for the project.
  • The difference between the pending quantity value and the actual quantity value for overtime before applying the new actual value.
  • The difference between the pending quantity value and the actual quantity value before applying the new actual value.
  • The skill level that is associated with the role. The values are 'Master', 'Expert', 'Skilled', 'Proficient', and 'Inexperienced'. If the current user does not have the ViewResourceRoleProficiency global security privilege, this field may not be accessed.
  • Indicates if this WBS node is a Project/EPS node.
  • The short code that uniquely identifies the project.
  • The name of the associated project.
  • The unique ID of the associated project.
  • Indicates if this Project/EPS nose is a Project or EPS.
  • The value that indicates which price/unit will be used to calculate costs for the assignment, such as 'Resource', 'Role', and 'Override'. When a resource and only a resource is assigned to an activity, the rate source will automatically equal 'Resource'. When a role and only a role is assigned to an activity, the rate source will automatically equal 'Role'. When both a resource and role are assigned to the activity, the rate source can be either 'Resource' or 'Role' determined by the RateSourcePreference. In any case, the 'Override' value allows you to specify any other price/unit.
  • The rate type that determines which of the five prices specified for the resource will be used to calculate the cost for the resource assignment. Valid values are 'Price / Unit', 'Price / Unit2', 'Price / Unit3', 'Price / Unit4', 'Price / Unit5', and 'None'.
  • The remaining cost for the resource assignment on the activity. Computed as remaining cost = remaining units * cost per time.
  • The remaining duration of the resource assignment. The remaining duration is the remaining working time for the resource assignment on the activity, from the resource's remaining start date to the remaining finish date. The remaining working time is computed using the calendar determined by the activity Type. Resource Dependent activities use the resource's calendar, other activity types use the activity's calendar. Before the activity is started, the remaining duration is the same as the Original duration. After the activity is completed, the remaining duration is zero.
  • The date the resource is scheduled to finish the remaining work for the activity. This date is computed by the project scheduler but can be updated manually by the project manager. Before the activity is started, the remaining finish date is the same as the planned finish date.
  • The time lag between the activity's remaining start date and the resource's remaining start date on the activity. If the resource's remaining work starts on the activity's remaining start date, the lag is zero. Before the activity is started, the remaining lag is the same as the planned lag.
  • The remaining late finish date calculated by the scheduler.
  • The remaining late start date calculated by the scheduler.
  • The date the resource is scheduled to begin the remaining work for the activity. This date is computed by the project scheduler but can be updated manually by the project manager. Before the activity is started, the remaining start date is the same as the planned start date.
  • The remaining units of work to be performed by this resource on this activity. Before the activity is started, the remaining units are the same as the planned units. After the activity is completed, the remaining units are zero.
  • The units per time at which the resource will be performing work on the remaining portion of this activity. For example, a person assigned full time would perform 8 hours of work per day. A department of five people may perform at 5 days per day.
  • The name of the calendar for the resource.
  • The name of the resource curve that determines how resources and costs are distributed over time for this activity.
  • The unique ID of the resource curve.
  • The short code that uniquely identifies the resource.
  • The name of the resource.
  • The unique ID of the associated resource.
  • ResourceRequest
  • The resource type: "Labor", "Nonlabor", or "Material".
  • Determines if all new activities added to the project require approval.
  • The short code that uniquely identifies the role.
  • The name of the role. The role name uniquely identifies the role.
  • The unique ID of the role the resource is performing on this activity. A resource may be assigned to the same activity more than once, performing different roles. The project manager controls whether the same resource can be assigned to an activity more than once.
  • The short code that uniquely identifies a role.
  • The time distribution of the resource's remaining cost for resource assignments that have filled a role.
  • The time distribution of the resource's remaining units for resource assignments that have filled a role.
  • The start date of the resource assignment on the activity. Set to the remaining start date until the activity is started, then set to the actual start date.
  • The project status, either 'Planned', 'Active', 'Inactive', 'What-If', 'Requested', or 'Template'.
  • The percent complete of units for the resource assignment on the activity. Computed as actual units / at completion units * 100. Always in the range 0 to 100.
  • The total number of unread comments on this activity for a user.
  • The time distribution of the resource's remaining cost for resource assignments that have not filled a role.
  • The time distribution of the resource's remaining units for resource assignments that have not filled a role.
  • The unique ID of the WBS for the activity.
Nested Schema : ResourceRequest
Type: object
Show Source
Nested Schema : ResourceRequestCriterion
Type: array
Show Source
Nested Schema : ResourceRequestCriterion
Type: object
Show Source

400 Response

Bad Request.

401 Response

Unauthorized.

403 Response

Forbidden.

404 Response

Not Found.

405 Response

Invalid Input.

500 Response

Internal Server Error.
Back to Top