1. REST API for Oracle Fusion Cloud Project Management
  2. Tasks
  3. Project Insights

Get insights for a project

get

/fscmRestApi/resources/11.13.18.05/projectInsights/{ProjectId}

Request

Path Parameters
  • The value of this parameter could be a hash of the key that is used to uniquely identify the resource item. The client should not generate the hash key value. Instead, the client should query on the collection resource with a filter to navigate to a specific resource item. For example: products?q=InventoryItemId=
Query Parameters
  • This parameter specifies dependencies which are fields that are set before and rolled back after generating the response. Generally they are used to preview the effects of an attribute change. The fields specified in this parameter are always set in the resource instance in question. When a child resource collection is requested and the parameter is set, the fields will be set in the parent resource instance before generating the resource collection payload. The value of this query parameter is a set of dependency fields. Example: dependency=ProductId=2

    Format: <attr1>=<val1>,<attr2>=<value2>
  • When this parameter is provided, the specified children are included in the resource payload (instead of just a link). The value of this query parameter is "all" or "". More than one child can be specified using comma as a separator. Example: ?expand=Employees,Localizations. Nested children can also be provided following the format "Child.NestedChild" (Example: ?expand=Employees.Managers). If a nested child is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?expand=Employees.Managers" is the same as "?expand=Employees,Employees.Managers" (which will expand Employees and Managers).
  • This parameter filters the resource fields. Only the specified fields are returned, which means that if no fields are specified, no fields are returned (useful to get only the links). If an indirect child resource is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?fields=Employees.Managers:Empname" is the same as "?fields=;Employees:;Employees.Managers:Empname" (which will only return the "Empname" field for Managers). the value of this query parameter is a list of resource fields. The attribute can be a direct (Example: Employees) or indirect (Example: Employees.Managers) child. It cannot be combined with expand query parameter. If both are provided, only fields will be considered.

    Format: ?fields=Attribute1,Attribute2

    Format for fields in child resource: ?fields=Accessor1:Attribute1,Attribute2
  • This parameter can be used to show only certain links while accessing a singular resource or a resource collection. The parameter value format is a comma-separated list of : <link_relation>

    Example:
    self,canonical
  • The resource item payload will be filtered in order to contain only data (no links section, for example).
Header Parameters
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.

There's no request body for this operation.

Back to Top

Response

Supported Media Types

Default Response

