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

Response: Foreign keys in account_chart_template: account_journal_suspense_account_id -> account_account_template.id [constraint: account_chart_template_account_journal_suspense_account_id_fkey]; create_uid -> res_users.id [constraint: account_chart_template_create_uid_fkey]; currency_id -> res_currency.id [constraint: account_chart_template_currency_id_fkey]; default_cash_difference_expense_account_id -> account_account_template.id [constraint: account_chart_template_default_cash_difference_expense_acc_fkey]; default_cash_difference_income_account_id -> account_account_template.id [constraint: account_chart_template_default_cash_difference_income_acco_fkey]; default_pos_receivable_account_id -> account_account_template.id [constraint: account_chart_template_default_pos_receivable_account_id_fkey]; expense_currency_exchange_account_id -> account_account_template.id [constraint: account_chart_template_expense_currency_exchange_account_i_fkey]; income_currency_exchange_account_id -> account_account_template.id [constraint: account_chart_template_income_currency_exchange_account_id_fkey]; parent_id -> account_chart_template.id [constraint: account_chart_template_parent_id_fkey]; property_account_expense_categ_id -> account_account_template.id [constraint: account_chart_template_property_account_expense_categ_id_fkey]; property_account_expense_id -> account_account_template.id [constraint: account_chart_template_property_account_expense_id_fkey]; property_account_income_categ_id -> account_account_template.id [constraint: account_chart_template_property_account_income_categ_id_fkey]; property_account_income_id -> account_account_template.id [constraint: account_chart_template_property_account_income_id_fkey]; property_account_payable_id -> account_account_template.id [constraint: account_chart_template_property_account_payable_id_fkey]; property_account_receivable_id -> account_account_template.id [constraint: account_chart_template_property_account_receivable_id_fkey]; property_advance_tax_payment_account_id -> account_account_template.id [constraint: account_chart_template_property_advance_tax_payment_accoun_fkey]; property_cash_basis_base_account_id -> account_account_template.id [constraint: account_chart_template_property_cash_basis_base_account_id_fkey]; property_stock_account_input_categ_id -> account_account_template.id [constraint: account_chart_template_property_stock_account_input_categ__fkey]; property_stock_account_output_categ_id -> account_account_template.id [constraint: account_chart_template_property_stock_account_output_categ_fkey]; property_stock_valuation_account_id -> account_account_template.id [constraint: account_chart_template_property_stock_valuation_account_id_fkey]; property_tax_payable_account_id -> account_account_template.id [constraint: account_chart_template_property_tax_payable_account_id_fkey]; property_tax_receivable_account_id -> account_account_template.id [constraint: account_chart_template_property_tax_receivable_account_id_fkey]; write_uid -> res_users.id [constraint: account_chart_template_write_uid_fkey]. Total foreign key relationships: 23. Referenced tables: account_chart_template, account_account_template, res_users, res_currency.


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

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


How is assets.approval.matrix used in the system? or What is the assets.approval.matrix model?

Response: The assets.approval.matrix model represents Assets Approval Matrix in the ERP system. It contains 43 fields and is used to manage assets approval matrix data. Defined in module: equip3_accounting_masterdata. Key fields include: name, company_id, branch_id, assets_approval_matrix_line_ids, is_assets_approval, 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.


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

Response: The receivable_opening_balance table has 12 columns and 4 foreign key relationships. It stores data related to receivable opening balance in the system. The table has 1 indexes for performance optimization. Column types: integer: 5, character varying: 2, date: 2, double precision: 1, timestamp without time zone: 2. Nullable columns: 11, columns with defaults: 1.


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

Response: Foreign keys in setu_inventory_turnover_analysis_bi_report: product_category_id -> product_category.id [constraint: setu_inventory_turnover_analysis_bi_re_product_category_id_fkey]; company_id -> res_company.id [constraint: setu_inventory_turnover_analysis_bi_report_company_id_fkey]; create_uid -> res_users.id [constraint: setu_inventory_turnover_analysis_bi_report_create_uid_fkey]; product_id -> product_product.id [constraint: setu_inventory_turnover_analysis_bi_report_product_id_fkey]; warehouse_id -> stock_warehouse.id [constraint: setu_inventory_turnover_analysis_bi_report_warehouse_id_fkey]; wizard_id -> setu_inventory_turnover_analysis_report.id [constraint: setu_inventory_turnover_analysis_bi_report_wizard_id_fkey]; write_uid -> res_users.id [constraint: setu_inventory_turnover_analysis_bi_report_write_uid_fkey]. Total foreign key relationships: 7. Referenced tables: product_product, stock_warehouse, product_category, res_company, res_users, setu_inventory_turnover_analysis_report.


What models are connected to web_editor.converter.test.sub? or Show me the relational structure of web_editor.converter.test.sub.

Response: The web_editor.converter.test.sub model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


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

