> 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/material-request-cancel.md).
# Material Request – Cancel
Steps to perform the material Request Cancel
The **Material Request Cancel** option is used to cancel an existing Material Request that was created by mistake or is no longer required.This feature allows users to cancel a complete Material Request and prevents further processing of the request.
## Steps to Perform a Material Request Cancellation
Step 1: Navigate to **Transactions** in the **Inventory** module.
1. Select **Material Request Cancel**.
* The Material Request Cancel screen will be displayed.
Step 2: Locate the **Store** field.
1. Select the appropriate store from the available list.
Step 3: Click on the **Receipt No** field.
1. Select the Material Request number that needs to be cancelled.
* The details of the selected Material Request will be displayed on the screen.
Step 4:Click the **Cancel** button.
1. A dialog box will appear requesting a cancellation reason.
2. Enter the reason for cancellation (Examples: Material Request created by mistake, Request no longer required).
3. Click **OK** to confirm the cancellation reason.
Step 5: Review the cancellation details.
1. Click the **Save** button.
* The selected Material Request will be successfully cancelled and removed from further processing.
---
# 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/material-request-cancel.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.