The following table describes the default response for this task.
Headers
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
Body ()
Root Schema : projectInsights-item-response
Type: object
Show Source
  • Title: Actual Percentage Complete
    Read Only: true
    The percentage of reported work completed on the project.
  • Title: Actual Planned Cost
    Read Only: true
    The amount in the cost breakdown for a project that's attributed to planned costs.
  • Title: Actual Unplanned Cost
    Read Only: true
    The amount in the cost breakdown for a project that's attributed to unplanned costs.
  • Assignments
    Title: Assignments
    The Assignments resource is used to view details for the assignments ending soon and reserved assignments for a project.
  • Title: Assignments Ending
    Read Only: true
    The number of resources with assignments to the project that are scheduled to end within the next two weeks.
  • Title: Assignments Reserved Count
    Read Only: true
    The number of resources with reserved assignments to the project.
  • Title: Budget Spent
    Read Only: true
    The budgeted amount spent for the project.
  • Title: Budget to Date
    Read Only: true
    The amount of budget that's available to spend at that point in time for a project.
  • Title: Committed Cost
    Read Only: true
    The amount in the cost breakdown for a project that's attributed to committed costs. Commitments include purchase orders, purchase requisitions, and supplier invoices.
  • Title: Created By
    Read Only: true
    Maximum Length: 64
    The user who created the record.
  • Title: Creation Date
    Read Only: true
    The date when the record was created.
  • Title: Currency
    Read Only: true
    Maximum Length: 15
    The currency code for the project currency.
  • Title: Budget
    Read Only: true
    The total planned cost that's associated to the project tasks or task assignments in the current baseline budget.
  • Title: Expected Percentage Complete
    Read Only: true
    The percentage of work that should be complete as of today if the project is on schedule. The value is a calculation of expected duration multiplied by planned hours and then divided by the planned duration.
  • Title: Invoices Awaiting Approval
    Read Only: true
    The number of invoices submitted for the project that are pending approval.
  • Title: Last Update Date
    Read Only: true
    The date when the record was last updated.
  • Title: Last Updated By
    Read Only: true
    Maximum Length: 64
    The user who last updated the record.
  • Links
  • Title: Milestones at Risk
    Read Only: true
    The number of milestones that are at risk of being delayed.
  • Title: Milestones Due Soon
    Read Only: true
    The number of milestones that are due in the near future.
  • Title: Milestones Past Due
    Read Only: true
    The number of milestones that aren't completed by the finish date.
  • Missing Time Cards
    Title: Missing Time Cards
    The Missing Time Card resource is used to view the details of the missing or incomplete time card count for a project. It includes the resources and their expected hours for time cards that are missing or partially reported.
  • Title: Missing Time Cards Five Weeks Old
    Read Only: true
    The number of time cards that are missing or incomplete for a project and due five weeks ago. Only resources that are enabled to track time are considered.
  • Title: Missing Time Cards Four Weeks Old
    Read Only: true
    The number of time cards that are missing or incomplete for a project and due four weeks ago. Only resources that are enabled to track time are considered.
  • Title: Missing Time Cards One Week Old
    Read Only: true
    The number of time cards that are missing or incomplete for a project and due one week ago. Only resources that are enabled to track time are considered.
  • Title: Missing Time Cards Three Weeks Old
    Read Only: true
    The number of time cards that are missing or incomplete for a project and due three weeks ago. Only resources that are enabled to track time are considered.
  • Title: Missing Time Cards Two Weeks Old
    Read Only: true
    The number of time cards that are missing or incomplete for a project and due two weeks ago. Only resources that are enabled to track time are considered.
  • Pending Invoices
    Title: Pending Invoices
    The Pending Invoices resource is used to view the details of the invoices pending approval count for a project.
  • Title: Performance Health Status
    Read Only: true
    Maximum Length: 80
    The value representing the overall performance health of the project, such as at risk and on track. The list of values is defined in the lookup PJS_PERF_INDICATORS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • Title: Performance Health Status Code
    Read Only: true
    Maximum Length: 30
    The code representing the overall performance health of the project, such as at risk and on track. A list of values is defined in the lookup type PJS_PERF_INDICATORS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • Title: Planned
    Read Only: true
    The amount of effort planned for the project.
  • Title: Project ID
    The unique identifier of the project.
  • Title: Project Name
    Read Only: true
    Maximum Length: 240
    The display name of the project.
  • Task Exceptions
    Title: Task Exceptions
    The Task Exceptions resource is used to view the details of the task exceptions, milestones past due, and milestones due soon counts for a project. It includes what qualified the task or milestone as an exception.
  • Title: Task Exceptions Count
    Read Only: true
    The number of task exceptions for a project. Task exceptions occur when the team member changes the task dates or effort outside of the threshold values that were set during implementation or when the tasks are overdue.
  • Team Allocations
    Title: Team Allocations
    The Team Allocations resource is used to view the over and under allocated labor resource details for a project. It includes the weekly assignment, allocation, and variance hours per team member for the twelve weeks that start with the current week.
  • Title: Weeks Five to Eight Overallocated Resources
    Read Only: true
    The number of labor resources who are assigned to tasks for more than one hundred percent of their allocated hours during the next five to eight weeks of the project.
  • Title: Weeks Five to Eight Under Allocated Resources
    Read Only: true
    The number of labor resources who are assigned to tasks for less than their allocated hours during the next five to eight weeks of the project.
  • Title: Weeks Nine to Twelve Overallocated Resources
    Read Only: true
    The number of labor resources who are assigned to tasks for more than one hundred percent of their allocated hours during the next nine to twelve weeks of the project.
  • Title: Weeks Nine to Twelve Under Allocated Resources
    Read Only: true
    The number of labor resources who are assigned to tasks for less than their allocated hours during the next nine to twelve weeks of the project.
  • Title: Weeks One to Four Overallocated Resources
    Read Only: true
    The number of labor resources who are assigned to tasks for more than one hundred percent of their allocated hours for the four weeks of the project that start with the current week.
  • Title: Weeks One to Four Under Allocated Resources
    Read Only: true
    The number of labor resources who are assigned to tasks for less than their allocated hours for the four weeks of the project that start with the current week.
