> 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/queries/po-item-query.md).
# PO Item Query
The **PO (Purchase Order) Item Query** feature is used to view and check the details of items included in a Purchase Order.
## **Steps to Access and Use PO Item Query**
Step 1: Go to the **Purchase** main menu on your dashboard.
1. In the Purchase menu, click on **Queries**.
2. From the drop-down, select **PO Item Query**.
Step 2: On the PO Item Query screen, you can refine your search using the following filters:
1. **Date Range** – Select the start and end date to view POs within a specific period.
2. **Supplier Name** – Enter the supplier’s name to filter items by supplier.
3. **Item Selection** – Click the **search icon** next to the item field to select a specific item.
Step 3: Once you have entered all required filters, click the **Display** button.
* The system will generate and display the list of Purchase Order items that match your criteria.
Step 4: After the results are displayed, you can export the data for further analysis:
1. Click on the **Excel** button.
* The PO Item Query will be downloaded in **Excel format**, which you can save or print for reporting purposes.
---
# 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/queries/po-item-query.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.
