> 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-transactions-purchase-requisition.md).
# Purchase Requisition
Steps to create a purchase requisition
A **Purchase Requisition (PR)** is an internal request document used to inform the Purchase Department about the requirement for materials or services. It is created by department users, store personnel, or authorized staff whenever items need to be purchased.
## Steps to Create a Purchase Requisition
Step 1: Go to the **Purchase** main menu.
1. Click **Transaction**.
2. Select **Purchase Requisition**.
* After clicking **Purchase Requisition**, the Purchase Requisition entry screen will appear.
Step 2: Click on the **Basis** field.
1. Select either **Goods** or **Service**
* Choose the appropriate option based on the requirement.
Step 3: In the **Request Name** field, enter the name of the requisition.
Step 4: Select the appropriate **Cost Center** for which the items are required.
1. The Cost Center field is displayed based on the Purchase Type settings configured in the system.
Step 5: Select the **Purchase Order Date,** then select the required **Need By Date**.
Step 6: Choose the required **PO Type** from the available options.
* The PO Type defines the category or purpose of the purchase.
Step 7: Select the appropriate **Requisition Category** below the PO Type.
Step 8: Click the **Add** button to add item details.
* Ensure that all item details are entered correctly before proceeding.
Step 9: After entering all required details, click the **Save** button.
* The Purchase Requisition will be created 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/purchase-transactions-purchase-requisition.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.