Nested Schema : Assignments
Type: array
Title: Assignments
The Assignments resource is used to view details for the assignments ending soon and reserved assignments for a project.
Show Source
Nested Schema : Missing Time Cards
Type: array
Title: Missing Time Cards
The Missing Time Card resource is used to view the details of the missing or incomplete time card count for a project. It includes the resources and their expected hours for time cards that are missing or partially reported.
Show Source
Nested Schema : Pending Invoices
Type: array
Title: Pending Invoices
The Pending Invoices resource is used to view the details of the invoices pending approval count for a project.
Show Source
Nested Schema : Task Exceptions
Type: array
Title: Task Exceptions
The Task Exceptions resource is used to view the details of the task exceptions, milestones past due, and milestones due soon counts for a project. It includes what qualified the task or milestone as an exception.
Show Source
Nested Schema : Team Allocations
Type: array
Title: Team Allocations
The Team Allocations resource is used to view the over and under allocated labor resource details for a project. It includes the weekly assignment, allocation, and variance hours per team member for the twelve weeks that start with the current week.
Show Source
Nested Schema : projectInsights-Assignments-item-response
Type: object
Show Source
  • Title: Assignment End Date
    The date when the resource assignment to the project is scheduled to end.
  • Title: Assignment ID
    The unique identifier of the project resource assignment.
  • Title: Start Date
    The date when the resource assignment to the project is scheduled to start.
  • Title: Assignment Status
    Read Only: true
    Maximum Length: 80
    The project assignment status for a resource, such as reserved or pending adjustment. A list of values is defined in the lookup type PJR_ASSIGN_STATUS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • Title: Assignment Status Code
    Maximum Length: 30
    The code representing the project assignment status for a resource, such as RESERVED and PENDING_ADJUSTMENT. A list of values is defined in the lookup type PJR_ASSIGN_STATUS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • Title: Created By
    Maximum Length: 64
    The user who created the record.
  • Title: Creation Date
    The date when the record was created.
  • Title: Earliest Task Start Date
    The earliest start date for the set of tasks that are assigned to the labor resource for the project.
  • Title: Last Update Date
    The date when the record was last updated.
  • Title: Last Updated By
    Maximum Length: 64
    The user who last updated the record.
  • Title: Latest Task Finish Date
    The latest finish date for the set of tasks that are assigned to the labor resource.
  • Links
  • Title: Resource ID
    The unique identifier of the project enterprise labor resource.
  • Title: Resource
    Read Only: true
    Maximum Length: 240
    The name of the project enterprise labor resource.
