What columns have default values in account_journal? or What fields are available in account_journal?

Response: Columns in account_journal: id (integer) [NOT NULL] [DEFAULT: nextval('account_journal_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [NOT NULL] [COMMENT: Journal Name]; code (character varying) [NOT NULL] [LENGTH: 5] [COMMENT: Short Code]; active (boolean) [COMMENT: Active]; type (character varying) [NOT NULL] [COMMENT: Type]; default_account_id (integer) [PRECISION: 32] [COMMENT: Default Account]; payment_debit_account_id (integer) [PRECISION: 32] [COMMENT: Outstanding Receipts Account]; payment_credit_account_id (integer) [PRECISION: 32] [COMMENT: Outstanding Payments Account]; suspense_account_id (integer) [PRECISION: 32] [COMMENT: Suspense Account]; restrict_mode_hash_table (boolean) [COMMENT: Lock Posted Entries with Hash]; sequence (integer) [PRECISION: 32] [COMMENT: Sequence]; invoice_reference_type (character varying) [NOT NULL] [COMMENT: Communication Type]; invoice_reference_model (character varying) [NOT NULL] [COMMENT: Communication Standard]; currency_id (integer) [PRECISION: 32] [COMMENT: Currency]; company_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Company]; refund_sequence (boolean) [COMMENT: Dedicated Credit Note Sequence]; sequence_override_regex (text) [COMMENT: Sequence Override Regex]; at_least_one_inbound (boolean) [COMMENT: At Least One Inbound]; at_least_one_outbound (boolean) [COMMENT: At Least One Outbound]; profit_account_id (integer) [PRECISION: 32] [COMMENT: Profit Account]; loss_account_id (integer) [PRECISION: 32] [COMMENT: Loss Account]; bank_account_id (integer) [PRECISION: 32] [COMMENT: Bank Account]; bank_statements_source (character varying) [COMMENT: Bank Feeds]; sale_activity_type_id (integer) [PRECISION: 32] [COMMENT: Schedule Activity]; sale_activity_user_id (integer) [PRECISION: 32] [COMMENT: Activity User]; sale_activity_note (text) [COMMENT: Activity Summary]; alias_id (integer) [PRECISION: 32] [COMMENT: Email Alias]; secure_sequence_id (integer) [PRECISION: 32] [COMMENT: Secure Sequence]; show_on_dashboard (boolean) [COMMENT: Show journal on dashboard]; color (integer) [PRECISION: 32] [COMMENT: Color Index]; message_main_attachment_id (integer) [PRECISION: 32] [COMMENT: Main Attachment]; 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]; check_manual_sequencing (boolean) [COMMENT: Manual Numbering]; check_sequence_id (integer) [PRECISION: 32] [COMMENT: Check Sequence]; sequence_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Entry Sequence]; refund_sequence_id (integer) [PRECISION: 32] [COMMENT: Credit Note Entry Sequence]; use_reconcile (boolean) [COMMENT: Use Bank Reconcile?]; branch_id (integer) [PRECISION: 32] [COMMENT: Branch]; is_fiscal_book_exclude (boolean) [COMMENT: Exclude on Fiscal Book]; pos_method_type (character varying) [NOT NULL] [COMMENT: POS Method]; decimal_rounding (integer) [PRECISION: 32] [COMMENT: POS Decimal Rounding]. Total columns: 44. Statistics: 35 nullable, 1 with defaults, 1 with length constraints.


What one2many fields are in purchase.detail.excel.extended? or How does purchase.detail.excel.extended relate to other models?

Response: The purchase.detail.excel.extended model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


What does the approval.matrix.accounting.lines model represent? or Describe the approval.matrix.accounting.lines model in Odoo.

Response: The approval.matrix.accounting.lines model represents Approval Matrix Accounting Lines in the ERP system. It contains 31 fields and is used to manage approval matrix accounting lines data. Defined in module: equip3_accounting_masterdata. Key fields include: sequence, user_ids, minimum_approver, approval_matrix_id, approved_users, state_char, time_stamp, feedback, last_approved, approved, sequence2, approver_state, move_id, receipt_id, multi_receipt_id, voucher_id, payment_voc_id, acc_internal_transfer_id, account_budget_request_id, account_budget_id, budget_purchase_id, account_budget_req_id, customer_deposit_id, acc_vendor_deposit_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What operations can I perform on budget.change.req.line? or What business logic is in budget.change.req.line?

Response: To use the budget.change.req.line model, you need to provide values for required fields: budgetary_position_id, new_amount. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: budgetary_position_id [required]; new_amount [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 are the relationships in payable.flow.wizard? or What models are connected to payable.flow.wizard?

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


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

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


What models are connected to payment.acquirer? or What are the relationships in payment.acquirer?

Response: The payment.acquirer model has 11 relational fields: company_id -> res.company; view_template_id -> ir.ui.view; registration_view_template_id -> ir.ui.view; journal_id -> account.journal; country_ids -> res.country; module_id -> ir.module.module; payment_icon_ids -> payment.icon; inbound_payment_method_ids -> account.payment.method; website_id -> website; create_uid -> res.users; write_uid -> res.users. Many2many fields: country_ids, payment_icon_ids, inbound_payment_method_ids. One2many fields: none.


How to create records in return.approval.matrix.line? or What business logic is in return.approval.matrix.line?

Response: To use the return.approval.matrix.line model, you need to provide values for required fields: approver. Readonly fields: sequence1, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: sequence1 [readonly] [computed] [no_copy]; approver [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.


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

Response: Foreign keys in account_account_ctm_dynamic_balance_sheet_report_rel: ctm_dynamic_balance_sheet_report_id -> ctm_dynamic_balance_sheet_report.id [constraint: account_account_ctm_dynamic_b_ctm_dynamic_balance_sheet_re_fkey]; account_account_id -> account_account.id [constraint: account_account_ctm_dynamic_balance_she_account_account_id_fkey]. Total foreign key relationships: 2. Referenced tables: account_account, ctm_dynamic_balance_sheet_report.


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

Response: Foreign keys in mr_internal_transfer: create_uid -> res_users.id [constraint: mr_internal_transfer_create_uid_fkey]; source_warehouse_id -> stock_warehouse.id [constraint: mr_internal_transfer_source_warehouse_id_fkey]; write_uid -> res_users.id [constraint: mr_internal_transfer_write_uid_fkey]. Total foreign key relationships: 3. Referenced tables: stock_warehouse, res_users.


Describe the implementation of ai.chat.session. or How is ai.chat.session implemented technically?

Response: The ai.chat.session model is defined in module: ai_chat_agent. It has 11 computed fields: auto_compress_enabled, compression_threshold, trim_ratio, message_count, last_activity, total_tokens_used, last_tokens_used, last_job_id, has_running_job, display_name, __last_update. Stored computed fields: message_count, last_activity, total_tokens_used, last_tokens_used, last_job_id. Related fields: auto_compress_enabled -> config_id.auto_compress_enabled, compression_threshold -> config_id.compression_threshold, trim_ratio -> config_id.trim_ratio. Original module methods: start_ai_iteration_async, continue_ai_iteration_async, resume_ai_iteration_async, _process_ai_iteration_async, _handle_length_finish_reason, _continue_response_for_length, get_session_status, _get_user_message_hash, _get_cached_system_prompt, cleanup_old_sessions, _check_and_handle_stuck_jobs, cleanup_stuck_jobs, action_ai_rename_session, _generate_ai_session_name, cron_auto_rename_sessions, get_user_frequent_actions, get_quick_replies, _execute_tools_async, _continue_iteration_async, _format_tool_result_for_ai_async, _setup_environment, _call_litellm_completion_api_async, _call_dashscope_with_retry_async, _call_openrouter_with_openai_sdk_async, _call_anthropic_with_retry_async, _call_vertex_ai_with_retry_async, _format_openai_response, _prepare_litellm_params, _convert_tools_for_response_mode, _cleanup_incomplete_tool_calls, _build_conversation_messages, _build_multimodal_content, _safe_token_counter, build_conversation_messages, _compress_messages, _compress_individual_messages, _compress_single_message, _trim_excess_messages, _trim_messages, _compute_statistics, _compute_last_job, _compute_job_status, create, action_pause_session, action_resume_session, action_end_session, action_open_chat_interface, action_ai_chat_message.


How is utm.campaign used in the system? or Tell me about the utm.campaign model.

Response: The utm.campaign model represents UTM Campaign in the ERP system. It contains 26 fields and is used to manage utm campaign data. Defined in module: utm. Key fields include: name, user_id, stage_id, tag_ids, is_website, color, click_count, use_leads, crm_lead_count, mailing_mail_ids, mailing_mail_count, received_ratio, opened_ratio, replied_ratio, bounced_ratio, quotation_count, invoiced_amount, company_id, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How to work with ai.memory fields? or What fields are readonly in ai.memory?

Response: To use the ai.memory model, you need to provide values for required fields: context, content, importance, collection_type, user_id. Readonly fields: name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [readonly] [computed] [no_copy]; context [required]; content [required]; importance [required] [has_default]; collection_type [required] [has_default]; user_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.


Explain the stock_warn_insufficient_qty_repair table schema. or What indexes exist on stock_warn_insufficient_qty_repair?

Response: The stock_warn_insufficient_qty_repair table has 10 columns and 5 foreign key relationships. It stores data related to stock warn insufficient qty repair in the system. The table has 1 indexes for performance optimization. Column types: integer: 6, double precision: 1, character varying: 1, timestamp without time zone: 2. Nullable columns: 5, columns with defaults: 1.


What is the purchase_order_report table? or What is stored in purchase_order_report?

Response: The purchase_order_report table has 8 columns and 3 foreign key relationships. It stores data related to purchase order report in the system. The table has 1 indexes for performance optimization. Column types: integer: 4, timestamp without time zone: 4. Nullable columns: 5, columns with defaults: 1.


What models are connected to sh.mrp.quality.alert? or What are the relationships in sh.mrp.quality.alert?

Response: The sh.mrp.quality.alert model has 21 relational fields: product_id -> product.product; lot_id -> stock.production.lot; user_id -> res.users; team_id -> sh.qc.team; tag_ids -> sh.qc.alert.tags; partner_id -> res.partner; stage_id -> sh.qc.alert.stage; mrp_id -> mrp.production; workorder_id -> mrp.workorder; company_id -> res.company; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: tag_ids, message_partner_ids, message_channel_ids. One2many fields: activity_ids, message_follower_ids, message_ids, website_message_ids.


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

Response: The product_template_barcode table has 11 columns and 6 foreign key relationships. It stores data related to product template barcode in the system. The table has 1 indexes for performance optimization. Column types: integer: 7, character varying: 1, timestamp without time zone: 2, boolean: 1. Nullable columns: 9, columns with defaults: 1.


What is the ir.property model? or What does the ir.property model represent?

Response: The ir.property model represents Company Property in the ERP system. It contains 18 fields and is used to manage company property data. Defined in module: base. Key fields include: name, res_id, company_id, fields_id, value_float, value_integer, value_text, value_binary, value_reference, value_datetime, type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Describe the field structure of sh.split.rfq.wizard. or What computed fields exist in sh.split.rfq.wizard?

Response: The sh.split.rfq.wizard model has 10 fields. Field types distribution: selection: 1, many2one: 3, one2many: 1, integer: 1, char: 1, datetime: 3. Computed fields: 2. Field details: split_by (selection) [required] [module: sh_all_in_one_purchase_tools]; purchase_order_id (many2one) -> purchase.order [module: sh_all_in_one_purchase_tools]; ps_order_ids (one2many) -> purchase.order.split [module: equip3_purchase_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 are the technical details of sh.mrp.qc.measurement? or Which fields are stored computed fields in sh.mrp.qc.measurement?

Response: The sh.mrp.qc.measurement model is defined in module: sh_inventory_mrp_qc. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: default_get, action_validate.


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

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


What fields are available in account_move_return_inter_transfer_company_rel? or Show me the column structure of account_move_return_inter_transfer_company_rel.

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


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

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


How do I use the account.root model? or What operations can I perform on account.root?

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


What are common use cases for gamification.challenge.line? or What business logic is in gamification.challenge.line?

Response: To use the gamification.challenge.line model, you need to provide values for required fields: challenge_id, definition_id, target_goal. Readonly fields: condition, definition_suffix, definition_monetary, definition_full_suffix, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: challenge_id [required]; definition_id [required]; target_goal [required]; name [computed] [no_copy]; condition [readonly] [computed] [no_copy]; definition_suffix [readonly] [computed] [no_copy]; definition_monetary [readonly] [computed] [no_copy]; definition_full_suffix [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 indexes exist on store_filters_groups? or What is stored in store_filters_groups?

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


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

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


What columns does account_journal_tax_report_rel have? or What is stored in account_journal_tax_report_rel?

Response: The account_journal_tax_report_rel table has 2 columns and 2 foreign key relationships. It stores data related to account journal tax report 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 account_move_line relate to other tables? or Show me the foreign key constraints of account_move_line.

Response: Foreign keys in account_move_line: account_id -> account_account.id [constraint: account_move_line_account_id_fkey]; analytic_account_id -> account_analytic_account.id [constraint: account_move_line_analytic_account_id_fkey]; asset_category_id -> account_asset_category.id [constraint: account_move_line_asset_category_id_fkey]; branch_id -> res_branch.id [constraint: account_move_line_branch_id_fkey]; company_currency_id -> res_currency.id [constraint: account_move_line_company_currency_id_fkey]; company_id -> res_company.id [constraint: account_move_line_company_id_fkey]; create_uid -> res_users.id [constraint: account_move_line_create_uid_fkey]; currency_id -> res_currency.id [constraint: account_move_line_currency_id_fkey]; customer_deposit_id -> customer_deposit.id [constraint: account_move_line_customer_deposit_id_fkey]; fiscal_year -> sh_fiscal_year.id [constraint: account_move_line_fiscal_year_fkey]; full_reconcile_id -> account_full_reconcile.id [constraint: account_move_line_full_reconcile_id_fkey]; journal_id -> account_journal.id [constraint: account_move_line_journal_id_fkey]; message_main_attachment_id -> ir_attachment.id [constraint: account_move_line_message_main_attachment_id_fkey]; move_id -> account_move.id [constraint: account_move_line_move_id_fkey]; partner_id -> res_partner.id [constraint: account_move_line_partner_id_fkey]; payment_id -> account_payment.id [constraint: account_move_line_payment_id_fkey]; period_id -> sh_account_period.id [constraint: account_move_line_period_id_fkey]; pos_branch_id -> res_branch.id [constraint: account_move_line_pos_branch_id_fkey]; product_id -> product_product.id [constraint: account_move_line_product_id_fkey]; product_uom_id -> uom_uom.id [constraint: account_move_line_product_uom_id_fkey]; purchase_line_id -> purchase_order_line.id [constraint: account_move_line_purchase_line_id_fkey]; reconcile_model_id -> account_reconcile_model.id [constraint: account_move_line_reconcile_model_id_fkey]; statement_id -> account_bank_statement.id [constraint: account_move_line_statement_id_fkey]; statement_line_id -> account_bank_statement_line.id [constraint: account_move_line_statement_line_id_fkey]; tax_group_id -> account_tax_group.id [constraint: account_move_line_tax_group_id_fkey]; tax_line_id -> account_tax.id [constraint: account_move_line_tax_line_id_fkey]; tax_repartition_line_id -> account_tax_repartition_line.id [constraint: account_move_line_tax_repartition_line_id_fkey]; vendor_deposit_id -> vendor_deposit.id [constraint: account_move_line_vendor_deposit_id_fkey]; write_uid -> res_users.id [constraint: account_move_line_write_uid_fkey]. Total foreign key relationships: 29. Referenced tables: product_product, account_bank_statement, sh_fiscal_year, purchase_order_line, res_company, ir_attachment, account_full_reconcile, account_bank_statement_line, account_move, account_journal, account_tax_repartition_line, account_tax_group, account_account, res_currency, res_users, res_branch, account_analytic_account, res_partner, account_tax, customer_deposit, vendor_deposit, account_reconcile_model, account_payment, sh_account_period, account_asset_category, uom_uom.


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

Response: Columns in apps_installation_activity_log: id (integer) [NOT NULL] [DEFAULT: nextval('apps_installation_activity_log_id_seq'::regclass)] [PRECISION: 32]; activity_date (timestamp without time zone) [COMMENT: Activity Date]; module_name (character varying) [COMMENT: Module Name]; technical_name (character varying) [COMMENT: Technical Name]; latest_version (character varying) [COMMENT: Latest Version]; user_id (integer) [PRECISION: 32] [COMMENT: User]; activity (character varying) [COMMENT: Activity]; description (text) [COMMENT: Description]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 12. Statistics: 11 nullable, 1 with defaults, 0 with length constraints.


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

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


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

Response: Columns in approved_users_purchase_request_patner_rel: request_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.


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

Response: Foreign keys in account_analytic_default_account_analytic_tag_rel: account_analytic_default_id -> account_analytic_default.id [constraint: account_analytic_default_accou_account_analytic_default_id_fkey]; account_analytic_tag_id -> account_analytic_tag.id [constraint: account_analytic_default_account_a_account_analytic_tag_id_fkey]. Total foreign key relationships: 2. Referenced tables: account_analytic_default, account_analytic_tag.


What are common use cases for account.financial.ratio? or How to create records in account.financial.ratio?

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


What data can be stored in ks.sales.forecast? or Describe the field structure of ks.sales.forecast.

Response: The ks.sales.forecast model has 69 fields. Field types distribution: char: 7, boolean: 11, selection: 8, binary: 1, many2one: 6, datetime: 5, many2many: 3, integer: 20, text: 2, one2many: 4, date: 2. Computed fields: 24. Field details: ks_name (char) [readonly] [module: ks_sales_forecast]; ks_is_file (boolean) [module: ks_sales_forecast]; ks_file_type (selection) [module: ks_sales_forecast]; ks_import_file (binary) [module: ks_sales_forecast]; ks_file_name (char) [module: ks_sales_forecast]; ks_is_method_change (boolean) [module: ks_sales_forecast]; ks_forecast_method (selection) [module: ks_sales_forecast]; ks_default_forecast_method (selection) [readonly] [compute: ks_default_forecast_method_value] [stored] [module: ks_sales_forecast]; ks_predicted_forecast_method (char) [module: ks_sales_forecast]; ks_model (many2one) [readonly] -> ir.model [module: ks_sales_forecast]; ks_start_date (datetime) [required] [module: ks_sales_forecast]; ks_end_date (datetime) [required] [module: ks_sales_forecast]; ks_forecast_base (selection) [module: ks_sales_forecast]; ks_product_ids (many2many) -> product.product [module: ks_sales_forecast]; ks_p (integer) [module: ks_sales_forecast]; ks_d (integer) [module: ks_sales_forecast]; ks_q (integer) [module: ks_sales_forecast]; ks_P (integer) [module: ks_sales_forecast]; ks_D (integer) [module: ks_sales_forecast]; ks_Q (integer) [module: ks_sales_forecast]; ks_m (integer) [module: ks_sales_forecast]; ks_trend (selection) [module: ks_sales_forecast]; ks_forecast_unit (integer) [required] [module: ks_sales_forecast]; ks_forecast_period (selection) [required] [module: ks_sales_forecast]; ks_is_predicted (boolean) [module: ks_sales_forecast]; ks_is_predicted_method (boolean) [readonly] [compute: ks_compute_predicted_method] [not stored] [module: ks_sales_forecast]; ks_chart_data (text) [module: ks_sales_forecast]; ks_report_data (text) [module: ks_sales_forecast]; ks_graph_view (integer) [module: ks_sales_forecast]; ks_outcome (boolean) [module: ks_sales_forecast]; ks_danger_outcome (boolean) [module: ks_sales_forecast]; ks_resp (integer) [readonly] [module: ks_sales_forecast]; ks_resd (integer) [readonly] [module: ks_sales_forecast]; ks_resq (integer) [readonly] [module: ks_sales_forecast]; ks_sp (integer) [readonly] [module: ks_sales_forecast]; ks_sd (integer) [readonly] [module: ks_sales_forecast]; ks_sq (integer) [readonly] [module: ks_sales_forecast]; activity_ids (one2many) -> mail.activity [module: mail]; activity_state (selection) [readonly] [compute: _compute_activity_state] [not stored] [module: mail]; activity_user_id (many2one) -> res.users [compute: <bound method Field._compute_related of ks.sales.forecast.activity_user_id>] [not stored] [module: mail] [related: activity_ids.user_id] [inverse: <bound method Field._inverse_related of ks.sales.forecast.activity_user_id>]; activity_type_id (many2one) -> mail.activity.type [compute: <bound method Field._compute_related of ks.sales.forecast.activity_type_id>] [not stored] [module: mail] [related: activity_ids.activity_type_id] [inverse: <bound method Field._inverse_related of ks.sales.forecast.activity_type_id>]; activity_type_icon (char) [readonly] [compute: <bound method Field._compute_related of ks.sales.forecast.activity_type_icon>] [not stored] [module: mail] [related: activity_ids.icon]; activity_date_deadline (date) [readonly] [compute: _compute_activity_date_deadline] [not stored] [module: mail]; my_activity_date_deadline (date) [readonly] [compute: _compute_my_activity_date_deadline] [not stored] [module: mail]; activity_summary (char) [compute: <bound method Field._compute_related of ks.sales.forecast.activity_summary>] [not stored] [module: mail] [related: activity_ids.summary] [inverse: <bound method Field._inverse_related of ks.sales.forecast.activity_summary>]; activity_exception_decoration (selection) [readonly] [compute: _compute_activity_exception_type] [not stored] [module: mail]; activity_exception_icon (char) [readonly] [compute: _compute_activity_exception_type] [not stored] [module: mail]; 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].


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

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


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

Response: Foreign keys in return_picking_rel: account_move_id -> account_move.id [constraint: return_picking_rel_account_move_id_fkey]; stock_picking_id -> stock_picking.id [constraint: return_picking_rel_stock_picking_id_fkey]. Total foreign key relationships: 2. Referenced tables: stock_picking, account_move.


What methods are available in account.bank.statement? or What methods are defined in account.bank.statement original module?

Response: The account.bank.statement model is defined in module: account. It has 30 computed fields: balance_start, balance_end_real, currency_id, journal_type, company_id, total_entry_encoding, balance_end, difference, move_line_count, all_lines_reconciled, is_difference_zero, previous_statement_id, is_valid_balance_start, country_code, account_id, 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, sequence_prefix, sequence_number, display_name, __last_update. Stored computed fields: balance_start, balance_end_real, company_id, total_entry_encoding, balance_end, difference, previous_statement_id, is_valid_balance_start, sequence_prefix, sequence_number. Related fields: journal_type -> journal_id.type, company_id -> journal_id.company_id, country_code -> company_id.country_id.code, account_id -> journal_id.default_account_id. Original module methods: _compute_starting_balance, _compute_ending_balance, _end_balance, _is_difference_zero, _compute_currency, _get_move_line_count, _default_journal, _compute_is_valid_balance_start, _get_previous_statement, write, create, _compute_all_lines_reconciled, onchange_journal_id, _check_balance_end_real_same_as_computed, unlink, _check_journal, _constrains_date_sequence, open_cashbox_id, button_post, button_validate, button_validate_or_action, button_reopen, button_reprocess, button_journal_entries, _get_last_sequence_domain, _get_starting_sequence, _message_post_process_attachments, init, _compute_split_sequence, _deduce_sequence_number_reset, _get_last_sequence, _get_sequence_format_param, _set_next_sequence.


What methods are available in sh.stock.move.pass.fail? or What are the technical details of sh.stock.move.pass.fail?

Response: The sh.stock.move.pass.fail model is defined in module: sh_inventory_mrp_qc. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: default_get, action_pass, action_fail.


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

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


What computed fields exist in mail.activity.mixin? or What are the available fields for mail.activity.mixin?

Response: The mail.activity.mixin model has 13 fields. Field types distribution: one2many: 1, selection: 2, many2one: 2, char: 4, date: 2, integer: 1, datetime: 1. Computed fields: 11. Field details: activity_ids (one2many) [readonly] -> mail.activity [module: mail]; activity_state (selection) [readonly] [compute: _compute_activity_state] [not stored] [module: mail]; activity_user_id (many2one) [readonly] -> res.users [compute: <bound method Field._compute_related of mail.activity.mixin.activity_user_id>] [not stored] [module: mail] [related: activity_ids.user_id] [inverse: <bound method Field._inverse_related of mail.activity.mixin.activity_user_id>]; activity_type_id (many2one) [readonly] -> mail.activity.type [compute: <bound method Field._compute_related of mail.activity.mixin.activity_type_id>] [not stored] [module: mail] [related: activity_ids.activity_type_id] [inverse: <bound method Field._inverse_related of mail.activity.mixin.activity_type_id>]; activity_type_icon (char) [readonly] [compute: <bound method Field._compute_related of mail.activity.mixin.activity_type_icon>] [not stored] [module: mail] [related: activity_ids.icon]; activity_date_deadline (date) [readonly] [compute: _compute_activity_date_deadline] [not stored] [module: mail]; my_activity_date_deadline (date) [readonly] [compute: _compute_my_activity_date_deadline] [not stored] [module: mail]; activity_summary (char) [readonly] [compute: <bound method Field._compute_related of mail.activity.mixin.activity_summary>] [not stored] [module: mail] [related: activity_ids.summary] [inverse: <bound method Field._inverse_related of mail.activity.mixin.activity_summary>]; activity_exception_decoration (selection) [readonly] [compute: _compute_activity_exception_type] [not stored] [module: mail]; activity_exception_icon (char) [readonly] [compute: _compute_activity_exception_type] [not stored] [module: mail]; 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 field structure of account.ebupot. or Which fields are required in account.ebupot?

Response: The account.ebupot model has 18 fields. Field types distribution: many2one: 5, char: 3, boolean: 1, one2many: 1, selection: 1, date: 2, binary: 1, integer: 1, datetime: 3. Computed fields: 3. Field details: year (many2one) -> sh.fiscal.year [module: equip3_accounting_efaktur]; name (char) [module: equip3_accounting_efaktur]; is_used (boolean) [module: equip3_accounting_efaktur]; invoice_ids (one2many) -> account.move [module: equip3_accounting_efaktur]; tax_report_id (selection) [module: equip3_accounting_efaktur]; date_from (date) [module: equip3_accounting_efaktur]; date_to (date) [module: equip3_accounting_efaktur]; partner_id (many2one) -> res.partner [module: equip3_accounting_efaktur]; company_id (many2one) [readonly] -> res.company [module: equip3_accounting_efaktur]; ebupot_template (binary) [readonly] [compute: _get_template] [not stored] [module: equip3_accounting_efaktur]; tahun_pajak (char) [module: equip3_accounting_efaktur]; 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 data can be stored in report.equip3_inventory_reports.expiring_product_calendar? or List all fields in the report.equip3_inventory_reports.expiring_product_calendar model.

Response: The report.equip3_inventory_reports.expiring_product_calendar 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 journal_account_type_control_rel table structure. or Tell me about the journal_account_type_control_rel table.

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


What models are connected to gamification.goal.wizard? or List all relational fields in gamification.goal.wizard.

Response: The gamification.goal.wizard model has 3 relational fields: goal_id -> gamification.goal; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


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

Response: Foreign keys in account_bank_statement_closebalance: create_uid -> res_users.id [constraint: account_bank_statement_closebalance_create_uid_fkey]; write_uid -> res_users.id [constraint: account_bank_statement_closebalance_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


List all relational fields in sh.product.qrcode.generator.wizard. or Describe the many2many relations for sh.product.qrcode.generator.wizard.

Response: The sh.product.qrcode.generator.wizard model has 4 relational fields: product_tmpl_ids -> product.template; product_var_ids -> product.product; create_uid -> res.users; write_uid -> res.users. Many2many fields: product_tmpl_ids, product_var_ids. One2many fields: none.


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

Response: Foreign keys in stock_picking: assembly_id -> assembly_production_record.id [constraint: stock_picking_assembly_id_fkey]; backorder_id -> stock_picking.id [constraint: stock_picking_backorder_id_fkey]; batch_id -> stock_picking_batch.id [constraint: stock_picking_batch_id_fkey]; branch_id -> res_branch.id [constraint: stock_picking_branch_id_fkey]; branch_id -> res_branch.id [constraint: stock_picking_branch_id_fkey1]; branch_id -> res_branch.id [constraint: stock_picking_branch_id_fkey10]; branch_id -> res_branch.id [constraint: stock_picking_branch_id_fkey11]; branch_id -> res_branch.id [constraint: stock_picking_branch_id_fkey12]; branch_id -> res_branch.id [constraint: stock_picking_branch_id_fkey13]; branch_id -> res_branch.id [constraint: stock_picking_branch_id_fkey14]; branch_id -> res_branch.id [constraint: stock_picking_branch_id_fkey15]; branch_id -> res_branch.id [constraint: stock_picking_branch_id_fkey16]; branch_id -> res_branch.id [constraint: stock_picking_branch_id_fkey17]; branch_id -> res_branch.id [constraint: stock_picking_branch_id_fkey18]; branch_id -> res_branch.id [constraint: stock_picking_branch_id_fkey19]; branch_id -> res_branch.id [constraint: stock_picking_branch_id_fkey2]; branch_id -> res_branch.id [constraint: stock_picking_branch_id_fkey20]; branch_id -> res_branch.id [constraint: stock_picking_branch_id_fkey21]; branch_id -> res_branch.id [constraint: stock_picking_branch_id_fkey22]; branch_id -> res_branch.id [constraint: stock_picking_branch_id_fkey23]; branch_id -> res_branch.id [constraint: stock_picking_branch_id_fkey24]; branch_id -> res_branch.id [constraint: stock_picking_branch_id_fkey3]; branch_id -> res_branch.id [constraint: stock_picking_branch_id_fkey4]; branch_id -> res_branch.id [constraint: stock_picking_branch_id_fkey5]; branch_id -> res_branch.id [constraint: stock_picking_branch_id_fkey6]; branch_id -> res_branch.id [constraint: stock_picking_branch_id_fkey7]; branch_id -> res_branch.id [constraint: stock_picking_branch_id_fkey8]; branch_id -> res_branch.id [constraint: stock_picking_branch_id_fkey9]; carrier_id -> delivery_carrier.id [constraint: stock_picking_carrier_id_fkey]; company_id -> res_company.id [constraint: stock_picking_company_id_fkey]; create_uid -> res_users.id [constraint: stock_picking_create_uid_fkey]; customer_partner_id -> res_partner.id [constraint: stock_picking_customer_partner_id_fkey]; group_id -> procurement_group.id [constraint: stock_picking_group_id_fkey]; internal_transfer_line_id -> internal_transfer_line.id [constraint: stock_picking_internal_transfer_line_id_fkey]; kitchen_id -> kitchen_production_record.id [constraint: stock_picking_kitchen_id_fkey]; kitchen_outlet_warehouse_id -> stock_warehouse.id [constraint: stock_picking_kitchen_outlet_warehouse_id_fkey]; kitchen_warehouse_id -> stock_warehouse.id [constraint: stock_picking_kitchen_warehouse_id_fkey]; location_dest_id -> stock_location.id [constraint: stock_picking_location_dest_id_fkey]; location_id -> stock_location.id [constraint: stock_picking_location_id_fkey]; message_main_attachment_id -> ir_attachment.id [constraint: stock_picking_message_main_attachment_id_fkey]; mr_id -> material_request.id [constraint: stock_picking_mr_id_fkey]; operation_warehouse_id -> stock_warehouse.id [constraint: stock_picking_operation_warehouse_id_fkey]; owner_id -> res_partner.id [constraint: stock_picking_owner_id_fkey]; partner_id -> res_partner.id [constraint: stock_picking_partner_id_fkey]; picking_batch_id -> stock_picking_batch.id [constraint: stock_picking_picking_batch_id_fkey]; picking_type_id -> stock_picking_type.id [constraint: stock_picking_picking_type_id_fkey]; pos_branch_id -> res_branch.id [constraint: stock_picking_pos_branch_id_fkey]; pos_order_id -> pos_order.id [constraint: stock_picking_pos_order_id_fkey]; pos_session_id -> pos_session.id [constraint: stock_picking_pos_session_id_fkey]; purchase_id -> purchase_order.id [constraint: stock_picking_purchase_id_fkey]; report_template_id1 -> ir_act_report_xml.id [constraint: stock_picking_report_template_id1_fkey]; report_template_id -> ir_act_report_xml.id [constraint: stock_picking_report_template_id_fkey]; rma_id -> dev_rma_rma.id [constraint: stock_picking_rma_id_fkey]; sale_id -> sale_order.id [constraint: stock_picking_sale_id_fkey]; stage_id -> order_stage.id [constraint: stock_picking_stage_id_fkey]; transfer_id -> internal_transfer.id [constraint: stock_picking_transfer_id_fkey]; user_id -> res_users.id [constraint: stock_picking_user_id_fkey]; warehouse_id -> stock_warehouse.id [constraint: stock_picking_warehouse_id_fkey]; website_id -> website.id [constraint: stock_picking_website_id_fkey]; write_uid -> res_users.id [constraint: stock_picking_write_uid_fkey]. Total foreign key relationships: 60. Referenced tables: stock_picking_batch, order_stage, stock_location, res_company, ir_attachment, procurement_group, assembly_production_record, material_request, stock_picking_type, stock_picking, res_users, res_branch, stock_warehouse, website, delivery_carrier, res_partner, ir_act_report_xml, sale_order, pos_order, internal_transfer_line, dev_rma_rma, pos_session, kitchen_production_record, purchase_order, internal_transfer.


Which fields are required in ir.rule? or What are the available fields for ir.rule?

Response: The ir.rule model has 17 fields. Field types distribution: char: 2, boolean: 6, many2one: 3, many2many: 1, text: 1, integer: 1, datetime: 3. Computed fields: 3. Field details: name (char) [module: base]; active (boolean) [module: base]; model_id (many2one) [required] -> ir.model [module: base]; groups (many2many) -> res.groups [module: base]; domain_force (text) [module: base]; perm_read (boolean) [module: base]; perm_write (boolean) [module: base]; perm_create (boolean) [module: base]; perm_unlink (boolean) [module: base]; global (boolean) [readonly] [compute: _compute_global] [stored] [module: base]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


Show me the foreign key constraints of dev_rma_line_stock_picking_rel. or How does dev_rma_line_stock_picking_rel relate to other tables?

Response: Foreign keys in dev_rma_line_stock_picking_rel: dev_rma_line_id -> dev_rma_line.id [constraint: dev_rma_line_stock_picking_rel_dev_rma_line_id_fkey]; stock_picking_id -> stock_picking.id [constraint: dev_rma_line_stock_picking_rel_stock_picking_id_fkey]. Total foreign key relationships: 2. Referenced tables: stock_picking, dev_rma_line.


What are the relationships in sh.report.template? or Show me the relational structure of sh.report.template.

Response: The sh.report.template model has 4 relational fields: section_line -> sh.report.section; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: section_line.


What does the sh.model.fields.global.selection model represent? or Describe the sh.model.fields.global.selection model in Odoo.

Response: The sh.model.fields.global.selection model represents Custom Field Model description in the ERP system. It contains 11 fields and is used to manage custom field model description data. Defined in module: sh_global_custom_fields. Key fields include: sh_field_id, value, name, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: The mr_approval_matrix_line table has 16 columns and 6 foreign key relationships. It stores data related to mr approval matrix line in the system. The table has 2 indexes for performance optimization. Column types: integer: 10, text: 1, timestamp without time zone: 3, character varying: 1, boolean: 1. Nullable columns: 14, columns with defaults: 1.


How is invoice.confirmation.availability used in the system? or Can you explain the purpose of invoice.confirmation.availability?

Response: The invoice.confirmation.availability model represents Confirmation Wizard in the ERP system. It contains 10 fields and is used to manage confirmation wizard data. Defined in module: equip3_accounting_operation. Key fields include: message, invoice_id, whatsapp, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How is pos.sale.analytic implemented technically? or What methods are available in pos.sale.analytic?

Response: The pos.sale.analytic model is defined in module: equip3_pos_general. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: _sale_order_select, _pos_order_select, init.


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

Response: Columns in product_margin: id (integer) [NOT NULL] [DEFAULT: nextval('product_margin_id_seq'::regclass)] [PRECISION: 32]; from_date (date) [COMMENT: From]; to_date (date) [COMMENT: To]; invoice_state (character varying) [NOT NULL] [COMMENT: Invoice State]; 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: 6 nullable, 1 with defaults, 0 with length constraints.


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

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


List all constraint names in link_tracker_click. or What are the foreign keys in link_tracker_click?

Response: Foreign keys in link_tracker_click: campaign_id -> utm_campaign.id [constraint: link_tracker_click_campaign_id_fkey]; country_id -> res_country.id [constraint: link_tracker_click_country_id_fkey]; create_uid -> res_users.id [constraint: link_tracker_click_create_uid_fkey]; link_id -> link_tracker.id [constraint: link_tracker_click_link_id_fkey]; mailing_trace_id -> mailing_trace.id [constraint: link_tracker_click_mailing_trace_id_fkey]; mass_mailing_id -> mailing_mailing.id [constraint: link_tracker_click_mass_mailing_id_fkey]; write_uid -> res_users.id [constraint: link_tracker_click_write_uid_fkey]. Total foreign key relationships: 7. Referenced tables: link_tracker, res_country, mailing_mailing, res_users, mailing_trace, utm_campaign.


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

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


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

Response: Columns in pos_promotion_discount_category: id (integer) [NOT NULL] [DEFAULT: nextval('pos_promotion_discount_category_id_seq'::regclass)] [PRECISION: 32]; active (boolean) [COMMENT: Active]; category_id (integer) [PRECISION: 32] [COMMENT: POS Category]; discount (double precision) [PRECISION: 53] [COMMENT: Discount %]; min_qty (double precision) [PRECISION: 53] [COMMENT: Min QTY]; discount2 (double precision) [PRECISION: 53] [COMMENT: Discount % 2]; multi_discount (character varying) [COMMENT: Multi Discount]; promotion_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Promotion]; discount_fixed_amount (double precision) [PRECISION: 53] [COMMENT: Fixed Amount Discount]; max_discount_amount (double precision) [PRECISION: 53] [COMMENT: Max. 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]. Total columns: 14. Statistics: 12 nullable, 1 with defaults, 0 with length constraints.


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

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


What one2many fields are in account.analytic.default? or What are the relationships in account.analytic.default?

Response: The account.analytic.default model has 19 relational fields: analytic_id -> account.analytic.account; analytic_tag_ids -> account.analytic.tag; product_id -> product.product; user_id -> res.users; company_id -> res.company; partner_id -> res.partner; account_id -> account.account; branch_id -> res.branch; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: analytic_tag_ids, message_partner_ids, message_channel_ids. One2many fields: activity_ids, message_follower_ids, message_ids, website_message_ids.


What modules define account.payment.method? or Which fields in account.payment.method are computed?

Response: The account.payment.method 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: .


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

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


What are the foreign keys in purchase_requisition? or List all constraint names in purchase_requisition.

Response: Foreign keys in purchase_requisition: branch_id -> res_branch.id [constraint: purchase_requisition_branch_id_fkey]; company_id -> res_company.id [constraint: purchase_requisition_company_id_fkey]; create_uid -> res_users.id [constraint: purchase_requisition_create_uid_fkey]; currency_id -> res_currency.id [constraint: purchase_requisition_currency_id_fkey]; destination_warehouse -> stock_warehouse.id [constraint: purchase_requisition_destination_warehouse_fkey]; message_main_attachment_id -> ir_attachment.id [constraint: purchase_requisition_message_main_attachment_id_fkey]; picking_type_id -> stock_picking_type.id [constraint: purchase_requisition_picking_type_id_fkey]; purchase_id -> purchase_order.id [constraint: purchase_requisition_purchase_id_fkey]; purchase_request_id -> purchase_request.id [constraint: purchase_requisition_purchase_request_id_fkey]; type_id -> purchase_requisition_type.id [constraint: purchase_requisition_type_id_fkey]; user_id -> res_users.id [constraint: purchase_requisition_user_id_fkey]; vendor_id -> res_partner.id [constraint: purchase_requisition_vendor_id_fkey]; warehouse_id -> stock_warehouse.id [constraint: purchase_requisition_warehouse_id_fkey]; write_uid -> res_users.id [constraint: purchase_requisition_write_uid_fkey]. Total foreign key relationships: 14. Referenced tables: stock_warehouse, purchase_requisition_type, stock_picking_type, res_partner, purchase_request, res_company, ir_attachment, res_currency, res_users, purchase_order, res_branch.


What columns have default values in dev_credit_note_wizard_purchase_order_rel? or What are the column types in dev_credit_note_wizard_purchase_order_rel?

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


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

Response: Foreign keys in stock_return_product: product_id -> product_product.id [constraint: stock_return_product_product_id_fkey]; return_id -> asp_asm_stock.id [constraint: stock_return_product_return_id_fkey]. Total foreign key relationships: 2. Referenced tables: product_product, asp_asm_stock.


How is sh.model.fields.purchase.order.selection used in the system? or What does the sh.model.fields.purchase.order.selection model represent?

Response: The sh.model.fields.purchase.order.selection model represents Field Selection in the ERP system. It contains 11 fields and is used to manage field selection data. Defined in module: sh_all_in_one_purchase_tools. Key fields include: sh_field_po_id, value, name, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: Columns in wizard_asset_create: id (integer) [NOT NULL] [DEFAULT: nextval('wizard_asset_create_id_seq'::regclass)] [PRECISION: 32]; date (date) [COMMENT: Date]; first_depreciation_manual_date (date) [COMMENT: First Depreciation Date]; salvage_value (double precision) [PRECISION: 53] [COMMENT: Salvage Value]; method (character varying) [COMMENT: Computation Method]; method_time (character varying) [COMMENT: Time Method Based On]; prorata (boolean) [COMMENT: Prorata Temporis]; cut_off_asset_date (integer) [PRECISION: 32] [COMMENT: Cut Off Asset Date]; method_number_fiscal (integer) [PRECISION: 32] [COMMENT: Number of Depreciations]; method_period_fiscal (integer) [PRECISION: 32] [COMMENT: Number of Months in a Period]; 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: 14. Statistics: 13 nullable, 1 with defaults, 0 with length constraints.


What business logic is in ai.chat.session? or How do I use the ai.chat.session model?

Response: To use the ai.chat.session model, you need to provide values for required fields: name, user_id, config_id, state. Readonly fields: auto_compress_enabled, compression_threshold, trim_ratio, message_count, last_activity, total_tokens_used, last_tokens_used, last_job_id, has_running_job, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [required] [has_default]; user_id [required] [has_default]; config_id [required]; state [required] [has_default] [no_copy]; auto_compress_enabled [readonly] [computed] [no_copy]; compression_threshold [readonly] [computed] [no_copy]; trim_ratio [readonly] [computed] [no_copy]; message_count [readonly] [computed] [no_copy]; last_activity [readonly] [computed] [no_copy]; total_tokens_used [readonly] [computed] [no_copy]; last_tokens_used [readonly] [computed] [no_copy]; last_job_id [readonly] [computed] [no_copy]; has_running_job [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 modules define account.analytic.group? or What is the module hierarchy for account.analytic.group?

Response: The account.analytic.group model is defined in module: analytic. It has 23 computed fields: complete_name, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, display_name, __last_update. Stored computed fields: complete_name. Related fields: activity_user_id -> activity_ids.user_id, activity_type_id -> activity_ids.activity_type_id, activity_type_icon -> activity_ids.icon, activity_summary -> activity_ids.summary. Original module methods: _compute_complete_name.


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

Response: The customer_voucher table has 12 columns and 4 foreign key relationships. It stores data related to customer voucher in the system. The table has 1 indexes for performance optimization. Column types: integer: 5, character varying: 2, date: 2, boolean: 1, timestamp without time zone: 2. Nullable columns: 11, columns with defaults: 1.


How is restaurant.printer used in the system? or Tell me about the restaurant.printer model.

Response: The restaurant.printer model represents Restaurant Printer in the ERP system. It contains 12 fields and is used to manage restaurant printer data. Defined in module: pos_restaurant. Key fields include: name, proxy_ip, product_categories_ids, printer_type, epson_printer_ip, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What is the module hierarchy for gamification.karma.tracking? or Which fields are stored computed fields in gamification.karma.tracking?

Response: The gamification.karma.tracking model is defined in module: gamification. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: _consolidate_last_month, _process_consolidate.


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

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


What data can be stored in analytic.priority? or Show me the fields of analytic.priority.

Response: The analytic.priority model has 9 fields. Field types distribution: integer: 2, selection: 1, char: 1, many2one: 2, datetime: 3. Computed fields: 2. Field details: priority (integer) [module: equip3_accounting_analytical]; object_id (selection) [module: equip3_accounting_analytical]; 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 bve_view_res_groups_rel? or Which columns are nullable in bve_view_res_groups_rel?

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


What is stored in pos_service_charge? or What columns does pos_service_charge have?

Response: The pos_service_charge table has 13 columns and 5 foreign key relationships. It stores data related to pos service charge in the system. The table has 1 indexes for performance optimization. Column types: integer: 6, character varying: 2, double precision: 3, timestamp without time zone: 2. Nullable columns: 8, columns with defaults: 1.


What methods are defined in mail.message.subtype original module? or What modules define mail.message.subtype?

Response: The mail.message.subtype model is defined in module: mail. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: create, write, unlink, _get_auto_subscription_subtypes, default_subtypes, _default_subtypes, _valid_field_parameter, _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.


What relationships exist for pos_account_cashbox_line? or Describe the relational structure of pos_account_cashbox_line.

Response: Foreign keys in pos_account_cashbox_line: create_uid -> res_users.id [constraint: pos_account_cashbox_line_create_uid_fkey]; pos_config_id -> pos_config.id [constraint: pos_account_cashbox_line_pos_config_id_fkey]; write_uid -> res_users.id [constraint: pos_account_cashbox_line_write_uid_fkey]. Total foreign key relationships: 3. Referenced tables: pos_config, res_users.


What one2many fields are in ks_ninja_dashboard.item_action? or Describe the many2many relations for ks_ninja_dashboard.item_action.

Response: The ks_ninja_dashboard.item_action model has 5 relational fields: ks_dashboard_item_ids -> ks_dashboard_ninja.item; ks_dashboard_ninja_id -> ks_dashboard_ninja.board; ks_dashboard_ninja_ids -> ks_dashboard_ninja.board; create_uid -> res.users; write_uid -> res.users. Many2many fields: ks_dashboard_item_ids, ks_dashboard_ninja_ids. One2many fields: none.


What business logic is in mail.thread.blacklist? or How to work with mail.thread.blacklist fields?

Response: To use the mail.thread.blacklist model, you need to provide values for required fields: none. Readonly fields: email_normalized, is_blacklisted, message_bounce, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, __last_update. Field usage details: email_normalized [readonly] [computed] [no_copy]; is_blacklisted [readonly] [computed] [no_copy]; message_bounce [readonly] [has_default]; message_is_follower [readonly] [computed] [no_copy]; message_follower_ids [readonly] [no_copy]; message_partner_ids [readonly] [computed] [no_copy]; message_channel_ids [readonly] [computed] [no_copy]; message_ids [readonly] [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_main_attachment_id [readonly] [no_copy]; website_message_ids [readonly] [no_copy]; message_has_sms_error [readonly] [computed] [no_copy]; id [readonly]; display_name [readonly] [computed] [no_copy]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


What is stored in kitchen_safety_stock_line? or What is the kitchen_safety_stock_line table?

Response: The kitchen_safety_stock_line table has 8 columns and 4 foreign key relationships. It stores data related to kitchen safety stock line in the system. The table has 1 indexes for performance optimization. Column types: integer: 5, numeric: 1, timestamp without time zone: 2. Nullable columns: 4, columns with defaults: 1.


What fields does ks_dashboard_ninja.ks_grid_per_company have? or What data can be stored in ks_dashboard_ninja.ks_grid_per_company?

Response: The ks_dashboard_ninja.ks_grid_per_company model has 11 fields. Field types distribution: char: 3, many2one: 4, integer: 1, datetime: 3. Computed fields: 2. Field details: name (char) [module: ks_dashboard_ninja]; ks_dashboard_ninja_id (many2one) -> ks_dashboard_ninja.board [module: ks_dashboard_ninja]; ks_gridstack_config (char) [module: ks_dashboard_ninja]; ks_company_id (many2one) -> res.company [module: ks_dashboard_ninja]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


How to query res.users.log data? or How to create records in res.users.log?

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


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

Response: The coupon_reward_product_product_rel table has 2 columns and 2 foreign key relationships. It stores data related to coupon reward product product 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 ks.sales.forecast.report relate to other models? or Show me the relational structure of ks.sales.forecast.report.

Response: The ks.sales.forecast.report model has 3 relational fields: binding_model_id -> ir.model; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


What methods are available in ir.qweb.field.float? or What modules define ir.qweb.field.float?

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


Can you explain the purpose of res.users.qiscuss? or What is the res.users.qiscuss model?

Response: The res.users.qiscuss model represents Res Users Qiscuss Access in the ERP system. It contains 10 fields and is used to manage res users qiscuss access data. Defined in module: equip3_crm_whatsapp. Key fields include: user_id, email, password, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

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


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

Response: The sh_correct_qc_measurement table has 11 columns and 5 foreign key relationships. It stores data related to sh correct qc measurement in the system. The table has 1 indexes for performance optimization. Column types: integer: 6, double precision: 1, text: 2, timestamp without time zone: 2. Nullable columns: 10, columns with defaults: 1.


How to work with mail.bot fields? or What are common use cases for mail.bot?

Response: To use the mail.bot 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.


Can you explain the purpose of vendor.payment.request? or Describe the vendor.payment.request model in Odoo.

Response: The vendor.payment.request model represents Vendor Payment Request in the ERP system. It contains 16 fields and is used to manage vendor payment request data. Defined in module: equip3_purchase_operation. Key fields include: name, user_id, description, company_id, branch_id, component_line_id, state, amount_total, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What are the foreign keys in hr_employee_mrp_labor_group_rel? or What tables does hr_employee_mrp_labor_group_rel reference?

Response: Foreign keys in hr_employee_mrp_labor_group_rel: hr_employee_id -> hr_employee.id [constraint: hr_employee_mrp_labor_group_rel_hr_employee_id_fkey]; mrp_labor_group_id -> mrp_labor_group.id [constraint: hr_employee_mrp_labor_group_rel_mrp_labor_group_id_fkey]. Total foreign key relationships: 2. Referenced tables: hr_employee, mrp_labor_group.


How is kpi.measure.item implemented technically? or What methods are defined in kpi.measure.item original module?

Response: The kpi.measure.item model is defined in module: kpi_scorecard. It has 7 computed fields: model_id, model_name, measure_type, existing_kpi, help_notes, display_name, __last_update. Stored computed fields: model_id, model_name, measure_type. Related fields: model_id -> measure_id.model_id, model_name -> measure_id.model_name, measure_type -> measure_id.measure_type, existing_kpi -> measure_id.existing_kpi. Original module methods: unlink, _calculate_for_period, _compute_show_kpi_help.


How is theme.ir.ui.view implemented technically? or What are the technical details of theme.ir.ui.view?

Response: The theme.ir.ui.view model is defined in module: website. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: compute_arch_fs, _convert_to_base_model, get_base_url, get_website_meta.


What operations can I perform on ir.qweb.field.contact? or What fields are readonly in ir.qweb.field.contact?

Response: To use the ir.qweb.field.contact 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 can be stored in resource.calendar.attendance? or Show me the fields of resource.calendar.attendance.

Response: The resource.calendar.attendance model has 20 fields. Field types distribution: char: 2, selection: 4, date: 2, float: 2, many2one: 4, boolean: 1, integer: 2, datetime: 3. Computed fields: 3. Field details: name (char) [required] [module: resource]; dayofweek (selection) [required] [module: resource]; date_from (date) [module: resource]; date_to (date) [module: resource]; hour_from (float) [required] [module: resource]; hour_to (float) [required] [module: resource]; calendar_id (many2one) [required] -> resource.calendar [module: resource]; day_period (selection) [required] [module: resource]; resource_id (many2one) -> resource.resource [module: resource]; week_type (selection) [module: resource]; two_weeks_calendar (boolean) [readonly] [compute: <bound method Field._compute_related of resource.calendar.attendance.two_weeks_calendar>] [not stored] [module: resource] [related: calendar_id.two_weeks_calendar]; display_type (selection) [module: resource]; sequence (integer) [module: resource]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


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

Response: The res_partner table has 189 columns and 38 foreign key relationships. It stores data related to res partner in the system. The table has 12 indexes for performance optimization. Column types: integer: 47, character varying: 69, timestamp without time zone: 5, date: 9, text: 12, double precision: 14, boolean: 28, numeric: 5. Nullable columns: 188, columns with defaults: 1.


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

Response: The restaurant.table model represents Restaurant Table in the ERP system. It contains 17 fields and is used to manage restaurant table data. Defined in module: pos_restaurant. Key fields include: name, floor_id, shape, position_h, position_v, width, height, seats, color, active, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: The stock_valuation_layer table has 24 columns and 13 foreign key relationships. It stores data related to stock valuation layer in the system. The table has 9 indexes for performance optimization. Column types: integer: 14, numeric: 5, character varying: 2, timestamp without time zone: 3. Nullable columns: 21, columns with defaults: 1.


List all relational fields in ir.actions.act_window.view. or Show me the relational structure of ir.actions.act_window.view.

Response: The ir.actions.act_window.view model has 4 relational fields: view_id -> ir.ui.view; act_window_id -> ir.actions.act_window; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


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

Response: The res_partner_bank table has 19 columns and 6 foreign key relationships. It stores data related to res partner bank in the system. The table has 4 indexes for performance optimization. Column types: integer: 8, boolean: 1, character varying: 8, timestamp without time zone: 2. Nullable columns: 16, columns with defaults: 1.


Can you explain the purpose of report.equip3_pos_report.report_pos_payment? or What is the report.equip3_pos_report.report_pos_payment model?

Response: The report.equip3_pos_report.report_pos_payment model represents POS Payment Report in the ERP system. It contains 3 fields and is used to manage pos payment report data. Defined in module: equip3_pos_report. Key fields include: id, display_name, __last_update.


Describe the relational structure of field_conditional_access. or What are the foreign keys in field_conditional_access?

Response: Foreign keys in field_conditional_access: access_management_id -> access_management.id [constraint: field_conditional_access_access_management_id_fkey]; attrs_field_id -> ir_model_fields.id [constraint: field_conditional_access_attrs_field_id_fkey]; create_uid -> res_users.id [constraint: field_conditional_access_create_uid_fkey]; domain_field_id -> ir_model_fields.id [constraint: field_conditional_access_domain_field_id_fkey]; model_id -> ir_model.id [constraint: field_conditional_access_model_id_fkey]; write_uid -> res_users.id [constraint: field_conditional_access_write_uid_fkey]. Total foreign key relationships: 6. Referenced tables: ir_model, access_management, res_users, ir_model_fields.


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

Response: The res_company_sh_purchase_details_report_wizard_rel table has 2 columns and 2 foreign key relationships. It stores data related to res company sh purchase details report wizard rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


Can you explain the purpose of weight.scale.barcode.format? or Describe the weight.scale.barcode.format model in Odoo.

Response: The weight.scale.barcode.format model represents weight.scale.barcode.format in the ERP system. It contains 10 fields and is used to manage weight.scale.barcode.format data. Defined in module: equip3_pos_masterdata. Key fields include: name, line_ids, total_digit, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What fields does choose.delivery.carrier have? or Which fields are required in choose.delivery.carrier?

Response: The choose.delivery.carrier model has 18 fields. Field types distribution: many2one: 7, selection: 1, float: 2, many2many: 1, text: 2, integer: 1, char: 1, datetime: 3. Computed fields: 8. Field details: order_id (many2one) [required] -> sale.order [module: delivery]; partner_id (many2one) [required] [readonly] -> res.partner [compute: <bound method Field._compute_related of choose.delivery.carrier.partner_id>] [not stored] [module: delivery] [related: order_id.partner_id]; carrier_id (many2one) [required] -> delivery.carrier [module: delivery]; delivery_type (selection) [readonly] [compute: <bound method Field._compute_related of choose.delivery.carrier.delivery_type>] [not stored] [module: delivery] [related: carrier_id.delivery_type]; delivery_price (float) [module: delivery]; display_price (float) [readonly] [module: delivery]; currency_id (many2one) [readonly] -> res.currency [compute: <bound method Field._compute_related of choose.delivery.carrier.currency_id>] [not stored] [module: delivery] [related: order_id.currency_id]; company_id (many2one) [readonly] -> res.company [compute: <bound method Field._compute_related of choose.delivery.carrier.company_id>] [not stored] [module: delivery] [related: order_id.company_id]; available_carrier_ids (many2many) [readonly] -> delivery.carrier [compute: _compute_available_carrier] [not stored] [module: delivery]; invoicing_message (text) [readonly] [compute: _compute_invoicing_message] [not stored] [module: delivery]; delivery_message (text) [readonly] [module: delivery]; 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 relationships exist for stock_production_lot_warranty_claim_rel? or What are the foreign keys in stock_production_lot_warranty_claim_rel?

Response: Foreign keys in stock_production_lot_warranty_claim_rel: stock_production_lot_id -> stock_production_lot.id [constraint: stock_production_lot_warranty_clai_stock_production_lot_id_fkey]; warranty_claim_id -> warranty_claim.id [constraint: stock_production_lot_warranty_claim_rel_warranty_claim_id_fkey]. Total foreign key relationships: 2. Referenced tables: warranty_claim, stock_production_lot.


What business logic is in invoice.printout.editor? or What operations can I perform on invoice.printout.editor?

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


How to work with account.move fields? or How to create records in account.move?

Response: To use the account.move model, you need to provide values for required fields: move_type, currency_id, name, auto_reverse_date_mode, date, journal_id, state. Readonly fields: highest_name, move_type, type_name, suitable_journal_ids, company_id, currency_id, country_code, user_id, is_move_sent, payment_state, invoice_origin, preferred_payment_method_id, debit_origin_id, debit_note_count, edi_state, edi_error_count, edi_web_services_to_process, edi_show_cancel_button, edi_show_abandon_cancel_button, edi_error_message, edi_blocking_level, loan_line_id, loan_id, payment_fields_boolean, ppn, pph, tax_pay_seprately_amount, transaction_ids, authorized_transaction_ids, purchase_vendor_bill_id, purchase_id, period_id, fiscal_year, auto_reversed, partner_shipping_id, l10n_id_attachment_id, l10n_id_csv_created, l10n_id_need_kode_transaksi, landed_costs_visible, website_id, discount_amt, amount_untaxed, discount_amt_line, discount_account_id, interest, repair_ids, sh_invoice_bm_is_cont_scan, commission_count, down_payment_amount, total_down_payment_amount, report_template_id1, amount_to_text, timesheet_ids, timesheet_count, approval_matrix_id, is_invoice_approval_matrix, approval_matrix_line_id, is_approve_button, state1, state2, invoice_origin_id, invoice_origin_date, reason, ref_no, to_approve_state_payment_count, date, journal_id, company_currency_id, line_ids, commercial_partner_id, amount_tax, amount_tax2, subtotal_amount, amount_total, amount_untaxed_signed, amount_tax_signed, amount_total_signed, amount_residual_signed, amount_by_group, reversed_entry_id, fiscal_position_id, invoice_date, invoice_date_due, invoice_payment_term_id, invoice_line_ids, display_qr_code, invoice_outstanding_credits_debits_widget, invoice_has_outstanding, invoice_payments_widget, invoice_partner_display_name, invoice_cash_rounding_id, invoice_filter_type_domain, bank_partner_id, invoice_has_matching_suspense_amount, tax_lock_date_message, has_reconciled_entries, show_reset_to_draft_button, restrict_mode_hash_table, secure_sequence_number, inalterable_hash, string_to_hash, mr_show_analytic_account, journal_entries_template, analytic_tag_dynamic, reversal_avail, is_record_created, count_merged_invoice, is_button_update_invisible, partner_id, state, status_code, code, check, check_invisible, total_tax_ppn, total_inv_ppn, subtotal_inv_ppn, check_invisible_ebupot, ebupot_template, l10n_id_kode_transaksi, hide_button_upload, hide_button_upload_cn, nomor_seri_domain, current_rate, current_inverse_rate, amount_residual, tax_rate, taxes_base_price, sales_times_tax_rate, tax_applies_on, currency_revaluation_count, filter_sale_order_reference_ids, exchange_stage, exchange_date, exchange_status, purchase_order_id, amount_swo, is_services_orders, filter_sale_order_ids, filter_purchase_order_ids, filter_picking_ids, receiving_note_names, receiving_note_dates, sequence, pos_branch_id, pos_session_id, 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, access_url, access_warning, sequence_prefix, sequence_number, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: highest_name [readonly] [computed] [no_copy]; move_type [required] [readonly] [has_default]; type_name [readonly] [computed] [no_copy]; suitable_journal_ids [readonly] [computed] [no_copy]; company_id [readonly] [computed] [no_copy]; currency_id [required] [readonly] [has_default] [has_states]; country_code [readonly] [computed] [no_copy]; user_id [readonly] [computed] [no_copy]; is_move_sent [readonly] [has_default] [no_copy]; payment_state [readonly] [computed] [no_copy]; invoice_origin [readonly]; preferred_payment_method_id [readonly] [computed] [no_copy]; debit_origin_id [readonly] [no_copy]; debit_note_count [readonly] [computed] [no_copy]; edi_state [readonly] [computed] [no_copy]; edi_error_count [readonly] [computed] [no_copy]; edi_web_services_to_process [readonly] [computed] [no_copy]; edi_show_cancel_button [readonly] [computed] [no_copy]; edi_show_abandon_cancel_button [readonly] [computed] [no_copy]; edi_error_message [readonly] [computed] [no_copy]; edi_blocking_level [readonly] [computed] [no_copy]; loan_line_id [readonly]; loan_id [readonly]; payment_fields_boolean [readonly] [computed] [no_copy]; ppn [readonly]; pph [readonly]; tax_pay_seprately_amount [readonly] [computed] [no_copy]; name [required] [computed] [has_default] [no_copy]; transaction_ids [readonly] [no_copy]; authorized_transaction_ids [readonly] [computed] [no_copy]; purchase_vendor_bill_id [readonly] [has_states]; purchase_id [readonly] [has_states]; period_id [readonly] [computed] [no_copy]; fiscal_year [readonly] [computed] [no_copy]; auto_reverse_date_mode [required] [has_default] [no_copy]; auto_reversed [readonly] [no_copy]; partner_shipping_id [readonly] [has_states]; l10n_id_attachment_id [readonly] [no_copy]; l10n_id_csv_created [readonly] [computed] [no_copy]; l10n_id_need_kode_transaksi [readonly] [computed] [no_copy]; landed_costs_visible [readonly] [computed] [no_copy]; website_id [readonly] [computed] [no_copy]; discount_amt [readonly] [computed] [no_copy]; amount_untaxed [readonly] [computed] [no_copy]; discount_amt_line [readonly] [computed] [no_copy]; discount_account_id [readonly] [computed] [no_copy]; interest [readonly]; repair_ids [readonly] [no_copy]; sh_invoice_bm_is_cont_scan [readonly] [has_default]; commission_count [readonly] [computed] [no_copy]; down_payment_amount [readonly] [computed] [no_copy]; total_down_payment_amount [readonly] [computed] [no_copy]; report_template_id1 [readonly] [computed] [no_copy]; amount_to_text [readonly] [computed] [no_copy]; timesheet_ids [readonly] [no_copy]; timesheet_count [readonly] [computed] [no_copy]; approval_matrix_id [readonly] [computed] [no_copy]; is_invoice_approval_matrix [readonly] [computed] [no_copy]; approval_matrix_line_id [readonly] [computed] [no_copy]; is_approve_button [readonly] [computed] [no_copy]; state1 [readonly] [computed] [no_copy]; state2 [readonly] [computed] [no_copy]; invoice_origin_id [readonly] [has_states] [no_copy]; invoice_origin_date [readonly] [has_states] [no_copy]; reason [readonly] [has_states] [no_copy]; ref_no [readonly] [has_states] [no_copy]; to_approve_state_payment_count [readonly] [computed] [no_copy]; date [required] [readonly] [has_default] [has_states] [no_copy]; journal_id [required] [readonly] [has_default] [has_states]; company_currency_id [readonly] [computed] [no_copy]; line_ids [readonly] [has_states]; commercial_partner_id [readonly] [computed] [no_copy]; amount_tax [readonly] [computed] [no_copy]; amount_tax2 [readonly] [computed] [no_copy]; subtotal_amount [readonly] [computed] [no_copy]; amount_total [readonly] [computed] [no_copy]; amount_untaxed_signed [readonly] [computed] [no_copy]; amount_tax_signed [readonly] [computed] [no_copy]; amount_total_signed [readonly] [computed] [no_copy]; amount_residual_signed [readonly] [computed] [no_copy]; amount_by_group [readonly] [computed] [no_copy]; reversed_entry_id [readonly] [no_copy]; fiscal_position_id [readonly] [has_states]; invoice_date [readonly] [has_states] [no_copy]; invoice_date_due [readonly] [has_states] [no_copy]; invoice_payment_term_id [readonly] [has_states]; invoice_line_ids [readonly] [has_states] [no_copy]; display_qr_code [readonly] [computed] [no_copy]; invoice_outstanding_credits_debits_widget [readonly] [computed] [no_copy]; invoice_has_outstanding [readonly] [computed] [no_copy]; invoice_payments_widget [readonly] [computed] [no_copy]; invoice_partner_display_name [readonly] [computed] [no_copy]; invoice_cash_rounding_id [readonly] [has_states]; invoice_filter_type_domain [readonly] [computed] [no_copy]; bank_partner_id [readonly] [computed] [no_copy]; invoice_has_matching_suspense_amount [readonly] [computed] [no_copy]; tax_lock_date_message [readonly] [computed] [no_copy]; has_reconciled_entries [readonly] [computed] [no_copy]; show_reset_to_draft_button [readonly] [computed] [no_copy]; restrict_mode_hash_table [readonly] [computed] [no_copy]; secure_sequence_number [readonly] [no_copy]; inalterable_hash [readonly] [no_copy]; string_to_hash [readonly] [computed] [no_copy]; mr_show_analytic_account [readonly] [computed] [no_copy]; journal_entries_template [readonly] [has_states] [no_copy]; analytic_tag_dynamic [readonly] [computed] [no_copy]; reversal_avail [readonly] [computed] [has_default] [no_copy]; is_record_created [readonly] [computed] [has_default] [no_copy]; count_merged_invoice [readonly] [computed] [no_copy]; is_button_update_invisible [readonly] [computed] [no_copy]; partner_id [readonly] [has_states]; state [required] [readonly] [has_default] [no_copy]; status_code [readonly] [computed] [no_copy]; code [readonly] [computed] [no_copy]; check [readonly] [computed] [no_copy]; check_invisible [readonly] [computed] [no_copy]; total_tax_ppn [readonly] [computed] [no_copy]; total_inv_ppn [readonly] [computed] [no_copy]; subtotal_inv_ppn [readonly] [computed] [no_copy]; check_invisible_ebupot [readonly] [computed] [no_copy]; ebupot_template [readonly] [computed] [no_copy]; l10n_id_kode_transaksi [readonly] [has_states] [no_copy]; hide_button_upload [readonly] [computed] [no_copy]; hide_button_upload_cn [readonly] [computed] [no_copy]; nomor_seri_domain [readonly] [computed] [no_copy]; current_rate [readonly] [has_default]; current_inverse_rate [readonly] [has_default]; amount_residual [readonly] [computed] [no_copy]; tax_rate [readonly]; taxes_base_price [readonly] [computed] [no_copy]; sales_times_tax_rate [readonly] [computed] [no_copy]; tax_applies_on [readonly] [computed] [no_copy]; currency_revaluation_count [readonly] [computed] [has_default] [no_copy]; filter_sale_order_reference_ids [readonly] [computed] [no_copy]; exchange_stage [readonly] [computed] [no_copy]; exchange_date [readonly] [computed] [no_copy]; exchange_status [readonly] [computed] [no_copy]; purchase_order_id [readonly] [computed] [no_copy]; amount_swo [readonly] [computed] [no_copy]; is_services_orders [readonly] [computed] [no_copy]; filter_sale_order_ids [readonly] [computed] [no_copy]; filter_purchase_order_ids [readonly] [computed] [no_copy]; filter_picking_ids [readonly] [computed] [no_copy]; receiving_note_names [readonly] [computed] [no_copy]; receiving_note_dates [readonly] [computed] [no_copy]; sequence [readonly] [computed] [no_copy]; pos_branch_id [readonly] [has_default]; pos_session_id [readonly]; 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]; access_url [readonly] [computed] [no_copy]; access_warning [readonly] [computed] [no_copy]; sequence_prefix [readonly] [computed] [no_copy]; sequence_number [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.


How does pos.loyalty.category relate to other models? or Show me the relational structure of pos.loyalty.category.

Response: The pos.loyalty.category model has 3 relational fields: company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.