Update a personal payment method

patch

/hcmRestApi/resources/11.13.18.05/personalPaymentMethods/{personalPaymentMethodsUniqID}

Request

Path Parameters
  • This is the hash key of the attributes which make up the composite key for the Personal Payment Methods resource and used to uniquely identify an instance of Personal Payment Methods. The client should not generate the hash key value. Instead, the client should query on the Personal Payment Methods collection resource in order to navigate to a specific instance of Personal Payment Methods to get the hash key.
Header Parameters
  • This header accepts a string value. The string is a semi-colon separated list of =. It is used to perform effective date range operations. The accepted parameters are RangeMode, RangeSpan, RangeStartDate, RangeEndDate, RangeStartSequence and RangeEndSequence. The parameter values are always strings. The possible values for RangeMode are SET_LOGICAL_START, SET_LOGICAL_END, END_DATE, SET_EFFECTIVE_START, SET_EFFECTIVE_END, REPLACE_CORRECTION, REPLACE_UPDATE, RECONCILE_CORRECTION, CORRECTION, RECONCILE_UPDATE, UPDATE, ZAP and DELETE_CHANGES. The possible values for RangeSpan are PHYSICAL_ROW_END_DATE and LOGICAL_ROW_END_DATE. The values for RangeStartDate and RangeEndDate have to be a string representation of a date in yyyy-MM-dd format. The value for RangeStartSequence and RangeEndSequence must be strings such that when parsed they yield positive integers.
  • 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
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 : personalPaymentMethods-item-response
Type: object
Show Source
Back to Top

Examples

This example shows how to update a payment method by submitting a PATCH request on the REST resource.

curl -i -u "<username>:<password>" -H "Effective-Of=RangeMode=UPDATE;RangeStartDate=2016-01-01" -X PATCH -d <payload> https://<host>:<port>/hcmRestApi/resources/11.13.18.05/personalPaymentMethods/<Generated Unique Id>

Example of Payload

The following is an example of the request payload.

 {	
	"PersonalPaymentMethodId": 300100181650365,
	"Name": "Cheque Payment Method",
	"EffectiveStartDate": "2010-10-12",
	"EffectiveEndDate": "4712-12-31",
	"PayrollRelationshipId": 300100006014818,
	"Percentage": 29  
} 

Example of Response Header

The following is an example of the response header.

HTTP/1.1 200 OK                     
Content-Type : application/vnd.oracle.adf.resourceitem+json

Example of Response Body

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

{
  "PersonalPaymentMethodId" : 300100181650365,
  "Name" : "Cheque Payment Method",
  "EffectiveStartDate" : "2016-01-01",
  "EffectiveEndDate" : "4712-12-31",
  "OrgPaymentMethodId" : 300100005800591,
  "BankAccountId" : null,
  "PaymentAmountType" : "P",
  "Amount" : null,
  "Percentage" : 29,
  "Priority" : 9,
  "PayrollRelationshipId" : 300100006014818,
  "PartyId" : 300100006001613,
  "PersonNumber" : "300100006014805",
  "links" : [ ]
}

This example shows how to correct a payment method by submitting a PATCH request on the REST resource.

curl -i -u "<username>:<password>" -H "Content-Type: application/vnd.oracle.adf.resourceitem+json" -H "Effective-Of:RangeMode=CORRECTION" -X PATCH -d " <payload> https://<host>:<port>/hcmRestApi/resources/11.13.18.05/personalPaymentMethods/<Generated PPM Id>

Example of Payload

The following is an example of the request payload.

{  
  "PersonalPaymentMethodId": 300100181650365,
  "Name": "Cheque Payment Method",
  "EffectiveStartDate": "2010-10-12",
  "EffectiveEndDate": "4712-12-31",
  "Percentage": 29,
  "PayrollRelationshipId": 300100006014818
}

Example of Response Header

The following is an example of the response header.

HTTP/1.1 200 OK                     
Content-Type : application/vnd.oracle.adf.resourceitem+json
Back to Top