What computed fields exist in customer.deposit.wizard? or What fields does customer.deposit.wizard have?

Response: The customer.deposit.wizard model has 9 fields. Field types distribution: text: 1, boolean: 1, integer: 1, char: 1, many2one: 2, datetime: 3. Computed fields: 2. Field details: reason (text) [module: equip3_accounting_deposit]; add_amount (boolean) [module: equip3_accounting_deposit]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


How do I use the sh.sale.analysis.xls model? or How to query sh.sale.analysis.xls data?

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


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

Response: The asset_cip_line table has 13 columns and 6 foreign key relationships. It stores data related to asset cip line in the system. The table has 1 indexes for performance optimization. Column types: integer: 7, character varying: 1, double precision: 1, boolean: 2, timestamp without time zone: 2. Nullable columns: 11, columns with defaults: 1.


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

Response: The product_alternative_rel table has 2 columns and 2 foreign key relationships. It stores data related to product alternative 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 asp.asm.stock.line? or List all relational fields in asp.asm.stock.line.

Response: The asp.asm.stock.line model has 8 relational fields: product_id -> product.product; location_id -> stock.location; filter_location_ids -> stock.location; asp_asm_stock_id -> asp.asm.stock; category_uom_id -> uom.category; uom_id -> uom.uom; create_uid -> res.users; write_uid -> res.users. Many2many fields: filter_location_ids. One2many fields: none.


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

Response: The cashback.line model represents cashback.line in the ERP system. It contains 16 fields and is used to manage cashback.line data. Defined in module: equip3_sale_loyalty. Key fields include: sequence, product_id, name, product_uom_qty, price_unit, total, customer_voucher_id, order_id, invoice_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: The s_curve_budget table has 11 columns and 5 foreign key relationships. It stores data related to s curve budget in the system. The table has 2 indexes for performance optimization. Column types: integer: 6, character varying: 1, date: 2, timestamp without time zone: 2. Nullable columns: 9, columns with defaults: 1.


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

Response: Columns in nsfp_registration_wizard: id (integer) [NOT NULL] [DEFAULT: nextval('nsfp_registration_wizard_id_seq'::regclass)] [PRECISION: 32]; fiscal_year (integer) [PRECISION: 32] [COMMENT: Fiscal Year]; start (character varying) [LENGTH: 100] [COMMENT: Start]; end (character varying) [LENGTH: 100] [COMMENT: End]; 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: 7 nullable, 1 with defaults, 2 with length constraints.


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

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


What operations can I perform on sh.correct.qc.measurement? or What fields are readonly in sh.correct.qc.measurement?

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


What data can be stored in sh.qc.alert.line? or Show me the fields of sh.qc.alert.line.

Response: The sh.qc.alert.line model has 10 fields. Field types distribution: many2one: 5, integer: 1, char: 1, datetime: 3. Computed fields: 2. Field details: alert_id (many2one) -> sh.qc.alert [module: sh_inventory_mrp_qc]; product_id (many2one) [required] -> product.product [module: sh_inventory_mrp_qc]; partner_id (many2one) -> res.partner [module: sh_inventory_mrp_qc]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


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

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


What are the available fields for payment.sale.details.report? or What computed fields exist in payment.sale.details.report?

Response: The payment.sale.details.report model has 10 fields. Field types distribution: char: 2, float: 1, many2one: 3, integer: 1, datetime: 3. Computed fields: 2. Field details: name (char) [module: equip3_sale_report]; total (float) [module: equip3_sale_report]; details_id (many2one) -> sh.sale.details.report.wizard [module: equip3_sale_report]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


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

Response: The stock_valuation_layer_revaluation table has 12 columns and 6 foreign key relationships. It stores data related to stock valuation layer revaluation in the system. The table has 1 indexes for performance optimization. Column types: integer: 7, numeric: 1, character varying: 1, date: 1, timestamp without time zone: 2. Nullable columns: 8, columns with defaults: 1.


Which fields in bus.bus are computed? or What modules define bus.bus?

Response: The bus.bus model is defined in module: bus. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: _gc_messages, sendmany, sendone, poll.


How to query coupon.reward data? or How to create records in coupon.reward?

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


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

Response: Columns in crm_merge_opportunity: id (integer) [NOT NULL] [DEFAULT: nextval('crm_merge_opportunity_id_seq'::regclass)] [PRECISION: 32]; user_id (integer) [PRECISION: 32] [COMMENT: Salesperson]; team_id (integer) [PRECISION: 32] [COMMENT: Sales Team]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 7. Statistics: 6 nullable, 1 with defaults, 0 with length constraints.


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

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


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

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


What computed fields exist in pos.promotion.specific.product? or What are the available fields for pos.promotion.specific.product?

Response: The pos.promotion.specific.product model has 13 fields. Field types distribution: boolean: 1, selection: 1, float: 1, many2one: 4, many2many: 1, integer: 1, char: 1, datetime: 3. Computed fields: 2. Field details: active (boolean) [module: equip3_pos_masterdata]; type_apply (selection) [required] [module: equip3_pos_masterdata]; qty_free (float) [module: equip3_pos_masterdata]; product_id (many2one) -> product.product [module: equip3_pos_masterdata]; product_ids (many2many) -> product.product [module: equip3_pos_masterdata]; promotion_id (many2one) [required] -> pos.promotion [module: equip3_pos_masterdata]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


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

Response: Foreign keys in sms_resend_recipient: create_uid -> res_users.id [constraint: sms_resend_recipient_create_uid_fkey]; notification_id -> mail_message_res_partner_needaction_rel.id [constraint: sms_resend_recipient_notification_id_fkey]; sms_resend_id -> sms_resend.id [constraint: sms_resend_recipient_sms_resend_id_fkey]; write_uid -> res_users.id [constraint: sms_resend_recipient_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: mail_message_res_partner_needaction_rel, res_users, sms_resend.


What are the technical details of sh.report.section? or What methods are available in sh.report.section?

Response: The sh.report.section model is defined in module: sh_all_in_one_purchase_tools. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: .


What business logic is in hr.plan? or How to create records in hr.plan?

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


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

Response: Columns in account_account_map: id (integer) [NOT NULL] [DEFAULT: nextval('account_account_map_id_seq'::regclass)] [PRECISION: 32]; company_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Parent Company]; child_company_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Child Company]; ownership (double precision) [PRECISION: 53] [COMMENT: Parent Ownership]; 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: 5 nullable, 1 with defaults, 0 with length constraints.


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

Response: Foreign keys in account_journal_account_reconcile_model_rel: account_reconcile_model_id -> account_reconcile_model.id [constraint: account_journal_account_reconci_account_reconcile_model_id_fkey]; account_journal_id -> account_journal.id [constraint: account_journal_account_reconcile_model_account_journal_id_fkey]. Total foreign key relationships: 2. Referenced tables: account_reconcile_model, account_journal.


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

