> 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-reports/mm-reports-material-request-status-report.md).
# Material Request Status Report
Steps to view material request status report
The **Material Request Status Report** provides a complete list of all **Material Requests (MR)** or **Store Indents** along with their current status across one or more stores.This report helps users monitor the progress of material requests and track whether they are approved, pending, short closed, or completed.
## Steps to View the Material Request Status Report
Step 1: Navigate to the **Reports** menu in the **Inventory** module.
1. Select **Material Request Status Report**.
* The report screen will be displayed.
Step 2: Click the **Funnel Filter** option.
1. Use the available filter options to refine the report.
* You can filter the report based on Material Request Number (MR No.)
* These filters help you locate specific Material Requests quickly and accurately.
Step 3: Choose the required filter **Options**based on your requirement.
Step 4: After applying the required filters, click the **Display** button.
1. The system will generate and display the Material Request Status Report.
Step 5: Print or Export the Report
1. Once the report is displayed, you can:
* Click the **Print** button to print the report..png?alt=media)
* Click the **Excel** button to export and download the report in Microsoft Excel format..png?alt=media)
---
# 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-reports/mm-reports-material-request-status-report.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.