Response: Foreign keys in sh_purchase_payment_report_wizard: create_uid -> res_users.id [constraint: sh_purchase_payment_report_wizard_create_uid_fkey]; write_uid -> res_users.id [constraint: sh_purchase_payment_report_wizard_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


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

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


Tell me about the export.efaktur model. or Describe the export.efaktur model in Odoo.

Response: The export.efaktur model represents export.efaktur in the ERP system. It contains 12 fields and is used to manage export.efaktur data. Defined in module: equip3_accounting_efaktur. Key fields include: partner_id, tax_report_id, date_from, date_to, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What field types are used in project.project? or What computed fields exist in project.project?

Response: The project.project model has 87 fields. Field types distribution: char: 9, html: 2, boolean: 16, integer: 13, many2one: 18, many2many: 7, one2many: 8, selection: 6, date: 2, datetime: 4, text: 2. Computed fields: 43. Field details: name (char) [required] [module: project]; description (html) [module: project]; active (boolean) [module: project]; sequence (integer) [module: project]; partner_id (many2one) -> res.partner [module: project]; partner_email (char) [compute: _compute_partner_email] [stored] [module: project] [inverse: _inverse_partner_email]; partner_phone (char) [compute: _compute_partner_phone] [stored] [module: project] [inverse: _inverse_partner_phone]; company_id (many2one) [required] -> res.company [module: project]; currency_id (many2one) [readonly] -> res.currency [compute: <bound method Field._compute_related of project.project.currency_id>] [not stored] [module: project] [related: company_id.currency_id]; favorite_user_ids (many2many) -> res.users [module: project]; is_favorite (boolean) [compute: _compute_is_favorite] [not stored] [module: project] [inverse: _inverse_is_favorite]; label_tasks (char) [module: project]; tasks (one2many) -> project.task [module: project]; resource_calendar_id (many2one) [readonly] -> resource.calendar [compute: <bound method Field._compute_related of project.project.resource_calendar_id>] [not stored] [module: project] [related: company_id.resource_calendar_id]; type_ids (many2many) -> project.task.type [module: project]; task_count (integer) [readonly] [compute: _compute_task_count] [not stored] [module: project]; task_ids (one2many) -> project.task [module: project]; color (integer) [module: project]; user_id (many2one) -> res.users [module: project]; alias_enabled (boolean) [compute: _compute_alias_enabled] [not stored] [module: project]; alias_id (many2one) [required] -> mail.alias [module: project]; privacy_visibility (selection) [required] [module: project]; allowed_user_ids (many2many) -> res.users [compute: _compute_allowed_users] [not stored] [module: project] [inverse: _inverse_allowed_user]; allowed_internal_user_ids (many2many) -> res.users [module: project]; allowed_portal_user_ids (many2many) -> res.users [module: project]; doc_count (integer) [readonly] [compute: _compute_attached_docs_count] [not stored] [module: project]; date_start (date) [module: project]; date (date) [module: project]; subtask_project_id (many2one) -> project.project [module: project]; allow_subtasks (boolean) [module: project]; allow_recurring_tasks (boolean) [module: project]; rating_request_deadline (datetime) [readonly] [compute: _compute_rating_request_deadline] [stored] [module: project]; rating_active (boolean) [module: project]; rating_status (selection) [required] [module: project]; rating_status_period (selection) [required] [module: project]; allow_timesheets (boolean) [compute: _compute_allow_timesheets] [stored] [module: hr_timesheet]; analytic_account_id (many2one) -> account.analytic.account [module: hr_timesheet]; timesheet_ids (one2many) -> account.analytic.line [module: hr_timesheet]; timesheet_encode_uom_id (many2one) [readonly] -> uom.uom [compute: <bound method Field._compute_related of project.project.timesheet_encode_uom_id>] [not stored] [module: hr_timesheet] [related: company_id.timesheet_encode_uom_id]; total_timesheet_time (integer) [readonly] [compute: _compute_total_timesheet_time] [not stored] [module: hr_timesheet]; encode_uom_in_days (boolean) [readonly] [compute: _compute_encode_uom_in_days] [not stored] [module: hr_timesheet]; sale_line_id (many2one) -> sale.order.line [module: sale_project]; sale_order_id (many2one) -> sale.order [module: sale_project]; bill_type (selection) [module: sale_timesheet]; pricing_type (selection) [module: sale_timesheet]; sale_line_employee_ids (one2many) -> project.sale.line.employee.map [module: sale_timesheet]; allow_billable (boolean) [module: sale_timesheet]; display_create_order (boolean) [readonly] [compute: _compute_display_create_order] [not stored] [module: sale_timesheet]; timesheet_product_id (many2one) -> product.product [compute: _compute_timesheet_product_id] [stored] [module: sale_timesheet]; warning_employee_rate (boolean) [readonly] [compute: _compute_warning_employee_rate] [not stored] [module: sale_timesheet]; 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]; rating_ids (one2many) -> rating.rating [module: rating]; rating_percentage_satisfaction (integer) [readonly] [compute: _compute_rating_percentage_satisfaction] [not stored] [module: rating]; access_url (char) [readonly] [compute: _compute_access_url] [not stored] [module: portal]; access_token (char) [module: portal]; access_warning (text) [readonly] [compute: _compute_access_warning] [not stored] [module: portal]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None]; alias_name (char) [compute: <bound method Field._compute_related of project.project.alias_name>] [not stored] [module: None] [related: alias_id.alias_name] [inverse: <bound method Field._inverse_related of project.project.alias_name>]; alias_model_id (many2one) [required] -> ir.model [compute: <bound method Field._compute_related of project.project.alias_model_id>] [not stored] [module: None] [related: alias_id.alias_model_id] [inverse: <bound method Field._inverse_related of project.project.alias_model_id>]; alias_user_id (many2one) -> res.users [compute: <bound method Field._compute_related of project.project.alias_user_id>] [not stored] [module: None] [related: alias_id.alias_user_id] [inverse: <bound method Field._inverse_related of project.project.alias_user_id>]; alias_defaults (text) [required] [compute: <bound method Field._compute_related of project.project.alias_defaults>] [not stored] [module: None] [related: alias_id.alias_defaults] [inverse: <bound method Field._inverse_related of project.project.alias_defaults>]; alias_force_thread_id (integer) [compute: <bound method Field._compute_related of project.project.alias_force_thread_id>] [not stored] [module: None] [related: alias_id.alias_force_thread_id] [inverse: <bound method Field._inverse_related of project.project.alias_force_thread_id>]; alias_domain (char) [readonly] [compute: <bound method Field._compute_related of project.project.alias_domain>] [not stored] [module: None] [related: alias_id.alias_domain] [inverse: <bound method Field._inverse_related of project.project.alias_domain>]; alias_parent_model_id (many2one) -> ir.model [compute: <bound method Field._compute_related of project.project.alias_parent_model_id>] [not stored] [module: None] [related: alias_id.alias_parent_model_id] [inverse: <bound method Field._inverse_related of project.project.alias_parent_model_id>]; alias_parent_thread_id (integer) [compute: <bound method Field._compute_related of project.project.alias_parent_thread_id>] [not stored] [module: None] [related: alias_id.alias_parent_thread_id] [inverse: <bound method Field._inverse_related of project.project.alias_parent_thread_id>]; alias_bounced_content (html) [compute: <bound method Field._compute_related of project.project.alias_bounced_content>] [not stored] [module: None] [related: alias_id.alias_bounced_content] [inverse: <bound method Field._inverse_related of project.project.alias_bounced_content>]; alias_contact (selection) [required] [compute: <bound method Field._compute_related of project.project.alias_contact>] [not stored] [module: None] [related: alias_id.alias_contact] [inverse: <bound method Field._inverse_related of project.project.alias_contact>].


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

Response: Foreign keys in supplier_approval_supplier_rel: product_supplierinfo_approval_id -> product_supplierinfo_approval.id [constraint: supplier_approval_supplier_re_product_supplierinfo_approva_fkey]; res_users_id -> res_users.id [constraint: supplier_approval_supplier_rel_res_users_id_fkey]. Total foreign key relationships: 2. Referenced tables: res_users, product_supplierinfo_approval.


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

Response: Foreign keys in account_asset_fiscal_line: asset_id -> account_asset_asset.id [constraint: account_asset_fiscal_line_asset_id_fkey]; create_uid -> res_users.id [constraint: account_asset_fiscal_line_create_uid_fkey]; write_uid -> res_users.id [constraint: account_asset_fiscal_line_write_uid_fkey]. Total foreign key relationships: 3. Referenced tables: account_asset_asset, res_users.


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

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


What are the technical details of approval.reject? or How is approval.reject implemented technically?

Response: The approval.reject 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: action_reject.


How is invoice.template.footer implemented technically? or What modules define invoice.template.footer?

Response: The invoice.template.footer model is defined in module: equip3_accounting_operation. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: .


What one2many fields are in pos.profit.and.loss? or What are the relationships in pos.profit.and.loss?

Response: The pos.profit.and.loss model has 12 relational fields: pos_order_line_id -> pos.order.line; product_id -> product.product; product_uom_id -> uom.uom; pos_branch_id -> res.branch; partner_id -> res.partner; company_id -> res.company; pos_config_id -> pos.config; order_id -> pos.order; session_id -> pos.session; categ_id -> product.category; pos_categ_id -> pos.category; vendor_id -> res.partner. Many2many fields: none. One2many fields: none.


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

