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

Response: Columns in account_group_template: id (integer) [NOT NULL] [DEFAULT: nextval('account_group_template_id_seq'::regclass)] [PRECISION: 32]; parent_id (integer) [PRECISION: 32] [COMMENT: Parent]; name (character varying) [NOT NULL] [COMMENT: Name]; code_prefix_start (character varying) [COMMENT: Code Prefix Start]; code_prefix_end (character varying) [COMMENT: Code Prefix End]; chart_template_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Chart Template]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 10. Statistics: 7 nullable, 1 with defaults, 0 with length constraints.


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

Response: Foreign keys in sh_send_notification: create_uid -> res_users.id [constraint: sh_send_notification_create_uid_fkey]; write_uid -> res_users.id [constraint: sh_send_notification_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


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

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


What are the available fields for remove.action? or Describe the field structure of remove.action.

Response: The remove.action model has 25 fields. Field types distribution: many2one: 4, many2many: 4, boolean: 10, char: 3, integer: 1, datetime: 3. Computed fields: 4. Field details: access_management_id (many2one) -> access.management [module: simplify_access_management]; model_id (many2one) -> ir.model [module: simplify_access_management]; view_data_ids (many2many) -> view.data [module: simplify_access_management]; server_action_ids (many2many) -> action.data [module: simplify_access_management]; report_action_ids (many2many) -> action.data [module: simplify_access_management]; restrict_export (boolean) [module: simplify_access_management]; restrict_import (boolean) [module: simplify_access_management]; restrict_upload_acc_move (boolean) [module: simplify_access_management]; readonly (boolean) [module: simplify_access_management]; restrict_create (boolean) [module: simplify_access_management]; restrict_edit (boolean) [module: simplify_access_management]; restrict_delete (boolean) [module: simplify_access_management]; restrict_archive_unarchive (boolean) [module: simplify_access_management]; restrict_duplicate (boolean) [module: simplify_access_management]; restrict_chatter (boolean) [module: simplify_access_management]; model_name (char) [readonly] [compute: _compute_model_name] [not stored] [module: simplify_access_management]; model (char) [readonly] [compute: <bound method Field._compute_related of remove.action.model>] [stored] [module: advance_access_management] [related: model_id.model]; view_ids (many2many) -> ir.ui.view [module: advance_access_management]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


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

Response: Foreign keys in account_move_line_account_payment_register_rel: account_payment_register_id -> account_payment_register.id [constraint: account_move_line_account_paym_account_payment_register_id_fkey]; account_move_line_id -> account_move_line.id [constraint: account_move_line_account_payment_re_account_move_line_id_fkey1]; account_move_line_id -> account_move_line.id [constraint: account_move_line_account_payment_reg_account_move_line_id_fkey]. Total foreign key relationships: 3. Referenced tables: account_move_line, account_payment_register.


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

Response: Columns in account_pettycash_voucher_wizard: id (integer) [NOT NULL] [DEFAULT: nextval('account_pettycash_voucher_wizard_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [NOT NULL] [COMMENT: Name]; number (character varying) [NOT NULL] [COMMENT: Number]; fund (integer) [PRECISION: 32] [COMMENT: Fund]; partner_id (integer) [PRECISION: 32] [COMMENT: Partner]; date (date) [NOT NULL] [COMMENT: Date]; ba_ca_journal_id (integer) [PRECISION: 32] [COMMENT: Bank/Cash Journal]; payment_reference (character varying) [COMMENT: Payment Reference]; submitter_id (integer) [PRECISION: 32] [COMMENT: Submitter]; currency_id (integer) [PRECISION: 32] [COMMENT: Currency]; company_id (integer) [PRECISION: 32] [COMMENT: Company]; state (character varying) [COMMENT: Status]; total (numeric) [COMMENT: Total]; is_pettycash_voucher_approved (boolean) [COMMENT: Petty Cash Voucher Approved]; move_id (integer) [PRECISION: 32] [COMMENT: Journal Entry]; narration (text) [COMMENT: Notes]; voucher_type (character varying) [COMMENT: Type]; tax_amount (numeric) [COMMENT: Tax Amount]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 22. Statistics: 18 nullable, 1 with defaults, 0 with length constraints.


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

Response: Foreign keys in setu_inventory_overstock_report: company_id -> res_company.id [constraint: setu_inventory_overstock_report_company_id_fkey]; create_uid -> res_users.id [constraint: setu_inventory_overstock_report_create_uid_fkey]; write_uid -> res_users.id [constraint: setu_inventory_overstock_report_write_uid_fkey]. Total foreign key relationships: 3. Referenced tables: res_users, res_company.


How to query ks_dashboard_ninja.ks_grid_per_company data? or What business logic is in ks_dashboard_ninja.ks_grid_per_company?

Response: To use the ks_dashboard_ninja.ks_grid_per_company 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.


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

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


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

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


Show me the fields of format.address.mixin. or Describe the field structure of format.address.mixin.

Response: The format.address.mixin 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].


Which fields are stored computed fields in wizard.scrap.order.report? or What methods are available in wizard.scrap.order.report?

Response: The wizard.scrap.order.report model is defined in module: eq_scrap_order_report. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: check_date_range, get_scrap_order_data, print_report, go_back, print_xls_report.


Describe the implementation of res.company. or What methods are defined in res.company original module?

Response: The res.company model is defined in module: base. It has 49 computed fields: name, logo, logo_web, street2, zip, city, state_id, country_id, website, catchall_email, catchall_formatted, email_formatted, 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, account_tax_fiscal_country_id, account_opening_journal_id, country_code, website_theme_onboarding_done, report_template_id1, report_sale_template_id1, report_po_template_id1, report_delivery_template_id1, logo_footer, street, phone, email, vat, mr_show_analytic_account, contact_address, display_name, __last_update. Stored computed fields: name, logo_web, account_tax_fiscal_country_id, logo_footer, phone, email. Related fields: name -> partner_id.name, logo -> partner_id.image_1920, website -> partner_id.website, 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, account_opening_journal_id -> account_opening_move_id.journal_id, country_code -> country_id.code, phone -> partner_id.phone, email -> partner_id.email, vat -> partner_id.vat. Original module methods: _populate_factories, _populate, copy, _get_logo, _default_currency_id, _get_default_favicon, init, _get_company_address_field_names, _get_company_address_update, _compute_address, _inverse_street, _inverse_street2, _inverse_zip, _inverse_city, _inverse_state, _inverse_country, _compute_logo_web, _onchange_state, _onchange_country_id, _name_search, _company_default_get, cache_restart, create, write, _check_parent_id, open_company_edit_report, write_company_and_print_report, action_open_base_onboarding_company, set_onboarding_step_done, get_and_update_onbarding_state, action_save_onboarding_company_step, _get_main_company.


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

Response: Foreign keys in product_ribbon: create_uid -> res_users.id [constraint: product_ribbon_create_uid_fkey]; write_uid -> res_users.id [constraint: product_ribbon_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


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

Response: Foreign keys in product_category_res_partner_rel: product_category_id -> product_category.id [constraint: product_category_res_partner_rel_product_category_id_fkey]; res_partner_id -> res_partner.id [constraint: product_category_res_partner_rel_res_partner_id_fkey]. Total foreign key relationships: 2. Referenced tables: res_partner, product_category.


What fields does module.advanced.upgrade have? or What computed fields exist in module.advanced.upgrade?

Response: The module.advanced.upgrade model has 17 fields. Field types distribution: many2one: 4, char: 6, selection: 1, one2many: 1, boolean: 1, integer: 1, datetime: 3. Computed fields: 8. Field details: module_id (many2one) [required] -> ir.module.module [module: equip3_config]; module_shortdesc (char) [readonly] [compute: <bound method Field._compute_related of module.advanced.upgrade.module_shortdesc>] [not stored] [module: equip3_config] [related: module_id.shortdesc]; module_name (char) [readonly] [compute: <bound method Field._compute_related of module.advanced.upgrade.module_name>] [not stored] [module: equip3_config] [related: module_id.name]; module_author (char) [readonly] [compute: <bound method Field._compute_related of module.advanced.upgrade.module_author>] [not stored] [module: equip3_config] [related: module_id.author]; module_installed_version (char) [readonly] [compute: <bound method Field._compute_related of module.advanced.upgrade.module_installed_version>] [not stored] [module: equip3_config] [related: module_id.installed_version]; module_latest_version (char) [readonly] [compute: <bound method Field._compute_related of module.advanced.upgrade.module_latest_version>] [not stored] [module: equip3_config] [related: module_id.latest_version]; module_state (selection) [readonly] [compute: <bound method Field._compute_related of module.advanced.upgrade.module_state>] [not stored] [module: equip3_config] [related: module_id.state]; children_ids (one2many) -> module.advanced.upgrade [module: equip3_config]; parent_id (many2one) -> module.advanced.upgrade [module: equip3_config]; selected (boolean) [module: equip3_config]; 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 constraint names in extract_rfq_wizard. or What are the foreign keys in extract_rfq_wizard?

Response: Foreign keys in extract_rfq_wizard: create_uid -> res_users.id [constraint: extract_rfq_wizard_create_uid_fkey]; write_uid -> res_users.id [constraint: extract_rfq_wizard_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


What does the res.partner.industry model represent? or Can you explain the purpose of res.partner.industry?

Response: The res.partner.industry model represents Industry in the ERP system. It contains 10 fields and is used to manage industry data. Defined in module: base. Key fields include: name, full_name, active, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How to work with approval.matrix.accounting fields? or How to query approval.matrix.accounting data?

Response: To use the approval.matrix.accounting model, you need to provide values for required fields: name, company_id, approval_matrix_line_ids. Readonly fields: company_id, filter_branch_ids, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, access_url, access_warning, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [required]; company_id [required] [readonly] [has_default]; filter_branch_ids [readonly] [computed] [no_copy]; approval_matrix_line_ids [required] [no_copy]; activity_state [readonly] [computed] [no_copy]; activity_user_id [computed] [no_copy]; activity_type_id [computed] [no_copy]; activity_type_icon [readonly] [computed] [no_copy]; activity_date_deadline [readonly] [computed] [no_copy]; my_activity_date_deadline [readonly] [computed] [no_copy]; activity_summary [computed] [no_copy]; activity_exception_decoration [readonly] [computed] [no_copy]; activity_exception_icon [readonly] [computed] [no_copy]; message_is_follower [readonly] [computed] [no_copy]; message_partner_ids [readonly] [computed] [no_copy]; message_channel_ids [readonly] [computed] [no_copy]; message_unread [readonly] [computed] [no_copy]; message_unread_counter [readonly] [computed] [no_copy]; message_needaction [readonly] [computed] [no_copy]; message_needaction_counter [readonly] [computed] [no_copy]; message_has_error [readonly] [computed] [no_copy]; message_has_error_counter [readonly] [computed] [no_copy]; message_attachment_count [readonly] [computed] [no_copy]; message_has_sms_error [readonly] [computed] [no_copy]; access_url [readonly] [computed] [no_copy]; access_warning [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 many columns are in res_users_warranty_settings_rel? or What indexes exist on res_users_warranty_settings_rel?

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


What are the available fields for pos.promotion.multilevel.condition? or Which fields are required in pos.promotion.multilevel.condition?

Response: The pos.promotion.multilevel.condition model has 11 fields. Field types distribution: boolean: 1, many2one: 4, float: 1, integer: 1, char: 1, datetime: 3. Computed fields: 2. Field details: active (boolean) [module: equip3_pos_masterdata]; product_id (many2one) [required] -> product.product [module: equip3_pos_masterdata]; minimum_quantity (float) [required] [module: equip3_pos_masterdata]; promotion_id (many2one) [required] -> pos.promotion [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].


How to create records in auditlog.rule? or What business logic is in auditlog.rule?

Response: To use the auditlog.rule model, you need to provide values for required fields: name, log_type, state. Readonly fields: model_name, model_model, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [required] [has_states]; model_name [readonly]; model_model [readonly]; log_type [required] [has_default] [has_states]; state [required] [has_default] [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.


Tell me about the cancel.picking model. or What is the cancel.picking model?

Response: The cancel.picking model represents Cancel Picking in the ERP system. It contains 8 fields and is used to manage cancel picking data. Defined in module: equip3_inventory_operation. Key fields include: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Which fields in hide.filters.groups are computed? or What methods are defined in hide.filters.groups original module?

Response: The hide.filters.groups model is defined in module: simplify_access_management. It has 3 computed fields: model_name, display_name, __last_update. Stored computed fields: model_name. Related fields: model_name -> model_id.model. Original module methods: _get_filter_groups, load_views, fields_view_get, _get_access_management_domain_record, _check_access_management_right, _display_access_management_error, unlink, write, create.


Describe the global_search_ir_model_fields_rel table structure. or Explain the global_search_ir_model_fields_rel table schema.

Response: The global_search_ir_model_fields_rel table has 2 columns and 2 foreign key relationships. It stores data related to global search ir model fields rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


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

Response: Foreign keys in mr_approval_matrix: branch_id -> res_branch.id [constraint: mr_approval_matrix_branch_id_fkey]; campaign_id -> utm_campaign.id [constraint: mr_approval_matrix_campaign_id_fkey]; company_id -> res_company.id [constraint: mr_approval_matrix_company_id_fkey]; create_uid -> res_users.id [constraint: mr_approval_matrix_create_uid_fkey]; medium_id -> utm_medium.id [constraint: mr_approval_matrix_medium_id_fkey]; message_main_attachment_id -> ir_attachment.id [constraint: mr_approval_matrix_message_main_attachment_id_fkey]; source_id -> utm_source.id [constraint: mr_approval_matrix_source_id_fkey]; warehouse_id -> stock_warehouse.id [constraint: mr_approval_matrix_warehouse_id_fkey]; write_uid -> res_users.id [constraint: mr_approval_matrix_write_uid_fkey]. Total foreign key relationships: 9. Referenced tables: utm_source, stock_warehouse, utm_medium, res_company, ir_attachment, res_users, res_branch, utm_campaign.


How does base.module.uninstall relate to other models? or Describe the many2many relations for base.module.uninstall.

Response: The base.module.uninstall model has 5 relational fields: module_id -> ir.module.module; module_ids -> ir.module.module; model_ids -> ir.model; create_uid -> res.users; write_uid -> res.users. Many2many fields: module_ids, model_ids. One2many fields: none.


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

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


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

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


What data can be stored in sh.mrp.pass.fail? or Describe the field structure of sh.mrp.pass.fail.

Response: The sh.mrp.pass.fail model has 12 fields. Field types distribution: many2one: 6, text: 1, integer: 1, char: 1, datetime: 3. Computed fields: 2. Field details: product_id (many2one) [readonly] -> product.product [module: sh_inventory_mrp_qc]; sh_message (text) [readonly] [module: sh_inventory_mrp_qc]; sh_quality_point_id (many2one) -> sh.qc.point [module: sh_inventory_mrp_qc]; mrp_id (many2one) -> mrp.production [module: sh_inventory_mrp_qc]; workorder_id (many2one) -> mrp.workorder [module: sh_inventory_mrp_qc]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


Describe the field structure of action.data. or Which fields are required in action.data?

Response: The action.data model has 9 fields. Field types distribution: char: 2, many2one: 3, integer: 1, datetime: 3. Computed fields: 2. Field details: name (char) [module: simplify_access_management]; action_id (many2one) -> ir.actions.actions [module: simplify_access_management]; 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 mrp.workcenter.productivity.loss model. or What are the available fields for mrp.workcenter.productivity.loss?

Response: The mrp.workcenter.productivity.loss model has 12 fields. Field types distribution: char: 2, integer: 2, boolean: 1, many2one: 3, selection: 1, datetime: 3. Computed fields: 3. Field details: name (char) [required] [module: mrp]; sequence (integer) [module: mrp]; manual (boolean) [module: mrp]; loss_id (many2one) -> mrp.workcenter.productivity.loss.type [module: mrp]; loss_type (selection) [compute: <bound method Field._compute_related of mrp.workcenter.productivity.loss.loss_type>] [stored] [module: mrp] [related: loss_id.loss_type] [inverse: <bound method Field._inverse_related of mrp.workcenter.productivity.loss.loss_type>]; 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 columns are nullable in base_module_uninstall? or What columns have default values in base_module_uninstall?

Response: Columns in base_module_uninstall: id (integer) [NOT NULL] [DEFAULT: nextval('base_module_uninstall_id_seq'::regclass)] [PRECISION: 32]; show_all (boolean) [COMMENT: Show All]; module_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Module]; 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: 5 nullable, 1 with defaults, 0 with length constraints.


What fields are readonly in product.sale.details.report? or How to work with product.sale.details.report fields?

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


What foreign keys exist in report.sh_purchase_reports.sh_top_purchasing_product_doc? or What are the relationships in report.sh_purchase_reports.sh_top_purchasing_product_doc?

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


Describe the many2many relations for sh.sale.analysis.wizard. or What are the relationships in sh.sale.analysis.wizard?

Response: The sh.sale.analysis.wizard model has 7 relational fields: sh_product_ids -> product.product; company_ids -> res.company; sh_partner_ids -> res.partner; company_id -> res.company; sale_analysis_dic -> user.order.dic; create_uid -> res.users; write_uid -> res.users. Many2many fields: sh_product_ids, company_ids, sh_partner_ids. One2many fields: sale_analysis_dic.


Show me the foreign key constraints of im_livechat_channel_im_user. or What tables are connected to im_livechat_channel_im_user?

Response: Foreign keys in im_livechat_channel_im_user: channel_id -> im_livechat_channel.id [constraint: im_livechat_channel_im_user_channel_id_fkey]; user_id -> res_users.id [constraint: im_livechat_channel_im_user_user_id_fkey]. Total foreign key relationships: 2. Referenced tables: res_users, im_livechat_channel.


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

Response: Foreign keys in apply_voucher: create_uid -> res_users.id [constraint: apply_voucher_create_uid_fkey]; customer_id -> res_partner.id [constraint: apply_voucher_customer_id_fkey]; write_uid -> res_users.id [constraint: apply_voucher_write_uid_fkey]. Total foreign key relationships: 3. Referenced tables: res_partner, res_users.


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

Response: Columns in pos_cash_in_out: id (integer) [NOT NULL] [DEFAULT: nextval('pos_cash_in_out_id_seq'::regclass)] [PRECISION: 32]; action (character varying) [COMMENT: Action]; product_id (integer) [PRECISION: 32] [COMMENT: Product Service]; amount (numeric) [COMMENT: Amount]; reason (character varying) [COMMENT: Reason]; pos_session_id (integer) [PRECISION: 32] [COMMENT: POS Session]; account_move_id (integer) [PRECISION: 32] [COMMENT: Journal Entry]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 11. Statistics: 10 nullable, 1 with defaults, 0 with length constraints.


List all relational fields in account.tax.report. or What models are connected to account.tax.report?

Response: The account.tax.report model has 7 relational fields: country_id -> res.country; line_ids -> account.tax.report.line; root_line_ids -> account.tax.report.line; company_id -> res.company; branch_id -> res.branch; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: line_ids, root_line_ids.


What one2many fields are in report.equip3_pos_report.report_profit_loss? or Show me the relational structure of report.equip3_pos_report.report_profit_loss.

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


Describe the field structure of purchase.agreement.approval.matrix.lines. or List all fields in the purchase.agreement.approval.matrix.lines model.

Response: The purchase.agreement.approval.matrix.lines model has 20 fields. Field types distribution: integer: 5, many2many: 3, char: 2, datetime: 4, text: 1, boolean: 1, many2one: 4. Computed fields: 4. Field details: sequence (integer) [module: equip3_purchase_other_operation]; user_ids (many2many) [required] -> res.users [module: equip3_purchase_other_operation]; minimum_approver (integer) [required] [module: equip3_purchase_other_operation]; status (char) [module: equip3_purchase_other_operation]; time (datetime) [module: equip3_purchase_other_operation]; feedback (text) [module: equip3_purchase_other_operation]; approved (boolean) [module: equip3_purchase_other_operation]; approval (integer) [module: equip3_purchase_other_operation]; user_approved_ids (many2many) -> res.users [module: equip3_purchase_other_operation]; approval_matrix (many2one) -> purchase.agreement [module: equip3_purchase_other_operation]; sequence2 (integer) [readonly] [compute: <bound method Field._compute_related of purchase.agreement.approval.matrix.lines.sequence2>] [stored] [module: equip3_purchase_other_operation] [related: sequence]; user_ids_domain (many2many) [readonly] -> res.users [compute: _compute_user_domain] [not stored] [module: equip3_purchase_other_operation]; last_approved (many2one) -> res.users [module: equip3_purchase_other_operation]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


What methods are available in mail.blacklist? or What are the technical details of mail.blacklist?

Response: The mail.blacklist model is defined in module: mail. It has 13 computed fields: message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: create, write, _search, _add, action_remove_with_reason, _remove, mail_action_blacklist_remove, action_add, _Attachment, _get_followers, _search_follower_partners, _search_follower_channels, _compute_is_follower, _search_is_follower, _get_message_unread, _get_message_needaction, _search_message_needaction, _compute_message_has_error, _search_message_has_error, _compute_message_attachment_count, unlink, copy_data, get_empty_list_help, _compute_field_value, _creation_subtype, _get_creation_message, _creation_message, get_mail_message_access, _get_mail_message_access, _valid_field_parameter, with_lang, _fallback_lang, message_change_thread, _prepare_tracking, _discard_tracking, _finalize_tracking, _get_tracked_fields, _message_track_post_template, _track_template, message_track, static_message_track, _message_track, _track_subtype, _routing_warn, _routing_create_bounce_email, _routing_handle_bounce, _routing_check_route, _routing_reset_bounce, message_route, _message_route_process, message_process, message_new, message_update, _message_receive_bounce, _message_reset_bounce, _message_parse_extract_payload_postprocess, _message_parse_extract_payload, _message_parse_extract_bounce, message_parse, _message_get_default_recipients_on_records, _message_add_suggested_recipient, _message_get_suggested_recipients, _mail_search_on_user, _mail_search_on_partner, _mail_find_user_for_gateway, _mail_find_partner_from_emails, _message_partner_info_from_emails, _message_post_process_attachments, message_post, _message_set_main_attachment_id, _message_post_after_hook, message_post_with_view, message_post_with_template, message_notify, _message_log, _message_log_batch, _message_compute_author, _message_create, _notify_thread, _notify_record_by_inbox, _notify_record_by_email, _notify_prepare_template_context, _notify_by_email_add_values, _notify_compute_recipients, _notify_encode_link, _notify_get_action_link, _notify_get_groups, _notify_classify_recipients, _notify_get_reply_to_on_records, _notify_email_recipient_values, message_subscribe, _message_subscribe, message_unsubscribe, _message_auto_subscribe_followers, _message_auto_subscribe_notify, _message_auto_subscribe, _get_mail_redirect_suggested_company, _mail_track, _message_get_default_recipients, _notify_get_reply_to, _alias_check_contact, _alias_get_error_message, _get_default_activity_view, _notify_email_headers, _notify_email_header_dict.


How do I use the purchase.tender.create.lines.wizard model? or What business logic is in purchase.tender.create.lines.wizard?

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


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

Response: The hr_departure_wizard table has 10 columns and 3 foreign key relationships. It stores data related to hr departure wizard in the system. The table has 1 indexes for performance optimization. Column types: integer: 4, character varying: 1, text: 1, date: 1, boolean: 1, timestamp without time zone: 2. Nullable columns: 7, columns with defaults: 1.


Describe the many2many relations for restore.lead.type. or How does restore.lead.type relate to other models?

Response: The restore.lead.type model has 3 relational fields: lead_type_id -> crm.lead.type; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


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

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


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

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


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

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


Show me the fields of stock.immediate.transfer. or What field types are used in stock.immediate.transfer?

Response: The stock.immediate.transfer model has 10 fields. Field types distribution: many2many: 1, boolean: 1, one2many: 1, integer: 1, char: 1, many2one: 2, datetime: 3. Computed fields: 2. Field details: pick_ids (many2many) -> stock.picking [module: stock]; show_transfers (boolean) [module: stock]; immediate_transfer_line_ids (one2many) -> stock.immediate.transfer.line [module: stock]; 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 columns are nullable in purchase_order_wizard? or What are the column types in purchase_order_wizard?

Response: Columns in purchase_order_wizard: id (integer) [NOT NULL] [DEFAULT: nextval('purchase_order_wizard_id_seq'::regclass)] [PRECISION: 32]; sh_group_by_partner (boolean) [COMMENT: Group By]; sh_cancel_old_rfqs (character varying) [COMMENT: Cancel Old RFQ'S]; sh_create_po (character varying) [COMMENT: Create RFQ/Purchase Order]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]; partner_id (integer) [PRECISION: 32] [COMMENT: Vendor]; date_planned (timestamp without time zone) [COMMENT: Scheduled Date]; order_selection (character varying) [COMMENT: Order Selection]; so_id (integer) [PRECISION: 32] [COMMENT: Source Document]; is_dropship (boolean) [COMMENT: Is Dropship]. Total columns: 13. Statistics: 12 nullable, 1 with defaults, 0 with length constraints.


What fields does mail.bot have? or What computed fields exist in mail.bot?

Response: The mail.bot 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 is the overhead_time table? or What indexes exist on overhead_time?

Response: The overhead_time table has 8 columns and 4 foreign key relationships. It stores data related to overhead time in the system. The table has 1 indexes for performance optimization. Column types: integer: 5, double precision: 1, timestamp without time zone: 2. Nullable columns: 7, columns with defaults: 1.


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

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


What one2many fields are in queue.job.channel? or Describe the many2many relations for queue.job.channel.

Response: The queue.job.channel model has 4 relational fields: parent_id -> queue.job.channel; job_function_ids -> queue.job.function; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: job_function_ids.


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

Response: Foreign keys in account_analytic_tag_account_asset_asset_rel: account_analytic_tag_id -> account_analytic_tag.id [constraint: account_analytic_tag_account_asse_account_analytic_tag_id_fkey1]; account_asset_asset_id -> account_asset_asset.id [constraint: account_analytic_tag_account_asset__account_asset_asset_id_fkey]. Total foreign key relationships: 2. Referenced tables: account_asset_asset, account_analytic_tag.


What are the relationships in pos.order.line.promotion? or List all relational fields in pos.order.line.promotion.

Response: The pos.order.line.promotion model has 4 relational fields: pos_order_line_id -> pos.order.line; promotion_id -> pos.promotion; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


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

Response: The opening_balance_line table has 11 columns and 5 foreign key relationships. It stores data related to opening balance line in the system. The table has 1 indexes for performance optimization. Column types: integer: 6, numeric: 2, date: 1, timestamp without time zone: 2. Nullable columns: 10, columns with defaults: 1.


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

Response: Foreign keys in account_resequence_wizard: create_uid -> res_users.id [constraint: account_resequence_wizard_create_uid_fkey]; write_uid -> res_users.id [constraint: account_resequence_wizard_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


Describe the implementation of target.activity.line. or What methods are defined in target.activity.line original module?

Response: The target.activity.line model is defined in module: equip3_crm_operation. It has 5 computed fields: user_id, achieved_target, remaining_target, display_name, __last_update. Stored computed fields: none. Related fields: user_id -> activity_id.user_id. Original module methods: _compute_target, create.


What are the technical details of analytic.sale.order.line? or Which fields in analytic.sale.order.line are computed?

Response: The analytic.sale.order.line model is defined in module: contract_recurring_invoice_analytic. It has 7 computed fields: name, product_uom, price_subtotal, price_tax, price_total, display_name, __last_update. Stored computed fields: name, price_subtotal, price_tax, price_total. Related fields: product_uom -> product_id.uom_id. Original module methods: _compute_product_name, _compute_amount.


How is res.country.state implemented technically? or Describe the implementation of res.country.state.

Response: The res.country.state model is defined in module: base. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: _name_search, name_get, create.


List all relational fields in receipt.voucher. or How does receipt.voucher relate to other models?

Response: The receipt.voucher model has 22 relational fields: create_by -> res.users; payment_ids -> account.payment; partner_id -> res.partner; partner_ids -> res.partner; bank_id -> account.journal; customer_invoice_ids -> account.move; currency_id -> res.currency; company_id -> res.company; branch_id -> res.branch; receipt_voucher_line_ids -> receipt.voucher.line; customer_allowed_ids -> account.move; 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: partner_ids, customer_invoice_ids, customer_allowed_ids, message_partner_ids, message_channel_ids. One2many fields: payment_ids, receipt_voucher_line_ids, activity_ids, message_follower_ids, message_ids, website_message_ids.


What fields are readonly in account.partner.ageing? or How do I use the account.partner.ageing model?

Response: To use the account.partner.ageing model, you need to provide values for required fields: period_length, result_selection, journal_ids, target_move, company_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: period_length [required] [has_default]; result_selection [required] [has_default]; journal_ids [required] [has_default]; target_move [required] [has_default]; company_id [required] [has_default]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


How to work with overhead.time fields? or What operations can I perform on overhead.time?

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


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

Response: Columns in do_approval_matrix_detail: id (integer) [NOT NULL] [DEFAULT: nextval('do_approval_matrix_detail_id_seq'::regclass)] [PRECISION: 32]; usage (character varying) [COMMENT: Location Type]; company_id (integer) [PRECISION: 32] [COMMENT: Company]; do_approval_matrix_id2 (integer) [PRECISION: 32] [COMMENT: Do Approval Matrix Id2]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 8. Statistics: 7 nullable, 1 with defaults, 0 with length constraints.


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

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


What data can be stored in new.customer? or What field types are used in new.customer?

Response: The new.customer model has 9 fields. Field types distribution: char: 2, many2one: 3, integer: 1, datetime: 3. Computed fields: 2. Field details: name (char) [module: equip3_sale_report]; top_id (many2one) -> sh.tc.top.customer.wizard [module: equip3_sale_report]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


Explain the wizard_report_menu_create table schema. or What is stored in wizard_report_menu_create?

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


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

Response: Foreign keys in product_product_warranty_claim_rel: product_product_id -> product_product.id [constraint: product_product_warranty_claim_rel_product_product_id_fkey]; warranty_claim_id -> warranty_claim.id [constraint: product_product_warranty_claim_rel_warranty_claim_id_fkey]. Total foreign key relationships: 2. Referenced tables: product_product, warranty_claim.


What business logic is in sales.margin.xls? or How to query sales.margin.xls data?

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


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

Response: Foreign keys in website_robots: create_uid -> res_users.id [constraint: website_robots_create_uid_fkey]; write_uid -> res_users.id [constraint: website_robots_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


Describe the columns of tax_sale_details_report. or What are the length constraints in tax_sale_details_report?

Response: Columns in tax_sale_details_report: id (integer) [NOT NULL] [DEFAULT: nextval('tax_sale_details_report_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [COMMENT: Name]; total (double precision) [PRECISION: 53] [COMMENT: Total]; details_id (integer) [PRECISION: 32] [COMMENT: Details]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 8. Statistics: 7 nullable, 1 with defaults, 0 with length constraints.


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

Response: Columns in rn_approval_matrix_line: id (integer) [NOT NULL] [DEFAULT: nextval('rn_approval_matrix_line_id_seq'::regclass)] [PRECISION: 32]; sequence (integer) [PRECISION: 32] [COMMENT: Sequence]; sequence1 (integer) [PRECISION: 32] [COMMENT: No.]; minimal_approver (integer) [PRECISION: 32] [COMMENT: Minimum Approver]; approval_status (text) [COMMENT: Approval Status]; feedback (character varying) [COMMENT: Feedback]; time_stamp (timestamp without time zone) [COMMENT: TimeStamp]; last_approved (integer) [PRECISION: 32] [COMMENT: Users]; approved (boolean) [COMMENT: Approved]; rn_approval_matrix_id1 (integer) [PRECISION: 32] [COMMENT: Rn Approval Matrix Id1]; picking_id (integer) [PRECISION: 32] [COMMENT: picking]; state (text) [COMMENT: State]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 16. Statistics: 15 nullable, 1 with defaults, 0 with length constraints.


What are the available fields for gamification.karma.rank? or Show me the fields of gamification.karma.rank.

Response: The gamification.karma.rank model has 18 fields. Field types distribution: text: 1, html: 2, integer: 3, one2many: 1, binary: 5, char: 1, many2one: 2, datetime: 3. Computed fields: 7. Field details: name (text) [required] [module: gamification]; description (html) [module: gamification]; description_motivational (html) [module: gamification]; karma_min (integer) [required] [module: gamification]; user_ids (one2many) -> res.users [module: gamification]; rank_users_count (integer) [readonly] [compute: _compute_rank_users_count] [not stored] [module: gamification]; image_1920 (binary) [module: base]; image_1024 (binary) [readonly] [compute: <bound method Field._compute_related of gamification.karma.rank.image_1024>] [stored] [module: base] [related: image_1920]; image_512 (binary) [readonly] [compute: <bound method Field._compute_related of gamification.karma.rank.image_512>] [stored] [module: base] [related: image_1920]; image_256 (binary) [readonly] [compute: <bound method Field._compute_related of gamification.karma.rank.image_256>] [stored] [module: base] [related: image_1920]; image_128 (binary) [readonly] [compute: <bound method Field._compute_related of gamification.karma.rank.image_128>] [stored] [module: base] [related: image_1920]; 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 res_groups_kpi_item_edit_rel_table. or What fields are available in res_groups_kpi_item_edit_rel_table?

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


Show me the relational structure of auditlog.http.request. or Describe the many2many relations for auditlog.http.request.

Response: The auditlog.http.request model has 5 relational fields: user_id -> res.users; http_session_id -> auditlog.http.session; log_ids -> auditlog.log; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: log_ids.


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

Response: Foreign keys in sh_custom_model_tab: create_uid -> res_users.id [constraint: sh_custom_model_tab_create_uid_fkey]; parent_view_id -> ir_ui_view.id [constraint: sh_custom_model_tab_parent_view_id_fkey]; view_id -> ir_ui_view.id [constraint: sh_custom_model_tab_view_id_fkey]; write_uid -> res_users.id [constraint: sh_custom_model_tab_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: ir_ui_view, res_users.


How to query payment.voucher data? or How to create records in payment.voucher?

Response: To use the payment.voucher model, you need to provide values for required fields: name, partner_ids, bank_id, vendor_bill_ids, company_id, currency_id. Readonly fields: amount, payment_count, approval_matrix_id, is_payment_voucher_approval_matrix, approval_matrix_line_id, is_approve_button, state1, state2, amount_to_text, vendor_allowed_ids, is_cutoff_date, 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 [required] [has_default]; partner_ids [required]; bank_id [required]; vendor_bill_ids [required]; company_id [required] [has_default]; currency_id [required] [has_default]; amount [readonly] [computed] [no_copy]; payment_count [readonly] [computed] [no_copy]; approval_matrix_id [readonly] [computed] [no_copy]; is_payment_voucher_approval_matrix [readonly] [computed] [no_copy]; approval_matrix_line_id [readonly] [computed] [no_copy]; is_approve_button [readonly] [computed] [no_copy]; state1 [readonly] [computed] [no_copy]; state2 [readonly] [computed] [no_copy]; amount_to_text [readonly] [computed] [no_copy]; vendor_allowed_ids [readonly] [computed] [no_copy]; is_cutoff_date [readonly] [computed] [no_copy]; activity_state [readonly] [computed] [no_copy]; activity_user_id [computed] [no_copy]; activity_type_id [computed] [no_copy]; activity_type_icon [readonly] [computed] [no_copy]; activity_date_deadline [readonly] [computed] [no_copy]; my_activity_date_deadline [readonly] [computed] [no_copy]; activity_summary [computed] [no_copy]; activity_exception_decoration [readonly] [computed] [no_copy]; activity_exception_icon [readonly] [computed] [no_copy]; message_is_follower [readonly] [computed] [no_copy]; message_partner_ids [readonly] [computed] [no_copy]; message_channel_ids [readonly] [computed] [no_copy]; message_unread [readonly] [computed] [no_copy]; message_unread_counter [readonly] [computed] [no_copy]; message_needaction [readonly] [computed] [no_copy]; message_needaction_counter [readonly] [computed] [no_copy]; message_has_error [readonly] [computed] [no_copy]; message_has_error_counter [readonly] [computed] [no_copy]; message_attachment_count [readonly] [computed] [no_copy]; message_has_sms_error [readonly] [computed] [no_copy]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


What foreign keys exist in purchase.requisition.type? or What models are connected to purchase.requisition.type?

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


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

Response: Foreign keys in purchase_detail_excel_extended: create_uid -> res_users.id [constraint: purchase_detail_excel_extended_create_uid_fkey]; write_uid -> res_users.id [constraint: purchase_detail_excel_extended_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


List all fields in the pos.loyalty.rule model. or What field types are used in pos.loyalty.rule?

Response: The pos.loyalty.rule model has 25 fields. Field types distribution: integer: 3, char: 3, boolean: 4, many2one: 3, many2many: 3, float: 2, selection: 3, text: 1, datetime: 3. Computed fields: 4. Field details: sequence (integer) [module: equip3_pos_membership]; name (char) [required] [module: equip3_pos_membership]; active (boolean) [module: equip3_pos_membership]; loyalty_id (many2one) [required] -> pos.loyalty [module: equip3_pos_membership]; pos_loyalty_category_ids (many2many) -> pos.loyalty.category [module: equip3_pos_membership]; coefficient (float) [required] [module: equip3_pos_membership]; type (selection) [required] [module: equip3_pos_membership]; product_ids (many2many) -> product.product [module: equip3_pos_membership]; category_ids (many2many) -> pos.category [module: equip3_pos_membership]; categories (char) [readonly] [compute: _compute_categories] [not stored] [module: equip3_pos_membership]; min_amount (float) [required] [module: equip3_pos_membership]; coefficient_note (text) [readonly] [compute: _get_coefficient_note] [not stored] [module: equip3_pos_membership]; is_multi (boolean) [module: equip3_pos_membership]; calc_point_without_point_as_payment (boolean) [module: equip3_pos_membership]; state (selection) [module: equip3_pos_membership]; is_expired_period (boolean) [module: equip3_pos_membership]; expired_period (selection) [module: equip3_pos_membership]; expired_period_value (integer) [module: equip3_pos_membership]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


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

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


What methods are defined in stock.move.line original module? or What are the technical details of stock.move.line?

Response: The stock.move.line model is defined in module: stock. It has 23 computed fields: product_uom_category_id, product_qty, lots_visible, picking_code, picking_type_use_create_lots, picking_type_use_existing_lots, state, is_initial_demand_editable, is_locked, reference, tracking, origin, picking_type_entire_packs, is_double_product_usage, sale_price, product_type, quant_package_ids, source_picking_id, is_batch_shipping_packing, is_batch_shipping_delivery, description, display_name, __last_update. Stored computed fields: product_qty, state, reference. Related fields: product_uom_category_id -> product_id.uom_id.category_id, picking_code -> picking_id.picking_type_id.code, picking_type_use_create_lots -> picking_id.picking_type_id.use_create_lots, picking_type_use_existing_lots -> picking_id.picking_type_id.use_existing_lots, state -> move_id.state, is_initial_demand_editable -> move_id.is_initial_demand_editable, is_locked -> move_id.is_locked, reference -> move_id.reference, tracking -> product_id.tracking, origin -> move_id.origin, picking_type_entire_packs -> picking_id.picking_type_id.show_entire_packs, product_type -> product_id.type, source_picking_id -> move_id.source_picking_id, is_batch_shipping_packing -> move_id.is_batch_shipping_packing, is_batch_shipping_delivery -> move_id.is_batch_shipping_delivery, description -> product_id.display_name. Original module methods: _compute_lots_visible, _compute_product_qty, _set_product_qty, _check_lot_product, _check_reserved_done_quantity, _check_positive_qty_done, _onchange_product_id, _onchange_serial_number, _onchange_qty_done, init, create, write, unlink, _action_done, _get_similar_move_lines, _create_and_assign_production_lot, _assign_production_lot, _reservation_is_updatable, _log_message, _free_reservation, _should_bypass_reservation, _get_aggregated_product_quantities.


Can you explain the purpose of purchase.agreement.approval.matrix? or How is purchase.agreement.approval.matrix used in the system?

Response: The purchase.agreement.approval.matrix model represents Approval Matrix Purchase Agreement in the ERP system. It contains 46 fields and is used to manage approval matrix purchase agreement data. Defined in module: equip3_purchase_other_operation. Key fields include: name, company_id, branch_id, minimum_amt, maximum_amt, approval_matrix_purchase_agreement_line_ids, is_good_services_order, order_type, campaign_id, source_id, medium_id, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, access_url, access_token, access_warning, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What operations can I perform on create.purchase.request.direct.lines? or How to create records in create.purchase.request.direct.lines?

Response: To use the create.purchase.request.direct.lines model, you need to provide values for required fields: wiz_id, name, product_uom_id. Readonly fields: wiz_id, rem_qty, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: wiz_id [required] [readonly]; request_id [computed] [no_copy]; product_id [computed] [no_copy]; name [required]; product_uom_id [required]; rem_qty [readonly] [computed] [has_default] [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 columns are nullable in limit_request_wizard? or Show me the column structure of limit_request_wizard.

Response: Columns in limit_request_wizard: id (integer) [NOT NULL] [DEFAULT: nextval('limit_request_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 fields in the report.accounting_pdf_reports.report_general_ledger model. or What computed fields exist in report.accounting_pdf_reports.report_general_ledger?

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


How is calendar.attendee used in the system? or Can you explain the purpose of calendar.attendee?

Response: The calendar.attendee model represents Calendar Attendee Information in the ERP system. It contains 15 fields and is used to manage calendar attendee information data. Defined in module: calendar. Key fields include: event_id, partner_id, state, common_name, email, availability, access_token, recurrence_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Describe the many2many relations for crm.phonecall. or What are the relationships in crm.phonecall?

Response: The crm.phonecall model has 17 relational fields: team_id -> crm.team; user_id -> res.users; partner_id -> res.partner; company_id -> res.company; tag_ids -> crm.tag; opportunity_id -> crm.lead; campaign_id -> utm.campaign; source_id -> utm.source; medium_id -> utm.medium; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: tag_ids, message_partner_ids, message_channel_ids. One2many fields: message_follower_ids, message_ids, website_message_ids.


How is sale.order implemented technically? or Describe the implementation of sale.order.

Response: The sale.order model is defined in module: sale. It has 130 computed fields: is_expired, currency_id, invoice_count, invoice_ids, invoice_status, amount_by_group, currency_rate, amount_undiscounted, type_name, authorized_transaction_ids, reward_amount, promo_code, purchase_order_count, delivery_count, effective_date, expected_date, json_popover, show_json_popover, website_order_line, cart_quantity, only_services, is_abandoned_cart, inter_transfer_count, discount_amt, discount_amt_line, warranty_sale, delivery_set, is_all_service, order_revised_count, margin, margin_percent, mrp_production_count, tasks_ids, tasks_count, visible_project, project_ids, sh_purchase_count, sh_so_po_is_show_so_to_po_btn_flag, company_currency_id, report_template_id1, amount_to_text, timesheet_ids, timesheet_count, timesheet_encode_uom_id, timesheet_total_duration, amount_delivery, order_line_count, sale_state_1, state_2, revised_state, approval_matrix_state, approval_matrix_state_1, approving_matrix_sale_id, is_customer_approval_matrix, hide_proforma, is_approval_matrix_filled, is_approve_button, approval_matrix_line_id, analytic_accounting, group_multi_do, is_print_report, qty_delivered, count_delivered, multilevel_disc, is_sale_order, partner_name, is_hidden_button, lock_sale_order, sale_hidden_compute_field, date_kanban, down_payment_amount, total_amount_without_dp, amount_untaxed, amount_tax, amount_total, city_id, state_id, show_mobile, amount_subtotal, approved_matrix_limit_ids, is_over_limit_validation, is_limit_matrix_filled, limit_approval_matrix_line_id, is_approve_button_limit, limit_matrix_state, limit_matrix_state_1, limit_matrix_state_2, sale_limit_state, sale_limit_state_1, sale_limit_state_2, sale_limit_state_3, sale_limit_state_4, sale_limit_state_5, approval_matrix_state_2, approval_matrix_state_3, approval_matrix_state_4, approval_matrix_state_5, approval_matrix_state_6, approval_matrix_state_7, approval_matrix_state_8, approval_matrix_state_9, creditlim, hide_button_revise, have_available_customer_voucher, cn_cashback_count, purchase_request_count, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, access_url, access_warning, display_name, __last_update. Stored computed fields: currency_id, invoice_status, currency_rate, effective_date, inter_transfer_count, discount_amt, discount_amt_line, margin, margin_percent, amount_delivery, order_line_count, approving_matrix_sale_id, analytic_accounting, partner_name, down_payment_amount, total_amount_without_dp, amount_untaxed, amount_tax, amount_total, city_id, state_id, amount_subtotal, approved_matrix_limit_ids, hide_button_revise. Related fields: currency_id -> pricelist_id.currency_id, promo_code -> code_promo_program_id.promo_code, company_currency_id -> company_id.currency_id, timesheet_encode_uom_id -> company_id.timesheet_encode_uom_id, sale_state_1 -> sale_state, state_2 -> state, revised_state -> state, approval_matrix_state -> state, approval_matrix_state_1 -> state, partner_name -> partner_id.name, city_id -> partner_id.res_city_id, state_id -> partner_id.state_id, limit_matrix_state -> state, limit_matrix_state_1 -> state, limit_matrix_state_2 -> state, sale_limit_state -> state, sale_limit_state_1 -> state, sale_limit_state_2 -> state, sale_limit_state_3 -> state, sale_limit_state_4 -> state, sale_limit_state_5 -> state, approval_matrix_state_2 -> state, approval_matrix_state_3 -> state, approval_matrix_state_4 -> state, approval_matrix_state_5 -> state, approval_matrix_state_6 -> state, approval_matrix_state_7 -> state, approval_matrix_state_8 -> state, approval_matrix_state_9 -> state, creditlim -> partner_id.customer_credit, 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_validity_date, _get_default_require_signature, _get_default_require_payment, _amount_all, _get_invoiced, _get_invoice_status, get_empty_list_help, _default_note, _get_default_team, _compute_tax_id, _search_invoice_ids, _check_order_line_company_id, _compute_currency_rate, _compute_access_url, _compute_is_expired, _compute_expected_date, _onchange_commitment_date, _compute_authorized_transaction_ids, _compute_amount_undiscounted, _compute_type_name, unlink, validate_taxes_on_sales_order, _track_subtype, onchange_partner_shipping_id, onchange_partner_id, onchange_user_id, onchange_partner_id_warning, _onchange_pricelist_id, update_prices, create, _compute_field_value, copy_data, name_get, _name_search, _prepare_invoice, action_quotation_sent, action_view_invoice, _get_invoice_grouping_keys, _nothing_to_invoice_error, _get_invoiceable_lines, _create_invoices, action_draft, action_cancel, _show_cancel_wizard, _find_mail_template, action_quotation_send, message_post, _sms_get_number_fields, _sms_get_partner_fields, _send_order_confirmation_mail, action_done, action_unlock, _action_confirm, _prepare_confirmation_values, action_confirm, _get_forbidden_state_confirm, _prepare_analytic_account_data, _create_analytic_account, _amount_by_group, has_to_be_signed, has_to_be_paid, _notify_get_groups, _create_payment_transaction, preview_sale_order, _force_lines_to_invoice_policy_order, payment_action_capture, payment_action_void, get_portal_last_transaction, _get_customer_lead, _get_report_base_filename, _get_payment_type, _get_portal_return_action, _prepare_down_payment_section_line, add_option_to_order_with_taxcloud.


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

Response: Columns in salesperson_tracking_history: id (integer) [NOT NULL] [DEFAULT: nextval('salesperson_tracking_history_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [COMMENT: Name]; history_data (text) [COMMENT: History Data]; tracking_history_id (integer) [PRECISION: 32] [COMMENT: Salesperson Tracking History ref]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 8. Statistics: 7 nullable, 1 with defaults, 0 with length constraints.


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

Response: The account_bank_statement_integrate table has 13 columns and 4 foreign key relationships. It stores data related to account bank statement integrate in the system. The table has 1 indexes for performance optimization. Column types: integer: 5, character varying: 3, date: 3, timestamp without time zone: 2. Nullable columns: 9, columns with defaults: 1.


Which fields are required in mrp.workorder? or What computed fields exist in mrp.workorder?

Response: The mrp.workorder model has 71 fields. Field types distribution: char: 4, many2one: 14, selection: 7, boolean: 9, float: 8, datetime: 8, integer: 5, binary: 1, text: 1, one2many: 13, many2many: 1. Computed fields: 41. Field details: name (char) [required] [module: mrp]; workcenter_id (many2one) [required] -> mrp.workcenter [module: mrp]; working_state (selection) [compute: <bound method Field._compute_related of mrp.workorder.working_state>] [not stored] [module: mrp] [related: workcenter_id.working_state]; product_id (many2one) [readonly] -> product.product [compute: <bound method Field._compute_related of mrp.workorder.product_id>] [stored] [module: mrp] [related: production_id.product_id]; product_tracking (selection) [readonly] [compute: <bound method Field._compute_related of mrp.workorder.product_tracking>] [not stored] [module: mrp] [related: product_id.tracking]; product_uom_id (many2one) [required] [readonly] -> uom.uom [module: mrp]; use_create_components_lots (boolean) [readonly] [compute: <bound method Field._compute_related of mrp.workorder.use_create_components_lots>] [not stored] [module: mrp] [related: production_id.picking_type_id.use_create_components_lots]; production_id (many2one) [required] [readonly] -> mrp.production [module: mrp]; production_availability (selection) [readonly] [compute: <bound method Field._compute_related of mrp.workorder.production_availability>] [stored] [module: mrp] [related: production_id.reservation_state]; production_state (selection) [readonly] [compute: <bound method Field._compute_related of mrp.workorder.production_state>] [not stored] [module: mrp] [related: production_id.state]; production_bom_id (many2one) [readonly] -> mrp.bom [compute: <bound method Field._compute_related of mrp.workorder.production_bom_id>] [not stored] [module: mrp] [related: production_id.bom_id]; qty_production (float) [readonly] [compute: <bound method Field._compute_related of mrp.workorder.qty_production>] [not stored] [module: mrp] [related: production_id.product_qty]; company_id (many2one) [readonly] -> res.company [compute: <bound method Field._compute_related of mrp.workorder.company_id>] [not stored] [module: mrp] [related: production_id.company_id]; qty_producing (float) [compute: _compute_qty_producing] [not stored] [module: mrp] [inverse: _set_qty_producing]; qty_remaining (float) [readonly] [compute: _compute_qty_remaining] [not stored] [module: mrp]; qty_produced (float) [readonly] [module: mrp]; is_produced (boolean) [readonly] [compute: _compute_is_produced] [not stored] [module: mrp]; state (selection) [readonly] [module: mrp]; leave_id (many2one) -> resource.calendar.leaves [module: mrp]; date_planned_start (datetime) [compute: _compute_dates_planned] [stored] [module: mrp] [inverse: _set_dates_planned]; date_planned_finished (datetime) [compute: _compute_dates_planned] [stored] [module: mrp] [inverse: _set_dates_planned]; date_start (datetime) [module: mrp]; date_finished (datetime) [module: mrp]; duration_expected (float) [module: mrp]; duration (float) [compute: _compute_duration] [stored] [module: mrp] [inverse: _set_duration]; duration_unit (float) [readonly] [compute: _compute_duration] [stored] [module: mrp]; duration_percent (integer) [readonly] [compute: _compute_duration] [stored] [module: mrp]; progress (float) [readonly] [compute: _compute_progress] [not stored] [module: mrp]; operation_id (many2one) -> mrp.routing.workcenter [module: mrp]; worksheet (binary) [readonly] [compute: <bound method Field._compute_related of mrp.workorder.worksheet>] [not stored] [module: mrp] [related: operation_id.worksheet]; worksheet_type (selection) [readonly] [compute: <bound method Field._compute_related of mrp.workorder.worksheet_type>] [not stored] [module: mrp] [related: operation_id.worksheet_type]; worksheet_google_slide (char) [readonly] [compute: <bound method Field._compute_related of mrp.workorder.worksheet_google_slide>] [not stored] [module: mrp] [related: operation_id.worksheet_google_slide]; operation_note (text) [readonly] [compute: <bound method Field._compute_related of mrp.workorder.operation_note>] [not stored] [module: mrp] [related: operation_id.note]; move_raw_ids (one2many) -> stock.move [module: mrp]; move_finished_ids (one2many) -> stock.move [module: mrp]; move_line_ids (one2many) -> stock.move.line [module: mrp]; finished_lot_id (many2one) -> stock.production.lot [compute: _compute_finished_lot_id] [not stored] [module: mrp] [inverse: _set_finished_lot_id]; time_ids (one2many) -> mrp.workcenter.productivity [module: mrp]; is_user_working (boolean) [readonly] [compute: _compute_working_users] [not stored] [module: mrp]; working_user_ids (one2many) [readonly] -> res.users [compute: _compute_working_users] [not stored] [module: mrp]; last_working_user_id (one2many) [readonly] -> res.users [compute: _compute_working_users] [not stored] [module: mrp]; next_work_order_id (many2one) -> mrp.workorder [module: mrp]; scrap_ids (one2many) -> stock.scrap [module: mrp]; scrap_count (integer) [readonly] [compute: _compute_scrap_move_count] [not stored] [module: mrp]; production_date (datetime) [compute: <bound method Field._compute_related of mrp.workorder.production_date>] [stored] [module: mrp] [related: production_id.date_planned_start] [inverse: <bound method Field._inverse_related of mrp.workorder.production_date>]; json_popover (char) [readonly] [compute: _compute_json_popover] [not stored] [module: mrp]; show_json_popover (boolean) [readonly] [compute: _compute_json_popover] [not stored] [module: mrp]; consumption (selection) [required] [module: mrp]; sh_mrp_workorder_quality_check_ids (one2many) -> sh.mrp.quality.check [module: sh_inventory_mrp_qc]; sh_mrp_workorder_quality_alert_ids (one2many) -> sh.mrp.quality.alert [module: sh_inventory_mrp_qc]; sh_mrp_workorder_pass_fail_ids (one2many) -> sh.mrp.pass.fail [module: sh_inventory_mrp_qc]; sh_mrp_workorder_pics_ids (one2many) -> sh.mrp.pics [module: sh_inventory_mrp_qc]; sh_mrp_workorder_measurement_ids (one2many) -> sh.mrp.measurement [module: sh_inventory_mrp_qc]; sh_mrp_workorder_qc_measurement_ids (one2many) -> sh.mrp.qc.measurement [module: sh_inventory_mrp_qc]; qc_count (integer) [readonly] [compute: _compute_get_qc_count] [not stored] [module: sh_inventory_mrp_qc]; qc_alert_count (integer) [readonly] [compute: _compute_get_qc_alert_count] [not stored] [module: sh_inventory_mrp_qc]; sh_workorder_quality_point_id (many2one) [readonly] -> sh.qc.point [compute: <bound method Field._compute_related of mrp.workorder.sh_workorder_quality_point_id>] [not stored] [module: sh_inventory_mrp_qc] [related: production_id.sh_mrp_quality_point_id]; need_qc (boolean) [readonly] [compute: <bound method Field._compute_related of mrp.workorder.need_qc>] [stored] [module: sh_inventory_mrp_qc] [related: production_id.need_qc]; pending_qc (boolean) [readonly] [compute: _compute_check_qc] [not stored] [module: sh_inventory_mrp_qc]; qc_fail (boolean) [readonly] [compute: _compute_check_qc] [not stored] [module: sh_inventory_mrp_qc]; qc_pass (boolean) [readonly] [compute: _compute_check_qc] [not stored] [module: sh_inventory_mrp_qc]; attachment_ids (many2many) -> ir.attachment [module: sh_inventory_mrp_qc]; partner_id (many2one) [readonly] -> res.partner [compute: <bound method Field._compute_related of mrp.workorder.partner_id>] [not stored] [module: sh_inventory_mrp_qc] [related: production_id.partner_id]; is_mandatory (boolean) [readonly] [compute: _compute_check_qc_mandatory] [not stored] [module: sh_inventory_mrp_qc]; 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].


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

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


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

Response: Foreign keys in allow_pos_categories_out_of_stock: pos_category_id -> pos_category.id [constraint: allow_pos_categories_out_of_stock_pos_category_id_fkey]; pos_config_id -> pos_config.id [constraint: allow_pos_categories_out_of_stock_pos_config_id_fkey]. Total foreign key relationships: 2. Referenced tables: pos_config, pos_category.


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

Response: Foreign keys in ir_mail_server: create_uid -> res_users.id [constraint: ir_mail_server_create_uid_fkey]; write_uid -> res_users.id [constraint: ir_mail_server_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


What foreign keys exist in apply.voucher? or How does apply.voucher relate to other models?

Response: The apply.voucher model has 4 relational fields: customer_id -> res.partner; voucher_ids -> customer.voucher; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: voucher_ids.


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

Response: Columns in digest_tip: id (integer) [NOT NULL] [DEFAULT: nextval('digest_tip_id_seq'::regclass)] [PRECISION: 32]; sequence (integer) [PRECISION: 32] [COMMENT: Sequence]; name (character varying) [COMMENT: Name]; tip_description (text) [COMMENT: Tip description]; group_id (integer) [PRECISION: 32] [COMMENT: Authorized Group]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 9. Statistics: 8 nullable, 1 with defaults, 0 with length constraints.


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

Response: The mail.template model has 10 relational fields: model_id -> ir.model; attachment_ids -> ir.attachment; report_template -> ir.actions.report; mail_server_id -> ir.mail_server; ref_ir_act_window -> ir.actions.act_window; model_object_field -> ir.model.fields; sub_object -> ir.model; sub_model_object_field -> ir.model.fields; create_uid -> res.users; write_uid -> res.users. Many2many fields: attachment_ids. One2many fields: none.