Please enable JavaScript to view this site.

Made in EU
Odoo Forums

Navigation: Schema: stock > Tables

rule

Stock Rule

Catalog: Odoo

Schema: stock

Documentation:

A rule describe what a procurement should do; produce, buy, move, ...

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

Name

Data Type

Label

Required

Documentation

action

string

Action

 

active

boolean

Active

If unchecked, it will allow you to hide the rule without removing it.

auto

string

Automatic Move

The 'Manual Operation' value will create a stock move after the current one. With 'Automatic No Step Added', the location is replaced in the original move.

company_id_label

string

 

 

company_id

string

 

 

create_date

datetime

Created on

 

create_uid_label

string

 

 

create_uid

string

 

 

delay

int32

Lead Time

The expected date of the created transfer will be computed based on this lead time.

display_name

string

Display Name

 

group_id_label

string

 

 

group_id

string

 

 

group_propagation_option

string

Propagation of Procurement Group

 

id

int32

ID

 

location_dest_id_label

string

 

 

location_dest_id

string

 

 

location_src_id_label

string

 

 

location_src_id

string

 

 

name

string

Name

This field will fill the packing origin and the name of its moves

partner_address_id_label

string

 

Address where goods should be delivered. Optional.

partner_address_id

string

 

Address where goods should be delivered. Optional.

picking_type_code_domain

string

Picking Type Code Domain

 

picking_type_id_label

string

 

 

picking_type_id

string

 

 

procure_method

string

Supply Method

Take From Stock: the products will be taken from the available stock of the source location.Trigger Another Rule: the system will try to find a stock rule to bring the products in the source location. The available stock will be ignored.Take From Stock, if Unavailable, Trigger Another Rule: the products will be taken from the available stock of the source location.If there is no stock available, the system will try to find a rule to bring the products in the source location.

propagate_cancel

boolean

Cancel Next Move

When ticked, if the move created by this rule is cancelled, the next move will be cancelled too.

propagate_carrier

boolean

Propagation of carrier

When ticked, carrier of shipment will be propagated.

propagate_warehouse_id_label

string

 

The warehouse to propagate on the created move/procurement, which can be different of the warehouse this rule is for (e.g for resupplying rules from another warehouse)

propagate_warehouse_id

string

 

The warehouse to propagate on the created move/procurement, which can be different of the warehouse this rule is for (e.g for resupplying rules from another warehouse)

route_company_id_label

string

 

Leave this field empty if this route is shared between all companies

route_company_id

string

 

Leave this field empty if this route is shared between all companies

route_id_label

string

 

 

route_id

string

 

 

route_sequence

int32

Route Sequence

 

rule_message

string

Rule Message

 

sequence

int32

Sequence

 

warehouse_id_label

string

 

 

warehouse_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