Response: Columns in account_bank_cashbox_line: id (integer) [NOT NULL] [DEFAULT: nextval('account_bank_cashbox_line_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [COMMENT: Name]; coin_value (numeric) [NOT NULL] [COMMENT: Coin/Bill Value]; number (integer) [PRECISION: 32] [COMMENT: #Coins/Bills]; cashbox_id (integer) [PRECISION: 32] [COMMENT: Cashbox]; pos_session_id (integer) [PRECISION: 32] [COMMENT: Session ID]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 10. Statistics: 8 nullable, 1 with defaults, 0 with length constraints.


Describe the field structure of crm.lead2opportunity.partner. or What are the available fields for crm.lead2opportunity.partner?

Response: The crm.lead2opportunity.partner model has 15 fields. Field types distribution: selection: 2, many2one: 6, many2many: 1, boolean: 1, integer: 1, char: 1, datetime: 3. Computed fields: 8. Field details: name (selection) [compute: _compute_name] [stored] [module: crm]; action (selection) [compute: _compute_action] [stored] [module: crm]; lead_id (many2one) [required] -> crm.lead [module: crm]; duplicated_lead_ids (many2many) -> crm.lead [compute: _compute_duplicated_lead_ids] [stored] [module: crm]; partner_id (many2one) -> res.partner [compute: _compute_partner_id] [stored] [module: crm]; user_id (many2one) -> res.users [compute: _compute_user_id] [stored] [module: crm]; team_id (many2one) -> crm.team [compute: _compute_team_id] [stored] [module: crm]; force_assignment (boolean) [module: crm]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


What computed fields exist in stock.picking.to.batch? or Show me the fields of stock.picking.to.batch.

Response: The stock.picking.to.batch model has 10 fields. Field types distribution: many2one: 4, selection: 1, integer: 1, char: 1, datetime: 3. Computed fields: 2. Field details: batch_id (many2one) -> stock.picking.batch [module: stock_picking_batch]; mode (selection) [module: stock_picking_batch]; user_id (many2one) -> res.users [module: stock_picking_batch]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


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

Response: The asp_asm_stock_line table has 14 columns and 7 foreign key relationships. It stores data related to asp asm stock line in the system. The table has 1 indexes for performance optimization. Column types: integer: 8, character varying: 2, numeric: 2, timestamp without time zone: 2. Nullable columns: 13, columns with defaults: 1.


Describe the implementation of stock.quant.queue. or How is stock.quant.queue implemented technically?

Response: The stock.quant.queue model is defined in module: equip3_pos_general. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: autoUpdateStock.


What foreign keys exist in stock.warn.insufficient.qty.repair? or List all relational fields in stock.warn.insufficient.qty.repair.

Response: The stock.warn.insufficient.qty.repair model has 6 relational fields: repair_id -> repair.order; product_id -> product.product; location_id -> stock.location; quant_ids -> stock.quant; create_uid -> res.users; write_uid -> res.users. Many2many fields: quant_ids. One2many fields: none.


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

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


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

Response: Columns in mail_channel_partner: id (integer) [NOT NULL] [DEFAULT: nextval('mail_channel_partner_id_seq'::regclass)] [PRECISION: 32]; custom_channel_name (character varying) [COMMENT: Custom channel name]; partner_id (integer) [PRECISION: 32] [COMMENT: Recipient]; channel_id (integer) [PRECISION: 32] [COMMENT: Channel]; fetched_message_id (integer) [PRECISION: 32] [COMMENT: Last Fetched]; seen_message_id (integer) [PRECISION: 32] [COMMENT: Last Seen]; fold_state (character varying) [COMMENT: Conversation Fold State]; is_minimized (boolean) [COMMENT: Conversation is minimized]; is_pinned (boolean) [COMMENT: Is pinned on the interface]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 13. Statistics: 12 nullable, 1 with defaults, 0 with length constraints.


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

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


What computed fields exist in restaurant.table? or What data can be stored in restaurant.table?

Response: The restaurant.table model has 17 fields. Field types distribution: char: 3, many2one: 3, selection: 1, float: 4, integer: 2, boolean: 1, datetime: 3. Computed fields: 2. Field details: name (char) [required] [module: pos_restaurant]; floor_id (many2one) -> restaurant.floor [module: pos_restaurant]; shape (selection) [required] [module: pos_restaurant]; position_h (float) [module: pos_restaurant]; position_v (float) [module: pos_restaurant]; width (float) [module: pos_restaurant]; height (float) [module: pos_restaurant]; seats (integer) [module: pos_restaurant]; color (char) [module: pos_restaurant]; active (boolean) [module: pos_restaurant]; 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 expiry_picking_confirmation_stock_production_lot_rel reference? or What relationships exist for expiry_picking_confirmation_stock_production_lot_rel?

Response: Foreign keys in expiry_picking_confirmation_stock_production_lot_rel: expiry_picking_confirmation_id -> expiry_picking_confirmation.id [constraint: expiry_picking_confirmation_s_expiry_picking_confirmation__fkey]; stock_production_lot_id -> stock_production_lot.id [constraint: expiry_picking_confirmation_stock__stock_production_lot_id_fkey]. Total foreign key relationships: 2. Referenced tables: stock_production_lot, expiry_picking_confirmation.


Show me the column structure of queue_jobs_kill. or What fields are available in queue_jobs_kill?

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


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

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


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

Response: Columns in global_search: id (integer) [NOT NULL] [DEFAULT: nextval('global_search_id_seq'::regclass)] [PRECISION: 32]; model_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Applies To]; main_field_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Name Field]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 7. Statistics: 4 nullable, 1 with defaults, 0 with length constraints.


What are the technical details of ir.config_parameter? or What methods are defined in ir.config_parameter original module?

Response: The ir.config_parameter 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: init, get_param, _get_param, set_param, create, write, unlink.


How does ai.memory.export.import.wizard relate to other models? or What are the relationships in ai.memory.export.import.wizard?

Response: The ai.memory.export.import.wizard model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


What data can be stored in pos.loyalty.category? or List all fields in the pos.loyalty.category model.

Response: The pos.loyalty.category model has 20 fields. Field types distribution: char: 6, boolean: 1, float: 3, selection: 1, binary: 2, many2one: 3, integer: 1, datetime: 3. Computed fields: 3. Field details: name (char) [required] [module: equip3_pos_membership]; code (char) [module: equip3_pos_membership]; active (boolean) [module: equip3_pos_membership]; from_point (float) [required] [module: equip3_pos_membership]; to_point (float) [required] [module: equip3_pos_membership]; coefficient (float) [required] [module: equip3_pos_membership]; member_card (selection) [module: equip3_pos_membership]; card_template_barcode (binary) [module: equip3_pos_membership]; card_template_qrcode (binary) [module: equip3_pos_membership]; card_template_barcode_name (char) [module: equip3_pos_membership]; card_template_qrcode_name (char) [module: equip3_pos_membership]; member_card_preview (char) [readonly] [compute: _compute_member_card_preview] [not stored] [module: equip3_pos_membership]; company_id (many2one) -> res.company [module: equip3_pos_membership]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


How is hr.job used in the system? or Tell me about the hr.job model.

Response: The hr.job model represents Job Position in the ERP system. It contains 33 fields and is used to manage job position data. Defined in module: hr. Key fields include: name, expected_employees, no_of_employee, no_of_recruitment, no_of_hired_employee, employee_ids, description, requirements, department_id, company_id, state, 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.


Can you explain the purpose of do.approval_matrix_line? or Describe the do.approval_matrix_line model in Odoo.

Response: The do.approval_matrix_line model represents Delivery Order Approval line in the ERP system. It contains 19 fields and is used to manage delivery order approval line data. Defined in module: equip3_inventory_operation. Key fields include: sequence, sequence1, approver, minimal_approver, approval_status, feedback, time_stamp, last_approved, approved, do_approval_matrix_id1, picking_id, approved_users, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: Foreign keys in target_activity_line_res: activity_id -> target_activity.id [constraint: target_activity_line_res_activity_id_fkey]; activity_type -> mail_activity_type.id [constraint: target_activity_line_res_activity_type_fkey]; create_uid -> res_users.id [constraint: target_activity_line_res_create_uid_fkey]; user_id -> res_users.id [constraint: target_activity_line_res_user_id_fkey]; write_uid -> res_users.id [constraint: target_activity_line_res_write_uid_fkey]. Total foreign key relationships: 5. Referenced tables: target_activity, mail_activity_type, res_users.


How is mail.template.preview used in the system? or Tell me about the mail.template.preview model.

