What data can be stored in link.tracker? or Which fields are required in link.tracker?

Response: The link.tracker model has 22 fields. Field types distribution: char: 9, one2many: 2, integer: 2, many2one: 6, datetime: 3. Computed fields: 8. Field details: url (char) [required] [module: link_tracker]; absolute_url (char) [readonly] [compute: _compute_absolute_url] [not stored] [module: link_tracker]; short_url (char) [readonly] [compute: _compute_short_url] [not stored] [module: link_tracker]; redirected_url (char) [readonly] [compute: _compute_redirected_url] [not stored] [module: link_tracker]; short_url_host (char) [readonly] [compute: _compute_short_url_host] [not stored] [module: link_tracker]; title (char) [module: link_tracker]; label (char) [module: link_tracker]; link_code_ids (one2many) -> link.tracker.code [module: link_tracker]; code (char) [readonly] [compute: _compute_code] [not stored] [module: link_tracker]; link_click_ids (one2many) -> link.tracker.click [module: link_tracker]; count (integer) [readonly] [compute: _compute_count] [stored] [module: link_tracker]; mass_mailing_id (many2one) -> mailing.mailing [module: mass_mailing]; campaign_id (many2one) -> utm.campaign [module: utm]; source_id (many2one) -> utm.source [module: utm]; medium_id (many2one) -> utm.medium [module: utm]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


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

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


Show me the fields of report.equip3_kitchen_operations.report_cooking_list. or What are the available fields for report.equip3_kitchen_operations.report_cooking_list?

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


What field types are used in report.accounting_pdf_reports.report_tax? or List all fields in the report.accounting_pdf_reports.report_tax model.

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


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

Response: Foreign keys in purchase_order_history: create_uid -> res_users.id [constraint: purchase_order_history_create_uid_fkey]; name -> purchase_order_line.id [constraint: purchase_order_history_name_fkey]; order_id -> purchase_order.id [constraint: purchase_order_history_order_id_fkey]; write_uid -> res_users.id [constraint: purchase_order_history_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: purchase_order_line, res_users, purchase_order.


How is purchase.price.history used in the system? or Describe the purchase.price.history model in Odoo.

Response: The purchase.price.history model represents Purchase Price History in the ERP system. It contains 16 fields and is used to manage purchase price history data. Defined in module: sh_all_in_one_purchase_tools. Key fields include: name, partner_id, variant_id, purchase_order_id, order_date, quantity, purchase_price, currency_id, total_price, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: Columns in mr_line_internal_transfer_line: id (integer) [NOT NULL] [DEFAULT: nextval('mr_line_internal_transfer_line_id_seq'::regclass)] [PRECISION: 32]; mr_id (integer) [PRECISION: 32] [COMMENT: Reference]; mr_line_id (integer) [PRECISION: 32] [COMMENT: Mr Line]; no (integer) [PRECISION: 32] [COMMENT: No]; product_id (integer) [PRECISION: 32] [COMMENT: Product]; description (character varying) [COMMENT: Description]; uom_id (integer) [PRECISION: 32] [COMMENT: Unit of Measure]; source_location (integer) [PRECISION: 32] [COMMENT: Source Location]; source_warehouse_id (integer) [PRECISION: 32] [COMMENT: Source Warehouse]; current_qty (double precision) [PRECISION: 53] [COMMENT: Available Quantity]; virtual_available (double precision) [PRECISION: 53] [COMMENT: Forecasted Quantity]; qty_transfer (double precision) [NOT NULL] [PRECISION: 53] [COMMENT: Quantity To Transfer]; mr_ir_wizard (integer) [PRECISION: 32] [COMMENT: Mr Ir Wizard]; 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: 17. Statistics: 15 nullable, 1 with defaults, 0 with length constraints.


Which fields are required in show.material.done.popup? or Describe the field structure of show.material.done.popup.

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


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

Response: Foreign keys in restaurant_table: create_uid -> res_users.id [constraint: restaurant_table_create_uid_fkey]; floor_id -> restaurant_floor.id [constraint: restaurant_table_floor_id_fkey]; write_uid -> res_users.id [constraint: restaurant_table_write_uid_fkey]. Total foreign key relationships: 3. Referenced tables: res_users, restaurant_floor.


What business logic is in resource.test? or What are common use cases for resource.test?

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


Show me the relational structure of pos.bus.log. or What one2many fields are in pos.bus.log?

Response: The pos.bus.log model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


What are the available fields for account.cashbox.wizard? or What computed fields exist in account.cashbox.wizard?

Response: The account.cashbox.wizard model has 14 fields. Field types distribution: many2one: 3, one2many: 2, float: 1, boolean: 3, integer: 1, char: 1, datetime: 3. Computed fields: 3. Field details: pos_session_id (many2one) -> pos.session [module: equip3_pos_cashbox]; line_ids (one2many) -> account.cashbox.wizard.line [module: equip3_pos_cashbox]; amount_total (float) [readonly] [compute: _compute_amount_total] [not stored] [module: equip3_pos_cashbox]; is_closing_wizard (boolean) [module: equip3_pos_cashbox]; is_validate (boolean) [module: equip3_pos_cashbox]; is_return (boolean) [module: equip3_pos_cashbox]; line_bank_ids (one2many) -> account.cashbox.wizard.bank.line [module: allfresh_mod_pos]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


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

Response: The account.voucher model is defined in module: aos_account_voucher. It has 35 computed fields: doc_count, currency_id, amount, tax_amount, paid, untax_amount, approval_matrix_id, is_other_income_approval_matrix, approval_matrix_line_id, is_approve_button, state1, state2, is_voucher_fund_custodian, 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: currency_id, amount, tax_amount, untax_amount. Related fields: state1 -> state, state2 -> state, 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: _default_journal, _default_payment_journal, _compute_voucher_docs_count, _get_report_base_filename, _get_move_display_name, _convert_num2words, print_payment_voucher, attachment_voucher_view, _check_paid, _get_currency, _get_company, _check_company_id, name_get, _get_journal_currency, _compute_total, onchange_date, onchange_partner_id, proforma_voucher, action_cancel_draft, cancel_voucher, unlink, first_move_line_get, account_move_get, _convert, _prepare_voucher_move_line, voucher_move_line_create, action_move_line_create.


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

Response: Foreign keys in product_pricelist_item: base_pricelist_id -> product_pricelist.id [constraint: product_pricelist_item_base_pricelist_id_fkey]; categ_id -> product_category.id [constraint: product_pricelist_item_categ_id_fkey]; company_id -> res_company.id [constraint: product_pricelist_item_company_id_fkey]; create_uid -> res_users.id [constraint: product_pricelist_item_create_uid_fkey]; currency_id -> res_currency.id [constraint: product_pricelist_item_currency_id_fkey]; pos_category_id -> pos_category.id [constraint: product_pricelist_item_pos_category_id_fkey]; pricelist_id -> product_pricelist.id [constraint: product_pricelist_item_pricelist_id_fkey]; pricelist_uom_id -> uom_uom.id [constraint: product_pricelist_item_pricelist_uom_id_fkey]; product_id -> product_product.id [constraint: product_pricelist_item_product_id_fkey]; product_tmpl_id -> product_template.id [constraint: product_pricelist_item_product_tmpl_id_fkey]; uom_id -> uom_uom.id [constraint: product_pricelist_item_uom_id_fkey]; write_uid -> res_users.id [constraint: product_pricelist_item_write_uid_fkey]. Total foreign key relationships: 12. Referenced tables: product_product, product_category, uom_uom, res_company, product_pricelist, product_template, res_currency, res_users, pos_category.


What are the available fields for product.pricelist.history? or Which fields are required in product.pricelist.history?

Response: The product.pricelist.history model has 25 fields. Field types distribution: many2one: 11, datetime: 4, char: 7, integer: 2, boolean: 1. Computed fields: 3. Field details: pricelist_id (many2one) -> product.pricelist [module: equip3_sale_masterdata]; logdate (datetime) [module: equip3_sale_masterdata]; user_id (many2one) -> res.users [module: equip3_sale_masterdata]; name (char) [module: equip3_sale_masterdata]; method (char) [module: equip3_sale_masterdata]; description (char) [module: equip3_sale_masterdata]; old_value_text (char) [module: equip3_sale_masterdata]; new_value_text (char) [module: equip3_sale_masterdata]; category_id (many2one) -> product.category [module: equip3_sale_masterdata]; product_tmpl_id (many2one) -> product.template [module: equip3_sale_masterdata]; product_id (many2one) -> product.product [module: equip3_sale_masterdata]; uom_id (many2one) -> uom.uom [module: equip3_sale_masterdata]; model (char) [module: equip3_sale_masterdata]; pl_id (integer) [module: equip3_sale_masterdata]; pricelist_item_id (many2one) -> product.pricelist.item [module: allfresh_mod_pricelist]; company_id (many2one) -> res.company [module: allfresh_mod_pricelist]; currency_id (many2one) [readonly] -> res.currency [compute: <bound method Field._compute_related of product.pricelist.history.currency_id>] [not stored] [module: allfresh_mod_pricelist] [related: company_id.currency_id]; is_seen (boolean) [module: allfresh_mod_pricelist]; 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].


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

