> For the complete documentation index, see [llms.txt](https://kb.logicerp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/order-processing/purchase-order/po-configuration/filter-purchase-indents-retrieval-on-basis-of-department.md).
# Filter Purchase Indents Retrieval on basis of Department
**YouTube:** [How to Filter Purchase Indent Retrieval by Department in Purchase Orders?](https://youtu.be/RISCP9hy7A8)
## How to Filter Purchase Indent Retrieval by Department in Purchase Orders?
This tutorial explains how to filter **Purchase Indents** in a Purchase Order based on the selected **Department** in Logic ERP. This feature ensures that users can retrieve only department-specific indents, improve accuracy and simplify the procurement process.
***
### **Objective of This Feature**
* Filter Purchase Indents department-wise
* Display only relevant indents during retrieval
* Improve procurement accuracy
* Simplify Purchase Order creation process
***
### **Observe Default Indent Retrieval**
* In the header section, you will find the:
* Department Field.
* If Department Field is Not Visible.
* Enable it using **Column Lock Option.**
**Transaction Process (Without Department)**
* Create a **New Purchase Order.**
* Proceed without selecting any Department.
* Select the **Supplier.**
* Move to the **Item Details Section.**
**Retrieve Purchase Indent**
* Click on **Retrieve Option.**
* Select **Purchase Indent.**
**Default System Behavior**
* While searching for Indents:
* System displays all Purchase Indents related to the selected Supplier.
* Regardless of Department.
***
### **Enable Department-Based Indent Filter**
* Open the **Purchase Order Configuration Window**
* Navigate to **Default Settings**
* Locate and enable the option labeled as:
> **“Filter Purchase Indents Retrieval on basis of Department”**
* Click **Save**
***
### **Verify Department-Based Filtering**
**Transaction Process**
* Create a **New Purchase Order** again
* Select the:
* **Department**
* **Supplier**
**Retrieve Purchase Indents**
* Go to the **Item Details Section**
* Click on **Retrieve Indents**
**System Behavior**
* System now displays:
* Only the Purchase Indents related to the selected Department and Supplier
***
### **Key Benefits**
* Faster Purchase Indent retrieval
* Improved procurement accuracy
* Reduced confusion during indent selection
* Better department-wise control and management
***
### **Best Practice Tips**
* Ensure Departments are properly configured in the system
* Assign Purchase Indents to correct Departments
* Use department-wise filtering for better workflow management
***
### **Final Outcome**
* Purchase Indents are filtered based on the selected Department
* Users can retrieve only relevant department-specific indents
* Improved efficiency and accuracy in Purchase Order processing
* Better procurement control across departments
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/order-processing/purchase-order/po-configuration/filter-purchase-indents-retrieval-on-basis-of-department.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.