Documentation
Business Units
Business Units provides a durable Organization-level operating and financial reporting dimension used across AkshaERP.
What Business Units is for
Business Units maintains Organization-level operating or financial reporting divisions.
A Business Unit can become part of financial dimensions used by GL, Sales, Inventory, Circulation and other AkshaERP transactions.
Create a Business Unit
Choose Create and enter Organization, Business Unit Code, Business Unit Name and Business Unit Type.
A new Business Unit starts as Active.
- Code is normalized to uppercase.
- Code can use letters, numbers, underscore and dash.
- Code is unique inside the Organization.
- The same Code can exist in a different Organization.
Organization and Type
An Active Business Unit must belong to an Active Organization.
Business Unit Type is a controlled classification configured for the implementation.
Hierarchy and defaults
A Business Unit can optionally use a Parent Business Unit, Default Branch and Manager Employee.
- Parent must belong to the same Organization.
- Circular hierarchy is prevented.
- An Active Business Unit cannot use an Inactive Parent.
- Default Branch must belong to the same Organization.
- An Active Business Unit requires an Active Default Branch when selected.
- Manager must be a valid current Employee for an Active Business Unit.
Effective dates
Effective Start Date and Effective End Date are optional. If both are entered, End Date cannot be earlier than Start Date.
Review Usage
Usage shows current hierarchy, access and default-master references that can prevent deactivation.
- Active child Business Units
- User Business Unit assignments
- Role Business Unit assignments
- Branch and Organization defaults
- Financial Dimension Rule defaults
- Item, Partner and other active master defaults
Activate and deactivate
Deactivate removes the Business Unit from new Active lookup while preserving its historical identity.
Activate returns a valid inactive Business Unit to service after important references are revalidated.
Inactive Business Units and historical records
Inactive Business Units stop appearing in normal Active Business Unit searches used for new setup.
Existing records can continue to display the Business Unit they already reference.
Business Unit access
AkshaERP includes User and Role Business Unit assignment structures used by Financial Dimensions.
Access mapping should be reviewed carefully before an implementation enables a stricter Business Unit access policy because the dimension can affect accounting and transaction processing.
History
History records master events such as Create, Update, Activate and Deactivate with the user, time and summary.
Recommended setup sequence
- Confirm the Organization.
- Search for an existing Business Unit.
- Choose the final Code and Type.
- Configure Parent, Default Branch and Manager where needed.
- Maintain effectivity dates if required.
- Save the Business Unit.
- Configure financial-dimension defaults/rules and access.
- Review Usage before later deactivation.
Related pages
Frequently asked questions
Can I change a Business Unit Code after creation?
No. Business Unit Code is treated as a stable operating and financial identifier after creation.
Can I move a Business Unit to another Organization?
Not through normal Business Unit maintenance. Organization is part of its durable identity.
Can two Organizations use the same Business Unit Code?
Yes. Code uniqueness is enforced within each Organization.
Can a Business Unit have a Parent?
Yes. The Parent must belong to the same Organization, and AkshaERP prevents circular hierarchy.
Why can’t I deactivate a Business Unit?
A current dependency still uses it. Open Usage and resolve active child, User/Role assignment or default-master references first.
Will deactivation change old transactions?
No. Historical records retain the Business Unit they already reference.
Can I permanently delete a Business Unit?
Normal permanent deletion is not provided. Deactivate it after resolving active dependencies.