Response: The mail.template.preview model represents Email Template Preview in the ERP system. It contains 22 fields and is used to manage email template preview data. Defined in module: mail. Key fields include: mail_template_id, model_id, resource_ref, lang, no_record, error_msg, subject, email_from, email_to, email_cc, reply_to, scheduled_date, body_html, attachment_ids, partner_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: Foreign keys in base_language_export: create_uid -> res_users.id [constraint: base_language_export_create_uid_fkey]; write_uid -> res_users.id [constraint: base_language_export_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


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

Response: Columns in stock_production_lot: id (integer) [NOT NULL] [DEFAULT: nextval('stock_production_lot_id_seq'::regclass)] [PRECISION: 32]; message_main_attachment_id (integer) [PRECISION: 32] [COMMENT: Main Attachment]; name (character varying) [NOT NULL] [COMMENT: Lot/Serial Number]; ref (character varying) [COMMENT: Internal Reference]; product_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Product]; product_uom_id (integer) [PRECISION: 32] [COMMENT: Unit of Measure]; note (text) [COMMENT: Description]; company_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Company]; 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]; expiration_date (timestamp without time zone) [COMMENT: Expiration Date]; use_date (timestamp without time zone) [COMMENT: Best before Date]; removal_date (timestamp without time zone) [COMMENT: Removal Date]; alert_date (timestamp without time zone) [COMMENT: Alert Date]; product_expiry_reminded (boolean) [COMMENT: Expiry has been reminded]; state_check (character varying) [COMMENT: Expiry State]; start_date_warranty (date) [COMMENT: Warranty Start Date]; end_date_warranty (date) [COMMENT: Warranty End Date]; renewal_times (integer) [PRECISION: 32] [COMMENT: No. of Renew]; kitchen_production_finished_id (integer) [PRECISION: 32] [COMMENT: Kitchen Production]; kitchen_production_byproduct_id (integer) [PRECISION: 32] [COMMENT: Kitchen Production]; kitchen_production_rejected_id (integer) [PRECISION: 32] [COMMENT: Kitchen Production]; kitchen_expiration_date (timestamp without time zone) [COMMENT: Kitchen Expiration Date]; kitchen_qty (double precision) [PRECISION: 53] [COMMENT: Kitchen Quantity]; finish_good_rework_byproduct_id (integer) [PRECISION: 32] [COMMENT: Finish Good Rework Byproduct]; finish_good_rework_finished_id (integer) [PRECISION: 32] [COMMENT: Finish Good Rework Finished]; finish_good_rework_rejected_id (integer) [PRECISION: 32] [COMMENT: Finish Good Rework Rejected]; assembly_production_finished_id (integer) [PRECISION: 32] [COMMENT: Assembly Production Finished]; assembly_production_byproduct_id (integer) [PRECISION: 32] [COMMENT: Assembly Production ByProduct]; assembly_production_rejected_id (integer) [PRECISION: 32] [COMMENT: Assembly Production Rejected]; assembly_expiration_date (timestamp without time zone) [COMMENT: Assembly Expiration Date]; assembly_qty (double precision) [PRECISION: 53] [COMMENT: Assmble Quantity]; active (boolean) [COMMENT: Active]; barcode (character varying) [COMMENT: Barcode]; replace_product_public_price (boolean) [COMMENT: Replace public price of product]; public_price (double precision) [PRECISION: 53] [COMMENT: Sale price]. Total columns: 38. Statistics: 34 nullable, 1 with defaults, 0 with length constraints.


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

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


What foreign keys exist in auth_totp.wizard? or What models are connected to auth_totp.wizard?

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


Can you explain the purpose of l10n_id_efaktur.efaktur.range? or Describe the l10n_id_efaktur.efaktur.range model in Odoo.

Response: The l10n_id_efaktur.efaktur.range model represents Available E-faktur range in the ERP system. It contains 11 fields and is used to manage available e-faktur range data. Defined in module: l10n_id_efaktur. Key fields include: company_id, max, min, available, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Which fields are stored computed fields in sale.order.template.line? or What modules define sale.order.template.line?

Response: The sale.order.template.line model is defined in module: sale_management. It has 4 computed fields: company_id, product_uom_category_id, display_name, __last_update. Stored computed fields: company_id. Related fields: company_id -> sale_order_template_id.company_id, product_uom_category_id -> product_id.uom_id.category_id. Original module methods: _onchange_product_id, create, write.


What fields does account.fiscal.year have? or Show me the fields of account.fiscal.year.

Response: The account.fiscal.year model has 11 fields. Field types distribution: char: 2, date: 2, many2one: 3, integer: 1, datetime: 3. Computed fields: 2. Field details: name (char) [required] [module: om_account_accountant]; date_from (date) [required] [module: om_account_accountant]; date_to (date) [required] [module: om_account_accountant]; company_id (many2one) [required] -> res.company [module: om_account_accountant]; 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 indexes exist on purchase_order_wizard_res_partner_rel? or What columns does purchase_order_wizard_res_partner_rel have?

Response: The purchase_order_wizard_res_partner_rel table has 2 columns and 2 foreign key relationships. It stores data related to purchase order wizard res 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 columns of sh_quality_alert. or List all columns in sh_quality_alert.

Response: Columns in sh_quality_alert: id (integer) [NOT NULL] [DEFAULT: nextval('sh_quality_alert_id_seq'::regclass)] [PRECISION: 32]; message_main_attachment_id (integer) [PRECISION: 32] [COMMENT: Main Attachment]; name (character varying) [COMMENT: Name]; title (character varying) [COMMENT: Title]; product_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Product]; lot_id (integer) [PRECISION: 32] [COMMENT: Lot Number]; user_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Responsible]; team_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Team]; sh_priority (character varying) [COMMENT: Priority]; color (integer) [PRECISION: 32] [COMMENT: Color Index]; sh_description (text) [COMMENT: Description]; partner_id (integer) [PRECISION: 32] [COMMENT: Partner]; stage_id (integer) [PRECISION: 32] [COMMENT: Stage]; piking_id (integer) [PRECISION: 32] [COMMENT: Picking Ref.]; company_id (integer) [PRECISION: 32] [COMMENT: Company]; 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: 19. Statistics: 15 nullable, 1 with defaults, 0 with length constraints.


What does the crm.recurring.plan model represent? or How is crm.recurring.plan used in the system?

Response: The crm.recurring.plan model represents CRM Recurring revenue plans in the ERP system. It contains 11 fields and is used to manage crm recurring revenue plans data. Defined in module: crm. Key fields include: name, number_of_months, active, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

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


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