Nested Schema : projectInsights-MissingTimeCards-item-response
Type: object
Show Source
  • Title: Category Code for Five Weeks Old Missing Time Card
    Maximum Length: 30
    The code that represents the categorization of the missing time card for the week ending five weeks ago. Values include ORA_PJS_MISSING_TIMECARD, ORA_PJS_MISSING_HOURS, and ORA_PJS_IN_PROCESS. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_CATEGORY. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • Title: Category Code for Four Weeks Old Missing Time Card
    Maximum Length: 30
    The code that represents the categorization of the missing time card for the week ending four weeks ago. Values include ORA_PJS_MISSING_TIMECARD, ORA_PJS_MISSING_HOURS, and ORA_PJS_IN_PROCESS. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_CATEGORY. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • Title: Category Code for One Week Old Missing Time Card
    Maximum Length: 30
    The code that represents the categorization of the missing time card for the week ending one week ago. Values include ORA_PJS_MISSING_TIMECARD, ORA_PJS_MISSING_HOURS, and ORA_PJS_IN_PROCESS. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_CATEGORY. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • Title: Category Code for Three Weeks Old Missing Time Card
    Maximum Length: 30
    The code that represents the categorization of the missing time card for the week ending three weeks ago. Values include ORA_PJS_MISSING_TIMECARD, ORA_PJS_MISSING_HOURS, and ORA_PJS_IN_PROCESS. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_CATEGORY. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • Title: Category Code for Two Weeks Old Missing Time Card
    Maximum Length: 30
    The code that represents the categorization of the missing time card for the week ending two weeks ago. Values include ORA_PJS_MISSING_TIMECARD, ORA_PJS_MISSING_HOURS, and ORA_PJS_IN_PROCESS. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_CATEGORY. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • Title: Category for Five Weeks Old Missing Time Card
    The categorization of the missing time card for the week ending five weeks ago. Values include missing, partially reported, and in progress. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_CATEGORY. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • Title: Category for Four Weeks Old Missing Time Card
    The categorization of the missing time card for the week ending four weeks ago. Values include missing, partially reported, and in progress. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_CATEGORY. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • Title: Category for One Week Old Missing Time Card
    The categorization of the missing time card for the week ending one week ago. Values include missing, partially reported, and in progress. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_CATEGORY. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • Title: Category for Three Weeks Old Missing Time Card
    The categorization of the missing time card for the week ending three weeks ago. Values include missing, partially reported, and in progress. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_CATEGORY. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • Title: Category for Two Weeks Old Missing Time Card
    The categorization of the missing time card for the week ending two weeks ago. Values include missing, partially reported, and in progress. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_CATEGORY. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • Title: Commentary Code for Five Weeks Old Time Card
    Maximum Length: 30
    The code that represents the additional commentary for the time card for the week ending five weeks ago. The commentary is for a time card that exists but isn't yet approved and successfully transferred. Values are ORA_PJS_SAVED, ORA_PJS_AWAITING_APPROVAL, ORA_PJS_AWAITING_PROCESSING, ORA_PJS_REJECTED, and ORA_PJS_HOURS. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_COMMENTS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • Title: Commentary Code for Four Weeks Old Time Card
    Maximum Length: 30
    The code that represents the additional commentary for the time card for the week ending four weeks ago. The commentary is for a time card that exists but isn't yet approved and successfully transferred. Values are ORA_PJS_SAVED, ORA_PJS_AWAITING_APPROVAL, ORA_PJS_AWAITING_PROCESSING, ORA_PJS_REJECTED, and ORA_PJS_HOURS. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_COMMENTS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • Title: Commentary Code for One Week Old Time Card
    Maximum Length: 30
    The code that represents the additional commentary for the time card for the week ending one week ago. The commentary is for a time card that exists but isn't yet approved and successfully transferred. Values are ORA_PJS_SAVED, ORA_PJS_AWAITING_APPROVAL, ORA_PJS_AWAITING_PROCESSING, ORA_PJS_REJECTED, and ORA_PJS_HOURS. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_COMMENTS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • Title: Commentary Code for Three Weeks Old Time Card
    Maximum Length: 30
    The code that represents the additional commentary for the time card for the week ending three weeks ago. The commentary is for a time card that exists but isn't yet approved and successfully transferred. Values are ORA_PJS_SAVED, ORA_PJS_AWAITING_APPROVAL, ORA_PJS_AWAITING_PROCESSING, ORA_PJS_REJECTED, and ORA_PJS_HOURS. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_COMMENTS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • Title: Commentary Code for Two Weeks Old Time Card
    Maximum Length: 30
    The code that represents the additional commentary for the time card for the week ending two weeks ago. The commentary is for a time card that exists but isn't yet approved and successfully transferred. Values are ORA_PJS_SAVED, ORA_PJS_AWAITING_APPROVAL, ORA_PJS_AWAITING_PROCESSING, ORA_PJS_REJECTED, and ORA_PJS_HOURS. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_COMMENTS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • Title: Commentary for Five Weeks Old Time Card
    Additional commentary for the time card for the week ending five weeks ago. The commentary is for a time card that exists but isn't yet approved and successfully transferred. Values are saved, awaiting approval, awaiting processing, rejected, and hours less than scheduled. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_COMMENTS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • Title: Commentary for Four Weeks Old Time Card
    Additional commentary for the time card for the week ending four weeks ago. The commentary is for a time card that exists but isn't yet approved and successfully transferred. Values are saved, awaiting approval, awaiting processing, rejected, and hours less than scheduled. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_COMMENTS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • Title: Commentary for One Week Old Time Card
    Additional commentary for the time card for the week ending one week ago. The commentary is for a time card that exists but isn't yet approved and successfully transferred. Values are saved, awaiting approval, awaiting processing, rejected, and hours less than scheduled. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_COMMENTS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • Title: Commentary for Three Weeks Old Time Card
    Additional commentary for the time card for the week ending three weeks ago. The commentary is for a time card that exists but isn't yet approved and successfully transferred. Values are saved, awaiting approval, awaiting processing, rejected, and hours less than scheduled. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_COMMENTS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • Title: Commentary for Two Weeks Old Time Card
    Additional commentary for the time card for the week ending two weeks ago. The commentary is for a time card that exists but isn't yet approved and successfully transferred. Values are saved, awaiting approval, awaiting processing, rejected, and hours less than scheduled. A list of values is defined in the lookup type ORA_PJS_UDB_TIMECARD_COMMENTS. Review the list of values using the Setup and Maintenance work area and the Manage Standard Lookups task.
  • Title: Created By
    Maximum Length: 64
    The user who created the record.
  • Title: Creation Date
    The date when the record was created.
  • Title: Default Hours Five Weeks Ago
    The default hours for the week ending five weeks ago for the resource and project.
  • Title: Default Hours Four Weeks Ago
    The default hours for the week ending four weeks ago for the resource and project.
  • Title: Default Hours One Week Ago
    The default hours for the week ending one week ago for the resource and project.
  • Title: Default Hours Three Weeks Ago
    The default hours for the week ending three weeks ago for the resource and project.
  • Title: Default Hours Two Weeks Ago
    The default hours for the week ending two weeks ago for the resource and project.
  • Title: Last Update Date
    The date when the record was last updated.
  • Title: Last Updated By
    Maximum Length: 64
    The user who last updated the record.
  • Links
  • Title: Resource ID
    Read Only: true
    The unique identifier of the project enterprise labor resource.
  • Title: Resource Name
    Read Only: true
    Maximum Length: 240
    The name of the project enterprise labor resource.
  • Title: Scheduled Hours Five Weeks Ago
    The effort in hours for the week ending five weeks ago for the resource and project.
  • Title: Scheduled Hours Four Weeks Ago
    The effort in hours for the week ending four weeks ago for the resource and project.
  • Title: Scheduled Hours One Week Ago
    The effort in hours for the week ending one week ago for the resource and project.
  • Title: Scheduled Hours Three Weeks Ago
    The effort in hours for the week ending three weeks ago for the resource and project.
  • Title: Scheduled Hours Two Weeks Ago
    The effort in hours for the week ending two weeks ago for the resource and project.
  • Title: Time Card Hours Five Weeks Ago
    The effort in hours reported on a time card for the week ending five weeks ago for the resource and project.
  • Title: Time Card Hours Four Weeks Ago
    The effort in hours reported on a time card for the week ending four weeks ago for the resource and project.
  • Title: Time Card Hours One Week Ago
    The effort in hours reported on a time card for the week ending one week ago for the resource and project.
  • Title: Time Card Hours Three Weeks Ago
    The effort in hours reported on a time card for the week ending three weeks ago for the resource and project.
  • Title: Time Card Hours Two Weeks Ago
    The effort in hours reported on a time card for the week ending two weeks ago for the resource and project.
