> 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/masters/po-type.md).
# PO Type
The **PO Type (Purchase Order Type)** master is used to create and manage different types of Purchase Orders in the system.
## **Steps to Create PO Type**
Step 1: Navigate to the **Purchase** main menu from the dashboard.
1. Click on **Masters**.
2. From the Masters menu, select **PO Type**.
* After clicking **PO Type**, the PO Type management screen will open.
Step 2: Click on the **Add** button.
1. Enter the required details in the fields provided:
* **PO Type Name** – Enter the name of the purchase order type
* **PO ID** – Enter a unique identification code for the PO type
Step 3: Select the **Active** checkbox to activate the PO Type.
1. Enable or disable the required menus based on business requirements.
* This helps control which features are available for this PO type.
Step 4: After entering all required details and settings, click on the **Save** button.
* The system will successfully create and store the new PO Type.
---
# 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/masters/po-type.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.
