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

Response: Foreign keys in crm_meeting_overview: calendar_id -> calendar_event.id [constraint: crm_meeting_overview_calendar_id_fkey]; create_uid -> res_users.id [constraint: crm_meeting_overview_create_uid_fkey]; final_quotation -> quotation_amount.id [constraint: crm_meeting_overview_final_quotation_fkey]; message_main_attachment_id -> ir_attachment.id [constraint: crm_meeting_overview_message_main_attachment_id_fkey]; opportunity_id -> crm_lead.id [constraint: crm_meeting_overview_opportunity_id_fkey]; write_uid -> res_users.id [constraint: crm_meeting_overview_write_uid_fkey]. Total foreign key relationships: 6. Referenced tables: quotation_amount, calendar_event, ir_attachment, res_users, crm_lead.


Tell me about the report.sh_purchase_reports.sh_top_purchasing_product_doc model. or Can you explain the purpose of report.sh_purchase_reports.sh_top_purchasing_product_doc?

Response: The report.sh_purchase_reports.sh_top_purchasing_product_doc model represents top purchasing product report abstract model in the ERP system. It contains 3 fields and is used to manage top purchasing product report abstract model data. Defined in module: sh_purchase_reports. Key fields include: id, display_name, __last_update.


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

Response: Foreign keys in im_livechat_channel_country_rel: channel_id -> im_livechat_channel_rule.id [constraint: im_livechat_channel_country_rel_channel_id_fkey]; country_id -> res_country.id [constraint: im_livechat_channel_country_rel_country_id_fkey]. Total foreign key relationships: 2. Referenced tables: im_livechat_channel_rule, res_country.


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

Response: Foreign keys in qiscus_wa_template_content: create_uid -> res_users.id [constraint: qiscus_wa_template_content_create_uid_fkey]; template_id -> qiscus_wa_template.id [constraint: qiscus_wa_template_content_template_id_fkey]; write_uid -> res_users.id [constraint: qiscus_wa_template_content_write_uid_fkey]. Total foreign key relationships: 3. Referenced tables: qiscus_wa_template, res_users.


Can you explain the purpose of approval.matrix.accounting? or Tell me about the approval.matrix.accounting model.

