Create a currency

post

/fscmRestApi/resources/11.13.18.05/publicSectorCurrencies

Request

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: Currency Code
    Maximum Length: 3
    Currency code identifier.
  • Maximum Length: 3
    The three-digit code for the currency according to the ISO 4217 standard.
  • Title: Decimal Position
    The number of decimal positions used for amounts in the related currency.
  • Maximum Length: 1
    Default Value: false
    Indicates whether the seed data is logically deleted. If the value is Y, the seed data has been deleted. The default value is N.
  • Title: Description
    Maximum Length: 50
    The description of the currency.
  • Default Value: 0
    Indicates the level at which the seed data is locked. The value 0 indicates customer data. The value 1 means the fields are read-only. The value 2 means that only some fields can be updated.
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 : publicSectorCurrencies-item-response
Type: object
Show Source
Back to Top