1. P6 EPPM REST API Release 25
  2. Tasks
  3. SyncService

Update Project

put

/syncService/updateProject

Send a request to this endpoint to update one or more Project. For each JSON object provided in the request body, an application object with a matching ID value will be updated to reflect the JSON contents.

Request

Header Parameters
Supported Media Types
Request Body - application/json ()
Root Schema : UpdateProjectSyncRequest
Type: object
Title: UpdateProjectSyncRequest
Update Project Sync Request
Show Source
Nested Schema : Activity
Type: array
Show Source
Nested Schema : ActivityCode
Type: array
Show Source
Nested Schema : ActivityCodeType
Type: array
Show Source
Nested Schema : ActivityExpense
Type: array
Show Source
Nested Schema : ActivityNote
Type: array
Show Source
Nested Schema : ActivityRisk
Type: array
Show Source
Nested Schema : ActivityStep
Type: array
Show Source
Nested Schema : BaselineProject
Type: object
Title: BaselineProject
BaselineProject Entity
Show Source
Nested Schema : BaselineType
Type: array
Show Source
Nested Schema : Calendar
Type: array
Show Source
Nested Schema : CBS
Type: array
Show Source
Nested Schema : CostAccount
Type: array
Show Source
Nested Schema : Currency
Type: array
Show Source
Nested Schema : EPS
Type: array
Show Source
Nested Schema : ExpenseCategory
Type: array
Show Source
Nested Schema : FinancialPeriod
Type: array
Show Source
Nested Schema : GlobalPreferences
Type: array
Show Source
Nested Schema : LeanTask
Type: array
Show Source
Nested Schema : Location
Type: array
Show Source
Nested Schema : NotebookTopic
Type: array
Show Source
Nested Schema : Project
Type: object
Title: Project
Project Entity
Show Source
Nested Schema : ProjectCode
Type: array
Show Source
Nested Schema : ProjectCodeType
Type: array
Show Source
Nested Schema : ProjectResource
Type: array
Show Source
Nested Schema : Relationship
Type: array
Show Source
Nested Schema : RequestSettings
Type: object
Title: RequestSettings
Update RequestSettings Entity
Show Source
Nested Schema : Resource
Type: array
Show Source
Nested Schema : ResourceAssignment
Type: array
Show Source
Nested Schema : ResourceAssignmentCode
Type: array
Show Source
Nested Schema : ResourceAssignmentCodeType
Type: array
Show Source
Nested Schema : ResourceCode
Type: array
Show Source
Nested Schema : ResourceCodeType
Type: array
Show Source
Nested Schema : ResourceCurve
Type: array
Show Source
Nested Schema : ResourceRate
Type: array
Show Source
Nested Schema : ResourceRole
Type: array
Show Source
Nested Schema : Risk
Type: array
Show Source
Nested Schema : RiskImpact
Type: array
Show Source
Nested Schema : RiskMatrix
Type: array
Show Source
Nested Schema : RiskMatrixScore
Type: array
Show Source
Nested Schema : RiskMatrixThreshold
Type: array
Show Source
Nested Schema : RiskResponseAction
Type: array
Show Source
Nested Schema : RiskResponseActionImpact
Type: array
Show Source
Nested Schema : RiskResponsePlan
Type: array
Show Source
Nested Schema : RiskThreshold
Type: array
Show Source
Nested Schema : RiskThresholdLevel
Type: array
Show Source
Nested Schema : Role
Type: array
Show Source
Nested Schema : RoleCode
Type: array
Show Source
Nested Schema : RoleCodeType
Type: array
Show Source
Nested Schema : RoleLimit
Type: object
Additional Properties Allowed
Show Source
Nested Schema : RoleRate
Type: array
Show Source
Nested Schema : UDFType
Type: array
Show Source
Nested Schema : UnitOfMeasure
Type: array
Show Source
Nested Schema : WBS
Type: array
Show Source
Nested Schema : WBSCategory
Type: array
Show Source
Nested Schema : Activity
Type: object
Title: Activity
Activity Entity
Show Source
  • The difference between the planned value of work scheduled and the actual cost of work performed. Computed as accounting variance = planned value - actual cost . A negative value indicates that actual costs have exceeded the scheduled costs.
  • The difference between the planned value of work scheduled and the actual work performed. Computed as accounting variance labor units = planned value labor units - actual units. A negative value indicates that actual costs have exceeded the scheduled costs.
  • The action needed to be performed: "create", "update", "delete", "match" or "none".
  • The unique user ID of the activity owner.
  • The total working time from the activity actual start date to the actual finish date (for completed activities), or to the current data date (for in-progress activities). The actual working time is computed using the activity's calendar.
  • The actual costs for all project expenses associated with the activity.
  • The date on which the activity is actually finished.
  • The actual costs for all labor resources assigned to the activity. If no resources are assigned, computed as the activity actual labor units * project default price / time.
  • The actual units for all labor resources assigned to the activity.
  • The sum of all regular and overtime costs for material resources.
  • The actual costs for all nonlabor resources assigned to the activity. If no resources are assigned, computed as the activity actual nonlabor units * project default price / time.
  • The actual units for all nonlabor resources assigned to the activity.
  • The date on which the activity is actually started.
  • The actual this period labor cost for all labor resources assigned to the activity.
  • The actual this period labor units (hours) for all labor resources assigned to the activity.
  • The sum of all material resource costs for the current period.
  • The actual this period nonlabor cost for all nonlabor resources assigned to the activity. If no resources are assigned, computed as the activity actual nonlabor units * project default price / time.
  • The actual this period nonlabor units (hours) for all nonlabor resources assigned to the activity.
  • The actual total cost for the activity, including labor resources, nonlabor resources, and project expenses. Actual total cost = actual labor costs + actual nonlabor costs + actual expense costs.
  • The sum of Actual Labor Units and Actual Nonlabor Units.
  • 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 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 costs for all labor resources assigned to the activity. Computed as actual labor cost + remaining labor cost. Same as the planned labor costs if the activity is not started and the actual labor costs once the activity is completed.
  • The sum of the actual plus remaining units for all labor resources assigned to the activity. Computed as actual labor units + remaining labor units. Same as the planned labor units if the activity is not started and the actual labor units once the activity is completed.
  • The project baseline planned total labor units minus the estimate at completion labor units.
  • The project baseline planned total labor units minus the estimate at completion labor units.
  • The sum of the actual plus remaining costs for all nonlabor resources assigned to the activity. Computed as actual nonlabor cost + remaining nonlabor cost. Same as the planned nonlabor costs if the activity is not started and the actual nonlabor costs once the activity is completed.
  • The sum of the actual plus remaining units for all nonlabor resources assigned to the activity. Computed as actual nonlabor units + remaining nonlabor units. Same as the planned nonlabor units if the activity is not started and the actual nonlabor units once the activity is completed.
  • The total cost at completion for the activity, including labor resources, nonlabor resources, and project expenses. At completion total cost = at completion labor cost + at completion nonlabor cost + at completion expense cost.
  • The sum of the actual plus remaining units for the resource assignment on the activity.
  • The difference between the project baseline total cost and the current estimate of total cost. Computed as VAC = BAC - EAC. A negative value indicates an estimated cost overrun. BAC is computed from the current project baseline.
  • 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 duration for the activity in the primary baseline. The duration is the total working time from the activity current start date to the current finish date. Same as the actual duration plus the remaining duration. The total working time is computed using the activity's calendar.
  • The current finish date of the activity in the primary baseline. Set to 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 planned duration for the activity in the primary baseline. Planned duration is the total working time from the activity current start date to the current finish date. Same as the actual duration plus the remaining duration. The total working time is computed using the activity's calendar. This field is named Baseline 1 Budgeted Duration in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.
  • The planned costs for all project expenses associated with the activity. This field is named Baseline 1 Budgeted Expense Cost in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.
  • The cost at completion for all labor resources assigned to the activity in the primary baseline. Computed from the primary baseline at completion labor units. If no resources are assigned, computed as the activity BL labor units * project default price / time. This field is named Baseline 1 Budgeted Labor Cost in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.
  • The planned units for all labor resources assigned to the activity. This field is named Baseline 1 Budgeted Labor Units in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.
  • The Planned Material Cost for a primary baseline activity.
  • The planned costs for all nonlabor resources assigned to the activity. If no resources are assigned, computed as the activity planned nonlabor units * project default price / time. This field is named Baseline 1 Budgeted Non Labor Cost in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.
  • The planned units for all nonlabor resources assigned to the activity. This field is named Baseline 1 Budgeted Non Labor Units in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.
  • The planned total cost for the activity, including labor resources, nonlabor resources, and project expenses. Planned total cost = planned labor cost + planned nonlabor cost + planned expense cost. This field is named Baseline 1 Budgeted Total Cost in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.
  • The current start date of the activity in the primary baseline. Set to the planned start date until the activity is started, then set to the actual start date.
  • The duration for the activity in the secondary baseline. The duration is the total working time from the activity current start date to the current finish date. Same as the actual duration plus the remaining duration. The total working time is computed using the activity's calendar.
  • The planned units for all labor resources assigned to the activity. This field is named Baseline Budgeted Labor Units in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.The current finish date of the activity in the user's secondary baseline. Set to 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 planned duration for the activity in the secondary baseline. Planned duration is the total working time from the activity current start date to the current finish date. Same as the actual duration plus the remaining duration. The total working time is computed using the activity's calendar. This field is named Baseline 2 Budgeted Duration in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.
  • The planned costs for all project expenses associated with the activity. This field is named Baseline 2 Budgeted Expense Cost in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.
  • The planned costs for all project expenses associated with the activity in the user's secondary baseline. This field is named Baseline Budgeted Expense Cost in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.
  • The planned units for all labor resources assigned to the activity. This field is named Baseline 2 Budgeted Labor Units in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.
  • The Planned Material Cost for the activity in the user's secondary baseline.
  • The planned costs for all nonlabor resources assigned to the activity. If no resources are assigned, computed as the activity planned nonlabor units * project default price / time. This field is named Baseline 2 Budgeted Non Labor Cost in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.
  • The planned units for all nonlabor resources assigned to the activity. This field is named Baseline 2 Budgeted Non Labor Units in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.
  • The planned total cost for the activity, including labor resources, nonlabor resources, and project expenses. Planned total cost = planned labor cost + planned nonlabor cost + planned expense cost. This field is named Baseline 2 Budgeted Total Cost in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.
  • The current start date of the activity in the user's secondary baseline. Set to the planned start date until the activity is started, then set to the actual start date.
  • The duration for the activity in the tertiary baseline.The duration is the total working time from the activity current start date to the current finish date. Same as the actual duration plus the remaining duration. The total working time is computed using the activity's calendar.
  • The current finish date of the activity in the user's tertiary baseline. Set to 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 planned duration for the activity in the tertiary baseline. Planned duration is the total working time from the activity current start date to the current finish date. Same as the actual duration plus the remaining duration. The total working time is computed using the activity's calendar. This field is named Baseline 3 Budgeted Duration in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.
  • The planned costs for all project expenses associated with the activity. This field is named Baseline 3 Budgeted Expense Cost in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.
  • The planned costs for all project expenses associated with the activity in the user's tertiary baseline. This field is named Baseline Budgeted Expense Cost in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.
  • The planned units for all labor resources assigned to the activity. This field is named Baseline 3 Budgeted Labor Units in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.
  • The Planned Material Cost for the activity in the user's tertiary baseline.
  • The planned costs for all nonlabor resources assigned to the activity. If no resources are assigned, computed as the activity planned nonlabor units * project default price / time. This field is named Baseline 3 Budgeted Non Labor Cost in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.
  • The planned units for all nonlabor resources assigned to the activity. This field is named Baseline 3 Budgeted Non Labor Units in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.
  • The planned total cost for the activity, including labor resources, nonlabor resources, and project expenses. Planned total cost = planned labor cost + planned nonlabor cost + planned expense cost. This field is named Baseline 3 Budgeted Total Cost in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.
  • The current start date of the activity in the user's tertiary baseline. Set to the planned start date until the activity is started, then set to the actual start date.
  • The duration for the activity in the project baseline. The duration is the total working time from the activity current start date to the current finish date. Same as the actual duration plus the remaining duration. The total working time is computed using the activity's calendar.
  • The current finish date of the activity in the project baseline. Set to 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 planned duration for the activity in the project baseline. Planned duration is the total working time from the activity current start date to the current finish date. Same as the actual duration plus the remaining duration. The total working time is computed using the activity's calendar. This field is named Baseline Budgeted Duration in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.
  • The planned costs for all project expenses associated with the activity. This field is named Baseline Budgeted Expense Cost in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.
  • The cost at completion for all labor resources assigned to the activity in the project baseline. Computed from the baseline at completion labor units. If no resources are assigned, computed as the activity BL labor units * project default price / time. This field is named Baseline Budgeted Labor Cost in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.
  • The planned units for all labor resources assigned to the activity. This field is named Baseline Budgeted Labor Units in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.
  • The Planned Material Cost for a project baseline activity.
  • The planned costs for all nonlabor resources assigned to the activity. If no resources are assigned, computed as the activity planned nonlabor units * project default price / time. This field is named Baseline Budgeted Non Labor Cost in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.
  • The planned units for all nonlabor resources assigned to the activity. This field is named Baseline Budgeted Non Labor Units in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.
  • The planned total cost for the activity, including labor resources, nonlabor resources, and project expenses. Planned total cost = planned labor cost + planned nonlabor cost + planned expense cost. This field is named Baseline Budgeted Total Cost in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.
  • The current start date of the activity in the project baseline. Set to the planned start date until the activity is started, then set to the actual start date.
  • The planned total cost through activity completion. Computed as planned labor cost + planned nonlabor cost + planned expense cost, same as the planned total cost.
  • The name of the calendar.
  • The unique ID of the calendar assigned to the activity. Activity calendars can be assigned from the global calendar pool or the project calendar pool.
  • The unique name of the Unifier CBS Code. Assign CBS codes to activities so that you can filter which activities you will send to Unifier.
  • The unique Id of CBS Code.
  • The identifier of the CoUnifier CBS.
  • Code
  • The percent complete of costs for all labor resources, nonlabor resources, and expenses for the activity. Computed as actual total cost / at completion total cost * 100. Always in the range 0 to 100.
  • The percent complete of planned costs for all labor resources, nonlabor resources, and expenses for the activity. Computed as actual total cost / BL planned total cost * 100. The value can exceed 100.
  • The earned value divided by the actual cost. A value less than 1 indicates that actual cost have exceeded the planned value.
  • The ratio of the earned value labor units and the actual work performed. Computed as CPI labor units = earned value labor units / actual labor units .
  • The difference between the earned value and the actual cost of work performed. Computed as CV = earned value - actual costs. A negative value indicates that actual costs have exceeded the value of work performed.
  • The ratio of the cost variance and the earned value of work performed. Computed as CVI = cost variance / earned value.
  • The ratio of the cost variance labor units and the earned value of work performed. Computed as CVI labor units = CV labor units / earned value labor units
  • The difference between the earned value of labor units and the actual cost of labor units. Calculated as CV labor units = earned value planned units - actual units. A negative value indicates that actual costs have exceeded the value of work performed.
  • The date this activity was created.
  • The name of the user that created this activity.
  • The current data date for the project. The project status is up to date as of the data date. The data date is modified when project actuals are applied.
  • The duration between the activity's primary baseline duration and the at complete duration. Computed as primary baseline duration - at completion duration.
  • The duration between the activity's secondary baseline duration and the at complete duration. Computed as secondary baseline duration - at completion duration.
  • The duration between the activity's tertiary baseline duration and the at complete duration. Computed as tertiary baseline duration - at completion duration.
  • The percent complete of the activity duration. Computed as (planned duration - remaining duration) / planned duration * 100. Always in the range 0 to 100. The planned duration is taken from the current plan, not from the baseline.
  • The activity actual duration percent of planned. Computed as actual duration / BL duration * 100. The value can exceed 100. The BL duration is the activity's at completion duration from the project baseline.
  • The duration type of the activity. One of 'Fixed Units/Time', 'Fixed Duration and Units/Time', 'Fixed Units', or 'Fixed Duration and Units'. For 'Fixed Units/Time' activities, the resource units per time are constant when the activity duration or units are changed. This type is used when an activity has fixed resources with fixed productivity output per time period. For 'Fixed Duration and Units/Time' activities, the activity duration is constant as the units or resource units per time are changed. This type is used when the activity is to be completed within a fixed time period regardless of the resources assigned. For 'Fixed Units' activities, the activity units are constant when the duration or resource units per time are changed. This type is used when the total amount of work is fixed, and increasing the resources can decrease the activity duration.
  • The duration between the activity's project baseline duration and the at complete duration. Computed as project baseline duration - at completion duration.
  • The earliest possible date the activity can finish. This date is computed by the project scheduler based on network logic, schedule constraints, and resource availability.
  • The earliest possible date the remaining work for the activity can begin. This date is computed by the project scheduler based on network logic, schedule constraints, and resource availability.
  • The portion of the project baseline total cost of the activity that is actually completed as of the project data date. Computed as earned value = BAC * performance % complete. The method for computing performance % complete depends on the earned-value technique selected for the activity's WBS. BAC is computed from the project baseline.
  • The portion of the project baseline labor units that is actually completed as of the project data date. Computed as labor units earned value = project baseline labor units * performance % complete. The method for computing performance % complete depends on the earned-value technique selected for the activity's WBS. The BL labor units is taken from the project baseline.
  • The estimated cost at completion for the activity. Computed as the actual total cost plus the estimate-to-complete cost; EAC = ACWP + ETC. Note that the method for computing ETC depends on the earned-value technique selected for the activity's WBS.
  • The estimated labor units at completion of the activity. Calculated as actual labor units + estimate to complete labor units. estimate to complete labor units is calculated based off of the earned value setting on the WBS.
  • The estimated cost to complete the activity. Computed as either the remaining total cost for the activity (remaining total cost), or as PF * (BAC - earned value), depending on the earned-value technique selected for the activity's WBS. BAC is computed from the project baseline.
  • The estimated quantity to complete the activity. Computed as either the remaining total units for the activity (remaining total units), or as PF * (BL labor units - earned value), depending on the earned-value technique selected for the activity's WBS.
  • The date the activity is expected to be finished according to the progress made on the activity's work products. The expected finish date is entered manually by people familiar with progress of the activity's work products.
  • The difference between primary baseline expense cost and at completion expense cost. Calculated as primary baseline expense cost - at completion expense cost (at completion expense cost = actual expense cost + remaining expense cost).
  • The difference between secondary baseline expense cost and at completion expense cost. Calculated as secondary baseline expense cost - at completion expense cost (at completion expense cost = actual expense cost + remaining expense cost).
  • The difference between tertiary baseline expense cost and at completion expense cost. Calculated as tertiary baseline expense cost - at completion expense cost (at completion expense cost = actual expense cost + remaining expense cost).
  • The percent complete of costs for all expenses associated with the activity. Computed as actual expense cost / at completion expense cost * 100. Always in the range 0 to 100.
  • The difference between project baseline expense cost and at completion expense cost. Calculated as project baseline expense cost - at completion expense cost (at completion expense cost = actual expense cost + remaining expense cost).
  • The date value that determines the early start date for imported activities with external constraints lost (relations from/to external projects that do not exist in the database). This field is the relationship early finish date (REF) when the lost relationship type is FS or SS. When the relationship type is SF or FF, this field is calculated as REF - RD of the successor.
  • The date value that determines the Late Finish Date for imported activities with external constraints lost (from/to external projects that do not exist in the database). This field is the relationship late finish date (RLF) when the lost relationship type is FS or FF. When the relationship type is SS or SF, this field is calculated as RLS + RD of the predecessor.
  • The feedback from the resource.
  • The current finish date of the activity. Set to 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 duration between the finish date in the current project and the primary baseline finish date. Calculated as finish date - primary baseline finish date.
  • the duration between the finish date in the current project and the secondary baseline finish date. Calculated as finish date - secondary baseline finish date.
  • the duration between the finish date in the current project and the tertiary baseline finish date. Calculated as finish date - tertiary baseline finish date.
  • The duration between the finish date in the current project and the project baseline finish date. Calculated as finish date - project baseline finish date.
  • The integer representing the critical path this activity is on. The value 1 is the most critical path, value 2 is the second most critical path, etc.
  • The integer representing the order in which this object was found on one of the critical paths.
  • The amount of time the activity can be delayed before delaying the start date of any successor activity.
  • The globally unique ID generated by the system.
  • The flag that indicates whether a resource assignment on the activity has future bucket data.
  • The short ID that uniquely identifies the activity within the project.
  • The boolean value indicating if this business object is related to a Project or Baseline
  • The flag that indicates 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.
  • The flag that indicates whether an activity is on the longest path. Default = 'N'
  • The flag that indicates that a resource has sent feedback notes about this activity which have not been reviewed yet.
  • The boolean value indicating if this business object has been assigned a star in P6 Team Member
  • The boolean value indicating if this business object is related to a template Project.
  • Indicates if this WBS is a workpackage in Prime or not.
  • The difference between primary baseline labor cost and at completion labor cost. Calculated as BL labor cost - at completion labor cost
  • The difference between secondary baseline labor cost and at completion labor cost. Calculated as BL labor cost - at completion labor cost
  • The difference between tertiary baseline labor cost and at completion labor cost. Calculated as BL labor cost - at completion labor cost
  • The percent complete of costs for all labor resources assigned to the activity. Computed as actual labor cost / at completion labor cost * 100. Always in the range 0 to 100.
  • The difference between project baseline labor cost and at completion labor cost. Calculated as BL labor cost - at completion labor cost
  • The difference between primary baseline labor units and at completion labor units. Calculated as BL labor units - at completion labor units.
  • The difference between secondary baseline labor units and at completion labor units. Calculated as BL labor units - at completion labor units.
  • The difference between tertiary baseline labor units and at completion labor units. Calculated as BL labor units - at completion labor units.
  • The percent complete of units for all labor resources for the activity. Computed as actual labor units / at completion labor units * 100. Always in the range 0 to 100.
  • The difference between project baseline labor units and at completion labor units. Calculated as BL labor units - at completion labor units.
  • The date this activity was last updated.
  • The name of the user that last updated this activity.
  • The latest possible date the activity must finish without delaying the project finish date. This date is computed by the project scheduler based on network logic, schedule constraints, and resource availability.
  • The latest possible date the remaining work for the activity must begin without delaying the project finish date. This date is computed by the project scheduler based on network logic, schedule constraints, and resource availability.
  • The activity priority used to prioritize activities in a project when performing resource leveling. Valid values are 'Top', 'High', 'Normal', 'Low', and 'Lowest'.
  • The name of the location assigned to the activity.
  • The unique ID of the location assigned to the activity.
  • The primary Baseline Planned Material Cost minus the At Completion Material Cost.
  • The secondary Baseline Planned Material Cost minus the At Completion Material Cost.
  • The tertiary Baseline Planned Material Cost minus the At Completion Material Cost.
  • The percent complete of costs for all material resources assigned to the activity. Computed as actual nonlabor cost / at completion nonlabor cost * 100. Always in the range 0 to 100.
  • The project BaselinePlannedMaterialCost minus the AtCompletionMaterialCost.
  • The maximum duration of the activity.
  • The minimum duration of the activity.
  • The most likely duration of the activity.
  • The name of the activity. The activity name does not have to be unique.
  • The difference between the primary baseline nonlabor cost and at completion nonlabor cost. Calculated as BL nonlabor cost - at completion nonlabor cost.
  • The difference between the secondary baseline nonlabor cost and at completion nonlabor cost. Calculated as BL nonlabor cost - at completion nonlabor cost.
  • The difference between the tertiary baseline nonlabor cost and at completion nonlabor cost. Calculated as BL nonlabor cost - at completion nonlabor cost.
  • The percent complete of costs for all nonlabor resources assigned to the activity. Computed as actual nonlabor cost / at completion nonlabor cost * 100. Always in the range 0 to 100.
  • The difference between the project baseline labor cost and at completion labor cost. Calculated as BL nonlabor cost - at completion nonlabor cost.
  • The difference between the primary baseline nonlabor units and at completion nonlabor units. Calculated as BL nonlabor units - at completion nonlabor units.
  • The difference between the secondary baseline nonlabor units and at completion nonlabor units. Calculated as BL nonlabor units - at completion nonlabor units.
  • The difference between the tertiary baseline nonlabor units and at completion nonlabor units. Calculated as BL nonlabor units - at completion nonlabor units.
  • The percent complete of units for all nonlabor resources for the activity. Computed as actual nonlabor units / at completion nonlabor units * 100. Always in the range 0 to 100.
  • The difference between the project baseline labor units and at completion labor units. Calculated as BL nonlabor units - at completion nonlabor units.
  • The notes from the project manager to the timesheet resources.
  • The unique ID generated by the system.
  • A comma separated list of activity owner IDs.
  • A comma separated list of activity owner names.
  • The activity percent complete. This value is tied to the activity duration % complete, units % complete, or physical % complete, depending on the setting for the activity's percent complete type, which is one of Duration, Units, or Physical. Always in the range 0 to 100.
  • The activity percent complete type: 'Physical', 'Duration', or 'Units'.
  • The activity performance percent complete. The performance percent complete is used to compute earned value and may be based on the activity % complete, on the 0/100 rule, on the 50/50 rule, etc., depending on the technique for computing earned-value percent complete for the activity's WBS. The performance % complete specifies what percentage of the activity's planned worth has been earned so far.
  • The physical percent complete, which can either be user entered or calculated from the activity's weighted steps.
  • The total working time from the activity planned start date to the planned finish date. The planned working time is computed using the activity's calendar. This field is named OriginalDuration in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.
  • The planned costs for all project expenses associated with the activity. This field is named BudgetedExpenseCost in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.
  • The date the activity is scheduled to finish. 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.
  • The planned costs for all labor resources assigned to the activity. If no resources are assigned, computed as the activity planned labor units * project default price / time. This field is named BudgetedLaborCost in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.
  • The planned units for all labor resources assigned to the activity. This field is named BudgetedLaborUnits in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.
  • The sum of all material resource costs.
  • The planned costs for all nonlabor resources assigned to the activity. If no resources are assigned, computed as the activity planned nonlabor units * project default price / time. This field is named BudgetedNonLaborCost in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.
  • The planned units for all nonlabor resources assigned to the activity. This field is named BudgetedNonLaborUnits in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.
  • The date the activity is scheduled to begin. 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.
  • The planned total cost for the activity, including labor resources, nonlabor resources, and project expenses. Planned total cost = planned labor cost + planned nonlabor cost + planned material cost + planned expense cost. This field is named BudgetedTotalCost in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.
  • The sum of Planned Labor Units and Planned Nonlabor Units. This field is named BudgetedTotalUnits in Primavera's Engineering & Construction and Maintenance & Turnaround solutions.
  • The portion of the project baseline total cost of the activity that is scheduled to be completed as of the project data date. Computed as BAC * schedule % complete. Also known as the work scheduled to be performed for the activity. The schedule % complete specifies how much of the activity's project baseline duration has been completed so far. BAC is computed from the project baseline.
  • The portion of the project baseline labor units that is scheduled to be completed as of the project data date. Computed as BL labor units * schedule % complete. The schedule % complete specifies how much of the activity's project baseline duration has been completed so far. BL labor units is taken from the project baseline.
  • The Post Response Pessimistic Finish date calculated by Oracle Prime during quantitative risk analysis.
  • The Post Response Pessimistic Start date calculated by Oracle Prime during quantitative risk analysis.
  • The Pre Response Pessimistic Finish date calculated by Oracle Prime during quantitative risk analysis.
  • The Pre Response Pessimistic Start date calculated by Oracle Prime during quantitative risk analysis.
  • The constraint date for the activity, if the activity has a constraint. The activity's constraint type determines whether this is a start date or finish date. Activity constraints are used by the project scheduler.
  • The type of constraint applied to the activity start or finish date. Activity constraints are used by the project scheduler. Start date constraints are 'Start On', 'Start On or Before', and 'Start On or After'. Finish date constraints are 'Finish On', 'Finish On or Before', and 'Finish On or After'. Another type of constraint, 'As Late As Possible', schedules the activity as late as possible based on the available free float.
  • The name of the resource.
  • The name of the resource.
  • The unique ID of the primary resource for the activity. The primary resource is responsible for the overall work on the activity and updates the activity status using Timesheets.
  • Indicates if this WBS node is a Project/EPS node.
  • The short code of the associated project.
  • The name of the associated project.
  • The character used to differentiate levels of a project or WBS structure when exporting to CPP format.
  • The unique ID of the associated project.
  • Indicates if this Project/EPS nose is a Project or EPS.
  • The remaining duration of the activity. Remaining duration is the total working time from the activity remaining start date to the remaining finish date. The remaining working time is computed using the activity's calendar. Before the activity is started, the remaining duration is the same as the planned duration. After the activity is completed the remaining duration is zero.
  • The remaining late end date, which is calculated by the scheduler.
  • The date the remaining work for the activity is scheduled to begin. 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. This is the start date that Timesheets users follow.
  • The remaining costs for all project expenses associated with the activity.
  • The amount of time remaining by which the activity can be delayed before delaying the project finish date. Computed as late finish - remaining finish. If the remaining finish is the same as the early finish (in general, when the activity is not started), then the remaining float is the same as the total float.
  • The remaining costs for all labor resources assigned to the activity. If no resources are assigned, computed as the activity remaining labor units * project default price / time.
  • The remaining units for all labor resources assigned to the activity. The remaining units reflects the work remaining to be done for the 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 remaining late finish date calculated by the scheduler.
  • The remaining late start date calculated by the scheduler.
  • The sum of all material resource remaining costs.
  • The remaining costs for all nonlabor resources assigned to the activity. If no resources are assigned, computed as the activity remaining nonlabor units * project default price / time.
  • The remaining units for all nonlabor resources assigned to the activity. The remaining units reflects the work remaining to be done for the 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 remaining total cost for the activity, including labor resources, nonlabor resources, and project expenses. Remaining total cost = remaining labor costs + remaining nonlabor costs + remaining expense costs.
  • The sum of Remaining Labor Units and Remaining Nonlabor Units.
  • The date when a suspended task or resource dependent activity should be resumed. The resume date must be later than the suspend date and earlier than the actual finish date. The Suspend/Resume period behaves like a nonworktime on the activity calendar or resource calendar for task and resource dependent activities.
  • The finish date of the activity as proposed by the primary resource using Timesheets, while the activity is in "For Review" state. If the project manager approves the activity completion, the review finish is copied to the actual finish.
  • The indicator that determines whether the activity status updates made in Team Member interfaces must be approved before committing changes.
  • The activity review status. Valid values are 'OK', 'For Review', and 'Rejected'. Primary resources set the status to 'For Review' when they believe the activity is completed but are not allowed to mark activities as completed.
  • The activity schedule percent complete, which specifies how much of the activity's project baseline duration has been completed so far. Computed based on where the current data date falls relative to the activity's project baseline start and finish dates. If the data date is earlier than the BL start, the schedule % complete is 0. If the data date is later than the BL finish, the schedule % complete is 100. The schedule % complete indicates how much of the activity duration should be currently completed, relative to the selected project baseline.
  • The ratio of the earned value of work performed and the work scheduled to be performed. Computed as SPI = earned value/ planned value. A value less than 1 indicates that less work was actually performed than was scheduled.
  • The ratio of the earned value of labor units and the planned value of labor units. Computed as SPI labor units = earned value labor units / planned value labor units.
  • The difference between the earned value of work performed and the work scheduled to be performed. Computed as SV = earned value - planned value. A negative value indicates that less work was actually performed than was scheduled.
  • The ratio of the schedule variance and the work scheduled to be performed. Computed as SVI = SV / planned value.
  • The ratio of the schedule variance and the work scheduled to be performed. Computed as SVI labor units = SV labor units / planned value labor units.
  • The difference between the earned value of work performed and the work scheduled to be performed. Computed as SV labor units = earned value labor units - planned value labor units.
  • The date to be used for the cstr_type2 assignment, if the activity has a cstr_type2 value. The activity's constraint type determines whether this is a start date or finish date. Activity constraints are used by the project scheduler.
  • The additional constraint to be used by the scheduler. If more than one constraint is assigned, this value should be restricted to one of the following: "Start On or Before", "Start On or After", "Finish On or Before", or "Finish On or After".
  • The start date of the activity. Set to the remaining start date until the activity is started, then set to the actual start date.
  • The duration between the start date in the current project and the primary baseline start date. Calculated as start date - primary baseline start date.
  • The duration between the start date in the current project and the secondary baseline start date. Calculated as start date - secondary baseline start date.
  • The duration between the start date in the current project and the tertiary baseline start date. Calculated as start date - tertiary baseline start date.
  • The duration between the start date in the current project and the project baseline start date. Calculated as start date - project baseline start date.
  • The current status of the activity, either 'Not Started', 'In Progress', or 'Completed'.
  • The project status, either 'Planned', 'Active', 'Inactive', 'What-If', 'Requested', or 'Template'.
  • The start date when the progress of a task or resource dependent activity is delayed from. The suspend date must be later than the actual start date, which the activity must have. The progress of the activity can be resumed by setting the resume date. The Suspend/Resume period behaves like a nonworktime on the activity calendar or resource calendar for task and resource dependent activities.
  • The TCPI, which is calculated as (budget at completion - earned value) / (estimate at completion - ACWP).
  • The difference between the primary baseline total cost and the at completion total cost. Calculated as BL total cost - at completion total cost.
  • The difference between the secondary baseline total cost and the at completion total cost. Calculated as BL total cost - at completion total cost.
  • The difference between the tertiary baseline total cost and the at completion total cost. Calculated as BL total cost - at completion total cost.
  • The difference between the project baseline total cost and the at completion total cost. Calculated as BL total cost - at completion total cost.
  • The amount of time the activity can be delayed before delaying the project finish date. Total float can be computed as late start - early start or as late finish - early finish; this option can be set when running the project scheduler.
  • The total stored period earned value cost for each activity.
  • The total stored period earned value labor units for each activity.
  • The total stored period expense cost for each activity.
  • The total stored period labor cost for each activity.
  • The total stored period labor units for each activity.
  • The total stored period material cost for each activity.
  • The total stored period non labor cost for each activity.
  • The total stored period non labor units for each activity.
  • The total stored period planned value cost for each activity.
  • The total stored period planned value labor units for each activity.
  • The type of activity, either 'Task Dependent', 'Resource Dependent', 'Level of Effort', 'Start Milestone', 'Finish Milestone', or 'WBS Summary'. A 'Task Dependent' activity is scheduled using the activity's calendar rather than the calendars of the assigned resources. A 'Resource Dependent' activity is scheduled using the calendars of the assigned resources. This type is used when several resources are assigned to the activity, but they may work separately. A 'Start Milestone' or 'Finish Milestone' is a zero-duration activity without resources, marking a significant project event. A 'Level of Effort' activity has a duration that is determined by its dependent activities. Administration-type activities are typically 'Level of Effort'. A 'WBS Summary' comprises a group of activities that share a common WBS level. For example, all activities whose WBS codes start with A (A.1, A.1.1, A.1.1.2, A.2, A.3 and so forth) can be part of one WBS activity whose WBS code is A.
  • UDF
  • The percent complete of units for all labor and nonlabor resources assigned to the activity. Computed as actual units / at completion units * 100. Always in the range 0 to 100.
  • The number of Team Member Discussion comments associated with the Activity which have not yet been read.
  • The short code assigned to each WBS element for identification. Each WBS element is uniquely identified by concatenating its own code together with its parents' codes.
  • The name of the WBS element.
  • The unique ID of the WBS for the activity.
  • The WBS hierarchy of the activity.