Response: The approval.matrix.accounting model represents Approval Matrix Accounting in the ERP system. It contains 47 fields and is used to manage approval matrix accounting data. Defined in module: equip3_accounting_masterdata. Key fields include: approval_matrix_type, change_amount, name, min_amount, max_amount, company_id, branch_id, filter_branch_ids, approval_matrix_line_ids, campaign_id, source_id, medium_id, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, access_url, access_token, access_warning, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: Columns in pos_loyalty_reward: id (integer) [NOT NULL] [DEFAULT: nextval('pos_loyalty_reward_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]; sequence (integer) [PRECISION: 32] [COMMENT: Sequence]; name (character varying) [NOT NULL] [COMMENT: Name]; active (boolean) [COMMENT: Active]; loyalty_id (integer) [PRECISION: 32] [COMMENT: Loyalty]; product_redeem_loyalty_id (integer) [PRECISION: 32] [COMMENT: Loyalty]; reward_redeem_loyalty_id (integer) [PRECISION: 32] [COMMENT: Loyalty]; redeem_point (double precision) [PRECISION: 53] [COMMENT: Redeem Point]; type (character varying) [NOT NULL] [COMMENT: Type of Reward]; coefficient (numeric) [NOT NULL] [COMMENT: Coefficient Ratio]; redeem_coefficient (numeric) [NOT NULL] [COMMENT: Redeem Coefficient]; discount (double precision) [PRECISION: 53] [COMMENT: Discount %]; min_amount (double precision) [PRECISION: 53] [COMMENT: Min Amount]; gift_quantity (double precision) [PRECISION: 53] [COMMENT: Gift Quantity]; price_resale (double precision) [PRECISION: 53] [COMMENT: Price of resale]; state (character varying) [COMMENT: State]. Total columns: 20. Statistics: 15 nullable, 1 with defaults, 0 with length constraints.


How is ir.ui.view.custom used in the system? or Can you explain the purpose of ir.ui.view.custom?

Response: The ir.ui.view.custom model represents Custom View in the ERP system. It contains 10 fields and is used to manage custom view data. Defined in module: base. Key fields include: ref_id, user_id, arch, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: Columns in mail_alias: id (integer) [NOT NULL] [DEFAULT: nextval('mail_alias_id_seq'::regclass)] [PRECISION: 32]; alias_name (character varying) [COMMENT: Alias Name]; alias_model_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Aliased Model]; alias_user_id (integer) [PRECISION: 32] [COMMENT: Owner]; alias_defaults (text) [NOT NULL] [COMMENT: Default Values]; alias_force_thread_id (integer) [PRECISION: 32] [COMMENT: Record Thread ID]; alias_parent_model_id (integer) [PRECISION: 32] [COMMENT: Parent Model]; alias_parent_thread_id (integer) [PRECISION: 32] [COMMENT: Parent Record Thread ID]; alias_contact (character varying) [NOT NULL] [COMMENT: Alias Contact Security]; alias_bounced_content (text) [COMMENT: Custom Bounced Message]; 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: 14. Statistics: 10 nullable, 1 with defaults, 0 with length constraints.


What one2many fields are in stock.immediate.transfer.line? or How does stock.immediate.transfer.line relate to other models?

Response: The stock.immediate.transfer.line model has 4 relational fields: immediate_transfer_id -> stock.immediate.transfer; picking_id -> stock.picking; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


List all relational fields in ir.qweb.field.image_url. or What foreign keys exist in ir.qweb.field.image_url?

Response: The ir.qweb.field.image_url model has no explicit relational fields defined in its field metadata.


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

Response: The im_livechat_channel_rule table has 10 columns and 3 foreign key relationships. It stores data related to im livechat channel rule in the system. The table has 1 indexes for performance optimization. Column types: integer: 6, character varying: 2, timestamp without time zone: 2. Nullable columns: 8, columns with defaults: 1.


Describe the field structure of milestone.contract.template. or What are the available fields for milestone.contract.template?

Response: The milestone.contract.template model has 11 fields. Field types distribution: char: 2, many2one: 3, one2many: 2, integer: 1, datetime: 3. Computed fields: 2. Field details: name (char) [required] [module: equip3_purchase_operation]; checklist_template_id (many2one) -> purchase.custom.checklist.template [module: equip3_purchase_operation]; line_ids (one2many) -> milestone.contract.template.line [module: equip3_purchase_operation]; checklist_ids (one2many) -> milestone.contract.template.checklist [module: equip3_purchase_operation]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


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

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


What operations can I perform on account.loan.post? or What are common use cases for account.loan.post?

Response: To use the account.loan.post model, you need to provide values for required fields: loan_id, journal_id, account_id. Readonly fields: loan_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: loan_id [required] [readonly]; journal_id [required] [has_default]; account_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.


Describe the field structure of limit.approval.matrix. or List all fields in the limit.approval.matrix model.

Response: The limit.approval.matrix model has 45 fields. Field types distribution: char: 7, many2one: 10, selection: 3, float: 2, one2many: 5, date: 2, boolean: 5, many2many: 2, integer: 5, text: 1, datetime: 3. Computed fields: 24. Field details: name (char) [required] [module: equip3_sale_other_operation]; company_id (many2one) [required] -> res.company [module: equip3_sale_other_operation]; branch_id (many2one) [required] -> res.branch [module: equip3_sale_other_operation]; config (selection) [required] [module: equip3_sale_other_operation]; minimum_amt (float) [required] [module: equip3_sale_other_operation]; maximum_amt (float) [required] [module: equip3_sale_other_operation]; approver_matrix_line_ids (one2many) -> limit.approval.matrix.lines [module: equip3_sale_other_operation]; campaign_id (many2one) -> utm.campaign [module: utm]; source_id (many2one) -> utm.source [module: utm]; medium_id (many2one) -> utm.medium [module: utm]; activity_ids (one2many) -> mail.activity [module: mail]; activity_state (selection) [readonly] [compute: _compute_activity_state] [not stored] [module: mail]; activity_user_id (many2one) -> res.users [compute: <bound method Field._compute_related of limit.approval.matrix.activity_user_id>] [not stored] [module: mail] [related: activity_ids.user_id] [inverse: <bound method Field._inverse_related of limit.approval.matrix.activity_user_id>]; activity_type_id (many2one) -> mail.activity.type [compute: <bound method Field._compute_related of limit.approval.matrix.activity_type_id>] [not stored] [module: mail] [related: activity_ids.activity_type_id] [inverse: <bound method Field._inverse_related of limit.approval.matrix.activity_type_id>]; activity_type_icon (char) [readonly] [compute: <bound method Field._compute_related of limit.approval.matrix.activity_type_icon>] [not stored] [module: mail] [related: activity_ids.icon]; activity_date_deadline (date) [readonly] [compute: _compute_activity_date_deadline] [not stored] [module: mail]; my_activity_date_deadline (date) [readonly] [compute: _compute_my_activity_date_deadline] [not stored] [module: mail]; activity_summary (char) [compute: <bound method Field._compute_related of limit.approval.matrix.activity_summary>] [not stored] [module: mail] [related: activity_ids.summary] [inverse: <bound method Field._inverse_related of limit.approval.matrix.activity_summary>]; activity_exception_decoration (selection) [readonly] [compute: _compute_activity_exception_type] [not stored] [module: mail]; activity_exception_icon (char) [readonly] [compute: _compute_activity_exception_type] [not stored] [module: mail]; message_is_follower (boolean) [readonly] [compute: _compute_is_follower] [not stored] [module: mail]; message_follower_ids (one2many) -> mail.followers [module: mail]; message_partner_ids (many2many) [readonly] -> res.partner [compute: _get_followers] [not stored] [module: mail]; message_channel_ids (many2many) [readonly] -> mail.channel [compute: _get_followers] [not stored] [module: mail]; message_ids (one2many) -> mail.message [module: mail]; message_unread (boolean) [readonly] [compute: _get_message_unread] [not stored] [module: mail]; message_unread_counter (integer) [readonly] [compute: _get_message_unread] [not stored] [module: mail]; message_needaction (boolean) [readonly] [compute: _get_message_needaction] [not stored] [module: mail]; message_needaction_counter (integer) [readonly] [compute: _get_message_needaction] [not stored] [module: mail]; message_has_error (boolean) [readonly] [compute: _compute_message_has_error] [not stored] [module: mail]; message_has_error_counter (integer) [readonly] [compute: _compute_message_has_error] [not stored] [module: mail]; message_attachment_count (integer) [readonly] [compute: _compute_message_attachment_count] [not stored] [module: mail]; message_main_attachment_id (many2one) -> ir.attachment [module: mail]; website_message_ids (one2many) -> mail.message [module: portal]; message_has_sms_error (boolean) [readonly] [compute: _compute_message_has_sms_error] [not stored] [module: sms]; access_url (char) [readonly] [compute: _compute_access_url] [not stored] [module: portal]; access_token (char) [module: portal]; access_warning (text) [readonly] [compute: _compute_access_warning] [not stored] [module: portal]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


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

Response: Foreign keys in pos_coupon_program: base_on_product_id -> product_product.id [constraint: pos_coupon_program_base_on_product_id_fkey]; company_id -> res_company.id [constraint: pos_coupon_program_company_id_fkey]; create_uid -> res_users.id [constraint: pos_coupon_program_create_uid_fkey]; reward_product_id -> product_product.id [constraint: pos_coupon_program_reward_product_id_fkey]; write_uid -> res_users.id [constraint: pos_coupon_program_write_uid_fkey]. Total foreign key relationships: 5. Referenced tables: product_product, res_users, res_company.


Show me the relational structure of closing.balance.confirm.wizard. or What models are connected to closing.balance.confirm.wizard?

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


How is account.open.chart implemented technically? or What methods are defined in account.open.chart original module?

Response: The account.open.chart model is defined in module: account_parent. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: onchange_date_to, _build_contexts, build_domain_context, account_chart_open_window, _amount_to_str, _m2o_to_str, _selection_to_str, _date_to_str, _float_html_formating, get_accounts, line_data, _lines, get_account_lines, account_type_data, get_at_accounts, at_line_data, _at_lines, get_account_type_lines, get_lines, get_all_lines, get_pdf_lines, get_pdf, get_heading, _get_html, get_html.


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

Response: Columns in picking_order_line: id (integer) [NOT NULL] [DEFAULT: nextval('picking_order_line_id_seq'::regclass)] [PRECISION: 32]; picking_order_id (integer) [PRECISION: 32] [COMMENT: Order Ref]; product_id (integer) [PRECISION: 32] [COMMENT: Product]; price_unit (numeric) [COMMENT: Unit Price]; qty (numeric) [COMMENT: Quantity]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 9. Statistics: 8 nullable, 1 with defaults, 0 with length constraints.


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

Response: Foreign keys in account_analytic_tag_dev_rma_rma_rel: account_analytic_tag_id -> account_analytic_tag.id [constraint: account_analytic_tag_dev_rma_rma_r_account_analytic_tag_id_fkey]; dev_rma_rma_id -> dev_rma_rma.id [constraint: account_analytic_tag_dev_rma_rma_rel_dev_rma_rma_id_fkey]. Total foreign key relationships: 2. Referenced tables: dev_rma_rma, account_analytic_tag.


Which fields in account.analytic.new are computed? or What modules define account.analytic.new?

Response: The account.analytic.new model is defined in module: equip3_accounting_analytical. It has 22 computed fields: activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, display_name, __last_update. Stored computed fields: none. Related fields: activity_user_id -> activity_ids.user_id, activity_type_id -> activity_ids.activity_type_id, activity_type_icon -> activity_ids.icon, activity_summary -> activity_ids.summary. Original module methods: create.


What does the report.dynamic_accounts_report.trial_balance model represent? or Tell me about the report.dynamic_accounts_report.trial_balance model.

Response: The report.dynamic_accounts_report.trial_balance model represents Trial Balance Report in the ERP system. It contains 3 fields and is used to manage trial balance report data. Defined in module: dynamic_accounts_report. Key fields include: id, display_name, __last_update.


What methods are available in account.debt.collection? or Which fields in account.debt.collection are computed?

Response: The account.debt.collection model is defined in module: equip3_accounting_operation. It has 26 computed fields: amount, is_pic, 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: _write_line_detail, _compute_amount, check_who_is_login, update_state_debt_collection, check_duplicate, action_confirm, action_cancel, action_register_payment, _create_payments, _get_batches, prepare_payment_vals.


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

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


What business logic is in l10n_id_efaktur.efaktur.range? or What operations can I perform on l10n_id_efaktur.efaktur.range?

Response: To use the l10n_id_efaktur.efaktur.range model, you need to provide values for required fields: company_id. Readonly fields: available, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: company_id [required] [has_default]; max [computed]; min [computed]; available [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 work with report.stock.quantity.new fields? or What operations can I perform on report.stock.quantity.new?

Response: To use the report.stock.quantity.new model, you need to provide values for required fields: none. Readonly fields: date, product_tmpl_id, product_id, state, product_qty, move_ids, company_id, warehouse_id, id, display_name, __last_update. Field usage details: date [readonly]; product_tmpl_id [readonly] [computed] [no_copy]; product_id [readonly]; state [readonly] [no_copy]; product_qty [readonly]; move_ids [readonly] [no_copy]; company_id [readonly]; warehouse_id [readonly]; id [readonly]; display_name [readonly] [computed] [no_copy]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


Tell me about the website.menu model. or What does the website.menu model represent?

Response: The website.menu model represents Website Menu in the ERP system. It contains 25 fields and is used to manage website menu data. Defined in module: website. Key fields include: name, url, page_id, new_window, sequence, website_id, parent_id, child_id, parent_path, is_visible, group_ids, is_mega_menu, mega_menu_content, mega_menu_classes, theme_template_id, is_display_in_delivery_control_app, user_logged, user_not_logged, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What models are connected to base_import.tests.models.m2o.required.related? or How does base_import.tests.models.m2o.required.related relate to other models?

Response: The base_import.tests.models.m2o.required.related model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


How does account.open.chart relate to other models? or List all relational fields in account.open.chart.

Response: The account.open.chart model has 3 relational fields: company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


How is purchase.order implemented technically? or Describe the implementation of purchase.order.

Response: The purchase.order model is defined in module: purchase. It has 117 computed fields: invoice_count, invoice_ids, invoice_status, date_calendar_start, product_id, currency_rate, receipt_reminder_email, reminder_date_before_receipt, is_quantity_copy, picking_count, picking_ids, default_location_dest_id_usage, is_shipped, effective_date, on_time_rate, complete_state, custom_checklist, purchase_show_signature, chk_sign_confirm, purchase_show_enable_other_sign, document_count, text_message, po_extract_count, po_split_count, sh_hidden_compute_field, cancel_lines, sh_msg, po_count, sh_purchase_revision_config, visible_eval, mrp_production_count, sale_order_count, inter_transfer_count, discount_amt, discount_amt_line, total_invoices_amount, hide_create_bill, payment_status, down_payment_amount, total_down_payment_amount, report_template_id1, amount_to_text, is_vendor_pricelist, is_hold_purchase_order, approval_matrix_id, is_approval_matrix, state1, po_state, approved_matrix_ids, is_approve_button, approval_matrix_line_id, analytic_accounting, readonly_price, timezone_date, is_group_good_services_order, have_product_service, swo_count, is_taxes, actual_progress, remaining_progress, progress_paid, available_partner_invoice_ids, is_product_brand_filter, is_service_work_order, is_purchase_vendor_rating_warning, is_product_service_operation_receiving, show_analytic_tags, amount_untaxed, amount_tax, amount_total, discount_amt_before, discount_amt_line_before, amount_subtotal, bo_count, multilevel_disc, vendor_invoice_documents_count, tender_scope, price_rating, is_btn_approval_matrix, is_blanket_cancel, days_to_approve, is_approval_matrix_direct, approved_matrix_direct_ids, approved_matrix_direct_id, state_direct_on, state_direct_off, is_approve_button_direct, promo_code, client_order_ref, branch_ids, date_planned, persentase_antar_badan, form_view_opened, 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: invoice_count, invoice_ids, invoice_status, date_calendar_start, currency_rate, picking_count, picking_ids, effective_date, cancel_lines, inter_transfer_count, discount_amt, discount_amt_line, down_payment_amount, total_down_payment_amount, approval_matrix_id, approved_matrix_ids, analytic_accounting, timezone_date, actual_progress, remaining_progress, progress_paid, is_product_service_operation_receiving, show_analytic_tags, amount_untaxed, amount_tax, amount_total, discount_amt_before, discount_amt_line_before, amount_subtotal, tender_scope, days_to_approve, approved_matrix_direct_ids, client_order_ref, branch_ids, date_planned. Related fields: product_id -> order_line.product_id, receipt_reminder_email -> partner_id.receipt_reminder_email, reminder_date_before_receipt -> partner_id.reminder_date_before_receipt, is_quantity_copy -> requisition_id.is_quantity_copy, default_location_dest_id_usage -> picking_type_id.default_location_dest_id.usage, on_time_rate -> partner_id.on_time_rate, purchase_show_signature -> company_id.purchase_show_signature, chk_sign_confirm -> company_id.chk_sign_confirm, purchase_show_enable_other_sign -> company_id.purchase_enable_other_sign_option, sh_purchase_revision_config -> company_id.sh_purchase_revision, state1 -> state, po_state -> state, discount_amt_before -> discount_amt, discount_amt_line_before -> discount_amt_line, tender_scope -> agreement_id.tender_scope, state_direct_on -> state, state_direct_off -> state, promo_code -> code_promo_program_id.promo_code, persentase_antar_badan -> partner_id.persentase_antar_badan, activity_user_id -> activity_ids.user_id, activity_type_id -> activity_ids.activity_type_id, activity_type_icon -> activity_ids.icon, activity_summary -> activity_ids.summary. Original module methods: _amount_all, _get_invoiced, _compute_invoice, _check_order_line_company_id, _compute_access_url, _compute_date_calendar_start, _name_search, _compute_currency_rate, _compute_date_planned, name_get, onchange_date_planned, create, unlink, copy, _must_delete_date_planned, onchange, _track_subtype, _get_report_base_filename, onchange_partner_id, _compute_tax_id, onchange_partner_id_warning, action_rfq_send, message_post, print_quotation, button_approve, button_draft, button_confirm, button_cancel, button_unlock, button_done, _add_supplier_to_product, action_create_invoice, _prepare_invoice, action_view_invoice, retrieve_dashboard, _send_reminder_mail, send_reminder_preview, _get_orders_to_remind, get_confirm_url, get_update_url, confirm_reminder_mail, _approval_allowed, _confirm_reception_mail, _update_date_planned_for_lines, _create_update_date_activity, _update_update_date_activity.


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

Response: Columns in currency_invoice_revaluation: id (integer) [NOT NULL] [DEFAULT: nextval('currency_invoice_revaluation_id_seq'::regclass)] [PRECISION: 32]; revaluation_period_start (date) [NOT NULL] [COMMENT: Revaluation Period Start]; revaluation_period_end (date) [NOT NULL] [COMMENT: Revaluation Period End]; revaluation_date (date) [NOT NULL] [COMMENT: Revaluation Date]; journal_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Unrealized Exchange Journal]; income_unrealized_account (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Unrealized Gain Account]; expense_unrealized_account (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Unrealized Loss Account]; 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: 4 nullable, 1 with defaults, 0 with length constraints.


How is account.account implemented technically? or What modules define account.account?

Response: The account.account model is defined in module: account. It has 35 computed fields: balance, credit, debit, initial_balance, used, internal_type, internal_group, group_id, root_id, opening_debit, opening_credit, opening_balance, is_off_balance, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, display_name, __last_update. Stored computed fields: internal_type, internal_group, group_id, root_id, is_off_balance. Related fields: internal_type -> user_type_id.type, internal_group -> user_type_id.internal_group, 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: _check_reconcile, _check_user_type_id_unique_current_year_earning, _constrains_reconcile, _constrains_allowed_journal_ids, _check_journal_consistency, _check_company_consistency, _check_user_type_id_sales_purchase_journal, _check_used_as_journal_default_debit_credit_account, _compute_account_root, _compute_account_group, _search_used, _compute_used, _search_new_account_code, _compute_opening_debit_credit, _compute_is_off_balance, _set_opening_debit, _set_opening_credit, _set_opening_debit_credit, default_get, _name_search, _onchange_user_type_id, name_get, copy, load, _toggle_reconcile_to_true, _toggle_reconcile_to_false, write, unlink, action_read_account, action_duplicate_accounts, _message_post_process_attachments.


Show me the fields of pos.gift.card.recharge. or What field types are used in pos.gift.card.recharge?

Response: The pos.gift.card.recharge model has 12 fields. Field types distribution: many2one: 5, date: 1, float: 1, integer: 1, char: 1, datetime: 3. Computed fields: 2. Field details: card_id (many2one) [readonly] -> pos.gift.card [module: equip3_pos_masterdata]; customer_id (many2one) -> res.partner [module: equip3_pos_masterdata]; recharge_date (date) [module: equip3_pos_masterdata]; user_id (many2one) -> res.users [module: equip3_pos_masterdata]; amount (float) [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].


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

Response: Columns in ai_agent_config: id (integer) [NOT NULL] [DEFAULT: nextval('ai_agent_config_id_seq'::regclass)] [PRECISION: 32]; _model_cache (text) [COMMENT: Model Cache]; _cache_timestamp (timestamp without time zone) [COMMENT: Cache Timestamp]; name (character varying) [NOT NULL] [COMMENT: Configuration Name]; provider (character varying) [NOT NULL] [COMMENT: AI Provider]; api_key (character varying) [COMMENT: API Key]; model (character varying) [COMMENT: Model]; model_info (text) [COMMENT: Model Info]; temperature (double precision) [PRECISION: 53] [COMMENT: Temperature]; auto_compress_enabled (boolean) [COMMENT: Auto Compress Messages]; compression_threshold (integer) [PRECISION: 32] [COMMENT: Compression Threshold]; trim_ratio (double precision) [PRECISION: 53] [COMMENT: Trim Ratio]; rules (text) [COMMENT: Rules]; active (boolean) [COMMENT: Active]; is_default (boolean) [COMMENT: Default Configuration]; is_utility_model (boolean) [COMMENT: Utility Model]; is_embedding_model (boolean) [COMMENT: Embedding Model]; max_input_tokens (integer) [PRECISION: 32] [COMMENT: Max Input Tokens]; max_output_tokens (integer) [PRECISION: 32] [COMMENT: Max Output Tokens]; is_support_vision (boolean) [COMMENT: Support Vision]; is_support_pdf_input (boolean) [COMMENT: Support PDF Input]; tool_sql_query (boolean) [COMMENT: SQL Query]; tool_orm_universal (boolean) [COMMENT: ORM Universal]; tool_get_model_info (boolean) [COMMENT: Get Model Info]; tool_shell_command (boolean) [COMMENT: Shell Command]; tool_pdf_maker (boolean) [COMMENT: PDF Maker]; tool_excel_maker (boolean) [COMMENT: Excel Maker]; 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]; tool_filesystem_safe (boolean) [COMMENT: Filesystem Safe]; tool_session_summarize (boolean) [COMMENT: Session Summarize]; tool_sequential_thinking (boolean) [COMMENT: Sequential Thinking]; enable_dynamic_quick_actions (boolean) [COMMENT: Dynamic Quick Actions]; enable_quick_replies (boolean) [COMMENT: Quick Replies]; tool_web_search (boolean) [COMMENT: Web Search]; is_quick_chat_default (boolean) [COMMENT: Quick Chat Default]; mode (character varying) [COMMENT: Supported Model]; vertex_project (character varying) [COMMENT: Vertex Project ID]; vertex_location (character varying) [COMMENT: Vertex Location]; vertex_credentials_filename (character varying) [COMMENT: Credentials Filename]; is_fine_tuned_model (boolean) [COMMENT: Fine-tuned Model]; base_model (character varying) [COMMENT: Base Model]; fine_tuned_model_id (character varying) [COMMENT: Fine-tuned Model ID]. Total columns: 45. Statistics: 42 nullable, 1 with defaults, 0 with length constraints.


