What data types are used in crossovered_budget? or What columns have default values in crossovered_budget?

Response: Columns in crossovered_budget: id (integer) [NOT NULL] [DEFAULT: nextval('crossovered_budget_id_seq'::regclass)] [PRECISION: 32]; message_main_attachment_id (integer) [PRECISION: 32] [COMMENT: Main Attachment]; name (character varying) [NOT NULL] [COMMENT: Budget Name]; user_id (integer) [PRECISION: 32] [COMMENT: Responsible]; date_from (date) [NOT NULL] [COMMENT: Start Date]; date_to (date) [NOT NULL] [COMMENT: End Date]; state (character varying) [NOT NULL] [COMMENT: Status]; company_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Company]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]; request_partner_id (integer) [PRECISION: 32] [COMMENT: Requested Partner]; currency_id (integer) [PRECISION: 32] [COMMENT: Currency]; complete_name (character varying) [COMMENT: Complete Name]; parent_id (integer) [PRECISION: 32] [COMMENT: Parent Budget]; branch_id (integer) [PRECISION: 32] [COMMENT: Branch]; is_parent_budget (boolean) [COMMENT: Is Parent Budget]; date_today (date) [COMMENT: Today Date]. Total columns: 19. Statistics: 13 nullable, 1 with defaults, 0 with length constraints.


What indexes exist on account_payment_res_partner_bank_rel? or Describe the account_payment_res_partner_bank_rel table structure.

Response: The account_payment_res_partner_bank_rel table has 2 columns and 2 foreign key relationships. It stores data related to account payment res partner bank rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


What columns does ir_default have? or What indexes exist on ir_default?

Response: The ir_default table has 10 columns and 5 foreign key relationships. It stores data related to ir default in the system. The table has 4 indexes for performance optimization. Column types: integer: 6, character varying: 2, timestamp without time zone: 2. Nullable columns: 7, columns with defaults: 1.


What data types are used in purchase_request_revision_request_rel? or Which columns are nullable in purchase_request_revision_request_rel?

Response: Columns in purchase_request_revision_request_rel: pr_id (integer) [NOT NULL] [PRECISION: 32]; revision_id (integer) [NOT NULL] [PRECISION: 32]. Total columns: 2. Statistics: 0 nullable, 0 with defaults, 0 with length constraints.


What are the relationships in kpi.period.value? or List all relational fields in kpi.period.value.

Response: The kpi.period.value model has 4 relational fields: period_id -> kpi.period; constant_id -> kpi.constant; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


Describe the implementation of ai.agent.config. or Which fields are stored computed fields in ai.agent.config?

Response: The ai.agent.config model is defined in module: ai_chat_agent. It has 11 computed fields: model_info, full_system_prompt, total_sessions, total_messages, max_input_tokens, max_output_tokens, is_support_vision, is_support_pdf_input, mode, display_name, __last_update. Stored computed fields: model_info, max_input_tokens, max_output_tokens, is_support_vision, is_support_pdf_input, mode. Related fields: none. Original module methods: _get_default_utility_model, get_postgresql_version, _generate_compiled_system_prompt, _compute_full_system_prompt, _compute_model_info, _get_openrouter_model_info, _get_vertex_ai_model_info, _check_compress_model, _check_temperature, _check_trim_ratio, _check_compression_threshold, get_max_tokens_for_compression, _check_default_unique, _onchange_provider, _onchange_is_fine_tuned_model, get_full_model_name, _get_model_options, _fetch_models_with_litellm, _fetch_openrouter_models, _fetch_vertex_ai_models, get_litellm_chat_params, get_available_models, get_available_base_models, action_refresh_models, get_models_for_provider_secure, _compute_statistics, get_default_config, get_quick_chat_config, set_as_quick_chat_default, _check_quick_chat_default_unique, _check_provider_config, test_connection, _test_litellm_connection, _test_openrouter_connection, _setup_vertex_ai_credentials, _test_vertex_ai_connection, action_test_connection, action_select_model, action_open_chat_interface, get_enabled_tools, is_tool_enabled, action_enable_all_tools, action_disable_all_tools.


How do I use the crm.lead.lost model? or How to work with crm.lead.lost fields?

Response: To use the crm.lead.lost model, you need to provide values for required fields: none. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


What methods are available in milestone.contract.template.line? or Describe the implementation of milestone.contract.template.line.

Response: The milestone.contract.template.line model is defined in module: equip3_purchase_operation. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: .


Describe the acrux_chat_conversation table structure. or Tell me about the acrux_chat_conversation table.

Response: The acrux_chat_conversation table has 23 columns and 8 foreign key relationships. It stores data related to acrux chat conversation in the system. The table has 1 indexes for performance optimization. Column types: integer: 9, character varying: 8, timestamp without time zone: 5, boolean: 1. Nullable columns: 17, columns with defaults: 1.


What columns does purchase_flow_asset have? or Explain the purchase_flow_asset table schema.

Response: The purchase_flow_asset table has 6 columns and 2 foreign key relationships. It stores data related to purchase flow asset in the system. The table has 1 indexes for performance optimization. Column types: integer: 3, character varying: 1, timestamp without time zone: 2. Nullable columns: 5, columns with defaults: 1.


Explain the coupon_generate_wizard table schema. or How many columns are in coupon_generate_wizard?

Response: The coupon_generate_wizard table has 8 columns and 2 foreign key relationships. It stores data related to coupon generate wizard in the system. The table has 1 indexes for performance optimization. Column types: integer: 4, character varying: 2, timestamp without time zone: 2. Nullable columns: 7, columns with defaults: 1.


How do I use the stock.valuation.adjustment.lines model? or What business logic is in stock.valuation.adjustment.lines?

Response: To use the stock.valuation.adjustment.lines model, you need to provide values for required fields: cost_id, product_id, quantity. Readonly fields: name, cost_line_id, move_id, final_cost, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [readonly] [computed] [no_copy]; cost_id [required]; cost_line_id [readonly]; move_id [readonly]; product_id [required]; quantity [required] [has_default]; final_cost [readonly] [computed] [no_copy]; currency_id [readonly] [computed] [no_copy]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


What one2many fields are in kpi.copy.template? or What foreign keys exist in kpi.copy.template?

Response: The kpi.copy.template model has 4 relational fields: period_id -> kpi.period; template_id -> kpi.period; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


Explain the res_partner_sh_sale_invoice_summary_wizard_rel table schema. or Tell me about the res_partner_sh_sale_invoice_summary_wizard_rel table.

Response: The res_partner_sh_sale_invoice_summary_wizard_rel table has 2 columns and 2 foreign key relationships. It stores data related to res partner sh sale invoice summary wizard rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


What foreign keys exist in stock.inventory? or What models are connected to stock.inventory?

Response: The stock.inventory model has 32 relational fields: line_ids -> stock.inventory.line; move_ids -> stock.move; company_id -> res.company; product_ids -> product.product; warehouse_id -> stock.warehouse; user_id -> res.users; adjustment_account_id -> account.account; filtered_adjustment_account_id -> account.account; analytic_tag_ids -> account.analytic.tag; branch_id -> res.branch; approval_matrix_id -> stock.inventory.approval.matrix; approved_matrix_ids -> stock.inventory.approval.matrix.line; approval_matrix_line_id -> stock.inventory.approval.matrix.line; product_categories -> product.category; location_ids -> stock.location; uom_conversion_ids -> uom.conversion.history; wizard_id -> stock.inventory.wizard; pos_branch_id -> res.branch; account_move_ids -> account.move; user_id_1 -> res.users; user_id_2 -> res.users; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: product_ids, filtered_adjustment_account_id, analytic_tag_ids, product_categories, location_ids, message_partner_ids, message_channel_ids. One2many fields: line_ids, move_ids, approved_matrix_ids, uom_conversion_ids, account_move_ids, activity_ids, message_follower_ids, message_ids, website_message_ids.


What is the module hierarchy for crm.lead.lost? or Which fields are stored computed fields in crm.lead.lost?

Response: The crm.lead.lost model is defined in module: crm. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: action_lost_reason_apply.


List all constraint names in account_debit_note. or What tables are connected to account_debit_note?

Response: Foreign keys in account_debit_note: create_uid -> res_users.id [constraint: account_debit_note_create_uid_fkey]; journal_id -> account_journal.id [constraint: account_debit_note_journal_id_fkey]; write_uid -> res_users.id [constraint: account_debit_note_write_uid_fkey]. Total foreign key relationships: 3. Referenced tables: res_users, account_journal.


How to create records in return.approval.matrix? or What fields are readonly in return.approval.matrix?

Response: To use the return.approval.matrix model, you need to provide values for required fields: name. Readonly fields: create_date, create_uid, id, display_name, write_uid, write_date, __last_update. Field usage details: name [required]; create_date [readonly]; create_uid [readonly]; id [readonly]; display_name [readonly] [computed] [no_copy]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


How to create records in sale.adv.wizard.product.line? or What fields are readonly in sale.adv.wizard.product.line?

