> 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/faq-on-transaction/how-do-i-create-a-new-purchase-requisition.md).

# How do I create a new Purchase Requisition?

To create a new Purchase Requisition (PR) in the system, follow these step-by-step instructions:

1. Navigate to the Menu: Go to the Purchase main menu.
2. Open the Screen: Click on **Transaction > Purchase Requisition**.
3. Select Basis: Click on Basis and select either Goods or Service.
4. **Enter Request Details:**
   * Input the Request Name according to your requirements.
   * Select the Cost Center for which the items are required (the visibility of this field depends on your Purchase Type Settings).
   * Select the purchase order date and the required "Need By" date.
5. **Set the Category:** Select the Purchase Order (PO) type and choose the Req Category directly below it.
6. **Add Items:** Click the Add button to add a PO item. Enter the item name, category, product name, details, quantity, rate, and amount.
7. Save: Once everything is configured, click the Save button to finalize and create the purchase requisition.


---

# 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/faq-on-transaction/how-do-i-create-a-new-purchase-requisition.md?ask=<question>&goal=<user_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.