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

Response: Foreign keys in pos_config_settings: company_id -> res_company.id [constraint: pos_config_settings_company_id_fkey]; create_uid -> res_users.id [constraint: pos_config_settings_create_uid_fkey]; write_uid -> res_users.id [constraint: pos_config_settings_write_uid_fkey]. Total foreign key relationships: 3. Referenced tables: res_users, res_company.


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

Response: Foreign keys in res_company_sh_purchase_report_representative_wizard_rel: sh_purchase_report_representative_wizard_id -> sh_purchase_report_representative_wizard.id [constraint: res_company_sh_purchase_repor_sh_purchase_report_represent_fkey]; res_company_id -> res_company.id [constraint: res_company_sh_purchase_report_representati_res_company_id_fkey]. Total foreign key relationships: 2. Referenced tables: sh_purchase_report_representative_wizard, res_company.


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

Response: Foreign keys in account_cashbox_line: cashbox_id -> account_bank_statement_cashbox.id [constraint: account_cashbox_line_cashbox_id_fkey]; create_uid -> res_users.id [constraint: account_cashbox_line_create_uid_fkey]; pos_config_id -> pos_config.id [constraint: account_cashbox_line_pos_config_id_fkey]; pos_session_id -> pos_session.id [constraint: account_cashbox_line_pos_session_id_fkey]; write_uid -> res_users.id [constraint: account_cashbox_line_write_uid_fkey]. Total foreign key relationships: 5. Referenced tables: account_bank_statement_cashbox, pos_config, pos_session, res_users.


How do I use the access.group model? or How to work with access.group fields?

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


What is the module hierarchy for receivable.flow.wizard? or What methods are defined in receivable.flow.wizard original module?

Response: The receivable.flow.wizard model is defined in module: equip3_accounting_flow. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: button_customers, button_invoice, button_receipt, button_partner_ageing, button_customer_statement, button_currency_receivable, button_credit_note, button_customer_multi, button_other_income, button_receipt_giro, button_revaluation, button_ibt, button_recurring_invoice, button_customer_topay, button_customer_deposit.


What data can be stored in bo.approval.matrix.sale.reject? or Show me the fields of bo.approval.matrix.sale.reject.

Response: The bo.approval.matrix.sale.reject model has 8 fields. Field types distribution: text: 1, integer: 1, char: 1, many2one: 2, datetime: 3. Computed fields: 2. Field details: reason (text) [module: equip3_sale_other_operation_cont]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


What are the technical details of report.equip3_accounting_reports.customer_statement? or What methods are available in report.equip3_accounting_reports.customer_statement?

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


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

Response: Foreign keys in snailmail_letter: attachment_id -> ir_attachment.id [constraint: snailmail_letter_attachment_id_fkey]; company_id -> res_company.id [constraint: snailmail_letter_company_id_fkey]; country_id -> res_country.id [constraint: snailmail_letter_country_id_fkey]; create_uid -> res_users.id [constraint: snailmail_letter_create_uid_fkey]; message_id -> mail_message.id [constraint: snailmail_letter_message_id_fkey]; partner_id -> res_partner.id [constraint: snailmail_letter_partner_id_fkey]; report_template -> ir_act_report_xml.id [constraint: snailmail_letter_report_template_fkey]; state_id -> res_country_state.id [constraint: snailmail_letter_state_id_fkey]; user_id -> res_users.id [constraint: snailmail_letter_user_id_fkey]; write_uid -> res_users.id [constraint: snailmail_letter_write_uid_fkey]. Total foreign key relationships: 10. Referenced tables: res_country, res_partner, ir_act_report_xml, res_company, mail_message, res_country_state, ir_attachment, res_users.


What foreign keys exist in sh.purchase.details.report.wizard? or List all relational fields in sh.purchase.details.report.wizard.

Response: The sh.purchase.details.report.wizard model has 4 relational fields: company_ids -> res.company; branch_ids -> res.branch; create_uid -> res.users; write_uid -> res.users. Many2many fields: company_ids, branch_ids. One2many fields: none.


How is account.tax.map.sales.line used in the system? or What is the account.tax.map.sales.line model?

Response: The account.tax.map.sales.line model represents Account Tax Map Sales Line in the ERP system. It contains 17 fields and is used to manage account tax map sales line data. Defined in module: equip3_accounting_masterdata. Key fields include: company_id, sales_tax_id, target_company, target_sales_tax, map_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, line_ids, child_company_id, ownership, sales_line_ids, purchase_line_ids.


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

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


List all constraint names in mrp_consumption_warning. or How does mrp_consumption_warning relate to other tables?