Response: Foreign keys in purchase_quotation_excel_extended: create_uid -> res_users.id [constraint: purchase_quotation_excel_extended_create_uid_fkey]; write_uid -> res_users.id [constraint: purchase_quotation_excel_extended_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


What are common use cases for product.template.create.variant.line? or What business logic is in product.template.create.variant.line?

Response: To use the product.template.create.variant.line model, you need to provide values for required fields: attribute_id. Readonly fields: filter_value_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: attribute_id [required]; filter_value_ids [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 vendor.evaluation model? or What does the vendor.evaluation model represent?

Response: The vendor.evaluation model represents Vendor Evaluation in the ERP system. It contains 108 fields and is used to manage vendor evaluation data. Defined in module: vendor_evaluation. Key fields include: name, state, vendor, period_start, period_end, manager, is_manager, user_id, price_check, price_factor, price, price_cmt, delivery_check, delivery_factor, delivery, delivery_cmt, quality_check, quality_factor, quality, quality_cmt, document_check, document_factor, document, document_cmt, commitment_check, commitment_factor, commitment, commitment_cmt, dependability_check, dependability_factor, dependability, dependability_cmt, skill_check, skill_factor, skill, skill_cmt, support_check, support_factor, support, support_cmt, relation_check, relation_factor, relation, relation_cmt, other_check, other_factor, other, other_cmt, final_point, final_rate, on_time_rate, on_time_rate_check, on_time_rate_factor, on_time_rate_star, on_time_rate_cmt, fulfillment, fulfillment_check, fulfillment_factor, fulfillment_star, fulfillment_cmt, fulfillment_avg, on_time_rate_avg, final_point_avg, vendor_evaluation_count, evaluation_template_id, evaluation_eval_ids, email, business, date, final_cmt, branch_id, company_id, on_time_rate_res, fulfillment_res, vendor_res, final_point_res, 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 does the sh.stock.move.pass.fail model represent? or What is the sh.stock.move.pass.fail model?

Response: The sh.stock.move.pass.fail model represents Stock Move Quality Measurement Pass Fail in the ERP system. It contains 11 fields and is used to manage stock move quality measurement pass fail data. Defined in module: sh_inventory_mrp_qc. Key fields include: product_id, sh_message, sh_quality_point_id, picking_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How does approval.matrix.purchase.order relate to other models? or What models are connected to approval.matrix.purchase.order?

Response: The approval.matrix.purchase.order model has 17 relational fields: company_id -> res.company; branch_id -> res.branch; approval_matrix_purchase_order_line_ids -> approval.matrix.purchase.order.line; campaign_id -> utm.campaign; source_id -> utm.source; medium_id -> utm.medium; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: message_partner_ids, message_channel_ids. One2many fields: approval_matrix_purchase_order_line_ids, activity_ids, message_follower_ids, message_ids, website_message_ids.


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

Response: Foreign keys in pos_coupon_product_product_as_specific_product_rel: pos_coupon_id -> pos_coupon.id [constraint: pos_coupon_product_product_as_specific_produ_pos_coupon_id_fkey]; product_id -> product_product.id [constraint: pos_coupon_product_product_as_specific_product__product_id_fkey]; product_id -> product_product.id [constraint: pos_coupon_product_product_as_specific_product_product_id_fkey1]; product_id -> product_product.id [constraint: pos_coupon_product_product_as_specific_product_product_id_fkey2]; product_id -> product_product.id [constraint: pos_coupon_product_product_as_specific_product_product_id_fkey3]; product_id -> product_product.id [constraint: pos_coupon_product_product_as_specific_product_product_id_fkey4]. Total foreign key relationships: 6. Referenced tables: product_product, pos_coupon.


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

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


What foreign keys exist in purchase.product.template? or What are the relationships in purchase.product.template?

Response: The purchase.product.template model has 5 relational fields: purchase_product_template_ids -> purchase.product.template.line; branch_id -> res.branch; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: purchase_product_template_ids.


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

Response: Foreign keys in limit_request_product_brand_rel: limit_request_id -> limit_request.id [constraint: limit_request_product_brand_rel_limit_request_id_fkey]; product_brand_id -> product_brand.id [constraint: limit_request_product_brand_rel_product_brand_id_fkey]. Total foreign key relationships: 2. Referenced tables: limit_request, product_brand.


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

Response: Foreign keys in limit_request_wizard: create_uid -> res_users.id [constraint: limit_request_wizard_create_uid_fkey]; write_uid -> res_users.id [constraint: limit_request_wizard_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


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

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


How to query pos.promotion.tebus.murah data? or What are common use cases for pos.promotion.tebus.murah?

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


What data can be stored in account.tax.map.sales.line? or Describe the field structure of account.tax.map.sales.line.

Response: The account.tax.map.sales.line model has 17 fields. Field types distribution: many2one: 8, integer: 1, char: 1, datetime: 3, one2many: 3, float: 1. Computed fields: 9. Field details: company_id (many2one) [readonly] -> res.company [compute: <bound method Field._compute_related of account.tax.map.sales.line.company_id>] [not stored] [module: equip3_accounting_masterdata] [related: map_id.company_id]; sales_tax_id (many2one) -> account.tax [module: equip3_accounting_masterdata]; target_company (many2one) [readonly] -> res.company [compute: <bound method Field._compute_related of account.tax.map.sales.line.target_company>] [not stored] [module: equip3_accounting_masterdata] [related: map_id.child_company_id]; target_sales_tax (many2one) -> account.tax [module: equip3_accounting_masterdata]; map_id (many2one) [required] -> account.account.map [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]; line_ids (one2many) -> account.account.map.line [compute: <bound method Field._compute_related of account.tax.map.sales.line.line_ids>] [not stored] [module: None] [related: map_id.line_ids] [inverse: <bound method Field._inverse_related of account.tax.map.sales.line.line_ids>]; child_company_id (many2one) [required] -> res.company [compute: <bound method Field._compute_related of account.tax.map.sales.line.child_company_id>] [not stored] [module: None] [related: map_id.child_company_id] [inverse: <bound method Field._inverse_related of account.tax.map.sales.line.child_company_id>]; ownership (float) [compute: <bound method Field._compute_related of account.tax.map.sales.line.ownership>] [not stored] [module: None] [related: map_id.ownership] [inverse: <bound method Field._inverse_related of account.tax.map.sales.line.ownership>]; sales_line_ids (one2many) -> account.tax.map.sales.line [compute: <bound method Field._compute_related of account.tax.map.sales.line.sales_line_ids>] [not stored] [module: None] [related: map_id.sales_line_ids] [inverse: <bound method Field._inverse_related of account.tax.map.sales.line.sales_line_ids>]; purchase_line_ids (one2many) -> account.tax.map.purchase.line [compute: <bound method Field._compute_related of account.tax.map.sales.line.purchase_line_ids>] [not stored] [module: None] [related: map_id.purchase_line_ids] [inverse: <bound method Field._inverse_related of account.tax.map.sales.line.purchase_line_ids>].


How to query pos.zone data? or How to work with pos.zone fields?

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


Describe the field structure of free.product.lines. or What computed fields exist in free.product.lines?

Response: The free.product.lines model has 12 fields. Field types distribution: many2one: 5, char: 2, float: 1, integer: 1, datetime: 3. Computed fields: 2. Field details: product_id (many2one) [required] -> product.product [module: equip3_sale_loyalty]; description (char) [required] [module: equip3_sale_loyalty]; quantity (float) [required] [module: equip3_sale_loyalty]; uom_id (many2one) [required] -> uom.uom [module: equip3_sale_loyalty]; customer_target_id (many2one) -> customer.target [module: equip3_sale_loyalty]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


Which fields in pos.backup.orders are computed? or How is pos.backup.orders implemented technically?

Response: The pos.backup.orders model is defined in module: equip3_pos_masterdata. It has 4 computed fields: branch_id, company_id, display_name, __last_update. Stored computed fields: none. Related fields: branch_id -> config_id.pos_branch_id, company_id -> config_id.company_id. Original module methods: automaticBackupUnpaidOrders, getUnpaidOrders.


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

Response: The whatsapp_template_message_variable table has 8 columns and 3 foreign key relationships. It stores data related to whatsapp template message variable 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.


Can you explain the purpose of res.users.apikeys.show? or Tell me about the res.users.apikeys.show model.

Response: The res.users.apikeys.show model represents res.users.apikeys.show in the ERP system. It contains 4 fields and is used to manage res.users.apikeys.show data. Defined in module: base. Key fields include: key, id, display_name, __last_update.


Describe the field structure of im_livechat.report.operator. or What are the available fields for im_livechat.report.operator?

Response: The im_livechat.report.operator model has 10 fields. Field types distribution: many2one: 3, integer: 2, datetime: 2, float: 2, char: 1. Computed fields: 2. Field details: partner_id (many2one) [readonly] -> res.partner [module: im_livechat]; livechat_channel_id (many2one) [readonly] -> im_livechat.channel [module: im_livechat]; nbr_channel (integer) [readonly] [module: im_livechat]; channel_id (many2one) [readonly] -> mail.channel [module: im_livechat]; start_date (datetime) [readonly] [module: im_livechat]; time_to_answer (float) [readonly] [module: im_livechat]; duration (float) [readonly] [module: im_livechat]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field] [not stored] [module: None].


What data can be stored in product.warranty? or Which fields are required in product.warranty?

Response: The product.warranty model has 30 fields. Field types distribution: many2one: 9, char: 6, text: 1, boolean: 1, date: 2, integer: 2, one2many: 2, selection: 2, many2many: 1, float: 1, datetime: 3. Computed fields: 2. Field details: partner_id (many2one) [required] -> res.partner [module: bi_warranty_registration]; phone (char) [module: bi_warranty_registration]; email (char) [module: bi_warranty_registration]; comment (text) [module: bi_warranty_registration]; accept1 (boolean) [module: bi_warranty_registration]; product_id (many2one) [required] -> product.product [module: bi_warranty_registration]; serial_no (char) [module: bi_warranty_registration]; warranty_end_date (date) [readonly] [module: bi_warranty_registration]; merchant (char) [module: bi_warranty_registration]; renew_no (integer) [readonly] [module: bi_warranty_registration]; warranty_create_date (date) [module: bi_warranty_registration]; product_serial_id (many2one) [required] -> stock.production.lot [module: bi_warranty_registration]; warranty_history_ids (one2many) [readonly] -> warranty.history [module: bi_warranty_registration]; warranty_type (selection) [module: bi_warranty_registration]; warranty_team (many2one) -> crm.team [module: bi_warranty_registration]; tags_w (many2many) -> warranty.tag [module: bi_warranty_registration]; model_no (char) [module: bi_warranty_registration]; warranty_cost (float) [module: bi_warranty_registration]; warranty_claim_ids (one2many) [readonly] -> warranty.claim [module: bi_warranty_registration]; warranty_sales_person (many2one) -> res.users [module: bi_warranty_registration]; state (selection) [module: bi_warranty_registration]; so_id (many2one) -> sale.order [module: bi_warranty_registration]; company_id (many2one) -> res.company [module: bi_warranty_registration]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


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

Response: Foreign keys in payment_acquirer: company_id -> res_company.id [constraint: payment_acquirer_company_id_fkey]; create_uid -> res_users.id [constraint: payment_acquirer_create_uid_fkey]; journal_id -> account_journal.id [constraint: payment_acquirer_journal_id_fkey]; module_id -> ir_module_module.id [constraint: payment_acquirer_module_id_fkey]; registration_view_template_id -> ir_ui_view.id [constraint: payment_acquirer_registration_view_template_id_fkey]; view_template_id -> ir_ui_view.id [constraint: payment_acquirer_view_template_id_fkey]; website_id -> website.id [constraint: payment_acquirer_website_id_fkey]; write_uid -> res_users.id [constraint: payment_acquirer_write_uid_fkey]. Total foreign key relationships: 8. Referenced tables: website, ir_ui_view, res_company, res_users, ir_module_module, account_journal.


What operations can I perform on report.layout? or How to query report.layout data?

Response: To use the report.layout model, you need to provide values for required fields: view_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: view_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.


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

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


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

Response: The account_account_tag_account_general_ledger_rel table has 2 columns and 2 foreign key relationships. It stores data related to account account tag account general ledger rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


Can you explain the purpose of ai.model.selection.wizard? or What does the ai.model.selection.wizard model represent?

Response: The ai.model.selection.wizard model represents AI Model Selection Wizard in the ERP system. It contains 12 fields and is used to manage ai model selection wizard data. Defined in module: ai_chat_agent. Key fields include: config_id, provider, available_models_text, selected_model, error_message, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What are the technical details of pos.session.log.cashier? or Describe the implementation of pos.session.log.cashier.

Response: The pos.session.log.cashier model is defined in module: equip3_pos_general. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: .


What tables are connected to pos_payment_method_mdr? or What tables does pos_payment_method_mdr reference?

Response: Foreign keys in pos_payment_method_mdr: card_group_id -> group_card.id [constraint: pos_payment_method_mdr_card_group_id_fkey]; card_payment_id -> card_payment.id [constraint: pos_payment_method_mdr_card_payment_id_fkey]; create_uid -> res_users.id [constraint: pos_payment_method_mdr_create_uid_fkey]; payment_method_id -> pos_payment_method.id [constraint: pos_payment_method_mdr_payment_method_id_fkey]; write_uid -> res_users.id [constraint: pos_payment_method_mdr_write_uid_fkey]. Total foreign key relationships: 5. Referenced tables: pos_payment_method, card_payment, res_users, group_card.


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

Response: The do_approval_matrix_detail table has 8 columns and 4 foreign key relationships. It stores data related to do approval matrix detail in the system. The table has 1 indexes for performance optimization. Column types: integer: 5, character varying: 1, timestamp without time zone: 2. Nullable columns: 7, columns with defaults: 1.


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

Response: The transfer_log_activity table has 13 columns and 4 foreign key relationships. It stores data related to transfer log activity in the system. The table has 1 indexes for performance optimization. Column types: integer: 5, character varying: 3, timestamp without time zone: 3, double precision: 2. Nullable columns: 12, columns with defaults: 1.


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

Response: Foreign keys in sh_mrp_qc_measurement: create_uid -> res_users.id [constraint: sh_mrp_qc_measurement_create_uid_fkey]; mrp_id -> mrp_production.id [constraint: sh_mrp_qc_measurement_mrp_id_fkey]; product_id -> product_product.id [constraint: sh_mrp_qc_measurement_product_id_fkey]; quality_point_id -> sh_qc_point.id [constraint: sh_mrp_qc_measurement_quality_point_id_fkey]; workorder_id -> mrp_workorder.id [constraint: sh_mrp_qc_measurement_workorder_id_fkey]; write_uid -> res_users.id [constraint: sh_mrp_qc_measurement_write_uid_fkey]. Total foreign key relationships: 6. Referenced tables: product_product, mrp_production, mrp_workorder, res_users, sh_qc_point.


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

Response: Foreign keys in account_analytic_tag_crossovered_budget_rel: account_analytic_tag_id -> account_analytic_tag.id [constraint: account_analytic_tag_crossovered_b_account_analytic_tag_id_fkey]; crossovered_budget_id -> crossovered_budget.id [constraint: account_analytic_tag_crossovered_bud_crossovered_budget_id_fkey]. Total foreign key relationships: 2. Referenced tables: crossovered_budget, account_analytic_tag.


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

Response: Foreign keys in account_journal_customer_statement_rel: customer_statement_id -> customer_statement.id [constraint: account_journal_customer_statement_r_customer_statement_id_fkey]; account_journal_id -> account_journal.id [constraint: account_journal_customer_statement_rel_account_journal_id_fkey]. Total foreign key relationships: 2. Referenced tables: customer_statement, account_journal.


How does account.keterangan.tambahan relate to other models? or What models are connected to account.keterangan.tambahan?

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


Can you explain the purpose of blanket.quotation.line? or Tell me about the blanket.quotation.line model.

Response: The blanket.quotation.line model represents blanket.quotation.line in the ERP system. It contains 19 fields and is used to manage blanket.quotation.line data. Defined in module: equip3_purchase_other_operation. Key fields include: bq_id, product_id, vendor_id, remaining_quantity, new_quatation_quantity, blanket_order_line_id, unit_of_measure_id, unit_price, subtotal, is_goods_orders, is_services_orders, is_assets_orders, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Describe the mail.alias.mixin model in Odoo. or How is mail.alias.mixin used in the system?

Response: The mail.alias.mixin model represents Email Aliases Mixin in the ERP system. It contains 18 fields and is used to manage email aliases mixin data. Defined in module: mail. Key fields include: alias_id, id, display_name, __last_update, alias_name, alias_model_id, alias_user_id, alias_defaults, alias_force_thread_id, alias_domain, alias_parent_model_id, alias_parent_thread_id, alias_bounced_content, alias_contact, create_uid, create_date, write_uid, write_date.


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

Response: The ir.module.module model represents Module in the ERP system. It contains 41 fields and is used to manage module data. Defined in module: base. Key fields include: name, category_id, shortdesc, summary, description, description_html, author, maintainer, contributors, website, installed_version, latest_version, published_version, url, sequence, dependencies_id, exclusion_ids, auto_install, state, demo, license, menus_by_module, reports_by_module, views_by_module, application, icon, icon_image, to_buy, has_iap, version_status, imported, local_updatable, image_ids, is_installed_on_current_website, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: Columns in account_cash_flow: id (integer) [NOT NULL] [DEFAULT: nextval('account_cash_flow_id_seq'::regclass)] [PRECISION: 32]; company_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Company]; target_move (character varying) [NOT NULL] [COMMENT: Target Moves]; date_from (date) [COMMENT: Start Date]; date_to (date) [COMMENT: End Date]; today (date) [COMMENT: Report Date]; levels (character varying) [NOT NULL] [COMMENT: Levels]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]; report_currency_id (integer) [PRECISION: 32] [COMMENT: Report Currency]. Total columns: 12. Statistics: 8 nullable, 1 with defaults, 0 with length constraints.


