> 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-transactions/faq-on-material/how-to-view-consumption-departmentwise-to-analyze-item-usage-following-sales-posting.md).

# How to view Consumption Departmentwise to analyze item usage following sales posting ?

To analyze item usage following your sales posting, you can use either the Item Consumption Query for a specific product or the Departmentwise Item Consumption Summary for an overall departmental view.

***

1\. Item Consumption Query (Product-Level View)This query provides a detailed list of all receipt and issue transactions for a selected item within a specified store and time frame.

1. Go to Queries > Item Consumption Query.
2. Click the Item Search icon, choose the item, and select the date range.
3. Click the Display button to load the transactions.
4. *(Optional)* Click the Advance search Filter option to refine your view, or click the Excel button to download the report.

***

2\. Departmentwise Item Consumption Summary (Department-Level View)This report presents a consolidated summary of items consumed across each department, detailing total quantities and monetary values based on issued and recorded transactions.

1. Go to Analysis > Departmentwise Item Consumption Summary.
2. Use the Funnel filter or Group By drop-down options to filter for specific information or customize the grouping.
3. Review the departmental usage and consumption patterns on your screen.


---

# 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-transactions/faq-on-material/how-to-view-consumption-departmentwise-to-analyze-item-usage-following-sales-posting.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.