Nested Schema : projectInsights-PendingInvoices-item-response
Type: object
Show Source
Nested Schema : projectInsights-TaskExceptions-item-response
Type: object
Show Source
  • Title: Actual Hours
    The actual effort spent on the project task.
  • Title: Created By
    Maximum Length: 64
    The user who created the record.
  • Title: Creation Date
    The date when the record was created.
  • Title: Finish Delayed Indicator
    Maximum Length: 1
    Indicates whether the task finish date was updated to a later date and is beyond the threshold that was set during implementation. If true, then the finish date change is beyond the threshold.
  • Title: Finish Past Due Indicator
    Maximum Length: 1
    Indicates whether the project task finished on time. If true, then the task didn't finish on time.
  • Title: Last Update Date
    The date when the record was last updated.
  • Title: Last Updated By
    Maximum Length: 64
    The user who last updated the record.
  • Links
  • Title: Milestone
    Maximum Length: 1
    Indicates whether the task is a project milestone. If true, then the task is a milestone.
  • Title: Number of Exceptions
    The number of exceptions for a task. Task exceptions occur when the team member changes the task dates or effort outside of the threshold values that were set during implementation or when the tasks are overdue.
  • Title: Percent Complete
    The percentage of work completed for a task.
  • Title: Planned
    The planned effort required to complete the project task.
  • Title: Planned Finish Date
    The date when work is scheduled to end for a project task.
  • Title: Planned Hours Increased Indicator
    Maximum Length: 1
    Indicates whether the number of hours planned for a project task has increased more than the threshold that was set during implementation. If true, then the planned hours change is over the threshold.
  • Title: Planned Start Date
    The date when work is scheduled to start for a project task.
  • Title: Start Delayed Indicator
    Maximum Length: 1
    Indicates whether the task start date was updated to a later date and is beyond the threshold that was set during implementation. If true, then the start date change is beyond the threshold.
  • Title: Start Past Due Indicator
    Maximum Length: 1
    Indicates whether the project task started on time. If true, then the task didn't start on time.
  • The unique identifier of the project task.
  • Title: Task Name
    Read Only: true
    Maximum Length: 255
    The name of the project task.