Response: The setu_inventory_age_bi_report table has 17 columns and 6 foreign key relationships. It stores data related to setu inventory age bi report in the system. The table has 1 indexes for performance optimization. Column types: integer: 8, double precision: 6, date: 1, timestamp without time zone: 2. Nullable columns: 16, columns with defaults: 1.


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

Response: Foreign keys in meetings_salespersons: calendar_event_id -> calendar_event.id [constraint: meetings_salespersons_calendar_event_id_fkey]; create_uid -> res_users.id [constraint: meetings_salespersons_create_uid_fkey]; salesperson_id -> res_users.id [constraint: meetings_salespersons_salesperson_id_fkey]; write_uid -> res_users.id [constraint: meetings_salespersons_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: calendar_event, res_users.


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

Response: Foreign keys in group_card_pos_payment_method_mdr_rel: pos_payment_method_mdr_id -> pos_payment_method_mdr.id [constraint: group_card_pos_payment_method_md_pos_payment_method_mdr_id_fkey]; group_card_id -> group_card.id [constraint: group_card_pos_payment_method_mdr_rel_group_card_id_fkey]. Total foreign key relationships: 2. Referenced tables: pos_payment_method_mdr, group_card.


Describe the many2many relations for membership.membership_line. or Show me the relational structure of membership.membership_line.

Response: The membership.membership_line model has 7 relational fields: partner -> res.partner; membership_id -> product.product; account_invoice_line -> account.move.line; account_invoice_id -> account.move; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


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

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


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

Response: Columns in stock_inventory: id (integer) [NOT NULL] [DEFAULT: nextval('stock_inventory_id_seq'::regclass)] [PRECISION: 32]; message_main_attachment_id (integer) [PRECISION: 32] [COMMENT: Main Attachment]; name (character varying) [NOT NULL] [COMMENT: Inventory Reference]; date (timestamp without time zone) [NOT NULL] [COMMENT: Inventory Date]; state (character varying) [COMMENT: Status]; company_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Company]; start_empty (boolean) [COMMENT: Empty Inventory]; prefill_counted_quantity (character varying) [COMMENT: Counted Quantities]; exhausted (boolean) [COMMENT: Include Exhausted Products]; 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]; accounting_date (date) [COMMENT: Accounting Date]; branch_id (integer) [PRECISION: 32] [COMMENT: Branch]; sh_inventory_adjt_barcode_mobile (character varying) [COMMENT: Mobile Barcode]; sh_inventory_adjt_bm_is_cont_scan (character varying) [COMMENT: Continuously Scan?]; force_date (timestamp without time zone) [COMMENT: Force Date]; warehouse_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Warehouse]; user_id (integer) [PRECISION: 32] [COMMENT: Responsible]; inventoried_product (character varying) [COMMENT: Inventoried Product]; is_adj_value (boolean) [COMMENT: Input Unit Price]; adjustment_account_id (integer) [PRECISION: 32] [COMMENT: Adjustment Account]; inv_ref (character varying) [COMMENT: Inv Ref]; description (text) [COMMENT: Description]; user_id_1 (integer) [PRECISION: 32] [COMMENT: User 1]; user_id_2 (integer) [PRECISION: 32] [COMMENT: User 2]; wizard_id (integer) [PRECISION: 32] [COMMENT: Wizard]; is_user_id_1_adjusment (boolean) [COMMENT: Is User Id 1 Adjusment]; is_user_id_2_adjusment (boolean) [COMMENT: Is User Id 2 Adjusment]; is_user_id_1 (boolean) [COMMENT: Is User Id 1]; is_user_id_2 (boolean) [COMMENT: Is User Id 2]; pos_branch_id (integer) [PRECISION: 32] [COMMENT: Branch]; fifo_avco_adjustment_data (character varying) [COMMENT: Fifo Avco Adjustment Data]. Total columns: 34. Statistics: 29 nullable, 1 with defaults, 0 with length constraints.


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

Response: Columns in pos_profit_loss_wizard: id (integer) [NOT NULL] [DEFAULT: nextval('pos_profit_loss_wizard_id_seq'::regclass)] [PRECISION: 32]; start_dt (date) [NOT NULL] [COMMENT: Start Date]; end_dt (date) [NOT NULL] [COMMENT: End Date]; pos_branch_id (integer) [PRECISION: 32] [COMMENT: Branch]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 8. Statistics: 5 nullable, 1 with defaults, 0 with length constraints.


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

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


What is the resource.mixin model? or Describe the resource.mixin model in Odoo.

Response: The resource.mixin model represents Resource Mixin in the ERP system. It contains 7 fields and is used to manage resource mixin data. Defined in module: resource. Key fields include: resource_id, company_id, resource_calendar_id, tz, id, display_name, __last_update.


Which fields are stored computed fields in account.cash.flow.statement? or What methods are available in account.cash.flow.statement?

Response: The account.cash.flow.statement model is defined in module: equip3_accounting_reports. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: view_report, sum_tmp_account, _check_list, _sum_list, _sum_list_minus, get_filter, get_filter_data, _query_1, _query_1_receipt, _query_1_payment, _query_2_receipt, _query_2_paid, _query_3, _query_4, _query_8, _query_9, _query_addition, _query_deduction, _query_10, _query_net_income, _query_unclass, _query_all, _query_7, _get_report_values, _get_lines, get_journal_lines, create, write, _get_currency, _get_dates_previous_year, _get_dates_previous_period, _init_filter_date, _get_dates_period, get_dynamic_xlsx_report, _domain_branch.


What are the column types in product_template_attribute_value_sale_order_line_rel? or List all columns in product_template_attribute_value_sale_order_line_rel.

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


What does the warranty.settings model represent? or Can you explain the purpose of warranty.settings?

