1. REST API for Oracle Fusion Cloud SCM
  2. Tasks
  3. Inventory Management
  4. List of Values
  5. Active Locators

Get all locators

get

/fscmRestApi/resources/11.13.18.05/activeLocators

Request

Query Parameters
  • 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
  • Used as a predefined finder to search the collection.

    Format: ?finder=<finderName>;<variableName>=<variableValue>,<variableName2>=<variableValue2>

    The following are the available finder names and corresponding finder variables:

    • PrimaryKey: Finds active locators according to the inventory location identifier.
      Finder Variables:
      • InventoryLocationId; integer; Value that uniquely identifies the inventory location.
    • filterByOpenCounts: Finds the cycle count definitions that have open count sequences.
      Finder Variables:
      • param_CycleCountHeaderId; integer; Finds the cycle count definitions that have open count sequences by cycle count headers.
      • param_Subinventory; string; Finds the cycle count definitions that have open count sequences by subinventory.
    • findByOrganizationSubinventory: Finds the locator.
      Finder Variables:
      • bindItem; string; Name of the inventory item.
      • bindOrgId; integer; Value that uniquely identifies the organization.
      • bindSubinventory; string; Value that uniquely identifies the subinventory.
    • findItemRestrictedLocators: Finds the locator based on the restricted locators setup defined at the item organization.
      Finder Variables:
      • bindItem; string; Name of the inventory item.
    • findOnhand: Finds on-hand inventory.
      Finder Variables:
      • bindLocatorId; integer; Value that uniquely identifies the locator.
      • bindOrgId; integer; Value that uniquely identifies the organization.
      • bindSubinventory; string; Name of the subinventory.
    • findPendingTransactions: Finds pending inventory transactions.
      Finder Variables:
      • bindLocatorId; integer; Value that uniquely identifies the locator.
      • bindOrgId; integer; Value that uniquely identifies the organization.
      • bindSubinventory; string; Name of the subinventory.
    • findPendingTransferTransactions: Finds pending inventory transfer transactions.
      Finder Variables:
      • bindLocatorId; integer; Value that uniquely identifies the locator.
      • bindOrgId; integer; Value that uniquely identifies the organization.
      • bindSubinventory; string; Name of the subinventory.
    • findRestrictedLocators: Finds inventory locators that the warehouse can use to fulfill the item and meet the requirements of the transaction type.
      Finder Variables:
      • bindItemId; integer; Value that uniquely identifies the item.
      • bindTransactionTypeId; integer; Value that uniquely identifies the transaction type.
    • findTransactableLocators: Name of the transactable locator.
      Finder Variables:
      • bindItemId; integer; Value that uniquely identifies the item.
      • bindTransactionTypeId; integer; Value that uniquely identifies the transactable locator.
  • This parameter restricts the number of resources returned inside the resource collection. If the limit exceeds the resource count then the framework will only return the available resources.
  • 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
  • Used to define the starting position of the resource collection. If offset exceeds the resource count then no resources are returned. Default value is 0.
  • The resource item payload will be filtered in order to contain only data (no links section, for example).
  • This parameter orders a resource collection based on the specified fields. The parameter value is a comma-separated string of attribute names, each optionally followed by a colon and "asc" or "desc". Specify "asc" for ascending and "desc" for descending. The default value is "asc". For example, ?orderBy=field1:asc,field2:desc
  • This query parameter defines the where clause. The resource collection will be queried using the provided expressions. The value of this query parameter is one or more expressions. Example: ?q=Deptno>=10 and <= 30;Loc!=NY

    Format: ?q=expression1;expression2

    You can use these queryable attributes to filter this collection resource using the q query parameter:
    • Description; string; Description of the locator.
    • DisableDate; string; Date when the warehouse disabled the locator.
    • InventoryLocationId; integer; Value that uniquely identifies the inventory locator.
    • InventoryLocationType; string; Value that identifies the type of location. Valid values include 1,2,3, and so on. A list of accepted values is defined in the lookup type INV_LOCATOR_TYPES. There is no default value for this attribute.
    • Locator; string; Physical area in the subinventory, such as a row, aisle, bin, or shelf, that stores the item.
    • LocatorType; string; Name of the type of locator. Valid values include Dock door, Staging lane, and so on. A list of accepted values is defined in the lookup type INV_LOCATOR_TYPES. There is no default value for this attribute.
    • OrganizationCode; string; Abbreviation that identifies the organization.
    • OrganizationId; integer; Value that uniquely identifies the organization.
    • OrganizationName; string; Name of the organization.
    • PickingOrder; number; Sequence to use when picking the item.
    • StatusCode; string; Abbreviation that identifies the status.
    • StatusId; integer; Value that uniquely identifies the status.
    • SubinventoryCode; string; Name of the subinventory.
    • SubinventoryId; integer; Value that uniquely identifies the subinventory.
  • The resource collection representation will include the "estimated row count" when "?totalResults=true", otherwise the count is not included. The default value is "false".
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 : activeLocators
Type: object
Show Source
Nested Schema : Items
Type: array
Title: Items
The items in the collection.
Show Source
Nested Schema : activeLocators-item-response
Type: object
Show Source
Back to Top

Examples

This example describes how to get all active locators.

Example cURL Command

Use the following cURL command to submit a request on the REST resource. This example gets all active locators that allow subinventory transfer:

curl -u username:password "https://servername/fscmRestApi/resources/version/activeLocators?onlyData=true&finder=findRestrictedLocators;bindTransactionTypeId=2"

Example Response Body

The following example includes the contents of the response body in JSON format:

{
  "items" : [ {
    "InventoryLocationId" : 536,
    "Locator" : "CM.43.669",
    "OrganizationId" : 605,
    "OrganizationName" : "San Diego Manufacturing",
    "OrganizationCode" : "P3",
    "SubinventoryId" : 4801,
    "SubinventoryCode" : "Stores",
    "Description" : "CM43669",
    "DisableDate" : null,
    "InventoryLocationType" : "3",
    "LocatorType" : "Storage location",
    "PickingOrder" : null,
    "StatusId" : 1,
    "StatusCode" : "Active"
  } ],
  "count" : 1,
  "hasMore" : false,
  "limit" : 25,
  "offset" : 0,
  "links" : [ {
    "rel" : "self",
    "href" : "https://servername/fscmRestApi/resources/version/activeLocators",
    "name" : "activeLocators",
    "kind" : "collection"
  } ]
}
Back to Top