> 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-amendment.md).
# PO Amendment
The **Purchase Order Amendment** transaction is used to modify or update an existing Purchase Order (PO). This feature allows users to make necessary changes to Purchase Orders after they have been created.Multiple amendments can be made to the same Purchase Order whenever required.
## Steps for Purchase Order Amendment
Step 1: Go to the **Purchase** main menu.
1. Click **Transaction**.
2. Select **Purchase Order Amendment**.
* The Purchase Order Amendment screen will appear.
Step 2: Click on the **PO No** field.
1. The system will display the list of available Purchase Orders.
2. Select the Purchase Order that needs to be amended.
* The selected Purchase Order details will be loaded into the amendment screen.
Step 3: Modify the Purchase Order Details.
1. Verify all modified details carefully before saving.
Step 4: After completing the required changes, click the **Save** button.
* The system will save the amended 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-amendment.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.
