What are the available fields for credit.limit.approval? or What fields does credit.limit.approval have?

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


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

Response: The account_account_account_cash_flow_rel table has 2 columns and 2 foreign key relationships. It stores data related to account account account cash flow 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 relational structure of account.bank.statement.line. or How does account.bank.statement.line relate to other models?

Response: The account.bank.statement.line model has 133 relational fields: move_id -> account.move; statement_id -> account.bank.statement; foreign_currency_id -> res.currency; currency_id -> res.currency; partner_id -> res.partner; payment_ids -> account.payment; branch_id -> res.branch; pos_branch_id -> res.branch; voucher_id -> pos.voucher; pos_session_id -> pos.session; pos_statement_id -> pos.order; create_uid -> res.users; write_uid -> res.users; suitable_journal_ids -> account.journal; company_id -> res.company; user_id -> res.users; invoice_user_id -> res.users; preferred_payment_method_id -> account.payment.method; debit_origin_id -> account.move; debit_note_ids -> account.move; edi_document_ids -> account.edi.document; loan_line_id -> account.loan.line; loan_id -> account.loan; journal_bank_id -> account.journal; tax_payment_move_id -> account.move; asset_depreciation_ids -> account.asset.depreciation.line; transaction_ids -> payment.transaction; authorized_transaction_ids -> payment.transaction; purchase_vendor_bill_id -> purchase.bill.union; purchase_id -> purchase.order; sh_invoice_recurring_order_id -> invoice.recurring; period_id -> sh.account.period; fiscal_year -> sh.fiscal.year; stock_move_id -> stock.move; stock_valuation_layer_ids -> stock.valuation.layer; auto_reverse_journal_id -> account.journal; pos_order_ids -> pos.order; team_id -> crm.team; partner_shipping_id -> res.partner; consignment_pos_ids -> pos.order; l10n_id_attachment_id -> ir.attachment; landed_costs_ids -> stock.landed.cost; website_id -> website; discount_account_id -> account.account; warranty_reg_id -> product.warranty; related_project_id -> account.analytic.account; repair_ids -> repair.order; target_commission_id -> sh.target.commision; down_payment_purchase_id -> purchase.order; report_template_id1 -> ir.actions.report; report_template_id -> ir.actions.report; timesheet_ids -> account.analytic.line; approval_matrix_id -> approval.matrix.accounting; approved_matrix_ids -> approval.matrix.accounting.lines; approval_matrix_line_id -> approval.matrix.accounting.lines; analytic_group_ids -> account.analytic.tag; invoice_origin_id -> account.move; request_partner_id -> res.partner; journal_id -> account.journal; company_currency_id -> res.currency; line_ids -> account.move.line; commercial_partner_id -> res.partner; partner_bank_id -> res.partner.bank; payment_id -> account.payment; statement_line_id -> account.bank.statement.line; tax_cash_basis_rec_id -> account.partial.reconcile; tax_cash_basis_move_id -> account.move; reversed_entry_id -> account.move; reversal_move_id -> account.move; fiscal_position_id -> account.fiscal.position; invoice_payment_term_id -> account.payment.term; invoice_line_ids -> account.move.line; invoice_incoterm_id -> account.incoterms; invoice_vendor_bill_id -> account.move; invoice_cash_rounding_id -> account.cash.rounding; bank_partner_id -> res.partner; journal_entries_template -> account.move.template; analytic_tag_dynamic -> account.analytic.tag; approvers_ids -> res.users; approved_user_ids -> res.users; internal_tf_id -> account.internal.transfer; new_invoice_id -> account.move; account_asset_id -> account.asset.asset; customer_deposit_ids -> customer.deposit; vendor_deposit_ids -> vendor.deposit; nomor_seri -> account.efaktur; ebupot_id -> account.ebupot; nomor_seri_bupot -> account.ebupot; l10n_id_replace_invoice_id -> account.move; keterangan_tambahan -> account.keterangan.tambahan; signature_country_id -> res.country; signature_city_id -> res.country.city; currency_revaluation_id -> account.move; children_ids -> account.move; currency_revaluation_ref_id -> account.move; pettycash_id -> account.pettycash; sale_order_reference_id -> sale.order; filter_sale_order_reference_ids -> sale.order; exchange_id -> account.invoice.exchange; assembly_id -> assembly.production.record; stock_scrap_id -> stock.scrap.request; kitchen_id -> kitchen.production.record; purchase_order_id -> purchase.order; swo_ids -> service.work.order; finish_good_rework_id -> finish.good.rework; sale_order_ids -> sale.order; filter_sale_order_ids -> sale.order; purchase_order_ids -> purchase.order; filter_purchase_order_ids -> purchase.order; picking_ids -> stock.picking; filter_picking_ids -> stock.picking; cashback_line_ids -> cashback.line; so_cashback_id -> sale.order; return_picking_ids -> stock.picking; picking_id -> stock.picking; rma_id -> dev.rma.rma; account_invoice_ids -> account.invoice.exchange; pos_order_id -> pos.order; deposit_account_journal_id -> account.journal; create_from_session_id -> pos.session; inventory_id -> stock.inventory; campaign_id -> utm.campaign; source_id -> utm.source; medium_id -> utm.medium; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message. Many2many fields: payment_ids, suitable_journal_ids, transaction_ids, authorized_transaction_ids, analytic_group_ids, analytic_tag_dynamic, approvers_ids, approved_user_ids, customer_deposit_ids, vendor_deposit_ids, filter_sale_order_reference_ids, sale_order_ids, filter_sale_order_ids, purchase_order_ids, filter_purchase_order_ids, picking_ids, filter_picking_ids, return_picking_ids, account_invoice_ids, message_partner_ids, message_channel_ids. One2many fields: debit_note_ids, edi_document_ids, asset_depreciation_ids, stock_valuation_layer_ids, pos_order_ids, consignment_pos_ids, landed_costs_ids, repair_ids, timesheet_ids, approved_matrix_ids, line_ids, reversal_move_id, invoice_line_ids, children_ids, swo_ids, cashback_line_ids, activity_ids, message_follower_ids, message_ids, website_message_ids.


What are the available fields for approval.matrix.purchase.request? or Which fields are required in approval.matrix.purchase.request?

