Navigation: Schema: hr > Tables

leave_allocation

Time Off Allocation

Catalog: Odoo

Schema: hr

Documentation:

Allocation Requests Access specifications: similar to leave requests

The data in this table is partitioned per value of the column.

This is a read-only table. The Odoo API may not support changing the data or the Invantive SQL driver for Odoo does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the Odoo API.

Table Columns

The columns of the table leave_allocation are shown below. Each column has an SQL data type.

Name	Data Type	Label	Required	Documentation
accrual_plan_id_label	string		☐
accrual_plan_id	string		☐
active_employee	boolean	Active Employee	☐	If the active field is set to False, it will allow you to hide the resource record without removing it.
active	boolean	Active	☐
activity_calendar_event_id_label	string		☐
activity_calendar_event_id	string		☐
activity_date_deadline	datetime	Next Activity Deadline	☐
activity_exception_decoration	string	Activity Exception Decoration	☐	Type of the exception activity on record.
activity_exception_icon	string	Icon	☐	Icon to indicate an exception activity.
activity_ids	string		☐
activity_state	string	Activity State	☐	Status based on activitiesOverdue: Due date is already passedToday: Activity date is todayPlanned: Future activities.
activity_summary	string	Next Activity Summary	☐
activity_type_icon	string	Activity Type Icon	☐	Font awesome icon e.g. fa-tasks
activity_type_id_label	string		☐
activity_type_id	string		☐
activity_user_id_label	string		☐
activity_user_id	string		☐
allocation_type	string	Allocation Type	☑
approver_id_label	string		☐	This area is automatically filled by the user who validates the allocation
approver_id	string		☐	This area is automatically filled by the user who validates the allocation
can_approve	boolean	Can Approve	☐
can_reset	boolean	Can reset	☐
category_id_label	string		☐
category_id	string		☐
create_date	datetime	Created on	☐
create_uid_label	string		☐
create_uid	string		☐
date_from	datetime	Start Date	☑
date_to	datetime	End Date	☐
department_id_label	string		☐
department_id	string		☐
display_name	string	Display Name	☐
duration_display	string	Allocated (Days/Hours)	☐	Field allowing to see the allocation duration in days or hours depending on the type_request_unit
employee_company_id_label	string		☐
employee_company_id	string		☐
employee_id_label	string		☐
employee_id	string		☐
employee_ids	string		☐
employee_overtime	decimal	Total Overtime	☐
has_message	boolean	Has Message	☐
holiday_status_id_label	string		☐
holiday_status_id	string		☐
holiday_type	string	Allocation Mode	☑	Allow to create requests in batchs:- By Employee: for a specific employee- By Company: all employees of the specified company- By Department: all employees of the specified department- By Employee Tag: all employees of the specific employee group category
hr_attendance_overtime	boolean	Count Extra Hours	☐
id	int32	ID	☐
is_officer	boolean	Is Officer	☐
lastcall	datetime	Date of the last accrual allocation	☐
leaves_taken	decimal	Time off Taken	☐
linked_request_ids	string		☐
manager_id_label	string		☐
manager_id	string		☐
max_leaves	decimal	Max Leaves	☐
message_attachment_count	int32	Attachment Count	☐
message_follower_ids	string		☐
message_has_error_counter	int32	Number of errors	☐	Number of messages with delivery error
message_has_error	boolean	Message Delivery error	☐	If checked, some messages have a delivery error.
message_has_sms_error	boolean	SMS Delivery error	☐	If checked, some messages have a delivery error.
message_ids	string		☐
message_is_follower	boolean	Is Follower	☐
message_main_attachment_id_label	string		☐
message_main_attachment_id	string		☐
message_needaction_counter	int32	Number of Actions	☐	Number of messages which requires an action
message_needaction	boolean	Action Needed	☐	If checked, new messages require your attention.
message_partner_ids	string		☐
mode_company_id_label	string		☐
mode_company_id	string		☐
multi_employee	boolean	Multi Employee	☐	Holds whether this allocation concerns more than 1 employee
my_activity_date_deadline	datetime	My Activity Deadline	☐
name_validity	string	Description with validity	☐
name	string	Description	☐
nextcall	datetime	Date of the next accrual allocation	☐
notes	string	Reasons	☐
number_of_days_display	decimal	Duration (days)	☐	If Accrual Allocation: Number of days allocated in addition to the ones you will get via the accrual' system.
number_of_days	decimal	Number of Days	☐	Duration in days. Reference field to use when necessary.
number_of_hours_display	decimal	Duration (hours)	☐	If Accrual Allocation: Number of hours allocated in addition to the ones you will get via the accrual' system.
overtime_deductible	boolean	Overtime Deductible	☐
overtime_id_label	string		☐
overtime_id	string		☐
parent_id_label	string		☐
parent_id	string		☐
private_name	string	Allocation Description	☐
state	string	Status	☐	The status is set to 'To Submit', when an allocation request is created.The status is 'To Approve', when an allocation request is confirmed by user.The status is 'Refused', when an allocation request is refused by manager.The status is 'Approved', when an allocation request is approved by manager.
taken_leave_ids	string		☐
type_request_unit	string	Take Time Off in	☐
validation_type	string	Validation Type	☐	Select the level of approval needed in case of request by employee- No validation needed: The employee's request is automatically approved.- Approved by Time Off Officer: The employee's request need to be manually approved by the Time Off Officer.
website_message_ids	string		☐	Website communication history
write_date	datetime	Last Updated on	☐
write_uid_label	string		☐
write_uid	string		☐

