Update descriptive flexfields for an invoice installment

patch

/fscmRestApi/resources/11.13.18.05/invoices/{invoicesUniqID}/child/invoiceInstallments/{invoiceInstallmentsUniqID}/child/invoiceInstallmentDff/{invoiceInstallmentDffUniqID}

Request

Path Parameters
  • This is the hash key of the attributes which make up the composite key--- InvoiceId and InstallmentNumber ---for the Invoice Installments Descriptive Flexfields resource and used to uniquely identify an instance of Invoice Installments Descriptive Flexfields. The client should not generate the hash key value. Instead, the client should query on the Invoice Installments Descriptive Flexfields collection resource with a filter on the primary key values in order to navigate to a specific instance of Invoice Installments Descriptive Flexfields.

    For example: invoiceInstallmentDff?q=InvoiceId=<value1>;InstallmentNumber=<value2>
  • This is the hash key of the attributes which make up the composite key for the Invoice Installments resource and used to uniquely identify an instance of Invoice Installments. The client should not generate the hash key value. Instead, the client should query on the Invoice Installments collection resource in order to navigate to a specific instance of Invoice Installments to get the hash key.
  • This is the hash key of the attributes which make up the composite key for the Invoices resource and used to uniquely identify an instance of Invoices. The client should not generate the hash key value. Instead, the client should query on the Invoices collection resource in order to navigate to a specific instance of Invoices 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.
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 : invoices-invoiceInstallments-invoiceInstallmentDff-item-response
Type: object
Show Source
Back to Top