tbl_assets_type_employee_mapping

-1 rows


Description

Module: Asset Management - Asset Type to Employee Eligibility Mapping
Purpose: Stores the rules defining which specific asset types (e.g., Laptop, Desk Phone, Company Car) are allocated, available to, or authorized for an individual employee.
Data: Captures a mapping between a specific Asset Type ID and an Employee ID.
Process Usage:
- Authorization/Eligibility: Used during asset allocation or request processes to validate if a given employee is allowed to possess or request an asset of a particular type.
- Default Allocation: May be used to pre-define the standard set of assets an employee should receive upon joining (e.g., all new hires get a “Standard Laptop” asset type).
Key Points:
- Many-to-Many Relationship: An employee can be mapped to multiple asset types, and an asset type can be mapped to many employees.
- Acts as a dynamic eligibility check rather than a static allocation record.
Business Impact: Ensures controlled distribution of company resources and streamlines the onboarding/asset request process by enforcing eligibility rules.

Columns

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

Primary key
Format: Long (auto-increment)
Used as: Unique identifier for this specific asset type-employee eligibility mapping record.
asset_type_id int8 19 null

FK: public.tbl_asset_type.id (Implied)
Meaning: The ID of the specific type of asset (e.g., Laptop, Mobile Phone) to which the employee is mapped.
employee_id varchar 100 null

FK: public.tbl_employee.employeeid
Meaning: The Employee ID who is eligible for or mapped to this asset type.
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_assets_type_employee_mapping Primary key Asc id

Relationships

Close relationships within degrees of separation