> 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-reports/faq-on-reports/how-to-check-pr-status.md).

# How to check PR status ?

You can check the status of your Purchase Requisitions (PRs) using two different reports, depending on whether you need an overall requisition overview or a detailed item-by-item breakdown.

**1. Purchase Requisition Status Report**

Use this report to view the overall current status of any PRs raised within your organization.

* How to Access:
  1. Go to the Purchase main menu.
  2. Click on **Reports > Purchase Requisition Status Report.**
  3. Click on the Advance Filter option to narrow down your results.
  4. Click the option button to select your specific criteria.
  5. Click the Display button to view the report on your screen.
  6. *(Optional)* Click the Excel button to download the report in Excel format.

**2. Item-wise PR Status Report**

If you want to track the status of each individual item listed inside your purchase requisitions rather than just the overall PR status, use this report.

* How to Access:
  1. Go to the Purchase main menu.
  2. Click on Reports > Item wise PR Status Report.
  3. Click on the Advance Filter option.
  4. Click the option button to select your criteria.
  5. Click the Display button to load the report.
  6. *(Optional)* Click the Excel button to download the data.


---

# 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-reports/faq-on-reports/how-to-check-pr-status.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.