> 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/purchase/purchase-module/purchase-transactions/po-cancel.md).
# PO Cancel
The **Purchase Order Cancel** option is used to cancel an already created Purchase Order (PO). This feature allows users to stop further processing of a PO when it is no longer required or was created incorrectly.
* Once a Purchase Order is cancelled, it cannot be used for any further procurement activities.
## Steps to Cancel a Purchase Order
Step 1: Go to the **Purchase** main menu.
1. Click **Transaction**.
2. Select **Purchase Order Cancel**.
* The Purchase Order Cancel screen will appear.
Step 2: Click the **Open** button in the PO Cancel screen.
Step 3: Click the **PO No Search Icon**.
1. A list of Purchase Orders will be displayed.
2. Select the required **PO**.
3. Choose the appropriate **PO Type** and **Vendor Name.**
* Ensure the correct Purchase Order is selected before proceeding.
Step 4: Click the **PR button**.
1. The PR item selection window will appear.
2. Select the required **Purchase Requisition (PR)** linked to the PO.
3. Click **OK**.
* The selected PR items will be loaded into the screen.
Step 5: Click the **Save** button.
* The system will cancel the selected Purchase Order successfully.
---
# 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/purchase/purchase-module/purchase-transactions/po-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.
