Create a participant role

post

/fscmRestApi/resources/11.13.18.05/incentiveCompensationParticipants/{incentiveCompensationParticipantsUniqID}/child/ParticipantRoles

Request

Path Parameters
  • This is the hash key of the attributes which make up the composite key for the Participants resource and used to uniquely identify an instance of Participants. The client should not generate the hash key value. Instead, the client should query on the Participants collection resource in order to navigate to a specific instance of Participants to get the hash key.
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.
  • Contains one of the following values: true or false. If true, the server performs an Upsert operation instead of a Create operation. During an Upsert operation, the server attempts to find an existing resource that matches the payload. If a match is found, the server updates the existing resource instead of creating a new one. If not found or false (default), the server performs a Create operation. Note that the Upsert operation isn't supported for date-effective REST resources.
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
  • Title: Role End Date
    The date when the role assignment ends for that participant. The format is yyyy-mm-dd.
  • Title: Participant Identifier
    The unique identifier of the participant record.
  • Title: Participant Role ID
    The unique identifier for the participant role.
  • Title: Preserve Assignment
    Indicates whether to keep the role assignment and to prevent update by the automatic the role assignment process. Possible values include TRUE to prevent update. In cases where the Role is added manually to participants, the Preserve Assignment is set as True, and FALSE to allow update.
  • Title: Role ID
    The unique identifier for a role assigned to a participant record.
  • Title: Role Start Date
    The date when the role assignment starts for a participant. This is a mandatory field. The format is yyyy-mm-dd.
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 : incentiveCompensationParticipants-ParticipantRoles-item-response
Type: object
Show Source
  • Title: Access Type
    Read Only: true
    Maximum Length: 30
    Default Value: INDIVIDUAL
    The lookup code that represents the access type, such as manager or individual. Possible values include INDIVIDUAL which specifies that the participant access is individual, and MANAGER which specifies that the participant access is manager. The default value is INDIVIDUAL. A list of acceptable values is defined in the lookup CN_ACCESS_TYPE. Review and update the value for this attribute using the Setup and Maintenance, Manage Incentive Compensation Lookups task.
  • Title: Created By
    Read Only: true
    Maximum Length: 64
    The user who created the record.
  • Title: Creation Date
    Read Only: true
    The date and time when the record was created.
  • Title: Role End Date
    The date when the role assignment ends for that participant. The format is yyyy-mm-dd.
  • Title: Last Updated Date
    Read Only: true
    The date and time when the record was last updated.
  • Title: Last Updated By
    Read Only: true
    Maximum Length: 64
    The user who last updated the record.
  • Title: Last Update Login
    Read Only: true
    Maximum Length: 32
    The session login of the user who last updated the record.
  • Links
  • Title: Participant Identifier
    The unique identifier of the participant record.
  • Title: Participant Role ID
    The unique identifier for the participant role.
  • Title: Preserve Assignment
    Indicates whether to keep the role assignment and to prevent update by the automatic the role assignment process. Possible values include TRUE to prevent update. In cases where the Role is added manually to participants, the Preserve Assignment is set as True, and FALSE to allow update.
  • Title: Role ID
    The unique identifier for a role assigned to a participant record.
  • Title: Role Name
    Read Only: true
    Maximum Length: 60
    The name of the role.
  • Title: Role Start Date
    The date when the role assignment starts for a participant. This is a mandatory field. The format is yyyy-mm-dd.
Back to Top

Examples

The following example shows how to create a participant role by submitting a POST request on the REST resource using cURL.

cURL Command

curl -u <username:password> \ -X POST -d @example_request_payload.json https://servername.fa.us2.oraclecloud.com/fscmRestApi/resources/11.13.18.05/incentiveCompensationParticipants/999666333000584/child/ParticipantRoles

Example of Request Body

The following example shows the contents of the request body in JSON format.

{
"StartDateActive": "2017-02-01",
  "RoleId": 300100089821754,
  "EndDateActive": "2017-12-31"
}

Example of Response Body

The following example shows the contents of the response body in JSON format.

{
  "ParticipantRoleId": 300100089854605,
  "CreatedBy": "OIC_MGR_OPERATIONS",
  "CreationDate": "2017-05-16T07:34:28-07:00",
  "EndDateActive": "2017-12-31",
  "LastUpdateDate": "2017-05-16T07:34:28.024-07:00",
  "LastUpdateLogin": "4FA525997C5C6DC5E0532DD6F00A3E7B",
  "LastUpdatedBy": "OIC_MGR_OPERATIONS",
  "ParticipantId": 999666333000584,
  "RoleId": 300100089821754,
  "RoleName": "US Sales Representative",
  "StartDateActive": "2017-02-01",
  "AccessType": false,
  "PreserveRoleAssignmentFlag": true,
  "links": [
    ...
  ]
}
Back to Top