> For the complete documentation index, see [llms.txt](https://docs.novacura.com/marketplace-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novacura.com/marketplace-documentation/applications/explore-apps/infor-m3/documentation/supply-chain-execution/count-stock.md).
# Count Stock
An overview of an application used for counting Balance Id(s) as part of ongoing physical inventory.
## Overview
Application Overview
### Features
* Search for Inventory Counts.
* Browse after Physical Inventory Numbers.
* Select Inventory Count Line.
* Report Inventory Count Line details.
* Report quantitative data, like Quantity and Catch Weight, if applicable.
## User Steps
### Search Inventory Count
{% hint style="info" %}
Use the following User Step to fetch existing Inventory Count lists.
{% endhint %}
**INFO/HEADER DATA**
* N/A
**INPUT DATA**
* Inventory Count \*\
\
\* indicates an input field is mandatory
**FUNCTIONALITY**
* Type in/scan the inventory count number value inside the **Inventory Count** Text Input.
Typing in Inventory Count number.
* Click **EXIT** to get back to the main menu.
* Click **LIST** to get to [**List**](#list) User Step.
* Click **NEXT** to get to [**Select Count Line**](#select-count-line) User Step.
#### List
{% hint style="info" %}
Use the following User Step to browse after existing inventory count lists.
{% endhint %}
**INFO/HEADER DATA**
* N/A
**INPUT DATA**
* Inventory Count(s)
* Physical Inventory Number
* Physical Inventory Name
* Number of active (not reported) Inventory Count Lines
**FUNCTIONALITY**
* Browse through the list of available inventory counts.
* Use Search Bar to filter the list, using item inventory count number or name.
Browsing through inventory counts using names.
* Click **BACK** to get back to [**Search Inventory Count**](#search-inventory-count) User Step.
* Tap on an item number to select one (acts as **NEXT**) and continue to [**Select Count Line**](#select-count-line) User Step.
### Select Count Line
{% hint style="info" %}
Use the following User Step to select a Balance Id for details check-up.
{% endhint %}
**INFO/HEADER DATA**
* Inventory Count
* Inventory Count Number
* Number of active (not reported) Inventory Count Lines
**INPUT DATA**
* Inventory Count Line(s)
* Line Number
* Location
* Item Number
* Lot Number (if applicable)
* Container Number (if applicable)
* On-hand Balance Quantity (Basic Unit of Measure)
**FUNCTIONALITY**
* Browse through the list of searched Count Line(s).
* Use Search Bar to filter the list, using details of Balance Id(s) to be counted.
Browsing through available count lines.
* Click **BACK** to get back to [**Search Inventory Count**](#search-inventory-count) User Step.
* Tap on a Line number to select one (acts as **NEXT**) and get to [**Report Quantity**](#report-quantity) User Step.
### Report Quantity
{% hint style="info" %}
Use the following User Step to report quantitative data.
{% endhint %}
**INFO/HEADER DATA**
* Selected Count Line
* Line Number
* Location
* Item Number
* Lot Number (if applicable)
* Container or Package Number (if applicable)
**INPUT DATA**
* Quantity \*
* Catch Weight \* (if applicable)\
\
\* indicates an input field is mandatory
**FUNCTIONALITY**
* Type in/scan the numeric quantity value inside the **Quantity** Numeric Input.
* Type in/scan the numeric catch weight value inside the **Catch Weight** Numeric Input.
Typing in Quantity.
Typing in Catch Weight.
* Click **BACK** to get back to [**Select Count Line**](#select-count-line) User Step.
* Click **COUNT** to run the transaction.
* You will be brought back to updated [**Select Count Line**](#select-count-line) User Step with previously applied filter. If the list is empty, You will be brought back to [**Search Inventory Count**](#search-inventory-count) User Step.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.novacura.com/marketplace-documentation/applications/explore-apps/infor-m3/documentation/supply-chain-execution/count-stock.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