Response: The warranty.settings model represents Warranty Settings in the ERP system. It contains 854 fields and is used to manage warranty settings data. Defined in module: bi_warranty_registration. Key fields include: renew_notif, setting_desc, warranty_tmpl, renew_tmpl, company_id, create_warranty_from_saleorder, user_default_rights, external_email_server_default, module_base_import, module_google_calendar, module_microsoft_calendar, module_google_drive, module_google_spreadsheet, module_auth_oauth, module_auth_ldap, module_base_gengo, module_account_inter_company_rules, module_pad, module_voip, module_web_unsplash, module_partner_autocomplete, module_base_geolocalize, module_google_recaptcha, report_footer, group_multi_currency, paperformat_id, external_report_layout_id, show_effect, company_count, active_user_count, language_count, company_name, company_informations, app_default_superbar_lazy_search, geoloc_provider_id, geoloc_provider_techname, geoloc_provider_googlemap_key, recaptcha_public_key, recaptcha_private_key, recaptcha_min_score, fail_counter, alias_domain, unsplash_access_key, app_system_name, app_show_lang, app_show_debug, app_show_documentation, app_show_documentation_dev, app_show_support, app_show_account, app_show_enterprise, app_show_share, app_show_poweredby, group_show_author_in_apps, module_odoo_referral, app_documentation_url, app_documentation_dev_url, app_support_url, app_account_title, app_account_url, app_enterprise_url, app_ribbon_name, auth_signup_reset_password, auth_signup_template_user_id, resource_calendar_id, module_hr_presence, module_hr_skills, hr_presence_control_login, hr_presence_control_email, hr_presence_control_ip, module_hr_attendance, hr_presence_control_email_amount, hr_presence_control_ip_list, hr_employee_self_edit, kpi_company_id, kpi_history_tolerance, show_kpi_help, group_discount_per_so_line, group_uom, group_product_variant, module_sale_product_configurator, module_sale_product_matrix, group_stock_packaging, group_product_pricelist, group_sale_pricelist, product_pricelist_setting, product_weight_in_lbs, product_volume_volume_in_cubic_feet, enable_menu_search, enable_web_push_notification, api_key, vapid, config_details, sh_multi_barcode_unique, is_sh_product_qrcode_generator_when_create, snailmail_color, snailmail_cover, snailmail_duplex, digest_emails, digest_id, sh_product_stock, sh_product_attribute, sh_product_image, sh_product_category, sh_product_code, sh_product_barcode, sh_product_sale_price, sh_product_sale_description, sh_touch_kyboard, sh_welcome_message, sh_message, sh_company_logo, sh_display, sh_display_view, sh_display_landscape, sh_display_portrait, sh_delay_screen, has_accounting_entries, currency_id, has_chart_of_accounts, chart_template_id, purchase_tax_id, tax_calculation_rounding_method, module_account_accountant, group_analytic_accounting, group_warning_account, group_cash_rounding, group_show_line_subtotals_tax_excluded, group_show_line_subtotals_tax_included, group_show_sale_receipts, group_show_purchase_receipts, show_line_subtotals_tax_selection, module_account_budget, module_account_payment, module_account_reports, module_account_check_printing, module_account_batch_payment, module_account_sepa, module_account_sepa_direct_debit, module_account_plaid, module_account_yodlee, module_account_bank_statement_import_qif, module_account_bank_statement_import_ofx, module_account_bank_statement_import_csv, module_account_bank_statement_import_camt, module_currency_rate_live, module_account_intrastat, module_product_margin, module_l10n_eu_service, module_account_taxcloud, module_account_invoice_extract, module_snailmail_account, tax_exigibility, tax_cash_basis_journal_id, account_cash_basis_base_account_id, qr_code, invoice_is_print, invoice_is_email, incoterm_id, invoice_terms, use_invoice_terms, country_code, crm_alias_prefix, generate_lead_from_alias, group_use_lead, group_use_recurring_revenues, module_crm_iap_lead, module_crm_iap_lead_website, module_crm_iap_lead_enrich, module_mail_client_extension, lead_enrich_auto, lead_mining_in_pipeline, predictive_lead_scoring_start_date, predictive_lead_scoring_start_date_str, predictive_lead_scoring_fields, predictive_lead_scoring_fields_str, group_mass_mailing_campaign, mass_mailing_outgoing_mail_server, mass_mailing_mail_server_id, show_blacklist_buttons, module_project_forecast, module_hr_timesheet, group_subtask_project, group_project_rating, group_project_recurring_tasks, module_product_expiry, group_stock_production_lot, group_lot_on_delivery_slip, group_stock_tracking_lot, group_stock_tracking_owner, group_stock_adv_location, group_warning_stock, group_stock_sign_delivery, module_stock_picking_batch, module_stock_barcode, stock_move_email_validation, stock_mail_confirmation_template_id, module_stock_sms, group_stock_multi_locations, website_id, website_name, website_domain, website_country_group_ids, website_company_id, website_logo, language_ids, website_language_count, website_default_lang_id, website_default_lang_code, specific_user_account, website_cookies_bar, google_analytics_key, google_management_client_id, google_management_client_secret, google_search_console, cdn_activated, cdn_url, cdn_filters, social_twitter, social_facebook, social_github, social_linkedin, social_youtube, social_instagram, has_social_network, favicon, social_default_image, google_maps_api_key, group_multi_website, has_google_analytics, has_google_analytics_dashboard, has_google_maps, has_google_search_console, has_default_share_image, account_check_printing_layout, account_check_printing_date_label, account_check_printing_multi_stub, account_check_printing_margin_top, account_check_printing_margin_left, account_check_printing_margin_right, vat_check_vies, group_show_form_view, picking_operation_type, sh_it_barcode_mobile_type, sh_it_bm_is_cont_scan, sh_it_bm_is_notify_on_success, sh_it_bm_is_notify_on_fail, sh_it_bm_is_sound_on_success, sh_it_bm_is_sound_on_fail, sh_it_bm_is_add_product, module_project_timesheet_synchro, module_project_timesheet_holidays, project_time_mode_id, timesheet_encode_uom_id, timesheet_min_duration, timesheet_rounding, is_encode_uom_days, manufacturing_lead, use_manufacturing_lead, group_mrp_byproducts, module_mrp_mps, module_mrp_plm, module_mrp_workorder, module_quality_control, module_mrp_subcontracting, group_mrp_routings, group_locked_by_default, group_expiry_date_on_delivery_slip, lock_confirmed_po, po_lock, po_order_approval, po_double_validation, po_double_validation_amount, company_currency_id, default_purchase_method, group_warning_purchase, module_account_3way_match, module_purchase_requisition, module_purchase_product_matrix, po_lead, use_po_lead, group_send_reminder, module_sg_bank_reconcile, module_sg_dbs_giro, sh_invoice_online_signature, sh_enable_approval, sh_restrict_for_close_period, invoice_is_snailmail, module_stock_landed_costs, stock_qty_forecast_method, stock_qty_forecast_interval, stock_qty_predicted_periods, stock_move_sms_validation, stock_sms_confirmation_template_id, channel_id, group_enable_discuss, group_disable_poll, app_stop_subscribe, inv_cost, is_cost_price_per_warehouse, fiscalyear_last_day, fiscalyear_last_month, period_lock_date, fiscalyear_lock_date, group_fiscal_year, sale_tax_id, module_pos_mercury, module_pos_adyen, module_pos_six, update_stock_quantities, module_stock_dropshipping, days_to_purchase, is_installed_sale, group_auto_done_setting, module_sale_margin, quotation_validity_days, use_quotation_validity_days, group_warning_sale, portal_confirmation_sign, portal_confirmation_pay, group_sale_delivery_address, group_proforma_sales, default_invoice_policy, deposit_default_product_id, auth_signup_uninvited, module_delivery, module_delivery_dhl, module_delivery_fedex, module_delivery_ups, module_delivery_usps, module_delivery_bpost, module_delivery_easypost, module_product_email_template, module_sale_coupon, module_sale_amazon, automatic_invoice, template_id, confirmation_template_id, sh_group_enable_report_section, group_enable_merge_purchase_order, po_operation_type, cancel_receipt, cancel_bill, group_enable_purchase_checklist, group_enable_purchase_custom_product_template, purchase_show_signature, chk_sign_confirm, purchase_enable_other_sign_option, sh_expiry_notification, sh_is_notify_vendor, sh_on_date_notify, enter_before_first_notify, enter_before_second_notify, enter_before_third_notify, enter_after_first_notify, enter_after_second_notify, enter_after_third_notify, attachment_email, group_enable_purchase_multi_product_adv, sh_purchase_configuration_limit, group_enable_purchase_order_history, item_limit_purchase, record_based_on_purchase, group_enable_purchase_price_history, purchase_order_information_in_message, purchase_product_detail_in_message, purchase_signature, purchase_display_in_message, po_send_pdf_in_message, sh_auto_add_followers, sh_portal_user_create, sh_tender_document_manage, sh_purchase_revision, is_enable_vendor_notification, user_ids, is_enable_auto_portal_user, is_enable_company_portal_user, is_enable_company_contact_portal_user, crm_default_team_id, crm_default_user_id, l10n_id_tax_address, l10n_id_tax_name, reminder_frequency, group_sale_order_template, company_so_template_id, module_sale_quotation_builder, security_lead, group_display_incoterm, group_lot_on_invoice, use_security_lead, default_picking_policy, sh_manage_tender_doc_portal, lc_journal_id, salesperson_id, salesteam_id, module_website_sale_delivery, sale_delivery_settings, group_delivery_invoice_address, module_website_sale_digital, module_website_sale_wishlist, module_website_sale_comparison, module_website_sale_stock, module_account, cart_recovery_mail_template, cart_abandoned_delay, mailsend_check, email_notification_days, res_user_ids, validate_picking, create_invoice, validate_invoice, allow_auto_intercompany, ks_forecast_method, use_sale_order_note, sale_order_note, keep_name_so, sh_sale_barcode_mobile_type, sh_sale_bm_is_cont_scan, sh_sale_bm_is_notify_on_success, sh_sale_bm_is_notify_on_fail, sh_sale_bm_is_sound_on_success, sh_sale_bm_is_sound_on_fail, sh_purchase_barcode_mobile_type, sh_purchase_bm_is_cont_scan, sh_purchase_bm_is_notify_on_success, sh_purchase_bm_is_notify_on_fail, sh_purchase_bm_is_sound_on_success, sh_purchase_bm_is_sound_on_fail, sh_invoice_barcode_mobile_type, sh_invoice_bm_is_cont_scan, sh_invoice_bm_is_notify_on_success, sh_invoice_bm_is_notify_on_fail, sh_invoice_bm_is_sound_on_success, sh_invoice_bm_is_sound_on_fail, sh_bom_barcode_mobile_type, sh_bom_bm_is_cont_scan, sh_bom_bm_is_notify_on_success, sh_bom_bm_is_notify_on_fail, sh_bom_bm_is_sound_on_success, sh_bom_bm_is_sound_on_fail, sh_stock_barcode_mobile_type, sh_stock_bm_is_cont_scan, sh_stock_bm_is_notify_on_success, sh_stock_bm_is_notify_on_fail, sh_stock_bm_is_sound_on_success, sh_stock_bm_is_sound_on_fail, sh_stock_bm_is_add_product, sh_inventory_adjt_barcode_mobile_type, sh_inventory_adjt_bm_is_cont_scan, sh_inventory_adjt_bm_is_notify_on_success, sh_inventory_adjt_bm_is_notify_on_fail, sh_inventory_adjt_bm_is_sound_on_success, sh_inventory_adjt_bm_is_sound_on_fail, sh_product_barcode_mobile_type, sh_product_bm_is_cont_scan, sh_product_bm_is_notify_on_success, sh_product_bm_is_notify_on_fail, sh_product_bm_is_sound_on_success, sh_product_bm_is_sound_on_fail, sh_product_bm_is_default_code, sh_product_bm_is_lst_price, sh_product_bm_is_qty_available, sh_product_bm_is_virtual_available, sh_global_document_search_is_enable, sh_global_document_search_is_sale, sh_global_document_search_is_purchase, sh_global_document_search_is_picking, sh_global_document_search_is_invoice, sh_global_document_search_is_product, sh_global_document_search_is_lot, sh_global_document_search_is_location, sh_global_document_search_action_target_type, sale_credit_limit_email_alerts, sale_email_specific_user_id, quot_to_po, so_to_po, inventory_availability, available_threshold, website_warehouse_id, down_payment_product_id, implementor_setting, general, purchase, sales, inventory, manufacturing, central_kitchen, human_resource, pos, simple_manufacturing, assembly, cutting, mining, agriculture, show_branch, past_x_days_sales, currency_exchange_journal_id, income_currency_exchange_account_id, expense_currency_exchange_account_id, unrealized_exchange_journal_id, income_unrealized_exchange_account_id, expense_unrealized_exchange_account_id, is_inverse_rate, is_taxes_rate, tax_discount_policy, sale_account_id, purchase_account_id, interest_income, interest_expense, deposit_reconcile_journal_id, journal_id, deposit_account_id, petty_cash_expense_account_id, overdue_template, tax_rounding_type, accounting, is_credit_note_approval_matrix, is_refund_approval_matrix, is_customer_deposit_approval_matrix, is_vendor_deposit_approval_matrix, is_receipt_giro_approval_matrix, is_payment_giro_approval_matrix, is_purchase_currency_approval_matrix, is_budget_approval_matrix, is_budget_change_req_approval_matrix, is_purchase_budget_approval_matrix, is_purchase_budget_change_req_approval_matrix, is_internal_transaction, is_analytic_groups_balance_sheet, is_assets_approving_matrix, is_cash_advance_approving_matrix, is_invoice_approval_matrix, is_bill_approval_matrix, is_other_income_approval_matrix, is_other_expense_approval_matrix, is_customer_multi_receipt_approval_matrix, is_vendor_multipayment_approval_matrix, is_receipt_approval_matrix, is_payment_approval_matrix, is_payment_voucher_approval_matrix, group_is_credit_note_approval_matrix, group_is_refund_approval_matrix, group_is_customer_deposit_approval_matrix, group_is_vendor_deposit_approval_matrix, group_is_receipt_giro_approval_matrix, group_is_payment_giro_approval_matrix, group_is_internal_transfer_approval_matrix, group_is_purchase_currency_approval_matrix, group_is_budget_approval_matrix, group_is_budget_change_req_approval_matrix, group_is_purchase_budget_approval_matrix, group_is_purchase_budget_change_req_approval_matrix, group_account_asset_category_fiscal, group_assets_approving_matrix, group_cash_advance_approval_matrix, group_is_invoice_approval_matrix, group_is_bill_approval_matrix, group_is_other_income_approval_matrix, group_is_other_expense_approval_matrix, group_is_customer_multi_receipt_approval_matrix, group_is_vendor_multipayment_approval_matrix, group_is_receipt_approval_matrix, group_is_payment_approval_matrix, group_is_payment_voucher_approval_matrix, module_om_account_budget, Use_received_date, customer_availability, automated_invoice_followup, followup_sending_date, reminder_interval_before, reminder_interval_before_unit, reminder_notification_before, reminder_interval_after, reminder_interval_after_unit, reminder_notification_after, invoice_bill_reminder, reminder_interval_before_invoice, reminder_interval_after_invoice, reminder_interval_before_unit_invoice, eminder_interval_after_unit_invoice, reminder_notification_before_invoice, reminder_notification_after_invoice, days_bill_before, days_bill_after, days_invoice_before, days_invoice_after, sending_date_bill_before, sending_date_bill_after, sending_date_invoice_before, sending_date_invoice_after, date_last_reminder_due_date, date_last_reminder_after_due_date, date_last_reminder_bill_due_date, date_last_reminder_bill_after_due_date, date_last_reminder_bill_before_due_date, is_invoice_cutoff_date, invoice_cutoff_date, post_discount_account, prefix_limit, is_material_request_approval_matrix, is_internal_transfer_approval_matrix, is_stock_count_approval, is_product_usage_approval, is_return_orders, return_type, is_inventory_adjustment_with_value, putaway_max_capacity, set_warehouse_sublevel, warehouse_sublevel_zone, warehouse_sublevel_shelf, warehouse_sublevel_rack, warehouse_sublevel_bin, group_is_three_dimension_warehouse, is_mbs_on_transfer_operations, is_mbs_on_product_usage, is_mbs_on_stock_count_and_inventory_adjustment, outgoing_routing_strategy, sort_quants_by, routing_order, is_receiving_notes_approval_matrix, is_adj_picking, is_delivery_order_approval_matrix, brand_setting, is_manufacturing_plan, allow_submit_purchase_request, allow_submit_material_request, mo_force_done, manufacturing_plan_conf, manufacturing_order_conf, mrp_plan_partial_availability, mp_auto_reserve_availability_materials, mo_auto_reserve_availability_materials, production_record_conf, mrp_production_partial_availability, mrp_submit_purchase_request, mrp_submit_material_request, mrp_force_done, manufacturing_mps, manufacturing_period, manufacturing_period_to_display, autogenerated_based_methods, send_wa_approval_notification_mrp, send_wa_approval_notification_mp, send_wa_approval_notification_mpr, is_vendor_approval_matrix, is_purchase_order_approval_matrix, is_purchase_request_approval_matrix, is_vendor_pricelist_approval_matrix, is_purchase_tender_approval_matrix, purchase_approval_matrix, is_blanket_order_approval_matrix, is_good_services_order, is_purchase_tender, is_blanket_order, is_direct_purchase_approval_matrix, is_pr_department, is_price_ratting_rfq_tender, retail, module_equip3_purchase_rental, is_product_brand_filter, is_product_vendor_pricelist_filter, is_service_work_order, is_purchase_request_assign_user, group_create_purchase_request_direct, is_customer_approval_matrix, is_customer_limit_matrix, is_over_limit_validation, is_bo_approval_matrix, show_sale_barcode_mobile_type, sh_sale_barcode_mobile_type_new, group_om_account_budget, credit_note_expiry_date, bom_tools, sale_order_multiple_pricelist, automatic_confirm_saleorder, automatic_invoice_create, is_delivery_acknowledgement, is_broadcast_order, module_pragmatic_portal_user, module_pragmatic_delivery_acknowledgement, module_pragmatic_website_cash_on_delivery, commission_pay_on, commission_calc, commission_pay_by, is_message_rn, send_notification_users_ids, bank_integrate_url, bank_integrate_username, bank_integrate_password, validate_api, accounting_budget_use_theoretical_achievement, is_pajak_express_integration, pajak_express_url, pajak_express_transaction_url, pajak_express_username, pajak_express_password, validate_api_first, validate_api_express, validate_api_express_fail, group_is_pajak_express_integration, is_call_bi_api, is_call_kemenkeu_api, token_kemenkeu_api, internal_type, ex_period, material_request, is_product_service_operation, is_product_service_operation_delivery, mr_expiry_days, itr_expiry_days, is_return_limit_policy, return_policy_days, is_display_warehouse_address, module_procurement_jit, is_warehouse_shipments, qty_can_minus, is_vendor_approval_email, is_vendor_approval_whatsapp, is_vendor_pricelist_approval_email, is_vendor_pricelist_approval_whatsapp, sale_matrix_config, is_total_amount, total_sequence, total_sequence_select, is_margin_amount, margin_sequence, margin_sequence_select, is_discount_amount, discount_sequence, discount_sequence_select, expired_date, multilevel_disc_sale, is_wa_so_approval, is_email_so_approval, show_select_product_button, lock_sale_order, product_pricelist_default, auto_mail, group_multi_do, whatsapp_instance_id, whatsapp_token, qr_code_image, whatsapp_authenticate, product_expiry, expiry_days_select, group_analytic_tags, pu_barcode_mobile_type, pu_bm_is_cont_scan, pu_bm_is_notify_on_success, pu_bm_is_notify_on_fail, pu_bm_is_sound_on_success, pu_bm_is_sound_on_fail, pu_bm_is_add_product, pr_expiry_notification, pr_on_date_notify, pr_enter_before_first_notify, pr_enter_after_first_notify, pr_expiry_date, pr_expiry_date_goods, pr_expiry_date_services, rfq_exp_date, po_exp_date, rfq_exp_date_goods, rfq_exp_date_services, po_exp_date_goods, po_exp_date_services, max_percentage, pr_qty_limit, multilevel_disc, is_email_notification_req, is_whatsapp_notification_req, vendor_purchase_limit, is_email_notification, is_whatsapp_notification, pr_order_average_price, is_purchase_vendor_rating_warning, is_product_service_operation_receiving, customer_credit_limit, customer_max_invoice_overdue_days, customer_open_invoice_limit, is_over_credit_limit, over_credit_limit_sequence, over_credit_limit_sequence_select, is_invoice_overdue, invoice_overdue_sequence, invoice_overdue_sequence_select, open_invoice_limit, open_invoice_limit_sequence, open_invoice_limit_sequence_select, is_wa_overlimit_approval, is_email_overlimit_approval, is_email_notification_customer_credit, is_whatsapp_notification_customer_credit, group_use_multi_salesperson_on_leads, is_auto_follow_up, interval_number, interval_type, number_of_repetition, expired_lot_serial_no, is_auto_validate, scrap_income_id, scrap_expense_id, pt_expiry_notification, pt_on_date_notify, pt_enter_before_first_notify, pt_enter_after_first_notify, pt_expiry_date, bo_expiry_notification, bo_enter_before_first_notify, bo_enter_after_first_notify, pt_goods_order_expiry_date, pt_service_order_expiry_date, bo_goods_order_expiry_date, bo_service_order_expiry_date, is_email_notification_tender, is_whatsapp_notification_tender, is_email_notification_bo, is_whatsapp_notification_bo, notifications_expiry_voucher, notifications_time, bo_expiry_date, bo_before_exp_notify, bo_days_before_exp_notify, bo_on_date_notify, bo_approval_email_notify, bo_approval_wa_notify, is_order_rounding, order_rounding_type, rounding_multiplier, pos_product_discount1_id, apply_rounding_type, rounding_method_id, pos_def_receipt_template_id, is_pos_receivable, direct_control, qty_limit, budget_limit, is_email_notification_direct_purchase, is_whatsapp_notification_direct_purchase, is_post_closing_cashbox_value_in_session, allow_create_member_in_pos_screen, pkp_customer, membership_pluspoint_rounding, membership_pluspoint_rounding_type, membership_pluspoint_rounding_multiplier, is_pos_use_deposit, is_return_request_approval_matrix, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What foreign keys exist in pos.loyalty.update.point? or List all relational fields in pos.loyalty.update.point.

