> 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/mm-analysis-issue-analysis.md).
# Issue Analysis
Steps to view issue analysis
The **Issue Analysis Report** provides detailed information about all issue transactions recorded in the **Materials Management (MM) Module**. This report is similar to the **Issue List Report** but offers additional analytical capabilities to help users evaluate and monitor inventory issues more effectively.
## Steps to View the Issue Analysis Report
Step 1: Navigate to the **Analysis** menu in the **Inventory** module.
1. Select **Issue Analysis**.
* The **Issue Analysis** Report screen will be displayed.
Step 2: Click the **Funnel Filter** icon.
1. Select the required filter criteria to refine the report.
2. Use the **Group By** drop-down to organise the report data.
Step 3: After selecting the required filters and grouping options, click the **Display** button.
* The system will generate and display the Issue Analysis Report.
---
# 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/mm-analysis-issue-analysis.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.
