Update a payment plan role

patch

/fscmRestApi/resources/11.13.18.05/incentiveCompensationPaymentPlans/{PaymentPlanId}/child/PaymentPlanRoles/{RolePaymentPlanId}

Request

Path Parameters
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.
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
  • Title: End Date
    The date when the role assignment for a payment plan becomes inactive. The acceptable format is yyyy-mm-dd. The date must be equal to or earlier than the payment plan end date.
  • The unique identifier of the payment plan.
  • The unique identifier off the payment plan role.
  • Title: Start Date
    The date when the role assignment for a payment plan becomes active. The acceptable format is yyyy-mm-dd. The date must be equal to or later than the payment plan start date.
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 : incentiveCompensationPaymentPlans-PaymentPlanRoles-item-response
Type: object
Show Source
Back to Top