Response: The pos.loyalty.update.point model has 5 relational fields: member_id -> res.partner; pos_order_ids -> pos.order; history_ids -> pos.loyalty.history.update.point; create_uid -> res.users; write_uid -> res.users. Many2many fields: pos_order_ids. One2many fields: history_ids.


What is the base_import.tests.models.char model? or Can you explain the purpose of base_import.tests.models.char?

Response: The base_import.tests.models.char model represents Tests : Base Import Model, Character in the ERP system. It contains 8 fields and is used to manage tests : base import model, character data. Defined in module: base_import. Key fields include: value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


List all relational fields in res.country.group. or What are the relationships in res.country.group?

Response: The res.country.group model has 4 relational fields: country_ids -> res.country; pricelist_ids -> product.pricelist; create_uid -> res.users; write_uid -> res.users. Many2many fields: country_ids, pricelist_ids. One2many fields: none.


How is account.financial.year.op used in the system? or What is the account.financial.year.op model?

Response: The account.financial.year.op model represents Opening Balance of Financial Year in the ERP system. It contains 12 fields and is used to manage opening balance of financial year data. Defined in module: account. Key fields include: company_id, opening_move_posted, opening_date, fiscalyear_last_day, fiscalyear_last_month, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What one2many fields are in stock.day.average? or How does stock.day.average relate to other models?

