Get one inventory

get

/fscmRestApi/resources/11.13.18.05/physicalInventories/{physicalInventoriesUniqID}

Request

Path Parameters
  • This is the hash key of the attributes which make up the composite key--- OrganizationId and PhysicalInventoryId ---for the Physical Inventories resource and used to uniquely identify an instance of Physical Inventories. The client should not generate the hash key value. Instead, the client should query on the Physical Inventories collection resource with a filter on the primary key values in order to navigate to a specific instance of Physical Inventories.

    For example: physicalInventories?q=OrganizationId=<value1>;PhysicalInventoryId=<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 : physicalInventories-item-response
Type: object
Show Source
  • Value that indicates whether all or specific subinventories must be included in the physical inventory. A list of accepted values is defined in the lookup type INV_SUBINVENTORIES_FLAG. The default value is All.
  • Title: Subinventories to Count
    Maximum Length: 30
    Default Value: 1
    Value that indicates all or specific subinventories included in the physical inventory. A list of accepted values is defined in the lookup type INV_SUBINVENTORIES_FLAG. The default value is 1.
  • Value that indicates if the dynamic tag creation is permitted in the physical inventory. Contains one of the following values: Yes or No. If Yes, then dynamic tag creation is permitted. If No, then dynamic tag creation is not permitted. This attribute does not have a default value.
  • Title: Dynamic tags allowed
    Maximum Length: 30
    Value that indicates if the dynamic tag creation is permitted in the physical Inventory. Contains one of the following values: 1 or 2. If 1, then dynamic tag creation is permitted. If 2, then dynamic tag creation is not permitted. This attribute does not have a default value.
  • Value that indicates the level of approval required to post the physical inventory adjustments. A list of accepted values is defined in the lookup type INV_REQ_APPROVALS. This attribute does not have a default value.
  • Title: Approval Type
    Maximum Length: 30
    Value that indicates the level of approval required to post physical inventory adjustments. A list of accepted values is defined in the lookup type INV_REQ_APPROVALS. This attribute does not have a default value.
  • Title: Negative Quantity Tolerance Percentage
    Percent below the on-hand quantity that the adjustment transaction can vary. If the adjustment transaction exceeds the percent, then the adjustment transaction requires approval. For example, if Negative Quantity Tolerance Percentage is 10, and if the adjustment transaction requires an 11% negative adjustment to on-hand quantity, then the transaction requires approval.
  • Title: Positive Quantity Tolerance Percentage
    Percent above the on-hand quantity that the adjustment transaction can vary. If the adjustment transaction exceeds the percent, then the adjustment transaction requires approval. For example, if Positive Quantity Tolerance Percentage is 10, and if the adjustment transaction requires an 11% positive adjustment to on-hand quantity, then the transaction requires approval.
  • Title: Negative Adjustment Value Tolerance
    Total value of a physical inventory adjustment that is less than the current value of the item. The user specifies this limit.
  • Title: Positive Adjustment Value Tolerance
    Total value of a physical inventory adjustment that is greater than the current value of the item. The user specifies this limit.
  • Title: Description
    Maximum Length: 50
    Description of the physical inventory.
  • Value that indicates if the items with negative on-hand balances are excluded from physical counts. Contains one of the following values: Yes or No. If Yes, then items with negative on-hand balances are excluded from physical count. If No, then items with negative on-hand balances are not excluded from physical count. This attribute does not have a default value.
  • Title: Exclude negative balances
    Maximum Length: 30
    Value that indicates that items with negative on-hand balances are excluded from physical counts. Contains one of the following values: Y or N. If Y, then items with negative on-hand balances are excluded from physical count. If N, then items with negative on-hand balances are not excluded from physical count. This attribute does not have a default value.
  • Value that indicates that items with zero on-hand balances are excluded from physical counts. Contains one of the following values: Yes or No. If Yes, then items with negative on-hand balances are excluded from physical count. If No, then items with negative on-hand balances are not excluded from physical count. This attribute does not have a default value.
  • Title: Exclude zero balances
    Maximum Length: 30
    Value that indicates that items with zero on-hand balances are excluded from physical counts. Contains one of the following values: Y or N. If Y, then items with negative on-hand balances are excluded from physical count. If N, then items with negative on-hand balances are not excluded from physical count. This attribute does not have a default value.
  • Fifth user-defined sequence in which the physical inventory tags are generated. A list of accepted values is defined in the lookup type INV_TAG_GEN_SEQUENCE. There is no default value for this attribute.
  • Title: Sequence 5
    Maximum Length: 30
    Abbreviation that identifies the fifth sequence that the user defines when the application creates the physical inventory tag.
  • First user-defined sequence in which the physical inventory tags are generated. A list of accepted values is defined in the lookup type INV_TAG_GEN_SEQUENCE. This attribute does not have a default value.
  • Title: Sequence 1
    Maximum Length: 30
    Abbreviation that identifies the first sequence that the user defines when the application creates the physical inventory tag.
  • Fourth user-defined sequence in which the physical inventory tags are generated. A list of accepted values is defined in the lookup type INV_TAG_GEN_SEQUENCE. This attribute does not have a default value.
  • Title: Sequence 4
    Maximum Length: 30
    Abbreviation that identifies the fourth sequence that the user defines when the application creates the physical inventory tag.
  • Title: Snapshot Date
    Date when the application no longer allows changes to inventory.
  • Title: Adjustment Date
    Date when the application most recently adjusted the transaction.
  • Links
  • Title: Starting Default Tag
    Maximum Length: 40
    Next tag number in the sequence of tag numbers that the application creates for this physical inventory.
  • Title: Number of Blank Tags
    Number of empty tags to create.
  • Number of stock keeping units where the application no longer permits changes. These units reside in physical inventory.
  • Abbreviation that identifies the organization.
  • Value that uniquely identifies the organization.
  • Title: Date
    Date when the person physically counted the inventory.
  • Flexfields
    Title: Flexfields
    The Flexfields for Physical Inventories resource manages descriptive flexfields for physical inventories.
  • Value that uniquely identifies the physical inventory.
  • Title: Physical Inventory
    Maximum Length: 30
    Name of the physical inventory.
  • Subinventories
    Title: Subinventories
    The Physical Inventory Subinventories resource manages operations on physical inventory subinventories.
  • Second user-defined sequence in which the physical inventory tags are generated. A list of accepted values is defined in the lookup type INV_TAG_GEN_SEQUENCE. This attribute does not have a default value.
  • Title: Sequence 2
    Maximum Length: 30
    Abbreviation that identifies the second sequence that the user defines when the application creates the physical inventory tag.
  • Seventh user-defined sequence in which the physical inventory tags are generated. A list of accepted values is defined in the lookup type INV_TAG_GEN_SEQUENCE. There is no default value for this attribute.
  • Title: Sequence 7
    Maximum Length: 30
    Abbreviation that identifies the seventh sequence that the user defines when the application creates the physical inventory tag.
  • Value that indicates if the dynamic tag creation is permitted in the physical inventory. Contains one of the following values: Yes or No. If Yes, then serial numbers are displayed on physical inventory tags. If No, then serial numbers are not displayed on physical inventory tags. This attribute does not have a default value.
  • Title: Show serial numbers on tags
    Maximum Length: 1
    Value that indicates if the dynamic tag creation is permitted in the physical Inventory. Contains one of the following values: 1 or 2. If 1, then serial numbers are displayed on physical inventory tags. If 2, then serial numbers are not displayed on physical inventory tags. This attribute does not have a default value.
  • Sixth user-defined sequence in which the physical inventory tags are generated. A list of accepted values is defined in the lookup type INV_TAG_GEN_SEQUENCE. There is no default value for this attribute.
  • Title: Sequence 6
    Maximum Length: 30
    Abbreviation that identifies the sixth sequence that the user defines when the application creates the physical inventory tag.
  • Title: Starting Blank Tag
    Maximum Length: 40
    Starting empty tag number or the next empty tag number to create.
  • Type of physical inventory tags generated when the generate tags action is started. A list of accepted values is defined in the lookup type INV_GENERATE_TAG_TYPE. This attribute does not have a default value.
  • Title: Tag Type
    Maximum Length: 30
    Value that indicates the types of physical inventory tags generated when the generate tags action is started. A list of accepted values is defined in the lookup type INV_GENERATE_TAG_TYPE. This attribute does not have a default value.
  • Third user-defined sequence in which the physical inventory tags are generated. A list of accepted values is defined in the lookup type INV_TAG_GEN_SEQUENCE. This attribute does not have a default value.
  • Title: Sequence 3
    Maximum Length: 30
    Abbreviation that identifies the third sequence that the user defines when the application creates the physical inventory tag.
  • Total value of all adjustments in physical inventory.
Nested Schema : Flexfields
Type: array
Title: Flexfields
The Flexfields for Physical Inventories resource manages descriptive flexfields for physical inventories.
Show Source
Nested Schema : Subinventories
Type: array
Title: Subinventories
The Physical Inventory Subinventories resource manages operations on physical inventory subinventories.
Show Source
Nested Schema : physicalInventories-physicalInventoryDFFs-item-response
Type: object
Show Source
Nested Schema : physicalInventories-physicalInventorySubinventories-item-response
Type: object
Show Source
Back to Top