> 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/pick-department-auto-where-employee-is-chosen.md).

# Pick Department Auto where Employee is Chosen

**YouTube:** [How to Auto-Select Department Based on Employee in Purchase Orders?](https://youtu.be/vmL7j8WDd5c)

## How to Auto - Select Department Based on Employee in Purchase Order?

This tutorial explains how to automatically pick the **Department Name** when an employee is selected in a Purchase Order in Logic ERP. This feature helps streamline transaction entry by automatically fetching department details from the Employee Master.

***

### **Objective of This Feature**

* Automatically fetch department based on selected employee
* Reduce manual department entry
* Improve transaction accuracy
* Save time during Purchase Order creation

***

### **Enable Auto Department Feature**

* Open **Purchase Order Configuration Window**
* Navigate to **Default Options**
* Locate and enable the option labeled as:

> **“Pick Department Auto where Employee is Chosen”**

<figure><img src="/files/IOnUgnLLBql1UL8ql2C5" alt=""><figcaption></figcaption></figure>

* Verify that the **Worker/Employee Name Field** is enabled

**If Field is Not Visible**

* Go to **General Options**
* Click on **Column Locks**
* Search for **Worker’s Name Column**

<figure><img src="/files/l3ETkHPrWrzdygagkcnO" alt=""><figcaption></figcaption></figure>

**Action**

* Unlock the column
* Save the configuration

***

### **Verify Auto Department Picking**

* Initiate a **New Purchase Order Entry**
* Select the **Supplier**
* Choose the **Employee Name**

<figure><img src="/files/2sSKI1bEEit5q7kKOdOn" alt=""><figcaption></figcaption></figure>

**System Behavior**

* As soon as the employee is selected:
  * System automatically picks the **Department Name** linked with the employee

***

### **Review Employee Department Mapping**

* Navigate to **Payroll Setups**
* Open **Setup Employee Window**&#x20;

<figure><img src="/files/UkWvOuNG1U5CU9rg6Rvw" alt=""><figcaption></figcaption></figure>

**Purpose**

* Here you can:
  * View
  * Define
  * Update the employee’s department name

***

### **Key Benefits**

* Eliminates manual department selection
* Improves accuracy in transaction records
* Speeds up Purchase Order entry process
* Ensures proper employee-department mapping

***

### **Best Practice Tips**

* Ensure departments are properly defined in Employee Master
* Keep employee records updated regularly
* Enable only required fields through column settings

***

### **Final Outcome**

* Department is automatically picked when employee is selected
* Faster and more accurate Purchase Order entry
* Reduced manual effort and errors
* Improved workflow efficiency and data consistency


---

# 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/pick-department-auto-where-employee-is-chosen.md?ask=<question>&goal=<endgoal>
```

`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.
