> 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/inventory/issue-register/issue-register-configuration/department-selection-mandatory.md).
# Department Selection Mandatory
**YouTube:** [How to Make Department Selection Mandatory in the Issue Register?](https://www.youtube.com/watch?v=p8C_YeCa1dM)
## How to Make Department Selection Mandatory in the Issue Register?
In this tutorial, we will learn how to make **Department Selection** mandatory while creating an **Issue Register** entry in Logic ERP. This feature ensures that every Issue Register transaction is linked to a department, improving departmental tracking and accountability.
***
### Objective of This Feature
* Make Department selection mandatory during Issue Register entry.
* Ensure every transaction is assigned to a department.
* Improve departmental tracking and reporting.
* Prevent incomplete document entries.
* Maintain accurate inventory movement records.
***
### Access to the Issue Register Configuration
* Go to the **Issue Register** module.
* Open the **Configuration** window.
* Navigate to the **Other Settings** section.
* Locate and enable the option labeled as:
> **"Department Selection Mandatory"**
If the **Department Name** field is not visible:
* Open **Column Locks**.
* Locate the **Department Name** column.
* Enable the feature by ticking the checkbox.
* Save the configuration.
***
### Create a New Issue Register Entry
* Initiate a **New Issue Register** entry.
**Result**
* The **Department Name** field is now visible in the header section.
* Press the **Space Bar** in the Department Name field to open the Department search window and select the required department.
> **Note:** Departments can be created and managed through the **Setup Employee Department** module.
**Observe the Validation**
* Proceed with the Issue Register entry **without selecting a Department Name** and attempt to save the document.
**Result**
* The system restricts the action and displays an error message indicating that **Department Name selection is mandatory**.
**Select the Department and Save**
* Select the appropriate **Department Name**.
* Save the document again.
#### Result
The Issue Register entry is saved successfully.
***
### Key Benefits
* Ensures every Issue Register entry is department-wise.
* Improves departmental inventory tracking.
* Prevents incomplete transaction entries.
* Supports accurate reporting and analysis.
* Enhances inventory accountability.
***
### Best Practice Tips
* Enable the **Department Name** column before using this feature.
* Ensure all required departments are created in the **Setup Employee Department** module.
* Always assign the correct department to maintain accurate inventory records.
* Use department-wise reporting for better stock monitoring and internal control.
***
### Final Outcome
By enabling **Department Selection Mandatory**, Logic ERP requires users to select a department before saving an Issue Register entry. This ensures accurate departmental allocation, improves inventory tracking, and maintains complete and consistent transaction records.
---
# 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/inventory/issue-register/issue-register-configuration/department-selection-mandatory.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.