Response: To use the sale.adv.wizard.product.line model, you need to provide values for required fields: none. Readonly fields: default_code, standard_price, uom_po_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: default_code [readonly] [computed] [no_copy]; standard_price [readonly] [computed] [no_copy]; uom_po_id [readonly] [computed] [no_copy]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


What does the import.pricelist.wizard model represent? or Describe the import.pricelist.wizard model in Odoo.

Response: The import.pricelist.wizard model represents import.pricelist.wizard in the ERP system. It contains 10 fields and is used to manage import.pricelist.wizard data. Defined in module: equip3_pos_general. Key fields include: name, file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Describe the columns of sh_mrp_correct_qc_measurement. or What columns have default values in sh_mrp_correct_qc_measurement?

Response: Columns in sh_mrp_correct_qc_measurement: id (integer) [NOT NULL] [DEFAULT: nextval('sh_mrp_correct_qc_measurement_id_seq'::regclass)] [PRECISION: 32]; product_id (integer) [PRECISION: 32] [COMMENT: Product]; sh_measure (double precision) [PRECISION: 53] [COMMENT: Measure]; sh_message (text) [COMMENT: Message]; sh_text (text) [COMMENT: Measurement Message]; sh_quality_point_id (integer) [PRECISION: 32] [COMMENT: Quality Control Point]; mrp_id (integer) [PRECISION: 32] [COMMENT: Manufacturing]; workorder_id (integer) [PRECISION: 32] [COMMENT: Work Order]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 12. Statistics: 11 nullable, 1 with defaults, 0 with length constraints.


What columns does pos_promotion_discount_order have? or What is the pos_promotion_discount_order table?

Response: The pos_promotion_discount_order table has 13 columns and 3 foreign key relationships. It stores data related to pos promotion discount order in the system. The table has 1 indexes for performance optimization. Column types: integer: 4, boolean: 1, double precision: 5, character varying: 1, timestamp without time zone: 2. Nullable columns: 11, columns with defaults: 1.


What modules define format.address.mixin? or What are the technical details of format.address.mixin?

Response: The format.address.mixin model is defined in module: base. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: _fields_view_get_address, create.


How many columns are in account_journal_account_pettycash_analysis_rel? or What indexes exist on account_journal_account_pettycash_analysis_rel?

Response: The account_journal_account_pettycash_analysis_rel table has 2 columns and 2 foreign key relationships. It stores data related to account journal account pettycash analysis rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


List all constraint names in sh_custom_field_model. or What relationships exist for sh_custom_field_model?

Response: Foreign keys in sh_custom_field_model: create_uid -> res_users.id [constraint: sh_custom_field_model_create_uid_fkey]; inherit_view_obj -> ir_ui_view.id [constraint: sh_custom_field_model_inherit_view_obj_fkey]; ir_model_fields_obj -> ir_model_fields.id [constraint: sh_custom_field_model_ir_model_fields_obj_fkey]; ir_ui_view_obj -> ir_ui_view.id [constraint: sh_custom_field_model_ir_ui_view_obj_fkey]; model_id -> ir_model.id [constraint: sh_custom_field_model_model_id_fkey]; parent_view_id -> ir_ui_view.id [constraint: sh_custom_field_model_parent_view_id_fkey]; ref_model_id -> ir_model.id [constraint: sh_custom_field_model_ref_model_id_fkey]; related_field_id -> ir_model_fields.id [constraint: sh_custom_field_model_related_field_id_fkey]; relation_field_id -> ir_model_fields.id [constraint: sh_custom_field_model_relation_field_id_fkey]; serialization_field_id -> ir_model_fields.id [constraint: sh_custom_field_model_serialization_field_id_fkey]; sh_position_field -> ir_model_fields.id [constraint: sh_custom_field_model_sh_position_field_fkey]; write_uid -> res_users.id [constraint: sh_custom_field_model_write_uid_fkey]. Total foreign key relationships: 12. Referenced tables: ir_model, ir_ui_view, res_users, ir_model_fields.


What operations can I perform on report.equip3_inventory_masterdata.report_product_forecast? or What are common use cases for report.equip3_inventory_masterdata.report_product_forecast?

Response: To use the report.equip3_inventory_masterdata.report_product_forecast model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. Field usage details: id [readonly]; display_name [readonly] [computed] [no_copy]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


How many columns are in pos_config_users_void_order_line_rel? or What indexes exist on pos_config_users_void_order_line_rel?

Response: The pos_config_users_void_order_line_rel table has 2 columns and 2 foreign key relationships. It stores data related to pos config users void order line rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


What computed fields exist in ir.model.data? or What are the available fields for ir.model.data?

Response: The ir.model.data model has 14 fields. Field types distribution: char: 6, many2one_reference: 1, boolean: 1, integer: 1, many2one: 2, datetime: 3. Computed fields: 4. Field details: name (char) [required] [module: base]; complete_name (char) [readonly] [compute: _compute_complete_name] [not stored] [module: base]; model (char) [required] [module: base]; module (char) [required] [module: base]; res_id (many2one_reference) [module: base]; noupdate (boolean) [module: base]; reference (char) [readonly] [compute: _compute_reference] [not stored] [module: base]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


What operations can I perform on product.template.attribute.line? or How to work with product.template.attribute.line fields?

Response: To use the product.template.attribute.line model, you need to provide values for required fields: product_tmpl_id, attribute_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: product_tmpl_id [required]; attribute_id [required]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


What foreign keys exist in pos.sale.analytic? or What are the relationships in pos.sale.analytic?

Response: The pos.sale.analytic model has 7 relational fields: user_id -> res.users; product_id -> product.product; product_categ_id -> product.category; pos_categ_id -> pos.category; product_tmpl_id -> product.template; company_id -> res.company; pos_branch_id -> res.branch. Many2many fields: none. One2many fields: none.


What computed fields exist in ir.qweb.field.text? or What are the available fields for ir.qweb.field.text?

Response: The ir.qweb.field.text model has 3 fields. Field types distribution: integer: 1, char: 1, datetime: 1. Computed fields: 2. Field details: id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field] [not stored] [module: None].


What fields are available in account_journal_outbound_payment_method_rel? or What are the length constraints in account_journal_outbound_payment_method_rel?

Response: Columns in account_journal_outbound_payment_method_rel: journal_id (integer) [NOT NULL] [PRECISION: 32]; outbound_payment_method (integer) [NOT NULL] [PRECISION: 32]. Total columns: 2. Statistics: 0 nullable, 0 with defaults, 0 with length constraints.


What one2many fields are in initial.balance.line? or List all relational fields in initial.balance.line.

Response: The initial.balance.line model has 6 relational fields: account_id -> account.account; company_id -> res.company; currency_id -> res.currency; period_id -> sh.account.period; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


Which fields in account.petty.cash.report are computed? or Which fields are stored computed fields in account.petty.cash.report?

Response: The account.petty.cash.report model is defined in module: equip3_accounting_reports. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: init, _select, _from, _group_by.


Which fields are stored computed fields in pos.cash.in.out? or What methods are defined in pos.cash.in.out original module?

Response: The pos.cash.in.out model is defined in module: equip3_pos_cashbox. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: _prepare_journal_for_cash_management.


Describe the field structure of purchase.price.history. or What computed fields exist in purchase.price.history?

Response: The purchase.price.history model has 16 fields. Field types distribution: many2one: 7, datetime: 4, float: 2, monetary: 1, integer: 1, char: 1. Computed fields: 10. Field details: name (many2one) -> purchase.order.line [module: sh_all_in_one_purchase_tools]; partner_id (many2one) [readonly] -> res.partner [compute: <bound method Field._compute_related of purchase.price.history.partner_id>] [not stored] [module: sh_all_in_one_purchase_tools] [related: name.partner_id]; variant_id (many2one) [readonly] -> product.product [compute: <bound method Field._compute_related of purchase.price.history.variant_id>] [not stored] [module: sh_all_in_one_purchase_tools] [related: name.product_id]; purchase_order_id (many2one) [readonly] -> purchase.order [compute: <bound method Field._compute_related of purchase.price.history.purchase_order_id>] [not stored] [module: sh_all_in_one_purchase_tools] [related: name.order_id]; order_date (datetime) [readonly] [compute: <bound method Field._compute_related of purchase.price.history.order_date>] [not stored] [module: sh_all_in_one_purchase_tools] [related: name.order_id.date_order]; quantity (float) [readonly] [compute: <bound method Field._compute_related of purchase.price.history.quantity>] [not stored] [module: sh_all_in_one_purchase_tools] [related: name.product_qty]; purchase_price (float) [readonly] [compute: <bound method Field._compute_related of purchase.price.history.purchase_price>] [not stored] [module: sh_all_in_one_purchase_tools] [related: name.price_unit]; currency_id (many2one) [readonly] -> res.currency [compute: <bound method Field._compute_related of purchase.price.history.currency_id>] [not stored] [module: sh_all_in_one_purchase_tools] [related: name.currency_id]; total_price (monetary) [readonly] [compute: <bound method Field._compute_related of purchase.price.history.total_price>] [not stored] [module: sh_all_in_one_purchase_tools] [related: name.price_subtotal]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


What is the mrp_production_production_rel table? or Explain the mrp_production_production_rel table schema.

