Describe the field structure of purchase.request.line. or Show me the fields of purchase.request.line.

Response: The purchase.request.line model has 98 fields. Field types distribution: char: 9, float: 19, many2one: 23, date: 4, text: 2, boolean: 12, selection: 6, many2many: 4, one2many: 8, monetary: 1, integer: 7, datetime: 3. Computed fields: 58. Field details: name (char) [module: purchase_request]; product_qty (float) [module: purchase_request]; request_id (many2one) [readonly] -> purchase.request [module: purchase_request]; company_id (many2one) [readonly] -> res.company [compute: <bound method Field._compute_related of purchase.request.line.company_id>] [stored] [module: purchase_request] [related: request_id.company_id]; analytic_account_id (many2one) -> account.analytic.account [module: purchase_request]; requested_by (many2one) [readonly] -> res.users [compute: <bound method Field._compute_related of purchase.request.line.requested_by>] [stored] [module: purchase_request] [related: request_id.requested_by]; assigned_to (many2one) [readonly] -> res.users [compute: <bound method Field._compute_related of purchase.request.line.assigned_to>] [stored] [module: purchase_request] [related: request_id.assigned_to]; date_start (date) [readonly] [compute: <bound method Field._compute_related of purchase.request.line.date_start>] [stored] [module: purchase_request] [related: request_id.date_start]; description (text) [compute: <bound method Field._compute_related of purchase.request.line.description>] [stored] [module: purchase_request] [related: request_id.description] [inverse: <bound method Field._inverse_related of purchase.request.line.description>]; origin (char) [readonly] [compute: <bound method Field._compute_related of purchase.request.line.origin>] [stored] [module: purchase_request] [related: request_id.origin]; is_editable (boolean) [readonly] [compute: _compute_is_editable] [not stored] [module: purchase_request]; specifications (text) [module: purchase_request]; request_state (selection) [readonly] [compute: <bound method Field._compute_related of purchase.request.line.request_state>] [stored] [module: purchase_request] [related: request_id.state]; supplier_id (many2one) [readonly] -> res.partner [compute: _compute_supplier_id] [stored] [module: purchase_request]; cancelled (boolean) [readonly] [module: purchase_request]; purchased_qty (float) [readonly] [compute: _compute_purchased_qty] [not stored] [module: purchase_request]; purchase_lines (many2many) [readonly] -> purchase.order.line [module: purchase_request]; purchase_state (selection) [readonly] [compute: _compute_purchase_state] [stored] [module: purchase_request]; move_dest_ids (one2many) -> stock.move [module: purchase_request]; orderpoint_id (many2one) -> stock.warehouse.orderpoint [module: purchase_request]; purchase_request_allocation_ids (one2many) -> purchase.request.allocation [module: purchase_request]; qty_in_progress (float) [readonly] [compute: _compute_qty] [stored] [module: purchase_request]; qty_done (float) [readonly] [compute: _compute_qty] [stored] [module: purchase_request]; qty_cancelled (float) [readonly] [compute: _compute_qty_cancelled] [stored] [module: purchase_request]; qty_to_buy (boolean) [readonly] [compute: _compute_qty_to_buy] [stored] [module: purchase_request]; pending_qty_to_receive (float) [readonly] [compute: _compute_qty_to_buy] [stored] [module: purchase_request]; estimated_cost (monetary) [module: purchase_request]; currency_id (many2one) [readonly] -> res.currency [compute: <bound method Field._compute_related of purchase.request.line.currency_id>] [not stored] [module: purchase_request] [related: company_id.currency_id]; mr_line_id (many2one) -> material.request.line [module: equip3_inventory_operation]; cancelled_qty (float) [readonly] [module: equip3_inventory_operation]; branch_id (many2one) [readonly] -> res.branch [compute: <bound method Field._compute_related of purchase.request.line.branch_id>] [not stored] [module: equip3_purchase_operation] [related: request_id.branch_id]; sequence (integer) [module: equip3_purchase_operation]; sequence2 (integer) [module: equip3_purchase_operation]; remaning_qty (float) [readonly] [compute: _compute_new_remaning_qty] [not stored] [module: equip3_purchase_operation]; purchase_req_budget (float) [readonly] [module: equip3_purchase_operation]; rem_budget (float) [readonly] [module: equip3_purchase_operation]; purchase_req_state (selection) [readonly] [compute: <bound method Field._compute_related of purchase.request.line.purchase_req_state>] [stored] [module: equip3_purchase_operation] [related: request_id.purchase_req_state]; assigned_to_partner_id (many2one) [readonly] -> res.partner [compute: <bound method Field._compute_related of purchase.request.line.assigned_to_partner_id>] [stored] [module: equip3_purchase_operation] [related: assigned_to.partner_id]; set_order (char) [readonly] [compute: _compute_order_id] [stored] [module: equip3_purchase_operation]; is_goods_orders (boolean) [readonly] [compute: <bound method Field._compute_related of purchase.request.line.is_goods_orders>] [stored] [module: equip3_purchase_operation] [related: request_id.is_goods_orders]; is_services_orders (boolean) [readonly] [compute: <bound method Field._compute_related of purchase.request.line.is_services_orders>] [stored] [module: equip3_purchase_operation] [related: request_id.is_services_orders]; price_total (float) [readonly] [compute: _compute_price_total] [not stored] [module: equip3_purchase_operation]; dest_loc_id (many2one) [readonly] -> stock.warehouse [compute: compute_destination] [stored] [module: equip3_purchase_operation]; picking_type_dest (many2one) -> stock.picking.type [module: equip3_purchase_operation]; current_qty (float) [readonly] [compute: _compute_current_qty] [stored] [module: equip3_purchase_operation]; date_required (date) [required] [readonly] [compute: compute_receipt] [stored] [module: equip3_purchase_operation]; product_uom_id (many2one) -> uom.uom [module: equip3_purchase_operation]; product_uom_category_id (many2one) [readonly] -> uom.category [compute: <bound method Field._compute_related of purchase.request.line.product_uom_category_id>] [not stored] [module: equip3_purchase_operation] [related: product_id.uom_id.category_id]; incoming_stock (float) [readonly] [compute: _compute_incoming_stock] [stored] [module: equip3_purchase_operation]; purchase_req_budget_2 (float) [readonly] [compute: _get_purchase_req_budget] [not stored] [module: equip3_accounting_salepurchase_operation]; realized_amount (float) [module: equip3_accounting_salepurchase_operation]; confirm_purchase_req_budget (float) [module: equip3_accounting_salepurchase_operation]; confirm_realized_amount (float) [module: equip3_accounting_salepurchase_operation]; confirm_budget_data (boolean) [module: equip3_accounting_salepurchase_operation]; analytic_account_group_ids (many2many) -> account.analytic.tag [module: equip3_purchase_other_operation]; purchase_order (char) [readonly] [compute: _compute_purchase_order] [not stored] [module: equip3_purchase_other_operation]; agreement_id (many2one) -> purchase.agreement [module: equip3_purchase_other_operation]; agreement_state (selection) [readonly] [compute: <bound method Field._compute_related of purchase.request.line.agreement_state>] [not stored] [module: equip3_purchase_other_operation] [related: agreement_id.state]; tender_qty (float) [readonly] [compute: _compute_tender_qty] [stored] [module: equip3_purchase_other_operation]; tender_line_ids (one2many) -> purchase.agreement.line [module: equip3_purchase_other_operation]; purchase_order_line_ids (one2many) -> purchase.order.line [module: equip3_purchase_other_operation]; qty_received (float) [readonly] [compute: _compute_qty_received] [stored] [module: equip3_purchase_other_operation]; is_assets_orders (boolean) [readonly] [compute: <bound method Field._compute_related of purchase.request.line.is_assets_orders>] [stored] [module: equip3_purchase_asset] [related: request_id.is_assets_orders]; product_id (many2one) [required] -> product.product [module: equip3_purchase_asset]; barcode (char) [module: allfresh_mod_purchase]; merchendise_id (many2one) -> merchendise.code [module: allfresh_mod_purchase]; activity_ids (one2many) -> mail.activity [module: mail]; activity_state (selection) [readonly] [compute: _compute_activity_state] [not stored] [module: mail]; activity_user_id (many2one) -> res.users [compute: <bound method Field._compute_related of purchase.request.line.activity_user_id>] [not stored] [module: mail] [related: activity_ids.user_id] [inverse: <bound method Field._inverse_related of purchase.request.line.activity_user_id>]; activity_type_id (many2one) -> mail.activity.type [compute: <bound method Field._compute_related of purchase.request.line.activity_type_id>] [not stored] [module: mail] [related: activity_ids.activity_type_id] [inverse: <bound method Field._inverse_related of purchase.request.line.activity_type_id>]; activity_type_icon (char) [readonly] [compute: <bound method Field._compute_related of purchase.request.line.activity_type_icon>] [not stored] [module: mail] [related: activity_ids.icon]; activity_date_deadline (date) [readonly] [compute: _compute_activity_date_deadline] [not stored] [module: mail]; my_activity_date_deadline (date) [readonly] [compute: _compute_my_activity_date_deadline] [not stored] [module: mail]; activity_summary (char) [compute: <bound method Field._compute_related of purchase.request.line.activity_summary>] [not stored] [module: mail] [related: activity_ids.summary] [inverse: <bound method Field._inverse_related of purchase.request.line.activity_summary>]; activity_exception_decoration (selection) [readonly] [compute: _compute_activity_exception_type] [not stored] [module: mail]; activity_exception_icon (char) [readonly] [compute: _compute_activity_exception_type] [not stored] [module: mail]; message_is_follower (boolean) [readonly] [compute: _compute_is_follower] [not stored] [module: mail]; message_follower_ids (one2many) -> mail.followers [module: mail]; message_partner_ids (many2many) [readonly] -> res.partner [compute: _get_followers] [not stored] [module: mail]; message_channel_ids (many2many) [readonly] -> mail.channel [compute: _get_followers] [not stored] [module: mail]; message_ids (one2many) -> mail.message [module: mail]; message_unread (boolean) [readonly] [compute: _get_message_unread] [not stored] [module: mail]; message_unread_counter (integer) [readonly] [compute: _get_message_unread] [not stored] [module: mail]; message_needaction (boolean) [readonly] [compute: _get_message_needaction] [not stored] [module: mail]; message_needaction_counter (integer) [readonly] [compute: _get_message_needaction] [not stored] [module: mail]; message_has_error (boolean) [readonly] [compute: _compute_message_has_error] [not stored] [module: mail]; message_has_error_counter (integer) [readonly] [compute: _compute_message_has_error] [not stored] [module: mail]; message_attachment_count (integer) [readonly] [compute: _compute_message_attachment_count] [not stored] [module: mail]; message_main_attachment_id (many2one) -> ir.attachment [module: mail]; website_message_ids (one2many) -> mail.message [module: portal]; message_has_sms_error (boolean) [readonly] [compute: _compute_message_has_sms_error] [not stored] [module: sms]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


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