What foreign keys exist in hr.plan.wizard? or Describe the many2many relations for hr.plan.wizard.

Response: The hr.plan.wizard model has 4 relational fields: plan_id -> hr.plan; employee_id -> hr.employee; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


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

Response: The sh_back_theme_config_settings table has 85 columns and 2 foreign key relationships. It stores data related to sh back theme config settings in the system. The table has 1 indexes for performance optimization. Column types: integer: 10, character varying: 62, boolean: 9, bytea: 2, timestamp without time zone: 2. Nullable columns: 84, columns with defaults: 1.


What are common use cases for report.dynamic_accounts_report.partner_ledger? or How do I use the report.dynamic_accounts_report.partner_ledger model?

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


What is the module hierarchy for sh.tsp.top.purchasing.product? or Describe the implementation of sh.tsp.top.purchasing.product.

Response: The sh.tsp.top.purchasing.product 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: .


How is crm.quotation.partner used in the system? or What does the crm.quotation.partner model represent?

Response: The crm.quotation.partner model represents Create new or use existing Customer on new Quotation in the ERP system. It contains 10 fields and is used to manage create new or use existing customer on new quotation data. Defined in module: sale_crm. Key fields include: action, lead_id, partner_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: Columns in dev_purchase_team: id (integer) [NOT NULL] [DEFAULT: nextval('dev_purchase_team_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [NOT NULL] [COMMENT: Purchase Name]; user_id (integer) [PRECISION: 32] [COMMENT: Team Leader]; company_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Company]; active (boolean) [COMMENT: Active]; 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]; branch_id (integer) [PRECISION: 32] [COMMENT: Branch]. Total columns: 10. Statistics: 7 nullable, 1 with defaults, 0 with length constraints.


Describe the sh.sale.category.wizard model in Odoo. or What does the sh.sale.category.wizard model represent?

Response: The sh.sale.category.wizard model represents Sale By Category Wizard in the ERP system. It contains 14 fields and is used to manage sale by category wizard data. Defined in module: sh_sale_reports. Key fields include: sh_end_date, sh_category_ids, company_ids, company_id, category_order_dic, currency_precision, sh_start_date, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: Foreign keys in access_group_access_management_rel_bits: access_management_id -> access_management.id [constraint: access_group_access_management_rel_bi_access_management_id_fkey]; access_group_id -> access_group.id [constraint: access_group_access_management_rel_bits_access_group_id_fkey]. Total foreign key relationships: 2. Referenced tables: access_management, access_group.


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

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


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

Response: The account_analytic_tag_account_payment_register_rel table has 2 columns and 3 foreign key relationships. It stores data related to account analytic tag account payment register rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


What foreign keys exist in account.ebupot? or Describe the many2many relations for account.ebupot.

Response: The account.ebupot model has 6 relational fields: year -> sh.fiscal.year; invoice_ids -> account.move; partner_id -> res.partner; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: invoice_ids.


What fields are readonly in image.mixin? or How to query image.mixin data?

Response: To use the image.mixin model, you need to provide values for required fields: none. Readonly fields: image_1920, image_1024, image_512, image_256, image_128, id, display_name, __last_update. Field usage details: image_1920 [readonly]; image_1024 [readonly] [computed] [no_copy]; image_512 [readonly] [computed] [no_copy]; image_256 [readonly] [computed] [no_copy]; image_128 [readonly] [computed] [no_copy]; id [readonly]; display_name [readonly] [computed] [no_copy]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


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

Response: The res_mail_activity table has 13 columns and 6 foreign key relationships. It stores data related to res mail activity in the system. The table has 1 indexes for performance optimization. Column types: integer: 7, character varying: 3, date: 1, timestamp without time zone: 2. Nullable columns: 12, columns with defaults: 1.


Explain the mr_analytic_rel table schema. or What columns does mr_analytic_rel have?

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


What foreign keys exist in mrp.routing.workcenter? or What are the relationships in mrp.routing.workcenter?

Response: The mrp.routing.workcenter model has 10 relational fields: bom_id -> mrp.bom; company_id -> res.company; workorder_ids -> mrp.workorder; branch_id -> res.branch; workcenter_id -> mrp.workcenter; workcenter_ids -> mrp.workcenter; location_id -> stock.location; workcenter_group_id -> mrp.workcenter.group; create_uid -> res.users; write_uid -> res.users. Many2many fields: workcenter_ids. One2many fields: workorder_ids.


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

Response: Columns in gamification_challenge: id (integer) [NOT NULL] [DEFAULT: nextval('gamification_challenge_id_seq'::regclass)] [PRECISION: 32]; message_main_attachment_id (integer) [PRECISION: 32] [COMMENT: Main Attachment]; name (character varying) [NOT NULL] [COMMENT: Challenge Name]; description (text) [COMMENT: Description]; state (character varying) [NOT NULL] [COMMENT: State]; manager_id (integer) [PRECISION: 32] [COMMENT: Responsible]; user_domain (character varying) [COMMENT: User domain]; period (character varying) [NOT NULL] [COMMENT: Periodicity]; start_date (date) [COMMENT: Start Date]; end_date (date) [COMMENT: End Date]; reward_id (integer) [PRECISION: 32] [COMMENT: For Every Succeeding User]; reward_first_id (integer) [PRECISION: 32] [COMMENT: For 1st user]; reward_second_id (integer) [PRECISION: 32] [COMMENT: For 2nd user]; reward_third_id (integer) [PRECISION: 32] [COMMENT: For 3rd user]; reward_failure (boolean) [COMMENT: Reward Bests if not Succeeded?]; reward_realtime (boolean) [COMMENT: Reward as soon as every goal is reached]; visibility_mode (character varying) [NOT NULL] [COMMENT: Display Mode]; report_message_frequency (character varying) [NOT NULL] [COMMENT: Report Frequency]; report_message_group_id (integer) [PRECISION: 32] [COMMENT: Send a copy to]; report_template_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Report Template]; remind_update_delay (integer) [PRECISION: 32] [COMMENT: Non-updated manual goals will be reminded after]; last_report_date (date) [COMMENT: Last Report Date]; next_report_date (date) [COMMENT: Next Report Date]; challenge_category (character varying) [NOT NULL] [COMMENT: Appears in]; 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: 28. Statistics: 20 nullable, 1 with defaults, 0 with length constraints.


What methods are available in opening.balance? or Describe the implementation of opening.balance.

Response: The opening.balance model is defined in module: equip3_accounting_opening_balance. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: onchange_line_item, coa_list, generate_je.


What is the module hierarchy for limit.request? or Which fields are stored computed fields in limit.request?

Response: The limit.request model is defined in module: equip3_sale_other_operation. It has 35 computed fields: last_credit_limit, last_open_inv_no, last_max_invoice, state1, state2, limit_approval_matrix, approval_matrix_line_id, approval2, new_amount, last_amount, is_approve_button, user_id, is_credit_limit_brand, 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: last_credit_limit, last_open_inv_no, last_max_invoice, new_amount, last_amount. Related fields: state1 -> state, state2 -> state, user_id -> create_uid, is_credit_limit_brand -> partner_id.set_customer_credit_limit_per_brand, 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: set_brand_ids, _domain_company, _get_approve_button, _get_last_amount, _get_new_amount, _get_approval, _show_approval, action_rejected, action_reject_approval, request_approve, _send_whatsapp_message_approval, _send_qiscus_whatsapp_approval, request_approval, action_approve_approval, set_user_approval, _get_limit_matrix, create_approval, _onchange_limit_type, _compute_last_limit, request_confirm, create.


How is sh.sale.product.indent.xls implemented technically? or What is the module hierarchy for sh.sale.product.indent.xls?

Response: The sh.sale.product.indent.xls model is defined in module: sh_sale_reports. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: download_report.


What methods are defined in picking.order.wizard original module? or What is the module hierarchy for picking.order.wizard?

Response: The picking.order.wizard model is defined in module: pragmatic_odoo_delivery_boy. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: assign_drivers_zipcode_wise.


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

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


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

Response: The account_analytic_tag_stock_quant_rel table has 2 columns and 5 foreign key relationships. It stores data related to account analytic tag stock quant rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


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

Response: Foreign keys in bve_view_line: bve_view_id -> bve_view.id [constraint: bve_view_line_bve_view_id_fkey]; create_uid -> res_users.id [constraint: bve_view_line_create_uid_fkey]; field_id -> ir_model_fields.id [constraint: bve_view_line_field_id_fkey]; join_model_id -> ir_model.id [constraint: bve_view_line_join_model_id_fkey]; model_id -> ir_model.id [constraint: bve_view_line_model_id_fkey]; write_uid -> res_users.id [constraint: bve_view_line_write_uid_fkey]. Total foreign key relationships: 6. Referenced tables: ir_model, res_users, bve_view, ir_model_fields.


What methods are available in mrp.immediate.production? or How is mrp.immediate.production implemented technically?

Response: The mrp.immediate.production model is defined in module: mrp. It has 3 computed fields: show_productions, display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: default_get, _compute_show_production, process.


What methods are available in mrp.production.backorder? or Describe the implementation of mrp.production.backorder.

Response: The mrp.production.backorder model is defined in module: mrp. It has 3 computed fields: show_backorder_lines, display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: _compute_show_backorder_lines, action_close_mo, action_backorder.


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

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


What is the module hierarchy for ir.module.module? or What modules define ir.module.module?

Response: The ir.module.module model is defined in module: base. It has 12 computed fields: description_html, installed_version, menus_by_module, reports_by_module, views_by_module, icon_image, has_iap, version_status, local_updatable, is_installed_on_current_website, display_name, __last_update. Stored computed fields: menus_by_module, reports_by_module, views_by_module, version_status, local_updatable. Related fields: none. Original module methods: fields_view_get, _get_desc, _get_latest_version, _get_views, _get_icon_image, _compute_has_iap, unlink, _state_update, button_install, button_immediate_install, button_install_cancel, module_uninstall, _remove_copied_views, downstream_dependencies, upstream_dependencies, next, _button_immediate_function, button_immediate_uninstall, button_uninstall, button_uninstall_wizard, button_uninstall_cancel, button_immediate_upgrade, button_upgrade, button_upgrade_cancel, create, update_list, download, install_from_urls, get_apps_server, _update_dependencies, _update_exclusions, _update_category, _update_translations, _check, _installed, search_panel_select_range.


Tell me about the initial.balance.line model. or What does the initial.balance.line model represent?

Response: The initial.balance.line model represents initial Balance Sheet in the ERP system. It contains 17 fields and is used to manage initial balance sheet data. Defined in module: equip3_accounting_reports. Key fields include: name, report_name, account_id, company_id, currency_id, debit_amount, credit_amount, balance_amount, period_id, valid_value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

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


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

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


What business logic is in im_livechat.report.operator? or How to work with im_livechat.report.operator fields?

Response: To use the im_livechat.report.operator model, you need to provide values for required fields: none. Readonly fields: partner_id, livechat_channel_id, nbr_channel, channel_id, start_date, time_to_answer, duration, id, display_name, __last_update. Field usage details: partner_id [readonly]; livechat_channel_id [readonly]; nbr_channel [readonly]; channel_id [readonly]; start_date [readonly]; time_to_answer [readonly]; duration [readonly]; id [readonly]; display_name [readonly] [computed] [no_copy]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


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

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


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

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


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

Response: Foreign keys in setu_inventory_age_bi_report: company_id -> res_company.id [constraint: setu_inventory_age_bi_report_company_id_fkey]; create_uid -> res_users.id [constraint: setu_inventory_age_bi_report_create_uid_fkey]; product_category_id -> product_category.id [constraint: setu_inventory_age_bi_report_product_category_id_fkey]; product_id -> product_product.id [constraint: setu_inventory_age_bi_report_product_id_fkey]; wizard_id -> setu_inventory_age_report.id [constraint: setu_inventory_age_bi_report_wizard_id_fkey]; write_uid -> res_users.id [constraint: setu_inventory_age_bi_report_write_uid_fkey]. Total foreign key relationships: 6. Referenced tables: product_product, setu_inventory_age_report, product_category, res_company, res_users.


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

Response: The pos_loyalty_point table has 20 columns and 7 foreign key relationships. It stores data related to pos loyalty point in the system. The table has 3 indexes for performance optimization. Column types: integer: 8, timestamp without time zone: 3, double precision: 3, character varying: 3, boolean: 3. Nullable columns: 17, columns with defaults: 1.


What are the technical details of account.cashbox.wizard.line? or Which fields in account.cashbox.wizard.line are computed?

Response: The account.cashbox.wizard.line model is defined in module: equip3_pos_cashbox. It has 5 computed fields: subtotal, currency_id, is_closing_line, display_name, __last_update. Stored computed fields: none. Related fields: currency_id -> cashbox_id.currency_id, is_closing_line -> account_cashbox_wizard_id.is_closing_wizard. Original module methods: _sub_total.


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

Response: Foreign keys in rating_rating: create_uid -> res_users.id [constraint: rating_rating_create_uid_fkey]; message_id -> mail_message.id [constraint: rating_rating_message_id_fkey]; parent_res_model_id -> ir_model.id [constraint: rating_rating_parent_res_model_id_fkey]; partner_id -> res_partner.id [constraint: rating_rating_partner_id_fkey]; publisher_id -> res_partner.id [constraint: rating_rating_publisher_id_fkey]; rated_partner_id -> res_partner.id [constraint: rating_rating_rated_partner_id_fkey]; res_model_id -> ir_model.id [constraint: rating_rating_res_model_id_fkey]; write_uid -> res_users.id [constraint: rating_rating_write_uid_fkey]. Total foreign key relationships: 8. Referenced tables: mail_message, ir_model, res_partner, res_users.


Tell me about the repair.tags model. or What does the repair.tags model represent?

Response: The repair.tags model represents Repair Tags in the ERP system. It contains 9 fields and is used to manage repair tags data. Defined in module: repair. Key fields include: name, color, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What methods are available in mrp.workcenter.productivity.loss? or What are the technical details of mrp.workcenter.productivity.loss?

Response: The mrp.workcenter.productivity.loss model is defined in module: mrp. It has 3 computed fields: loss_type, display_name, __last_update. Stored computed fields: loss_type. Related fields: loss_type -> loss_id.loss_type. Original module methods: .


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

Response: Foreign keys in account_reconcile_model_template_res_partner_rel: account_reconcile_model_template_id -> account_reconcile_model_template.id [constraint: account_reconcile_model_templ_account_reconcile_model_temp_fkey]; res_partner_id -> res_partner.id [constraint: account_reconcile_model_template_res_partne_res_partner_id_fkey]. Total foreign key relationships: 2. Referenced tables: res_partner, account_reconcile_model_template.


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

Response: Columns in website_sale_payment_acquirer_onboarding_wizard: id (integer) [NOT NULL] [DEFAULT: nextval('website_sale_payment_acquirer_onboarding_wizard_id_seq'::regclass)] [PRECISION: 32]; payment_method (character varying) [COMMENT: Payment Method]; paypal_user_type (character varying) [COMMENT: Paypal User Type]; paypal_email_account (character varying) [COMMENT: Email]; paypal_seller_account (character varying) [COMMENT: Merchant Account ID]; paypal_pdt_token (character varying) [COMMENT: PDT Identity Token]; stripe_secret_key (character varying) [COMMENT: Stripe Secret Key]; stripe_publishable_key (character varying) [COMMENT: Stripe Publishable Key]; manual_name (character varying) [COMMENT: Method]; journal_name (character varying) [COMMENT: Bank Name]; acc_number (character varying) [COMMENT: Account Number]; manual_post_msg (text) [COMMENT: Payment Instructions]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 16. Statistics: 15 nullable, 1 with defaults, 0 with length constraints.


What one2many fields are in crm.salesperson.tracking.report? or Describe the many2many relations for crm.salesperson.tracking.report.

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


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

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


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

Response: Columns in vendor_evaluation_template: id (integer) [NOT NULL] [DEFAULT: nextval('vendor_evaluation_template_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [NOT NULL] [COMMENT: 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]. Total columns: 6. Statistics: 4 nullable, 1 with defaults, 0 with length constraints.


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

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