What relationships exist for account_reconcile_model_partner_mapping? or How does account_reconcile_model_partner_mapping relate to other tables?

Response: Foreign keys in account_reconcile_model_partner_mapping: create_uid -> res_users.id [constraint: account_reconcile_model_partner_mapping_create_uid_fkey]; model_id -> account_reconcile_model.id [constraint: account_reconcile_model_partner_mapping_model_id_fkey]; partner_id -> res_partner.id [constraint: account_reconcile_model_partner_mapping_partner_id_fkey]; write_uid -> res_users.id [constraint: account_reconcile_model_partner_mapping_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: res_partner, account_reconcile_model, res_users.


Which columns are nullable in excel_report_stock_categ_rel? or What are the length constraints in excel_report_stock_categ_rel?

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


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

Response: The stock_inventory_line table has 37 columns and 17 foreign key relationships. It stores data related to stock inventory line in the system. The table has 6 indexes for performance optimization. Column types: integer: 20, boolean: 4, numeric: 5, timestamp without time zone: 3, double precision: 3, character varying: 2. Nullable columns: 32, columns with defaults: 1.


Show me the foreign key constraints of acrux_chat_select_conversation_wizard. or What relationships exist for acrux_chat_select_conversation_wizard?

Response: Foreign keys in acrux_chat_select_conversation_wizard: conversation_id -> acrux_chat_conversation.id [constraint: acrux_chat_select_conversation_wizard_conversation_id_fkey]; create_uid -> res_users.id [constraint: acrux_chat_select_conversation_wizard_create_uid_fkey]; write_uid -> res_users.id [constraint: acrux_chat_select_conversation_wizard_write_uid_fkey]. Total foreign key relationships: 3. Referenced tables: acrux_chat_conversation, res_users.


Describe the gamification.goal.definition model in Odoo. or How is gamification.goal.definition used in the system?

Response: The gamification.goal.definition model represents Gamification Goal Definition in the ERP system. It contains 26 fields and is used to manage gamification goal definition data. Defined in module: gamification. Key fields include: name, description, monetary, suffix, full_suffix, computation_mode, display_mode, model_id, model_inherited_ids, field_id, field_date_id, domain, batch_mode, batch_distinctive_field, batch_user_expression, compute_code, condition, action_id, res_id_field, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What tables are connected to hr_plan_activity_type? or How does hr_plan_activity_type relate to other tables?

Response: Foreign keys in hr_plan_activity_type: activity_type_id -> mail_activity_type.id [constraint: hr_plan_activity_type_activity_type_id_fkey]; create_uid -> res_users.id [constraint: hr_plan_activity_type_create_uid_fkey]; responsible_id -> res_users.id [constraint: hr_plan_activity_type_responsible_id_fkey]; write_uid -> res_users.id [constraint: hr_plan_activity_type_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: mail_activity_type, res_users.


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

Response: Foreign keys in customer_deposit: branch_id -> res_branch.id [constraint: customer_deposit_branch_id_fkey]; campaign_id -> utm_campaign.id [constraint: customer_deposit_campaign_id_fkey]; company_id -> res_company.id [constraint: customer_deposit_company_id_fkey]; create_from_session_id -> pos_session.id [constraint: customer_deposit_create_from_session_id_fkey]; create_uid -> res_users.id [constraint: customer_deposit_create_uid_fkey]; currency_id -> res_currency.id [constraint: customer_deposit_currency_id_fkey]; deposit_account_id -> account_account.id [constraint: customer_deposit_deposit_account_id_fkey]; deposit_move_id -> account_move.id [constraint: customer_deposit_deposit_move_id_fkey]; deposit_reconcile_journal_id -> account_journal.id [constraint: customer_deposit_deposit_reconcile_journal_id_fkey]; journal_id -> account_journal.id [constraint: customer_deposit_journal_id_fkey]; medium_id -> utm_medium.id [constraint: customer_deposit_medium_id_fkey]; message_main_attachment_id -> ir_attachment.id [constraint: customer_deposit_message_main_attachment_id_fkey]; partner_id -> res_partner.id [constraint: customer_deposit_partner_id_fkey]; request_partner_id -> res_partner.id [constraint: customer_deposit_request_partner_id_fkey]; return_deposit -> account_move.id [constraint: customer_deposit_return_deposit_fkey]; source_id -> utm_source.id [constraint: customer_deposit_source_id_fkey]; write_uid -> res_users.id [constraint: customer_deposit_write_uid_fkey]. Total foreign key relationships: 17. Referenced tables: account_journal, utm_source, pos_session, utm_medium, res_partner, res_company, account_account, ir_attachment, res_currency, res_users, res_branch, account_move, utm_campaign.


Describe the account_analytic_tag_account_voucher_line_rel table structure. or What is the account_analytic_tag_account_voucher_line_rel table?

Response: The account_analytic_tag_account_voucher_line_rel table has 2 columns and 2 foreign key relationships. It stores data related to account analytic tag account voucher 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 does pos.keyboard.shortcuts relate to other models? or What are the relationships in pos.keyboard.shortcuts?

Response: The pos.keyboard.shortcuts model has 3 relational fields: payment_methods -> pos.payment.method.key; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: payment_methods.


What one2many fields are in service.work.order? or What are the relationships in service.work.order?

Response: The service.work.order model has 11 relational fields: partner_id -> res.partner; account_analytic_tag_ids -> account.analytic.tag; company_id -> res.company; branch_id -> res.branch; order_line -> service.work.order.line; purchase_order_id -> purchase.order; checklist_ids -> service.work.order.checklist; purchase_line_milestone_id -> milestone.contract.template.purchase; move_id -> account.move; create_uid -> res.users; write_uid -> res.users. Many2many fields: account_analytic_tag_ids. One2many fields: order_line, checklist_ids.


Tell me about the report.equip3_accounting_reports.balance_sheet model. or What is the report.equip3_accounting_reports.balance_sheet model?

Response: The report.equip3_accounting_reports.balance_sheet model represents report.equip3_accounting_reports.balance_sheet in the ERP system. It contains 3 fields and is used to manage report.equip3_accounting_reports.balance_sheet data. Defined in module: equip3_accounting_reports. Key fields include: id, display_name, __last_update.


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

Response: The purchase_agreement table has 52 columns and 19 foreign key relationships. It stores data related to purchase agreement in the system. The table has 3 indexes for performance optimization. Column types: integer: 22, character varying: 11, timestamp without time zone: 5, date: 2, text: 2, boolean: 9, numeric: 1. Nullable columns: 48, columns with defaults: 1.


What is the pos_zone table? or What indexes exist on pos_zone?

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


What does the report.sh_purchase_reports.sh_po_bill_summary_doc model represent? or What is the report.sh_purchase_reports.sh_po_bill_summary_doc model?

Response: The report.sh_purchase_reports.sh_po_bill_summary_doc model represents Purchase Bill Summary report abstract model in the ERP system. It contains 3 fields and is used to manage purchase bill summary report abstract model data. Defined in module: sh_purchase_reports. Key fields include: id, display_name, __last_update.


What are the length constraints in team_customer_segment? or What data types are used in team_customer_segment?

Response: Columns in team_customer_segment: id (integer) [NOT NULL] [DEFAULT: nextval('team_customer_segment_id_seq'::regclass)] [PRECISION: 32]; team_id (integer) [PRECISION: 32] [COMMENT: Sales team]; rfm_segment_id (integer) [PRECISION: 32] [COMMENT: RFM Segment]; total_orders (integer) [PRECISION: 32] [COMMENT: Total Orders]; total_revenue (double precision) [PRECISION: 53] [COMMENT: Total Revenue]; 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.


Show me the column structure of ai_model_selection_wizard. or What columns have default values in ai_model_selection_wizard?

Response: Columns in ai_model_selection_wizard: id (integer) [NOT NULL] [DEFAULT: nextval('ai_model_selection_wizard_id_seq'::regclass)] [PRECISION: 32]; config_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Configuration]; selected_model (character varying) [NOT NULL] [COMMENT: Select Model]; error_message (text) [COMMENT: Error Message]; 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: 5 nullable, 1 with defaults, 0 with length constraints.


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

Response: The sh_top_purchasing_excel_extended table has 6 columns and 2 foreign key relationships. It stores data related to sh top purchasing excel extended 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.


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

Response: The advertisement_images table has 17 columns and 2 foreign key relationships. It stores data related to advertisement images in the system. The table has 1 indexes for performance optimization. Column types: integer: 5, character varying: 8, text: 1, boolean: 1, timestamp without time zone: 2. Nullable columns: 16, columns with defaults: 1.


Which fields are stored computed fields in sh.custom.tab.purchase? or What modules define sh.custom.tab.purchase?

Response: The sh.custom.tab.purchase model is defined in module: sh_all_in_one_purchase_tools. It has 3 computed fields: invisible_tab, display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: get_tab_list, _compute_check_invisible_tab, unlink, write, create_tab.


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

Response: The pos_promotion_gift_condition table has 9 columns and 4 foreign key relationships. It stores data related to pos promotion gift condition in the system. The table has 1 indexes for performance optimization. Column types: integer: 5, boolean: 1, double precision: 1, timestamp without time zone: 2. Nullable columns: 5, columns with defaults: 1.


What fields are readonly in account.loan.generate.wizard? or What are common use cases for account.loan.generate.wizard?

Response: To use the account.loan.generate.wizard model, you need to provide values for required fields: date, loan_type. Readonly fields: date, loan_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: date [required] [readonly] [has_default]; loan_type [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.


How does account_analytic_tag_account_payment_register_rel relate to other tables? or What tables does account_analytic_tag_account_payment_register_rel reference?

Response: Foreign keys in account_analytic_tag_account_payment_register_rel: account_payment_register_id -> account_payment_register.id [constraint: account_analytic_tag_account_p_account_payment_register_id_fkey]; account_analytic_tag_id -> account_analytic_tag.id [constraint: account_analytic_tag_account_paym_account_analytic_tag_id_fkey1]; account_analytic_tag_id -> account_analytic_tag.id [constraint: account_analytic_tag_account_paym_account_analytic_tag_id_fkey7]. Total foreign key relationships: 3. Referenced tables: account_analytic_tag, account_payment_register.


Show me the fields of ir.qweb.field.qweb. or What data can be stored in ir.qweb.field.qweb?

Response: The ir.qweb.field.qweb 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 do I use the pos.gift.card model? or What operations can I perform on pos.gift.card?

Response: To use the pos.gift.card model, you need to provide values for required fields: none. Readonly fields: card_no, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: card_no [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 relational structure of dev_rma_line. or How does dev_rma_line relate to other tables?

Response: Foreign keys in dev_rma_line: account_move_id -> account_move.id [constraint: dev_rma_line_account_move_id_fkey]; create_uid -> res_users.id [constraint: dev_rma_line_create_uid_fkey]; move_id -> stock_move.id [constraint: dev_rma_line_move_id_fkey]; picking_id -> stock_picking.id [constraint: dev_rma_line_picking_id_fkey]; picking_id -> stock_picking.id [constraint: dev_rma_line_picking_id_fkey1]; picking_id -> stock_picking.id [constraint: dev_rma_line_picking_id_fkey2]; product_id -> product_product.id [constraint: dev_rma_line_product_id_fkey]; purchase_id -> purchase_order.id [constraint: dev_rma_line_purchase_id_fkey]; replace_product_id -> product_product.id [constraint: dev_rma_line_replace_product_id_fkey]; return_reason -> return_reason.id [constraint: dev_rma_line_return_reason_fkey]; rma_id -> dev_rma_rma.id [constraint: dev_rma_line_rma_id_fkey]; sale_id -> sale_order.id [constraint: dev_rma_line_sale_id_fkey]; write_uid -> res_users.id [constraint: dev_rma_line_write_uid_fkey]. Total foreign key relationships: 13. Referenced tables: product_product, dev_rma_rma, stock_move, sale_order, stock_picking, return_reason, res_users, purchase_order, account_move.


Show me the foreign key constraints of blanket_approval_matrix_lines_res_users_rel. or What are the foreign keys in blanket_approval_matrix_lines_res_users_rel?

Response: Foreign keys in blanket_approval_matrix_lines_res_users_rel: blanket_approval_matrix_lines_id -> blanket_approval_matrix_lines.id [constraint: blanket_approval_matrix_lines_blanket_approval_matrix_line_fkey]; res_users_id -> res_users.id [constraint: blanket_approval_matrix_lines_res_users_rel_res_users_id_fkey]. Total foreign key relationships: 2. Referenced tables: blanket_approval_matrix_lines, res_users.


How to work with finish.good.rework fields? or What fields are readonly in finish.good.rework?

Response: To use the finish.good.rework model, you need to provide values for required fields: product_tmpl_ids, product_ids, company_id, product_qty, rejected_qty, product_uom_id, state, location_src_id, location_dest_id, picking_type_id, date_planned_start, warehouse_id. Readonly fields: product_tmpl_ids, product_ids, name, company_id, is_branch_required, product_qty, rejected_qty, product_uom_id, product_uom_category_id, bom_id, branch_id, state, location_src_id, location_dest_id, picking_type_id, date_planned_start, date_planned_finished, date_deadline, procurement_group_id, production_location_id, warehouse_id, product_tracking, account_move_ids, purchase_request_ids, internal_transfer_count, product_use_expiration_date, show_submit_button, is_autogenerate, default_finished_lot_qty, default_rejected_lot_qty, show_byproduct_lot_tab, byproduct_manual_product_ids, default_byproduct_lot_qty, default_next_byproduct_product_id, any_byproduct_is_autogenerate, all_byproduct_is_autogenerate, total_bom_cost, total_bom_sub_total, total_bom_quantity, total_product_cost, total_product_sub_total, total_product_quantity, total_overall, total_overall_sub_total, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, 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, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: product_tmpl_ids [required] [readonly] [has_states]; product_ids [required] [readonly] [has_states]; name [readonly] [has_default] [no_copy]; company_id [required] [readonly] [has_default] [has_states]; is_branch_required [readonly] [computed] [no_copy]; product_qty [required] [readonly] [has_default] [has_states]; rejected_qty [required] [readonly] [has_default] [has_states]; product_uom_id [required] [readonly] [has_states]; product_uom_category_id [readonly] [computed] [no_copy]; bom_id [readonly] [has_states]; branch_id [readonly] [has_default] [has_states]; state [required] [readonly] [has_default] [no_copy]; location_src_id [required] [readonly] [has_default] [has_states]; location_dest_id [required] [readonly] [has_default] [has_states]; picking_type_id [required] [readonly] [has_default] [has_states]; date_planned_start [required] [readonly] [has_default] [has_states] [no_copy]; date_planned_finished [readonly] [has_default] [has_states] [no_copy]; date_deadline [readonly] [computed] [no_copy]; procurement_group_id [readonly] [no_copy]; production_location_id [readonly] [computed] [no_copy]; warehouse_id [required] [readonly] [has_default] [has_states] [no_copy]; product_tracking [readonly] [computed] [no_copy]; account_move_ids [readonly] [no_copy]; purchase_request_ids [readonly] [no_copy]; internal_transfer_count [readonly] [computed] [no_copy]; product_use_expiration_date [readonly] [computed] [no_copy]; show_submit_button [readonly] [computed] [no_copy]; is_autogenerate [readonly] [computed] [no_copy]; default_finished_lot_qty [readonly] [computed] [no_copy]; default_rejected_lot_qty [readonly] [computed] [no_copy]; show_byproduct_lot_tab [readonly] [computed] [no_copy]; byproduct_manual_product_ids [readonly] [computed] [no_copy]; default_byproduct_lot_qty [readonly] [computed] [no_copy]; default_next_byproduct_product_id [readonly] [computed] [no_copy]; any_byproduct_is_autogenerate [readonly] [computed] [no_copy]; all_byproduct_is_autogenerate [readonly] [computed] [no_copy]; total_bom_cost [readonly] [computed] [no_copy]; total_bom_sub_total [readonly] [computed] [no_copy]; total_bom_quantity [readonly] [computed] [no_copy]; total_product_cost [readonly] [computed] [no_copy]; total_product_sub_total [readonly] [computed] [no_copy]; total_product_quantity [readonly] [computed] [no_copy]; total_overall [readonly] [computed] [no_copy]; total_overall_sub_total [readonly] [computed] [no_copy]; activity_state [readonly] [computed] [no_copy]; activity_user_id [computed] [no_copy]; activity_type_id [computed] [no_copy]; activity_type_icon [readonly] [computed] [no_copy]; activity_date_deadline [readonly] [computed] [no_copy]; my_activity_date_deadline [readonly] [computed] [no_copy]; activity_summary [computed] [no_copy]; activity_exception_decoration [readonly] [computed] [no_copy]; activity_exception_icon [readonly] [computed] [no_copy]; message_is_follower [readonly] [computed] [no_copy]; message_partner_ids [readonly] [computed] [no_copy]; message_channel_ids [readonly] [computed] [no_copy]; message_unread [readonly] [computed] [no_copy]; message_unread_counter [readonly] [computed] [no_copy]; message_needaction [readonly] [computed] [no_copy]; message_needaction_counter [readonly] [computed] [no_copy]; message_has_error [readonly] [computed] [no_copy]; message_has_error_counter [readonly] [computed] [no_copy]; message_attachment_count [readonly] [computed] [no_copy]; message_has_sms_error [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 are the column types in account_budget_rel? or What fields are available in account_budget_rel?

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


What is the module hierarchy for void.order.line? or What modules define void.order.line?

Response: The void.order.line model is defined in module: allfresh_mod_pos. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: .


How do I use the sh.purchase.bill.summary.xls model? or What fields are readonly in sh.purchase.bill.summary.xls?

Response: To use the sh.purchase.bill.summary.xls model, you need to provide values for required fields: none. Readonly fields: file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: file_name [readonly]; 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 types are used in account_move_line_account_payment_register_rel? or What are the length constraints in account_move_line_account_payment_register_rel?

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


Describe the relational structure of lost_customer. or What tables are connected to lost_customer?

Response: Foreign keys in lost_customer: create_uid -> res_users.id [constraint: lost_customer_create_uid_fkey]; top_id -> sh_tc_top_customer_wizard.id [constraint: lost_customer_top_id_fkey]; write_uid -> res_users.id [constraint: lost_customer_write_uid_fkey]. Total foreign key relationships: 3. Referenced tables: sh_tc_top_customer_wizard, res_users.


What are the relationships in report.pos.order? or Describe the many2many relations for report.pos.order.

Response: The report.pos.order model has 20 relational fields: order_id -> pos.order; partner_id -> res.partner; product_id -> product.product; product_tmpl_id -> product.template; user_id -> res.users; company_id -> res.company; journal_id -> account.journal; product_categ_id -> product.category; config_id -> pos.config; pos_categ_id -> pos.category; pricelist_id -> product.pricelist; session_id -> pos.session; employee_id -> hr.employee; pos_branch_id -> res.branch; promotion_id -> pos.promotion; hour_group_id -> hour.group; zone_id -> pos.zone; voucher_id -> pos.voucher; analytic_account_id -> account.analytic.account; cashier_id -> res.users. Many2many fields: none. One2many fields: none.


Show me the relational structure of purchase.change.request.wizard. or What models are connected to purchase.change.request.wizard?

Response: The purchase.change.request.wizard model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


List all constraint names in dev_purchase_team. or Show me the foreign key constraints of dev_purchase_team.

Response: Foreign keys in dev_purchase_team: branch_id -> res_branch.id [constraint: dev_purchase_team_branch_id_fkey]; company_id -> res_company.id [constraint: dev_purchase_team_company_id_fkey]; create_uid -> res_users.id [constraint: dev_purchase_team_create_uid_fkey]; user_id -> res_users.id [constraint: dev_purchase_team_user_id_fkey]; write_uid -> res_users.id [constraint: dev_purchase_team_write_uid_fkey]. Total foreign key relationships: 5. Referenced tables: res_company, res_users, res_branch.


Which fields are required in report.stock.report_product_product_replenishment? or What computed fields exist in report.stock.report_product_product_replenishment?

Response: The report.stock.report_product_product_replenishment 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].


Describe the res_groups_kpi_item_edit_rel_table table structure. or What is stored in res_groups_kpi_item_edit_rel_table?

Response: The res_groups_kpi_item_edit_rel_table table has 2 columns and 2 foreign key relationships. It stores data related to res groups kpi item edit rel table in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


Describe the ir.qweb.field.datetime model in Odoo. or What does the ir.qweb.field.datetime model represent?

Response: The ir.qweb.field.datetime model represents Qweb Field Datetime in the ERP system. It contains 3 fields and is used to manage qweb field datetime data. Defined in module: base. Key fields include: id, display_name, __last_update.


List all relational fields in sale.order.repair. or How does sale.order.repair relate to other models?

Response: The sale.order.repair model has 4 relational fields: repair_line_ids -> sale.order.repair.line; return_sale_order_id -> dev.rma.rma; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: repair_line_ids.


What are common use cases for web.environment.ribbon.backend? or What business logic is in web.environment.ribbon.backend?

Response: To use the web.environment.ribbon.backend 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 stock_quant_package? or Tell me about the stock_quant_package table.

Response: The stock_quant_package table has 28 columns and 10 foreign key relationships. It stores data related to stock quant package in the system. The table has 5 indexes for performance optimization. Column types: integer: 12, character varying: 4, timestamp without time zone: 2, double precision: 8, date: 1, boolean: 1. Nullable columns: 27, columns with defaults: 1.


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

Response: Foreign keys in acrux_chat_pop_message: create_uid -> res_users.id [constraint: acrux_chat_pop_message_create_uid_fkey]; write_uid -> res_users.id [constraint: acrux_chat_pop_message_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


Describe the field structure of payable.flow.wizard. or What data can be stored in payable.flow.wizard?

Response: The payable.flow.wizard model has 8 fields. Field types distribution: char: 2, integer: 1, many2one: 2, datetime: 3. Computed fields: 2. Field details: name (char) [module: equip3_accounting_flow]; 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 tables are connected to sale_order_transaction_rel? or List all constraint names in sale_order_transaction_rel.

Response: Foreign keys in sale_order_transaction_rel: sale_order_id -> sale_order.id [constraint: sale_order_transaction_rel_sale_order_id_fkey]; transaction_id -> payment_transaction.id [constraint: sale_order_transaction_rel_transaction_id_fkey]. Total foreign key relationships: 2. Referenced tables: payment_transaction, sale_order.


What relationships exist for stock_life? or What tables are connected to stock_life?

Response: Foreign keys in stock_life: create_uid -> res_users.id [constraint: stock_life_create_uid_fkey]; is_customer -> res_partner.id [constraint: stock_life_is_customer_fkey]; write_uid -> res_users.id [constraint: stock_life_write_uid_fkey]. Total foreign key relationships: 3. Referenced tables: res_partner, res_users.


What models are connected to sh.custom.tab.purchase? or Show me the relational structure of sh.custom.tab.purchase.

Response: The sh.custom.tab.purchase model has 4 relational fields: groups -> res.groups; view_id -> ir.ui.view; create_uid -> res.users; write_uid -> res.users. Many2many fields: groups. One2many fields: none.


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

Response: The stock_picking table has 101 columns and 60 foreign key relationships. It stores data related to stock picking in the system. The table has 13 indexes for performance optimization. Column types: integer: 38, character varying: 15, text: 4, timestamp without time zone: 8, boolean: 25, double precision: 4, numeric: 7. Nullable columns: 95, columns with defaults: 1.


What tables are connected to res_partner_sh_purchase_analysis_wizard_rel? or How does res_partner_sh_purchase_analysis_wizard_rel relate to other tables?

Response: Foreign keys in res_partner_sh_purchase_analysis_wizard_rel: sh_purchase_analysis_wizard_id -> sh_purchase_analysis_wizard.id [constraint: res_partner_sh_purchase_analy_sh_purchase_analysis_wizard__fkey]; res_partner_id -> res_partner.id [constraint: res_partner_sh_purchase_analysis_wizard_rel_res_partner_id_fkey]. Total foreign key relationships: 2. Referenced tables: res_partner, sh_purchase_analysis_wizard.


What methods are defined in project.task.type original module? or What are the technical details of project.task.type?

Response: The project.task.type model is defined in module: project. It has 3 computed fields: disabled_rating_warning, display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: _populate_factories, _get_default_project_ids, unlink_wizard, write, _compute_disabled_rating_warning.


What methods are defined in account.balance.report original module? or Which fields in account.balance.report are computed?

Response: The account.balance.report model is defined in module: accounting_pdf_reports. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: _print_report, pre_print_report.


List all fields in the do.approval_matrix_detail model. or What data can be stored in do.approval_matrix_detail?

Response: The do.approval_matrix_detail model has 11 fields. Field types distribution: many2many: 1, selection: 1, many2one: 4, integer: 1, char: 1, datetime: 3. Computed fields: 2. Field details: location_name (many2many) [readonly] -> stock.location [module: equip3_inventory_operation]; usage (selection) [readonly] [module: equip3_inventory_operation]; company_id (many2one) [readonly] -> res.company [module: equip3_inventory_operation]; do_approval_matrix_id2 (many2one) -> do.approval.matrix [module: equip3_inventory_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].


What is the hide.field model? or Can you explain the purpose of hide.field?

Response: The hide.field model represents Fields Rights in the ERP system. It contains 16 fields and is used to manage fields rights data. Defined in module: simplify_access_management. Key fields include: access_management_id, model_id, field_id, invisible, readonly, required, external_link, create_option, edit_option, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


List all columns in purchase_request_allocation. or What data types are used in purchase_request_allocation?

Response: Columns in purchase_request_allocation: id (integer) [NOT NULL] [DEFAULT: nextval('purchase_request_allocation_id_seq'::regclass)] [PRECISION: 32]; purchase_request_line_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Purchase Request Line]; company_id (integer) [PRECISION: 32] [COMMENT: Company]; stock_move_id (integer) [PRECISION: 32] [COMMENT: Stock Move]; purchase_line_id (integer) [PRECISION: 32] [COMMENT: Purchase Line]; requested_product_uom_qty (double precision) [PRECISION: 53] [COMMENT: Requested Quantity]; allocated_product_qty (double precision) [PRECISION: 53] [COMMENT: Allocated Quantity]; 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: 11. Statistics: 9 nullable, 1 with defaults, 0 with length constraints.


What fields are available in pos_config_users_void_order_line_rel? or What are the column types in pos_config_users_void_order_line_rel?

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


What are the column types in res_groups_implied_rel? or Describe the columns of res_groups_implied_rel.

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


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

Response: The blanketwiz.blanketwiz model represents Sale Blanket Wizard in the ERP system. It contains 8 fields and is used to manage sale blanket wizard data. Defined in module: blanket_sale_order_app. Key fields include: wiz_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What fields does stock.traceability.report have? or List all fields in the stock.traceability.report model.

Response: The stock.traceability.report 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 are the relationships in pos.profit.loss.wizard? or What one2many fields are in pos.profit.loss.wizard?

Response: The pos.profit.loss.wizard model has 3 relational fields: pos_branch_id -> res.branch; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


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

Response: The change_production_qty table has 7 columns and 3 foreign key relationships. It stores data related to change production qty in the system. The table has 1 indexes for performance optimization. Column types: integer: 4, numeric: 1, timestamp without time zone: 2. Nullable columns: 4, columns with defaults: 1.


What columns have default values in dev_rma_rma_stock_picking_rel? or List all columns in dev_rma_rma_stock_picking_rel.

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


What indexes exist on repair_order_repair_tags_rel? or What is stored in repair_order_repair_tags_rel?

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


Tell me about the nsfp.registration model. or What does the nsfp.registration model represent?

Response: The nsfp.registration model represents nsfp.registration in the ERP system. It contains 15 fields and is used to manage nsfp.registration data. Defined in module: equip3_accounting_efaktur. Key fields include: record_id, fiscal_year, start, end, last_number, registration_date, is_use, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What tables does pos_promotion_selected_brand_product_rel reference? or How does pos_promotion_selected_brand_product_rel relate to other tables?

Response: Foreign keys in pos_promotion_selected_brand_product_rel: pos_promotion_selected_brand_id -> pos_promotion_selected_brand.id [constraint: pos_promotion_selected_brand_pos_promotion_selected_brand_fkey1]; product_id -> product_product.id [constraint: pos_promotion_selected_brand_product_rel_product_id_fkey]. Total foreign key relationships: 2. Referenced tables: product_product, pos_promotion_selected_brand.


What columns have default values in pos_config_product_hidden_rel? or List all columns in pos_config_product_hidden_rel.

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


Show me the column structure of ir_server_object_lines. or What data types are used in ir_server_object_lines?

Response: Columns in ir_server_object_lines: id (integer) [NOT NULL] [DEFAULT: nextval('ir_server_object_lines_id_seq'::regclass)] [PRECISION: 32]; server_id (integer) [PRECISION: 32] [COMMENT: Related Server Action]; col1 (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Field]; value (text) [NOT NULL] [COMMENT: Value]; evaluation_type (character varying) [NOT NULL] [COMMENT: Evaluation Type]; 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: 5 nullable, 1 with defaults, 0 with length constraints.


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

Response: Columns in pos_order_line_promotion: id (integer) [NOT NULL] [DEFAULT: nextval('pos_order_line_promotion_id_seq'::regclass)] [PRECISION: 32]; sequence (integer) [PRECISION: 32] [COMMENT: Sequence]; pos_order_line_id (integer) [PRECISION: 32] [COMMENT: POS Order Line]; promotion_id (integer) [PRECISION: 32] [COMMENT: Promotion]; promotion_disc (numeric) [COMMENT: Promotion (Discount %)]; price (double precision) [PRECISION: 53] [COMMENT: Price (After Discount)]; amount_percentage (numeric) [COMMENT: Discount Amount (Percentage %)]; amount (double precision) [PRECISION: 53] [COMMENT: Discount Amount]; 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]; discount_type (character varying) [COMMENT: Discount Type]. Total columns: 13. Statistics: 12 nullable, 1 with defaults, 0 with length constraints.


What business logic is in team.customer.segment? or How to query team.customer.segment data?

Response: To use the team.customer.segment model, you need to provide values for required fields: none. Readonly fields: total_orders, total_revenue, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: total_orders [readonly] [computed] [no_copy]; total_revenue [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.


Show me the column structure of remove_action_ir_ui_view_rel_ah. or Which columns are nullable in remove_action_ir_ui_view_rel_ah?

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


What columns have default values in customer_degree_trust? or Show me the column structure of customer_degree_trust.

Response: Columns in customer_degree_trust: id (integer) [NOT NULL] [DEFAULT: nextval('customer_degree_trust_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [NOT NULL] [COMMENT: Name]; overdue_day (integer) [PRECISION: 32] [COMMENT: Overdue Days]; no_of_overdue_invoices (integer) [PRECISION: 32] [COMMENT: Number Of Overdue Invoices]; index (integer) [PRECISION: 32] [COMMENT: Index]; 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]. Total columns: 10. Statistics: 7 nullable, 1 with defaults, 0 with length constraints.


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

Response: The product.product model has 103 relational fields: product_tmpl_id -> product.template; product_template_attribute_value_ids -> product.template.attribute.value; barcode_line_ids -> product.template.barcode; stock_quant_ids -> stock.quant; stock_move_ids -> stock.move; orderpoint_ids -> stock.warehouse.orderpoint; putaway_rule_ids -> stock.putaway.rule; variant_bom_ids -> mrp.bom; bom_line_ids -> mrp.bom.line; stock_valuation_layer_ids -> stock.valuation.layer; product_cost_ids -> product.warehouse.cost; last_supplier_id -> res.partner; purchase_order_line_ids -> purchase.order.line; purchase_price_history_line_ids -> purchase.price.history; website_id -> website; product_variant_image_ids -> product.image; alternative_product_ids -> product.product; packaging_ids -> product.packaging; categ_id -> product.category; last_customer_id -> res.partner; product_lots_ids -> stock.production.lot; product_bom_id -> pos.product.bom; purchase_req_line_ids -> purchase.request.line; warehouse_price_ids -> product.warehouse.price; 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; currency_id -> res.currency; cost_currency_id -> res.currency; pricelist_id -> product.pricelist; uom_id -> uom.uom; uom_po_id -> uom.uom; seller_ids -> product.supplierinfo; variant_seller_ids -> product.supplierinfo; attribute_line_ids -> product.template.attribute.line; valid_product_template_attribute_line_ids -> product.template.attribute.line; product_variant_ids -> product.product; product_variant_id -> product.product; rating_ids -> rating.rating; taxes_id -> account.tax; property_account_income_id -> account.account; property_account_expense_id -> account.account; responsible_id -> res.users; property_stock_production -> stock.location; property_stock_inventory -> stock.location; location_id -> stock.location; warehouse_id -> stock.warehouse; route_from_categ_ids -> stock.location.route; bom_ids -> mrp.bom; deferred_revenue_category_id -> account.asset.category; email_template_id -> mail.template; property_account_creditor_price_difference -> account.account; pos_categ_id -> pos.category; route_ids -> stock.location.route; consignment_partner_id -> res.partner; optional_product_ids -> product.template; accessory_product_ids -> product.product; website_ribbon_id -> product.ribbon; public_categ_ids -> product.public.category; product_template_image_ids -> product.image; bi_pack_ids -> bi.product.pack; project_template_id -> project.project; multi_companies_all -> res.company; product_brand_id -> product.brand; project_id -> project.project; brand_attribute_id -> product.attribute; brand_ids -> product.brand; branch_id -> res.branch; secondary_uom_id -> uom.uom; multi_warehouses_all -> stock.warehouse; product_brand_ids -> product.brand; def_packaging_id -> product.packaging; group_stock_ids -> product.packaging; reordering_rules_ids -> stock.warehouse.orderpoint; variant_attribute_value_ids -> product.variant.attribute.value; product_ratio_line -> product.ratio.line; uom_categ_id -> uom.category; merchendise_id -> merchendise.code; asset_category_id -> account.asset.category; company_id -> res.company; sell_ids -> product.supplierinfo; template_purchase_price_history_line_ids -> purchase.price.history; combo_option_id -> combo.option; combo_option_items -> combo.option.item; pos_combo_item_ids -> pos.combo.item; pos_categ_ids -> pos.category; price_uom_ids -> product.uom.price; cross_ids -> product.cross; product_price_quantity_ids -> product.price.quantity; combo_limit_ids -> pos.combo.limit; uom_ids -> uom.uom; note_ids -> pos.note; tag_ids -> pos.tag; pos_branch_id -> res.branch; supplier_taxes_id -> account.tax. Many2many fields: product_template_attribute_value_ids, purchase_price_history_line_ids, alternative_product_ids, packaging_ids, message_partner_ids, message_channel_ids, valid_product_template_attribute_line_ids, taxes_id, route_from_categ_ids, route_ids, optional_product_ids, accessory_product_ids, public_categ_ids, multi_companies_all, brand_ids, multi_warehouses_all, product_brand_ids, group_stock_ids, template_purchase_price_history_line_ids, pos_categ_ids, uom_ids, note_ids, tag_ids, supplier_taxes_id. One2many fields: barcode_line_ids, stock_quant_ids, stock_move_ids, orderpoint_ids, putaway_rule_ids, variant_bom_ids, bom_line_ids, stock_valuation_layer_ids, product_cost_ids, purchase_order_line_ids, product_variant_image_ids, product_lots_ids, product_bom_id, purchase_req_line_ids, warehouse_price_ids, activity_ids, message_follower_ids, message_ids, website_message_ids, seller_ids, variant_seller_ids, attribute_line_ids, product_variant_ids, rating_ids, bom_ids, product_template_image_ids, bi_pack_ids, reordering_rules_ids, variant_attribute_value_ids, product_ratio_line, sell_ids, combo_option_items, pos_combo_item_ids, price_uom_ids, cross_ids, product_price_quantity_ids, combo_limit_ids.


What columns have default values in budget_scurve_account_lines_rel? or List all columns in budget_scurve_account_lines_rel.

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


Describe the implementation of generate.closing.entries.confirmation.wizard. or How is generate.closing.entries.confirmation.wizard implemented technically?

Response: The generate.closing.entries.confirmation.wizard model is defined in module: equip3_accounting_operation. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: default_get, action_continue.


What is the membership_invoice table? or What indexes exist on membership_invoice?

Response: The membership_invoice table has 7 columns and 3 foreign key relationships. It stores data related to membership invoice in the system. The table has 1 indexes for performance optimization. Column types: integer: 4, numeric: 1, timestamp without time zone: 2. Nullable columns: 4, columns with defaults: 1.


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

Response: Foreign keys in itr_matrix_reject: create_uid -> res_users.id [constraint: itr_matrix_reject_create_uid_fkey]; write_uid -> res_users.id [constraint: itr_matrix_reject_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


Describe the columns of setu_stock_movement_report. or What fields are available in setu_stock_movement_report?

Response: Columns in setu_stock_movement_report: id (integer) [NOT NULL] [DEFAULT: nextval('setu_stock_movement_report_id_seq'::regclass)] [PRECISION: 32]; get_report_from_beginning (boolean) [COMMENT: Report up to a certain date?]; start_date (date) [COMMENT: Start Date]; end_date (date) [COMMENT: End Date]; upto_date (date) [COMMENT: Inventory movements up to a certain date]; 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]; company_id (integer) [PRECISION: 32] [COMMENT: Company]; is_product_daily (boolean) [COMMENT: Display Each Product Daily]; is_movement_daily (boolean) [COMMENT: Display Each Movement Daily]. Total columns: 12. Statistics: 11 nullable, 1 with defaults, 0 with length constraints.


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

Response: Columns in product_product_stock_inventory_rel: stock_inventory_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.


Can you explain the purpose of sh.top.purchasing.excel.extended? or Tell me about the sh.top.purchasing.excel.extended model.

Response: The sh.top.purchasing.excel.extended model represents Excel Extended in the ERP system. It contains 9 fields and is used to manage excel extended data. Defined in module: sh_purchase_reports. Key fields include: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What is stored in mailing_trace? or What indexes exist on mailing_trace?

Response: The mailing_trace table has 25 columns and 5 foreign key relationships. It stores data related to mailing trace in the system. The table has 5 indexes for performance optimization. Column types: integer: 8, character varying: 6, timestamp without time zone: 11. Nullable columns: 23, columns with defaults: 1.


Describe the product_category_sh_target_commision_rel table structure. or What columns does product_category_sh_target_commision_rel have?

Response: The product_category_sh_target_commision_rel table has 2 columns and 2 foreign key relationships. It stores data related to product category sh target commision rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


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

Response: Foreign keys in ir_demo_failure: create_uid -> res_users.id [constraint: ir_demo_failure_create_uid_fkey]; module_id -> ir_module_module.id [constraint: ir_demo_failure_module_id_fkey]; wizard_id -> ir_demo_failure_wizard.id [constraint: ir_demo_failure_wizard_id_fkey]; write_uid -> res_users.id [constraint: ir_demo_failure_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: ir_demo_failure_wizard, res_users, ir_module_module.


Show me the fields of currency.invoice.revaluation. or What data can be stored in currency.invoice.revaluation?

Response: The currency.invoice.revaluation model has 13 fields. Field types distribution: date: 3, many2one: 5, integer: 1, char: 1, datetime: 3. Computed fields: 2. Field details: revaluation_period_start (date) [required] [module: equip3_accounting_multicurrency]; revaluation_period_end (date) [required] [module: equip3_accounting_multicurrency]; revaluation_date (date) [required] [module: equip3_accounting_multicurrency]; journal_id (many2one) [required] -> account.journal [module: equip3_accounting_multicurrency]; income_unrealized_account (many2one) [required] -> account.account [module: equip3_accounting_multicurrency]; expense_unrealized_account (many2one) [required] -> account.account [module: equip3_accounting_multicurrency]; 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 module hierarchy for report.equip3_accounting_reports.tax_report? or Which fields are stored computed fields in report.equip3_accounting_reports.tax_report?

Response: The report.equip3_accounting_reports.tax_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: _get_report_values.


What data types are used in mr_internal_transfer? or What are the column types in mr_internal_transfer?

Response: Columns in mr_internal_transfer: id (integer) [NOT NULL] [DEFAULT: nextval('mr_internal_transfer_id_seq'::regclass)] [PRECISION: 32]; source_warehouse_id (integer) [PRECISION: 32] [COMMENT: Source Warehouse]; 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.


Show me the foreign key constraints of account_user_reminder_lines. or What are the foreign keys in account_user_reminder_lines?

Response: Foreign keys in account_user_reminder_lines: account_line_id -> account_user_reminder.id [constraint: account_user_reminder_lines_account_line_id_fkey]; create_uid -> res_users.id [constraint: account_user_reminder_lines_create_uid_fkey]; write_uid -> res_users.id [constraint: account_user_reminder_lines_write_uid_fkey]. Total foreign key relationships: 3. Referenced tables: account_user_reminder, res_users.


What models are connected to rfm.yearly.analysis.by.segment? or Describe the many2many relations for rfm.yearly.analysis.by.segment.

Response: The rfm.yearly.analysis.by.segment model has 1 relational fields: segment_id -> setu.rfm.segment. Many2many fields: none. One2many fields: none.


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

Response: The sh_purchase_analysis_xls table has 6 columns and 2 foreign key relationships. It stores data related to sh purchase analysis xls 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.


How do I use the report.equip3_pos_report.report_pos_payment model? or What operations can I perform on report.equip3_pos_report.report_pos_payment?

Response: To use the report.equip3_pos_report.report_pos_payment 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.


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

Response: Columns in blacklist_partner_wiz: id (integer) [NOT NULL] [DEFAULT: nextval('blacklist_partner_wiz_id_seq'::regclass)] [PRECISION: 32]; partner_id (integer) [PRECISION: 32] [COMMENT: Partner]; user_id (integer) [PRECISION: 32] [COMMENT: Blacklisted by]; type (character varying) [COMMENT: Type]; reason (character varying) [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: 9. Statistics: 8 nullable, 1 with defaults, 0 with length constraints.


What operations can I perform on generate.closing.entries.confirmation.wizard? or How do I use the generate.closing.entries.confirmation.wizard model?

Response: To use the generate.closing.entries.confirmation.wizard model, you need to provide values for required fields: fiscal_year_id, closing_entry_date, journal_id, description, summary_account_id, retained_earnings_account_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: fiscal_year_id [required]; closing_entry_date [required]; journal_id [required]; description [required]; summary_account_id [required]; retained_earnings_account_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 field types are used in void.order.line? or What fields does void.order.line have?

Response: The void.order.line model has 12 fields. Field types distribution: char: 2, many2one: 6, integer: 1, datetime: 3. Computed fields: 2. Field details: name (char) [module: allfresh_mod_pos]; session_id (many2one) -> pos.session [module: allfresh_mod_pos]; order_id (many2one) -> pos.order [module: allfresh_mod_pos]; void_uid (many2one) -> res.users [module: allfresh_mod_pos]; cashier_id (many2one) -> res.users [module: allfresh_mod_pos]; 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 field structure of report.stock.quantity. or Show me the fields of report.stock.quantity.

Response: The report.stock.quantity model has 11 fields. Field types distribution: date: 1, many2one: 4, selection: 1, float: 1, one2many: 1, integer: 1, char: 1, datetime: 1. Computed fields: 3. Field details: date (date) [readonly] [module: stock]; product_tmpl_id (many2one) [readonly] -> product.template [compute: <bound method Field._compute_related of report.stock.quantity.product_tmpl_id>] [not stored] [module: stock] [related: product_id.product_tmpl_id]; product_id (many2one) [readonly] -> product.product [module: stock]; state (selection) [readonly] [module: stock]; product_qty (float) [readonly] [module: stock]; move_ids (one2many) [readonly] -> stock.move [module: stock]; company_id (many2one) [readonly] -> res.company [module: stock]; warehouse_id (many2one) [readonly] -> stock.warehouse [module: stock]; 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].


Can you explain the purpose of lost.product? or What is the lost.product model?

Response: The lost.product model represents lost.product in the ERP system. It contains 9 fields and is used to manage lost.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.


Describe the implementation of mail.thread. or What modules define mail.thread?

Response: The mail.thread model is defined in module: mail. It has 13 computed fields: 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: none. Original module methods: _Attachment, _get_followers, _search_follower_partners, _search_follower_channels, _compute_is_follower, _search_is_follower, _get_message_unread, _get_message_needaction, _search_message_needaction, _compute_message_has_error, _search_message_has_error, _compute_message_attachment_count, create, write, unlink, copy_data, get_empty_list_help, _compute_field_value, _creation_subtype, _get_creation_message, _creation_message, get_mail_message_access, _get_mail_message_access, _valid_field_parameter, with_lang, _fallback_lang, message_change_thread, _prepare_tracking, _discard_tracking, _finalize_tracking, _get_tracked_fields, _message_track_post_template, _track_template, message_track, static_message_track, _message_track, _track_subtype, _routing_warn, _routing_create_bounce_email, _routing_handle_bounce, _routing_check_route, _routing_reset_bounce, message_route, _message_route_process, message_process, message_new, message_update, _message_receive_bounce, _message_reset_bounce, _message_parse_extract_payload_postprocess, _message_parse_extract_payload, _message_parse_extract_bounce, message_parse, _message_get_default_recipients_on_records, _message_add_suggested_recipient, _message_get_suggested_recipients, _mail_search_on_user, _mail_search_on_partner, _mail_find_user_for_gateway, _mail_find_partner_from_emails, _message_partner_info_from_emails, _message_post_process_attachments, message_post, _message_set_main_attachment_id, _message_post_after_hook, message_post_with_view, message_post_with_template, message_notify, _message_log, _message_log_batch, _message_compute_author, _message_create, _notify_thread, _notify_record_by_inbox, _notify_record_by_email, _notify_prepare_template_context, _notify_by_email_add_values, _notify_compute_recipients, _notify_encode_link, _notify_get_action_link, _notify_get_groups, _notify_classify_recipients, _notify_get_reply_to_on_records, _notify_email_recipient_values, message_subscribe, _message_subscribe, message_unsubscribe, _message_auto_subscribe_followers, _message_auto_subscribe_notify, _message_auto_subscribe, _get_mail_redirect_suggested_company, _mail_track, _message_get_default_recipients, _notify_get_reply_to, _alias_check_contact, _alias_get_error_message, _get_default_activity_view, _notify_email_headers, _notify_email_header_dict.


Describe the implementation of account.tour.upload.bill.email.confirm. or Which fields in account.tour.upload.bill.email.confirm are computed?

Response: The account.tour.upload.bill.email.confirm model is defined in module: account. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: apply.


What foreign keys exist in service.work.order.checklist? or What are the relationships in service.work.order.checklist?

Response: The service.work.order.checklist model has 3 relational fields: swo_id -> service.work.order; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


What foreign keys exist in all.loyalty.history? or How does all.loyalty.history relate to other models?

Response: The all.loyalty.history model has 7 relational fields: order_id -> sale.order; pos_order_id -> pos.order; partner_id -> res.partner; currency_id -> res.currency; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


What data types are used in generate_closing_entries? or What are the column types in generate_closing_entries?

Response: Columns in generate_closing_entries: id (integer) [NOT NULL] [DEFAULT: nextval('generate_closing_entries_id_seq'::regclass)] [PRECISION: 32]; fiscal_year_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Fiscal Year to close]; closing_entry_date (date) [NOT NULL] [COMMENT: Closing Entry Date]; journal_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Journal]; description (text) [NOT NULL] [COMMENT: Description]; summary_account_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Profit and Loss Summary Account]; retained_earnings_account_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Retained Earnings Account]; 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: 11. Statistics: 4 nullable, 1 with defaults, 0 with length constraints.


What tables does pos_generate_efaktur_digunggung reference? or What relationships exist for pos_generate_efaktur_digunggung?

Response: Foreign keys in pos_generate_efaktur_digunggung: account_move_id -> account_move.id [constraint: pos_generate_efaktur_digunggung_account_move_id_fkey]; create_uid -> res_users.id [constraint: pos_generate_efaktur_digunggung_create_uid_fkey]; gen_efaktur_id -> pos_generate_efaktur.id [constraint: pos_generate_efaktur_digunggung_gen_efaktur_id_fkey]; partner_id -> res_partner.id [constraint: pos_generate_efaktur_digunggung_partner_id_fkey]; write_uid -> res_users.id [constraint: pos_generate_efaktur_digunggung_write_uid_fkey]. Total foreign key relationships: 5. Referenced tables: res_partner, pos_generate_efaktur, res_users, account_move.


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

Response: The cash_box_out table has 7 columns and 2 foreign key relationships. It stores data related to cash box out in the system. The table has 1 indexes for performance optimization. Column types: integer: 3, text: 1, numeric: 1, timestamp without time zone: 2. Nullable columns: 4, columns with defaults: 1.


What tables does account_journal_account_trial_balance_rel reference? or List all constraint names in account_journal_account_trial_balance_rel.

Response: Foreign keys in account_journal_account_trial_balance_rel: account_trial_balance_id -> account_trial_balance.id [constraint: account_journal_account_trial_bal_account_trial_balance_id_fkey]; account_journal_id -> account_journal.id [constraint: account_journal_account_trial_balance_r_account_journal_id_fkey]. Total foreign key relationships: 2. Referenced tables: account_trial_balance, account_journal.


Describe the implementation of base_import.tests.models.preview. or How is base_import.tests.models.preview implemented technically?

Response: The base_import.tests.models.preview model is defined in module: base_import. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: get_import_templates.


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

Response: The report.excel.fields model has 41 fields. Field types distribution: integer: 7, boolean: 7, char: 6, many2one: 5, selection: 6, many2many: 2, float: 1, date: 1, datetime: 4, text: 2. Computed fields: 6. Field details: sequence (integer) [module: report_excel]; active (boolean) [module: report_excel]; show (boolean) [module: report_excel]; cell (char) [required] [module: report_excel]; report_excel_section_id (many2one) -> report.excel.section [module: report_excel]; group_by (boolean) [module: report_excel]; aggregate (selection) [module: report_excel]; aggregate_ids (many2many) [readonly] -> report.excel.aggregate [compute: _compute_aggregate_ids] [not stored] [module: report_excel]; aggregate_id (many2one) -> report.excel.aggregate [module: report_excel]; having_operator (selection) [module: report_excel]; having_selection (selection) [module: report_excel]; having_param_ids (many2many) [readonly] -> report.excel.param [compute: _compute_aggregate_ids] [not stored] [module: report_excel]; having_param_id (many2one) -> report.excel.param [module: report_excel]; having_value_type (selection) [module: report_excel]; having_value_float (float) [module: report_excel]; having_value_date (date) [module: report_excel]; having_value_datetime (datetime) [module: report_excel]; cumulative_having_field (char) [readonly] [compute: _compute_cumulative_having_field] [not stored] [module: report_excel]; sort_by (selection) [module: report_excel]; formula (boolean) [module: report_excel]; formulas (text) [module: report_excel]; check_root_model (boolean) [module: report_excel]; root_model_id (integer) [module: report_excel]; root_model_name (selection) [module: report_excel]; model_field_selector (char) [module: report_excel]; cumulative_model_field (char) [readonly] [compute: _compute_cumulative_model_field] [not stored] [module: report_excel]; field_type (char) [module: report_excel]; image_bool (boolean) [module: report_excel]; colOff (integer) [module: report_excel]; rowOff (integer) [module: report_excel]; cx (integer) [module: report_excel]; cy (integer) [module: report_excel]; locked_canvases_bool (boolean) [module: report_excel]; description (text) [module: report_excel]; 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 purchase_request_line have? or What indexes exist on purchase_request_line?

Response: The purchase_request_line table has 56 columns and 18 foreign key relationships. It stores data related to purchase request line in the system. The table has 3 indexes for performance optimization. Column types: integer: 21, character varying: 7, numeric: 6, date: 2, text: 2, boolean: 6, timestamp without time zone: 2, double precision: 10. Nullable columns: 53, columns with defaults: 1.


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

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


What tables does mail_wizard_invite reference? or Describe the relational structure of mail_wizard_invite.

Response: Foreign keys in mail_wizard_invite: create_uid -> res_users.id [constraint: mail_wizard_invite_create_uid_fkey]; write_uid -> res_users.id [constraint: mail_wizard_invite_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


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

Response: Foreign keys in hr_department_mail_channel_rel: hr_department_id -> hr_department.id [constraint: hr_department_mail_channel_rel_hr_department_id_fkey]; mail_channel_id -> mail_channel.id [constraint: hr_department_mail_channel_rel_mail_channel_id_fkey]. Total foreign key relationships: 2. Referenced tables: hr_department, mail_channel.


Which fields are stored computed fields in ir.model.fields? or What is the module hierarchy for ir.model.fields?

Response: The ir.model.fields model is defined in module: base. It has 8 computed fields: relation_field_id, selection, copied, related_field_id, modules, relation_model_name, display_name, __last_update. Stored computed fields: relation_field_id, copied, related_field_id. Related fields: none. Original module methods: _compute_relation_field_id, _compute_related_field_id, _compute_selection, _inverse_selection, _compute_copied, _in_modules, _check_domain, _check_name, _related_field, _check_related, _onchange_related, _check_depends, _onchange_compute, _check_relation_table, _custom_many2many_names, _onchange_ttype, _onchange_relation_table, _onchange_required, _get, _get_ids, _drop_column, _prepare_update, unlink, create, write, name_get, _existing_field_data, _reflect_field_params, _reflect_fields, _all_manual_field_data, _get_manual_field_data, _instanciate_attrs, _instanciate, _add_manual_fields.


What are the available fields for vendor.evaluation.rating? or What computed fields exist in vendor.evaluation.rating?

Response: The vendor.evaluation.rating model has 9 fields. Field types distribution: many2one: 2, float: 3, integer: 2, char: 1, datetime: 1. Computed fields: 2. Field details: partner_id (many2one) -> res.partner [module: equip3_purchase_report]; fulfillment_avg (float) [module: equip3_purchase_report]; on_time_rate_avg (float) [module: equip3_purchase_report]; final_point_avg (float) [module: equip3_purchase_report]; vendor_evaluation_count (integer) [module: equip3_purchase_report]; branch_id (many2one) -> res.branch [module: equip3_purchase_report]; 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 are the length constraints in journal_account_control_rel? or What data types are used in journal_account_control_rel?

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


What field types are used in res.mail.activity? or List all fields in the res.mail.activity model.

Response: The res.mail.activity model has 15 fields. Field types distribution: char: 3, many2one: 6, date: 1, selection: 1, integer: 1, datetime: 3. Computed fields: 2. Field details: name (char) [module: equip3_crm_operation]; activity_type_id (many2one) -> mail.activity.type [module: equip3_crm_operation]; summary (char) [module: equip3_crm_operation]; date_deadline (date) [module: equip3_crm_operation]; calendar_event_id (many2one) -> calendar.event [module: equip3_crm_operation]; res_id (many2one) -> crm.lead [module: equip3_crm_operation]; act_id (many2one) -> mail.activity [module: equip3_crm_operation]; state (selection) [module: equip3_crm_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].


Show me the relational structure of pos.gift.card.exchange.history. or List all relational fields in pos.gift.card.exchange.history.

Response: The pos.gift.card.exchange.history model has 3 relational fields: customer_id -> res.partner; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


Can you explain the purpose of mrp.immediate.production.line? or Tell me about the mrp.immediate.production.line model.

Response: The mrp.immediate.production.line model represents Immediate Production Line in the ERP system. It contains 10 fields and is used to manage immediate production line data. Defined in module: mrp. Key fields include: immediate_production_id, production_id, to_immediate, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What business logic is in sale.summary.commission.report? or How do I use the sale.summary.commission.report model?

Response: To use the sale.summary.commission.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.


What fields are readonly in account.cashbox.line? or What operations can I perform on account.cashbox.line?

Response: To use the account.cashbox.line model, you need to provide values for required fields: coin_value. Readonly fields: subtotal, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: coin_value [required]; subtotal [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 fields does sh.sale.report.salesperson.wizard have? or Which fields are required in sh.sale.report.salesperson.wizard?

Response: The sh.sale.report.salesperson.wizard model has 15 fields. Field types distribution: datetime: 5, many2many: 2, selection: 1, many2one: 3, one2many: 1, integer: 2, char: 1. Computed fields: 2. Field details: date_start (datetime) [required] [module: sh_sale_reports]; date_end (datetime) [required] [module: sh_sale_reports]; user_ids (many2many) -> res.users [module: sh_sale_reports]; state (selection) [module: sh_sale_reports]; company_ids (many2many) -> res.company [module: sh_sale_reports]; company_id (many2one) -> res.company [module: equip3_sale_report]; user_order_dic (one2many) -> user.order.dic [module: equip3_sale_report]; currency_precision (integer) [module: equip3_sale_report]; 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 column types in pos_gift_card_exchange_history? or What fields are available in pos_gift_card_exchange_history?

Response: Columns in pos_gift_card_exchange_history: id (integer) [NOT NULL] [DEFAULT: nextval('pos_gift_card_exchange_history_id_seq'::regclass)] [PRECISION: 32]; customer_id (integer) [PRECISION: 32] [COMMENT: Customer]; old_card_no (character varying) [COMMENT: Old Card No.]; new_card_no (character varying) [COMMENT: New Card No.]; 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: 7 nullable, 1 with defaults, 0 with length constraints.


Describe the implementation of do.approval_matrix_line. or What are the technical details of do.approval_matrix_line?

Response: The do.approval_matrix_line model is defined in module: equip3_inventory_operation. It has 3 computed fields: sequence1, display_name, __last_update. Stored computed fields: sequence1. Related fields: sequence1 -> sequence. Original module methods: default_get, min_approver_validation.


What is the module hierarchy for account.tax.report? or Which fields in account.tax.report are computed?

Response: The account.tax.report model is defined in module: account. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: write, copy, get_lines_in_hierarchy, get_checks_to_perform, validate_country_id.


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

Response: Foreign keys in account_deposit_reconcile: create_uid -> res_users.id [constraint: account_deposit_reconcile_create_uid_fkey]; write_uid -> res_users.id [constraint: account_deposit_reconcile_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


What fields are readonly in invoice.printout.editor.lines? or What operations can I perform on invoice.printout.editor.lines?

Response: To use the invoice.printout.editor.lines model, you need to provide values for required fields: none. Readonly fields: field_description, name, ttype, model, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: field_description [readonly] [computed] [no_copy]; name [readonly] [computed] [no_copy]; ttype [readonly] [computed] [no_copy]; model [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 are the foreign keys in cancel_tender_memory? or What tables are connected to cancel_tender_memory?

Response: Foreign keys in cancel_tender_memory: create_uid -> res_users.id [constraint: cancel_tender_memory_create_uid_fkey]; tender_id -> purchase_agreement.id [constraint: cancel_tender_memory_tender_id_fkey]; write_uid -> res_users.id [constraint: cancel_tender_memory_write_uid_fkey]. Total foreign key relationships: 3. Referenced tables: purchase_agreement, res_users.


What business logic is in mr_line.internal_transfer_line? or What fields are readonly in mr_line.internal_transfer_line?

Response: To use the mr_line.internal_transfer_line model, you need to provide values for required fields: qty_transfer. Readonly fields: no, virtual_available, filter_warehouse_ids, filter_location_ids, dest_warehouse_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: no [readonly]; virtual_available [readonly]; qty_transfer [required]; filter_warehouse_ids [readonly] [computed] [no_copy]; filter_location_ids [readonly] [computed] [no_copy]; dest_warehouse_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 methods are available in res.users.tag? or Which fields in res.users.tag are computed?

Response: The res.users.tag model is defined in module: report_user_access_right. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: .


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

Response: Columns in ir_demo: id (integer) [NOT NULL] [DEFAULT: nextval('ir_demo_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 operations can I perform on sh.qc.measurement.line? or How to work with sh.qc.measurement.line fields?

Response: To use the sh.qc.measurement.line model, you need to provide values for required fields: none. Readonly fields: sh_text, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: sh_text [readonly]; 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.


List all fields in the account.tax.report.wizard model. or Describe the field structure of account.tax.report.wizard.

Response: The account.tax.report.wizard model has 13 fields. Field types distribution: many2many: 1, date: 2, selection: 1, many2one: 4, integer: 1, char: 1, datetime: 3. Computed fields: 2. Field details: journal_ids (many2many) [required] -> account.journal [module: account]; date_from (date) [module: account]; date_to (date) [module: account]; target_move (selection) [required] [module: account]; report_currency_id (many2one) -> res.currency [module: equip3_accounting_reports]; company_id (many2one) [required] -> 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].


Describe the field structure of itr.approval.matrix.line. or What data can be stored in itr.approval.matrix.line?

Response: The itr.approval.matrix.line model has 34 fields. Field types distribution: integer: 8, many2many: 4, many2one: 6, text: 1, datetime: 4, char: 2, boolean: 6, one2many: 3. Computed fields: 14. Field details: sequence (integer) [module: equip3_inventory_masterdata]; user_ids (many2many) [required] -> res.users [module: equip3_inventory_masterdata]; minimum_approver (integer) [required] [module: equip3_inventory_masterdata]; itr_approval_matrix (many2one) -> itr.approval.matrix [module: equip3_inventory_masterdata]; approved_users (many2many) -> res.users [module: equip3_inventory_masterdata]; state_char (text) [module: equip3_inventory_masterdata]; time_stamp (datetime) [module: equip3_inventory_masterdata]; feedback (char) [module: equip3_inventory_masterdata]; last_approved (many2one) -> res.users [module: equip3_inventory_masterdata]; approved (boolean) [module: equip3_inventory_masterdata]; sequence2 (integer) [readonly] [compute: <bound method Field._compute_related of itr.approval.matrix.line.sequence2>] [stored] [module: equip3_inventory_masterdata] [related: sequence]; transfer_id (many2one) -> internal.transfer [module: equip3_inventory_operation]; message_is_follower (boolean) [readonly] [compute: _compute_is_follower] [not stored] [module: mail]; message_follower_ids (one2many) -> mail.followers [module: mail]; message_partner_ids (many2many) [readonly] -> res.partner [compute: _get_followers] [not stored] [module: mail]; message_channel_ids (many2many) [readonly] -> mail.channel [compute: _get_followers] [not stored] [module: mail]; message_ids (one2many) -> mail.message [module: mail]; message_unread (boolean) [readonly] [compute: _get_message_unread] [not stored] [module: mail]; message_unread_counter (integer) [readonly] [compute: _get_message_unread] [not stored] [module: mail]; message_needaction (boolean) [readonly] [compute: _get_message_needaction] [not stored] [module: mail]; message_needaction_counter (integer) [readonly] [compute: _get_message_needaction] [not stored] [module: mail]; message_has_error (boolean) [readonly] [compute: _compute_message_has_error] [not stored] [module: mail]; message_has_error_counter (integer) [readonly] [compute: _compute_message_has_error] [not stored] [module: mail]; message_attachment_count (integer) [readonly] [compute: _compute_message_attachment_count] [not stored] [module: mail]; message_main_attachment_id (many2one) -> ir.attachment [module: mail]; website_message_ids (one2many) -> mail.message [module: portal]; message_has_sms_error (boolean) [readonly] [compute: _compute_message_has_sms_error] [not 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].


What operations can I perform on purchase.detail.excel.extended? or What are common use cases for purchase.detail.excel.extended?

Response: To use the purchase.detail.excel.extended 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 defined in report.sh_purchase_reports.sh_po_by_category_doc original module? or What is the module hierarchy for report.sh_purchase_reports.sh_po_by_category_doc?

Response: The report.sh_purchase_reports.sh_po_by_category_doc model is defined in module: sh_purchase_reports. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: _get_report_values.


What methods are available in pos.gift.card? or Which fields are stored computed fields in pos.gift.card?

Response: The pos.gift.card model is defined in module: equip3_pos_masterdata. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: _send_mail_balance_and_expired_coupon, random_cardno, write_gift_card_from_ui.


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

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


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

Response: The mailing_contact_list_rel table has 9 columns and 4 foreign key relationships. It stores data related to mailing contact list rel in the system. The table has 3 indexes for performance optimization. Column types: integer: 5, boolean: 1, timestamp without time zone: 3. Nullable columns: 6, columns with defaults: 1.


Which fields are required in account.debt.collection.line? or Show me the fields of account.debt.collection.line.

Response: The account.debt.collection.line model has 28 fields. Field types distribution: many2one: 10, date: 5, monetary: 3, selection: 1, boolean: 2, integer: 3, char: 1, datetime: 3. Computed fields: 11. Field details: debt_collection_id (many2one) [readonly] -> account.debt.collection [module: equip3_accounting_operation]; invoice_id (many2one) [readonly] -> account.move [module: equip3_accounting_operation]; invoice_date (date) [readonly] [module: equip3_accounting_operation]; currency_id (many2one) [required] -> res.currency [module: equip3_accounting_operation]; amount_invoice (monetary) [readonly] [module: equip3_accounting_operation]; amount_residual (monetary) [readonly] [module: equip3_accounting_operation]; state (selection) [readonly] [module: equip3_accounting_operation]; journal_id (many2one) -> account.journal [module: equip3_accounting_operation]; date (date) [module: equip3_accounting_operation]; amount (monetary) [module: equip3_accounting_operation]; is_full_collect (boolean) [module: equip3_accounting_operation]; payment_id (many2one) [readonly] -> account.payment [module: equip3_accounting_operation]; is_pic_line (boolean) [readonly] [compute: check_pic_line] [not stored] [module: equip3_accounting_operation]; user_id (many2one) [readonly] -> res.users [compute: <bound method Field._compute_related of account.debt.collection.line.user_id>] [not stored] [module: equip3_accounting_reports] [related: debt_collection_id.person_in_charge]; partner_id (many2one) [readonly] -> res.partner [compute: <bound method Field._compute_related of account.debt.collection.line.partner_id>] [stored] [module: equip3_accounting_reports] [related: debt_collection_id.partner_id]; deadline_date (date) [readonly] [compute: <bound method Field._compute_related of account.debt.collection.line.deadline_date>] [stored] [module: equip3_accounting_reports] [related: debt_collection_id.deadline_date]; invoice_due_date (date) [readonly] [compute: <bound method Field._compute_related of account.debt.collection.line.invoice_due_date>] [stored] [module: equip3_accounting_reports] [related: invoice_id.invoice_date_due]; total_due_date (integer) [readonly] [compute: _compute_total_due_date] [not stored] [module: equip3_accounting_reports]; debt_coll_pic (many2one) [readonly] -> res.users [compute: _compute_debt_coll_pic] [stored] [module: equip3_accounting_reports]; invoice_week_number (integer) [readonly] [compute: _compute_invoice_week_number] [stored] [module: equip3_accounting_reports]; invoice_week_start (date) [readonly] [compute: _compute_invoice_week_start] [stored] [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].


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

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


List all columns in res_groups_report_rel. or Describe the columns of res_groups_report_rel.

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


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

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


What operations can I perform on account.print.journal? or What fields are readonly in account.print.journal?

Response: To use the account.print.journal model, you need to provide values for required fields: sort_selection, journal_ids, target_move, company_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: sort_selection [required] [has_default]; journal_ids [required] [has_default]; target_move [required] [has_default]; company_id [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.