1. REST API for Oracle Fusion Cloud Project Management
  2. Tasks
  3. Projects
  4. Project Team Members

Get a project team member

get

/fscmRestApi/resources/11.13.18.05/projects/{ProjectId}/child/ProjectTeamMembers/{TeamMemberId}

Request

Path Parameters
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 : projects-ProjectTeamMembers-item-response
Type: object
Show Source
  • Title: Assignment Type
    Indicates if a request is for a billable or a nonbillable assignment. Examples are BILLABLE, NON-BILLABLE, or leave blank.
  • Title: Assignment Type Code
    Code to indicate if a request is for a billable or a nonbillable assignment. Examples are BILLABLE, NON-BILLABLE, or leave blank.
  • Title: Billable Percent
    Indicates the percentage of assignment time that is billable for an assignment that is defined as billable assignment. For a non-billable assignment, the value is ignored. Valid values are positive integers between 0 and 100.
  • Title: Billable Percent Reason
    Indicates the reason that the billable percentage of the project resource assignment is less than 100%. For a non-billable assignment, the value is ignored.
  • Title: Billable Percent Reason Code
    Code that indicates the reason that the billable percentage of the project resource assignment is less than 100%. For a non-billable assignment, the value is ignored.
  • Title: Team Member End Date
    Date on which the assignment of the project team member to the project is scheduled to end.
  • Links
  • Title: Team Member Email
    Maximum Length: 240
    Email of the person assigned as a team member to the project.
  • Title: Person ID
    Unique identifier of the person assigned as a team member to the project.
  • Title: Team Member Name
    Maximum Length: 240
    Name of the person assigned as a team member to the project.
  • Title: Project ID
    Unique identifier of the project.
  • Title: Project Role
    Maximum Length: 240
    A classification of the relationship that an employee has to a project. You use project roles to define an employee's level of access to project information. Examples are Project Manager, Project Accountant, and Technical Lead.
  • Title: Resource Allocation Percentage
    Percentage of time for which a resource is assigned to the project. The default value is 100.
  • Title: Resource Assignment Effort in Hours
    Number of hours for which a resource is assigned to the project.
  • Title: Resource Planning Bill Rate
    Bill Rate of the resource assignment for the planning purpose. If no value is specified, Bill Rate of the resource defined in Project Enterprise Resource is used if it is available in the project currency.
  • Title: Resource Planning Cost Rate
    Cost Rate of the resource assignment for the planning purpose. If no value is specified, Cost Rate of the resource defined in Project Enterprise Resource is used if it is available in the project currency.
  • Title: Team Member Start Date
    Date from which the assignment of the team member to the project is scheduled to begin.
  • Title: Team Member ID
    Read Only: true
    Unique identifier of the team member assigned to the project.
  • Title: Track Time
    Maximum Length: 255
    Indicates whether time cards are expected from internal team members. Valid values are true and false. The default value is false. Information about missing time cards is displayed on the project manager dashboard.
Back to Top

Examples

The following example shows how to get a project team member 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.0.0/projects/300100072711280/child/ProjectTeamMembers/300100072711289

Example of Response Body

The following example shows the contents of the response body in JSON format, including the details of the team member with team member ID 300100072711289 assigned to the project with project ID 300100072711280.

{
  "FinishDate": null
  "PersonEmail": "prj_wf_in_grp@oracle.com"
  "PersonName": "Abraham Mason"
  "ProjectId": 300100072711280
  "ProjectRole": "Project Manager"
  "StartDate": "2015-01-01"
  "TeamMemberId": 300100072711289
  -"links": [3]
  -0:  {
    "rel": "self"
    ...
       }
}
Back to Top