> 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-request-reprint.md).
# Purchase Request Reprint
The **Purchase Requisition Reprint** transaction is used to view and print previously created Purchase Requisitions. This feature helps users reprint requisition documents whenever required for verification, approval, documentation, or record-keeping purposes.
## Steps to Reprint a Purchase Requisition
Step 1: Go to the **Purchase** main menu.
1. Click **Transaction**.
2. Select **Purchase Requisition Reprint**.
* After selecting the option, the Purchase Requisition Reprint screen will appear.
Step 2: Select the required **Date** range or transaction date.
1. Choose the appropriate **Status** from the available options.
Step 3: Click the **Display** button.
* The system will display the list of Purchase Requisitions based on the selected date and status.
Step 4: From the displayed list, select the required Purchase Requisition or bill that needs to be reprinted.
Step 5: Click the **Print** button available at the top-right corner of the screen.
* The selected Purchase Requisition will open in print format and can be printed or saved as required.
---
# 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-request-reprint.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.