Nested Schema : Code
Type: array
Show Source
Nested Schema : UDF
Type: array
Show Source
Nested Schema : Code
Type: object
Title: Code
Code Entity
Show Source
Nested Schema : UDF
Type: object
Title: UDF
UDF Entity
Show Source
Nested Schema : ActivityCode
Type: object
Title: ActivityCode
ActivityCode Entity
Show Source
Nested Schema : ActivityCodeType
Type: object
Title: ActivityCodeType
ActivityCodeType Entity
Show Source
Nested Schema : ActivityExpense
Type: object
Title: ActivityExpense
ActivityExpense Entity
Show Source
Nested Schema : UDF
Type: array
Show Source
Nested Schema : ActivityNote
Type: object
Title: ActivityNote
ActivityNote Entity
Show Source
Nested Schema : ActivityRisk
Type: object
Title: ActivityRisk
ActivityRisk Entity
Show Source
Nested Schema : ActivityStep
Type: object
Title: ActivityStep
ActivityStep Entity
Show Source
Nested Schema : UDF
Type: array
Show Source
Nested Schema : Code
Type: array
Show Source
Nested Schema : UDF
Type: array
Show Source
Nested Schema : BaselineType
Type: object
Title: BaselineType
BaselineType Entity
Show Source
Nested Schema : Calendar
Type: object
Title: Calendar
Calendar Entity
Show Source
Nested Schema : HolidayOrExceptions
Type: object
HolidayOrExceptions
Show Source
Nested Schema : StandardWorkWeek
Type: object
Show Source
Nested Schema : HolidayOrException
Type: array
Show Source
Nested Schema : HolidayOrException
Type: object
Show Source
Nested Schema : WorkTime
Type: array
Show Source
Nested Schema : WorkTime
Type: object
Show Source
Nested Schema : StandardWorkHours
Type: array
Show Source
Nested Schema : StandardWorkHours
Type: object
Show Source
Nested Schema : WorkTime
Type: array
Show Source
Nested Schema : CBS
Type: object
Title: CBS
CBS Entity
Show Source
Nested Schema : CostAccount
Type: object
Title: CostAccount
CostAccount Entity
Show Source
Nested Schema : Currency
Type: object
Title: Currency
Currency Entity
Show Source
Nested Schema : EPS
Type: object
Title: EPS
EPS Entity
Show Source
Nested Schema : ExpenseCategory
Type: object
Title: ExpenseCategory
ExpenseCategory Entity
Show Source
Nested Schema : FinancialPeriod
Type: object
Title: FinancialPeriod
FinancialPeriod Entity
Show Source
Nested Schema : GlobalPreferences
Type: object
Title: GlobalPreferences
GlobalPreferences Entity
Show Source
Nested Schema : LeanTask
Type: object
Title: LeanTask
LeanTask Entity
Show Source
Nested Schema : Location
Type: object
Title: Location
Location Entity
Show Source
Nested Schema : NotebookTopic
Type: object
Title: NotebookTopic
NotebookTopic Entity
Show Source
Nested Schema : Code
Type: array
Show Source
Nested Schema : UDF
Type: array
Show Source
Nested Schema : ProjectCode
Type: object
Title: ProjectCode
ProjectCode Entity
Show Source
Nested Schema : ProjectCodeType
Type: object
Title: ProjectCodeType
ProjectCodeType Entity
Show Source
Nested Schema : ProjectResource
Type: object
Title: ProjectResource
ProjectResource Entity
Show Source
Nested Schema : ResourceRequest
Type: object
Show Source
Nested Schema : ResourceRequestCriterion
Type: array
Show Source
Nested Schema : ResourceRequestCriterion
Type: object
Show Source
Nested Schema : Relationship
Type: object
Title: Relationship
Relationship Entity
Show Source
Nested Schema : Resource
Type: object
Title: Resource
Resource Entity
Show Source
Nested Schema : Code
Type: array
Show Source
Nested Schema : UDF
Type: array
Show Source
Nested Schema : ResourceAssignment
Type: object
Title: ResourceAssignment
ResourceAssignment Entity
Show Source
Nested Schema : Code
Type: array
Show Source
Nested Schema : UDF
Type: array
Show Source
Nested Schema : ResourceAssignmentCode
Type: object
Title: ResourceAssignmentCode
ResourceAssignmentCode Entity
Show Source
Nested Schema : ResourceAssignmentCodeType
Type: object
Title: ResourceAssignmentCodeType
ResourceAssignmentCodeType Entity
Show Source
Nested Schema : ResourceCode
Type: object
Title: ResourceCode
ResourceCode Entity
Show Source
Nested Schema : ResourceCodeType
Type: object
Title: ResourceCodeType
ResourceCodeType Entity
Show Source
Nested Schema : ResourceCurve
Type: object
Title: ResourceCurve
ResourceCurve Entity
Show Source
Nested Schema : Values
Type: object
Show Source
Nested Schema : ResourceRate
Type: object
Title: ResourceRate
ResourceRate Entity
Show Source
Nested Schema : ResourceRole
Type: object
Title: ResourceRole
ResourceRole Entity
Show Source
Nested Schema : Risk
Type: object
Title: Risk
Risk Entity
Show Source
Nested Schema : UDF
Type: array
Show Source
Nested Schema : RiskImpact
Type: object
Title: RiskImpact
RiskImpact Entity
Show Source
Nested Schema : RiskMatrix
Type: object
Title: RiskMatrix
RiskMatrix Entity
Show Source
Nested Schema : RiskMatrixScore
Type: object
Title: RiskMatrixScore
RiskMatrixScore Entity
Show Source
Nested Schema : RiskMatrixThreshold
Type: object
Title: RiskMatrixThreshold
RiskMatrixThreshold Entity
Show Source
Nested Schema : RiskResponseAction
Type: object
Title: RiskResponseAction
RiskResponseAction Entity
Show Source
Nested Schema : RiskResponseActionImpact
Type: object
Title: RiskResponseActionImpact
RiskResponseActionImpact Entity
Show Source
Nested Schema : RiskResponsePlan
Type: object
Title: RiskResponsePlan
RiskResponsePlan Entity
Show Source
Nested Schema : RiskThreshold
Type: object
Title: RiskThreshold
RiskThreshold Entity
Show Source
Nested Schema : RiskThresholdLevel
Type: object
Title: RiskThresholdLevel
RiskThresholdLevel Entity
Show Source
Nested Schema : Role
Type: object
Title: Role
Role Entity
Show Source
Nested Schema : Code
Type: array
Show Source
Nested Schema : RoleCode
Type: object
Title: RoleCode
RoleCode Entity
Show Source
Nested Schema : RoleCodeType
Type: object
Title: RoleCodeType
RoleCodeType Entity
Show Source
Nested Schema : additionalProperties
Type: object
Nested Schema : RoleRate
Type: object
Title: RoleRate
RoleRate Entity
Show Source
Nested Schema : UDFType
Type: object
Title: UDFType
UDFType Entity
Show Source
Nested Schema : UnitOfMeasure
Type: object
Title: UnitOfMeasure
UnitOfMeasure Entity
Show Source
Nested Schema : WBS
Type: object
Title: WBS
WBS Entity
Show Source
Nested Schema : UDF
Type: array
Show Source
Nested Schema : WBSCategory
Type: object
Title: WBSCategory
WBSCategory Entity
Show Source
Back to Top

Response

Supported Media Types

200 Response

OK.
Body ()
Root Schema : UpdateProjectResponseType
Type: object
Title: UpdateProjectResponseType
Update Project Sync Response
Show Source
Nested Schema : GeneralResponseType
Type: object
Title: GeneralResponseType
General Response
Show Source
Nested Schema : DeleteUnreferencedResponseType
Type: object
Title: DeleteUnreferencedResponseType
Delete Unreferenced Response
Show Source
Nested Schema : GlobalPreferencesResponseType
Type: object
Title: GlobalPreferencesResponseType
Global Preferences Response
Show Source
Nested Schema : CodeResponseType
Type: object
Title: CodeResponseType
Code Response
Show Source
Nested Schema : UDFResponseType
Type: object
Title: UDFResponseType
UDF Response
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