Response: The mrp_production_production_rel table has 2 columns and 2 foreign key relationships. It stores data related to mrp production production rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


Show me the column structure of web_editor_converter_test. or List all columns in web_editor_converter_test.

Response: Columns in web_editor_converter_test: id (integer) [NOT NULL] [DEFAULT: nextval('web_editor_converter_test_id_seq'::regclass)] [PRECISION: 32]; char (character varying) [COMMENT: Char]; integer (integer) [PRECISION: 32] [COMMENT: Integer]; float (double precision) [PRECISION: 53] [COMMENT: Float]; numeric (numeric) [COMMENT: Numeric]; many2one (integer) [PRECISION: 32] [COMMENT: Many2One]; binary (bytea) [COMMENT: Binary]; date (date) [COMMENT: Date]; datetime (timestamp without time zone) [COMMENT: Datetime]; selection_str (character varying) [COMMENT: Lorsqu'un pancake prend l'avion à destination de Toronto et qu'il fait une escale technique à St Claude, on dit:]; html (text) [COMMENT: Html]; text (text) [COMMENT: Text]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 16. Statistics: 15 nullable, 1 with defaults, 0 with length constraints.


What tables are connected to mail_followers_mail_message_subtype_rel? or What tables does mail_followers_mail_message_subtype_rel reference?

Response: Foreign keys in mail_followers_mail_message_subtype_rel: mail_message_subtype_id -> mail_message_subtype.id [constraint: mail_followers_mail_message_subtyp_mail_message_subtype_id_fkey]; mail_followers_id -> mail_followers.id [constraint: mail_followers_mail_message_subtype_rel_mail_followers_id_fkey]. Total foreign key relationships: 2. Referenced tables: mail_message_subtype, mail_followers.


Can you explain the purpose of purchase.requisition? or What is the purchase.requisition model?

Response: The purchase.requisition model represents Purchase Requisition in the ERP system. It contains 79 fields and is used to manage purchase requisition data. Defined in module: purchase_requisition. Key fields include: name, origin, order_count, ordering_date, user_id, description, company_id, purchase_ids, line_ids, product_id, is_quantity_copy, currency_id, warehouse_id, picking_type_id, purchase_id, type_id, purchase_request_id, branch_id, account_tag_ids, analytic_accounting, destination_warehouse, date_end, schedule_date, set_single_delivery_date, set_single_delivery_destination, approval_matrix_id, is_blanket_order_approval_matrix, approved_matrix_ids, approval_matrix_line_id, is_approve_button, state, bo_state, bo_state1, state1, state2, bo_state2, state_blanket_order, partner_id, is_bo_confirm, vendor_id, show_analytic_tags, is_goods_orders, is_services_orders, is_assets_orders, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, access_url, access_token, access_warning, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How to work with cluster.warehouse.line fields? or How do I use the cluster.warehouse.line model?

Response: To use the cluster.warehouse.line model, you need to provide values for required fields: none. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


What data can be stored in crm.merge.opportunity? or List all fields in the crm.merge.opportunity model.

Response: The crm.merge.opportunity model has 10 fields. Field types distribution: many2many: 1, many2one: 4, integer: 1, char: 1, datetime: 3. Computed fields: 3. Field details: opportunity_ids (many2many) -> crm.lead [module: crm]; user_id (many2one) -> res.users [module: crm]; team_id (many2one) -> crm.team [compute: _compute_team_id] [stored] [module: crm]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


Describe the columns of account_reconcile_model_line_template. or What data types are used in account_reconcile_model_line_template?

Response: Columns in account_reconcile_model_line_template: id (integer) [NOT NULL] [DEFAULT: nextval('account_reconcile_model_line_template_id_seq'::regclass)] [PRECISION: 32]; model_id (integer) [PRECISION: 32] [COMMENT: Model]; sequence (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Sequence]; account_id (integer) [PRECISION: 32] [COMMENT: Account]; label (character varying) [COMMENT: Journal Item Label]; amount_type (character varying) [NOT NULL] [COMMENT: Amount Type]; amount_string (character varying) [COMMENT: Amount]; force_tax_included (boolean) [COMMENT: Tax Included in Price]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 12. Statistics: 9 nullable, 1 with defaults, 0 with length constraints.


Which fields are stored computed fields in mrp.consumption.warning.line? or How is mrp.consumption.warning.line implemented technically?

Response: The mrp.consumption.warning.line model is defined in module: mrp. It has 4 computed fields: consumption, product_uom_id, display_name, __last_update. Stored computed fields: none. Related fields: consumption -> mrp_production_id.consumption, product_uom_id -> product_id.uom_id. Original module methods: .


Show me the fields of limit.request.wizard. or Which fields are required in limit.request.wizard?

Response: The limit.request.wizard model has 7 fields. Field types distribution: integer: 1, char: 1, many2one: 2, datetime: 3. Computed fields: 2. Field details: id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


What columns does crm_phonecall2phonecall have? or Tell me about the crm_phonecall2phonecall table.

Response: The crm_phonecall2phonecall table has 14 columns and 5 foreign key relationships. It stores data related to crm phonecall2phonecall in the system. The table has 2 indexes for performance optimization. Column types: integer: 6, character varying: 4, timestamp without time zone: 3, text: 1. Nullable columns: 11, columns with defaults: 1.


What foreign keys exist in account.multipayment.difference? or What are the relationships in account.multipayment.difference?

Response: The account.multipayment.difference model has 6 relational fields: payment_id -> account.multipayment; account_id -> account.account; currency_id -> res.currency; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


How is account.loan.line implemented technically? or What modules define account.loan.line?

Response: The account.loan.line model is defined in module: account_loan. It has 12 computed fields: name, is_leasing, loan_type, loan_state, long_term_loan_account_id, currency_id, principal_amount, final_pending_principal_amount, has_moves, has_invoices, display_name, __last_update. Stored computed fields: loan_state. Related fields: is_leasing -> loan_id.is_leasing, loan_type -> loan_id.loan_type, loan_state -> loan_id.state, long_term_loan_account_id -> loan_id.long_term_loan_account_id, currency_id -> loan_id.currency_id. Original module methods: _compute_has_moves, _compute_has_invoices, _compute_name, _compute_amounts, compute_amount, check_amount, compute_interest, check_move_amount, move_vals, move_line_vals, invoice_vals, invoice_line_vals, generate_move, generate_invoice, _get_long_term_move_line_vals, view_account_values, view_process_values, view_account_moves, view_account_invoices.


How is res.bank used in the system? or What is the res.bank model?

Response: The res.bank model represents Bank in the ERP system. It contains 20 fields and is used to manage bank data. Defined in module: base. Key fields include: name, street, street2, zip, city, state, country, email, phone, active, bic, code, bank_provider, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Tell me about the budget_budget table. or What is stored in budget_budget?

Response: The budget_budget table has 14 columns and 6 foreign key relationships. It stores data related to budget budget in the system. The table has 4 indexes for performance optimization. Column types: integer: 7, character varying: 3, date: 2, timestamp without time zone: 2. Nullable columns: 8, columns with defaults: 1.


What computed fields exist in sh.tsp.top.selling.product? or List all fields in the sh.tsp.top.selling.product model.

Response: The sh.tsp.top.selling.product model has 9 fields. Field types distribution: many2one: 3, float: 1, integer: 1, char: 1, datetime: 3. Computed fields: 2. Field details: product_id (many2one) -> product.product [module: sh_sale_reports]; qty (float) [module: sh_sale_reports]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


Describe the relational structure of ai_chat_message. or List all constraint names in ai_chat_message.

Response: Foreign keys in ai_chat_message: create_uid -> res_users.id [constraint: ai_chat_message_create_uid_fkey]; session_id -> ai_chat_session.id [constraint: ai_chat_message_session_id_fkey]; user_id -> res_users.id [constraint: ai_chat_message_user_id_fkey]; write_uid -> res_users.id [constraint: ai_chat_message_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: ai_chat_session, res_users.


Describe the relational structure of purchase_requisition_type. or List all constraint names in purchase_requisition_type.

Response: Foreign keys in purchase_requisition_type: create_uid -> res_users.id [constraint: purchase_requisition_type_create_uid_fkey]; write_uid -> res_users.id [constraint: purchase_requisition_type_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


What models are connected to account.account.map.line? or What are the relationships in account.account.map.line?

Response: The account.account.map.line model has 11 relational fields: company_id -> res.company; account_id -> account.account; target_company -> res.company; target_account -> account.account; map_id -> account.account.map; create_uid -> res.users; write_uid -> res.users; line_ids -> account.account.map.line; child_company_id -> res.company; sales_line_ids -> account.tax.map.sales.line; purchase_line_ids -> account.tax.map.purchase.line. Many2many fields: none. One2many fields: line_ids, sales_line_ids, purchase_line_ids.


Tell me about the approval.matrix.vendor.reject model. or Can you explain the purpose of approval.matrix.vendor.reject?

Response: The approval.matrix.vendor.reject model represents approval.matrix.vendor.reject in the ERP system. It contains 8 fields and is used to manage approval.matrix.vendor.reject data. Defined in module: equip3_purchase_masterdata. Key fields include: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What tables does approval_matrix_purchase_agreement_line_res_users_rel reference? or Show me the foreign key constraints of approval_matrix_purchase_agreement_line_res_users_rel.

Response: Foreign keys in approval_matrix_purchase_agreement_line_res_users_rel: approval_matrix_purchase_agreement_line_id -> approval_matrix_purchase_agreement_line.id [constraint: approval_matrix_purchase_agre_approval_matrix_purchase_agr_fkey]; res_users_id -> res_users.id [constraint: approval_matrix_purchase_agreement_line_res__res_users_id_fkey1]; res_users_id -> res_users.id [constraint: approval_matrix_purchase_agreement_line_res__res_users_id_fkey2]; res_users_id -> res_users.id [constraint: approval_matrix_purchase_agreement_line_res__res_users_id_fkey3]; res_users_id -> res_users.id [constraint: approval_matrix_purchase_agreement_line_res__res_users_id_fkey4]; res_users_id -> res_users.id [constraint: approval_matrix_purchase_agreement_line_res__res_users_id_fkey5]; res_users_id -> res_users.id [constraint: approval_matrix_purchase_agreement_line_res__res_users_id_fkey6]; res_users_id -> res_users.id [constraint: approval_matrix_purchase_agreement_line_res__res_users_id_fkey7]; res_users_id -> res_users.id [constraint: approval_matrix_purchase_agreement_line_res_u_res_users_id_fkey]. Total foreign key relationships: 9. Referenced tables: approval_matrix_purchase_agreement_line, res_users.


What indexes exist on queue_job_queue_jobs_kill_rel? or What columns does queue_job_queue_jobs_kill_rel have?

Response: The queue_job_queue_jobs_kill_rel table has 2 columns and 2 foreign key relationships. It stores data related to queue job queue jobs kill rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


What tables are connected to asset_cip? or List all constraint names in asset_cip.

Response: Foreign keys in asset_cip: asset_category -> account_asset_category.id [constraint: asset_cip_asset_category_fkey]; branch_id -> res_branch.id [constraint: asset_cip_branch_id_fkey]; cip_account -> account_account.id [constraint: asset_cip_cip_account_fkey]; create_uid -> res_users.id [constraint: asset_cip_create_uid_fkey]; currency -> res_currency.id [constraint: asset_cip_currency_fkey]; move_id -> account_move.id [constraint: asset_cip_move_id_fkey]; write_uid -> res_users.id [constraint: asset_cip_write_uid_fkey]. Total foreign key relationships: 7. Referenced tables: account_account, res_currency, res_users, res_branch, account_asset_category, account_move.


How do I use the picking.order.line model? or What operations can I perform on picking.order.line?

Response: To use the picking.order.line model, you need to provide values for required fields: none. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


Can you explain the purpose of hour.group? or Tell me about the hour.group model.

Response: The hour.group model represents Hour Group in the ERP system. It contains 12 fields and is used to manage hour group data. Defined in module: equip3_pos_masterdata. Key fields include: name, start_hour, end_hour, active, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What one2many fields are in account.common.account.report? or What foreign keys exist in account.common.account.report?

Response: The account.common.account.report model has 5 relational fields: journal_ids -> account.journal; report_currency_id -> res.currency; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: journal_ids. One2many fields: none.


How many columns are in calendar_event? or Describe the calendar_event table structure.

Response: The calendar_event table has 49 columns and 11 foreign key relationships. It stores data related to calendar event in the system. The table has 4 indexes for performance optimization. Column types: integer: 15, character varying: 14, timestamp without time zone: 6, boolean: 8, date: 2, double precision: 1, text: 3. Nullable columns: 43, columns with defaults: 1.


How many columns are in calendar_event_type? or What is stored in calendar_event_type?

Response: The calendar_event_type table has 7 columns and 2 foreign key relationships. It stores data related to calendar event type in the system. The table has 2 indexes for performance optimization. Column types: integer: 3, character varying: 1, timestamp without time zone: 2, boolean: 1. Nullable columns: 5, columns with defaults: 1.


Tell me about the account_analytic_tag_account_asset_asset_rel table. or What columns does account_analytic_tag_account_asset_asset_rel have?

Response: The account_analytic_tag_account_asset_asset_rel table has 2 columns and 2 foreign key relationships. It stores data related to account analytic tag account asset asset rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


What one2many fields are in report.equip3_inventory_reports.expiring_product_calendar? or List all relational fields in report.equip3_inventory_reports.expiring_product_calendar.

Response: The report.equip3_inventory_reports.expiring_product_calendar model has no explicit relational fields defined in its field metadata.


What are the column types in product_product_target_kpi_rel? or Show me the column structure of product_product_target_kpi_rel.

Response: Columns in product_product_target_kpi_rel: target_kpi_id (integer) [NOT NULL] [PRECISION: 32]; product_product_id (integer) [NOT NULL] [PRECISION: 32]. Total columns: 2. Statistics: 0 nullable, 0 with defaults, 0 with length constraints.


Describe the implementation of ir.qweb.field.date. or What methods are available in ir.qweb.field.date?

Response: The ir.qweb.field.date model is defined in module: base. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: get_available_options, value_to_html, attributes, record_to_html, user_lang, create.


Tell me about the mr_line.internal_transfer_line model. or How is mr_line.internal_transfer_line used in the system?

Response: The mr_line.internal_transfer_line model represents mr_line.internal_transfer_line in the ERP system. It contains 22 fields and is used to manage mr_line.internal_transfer_line data. Defined in module: equip3_inventory_operation. Key fields include: mr_id, mr_line_id, no, product_id, description, uom_id, source_location, source_warehouse_id, current_qty, virtual_available, qty_transfer, mr_ir_wizard, filter_warehouse_ids, filter_location_ids, dest_warehouse_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


List all relational fields in setu.inventory.turnover.analysis.report. or How does setu.inventory.turnover.analysis.report relate to other models?

Response: The setu.inventory.turnover.analysis.report model has 7 relational fields: product_category_ids -> product.category; product_ids -> product.product; warehouse_ids -> stock.warehouse; company_id -> res.company; company_ids -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: product_category_ids, product_ids, warehouse_ids, company_ids. One2many fields: none.


Tell me about the sale_data_margin table. or What is the sale_data_margin table?

Response: The sale_data_margin table has 11 columns and 5 foreign key relationships. It stores data related to sale data margin in the system. The table has 1 indexes for performance optimization. Column types: integer: 6, character varying: 1, timestamp without time zone: 3, double precision: 1. Nullable columns: 10, columns with defaults: 1.


What foreign keys exist in setu.inventory.age.bi.report? or What models are connected to setu.inventory.age.bi.report?

Response: The setu.inventory.age.bi.report model has 6 relational fields: product_id -> product.product; product_category_id -> product.category; company_id -> res.company; wizard_id -> setu.inventory.age.report; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


How is stock.traceability.report used in the system? or Tell me about the stock.traceability.report model.

Response: The stock.traceability.report model represents Traceability Report in the ERP system. It contains 7 fields and is used to manage traceability report data. Defined in module: stock. Key fields include: id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Which fields in gamification.badge.user are computed? or What methods are available in gamification.badge.user?

Response: The gamification.badge.user model is defined in module: gamification. It has 4 computed fields: badge_name, level, display_name, __last_update. Stored computed fields: level. Related fields: badge_name -> badge_id.name, level -> badge_id.level. Original module methods: _send_badge, create.


What is the kpi_category table? or Tell me about the kpi_category table.

Response: The kpi_category table has 12 columns and 4 foreign key relationships. It stores data related to kpi category in the system. The table has 1 indexes for performance optimization. Column types: integer: 6, character varying: 1, boolean: 2, text: 1, timestamp without time zone: 2. Nullable columns: 10, columns with defaults: 1.


Describe the new.product model in Odoo. or How is new.product used in the system?

Response: The new.product model represents new.product in the ERP system. It contains 9 fields and is used to manage new.product data. Defined in module: equip3_sale_report. Key fields include: name, top_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Show me the relational structure of report.equip3_accounting_reports.tax_report. or List all relational fields in report.equip3_accounting_reports.tax_report.

Response: The report.equip3_accounting_reports.tax_report model has no explicit relational fields defined in its field metadata.


Which columns are nullable in product_pricelist? or What are the column types in product_pricelist?

Response: Columns in product_pricelist: id (integer) [NOT NULL] [DEFAULT: nextval('product_pricelist_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [NOT NULL] [COMMENT: Pricelist Name]; active (boolean) [COMMENT: Active]; currency_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Currency]; company_id (integer) [PRECISION: 32] [COMMENT: Company]; sequence (integer) [PRECISION: 32] [COMMENT: Sequence]; discount_policy (character varying) [NOT NULL] [COMMENT: Discount Policy]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]; website_id (integer) [PRECISION: 32] [COMMENT: Website]; code (character varying) [COMMENT: E-commerce Promotional Code]; selectable (boolean) [COMMENT: Selectable]; from_date (timestamp without time zone) [COMMENT: From Date]; to_date (timestamp without time zone) [COMMENT: To Date]; customer_category (integer) [PRECISION: 32] [COMMENT: Customer Category]; is_external_link (boolean) [COMMENT: Is External Link]; barcode (character varying) [COMMENT: Barcode]. Total columns: 19. Statistics: 15 nullable, 1 with defaults, 0 with length constraints.


Tell me about the account.root model. or What does the account.root model represent?

Response: The account.root model represents Account codes first 2 digits in the ERP system. It contains 6 fields and is used to manage account codes first 2 digits data. Defined in module: account. Key fields include: name, parent_id, company_id, id, display_name, __last_update.


Describe the field structure of sms.composer. or What fields does sms.composer have?

Response: The sms.composer model has 30 fields. Field types distribution: selection: 1, char: 8, integer: 6, boolean: 6, text: 3, many2one: 3, datetime: 3. Computed fields: 14. Field details: composition_mode (selection) [required] [compute: _compute_composition_mode] [stored] [module: sms]; res_model (char) [module: sms]; res_id (integer) [module: sms]; res_ids (char) [module: sms]; res_ids_count (integer) [readonly] [compute: _compute_recipients_count] [not stored] [module: sms]; use_active_domain (boolean) [module: sms]; active_domain (text) [readonly] [module: sms]; active_domain_count (integer) [readonly] [compute: _compute_recipients_count] [not stored] [module: sms]; comment_single_recipient (boolean) [readonly] [compute: _compute_comment_single_recipient] [not stored] [module: sms]; mass_keep_log (boolean) [module: sms]; mass_force_send (boolean) [module: sms]; mass_use_blacklist (boolean) [module: sms]; recipient_valid_count (integer) [readonly] [compute: _compute_recipients] [not stored] [module: sms]; recipient_invalid_count (integer) [readonly] [compute: _compute_recipients] [not stored] [module: sms]; recipient_single_description (text) [readonly] [compute: _compute_recipient_single] [not stored] [module: sms]; recipient_single_number (char) [readonly] [compute: _compute_recipient_single] [not stored] [module: sms]; recipient_single_number_itf (char) [compute: _compute_recipient_single] [stored] [module: sms]; recipient_single_valid (boolean) [readonly] [compute: _compute_recipient_single_valid] [not stored] [module: sms]; number_field_name (char) [module: sms]; numbers (char) [module: sms]; sanitized_numbers (char) [readonly] [compute: _compute_sanitized_numbers] [not stored] [module: sms]; template_id (many2one) -> sms.template [module: sms]; body (text) [required] [compute: _compute_body] [stored] [module: sms]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


Which fields are required in report.dynamic_accounts_report.balance_sheet? or Describe the field structure of report.dynamic_accounts_report.balance_sheet.

Response: The report.dynamic_accounts_report.balance_sheet model has 3 fields. Field types distribution: integer: 1, char: 1, datetime: 1. Computed fields: 2. Field details: id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field] [not stored] [module: None].


How to create records in sale.order.option? or What business logic is in sale.order.option?

Response: To use the sale.order.option model, you need to provide values for required fields: name, product_id, price_unit, uom_id, quantity. Readonly fields: is_present, product_uom_category_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: is_present [readonly] [computed] [no_copy]; name [required]; product_id [required]; price_unit [required]; uom_id [required]; product_uom_category_id [readonly] [computed] [no_copy]; quantity [required] [has_default]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


Describe the field structure of kpi.measure.item. or What computed fields exist in kpi.measure.item?

Response: The kpi.measure.item model has 20 fields. Field types distribution: char: 4, many2one: 5, text: 2, selection: 1, boolean: 2, integer: 2, html: 1, datetime: 3. Computed fields: 7. Field details: name (char) [required] [module: kpi_scorecard]; measure_id (many2one) [required] -> kpi.measure [module: kpi_scorecard]; domain (text) [required] [module: kpi_scorecard]; model_id (many2one) [readonly] -> ir.model [compute: <bound method Field._compute_related of kpi.measure.item.model_id>] [stored] [module: kpi_scorecard] [related: measure_id.model_id]; model_name (char) [readonly] [compute: <bound method Field._compute_related of kpi.measure.item.model_name>] [stored] [module: kpi_scorecard] [related: measure_id.model_name]; measure_type (selection) [readonly] [compute: <bound method Field._compute_related of kpi.measure.item.measure_type>] [stored] [module: kpi_scorecard] [related: measure_id.measure_type]; company_id (many2one) -> res.company [module: kpi_scorecard]; active (boolean) [module: kpi_scorecard]; description (text) [module: kpi_scorecard]; sequence (integer) [module: kpi_scorecard]; existing_kpi (char) [readonly] [compute: <bound method Field._compute_related of kpi.measure.item.existing_kpi>] [not stored] [module: kpi_scorecard] [related: measure_id.existing_kpi]; help_notes (html) [readonly] [compute: <function kpi_help._compute_show_kpi_help at 0x2f195ae50>] [not stored] [module: kpi_scorecard]; kpi_help_dummy (boolean) [module: kpi_scorecard]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


What models are connected to account.move? or What are the relationships in account.move?

Response: The account.move model has 127 relational fields: suitable_journal_ids -> account.journal; company_id -> res.company; currency_id -> res.currency; user_id -> res.users; invoice_user_id -> res.users; preferred_payment_method_id -> account.payment.method; debit_origin_id -> account.move; debit_note_ids -> account.move; edi_document_ids -> account.edi.document; loan_line_id -> account.loan.line; loan_id -> account.loan; journal_bank_id -> account.journal; tax_payment_move_id -> account.move; asset_depreciation_ids -> account.asset.depreciation.line; transaction_ids -> payment.transaction; authorized_transaction_ids -> payment.transaction; purchase_vendor_bill_id -> purchase.bill.union; purchase_id -> purchase.order; sh_invoice_recurring_order_id -> invoice.recurring; period_id -> sh.account.period; fiscal_year -> sh.fiscal.year; stock_move_id -> stock.move; stock_valuation_layer_ids -> stock.valuation.layer; auto_reverse_journal_id -> account.journal; pos_order_ids -> pos.order; team_id -> crm.team; partner_shipping_id -> res.partner; consignment_pos_ids -> pos.order; l10n_id_attachment_id -> ir.attachment; landed_costs_ids -> stock.landed.cost; website_id -> website; discount_account_id -> account.account; warranty_reg_id -> product.warranty; related_project_id -> account.analytic.account; repair_ids -> repair.order; target_commission_id -> sh.target.commision; down_payment_purchase_id -> purchase.order; report_template_id1 -> ir.actions.report; report_template_id -> ir.actions.report; timesheet_ids -> account.analytic.line; approval_matrix_id -> approval.matrix.accounting; approved_matrix_ids -> approval.matrix.accounting.lines; approval_matrix_line_id -> approval.matrix.accounting.lines; analytic_group_ids -> account.analytic.tag; invoice_origin_id -> account.move; request_partner_id -> res.partner; journal_id -> account.journal; company_currency_id -> res.currency; line_ids -> account.move.line; commercial_partner_id -> res.partner; partner_bank_id -> res.partner.bank; payment_id -> account.payment; statement_line_id -> account.bank.statement.line; tax_cash_basis_rec_id -> account.partial.reconcile; tax_cash_basis_move_id -> account.move; reversed_entry_id -> account.move; reversal_move_id -> account.move; fiscal_position_id -> account.fiscal.position; invoice_payment_term_id -> account.payment.term; invoice_line_ids -> account.move.line; invoice_incoterm_id -> account.incoterms; invoice_vendor_bill_id -> account.move; invoice_cash_rounding_id -> account.cash.rounding; bank_partner_id -> res.partner; journal_entries_template -> account.move.template; analytic_tag_dynamic -> account.analytic.tag; approvers_ids -> res.users; approved_user_ids -> res.users; internal_tf_id -> account.internal.transfer; new_invoice_id -> account.move; partner_id -> res.partner; account_asset_id -> account.asset.asset; customer_deposit_ids -> customer.deposit; vendor_deposit_ids -> vendor.deposit; nomor_seri -> account.efaktur; ebupot_id -> account.ebupot; nomor_seri_bupot -> account.ebupot; l10n_id_replace_invoice_id -> account.move; keterangan_tambahan -> account.keterangan.tambahan; signature_country_id -> res.country; signature_city_id -> res.country.city; currency_revaluation_id -> account.move; children_ids -> account.move; currency_revaluation_ref_id -> account.move; pettycash_id -> account.pettycash; sale_order_reference_id -> sale.order; filter_sale_order_reference_ids -> sale.order; exchange_id -> account.invoice.exchange; assembly_id -> assembly.production.record; stock_scrap_id -> stock.scrap.request; kitchen_id -> kitchen.production.record; purchase_order_id -> purchase.order; swo_ids -> service.work.order; finish_good_rework_id -> finish.good.rework; branch_id -> res.branch; sale_order_ids -> sale.order; filter_sale_order_ids -> sale.order; purchase_order_ids -> purchase.order; filter_purchase_order_ids -> purchase.order; picking_ids -> stock.picking; filter_picking_ids -> stock.picking; cashback_line_ids -> cashback.line; so_cashback_id -> sale.order; return_picking_ids -> stock.picking; picking_id -> stock.picking; rma_id -> dev.rma.rma; account_invoice_ids -> account.invoice.exchange; pos_branch_id -> res.branch; pos_session_id -> pos.session; pos_order_id -> pos.order; deposit_account_journal_id -> account.journal; create_from_session_id -> pos.session; inventory_id -> stock.inventory; campaign_id -> utm.campaign; source_id -> utm.source; medium_id -> utm.medium; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: suitable_journal_ids, transaction_ids, authorized_transaction_ids, analytic_group_ids, analytic_tag_dynamic, approvers_ids, approved_user_ids, customer_deposit_ids, vendor_deposit_ids, filter_sale_order_reference_ids, sale_order_ids, filter_sale_order_ids, purchase_order_ids, filter_purchase_order_ids, picking_ids, filter_picking_ids, return_picking_ids, account_invoice_ids, message_partner_ids, message_channel_ids. One2many fields: debit_note_ids, edi_document_ids, asset_depreciation_ids, stock_valuation_layer_ids, pos_order_ids, consignment_pos_ids, landed_costs_ids, repair_ids, timesheet_ids, approved_matrix_ids, line_ids, reversal_move_id, invoice_line_ids, children_ids, swo_ids, cashback_line_ids, activity_ids, message_follower_ids, message_ids, website_message_ids.


What data types are used in stock_scheduler_compute? or Which columns are nullable in stock_scheduler_compute?

Response: Columns in stock_scheduler_compute: id (integer) [NOT NULL] [DEFAULT: nextval('stock_scheduler_compute_id_seq'::regclass)] [PRECISION: 32]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 5. Statistics: 4 nullable, 1 with defaults, 0 with length constraints.


How do I use the resource.resource model? or How to query resource.resource data?

Response: To use the resource.resource model, you need to provide values for required fields: name, resource_type, time_efficiency, calendar_id, tz. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [required]; resource_type [required] [has_default]; time_efficiency [required] [has_default]; calendar_id [required] [has_default]; tz [required] [has_default]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


Which fields are required in pos.coupon? or What field types are used in pos.coupon?

Response: The pos.coupon model has 32 fields. Field types distribution: boolean: 1, char: 7, selection: 5, many2many: 2, integer: 6, datetime: 5, many2one: 4, float: 1, one2many: 1. Computed fields: 5. Field details: active (boolean) [module: equip3_pos_masterdata]; name (char) [required] [readonly] [module: equip3_pos_masterdata]; number (char) [module: equip3_pos_masterdata]; code (char) [module: equip3_pos_masterdata]; type_apply (selection) [required] [module: equip3_pos_masterdata]; product_ids (many2many) -> product.product [module: equip3_pos_masterdata]; minimum_purchase_quantity (integer) [module: equip3_pos_masterdata]; sequence_generate_method (selection) [required] [module: equip3_pos_masterdata]; manual_input_sequence (char) [module: equip3_pos_masterdata]; start_date (datetime) [module: equip3_pos_masterdata]; end_date (datetime) [module: equip3_pos_masterdata]; no_of_usage (integer) [module: equip3_pos_masterdata]; no_of_used (integer) [readonly] [compute: _compute_get_no_of_used] [not stored] [module: equip3_pos_masterdata]; coupon_program_id (many2one) -> pos.coupon.program [module: equip3_pos_masterdata]; company_id (many2one) -> res.company [module: equip3_pos_masterdata]; state (selection) [module: equip3_pos_masterdata]; reward_type (selection) [required] [module: equip3_pos_masterdata]; reward_product_ids (many2many) -> product.product [module: equip3_pos_masterdata]; reward_quantity (integer) [module: equip3_pos_masterdata]; reward_discount_type (selection) [module: equip3_pos_masterdata]; reward_discount_amount (integer) [module: equip3_pos_masterdata]; reward_max_discount_amount (float) [module: equip3_pos_masterdata]; use_history_ids (one2many) [readonly] -> pos.coupon.use.history [module: equip3_pos_masterdata]; product_display_name (char) [readonly] [compute: _compute_product_display_name] [not stored] [module: equip3_pos_masterdata]; reward_product_display_name (char) [readonly] [compute: _compute_reward_product_display_name] [not stored] [module: equip3_pos_masterdata]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


Describe the relational structure of mrp_production_backorder_line. or How does mrp_production_backorder_line relate to other tables?

Response: Foreign keys in mrp_production_backorder_line: create_uid -> res_users.id [constraint: mrp_production_backorder_line_create_uid_fkey]; mrp_production_backorder_id -> mrp_production_backorder.id [constraint: mrp_production_backorder_line_mrp_production_backorder_id_fkey]; mrp_production_id -> mrp_production.id [constraint: mrp_production_backorder_line_mrp_production_id_fkey]; write_uid -> res_users.id [constraint: mrp_production_backorder_line_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: mrp_production_backorder, mrp_production, res_users.


Tell me about the account_journal_account_tax_report_wizard_rel table. or How many columns are in account_journal_account_tax_report_wizard_rel?

Response: The account_journal_account_tax_report_wizard_rel table has 2 columns and 2 foreign key relationships. It stores data related to account journal account tax report wizard rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


What tables does setu_stock_movement_report_stock_warehouse_rel reference? or What tables are connected to setu_stock_movement_report_stock_warehouse_rel?

Response: Foreign keys in setu_stock_movement_report_stock_warehouse_rel: setu_stock_movement_report_id -> setu_stock_movement_report.id [constraint: setu_stock_movement_report_st_setu_stock_movement_report_i_fkey]; stock_warehouse_id -> stock_warehouse.id [constraint: setu_stock_movement_report_stock_wareho_stock_warehouse_id_fkey]. Total foreign key relationships: 2. Referenced tables: stock_warehouse, setu_stock_movement_report.


What field types are used in account.common.account.report? or What are the available fields for account.common.account.report?

Response: The account.common.account.report model has 14 fields. Field types distribution: selection: 2, many2many: 1, date: 2, many2one: 4, integer: 1, char: 1, datetime: 3. Computed fields: 2. Field details: display_account (selection) [required] [readonly] [module: accounting_pdf_reports]; journal_ids (many2many) [required] [readonly] -> account.journal [module: account]; date_from (date) [readonly] [module: account]; date_to (date) [readonly] [module: account]; target_move (selection) [required] [readonly] [module: account]; report_currency_id (many2one) [readonly] -> res.currency [module: equip3_accounting_reports]; company_id (many2one) [required] [readonly] -> res.company [module: equip3_accounting_reports]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


How does module.advanced.upgrade relate to other models? or What are the relationships in module.advanced.upgrade?

Response: The module.advanced.upgrade model has 5 relational fields: module_id -> ir.module.module; children_ids -> module.advanced.upgrade; parent_id -> module.advanced.upgrade; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: children_ids.


Show me the column structure of sh_sale_analysis_xls. or List all columns in sh_sale_analysis_xls.

Response: Columns in sh_sale_analysis_xls: id (integer) [NOT NULL] [DEFAULT: nextval('sh_sale_analysis_xls_id_seq'::regclass)] [PRECISION: 32]; file_name (character varying) [LENGTH: 64] [COMMENT: Excel File]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 6. Statistics: 5 nullable, 1 with defaults, 1 with length constraints.


Tell me about the purchase_requisition table. or What is the purchase_requisition table?

Response: The purchase_requisition table has 34 columns and 14 foreign key relationships. It stores data related to purchase requisition in the system. The table has 3 indexes for performance optimization. Column types: integer: 15, character varying: 6, date: 2, timestamp without time zone: 3, text: 1, boolean: 7. Nullable columns: 27, columns with defaults: 1.


How to query ir.qweb.field.image_url data? or How to create records in ir.qweb.field.image_url?

Response: To use the ir.qweb.field.image_url model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. Field usage details: id [readonly]; display_name [readonly] [computed] [no_copy]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


Show me the relational structure of purchase.team.analysis. or What foreign keys exist in purchase.team.analysis?

Response: The purchase.team.analysis model has 5 relational fields: user_id -> res.users; purchase_ids -> purchase.order; branch_id -> res.branch; create_uid -> res.users; write_uid -> res.users. Many2many fields: purchase_ids. One2many fields: none.


Tell me about the pos_make_payment table. or What is stored in pos_make_payment?

Response: The pos_make_payment table has 12 columns and 5 foreign key relationships. It stores data related to pos make payment in the system. The table has 1 indexes for performance optimization. Column types: integer: 6, numeric: 1, character varying: 1, timestamp without time zone: 3, double precision: 1. Nullable columns: 7, columns with defaults: 1.


Describe the customer.order.dic model in Odoo. or How is customer.order.dic used in the system?

Response: The customer.order.dic model represents customer.order.dic in the ERP system. It contains 10 fields and is used to manage customer.order.dic data. Defined in module: equip3_sale_report. Key fields include: report_id, list_order, saleperson, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What methods are available in ir.filters? or What methods are defined in ir.filters original module?

Response: The ir.filters model is defined in module: base. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: _list_all_models, copy, _get_eval_domain, _get_action_domain, get_filters, _check_global_default, create_or_replace, _auto_init, create.


What business logic is in force.done.memory? or How to work with force.done.memory fields?

Response: To use the force.done.memory model, you need to provide values for required fields: blanket_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: blanket_id [required]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


What is the module hierarchy for customer.statement? or What methods are defined in customer.statement original module?

Response: The customer.statement model is defined in module: equip3_accounting_reports. It has 26 computed fields: activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, access_url, access_warning, sequence_prefix, sequence_number, display_name, __last_update. Stored computed fields: sequence_prefix, sequence_number. Related fields: activity_user_id -> activity_ids.user_id, activity_type_id -> activity_ids.activity_type_id, activity_type_icon -> activity_ids.icon, activity_summary -> activity_ids.summary. Original module methods: get_mail_template, view_report, get_filter, get_filter_data, _get_report_values, create, write, _get_partners, address, partner_address, _get_currency, get_dynamic_xlsx_report, _domain_branch.


What one2many fields are in pos.coupon.use.history? or What are the relationships in pos.coupon.use.history?

Response: The pos.coupon.use.history model has 6 relational fields: coupon_id -> pos.coupon; pos_order_id -> pos.order; cashier_id -> res.users; payment_id -> pos.payment; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


How is purchase.excel.extended implemented technically? or Describe the implementation of purchase.excel.extended.

Response: The purchase.excel.extended model is defined in module: sh_all_in_one_purchase_tools. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: download_report.


What data types are used in sh_mrp_allow_qc_measurement? or What fields are available in sh_mrp_allow_qc_measurement?

Response: Columns in sh_mrp_allow_qc_measurement: id (integer) [NOT NULL] [DEFAULT: nextval('sh_mrp_allow_qc_measurement_id_seq'::regclass)] [PRECISION: 32]; product_id (integer) [PRECISION: 32] [COMMENT: Product]; sh_message (text) [COMMENT: Measurement Message]; sh_quality_point_id (integer) [PRECISION: 32] [COMMENT: Quality Control Point]; mrp_id (integer) [PRECISION: 32] [COMMENT: Manufacturing]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 9. Statistics: 8 nullable, 1 with defaults, 0 with length constraints.


What methods are available in crm.activity.report? or What modules define crm.activity.report?

Response: The crm.activity.report model is defined in module: crm. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: _select, _from, _join, _where, init.


What are the length constraints in stock_rules_report? or Show me the column structure of stock_rules_report.

Response: Columns in stock_rules_report: id (integer) [NOT NULL] [DEFAULT: nextval('stock_rules_report_id_seq'::regclass)] [PRECISION: 32]; product_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Product]; product_tmpl_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Product Template]; product_has_variants (boolean) [NOT NULL] [COMMENT: Has variants]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 8. Statistics: 4 nullable, 1 with defaults, 0 with length constraints.


What are the foreign keys in it_analytic_rel? or What relationships exist for it_analytic_rel?

Response: Foreign keys in it_analytic_rel: it_id -> account_analytic_tag.id [constraint: it_analytic_rel_it_id_fkey]; tag_id -> internal_transfer.id [constraint: it_analytic_rel_tag_id_fkey]. Total foreign key relationships: 2. Referenced tables: internal_transfer, account_analytic_tag.


Show me the column structure of approval_request_reject. or Describe the columns of approval_request_reject.

Response: Columns in approval_request_reject: id (integer) [NOT NULL] [DEFAULT: nextval('approval_request_reject_id_seq'::regclass)] [PRECISION: 32]; reason (text) [NOT NULL] [COMMENT: Reason]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 6. Statistics: 4 nullable, 1 with defaults, 0 with length constraints.


What fields are available in account_journal_account_tax_report_wizard_rel? or What data types are used in account_journal_account_tax_report_wizard_rel?

Response: Columns in account_journal_account_tax_report_wizard_rel: account_tax_report_wizard_id (integer) [NOT NULL] [PRECISION: 32]; account_journal_id (integer) [NOT NULL] [PRECISION: 32]. Total columns: 2. Statistics: 0 nullable, 0 with defaults, 0 with length constraints.


How to work with ks.sales.forecast.report fields? or What operations can I perform on ks.sales.forecast.report?

Response: To use the ks.sales.forecast.report model, you need to provide values for required fields: type, name, binding_type. Readonly fields: type, name, xml_id, help, binding_model_id, binding_type, binding_view_types, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: type [required] [readonly] [has_default]; name [required] [readonly]; xml_id [readonly] [computed] [no_copy]; help [readonly]; binding_model_id [readonly]; binding_type [required] [readonly] [has_default]; binding_view_types [readonly] [has_default]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


What relationships exist for limit_approval_matrix_sale_reject? or List all constraint names in limit_approval_matrix_sale_reject.

Response: Foreign keys in limit_approval_matrix_sale_reject: create_uid -> res_users.id [constraint: limit_approval_matrix_sale_reject_create_uid_fkey]; write_uid -> res_users.id [constraint: limit_approval_matrix_sale_reject_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


What one2many fields are in credit.limit.approval? or Show me the relational structure of credit.limit.approval.

Response: The credit.limit.approval model has 6 relational fields: user_ids -> res.users; user_approved_ids -> res.users; credit_id -> limit.request; last_approved -> res.users; create_uid -> res.users; write_uid -> res.users. Many2many fields: user_ids, user_approved_ids. One2many fields: none.


What models are connected to sms.template? or List all relational fields in sms.template.

Response: The sms.template model has 7 relational fields: model_id -> ir.model; sidebar_action_id -> ir.actions.act_window; model_object_field -> ir.model.fields; sub_object -> ir.model; sub_model_object_field -> ir.model.fields; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


Describe the relational structure of sh_sale_product_indent_wizard. or How does sh_sale_product_indent_wizard relate to other tables?

Response: Foreign keys in sh_sale_product_indent_wizard: company_id -> res_company.id [constraint: sh_sale_product_indent_wizard_company_id_fkey]; create_uid -> res_users.id [constraint: sh_sale_product_indent_wizard_create_uid_fkey]; write_uid -> res_users.id [constraint: sh_sale_product_indent_wizard_write_uid_fkey]. Total foreign key relationships: 3. Referenced tables: res_users, res_company.


Show me the fields of report.sh_sale_reports.sh_sales_product_profit_doc. or What fields does report.sh_sale_reports.sh_sales_product_profit_doc have?

Response: The report.sh_sale_reports.sh_sales_product_profit_doc model has 3 fields. Field types distribution: integer: 1, char: 1, datetime: 1. Computed fields: 2. Field details: id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field] [not stored] [module: None].


List all columns in stock_inventory_request_matrix_reject. or What fields are available in stock_inventory_request_matrix_reject?

Response: Columns in stock_inventory_request_matrix_reject: id (integer) [NOT NULL] [DEFAULT: nextval('stock_inventory_request_matrix_reject_id_seq'::regclass)] [PRECISION: 32]; reason (text) [COMMENT: Reason]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 6. Statistics: 5 nullable, 1 with defaults, 0 with length constraints.


List all relational fields in kpi.category. or What are the relationships in kpi.category?

Response: The kpi.category model has 11 relational fields: parent_id -> kpi.category; child_ids -> kpi.category; company_id -> res.company; user_ids -> res.users; user_group_ids -> res.groups; access_user_ids -> res.users; edit_user_ids -> res.users; edit_user_group_ids -> res.groups; edit_access_user_ids -> res.users; create_uid -> res.users; write_uid -> res.users. Many2many fields: user_ids, user_group_ids, access_user_ids, edit_user_ids, edit_user_group_ids, edit_access_user_ids. One2many fields: child_ids.


How many columns are in product_template_attribute_value_sale_order_line_rel? or What columns does product_template_attribute_value_sale_order_line_rel have?

Response: The product_template_attribute_value_sale_order_line_rel table has 2 columns and 4 foreign key relationships. It stores data related to product template attribute value sale order line rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


How to work with pos.order.location fields? or What business logic is in pos.order.location?

Response: To use the pos.order.location model, you need to provide values for required fields: none. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


What is the purchase.request.line.make.purchase.order model? or Describe the purchase.request.line.make.purchase.order model in Odoo.

Response: The purchase.request.line.make.purchase.order model represents Purchase Request Line Make Purchase Order in the ERP system. It contains 15 fields and is used to manage purchase request line make purchase order data. Defined in module: purchase_request. Key fields include: item_ids, sync_data_planned, supplier_ids, supplier_id, create_rfq, partner_id, pr_id, purchase_order_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What business logic is in dev.purchase.team? or What are common use cases for dev.purchase.team?

Response: To use the dev.purchase.team model, you need to provide values for required fields: name, company_id. Readonly fields: company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [required]; company_id [required] [readonly] [has_default]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


Describe the stock.picking.batch.validate.line model in Odoo. or Can you explain the purpose of stock.picking.batch.validate.line?

Response: The stock.picking.batch.validate.line model represents Stock Picking Batch Validate Data in the ERP system. It contains 14 fields and is used to manage stock picking batch validate data data. Defined in module: equip3_inventory_operations_countd. Key fields include: line_id, product_id, transfer_id, location_id, product_uom_qty, reserved_availability, quantity_done, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What columns does it_analytic_rel have? or Tell me about the it_analytic_rel table.

Response: The it_analytic_rel table has 2 columns and 2 foreign key relationships. It stores data related to it analytic rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


Describe the implementation of queue.job. or What are the technical details of queue.job?

Response: The queue.job model is defined in module: queue_job. It has 25 computed fields: record_ids, dependency_graph, graph_jobs_count, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, display_name, __last_update. Stored computed fields: none. Related fields: activity_user_id -> activity_ids.user_id, activity_type_id -> activity_ids.activity_type_id, activity_type_icon -> activity_ids.icon, activity_summary -> activity_ids.summary. Original module methods: init, _compute_record_ids, _compute_dependency_graph, _dependency_graph_vis_node, _compute_graph_jobs_count, create, write, open_related_action, open_graph_jobs, _change_job_state, button_done, button_cancelled, action_kill_job, action_cancel_job, action_cleanup_stale_jobs, get_process_status, requeue, _message_post_on_failure, _subscribe_users_domain, _message_failed_job, _needaction_domain_get, autovacuum, requeue_stuck_jobs, _get_stuck_jobs_domain, _get_stuck_jobs_to_requeue, related_action_open_record, _test_job, with_delay, delayable, _patch_job_auto_delay, _job_store_values, _job_prepare_context_before_enqueue_keys, _job_prepare_context_before_enqueue.


What foreign keys exist in mass.editing.line? or What one2many fields are in mass.editing.line?

Response: The mass.editing.line model has 5 relational fields: server_action_id -> ir.actions.server; model_id -> ir.model; field_id -> ir.model.fields; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


How to create records in tax.sale.details.report? or What business logic is in tax.sale.details.report?

Response: To use the tax.sale.details.report model, you need to provide values for required fields: none. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


Which columns are nullable in queue_requeue_job? or What are the column types in queue_requeue_job?

Response: Columns in queue_requeue_job: id (integer) [NOT NULL] [DEFAULT: nextval('queue_requeue_job_id_seq'::regclass)] [PRECISION: 32]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 5. Statistics: 4 nullable, 1 with defaults, 0 with length constraints.


What does the print.purchase.tender.report model represent? or What is the print.purchase.tender.report model?

Response: The print.purchase.tender.report model represents Purchase Tender Pdf/XLS Report in the ERP system. It contains 9 fields and is used to manage purchase tender pdf/xls report data. Defined in module: equip3_purchase_other_operation. Key fields include: selection, purchase_agreement_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Show me the fields of excel.extended. or Which fields are required in excel.extended?

Response: The excel.extended model has 9 fields. Field types distribution: binary: 1, char: 2, integer: 1, many2one: 2, datetime: 3. Computed fields: 2. Field details: excel_file (binary) [module: sh_purchase_reports]; file_name (char) [module: sh_purchase_reports]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


What field types are used in account.payment.reconcile? or Show me the fields of account.payment.reconcile.

Response: The account.payment.reconcile model has 14 fields. Field types distribution: many2one: 4, selection: 1, date: 1, one2many: 1, float: 2, integer: 1, char: 1, datetime: 3. Computed fields: 6. Field details: payment_id (many2one) -> account.payment [module: equip3_accounting_operation]; payment_type (selection) [required] [readonly] [compute: <bound method Field._compute_related of account.payment.reconcile.payment_type>] [not stored] [module: equip3_accounting_operation] [related: payment_id.payment_type]; partner_id (many2one) [readonly] -> res.partner [compute: <bound method Field._compute_related of account.payment.reconcile.partner_id>] [not stored] [module: equip3_accounting_operation] [related: payment_id.partner_id]; date_reconcile (date) [module: equip3_accounting_operation]; allocation_line_ids (one2many) -> account.payment.reconcile.line [module: equip3_accounting_operation]; payment_amount (float) [readonly] [compute: _payment_amount] [not stored] [module: equip3_accounting_operation]; limit_amount (float) [readonly] [compute: _payment_limit] [not stored] [module: equip3_accounting_operation]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


List all relational fields in mail.alias.mixin. or What one2many fields are in mail.alias.mixin?

Response: The mail.alias.mixin model has 6 relational fields: alias_id -> mail.alias; alias_model_id -> ir.model; alias_user_id -> res.users; alias_parent_model_id -> ir.model; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


How does invoice_printout_editor relate to other tables? or What are the foreign keys in invoice_printout_editor?

Response: Foreign keys in invoice_printout_editor: create_uid -> res_users.id [constraint: invoice_printout_editor_create_uid_fkey]; template_id -> invoice_templates.id [constraint: invoice_printout_editor_template_id_fkey]; write_uid -> res_users.id [constraint: invoice_printout_editor_write_uid_fkey]. Total foreign key relationships: 3. Referenced tables: invoice_templates, res_users.


What indexes exist on dev_credit_note_wizard? or What columns does dev_credit_note_wizard have?

Response: The dev_credit_note_wizard table has 8 columns and 5 foreign key relationships. It stores data related to dev credit note wizard in the system. The table has 1 indexes for performance optimization. Column types: integer: 6, timestamp without time zone: 2. Nullable columns: 7, columns with defaults: 1.


What methods are available in queue.requeue.job? or How is queue.requeue.job implemented technically?

Response: The queue.requeue.job model is defined in module: queue_job. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: _default_job_ids, requeue, with_delay, delayable, _patch_job_auto_delay, _job_store_values, _job_prepare_context_before_enqueue_keys, _job_prepare_context_before_enqueue.


How is pos.top.selling.wizard used in the system? or Describe the pos.top.selling.wizard model in Odoo.

Response: The pos.top.selling.wizard model represents POS Top Selling Wizard in the ERP system. It contains 14 fields and is used to manage pos top selling wizard data. Defined in module: equip3_pos_report. Key fields include: start_dt, end_dt, report_type, no_product, top_selling, branch_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What columns does approved_users_blanket_order_rel have? or What indexes exist on approved_users_blanket_order_rel?

Response: The approved_users_blanket_order_rel table has 2 columns and 2 foreign key relationships. It stores data related to approved users blanket order rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


What indexes exist on product_attribute_value_sale_adv_wizard_rel? or Tell me about the product_attribute_value_sale_adv_wizard_rel table.

Response: The product_attribute_value_sale_adv_wizard_rel table has 2 columns and 2 foreign key relationships. It stores data related to product attribute value sale adv wizard rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


What tables are connected to res_company_sh_purchase_details_report_wizard_rel? or What are the foreign keys in res_company_sh_purchase_details_report_wizard_rel?

Response: Foreign keys in res_company_sh_purchase_details_report_wizard_rel: sh_purchase_details_report_wizard_id -> sh_purchase_details_report_wizard.id [constraint: res_company_sh_purchase_detai_sh_purchase_details_report_w_fkey]; res_company_id -> res_company.id [constraint: res_company_sh_purchase_details_report_wiza_res_company_id_fkey]. Total foreign key relationships: 2. Referenced tables: sh_purchase_details_report_wizard, res_company.


What does the report.dynamic_accounts_report.partner_ageing model represent? or Can you explain the purpose of report.dynamic_accounts_report.partner_ageing?

Response: The report.dynamic_accounts_report.partner_ageing model represents Partner Ageing Report in the ERP system. It contains 3 fields and is used to manage partner ageing report data. Defined in module: dynamic_accounts_report. Key fields include: id, display_name, __last_update.


Which fields are required in acrux.chat.base.message? or List all fields in the acrux.chat.base.message model.

Response: The acrux.chat.base.message model has 7 fields. Field types distribution: text: 1, selection: 1, char: 2, integer: 2, datetime: 1. Computed fields: 2. Field details: text (text) [readonly] [module: acrux_chat]; ttype (selection) [required] [readonly] [module: acrux_chat]; res_model (char) [readonly] [module: acrux_chat]; res_id (integer) [readonly] [module: acrux_chat]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field] [not stored] [module: None].


Show me the fields of stock.day.average.line. or List all fields in the stock.day.average.line model.

Response: The stock.day.average.line model has 16 fields. Field types distribution: many2one: 4, float: 6, boolean: 1, integer: 1, char: 1, datetime: 3. Computed fields: 3. Field details: order_id (many2one) -> stock.day.average [module: equip3_inventory_control]; warehouse_id (many2one) -> stock.warehouse [module: equip3_inventory_control]; quantity (float) [module: equip3_inventory_control]; run_rate (float) [module: equip3_inventory_control]; stock_days (float) [module: equip3_inventory_control]; average_stock (float) [module: equip3_inventory_control]; optimal_qty (float) [module: equip3_inventory_control]; total_optimal_qty (float) [module: equip3_inventory_control]; is_need_itr (boolean) [readonly] [compute: compute_need_itr] [not stored] [module: equip3_inventory_control]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


What are the technical details of do.matrix.reject? or What methods are defined in do.matrix.reject original module?

Response: The do.matrix.reject model is defined in module: equip3_inventory_operation. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: action_reject.