Scenario:
The organisation wants to classify employees such as Permanent, Contract, or Trainee.
Action:
User enters category code, name, description, and saves the record.
Outcome:
A new employee category is created and stored in the system.
Scenario:
Different employee categories follow different HR or operational rules.
Action:
User defines category-related attributes such as type or applicability.
Outcome:
Employee category is standardised for consistent usage across modules.
Scenario:
Employees must be mapped to a defined category during creation.
Action:
User selects the employee category in Employee Master.
Outcome:
Employee is correctly classified under the selected category.
Scenario:
Attendance, payroll, or MES transactions depend on employee category.
Action:
System fetches category data during transaction processing.
Outcome:
Category-specific rules are applied in ERP/MES transactions.
Scenario:
Management requires reports based on employee categories.
Action:
System groups employee data based on category.
Outcome:
Accurate category-wise employee, attendance, and cost reports are generated.