What are common use cases for report.sh_purchase_reports.sh_vend_po_analysis_doc? or What fields are readonly in report.sh_purchase_reports.sh_vend_po_analysis_doc?

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


What models are connected to account.analytic.account? or Describe the many2many relations for account.analytic.account.

Response: The account.analytic.account model has 20 relational fields: line_ids -> account.analytic.line; partner_id -> res.partner; currency_id -> res.currency; project_ids -> project.project; crossovered_budget_line -> crossovered.budget.lines; subscription_product_line_ids -> analytic.sale.order.line; not_subscription_product_line_ids -> analytic.sale.order.line; journal_id -> account.journal; order_invoice_currency_id -> res.currency; group_id -> account.analytic.group; company_id -> res.company; branch_id -> res.branch; 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: message_partner_ids, message_channel_ids. One2many fields: line_ids, project_ids, crossovered_budget_line, subscription_product_line_ids, not_subscription_product_line_ids, message_follower_ids, message_ids, website_message_ids.


What data can be stored in user.order.dic? or Show me the fields of user.order.dic.

Response: The user.order.dic model has 20 fields. Field types distribution: many2one: 8, one2many: 4, char: 4, integer: 1, datetime: 3. Computed fields: 2. Field details: report_id (many2one) -> sh.sale.report.salesperson.wizard [module: equip3_sale_report]; list_order (one2many) -> list.order [module: equip3_sale_report]; saleperson (char) [module: equip3_sale_report]; payment_report_id (many2one) -> sh.payment.report.wizard [module: equip3_sale_report]; list_pay (one2many) -> list.pay [module: equip3_sale_report]; list_product (one2many) -> list.product [module: equip3_sale_report]; sale_analysis_id (many2one) -> sh.sale.analysis.wizard [module: equip3_sale_report]; prduct_profit_id (many2one) -> sh.sale.product.profit.wizard [module: equip3_sale_report]; product (char) [module: equip3_sale_report]; sale_categ_id (many2one) -> sh.sale.category.wizard [module: equip3_sale_report]; categ (char) [module: equip3_sale_report]; product_indent_id (many2one) -> sh.sale.product.indent.wizard [module: equip3_sale_report]; category_ids (one2many) -> list.category [module: equip3_sale_report]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


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

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


How to create records in stock.change.product.qty? or How to query stock.change.product.qty data?