Nested Schema : projectInsights-TeamAllocations-item-response
Type: object
Show Source
Links
Assignments
Parameters:
  • ProjectId: $request.path.ProjectId
The Assignments resource is used to view details for the assignments ending soon and reserved assignments for a project.
MissingTimeCards
Parameters:
  • ProjectId: $request.path.ProjectId
The Missing Time Card resource is used to view the details of the missing or incomplete time card count for a project. It includes the resources and their expected hours for time cards that are missing or partially reported.
PendingInvoices
Parameters:
  • ProjectId: $request.path.ProjectId
The Pending Invoices resource is used to view the details of the invoices pending approval count for a project.
TaskExceptions
Parameters:
  • ProjectId: $request.path.ProjectId
The Task Exceptions resource is used to view the details of the task exceptions, milestones past due, and milestones due soon counts for a project. It includes what qualified the task or milestone as an exception.
TeamAllocations
Parameters:
  • ProjectId: $request.path.ProjectId
The Team Allocations resource is used to view the over and under allocated labor resource details for a project. It includes the weekly assignment, allocation, and variance hours per team member for the twelve weeks that start with the current week.
Back to Top

Examples

The following example shows how to get insights for a project by submitting a GET request on the REST resource using cURL.

curl --user ppm_cloud_user https://your_organization.com:port/fscmRestApi/resources/11.13.18.05/projectInsights/300100061807448

Response Body Example

The following shows an example of the response body in JSON format of all project templates.

{
      "ProjectId": 300100061807448,
      "ProjectName": "Fox Stores",
      "ActualPercentComplete": 42,
      "ExpectedPercentComplete": 45,
      "PlannedEffort": 1600,
      "TaskExceptionsCount": 4,
      "WeekOneToFourUnderAllocated": 1,
      "WeekFiveToEightUnderAllocated": 0,
      "WeekNineToTwelveUnderAllocated": 0,
      "WeekOneToFourOverAllocated": 1,
      "WeekFiveToEightOverAllocated": 0,
      "WeekNineToTwelveOverAllocated": 0,
      "AssignmentsEndingSoon": 1,
      "AssignmentsReserved": 2,
      "MilestonesAtRisk": 0,
      "MilestonesDueSoon": 1,
      "MilestonesPastDue": 0,
      "MissingTimeCardsFiveWeeksOld": null,
      "MissingTimeCardsFourWeeksOld": null,
      "MissingTimeCardsThreeWeeksOld": 1,
      "MissingTimeCardsTwoWeeksOld": 0,
      "MissingTimeCardsOneWeekOld": 1,
      "CurrentBaselineBudget": 2560000,
      "CurrencyCode": "USD",
      "BudgetSpentAmount": 453000,
      "BudgetToDateAmount": 471000,
      "ActualUnplannedCost": 20800,
      "ActualPlannedCost": 431200,
      "CommittedCost": 504000,
      "InvoicesAwaitingApproval": 1,
      "PerformanceHealthStatusCode": "INDICATOR_4",
      "PerformanceHealthStatus": "On track",
      "CreatedBy": "Lisa.Williams",
      "CreationDate": "2019-09-07T05:42:39+00:00",
      "LastUpdateDate": "2019-10-28T09:14:32+00:00",
      "LastUpdatedBy": "Lisa.Williams",
      "links": [
 ....
 ]
}
Back to Top