> 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-can-i-approve-a-pr.md).

# How can I approve a PR ?

We can approve a Purchase Requisition (PR) in the system.To approve a PR, follow these steps:

1. Go to the Purchase main menu.
2. Click on **Transaction > Approval.**
3. Click the Open button and choose the relevant request number.
4. Click on the Save button to complete the approval.

**Approval Rules and Settings**

If you need to configure how these approvals are routed or who has permission to approve them, you can manage these rules in the Masters section:

* PO Approval Settings: Navigate to **Masters > PO Approval Settings** to select your transaction (Tm) type and PO type, then enable the appropriate Approval Level and Approval Procedure.
* Approval Authority: Navigate to **Masters > Approval Authority** to assign specific users as the authorized approvers based on transaction type, PO type, and request category.


---

# 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-can-i-approve-a-pr.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.