Response: Columns in pos_pack_operation_lot: id (integer) [NOT NULL] [DEFAULT: nextval('pos_pack_operation_lot_id_seq'::regclass)] [PRECISION: 32]; pos_order_line_id (integer) [PRECISION: 32] [COMMENT: Pos Order Line]; lot_name (character varying) [COMMENT: Lot Name]; 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]; quantity (double precision) [PRECISION: 53] [COMMENT: Quantity]; lot_id (integer) [PRECISION: 32] [COMMENT: Lot/Serial Number]. Total columns: 9. Statistics: 8 nullable, 1 with defaults, 0 with length constraints.


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

Response: Foreign keys in product_category_sh_purchase_product_indent_wizard_rel: sh_purchase_product_indent_wizard_id -> sh_purchase_product_indent_wizard.id [constraint: product_category_sh_purchase__sh_purchase_product_indent_w_fkey]; product_category_id -> product_category.id [constraint: product_category_sh_purchase_product_i_product_category_id_fkey]. Total foreign key relationships: 2. Referenced tables: product_category, sh_purchase_product_indent_wizard.


Can you explain the purpose of resource.test? or What is the resource.test model?

Response: The resource.test model represents Test Resource Model in the ERP system. It contains 12 fields and is used to manage test resource model data. Defined in module: resource. Key fields include: name, resource_id, company_id, resource_calendar_id, tz, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Tell me about the report.equip3_inventory_reports.expiring_product_calendar model. or What is the report.equip3_inventory_reports.expiring_product_calendar model?

Response: The report.equip3_inventory_reports.expiring_product_calendar model represents Expiring Product Calendar Report in the ERP system. It contains 3 fields and is used to manage expiring product calendar report data. Defined in module: equip3_inventory_reports. Key fields include: id, display_name, __last_update.


What is the account.cashbox.wizard.validate model? or Can you explain the purpose of account.cashbox.wizard.validate?

Response: The account.cashbox.wizard.validate model represents account.cashbox.wizard.validate in the ERP system. It contains 9 fields and is used to manage account.cashbox.wizard.validate data. Defined in module: equip3_pos_cashbox. Key fields include: pin, account_cashbox_wizard_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What fields does ai.generate.training.data have? or Describe the field structure of ai.generate.training.data.

Response: The ai.generate.training.data model has 28 fields. Field types distribution: selection: 3, integer: 4, boolean: 10, text: 1, float: 4, char: 1, many2one: 2, datetime: 3. Computed fields: 2. Field details: data_source (selection) [required] [module: ai_chat_agent]; output_format (selection) [required] [module: ai_chat_agent]; num_examples (integer) [module: ai_chat_agent]; all_datas (boolean) [module: ai_chat_agent]; run_in_queue (boolean) [module: ai_chat_agent]; training_data (text) [module: ai_chat_agent]; use_cache (boolean) [module: ai_chat_agent]; cache_ttl (integer) [module: ai_chat_agent]; generate_validation (boolean) [module: ai_chat_agent]; validation_split_ratio (float) [module: ai_chat_agent]; max_validation_ratio (float) [module: ai_chat_agent]; validation_strategy (selection) [module: ai_chat_agent]; validation_examples_count (integer) [module: ai_chat_agent]; enable_quality_scoring (boolean) [module: ai_chat_agent]; quality_threshold (float) [module: ai_chat_agent]; enable_diverse_patterns (boolean) [module: ai_chat_agent]; include_metadata (boolean) [module: ai_chat_agent]; enable_paraphrasing (boolean) [module: ai_chat_agent]; paraphrase_ratio (float) [module: ai_chat_agent]; compress_output (boolean) [module: ai_chat_agent]; split_by_model (boolean) [module: ai_chat_agent]; 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 query account.common.journal.report data? or How to create records in account.common.journal.report?

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


What are the relationships in product.packaging? or What models are connected to product.packaging?

Response: The product.packaging model has 7 relational fields: product_uom_id -> uom.uom; company_id -> res.company; product_id -> product.product; filter_value_ids -> product.attribute.value; measure_ids -> measure.for.packaging; create_uid -> res.users; write_uid -> res.users. Many2many fields: product_id, filter_value_ids, measure_ids. One2many fields: none.


What are the available fields for sh.qc.team? or What field types are used in sh.qc.team?

