Department
Department separates transactions, stock, expenses, and reports by work location or cost center. This data is usually used together with Division so records are easier to trace.
Used By
operations admins according to menu access rights
Data Type
master
Search Keys
Code, Name
When to Use This Form
- When the company adds a new work location, warehouse, service area, or cost center.
- When transactions need to be separated per department for stock, expense, or performance reports.
- When an old department is renamed, moved to another division, or no longer used.
Before You Start
- Make sure the Division that owns the department has been created and is still active.
- Agree on the department code so it is easy to tell apart from other branches, warehouses, or cost centers.
Workflow
- Open Settings / Organization / Department List.
- Enter the code, name, and a description if needed so the department is easy to recognize.
- Select the correct Division because this choice affects transaction filters and reports.
- Set the active status according to whether the department may still be used for new transactions.
- Save, then re-check the department options on related transactions.
Key Fields
| Field | Explanation for Users | Status |
|---|---|---|
Code
id |
Department code used as a short identifier on transactions and reports. | Required |
Name
name |
Department name shown in entry options, filters, and reports. | Required |
Division
division |
Division that owns the department. This choice helps separate transactions per branch or business unit. | Required |
Active
isactive |
Determines whether the department can still be used for new transactions. | Optional |
Last Modified
updatetimestamp |
The last time the department data was updated by the application. | Optional |
Details and Relations
- This form has no additional details. Its main relation is the Division that is the parent of the department.
What Happens After Saving
- Active departments can be selected on transactions and report filters that use department separation.
- Changing the Division can change how data is grouped in branch or business unit reports.
- A deactivated department is not recommended for new transactions, but old history can still be traced.
Common Problems
- Department does not appear on transactions: check the active status, Division, and user access rights.
- Reports look mixed up: check whether transactions use the right department.
- Data cannot be saved: make sure the code, name, and Division have been filled in.
Available Fields
The following list summarizes the fields available on the form. Rarely used fields are still listed so they are easy to look up during training or support.
| Field | Explanation for Users | Status |
|---|---|---|
Code
id |
Department code used as a short identifier on transactions and reports. | Required |
Name
name |
Department name shown in entry options, filters, and reports. | Required |
Description
description |
Additional remarks if the department name needs more detailed explanation. | Optional |
Division
division |
Division that owns the department. This choice helps separate transactions per branch or business unit. | Required |
Active
isactive |
Determines whether the department can still be used for new transactions. | Optional |
Created By
usercreate |
User who first created the department data. | Optional |
Modified By
useredit |
User who last modified the department data. | Optional |
Last Modified
updatetimestamp |
The last time the department data was updated by the application. | Optional |
User Checklist
Menu Location
- Settings / Organization / Department List
/form/departement