Response: The approval.matrix.purchase.request model has 48 fields. Field types distribution: char: 7, many2one: 11, float: 2, boolean: 7, one2many: 5, selection: 3, date: 2, many2many: 2, integer: 5, text: 1, datetime: 3. Computed fields: 26. Field details: name (char) [required] [module: equip3_purchase_operation]; company_id (many2one) [required] [readonly] -> res.company [module: equip3_purchase_operation]; branch_id (many2one) [required] -> res.branch [module: equip3_purchase_operation]; department_id (many2one) -> hr.department [module: equip3_purchase_operation]; minimum_amt (float) [required] [module: equip3_purchase_operation]; maximum_amt (float) [required] [module: equip3_purchase_operation]; is_purchase_request_department (boolean) [readonly] [compute: _compute_pr_department] [not stored] [module: equip3_purchase_operation]; approval_matrix_purchase_request_line_ids (one2many) -> approval.matrix.purchase.request.line [module: equip3_purchase_operation]; is_good_services_order (boolean) [readonly] [compute: _compute_is_good_services_order] [not stored] [module: equip3_purchase_operation]; order_type (selection) [module: equip3_purchase_asset]; 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.purchase.request.activity_user_id>] [not stored] [module: mail] [related: activity_ids.user_id] [inverse: <bound method Field._inverse_related of approval.matrix.purchase.request.activity_user_id>]; activity_type_id (many2one) -> mail.activity.type [compute: <bound method Field._compute_related of approval.matrix.purchase.request.activity_type_id>] [not stored] [module: mail] [related: activity_ids.activity_type_id] [inverse: <bound method Field._inverse_related of approval.matrix.purchase.request.activity_type_id>]; activity_type_icon (char) [readonly] [compute: <bound method Field._compute_related of approval.matrix.purchase.request.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.purchase.request.activity_summary>] [not stored] [module: mail] [related: activity_ids.summary] [inverse: <bound method Field._inverse_related of approval.matrix.purchase.request.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 columns have default values in product_public_category_product_template_rel? or Show me the column structure of product_public_category_product_template_rel.

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


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

Response: The reset_view_arch_wizard table has 8 columns and 4 foreign key relationships. It stores data related to reset view arch wizard in the system. The table has 1 indexes for performance optimization. Column types: integer: 5, character varying: 1, timestamp without time zone: 2. Nullable columns: 6, columns with defaults: 1.


What are the technical details of pos.order? or What methods are defined in pos.order original module?

Response: The pos.order model is defined in module: point_of_sale. It has 53 computed fields: config_id, invoice_group, picking_count, failed_pickings, sale_journal, session_move_id, is_invoiced, cashier, currency_rate, receivable_invoice_count, payment_paid, total_before_discount, total_discount, total_after_discount, total_after_discount_w_o_tax, pos_coupon_id, is_past_date, self_order_id, margin, is_paid_full, receipt_count, return_order_state, is_show_pos_payment, customer_deposit_amount, location_id, date_order_str, amount_sales, amount_discount, amount_payment, amount_ppn, amount_nett_sales, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, display_name, __last_update. Stored computed fields: sale_journal, cashier, currency_rate, is_past_date, margin, location_id. Related fields: config_id -> session_id.config_id, invoice_group -> config_id.module_account, sale_journal -> session_id.config_id.journal_id, session_move_id -> session_id.move_id, activity_user_id -> activity_ids.user_id, activity_type_id -> activity_ids.activity_type_id, activity_type_icon -> activity_ids.icon, activity_summary -> activity_ids.summary. Original module methods: _amount_line_tax, _order_fields, _payment_fields, _get_valid_session, _process_order, _process_payment_lines, _prepare_invoice_line, _get_pos_anglo_saxon_price_unit, _compute_is_invoiced, _compute_picking_count, _compute_currency_rate, _onchange_amount_all, _compute_batch_amount_all, _onchange_partner_id, unlink, create, _complete_values_from_session, write, action_stock_picking, action_view_invoice, _is_pos_order_paid, _get_rounded_amount, _create_invoice, action_pos_order_paid, _prepare_invoice_vals, action_pos_order_invoice, action_pos_order_cancel, create_from_ui, _create_order_picking, add_payment, _prepare_refund_values, refund, action_receipt_to_customer, remove_from_ui, search_paid_order_ids, _export_for_ui, export_for_ui.


Describe the account.equity.move model in Odoo. or What does the account.equity.move model represent?

Response: The account.equity.move model represents account.equity.move in the ERP system. It contains 14 fields and is used to manage account.equity.move data. Defined in module: equip3_accounting_reports. Key fields include: display_account, journal_ids, date_from, date_to, target_move, report_currency_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: Foreign keys in gamification_challenge_users_rel: gamification_challenge_id -> gamification_challenge.id [constraint: gamification_challenge_users_rel_gamification_challenge_id_fkey]; res_users_id -> res_users.id [constraint: gamification_challenge_users_rel_res_users_id_fkey]. Total foreign key relationships: 2. Referenced tables: res_users, gamification_challenge.


Which fields are required in assembly.safety.stock.line? or What computed fields exist in assembly.safety.stock.line?

Response: The assembly.safety.stock.line model has 10 fields. Field types distribution: many2one: 4, float: 1, integer: 1, char: 1, datetime: 3. Computed fields: 2. Field details: stock_id (many2one) [required] -> assembly.safety.stock [module: equip3_assembly_operations]; product_id (many2one) [required] -> product.product [module: equip3_assembly_operations]; product_qty (float) [required] [module: equip3_assembly_operations]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


Can you explain the purpose of target.activity.line.res? or How is target.activity.line.res used in the system?

Response: The target.activity.line.res model represents target.activity.line.res in the ERP system. It contains 13 fields and is used to manage target.activity.line.res data. Defined in module: equip3_crm_operation. Key fields include: activity_id, user_id, activity_type, activity_done, target_activity, date, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What operations can I perform on asp.asm.stock? or How to query asp.asm.stock data?

Response: To use the asp.asm.stock model, you need to provide values for required fields: warehouse_id, company_id. Readonly fields: inv_ref, state, company_id, branch_id, domain_warehouse_id, product_ids, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: inv_ref [readonly] [has_default]; state [readonly] [has_default] [no_copy]; warehouse_id [required] [has_states]; company_id [required] [readonly] [has_default] [has_states]; branch_id [readonly] [computed] [has_default] [no_copy]; domain_warehouse_id [readonly] [computed] [no_copy]; product_ids [readonly] [computed] [no_copy]; activity_state [readonly] [computed] [no_copy]; activity_user_id [computed] [no_copy]; activity_type_id [computed] [no_copy]; activity_type_icon [readonly] [computed] [no_copy]; activity_date_deadline [readonly] [computed] [no_copy]; my_activity_date_deadline [readonly] [computed] [no_copy]; activity_summary [computed] [no_copy]; activity_exception_decoration [readonly] [computed] [no_copy]; activity_exception_icon [readonly] [computed] [no_copy]; message_is_follower [readonly] [computed] [no_copy]; message_partner_ids [readonly] [computed] [no_copy]; message_channel_ids [readonly] [computed] [no_copy]; message_unread [readonly] [computed] [no_copy]; message_unread_counter [readonly] [computed] [no_copy]; message_needaction [readonly] [computed] [no_copy]; message_needaction_counter [readonly] [computed] [no_copy]; message_has_error [readonly] [computed] [no_copy]; message_has_error_counter [readonly] [computed] [no_copy]; message_attachment_count [readonly] [computed] [no_copy]; message_has_sms_error [readonly] [computed] [no_copy]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


What does the account.tax.report.wizard model represent? or What is the account.tax.report.wizard model?

Response: The account.tax.report.wizard model represents Tax Report in the ERP system. It contains 13 fields and is used to manage tax report data. Defined in module: accounting_pdf_reports. Key fields include: journal_ids, date_from, date_to, target_move, report_currency_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What computed fields exist in res.city? or Which fields are required in res.city?

Response: The res.city model has 11 fields. Field types distribution: char: 3, many2one: 4, integer: 1, datetime: 3. Computed fields: 2. Field details: name (char) [required] [module: base_address_city]; zipcode (char) [module: base_address_city]; country_id (many2one) [required] -> res.country [module: base_address_city]; state_id (many2one) -> res.country.state [module: base_address_city]; 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 mrp_bom_tools relate to other tables? or What tables are connected to mrp_bom_tools?

Response: Foreign keys in mrp_bom_tools: bom_id -> mrp_bom.id [constraint: mrp_bom_tools_bom_id_fkey]; company_id -> res_company.id [constraint: mrp_bom_tools_company_id_fkey]; create_uid -> res_users.id [constraint: mrp_bom_tools_create_uid_fkey]; operation_id -> mrp_routing_workcenter.id [constraint: mrp_bom_tools_operation_id_fkey]; operation_two_id -> mrp_bom_operation.id [constraint: mrp_bom_tools_operation_two_id_fkey]; product_id -> product_product.id [constraint: mrp_bom_tools_product_id_fkey]; uom_id -> uom_uom.id [constraint: mrp_bom_tools_uom_id_fkey]; workorder_id -> mrp_workorder.id [constraint: mrp_bom_tools_workorder_id_fkey]; write_uid -> res_users.id [constraint: mrp_bom_tools_write_uid_fkey]. Total foreign key relationships: 9. Referenced tables: product_product, mrp_routing_workcenter, res_company, mrp_workorder, res_users, mrp_bom, uom_uom, mrp_bom_operation.


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

Response: Foreign keys in res_users_rn_approval_matrix_line_rel: rn_approval_matrix_line_id -> rn_approval_matrix_line.id [constraint: res_users_rn_approval_matrix_li_rn_approval_matrix_line_id_fkey]; res_users_id -> res_users.id [constraint: res_users_rn_approval_matrix_line_rel_res_users_id_fkey]. Total foreign key relationships: 2. Referenced tables: rn_approval_matrix_line, res_users.


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

Response: Foreign keys in res_groups_report_rel: gid -> res_groups.id [constraint: res_groups_report_rel_gid_fkey]; uid -> ir_act_report_xml.id [constraint: res_groups_report_rel_uid_fkey]. Total foreign key relationships: 2. Referenced tables: ir_act_report_xml, res_groups.


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

Response: Foreign keys in account_journal_account_reconcile_model_template_rel: account_reconcile_model_template_id -> account_reconcile_model_template.id [constraint: account_journal_account_recon_account_reconcile_model_temp_fkey]; account_journal_id -> account_journal.id [constraint: account_journal_account_reconcile_mode_account_journal_id_fkey1]. Total foreign key relationships: 2. Referenced tables: account_reconcile_model_template, account_journal.


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

Response: The snailmail_letter_format_error table has 7 columns and 3 foreign key relationships. It stores data related to snailmail letter format error in the system. The table has 1 indexes for performance optimization. Column types: integer: 4, boolean: 1, timestamp without time zone: 2. Nullable columns: 6, columns with defaults: 1.


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

Response: Foreign keys in ir_ui_view: create_uid -> res_users.id [constraint: ir_ui_view_create_uid_fkey]; inherit_id -> ir_ui_view.id [constraint: ir_ui_view_inherit_id_fkey]; theme_template_id -> theme_ir_ui_view.id [constraint: ir_ui_view_theme_template_id_fkey]; website_id -> website.id [constraint: ir_ui_view_website_id_fkey]; write_uid -> res_users.id [constraint: ir_ui_view_write_uid_fkey]. Total foreign key relationships: 5. Referenced tables: website, ir_ui_view, theme_ir_ui_view, res_users.


Describe the crossovered.budget model in Odoo. or How is crossovered.budget used in the system?

Response: The crossovered.budget model represents Budget in the ERP system. It contains 45 fields and is used to manage budget data. Defined in module: om_account_budget. Key fields include: name, user_id, date_from, date_to, crossovered_budget_line, company_id, approval_matrix, request_partner_id, is_allowed_to_approval_matrix, approved_matrix_ids, approval_matrix_line_id, is_approve_button, currency_id, state, complete_name, parent_id, branch_id, is_parent_budget, state1, state2, account_tag_ids, date_today, is_use_theoretical_achievement, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

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


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

Response: The open_stock_series table has 23 columns and 5 foreign key relationships. It stores data related to open stock series in the system. The table has 1 indexes for performance optimization. Column types: integer: 14, character varying: 4, boolean: 1, date: 2, timestamp without time zone: 2. Nullable columns: 22, columns with defaults: 1.


How does wizard.report.menu.create relate to other models? or What one2many fields are in wizard.report.menu.create?

Response: The wizard.report.menu.create model has 3 relational fields: menu_id -> ir.ui.menu; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


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

Response: Foreign keys in utm_medium: create_uid -> res_users.id [constraint: utm_medium_create_uid_fkey]; write_uid -> res_users.id [constraint: utm_medium_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


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

Response: Columns in base_import_tests_models_preview: id (integer) [NOT NULL] [DEFAULT: nextval('base_import_tests_models_preview_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [COMMENT: Name]; somevalue (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Some Value]; othervalue (integer) [PRECISION: 32] [COMMENT: Other Variable]; 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.


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

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


What are common use cases for mail.thread.cc? or How do I use the mail.thread.cc model?

Response: To use the mail.thread.cc model, you need to provide values for required fields: none. Readonly fields: email_cc, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, __last_update. Field usage details: email_cc [readonly]; message_is_follower [readonly] [computed] [no_copy]; message_follower_ids [readonly] [no_copy]; message_partner_ids [readonly] [computed] [no_copy]; message_channel_ids [readonly] [computed] [no_copy]; message_ids [readonly] [no_copy]; message_unread [readonly] [computed] [no_copy]; message_unread_counter [readonly] [computed] [no_copy]; message_needaction [readonly] [computed] [no_copy]; message_needaction_counter [readonly] [computed] [no_copy]; message_has_error [readonly] [computed] [no_copy]; message_has_error_counter [readonly] [computed] [no_copy]; message_attachment_count [readonly] [computed] [no_copy]; message_main_attachment_id [readonly] [no_copy]; website_message_ids [readonly] [no_copy]; message_has_sms_error [readonly] [computed] [no_copy]; id [readonly]; display_name [readonly] [computed] [no_copy]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


Which fields in mass.editing.wizard are computed? or What are the technical details of mass.editing.wizard?

Response: The mass.editing.wizard model is defined in module: mass_editing. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: default_get, _prepare_fields, _insert_field_in_arch, _get_field_options, fields_view_get, _clean_check_company_field_domain, create, read, button_apply.


Describe the implementation of payment.voucher.matrix.reject. or What are the technical details of payment.voucher.matrix.reject?

Response: The payment.voucher.matrix.reject model is defined in module: equip3_accounting_operation. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: action_reject.


Show me the relational structure of list.top.product.compare. or What one2many fields are in list.top.product.compare?

Response: The list.top.product.compare model has 3 relational fields: top_id -> sh.tsp.top.selling.product.wizard; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


What are the available fields for snailmail.confirm? or What field types are used in snailmail.confirm?

Response: The snailmail.confirm model has 4 fields. Field types distribution: char: 2, integer: 1, datetime: 1. Computed fields: 2. Field details: model_name (char) [readonly] [module: snailmail]; 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 columns have default values in hr_departure_wizard? or What are the length constraints in hr_departure_wizard?

Response: Columns in hr_departure_wizard: id (integer) [NOT NULL] [DEFAULT: nextval('hr_departure_wizard_id_seq'::regclass)] [PRECISION: 32]; departure_reason (character varying) [COMMENT: Departure Reason]; departure_description (text) [COMMENT: Additional Information]; departure_date (date) [NOT NULL] [COMMENT: Departure Date]; employee_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Employee]; archive_private_address (boolean) [COMMENT: Archive Private Address]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 10. Statistics: 7 nullable, 1 with defaults, 0 with length constraints.


What does the journal.entry.report model represent? or What is the journal.entry.report model?

Response: The journal.entry.report model represents journal.entry.report in the ERP system. It contains 15 fields and is used to manage journal.entry.report data. Defined in module: equip3_accounting_reports. Key fields include: company_id, journal_ids, account_ids, display_account, target_move, date_from, date_to, move_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How many columns are in mail_activity_type_mail_template_rel? or What is the mail_activity_type_mail_template_rel table?

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


How do I use the res.branch model? or What fields are readonly in res.branch?

Response: To use the res.branch model, you need to provide values for required fields: name, company_id. Readonly fields: config_ids, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [required]; company_id [required]; config_ids [readonly] [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.


Show me the fields of approval.matrix.sale.reject. or What are the available fields for approval.matrix.sale.reject?

Response: The 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_operation]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


What models are connected to website.track? or How does website.track relate to other models?

Response: The website.track model has 3 relational fields: visitor_id -> website.visitor; page_id -> website.page; product_id -> product.product. Many2many fields: none. One2many fields: none.


What data can be stored in pos.payment.method? or Show me the fields of pos.payment.method.

Response: The pos.payment.method model has 54 fields. Field types distribution: char: 8, many2one: 10, boolean: 21, many2many: 3, selection: 5, float: 2, one2many: 1, integer: 1, datetime: 3. Computed fields: 7. Field details: name (char) [required] [module: point_of_sale]; receivable_account_id (many2one) [required] -> account.account [module: point_of_sale]; is_cash_count (boolean) [module: point_of_sale]; cash_journal_id (many2one) -> account.journal [module: point_of_sale]; split_transactions (boolean) [module: point_of_sale]; open_session_ids (many2many) [readonly] -> pos.session [compute: _compute_open_session_ids] [not stored] [module: point_of_sale]; config_ids (many2many) -> pos.config [module: point_of_sale]; company_id (many2one) -> res.company [module: point_of_sale]; use_payment_terminal (selection) [module: point_of_sale]; hide_use_payment_terminal (boolean) [readonly] [compute: _compute_hide_use_payment_terminal] [not stored] [module: point_of_sale]; active (boolean) [module: point_of_sale]; apply_charges (boolean) [module: equip3_pos_masterdata]; fees_amount (float) [module: equip3_pos_masterdata]; fees_type (selection) [module: equip3_pos_masterdata]; fees_product_id (many2one) -> product.product [module: equip3_pos_masterdata]; optional (boolean) [module: equip3_pos_masterdata]; shortcut_key (char) [module: equip3_pos_masterdata]; jr_use_for (boolean) [module: equip3_pos_masterdata]; fullfill_amount (boolean) [module: equip3_pos_masterdata]; shortcut_keyboard (char) [module: equip3_pos_masterdata]; cheque_bank_information (boolean) [module: equip3_pos_masterdata]; discount (boolean) [module: equip3_pos_masterdata]; discount_type (selection) [module: equip3_pos_masterdata]; discount_amount (float) [module: equip3_pos_masterdata]; discount_product_id (many2one) -> product.product [module: equip3_pos_masterdata]; is_bank (boolean) [module: equip3_pos_masterdata]; generate_invoice (boolean) [module: equip3_pos_masterdata]; invoice_partner_id (many2one) -> res.partner [module: equip3_pos_masterdata]; able_use_card (boolean) [module: equip3_pos_masterdata]; is_mdr (boolean) [module: equip3_pos_masterdata]; is_mdr_discount (boolean) [module: equip3_pos_masterdata]; mdr_paid_by (selection) [module: equip3_pos_masterdata]; mdr_intermediary_account_id (many2one) -> account.account [module: equip3_pos_masterdata]; mdr_ids (one2many) -> pos.payment.method.mdr [module: equip3_pos_masterdata]; is_receivables (boolean) [module: equip3_pos_masterdata]; account_journal_id (many2one) -> account.journal [module: equip3_pos_masterdata]; is_receivables_show (boolean) [readonly] [compute: _compute_is_receivables_show] [not stored] [module: equip3_pos_general]; is_deposit_payment (boolean) [module: equip3_pos_membership]; is_edc_bca (boolean) [module: equip3_pos_payment_edc]; is_edc_manual_input (boolean) [module: equip3_pos_payment_edc]; edc_port (char) [module: equip3_pos_payment_edc]; trans_type (selection) [module: equip3_pos_payment_edc]; trans_type_code (char) [readonly] [compute: _compute_trans_type_code] [not stored] [module: equip3_pos_payment_edc]; is_payment_edc (boolean) [readonly] [compute: _compute_is_payment_edc] [stored] [module: equip3_pos_payment_edc]; payment_edc_url (char) [module: equip3_pos_payment_edc]; installment_tenor_ids (many2many) -> pos.payment.installment.tenor [module: equip3_pos_payment_edc]; installment_plan (char) [module: equip3_pos_payment_edc]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


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

Response: Foreign keys in crm_phonecall2phonecall: create_uid -> res_users.id [constraint: crm_phonecall2phonecall_create_uid_fkey]; partner_id -> res_partner.id [constraint: crm_phonecall2phonecall_partner_id_fkey]; team_id -> crm_team.id [constraint: crm_phonecall2phonecall_team_id_fkey]; user_id -> res_users.id [constraint: crm_phonecall2phonecall_user_id_fkey]; write_uid -> res_users.id [constraint: crm_phonecall2phonecall_write_uid_fkey]. Total foreign key relationships: 5. Referenced tables: res_partner, crm_team, res_users.


What operations can I perform on ir.actions.client? or How to work with ir.actions.client fields?

Response: To use the ir.actions.client model, you need to provide values for required fields: name, type, tag, context, binding_type. Readonly fields: params_store, xml_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [required]; type [required] [has_default]; tag [required]; context [required] [has_default]; params [computed] [no_copy]; params_store [readonly]; xml_id [readonly] [computed] [no_copy]; binding_type [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 are common use cases for crm.lead.scoring.frequency? or How to work with crm.lead.scoring.frequency fields?

Response: To use the crm.lead.scoring.frequency model, you need to provide values for required fields: none. Readonly fields: variable, value, won_count, lost_count, team_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: variable [readonly]; value [readonly]; won_count [readonly]; lost_count [readonly]; team_id [readonly]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


What does the ir.qweb.field.qweb model represent? or Can you explain the purpose of ir.qweb.field.qweb?

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


Describe the pos.report.journal model in Odoo. or What is the pos.report.journal model?

Response: The pos.report.journal model represents POS Report Journal in the ERP system. It contains 7 fields and is used to manage pos report journal data. Defined in module: equip3_pos_report. Key fields include: id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: The sh_product_barcode_mobile_wizard table has 10 columns and 3 foreign key relationships. It stores data related to sh product barcode mobile wizard in the system. The table has 1 indexes for performance optimization. Column types: integer: 4, character varying: 3, text: 1, timestamp without time zone: 2. Nullable columns: 8, columns with defaults: 1.


Which columns are nullable in mailing_list_merge? or Describe the columns of mailing_list_merge.

Response: Columns in mailing_list_merge: id (integer) [NOT NULL] [DEFAULT: nextval('mailing_list_merge_id_seq'::regclass)] [PRECISION: 32]; dest_list_id (integer) [PRECISION: 32] [COMMENT: Destination Mailing List]; merge_options (character varying) [NOT NULL] [COMMENT: Merge Option]; new_list_name (character varying) [COMMENT: New Mailing List Name]; archive_src_lists (boolean) [COMMENT: Archive source mailing lists]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 9. Statistics: 7 nullable, 1 with defaults, 0 with length constraints.


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

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


What are the relationships in mrp.bom.tools? or Show me the relational structure of mrp.bom.tools.

Response: The mrp.bom.tools model has 11 relational fields: bom_id -> mrp.bom; company_id -> res.company; workorder_id -> mrp.workorder; product_id -> product.product; uom_id -> uom.uom; operation_id -> mrp.routing.workcenter; allowed_operation_ids -> mrp.routing.workcenter; operation_two_ids -> mrp.bom.operation; operation_two_id -> mrp.bom.operation; create_uid -> res.users; write_uid -> res.users. Many2many fields: allowed_operation_ids, operation_two_ids. One2many fields: none.


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

Response: Foreign keys in report_extra_content: company_id -> res_company.id [constraint: report_extra_content_company_id_fkey]; create_uid -> res_users.id [constraint: report_extra_content_create_uid_fkey]; model_id -> ir_model.id [constraint: report_extra_content_model_id_fkey]; write_uid -> res_users.id [constraint: report_extra_content_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: ir_model, res_users, res_company.


What fields are available in acrux_chat_pop_message? or What data types are used in acrux_chat_pop_message?

Response: Columns in acrux_chat_pop_message: id (integer) [NOT NULL] [DEFAULT: nextval('acrux_chat_pop_message_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [COMMENT: Message]; info (text) [COMMENT: Detail]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 7. Statistics: 6 nullable, 1 with defaults, 0 with length constraints.


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

Response: Foreign keys in product_brand_relation: brand_id -> product_brand.id [constraint: product_brand_relation_brand_id_fkey]; tmpl_id -> product_template.id [constraint: product_brand_relation_tmpl_id_fkey]. Total foreign key relationships: 2. Referenced tables: product_brand, product_template.


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

Response: The report_reordering_view table has 12 columns and 5 foreign key relationships. It stores data related to report reordering view in the system. The table has 1 indexes for performance optimization. Column types: integer: 6, character varying: 2, double precision: 2, timestamp without time zone: 2. Nullable columns: 11, columns with defaults: 1.


How to create records in res.partner.rfm.segment.history? or What are common use cases for res.partner.rfm.segment.history?

Response: To use the res.partner.rfm.segment.history 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 relationships exist for mrp_quality_alert_report_res_users_rel? or Show me the foreign key constraints of mrp_quality_alert_report_res_users_rel.

Response: Foreign keys in mrp_quality_alert_report_res_users_rel: mrp_quality_alert_report_id -> mrp_quality_alert_report.id [constraint: mrp_quality_alert_report_res_u_mrp_quality_alert_report_id_fkey]; res_users_id -> res_users.id [constraint: mrp_quality_alert_report_res_users_rel_res_users_id_fkey]. Total foreign key relationships: 2. Referenced tables: mrp_quality_alert_report, res_users.


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

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


What fields are readonly in portal.share? or What business logic is in portal.share?

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


How to query rma.report data? or What are common use cases for rma.report?

Response: To use the rma.report model, you need to provide values for required fields: none. Readonly fields: name, date, deadline_date, user_id, team_id, partner_id, company_id, state, product_id, product_tmpl_id, categ_id, replace_product_id, replace_qty, country_id, commercial_partner_id, id, display_name, __last_update. Field usage details: name [readonly]; date [readonly]; deadline_date [readonly]; user_id [readonly]; team_id [readonly]; partner_id [readonly]; company_id [readonly]; state [readonly] [no_copy]; product_id [readonly]; product_tmpl_id [readonly]; categ_id [readonly]; replace_product_id [readonly]; replace_qty [readonly]; country_id [readonly]; commercial_partner_id [readonly]; id [readonly]; display_name [readonly] [computed] [no_copy]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


Which fields are stored computed fields in account.tax.repartition.line.template? or Describe the implementation of account.tax.repartition.line.template.

Response: The account.tax.repartition.line.template model is defined in module: account. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: create, _convert_tag_syntax_to_orm, validate_tax_template_link, validate_tags, get_repartition_line_create_vals.


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

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


What are the relationships in sale.order.cancel? or List all relational fields in sale.order.cancel.

Response: The sale.order.cancel model has 3 relational fields: order_id -> sale.order; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


What one2many fields are in sms.cancel? or List all relational fields in sms.cancel.

Response: The sms.cancel model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


Describe the pos.promotion.specific.product model in Odoo. or What does the pos.promotion.specific.product model represent?

Response: The pos.promotion.specific.product model represents Promotion for specific product in the ERP system. It contains 13 fields and is used to manage promotion for specific product data. Defined in module: equip3_pos_masterdata. Key fields include: active, type_apply, qty_free, product_id, product_ids, promotion_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What one2many fields are in portal.mixin? or Describe the many2many relations for portal.mixin.

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


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

Response: Foreign keys in account_full_reconcile: create_uid -> res_users.id [constraint: account_full_reconcile_create_uid_fkey]; exchange_move_id -> account_move.id [constraint: account_full_reconcile_exchange_move_id_fkey]; write_uid -> res_users.id [constraint: account_full_reconcile_write_uid_fkey]. Total foreign key relationships: 3. Referenced tables: res_users, account_move.


Which fields in account.financial.year.op are computed? or What is the module hierarchy for account.financial.year.op?

Response: The account.financial.year.op model is defined in module: account. It has 6 computed fields: opening_move_posted, opening_date, fiscalyear_last_day, fiscalyear_last_month, display_name, __last_update. Stored computed fields: none. Related fields: opening_date -> company_id.account_opening_date, fiscalyear_last_day -> company_id.fiscalyear_last_day, fiscalyear_last_month -> company_id.fiscalyear_last_month. Original module methods: _compute_opening_move_posted, _check_fiscalyear, write, action_save_onboarding_fiscal_year.


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

Response: The account_reconcile_model_line_template table has 12 columns and 4 foreign key relationships. It stores data related to account reconcile model line template in the system. The table has 1 indexes for performance optimization. Column types: integer: 6, character varying: 3, boolean: 1, timestamp without time zone: 2. Nullable columns: 9, columns with defaults: 1.


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

Response: The pos_voucher table has 32 columns and 10 foreign key relationships. It stores data related to pos voucher in the system. The table has 1 indexes for performance optimization. Column types: integer: 12, boolean: 3, character varying: 9, timestamp without time zone: 5, double precision: 3. Nullable columns: 29, columns with defaults: 1.


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

Response: Columns in pos_receipt_template: id (integer) [NOT NULL] [DEFAULT: nextval('pos_receipt_template_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [COMMENT: Name]; is_default (boolean) [COMMENT: Default Receipt]; size (character varying) [COMMENT: Receipt Size]; custom_size (double precision) [PRECISION: 53] [COMMENT: Custom Size]; is_need_header (boolean) [COMMENT: Need Header]; receipt_header_text (text) [COMMENT: Custom Header Text]; is_need_footer (boolean) [COMMENT: Need Footer]; receipt_footer_text (text) [COMMENT: Custom Footer Text]; is_receipt_disc_in_orderline (boolean) [COMMENT: Discount in orderline]; is_receipt_tax_include_orderline (boolean) [COMMENT: Product price Include taxes]; is_receipt_serial_lot_info (boolean) [COMMENT: Include serial or lot number]; is_receipt_savings_summary (boolean) [COMMENT: Include savings summary]; savings_summary_text (text) [COMMENT: Savings summary Text]; is_receipt_product_code (boolean) [COMMENT: Include Product Code]; company_id (integer) [PRECISION: 32] [COMMENT: Company]; voucher_receipt_display (character varying) [COMMENT: Voucher Receipt Display]; generate_voucher_id (integer) [PRECISION: 32] [COMMENT: Generate Voucher]; is_voucher_receipt (boolean) [COMMENT: Is Voucher Receipt]; is_show_discount_detail (boolean) [COMMENT: Show Discount Detail]; 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_receipt_member_info (boolean) [COMMENT: Loyalty member information]. Total columns: 25. Statistics: 24 nullable, 1 with defaults, 0 with length constraints.


What business logic is in payment.link.wizard? or How to create records in payment.link.wizard?

Response: To use the payment.link.wizard model, you need to provide values for required fields: res_model, res_id, amount. Readonly fields: partner_email, link, access_token, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: res_model [required]; res_id [required]; amount [required]; partner_email [readonly] [computed] [no_copy]; link [readonly] [computed] [no_copy]; access_token [readonly] [computed] [no_copy]; company_id [readonly] [computed] [no_copy]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


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

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


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

Response: The group_card_pos_payment_method_mdr_rel table has 2 columns and 2 foreign key relationships. It stores data related to group card pos payment method mdr rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


What data can be stored in mrp.workcenter.group? or What field types are used in mrp.workcenter.group?

Response: The mrp.workcenter.group model has 28 fields. Field types distribution: char: 3, many2one: 5, many2many: 3, boolean: 6, one2many: 3, integer: 5, datetime: 3. Computed fields: 14. Field details: code (char) [required] [module: equip3_manuf_masterdata]; name (char) [required] [module: equip3_manuf_masterdata]; company_id (many2one) [required] -> res.company [module: equip3_manuf_masterdata]; branch_id (many2one) -> res.branch [module: equip3_manuf_masterdata]; workcenter_ids (many2many) -> mrp.workcenter [module: equip3_manuf_masterdata]; is_branch_required (boolean) [readonly] [compute: <bound method Field._compute_related of mrp.workcenter.group.is_branch_required>] [not stored] [module: equip3_manuf_masterdata] [related: company_id.show_branch]; message_is_follower (boolean) [readonly] [compute: _compute_is_follower] [not stored] [module: mail]; message_follower_ids (one2many) -> mail.followers [module: mail]; message_partner_ids (many2many) [readonly] -> res.partner [compute: _get_followers] [not stored] [module: mail]; message_channel_ids (many2many) [readonly] -> mail.channel [compute: _get_followers] [not stored] [module: mail]; message_ids (one2many) -> mail.message [module: mail]; message_unread (boolean) [readonly] [compute: _get_message_unread] [not stored] [module: mail]; message_unread_counter (integer) [readonly] [compute: _get_message_unread] [not stored] [module: mail]; message_needaction (boolean) [readonly] [compute: _get_message_needaction] [not stored] [module: mail]; message_needaction_counter (integer) [readonly] [compute: _get_message_needaction] [not stored] [module: mail]; message_has_error (boolean) [readonly] [compute: _compute_message_has_error] [not stored] [module: mail]; message_has_error_counter (integer) [readonly] [compute: _compute_message_has_error] [not stored] [module: mail]; message_attachment_count (integer) [readonly] [compute: _compute_message_attachment_count] [not stored] [module: mail]; message_main_attachment_id (many2one) -> ir.attachment [module: mail]; website_message_ids (one2many) -> mail.message [module: portal]; message_has_sms_error (boolean) [readonly] [compute: _compute_message_has_sms_error] [not stored] [module: sms]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


How is purchase.request.wizard implemented technically? or What modules define purchase.request.wizard?

Response: The purchase.request.wizard model is defined in module: equip3_inventory_operation. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: create_pr.


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

Response: The qiscus.template model represents qiscus.template in the ERP system. It contains 37 fields and is used to manage qiscus.template data. Defined in module: equip3_crm_whatsapp. Key fields include: name, namespace, qiscus_template_id, content_ids, connector_id, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: Foreign keys in res_currency_rate: company_id -> res_company.id [constraint: res_currency_rate_company_id_fkey]; create_uid -> res_users.id [constraint: res_currency_rate_create_uid_fkey]; currency_id -> res_currency.id [constraint: res_currency_rate_currency_id_fkey]; write_uid -> res_users.id [constraint: res_currency_rate_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: res_currency, res_users, res_company.


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

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


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

Response: Columns in promotion_multi_by_product_rel: multi_by_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.


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

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


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

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


What is the customer_deposit table? or How many columns are in customer_deposit?

Response: The customer_deposit table has 36 columns and 17 foreign key relationships. It stores data related to customer deposit in the system. The table has 2 indexes for performance optimization. Column types: integer: 21, character varying: 5, boolean: 3, numeric: 3, timestamp without time zone: 3, double precision: 1. Nullable columns: 35, columns with defaults: 1.


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

Response: Foreign keys in stock_move_analytic_rel: move_id -> account_analytic_tag.id [constraint: stock_move_analytic_rel_move_id_fkey]; tag_id -> stock_move.id [constraint: stock_move_analytic_rel_tag_id_fkey]. Total foreign key relationships: 2. Referenced tables: stock_move, account_analytic_tag.


Tell me about the account.pettycash model. or What is the account.pettycash model?

Response: The account.pettycash model represents Account Petty Cash in the ERP system. It contains 65 fields and is used to manage account petty cash data. Defined in module: equip3_accounting_pettycash. Key fields include: replenish_interval, times, replenish_date, replenish_date_2, replenish_week, replenish_intervals, auto_replenish, cash_journal, number, name, custodian, main_cash_account_id, journal, amount, balance, virtual_balance, company_id, branch_id, effective_date, create_uid, create_date, state, move_id, voucher_id, paid_voucher_ids, is_custodian_user, custodian_partner, is_replenished, next_execute_date, campaign_id, source_id, medium_id, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, access_url, access_token, access_warning, id, display_name, write_uid, write_date, __last_update.


What are the available fields for order.stage? or Show me the fields of order.stage.

Response: The order.stage model has 15 fields. Field types distribution: char: 2, text: 1, integer: 2, many2many: 1, selection: 1, boolean: 1, datetime: 5, many2one: 2. Computed fields: 2. Field details: name (char) [required] [module: pragmatic_configurable_order_stages]; description (text) [module: pragmatic_configurable_order_stages]; sequence (integer) [module: pragmatic_configurable_order_stages]; warehouse_ids (many2many) -> stock.warehouse [module: pragmatic_configurable_order_stages]; action_type (selection) [module: pragmatic_configurable_order_stages]; is_hidden (boolean) [module: pragmatic_configurable_order_stages]; planned_date (datetime) [module: pragmatic_configurable_order_stages]; actual_date (datetime) [module: pragmatic_configurable_order_stages]; 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 purchase_request_warning_line. or How does purchase_request_warning_line relate to other tables?

Response: Foreign keys in purchase_request_warning_line: create_uid -> res_users.id [constraint: purchase_request_warning_line_create_uid_fkey]; product_id -> product_product.id [constraint: purchase_request_warning_line_product_id_fkey]; warning_id -> purchase_request_warning.id [constraint: purchase_request_warning_line_warning_id_fkey]; write_uid -> res_users.id [constraint: purchase_request_warning_line_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: product_product, purchase_request_warning, res_users.


Tell me about the free_product_lines table. or What is stored in free_product_lines?

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


What is the sale.summary.commission.report model? or How is sale.summary.commission.report used in the system?

Response: The sale.summary.commission.report model represents sale.summary.commission.report in the ERP system. It contains 13 fields and is used to manage sale.summary.commission.report data. Defined in module: equip3_sale_team_commission. Key fields include: start_date, end_date, sales_persons, commision_type, company_ids, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How does queue.jobs.kill relate to other models? or What one2many fields are in queue.jobs.kill?

Response: The queue.jobs.kill model has 3 relational fields: job_ids -> queue.job; create_uid -> res.users; write_uid -> res.users. Many2many fields: job_ids. One2many fields: none.


Show me the fields of l10n_id_efaktur.efaktur.range. or What computed fields exist in l10n_id_efaktur.efaktur.range?

Response: The l10n_id_efaktur.efaktur.range model has 11 fields. Field types distribution: many2one: 3, char: 3, integer: 2, datetime: 3. Computed fields: 5. Field details: company_id (many2one) [required] -> res.company [module: l10n_id_efaktur]; max (char) [compute: _compute_default] [stored] [module: l10n_id_efaktur]; min (char) [compute: _compute_default] [stored] [module: l10n_id_efaktur]; available (integer) [readonly] [compute: _compute_available] [stored] [module: l10n_id_efaktur]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


How does report.stock.demand relate to other models? or Show me the relational structure of report.stock.demand.

Response: The report.stock.demand model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


What one2many fields are in product.attribute? or What are the relationships in product.attribute?

Response: The product.attribute model has 6 relational fields: value_ids -> product.attribute.value; attribute_line_ids -> product.template.attribute.line; product_tmpl_ids -> product.template; product_brand_ids -> product.brand; create_uid -> res.users; write_uid -> res.users. Many2many fields: product_tmpl_ids, product_brand_ids. One2many fields: value_ids, attribute_line_ids.


What fields does queue.requeue.job have? or List all fields in the queue.requeue.job model.

Response: The queue.requeue.job model has 8 fields. Field types distribution: many2many: 1, integer: 1, char: 1, many2one: 2, datetime: 3. Computed fields: 2. Field details: job_ids (many2many) -> queue.job [module: queue_job]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


How to create records in whatsapp.template.message.variable? or What fields are readonly in whatsapp.template.message.variable?

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


What are the available fields for stock.track.confirmation? or What field types are used in stock.track.confirmation?

Response: The stock.track.confirmation model has 9 fields. Field types distribution: one2many: 1, many2one: 3, integer: 1, char: 1, datetime: 3. Computed fields: 2. Field details: tracking_line_ids (one2many) -> stock.track.line [module: stock]; inventory_id (many2one) -> stock.inventory [module: stock]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


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

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


Can you explain the purpose of full.inv.adjustment.import? or How is full.inv.adjustment.import used in the system?

Response: The full.inv.adjustment.import model represents Full Inv Adjustment Import in the ERP system. It contains 13 fields and is used to manage full inv adjustment import data. Defined in module: equip3_inventory_control. Key fields include: import_type, import_file, import_name, export_file, export_name, is_export, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Show me the fields of stock.landed.cost. or What field types are used in stock.landed.cost?

Response: The stock.landed.cost model has 53 fields. Field types distribution: char: 6, date: 3, many2many: 6, one2many: 7, text: 1, monetary: 1, selection: 6, many2one: 10, boolean: 5, integer: 5, datetime: 3. Computed fields: 27. Field details: name (char) [readonly] [module: stock_landed_costs]; date (date) [required] [module: stock_landed_costs]; picking_ids (many2many) -> stock.picking [module: stock_landed_costs]; allowed_picking_ids (many2many) [readonly] -> stock.picking [compute: _compute_allowed_picking_ids] [not stored] [module: stock_landed_costs]; cost_lines (one2many) -> stock.landed.cost.lines [module: stock_landed_costs]; valuation_adjustment_lines (one2many) -> stock.valuation.adjustment.lines [module: stock_landed_costs]; description (text) [module: stock_landed_costs]; amount_total (monetary) [readonly] [compute: _compute_total_amount] [stored] [module: stock_landed_costs]; state (selection) [readonly] [module: stock_landed_costs]; account_move_id (many2one) [readonly] -> account.move [module: stock_landed_costs]; account_journal_id (many2one) [required] -> account.journal [module: stock_landed_costs]; company_id (many2one) [readonly] -> res.company [compute: <bound method Field._compute_related of stock.landed.cost.company_id>] [not stored] [module: stock_landed_costs] [related: account_journal_id.company_id]; stock_valuation_layer_ids (one2many) -> stock.valuation.layer [module: stock_landed_costs]; vendor_bill_id (many2one) -> account.move [module: stock_landed_costs]; currency_id (many2one) [readonly] -> res.currency [compute: <bound method Field._compute_related of stock.landed.cost.currency_id>] [not stored] [module: stock_landed_costs] [related: company_id.currency_id]; target_model (selection) [required] [module: mrp_landed_costs]; mrp_production_ids (many2many) -> mrp.production [module: mrp_landed_costs]; allowed_mrp_production_ids (many2many) [readonly] -> mrp.production [compute: _compute_allowed_mrp_production_ids] [not stored] [module: mrp_landed_costs]; picking_type_id (selection) [required] [module: equip3_inventory_operation]; vendor_bill (selection) [required] [module: equip3_inventory_operation]; new_name (char) [module: equip3_accounting_reports]; 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 stock.landed.cost.activity_user_id>] [not stored] [module: mail] [related: activity_ids.user_id] [inverse: <bound method Field._inverse_related of stock.landed.cost.activity_user_id>]; activity_type_id (many2one) -> mail.activity.type [compute: <bound method Field._compute_related of stock.landed.cost.activity_type_id>] [not stored] [module: mail] [related: activity_ids.activity_type_id] [inverse: <bound method Field._inverse_related of stock.landed.cost.activity_type_id>]; activity_type_icon (char) [readonly] [compute: <bound method Field._compute_related of stock.landed.cost.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 stock.landed.cost.activity_summary>] [not stored] [module: mail] [related: activity_ids.summary] [inverse: <bound method Field._inverse_related of stock.landed.cost.activity_summary>]; activity_exception_decoration (selection) [readonly] [compute: _compute_activity_exception_type] [not stored] [module: mail]; activity_exception_icon (char) [readonly] [compute: _compute_activity_exception_type] [not stored] [module: mail]; message_is_follower (boolean) [readonly] [compute: _compute_is_follower] [not stored] [module: mail]; message_follower_ids (one2many) -> mail.followers [module: mail]; message_partner_ids (many2many) [readonly] -> res.partner [compute: _get_followers] [not stored] [module: mail]; message_channel_ids (many2many) [readonly] -> mail.channel [compute: _get_followers] [not stored] [module: mail]; message_ids (one2many) -> mail.message [module: mail]; message_unread (boolean) [readonly] [compute: _get_message_unread] [not stored] [module: mail]; message_unread_counter (integer) [readonly] [compute: _get_message_unread] [not stored] [module: mail]; message_needaction (boolean) [readonly] [compute: _get_message_needaction] [not stored] [module: mail]; message_needaction_counter (integer) [readonly] [compute: _get_message_needaction] [not stored] [module: mail]; message_has_error (boolean) [readonly] [compute: _compute_message_has_error] [not stored] [module: mail]; message_has_error_counter (integer) [readonly] [compute: _compute_message_has_error] [not stored] [module: mail]; message_attachment_count (integer) [readonly] [compute: _compute_message_attachment_count] [not stored] [module: mail]; message_main_attachment_id (many2one) -> ir.attachment [module: mail]; website_message_ids (one2many) -> mail.message [module: portal]; message_has_sms_error (boolean) [readonly] [compute: _compute_message_has_sms_error] [not stored] [module: sms]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


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

Response: Foreign keys in approved_users_res_patner_rel: app_mat_id -> approval_matrix_vendor_line.id [constraint: approved_users_res_patner_rel_app_mat_id_fkey]; user_id -> res_users.id [constraint: approved_users_res_patner_rel_user_id_fkey]. Total foreign key relationships: 2. Referenced tables: approval_matrix_vendor_line, res_users.


List all fields in the account.payment.term.line model. or What computed fields exist in account.payment.term.line?

Response: The account.payment.term.line model has 14 fields. Field types distribution: selection: 2, float: 1, integer: 4, many2one: 3, char: 1, datetime: 3. Computed fields: 2. Field details: value (selection) [required] [module: account]; value_amount (float) [module: account]; days (integer) [required] [module: account]; day_of_the_month (integer) [module: account]; option (selection) [required] [module: account]; payment_id (many2one) [required] -> account.payment.term [module: account]; sequence (integer) [module: account]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


Which fields in cust.deposit.amount.wizard are computed? or What are the technical details of cust.deposit.amount.wizard?

Response: The cust.deposit.amount.wizard model is defined in module: equip3_accounting_deposit. It has 4 computed fields: final_amount, final_remaining_amount, display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: default_get, _compute_amount_adding_deposit, action_request_for_approval, action_approve, action_reject, action_confirm.


Describe the field structure of report.reordering.view. or Which fields are required in report.reordering.view?

Response: The report.reordering.view model has 14 fields. Field types distribution: char: 3, many2one: 5, float: 2, integer: 1, datetime: 3. Computed fields: 2. Field details: barcode (char) [module: allfresh_mod_report_reordering]; product_id (many2one) -> product.product [module: allfresh_mod_report_reordering]; product_name (char) [module: allfresh_mod_report_reordering]; location_id (many2one) -> stock.location [module: allfresh_mod_report_reordering]; on_hand_qty (float) [readonly] [module: allfresh_mod_report_reordering]; order_qty (float) [module: allfresh_mod_report_reordering]; wizard_id (many2one) -> report.reordering [module: allfresh_mod_report_reordering]; 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 modules define report.point_of_sale.report_saledetails? or What are the technical details of report.point_of_sale.report_saledetails?

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


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

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


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

Response: The account_payment_term table has 15 columns and 6 foreign key relationships. It stores data related to account payment term in the system. The table has 2 indexes for performance optimization. Column types: integer: 8, character varying: 2, boolean: 1, text: 1, timestamp without time zone: 2, numeric: 1. Nullable columns: 12, columns with defaults: 1.


What fields does res.partner.rfm.segment.history have? or List all fields in the res.partner.rfm.segment.history model.

Response: The res.partner.rfm.segment.history model has 16 fields. Field types distribution: many2one: 7, date: 1, integer: 4, char: 1, datetime: 3. Computed fields: 2. Field details: partner_id (many2one) -> res.partner [module: setu_rfm_analysis]; history_date (date) [module: setu_rfm_analysis]; old_rfm_segment_id (many2one) -> setu.rfm.segment [module: setu_rfm_analysis]; new_rfm_segment_id (many2one) -> setu.rfm.segment [module: setu_rfm_analysis]; old_rfm_score_id (many2one) -> setu.rfm.score [module: setu_rfm_analysis]; new_rfm_score_id (many2one) -> setu.rfm.score [module: setu_rfm_analysis]; old_segment_rank (integer) [module: setu_rfm_analysis]; new_segment_rank (integer) [module: setu_rfm_analysis]; engagement_direction (integer) [module: setu_rfm_analysis]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


Can you explain the purpose of base.import.module? or What does the base.import.module model represent?

Response: The base.import.module model represents Import Module in the ERP system. It contains 11 fields and is used to manage import module data. Defined in module: base_import_module. Key fields include: module_file, state, import_message, force, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: Columns in bve_view: id (integer) [NOT NULL] [DEFAULT: nextval('bve_view_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [NOT NULL] [COMMENT: Name]; model_name (character varying) [COMMENT: Model Name]; note (text) [COMMENT: Notes]; state (character varying) [COMMENT: State]; action_id (integer) [PRECISION: 32] [COMMENT: Action]; view_id (integer) [PRECISION: 32] [COMMENT: View]; over_condition (text) [COMMENT: Over Condition]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 12. Statistics: 10 nullable, 1 with defaults, 0 with length constraints.


How do I use the mail.message model? or What business logic is in mail.message?

Response: To use the mail.message model, you need to provide values for required fields: message_type. Readonly fields: description, needaction, has_error, starred, message_id, need_moderation, rating_value, has_sms_error, snailmail_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: description [readonly] [computed] [no_copy]; author_avatar [computed] [no_copy]; needaction [readonly] [computed] [no_copy]; has_error [readonly] [computed] [no_copy]; starred [readonly] [computed] [no_copy]; message_id [readonly] [no_copy]; need_moderation [readonly] [computed] [no_copy]; rating_value [readonly] [computed] [no_copy]; has_sms_error [readonly] [computed] [no_copy]; snailmail_error [readonly] [computed] [no_copy]; message_type [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 is stored in bo_approval_matrix_sale_reject? or How many columns are in bo_approval_matrix_sale_reject?

Response: The bo_approval_matrix_sale_reject table has 6 columns and 2 foreign key relationships. It stores data related to bo approval matrix sale reject in the system. The table has 1 indexes for performance optimization. Column types: integer: 3, text: 1, timestamp without time zone: 2. Nullable columns: 5, columns with defaults: 1.


What one2many fields are in itr.approval.matrix.line? or What foreign keys exist in itr.approval.matrix.line?

Response: The itr.approval.matrix.line model has 13 relational fields: user_ids -> res.users; itr_approval_matrix -> itr.approval.matrix; approved_users -> res.users; last_approved -> res.users; transfer_id -> internal.transfer; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: user_ids, approved_users, message_partner_ids, message_channel_ids. One2many fields: message_follower_ids, message_ids, website_message_ids.


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

Response: Columns in stock_life: id (integer) [NOT NULL] [DEFAULT: nextval('stock_life_id_seq'::regclass)] [PRECISION: 32]; minimum_days (integer) [PRECISION: 32] [COMMENT: Minimum Expiry Days Prior]; is_customer (integer) [PRECISION: 32] [COMMENT: Customers]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 7. Statistics: 6 nullable, 1 with defaults, 0 with length constraints.


What are common use cases for kpi.constant? or What operations can I perform on kpi.constant?

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


What are the technical details of stock.quantity.history? or What is the module hierarchy for stock.quantity.history?

Response: The stock.quantity.history model is defined in module: stock. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: open_at_date.


What methods are defined in account.payment.term.line original module? or What are the technical details of account.payment.term.line?

Response: The account.payment.term.line model is defined in module: account. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: _check_percent, _check_days, _onchange_option.


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

Response: Foreign keys in user_warehouse_new_rel: user_id -> stock_warehouse.id [constraint: user_warehouse_new_rel_user_id_fkey]; warehouse_id -> res_users.id [constraint: user_warehouse_new_rel_warehouse_id_fkey]. Total foreign key relationships: 2. Referenced tables: stock_warehouse, res_users.


List all fields in the utm.tag model. or Describe the field structure of utm.tag.

Response: The utm.tag model has 9 fields. Field types distribution: char: 2, integer: 2, many2one: 2, datetime: 3. Computed fields: 2. Field details: name (char) [required] [module: utm]; color (integer) [module: utm]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


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

Response: Columns in account_open_chart: id (integer) [NOT NULL] [DEFAULT: nextval('account_open_chart_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]; display_account (character varying) [NOT NULL] [COMMENT: Display Accounts]; unfold (boolean) [COMMENT: Auto Unfold]; report_type (character varying) [COMMENT: Hierarchy based on]; show_initial_balance (boolean) [COMMENT: Show Initial Balance]; 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: 13. Statistics: 9 nullable, 1 with defaults, 0 with length constraints.


List all relational fields in allfresh.consignment.report. or What are the relationships in allfresh.consignment.report?

Response: The allfresh.consignment.report model has 5 relational fields: pos_branch_id -> res.branch; product_id -> product.product; consignment_move_id -> account.move; currency_id -> res.currency; company_id -> res.company. Many2many fields: none. One2many fields: none.


What modules define pos.promotion.tebus.murah.selected.brand? or What is the module hierarchy for pos.promotion.tebus.murah.selected.brand?

Response: The pos.promotion.tebus.murah.selected.brand model is defined in module: equip3_pos_masterdata. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: onchange_type_apply.


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

Response: Foreign keys in res_groups_kpi_item_edit_rel_table: kpi_item_id -> res_groups.id [constraint: res_groups_kpi_item_edit_rel_table_kpi_item_id_fkey]; res_groups_id -> kpi_item.id [constraint: res_groups_kpi_item_edit_rel_table_res_groups_id_fkey]. Total foreign key relationships: 2. Referenced tables: res_groups, kpi_item.