Response: Foreign keys in mail_activity_type: create_uid -> res_users.id [constraint: mail_activity_type_create_uid_fkey]; default_next_type_id -> mail_activity_type.id [constraint: mail_activity_type_default_next_type_id_fkey]; default_user_id -> res_users.id [constraint: mail_activity_type_default_user_id_fkey]; res_model_id -> ir_model.id [constraint: mail_activity_type_res_model_id_fkey]; write_uid -> res_users.id [constraint: mail_activity_type_write_uid_fkey]. Total foreign key relationships: 5. Referenced tables: ir_model, mail_activity_type, res_users.


What foreign keys exist in website.sale.extra.field? or Describe the many2many relations for website.sale.extra.field.

Response: The website.sale.extra.field model has 4 relational fields: website_id -> website; field_id -> ir.model.fields; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


Tell me about the vendor.payment.request.line model. or Can you explain the purpose of vendor.payment.request.line?

Response: The vendor.payment.request.line model represents Vendor Payment Request Line in the ERP system. It contains 16 fields and is used to manage vendor payment request line data. Defined in module: equip3_purchase_operation. Key fields include: payment_request_id, sequence, description, amount_total, currency_id, payable_amount, attachment_file, file_name, purchase_order_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: Foreign keys in crm_lead_crm_lead2opportunity_partner_mass_rel: crm_lead2opportunity_partner_mass_id -> crm_lead2opportunity_partner_mass.id [constraint: crm_lead_crm_lead2opportunit_crm_lead2opportunity_partner_fkey1]; crm_lead_id -> crm_lead.id [constraint: crm_lead_crm_lead2opportunity_partner_mass_rel_crm_lead_id_fkey]. Total foreign key relationships: 2. Referenced tables: crm_lead, crm_lead2opportunity_partner_mass.


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

Response: The account_analytic_line table has 32 columns and 20 foreign key relationships. It stores data related to account analytic line in the system. The table has 6 indexes for performance optimization. Column types: integer: 21, character varying: 4, date: 1, numeric: 1, double precision: 1, timestamp without time zone: 2, boolean: 2. Nullable columns: 26, columns with defaults: 1.


Describe the create.recurring.invoice model in Odoo. or Tell me about the create.recurring.invoice model.

Response: The create.recurring.invoice model represents Create Recurring Invoice in the ERP system. It contains 8 fields and is used to manage create recurring invoice data. Defined in module: contract_recurring_invoice_analytic. Key fields include: start_date, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: Foreign keys in product_product_quality_alert_report_rel: quality_alert_report_id -> quality_alert_report.id [constraint: product_product_quality_alert_repo_quality_alert_report_id_fkey]; product_product_id -> product_product.id [constraint: product_product_quality_alert_report_re_product_product_id_fkey]. Total foreign key relationships: 2. Referenced tables: product_product, quality_alert_report.


Show me the fields of product.pricelist. or What computed fields exist in product.pricelist?

Response: The product.pricelist model has 25 fields. Field types distribution: char: 4, boolean: 3, one2many: 2, many2one: 6, integer: 2, many2many: 2, selection: 1, datetime: 5. Computed fields: 2. Field details: name (char) [required] [module: product]; active (boolean) [module: product]; item_ids (one2many) -> product.pricelist.item [module: product]; currency_id (many2one) [required] -> res.currency [module: product]; sequence (integer) [module: product]; country_group_ids (many2many) -> res.country.group [module: product]; discount_policy (selection) [required] [module: product]; website_id (many2one) -> website [module: website_sale]; code (char) [module: website_sale]; selectable (boolean) [module: website_sale]; pricelist_history_ids (one2many) -> product.pricelist.history [module: equip3_sale_masterdata]; from_date (datetime) [module: equip3_sale_masterdata]; to_date (datetime) [module: equip3_sale_masterdata]; customer_category (many2one) -> customer.category [module: equip3_sale_masterdata]; company_id (many2one) [readonly] -> res.company [module: equip3_sale_operation]; barcode (char) [module: equip3_pos_masterdata]; is_external_link (boolean) [module: equip3_sale_other_operation_cont]; pos_config_ids (many2many) -> pos.config [module: allfresh_mod_pricelist]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


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

