Update one plan advanced option

patch

/fscmRestApi/resources/11.13.18.05/planOptions/{PlanId}/child/PlanAdvancedOptions/{ParameterId}

Request

Path Parameters
  • The value of this parameter could be a hash of the key that is used to uniquely identify the resource item. The client should not generate the hash key value. Instead, the client should query on the collection resource with a filter to navigate to a specific resource item. For example: products?q=InventoryItemId=
  • The value of this parameter could be a hash of the key that is used to uniquely identify the resource item. The client should not generate the hash key value. Instead, the client should query on the collection resource with a filter to navigate to a specific resource item. For example: products?q=InventoryItemId=
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
  • Determines the maximum number of groups into which all planned items must be divided by the solution engine. The calculations the engine performs plan supplies for the items in each group.
  • Maximum Length: 512
    Determines the settings for each thread after the items in a supply chain are split into threads to obtain an optimized solution.
  • Limits the numeric error in the solution algorithm using an industry standard called Markowitz Tolerance. Larger values typically reduce the error introduced in the algorithm.
  • Specifies the number of groups per thread to be used when plan decomposition is enabled in a constrained plan.
  • Determines the number of threads into which the items in a plan are split. Items across threads can't be part of the same supply chain.
  • Specifies the number of threads into which items in a supply chain need to be divided. The engine calculations then assign an algorithm to each thread, and the thread with the fastest solution is selected.
  • Plan version number.
  • Unique identifier of the parameter.
  • Uniquely identifies the plan.
  • Optimizes the size of the problem before the start of the solution process. Larger values typically mean greater problem complexity.
  • Determines the extent to which the solution model is scaled. Larger values typically reduce solution times but may also lead to larger constraint violations.
  • Specifies the tolerance to which a solution should conform using an industry standard called Simplex Feasibility Tolerance. Tightening this tolerance can produce smaller constraint violations but may also lead to more iterations in the search for the solution.
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 : planOptions-PlanAdvancedOptions-item-response
Type: object
Show Source
  • Read Only: true
    Maximum Length: 64
    User who created the plan advanced options.
  • Read Only: true
    Date when the plan advanced options was originally created.
  • Read Only: true
    Date when the user most recently updated the plan advanced options.
  • Read Only: true
    Maximum Length: 64
    User who performed the most recent update on the plan advanced options.
  • Read Only: true
    Maximum Length: 32
    Last time the user logged into the system.
  • Links
  • Determines the maximum number of groups into which all planned items must be divided by the solution engine. The calculations the engine performs plan supplies for the items in each group.
  • Maximum Length: 512
    Determines the settings for each thread after the items in a supply chain are split into threads to obtain an optimized solution.
  • Limits the numeric error in the solution algorithm using an industry standard called Markowitz Tolerance. Larger values typically reduce the error introduced in the algorithm.
  • Specifies the number of groups per thread to be used when plan decomposition is enabled in a constrained plan.
  • Determines the number of threads into which the items in a plan are split. Items across threads can't be part of the same supply chain.
  • Specifies the number of threads into which items in a supply chain need to be divided. The engine calculations then assign an algorithm to each thread, and the thread with the fastest solution is selected.
  • Plan version number.
  • Unique identifier of the parameter.
  • Uniquely identifies the plan.
  • Optimizes the size of the problem before the start of the solution process. Larger values typically mean greater problem complexity.
  • Determines the extent to which the solution model is scaled. Larger values typically reduce solution times but may also lead to larger constraint violations.
  • Specifies the tolerance to which a solution should conform using an industry standard called Simplex Feasibility Tolerance. Tightening this tolerance can produce smaller constraint violations but may also lead to more iterations in the search for the solution.
Back to Top