> For the complete documentation index, see [llms.txt](https://kb.logicerp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.logicerp.com/logic-erp-version-release-notes/october-2026/reports-queries/scheme-reports/scheme-campaign-wise-closing-stock.md).

# Scheme Campaign Wise Closing Stock

Logic ERP has corrected the **Scheme Campaign Wise Closing Stock** report. It now lists every scheme campaign running during the report period, shows **STOCK IN HAND** and **STOCK VALUE** on every row, and shows the first slab of each scheme campaign group. The report's configuration screen has also been updated.

***

### **Step 1: Open the Report**

* Navigate to **Reports/Queries** and select **Scheme Reports**.
* Open the **Scheme Campaign Wise Closing Stock**.

***

### **Step 2: Item Group Levels**

* Go to **Configuration > Report Options > Item Group Levels**.
* Tick **Item Group Levels** to choose one or more item group levels from the list.
* The levels you choose are now kept when the configuration is opened again. Earlier the list came up empty each time, and saving the configuration put it back to a single level.

***

### **What's corrected**

* The report now lists every scheme campaign whose period overlaps the report's date range, including a scheme campaign that starts before the from date and ends after the to date. Earlier such a scheme campaign was left out. More scheme campaigns and rows may appear. This is intended.
* **STOCK IN HAND** and **STOCK VALUE** are now shown on every row, whatever is ticked under **Item Consolidation**. Each row shows the stock of the items behind that row in its scheme campaign group. Earlier stock was shown only when both **Pack / Size** and **Item Name** were ticked, and was blank otherwise. Stock figures and their totals will **rise** on these reports. This is intended.
* **STOCK VALUE** is now filled even when **STOCK IN HAND** is not shown in the report.
* With **Transact Items Only** ticked, rows with stock are now shown even when **STOCK IN HAND** is not shown in the report, or when **Pack / Size** and **Item Name** are not both ticked. Earlier no rows were shown in these set-ups.
* When a scheme campaign group has several slabs, **SLAB VALUE**, **SLAB C.D.(%)**, **SLAB T.D.(%)** and **SLAB NEW RATE** now show its first slab, the one with the lowest **SLAB VALUE**. Earlier any one of its slabs could be shown.
* With **Transact Items Only** ticked, **SNO.** now numbers only the rows that are printed. Earlier the numbers had gaps.


---

# 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://kb.logicerp.com/logic-erp-version-release-notes/october-2026/reports-queries/scheme-reports/scheme-campaign-wise-closing-stock.md?ask=<question>&goal=<user_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.
