> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/material-management/material-management-module/mm-analysis/departmentwise-item-consumption-summary.md).
# Departmentwise Item Consumption Summary
The **Departmentwise Item Consumption Summary** report provides a consolidated view of items consumed by each department during a selected period. It displays the quantity of items used and, where applicable, the corresponding consumption value based on issued, consumed, or recorded inventory transactions.
## Steps to View the Departmentwise Item Consumption Summary
Step 1: Navigate to the **Analysis** menu in the **Inventory** module.
1. Select **Departmentwise Item Consumption Summary**.
* The **Departmentwise Item Consumption Summary** Report screen will be displayed.
Step 2: After opening the report page, select the required filters to generate the data.
* The report supports multiple filters, allowing users to narrow down and customise the results according to specific requirements.
Step 3: Use the **Funnel Filter.**
* The **Funnel Filter** allows you to refine the report by applying additional search conditions.
1. Use the Group By Option
* The **Group By** drop-down enables users to organise report data in different formats for easier analysis.
Step 4: After selecting the required filters and grouping options, click **Display** button.
1. The system will display the Departmentwise Item Consumption Summary based on the selected criteria.
---
# 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://help.rbsgo.com/material-management/material-management-module/mm-analysis/departmentwise-item-consumption-summary.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.
