> 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/quote-tabular-approval.md).
# Quote Tabular Approval
**Quote Tabular Approval** is a process used to review and approve vendor quotations displayed in a tabular format. This method allows users to compare multiple vendor quotations side by side for better evaluation and approval decisions.
## Steps for Quote Tabular Approval
Step 1: Go to the **Purchase** main menu.
1. Click **Transaction**.
2. Select **Quote Tabular Approval**.
* The Quote Approval screen will appear.
Step 2: Click the **Open** button.
* The system will display the list of available RFQ (Request for Quotation) numbers.
Step 3: Choose the required **RFQ No** from the displayed list.
1. Verify the RFQ details carefully.
2. Click the **OK** button.
* The quotation comparison screen will appear in tabular format.
Step 4: Review the displayed vendor quotations.
1. Select the required quotation by enabling the **Tick Mark** or selection option.
2. Click the **Save** button.
* The selected quotation will be approved 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/quote-tabular-approval.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.