Response: The sh.qc.team model has 50 fields. Field types distribution: many2one: 12, char: 9, many2many: 3, one2many: 4, selection: 3, date: 2, boolean: 5, integer: 7, datetime: 3, text: 1, html: 1. Computed fields: 32. Field details: sh_logged_user (many2one) [readonly] -> res.users [module: sh_inventory_mrp_qc]; name (char) [required] [module: sh_inventory_mrp_qc]; email (char) [module: sh_inventory_mrp_qc]; user_ids (many2many) -> res.users [module: sh_inventory_mrp_qc]; sh_employee (many2one) -> hr.employee [module: sh_inventory_mrp_qc]; company_id (many2one) [required] -> res.company [module: sh_inventory_mrp_qc]; name_id (char) [readonly] [module: sh_inventory_mrp_qc]; alias_id (many2one) [required] -> mail.alias [module: sh_inventory_mrp_qc]; activity_ids (one2many) -> mail.activity [module: mail]; activity_state (selection) [readonly] [compute: _compute_activity_state] [not stored] [module: mail]; activity_user_id (many2one) -> res.users [compute: <bound method Field._compute_related of sh.qc.team.activity_user_id>] [not stored] [module: mail] [related: activity_ids.user_id] [inverse: <bound method Field._inverse_related of sh.qc.team.activity_user_id>]; activity_type_id (many2one) -> mail.activity.type [compute: <bound method Field._compute_related of sh.qc.team.activity_type_id>] [not stored] [module: mail] [related: activity_ids.activity_type_id] [inverse: <bound method Field._inverse_related of sh.qc.team.activity_type_id>]; activity_type_icon (char) [readonly] [compute: <bound method Field._compute_related of sh.qc.team.activity_type_icon>] [not stored] [module: mail] [related: activity_ids.icon]; activity_date_deadline (date) [readonly] [compute: _compute_activity_date_deadline] [not stored] [module: mail]; my_activity_date_deadline (date) [readonly] [compute: _compute_my_activity_date_deadline] [not stored] [module: mail]; activity_summary (char) [compute: <bound method Field._compute_related of sh.qc.team.activity_summary>] [not stored] [module: mail] [related: activity_ids.summary] [inverse: <bound method Field._inverse_related of sh.qc.team.activity_summary>]; activity_exception_decoration (selection) [readonly] [compute: _compute_activity_exception_type] [not stored] [module: mail]; activity_exception_icon (char) [readonly] [compute: _compute_activity_exception_type] [not stored] [module: mail]; message_is_follower (boolean) [readonly] [compute: _compute_is_follower] [not stored] [module: mail]; message_follower_ids (one2many) -> mail.followers [module: mail]; message_partner_ids (many2many) [readonly] -> res.partner [compute: _get_followers] [not stored] [module: mail]; message_channel_ids (many2many) [readonly] -> mail.channel [compute: _get_followers] [not stored] [module: mail]; message_ids (one2many) -> mail.message [module: mail]; message_unread (boolean) [readonly] [compute: _get_message_unread] [not stored] [module: mail]; message_unread_counter (integer) [readonly] [compute: _get_message_unread] [not stored] [module: mail]; message_needaction (boolean) [readonly] [compute: _get_message_needaction] [not stored] [module: mail]; message_needaction_counter (integer) [readonly] [compute: _get_message_needaction] [not stored] [module: mail]; message_has_error (boolean) [readonly] [compute: _compute_message_has_error] [not stored] [module: mail]; message_has_error_counter (integer) [readonly] [compute: _compute_message_has_error] [not stored] [module: mail]; message_attachment_count (integer) [readonly] [compute: _compute_message_attachment_count] [not stored] [module: mail]; message_main_attachment_id (many2one) -> ir.attachment [module: mail]; website_message_ids (one2many) -> mail.message [module: portal]; message_has_sms_error (boolean) [readonly] [compute: _compute_message_has_sms_error] [not stored] [module: sms]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None]; alias_name (char) [compute: <bound method Field._compute_related of sh.qc.team.alias_name>] [not stored] [module: None] [related: alias_id.alias_name] [inverse: <bound method Field._inverse_related of sh.qc.team.alias_name>]; alias_model_id (many2one) [required] -> ir.model [compute: <bound method Field._compute_related of sh.qc.team.alias_model_id>] [not stored] [module: None] [related: alias_id.alias_model_id] [inverse: <bound method Field._inverse_related of sh.qc.team.alias_model_id>]; alias_user_id (many2one) -> res.users [compute: <bound method Field._compute_related of sh.qc.team.alias_user_id>] [not stored] [module: None] [related: alias_id.alias_user_id] [inverse: <bound method Field._inverse_related of sh.qc.team.alias_user_id>]; alias_defaults (text) [required] [compute: <bound method Field._compute_related of sh.qc.team.alias_defaults>] [not stored] [module: None] [related: alias_id.alias_defaults] [inverse: <bound method Field._inverse_related of sh.qc.team.alias_defaults>]; alias_force_thread_id (integer) [compute: <bound method Field._compute_related of sh.qc.team.alias_force_thread_id>] [not stored] [module: None] [related: alias_id.alias_force_thread_id] [inverse: <bound method Field._inverse_related of sh.qc.team.alias_force_thread_id>]; alias_domain (char) [readonly] [compute: <bound method Field._compute_related of sh.qc.team.alias_domain>] [not stored] [module: None] [related: alias_id.alias_domain] [inverse: <bound method Field._inverse_related of sh.qc.team.alias_domain>]; alias_parent_model_id (many2one) -> ir.model [compute: <bound method Field._compute_related of sh.qc.team.alias_parent_model_id>] [not stored] [module: None] [related: alias_id.alias_parent_model_id] [inverse: <bound method Field._inverse_related of sh.qc.team.alias_parent_model_id>]; alias_parent_thread_id (integer) [compute: <bound method Field._compute_related of sh.qc.team.alias_parent_thread_id>] [not stored] [module: None] [related: alias_id.alias_parent_thread_id] [inverse: <bound method Field._inverse_related of sh.qc.team.alias_parent_thread_id>]; alias_bounced_content (html) [compute: <bound method Field._compute_related of sh.qc.team.alias_bounced_content>] [not stored] [module: None] [related: alias_id.alias_bounced_content] [inverse: <bound method Field._inverse_related of sh.qc.team.alias_bounced_content>]; alias_contact (selection) [required] [compute: <bound method Field._compute_related of sh.qc.team.alias_contact>] [not stored] [module: None] [related: alias_id.alias_contact] [inverse: <bound method Field._inverse_related of sh.qc.team.alias_contact>].


What does the account.payment.term model represent? or How is account.payment.term used in the system?

Response: The account.payment.term model represents Payment Terms in the ERP system. It contains 42 fields and is used to manage payment terms data. Defined in module: account. Key fields include: interest_type, interest_percentage, account_id, name, active, note, line_ids, company_id, sequence, branch_id, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: Foreign keys in stock_landed_cost_lines: account_id -> account_account.id [constraint: stock_landed_cost_lines_account_id_fkey]; cost_id -> stock_landed_cost.id [constraint: stock_landed_cost_lines_cost_id_fkey]; create_uid -> res_users.id [constraint: stock_landed_cost_lines_create_uid_fkey]; product_id -> product_product.id [constraint: stock_landed_cost_lines_product_id_fkey]; write_uid -> res_users.id [constraint: stock_landed_cost_lines_write_uid_fkey]. Total foreign key relationships: 5. Referenced tables: product_product, stock_landed_cost, account_account, res_users.


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

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


What is the calendar.event.cancel.wizard model? or Can you explain the purpose of calendar.event.cancel.wizard?

