Please enable JavaScript to view this site.

Made in EU
Odoo Forums

Navigation: Schema: stock > Tables

warehouse_orderpoint

Minimum Inventory Rule

Catalog: Odoo

Schema: stock

Documentation:

Defines Minimum stock rules.

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

Name

Data Type

Label

Required

Documentation

active

boolean

Active

If the active field is set to False, it will allow you to hide the orderpoint without removing it.

allowed_location_ids

string

 

 

bom_id_label

string

 

 

bom_id

string

 

 

company_id_label

string

 

 

company_id

string

 

 

create_date

datetime

Created on

 

create_uid_label

string

 

 

create_uid

string

 

 

days_to_order

decimal

Days To Order

Numbers of days in advance that replenishments demands are created.

display_name

string

Display Name

 

group_id_label

string

 

Moves created through this orderpoint will be put in this procurement group. If none is given, the moves generated by stock rules will be grouped into one big picking.

group_id

string

 

Moves created through this orderpoint will be put in this procurement group. If none is given, the moves generated by stock rules will be grouped into one big picking.

id

int32

ID

 

lead_days_date

datetime

Lead Days Date

 

location_id_label

string

 

 

location_id

string

 

 

manufacturing_visibility_days

decimal

Manufacturing Visibility Days

Visibility Days applied on the manufacturing routes.

name

string

Name

 

product_category_id_label

string

 

 

product_category_id

string

 

 

product_id_label

string

 

 

product_id

string

 

 

product_max_qty

decimal

Max Quantity

When the virtual stock goes below the Min Quantity, Odoo generates a procurement to bring the forecasted quantity to the Quantity specified as Max Quantity.

product_min_qty

decimal

Min Quantity

When the virtual stock goes below the Min Quantity specified for this field, Odoo generates a procurement to bring the forecasted quantity to the Max Quantity.

product_tmpl_id_label

string

 

 

product_tmpl_id

string

 

 

product_uom_label

string

 

Default unit of measure used for all stock operations.

product_uom_name

string

Product unit of measure label

 

product_uom

string

 

Default unit of measure used for all stock operations.

purchase_visibility_days

decimal

Purchase Visibility Days

Visibility Days applied on the purchase routes.

qty_forecast

decimal

Forecast

 

qty_multiple

decimal

Multiple Quantity

The procurement quantity will be rounded up to this multiple. If it is 0, the exact quantity will be used.

qty_on_hand

decimal

On Hand

 

qty_to_order

decimal

To Order

 

route_id_label

string

 

 

route_id

string

 

 

rule_ids

string

 

 

show_bom

boolean

Show BoM column

 

show_supplier

boolean

Show supplier column

 

snoozed_until

datetime

Snoozed

Hidden until next scheduler.

supplier_id_label

string

 

 

supplier_id

string

 

 

trigger

string

Trigger

 

vendor_id_label

string

 

 

vendor_id

string

 

 

visibility_days

decimal

Visibility Days

Consider product forecast these many days in the future upon product replenishment, set to 0 for just-in-time.The value depends on the type of the route (Buy or Manufacture)

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