tbl_leavecarryforwardhistory

-1 rows


Description

Module: HRMS Leave Management
Purpose: Maintains complete historical record of leave carry forward, lapse, and encashment operations performed during year-end processing.
Data: Stores annual leave balance adjustments including carried forward amounts, lapsed leaves, and encashed balances.
Process Usage:
- Tracks year-end leave balance processing for compliance and audit purposes.
- Provides historical data for employee queries and dispute resolution.
- Supports reporting on leave utilization patterns over multiple years.
Key Points:
- Captures multiple carry forward scenarios (regular, tenure-based, with expiry).
- Maintains separate tracking for lapsed and encashed leave balances.
Business Impact: Essential for financial auditing, compliance reporting, and transparent leave balance management.

Columns

Column Type Size Nulls Auto Default Children Parents Comments
id bigserial 19 √ nextval('tbl_leavecarryforwardhistory_id_seq'::regclass)

Primary key
Format: BigSerial (auto-increment)
Used as: Unique identifier for each carry forward history record.
employeeid varchar 500 √ null
tbl_employee.employeeid Implied Constraint R

FK: public.tbl_employee.employeeid
Meaning: Employee for whom carry forward processing was performed.
Usage: Links history to specific employee record.
leavecode varchar 50 √ null

Leave type being processed
Format: String
Examples: “PL” (Privilege Leave), “CL” (Casual Leave)
Usage: Identifies which leave balance was subject to carry forward rules.
month int4 10 √ null

Month when carry forward processing occurred
Format: Integer (1-12)
Usage: Typically the year-end closing month (December for Calendar Year, March for Financial Year).
year int4 10 √ null

Year when carry forward processing occurred
Format: Integer (4-digit year)
Usage: The closing year for which balances are being carried forward.
carryoverexpirymonth int4 10 √ null

Scheduled expiry month for carried forward leaves
Format: Integer (1-12)
Usage: For policies with expiry, indicates when unused carried leaves will lapse.
Example: If carryOverExpiryMonth=6, carried leaves expire at end of June next year.
carryoverexpiryyear int4 10 √ null

Scheduled expiry year for carried forward leaves
Format: Integer (4-digit year)
Usage: The year when carried leaves are scheduled to expire.
companyid int8 19 √ null
openingbalance numeric 0 √ null
closingbalance numeric 0 √ null
carryforwardleave numeric 0 √ null
lapsleave numeric 0 √ null
lapsedtenure numeric 0 √ null
encashed numeric 0 √ null
encashedtenure numeric 0 √ null
carryovertype varchar 50 √ null

Type of carry forward processing performed
Format: String
Values: “CARRY_OVER_YEARLY”, “CARRY_OVER_YEARLY_TENURE”, “CARRY_OVER_CYCLE”
CARRY_OVER_YEARLY: Standard annual carry forward with ACCUMALATE cycle config
CARRY_OVER_YEARLY_TENURE: Carry forward with tenure-based limits (CARRY_OVER_WITH_TENURE_LIMIT)
CARRY_OVER_CYCLE: Cycle-based processing (non-accumalation scenarios)
Usage: Indicates which carry forward scenario was applied based on policy CarryOverCycleConfig and CarryOverYearlyConfig.
leavepolicyid int8 19 √ null

FK: public.tbl_leavecodepolicyconfig.id
Meaning: Policy that governed the carry forward rules for this processing.
Usage: References the specific policy configuration applied during year-end processing.
createdby varchar 50 √ null
createddate timestamp 29,6 √ null
modifiedby varchar 50 √ null
modifieddate timestamp 29,6 √ null

Indexes

Constraint Name Type Sort Column(s)
pk_tbl_leavecarryforwardhistory_id Primary key Asc id

Relationships

Close relationships within degrees of separation