How to create records in account.bank.statement.integrate? or What operations can I perform on account.bank.statement.integrate?

Response: To use the account.bank.statement.integrate model, you need to provide values for required fields: journal_id, date_from, date_to. Readonly fields: name, status, created_by, created_date, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [readonly] [has_default]; journal_id [required]; date_from [required]; date_to [required]; status [readonly]; created_by [readonly] [has_default]; created_date [readonly] [has_default]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


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

Response: Foreign keys in merge_picking: create_uid -> res_users.id [constraint: merge_picking_create_uid_fkey]; write_uid -> res_users.id [constraint: merge_picking_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


What does the stock.lot.serialize.line model represent? or Can you explain the purpose of stock.lot.serialize.line?

Response: The stock.lot.serialize.line model represents Stock Lot Serialize Line in the ERP system. It contains 13 fields and is used to manage stock lot serialize line data. Defined in module: equip3_inventory_operation. Key fields include: stock_move_id, sequence, move_id, product_id, demand_qty, qty_per_lot, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

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


What are common use cases for sh.sale.product.profit.xls? or How to create records in sh.sale.product.profit.xls?

Response: To use the sh.sale.product.profit.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.


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

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


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

Response: The board.board model is defined in module: board. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: create, fields_view_get, _arch_preprocessing.


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

Response: Columns in pos_promotion_multi_buy: id (integer) [NOT NULL] [DEFAULT: nextval('pos_promotion_multi_buy_id_seq'::regclass)] [PRECISION: 32]; active (boolean) [COMMENT: Active]; promotion_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Promotion]; list_price (double precision) [NOT NULL] [PRECISION: 53] [COMMENT: Sale Price]; qty_apply (double precision) [NOT NULL] [PRECISION: 53] [COMMENT: Qty bigger than or qual]; 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: 5 nullable, 1 with defaults, 0 with length constraints.


