Get one locator

get

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

Request

Path Parameters
  • Value that uniquely identifies the locator.
  • Value that uniquely identifies the item locator.
  • 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>
Query Parameters
  • This parameter specifies dependencies which are fields that are set before and rolled back after generating the response. Generally they are used to preview the effects of an attribute change. The fields specified in this parameter are always set in the resource instance in question. When a child resource collection is requested and the parameter is set, the fields will be set in the parent resource instance before generating the resource collection payload. The value of this query parameter is a set of dependency fields. Example: dependency=ProductId=2

    Format: <attr1>=<val1>,<attr2>=<value2>
  • When this parameter is provided, the specified children are included in the resource payload (instead of just a link). The value of this query parameter is "all" or "". More than one child can be specified using comma as a separator. Example: ?expand=Employees,Localizations. Nested children can also be provided following the format "Child.NestedChild" (Example: ?expand=Employees.Managers). If a nested child is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?expand=Employees.Managers" is the same as "?expand=Employees,Employees.Managers" (which will expand Employees and Managers).
  • This parameter filters the resource fields. Only the specified fields are returned, which means that if no fields are specified, no fields are returned (useful to get only the links). If an indirect child resource is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?fields=Employees.Managers:Empname" is the same as "?fields=;Employees:;Employees.Managers:Empname" (which will only return the "Empname" field for Managers). the value of this query parameter is a list of resource fields. The attribute can be a direct (Example: Employees) or indirect (Example: Employees.Managers) child. It cannot be combined with expand query parameter. If both are provided, only fields will be considered.

    Format: ?fields=Attribute1,Attribute2

    Format for fields in child resource: ?fields=Accessor1:Attribute1,Attribute2
  • This parameter can be used to show only certain links while accessing a singular resource or a resource collection. The parameter value format is a comma-separated list of : <link_relation>

    Example:
    self,canonical
  • The resource item payload will be filtered in order to contain only data (no links section, for example).
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.

There's no request body for this operation.

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
  • 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 isn't a default value for this attribute.
  • Read Only: true
    Date when the user created the item locator record.
  • 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.
  • Value that uniquely identifies the Item.
  • Title: Item Description
    Read Only: true
    Maximum Length: 240
    Value that identifies the description of the item associated with a locator in a subinventory.
  • Maximum Length: 255
    Name of the inventory item.
  • Title: Primary Image URL
    Read Only: true
    Maximum Length: 4000
    Value that provides a reference to the image of the item for which the count sequence is generated.
  • Links
  • Title: Description
    Read Only: true
    Maximum Length: 50
    Description of the locator that references the locator item.
  • Title: Locator
    Value that uniquely identifies the locator.
  • Read Only: true
    Value that uniquely identifies the item locator.
  • Maximum Length: 255
    Name of the locator that references the locator item.
  • Maximum Length: 255
    Abbreviation that identifies the organization that references the item locator.
  • Value that uniquely identifies the inventory organization.
  • 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.
  • Maximum Length: 10
    Abbreviation that identifies the subinventory.
Back to Top