> 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/purchase-order.md).
# Purchase Order
A **Purchase Order (PO)** is an official commercial document issued by a buyer to a supplier for purchasing products or services. It contains details such as item names, quantities, prices, delivery terms, and other purchase-related information.
* The Purchase Order serves as a formal agreement between the buyer and the supplier and helps control the procurement process within the organization.
## Steps to Create a Purchase Order
Step 1: Go to the **Purchase** main menu.
1. Click **Transaction**.
2. Select **Purchase Order**.
* After selecting the option, the Purchase Order screen will appear.
Step 2: Click the **PR** buttonavailable on the Purchase Order screen.
* The system will display the list of available Purchase Requisitions.
Step 3: Select the required Purchase Requisition (PR) from the displayed list.
1. Verify the requisition details carefully.
Step 4: Click the **OK** button to confirm the selected Purchase Requisition.
* The item details from the PR will automatically appear in the Purchase Order entry screen.
Step 5: Review all Purchase Order details carefully.
1. Click **Save** option to create the Purchase Order.
* Once saved, the Purchase Order will be generated successfully in the system.
---
# 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/purchase-order.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.