How does account.move.reversal relate to other models? or List all relational fields in account.move.reversal.

Response: The account.move.reversal model has 7 relational fields: move_ids -> account.move; new_move_ids -> account.move; journal_id -> account.journal; company_id -> res.company; currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: move_ids, new_move_ids. One2many fields: none.


What computed fields exist in do.matrix.reject? or What data can be stored in do.matrix.reject?

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


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

Response: The pmps_adv_wizard_product_line table has 8 columns and 4 foreign key relationships. It stores data related to pmps adv wizard product line in the system. The table has 1 indexes for performance optimization. Column types: integer: 5, double precision: 1, timestamp without time zone: 2. Nullable columns: 7, columns with defaults: 1.


How to work with kitchen.safety.stock.line fields? or How to create records in kitchen.safety.stock.line?

Response: To use the kitchen.safety.stock.line model, you need to provide values for required fields: stock_id, product_id, product_qty. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: stock_id [required] [no_copy]; product_id [required]; product_qty [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.


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

Response: The product_supplierinfo_approval table has 16 columns and 4 foreign key relationships. It stores data related to product supplierinfo approval in the system. The table has 1 indexes for performance optimization. Column types: integer: 9, text: 2, character varying: 1, boolean: 1, timestamp without time zone: 3. Nullable columns: 15, columns with defaults: 1.


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

Response: Foreign keys in hide_filters_groups: access_management_id -> access_management.id [constraint: hide_filters_groups_access_management_id_fkey]; create_uid -> res_users.id [constraint: hide_filters_groups_create_uid_fkey]; model_id -> ir_model.id [constraint: hide_filters_groups_model_id_fkey]; write_uid -> res_users.id [constraint: hide_filters_groups_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: ir_model, access_management, res_users.


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

Response: Columns in mrp_bom_byproduct: id (integer) [NOT NULL] [DEFAULT: nextval('mrp_bom_byproduct_id_seq'::regclass)] [PRECISION: 32]; product_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: By-product]; company_id (integer) [PRECISION: 32] [COMMENT: Company]; product_qty (numeric) [NOT NULL] [COMMENT: Quantity]; product_uom_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Unit of Measure]; bom_id (integer) [PRECISION: 32] [COMMENT: BoM]; operation_id (integer) [PRECISION: 32] [COMMENT: Produced in Operation]; 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]; allocated_cost (numeric) [COMMENT: Allocated Cost(%)]; cost (double precision) [PRECISION: 53] [COMMENT: Cost]; operation_two_id (integer) [PRECISION: 32] [COMMENT: Operation]; kitchen_allocated_cost (double precision) [PRECISION: 53] [COMMENT: Kitchen Allocated Cost (%)]; assembly_allocated_cost (double precision) [PRECISION: 53] [COMMENT: Allocated Cost (%)]. Total columns: 16. Statistics: 12 nullable, 1 with defaults, 0 with length constraints.


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

Response: Columns in stock_picking_type_dashboard: id (integer) [NOT NULL] [DEFAULT: nextval('stock_picking_type_dashboard_id_seq'::regclass)] [PRECISION: 32]; campaign_id (integer) [PRECISION: 32] [COMMENT: Campaign]; source_id (integer) [PRECISION: 32] [COMMENT: Source]; medium_id (integer) [PRECISION: 32] [COMMENT: Medium]; message_main_attachment_id (integer) [PRECISION: 32] [COMMENT: Main Attachment]; access_token (character varying) [COMMENT: Security Token]; name (character varying) [COMMENT: Operation Type]; warehouse_id (integer) [PRECISION: 32] [COMMENT: Warehouse]; code (character varying) [COMMENT: Type of Operation]; company_id (integer) [PRECISION: 32] [COMMENT: Company]; color (integer) [PRECISION: 32] [COMMENT: Color]; 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: 15. Statistics: 14 nullable, 1 with defaults, 0 with length constraints.


What data types are used in milestone_contract_template? or Show me the column structure of milestone_contract_template.