Response: To use the stock.change.product.qty model, you need to provide values for required fields: product_id, product_tmpl_id, new_quantity. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: product_id [required]; product_tmpl_id [required]; product_variant_count [computed] [no_copy]; new_quantity [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 the foreign keys in return_inter_transfer_company? or What relationships exist for return_inter_transfer_company?

Response: Foreign keys in return_inter_transfer_company: create_uid -> res_users.id [constraint: return_inter_transfer_company_create_uid_fkey]; currency_id -> res_currency.id [constraint: return_inter_transfer_company_currency_id_fkey]; from_warehouse -> stock_warehouse.id [constraint: return_inter_transfer_company_from_warehouse_fkey]; internal_id -> inter_transfer_company.id [constraint: return_inter_transfer_company_internal_id_fkey]; pricelist_id -> product_pricelist.id [constraint: return_inter_transfer_company_pricelist_id_fkey]; purchase_id -> purchase_order.id [constraint: return_inter_transfer_company_purchase_id_fkey]; sale_id -> sale_order.id [constraint: return_inter_transfer_company_sale_id_fkey]; to_warehouse -> stock_warehouse.id [constraint: return_inter_transfer_company_to_warehouse_fkey]; write_uid -> res_users.id [constraint: return_inter_transfer_company_write_uid_fkey]. Total foreign key relationships: 9. Referenced tables: stock_warehouse, sale_order, product_pricelist, inter_transfer_company, res_currency, res_users, purchase_order.


Show me the fields of account.partial.reconcile. or Which fields are required in account.partial.reconcile?

Response: The account.partial.reconcile model has 18 fields. Field types distribution: many2one: 9, monetary: 3, date: 1, integer: 1, char: 1, datetime: 3. Computed fields: 7. Field details: debit_move_id (many2one) [required] -> account.move.line [module: account]; credit_move_id (many2one) [required] -> account.move.line [module: account]; full_reconcile_id (many2one) -> account.full.reconcile [module: account]; company_currency_id (many2one) [readonly] -> res.currency [compute: <bound method Field._compute_related of account.partial.reconcile.company_currency_id>] [not stored] [module: account] [related: company_id.currency_id]; debit_currency_id (many2one) [readonly] -> res.currency [compute: _compute_debit_currency_id] [stored] [module: account]; credit_currency_id (many2one) [readonly] -> res.currency [compute: _compute_credit_currency_id] [stored] [module: account]; amount (monetary) [module: account]; debit_amount_currency (monetary) [module: account]; credit_amount_currency (monetary) [module: account]; company_id (many2one) -> res.company [compute: <bound method Field._compute_related of account.partial.reconcile.company_id>] [stored] [module: account] [related: debit_move_id.company_id]; max_date (date) [readonly] [compute: _compute_max_date] [stored] [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].


What data can be stored in vendor.payment.request.line? or What fields does vendor.payment.request.line have?

Response: The vendor.payment.request.line model has 16 fields. Field types distribution: many2one: 5, integer: 2, char: 3, monetary: 1, float: 1, binary: 1, datetime: 3. Computed fields: 4. Field details: payment_request_id (many2one) -> vendor.payment.request [module: equip3_purchase_operation]; sequence (integer) [module: equip3_purchase_operation]; description (char) [module: equip3_purchase_operation]; amount_total (monetary) [readonly] [compute: <bound method Field._compute_related of vendor.payment.request.line.amount_total>] [stored] [module: equip3_purchase_operation] [related: purchase_order_id.amount_total]; currency_id (many2one) [readonly] -> res.currency [compute: <bound method Field._compute_related of vendor.payment.request.line.currency_id>] [stored] [module: equip3_purchase_operation] [related: purchase_order_id.currency_id]; payable_amount (float) [module: equip3_purchase_operation]; attachment_file (binary) [module: equip3_purchase_operation]; file_name (char) [module: equip3_purchase_operation]; purchase_order_id (many2one) -> purchase.order [module: equip3_purchase_other_operation_cont]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


Show me the relational structure of product.pricelist. or How does product.pricelist relate to other models?

Response: The product.pricelist model has 10 relational fields: item_ids -> product.pricelist.item; currency_id -> res.currency; country_group_ids -> res.country.group; website_id -> website; pricelist_history_ids -> product.pricelist.history; customer_category -> customer.category; company_id -> res.company; pos_config_ids -> pos.config; create_uid -> res.users; write_uid -> res.users. Many2many fields: country_group_ids, pos_config_ids. One2many fields: item_ids, pricelist_history_ids.


How is stock.warn.insufficient.qty used in the system? or Tell me about the stock.warn.insufficient.qty model.

Response: The stock.warn.insufficient.qty model represents Warn Insufficient Quantity in the ERP system. It contains 8 fields and is used to manage warn insufficient quantity data. Defined in module: stock. Key fields include: product_id, location_id, quant_ids, quantity, product_uom_name, id, display_name, __last_update.


What operations can I perform on budget.scurve? or How do I use the budget.scurve model?

Response: To use the budget.scurve model, you need to provide values for required fields: budget_to_analyze, start_date, end_date. Readonly fields: crossovered_budget_line_count, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: budget_to_analyze [required] [has_default]; start_date [required]; end_date [required]; crossovered_budget_line_count [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 common use cases for crm.meeting.overview? or How to query crm.meeting.overview data?

Response: To use the crm.meeting.overview model, you need to provide values for required fields: none. Readonly fields: res_name, partner_ids, stage_id, order_ids, start, meeting_count, activity_ids, state_1, meeting_salesperson_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: activity_type_id [computed] [no_copy]; res_name [readonly] [computed] [no_copy]; partner_ids [readonly] [computed] [no_copy]; stage_id [readonly] [computed] [no_copy]; order_ids [readonly] [computed] [no_copy]; start [readonly] [computed] [no_copy]; meeting_count [readonly] [computed] [no_copy]; activity_ids [readonly] [computed] [no_copy]; state_1 [readonly] [computed] [no_copy]; meeting_salesperson_ids [readonly] [computed] [no_copy]; activity_state [readonly] [computed] [no_copy]; activity_user_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.


How is stock.scrap.approval.matrix used in the system? or What does the stock.scrap.approval.matrix model represent?

Response: The stock.scrap.approval.matrix model represents Stock Scrap Approval Matrix in the ERP system. It contains 44 fields and is used to manage stock scrap approval matrix data. Defined in module: equip3_inventory_masterdata. Key fields include: name, company_id, warehouse_id, branch_id, approval_line_count, sc_approval_matrix_line_ids, campaign_id, source_id, medium_id, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, access_url, access_token, access_warning, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What are the technical details of pmps.adv.settings? or Describe the implementation of pmps.adv.settings.

Response: The pmps.adv.settings model is defined in module: sh_all_in_one_purchase_tools. It has 4 computed fields: sh_pmps_pro_field_ids, sh_pmps_pro_attr_ids, display_name, __last_update. Stored computed fields: none. Related fields: sh_pmps_pro_field_ids -> company_id.sh_pmps_pro_field_ids, sh_pmps_pro_attr_ids -> company_id.sh_pmps_pro_attr_ids. Original module methods: sh_get_user_company, get_sh_pmps_pro_field_ids, get_sh_pmps_pro_attr_ids.


What methods are defined in approval.matrix.sale.reject original module? or Which fields in approval.matrix.sale.reject are computed?

Response: The approval.matrix.sale.reject model is defined in module: equip3_sale_operation. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: action_confirm.


What columns have default values in res_branch_tax_report_rel? or Which columns are nullable in res_branch_tax_report_rel?

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


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

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


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

Response: Foreign keys in product_attr_exclusion_value_ids_rel: product_template_attribute_exclusion_id -> product_template_attribute_exclusion.id [constraint: product_attr_exclusion_value__product_template_attribute_e_fkey]; product_template_attribute_value_id -> product_template_attribute_value.id [constraint: product_attr_exclusion_value__product_template_attribute_v_fkey]. Total foreign key relationships: 2. Referenced tables: product_template_attribute_value, product_template_attribute_exclusion.


Tell me about the mass.editing.line model. or What is the mass.editing.line model?

Response: The mass.editing.line model represents Mass Editing Line in the ERP system. It contains 13 fields and is used to manage mass editing line data. Defined in module: mass_editing. Key fields include: sequence, server_action_id, model_id, field_id, widget_option, apply_domain, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: The account_bank_statement_import_ir_attachment_rel table has 2 columns and 2 foreign key relationships. It stores data related to account bank statement import ir attachment rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


What operations can I perform on product.warehouse.cost.line? or What fields are readonly in product.warehouse.cost.line?

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


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

Response: Columns in pos_sync_session_order_line: id (integer) [NOT NULL] [DEFAULT: nextval('pos_sync_session_order_line_id_seq'::regclass)] [PRECISION: 32]; uid (character varying) [COMMENT: UID]; data (text) [COMMENT: Data]; name (text) [COMMENT: Name]; parent_id (integer) [PRECISION: 32] [COMMENT: Parent]; product_int (integer) [PRECISION: 32] [COMMENT: Product ID]; qty (integer) [PRECISION: 32] [COMMENT: Quantity]; pos_session_id (integer) [PRECISION: 32] [COMMENT: Session]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 12. Statistics: 11 nullable, 1 with defaults, 0 with length constraints.


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

Response: Foreign keys in res_users_tag: create_uid -> res_users.id [constraint: res_users_tag_create_uid_fkey]; write_uid -> res_users.id [constraint: res_users_tag_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


Describe the field structure of whatsapp.template.message.variable. or What computed fields exist in whatsapp.template.message.variable?

Response: The whatsapp.template.message.variable model has 10 fields. Field types distribution: many2one: 3, char: 3, integer: 1, datetime: 3. Computed fields: 2. Field details: wa_id (many2one) -> whatsapp.template.message [module: equip3_accounting_operation]; name (char) [module: equip3_accounting_operation]; description (char) [module: equip3_accounting_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].


How to work with stock.scrap.request.matrix.reject fields? or How to query stock.scrap.request.matrix.reject data?

Response: To use the stock.scrap.request.matrix.reject 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.


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

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


What is the stock_quant_queue table? or Explain the stock_quant_queue table schema.

Response: The stock_quant_queue table has 8 columns and 3 foreign key relationships. It stores data related to stock quant queue 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.


Show me the relational structure of ir.property. or What are the relationships in ir.property?

Response: The ir.property model has 4 relational fields: company_id -> res.company; fields_id -> ir.model.fields; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


What is the mass_editing_line table? or Explain the mass_editing_line table schema.

Response: The mass_editing_line table has 10 columns and 4 foreign key relationships. It stores data related to mass editing line in the system. The table has 1 indexes for performance optimization. Column types: integer: 6, character varying: 1, boolean: 1, timestamp without time zone: 2. Nullable columns: 7, columns with defaults: 1.


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

Response: The queue_job_function table has 8 columns and 2 foreign key relationships. It stores data related to queue job function in the system. The table has 2 indexes for performance optimization. Column types: integer: 3, character varying: 3, text: 2. Nullable columns: 6, columns with defaults: 1.


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

Response: Foreign keys in account_analytic_tag: branch_id -> res_branch.id [constraint: account_analytic_tag_branch_id_fkey]; company_id -> res_company.id [constraint: account_analytic_tag_company_id_fkey]; create_uid -> res_users.id [constraint: account_analytic_tag_create_uid_fkey]; message_main_attachment_id -> ir_attachment.id [constraint: account_analytic_tag_message_main_attachment_id_fkey]; write_uid -> res_users.id [constraint: account_analytic_tag_write_uid_fkey]. Total foreign key relationships: 5. Referenced tables: ir_attachment, res_company, res_users, res_branch.


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

Response: Foreign keys in res_branch_sh_purchase_bill_summary_wizard_rel: sh_purchase_bill_summary_wizard_id -> sh_purchase_bill_summary_wizard.id [constraint: res_branch_sh_purchase_bill_s_sh_purchase_bill_summary_wiz_fkey]; res_branch_id -> res_branch.id [constraint: res_branch_sh_purchase_bill_summary_wizard_r_res_branch_id_fkey]. Total foreign key relationships: 2. Referenced tables: sh_purchase_bill_summary_wizard, res_branch.


What are the available fields for assign.pr.line.wizard? or What data can be stored in assign.pr.line.wizard?

Response: The assign.pr.line.wizard model has 13 fields. Field types distribution: many2one: 7, char: 2, integer: 1, datetime: 3. Computed fields: 2. Field details: wizard_id (many2one) -> assign.pr.wizard [module: equip3_purchase_operation]; pr_line_id (many2one) -> purchase.request.line [module: equip3_purchase_operation]; name (char) [readonly] [module: equip3_purchase_operation]; user_id (many2one) [readonly] -> res.users [module: equip3_purchase_operation]; new_user_id (many2one) -> res.users [module: equip3_purchase_operation]; product_id (many2one) [readonly] -> product.product [module: equip3_purchase_operation]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


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

Response: Foreign keys in store_model_nodes: create_uid -> res_users.id [constraint: store_model_nodes_create_uid_fkey]; model_id -> ir_model.id [constraint: store_model_nodes_model_id_fkey]; write_uid -> res_users.id [constraint: store_model_nodes_write_uid_fkey]. Total foreign key relationships: 3. Referenced tables: ir_model, res_users.


What fields are readonly in sale.order.line? or How do I use the sale.order.line model?

Response: To use the sale.order.line model, you need to provide values for required fields: order_id, product_uom_qty, price_unit, customer_lead, name. Readonly fields: invoice_status, price_tax, price_reduce, price_reduce_taxinc, price_reduce_taxexcl, product_updatable, product_uom_category_id, product_uom_readonly, qty_to_invoice, qty_invoiced, untaxed_amount_invoiced, untaxed_amount_to_invoice, salesman_id, currency_id, state, is_configurable_product, product_template_attribute_value_ids, purchase_line_ids, purchase_line_count, product_type, virtual_available_at_date, scheduled_date, forecast_expected_date, free_qty_today, qty_available_today, warehouse_id, qty_to_deliver, is_mto, display_qty_widget, name_short, discount_type, product_qty, recompute_delivery_price, margin, margin_percent, is_service, qty_delivered_method, remaining_hours_available, remaining_hours, discount_line, setting, customer_id, user_id, sequence_no, company_id, last_sale_price, last_customer_sale_price, net_amount, branch_id, filter_delivery_address_id, hide_button_qa_sale, trigger, product_template_id, brand_ids, price_subtotal, price_total, tax_discount_policy, discounted_value, customer_voucher_id, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, access_url, access_warning, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: order_id [required] [no_copy]; invoice_status [readonly] [computed] [has_default] [no_copy]; price_tax [readonly] [computed] [no_copy]; price_reduce [readonly] [computed] [no_copy]; price_reduce_taxinc [readonly] [computed] [no_copy]; price_reduce_taxexcl [readonly] [computed] [no_copy]; product_updatable [readonly] [computed] [has_default] [no_copy]; product_uom_category_id [readonly] [computed] [no_copy]; product_uom_readonly [readonly] [computed] [no_copy]; qty_delivered [computed] [has_default] [no_copy]; qty_to_invoice [readonly] [computed] [no_copy]; qty_invoiced [readonly] [computed] [no_copy]; untaxed_amount_invoiced [readonly] [computed] [no_copy]; untaxed_amount_to_invoice [readonly] [computed] [no_copy]; salesman_id [readonly] [computed] [no_copy]; currency_id [readonly] [computed] [no_copy]; order_partner_id [computed] [no_copy]; state [readonly] [computed] [has_default] [no_copy]; is_configurable_product [readonly] [computed] [no_copy]; product_template_attribute_value_ids [readonly] [computed] [no_copy]; purchase_line_ids [readonly] [no_copy]; purchase_line_count [readonly] [computed] [no_copy]; product_type [readonly] [computed] [no_copy]; virtual_available_at_date [readonly] [computed] [no_copy]; scheduled_date [readonly] [computed] [no_copy]; forecast_expected_date [readonly] [computed] [no_copy]; free_qty_today [readonly] [computed] [no_copy]; qty_available_today [readonly] [computed] [no_copy]; warehouse_id [readonly] [computed] [no_copy]; qty_to_deliver [readonly] [computed] [no_copy]; is_mto [readonly] [computed] [no_copy]; display_qty_widget [readonly] [computed] [no_copy]; name_short [readonly] [computed] [no_copy]; discount_type [readonly] [computed] [no_copy]; product_qty [readonly] [computed] [no_copy]; recompute_delivery_price [readonly] [computed] [no_copy]; margin [readonly] [computed] [no_copy]; margin_percent [readonly] [computed] [no_copy]; purchase_price [computed]; is_service [readonly] [computed] [no_copy]; qty_delivered_method [readonly] [computed] [no_copy]; remaining_hours_available [readonly] [computed] [no_copy]; remaining_hours [readonly] [computed] [no_copy]; discount_line [readonly] [no_copy]; setting [readonly] [computed] [no_copy]; customer_id [readonly] [computed] [no_copy]; user_id [readonly] [computed] [no_copy]; sequence_no [readonly] [computed] [no_copy]; product_uom_qty [required] [has_default]; price_unit [required] [has_default]; customer_lead [required] [has_default]; company_id [readonly] [computed] [no_copy]; name [required]; last_sale_price [readonly] [computed] [no_copy]; last_customer_sale_price [readonly] [computed] [no_copy]; net_amount [readonly] [computed] [no_copy]; branch_id [readonly] [computed] [no_copy]; filter_delivery_address_id [readonly] [computed] [no_copy]; hide_button_qa_sale [readonly] [computed] [no_copy]; trigger [readonly] [computed] [no_copy]; product_template_id [readonly] [computed] [no_copy]; brand_ids [readonly] [computed] [no_copy]; price_subtotal [readonly] [computed] [no_copy]; price_total [readonly] [computed] [no_copy]; tax_discount_policy [readonly] [computed] [no_copy]; discounted_value [readonly] [computed] [no_copy]; customer_voucher_id [readonly]; activity_state [readonly] [computed] [no_copy]; activity_user_id [computed] [no_copy]; activity_type_id [computed] [no_copy]; activity_type_icon [readonly] [computed] [no_copy]; activity_date_deadline [readonly] [computed] [no_copy]; my_activity_date_deadline [readonly] [computed] [no_copy]; activity_summary [computed] [no_copy]; activity_exception_decoration [readonly] [computed] [no_copy]; activity_exception_icon [readonly] [computed] [no_copy]; message_is_follower [readonly] [computed] [no_copy]; message_partner_ids [readonly] [computed] [no_copy]; message_channel_ids [readonly] [computed] [no_copy]; message_unread [readonly] [computed] [no_copy]; message_unread_counter [readonly] [computed] [no_copy]; message_needaction [readonly] [computed] [no_copy]; message_needaction_counter [readonly] [computed] [no_copy]; message_has_error [readonly] [computed] [no_copy]; message_has_error_counter [readonly] [computed] [no_copy]; message_attachment_count [readonly] [computed] [no_copy]; message_has_sms_error [readonly] [computed] [no_copy]; access_url [readonly] [computed] [no_copy]; access_warning [readonly] [computed] [no_copy]; 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 models are connected to sale.data.margin? or What are the relationships in sale.data.margin?

Response: The sale.data.margin model has 6 relational fields: partner_id -> res.partner; company_id -> res.company; branch_id -> res.branch; order_line -> sale.data.margin.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: order_line.


What are the technical details of crm.meeting.overview? or What is the module hierarchy for crm.meeting.overview?

Response: The crm.meeting.overview model is defined in module: equip3_crm_meeting_overview. It has 31 computed fields: activity_type_id, res_name, partner_ids, stage_id, order_ids, start, meeting_count, activity_ids, state_1, meeting_salesperson_ids, activity_state, activity_user_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: start. Related fields: activity_type_id -> opportunity_id.activity_type_id, res_name -> opportunity_id.name, partner_ids -> calendar_id.partner_ids, stage_id -> opportunity_id.stage_id, order_ids -> opportunity_id.order_ids, start -> calendar_id.start, meeting_count -> opportunity_id.meeting_count, activity_ids -> calendar_id.activity_ids, state_1 -> calendar_id.state, meeting_salesperson_ids -> calendar_id.meeting_salesperson_ids, activity_user_id -> activity_ids.user_id, activity_type_icon -> activity_ids.icon, activity_summary -> activity_ids.summary. Original module methods: write.


What does the sh.sale.invoice.summary.xls model represent? or Tell me about the sh.sale.invoice.summary.xls model.

Response: The sh.sale.invoice.summary.xls model represents Sale Invoice Summary Xls Report in the ERP system. It contains 9 fields and is used to manage sale invoice summary xls report data. Defined in module: sh_sale_reports. Key fields include: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What field types are used in stock.return.move.line? or Describe the field structure of stock.return.move.line.

Response: The stock.return.move.line model has 12 fields. Field types distribution: many2one: 6, float: 1, integer: 1, char: 1, datetime: 3. Computed fields: 2. Field details: product_id (many2one) -> product.product [module: equip3_inventory_operation]; return_id (many2one) -> stock.return.picking [module: equip3_inventory_operation]; lot_id (many2one) -> stock.production.lot [module: equip3_inventory_operation]; qty (float) [module: equip3_inventory_operation]; uom_id (many2one) -> uom.uom [module: equip3_inventory_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 relationships exist for account_payment_term? or Show me the foreign key constraints of account_payment_term.

Response: Foreign keys in account_payment_term: account_id -> account_account.id [constraint: account_payment_term_account_id_fkey]; branch_id -> res_branch.id [constraint: account_payment_term_branch_id_fkey]; company_id -> res_company.id [constraint: account_payment_term_company_id_fkey]; create_uid -> res_users.id [constraint: account_payment_term_create_uid_fkey]; message_main_attachment_id -> ir_attachment.id [constraint: account_payment_term_message_main_attachment_id_fkey]; write_uid -> res_users.id [constraint: account_payment_term_write_uid_fkey]. Total foreign key relationships: 6. Referenced tables: res_company, account_account, ir_attachment, res_users, res_branch.


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

Response: The pos.config model represents Point of Sale Configuration in the ERP system. It contains 493 fields and is used to manage point of sale configuration data. Defined in module: point_of_sale. Key fields include: name, is_installed_account_accountant, journal_id, invoice_journal_id, currency_id, iface_cashdrawer, iface_electronic_scale, iface_vkeyboard, iface_customer_facing_display, iface_print_via_proxy, iface_scan_via_proxy, iface_big_scrollbars, iface_print_auto, iface_print_skip_screen, iface_tax_included, iface_start_categ_id, selectable_categ_ids, iface_display_categ_images, restrict_price_control, cash_control, receipt_header, receipt_footer, proxy_ip, active, uuid, sequence_id, sequence_line_id, session_ids, current_session_id, current_session_state, last_session_closing_cash, last_session_closing_date, last_session_closing_cashbox, pos_session_username, pos_session_state, pos_session_duration, pricelist_id, available_pricelist_ids, allowed_pricelist_ids, company_id, barcode_nomenclature_id, iface_tipproduct, tip_product_id, fiscal_position_ids, default_fiscal_position_id, default_cashbox_id, use_pricelist, tax_regime, tax_regime_selection, start_category, module_account, module_pos_discount, module_pos_loyalty, module_pos_mercury, manage_orders, product_configurator, is_posbox, is_header_or_footer, module_pos_hr, amount_authorized_diff, payment_method_ids, company_has_template, current_user_id, other_devices, rounding_method, cash_rounding, only_round_cash_method, has_active_session, show_allow_invoicing_alert, manual_discount, iface_discount, discount_pc, discount_product_id, epson_printer_ip, employee_ids, iface_splitbill, iface_printbill, iface_orderline_notes, floor_ids, printer_ids, is_table_management, is_order_printer, set_tip_after_payment, module_pos_restaurant, crm_team_id, group_pos_manager_id, group_pos_user_id, pos_receipt_template_id, order_loading_options, number_of_days, weight_scale_barcode_format_id, bnk_cash_control, restaurant_order, restaurant_order_login, restaurant_order_password, pos_config_cashbox_lines_ids, pos_config_cashbox_clsosing_line_ids, cashbox_lines_ids, pos_cashbox_lines_ids, printer_id, load_coupon_program, coupon_program_apply_type, coupon_program_ids, coupon_giftcard_ids, coupon_giftcard_create, user_id, allow_change_pos_profile, allow_numpad, allow_discount, allow_qty, allow_price, allow_remove_line, allow_minus, allow_payment, allow_customer, allow_add_order, allow_remove_order, allow_add_product, allow_payment_zero, allow_closing_session, allow_closing_all_sessions_online, allow_duplicate_session, allow_otp, twilio_acc_sid, twilio_auth_token, pos_otp_reset_time, pos_otp_msg, tax_affect_compliment, sale_order, sale_order_auto_confirm, sale_order_auto_invoice, sale_order_auto_delivery, sale_order_required_signature, pos_orders_management, pos_order_tracking, pos_order_tracking_remove_when_closing_session, shipping_order, pos_orders_load_orders_another_pos, pos_orders_filter_by_branch, pos_order_period_return_days, pos_allowed_return_category_ids, required_reason_return, display_return_days_receipt, display_onhand, allow_order_out_of_stock, allow_pos_categories_out_of_stock, hide_product_when_outof_stock, print_voucher, voucher_sequence_id, expired_days_voucher, sync_multi_session, sync_play_sound, sync_multi_session_with, sync_multi_session_manual_stop, sync_multi_session_alert_remove_order, sync_multi_session_offline, sync_to_pos_config_ids, sync_tracking_activities_user, display_person_add_line, internal_transfer, internal_transfer_picking_type_id, discount, discount_ids, delay, discount_limit, discount_limit_type, discount_limit_amount, return_products, return_method_id, return_covert_to_coupon, return_coupon_program_id, return_duplicate, return_viva_scan_barcode, validate_payment, validate_remove_order, validate_new_order, validate_change_minus, validate_quantity_change, validate_quantity_change_type, validate_price_change, validate_price_change_type, validate_discount_change, validate_discount_change_type, validate_remove_line, validate_return, validate_coupon, product_operation, note_order, signature_order, booking_orders, load_booked_orders_type, booking_orders_load_orders_another_pos, booking_orders_alert, booking_allow_confirm_sale, booking_orders_display_shipping_receipt, display_tax_orderline, display_tax_receipt, display_image_orderline, display_amount_discount, display_barcode, quickly_look_up_product, management_invoice, load_invoices_type, invoice_offline, wallet, payment_journal_ids, send_invoice_email, customer_default_id, auto_invoice, auto_invoice_with_customer_default, invoice_without_download, fiscal_position_auto_detect, display_sale_price_within_tax, display_cost_price, display_product_ref, display_product_detail, allow_remove_product, allow_edit_product, display_product_name_without_product_code, product_virtual_keyboard, hide_product_image, multi_location, update_stock_onhand, multi_stock_operation_type, multi_stock_operation_type_ids, product_view, update_tax, update_tax_ids, check_duplicate_email, check_duplicate_phone, check_required_phone, check_required_email, check_required_vat, add_sale_person, default_seller_id, seller_ids, force_seller, backup_orders, backup_orders_automatic, save_orders_removed, management_session, default_set_cash_open, default_set_cash_amount, default_set_cash_notes, cash_inout_reason_ids, barcode_receipt, qrcode_receipt, qrcode_ids, receipt_template, hide_mobile, hide_phone, hide_email, update_client, add_client, archive_client, remove_client, report_signature, report_product_summary, report_product_summary_auto_check_product, report_product_summary_auto_check_category, report_product_summary_auto_check_location, report_product_summary_auto_check_payment, report_order_summary, report_order_summary_auto_check_order, report_order_summary_auto_check_category, report_order_summary_auto_check_payment, report_order_summary_default_state, report_payment_summary, report_sale_summary, report_sale_summary_show_profit, default_product_sort_by, hide_order_screen, add_customer_before_products_already_in_shopping_cart, allow_cashier_select_pricelist, sale_with_package, allow_set_price_smaller_min_price, create_lots, fullfill_lots_type, fullfill_lots, stock_location_ids, validate_by_manager, discount_unlock_by_manager, assigned_user_ids, manager_ids, stock_location_id, stock_location_dest_id, discount_value, discount_value_limit, discount_global_id, posbox_save_orders, posbox_save_orders_server_ip, posbox_save_orders_server_port, analytic_account_id, limit_categories, iface_available_categ_ids, barcode_scan_timeout, rounding_automatic, rounding_type, service_charge_ids, service_charge_type, service_shipping_automatic, google_map_api_key, payment_reference, display_margin, start_session_oneclick, translate_products_name, set_product_name_from_field, replace_partners_name, set_partner_name_from_field, create_quotation, assign_orders_to_config_ids, product_generic_option, mrp, last_save_cache, category_ancestors, point_of_sale_update_stock_quantities, multi_session, display_filter_product_categories, product_category_ids, sessions_opened, search_query_only_start_when_enter, create_category_direct, create_product_direct, customer_facing_screen, customer_facing_screen_width, customer_facing_screen_height, rounding, rounding_factor, decimal_places, font_family, price_tag_color, header_background_color, cart_box_style, buttons_box_style, background, product_screen_background, cart_background, payment_screen_background, numpad_background, product_categories_height, product_width, product_height, product_margin, product_image_width, product_image_height, product_name_font_size, display_mobile_mode, display_mobile_screen_size, display_product_image, cart_width, whatsapp_api, whatsapp_token, whatsapp_send_type, whatsapp_message_receipt, checkin_screen, hidden_product_ids, warning_closing_session, warning_odoo_offline, pos_title, sync_partners_realtime, cache, local_network_printer, local_network_printer_ip_address, local_network_printer_port, product_recommendation, product_recommendation_number, show_session_information, tip_percent, tip_percent_max, categ_dislay_type, custom_sale, custom_sale_product_id, multi_currency, multi_currency_ids, allowed_employee_ids, fire_appetizer, fire_main_course, fire_dessert, enable_fire_appetizer, enable_fire_main_course, enable_fire_dessert, enable_seat_time, seat_time, show_product_template, available_product_domain, promotion_manual_select, promotion_auto_add, promotion_ids, is_manual_sync_for_sync_between_session, is_manual_sync_masterdata, is_manual_sync_member, is_auto_sync_product_stock, is_auto_sync_product_price, is_auto_sync_product, is_auto_sync_pricelist, is_auto_sync_promotion, is_auto_sync_coupon, is_monitor_auto_sync, is_force_sync_promotion, is_force_sync_pricelist, filter_load_pos_order, zone_id, product_voucher_service_id, product_coupon_service_id, display_table, display_all_product, product_categ_ids, product_categ_display_names, set_lines_to_done, order_receipt_tickets, qr_orders, login_title, login_required, login_create_partner, qrcode_order_screen, qrcode_order_auto_alert, customer_facing_display_html, user_ids, sync_manual_button, period_minutes_warning, enable_void_time, void_time, void_order_pin_ids, void_order_pins, void_order_line_pin_ids, void_order_line_pins, advertisement_image_ids, marquee_type, marquee_text, marque_color, marque_bg_color, marque_font_size, mute_video_sound, ac_width, ac_height, ac_qrcod, ac_qr_link, warehouse_id, is_order_rounding, order_rounding_type, picking_type_id, pos_branch_id, pos_branch_name, branch_telephone, branch_address, branch_street, branch_street_2, enable_gift_card, gift_card_account_id, gift_card_product_id, gift_payment_method_id, manual_card_number, msg_before_card_pay, is_difference_value_opening_control_validation, is_cash_management_with_validation, cashbox_payment_method_id, pos_cashbox_product_services, cashbox_line_amount, screen_type, is_allow_product_exchange, product_exchange_pin_ids, product_exchange_line_pins, is_save_order_history_local, save_order_history_local_days, is_save_order_to_pos_cache_service, link_pos_cache_service, select_shortcut, enable_shortcuts, display_point_receipt, pos_loyalty_id, pos_loyalty_ids, loyalty_combine_promotion, loyalty_redeem_in_pos_screen, is_allow_redeem_in_pos_screen, is_allow_create_member_in_pos_screen, customer_deposit_account_id, customer_deposit_reconcile_journal_id, order_summery, product_summery, product_categ_summery, loc_summery, payment_summery, pos_code, is_hide_pos_order_button, analytic_group_ids, is_pos_load_data_from_pos_cache_sdk, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: Foreign keys in coupon_rule: create_uid -> res_users.id [constraint: coupon_rule_create_uid_fkey]; write_uid -> res_users.id [constraint: coupon_rule_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


What business logic is in account.payment.register.payment.difference.line? or How do I use the account.payment.register.payment.difference.line model?

Response: To use the account.payment.register.payment.difference.line model, you need to provide values for required fields: name, account_id, payment_amount, company_id. Readonly fields: currency_id, payment_difference, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [required]; account_id [required] [no_copy]; payment_amount [required]; currency_id [readonly] [computed] [no_copy]; payment_difference [readonly] [computed] [no_copy]; company_id [required] [readonly] [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.


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

Response: Foreign keys in account_tax_repartition_line_template: account_id -> account_account_template.id [constraint: account_tax_repartition_line_template_account_id_fkey]; create_uid -> res_users.id [constraint: account_tax_repartition_line_template_create_uid_fkey]; invoice_tax_id -> account_tax_template.id [constraint: account_tax_repartition_line_template_invoice_tax_id_fkey]; refund_tax_id -> account_tax_template.id [constraint: account_tax_repartition_line_template_refund_tax_id_fkey]; write_uid -> res_users.id [constraint: account_tax_repartition_line_template_write_uid_fkey]. Total foreign key relationships: 5. Referenced tables: account_tax_template, account_account_template, res_users.


Describe the report.product.report_pricelist model in Odoo. or Tell me about the report.product.report_pricelist model.

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


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

Response: The account.tax model represents Tax in the ERP system. It contains 58 fields and is used to manage tax data. Defined in module: account. Key fields include: tax_paid_account, price_include_total, pay_separately, name, type_tax_use, tax_scope, amount_type, active, company_id, children_tax_ids, sequence, amount, description, price_include, include_base_amount, analytic, tax_group_id, hide_tax_exigibility, tax_exigibility, cash_basis_transition_account_id, invoice_repartition_line_ids, refund_repartition_line_ids, tax_fiscal_country_id, country_code, branch_id, is_ppn, 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 are common use cases for report.sh_purchase_reports.sh_payment_pr_report_doc? or How to query report.sh_purchase_reports.sh_payment_pr_report_doc data?

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


What are the relationships in pos.category? or What foreign keys exist in pos.category?

Response: The pos.category model has 7 relational fields: parent_id -> pos.category; child_id -> pos.category; pos_branch_ids -> res.branch; pos_config_ids -> pos.config; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: pos_branch_ids, pos_config_ids. One2many fields: child_id.


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

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


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

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


What field types are used in pos.generate.efaktur? or What are the available fields for pos.generate.efaktur?

Response: The pos.generate.efaktur model has 18 fields. Field types distribution: char: 3, selection: 1, date: 2, one2many: 4, many2one: 4, integer: 1, datetime: 3. Computed fields: 2. Field details: name (char) [required] [module: equip3_pos_membership]; other_name (char) [module: equip3_pos_membership]; state (selection) [module: equip3_pos_membership]; start_date (date) [module: equip3_pos_membership]; end_date (date) [module: equip3_pos_membership]; invoice_ids (one2many) -> pos.generate.efaktur.invoice [module: equip3_pos_membership]; digunggung_ids (one2many) -> pos.generate.efaktur.digunggung [module: equip3_pos_membership]; gabungan_ids (one2many) -> pos.generate.efaktur.gabungan [module: equip3_pos_membership]; other_ids (one2many) -> pos.generate.efaktur.other [module: equip3_pos_membership]; branch_id (many2one) -> res.branch [module: equip3_pos_membership]; company_id (many2one) -> res.company [module: equip3_pos_membership]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


Explain the mrp_quality_alert_report_res_users_rel table schema. or What is the mrp_quality_alert_report_res_users_rel table?

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


How does sh.sale.product.profit.wizard relate to other models? or What are the relationships in sh.sale.product.profit.wizard?

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


Which fields in account.cash.rounding are computed? or What are the technical details of account.cash.rounding?

Response: The account.cash.rounding model is defined in module: account. It has 5 computed fields: profit_account_id, loss_account_id, company_id, display_name, __last_update. Stored computed fields: none. Related fields: company_id -> profit_account_id.company_id. Original module methods: validate_rounding, round, compute_difference.


How to work with vendor.payment.request.line fields? or What fields are readonly in vendor.payment.request.line?

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


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

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


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

Response: Foreign keys in sh_mrp_quality_alert: company_id -> res_company.id [constraint: sh_mrp_quality_alert_company_id_fkey]; create_uid -> res_users.id [constraint: sh_mrp_quality_alert_create_uid_fkey]; lot_id -> stock_production_lot.id [constraint: sh_mrp_quality_alert_lot_id_fkey]; message_main_attachment_id -> ir_attachment.id [constraint: sh_mrp_quality_alert_message_main_attachment_id_fkey]; mrp_id -> mrp_production.id [constraint: sh_mrp_quality_alert_mrp_id_fkey]; partner_id -> res_partner.id [constraint: sh_mrp_quality_alert_partner_id_fkey]; product_id -> product_product.id [constraint: sh_mrp_quality_alert_product_id_fkey]; stage_id -> sh_qc_alert_stage.id [constraint: sh_mrp_quality_alert_stage_id_fkey]; team_id -> sh_qc_team.id [constraint: sh_mrp_quality_alert_team_id_fkey]; user_id -> res_users.id [constraint: sh_mrp_quality_alert_user_id_fkey]; workorder_id -> mrp_workorder.id [constraint: sh_mrp_quality_alert_workorder_id_fkey]; write_uid -> res_users.id [constraint: sh_mrp_quality_alert_write_uid_fkey]. Total foreign key relationships: 12. Referenced tables: product_product, sh_qc_team, res_partner, res_company, sh_qc_alert_stage, mrp_production, ir_attachment, mrp_workorder, res_users, stock_production_lot.


How to create records in approval.matrix.direct.purchase? or What business logic is in approval.matrix.direct.purchase?

Response: To use the approval.matrix.direct.purchase model, you need to provide values for required fields: name, company_id, branch_id, minimum_amt, maximum_amt. Readonly fields: company_id, is_good_services_order, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, access_url, access_warning, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [required]; company_id [required] [readonly] [has_default]; branch_id [required] [has_default]; minimum_amt [required]; maximum_amt [required]; is_good_services_order [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]; access_url [readonly] [computed] [no_copy]; access_warning [readonly] [computed] [no_copy]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


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

Response: Foreign keys in cashback_line: create_uid -> res_users.id [constraint: cashback_line_create_uid_fkey]; customer_voucher_id -> customer_voucher.id [constraint: cashback_line_customer_voucher_id_fkey]; invoice_id -> account_move.id [constraint: cashback_line_invoice_id_fkey]; order_id -> sale_order.id [constraint: cashback_line_order_id_fkey]; product_id -> product_product.id [constraint: cashback_line_product_id_fkey]; write_uid -> res_users.id [constraint: cashback_line_write_uid_fkey]. Total foreign key relationships: 6. Referenced tables: product_product, customer_voucher, sale_order, res_users, account_move.


What are the relationships in account.voucher.line? or How does account.voucher.line relate to other models?

Response: The account.voucher.line model has 11 relational fields: voucher_id -> account.voucher; product_id -> product.product; uom_id -> uom.uom; account_id -> account.account; account_analytic_id -> account.analytic.account; analytic_tag_ids -> account.analytic.tag; company_id -> res.company; tax_ids -> account.tax; currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: analytic_tag_ids, tax_ids. One2many fields: none.


How do I use the mrp.bom model? or What operations can I perform on mrp.bom?

Response: To use the mrp.bom model, you need to provide values for required fields: ready_to_produce, consumption, type, product_qty, product_uom_id, product_tmpl_id. Readonly fields: product_uom_category_id, sh_bom_bm_is_cont_scan, company_id, forecast_cost, bom_tools, next_new_sequence, operation_two_ids, is_branch_required, use_operations, product_name_display, 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_date, write_uid, write_date, __last_update. Field usage details: product_uom_category_id [readonly] [computed] [no_copy]; ready_to_produce [required] [has_default]; consumption [required] [has_default]; sh_bom_bm_is_cont_scan [readonly] [has_default]; type [required] [has_default]; product_qty [required] [has_default]; company_id [readonly] [has_default]; product_uom_id [required] [has_default]; forecast_cost [readonly] [computed] [no_copy]; bom_tools [readonly] [computed] [no_copy]; next_new_sequence [readonly] [computed] [no_copy]; operation_two_ids [readonly] [computed] [no_copy]; is_branch_required [readonly] [computed] [no_copy]; use_operations [readonly] [computed] [no_copy]; product_tmpl_id [required]; product_name_display [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_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


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

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


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

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


List all fields in the sale.order.partner.credit model. or What field types are used in sale.order.partner.credit?

Response: The sale.order.partner.credit model has 21 fields. Field types distribution: many2one: 4, float: 5, boolean: 3, char: 4, integer: 2, datetime: 3. Computed fields: 2. Field details: name (many2one) [readonly] -> sale.order [module: sh_sale_credit_limit]; order_partner (many2one) [readonly] -> res.partner [module: sh_sale_credit_limit]; customer_credit_limit (float) [readonly] [module: sh_sale_credit_limit]; set_customer_onhold (boolean) [module: sh_sale_credit_limit]; total_receivable (float) [readonly] [module: sh_sale_credit_limit]; current_order (float) [readonly] [module: sh_sale_credit_limit]; sale_orders_cnt_amt (char) [readonly] [module: sh_sale_credit_limit]; cust_invoice_cnt_amt (char) [readonly] [module: sh_sale_credit_limit]; sale_id (integer) [module: equip3_sale_other_operation]; invoice_number (char) [readonly] [module: equip3_sale_other_operation]; customer_max_invoice_overdue (float) [readonly] [module: equip3_sale_other_operation]; is_set_customer_on_hold (boolean) [readonly] [module: equip3_sale_other_operation]; avl_open_inv_limt (float) [readonly] [module: equip3_sale_other_operation]; customer_on_hold_open_invoice (boolean) [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 one2many fields are in sh.mpo.merge.purchase.order.wizard? or What models are connected to sh.mpo.merge.purchase.order.wizard?

Response: The sh.mpo.merge.purchase.order.wizard model has 5 relational fields: partner_id -> res.partner; purchase_order_id -> purchase.order; purchase_order_ids -> purchase.order; create_uid -> res.users; write_uid -> res.users. Many2many fields: purchase_order_ids. One2many fields: none.


What business logic is in ir.ui.menu? or How to query ir.ui.menu data?

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


What models are connected to report.sh_purchase_reports.rpt_purchase_order_day_wise? or Show me the relational structure of report.sh_purchase_reports.rpt_purchase_order_day_wise.

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


How does sh.qc.measurement.line relate to other models? or What are the relationships in sh.qc.measurement.line?

Response: The sh.qc.measurement.line model has 5 relational fields: measurement_id -> sh.qc.measurement; product_id -> product.product; quality_point_id -> sh.qc.point; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


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

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


What is the sh.tc.top.customer.wizard model? or What does the sh.tc.top.customer.wizard model represent?

Response: The sh.tc.top.customer.wizard model represents Top Customers in the ERP system. It contains 23 fields and is used to manage top customers data. Defined in module: sh_sale_reports. Key fields include: type, date_to, date_compare_from, date_compare_to, no_of_top_item, amount_total, team_id, currency_id, company_ids, company_id, top_customer_ids, top_customer_compare_ids, lost_cust_ids, new_cust_ids, sale_currency_id, date_from, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


List all relational fields in pos.payment.method. or What models are connected to pos.payment.method?

Response: The pos.payment.method model has 14 relational fields: receivable_account_id -> account.account; cash_journal_id -> account.journal; open_session_ids -> pos.session; config_ids -> pos.config; company_id -> res.company; fees_product_id -> product.product; discount_product_id -> product.product; invoice_partner_id -> res.partner; mdr_intermediary_account_id -> account.account; mdr_ids -> pos.payment.method.mdr; account_journal_id -> account.journal; installment_tenor_ids -> pos.payment.installment.tenor; create_uid -> res.users; write_uid -> res.users. Many2many fields: open_session_ids, config_ids, installment_tenor_ids. One2many fields: mdr_ids.


What computed fields exist in sh.product.barcode.mobile.wizard.line? or Which fields are required in sh.product.barcode.mobile.wizard.line?

Response: The sh.product.barcode.mobile.wizard.line model has 15 fields. Field types distribution: many2one: 7, float: 2, monetary: 1, integer: 1, char: 1, datetime: 3. Computed fields: 3. Field details: location_id (many2one) -> stock.location [module: equip3_inventory_operation]; on_hand_qty (float) [module: equip3_inventory_operation]; available_quantity (float) [module: equip3_inventory_operation]; product_uom_id (many2one) -> uom.uom [module: equip3_inventory_operation]; currency_id (many2one) [readonly] -> res.currency [compute: <bound method Field._compute_related of sh.product.barcode.mobile.wizard.line.currency_id>] [not stored] [module: equip3_inventory_operation] [related: company_id.currency_id]; value (monetary) [module: equip3_inventory_operation]; company_id (many2one) -> res.company [module: equip3_inventory_operation]; sh_product_barcode_id (many2one) -> sh.product.barcode.mobile.wizard [module: equip3_inventory_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].


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

Response: Foreign keys in account_analytic_tag_asp_asm_stock_rel: account_analytic_tag_id -> account_analytic_tag.id [constraint: account_analytic_tag_asp_asm_stock_account_analytic_tag_id_fkey]; asp_asm_stock_id -> asp_asm_stock.id [constraint: account_analytic_tag_asp_asm_stock_rel_asp_asm_stock_id_fkey]. Total foreign key relationships: 2. Referenced tables: asp_asm_stock, account_analytic_tag.


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

Response: The stock_production_lot table has 38 columns and 15 foreign key relationships. It stores data related to stock production lot in the system. The table has 3 indexes for performance optimization. Column types: integer: 17, character varying: 4, text: 1, timestamp without time zone: 8, boolean: 3, date: 2, double precision: 3. Nullable columns: 34, columns with defaults: 1.


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

Response: Columns in account_partner_ledger: id (integer) [NOT NULL] [DEFAULT: nextval('account_partner_ledger_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]; reconciled (character varying) [COMMENT: Reconcile Type]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]; report_currency_id (integer) [PRECISION: 32] [COMMENT: Report Currency]; show_all_transaction (character varying) [COMMENT: Show Outstanding Ledger Only]; expand (boolean) [COMMENT: Expand]. Total columns: 14. Statistics: 10 nullable, 1 with defaults, 0 with length constraints.


List all fields in the report.account.report_hash_integrity model. or Show me the fields of report.account.report_hash_integrity.

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


What business logic is in sh.tsp.top.purchasing.product? or How to query sh.tsp.top.purchasing.product data?

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


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

Response: Foreign keys in weight_scale_barcode_format_line: create_uid -> res_users.id [constraint: weight_scale_barcode_format_line_create_uid_fkey]; parent_id -> weight_scale_barcode_format.id [constraint: weight_scale_barcode_format_line_parent_id_fkey]; write_uid -> res_users.id [constraint: weight_scale_barcode_format_line_write_uid_fkey]. Total foreign key relationships: 3. Referenced tables: res_users, weight_scale_barcode_format.


What methods are available in mrp.bom.tools? or Which fields in mrp.bom.tools are computed?

Response: The mrp.bom.tools model is defined in module: equip3_manuf_masterdata. It has 5 computed fields: company_id, allowed_operation_ids, operation_two_ids, display_name, __last_update. Stored computed fields: company_id. Related fields: company_id -> bom_id.company_id, operation_two_ids -> bom_id.operation_two_ids. Original module methods: _compute_allowed_operation_ids, _onchange_product_id.


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

Response: The z_report_wizard table has 8 columns and 4 foreign key relationships. It stores data related to z report 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: 7, columns with defaults: 1.


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

Response: Columns in purchase_change_request_line: id (integer) [NOT NULL] [DEFAULT: nextval('purchase_change_request_line_id_seq'::regclass)] [PRECISION: 32]; purchase_chn_req_id (integer) [PRECISION: 32] [COMMENT: Purchase]; product_id (integer) [PRECISION: 32] [COMMENT: Product]; planned_amount (double precision) [PRECISION: 53] [COMMENT: Current Planned Amount]; new_amount (double precision) [PRECISION: 53] [COMMENT: New Planned Amount]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 9. Statistics: 8 nullable, 1 with defaults, 0 with length constraints.


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

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


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

Response: The wizard_vendor_deposit table has 7 columns and 2 foreign key relationships. It stores data related to wizard vendor deposit in the system. The table has 1 indexes for performance optimization. Column types: integer: 3, text: 1, boolean: 1, timestamp without time zone: 2. Nullable columns: 6, columns with defaults: 1.


How is account.common.report implemented technically? or Which fields are stored computed fields in account.common.report?

Response: The account.common.report 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: _onchange_company_id, _build_contexts, _print_report, check_report.


What fields are readonly in material.request.line.show.stock? or How to work with material.request.line.show.stock fields?

Response: To use the material.request.line.show.stock 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 fields does cust.credit.limit.report.wizard have? or What are the available fields for cust.credit.limit.report.wizard?

Response: The cust.credit.limit.report.wizard model has 10 fields. Field types distribution: many2many: 2, many2one: 3, integer: 1, char: 1, datetime: 3. Computed fields: 2. Field details: partner_ids (many2many) -> res.partner [module: equip3_sale_other_operation]; company_ids (many2many) -> res.company [module: equip3_sale_other_operation]; branch_id (many2one) [required] -> res.branch [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].


Show me the relational structure of product.removal. or What one2many fields are in product.removal?

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


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

Response: The access.management model has 16 relational fields: user_ids -> res.users; hide_menu_ids -> ir.ui.menu; hide_field_ids -> hide.field; remove_action_ids -> remove.action; access_domain_ah_ids -> access.domain.ah; hide_view_nodes_ids -> hide.view.nodes; self_module_menu_ids -> ir.ui.menu; self_model_ids -> ir.model; hide_chatter_ids -> hide.chatter; company_ids -> res.company; hide_filters_groups_ids -> hide.filters.groups; field_conditional_access_ids -> field.conditional.access; access_group_ids -> access.group; access_res_group_ids -> res.groups; create_uid -> res.users; write_uid -> res.users. Many2many fields: user_ids, hide_menu_ids, self_module_menu_ids, self_model_ids, company_ids, access_group_ids, access_res_group_ids. One2many fields: hide_field_ids, remove_action_ids, access_domain_ah_ids, hide_view_nodes_ids, hide_chatter_ids, hide_filters_groups_ids, field_conditional_access_ids.


What operations can I perform on calendar.event.cancel.wizard? or How to create records in calendar.event.cancel.wizard?

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


Which fields are stored computed fields in account.cashbox.wizard.bank.line? or How is account.cashbox.wizard.bank.line implemented technically?

Response: The account.cashbox.wizard.bank.line model is defined in module: allfresh_mod_pos. It has 4 computed fields: currency_id, is_closing_line, display_name, __last_update. Stored computed fields: none. Related fields: currency_id -> cashbox_id.currency_id, is_closing_line -> account_cashbox_wizard_bank_id.is_closing_wizard. Original module methods: .


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

Response: The account_asset_category table has 37 columns and 16 foreign key relationships. It stores data related to account asset category in the system. The table has 3 indexes for performance optimization. Column types: integer: 20, boolean: 7, character varying: 6, double precision: 1, date: 1, timestamp without time zone: 2. Nullable columns: 20, columns with defaults: 1.


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

Response: To use the resource.calendar model, you need to provide values for required fields: name, tz. Readonly fields: two_weeks_explanation, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [required]; attendance_ids [computed]; global_leave_ids [computed]; tz [required] [has_default]; two_weeks_explanation [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 receipt.payment.line.credit. or What data can be stored in receipt.payment.line.credit?

Response: The receipt.payment.line.credit model has 20 fields. Field types distribution: many2one: 7, date: 2, monetary: 5, boolean: 1, integer: 1, char: 1, datetime: 3. Computed fields: 2. Field details: line_id (many2one) [readonly] -> receipt.payment [module: equip3_accounting_operation]; currency_id (many2one) -> res.currency [module: equip3_accounting_operation]; invoice_id (many2one) [readonly] -> account.move [module: equip3_accounting_operation]; account_id (many2one) [readonly] -> account.account [module: equip3_accounting_operation]; invoice_date (date) [readonly] [module: equip3_accounting_operation]; invoice_date_due (date) [readonly] [module: equip3_accounting_operation]; original_amount (monetary) [readonly] [module: equip3_accounting_operation]; base_amount (monetary) [readonly] [module: equip3_accounting_operation]; original_unreconcile (monetary) [readonly] [module: equip3_accounting_operation]; base_unreconcile (monetary) [readonly] [module: equip3_accounting_operation]; is_full_reconcile (boolean) [module: equip3_accounting_operation]; amount (monetary) [module: equip3_accounting_operation]; payment_id (many2one) -> account.payment [module: equip3_accounting_operation]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


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

Response: Columns in calendar_alarm: id (integer) [NOT NULL] [DEFAULT: nextval('calendar_alarm_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [NOT NULL] [COMMENT: Name]; alarm_type (character varying) [NOT NULL] [COMMENT: Type]; duration (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Remind Before]; interval (character varying) [NOT NULL] [COMMENT: Unit]; duration_minutes (integer) [PRECISION: 32] [COMMENT: Duration in minutes]; 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: 5 nullable, 1 with defaults, 0 with length constraints.


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

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


Describe the crm.salesperson.tracking.history model in Odoo. or Can you explain the purpose of crm.salesperson.tracking.history?

Response: The crm.salesperson.tracking.history model represents crm.salesperson.tracking.history in the ERP system. It contains 11 fields and is used to manage crm.salesperson.tracking.history data. Defined in module: equip3_crm_tracking. Key fields include: sales_person_name, history_date, track_lan_lng, track_hist, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What is the user.order.dic model? or Can you explain the purpose of user.order.dic?

Response: The user.order.dic model represents user.order.dic in the ERP system. It contains 20 fields and is used to manage user.order.dic data. Defined in module: equip3_sale_report. Key fields include: report_id, list_order, saleperson, payment_report_id, list_pay, list_product, sale_analysis_id, prduct_profit_id, product, sale_categ_id, categ, product_indent_id, category_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: Foreign keys in blanketwiz_blanketwiz: create_uid -> res_users.id [constraint: blanketwiz_blanketwiz_create_uid_fkey]; write_uid -> res_users.id [constraint: blanketwiz_blanketwiz_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


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

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


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

Response: Columns in sh_tv_top_vendor_wizard: id (integer) [NOT NULL] [DEFAULT: nextval('sh_tv_top_vendor_wizard_id_seq'::regclass)] [PRECISION: 32]; type (character varying) [COMMENT: Report Type]; date_from (timestamp without time zone) [NOT NULL] [COMMENT: From Date]; date_to (timestamp without time zone) [NOT NULL] [COMMENT: To Date]; date_compare_from (timestamp without time zone) [COMMENT: Compare From Date]; date_compare_to (timestamp without time zone) [COMMENT: Compare To Date]; no_of_top_item (integer) [NOT NULL] [PRECISION: 32] [COMMENT: No of Items]; amount_total (numeric) [COMMENT: Total Purchase Amount]; currency_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Currency]; 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: 8 nullable, 1 with defaults, 0 with length constraints.


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

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


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

Response: Foreign keys in stock_warehouse_warehouse_capacity_report_rel: warehouse_capacity_report_id -> warehouse_capacity_report.id [constraint: stock_warehouse_warehouse_cap_warehouse_capacity_report_id_fkey]; stock_warehouse_id -> stock_warehouse.id [constraint: stock_warehouse_warehouse_capacity_repo_stock_warehouse_id_fkey]. Total foreign key relationships: 2. Referenced tables: stock_warehouse, warehouse_capacity_report.


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

Response: Foreign keys in project_delete_wizard_project_project_rel: project_delete_wizard_id -> project_delete_wizard.id [constraint: project_delete_wizard_project_pro_project_delete_wizard_id_fkey]; project_project_id -> project_project.id [constraint: project_delete_wizard_project_project_r_project_project_id_fkey]. Total foreign key relationships: 2. Referenced tables: project_project, project_delete_wizard.


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

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


What is the account.invoice.send model? or Can you explain the purpose of account.invoice.send?

Response: The account.invoice.send model represents Account Invoice Send in the ERP system. It contains 50 fields and is used to manage account invoice send data. Defined in module: account. Key fields include: is_email, invoice_without_email, is_print, printed, invoice_ids, composer_id, template_id, edi_format_ids, partner_id, snailmail_is_letter, snailmail_cost, invalid_addresses, invalid_invoice_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, subject, body, parent_id, attachment_ids, layout, add_sign, email_from, author_id, composition_mode, model, res_id, record_name, use_active_domain, active_domain, message_type, subtype_id, mail_activity_type_id, reply_to, no_auto_thread, is_log, partner_ids, notify, auto_delete, auto_delete_message, mail_server_id, mass_mailing_id, campaign_id, mass_mailing_name, mailing_list_ids, is_wp.


What operations can I perform on purchase.requisition.type? or What are common use cases for purchase.requisition.type?

Response: To use the purchase.requisition.type model, you need to provide values for required fields: name, exclusive, quantity_copy, line_copy. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [required]; exclusive [required] [has_default]; quantity_copy [required] [has_default]; line_copy [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 computed fields exist in stock.scrap.approval.matrix.line? or List all fields in the stock.scrap.approval.matrix.line model.

Response: The stock.scrap.approval.matrix.line model has 34 fields. Field types distribution: integer: 8, many2many: 4, many2one: 6, text: 1, datetime: 4, char: 2, boolean: 6, one2many: 3. Computed fields: 14. Field details: sequence (integer) [module: equip3_inventory_masterdata]; user_ids (many2many) [required] -> res.users [module: equip3_inventory_masterdata]; minimum_approver (integer) [required] [module: equip3_inventory_masterdata]; sc_approval_matrix (many2one) -> stock.scrap.approval.matrix [module: equip3_inventory_masterdata]; approved_users (many2many) -> res.users [module: equip3_inventory_masterdata]; state_char (text) [module: equip3_inventory_masterdata]; time_stamp (datetime) [module: equip3_inventory_masterdata]; feedback (char) [module: equip3_inventory_masterdata]; last_approved (many2one) -> res.users [module: equip3_inventory_masterdata]; approved (boolean) [module: equip3_inventory_masterdata]; sequence2 (integer) [readonly] [compute: <bound method Field._compute_related of stock.scrap.approval.matrix.line.sequence2>] [stored] [module: equip3_inventory_masterdata] [related: sequence]; scap_request_id (many2one) -> stock.scrap.request [module: equip3_inventory_control]; 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].