Update one locator

patch

/fscmRestApi/resources/11.13.18.05/subinventories/{subinventoriesUniqID}/child/locators/{InventoryLocationId}/child/itemLocators/{LocatorItemId}

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=
  • This is the hash key of the attributes which make up the composite key--- OrganizationId and SecondaryInventoryName ---for the Subinventories resource and used to uniquely identify an instance of Subinventories. The client should not generate the hash key value. Instead, the client should query on the Subinventories collection resource with a filter on the primary key values in order to navigate to a specific instance of Subinventories.

    For example: subinventories?q=OrganizationId=<value1>;SecondaryInventoryName=<value2>
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: Count Required
    Maximum Length: 1
    Contains one of the following values. 1. The application requires counting during periodic-automatic replenishment for the item in the locator. 2. The application doesn't require this counting. There's isn't a default value for this attribute.
  • Maximum Length: 255
    The type of periodic automatic replenishment. A list of accepted values is defined in the lookup type INV_DEFAULT_REPLEN_COUNT_TYPE. The default value is Order par.
  • Title: Replenishment Count Type
    Maximum Length: 30
    Abbreviation that identifies the type of periodic automatic replenishment. A list of accepted values is defined in the lookup type INV_DEFAULT_REPLEN_COUNT_TYPE. The default value is 4.
  • Maximum Length: 1
    Contains one of the following values: true or false. If true, then the full LPN transaction is enforced for the item in the locator. If false, then the full LPN transaction isn't enforced.
  • Date when the item was last replenished for a locator during par counting.
  • Indicates the number of bins used during PAR replenishment.
  • Title: PAR Level
    Level that the application uses during periodic-automatic replenishment for the item locator.
  • Title: PAR Maximum Quantity
    Maximum quantity to use during periodic-automatic replenishment.
  • Maximum Length: 3
    Code that identifies the unit of measure to use for quantities during periodic-automatic replenishment.
  • Title: PAR Level UOM
    Unit of measure to use for quantities during periodic-automatic replenishment.
  • Title: Count Tolerance Percentage
    Count tolerance percent to use before the application doesn't allow the count. This tolerance prevents data entry mistakes when counting, and prevents ordering too much quantity for the replenishment request.
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 : subinventories-locators-itemLocators-item-response
Type: object
Show Source
Back to Top