The inventory count widget is configured by default with 3 count types:


  • ABC Cycle Count - includes balances due for count based on ABC analysis
  • Unreconciled Count - includes balances that are unreconciled
  • Ad-hoc count - includes all balances in the storeroom


It is possible through configuration to change the available count types, and add custom count types.


To change the available count types, add a configuration map to the moduleconfig section of the STAUTOSCRIPT.STAMCONFIG automation script with the following properties:


Property NameValue
moduleInventoryCountModule
providersA list of configuration maps specifying the available counts



For example, the default configuration is as follows:

appConfig = {
  ...
  "moduleconfig": [
    ...
    {
      "module": "InventoryCountModule",
      "providers": [
        {
          "module": "AbcCycleCountModule"
        },
        {
          "module": "UnreconciledCountModule"
        },
        {
          "module": "AdhocCountModule"
        }
      ]
    }
  ]
}


Opqo displays the count types using the contents of the providers list.  Removing a count type from this list will remove it from the list displayed in the app. 



Note: For more information on Opqo configuration and the role and contents of the STAUTOSCRIPT.STAMCONFIG script, see the Configuration Overview article.



Default Count Type Queries


Each of the default count types use a corresponding query on the STAMINVBALANCE object structure.  These queries can be modified as necessary to refine the items due for count.


The queries used by each default count type are as follows:


Count TypeQuery Name
ABC Cycle Countcountccf
Unreconciled Countcountunreconciled
Adhoc Countcount



Note: If you customize these queries, ensure you delete/replace the "Standard:" prefix from the query description.  We recommend you replace "Standard:" with "Custom:" for easy identification.  This will ensure that future Opqo upgrades do not overwrite your customized query definitions. 




Custom Count Types


Custom count types are supported by the SavedQueryCountModule.  This count type identifies the items to be counted using a custom query added to the STAMINVBALANCE object structure.


A custom count type can be added by including a configuration map to the providers section with the following properties:


Property NameValue
moduleSavedQueryCountModule
nameThe display name for the count type in Opqo
savedQueryNameThe name of the query on the STAMINVBALANCE object structure to use to identify the items to count.
removeFromScopeOnCountSet to true to have Opqo remove balances from the user's count list as they are counted, or false to have them remain in the list.

Typically you want to set this to match whether balances fall out of scope of the query as they are counted. For example, this behavior is true for the default ABC Cycle Count, and false for the default Adhoc Count.

This property is optional, and if not specified will default to true.



For example, a configuration with an additional custom count might look like the following:


appConfig = {
  ...
  "moduleconfig": [
    ...
    {
      "module": "InventoryCountModule",
      "providers": [
        {
          "module": "AbcCycleCountModule"
        },
        {
          "module": "SavedQueryCountModule",
          "name": "Our custom count",
          "savedQueryName": "customcountquery"
        },
        {
          "module": "UnreconciledCountModule"
        },
        {
          "module": "AdhocCountModule"
        }
      ]
    }
  ]
}


A few notes on specifying custom queries:


  • The query is used as the base query for items to be counted, and should only include balances that are valid for counting:
    • Staging bins should be excluded.
    • Rotating items should be excluded.
  • The query should be marked public.
  • The most common type of query is to specify the query directly as an osclause, however it can be any valid object structure query type that applies to INVBALANCES mbos.
  • The default count query provides a good base to build custom queries upon.



If you have questions please do not hesitate to contact us or create a support ticket for more assistance.