Response: Foreign keys in sms_cancel: create_uid -> res_users.id [constraint: sms_cancel_create_uid_fkey]; write_uid -> res_users.id [constraint: sms_cancel_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


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

Response: Foreign keys in product_ratio_line: create_uid -> res_users.id [constraint: product_ratio_line_create_uid_fkey]; product_id -> product_product.id [constraint: product_ratio_line_product_id_fkey]; product_tmpl_id -> product_template.id [constraint: product_ratio_line_product_tmpl_id_fkey]; uom_id -> uom_uom.id [constraint: product_ratio_line_uom_id_fkey]; write_uid -> res_users.id [constraint: product_ratio_line_write_uid_fkey]. Total foreign key relationships: 5. Referenced tables: product_product, res_users, uom_uom, product_template.


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

Response: The auditlog_http_request table has 11 columns and 4 foreign key relationships. It stores data related to auditlog http request in the system. The table has 1 indexes for performance optimization. Column types: integer: 5, character varying: 4, timestamp without time zone: 2. Nullable columns: 10, columns with defaults: 1.


How to create records in gamification.badge.user? or How to query gamification.badge.user data?

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


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

Response: The pos_cash_in_out table has 11 columns and 5 foreign key relationships. It stores data related to pos cash in out in the system. The table has 1 indexes for performance optimization. Column types: integer: 6, character varying: 2, numeric: 1, timestamp without time zone: 2. Nullable columns: 10, columns with defaults: 1.


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

Response: The sh_stock_move_global_check table has 13 columns and 6 foreign key relationships. It stores data related to sh stock move global check in the system. The table has 1 indexes for performance optimization. Column types: integer: 7, text: 2, double precision: 1, character varying: 1, timestamp without time zone: 2. Nullable columns: 12, columns with defaults: 1.


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

Response: The account.bank.cashbox.line model has 5 relational fields: cashbox_id -> account.bank.statement.cashbox; currency_id -> res.currency; pos_session_id -> pos.session; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


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

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


What foreign keys exist in rn.matrix.reject? or How does rn.matrix.reject relate to other models?

Response: The rn.matrix.reject model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


What methods are available in blacklist.partner.wiz? or Describe the implementation of blacklist.partner.wiz.

Response: The blacklist.partner.wiz model is defined in module: equip3_purchase_masterdata. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: action_submit.


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

Response: Foreign keys in kitchen_safety_stock_line: create_uid -> res_users.id [constraint: kitchen_safety_stock_line_create_uid_fkey]; product_id -> product_product.id [constraint: kitchen_safety_stock_line_product_id_fkey]; stock_id -> kitchen_safety_stock.id [constraint: kitchen_safety_stock_line_stock_id_fkey]; write_uid -> res_users.id [constraint: kitchen_safety_stock_line_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: product_product, kitchen_safety_stock, res_users.


Show me the relational structure of report.accounting_pdf_reports.report_agedpartnerbalance. or What are the relationships in report.accounting_pdf_reports.report_agedpartnerbalance?

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


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

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


Show me the relational structure of theme.utils. or What models are connected to theme.utils?

Response: The theme.utils model has no explicit relational fields defined in its field metadata.


What are the relationships in ks_dashboard_ninja.ks_grid_per_company? or Describe the many2many relations for ks_dashboard_ninja.ks_grid_per_company.

Response: The ks_dashboard_ninja.ks_grid_per_company model has 4 relational fields: ks_dashboard_ninja_id -> ks_dashboard_ninja.board; ks_company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


Describe the field structure of account.unreconcile. or What data can be stored in account.unreconcile?

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


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

Response: Foreign keys in resource_calendar_attendance: calendar_id -> resource_calendar.id [constraint: resource_calendar_attendance_calendar_id_fkey]; create_uid -> res_users.id [constraint: resource_calendar_attendance_create_uid_fkey]; resource_id -> resource_resource.id [constraint: resource_calendar_attendance_resource_id_fkey]; write_uid -> res_users.id [constraint: resource_calendar_attendance_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: resource_calendar, resource_resource, res_users.


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

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


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

Response: Foreign keys in res_company_setu_inventory_turnover_analysis_report_rel: setu_inventory_turnover_analysis_report_id -> setu_inventory_turnover_analysis_report.id [constraint: res_company_setu_inventory_tu_setu_inventory_turnover_anal_fkey]; res_company_id -> res_company.id [constraint: res_company_setu_inventory_turnover_analysi_res_company_id_fkey]. Total foreign key relationships: 2. Referenced tables: res_company, setu_inventory_turnover_analysis_report.


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

Response: The pos.sync.session.order.line model represents Pos Sync Session Order Line in the ERP system. It contains 14 fields and is used to manage pos sync session order line data. Defined in module: equip3_pos_masterdata. Key fields include: uid, data, name, parent_id, product_int, qty, pos_session_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: The pos_promotion_tebus_murah_selected_brand table has 10 columns and 3 foreign key relationships. It stores data related to pos promotion tebus murah selected brand in the system. The table has 1 indexes for performance optimization. Column types: integer: 4, boolean: 1, character varying: 1, double precision: 2, timestamp without time zone: 2. Nullable columns: 7, columns with defaults: 1.


What field types are used in report.report_finished_good_rework? or What fields does report.report_finished_good_rework have?

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


What are the column types in approval_matrix_purchase_agreement_line? or Which columns are nullable in approval_matrix_purchase_agreement_line?

Response: Columns in approval_matrix_purchase_agreement_line: id (integer) [NOT NULL] [DEFAULT: nextval('approval_matrix_purchase_agreement_line_id_seq'::regclass)] [PRECISION: 32]; sequence (integer) [PRECISION: 32] [COMMENT: Sequence]; minimum_approver (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Minimum Approver]; approval_matrix_purchase_agreement (integer) [PRECISION: 32] [COMMENT: Approval Matrix]; sequence2 (integer) [PRECISION: 32] [COMMENT: No.]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 9. Statistics: 7 nullable, 1 with defaults, 0 with length constraints.


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

Response: The change_lock_date table has 9 columns and 3 foreign key relationships. It stores data related to change lock date in the system. The table has 1 indexes for performance optimization. Column types: integer: 4, date: 3, timestamp without time zone: 2. Nullable columns: 7, columns with defaults: 1.


What computed fields exist in pos.loyalty.reward.product? or What field types are used in pos.loyalty.reward.product?

Response: The pos.loyalty.reward.product model has 14 fields. Field types distribution: many2one: 5, integer: 2, char: 3, float: 1, datetime: 3. Computed fields: 6. Field details: gift_reward_id (many2one) -> pos.loyalty.reward [module: equip3_pos_membership]; product_id (many2one) -> product.product [module: equip3_pos_membership]; redeem_point (integer) [module: equip3_pos_membership]; default_code (char) [readonly] [compute: _compute_values] [not stored] [module: equip3_pos_membership]; list_price (float) [readonly] [compute: _compute_values] [not stored] [module: equip3_pos_membership]; uom_id (many2one) [readonly] -> uom.uom [compute: _compute_values] [not stored] [module: equip3_pos_membership]; sh_qr_code (char) [readonly] [compute: _compute_values] [not stored] [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].


What modules define uom.conversion.history? or What methods are available in uom.conversion.history?

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


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

Response: Foreign keys in product_warehouse_cost_line: company_id -> res_company.id [constraint: product_warehouse_cost_line_company_id_fkey]; create_uid -> res_users.id [constraint: product_warehouse_cost_line_create_uid_fkey]; prod_wh_cost_id -> product_warehouse_cost.id [constraint: product_warehouse_cost_line_prod_wh_cost_id_fkey]; warehouse_id -> stock_warehouse.id [constraint: product_warehouse_cost_line_warehouse_id_fkey]; write_uid -> res_users.id [constraint: product_warehouse_cost_line_write_uid_fkey]. Total foreign key relationships: 5. Referenced tables: stock_warehouse, product_warehouse_cost, res_users, res_company.


What does the multi.receipt.matrix.reject model represent? or Can you explain the purpose of multi.receipt.matrix.reject?

Response: The multi.receipt.matrix.reject model represents Receipt Payment Matrix Reject in the ERP system. It contains 8 fields and is used to manage receipt payment matrix reject data. Defined in module: equip3_accounting_operation. Key fields include: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

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


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

Response: The account_journal_group table has 8 columns and 3 foreign key relationships. It stores data related to account journal group 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: 5, columns with defaults: 1.


What fields are readonly in ks_dashboard_ninja.board_template? or How to create records in ks_dashboard_ninja.board_template?

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


What are the column types in measure_for_packaging? or Which columns are nullable in measure_for_packaging?

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


How to create records in invoice.confirmation.availability? or What are common use cases for invoice.confirmation.availability?

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


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

Response: Foreign keys in cust_credit_limit_xls: create_uid -> res_users.id [constraint: cust_credit_limit_xls_create_uid_fkey]; write_uid -> res_users.id [constraint: cust_credit_limit_xls_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


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

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


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

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


What is the module hierarchy for sh.top.vendor.excel.extended? or What methods are defined in sh.top.vendor.excel.extended original module?

Response: The sh.top.vendor.excel.extended model is defined in module: sh_purchase_reports. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: download_report.


What is the hr.plan model? or Tell me about the hr.plan model.

Response: The hr.plan model represents plan in the ERP system. It contains 10 fields and is used to manage plan data. Defined in module: hr. Key fields include: name, plan_activity_type_ids, active, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What data types are used in account_tax_group? or Describe the columns of account_tax_group.

Response: Columns in account_tax_group: id (integer) [NOT NULL] [DEFAULT: nextval('account_tax_group_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [NOT NULL] [COMMENT: Name]; sequence (integer) [PRECISION: 32] [COMMENT: Sequence]; 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: 5 nullable, 1 with defaults, 0 with length constraints.


What are the relationships in split.pr.wizard? or What models are connected to split.pr.wizard?

Response: The split.pr.wizard model has 4 relational fields: pr_line_id -> purchase.request.line; line_ids -> split.pr.line.wizard; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: line_ids.


What models are connected to sh.purchase.analysis.wizard? or What are the relationships in sh.purchase.analysis.wizard?

Response: The sh.purchase.analysis.wizard model has 6 relational fields: sh_partner_ids -> res.partner; sh_product_ids -> product.product; company_ids -> res.company; branch_ids -> res.branch; create_uid -> res.users; write_uid -> res.users. Many2many fields: sh_partner_ids, sh_product_ids, company_ids, branch_ids. One2many fields: none.


What field types are used in replace.product.wizard? or What data can be stored in replace.product.wizard?

Response: The replace.product.wizard model has 11 fields. Field types distribution: many2one: 4, float: 1, boolean: 1, integer: 1, char: 1, datetime: 3. Computed fields: 2. Field details: product_id (many2one) -> product.product [module: dev_rma]; replace_product_id (many2one) -> product.product [module: dev_rma]; replace_qty (float) [module: dev_rma]; is_same_product (boolean) [module: dev_rma]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


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

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


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

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


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

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


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

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


Show me the relational structure of kitchen.safety.stock.line. or What are the relationships in kitchen.safety.stock.line?

Response: The kitchen.safety.stock.line model has 4 relational fields: stock_id -> kitchen.safety.stock; product_id -> product.product; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


List all relational fields in checklist.reason. or Describe the many2many relations for checklist.reason.

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


What modules define report.equip3_pos_report.report_profit_loss? or How is report.equip3_pos_report.report_profit_loss implemented technically?

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


What does the purchase.detail.excel.extended model represent? or Can you explain the purpose of purchase.detail.excel.extended?

Response: The purchase.detail.excel.extended model represents Excel Extended in the ERP system. It contains 9 fields and is used to manage excel extended data. Defined in module: sh_purchase_reports. Key fields include: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Can you explain the purpose of report.account.report_invoice_with_payments? or What is the report.account.report_invoice_with_payments model?

Response: The report.account.report_invoice_with_payments model represents Account report with payment lines in the ERP system. It contains 3 fields and is used to manage account report with payment lines data. Defined in module: account. Key fields include: id, display_name, __last_update.


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

Response: Foreign keys in mail_resend_partner: create_uid -> res_users.id [constraint: mail_resend_partner_create_uid_fkey]; partner_id -> res_partner.id [constraint: mail_resend_partner_partner_id_fkey]; resend_wizard_id -> mail_resend_message.id [constraint: mail_resend_partner_resend_wizard_id_fkey]; write_uid -> res_users.id [constraint: mail_resend_partner_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: res_partner, res_users, mail_resend_message.


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

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


What operations can I perform on account.reconcile.model? or How to work with account.reconcile.model fields?

Response: To use the account.reconcile.model model, you need to provide values for required fields: name, sequence, company_id, rule_type, matching_order, match_nature. Readonly fields: company_id, show_decimal_separator, number_entries, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [required]; sequence [required] [has_default]; company_id [required] [readonly] [has_default]; rule_type [required] [has_default]; matching_order [required] [has_default]; match_nature [required] [has_default]; show_decimal_separator [readonly] [computed] [no_copy]; number_entries [readonly] [computed] [no_copy]; activity_state [readonly] [computed] [no_copy]; activity_user_id [computed] [no_copy]; activity_type_id [computed] [no_copy]; activity_type_icon [readonly] [computed] [no_copy]; activity_date_deadline [readonly] [computed] [no_copy]; my_activity_date_deadline [readonly] [computed] [no_copy]; activity_summary [computed] [no_copy]; activity_exception_decoration [readonly] [computed] [no_copy]; activity_exception_icon [readonly] [computed] [no_copy]; message_is_follower [readonly] [computed] [no_copy]; message_partner_ids [readonly] [computed] [no_copy]; message_channel_ids [readonly] [computed] [no_copy]; message_unread [readonly] [computed] [no_copy]; message_unread_counter [readonly] [computed] [no_copy]; message_needaction [readonly] [computed] [no_copy]; message_needaction_counter [readonly] [computed] [no_copy]; message_has_error [readonly] [computed] [no_copy]; message_has_error_counter [readonly] [computed] [no_copy]; message_attachment_count [readonly] [computed] [no_copy]; message_has_sms_error [readonly] [computed] [no_copy]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


How to query base.automation data? or How to create records in base.automation?

Response: To use the base.automation model, you need to provide values for required fields: action_server_id, trigger, name, type, model_id, activity_user_type, usage, state, binding_type. Readonly fields: last_run, least_delay_msg, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, model_name, crud_model_name, mass_edit_apply_domain_in_lines, xml_id, website_url. Field usage details: action_server_id [required]; trigger [required]; last_run [readonly] [no_copy]; least_delay_msg [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]; name [required] [computed]; type [required] [computed]; sequence [computed]; model_id [required] [computed]; model_name [readonly] [computed] [no_copy]; code [computed]; child_ids [computed]; crud_model_id [computed]; crud_model_name [readonly] [computed] [no_copy]; link_field_id [computed]; fields_lines [computed]; groups_id [computed]; mass_edit_line_ids [computed] [no_copy]; mass_edit_apply_domain_in_lines [readonly] [computed] [no_copy]; mass_edit_message [computed]; partner_ids [computed]; channel_ids [computed]; template_id [computed]; activity_type_id [computed]; activity_summary [computed]; activity_note [computed]; activity_date_deadline_range [computed]; activity_date_deadline_range_type [computed]; activity_user_type [required] [computed]; activity_user_id [computed]; activity_user_field_name [computed]; usage [required] [computed]; state [required] [computed]; sms_template_id [computed]; sms_mass_keep_log [computed]; xml_id [readonly] [computed] [no_copy]; website_path [computed]; website_url [readonly] [computed] [no_copy]; website_published [computed] [no_copy]; help [computed]; binding_model_id [computed]; binding_type [required] [computed]; binding_view_types [computed]. The model supports standard CRUD operations through the ORM.


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

Response: The tebus_murah_brand_ids_rel table has 2 columns and 2 foreign key relationships. It stores data related to tebus murah brand ids 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 length constraints in digest_digest_res_users_rel? or What are the column types in digest_digest_res_users_rel?

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


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

Response: The pos_config_users_product_exchange_pin_rel table has 2 columns and 2 foreign key relationships. It stores data related to pos config users product exchange pin 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 pos.generate.efaktur.gabungan? or Describe the implementation of pos.generate.efaktur.gabungan.

Response: The pos.generate.efaktur.gabungan model is defined in module: equip3_pos_membership. It has 3 computed fields: no_of_invoice, display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: _compute_no_of_invoice.


What data can be stored in res.users.apikeys.description? or List all fields in the res.users.apikeys.description model.

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


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

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


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

Response: Foreign keys in account_report_general_ledger: company_id -> res_company.id [constraint: account_report_general_ledger_company_id_fkey]; create_uid -> res_users.id [constraint: account_report_general_ledger_create_uid_fkey]; report_currency_id -> res_currency.id [constraint: account_report_general_ledger_report_currency_id_fkey]; write_uid -> res_users.id [constraint: account_report_general_ledger_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: res_currency, res_users, res_company.


Can you explain the purpose of receivable.flow.wizard? or Describe the receivable.flow.wizard model in Odoo.

Response: The receivable.flow.wizard model represents receivable.flow.wizard in the ERP system. It contains 8 fields and is used to manage receivable.flow.wizard data. Defined in module: equip3_accounting_flow. Key fields include: name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: The report_stock_demand table has 8 columns and 2 foreign key relationships. It stores data related to report stock demand in the system. The table has 1 indexes for performance optimization. Column types: integer: 3, date: 1, double precision: 1, boolean: 1, timestamp without time zone: 2. Nullable columns: 7, columns with defaults: 1.


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

Response: Foreign keys in sale_order_pricelist_wizard_line: create_uid -> res_users.id [constraint: sale_order_pricelist_wizard_line_create_uid_fkey]; line_id -> sale_order_line.id [constraint: sale_order_pricelist_wizard_line_line_id_fkey]; pricelist_id -> sale_order_pricelist_wizard.id [constraint: sale_order_pricelist_wizard_line_pricelist_id_fkey]; sh_pricelist_id -> product_pricelist.id [constraint: sale_order_pricelist_wizard_line_sh_pricelist_id_fkey]; sh_unit_measure -> uom_uom.id [constraint: sale_order_pricelist_wizard_line_sh_unit_measure_fkey]; write_uid -> res_users.id [constraint: sale_order_pricelist_wizard_line_write_uid_fkey]. Total foreign key relationships: 6. Referenced tables: product_pricelist, res_users, sale_order_line, sale_order_pricelist_wizard, uom_uom.


How to work with ir.actions.actions fields? or How to create records in ir.actions.actions?

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


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

Response: The kitchen_cooking_list_line table has 10 columns and 4 foreign key relationships. It stores data related to kitchen cooking list line in the system. The table has 1 indexes for performance optimization. Column types: integer: 5, numeric: 3, timestamp without time zone: 2. Nullable columns: 8, columns with defaults: 1.


What are the available fields for queue.job.demo? or Which fields are required in queue.job.demo?

Response: The queue.job.demo model has 7 fields. Field types distribution: integer: 1, char: 1, many2one: 2, datetime: 3. Computed fields: 2. Field details: 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 foreign keys exist in export.retur.pajak.masukan? or What are the relationships in export.retur.pajak.masukan?

Response: The export.retur.pajak.masukan model has 4 relational fields: partner_id -> res.partner; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


What methods are defined in internal.transfer original module? or What is the module hierarchy for internal.transfer?

Response: The internal.transfer model is defined in module: equip3_inventory_operation. It has 46 computed fields: state1, state2, state3, operation_count, internal_transfer_line_total, itr_approval_matrix_id, is_itr_approval_matrix, approved_matrix_ids, approval_matrix_line_id, is_approve_button, is_reset_to_draft, is_product_lines, company_id, filter_source_warehouse_id, filter_destination_warehouse_id, get_warehouse, is_mbs_on_transfer_operations, branch_id, domain_warehouse_source_id, domain_warehouse_destination_id, source_location_id, destination_location_id, 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, access_url, access_warning, display_name, __last_update. Stored computed fields: internal_transfer_line_total, approved_matrix_ids. Related fields: state1 -> state, state2 -> state, state3 -> state, company_id -> source_warehouse_id.company_id, branch_id -> source_warehouse_id.branch_id, source_location_id -> source_warehouse_id.lot_stock_id, destination_location_id -> destination_warehouse_id.lot_stock_id, activity_user_id -> activity_ids.user_id, activity_type_id -> activity_ids.activity_type_id, activity_type_icon -> activity_ids.icon, activity_summary -> activity_ids.summary. Original module methods: action_done, _compute_location, default_sh_it_bm_is_cont_scan, _onchange_sh_it_barcode_mobile, onchange_destination_warehouse_id, _compute_is_mbs_on_transfer_operations, _onchange_requested_by, _get_warehouses, _get_street, _get_address_details, compute_expiry_date, _compute_source_warehouse, _compute_destination_warehouse, _get_is_product_lines, _get_is_show_draft, _get_approve_button, _compute_approving_matrix_lines_itr, _get_approve_button_from_config, _get_approval_matrix, itr_request_for_approving, itr_approving, itr_reject, itr_reset_to_draft, _compute_source_loc, _onchange_warehouse_id_for_location, calculate_lines_total, _compute_destination_loc, upd_source, upd_dest, _compute_operation_count, check_qc, action_confirm, print_report, action_cancel, button_notes, default_get, _expire_date_cron, _expire_date_reminder_cron, send_email_notification, create, onchange_source_loction_id, onchange_dest_loction_id, calculate_transfer_qty.


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

Response: Foreign keys in pos_cash_in_out: account_move_id -> account_move.id [constraint: pos_cash_in_out_account_move_id_fkey]; create_uid -> res_users.id [constraint: pos_cash_in_out_create_uid_fkey]; pos_session_id -> pos_session.id [constraint: pos_cash_in_out_pos_session_id_fkey]; product_id -> product_product.id [constraint: pos_cash_in_out_product_id_fkey]; write_uid -> res_users.id [constraint: pos_cash_in_out_write_uid_fkey]. Total foreign key relationships: 5. Referenced tables: pos_session, res_users, account_move, product_product.


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

Response: Foreign keys in product_category: create_uid -> res_users.id [constraint: product_category_create_uid_fkey]; parent_id -> product_category.id [constraint: product_category_parent_id_fkey]; property_service_account_id -> account_account.id [constraint: product_category_property_service_account_id_fkey]; removal_strategy_id -> product_removal.id [constraint: product_category_removal_strategy_id_fkey]; stock_scrap_account -> account_account.id [constraint: product_category_stock_scrap_account_fkey]; stock_transfer_transit_account_id -> account_account.id [constraint: product_category_stock_transfer_transit_account_id_fkey]; write_uid -> res_users.id [constraint: product_category_write_uid_fkey]. Total foreign key relationships: 7. Referenced tables: product_removal, account_account, res_users, product_category.


List all relational fields in milestone.contract.template.checklist. or What are the relationships in milestone.contract.template.checklist?

Response: The milestone.contract.template.checklist model has 3 relational fields: template_id -> milestone.contract.template; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


List all columns in pos_config_pos_promotion_rel. or Show me the column structure of pos_config_pos_promotion_rel.

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


What foreign keys exist in account.bank.statement.import.journal.creation? or Show me the relational structure of account.bank.statement.import.journal.creation.

Response: The account.bank.statement.import.journal.creation model has 40 relational fields: journal_id -> account.journal; create_uid -> res.users; write_uid -> res.users; check_sequence_id -> ir.sequence; edi_format_ids -> account.edi.format; compatible_edi_ids -> account.edi.format; sequence_id -> ir.sequence; refund_sequence_id -> ir.sequence; pos_payment_method_ids -> pos.payment.method; type_control_ids -> account.account.type; account_control_ids -> account.account; default_account_type -> account.account.type; default_account_id -> account.account; payment_debit_account_id -> account.account; payment_credit_account_id -> account.account; suspense_account_id -> account.account; currency_id -> res.currency; company_id -> res.company; inbound_payment_method_ids -> account.payment.method; outbound_payment_method_ids -> account.payment.method; profit_account_id -> account.account; loss_account_id -> account.account; company_partner_id -> res.partner; bank_account_id -> res.partner.bank; bank_id -> res.bank; sale_activity_type_id -> mail.activity.type; sale_activity_user_id -> res.users; alias_id -> mail.alias; journal_group_ids -> account.journal.group; secure_sequence_id -> ir.sequence; branch_id -> res.branch; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message. Many2many fields: edi_format_ids, compatible_edi_ids, type_control_ids, account_control_ids, inbound_payment_method_ids, outbound_payment_method_ids, journal_group_ids, message_partner_ids, message_channel_ids. One2many fields: pos_payment_method_ids, activity_ids, message_follower_ids, message_ids, website_message_ids.


What are common use cases for account.partner.ledger? or How to work with account.partner.ledger fields?

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


What does the calendar.alarm_manager model represent? or Can you explain the purpose of calendar.alarm_manager?

Response: The calendar.alarm_manager model represents Event Alarm Manager in the ERP system. It contains 3 fields and is used to manage event alarm manager data. Defined in module: calendar. Key fields include: id, display_name, __last_update.


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

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


Show me the relational structure of mail.channel.partner. or What are the relationships in mail.channel.partner?

Response: The mail.channel.partner model has 6 relational fields: partner_id -> res.partner; channel_id -> mail.channel; fetched_message_id -> mail.message; seen_message_id -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


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

Response: The res_partner_rfm_segment_history table has 14 columns and 7 foreign key relationships. It stores data related to res partner rfm segment history in the system. The table has 1 indexes for performance optimization. Column types: integer: 11, date: 1, timestamp without time zone: 2. Nullable columns: 13, columns with defaults: 1.


List all relational fields in stock.warehouse. or Describe the many2many relations for stock.warehouse.

Response: The stock.warehouse model has 54 relational fields: partner_id -> res.partner; view_location_id -> stock.location; lot_stock_id -> stock.location; route_ids -> stock.location.route; wh_input_stock_loc_id -> stock.location; wh_qc_stock_loc_id -> stock.location; wh_output_stock_loc_id -> stock.location; wh_pack_stock_loc_id -> stock.location; mto_pull_id -> stock.rule; pick_type_id -> stock.picking.type; pack_type_id -> stock.picking.type; out_type_id -> stock.picking.type; in_type_id -> stock.picking.type; int_type_id -> stock.picking.type; crossdock_route_id -> stock.location.route; reception_route_id -> stock.location.route; delivery_route_id -> stock.location.route; resupply_wh_ids -> stock.warehouse; resupply_route_ids -> stock.location.route; manufacture_pull_id -> stock.rule; manufacture_mto_pull_id -> stock.rule; pbm_mto_pull_id -> stock.rule; sam_rule_id -> stock.rule; manu_type_id -> stock.picking.type; pbm_type_id -> stock.picking.type; sam_type_id -> stock.picking.type; pbm_route_id -> stock.location.route; pbm_loc_id -> stock.location; sam_loc_id -> stock.location; pos_type_id -> stock.picking.type; buy_pull_id -> stock.rule; default_delivery_location_id -> stock.location; driver_ids -> stock.warehouse.driver; company_id -> res.company; branch_id -> res.branch; lot_scrap_id -> stock.location; lot_expired_id -> stock.location; state_id -> res.country.state; country_id -> res.country; responsible_users -> res.users; default_receipt_location_id -> stock.location; pos_branch_id -> res.branch; analytic_tag_ids -> account.analytic.tag; 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: route_ids, resupply_wh_ids, responsible_users, analytic_tag_ids, message_partner_ids, message_channel_ids. One2many fields: resupply_route_ids, driver_ids, activity_ids, message_follower_ids, message_ids, website_message_ids.


What methods are available in account.reconcile.model.template? or What modules define account.reconcile.model.template?

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


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

Response: The pos_sessions_close table has 2 columns and 2 foreign key relationships. It stores data related to pos sessions close 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 length constraints in auditlog_log_line? or What columns have default values in auditlog_log_line?

Response: Columns in auditlog_log_line: id (integer) [NOT NULL] [DEFAULT: nextval('auditlog_log_line_id_seq'::regclass)] [PRECISION: 32]; field_id (integer) [PRECISION: 32] [COMMENT: Field]; log_id (integer) [PRECISION: 32] [COMMENT: Log]; old_value (text) [COMMENT: Old Value]; new_value (text) [COMMENT: New Value]; old_value_text (text) [COMMENT: Old value Text]; new_value_text (text) [COMMENT: New value Text]; field_name (character varying) [COMMENT: Technical name]; field_description (character varying) [COMMENT: Description]; name (character varying) [LENGTH: 64] [COMMENT: Resource Name]; model_id (integer) [PRECISION: 32] [COMMENT: Model]; model_name (character varying) [COMMENT: Model Name]; model_model (character varying) [COMMENT: Technical Model Name]; res_id (integer) [PRECISION: 32] [COMMENT: Resource ID]; user_id (integer) [PRECISION: 32] [COMMENT: User]; method (character varying) [LENGTH: 64] [COMMENT: Method]; http_session_id (integer) [PRECISION: 32] [COMMENT: Session]; http_request_id (integer) [PRECISION: 32] [COMMENT: HTTP Request]; log_type (character varying) [COMMENT: Type]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 23. Statistics: 22 nullable, 1 with defaults, 2 with length constraints.


Which fields are required in purchase.requisition.type? or Describe the field structure of purchase.requisition.type.

Response: The purchase.requisition.type model has 12 fields. Field types distribution: char: 2, integer: 2, selection: 3, many2one: 2, datetime: 3. Computed fields: 2. Field details: name (char) [required] [module: purchase_requisition]; sequence (integer) [module: purchase_requisition]; exclusive (selection) [required] [module: purchase_requisition]; quantity_copy (selection) [required] [module: purchase_requisition]; line_copy (selection) [required] [module: purchase_requisition]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


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

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


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

Response: Foreign keys in qc_product_rel: product_id -> product_product.id [constraint: qc_product_rel_product_id_fkey]; qc_id -> sh_qc_point.id [constraint: qc_product_rel_qc_id_fkey]. Total foreign key relationships: 2. Referenced tables: product_product, sh_qc_point.


What one2many fields are in crm.tag? or List all relational fields in crm.tag.

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


What is the sh.stock.move.pics model? or Tell me about the sh.stock.move.pics model.

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


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

Response: The account.root model has 6 fields. Field types distribution: char: 2, many2one: 2, integer: 1, datetime: 1. Computed fields: 2. Field details: name (char) [readonly] [module: account]; parent_id (many2one) [readonly] -> account.root [module: account]; company_id (many2one) [readonly] -> res.company [module: account]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field] [not stored] [module: None].


How do I use the sh.edit.title model? or What are common use cases for sh.edit.title?

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


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

Response: The sh_sale_product_profit_wizard table has 10 columns and 3 foreign key relationships. It stores data related to sh sale product profit wizard in the system. The table has 1 indexes for performance optimization. Column types: integer: 5, timestamp without time zone: 4, character varying: 1. Nullable columns: 7, columns with defaults: 1.


What does the account.invoice.to.draft model represent? or How is account.invoice.to.draft used in the system?

Response: The account.invoice.to.draft model represents Set to Draft the Selected Invoices in the ERP system. It contains 7 fields and is used to manage set to draft the selected invoices data. Defined in module: aos_base_account. Key fields include: id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

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


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

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


What modules define mail.alias? or What methods are defined in mail.alias original module?

Response: The mail.alias model is defined in module: mail. It has 3 computed fields: alias_domain, display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: _default_alias_domain, _alias_is_ascii, _compute_alias_domain, _check_alias_defaults, create, write, name_get, _clean_and_check_unique, open_document, open_parent_document, _get_alias_bounced_body_fallback, _get_alias_bounced_body, _valid_field_parameter, _mail_track, _message_get_default_recipients, _notify_get_reply_to, _alias_check_contact, _alias_get_error_message, _get_default_activity_view, _notify_email_headers, _notify_email_header_dict.


What operations can I perform on purchase.order.wizard? or How do I use the purchase.order.wizard model?

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


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

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


What does the report.sh_purchase_reports.sh_payment_pr_report_doc model represent? or How is report.sh_purchase_reports.sh_payment_pr_report_doc used in the system?

Response: The report.sh_purchase_reports.sh_payment_pr_report_doc model represents Bill payment report abstract model in the ERP system. It contains 3 fields and is used to manage bill payment report abstract model data. Defined in module: sh_purchase_reports. Key fields include: id, display_name, __last_update.


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

Response: Columns in pos_voucher: id (integer) [NOT NULL] [DEFAULT: nextval('pos_voucher_id_seq'::regclass)] [PRECISION: 32]; active (boolean) [COMMENT: Active]; customer_id (integer) [PRECISION: 32] [COMMENT: Customer]; code (character varying) [COMMENT: Ean13]; start_date (timestamp without time zone) [NOT NULL] [COMMENT: Start Date]; end_date (timestamp without time zone) [NOT NULL] [COMMENT: Expired Date]; state (character varying) [COMMENT: State]; value (double precision) [PRECISION: 53] [COMMENT: Amount]; apply_type (character varying) [COMMENT: Apply]; method (character varying) [COMMENT: Method]; use_date (timestamp without time zone) [COMMENT: Use Date]; user_id (integer) [PRECISION: 32] [COMMENT: Create User]; source (character varying) [COMMENT: Source Document]; pos_order_id (integer) [PRECISION: 32] [COMMENT: Order]; pos_order_line_id (integer) [PRECISION: 32] [COMMENT: Order Line]; number (character varying) [COMMENT: Number]; maximum_discount_amount (double precision) [PRECISION: 53] [COMMENT: Maximum Discount Amount]; minimum_purchase_amount (double precision) [PRECISION: 53] [COMMENT: Minimum Purchase Amount]; is_generate_voucher (boolean) [COMMENT: Is Generate Voucher]; generated_source_id (integer) [PRECISION: 32] [COMMENT: Source Document]; company_id (integer) [PRECISION: 32] [COMMENT: Company]; receipt_template_id (integer) [PRECISION: 32] [COMMENT: Receipt Template]; source_document_id (integer) [PRECISION: 32] [COMMENT: Source Document]; is_customize_sequence (boolean) [COMMENT: Customize Sequence]; sequence_generate_method (character varying) [COMMENT: Sequence Generate Method]; manual_input_sequence (character varying) [COMMENT: Manual Input Sequence]; running_number_prefix (character varying) [COMMENT: Running Number Prefix]; running_number_digit (integer) [PRECISION: 32] [COMMENT: Running Number Digit]; 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: 32. Statistics: 29 nullable, 1 with defaults, 0 with length constraints.


What foreign keys exist in res.company? or List all relational fields in res.company.

Response: The res.company model has 92 relational fields: child_ids -> res.company; user_ids -> res.users; state_id -> res.country.state; bank_ids -> res.partner.bank; country_id -> res.country; paperformat_id -> report.paperformat; external_report_layout_id -> ir.ui.view; nomenclature_id -> barcode.nomenclature; resource_calendar_ids -> resource.calendar; resource_calendar_id -> resource.calendar; 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; transfer_account_id -> account.account; chart_template_id -> account.chart.template; default_cash_difference_income_account_id -> account.account; default_cash_difference_expense_account_id -> account.account; account_journal_suspense_account_id -> account.account; account_sale_tax_id -> account.tax; account_purchase_tax_id -> account.tax; currency_exchange_journal_id -> account.journal; income_currency_exchange_account_id -> account.account; expense_currency_exchange_account_id -> account.account; property_stock_account_input_categ_id -> account.account; property_stock_account_output_categ_id -> account.account; property_stock_valuation_account_id -> account.account; bank_journal_ids -> account.journal; account_tax_fiscal_country_id -> res.country; incoterm_id -> account.incoterms; account_opening_move_id -> account.move; account_opening_journal_id -> account.journal; account_default_pos_receivable_account_id -> account.account; expense_accrual_account_id -> account.account; revenue_accrual_account_id -> account.account; automatic_entry_default_journal_id -> account.journal; tax_cash_basis_journal_id -> account.journal; account_cash_basis_base_account_id -> account.account; internal_transit_location_id -> stock.location; stock_mail_confirmation_template_id -> mail.template; project_time_mode_id -> uom.uom; timesheet_encode_uom_id -> uom.uom; stock_sms_confirmation_template_id -> sms.template; account_edi_proxy_client_ids -> account_edi_proxy_client.user; sh_pmps_pro_field_ids -> ir.model.fields; sh_pmps_pro_attr_ids -> product.attribute; sale_order_template_id -> sale.order.template; lc_journal_id -> account.journal; intercompany_warehouse_id -> stock.warehouse; sale_email_specific_user_id -> res.users; down_payment_product_id -> product.product; branch_ids -> res.branch; report_template_id1 -> ir.actions.report; report_template_id -> ir.actions.report; report_sale_template_id1 -> ir.actions.report; report_sale_template_id -> ir.actions.report; report_po_template_id1 -> ir.actions.report; report_po_template_id -> ir.actions.report; report_rfq_template_id -> ir.actions.report; report_delivery_template_id1 -> ir.actions.report; report_delivery_template_id -> ir.actions.report; report_picking_template_id -> ir.actions.report; font_id -> report.fonts; report_bank_id -> res.partner.bank; unrealized_exchange_journal_id -> account.journal; income_unrealized_exchange_account_id -> account.account; expense_unrealized_exchange_account_id -> account.account; sale_account_id -> account.account; purchase_account_id -> account.account; interest_income -> account.account; interest_expense -> account.account; deposit_account_id -> account.account; partner_id -> res.partner; currency_id -> res.currency; parent_id -> res.company; city_id -> res.country.city; company_delivery_product -> product.product; send_notification_users_ids -> res.users; sh_sale_pro_field_ids -> ir.model.fields; sh_sale_pro_attr_ids -> product.attribute; product_pricelist_default -> product.pricelist; report_pr_template_id -> ir.actions.report; rounding_method_id -> account.cash.rounding; pos_def_receipt_template_id -> pos.receipt.template; pos_product_discount1_id -> product.product; create_uid -> res.users; write_uid -> res.users. Many2many fields: user_ids, message_partner_ids, message_channel_ids, sh_pmps_pro_field_ids, sh_pmps_pro_attr_ids, send_notification_users_ids, sh_sale_pro_field_ids, sh_sale_pro_attr_ids. One2many fields: child_ids, bank_ids, resource_calendar_ids, activity_ids, message_follower_ids, message_ids, website_message_ids, bank_journal_ids, account_edi_proxy_client_ids, branch_ids.


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

Response: To use the coupon.coupon model, you need to provide values for required fields: code, state. Readonly fields: code, expiration_date, order_id, sales_order_id, pos_order_id, is_gift_card, redeem_history_ids, pos_create_date, pos_create_uid, pos_config_id, redeem_amount, balance_amount, pos_orderline_id, purchase_id, purchases_order_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: code [required] [readonly] [has_default]; expiration_date [readonly] [computed] [no_copy]; discount_line_product_id [computed] [no_copy]; order_id [readonly]; sales_order_id [readonly]; pos_order_id [readonly]; is_gift_card [readonly] [computed] [no_copy]; redeem_history_ids [readonly] [no_copy]; state [required] [has_default] [no_copy]; pos_create_date [readonly]; pos_create_uid [readonly]; pos_config_id [readonly]; redeem_amount [readonly] [computed] [no_copy]; balance_amount [readonly] [computed] [no_copy]; pos_orderline_id [readonly]; purchase_id [readonly]; purchases_order_id [readonly]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


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

Response: The queue_job table has 34 columns and 4 foreign key relationships. It stores data related to queue job in the system. The table has 8 indexes for performance optimization. Column types: integer: 9, character varying: 12, text: 6, timestamp without time zone: 6, double precision: 1. Nullable columns: 31, columns with defaults: 1.


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

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


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

Response: Columns in account_account_tag: id (integer) [NOT NULL] [DEFAULT: nextval('account_account_tag_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [NOT NULL] [COMMENT: Tag Name]; applicability (character varying) [NOT NULL] [COMMENT: Applicability]; color (integer) [PRECISION: 32] [COMMENT: Color Index]; active (boolean) [COMMENT: Active]; tax_negate (boolean) [COMMENT: Negate Tax Balance]; country_id (integer) [PRECISION: 32] [COMMENT: Country]; 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: 11. Statistics: 8 nullable, 1 with defaults, 0 with length constraints.


How to query base.partner.merge.line data? or What fields are readonly in base.partner.merge.line?

Response: To use the base.partner.merge.line model, you need to provide values for required fields: aggr_ids. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: aggr_ids [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 ir.qweb.field.date model in Odoo. or What does the ir.qweb.field.date model represent?

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


What methods are defined in approval.matrix.direct.purchase original module? or Which fields are stored computed fields in approval.matrix.direct.purchase?

Response: The approval.matrix.direct.purchase model is defined in module: equip3_purchase_other_operation_cont. It has 25 computed fields: is_good_services_order, 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, access_url, access_warning, display_name, __last_update. Stored computed fields: none. Related fields: activity_user_id -> activity_ids.user_id, activity_type_id -> activity_ids.activity_type_id, activity_type_icon -> activity_ids.icon, activity_summary -> activity_ids.summary. Original module methods: _compute_is_good_services_order, _check_validation_minimum_approver, _check_existing_record, _reset_sequence, onchange_company_id.


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

Response: The payment_voucher_line table has 13 columns and 4 foreign key relationships. It stores data related to payment voucher line in the system. The table has 1 indexes for performance optimization. Column types: integer: 5, numeric: 5, character varying: 1, timestamp without time zone: 2. Nullable columns: 12, columns with defaults: 1.


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

Response: Foreign keys in product_alternative_rel: dest_id -> product_template.id [constraint: product_alternative_rel_dest_id_fkey]; src_id -> product_template.id [constraint: product_alternative_rel_src_id_fkey]. Total foreign key relationships: 2. Referenced tables: product_template.


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

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


What business logic is in order.driver.message? or What fields are readonly in order.driver.message?

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


What is the product.pricelist.history model? or What does the product.pricelist.history model represent?

Response: The product.pricelist.history model represents product.pricelist.history in the ERP system. It contains 25 fields and is used to manage product.pricelist.history data. Defined in module: equip3_sale_masterdata. Key fields include: pricelist_id, logdate, user_id, name, method, description, old_value_text, new_value_text, category_id, product_tmpl_id, product_id, uom_id, model, pl_id, pricelist_item_id, company_id, currency_id, is_seen, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Which fields are stored computed fields in hide.chatter? or What is the module hierarchy for hide.chatter?

Response: The hide.chatter model is defined in module: simplify_access_management. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: load_views, fields_view_get, _get_access_management_domain_record, _check_access_management_right, _display_access_management_error, unlink, write, create.


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

Response: Foreign keys in account_pettycash_voucher_wizard: ba_ca_journal_id -> account_journal.id [constraint: account_pettycash_voucher_wizard_ba_ca_journal_id_fkey]; company_id -> res_company.id [constraint: account_pettycash_voucher_wizard_company_id_fkey]; create_uid -> res_users.id [constraint: account_pettycash_voucher_wizard_create_uid_fkey]; currency_id -> res_currency.id [constraint: account_pettycash_voucher_wizard_currency_id_fkey]; fund -> account_pettycash.id [constraint: account_pettycash_voucher_wizard_fund_fkey]; move_id -> account_move.id [constraint: account_pettycash_voucher_wizard_move_id_fkey]; partner_id -> res_users.id [constraint: account_pettycash_voucher_wizard_partner_id_fkey]; submitter_id -> res_users.id [constraint: account_pettycash_voucher_wizard_submitter_id_fkey]; write_uid -> res_users.id [constraint: account_pettycash_voucher_wizard_write_uid_fkey]. Total foreign key relationships: 9. Referenced tables: account_pettycash, res_company, res_currency, res_users, account_move, account_journal.


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

Response: Foreign keys in account_analytic_tag_pt_rel: pt_id -> purchase_agreement.id [constraint: account_analytic_tag_pt_rel_pt_id_fkey]; tag_id -> account_analytic_tag.id [constraint: account_analytic_tag_pt_rel_tag_id_fkey]. Total foreign key relationships: 2. Referenced tables: purchase_agreement, account_analytic_tag.


What computed fields exist in customer.order.dic? or What field types are used in customer.order.dic?

Response: The customer.order.dic model has 10 fields. Field types distribution: many2one: 3, one2many: 1, char: 2, integer: 1, datetime: 3. Computed fields: 2. Field details: report_id (many2one) -> sh.sale.invoice.summary.wizard [module: equip3_sale_report]; list_order (one2many) -> list.order [module: equip3_sale_report]; saleperson (char) [module: equip3_sale_report]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].