Update a project numbering configuration detail

patch

/fscmRestApi/resources/11.13.18.05/projectNumberingConfigurations/{ConfigurationId}/child/ProjectNumberingConfigurationDetails/{ConfigurationDetailId}

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: Determinant ID
    Unique identifier of the entity for which project numbering is set up.
  • Title: Determinant
    Name of the entity for which project numbering is set up.
  • Title: Method
    Maximum Length: 80
    Name of the project numbering method. Valid values are Automatic and Manual.
  • Title: Method Code
    Maximum Length: 25
    Code of the project numbering method. Valid values are AUTOMATIC and MANUAL
  • Title: Next Number
    Next number to be generated for an automatic project numbering configuration.
  • Title: Prefix
    Maximum Length: 7
    Prefix for the project numbering.
  • Title: Type
    Maximum Length: 80
    Name of the manual project numbering type. Valid values are Alphanumeric and Numeric.
  • Title: Type Code
    Maximum Length: 25
    Code of the manual project numbering type. Valid values are ALPHANUMERIC and NUMERIC.
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 : projectNumberingConfigurations-ProjectNumberingConfigurationDetails-item-response
Type: object
Show Source
Back to Top