tbl_tracking_master

-1 rows


Description

Module: HRMS Employee Tracking
Purpose: Defines fundamental tracking, attendance, and expense permissions for employees at the individual level, overriding system-wide defaults with personalized settings.
Data: Each row represents an employee’s specific tracking configuration, including auto-punchout timing, permission flags, and organizational context.
Process Usage:
- Configures employee-specific tracking rules and attendance behaviors.
- Defines auto-punchout timing to prevent missed clock-outs.
- Controls granular permissions for tracking, multiple punches, and expense claims.
Key Points:
- Employee-level tracking configuration overriding system defaults.
- Integrated role-based and branch-based permission management.
- Flexible auto-punchout system for different work patterns.
Business Impact: Enables personalized tracking configurations, ensures accurate attendance capture, and provides granular control over employee monitoring and expense permissions.

Columns

Column Type Size Nulls Auto Default Children Parents Comments
id serial 10 √ nextval('tbl_tracking_master_id_seq'::regclass)

Primary key
Format: Long (auto-increment)
Used as: Unique identifier for each employee tracking configuration.
employee_id varchar 500 √ null
tbl_employee.employeeid fk_tm_employee R

FK: public.tbl_employee.id
Purpose: Identifies the employee for whom this tracking configuration applies.
Dependency: Links tracking settings to individual employee master records.
Cardinality: One-to-One relationship (each employee has one tracking configuration).
employee_role_id int4 10 √ null

FK: public.tbl_role_master.id
Purpose: References the employee’s role for role-based tracking rule inheritance.
Usage: Enables role-specific default configurations and permission templates.
Business Logic: Role settings may provide defaults that can be overridden at employee level.
branch_id int8 19 √ null

FK: public.tbl_BranchMaster.BranchID
Purpose: Associates tracking configuration with the employee’s branch location.
Usage: Enables branch-specific tracking rules and location-based configurations.
Integration: Works with branch-level geo-fencing and compliance settings.
auto_punch_out_time time 15,6 √ null

Format: Time (HH:MM:SS)
Purpose: Automatic punch-out time that triggers system-generated clock-out if employee forgets.
Business Logic:
- System automatically records punch-out at specified time if no manual punch-out
- Prevents overtime miscalculations and missed clock-outs
- Configurable per employee based on shift patterns
Examples: “18:00:00” (6 PM), “17:30:00” (5:30 PM), “20:00:00” (8 PM)
expense_allowed bool 1 false

Flag Type: Boolean
True: Employee can submit travel and expense claims
False: Employee cannot submit expense claims
Usage Scenarios:
- TRUE: Sales teams, field engineers, traveling executives
- FALSE: Office-based administrative staff, non-travel roles
Integration: Works with tracking policy expense configurations for claim processing.
tracking_allowed bool 1 false

Flag Type: Boolean
True: Employee is subject to location tracking and monitoring
False: Employee tracking is disabled (exempt from geo-fencing)
Usage Scenarios:
- TRUE: Field staff, remote workers requiring location validation
- FALSE: Office-based staff, executives with privacy considerations
Business Impact: Controls whether employee location data is collected and monitored.
multi_punch_allowed bool 1 false

Flag Type: Boolean
True: Employee can record multiple punch-in/punch-out entries per day
False: Employee restricted to single punch-in/punch-out pair daily
Usage Scenarios:
- TRUE: Field staff with multiple site visits, flexible work arrangements
- FALSE: Standard office staff with fixed working hours
Business Logic: Enables flexible work patterns for mobile employees.
createdby varchar 50 √ null
createddate timestamp 29,6 √ null
modifiedby varchar 50 √ null
modifieddate timestamp 29,6 √ null
companyid int8 19 √ null

FK: public.tbl_company.CompanyId
Purpose: Identifies the company context for multi-tenant implementations.
Usage: Scopes tracking configurations to specific company entities.
Business Use: Essential for organizations with multiple legal entities or subsidiaries.

Indexes

Constraint Name Type Sort Column(s)
tbl_tracking_master_pk__tbl_trac__3213e83f55b53c37 Primary key Asc id
tbl_tracking_master_idx_employee_role_id Performance Asc employee_role_id
tbl_tracking_master_idx_employee_tbl_tracking_master Performance Asc employee_id
tbl_tracking_master_idx_expense_allowed Performance Asc expense_allowed

Relationships

Close relationships within degrees of separation