01-03-2023 15:29 Version 22.1.135-BETA+3826

Important Safety and Usage Information

Intended Use and Limitations: This software, developed by Invantive, is designed to support a variety of business and information technology data processing functions, such as accounting, financial reporting an sales reporting. It is important to note that this software is not designed, tested, or approved for use in environments where malfunction or failure could lead to life-threatening situations or severe physical or environmental damage. This includes, but is not limited to:

Nuclear facilities: The software should not be used for operations or functions related to the control, maintenance, or operation of nuclear facilities.
Defense and Military Applications: This software is not suitable for use in defense-related applications, including but not limited to weaponry control, military strategy planning, or any other aspects of national defense.
Aviation: The software is not intended for use in the operation, navigation, or communication systems of any aircraft or air traffic control environments.
Healthcare and Medicine Production: This software should not be utilized for medical device operation, patient data analysis for critical health decisions, pharmaceutical production, or medical research where its failure or malfunction could impact patient health.
Chemical and Hazardous Material Handling: This software is not intended for the management, control, or operational aspects of chemical plants or hazardous material handling facilities. Any malfunction in software used in these settings could result in dangerous chemical spills, explosions, or environmental disasters.
Transportation and Traffic Control Systems: The software should not be used for the control, operation, or management of transportation systems, including railway signal controls, subway systems, or traffic light management. Malfunctions in such critical systems could lead to severe accidents and endanger public safety.
Energy Grid and Utility Control Systems: This software is not designed for the control or operation of energy grid systems, including electrical substations, renewable energy control systems, or water utility control systems. The failure of software in these areas could lead to significant power outages, water supply disruptions, or other public utility failures, potentially endangering communities and causing extensive damage.
Other High-Risk Environments: Any other critical infrastructure and environments where a failure of the software could result in significant harm to individuals or the environment.

User Responsibility: Users must ensure that they understand the intended use of the software and refrain from deploying it in any setting that falls outside of its designed purpose. It is the responsibility of the user to assess the suitability of the software for their intended application, especially in any scenarios that might pose a risk to life, health, or the environment.

Disclaimer of Liability: Invantive disclaims any responsibility for damage, injury, or legal consequences resulting from the use or misuse of this software in prohibited or unintended applications.

Please enable JavaScript to view this site.

Odoo API Data Model

leave_allocation

Table Columns

Important Safety and Usage Information