Please enable JavaScript to view this site.

Made in EU
Odoo Forums

Navigation: Schema: hr > Tables

salary_rule

Salary Rule

Catalog: Odoo

Schema: hr

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 salary_rule are shown below. Each column has an SQL data type.

Name

Data Type

Label

Required

Documentation

account_credit_label

string

 

 

account_credit

string

 

 

account_debit_label

string

 

 

account_debit

string

 

 

active

boolean

Active

If the active field is set to false, it will allow you to hide the salary rule without removing it.

amount_fix

decimal

Fixed Amount

 

amount_percentage_base

string

Percentage based on

result will be affected to a variable

amount_percentage

decimal

Percentage (%)

For example, enter 50.0 to apply a percentage of 50%

amount_python_compute

string

Python Code

 

amount_select

string

Amount Type

The computation method for the rule amount.

analytic_account_id_label

string

 

 

analytic_account_id

string

 

 

appears_on_employee_cost_dashboard

boolean

View on Employer Cost Dashboard

Used to display the value in the employer cost dashboard.

appears_on_payroll_report

boolean

View on Payroll Reporting

 

appears_on_payslip

boolean

Appears on Payslip

Used to display the salary rule on payslip.

category_id_label

string

 

 

category_id

string

 

 

code

string

Code

The code of salary rules can be used as reference in computation of other rules. In that case, it is case sensitive.

condition_python

string

Python Condition

Applied this rule for calculation if condition is true. You can specify condition like basic > 1000.

condition_range_max

decimal

Maximum Range

The maximum amount, applied for this rule.

condition_range_min

decimal

Minimum Range

The minimum amount, applied for this rule.

condition_range

string

Range Based on

This will be used to compute the % fields values; in general it is on basic, but you can also use categories code fields in lowercase as a variable names (hra, ma, lta, etc.) and the variable basic.

condition_select

string

Condition Based on

 

create_date

datetime

Created on

 

create_uid_label

string

 

 

create_uid

string

 

 

display_name

string

Display Name

 

id

int32

ID

 

name

string

Name

 

not_computed_in_net

boolean

Not computed in net accountably

This field allows you to delete the value of this rule in the "Net Salary" rule at the accounting level to explicitly display the value of this rule in the accounting. For example, if you want to display the value of your representation fees, you can check this field.

note

string

Description

 

partner_id_label

string

 

Eventual third party involved in the salary payment of the employees.

partner_id

string

 

Eventual third party involved in the salary payment of the employees.

quantity

string

Quantity

It is used in computation for percentage and fixed amount. E.g. a rule for Meal Voucher having fixed amount of 1€ per worked day can have its quantity defined in expression like worked_days.WORK100.number_of_days.

sequence

int32

Sequence

Use to arrange calculation sequence

struct_id_label

string

 

 

struct_id

string

 

 

write_date

datetime

Last Updated on

 

write_uid_label

string

 

 

write_uid

string

 

 

 

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

X

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.

  
Disclaimer