Response: The calendar.event.cancel.wizard model represents Get Meeting Cancel Reason in the ERP system. It contains 8 fields and is used to manage get meeting cancel reason data. Defined in module: equip3_crm_operation. Key fields include: cancel_reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: Foreign keys in sh_mpo_merge_purchase_order_wizard: create_uid -> res_users.id [constraint: sh_mpo_merge_purchase_order_wizard_create_uid_fkey]; partner_id -> res_partner.id [constraint: sh_mpo_merge_purchase_order_wizard_partner_id_fkey]; purchase_order_id -> purchase_order.id [constraint: sh_mpo_merge_purchase_order_wizard_purchase_order_id_fkey]; write_uid -> res_users.id [constraint: sh_mpo_merge_purchase_order_wizard_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: res_partner, res_users, purchase_order.


What foreign keys exist in vendor.evaluation.template.line? or What models are connected to vendor.evaluation.template.line?

Response: The vendor.evaluation.template.line model has 3 relational fields: evaluation_template_id -> vendor.evaluation.template; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


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

Response: Foreign keys in purchase_agreement_legal_document: create_uid -> res_users.id [constraint: purchase_agreement_legal_document_create_uid_fkey]; legal_document_id -> purchase_agreement.id [constraint: purchase_agreement_legal_document_legal_document_id_fkey]; partner_id -> res_partner.id [constraint: purchase_agreement_legal_document_partner_id_fkey]; write_uid -> res_users.id [constraint: purchase_agreement_legal_document_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: res_partner, purchase_agreement, res_users.


What methods are defined in do.approval.matrix original module? or Describe the implementation of do.approval.matrix.

Response: The do.approval.matrix model is defined in module: equip3_inventory_operation. It has 23 computed fields: level, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, display_name, __last_update. Stored computed fields: none. Related fields: activity_user_id -> activity_ids.user_id, activity_type_id -> activity_ids.activity_type_id, activity_type_icon -> activity_ids.icon, activity_summary -> activity_ids.summary. Original module methods: compute_level, check_if_location_exists, onchange_warehouse.


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

Response: Foreign keys in vendor_deposit_history_rel: deposit_id -> vendor_deposit.id [constraint: vendor_deposit_history_rel_deposit_id_fkey]; move_id -> account_move.id [constraint: vendor_deposit_history_rel_move_id_fkey]. Total foreign key relationships: 2. Referenced tables: vendor_deposit, account_move.


What fields does bank.account.account have? or What field types are used in bank.account.account?

Response: The bank.account.account model has 12 fields. Field types distribution: char: 3, many2one: 5, integer: 1, datetime: 3. Computed fields: 2. Field details: acc_number (char) [required] [module: equip3_accounting_masterdata]; bank_id (many2one) -> res.bank [module: equip3_accounting_masterdata]; bank_bic (char) [module: equip3_accounting_masterdata]; company_id (many2one) -> res.company [module: equip3_accounting_masterdata]; branch_id (many2one) -> res.branch [module: equip3_accounting_masterdata]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


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

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


What are the relationships in mail.activity.mixin? or How does mail.activity.mixin relate to other models?

Response: The mail.activity.mixin model has 3 relational fields: activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type. Many2many fields: none. One2many fields: activity_ids.


How is pick.product.replenish used in the system? or Describe the pick.product.replenish model in Odoo.

Response: The pick.product.replenish model represents Pick Product Replenish in the ERP system. It contains 9 fields and is used to manage pick product replenish data. Defined in module: equip3_inventory_masterdata. Key fields include: product_id, product_tmpl_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What are the relationships in account.bank.statement.line.wizard? or What one2many fields are in account.bank.statement.line.wizard?

Response: The account.bank.statement.line.wizard model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


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

Response: Foreign keys in crm_salesperson_tracking: create_uid -> res_users.id [constraint: crm_salesperson_tracking_create_uid_fkey]; sales_person -> res_users.id [constraint: crm_salesperson_tracking_sales_person_fkey]; write_uid -> res_users.id [constraint: crm_salesperson_tracking_write_uid_fkey]. Total foreign key relationships: 3. Referenced tables: res_users.


What computed fields exist in im_livechat.channel? or What are the available fields for im_livechat.channel?

Response: The im_livechat.channel model has 30 fields. Field types distribution: char: 11, boolean: 4, text: 1, integer: 3, binary: 1, many2many: 1, one2many: 3, html: 1, many2one: 2, datetime: 3. Computed fields: 10. Field details: name (char) [required] [module: im_livechat]; button_text (char) [module: im_livechat]; default_message (char) [module: im_livechat]; input_placeholder (char) [module: im_livechat]; header_background_color (char) [module: im_livechat]; title_color (char) [module: im_livechat]; button_background_color (char) [module: im_livechat]; button_text_color (char) [module: im_livechat]; web_page (char) [readonly] [compute: _compute_web_page_link] [not stored] [module: im_livechat]; are_you_inside (boolean) [readonly] [compute: _are_you_inside] [not stored] [module: im_livechat]; script_external (text) [readonly] [compute: _compute_script_external] [not stored] [module: im_livechat]; nbr_channel (integer) [readonly] [compute: _compute_nbr_channel] [not stored] [module: im_livechat]; image_128 (binary) [module: im_livechat]; user_ids (many2many) -> res.users [module: im_livechat]; channel_ids (one2many) -> mail.channel [module: im_livechat]; rule_ids (one2many) -> im_livechat.channel.rule [module: im_livechat]; website_published (boolean) [compute: <bound method Field._compute_related of im_livechat.channel.website_published>] [not stored] [module: website] [related: is_published] [inverse: <bound method Field._inverse_related of im_livechat.channel.website_published>]; is_published (boolean) [module: website]; can_publish (boolean) [readonly] [compute: _compute_can_publish] [not stored] [module: website]; website_url (char) [readonly] [compute: _compute_website_url] [not stored] [module: website]; website_description (html) [module: website_livechat]; rating_ids (one2many) -> rating.rating [module: rating]; rating_percentage_satisfaction (integer) [readonly] [compute: _compute_rating_percentage_satisfaction] [not stored] [module: rating]; 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 relationships in purchase.tender.xls.report? or What foreign keys exist in purchase.tender.xls.report?

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


How is sh.purchase.details.report.wizard used in the system? or Can you explain the purpose of sh.purchase.details.report.wizard?

Response: The sh.purchase.details.report.wizard model represents purchase details report wizard model in the ERP system. It contains 12 fields and is used to manage purchase details report wizard model data. Defined in module: sh_purchase_reports. Key fields include: start_date, end_date, state, company_ids, branch_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How to work with order.picking fields? or How to create records in order.picking?

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


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

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


List all relational fields in replenishment.history.wizard. or What models are connected to replenishment.history.wizard?

Response: The replenishment.history.wizard model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


How do I use the sale.data.margin.line model? or How to query sale.data.margin.line data?

Response: To use the sale.data.margin.line 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 indexes exist on product_template_note_rel? or What is stored in product_template_note_rel?

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


Which fields in base.partner.merge.automatic.wizard are computed? or What are the technical details of base.partner.merge.automatic.wizard?

Response: The base.partner.merge.automatic.wizard model is defined in module: base. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: default_get, _get_fk_on, _update_foreign_keys, _update_reference_fields, _get_summable_fields, _update_values, _merge, _log_merge_operation, _generate_query, _compute_selected_groupby, _partner_use_in, _get_ordered_partner, _compute_models, action_skip, _action_next_screen, _process_query, action_start_manual_process, action_start_automatic_process, parent_migration_process_cb, action_update_all_process, action_merge, create.


What one2many fields are in sh.sale.details.report.wizard? or What foreign keys exist in sh.sale.details.report.wizard?

Response: The sh.sale.details.report.wizard model has 8 relational fields: team_ids -> crm.team; company_ids -> res.company; company_id -> res.company; payments -> payment.sale.details.report; taxes -> tax.sale.details.report; products -> product.sale.details.report; create_uid -> res.users; write_uid -> res.users. Many2many fields: team_ids, company_ids. One2many fields: payments, taxes, products.


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

Response: The crm_lead_crm_lead2opportunity_partner_rel table has 2 columns and 2 foreign key relationships. It stores data related to crm lead crm lead2opportunity partner 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 approved_users_delivery_partner_rel. or What tables are connected to approved_users_delivery_partner_rel?

Response: Foreign keys in approved_users_delivery_partner_rel: do_id -> do_approval_matrix_line.id [constraint: approved_users_delivery_partner_rel_do_id_fkey]; user_id -> res_users.id [constraint: approved_users_delivery_partner_rel_user_id_fkey]. Total foreign key relationships: 2. Referenced tables: do_approval_matrix_line, res_users.


How do I use the pos.category model? or How to query pos.category data?

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


What is the ram.tags model? or Can you explain the purpose of ram.tags?

Response: The ram.tags model represents RMA Tags in the ERP system. It contains 8 fields and is used to manage rma tags data. Defined in module: dev_rma. Key fields include: name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Show me the fields of theme.website.menu. or Describe the field structure of theme.website.menu.

Response: The theme.website.menu model has 14 fields. Field types distribution: char: 3, many2one: 4, boolean: 1, integer: 2, one2many: 1, datetime: 3. Computed fields: 2. Field details: name (char) [required] [module: website]; url (char) [module: website]; page_id (many2one) -> theme.website.page [module: website]; new_window (boolean) [module: website]; sequence (integer) [module: website]; parent_id (many2one) -> theme.website.menu [module: website]; copy_ids (one2many) [readonly] -> website.menu [module: website]; 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 report.equip3_pos_report.report_top_selling? or Which fields are required in report.equip3_pos_report.report_top_selling?

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


How does product.attribute.custom.value relate to other models? or What models are connected to product.attribute.custom.value?

Response: The product.attribute.custom.value model has 4 relational fields: custom_product_template_attribute_value_id -> product.template.attribute.value; sale_order_line_id -> sale.order.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


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

Response: The purchase_agreement_approval_matrix table has 16 columns and 14 foreign key relationships. It stores data related to purchase agreement approval matrix in the system. The table has 2 indexes for performance optimization. Column types: integer: 9, character varying: 3, double precision: 2, timestamp without time zone: 2. Nullable columns: 12, columns with defaults: 1.


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

Response: The account_move_line_account_tax_rel table has 2 columns and 2 foreign key relationships. It stores data related to account move line account tax 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 purchase.custom.checklist model in Odoo. or Can you explain the purpose of purchase.custom.checklist?

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


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

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


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

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


What are common use cases for new.product? or How to query new.product data?

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


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

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


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

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


What columns have default values in send_notifications_rn_users_config_settings_rel2? or What fields are available in send_notifications_rn_users_config_settings_rel2?

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


How do I use the calendar.contacts model? or What are common use cases for calendar.contacts?

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


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

Response: The ks_ninja_dashboard_item_action table has 8 columns and 3 foreign key relationships. It stores data related to ks ninja dashboard item action in the system. The table has 1 indexes for performance optimization. Column types: integer: 4, character varying: 2, timestamp without time zone: 2. Nullable columns: 7, columns with defaults: 1.


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

Response: Columns in create_recurring_invoice: id (integer) [NOT NULL] [DEFAULT: nextval('create_recurring_invoice_id_seq'::regclass)] [PRECISION: 32]; start_date (date) [NOT NULL] [COMMENT: 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 relational fields in pmps.adv.settings. or Show me the relational structure of pmps.adv.settings.

Response: The pmps.adv.settings model has 5 relational fields: company_id -> res.company; sh_pmps_pro_field_ids -> ir.model.fields; sh_pmps_pro_attr_ids -> product.attribute; create_uid -> res.users; write_uid -> res.users. Many2many fields: sh_pmps_pro_field_ids, sh_pmps_pro_attr_ids. One2many fields: none.


How do I use the mailing.mailing.schedule.date model? or How to query mailing.mailing.schedule.date data?

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


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

Response: Foreign keys in ir_model: create_uid -> res_users.id [constraint: ir_model_create_uid_fkey]; website_form_default_field_id -> ir_model_fields.id [constraint: ir_model_website_form_default_field_id_fkey]; write_uid -> res_users.id [constraint: ir_model_write_uid_fkey]. Total foreign key relationships: 3. Referenced tables: res_users, ir_model_fields.


List all relational fields in account.invoice.to.draft. or What are the relationships in account.invoice.to.draft?

Response: The account.invoice.to.draft model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


What modules define report.sh_purchase_reports.sh_vend_po_analysis_doc? or Which fields are stored computed fields in report.sh_purchase_reports.sh_vend_po_analysis_doc?

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


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

Response: The account_pettycash_fund_close table has 9 columns and 4 foreign key relationships. It stores data related to account pettycash fund close in the system. The table has 1 indexes for performance optimization. Column types: integer: 5, date: 1, double precision: 1, timestamp without time zone: 2. Nullable columns: 6, columns with defaults: 1.


Describe the field structure of account.payment.register. or Which fields are required in account.payment.register?

Response: The account.payment.register model has 73 fields. Field types distribution: date: 4, monetary: 6, char: 7, boolean: 14, many2one: 17, many2many: 7, selection: 5, integer: 3, float: 4, one2many: 1, binary: 1, html: 1, datetime: 3. Computed fields: 37. Field details: payment_date (date) [required] [module: account]; amount (monetary) [compute: _compute_amount] [stored] [module: account]; communication (char) [compute: _compute_communication] [stored] [module: account]; group_payment (boolean) [compute: _compute_group_payment] [stored] [module: account]; currency_id (many2one) -> res.currency [compute: _compute_currency_id] [stored] [module: account]; journal_id (many2one) -> account.journal [compute: _compute_journal_id] [stored] [module: account]; company_currency_id (many2one) [readonly] -> res.currency [compute: <bound method Field._compute_related of account.payment.register.company_currency_id>] [not stored] [module: account] [related: company_id.currency_id]; line_ids (many2many) [readonly] -> account.move.line [module: account]; payment_type (selection) [readonly] [compute: _compute_from_lines] [stored] [module: account]; partner_type (selection) [readonly] [compute: _compute_from_lines] [stored] [module: account]; source_amount (monetary) [readonly] [compute: _compute_from_lines] [stored] [module: account]; source_amount_currency (monetary) [readonly] [compute: _compute_from_lines] [stored] [module: account]; source_currency_id (many2one) [readonly] -> res.currency [compute: _compute_from_lines] [stored] [module: account]; can_edit_wizard (boolean) [readonly] [compute: _compute_from_lines] [stored] [module: account]; can_group_payments (boolean) [readonly] [compute: _compute_from_lines] [stored] [module: account]; company_id (many2one) [readonly] -> res.company [compute: _compute_from_lines] [stored] [module: account]; partner_id (many2one) [readonly] -> res.partner [compute: _compute_from_lines] [stored] [module: account]; payment_method_id (many2one) -> account.payment.method [compute: _compute_payment_method_id] [stored] [module: account]; available_payment_method_ids (many2many) [readonly] -> account.payment.method [compute: _compute_payment_method_fields] [not stored] [module: account]; hide_payment_method (boolean) [readonly] [compute: _compute_payment_method_fields] [not stored] [module: account]; payment_difference (monetary) [readonly] [compute: _compute_payment_difference] [not stored] [module: account]; payment_difference_handling (selection) [module: account]; writeoff_account_id (many2one) -> account.account [module: account]; writeoff_label (char) [module: account]; show_partner_bank_account (boolean) [readonly] [compute: _compute_show_require_partner_bank] [not stored] [module: account]; require_partner_bank_account (boolean) [readonly] [compute: _compute_show_require_partner_bank] [not stored] [module: account]; country_code (char) [readonly] [compute: <bound method Field._compute_related of account.payment.register.country_code>] [not stored] [module: account] [related: company_id.country_id.code]; is_prepayment (boolean) [module: equip3_accounting_recurring]; prepayment_journal_id (many2one) -> account.journal [module: equip3_accounting_recurring]; start_date (date) [module: equip3_accounting_recurring]; end_date (date) [readonly] [compute: _onchange_stop_recurring_interval] [not stored] [module: equip3_accounting_recurring]; recurring_interval (integer) [module: equip3_accounting_recurring]; recurring_interval_unit (selection) [module: equip3_accounting_recurring]; stop_recurring_interval (integer) [module: equip3_accounting_recurring]; stop_recurring_interval_unit (selection) [module: equip3_accounting_recurring]; revenue_account (many2one) -> account.account [module: equip3_accounting_recurring]; move_type (char) [module: equip3_accounting_recurring]; is_show_prepayment (boolean) [readonly] [compute: _compute_is_show_prepayment] [not stored] [module: equip3_accounting_recurring]; payment_token_id (many2one) -> payment.token [compute: _compute_payment_token_id] [stored] [module: payment_fix_register_token]; suitable_payment_token_partner_ids (many2many) [readonly] -> res.partner [compute: _compute_suitable_payment_token_partner_ids] [not stored] [module: payment_fix_register_token]; payment_method_code (char) [readonly] [compute: <bound method Field._compute_related of account.payment.register.payment_method_code>] [not stored] [module: payment_fix_register_token] [related: payment_method_id.code]; apply_manual_currency_exchange (boolean) [module: sr_manual_currency_exchange_rate]; manual_currency_exchange_rate (float) [module: sr_manual_currency_exchange_rate]; active_manual_currency_rate (boolean) [module: sr_manual_currency_exchange_rate]; receipt_approval_matrix_id (many2one) [readonly] -> approval.matrix.accounting [compute: _get_receipt_approval_matrix] [not stored] [module: equip3_accounting_operation]; is_receipt_approval_matrix (boolean) [readonly] [compute: _get_receipt_approve_button_from_config] [not stored] [module: equip3_accounting_operation]; difference_ids (one2many) -> account.payment.register.payment.difference.line [module: equip3_accounting_operation]; payment_difference_amount (monetary) [readonly] [compute: _compute_payment_difference_amount] [not stored] [module: equip3_accounting_operation]; partner_bank_id (many2one) -> res.partner.bank [compute: _compute_partner_bank_id] [stored] [module: equip3_accounting_operation]; administration (boolean) [module: equip3_accounting_operation]; analytic_group_ids (many2many) -> account.analytic.tag [module: equip3_accounting_operation]; administration_account (many2one) -> account.account [module: equip3_accounting_operation]; administration_fee (monetary) [module: equip3_accounting_operation]; current_rate_id (float) [module: equip3_accounting_multicurrency]; current_inverse_rate_id (float) [readonly] [compute: _compute_current_inverse_rate_id] [stored] [module: equip3_accounting_multicurrency]; is_same_main_currency (boolean) [readonly] [compute: _compute_check_same_main_currency] [not stored] [module: equip3_accounting_multicurrency]; inverse_rate (float) [module: equip3_accounting_multicurrency]; estimasi_transfer (date) [module: allfresh_mod_account_move]; is_vendor_deposit (boolean) [readonly] [compute: compute_vendor_deposit] [not stored] [module: allfresh_mod_account_move]; validated_move_ids (many2many) -> account.move [module: allfresh_mod_account_move]; available_partner_bank_ids (many2many) -> res.partner.bank [module: equip3_pos_general]; pos_validate_file (binary) [module: equip3_pos_general]; pos_validate_filename (char) [module: equip3_pos_general]; validate_data (html) [module: equip3_pos_general]; validated_line_ids (many2many) -> account.move.line [module: equip3_pos_general]; branch_id (many2one) -> res.branch [compute: _compute_branch_id] [stored] [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].


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

Response: Foreign keys in stock_immediate_transfer_line: create_uid -> res_users.id [constraint: stock_immediate_transfer_line_create_uid_fkey]; immediate_transfer_id -> stock_immediate_transfer.id [constraint: stock_immediate_transfer_line_immediate_transfer_id_fkey]; picking_id -> stock_picking.id [constraint: stock_immediate_transfer_line_picking_id_fkey]; write_uid -> res_users.id [constraint: stock_immediate_transfer_line_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: stock_immediate_transfer, stock_picking, res_users.


How is mr_line.internal_transfer_line implemented technically? or What are the technical details of mr_line.internal_transfer_line?

Response: The mr_line.internal_transfer_line model is defined in module: equip3_inventory_operation. It has 5 computed fields: filter_warehouse_ids, filter_location_ids, dest_warehouse_id, display_name, __last_update. Stored computed fields: none. Related fields: dest_warehouse_id -> mr_id.destination_warehouse_id. Original module methods: default_get, _onchange_warehouse_id, _get_locations, calculate_current_qty.


What are the technical details of warranty.history? or What methods are defined in warranty.history original module?

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


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

Response: Foreign keys in pos_loyalty: company_id -> res_company.id [constraint: pos_loyalty_company_id_fkey]; create_uid -> res_users.id [constraint: pos_loyalty_create_uid_fkey]; product_loyalty_id -> product_product.id [constraint: pos_loyalty_product_loyalty_id_fkey]; write_uid -> res_users.id [constraint: pos_loyalty_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: product_product, res_users, res_company.


Which fields in stock.inventory.line are computed? or What methods are available in stock.inventory.line?

Response: The stock.inventory.line model is defined in module: stock. It has 21 computed fields: categ_id, company_id, state, outdated, product_tracking, inv_cost, adjustment_account_id, filtered_adjustment_account_id, is_adj_val, analytic_tag_ids, to_call_difference_qty_compute, difference_qty, currency_id, difference_unit_price, user_id_1, user_id_2, barcode, s_no, current_user_id, display_name, __last_update. Stored computed fields: categ_id, company_id, difference_qty, user_id_1, user_id_2. Related fields: categ_id -> product_id.categ_id, company_id -> inventory_id.company_id, state -> inventory_id.state, product_tracking -> product_id.tracking, inv_cost -> company_id.inv_cost, adjustment_account_id -> inventory_id.adjustment_account_id, is_adj_val -> inventory_id.is_adj_value, analytic_tag_ids -> inventory_id.analytic_tag_ids, currency_id -> company_id.currency_id, user_id_1 -> inventory_id.user_id_1, user_id_2 -> inventory_id.user_id_2, barcode -> product_id.barcode. Original module methods: _domain_location_id, _domain_product_id, _compute_difference, _compute_outdated, _onchange_quantity_context, create, write, _check_no_duplicate_line, _check_product_id, _get_move_values, _get_virtual_location, _generate_moves, action_refresh_quantity, action_reset_product_qty, _search_difference_qty, _search_outdated.


What are the available fields for overhead.time? or Which fields are required in overhead.time?

Response: The overhead.time model has 10 fields. Field types distribution: many2one: 4, float: 1, integer: 1, char: 1, datetime: 3. Computed fields: 2. Field details: product (many2one) -> product.product [module: equip3_manuf_masterdata]; cost_hr (float) [module: equip3_manuf_masterdata]; mrp_workcenter_id (many2one) -> mrp.workcenter [module: equip3_manuf_masterdata]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


How is report.dynamic_accounts_report.trial_balance implemented technically? or What methods are available in report.dynamic_accounts_report.trial_balance?

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


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

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


What are the technical details of pos.note? or What methods are available in pos.note?

Response: The pos.note model is defined in module: equip3_pos_masterdata. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: .


List all relational fields in project.delete.wizard. or Show me the relational structure of project.delete.wizard.

Response: The project.delete.wizard model has 3 relational fields: project_ids -> project.project; create_uid -> res.users; write_uid -> res.users. Many2many fields: project_ids. One2many fields: none.


Describe the many2many relations for mr_line.pr.wizard. or List all relational fields in mr_line.pr.wizard.

Response: The mr_line.pr.wizard model has 3 relational fields: pr_wizard_line -> mr_line.pr.wizard_line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: pr_wizard_line.


What field types are used in efaktur.export? or What fields does efaktur.export have?

Response: The efaktur.export model has 13 fields. Field types distribution: many2one: 4, selection: 1, date: 2, binary: 1, integer: 1, char: 1, datetime: 3. Computed fields: 2. Field details: partner_id (many2one) -> res.partner [module: equip3_accounting_efaktur]; tax_report_id (selection) [module: equip3_accounting_efaktur]; date_from (date) [module: equip3_accounting_efaktur]; date_to (date) [module: equip3_accounting_efaktur]; company_id (many2one) [readonly] -> res.company [module: equip3_accounting_efaktur]; unduh (binary) [module: equip3_accounting_efaktur]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


What fields does account.asset.category.fiscal have? or What data can be stored in account.asset.category.fiscal?

Response: The account.asset.category.fiscal model has 25 fields. Field types distribution: many2one: 3, boolean: 4, selection: 6, integer: 7, date: 1, char: 1, datetime: 3. Computed fields: 3. Field details: asset_category_id (many2one) [required] -> account.asset.category [module: equip3_accounting_asset]; is_fiscal_asset_type (boolean) [readonly] [compute: _compute_is_fiscal_asset_type] [not stored] [module: equip3_accounting_asset]; method_time (selection) [module: equip3_accounting_asset]; method_number (integer) [module: equip3_accounting_asset]; method_period (integer) [module: equip3_accounting_asset]; method_end (date) [module: equip3_accounting_asset]; method (selection) [module: equip3_accounting_asset]; asset_type (selection) [module: equip3_accounting_asset]; asset_type_1 (selection) [module: equip3_accounting_asset]; sub_asset_type (selection) [module: equip3_accounting_asset]; non_building_type (selection) [module: equip3_accounting_asset]; method_number_fiscal (integer) [readonly] [module: equip3_accounting_asset]; prorata (boolean) [module: equip3_accounting_asset]; cut_off_asset_date (integer) [module: equip3_accounting_asset]; is_monthly_depreciation (boolean) [module: equip3_accounting_asset]; is_reset_january (boolean) [module: equip3_accounting_asset]; double_declining_method_number (integer) [module: equip3_accounting_asset]; double_declining_method_period (integer) [module: equip3_accounting_asset]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


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

Response: The barcode_configuration table has 34 columns and 3 foreign key relationships. It stores data related to barcode configuration in the system. The table has 1 indexes for performance optimization. Column types: integer: 16, character varying: 8, boolean: 8, timestamp without time zone: 2. Nullable columns: 24, columns with defaults: 1.


Describe the field structure of receipt.payment.line.debit. or What data can be stored in receipt.payment.line.debit?

Response: The receipt.payment.line.debit 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 data types are used in budget_scurve_account_analytic_tags_rel? or What are the length constraints in budget_scurve_account_analytic_tags_rel?

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


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

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


What are the length constraints in res_country? or What data types are used in res_country?

Response: Columns in res_country: id (integer) [NOT NULL] [DEFAULT: nextval('res_country_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [NOT NULL] [COMMENT: Country Name]; code (character varying) [LENGTH: 2] [COMMENT: Country Code]; address_format (text) [COMMENT: Layout in Reports]; address_view_id (integer) [PRECISION: 32] [COMMENT: Input View]; currency_id (integer) [PRECISION: 32] [COMMENT: Currency]; phone_code (integer) [PRECISION: 32] [COMMENT: Country Calling Code]; name_position (character varying) [COMMENT: Customer Name Position]; vat_label (character varying) [COMMENT: Vat Label]; state_required (boolean) [COMMENT: State Required]; zip_required (boolean) [COMMENT: Zip Required]; 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]; enforce_cities (boolean) [COMMENT: Enforce Cities]. Total columns: 16. Statistics: 14 nullable, 1 with defaults, 1 with length constraints.


What is the stock.scrap.request model? or Describe the stock.scrap.request model in Odoo.

Response: The stock.scrap.request model represents Stock Scrap Request in the ERP system. It contains 75 fields and is used to manage stock scrap request data. Defined in module: equip3_inventory_control. Key fields include: pu_barcode_mobile, pu_barcode_mobile_type, pu_bm_is_cont_scan, pu_bm_is_notify_on_success, pu_bm_is_notify_on_fail, pu_bm_is_sound_on_success, pu_bm_is_sound_on_fail, pu_bm_is_add_product, is_mbs_on_product_usage, company_id, branch_id, accounting, name, warehouse_id, state, scrap_ids, scrap_request_name, expire_date, date_done, scrap_type, is_product_usage, payment_method_id, is_payment_method, schedule_date, responsible_id, analytic_tag_ids, is_group_analytic_tags, scrap_state, scrap_state_1, is_product_usage_approval, approval_matrix_id, approved_matrix_ids, approval_matrix_line_id, is_approve_button, account_move_count, domain_warehouse_id, auto_scrap_notification, 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 data types are used in pos_payment? or List all columns in pos_payment.

Response: Columns in pos_payment: id (integer) [NOT NULL] [DEFAULT: nextval('pos_payment_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [COMMENT: Label]; pos_order_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Order]; amount (numeric) [NOT NULL] [COMMENT: Amount]; payment_method_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Payment Method]; payment_date (timestamp without time zone) [NOT NULL] [COMMENT: Date]; session_id (integer) [PRECISION: 32] [COMMENT: Session]; card_type (character varying) [COMMENT: Type of card used]; cardholder_name (character varying) [COMMENT: Cardholder Name]; transaction_id (character varying) [COMMENT: Payment Transaction ID]; payment_status (character varying) [COMMENT: Payment Status]; ticket (character varying) [COMMENT: Payment Receipt Info]; is_change (boolean) [COMMENT: Is this payment change?]; 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]; picking_order_id (integer) [PRECISION: 32] [COMMENT: POS Delivery Order statement]; voucher_id (integer) [PRECISION: 32] [COMMENT: Voucher]; voucher_code (character varying) [COMMENT: Voucher Code]; pos_branch_id (integer) [PRECISION: 32] [COMMENT: Branch]; ref (character varying) [COMMENT: Ref]; cheque_owner (character varying) [COMMENT: Cheque Owner]; cheque_bank_account (character varying) [COMMENT: Cheque Bank Account]; cheque_bank_id (integer) [PRECISION: 32] [COMMENT: Cheque Bank]; cheque_check_number (character varying) [COMMENT: Cheque Check Number]; cheque_card_name (character varying) [COMMENT: Cheque Card Name]; cheque_card_number (character varying) [COMMENT: Cheque Card Number]; cheque_card_type (character varying) [COMMENT: Cheque Card Type]; priority (character varying) [COMMENT: priority]; payment_card_id (integer) [PRECISION: 32] [COMMENT: Card Payment]; card_payment_number (character varying) [COMMENT: Card Payment Number]; payment_mdr_id (integer) [PRECISION: 32] [COMMENT: Payment MDR]; mdr_amount (double precision) [PRECISION: 53] [COMMENT: MDR Amount]; mdr_paid_by (character varying) [COMMENT: MDR Paid By]; total_without_mdr (double precision) [PRECISION: 53] [COMMENT: Total Amount Without MDR]; customer_deposit_id (integer) [PRECISION: 32] [COMMENT: Customer Deposit]; is_payment_edc (boolean) [COMMENT: EDC]; approval_code (character varying) [COMMENT: Approval Code]; installment_tenor (character varying) [COMMENT: Installment Tenor]; installment_amount (character varying) [COMMENT: Installment Monthly Amount]. Total columns: 41. Statistics: 36 nullable, 1 with defaults, 0 with length constraints.


Which fields are required in stock.track.line? or Show me the fields of stock.track.line.

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


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

Response: The account_pettycash table has 31 columns and 12 foreign key relationships. It stores data related to account pettycash in the system. The table has 2 indexes for performance optimization. Column types: integer: 14, character varying: 9, boolean: 1, double precision: 3, date: 2, timestamp without time zone: 2. Nullable columns: 25, columns with defaults: 1.


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

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


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

Response: Foreign keys in crm_tag_rel: lead_id -> crm_lead.id [constraint: crm_tag_rel_lead_id_fkey]; tag_id -> crm_tag.id [constraint: crm_tag_rel_tag_id_fkey]. Total foreign key relationships: 2. Referenced tables: crm_lead, crm_tag.


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

Response: Columns in mail_template: id (integer) [NOT NULL] [DEFAULT: nextval('mail_template_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [COMMENT: Name]; model_id (integer) [PRECISION: 32] [COMMENT: Applies to]; model (character varying) [COMMENT: Related Document Model]; subject (character varying) [COMMENT: Subject]; email_from (character varying) [COMMENT: From]; use_default_to (boolean) [COMMENT: Default recipients]; email_to (character varying) [COMMENT: To (Emails)]; partner_to (character varying) [COMMENT: To (Partners)]; email_cc (character varying) [COMMENT: Cc]; reply_to (character varying) [COMMENT: Reply-To]; body_html (text) [COMMENT: Body]; report_name (character varying) [COMMENT: Report Filename]; report_template (integer) [PRECISION: 32] [COMMENT: Optional report to print and attach]; mail_server_id (integer) [PRECISION: 32] [COMMENT: Outgoing Mail Server]; scheduled_date (character varying) [COMMENT: Scheduled Date]; auto_delete (boolean) [COMMENT: Auto Delete]; ref_ir_act_window (integer) [PRECISION: 32] [COMMENT: Sidebar action]; lang (character varying) [COMMENT: Language]; 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: 23. Statistics: 22 nullable, 1 with defaults, 0 with length constraints.


Can you explain the purpose of purchase.team.analysis? or How is purchase.team.analysis used in the system?

Response: The purchase.team.analysis model represents purchase.team.analysis in the ERP system. It contains 20 fields and is used to manage purchase.team.analysis data. Defined in module: equip3_purchase_report. Key fields include: days_to_approve, purchase_order_duration_to_confirm, amount_saved_from_cost_savings, number_of_successful_cost_savings, avg_amount_saved_from_cost_savings, avg_number_of_successful_cost_savings, user_id, purchase_ids, kpi_target, cost_saving_percentage, amount_purchased, cost_saving, branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Can you explain the purpose of stock.move.line? or Describe the stock.move.line model in Odoo.

Response: The stock.move.line model represents Product Moves (Stock Move Line) in the ERP system. It contains 64 fields and is used to manage product moves (stock move line) data. Defined in module: stock. Key fields include: picking_id, move_id, company_id, product_id, product_uom_id, product_uom_category_id, product_qty, product_uom_qty, qty_done, package_id, package_level_id, lot_id, lot_name, date, owner_id, location_id, location_dest_id, lots_visible, picking_code, picking_type_use_create_lots, picking_type_use_existing_lots, state, is_initial_demand_editable, is_locked, consume_line_ids, produce_line_ids, reference, tracking, origin, picking_type_entire_packs, description_picking, workorder_id, production_id, expiration_date, scrap_return_move_id, is_double_product_usage, sale_price, sequence, move_line_sequence, product_type, quant_package_ids, result_package_id, is_quant_update, force_to_reserve_qty, source_picking_id, source_move_id, is_batch_shipping_packing, is_batch_shipping_delivery, assembly_id, scrap_sale_price, is_low_stock, description, kitchen_id, finish_good_rework_id, exp_date, remark, pos_branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What methods are defined in dev.credit.note.wizard original module? or What is the module hierarchy for dev.credit.note.wizard?

Response: The dev.credit.note.wizard model is defined in module: dev_rma. It has 3 computed fields: picking_type_code, display_name, __last_update. Stored computed fields: none. Related fields: picking_type_code -> rma_id.picking_type_code. Original module methods: action_credit_notes.


What is the module hierarchy for bo.request.matrix.reject? or Describe the implementation of bo.request.matrix.reject.

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


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

Response: Foreign keys in target_kpi: branch_id -> res_branch.id [constraint: target_kpi_branch_id_fkey]; company_id -> res_company.id [constraint: target_kpi_company_id_fkey]; create_uid -> res_users.id [constraint: target_kpi_create_uid_fkey]; message_main_attachment_id -> ir_attachment.id [constraint: target_kpi_message_main_attachment_id_fkey]; purchase_team_id -> dev_purchase_team.id [constraint: target_kpi_purchase_team_id_fkey]; user_id -> res_users.id [constraint: target_kpi_user_id_fkey]; write_uid -> res_users.id [constraint: target_kpi_write_uid_fkey]. Total foreign key relationships: 7. Referenced tables: res_company, ir_attachment, res_users, res_branch, dev_purchase_team.


What columns does res_company have? or What is the res_company table?

Response: The res_company table has 363 columns and 65 foreign key relationships. It stores data related to res company in the system. The table has 4 indexes for performance optimization. Column types: integer: 83, character varying: 86, timestamp without time zone: 2, text: 5, bytea: 1, boolean: 172, date: 5, double precision: 8, numeric: 1. Nullable columns: 339, columns with defaults: 1.


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

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


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

Response: The sh_sale_pro_field_ids_rel_comp_table table has 2 columns and 2 foreign key relationships. It stores data related to sh sale pro field ids rel comp table in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


Which fields in extract.rfq.wizard are computed? or How is extract.rfq.wizard implemented technically?

Response: The extract.rfq.wizard model is defined in module: equip3_purchase_operation. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: default_get, action_extract_rfq.


Which fields are stored computed fields in stock.scrap.request.matrix.reject? or What methods are defined in stock.scrap.request.matrix.reject original module?

Response: The stock.scrap.request.matrix.reject model is defined in module: equip3_inventory_control. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: action_reject.


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

Response: Foreign keys in pos_order_log: campaign_id -> utm_campaign.id [constraint: pos_order_log_campaign_id_fkey]; config_id -> pos_config.id [constraint: pos_order_log_config_id_fkey]; create_uid -> res_users.id [constraint: pos_order_log_create_uid_fkey]; medium_id -> utm_medium.id [constraint: pos_order_log_medium_id_fkey]; message_main_attachment_id -> ir_attachment.id [constraint: pos_order_log_message_main_attachment_id_fkey]; session_id -> pos_session.id [constraint: pos_order_log_session_id_fkey]; source_id -> utm_source.id [constraint: pos_order_log_source_id_fkey]; write_uid -> res_users.id [constraint: pos_order_log_write_uid_fkey]. Total foreign key relationships: 8. Referenced tables: utm_source, utm_medium, pos_session, pos_config, ir_attachment, res_users, utm_campaign.


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

Response: To use the report.accounting_pdf_reports.report_partnerledger 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 columns does rn_matrix_reject have? or How many columns are in rn_matrix_reject?

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


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

Response: Foreign keys in account_account_journal_entry_report_rel: journal_entry_report_id -> journal_entry_report.id [constraint: account_account_journal_entry_repo_journal_entry_report_id_fkey]; account_account_id -> account_account.id [constraint: account_account_journal_entry_report_re_account_account_id_fkey]. Total foreign key relationships: 2. Referenced tables: journal_entry_report, account_account.


What computed fields exist in purchase.request.wizard.line? or What data can be stored in purchase.request.wizard.line?

Response: The purchase.request.wizard.line model has 17 fields. Field types distribution: many2one: 8, integer: 2, char: 2, float: 1, date: 1, datetime: 3. Computed fields: 3. Field details: mr_id (many2one) -> material.request [module: equip3_inventory_operation]; no (integer) [readonly] [module: equip3_inventory_operation]; product_id (many2one) -> product.product [module: equip3_inventory_operation]; description (char) [module: equip3_inventory_operation]; uom_id (many2one) -> uom.uom [module: equip3_inventory_operation]; qty_purchase (float) [required] [module: equip3_inventory_operation]; request_date (date) [required] [module: equip3_inventory_operation]; mr_pr_wizard (many2one) -> purchase.request.wizard [module: equip3_inventory_operation]; mr_line_id (many2one) -> material.request.line [module: equip3_inventory_operation]; dest_warehouse_id (many2one) [readonly] -> stock.warehouse [compute: <bound method Field._compute_related of purchase.request.wizard.line.dest_warehouse_id>] [not stored] [module: equip3_inventory_operation] [related: mr_id.destination_warehouse_id]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


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

Response: Foreign keys in groups_hide_filters_groups_store_filters_groups_rel: store_id -> store_filters_groups.id [constraint: groups_hide_filters_groups_store_filters_groups_r_store_id_fkey]; hide_id -> hide_filters_groups.id [constraint: groups_hide_filters_groups_store_filters_groups_re_hide_id_fkey]. Total foreign key relationships: 2. Referenced tables: hide_filters_groups, store_filters_groups.


What columns does account_equity_move have? or How many columns are in account_equity_move?

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


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

Response: Foreign keys in hide_view_nodes: access_management_id -> access_management.id [constraint: hide_view_nodes_access_management_id_fkey]; create_uid -> res_users.id [constraint: hide_view_nodes_create_uid_fkey]; model_id -> ir_model.id [constraint: hide_view_nodes_model_id_fkey]; write_uid -> res_users.id [constraint: hide_view_nodes_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: ir_model, access_management, res_users.


What is the milestone.contract.template.line model? or How is milestone.contract.template.line used in the system?

Response: The milestone.contract.template.line model represents Details Milestone Contract Term Template in the ERP system. It contains 11 fields and is used to manage details milestone contract term template data. Defined in module: equip3_purchase_operation. Key fields include: template_id, checklist_template_id, name, contract_term, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: Foreign keys in product_configurator_no_variant_attribute_value_rel: product_template_attribute_value_id -> product_template_attribute_value.id [constraint: product_configurator_no_varia_product_template_attribute_v_fkey]; sale_product_configurator_id -> sale_product_configurator.id [constraint: product_configurator_no_varia_sale_product_configurator_id_fkey]. Total foreign key relationships: 2. Referenced tables: product_template_attribute_value, sale_product_configurator.


What operations can I perform on sh.quality.check? or How to query sh.quality.check data?

Response: To use the sh.quality.check model, you need to provide values for required fields: none. Readonly fields: state, 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: state [readonly] [has_default] [no_copy]; activity_state [readonly] [computed] [no_copy]; activity_user_id [computed] [no_copy]; activity_type_id [computed] [no_copy]; activity_type_icon [readonly] [computed] [no_copy]; activity_date_deadline [readonly] [computed] [no_copy]; my_activity_date_deadline [readonly] [computed] [no_copy]; activity_summary [computed] [no_copy]; activity_exception_decoration [readonly] [computed] [no_copy]; activity_exception_icon [readonly] [computed] [no_copy]; message_is_follower [readonly] [computed] [no_copy]; message_partner_ids [readonly] [computed] [no_copy]; message_channel_ids [readonly] [computed] [no_copy]; message_unread [readonly] [computed] [no_copy]; message_unread_counter [readonly] [computed] [no_copy]; message_needaction [readonly] [computed] [no_copy]; message_needaction_counter [readonly] [computed] [no_copy]; message_has_error [readonly] [computed] [no_copy]; message_has_error_counter [readonly] [computed] [no_copy]; message_attachment_count [readonly] [computed] [no_copy]; message_has_sms_error [readonly] [computed] [no_copy]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


List all relational fields in crm.salesperson.tracking.history. or What are the relationships in crm.salesperson.tracking.history?

Response: The crm.salesperson.tracking.history model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


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

Response: The im_livechat_channel_country_rel table has 2 columns and 2 foreign key relationships. It stores data related to im livechat channel country rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.