Response: Columns in milestone_contract_template: id (integer) [NOT NULL] [DEFAULT: nextval('milestone_contract_template_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [NOT NULL] [COMMENT: Name]; checklist_template_id (integer) [PRECISION: 32] [COMMENT: Checklist Template]; 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.


How to work with account.account.map.line fields? or What are common use cases for account.account.map.line?

Response: To use the account.account.map.line model, you need to provide values for required fields: map_id, child_company_id. Readonly fields: company_id, target_company, target_account, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: company_id [readonly] [computed] [no_copy]; target_company [readonly] [computed] [no_copy]; target_account [readonly]; map_id [required]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]; line_ids [computed] [no_copy]; child_company_id [required] [computed]; ownership [computed]; sales_line_ids [computed] [no_copy]; purchase_line_ids [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


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

Response: The account_pettycash_voucher_wizard table has 22 columns and 9 foreign key relationships. It stores data related to account pettycash voucher wizard in the system. The table has 1 indexes for performance optimization. Column types: integer: 10, character varying: 5, date: 1, numeric: 2, boolean: 1, text: 1, timestamp without time zone: 2. Nullable columns: 18, columns with defaults: 1.


What is the sh.purchase.product.indent.wizard model? or Describe the sh.purchase.product.indent.wizard model in Odoo.

Response: The sh.purchase.product.indent.wizard model represents Purchase Product Indent Wizard in the ERP system. It contains 14 fields and is used to manage purchase product indent wizard data. Defined in module: sh_purchase_reports. Key fields include: sh_start_date, sh_end_date, sh_partner_ids, sh_status, sh_category_ids, company_ids, branch_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: Foreign keys in account_user_reminder: branch_id -> res_branch.id [constraint: account_user_reminder_branch_id_fkey]; company_id -> res_company.id [constraint: account_user_reminder_company_id_fkey]; create_uid -> res_users.id [constraint: account_user_reminder_create_uid_fkey]; write_uid -> res_users.id [constraint: account_user_reminder_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: res_company, res_users, res_branch.


Can you explain the purpose of crm.lead.salesperson.lines? or Tell me about the crm.lead.salesperson.lines model.

Response: The crm.lead.salesperson.lines model represents Salesperson in the ERP system. It contains 11 fields and is used to manage salesperson data. Defined in module: equip3_crm_operation. Key fields include: salesperson_id, weightage, status, lead_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What is the assets.approval.matrix.line model? or Describe the assets.approval.matrix.line model in Odoo.

Response: The assets.approval.matrix.line model represents Assets Approval Matrix Line in the ERP system. It contains 19 fields and is used to manage assets approval matrix line data. Defined in module: equip3_accounting_masterdata. Key fields include: sequence, user_ids, minimum_approver, assets_approval_matrix_id, sequence2, approved_users, state_char, time_stamp, feedback, last_approved, approved, assets_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Which fields in theme.ir.attachment are computed? or What modules define theme.ir.attachment?

Response: The theme.ir.attachment model is defined in module: website. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: _convert_to_base_model, get_base_url, get_website_meta.


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

Response: The assign_pr_line_wizard table has 11 columns and 7 foreign key relationships. It stores data related to assign pr line wizard in the system. The table has 1 indexes for performance optimization. Column types: integer: 8, character varying: 1, timestamp without time zone: 2. Nullable columns: 10, columns with defaults: 1.


Describe the field structure of ir.qweb.field.duration. or What field types are used in ir.qweb.field.duration?

Response: The ir.qweb.field.duration 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 foreign keys in project_project? or List all constraint names in project_project.

Response: Foreign keys in project_project: alias_id -> mail_alias.id [constraint: project_project_alias_id_fkey]; analytic_account_id -> account_analytic_account.id [constraint: project_project_analytic_account_id_fkey]; company_id -> res_company.id [constraint: project_project_company_id_fkey]; create_uid -> res_users.id [constraint: project_project_create_uid_fkey]; message_main_attachment_id -> ir_attachment.id [constraint: project_project_message_main_attachment_id_fkey]; partner_id -> res_partner.id [constraint: project_project_partner_id_fkey]; sale_line_id -> sale_order_line.id [constraint: project_project_sale_line_id_fkey]; sale_order_id -> sale_order.id [constraint: project_project_sale_order_id_fkey]; subtask_project_id -> project_project.id [constraint: project_project_subtask_project_id_fkey]; timesheet_product_id -> product_product.id [constraint: project_project_timesheet_product_id_fkey]; user_id -> res_users.id [constraint: project_project_user_id_fkey]; write_uid -> res_users.id [constraint: project_project_write_uid_fkey]. Total foreign key relationships: 12. Referenced tables: product_product, res_partner, sale_order, res_company, ir_attachment, res_users, sale_order_line, mail_alias, account_analytic_account, project_project.


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

Response: Columns in account_account_financial_report: report_line_id (integer) [NOT NULL] [PRECISION: 32]; account_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 setu_inventory_overstock_bi_report. or What relationships exist for setu_inventory_overstock_bi_report?

Response: Foreign keys in setu_inventory_overstock_bi_report: company_id -> res_company.id [constraint: setu_inventory_overstock_bi_report_company_id_fkey]; create_uid -> res_users.id [constraint: setu_inventory_overstock_bi_report_create_uid_fkey]; product_category_id -> product_category.id [constraint: setu_inventory_overstock_bi_report_product_category_id_fkey]; product_id -> product_product.id [constraint: setu_inventory_overstock_bi_report_product_id_fkey]; warehouse_id -> stock_warehouse.id [constraint: setu_inventory_overstock_bi_report_warehouse_id_fkey]; wizard_id -> setu_inventory_overstock_report.id [constraint: setu_inventory_overstock_bi_report_wizard_id_fkey]; write_uid -> res_users.id [constraint: setu_inventory_overstock_bi_report_write_uid_fkey]. Total foreign key relationships: 7. Referenced tables: product_product, stock_warehouse, product_category, res_company, res_users, setu_inventory_overstock_report.


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

Response: The pos.sync.session.log model represents Transactions Logs of POS Users in the ERP system. It contains 17 fields and is used to manage transactions logs of pos users data. Defined in module: equip3_pos_general. Key fields include: order_uid, create_date, send_from_session_id, send_to_session_id, user_id, user_receive_id, action, logs, state, branch_id, company_id, id, display_name, create_uid, write_uid, write_date, __last_update.


Describe the implementation of gamification.badge.user.wizard. or What methods are available in gamification.badge.user.wizard?

Response: The gamification.badge.user.wizard model is defined in module: gamification. It has 3 computed fields: user_id, display_name, __last_update. Stored computed fields: none. Related fields: user_id -> employee_id.user_id. Original module methods: action_grant_badge.


Show me the fields of pos.promotion.discount.category. or What are the available fields for pos.promotion.discount.category?

Response: The pos.promotion.discount.category model has 17 fields. Field types distribution: boolean: 1, many2one: 4, many2many: 1, float: 5, char: 2, integer: 1, datetime: 3. Computed fields: 2. Field details: active (boolean) [module: equip3_pos_masterdata]; category_id (many2one) -> pos.category [module: equip3_pos_masterdata]; category_ids (many2many) -> pos.category [module: equip3_pos_masterdata]; discount (float) [module: equip3_pos_masterdata]; min_qty (float) [module: equip3_pos_masterdata]; discount2 (float) [module: equip3_pos_masterdata]; multi_discount (char) [module: equip3_pos_masterdata]; promotion_id (many2one) [required] -> pos.promotion [module: equip3_pos_masterdata]; discount_fixed_amount (float) [module: equip3_pos_masterdata]; max_discount_amount (float) [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].


How does wizard.ir.model.menu.create relate to other models? or List all relational fields in wizard.ir.model.menu.create.

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


What business logic is in ir.qweb.field.text? or What operations can I perform on ir.qweb.field.text?

Response: To use the ir.qweb.field.text 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 tables does equip3_reporting_asset_wizard reference? or Show me the foreign key constraints of equip3_reporting_asset_wizard.

Response: Foreign keys in equip3_reporting_asset_wizard: create_uid -> res_users.id [constraint: equip3_reporting_asset_wizard_create_uid_fkey]; write_uid -> res_users.id [constraint: equip3_reporting_asset_wizard_write_uid_fkey]; year -> sh_fiscal_year.id [constraint: equip3_reporting_asset_wizard_year_fkey]. Total foreign key relationships: 3. Referenced tables: sh_fiscal_year, res_users.


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

Response: Columns in stock_warn_insufficient_qty_unbuild: id (integer) [NOT NULL] [DEFAULT: nextval('stock_warn_insufficient_qty_unbuild_id_seq'::regclass)] [PRECISION: 32]; product_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Product]; location_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Location]; quantity (double precision) [NOT NULL] [PRECISION: 53] [COMMENT: Quantity]; product_uom_name (character varying) [NOT NULL] [COMMENT: Unit of Measure]; unbuild_id (integer) [PRECISION: 32] [COMMENT: Unbuild]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 10. Statistics: 5 nullable, 1 with defaults, 0 with length constraints.


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

Response: Foreign keys in calendar_alarm: create_uid -> res_users.id [constraint: calendar_alarm_create_uid_fkey]; write_uid -> res_users.id [constraint: calendar_alarm_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


Show me the fields of picking.order. or What field types are used in picking.order?

Response: The picking.order model has 75 fields. Field types distribution: boolean: 7, many2one: 19, datetime: 7, selection: 6, float: 1, char: 18, one2many: 6, text: 2, date: 2, many2many: 2, integer: 5. Computed fields: 25. Field details: active (boolean) [module: pragmatic_odoo_delivery_boy]; delivery_boy (many2one) -> res.partner [module: pragmatic_odoo_delivery_boy]; sale_order (many2one) -> sale.order [module: pragmatic_odoo_delivery_boy]; invoice (many2one) -> account.move [module: pragmatic_odoo_delivery_boy]; picking (many2one) -> stock.picking [module: pragmatic_odoo_delivery_boy]; assigned_date (datetime) [module: pragmatic_odoo_delivery_boy]; partner_id (many2one) [readonly] -> res.partner [compute: <bound method Field._compute_related of picking.order.partner_id>] [not stored] [module: pragmatic_odoo_delivery_boy] [related: sale_order.partner_id]; state (selection) [readonly] [module: pragmatic_odoo_delivery_boy]; payment (selection) [readonly] [module: pragmatic_odoo_delivery_boy]; distance_btn_2_loc (float) [module: pragmatic_odoo_delivery_boy]; zip_code (char) [module: pragmatic_odoo_delivery_boy]; order_source (selection) [readonly] [module: pragmatic_odoo_delivery_boy]; pos_order_id (many2one) -> pos.order [module: pragmatic_odoo_delivery_boy]; name (char) [readonly] [module: pragmatic_odoo_delivery_boy]; pos_partner_id (many2one) -> res.partner [module: pragmatic_odoo_delivery_boy]; display_delivery_time (datetime) [module: pragmatic_odoo_delivery_boy]; delivery_time (datetime) [readonly] [module: pragmatic_odoo_delivery_boy]; street (char) [module: pragmatic_odoo_delivery_boy]; street2 (char) [module: pragmatic_odoo_delivery_boy]; city (char) [module: pragmatic_odoo_delivery_boy]; state_id (many2one) -> res.country.state [module: pragmatic_odoo_delivery_boy]; country_id (many2one) -> res.country [module: pragmatic_odoo_delivery_boy]; email (char) [module: pragmatic_odoo_delivery_boy]; phone (char) [module: pragmatic_odoo_delivery_boy]; bank_statement_ids (one2many) [readonly] -> pos.payment [module: pragmatic_odoo_delivery_boy]; lines (one2many) [readonly] -> picking.order.line [module: pragmatic_odoo_delivery_boy]; session_id (many2one) [readonly] -> pos.session [module: pragmatic_odoo_delivery_boy]; order_date (datetime) [readonly] [module: pragmatic_odoo_delivery_boy]; order_ref (char) [readonly] [module: pragmatic_odoo_delivery_boy]; cashier (many2one) -> res.users [module: pragmatic_odoo_delivery_boy]; order_note (text) [module: pragmatic_odoo_delivery_boy]; payment_status_with_driver (boolean) [module: pragmatic_odoo_delivery_boy]; payment_status (char) [module: pragmatic_odoo_delivery_boy]; warehouse_id (many2one) -> stock.warehouse [module: pragmatic_odoo_delivery_boy]; latitude (char) [module: pragmatic_odoo_delivery_boy]; longitude (char) [module: pragmatic_odoo_delivery_boy]; transaction_id (many2one) -> payment.transaction [module: pragmatic_odoo_delivery_boy]; acquirer_type (char) [module: pragmatic_odoo_delivery_boy]; delivery_type (selection) [module: pragmatic_odoo_delivery_boy]; stage_id (many2one) -> order.stage [module: pragmatic_odoo_delivery_boy]; activity_ids (one2many) -> mail.activity [module: mail]; activity_state (selection) [readonly] [compute: _compute_activity_state] [not stored] [module: mail]; activity_user_id (many2one) -> res.users [compute: <bound method Field._compute_related of picking.order.activity_user_id>] [not stored] [module: mail] [related: activity_ids.user_id] [inverse: <bound method Field._inverse_related of picking.order.activity_user_id>]; activity_type_id (many2one) -> mail.activity.type [compute: <bound method Field._compute_related of picking.order.activity_type_id>] [not stored] [module: mail] [related: activity_ids.activity_type_id] [inverse: <bound method Field._inverse_related of picking.order.activity_type_id>]; activity_type_icon (char) [readonly] [compute: <bound method Field._compute_related of picking.order.activity_type_icon>] [not stored] [module: mail] [related: activity_ids.icon]; activity_date_deadline (date) [readonly] [compute: _compute_activity_date_deadline] [not stored] [module: mail]; my_activity_date_deadline (date) [readonly] [compute: _compute_my_activity_date_deadline] [not stored] [module: mail]; activity_summary (char) [compute: <bound method Field._compute_related of picking.order.activity_summary>] [not stored] [module: mail] [related: activity_ids.summary] [inverse: <bound method Field._inverse_related of picking.order.activity_summary>]; activity_exception_decoration (selection) [readonly] [compute: _compute_activity_exception_type] [not stored] [module: mail]; activity_exception_icon (char) [readonly] [compute: _compute_activity_exception_type] [not stored] [module: mail]; message_is_follower (boolean) [readonly] [compute: _compute_is_follower] [not stored] [module: mail]; message_follower_ids (one2many) -> mail.followers [module: mail]; message_partner_ids (many2many) [readonly] -> res.partner [compute: _get_followers] [not stored] [module: mail]; message_channel_ids (many2many) [readonly] -> mail.channel [compute: _get_followers] [not stored] [module: mail]; message_ids (one2many) -> mail.message [module: mail]; message_unread (boolean) [readonly] [compute: _get_message_unread] [not stored] [module: mail]; message_unread_counter (integer) [readonly] [compute: _get_message_unread] [not stored] [module: mail]; message_needaction (boolean) [readonly] [compute: _get_message_needaction] [not stored] [module: mail]; message_needaction_counter (integer) [readonly] [compute: _get_message_needaction] [not stored] [module: mail]; message_has_error (boolean) [readonly] [compute: _compute_message_has_error] [not stored] [module: mail]; message_has_error_counter (integer) [readonly] [compute: _compute_message_has_error] [not stored] [module: mail]; message_attachment_count (integer) [readonly] [compute: _compute_message_attachment_count] [not stored] [module: mail]; message_main_attachment_id (many2one) -> ir.attachment [module: mail]; website_message_ids (one2many) -> mail.message [module: portal]; message_has_sms_error (boolean) [readonly] [compute: _compute_message_has_sms_error] [not stored] [module: sms]; access_url (char) [readonly] [compute: _compute_access_url] [not stored] [module: portal]; access_token (char) [module: portal]; access_warning (text) [readonly] [compute: _compute_access_warning] [not stored] [module: portal]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


List all relational fields in sh.mrp.pics. or Show me the relational structure of sh.mrp.pics.

Response: The sh.mrp.pics model has 7 relational fields: product_id -> product.product; sh_quality_point_id -> sh.qc.point; mrp_id -> mrp.production; workorder_id -> mrp.workorder; attachment_ids -> ir.attachment; create_uid -> res.users; write_uid -> res.users. Many2many fields: attachment_ids. One2many fields: none.


What is the uom.category model? or Can you explain the purpose of uom.category?

Response: The uom.category model represents Product UoM Categories in the ERP system. It contains 9 fields and is used to manage product uom categories data. Defined in module: uom. Key fields include: name, is_pos_groupable, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Tell me about the purchase.change.request model. or What does the purchase.change.request model represent?

Response: The purchase.change.request model represents Purchase Change Request in the ERP system. It contains 25 fields and is used to manage purchase change request data. Defined in module: equip3_accounting_budget. Key fields include: name, requested_id, budget_std_id, date, company_id, branch_id, pur_change_req_ids, state, state1, state2, budget_line, approval_matrix, is_allowed_to_approval_matrix, approved_matrix_ids, approval_matrix_line_id, is_approve_button, currency_id, request_partner_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: Columns in qiscus_wa_template: id (integer) [NOT NULL] [DEFAULT: nextval('qiscus_wa_template_id_seq'::regclass)] [PRECISION: 32]; message_main_attachment_id (integer) [PRECISION: 32] [COMMENT: Main Attachment]; name (character varying) [COMMENT: Name]; namespace (character varying) [COMMENT: Namespace]; qiscus_template_id (integer) [PRECISION: 32] [COMMENT: Qiscus Template]; category (character varying) [COMMENT: Category]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 10. Statistics: 9 nullable, 1 with defaults, 0 with length constraints.


Show me the fields of res.country.group. or Which fields are required in res.country.group?

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


Show me the relational structure of decimal.precision. or How does decimal.precision relate to other models?

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


Can you explain the purpose of sh.stock.move.text? or How is sh.stock.move.text used in the system?

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


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

Response: Foreign keys in project_task_create_timesheet: create_uid -> res_users.id [constraint: project_task_create_timesheet_create_uid_fkey]; task_id -> project_task.id [constraint: project_task_create_timesheet_task_id_fkey]; write_uid -> res_users.id [constraint: project_task_create_timesheet_write_uid_fkey]. Total foreign key relationships: 3. Referenced tables: project_task, res_users.


How to work with stock.package.destination fields? or How do I use the stock.package.destination model?

Response: To use the stock.package.destination model, you need to provide values for required fields: picking_id, move_line_ids, location_dest_id. Readonly fields: move_line_ids, filtered_location, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: picking_id [required]; move_line_ids [required] [readonly] [computed] [no_copy]; location_dest_id [required]; filtered_location [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.


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

Response: Columns in product_sale_details_report: id (integer) [NOT NULL] [DEFAULT: nextval('product_sale_details_report_id_seq'::regclass)] [PRECISION: 32]; product_id (integer) [PRECISION: 32] [COMMENT: Product]; product_name (character varying) [COMMENT: Name]; code (character varying) [COMMENT: Code]; quantity (double precision) [PRECISION: 53] [COMMENT: Qty]; price_unit (double precision) [PRECISION: 53] [COMMENT: Price Unit]; discount (double precision) [PRECISION: 53] [COMMENT: Disc]; uom (character varying) [COMMENT: UoM]; details_id (integer) [PRECISION: 32] [COMMENT: Details]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 13. Statistics: 12 nullable, 1 with defaults, 0 with length constraints.


Show me the fields of sh.purchase.analysis.wizard. or Describe the field structure of sh.purchase.analysis.wizard.

Response: The sh.purchase.analysis.wizard model has 15 fields. Field types distribution: datetime: 5, many2many: 4, selection: 2, integer: 1, char: 1, many2one: 2. Computed fields: 2. Field details: sh_start_date (datetime) [required] [module: sh_purchase_reports]; sh_end_date (datetime) [required] [module: sh_purchase_reports]; sh_partner_ids (many2many) [required] -> res.partner [module: sh_purchase_reports]; sh_status (selection) [module: sh_purchase_reports]; report_by (selection) [module: sh_purchase_reports]; sh_product_ids (many2many) -> product.product [module: sh_purchase_reports]; company_ids (many2many) -> res.company [module: sh_purchase_reports]; branch_ids (many2many) -> res.branch [module: equip3_purchase_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].


What field types are used in access.domain.ah? or List all fields in the access.domain.ah model.

Response: The access.domain.ah model has 17 fields. Field types distribution: many2one: 4, char: 3, boolean: 6, integer: 1, datetime: 3. Computed fields: 3. Field details: model_id (many2one) [required] -> ir.model [module: simplify_access_management]; model_name (char) [readonly] [compute: <bound method Field._compute_related of access.domain.ah.model_name>] [stored] [module: simplify_access_management] [related: model_id.model]; apply_domain (boolean) [module: simplify_access_management]; domain (char) [module: simplify_access_management]; access_management_id (many2one) -> access.management [module: simplify_access_management]; read_right (boolean) [module: simplify_access_management]; create_right (boolean) [module: simplify_access_management]; write_right (boolean) [module: simplify_access_management]; delete_right (boolean) [module: simplify_access_management]; soft_restrict (boolean) [module: advance_access_management]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


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

Response: Columns in purchase_request_line: id (integer) [NOT NULL] [DEFAULT: nextval('purchase_request_line_id_seq'::regclass)] [PRECISION: 32]; message_main_attachment_id (integer) [PRECISION: 32] [COMMENT: Main Attachment]; name (character varying) [COMMENT: Description]; product_uom_id (integer) [PRECISION: 32] [COMMENT: UoM]; product_qty (numeric) [COMMENT: Quantity]; request_id (integer) [PRECISION: 32] [COMMENT: Purchase Request]; company_id (integer) [PRECISION: 32] [COMMENT: Company]; analytic_account_id (integer) [PRECISION: 32] [COMMENT: Analytic Account]; requested_by (integer) [PRECISION: 32] [COMMENT: Requested by]; assigned_to (integer) [PRECISION: 32] [COMMENT: Assigned to]; date_start (date) [COMMENT: Creation date]; description (text) [COMMENT: PR Description]; origin (character varying) [COMMENT: Source Document]; date_required (date) [NOT NULL] [COMMENT: Request Date]; specifications (text) [COMMENT: Specifications]; request_state (character varying) [COMMENT: Request state]; supplier_id (integer) [PRECISION: 32] [COMMENT: Preferred supplier]; cancelled (boolean) [COMMENT: Cancelled]; purchase_state (character varying) [COMMENT: Purchase Status]; orderpoint_id (integer) [PRECISION: 32] [COMMENT: Orderpoint]; qty_in_progress (numeric) [COMMENT: Qty In Progress]; qty_done (numeric) [COMMENT: Qty Done]; qty_cancelled (numeric) [COMMENT: Qty Cancelled]; qty_to_buy (boolean) [COMMENT: There is some pending qty to buy]; pending_qty_to_receive (numeric) [COMMENT: Pending Qty to Receive]; estimated_cost (numeric) [COMMENT: Estimated Cost]; product_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Product]; 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]; mr_line_id (integer) [PRECISION: 32] [COMMENT: Mr Line]; cancelled_qty (double precision) [PRECISION: 53] [COMMENT: Cancelled Quantity]; sequence (integer) [PRECISION: 32] [COMMENT: Sequence]; sequence2 (integer) [PRECISION: 32] [COMMENT: No]; purchase_req_budget (double precision) [PRECISION: 53] [COMMENT: Purchase Request Budget]; rem_budget (double precision) [PRECISION: 53] [COMMENT: Remaining Budget]; purchase_req_state (character varying) [COMMENT: Purchase Req State]; assigned_to_partner_id (integer) [PRECISION: 32] [COMMENT: Related Partner]; set_order (character varying) [COMMENT: Set Order ID]; is_goods_orders (boolean) [COMMENT: Goods Orders]; is_services_orders (boolean) [COMMENT: Services Orders]; dest_loc_id (integer) [PRECISION: 32] [COMMENT: Destination]; picking_type_dest (integer) [PRECISION: 32] [COMMENT: Picking Type]; current_qty (double precision) [PRECISION: 53] [COMMENT: Current Qty in Warehouse]; incoming_stock (double precision) [PRECISION: 53] [COMMENT: Incoming Stock]; agreement_id (integer) [PRECISION: 32] [COMMENT: Purchase Tender]; tender_qty (double precision) [PRECISION: 53] [COMMENT: Tender Qty]; qty_received (double precision) [PRECISION: 53] [COMMENT: Received Qty]; is_assets_orders (boolean) [COMMENT: Assets Orders]; realized_amount (double precision) [PRECISION: 53] [COMMENT: Realized Budget]; confirm_purchase_req_budget (double precision) [PRECISION: 53] [COMMENT: Confirmed Purchase Request Budget]; confirm_realized_amount (double precision) [PRECISION: 53] [COMMENT: Confirmed Realized Budget]; confirm_budget_data (boolean) [COMMENT: Confirm Budget Data]; barcode (character varying) [COMMENT: Barcode]; merchendise_id (integer) [PRECISION: 32] [COMMENT: Merchendise Code]. Total columns: 56. Statistics: 53 nullable, 1 with defaults, 0 with length constraints.


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

Response: Foreign keys in account_invoice_send: composer_id -> mail_compose_message.id [constraint: account_invoice_send_composer_id_fkey]; create_uid -> res_users.id [constraint: account_invoice_send_create_uid_fkey]; template_id -> mail_template.id [constraint: account_invoice_send_template_id_fkey]; write_uid -> res_users.id [constraint: account_invoice_send_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: mail_compose_message, res_users, mail_template.


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

Response: The crm_lead_salesperson_lines table has 9 columns and 4 foreign key relationships. It stores data related to crm lead salesperson lines in the system. The table has 1 indexes for performance optimization. Column types: integer: 5, double precision: 1, character varying: 1, timestamp without time zone: 2. Nullable columns: 8, columns with defaults: 1.


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

Response: Foreign keys in mrp_bom_line: bom_id -> mrp_bom.id [constraint: mrp_bom_line_bom_id_fkey]; company_id -> res_company.id [constraint: mrp_bom_line_company_id_fkey]; create_uid -> res_users.id [constraint: mrp_bom_line_create_uid_fkey]; operation_id -> mrp_routing_workcenter.id [constraint: mrp_bom_line_operation_id_fkey]; operation_two_id -> mrp_bom_operation.id [constraint: mrp_bom_line_operation_two_id_fkey]; product_id -> product_product.id [constraint: mrp_bom_line_product_id_fkey]; product_uom_id -> uom_uom.id [constraint: mrp_bom_line_product_uom_id_fkey]; write_uid -> res_users.id [constraint: mrp_bom_line_write_uid_fkey]. Total foreign key relationships: 8. Referenced tables: product_product, mrp_routing_workcenter, res_company, res_users, mrp_bom, uom_uom, mrp_bom_operation.


Describe the implementation of product.ratio.line. or What modules define product.ratio.line?

Response: The product.ratio.line model is defined in module: equip3_inventory_masterdata. It has 6 computed fields: description, uom_ref_id, product_variant_ids, is_custom_uom, display_name, __last_update. Stored computed fields: none. Related fields: product_variant_ids -> product_tmpl_id.product_variant_ids, is_custom_uom -> uom_id.is_custom_uom. Original module methods: _compute_description, _compute_uom_reference, _onchange_uom_id, _onchange_product_tmpl_id, _check_null_ratio, _product_constrains.


What fields does ir.qweb.field.contact have? or Describe the field structure of ir.qweb.field.contact.

Response: The ir.qweb.field.contact 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 foreign keys exist in vendor.deposit.report? or Show me the relational structure of vendor.deposit.report.

Response: The vendor.deposit.report model has 7 relational fields: partner_id -> res.partner; currency_id -> res.currency; deposit_move_id -> account.move; return_deposit -> account.move; deposit_reconcile_journal_id -> account.journal; journal_id -> account.journal; deposit_account_id -> account.account. Many2many fields: none. One2many fields: none.


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

Response: Columns in hour_group: id (integer) [NOT NULL] [DEFAULT: nextval('hour_group_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [COMMENT: Name]; start_hour (double precision) [PRECISION: 53] [COMMENT: Start Hour]; end_hour (double precision) [PRECISION: 53] [COMMENT: End Hour]; active (boolean) [COMMENT: Active]; company_id (integer) [PRECISION: 32] [COMMENT: Company]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 10. Statistics: 9 nullable, 1 with defaults, 0 with length constraints.


Which fields are required in sh.tsp.top.purchasing.product.wizard? or What are the available fields for sh.tsp.top.purchasing.product.wizard?

Response: The sh.tsp.top.purchasing.product.wizard model has 15 fields. Field types distribution: selection: 1, datetime: 7, integer: 2, float: 1, many2many: 1, char: 1, many2one: 2. Computed fields: 2. Field details: type (selection) [module: sh_purchase_reports]; date_from (datetime) [required] [module: sh_purchase_reports]; date_to (datetime) [required] [module: sh_purchase_reports]; date_compare_from (datetime) [module: sh_purchase_reports]; date_compare_to (datetime) [module: sh_purchase_reports]; no_of_top_item (integer) [required] [module: sh_purchase_reports]; product_qty (float) [module: sh_purchase_reports]; company_ids (many2many) -> res.company [module: sh_purchase_reports]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


Tell me about the setu.inventory.outofstock.report model. or Describe the setu.inventory.outofstock.report model in Odoo.

Response:
The setu.inventory.outofstock.report model represents
        Inventory OutOfStock Report
        ===================================================================
        Inventory OutOfStock Report is used to capture all products which are having demand but stock shortage as well.
     in the ERP system. It contains 16 fields and is used to manage
        inventory outofstock report
        ===================================================================
        inventory outofstock report is used to capture all products which are having demand but stock shortage as well.
     data. Defined in module: setu_advance_inventory_reports. Key fields include: advance_stock_days, stock_file_data, start_date, end_date, product_category_ids, product_ids, warehouse_ids, company_id, company_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: Foreign keys in account_tax_filiation_rel: child_tax -> account_tax.id [constraint: account_tax_filiation_rel_child_tax_fkey]; parent_tax -> account_tax.id [constraint: account_tax_filiation_rel_parent_tax_fkey]. Total foreign key relationships: 2. Referenced tables: account_tax.


What data can be stored in auditlog.http.request? or Which fields are required in auditlog.http.request?

Response: The auditlog.http.request model has 13 fields. Field types distribution: char: 4, many2one: 4, one2many: 1, integer: 1, datetime: 3. Computed fields: 2. Field details: display_name (char) [readonly] [compute: _compute_display_name] [stored] [module: auditlog]; name (char) [module: auditlog]; root_url (char) [module: auditlog]; user_id (many2one) -> res.users [module: auditlog]; http_session_id (many2one) -> auditlog.http.session [module: auditlog]; user_context (char) [module: auditlog]; log_ids (one2many) -> auditlog.log [module: auditlog]; id (integer) [readonly] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


Can you explain the purpose of account.reconcile.model.line.template? or What does the account.reconcile.model.line.template model represent?

Response: The account.reconcile.model.line.template model represents Reconcile Model Line Template in the ERP system. It contains 15 fields and is used to manage reconcile model line template data. Defined in module: account. Key fields include: model_id, sequence, account_id, label, amount_type, amount_string, force_tax_included, tax_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What are common use cases for setu.inventory.fsn.analysis.bi.report? or How to query setu.inventory.fsn.analysis.bi.report data?

Response: To use the setu.inventory.fsn.analysis.bi.report 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 technical details of intrawarehouse.transfer.line? or What is the module hierarchy for intrawarehouse.transfer.line?

Response: The intrawarehouse.transfer.line model is defined in module: equip3_inventory_operation. It has 4 computed fields: filter_location_ids, warehouse_id, display_name, __last_update. Stored computed fields: none. Related fields: warehouse_id -> mr_id.destination_warehouse_id. Original module methods: _compute_location.


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

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


Show me the relational structure of return.reason. or What one2many fields are in return.reason?

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


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

Response: Foreign keys in pos_config_assign_orders_rel: assign_config_id -> pos_config.id [constraint: pos_config_assign_orders_rel_assign_config_id_fkey]; from_config_id -> pos_config.id [constraint: pos_config_assign_orders_rel_from_config_id_fkey]. Total foreign key relationships: 2. Referenced tables: pos_config.


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

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


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

Response: Columns in mail_moderation: id (integer) [NOT NULL] [DEFAULT: nextval('mail_moderation_id_seq'::regclass)] [PRECISION: 32]; email (character varying) [NOT NULL] [COMMENT: Email]; status (character varying) [NOT NULL] [COMMENT: Status]; channel_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Channel]; 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: 4 nullable, 1 with defaults, 0 with length constraints.


How is report.excel.param used in the system? or What does the report.excel.param model represent?

Response: The report.excel.param model represents Report Excel Params in the ERP system. It contains 15 fields and is used to manage report excel params data. Defined in module: report_excel. Key fields include: sequence, report_excel_id, name, code, type_param, param_ir_model_id, wizard_param_ir_model_field_id, param_required, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What is the sequence.mixin model? or What does the sequence.mixin model represent?

Response: The sequence.mixin model represents Automatic sequence in the ERP system. It contains 5 fields and is used to manage automatic sequence data. Defined in module: account. Key fields include: sequence_prefix, sequence_number, id, display_name, __last_update.


What modules define mailing.trace.report? or Which fields are stored computed fields in mailing.trace.report?

Response: The mailing.trace.report model is defined in module: mass_mailing. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: init, _report_get_request, _report_get_request_select_items, _report_get_request_from_items, _report_get_request_where_items, _report_get_request_group_by_items.


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

Response: Columns in res_branch: id (integer) [NOT NULL] [DEFAULT: nextval('res_branch_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [NOT NULL] [COMMENT: Name]; company_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Company]; telephone (character varying) [COMMENT: Telephone No]; address (text) [COMMENT: Address]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]; active_company_sequence (integer) [PRECISION: 32] [COMMENT: Sequence]; message_main_attachment_id (integer) [PRECISION: 32] [COMMENT: Main Attachment]; street (character varying) [COMMENT: Street]; street_2 (character varying) [COMMENT: Street2]; city (character varying) [COMMENT: City]; state_id (integer) [PRECISION: 32] [COMMENT: State]; country_id (integer) [PRECISION: 32] [COMMENT: Country]; zip_code (character varying) [COMMENT: Zip]; is_external_link (boolean) [COMMENT: Is External Link]; branch_code (character varying) [COMMENT: Branch Code]; npwp (character varying) [COMMENT: NPWP]; user_id (integer) [PRECISION: 32] [COMMENT: Branch Manager]. Total columns: 21. Statistics: 18 nullable, 1 with defaults, 0 with length constraints.


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

Response: The sh_notification_logger table has 10 columns and 3 foreign key relationships. It stores data related to sh notification logger in the system. The table has 1 indexes for performance optimization. Column types: integer: 4, character varying: 3, timestamp without time zone: 3. Nullable columns: 9, columns with defaults: 1.


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

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


How do I use the customer.deposit.wizard model? or How to work with customer.deposit.wizard fields?

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


What operations can I perform on pos.sale.report? or What fields are readonly in pos.sale.report?

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


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

Response: Foreign keys in account_analytic_tag_account_move_line_rel: account_analytic_tag_id -> account_analytic_tag.id [constraint: account_analytic_tag_account_mov_account_analytic_tag_id_fkey15]; account_analytic_tag_id -> account_analytic_tag.id [constraint: account_analytic_tag_account_move__account_analytic_tag_id_fkey]; account_analytic_tag_id -> account_analytic_tag.id [constraint: account_analytic_tag_account_move_account_analytic_tag_id_fkey4]; account_analytic_tag_id -> account_analytic_tag.id [constraint: account_analytic_tag_account_move_account_analytic_tag_id_fkey5]; account_analytic_tag_id -> account_analytic_tag.id [constraint: account_analytic_tag_account_move_account_analytic_tag_id_fkey7]; account_move_line_id -> account_move_line.id [constraint: account_analytic_tag_account_move_li_account_move_line_id_fkey1]; account_move_line_id -> account_move_line.id [constraint: account_analytic_tag_account_move_li_account_move_line_id_fkey2]; account_move_line_id -> account_move_line.id [constraint: account_analytic_tag_account_move_li_account_move_line_id_fkey3]; account_move_line_id -> account_move_line.id [constraint: account_analytic_tag_account_move_li_account_move_line_id_fkey4]; account_move_line_id -> account_move_line.id [constraint: account_analytic_tag_account_move_li_account_move_line_id_fkey5]; account_move_line_id -> account_move_line.id [constraint: account_analytic_tag_account_move_lin_account_move_line_id_fkey]. Total foreign key relationships: 11. Referenced tables: account_move_line, account_analytic_tag.


Tell me about the whatsapp.message.wizard model. or How is whatsapp.message.wizard used in the system?

Response: The whatsapp.message.wizard model represents whatsapp.message.wizard in the ERP system. It contains 16 fields and is used to manage whatsapp.message.wizard data. Defined in module: ss_whatsapp_connector. Key fields include: user_id, mobile_number, message, model, template_id, message_send, attachment_ids, crm_lead, company_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.