Response: The stock.day.average model has 17 relational fields: product_id -> product.product; branch_id -> res.branch; company_id -> res.company; users_ids -> res.users; cluster_id -> cluster.area; warehouse_line -> stock.day.average.line; 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: users_ids, message_partner_ids, message_channel_ids. One2many fields: warehouse_line, activity_ids, message_follower_ids, message_ids, website_message_ids.


Can you explain the purpose of product.warehouse.cost.line? or What is the product.warehouse.cost.line model?

Response: The product.warehouse.cost.line model represents Product Warehouse Cost in the ERP system. It contains 12 fields and is used to manage product warehouse cost data. Defined in module: equip3_accounting_stockoperation. Key fields include: prod_wh_cost_id, warehouse_id, cost, company_id, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How to work with product.ratio.line fields? or How to create records in product.ratio.line?

Response: To use the product.ratio.line model, you need to provide values for required fields: uom_id, product_tmpl_id, ratio. Readonly fields: description, uom_ref_id, product_variant_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: uom_id [required]; product_tmpl_id [required]; description [readonly] [computed] [no_copy]; ratio [required]; uom_ref_id [readonly] [computed] [no_copy]; product_variant_ids [readonly] [computed] [no_copy]; is_custom_uom [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 tables does mail_message reference? or How does mail_message relate to other tables?

Response: Foreign keys in mail_message: author_id -> res_partner.id [constraint: mail_message_author_id_fkey]; create_uid -> res_users.id [constraint: mail_message_create_uid_fkey]; mail_activity_type_id -> mail_activity_type.id [constraint: mail_message_mail_activity_type_id_fkey]; mail_server_id -> ir_mail_server.id [constraint: mail_message_mail_server_id_fkey]; moderator_id -> res_users.id [constraint: mail_message_moderator_id_fkey]; parent_id -> mail_message.id [constraint: mail_message_parent_id_fkey]; subtype_id -> mail_message_subtype.id [constraint: mail_message_subtype_id_fkey]; write_uid -> res_users.id [constraint: mail_message_write_uid_fkey]. Total foreign key relationships: 8. Referenced tables: mail_message_subtype, res_partner, ir_mail_server, mail_message, mail_activity_type, res_users.


What is the module hierarchy for tax.report? or What methods are defined in tax.report original module?

Response: The tax.report model is defined in module: equip3_accounting_reports. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: view_report, _get_currency, _get_report_values, get_filter, get_filter_data, create, write, get_dynamic_xlsx_report, _domain_branch.


What are the length constraints in account_balance_report_journal_rel? or What columns have default values in account_balance_report_journal_rel?

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


Tell me about the reject.picking.order model. or Describe the reject.picking.order model in Odoo.

Response: The reject.picking.order model represents reject.picking.order in the ERP system. It contains 12 fields and is used to manage reject.picking.order data. Defined in module: pragmatic_odoo_delivery_boy. Key fields include: driver_id, picking_id, assign_date, reject_date, reject_reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Show me the relational structure of format.address.mixin. or What foreign keys exist in format.address.mixin?

Response: The format.address.mixin model has no explicit relational fields defined in its field metadata.


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

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


What methods are defined in assets.approval.reject original module? or What methods are available in assets.approval.reject?

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


List all fields in the product.template.attribute.line model. or What computed fields exist in product.template.attribute.line?

Response: The product.template.attribute.line model has 12 fields. Field types distribution: boolean: 1, many2one: 4, many2many: 1, one2many: 1, integer: 1, char: 1, datetime: 3. Computed fields: 2. Field details: active (boolean) [module: product]; product_tmpl_id (many2one) [required] -> product.template [module: product]; attribute_id (many2one) [required] -> product.attribute [module: product]; value_ids (many2many) -> product.attribute.value [module: product]; product_template_value_ids (one2many) -> product.template.attribute.value [module: product]; 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 do I use the ir.qweb.field.barcode model? or What are common use cases for ir.qweb.field.barcode?

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


How is warranty.claim used in the system? or What does the warranty.claim model represent?

Response: The warranty.claim model represents Claim in the ERP system. It contains 35 fields and is used to manage claim data. Defined in module: bi_warranty_registration. Key fields include: id, name, active, action_next, date_action_next, description, resolution, create_date, write_date, date_deadline, date_closed, date, categ_id, priority, type_action, user_id, user_fault, team_id, company_id, partner_id, email_cc, email_from, partner_phone, stage_id, cause, product_ids, product_id, serial_nos, serial_no, warranty, stage_match, display_name, create_uid, write_uid, __last_update.


What foreign keys exist in base.language.install? or Describe the many2many relations for base.language.install.

Response: The base.language.install model has 3 relational fields: website_ids -> website; create_uid -> res.users; write_uid -> res.users. Many2many fields: website_ids. One2many fields: none.


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

Response: Foreign keys in product_product_setu_inventory_xyz_analysis_report_rel: setu_inventory_xyz_analysis_report_id -> setu_inventory_xyz_analysis_report.id [constraint: product_product_setu_inventor_setu_inventory_xyz_analysis__fkey]; product_product_id -> product_product.id [constraint: product_product_setu_inventory_xyz_anal_product_product_id_fkey]. Total foreign key relationships: 2. Referenced tables: product_product, setu_inventory_xyz_analysis_report.


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

Response: Foreign keys in barcode_configuration: create_uid -> res_users.id [constraint: barcode_configuration_create_uid_fkey]; currency -> res_currency.id [constraint: barcode_configuration_currency_fkey]; write_uid -> res_users.id [constraint: barcode_configuration_write_uid_fkey]. Total foreign key relationships: 3. Referenced tables: res_currency, res_users.


List all columns in all_redeem_rule. or What are the length constraints in all_redeem_rule?

Response: Columns in all_redeem_rule: id (integer) [NOT NULL] [DEFAULT: nextval('all_redeem_rule_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [COMMENT: Name]; min_amt (integer) [PRECISION: 32] [COMMENT: Minimum Points]; max_amt (integer) [PRECISION: 32] [COMMENT: Maximum Points]; reward_amt (integer) [PRECISION: 32] [COMMENT: Redemption Amount]; loyality_id (integer) [PRECISION: 32] [COMMENT: Loyalty ID]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 10. Statistics: 9 nullable, 1 with defaults, 0 with length constraints.


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

Response: Foreign keys in invoice_printout_editor_lines: create_uid -> res_users.id [constraint: invoice_printout_editor_lines_create_uid_fkey]; field_id -> ir_model_fields.id [constraint: invoice_printout_editor_lines_field_id_fkey]; invoice_footer_print_out_id -> invoice_printout_editor.id [constraint: invoice_printout_editor_lines_invoice_footer_print_out_id_fkey]; invoice_header_print_out_id -> invoice_printout_editor.id [constraint: invoice_printout_editor_lines_invoice_header_print_out_id_fkey]; invoice_table_print_out_id -> invoice_printout_editor.id [constraint: invoice_printout_editor_lines_invoice_table_print_out_id_fkey]; write_uid -> res_users.id [constraint: invoice_printout_editor_lines_write_uid_fkey]. Total foreign key relationships: 6. Referenced tables: res_users, invoice_printout_editor, ir_model_fields.


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

Response: Foreign keys in base_import_tests_models_char_noreadonly: create_uid -> res_users.id [constraint: base_import_tests_models_char_noreadonly_create_uid_fkey]; write_uid -> res_users.id [constraint: base_import_tests_models_char_noreadonly_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


What models are connected to auditlog.log? or What foreign keys exist in auditlog.log?

Response: The auditlog.log model has 7 relational fields: model_id -> ir.model; user_id -> res.users; line_ids -> auditlog.log.line; http_session_id -> auditlog.http.session; http_request_id -> auditlog.http.request; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: line_ids.


How to query limit.request data? or How to work with limit.request fields?

Response: To use the limit.request model, you need to provide values for required fields: branch_id, company_id. Readonly fields: name, last_credit_limit, last_open_inv_no, last_max_invoice, state1, state2, limit_approval_matrix, approval_matrix_line_id, approval2, new_amount, last_amount, is_approve_button, user_id, is_credit_limit_brand, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [readonly]; last_credit_limit [readonly] [computed] [no_copy]; last_open_inv_no [readonly] [computed] [no_copy]; last_max_invoice [readonly] [computed] [no_copy]; state1 [readonly] [computed] [no_copy]; state2 [readonly] [computed] [no_copy]; branch_id [required]; limit_approval_matrix [readonly] [computed] [no_copy]; approval_matrix_line_id [readonly] [computed] [no_copy]; approval2 [readonly] [computed] [no_copy]; new_amount [readonly] [computed] [no_copy]; last_amount [readonly] [computed] [no_copy]; is_approve_button [readonly] [computed] [no_copy]; user_id [readonly] [computed] [no_copy]; is_credit_limit_brand [readonly] [computed] [no_copy]; company_id [required] [has_default]; activity_state [readonly] [computed] [no_copy]; activity_user_id [computed] [no_copy]; activity_type_id [computed] [no_copy]; activity_type_icon [readonly] [computed] [no_copy]; activity_date_deadline [readonly] [computed] [no_copy]; my_activity_date_deadline [readonly] [computed] [no_copy]; activity_summary [computed] [no_copy]; activity_exception_decoration [readonly] [computed] [no_copy]; activity_exception_icon [readonly] [computed] [no_copy]; message_is_follower [readonly] [computed] [no_copy]; message_partner_ids [readonly] [computed] [no_copy]; message_channel_ids [readonly] [computed] [no_copy]; message_unread [readonly] [computed] [no_copy]; message_unread_counter [readonly] [computed] [no_copy]; message_needaction [readonly] [computed] [no_copy]; message_needaction_counter [readonly] [computed] [no_copy]; message_has_error [readonly] [computed] [no_copy]; message_has_error_counter [readonly] [computed] [no_copy]; message_attachment_count [readonly] [computed] [no_copy]; message_has_sms_error [readonly] [computed] [no_copy]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


List all relational fields in opening.balance. or How does opening.balance relate to other models?

Response: The opening.balance model has 6 relational fields: company_id -> res.company; journal_id -> account.journal; partner_id -> res.partner; line_ids -> opening.balance.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: line_ids.


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

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


How is ir.model.constraint used in the system? or Tell me about the ir.model.constraint model.

Response: The ir.model.constraint model represents Model Constraint in the ERP system. It contains 13 fields and is used to manage model constraint data. Defined in module: base. Key fields include: name, definition, message, model, module, type, write_date, create_date, id, display_name, create_uid, write_uid, __last_update.


What are the technical details of material.request.line? or What modules define material.request.line?

Response: The material.request.line model is defined in module: equip3_inventory_operation. It has 25 computed fields: product_uom_category_id, status, request_date, done_qty_dup, requested_by, company_id, pr_requested_qty, pr_pending_qty_to_receive, pr_in_progress_qty, pr_done_qty, pr_cancelled_qty, itr_requested_qty, itr_in_progress_qty, itr_done_qty, itr_returned_qty, analytic_account_group_ids, progress_quantity, pr_remaining_qty, itr_remaining_qty, itw_requested_qty, itw_in_progress_qty, itw_remaining_qty, itw_done_qty, display_name, __last_update. Stored computed fields: none. Related fields: product_uom_category_id -> product.uom_id.category_id, status -> material_request_id.status, request_date -> material_request_id.schedule_date, requested_by -> material_request_id.requested_by, company_id -> material_request_id.company_id, analytic_account_group_ids -> material_request_id.analytic_account_group_ids. Original module methods: default_get, action_show_stock, _compute_remaining_qty_pr, _compute_remaining_qty_itr, _compute_remaining_qty_itw, _compute_progress_quantity, _compute_itr_requested_qty, _compute_itw_requested_qty, _compute_itr_in_progress_qty, _compute_itw_in_progress_qty, _compute_itr_done_qty, _compute_itw_done_qty, _compute_itr_returned_qty, _compute_pr_requested_qty, _compute_pr_pending_qty_to_receive, _compute_pr_in_progress_qty, _compute_pr_done_qty, _compute_pr_cancelled_qty, _compute_done_qty, _get_uom, _check_product_type.


What computed fields exist in pos.cashbox.history? or What fields does pos.cashbox.history have?

Response: The pos.cashbox.history model has 14 fields. Field types distribution: float: 2, many2one: 5, datetime: 5, integer: 1, char: 1. Computed fields: 2. Field details: start_balance (float) [module: equip3_pos_cashbox]; closing_balance (float) [module: equip3_pos_cashbox]; opened_by_user_id (many2one) -> res.users [module: equip3_pos_cashbox]; pos_session_id (many2one) -> pos.session [module: equip3_pos_cashbox]; pos_config_id (many2one) -> pos.config [module: equip3_pos_cashbox]; start_date (datetime) [module: equip3_pos_cashbox]; closing_date (datetime) [module: equip3_pos_cashbox]; 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 column structure of us_id. or What are the column types in us_id?

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


How to query website.rewrite data? or What fields are readonly in website.rewrite?

Response: To use the website.rewrite model, you need to provide values for required fields: name. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [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 column types in account_tax_repartition_minus_report_line? or Show me the column structure of account_tax_repartition_minus_report_line.

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


Can you explain the purpose of report.equip3_accounting_reports.tax_report? or Tell me about the report.equip3_accounting_reports.tax_report model.

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


What is the module hierarchy for free.product.lines? or What methods are available in free.product.lines?

Response: The free.product.lines model is defined in module: equip3_sale_loyalty. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: _onchange_product_id.


How do I use the hide.view.nodes model? or What fields are readonly in hide.view.nodes?

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


What fields are available in mail_resend_cancel? or Which columns are nullable in mail_resend_cancel?

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


Show me the foreign key constraints of purchase_order_sh_purchase_update_mass_tag_wizard_rel. or Describe the relational structure of purchase_order_sh_purchase_update_mass_tag_wizard_rel.

Response: Foreign keys in purchase_order_sh_purchase_update_mass_tag_wizard_rel: sh_purchase_update_mass_tag_wizard_id -> sh_purchase_update_mass_tag_wizard.id [constraint: purchase_order_sh_purchase_up_sh_purchase_update_mass_tag__fkey]; purchase_order_id -> purchase_order.id [constraint: purchase_order_sh_purchase_update_mass_t_purchase_order_id_fkey]. Total foreign key relationships: 2. Referenced tables: sh_purchase_update_mass_tag_wizard, purchase_order.


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

Response: Foreign keys in sh_purchase_bill_summary_wizard: create_uid -> res_users.id [constraint: sh_purchase_bill_summary_wizard_create_uid_fkey]; write_uid -> res_users.id [constraint: sh_purchase_bill_summary_wizard_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


What operations can I perform on queue.job.demo? or How to create records in queue.job.demo?

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


Which columns are nullable in combo_option_item? or List all columns in combo_option_item.

Response: Columns in combo_option_item: id (integer) [NOT NULL] [DEFAULT: nextval('combo_option_item_id_seq'::regclass)] [PRECISION: 32]; combo_option_id (integer) [PRECISION: 32] [COMMENT: Combo Option]; product_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Product]; product_variant_id (integer) [PRECISION: 32] [COMMENT: Product]; extra_price (double precision) [PRECISION: 53] [COMMENT: Extra Price]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 9. Statistics: 7 nullable, 1 with defaults, 0 with length constraints.


What models are connected to pos.call.log? or How does pos.call.log relate to other models?

Response: The pos.call.log model has 4 relational fields: branch_id -> res.branch; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


What fields are readonly in pos.report.category? or How do I use the pos.report.category model?

Response: To use the pos.report.category 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.


Tell me about the account.asset.depreciation.line model. or What does the account.asset.depreciation.line model represent?

Response: The account.asset.depreciation.line model represents Asset depreciation line in the ERP system. It contains 19 fields and is used to manage asset depreciation line data. Defined in module: om_account_asset. Key fields include: name, sequence, asset_id, parent_state, amount, remaining_value, depreciated_value, depreciation_date, move_id, move_check, move_posted_check, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Describe the many2many relations for stock.valuation.layer.revaluation. or How does stock.valuation.layer.revaluation relate to other models?

Response: The stock.valuation.layer.revaluation model has 7 relational fields: company_id -> res.company; currency_id -> res.currency; product_id -> product.product; account_journal_id -> account.journal; account_id -> account.account; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


How is remove.pos.order implemented technically? or What methods are available in remove.pos.order?

Response: The remove.pos.order 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: remove_pos_orders.


Describe the many2many relations for product.uom.price. or Show me the relational structure of product.uom.price.

Response: The product.uom.price model has 4 relational fields: uom_id -> uom.uom; product_tmpl_id -> product.template; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


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

Response: Columns in wizard_quotation_agreement: id (integer) [NOT NULL] [DEFAULT: nextval('wizard_quotation_agreement_id_seq'::regclass)] [PRECISION: 32]; agreement_id (integer) [PRECISION: 32] [COMMENT: Tender]; company_id (integer) [PRECISION: 32] [COMMENT: Company]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 7. Statistics: 6 nullable, 1 with defaults, 0 with length constraints.


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

Response: Foreign keys in uom_conversion_history: create_uid -> res_users.id [constraint: uom_conversion_history_create_uid_fkey]; location_id -> stock_location.id [constraint: uom_conversion_history_location_id_fkey]; package_id -> stock_quant_package.id [constraint: uom_conversion_history_package_id_fkey]; partner_id -> res_partner.id [constraint: uom_conversion_history_partner_id_fkey]; prod_lot_id -> stock_production_lot.id [constraint: uom_conversion_history_prod_lot_id_fkey]; product_id -> product_product.id [constraint: uom_conversion_history_product_id_fkey]; si_uom_id -> stock_inventory.id [constraint: uom_conversion_history_si_uom_id_fkey]; uom_conversion -> uom_uom.id [constraint: uom_conversion_history_uom_conversion_fkey]; uom_id -> uom_uom.id [constraint: uom_conversion_history_uom_id_fkey]; write_uid -> res_users.id [constraint: uom_conversion_history_write_uid_fkey]. Total foreign key relationships: 10. Referenced tables: product_product, res_partner, stock_inventory, stock_location, stock_quant_package, res_users, stock_production_lot, uom_uom.


How to query change.password.user data? or How to work with change.password.user fields?

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


How to query pos.service.charge data? or How to create records in pos.service.charge?

Response: To use the pos.service.charge model, you need to provide values for required fields: name, product_id, type, amount. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [required]; product_id [required]; type [required] [has_default]; 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.


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

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


What models are connected to im_livechat.report.operator? or List all relational fields in im_livechat.report.operator.

Response: The im_livechat.report.operator model has 3 relational fields: partner_id -> res.partner; livechat_channel_id -> im_livechat.channel; channel_id -> mail.channel. Many2many fields: none. One2many fields: none.


What fields are available in coupon_coupon? or Which columns are nullable in coupon_coupon?

Response: Columns in coupon_coupon: id (integer) [NOT NULL] [DEFAULT: nextval('coupon_coupon_id_seq'::regclass)] [PRECISION: 32]; code (character varying) [NOT NULL] [COMMENT: Code]; state (character varying) [NOT NULL] [COMMENT: State]; partner_id (integer) [PRECISION: 32] [COMMENT: For Customer]; program_id (integer) [PRECISION: 32] [COMMENT: Program]; 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]; order_id (integer) [PRECISION: 32] [COMMENT: Order Reference]; sales_order_id (integer) [PRECISION: 32] [COMMENT: Used in]; purchase_id (integer) [PRECISION: 32] [COMMENT: Order Reference]; purchases_order_id (integer) [PRECISION: 32] [COMMENT: Used in]; pos_order_id (integer) [PRECISION: 32] [COMMENT: Pos Order]; origin (character varying) [COMMENT: Origin]; is_gift_card (boolean) [COMMENT: Is Gift Card]; is_returned_order (boolean) [COMMENT: Coverted from Return Order]; pos_create_date (timestamp without time zone) [COMMENT: POS Create Date]; pos_create_uid (integer) [PRECISION: 32] [COMMENT: POS User Create]; pos_config_id (integer) [PRECISION: 32] [COMMENT: POS Config Create]; base_amount (double precision) [PRECISION: 53] [COMMENT: Base Amount]; pos_orderline_id (integer) [PRECISION: 32] [COMMENT: Pos Order Line]. Total columns: 22. Statistics: 19 nullable, 1 with defaults, 0 with length constraints.


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

Response: Foreign keys in list_top_product_compare: create_uid -> res_users.id [constraint: list_top_product_compare_create_uid_fkey]; top_id -> sh_tsp_top_selling_product_wizard.id [constraint: list_top_product_compare_top_id_fkey]; write_uid -> res_users.id [constraint: list_top_product_compare_write_uid_fkey]. Total foreign key relationships: 3. Referenced tables: res_users, sh_tsp_top_selling_product_wizard.


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

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


Can you explain the purpose of ir.module.module.dependency? or What does the ir.module.module.dependency model represent?

Response: The ir.module.module.dependency model represents Module dependency in the ERP system. It contains 14 fields and is used to manage module dependency data. Defined in module: base. Key fields include: name, module_id, depend_id, state, auto_install_required, installed_version, latest_version, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How does stock.return.picking.line relate to other models? or What models are connected to stock.return.picking.line?

Response: The stock.return.picking.line model has 7 relational fields: product_id -> product.product; uom_id -> uom.uom; wizard_id -> stock.return.picking; move_id -> stock.move; return_reason -> return.reason; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


What are the relationships in budget.purchase? or How does budget.purchase relate to other models?

Response: The budget.purchase model has 19 relational fields: parent_id -> crossovered.budget; purchase_budget_line -> budget.purchase.lines; company_id -> res.company; branch_id -> res.branch; account_tag_ids -> account.analytic.tag; approval_matrix -> approval.matrix.accounting; request_partner_id -> res.partner; approved_matrix_ids -> approval.matrix.accounting.lines; approval_matrix_line_id -> approval.matrix.accounting.lines; currency_id -> res.currency; purchase_lines_id -> purchase.order.line; 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: account_tag_ids, message_partner_ids, message_channel_ids. One2many fields: purchase_budget_line, approved_matrix_ids, message_follower_ids, message_ids, website_message_ids.


How to work with coupon.rule fields? or How to query coupon.rule data?

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


Which fields in invoice.template.table are computed? or What are the technical details of invoice.template.table?

Response: The invoice.template.table model is defined in module: equip3_accounting_operation. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: .


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

Response: Columns in quality_check_report: id (integer) [NOT NULL] [DEFAULT: nextval('quality_check_report_id_seq'::regclass)] [PRECISION: 32]; date_from (date) [NOT NULL] [COMMENT: Start Date]; date_to (date) [NOT NULL] [COMMENT: End Date]; state (character varying) [COMMENT: Status]; group_by (character varying) [COMMENT: Group By]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 9. Statistics: 6 nullable, 1 with defaults, 0 with length constraints.


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

Response: Foreign keys in cancel_picking: create_uid -> res_users.id [constraint: cancel_picking_create_uid_fkey]; write_uid -> res_users.id [constraint: cancel_picking_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


Which fields are stored computed fields in sh.mrp.quality.check? or Describe the implementation of sh.mrp.quality.check.

Response: The sh.mrp.quality.check model is defined in module: sh_inventory_mrp_qc. It has 22 computed fields: activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, display_name, __last_update. Stored computed fields: none. Related fields: activity_user_id -> activity_ids.user_id, activity_type_id -> activity_ids.activity_type_id, activity_type_icon -> activity_ids.icon, activity_summary -> activity_ids.summary. Original module methods: accept, reject.


What are the length constraints in credit_limit_approval? or What are the column types in credit_limit_approval?

Response: Columns in credit_limit_approval: id (integer) [NOT NULL] [DEFAULT: nextval('credit_limit_approval_id_seq'::regclass)] [PRECISION: 32]; sequence (integer) [PRECISION: 32] [COMMENT: Sequence]; sequence2 (integer) [PRECISION: 32] [COMMENT: Sequence]; minimum_approver (integer) [PRECISION: 32] [COMMENT: Minimum Approver]; status (text) [COMMENT: Approval Status]; time (character varying) [COMMENT: Timestamp]; feedback (text) [COMMENT: Feedback]; approved (boolean) [COMMENT: Approved]; approval (integer) [PRECISION: 32] [COMMENT: Approval]; credit_id (integer) [PRECISION: 32] [COMMENT: Credit Limit Customer]; last_approved (integer) [PRECISION: 32] [COMMENT: Users]; 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: 15. Statistics: 14 nullable, 1 with defaults, 0 with length constraints.


How to query account.tax.repartition.line data? or How to work with account.tax.repartition.line fields?

Response: To use the account.tax.repartition.line model, you need to provide values for required fields: factor_percent, repartition_type. Readonly fields: factor, tax_id, tax_fiscal_country_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: factor_percent [required]; factor [readonly] [computed] [no_copy]; repartition_type [required] [has_default]; tax_id [readonly] [computed] [no_copy]; tax_fiscal_country_id [readonly] [computed] [no_copy]; company_id [readonly] [computed] [no_copy]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


How to work with utm.campaign fields? or How do I use the utm.campaign model?

Response: To use the utm.campaign model, you need to provide values for required fields: name, user_id, stage_id. Readonly fields: click_count, use_leads, crm_lead_count, 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. Field usage details: name [required]; user_id [required] [has_default]; stage_id [required] [has_default]; click_count [readonly] [computed] [no_copy]; use_leads [readonly] [computed] [no_copy]; crm_lead_count [readonly] [computed] [no_copy]; mailing_mail_count [readonly] [computed] [no_copy]; received_ratio [readonly] [computed] [no_copy]; opened_ratio [readonly] [computed] [no_copy]; replied_ratio [readonly] [computed] [no_copy]; bounced_ratio [readonly] [computed] [no_copy]; quotation_count [readonly] [computed] [no_copy]; invoiced_amount [readonly] [computed] [has_default] [no_copy]; company_id [readonly] [has_default] [has_states]; currency_id [readonly] [computed] [no_copy]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


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

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


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

Response: Foreign keys in product_id: company_id -> product_template.id [constraint: product_id_company_id_fkey]; prod_comp_id -> res_company.id [constraint: product_id_prod_comp_id_fkey]. Total foreign key relationships: 2. Referenced tables: res_company, product_template.


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

Response: Foreign keys in res_users_apikeys_description: create_uid -> res_users.id [constraint: res_users_apikeys_description_create_uid_fkey]; write_uid -> res_users.id [constraint: res_users_apikeys_description_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


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

Response: The limit_approval_matrix_lines_res_users_rel table has 2 columns and 2 foreign key relationships. It stores data related to limit approval matrix lines 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.


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

Response: The send_whatsapp_compose_message_ir_attachments_rel table has 2 columns and 2 foreign key relationships. It stores data related to send whatsapp compose message ir attachments rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


What business logic is in sale.order.template? or What operations can I perform on sale.order.template?

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


What is the module hierarchy for asset.asset.revalue.wizard? or How is asset.asset.revalue.wizard implemented technically?

Response: The asset.asset.revalue.wizard model is defined in module: equip3_accounting_asset. It has 3 computed fields: company_currency_id, display_name, __last_update. Stored computed fields: company_currency_id. Related fields: company_currency_id -> company_id.currency_id. Original module methods: default_get, confirm_revalue_asset.


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

Response: Foreign keys in purchase_flow_asset: create_uid -> res_users.id [constraint: purchase_flow_asset_create_uid_fkey]; write_uid -> res_users.id [constraint: purchase_flow_asset_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


What is the account.voucher.line model? or Describe the account.voucher.line model in Odoo.

Response: The account.voucher.line model represents Accounting Voucher Line in the ERP system. It contains 21 fields and is used to manage accounting voucher line data. Defined in module: aos_account_voucher. Key fields include: name, sequence, voucher_id, product_id, uom_id, account_id, price_unit, price_subtotal, quantity, account_analytic_id, analytic_tag_ids, company_id, tax_ids, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What field types are used in nsfp.registration? or Show me the fields of nsfp.registration.

Response: The nsfp.registration model has 15 fields. Field types distribution: integer: 2, many2one: 4, char: 5, boolean: 1, datetime: 3. Computed fields: 2. Field details: record_id (integer) [module: equip3_accounting_efaktur]; fiscal_year (many2one) -> sh.fiscal.year [module: equip3_accounting_efaktur]; start (char) [module: equip3_accounting_efaktur]; end (char) [module: equip3_accounting_efaktur]; last_number (char) [module: equip3_accounting_efaktur]; registration_date (char) [module: equip3_accounting_efaktur]; is_use (boolean) [module: equip3_accounting_efaktur]; company_id (many2one) -> res.company [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].


List all fields in the pos.promotion.tebus.murah model. or Describe the field structure of pos.promotion.tebus.murah.

Response: The pos.promotion.tebus.murah model has 13 fields. Field types distribution: boolean: 1, many2one: 4, float: 1, integer: 2, many2many: 1, char: 1, datetime: 3. Computed fields: 2. Field details: active (boolean) [module: equip3_pos_masterdata]; promotion_id (many2one) [required] -> pos.promotion [module: equip3_pos_masterdata]; product_id (many2one) [required] -> product.product [module: equip3_pos_masterdata]; price (float) [required] [module: equip3_pos_masterdata]; quantity (integer) [required] [module: equip3_pos_masterdata]; product_ids (many2many) -> product.product [module: equip3_pos_masterdata]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


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

Response: Foreign keys in merge_opportunity_rel: merge_id -> crm_merge_opportunity.id [constraint: merge_opportunity_rel_merge_id_fkey]; opportunity_id -> crm_lead.id [constraint: merge_opportunity_rel_opportunity_id_fkey]. Total foreign key relationships: 2. Referenced tables: crm_lead, crm_merge_opportunity.


Describe the implementation of procurement.group. or What is the module hierarchy for procurement.group?

Response: The procurement.group model is defined in module: stock. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: Procurement, run, _search_rule, _get_rule, _get_rule_domain, _merge_domain, _get_moves_to_assign_domain, _run_scheduler_tasks, run_scheduler, _get_orderpoint_domain.


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

Response: Foreign keys in product_product_sale_order_alternative_product_rel: sale_order_alternative_product_id -> sale_order_alternative_product.id [constraint: product_product_sale_order_al_sale_order_alternative_produ_fkey]; product_product_id -> product_product.id [constraint: product_product_sale_order_alternative__product_product_id_fkey]. Total foreign key relationships: 2. Referenced tables: product_product, sale_order_alternative_product.


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

Response: Foreign keys in mail_resend_message: create_uid -> res_users.id [constraint: mail_resend_message_create_uid_fkey]; mail_message_id -> mail_message.id [constraint: mail_resend_message_mail_message_id_fkey]; write_uid -> res_users.id [constraint: mail_resend_message_write_uid_fkey]. Total foreign key relationships: 3. Referenced tables: mail_message, res_users.


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

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


How to work with purchase.request.wizard.line fields? or What are common use cases for purchase.request.wizard.line?

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


List all relational fields in sh.mrp.quality.check. or Show me the relational structure of sh.mrp.quality.check.

Response: The sh.mrp.quality.check model has 17 relational fields: product_id -> product.product; sh_workorder_id -> mrp.workorder; sh_mrp -> mrp.production; control_point_id -> sh.qc.point; company_id -> res.company; attachment_ids -> ir.attachment; 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: attachment_ids, message_partner_ids, message_channel_ids. One2many fields: activity_ids, message_follower_ids, message_ids, website_message_ids.