Response: Foreign keys in mrp_consumption_warning: create_uid -> res_users.id [constraint: mrp_consumption_warning_create_uid_fkey]; write_uid -> res_users.id [constraint: mrp_consumption_warning_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


Show me the fields of pos.gift.card. or What computed fields exist in pos.gift.card?

Response: The pos.gift.card model has 17 fields. Field types distribution: char: 2, float: 1, many2one: 4, date: 2, boolean: 2, one2many: 2, integer: 1, datetime: 3. Computed fields: 2. Field details: card_no (char) [readonly] [module: equip3_pos_masterdata]; card_value (float) [module: equip3_pos_masterdata]; card_type (many2one) -> pos.gift.card.type [module: equip3_pos_masterdata]; customer_id (many2one) -> res.partner [module: equip3_pos_masterdata]; issue_date (date) [module: equip3_pos_masterdata]; expire_date (date) [module: equip3_pos_masterdata]; is_active (boolean) [module: equip3_pos_masterdata]; Paid (boolean) [module: equip3_pos_masterdata]; used_line (one2many) -> pos.gift.card.use [module: equip3_pos_masterdata]; recharge_line (one2many) -> pos.gift.card.recharge [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 business logic is in uom.category? or What operations can I perform on uom.category?

Response: To use the uom.category 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 relationships exist for res_city? or What tables are connected to res_city?

Response: Foreign keys in res_city: country_id -> res_country.id [constraint: res_city_country_id_fkey]; create_uid -> res_users.id [constraint: res_city_create_uid_fkey]; state_id -> res_country_state.id [constraint: res_city_state_id_fkey]; write_uid -> res_users.id [constraint: res_city_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: res_country_state, res_users, res_country.


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

Response: The list_product table has 19 columns and 4 foreign key relationships. It stores data related to list product in the system. The table has 1 indexes for performance optimization. Column types: integer: 6, character varying: 4, timestamp without time zone: 3, double precision: 6. Nullable columns: 18, columns with defaults: 1.


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

Response: Foreign keys in sh_split_rfq_wizard: create_uid -> res_users.id [constraint: sh_split_rfq_wizard_create_uid_fkey]; purchase_order_id -> purchase_order.id [constraint: sh_split_rfq_wizard_purchase_order_id_fkey]; write_uid -> res_users.id [constraint: sh_split_rfq_wizard_write_uid_fkey]. Total foreign key relationships: 3. Referenced tables: res_users, purchase_order.


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

Response: Columns in rel_sh_payment_report_wizard_res_user: sh_payment_report_wizard_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 fields does report.paperformat have? or What field types are used in report.paperformat?

Response: The report.paperformat model has 24 fields. Field types distribution: char: 2, boolean: 3, selection: 2, float: 6, integer: 5, one2many: 1, many2one: 2, datetime: 3. Computed fields: 4. Field details: name (char) [required] [module: base]; default (boolean) [module: base]; format (selection) [module: base]; margin_top (float) [module: base]; margin_bottom (float) [module: base]; margin_left (float) [module: base]; margin_right (float) [module: base]; page_height (integer) [module: base]; page_width (integer) [module: base]; orientation (selection) [module: base]; header_line (boolean) [module: base]; header_spacing (integer) [module: base]; dpi (integer) [required] [module: base]; report_ids (one2many) -> ir.actions.report [module: base]; print_page_width (float) [readonly] [compute: _compute_print_page_size] [not stored] [module: base]; print_page_height (float) [readonly] [compute: _compute_print_page_size] [not stored] [module: base]; custom_report (boolean) [module: dynamic_barcode_labels]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


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

Response: Foreign keys in mail_compose_message_ir_attachments_rel: attachment_id -> ir_attachment.id [constraint: mail_compose_message_ir_attachments_rel_attachment_id_fkey]; wizard_id -> mail_compose_message.id [constraint: mail_compose_message_ir_attachments_rel_wizard_id_fkey]. Total foreign key relationships: 2. Referenced tables: ir_attachment, mail_compose_message.


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

Response: The assets_approved_users_patner_rel table has 2 columns and 2 foreign key relationships. It stores data related to assets approved users 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 tables are connected to res_config_installer? or Describe the relational structure of res_config_installer.

Response: Foreign keys in res_config_installer: create_uid -> res_users.id [constraint: res_config_installer_create_uid_fkey]; write_uid -> res_users.id [constraint: res_config_installer_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


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

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


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

Response: Columns in website_menu: id (integer) [NOT NULL] [DEFAULT: nextval('website_menu_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [NOT NULL] [COMMENT: Menu]; url (character varying) [COMMENT: Url]; page_id (integer) [PRECISION: 32] [COMMENT: Related Page]; new_window (boolean) [COMMENT: New Window]; sequence (integer) [PRECISION: 32] [COMMENT: Sequence]; website_id (integer) [PRECISION: 32] [COMMENT: Website]; parent_id (integer) [PRECISION: 32] [COMMENT: Parent Menu]; parent_path (character varying) [COMMENT: Parent Path]; mega_menu_content (text) [COMMENT: Mega Menu Content]; mega_menu_classes (character varying) [COMMENT: Mega Menu Classes]; theme_template_id (integer) [PRECISION: 32] [COMMENT: Theme 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]; is_display_in_delivery_control_app (boolean) [COMMENT: Delivery]; user_logged (boolean) [COMMENT: User Logged]; user_not_logged (boolean) [COMMENT: User Not Logged]. Total columns: 19. Statistics: 17 nullable, 1 with defaults, 0 with length constraints.


How to create records in pos.promotion.discount.order? or How to work with pos.promotion.discount.order fields?

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


Which fields are required in report.equip3_purchase_other_operation.report_analyze_quot? or What data can be stored in report.equip3_purchase_other_operation.report_analyze_quot?

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


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

Response: To use the project.project model, you need to provide values for required fields: name, company_id, alias_id, privacy_visibility, rating_status, rating_status_period, alias_model_id, alias_defaults, alias_contact. Readonly fields: currency_id, resource_calendar_id, task_count, doc_count, rating_request_deadline, timesheet_encode_uom_id, total_timesheet_time, encode_uom_in_days, display_create_order, warning_employee_rate, 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, rating_percentage_satisfaction, access_url, access_warning, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, alias_domain. Field usage details: name [required]; partner_email [computed] [no_copy]; partner_phone [computed] [no_copy]; company_id [required] [has_default]; currency_id [readonly] [computed] [no_copy]; is_favorite [computed] [no_copy]; resource_calendar_id [readonly] [computed] [no_copy]; task_count [readonly] [computed] [no_copy]; alias_enabled [computed] [no_copy]; alias_id [required]; privacy_visibility [required] [has_default]; allowed_user_ids [computed] [no_copy]; doc_count [readonly] [computed] [no_copy]; rating_request_deadline [readonly] [computed] [no_copy]; rating_status [required] [has_default]; rating_status_period [required] [has_default]; allow_timesheets [computed] [has_default]; timesheet_encode_uom_id [readonly] [computed] [no_copy]; total_timesheet_time [readonly] [computed] [no_copy]; encode_uom_in_days [readonly] [computed] [no_copy]; display_create_order [readonly] [computed] [no_copy]; timesheet_product_id [computed] [has_default]; warning_employee_rate [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]; rating_percentage_satisfaction [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]; alias_name [computed] [no_copy]; alias_model_id [required] [computed]; alias_user_id [computed]; alias_defaults [required] [computed]; alias_force_thread_id [computed]; alias_domain [readonly] [computed] [no_copy]; alias_parent_model_id [computed]; alias_parent_thread_id [computed]; alias_bounced_content [computed]; alias_contact [required] [computed]. The model supports standard CRUD operations through the ORM.


What fields are readonly in report.accounting_pdf_reports.report_financial? or How to query report.accounting_pdf_reports.report_financial data?

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


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

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


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

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


List all relational fields in crm.team. or How does crm.team relate to other models?

Response: The crm.team model has 20 relational fields: currency_id -> res.currency; favorite_user_ids -> res.users; alias_id -> mail.alias; website_ids -> website; rma_ids -> dev.rma.rma; pos_config_ids -> pos.config; user_id -> res.users; company_id -> res.company; member_ids -> res.users; 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; alias_model_id -> ir.model; alias_user_id -> res.users; alias_parent_model_id -> ir.model. Many2many fields: favorite_user_ids, message_partner_ids, message_channel_ids. One2many fields: website_ids, rma_ids, pos_config_ids, member_ids, message_follower_ids, message_ids, website_message_ids.


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

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


How is im_livechat.channel.rule used in the system? or What does the im_livechat.channel.rule model represent?

Response: The im_livechat.channel.rule model represents Livechat Channel Rules in the ERP system. It contains 13 fields and is used to manage livechat channel rules data. Defined in module: im_livechat. Key fields include: regex_url, action, auto_popup_timer, channel_id, country_ids, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: Foreign keys in ir_rule: create_uid -> res_users.id [constraint: ir_rule_create_uid_fkey]; model_id -> ir_model.id [constraint: ir_rule_model_id_fkey]; write_uid -> res_users.id [constraint: ir_rule_write_uid_fkey]. Total foreign key relationships: 3. Referenced tables: ir_model, res_users.


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

Response: The product_warehouse_cost_wizard_line table has 9 columns and 5 foreign key relationships. It stores data related to product warehouse cost wizard line in the system. The table has 1 indexes for performance optimization. Column types: integer: 6, numeric: 1, timestamp without time zone: 2. Nullable columns: 7, columns with defaults: 1.


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

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


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

Response: Columns in auth_totp_wizard: id (integer) [NOT NULL] [DEFAULT: nextval('auth_totp_wizard_id_seq'::regclass)] [PRECISION: 32]; user_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: User]; secret (character varying) [NOT NULL] [COMMENT: Secret]; url (character varying) [COMMENT: Url]; qrcode (bytea) [COMMENT: Qrcode]; code (character varying) [LENGTH: 7] [COMMENT: Verification Code]; 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, 1 with length constraints.


How is snailmail.confirm used in the system? or Can you explain the purpose of snailmail.confirm?

Response: The snailmail.confirm model represents Snailmail Confirm in the ERP system. It contains 4 fields and is used to manage snailmail confirm data. Defined in module: snailmail. Key fields include: model_name, id, display_name, __last_update.


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

Response: Columns in account_tax_report_wizard: id (integer) [NOT NULL] [DEFAULT: nextval('account_tax_report_wizard_id_seq'::regclass)] [PRECISION: 32]; company_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Company]; date_from (date) [COMMENT: Start Date]; date_to (date) [COMMENT: End Date]; target_move (character varying) [NOT NULL] [COMMENT: Target Moves]; 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]; report_currency_id (integer) [PRECISION: 32] [COMMENT: Report Currency]. Total columns: 10. Statistics: 7 nullable, 1 with defaults, 0 with length constraints.


What does the report.equip3_pos_general.pos_sale_report_template model represent? or How is report.equip3_pos_general.pos_sale_report_template used in the system?

Response: The report.equip3_pos_general.pos_sale_report_template model represents Template Report of sale in the ERP system. It contains 3 fields and is used to manage template report of sale data. Defined in module: equip3_pos_general. Key fields include: id, display_name, __last_update.


Describe the account.loan.generate.wizard model in Odoo. or What is the account.loan.generate.wizard model?

Response: The account.loan.generate.wizard model represents Loan generate wizard in the ERP system. It contains 9 fields and is used to manage loan generate wizard data. Defined in module: account_loan. Key fields include: date, loan_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

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


Can you explain the purpose of void.order.line? or How is void.order.line used in the system?

Response: The void.order.line model represents void.order.line in the ERP system. It contains 12 fields and is used to manage void.order.line data. Defined in module: allfresh_mod_pos. Key fields include: name, session_id, order_id, void_uid, cashier_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: The product_product_setu_inventory_turnover_analysis_report_rel table has 2 columns and 2 foreign key relationships. It stores data related to product product setu inventory turnover analysis report rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


What business logic is in report.accounting_pdf_reports.report_general_ledger? or How do I use the report.accounting_pdf_reports.report_general_ledger model?

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


Show me the relational structure of vendor.payment.request.line. or What one2many fields are in vendor.payment.request.line?

Response: The vendor.payment.request.line model has 5 relational fields: payment_request_id -> vendor.payment.request; currency_id -> res.currency; purchase_order_id -> purchase.order; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


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

Response: The orderline.orderline model has 8 relational fields: reverse_id -> saleblanket.saleblanket; product_id -> product.product; product_uom -> uom.uom; tax_id -> account.tax; company_id -> res.company; analytic_tag_ids -> account.analytic.tag; create_uid -> res.users; write_uid -> res.users. Many2many fields: tax_id, analytic_tag_ids. One2many fields: none.


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

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


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

Response: To use the account.account.template model, you need to provide values for required fields: code, user_type_id, name. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: code [required]; user_type_id [required]; 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 indexes exist on product_template_create_variant_line? or Explain the product_template_create_variant_line table schema.

Response: The product_template_create_variant_line table has 7 columns and 4 foreign key relationships. It stores data related to product template create variant line in the system. The table has 2 indexes for performance optimization. Column types: integer: 5, timestamp without time zone: 2. Nullable columns: 5, columns with defaults: 1.


Describe the field structure of gamification.badge.user.wizard. or Show me the fields of gamification.badge.user.wizard.

Response: The gamification.badge.user.wizard model has 11 fields. Field types distribution: many2one: 5, text: 1, integer: 1, char: 1, datetime: 3. Computed fields: 3. Field details: badge_id (many2one) [required] -> gamification.badge [module: gamification]; comment (text) [module: gamification]; employee_id (many2one) [required] -> hr.employee [module: hr_gamification]; user_id (many2one) [required] [readonly] -> res.users [compute: <bound method Field._compute_related of gamification.badge.user.wizard.user_id>] [not stored] [module: hr_gamification] [related: employee_id.user_id]; 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 pos_qrcode. or What fields are available in pos_qrcode?

Response: Columns in pos_qrcode: id (integer) [NOT NULL] [DEFAULT: nextval('pos_qrcode_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [NOT NULL] [COMMENT: QrCode Label]; field_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Field Display]; config_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: POS Register]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 8. Statistics: 4 nullable, 1 with defaults, 0 with length constraints.


What does the pos.login.history model represent? or Describe the pos.login.history model in Odoo.

Response: The pos.login.history model represents Pos Login History in the ERP system. It contains 13 fields and is used to manage pos login history data. Defined in module: equip3_pos_report. Key fields include: user_id, pos_config_id, pos_branch_id, checkin_datetime, checkout_datetime, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: Columns in ai_memory_export_import_wizard: id (integer) [NOT NULL] [DEFAULT: nextval('ai_memory_export_import_wizard_id_seq'::regclass)] [PRECISION: 32]; operation (character varying) [NOT NULL] [COMMENT: Operation]; import_filename (character varying) [COMMENT: Import Filename]; import_mode (character varying) [COMMENT: Import Mode]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 8. Statistics: 6 nullable, 1 with defaults, 0 with length constraints.


How does report.stock.excel relate to other models? or What are the relationships in report.stock.excel?

Response: The report.stock.excel model has 5 relational fields: product_ids -> product.product; categ_ids -> pos.category; location_ids -> stock.location; create_uid -> res.users; write_uid -> res.users. Many2many fields: product_ids, categ_ids, location_ids. One2many fields: none.


What is the module hierarchy for sh.purchase.analysis.xls? or Which fields in sh.purchase.analysis.xls are computed?

Response: The sh.purchase.analysis.xls model is defined in module: sh_purchase_reports. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: download_report.


What are the available fields for pos.sync.session.order? or Which fields are required in pos.sync.session.order?

Response: The pos.sync.session.order model has 17 fields. Field types distribution: char: 3, text: 2, selection: 1, one2many: 1, many2one: 6, integer: 1, datetime: 3. Computed fields: 4. Field details: uid (char) [module: equip3_pos_masterdata]; data (text) [module: equip3_pos_masterdata]; name (text) [module: equip3_pos_masterdata]; database (char) [module: equip3_pos_masterdata]; state (selection) [module: equip3_pos_masterdata]; line_ids (one2many) -> pos.sync.session.order.line [module: equip3_pos_masterdata]; pos_config_id (many2one) -> pos.config [module: equip3_pos_masterdata]; pos_session_id (many2one) -> pos.session [module: equip3_pos_masterdata]; branch_id (many2one) [readonly] -> res.branch [compute: <bound method Field._compute_related of pos.sync.session.order.branch_id>] [not stored] [module: equip3_pos_general] [related: pos_session_id.pos_branch_id]; company_id (many2one) [readonly] -> res.company [compute: <bound method Field._compute_related of pos.sync.session.order.company_id>] [not stored] [module: equip3_pos_general] [related: pos_session_id.company_id]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


What data can be stored in qiscus.wa.template.content? or What field types are used in qiscus.wa.template.content?

Response: The qiscus.wa.template.content model has 13 fields. Field types distribution: many2one: 3, char: 3, integer: 2, text: 1, selection: 1, datetime: 3. Computed fields: 4. Field details: template_id (many2one) -> qiscus.wa.template [module: equip3_general_features]; name (char) [readonly] [compute: _compute_name] [not stored] [module: equip3_general_features]; language (char) [module: equip3_general_features]; content_id (integer) [module: equip3_general_features]; content (text) [module: equip3_general_features]; category (selection) [readonly] [compute: <bound method Field._compute_related of qiscus.wa.template.content.category>] [not stored] [module: equip3_general_features] [related: template_id.category]; 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 stock_quant? or What data types are used in stock_quant?

Response: Columns in stock_quant: id (integer) [NOT NULL] [DEFAULT: nextval('stock_quant_id_seq'::regclass)] [PRECISION: 32]; product_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Product]; company_id (integer) [PRECISION: 32] [COMMENT: Company]; location_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Location]; lot_id (integer) [PRECISION: 32] [COMMENT: Lot/Serial Number]; package_id (integer) [PRECISION: 32] [COMMENT: Package]; owner_id (integer) [PRECISION: 32] [COMMENT: Owner]; quantity (double precision) [PRECISION: 53] [COMMENT: Quantity]; reserved_quantity (double precision) [NOT NULL] [PRECISION: 53] [COMMENT: Reserved Quantity]; in_date (timestamp without time zone) [COMMENT: Incoming Date]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]; removal_date (timestamp without time zone) [COMMENT: Removal Date]; state_check (character varying) [COMMENT: state]; move_id (integer) [PRECISION: 32] [COMMENT: Stock Move]; is_low_stock (boolean) [COMMENT: Is Low Stock]; stock_quant_sequence (character varying) [COMMENT: No]; product_description (character varying) [COMMENT: Description]; initial_demand (double precision) [PRECISION: 53] [COMMENT: Initial Demand]; remaining (double precision) [PRECISION: 53] [COMMENT: Remaining]; quantity_done (numeric) [COMMENT: Done]; fulfillment (double precision) [PRECISION: 53] [COMMENT: Fulfillment (%)]; total_stock_in_package (double precision) [PRECISION: 53] [COMMENT: Stock Danger]; create_automatic (boolean) [COMMENT: Create Automatic]; product_category (integer) [PRECISION: 32] [COMMENT: Product category]; expire_date (timestamp without time zone) [COMMENT: Expiration_date]; warehouse_id (integer) [PRECISION: 32] [COMMENT: Warehouse]; active (boolean) [COMMENT: Active]. Total columns: 30. Statistics: 26 nullable, 1 with defaults, 0 with length constraints.


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

Response: Columns in account_analytic_tag_account_move_line_rel: account_move_line_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.


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

Response: Columns in account_asset_depreciation_line: id (integer) [NOT NULL] [DEFAULT: nextval('account_asset_depreciation_line_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [NOT NULL] [COMMENT: Depreciation Name]; sequence (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Sequence]; asset_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Asset]; amount (numeric) [NOT NULL] [COMMENT: Current Depreciation]; remaining_value (numeric) [NOT NULL] [COMMENT: Next Period Depreciation]; depreciated_value (double precision) [NOT NULL] [PRECISION: 53] [COMMENT: Cumulative Depreciation]; depreciation_date (date) [COMMENT: Depreciation Date]; move_id (integer) [PRECISION: 32] [COMMENT: Depreciation Entry]; move_check (boolean) [COMMENT: Linked]; move_posted_check (boolean) [COMMENT: Posted]; 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]; currency_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Currency]. Total columns: 16. Statistics: 8 nullable, 1 with defaults, 0 with length constraints.


What methods are available in payment.sale.details.report? or Which fields are stored computed fields in payment.sale.details.report?

Response: The payment.sale.details.report model is defined in module: equip3_sale_report. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: .


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

Response: Foreign keys in purchase_requisition_line: account_analytic_id -> account_analytic_account.id [constraint: purchase_requisition_line_account_analytic_id_fkey]; branch_id -> res_branch.id [constraint: purchase_requisition_line_branch_id_fkey]; company_id -> res_company.id [constraint: purchase_requisition_line_company_id_fkey]; create_uid -> res_users.id [constraint: purchase_requisition_line_create_uid_fkey]; destination_warehouse -> stock_warehouse.id [constraint: purchase_requisition_line_destination_warehouse_fkey]; move_dest_id -> stock_move.id [constraint: purchase_requisition_line_move_dest_id_fkey]; product_id -> product_product.id [constraint: purchase_requisition_line_product_id_fkey]; product_uom_id -> uom_uom.id [constraint: purchase_requisition_line_product_uom_id_fkey]; requisition_id -> purchase_requisition.id [constraint: purchase_requisition_line_requisition_id_fkey]; write_uid -> res_users.id [constraint: purchase_requisition_line_write_uid_fkey]. Total foreign key relationships: 10. Referenced tables: stock_warehouse, product_product, stock_move, res_company, res_users, purchase_requisition, res_branch, account_analytic_account, uom_uom.


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

Response: Columns in account_reconcile_model_template_res_partner_rel: account_reconcile_model_template_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 are the relationships in image.mixin? or What models are connected to image.mixin?

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


Can you explain the purpose of delivery.carrier? or How is delivery.carrier used in the system?

Response: The delivery.carrier model represents Shipping Methods in the ERP system. It contains 35 fields and is used to manage shipping methods data. Defined in module: delivery. Key fields include: name, active, sequence, integration_level, prod_environment, debug_logging, company_id, product_id, invoice_policy, country_ids, state_ids, zip_from, zip_to, margin, free_over, amount, can_generate_return, return_label_on_delivery, get_return_label_from_portal, fixed_price, price_rule_ids, website_description, delivery_type, website_published, website_id, is_published, can_publish, website_url, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Describe the field structure of pos.global.discount. or What data can be stored in pos.global.discount?

Response: The pos.global.discount model has 14 fields. Field types distribution: char: 3, float: 1, many2one: 4, selection: 1, many2many: 1, integer: 1, datetime: 3. Computed fields: 2. Field details: name (char) [required] [module: equip3_pos_masterdata]; amount (float) [required] [module: equip3_pos_masterdata]; product_id (many2one) [required] -> product.product [module: equip3_pos_masterdata]; reason (char) [required] [module: equip3_pos_masterdata]; type (selection) [required] [module: equip3_pos_masterdata]; branch_ids (many2many) -> res.branch [module: equip3_pos_masterdata]; company_id (many2one) -> res.company [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].


Tell me about the purchase.custom.checklist.line model. or Can you explain the purpose of purchase.custom.checklist.line?

Response: The purchase.custom.checklist.line model represents Purchase Custom Checklist Line in the ERP system. It contains 14 fields and is used to manage purchase custom checklist line data. Defined in module: sh_all_in_one_purchase_tools. Key fields include: name, description, updated_date, state, order_id, state2, feedback, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What are common use cases for stock.day.average? or What operations can I perform on stock.day.average?

Response: To use the stock.day.average model, you need to provide values for required fields: company_id. Readonly fields: company_id, transfer_count, 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: company_id [required] [readonly] [has_default]; transfer_count [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.


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

Response: Foreign keys in rel_sh_payment_report_wizard_res_user: sh_payment_report_wizard_id -> sh_payment_report_wizard.id [constraint: rel_sh_payment_report_wizard_r_sh_payment_report_wizard_id_fkey]; res_users_id -> res_users.id [constraint: rel_sh_payment_report_wizard_res_user_res_users_id_fkey]. Total foreign key relationships: 2. Referenced tables: sh_payment_report_wizard, res_users.


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

Response: Columns in blanket_approval_matrix: id (integer) [NOT NULL] [DEFAULT: nextval('blanket_approval_matrix_id_seq'::regclass)] [PRECISION: 32]; campaign_id (integer) [PRECISION: 32] [COMMENT: Campaign]; source_id (integer) [PRECISION: 32] [COMMENT: Source]; medium_id (integer) [PRECISION: 32] [COMMENT: Medium]; access_token (character varying) [COMMENT: Security Token]; message_main_attachment_id (integer) [PRECISION: 32] [COMMENT: Main Attachment]; name (character varying) [NOT NULL] [COMMENT: Name]; company_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Company]; branch_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Branch]; config (character varying) [NOT NULL] [COMMENT: Configuration]; minimum_amt (double precision) [NOT NULL] [PRECISION: 53] [COMMENT: Minimum Amount]; maximum_amt (double precision) [NOT NULL] [PRECISION: 53] [COMMENT: Maximum 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: 16. Statistics: 9 nullable, 1 with defaults, 0 with length constraints.


How is account.payment.reconcile.line used in the system? or What is the account.payment.reconcile.line model?

Response: The account.payment.reconcile.line model represents   in the ERP system. It contains 14 fields and is used to manage   data. Defined in module: equip3_accounting_operation. Key fields include: reconcile_line_id, currency_id, payment_type, partner_id, amount_due, invoice_id, allocation_amount, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: Foreign keys in snailmail_letter_cancel: create_uid -> res_users.id [constraint: snailmail_letter_cancel_create_uid_fkey]; write_uid -> res_users.id [constraint: snailmail_letter_cancel_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


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

Response: The website_menu table has 19 columns and 6 foreign key relationships. It stores data related to website menu in the system. The table has 3 indexes for performance optimization. Column types: integer: 8, character varying: 4, boolean: 4, text: 1, timestamp without time zone: 2. Nullable columns: 17, columns with defaults: 1.


How to create records in auditlog.http.request? or How to query auditlog.http.request data?

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


What modules define report.equip3_purchase_other_operation.report_analyze_quot? or Which fields are stored computed fields in report.equip3_purchase_other_operation.report_analyze_quot?

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


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

Response: Foreign keys in res_users_stock_day_average_rel: res_users_id -> res_users.id [constraint: res_users_stock_day_average_rel_res_users_id_fkey]; stock_day_average_id -> stock_day_average.id [constraint: res_users_stock_day_average_rel_stock_day_average_id_fkey]. Total foreign key relationships: 2. Referenced tables: res_users, stock_day_average.


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

Response: Columns in dev_rma_line: id (integer) [NOT NULL] [DEFAULT: nextval('dev_rma_line_id_seq'::regclass)] [PRECISION: 32]; move_id (integer) [PRECISION: 32] [COMMENT: Move]; product_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Product]; delivered_qty (double precision) [NOT NULL] [PRECISION: 53] [COMMENT: Delivered Qty]; return_qty (double precision) [PRECISION: 53] [COMMENT: Return Qty]; rma_id (integer) [PRECISION: 32] [COMMENT: RMA]; action (character varying) [COMMENT: Action]; replace_product_id (integer) [PRECISION: 32] [COMMENT: Rep. Product]; replace_qty (double precision) [PRECISION: 53] [COMMENT: Quantity]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]; return_reason (integer) [PRECISION: 32] [COMMENT: Reason]; already_returned_qty (numeric) [COMMENT: Already Returned Qty]; picking_id (integer) [PRECISION: 32] [COMMENT: Transfer Reference]; purchase_id (integer) [PRECISION: 32] [COMMENT: Purchase Order]; sale_id (integer) [PRECISION: 32] [COMMENT: Sale Order]; account_move_id (integer) [PRECISION: 32] [COMMENT: Invoice]; is_ppn (boolean) [COMMENT: Is PPN]; tax_number (character varying) [COMMENT: Nomor Seri Faktur Pajak]; is_done_bill (boolean) [COMMENT: Is Done Bill]; price_unit (double precision) [PRECISION: 53] [COMMENT: Price Unit]; so_antar_badan (character varying) [COMMENT: SO Reference]; po_antar_badan (character varying) [COMMENT: PO Reference]. Total columns: 25. Statistics: 22 nullable, 1 with defaults, 0 with length constraints.


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

Response: The iap_account table has 7 columns and 2 foreign key relationships. It stores data related to iap account 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.


List all relational fields in account.multipayment.credit. or How does account.multipayment.credit relate to other models?

Response: The account.multipayment.credit model has 8 relational fields: line_id -> account.multipayment; currency_id -> res.currency; invoice_id -> account.move; account_id -> account.account; payment_id -> account.payment; account_reverse_ids -> account.move; create_uid -> res.users; write_uid -> res.users. Many2many fields: account_reverse_ids. One2many fields: none.


Describe the field structure of report.excel.section. or List all fields in the report.excel.section model.

Response: The report.excel.section model has 31 fields. Field types distribution: integer: 5, char: 6, many2one: 6, one2many: 3, selection: 2, boolean: 4, text: 2, datetime: 3. Computed fields: 4. Field details: sequence (integer) [module: report_excel]; name (char) [required] [module: report_excel]; report_excel_id (many2one) -> report.excel [module: report_excel]; parent_id (many2one) -> report.excel.section [module: report_excel]; children_ids (one2many) -> report.excel.section [module: report_excel]; report_id (integer) [readonly] [compute: _compute_report_id] [not stored] [module: report_excel]; report_excel_param_content (char) [readonly] [compute: _compute_report_excel_param_content] [not stored] [module: report_excel]; type_data (selection) [required] [module: report_excel]; level (integer) [module: report_excel]; report_excel_fields_ids (one2many) -> report.excel.fields [module: report_excel]; root_model_related_field_id (many2one) -> ir.model.fields [module: report_excel]; root_model_id (many2one) -> ir.model [module: report_excel]; root_model_name (selection) [module: report_excel]; check_root_model (boolean) [module: report_excel]; section (boolean) [module: report_excel]; section_level (integer) [module: report_excel]; section_start (char) [required] [module: report_excel]; section_end (char) [required] [module: report_excel]; sql_bool (boolean) [module: report_excel]; sql_statement (text) [module: report_excel]; report_excel_fields_sql_ids (one2many) -> report.excel.fields.sql [module: report_excel]; domain (char) [module: report_excel]; archive_bool (boolean) [module: report_excel]; description (text) [module: report_excel]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


What computed fields exist in approval.matrix.accounting? or Show me the fields of approval.matrix.accounting.

Response: The approval.matrix.accounting model has 47 fields. Field types distribution: selection: 3, float: 3, char: 7, many2one: 10, many2many: 3, one2many: 5, date: 2, boolean: 5, integer: 5, text: 1, datetime: 3. Computed fields: 25. Field details: approval_matrix_type (selection) [module: equip3_accounting_masterdata]; change_amount (float) [module: equip3_accounting_masterdata]; name (char) [required] [module: equip3_accounting_masterdata]; min_amount (float) [module: equip3_accounting_masterdata]; max_amount (float) [module: equip3_accounting_masterdata]; company_id (many2one) [required] [readonly] -> res.company [module: equip3_accounting_masterdata]; branch_id (many2one) -> res.branch [module: equip3_accounting_masterdata]; filter_branch_ids (many2many) [readonly] -> res.branch [compute: _compute_branch_ids] [not stored] [module: equip3_accounting_masterdata]; approval_matrix_line_ids (one2many) [required] -> approval.matrix.accounting.lines [module: equip3_accounting_masterdata]; campaign_id (many2one) -> utm.campaign [module: utm]; source_id (many2one) -> utm.source [module: utm]; medium_id (many2one) -> utm.medium [module: utm]; activity_ids (one2many) -> mail.activity [module: mail]; activity_state (selection) [readonly] [compute: _compute_activity_state] [not stored] [module: mail]; activity_user_id (many2one) -> res.users [compute: <bound method Field._compute_related of approval.matrix.accounting.activity_user_id>] [not stored] [module: mail] [related: activity_ids.user_id] [inverse: <bound method Field._inverse_related of approval.matrix.accounting.activity_user_id>]; activity_type_id (many2one) -> mail.activity.type [compute: <bound method Field._compute_related of approval.matrix.accounting.activity_type_id>] [not stored] [module: mail] [related: activity_ids.activity_type_id] [inverse: <bound method Field._inverse_related of approval.matrix.accounting.activity_type_id>]; activity_type_icon (char) [readonly] [compute: <bound method Field._compute_related of approval.matrix.accounting.activity_type_icon>] [not stored] [module: mail] [related: activity_ids.icon]; activity_date_deadline (date) [readonly] [compute: _compute_activity_date_deadline] [not stored] [module: mail]; my_activity_date_deadline (date) [readonly] [compute: _compute_my_activity_date_deadline] [not stored] [module: mail]; activity_summary (char) [compute: <bound method Field._compute_related of approval.matrix.accounting.activity_summary>] [not stored] [module: mail] [related: activity_ids.summary] [inverse: <bound method Field._inverse_related of approval.matrix.accounting.activity_summary>]; activity_exception_decoration (selection) [readonly] [compute: _compute_activity_exception_type] [not stored] [module: mail]; activity_exception_icon (char) [readonly] [compute: _compute_activity_exception_type] [not stored] [module: mail]; message_is_follower (boolean) [readonly] [compute: _compute_is_follower] [not stored] [module: mail]; message_follower_ids (one2many) -> mail.followers [module: mail]; message_partner_ids (many2many) [readonly] -> res.partner [compute: _get_followers] [not stored] [module: mail]; message_channel_ids (many2many) [readonly] -> mail.channel [compute: _get_followers] [not stored] [module: mail]; message_ids (one2many) -> mail.message [module: mail]; message_unread (boolean) [readonly] [compute: _get_message_unread] [not stored] [module: mail]; message_unread_counter (integer) [readonly] [compute: _get_message_unread] [not stored] [module: mail]; message_needaction (boolean) [readonly] [compute: _get_message_needaction] [not stored] [module: mail]; message_needaction_counter (integer) [readonly] [compute: _get_message_needaction] [not stored] [module: mail]; message_has_error (boolean) [readonly] [compute: _compute_message_has_error] [not stored] [module: mail]; message_has_error_counter (integer) [readonly] [compute: _compute_message_has_error] [not stored] [module: mail]; message_attachment_count (integer) [readonly] [compute: _compute_message_attachment_count] [not stored] [module: mail]; message_main_attachment_id (many2one) -> ir.attachment [module: mail]; website_message_ids (one2many) -> mail.message [module: portal]; message_has_sms_error (boolean) [readonly] [compute: _compute_message_has_sms_error] [not stored] [module: sms]; access_url (char) [readonly] [compute: _compute_access_url] [not stored] [module: portal]; access_token (char) [module: portal]; access_warning (text) [readonly] [compute: _compute_access_warning] [not stored] [module: portal]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


What is the module hierarchy for equip3.reporting.asset.wizard? or What are the technical details of equip3.reporting.asset.wizard?

Response: The equip3.reporting.asset.wizard 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_download, get_months, _get_asset_value_residual, get_datas, get_value, get_depreciation_datas, get_accumulation_previous_datas, get_accumulation_additional_datas, get_book_year_previous_datas, get_book_year_datas, action_export_xlsx.


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

Response: The invoice_approved_user_rel table has 2 columns and 2 foreign key relationships. It stores data related to invoice approved user 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 stock_backorder_confirmation table? or What columns does stock_backorder_confirmation have?

Response: The stock_backorder_confirmation table has 6 columns and 2 foreign key relationships. It stores data related to stock backorder confirmation in the system. The table has 1 indexes for performance optimization. Column types: integer: 3, boolean: 1, timestamp without time zone: 2. Nullable columns: 5, columns with defaults: 1.


What data can be stored in kpi.scorecard.line? or Which fields are required in kpi.scorecard.line?

Response: The kpi.scorecard.line model has 24 fields. Field types distribution: many2one: 6, text: 1, float: 3, char: 5, selection: 1, integer: 2, boolean: 2, html: 1, datetime: 3. Computed fields: 13. Field details: kpi_id (many2one) [required] -> kpi.item [module: kpi_scorecard]; category_id (many2one) [readonly] -> kpi.category [compute: <bound method Field._compute_related of kpi.scorecard.line.category_id>] [stored] [module: kpi_scorecard] [related: kpi_id.category_id]; description (text) [readonly] [compute: <bound method Field._compute_related of kpi.scorecard.line.description>] [stored] [module: kpi_scorecard] [related: kpi_id.description]; period_id (many2one) -> kpi.period [module: kpi_scorecard]; target_value (float) [module: kpi_scorecard]; formatted_target_value (char) [readonly] [compute: <function kpi_scorecard_line._compute_formatted_actual_value at 0x2f1995e50>] [stored] [module: kpi_scorecard]; actual_value (float) [module: kpi_scorecard]; computation_error (char) [module: kpi_scorecard]; formatted_actual_value (char) [readonly] [compute: <function kpi_scorecard_line._compute_formatted_actual_value at 0x2f1995e50>] [stored] [module: kpi_scorecard]; result (selection) [readonly] [compute: <function kpi_scorecard_line._compute_formatted_actual_value at 0x2f1995e50>] [stored] [module: kpi_scorecard]; sequence (integer) [readonly] [compute: <function kpi_scorecard_line._compute_sequence at 0x2f1995ee0>] [stored] [module: kpi_scorecard]; all_parents (char) [readonly] [compute: <function kpi_scorecard_line._compute_sequence at 0x2f1995ee0>] [stored] [module: kpi_scorecard]; edit_rights (boolean) [readonly] [compute: <function kpi_scorecard_line._compute_edit_rights at 0x2f1995f70>] [not stored] [module: kpi_scorecard]; company_id (many2one) [readonly] -> res.company [compute: <bound method Field._compute_related of kpi.scorecard.line.company_id>] [stored] [module: kpi_scorecard] [related: period_id.company_id]; period_length (float) [readonly] [compute: <bound method Field._compute_related of kpi.scorecard.line.period_length>] [stored] [module: kpi_scorecard] [related: period_id.period_length]; help_notes (html) [readonly] [compute: <function kpi_help._compute_show_kpi_help at 0x2f195ae50>] [not stored] [module: kpi_scorecard]; kpi_help_dummy (boolean) [module: kpi_scorecard]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


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

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


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

Response: Foreign keys in pos_loyalty_category_pos_voucher_rel: pos_loyalty_category_id -> pos_loyalty_category.id [constraint: pos_loyalty_category_pos_voucher_r_pos_loyalty_category_id_fkey]; pos_voucher_id -> pos_voucher.id [constraint: pos_loyalty_category_pos_voucher_rel_pos_voucher_id_fkey]. Total foreign key relationships: 2. Referenced tables: pos_loyalty_category, pos_voucher.


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

Response: Foreign keys in product_warehouse_cost_wizard_line: company_id -> res_company.id [constraint: product_warehouse_cost_wizard_line_company_id_fkey]; create_uid -> res_users.id [constraint: product_warehouse_cost_wizard_line_create_uid_fkey]; prod_wh_cost_id -> product_warehouse_cost_wizard.id [constraint: product_warehouse_cost_wizard_line_prod_wh_cost_id_fkey]; warehouse_id -> stock_warehouse.id [constraint: product_warehouse_cost_wizard_line_warehouse_id_fkey]; write_uid -> res_users.id [constraint: product_warehouse_cost_wizard_line_write_uid_fkey]. Total foreign key relationships: 5. Referenced tables: stock_warehouse, res_users, product_warehouse_cost_wizard, res_company.


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

Response: Foreign keys in gamification_goal_definition: action_id -> ir_act_window.id [constraint: gamification_goal_definition_action_id_fkey]; batch_distinctive_field -> ir_model_fields.id [constraint: gamification_goal_definition_batch_distinctive_field_fkey]; create_uid -> res_users.id [constraint: gamification_goal_definition_create_uid_fkey]; field_date_id -> ir_model_fields.id [constraint: gamification_goal_definition_field_date_id_fkey]; field_id -> ir_model_fields.id [constraint: gamification_goal_definition_field_id_fkey]; model_id -> ir_model.id [constraint: gamification_goal_definition_model_id_fkey]; write_uid -> res_users.id [constraint: gamification_goal_definition_write_uid_fkey]. Total foreign key relationships: 7. Referenced tables: ir_model, res_users, ir_act_window, ir_model_fields.


What are the available fields for web_editor.converter.test? or List all fields in the web_editor.converter.test model.

Response: The web_editor.converter.test model has 18 fields. Field types distribution: char: 2, integer: 2, float: 2, many2one: 3, binary: 1, date: 1, datetime: 4, selection: 1, html: 1, text: 1. Computed fields: 2. Field details: char (char) [module: web_editor]; integer (integer) [module: web_editor]; float (float) [module: web_editor]; numeric (float) [module: web_editor]; many2one (many2one) -> web_editor.converter.test.sub [module: web_editor]; binary (binary) [module: web_editor]; date (date) [module: web_editor]; datetime (datetime) [module: web_editor]; selection_str (selection) [module: web_editor]; html (html) [module: web_editor]; text (text) [module: web_editor]; 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 is kpi.scorecard.line used in the system? or Can you explain the purpose of kpi.scorecard.line?

Response: The kpi.scorecard.line model represents KPI Target in the ERP system. It contains 24 fields and is used to manage kpi target data. Defined in module: kpi_scorecard. Key fields include: kpi_id, category_id, description, period_id, target_value, formatted_target_value, actual_value, computation_error, formatted_actual_value, result, sequence, all_parents, edit_rights, company_id, period_length, help_notes, kpi_help_dummy, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: Foreign keys in pos_keyboard_shortcuts: create_uid -> res_users.id [constraint: pos_keyboard_shortcuts_create_uid_fkey]; write_uid -> res_users.id [constraint: pos_keyboard_shortcuts_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


What are common use cases for tax.report? or How to work with tax.report fields?

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


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

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


What are the available fields for stock.landed.cost.lines? or Which fields are required in stock.landed.cost.lines?

Response: The stock.landed.cost.lines model has 14 fields. Field types distribution: char: 2, many2one: 6, monetary: 1, selection: 1, integer: 1, datetime: 3. Computed fields: 3. Field details: name (char) [module: stock_landed_costs]; cost_id (many2one) [required] -> stock.landed.cost [module: stock_landed_costs]; product_id (many2one) [required] -> product.product [module: stock_landed_costs]; price_unit (monetary) [required] [module: stock_landed_costs]; split_method (selection) [required] [module: stock_landed_costs]; account_id (many2one) -> account.account [module: stock_landed_costs]; currency_id (many2one) [readonly] -> res.currency [compute: <bound method Field._compute_related of stock.landed.cost.lines.currency_id>] [not stored] [module: stock_landed_costs] [related: cost_id.currency_id]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


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

Response: Foreign keys in global_search: create_uid -> res_users.id [constraint: global_search_create_uid_fkey]; main_field_id -> ir_model_fields.id [constraint: global_search_main_field_id_fkey]; model_id -> ir_model.id [constraint: global_search_model_id_fkey]; write_uid -> res_users.id [constraint: global_search_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: ir_model, res_users, ir_model_fields.


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

Response: The product_cancel table has 14 columns and 7 foreign key relationships. It stores data related to product cancel in the system. The table has 1 indexes for performance optimization. Column types: integer: 8, character varying: 1, double precision: 1, text: 1, date: 1, timestamp without time zone: 2. Nullable columns: 13, columns with defaults: 1.


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

Response: Foreign keys in mail_alias: alias_model_id -> ir_model.id [constraint: mail_alias_alias_model_id_fkey]; alias_parent_model_id -> ir_model.id [constraint: mail_alias_alias_parent_model_id_fkey]; alias_user_id -> res_users.id [constraint: mail_alias_alias_user_id_fkey]; create_uid -> res_users.id [constraint: mail_alias_create_uid_fkey]; write_uid -> res_users.id [constraint: mail_alias_write_uid_fkey]. Total foreign key relationships: 5. Referenced tables: ir_model, res_users.


How do I use the sh.wqm.quick.menu model? or What business logic is in sh.wqm.quick.menu?

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


Describe the field structure of vendor.delay.report. or What data can be stored in vendor.delay.report?

Response: The vendor.delay.report model has 10 fields. Field types distribution: many2one: 3, datetime: 2, float: 3, integer: 1, char: 1. Computed fields: 2. Field details: partner_id (many2one) [readonly] -> res.partner [module: purchase_stock]; product_id (many2one) [readonly] -> product.product [module: purchase_stock]; category_id (many2one) [readonly] -> product.category [module: purchase_stock]; date (datetime) [readonly] [module: purchase_stock]; qty_total (float) [readonly] [module: purchase_stock]; qty_on_time (float) [readonly] [module: purchase_stock]; on_time_rate (float) [readonly] [module: purchase_stock]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field] [not stored] [module: None].


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

Response: Foreign keys in account_journal_journal_entry_report_rel: journal_entry_report_id -> journal_entry_report.id [constraint: account_journal_journal_entry_repo_journal_entry_report_id_fkey]; account_journal_id -> account_journal.id [constraint: account_journal_journal_entry_report_re_account_journal_id_fkey]. Total foreign key relationships: 2. Referenced tables: journal_entry_report, account_journal.


Which fields are stored computed fields in sale.adv.wizard.product.line.specific? or What is the module hierarchy for sale.adv.wizard.product.line.specific?

Response: The sale.adv.wizard.product.line.specific model is defined in module: equip3_sale_operation. It has 5 computed fields: default_code, standard_price, uom_po_id, display_name, __last_update. Stored computed fields: none. Related fields: default_code -> product_id.default_code, standard_price -> product_id.standard_price, uom_po_id -> product_id.uom_po_id. Original module methods: .


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

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


What computed fields exist in warranty.renew? or Which fields are required in warranty.renew?

Response: The warranty.renew model has 12 fields. Field types distribution: many2one: 6, float: 1, integer: 1, char: 1, datetime: 3. Computed fields: 2. Field details: product_id (many2one) [required] -> product.product [module: bi_warranty_registration]; serial_no (many2one) [required] -> stock.production.lot [module: bi_warranty_registration]; partner_id (many2one) [required] -> res.partner [module: bi_warranty_registration]; warranty (many2one) -> product.warranty [module: bi_warranty_registration]; renew_amt (float) [module: bi_warranty_registration]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


Show me the relational structure of base.partner.merge.automatic.wizard. or How does base.partner.merge.automatic.wizard relate to other models?

Response: The base.partner.merge.automatic.wizard model has 6 relational fields: current_line_id -> base.partner.merge.line; line_ids -> base.partner.merge.line; partner_ids -> res.partner; dst_partner_id -> res.partner; create_uid -> res.users; write_uid -> res.users. Many2many fields: partner_ids. One2many fields: line_ids.


List all fields in the pos.generate.efaktur.other model. or What are the available fields for pos.generate.efaktur.other?

Response: The pos.generate.efaktur.other model has 11 fields. Field types distribution: many2one: 5, char: 2, integer: 1, datetime: 3. Computed fields: 2. Field details: gen_efaktur_id (many2one) -> pos.generate.efaktur [module: equip3_pos_membership]; partner_id (many2one) -> res.partner [module: equip3_pos_membership]; account_move_id (many2one) -> account.move [module: equip3_pos_membership]; l10n_id_tax_number (char) [module: equip3_pos_membership_l10n_id]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


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

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


What is the module hierarchy for ai.chat.job? or How is ai.chat.job implemented technically?

Response: The ai.chat.job model is defined in module: ai_chat_agent. It has 9 computed fields: state, current_step, error_message, queue_job_state, queue_job_exc_info, started_at, completed_at, display_name, __last_update. Stored computed fields: state, current_step, error_message, started_at, completed_at. Related fields: queue_job_state -> queue_job_id.state, queue_job_exc_info -> queue_job_id.exc_info. Original module methods: _compute_state, _compute_current_step, _compute_error_message, _compute_timestamps, create_ai_iteration_job, create_resume_job, update_progress, mark_completed, save_checkpoint, _serialize_tool_results, _make_json_safe, load_checkpoint, can_resume, is_stuck, handle_stuck_job, get_status, cleanup_old_jobs, unlink.


What data can be stored in calendar.alarm? or What field types are used in calendar.alarm?

Response: The calendar.alarm model has 12 fields. Field types distribution: char: 2, integer: 3, selection: 2, many2one: 2, datetime: 3. Computed fields: 3. Field details: name (char) [required] [module: calendar]; duration (integer) [required] [module: calendar]; interval (selection) [required] [module: calendar]; duration_minutes (integer) [readonly] [compute: _compute_duration_minutes] [stored] [module: calendar]; alarm_type (selection) [required] [module: calendar_sms]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


What are the technical details of mail.resend.cancel? or Which fields are stored computed fields in mail.resend.cancel?

Response: The mail.resend.cancel model is defined in module: mail. It has 3 computed fields: help_message, display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: _compute_help_message, cancel_resend_action, _valid_field_parameter, _mail_track, _message_get_default_recipients, _notify_get_reply_to, _alias_check_contact, _alias_get_error_message, _get_default_activity_view, _notify_email_headers, _notify_email_header_dict.


Describe the many2many relations for product.price.quantity. or What models are connected to product.price.quantity?

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


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

Response: To use the rating.rating model, you need to provide values for required fields: res_id. Readonly fields: res_name, res_model, resource_ref, parent_res_name, parent_ref, rating_image, rating_text, publisher_id, publisher_datetime, id, display_name, create_uid, write_uid, write_date, __last_update. Field usage details: res_name [readonly] [computed] [no_copy]; res_model [readonly] [computed] [no_copy]; res_id [required]; resource_ref [readonly] [computed] [no_copy]; parent_res_name [readonly] [computed] [no_copy]; parent_res_model [computed] [no_copy]; parent_ref [readonly] [computed] [no_copy]; rating_image [readonly] [computed] [no_copy]; rating_text [readonly] [computed] [no_copy]; is_internal [computed] [no_copy]; publisher_id [readonly]; publisher_datetime [readonly]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


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

Response: Columns in ctm_dynamic_balance_sheet_report: id (integer) [NOT NULL] [DEFAULT: nextval('ctm_dynamic_balance_sheet_report_id_seq'::regclass)] [PRECISION: 32]; company_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Company]; display_account (character varying) [NOT NULL] [COMMENT: Display Accounts]; target_move (character varying) [NOT NULL] [COMMENT: Target Move]; date_from (date) [COMMENT: Start date]; date_to (date) [COMMENT: End date]; comparison (integer) [PRECISION: 32] [COMMENT: Comparison]; previous (boolean) [COMMENT: Previous]; report_currency_id (integer) [PRECISION: 32] [COMMENT: Currency]; book (character varying) [NOT NULL] [COMMENT: Book]; consolidate (character varying) [NOT NULL] [COMMENT: Consolidate]; comp_detail (character varying) [NOT NULL] [COMMENT: Comparison Detail]; filter_budget (boolean) [COMMENT: Budget Filter]; budget (character varying) [NOT NULL] [COMMENT: Budget]; debit_credit (character varying) [NOT NULL] [COMMENT: Debit & Credit]; entities_comparison (character varying) [NOT NULL] [COMMENT: Entities Comparison]; 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]; all_account (character varying) [NOT NULL] [COMMENT: show all Account]. Total columns: 21. Statistics: 10 nullable, 1 with defaults, 0 with length constraints.


How is account.fiscal.year implemented technically? or Describe the implementation of account.fiscal.year.

Response: The account.fiscal.year model is defined in module: om_account_accountant. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: _check_dates.


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

Response: The mailing_list_mailing_list_merge_rel table has 2 columns and 2 foreign key relationships. It stores data related to mailing list mailing list merge 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 link_hide_view_nodes_store_model_nodes_rel have? or How many columns are in link_hide_view_nodes_store_model_nodes_rel?

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


Show me the fields of account.internal.transfer. or List all fields in the account.internal.transfer model.

Response: The account.internal.transfer model has 68 fields. Field types distribution: many2one: 18, boolean: 11, text: 2, monetary: 2, date: 3, datetime: 3, selection: 6, many2many: 4, one2many: 5, float: 2, char: 7, integer: 5. Computed fields: 32. Field details: request_partner_id (many2one) -> res.partner [module: equip3_accounting_operation]; bank_from_journal_id (many2one) -> account.journal [module: equip3_accounting_operation]; bank_to_journal_id (many2one) -> account.journal [module: equip3_accounting_operation]; transfer_in_transit (boolean) [module: equip3_accounting_operation]; account_in_transit (many2one) -> account.account [module: equip3_accounting_operation]; transfer_desc (text) [module: equip3_accounting_operation]; transfer_amount (monetary) [module: equip3_accounting_operation]; currency_id (many2one) [readonly] -> res.currency [module: equip3_accounting_operation]; transfer_date (date) [module: equip3_accounting_operation]; create_date (datetime) [readonly] [module: equip3_accounting_operation]; create_uid (many2one) [readonly] -> res.users [module: equip3_accounting_operation]; company_id (many2one) -> res.company [module: equip3_accounting_operation]; branch_id (many2one) -> res.branch [module: equip3_accounting_operation]; state (selection) [module: equip3_accounting_operation]; filter_branch_ids (many2many) [readonly] -> res.branch [compute: _compute_branch_ids] [not stored] [module: equip3_accounting_operation]; administration (boolean) [module: equip3_accounting_operation]; administration_account (many2one) -> account.account [module: equip3_accounting_operation]; administration_fee (monetary) [module: equip3_accounting_operation]; has_reconciled_entries (boolean) [module: equip3_accounting_operation]; approval_matrix_id (many2one) [readonly] -> approval.matrix.accounting [compute: _get_approval_matrix] [not stored] [module: equip3_accounting_operation]; is_internal_approval_matrix (boolean) [readonly] [compute: _get_approve_button_from_config] [not stored] [module: equip3_accounting_operation]; approved_matrix_ids (one2many) -> approval.matrix.accounting.lines [module: equip3_accounting_operation]; approval_matrix_line_id (many2one) [readonly] -> approval.matrix.accounting.lines [compute: _get_approve_button] [not stored] [module: equip3_accounting_operation]; is_approve_button (boolean) [readonly] [compute: _get_approve_button] [not stored] [module: equip3_accounting_operation]; state1 (selection) [readonly] [compute: <bound method Field._compute_related of account.internal.transfer.state1>] [not stored] [module: equip3_accounting_operation] [related: state]; state2 (selection) [readonly] [compute: <bound method Field._compute_related of account.internal.transfer.state2>] [not stored] [module: equip3_accounting_operation] [related: state]; analytic_group_ids (many2many) [readonly] -> account.analytic.tag [compute: _depends_analytic_group_ids] [not stored] [module: equip3_accounting_operation]; apply_manual_currency_exchange (boolean) [module: equip3_accounting_multicurrency]; manual_currency_exchange_rate (float) [module: equip3_accounting_multicurrency]; manual_currency_exchange_inverse_rate (float) [module: equip3_accounting_multicurrency]; type_curr (selection) [module: equip3_accounting_multicurrency]; name (char) [readonly] [module: allfresh_mod_account_move]; campaign_id (many2one) -> utm.campaign [module: utm]; source_id (many2one) -> utm.source [module: utm]; medium_id (many2one) -> utm.medium [module: utm]; activity_ids (one2many) -> mail.activity [module: mail]; activity_state (selection) [readonly] [compute: _compute_activity_state] [not stored] [module: mail]; activity_user_id (many2one) -> res.users [compute: <bound method Field._compute_related of account.internal.transfer.activity_user_id>] [not stored] [module: mail] [related: activity_ids.user_id] [inverse: <bound method Field._inverse_related of account.internal.transfer.activity_user_id>]; activity_type_id (many2one) -> mail.activity.type [compute: <bound method Field._compute_related of account.internal.transfer.activity_type_id>] [not stored] [module: mail] [related: activity_ids.activity_type_id] [inverse: <bound method Field._inverse_related of account.internal.transfer.activity_type_id>]; activity_type_icon (char) [readonly] [compute: <bound method Field._compute_related of account.internal.transfer.activity_type_icon>] [not stored] [module: mail] [related: activity_ids.icon]; activity_date_deadline (date) [readonly] [compute: _compute_activity_date_deadline] [not stored] [module: mail]; my_activity_date_deadline (date) [readonly] [compute: _compute_my_activity_date_deadline] [not stored] [module: mail]; activity_summary (char) [compute: <bound method Field._compute_related of account.internal.transfer.activity_summary>] [not stored] [module: mail] [related: activity_ids.summary] [inverse: <bound method Field._inverse_related of account.internal.transfer.activity_summary>]; activity_exception_decoration (selection) [readonly] [compute: _compute_activity_exception_type] [not stored] [module: mail]; activity_exception_icon (char) [readonly] [compute: _compute_activity_exception_type] [not stored] [module: mail]; message_is_follower (boolean) [readonly] [compute: _compute_is_follower] [not stored] [module: mail]; message_follower_ids (one2many) -> mail.followers [module: mail]; message_partner_ids (many2many) [readonly] -> res.partner [compute: _get_followers] [not stored] [module: mail]; message_channel_ids (many2many) [readonly] -> mail.channel [compute: _get_followers] [not stored] [module: mail]; message_ids (one2many) -> mail.message [module: mail]; message_unread (boolean) [readonly] [compute: _get_message_unread] [not stored] [module: mail]; message_unread_counter (integer) [readonly] [compute: _get_message_unread] [not stored] [module: mail]; message_needaction (boolean) [readonly] [compute: _get_message_needaction] [not stored] [module: mail]; message_needaction_counter (integer) [readonly] [compute: _get_message_needaction] [not stored] [module: mail]; message_has_error (boolean) [readonly] [compute: _compute_message_has_error] [not stored] [module: mail]; message_has_error_counter (integer) [readonly] [compute: _compute_message_has_error] [not stored] [module: mail]; message_attachment_count (integer) [readonly] [compute: _compute_message_attachment_count] [not stored] [module: mail]; message_main_attachment_id (many2one) -> ir.attachment [module: mail]; website_message_ids (one2many) -> mail.message [module: portal]; message_has_sms_error (boolean) [readonly] [compute: _compute_message_has_sms_error] [not stored] [module: sms]; access_url (char) [readonly] [compute: _compute_access_url] [not stored] [module: portal]; access_token (char) [module: portal]; access_warning (text) [readonly] [compute: _compute_access_warning] [not stored] [module: portal]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [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 indexes exist on res_company_sh_purchase_payment_report_wizard_rel? or What columns does res_company_sh_purchase_payment_report_wizard_rel have?

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


List all relational fields in product.warehouse.cost. or How does product.warehouse.cost relate to other models?

Response: The product.warehouse.cost model has 5 relational fields: product_id -> product.product; product_cost_line_ids -> product.warehouse.cost.line; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: product_cost_line_ids.