Update one matrix type

patch

/fscmRestApi/resources/11.13.18.05/pricingMatrixTypes/{pricingMatrixTypesUniqID}

Request

Path Parameters
  • This is the hash key of the attributes which make up the composite key for the Pricing Matrix Types resource and used to uniquely identify an instance of Pricing Matrix Types. The client should not generate the hash key value. Instead, the client should query on the Pricing Matrix Types collection resource in order to navigate to a specific instance of Pricing Matrix Types 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
  • Title: Active
    Maximum Length: 30
    Default Value: N
    Contains one of the following values. Y: pricing matrix type is active. N: pricing matrix type is inactive. This attribute doesn't have a default value.
  • Title: Allow Multiple Matrixes
    Maximum Length: 30
    Default Value: N
    Contains one of the following values. Y: pricing matrix type allows for multiple matrixes. N: pricing matrix type doesn't allow for multiple matrixes. This attribute doesn't have a default value.
  • Title: Description
    Maximum Length: 1000
    Description of the matrix type.
  • Title: Dynamic Matrix Class
    Value that uniquely identifies the matrix class for the matrix type.
  • Title: Name
    Maximum Length: 80
    Name of the pricing matrix type.
  • Value that uniquely identifies the matrix.
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 : pricingMatrixTypes-item-response
Type: object
Show Source
Back to Top