Can you explain the purpose of sale.order.line?

Response: The sale.order.line model represents Sales Order Line in the ERP system. It contains 161 fields and is used to manage sales order line data. Key fields include: order_id, sequence, invoice_lines, invoice_status, price_tax, price_reduce, price_reduce_taxinc, price_reduce_taxexcl, discount, product_updatable, product_uom_category_id, product_uom_readonly, product_custom_attribute_value_ids, product_no_variant_attribute_value_ids, qty_delivered, qty_delivered_manual, qty_to_invoice, qty_invoiced, untaxed_amount_invoiced, untaxed_amount_to_invoice, salesman_id, currency_id, order_partner_id, analytic_tag_ids, is_expense, is_downpayment, state, display_type, is_reward_line, sale_order_option_ids, is_configurable_product, product_template_attribute_value_ids, purchase_line_ids, purchase_line_count, product_packaging, route_id, move_ids, product_type, virtual_available_at_date, scheduled_date, forecast_expected_date, free_qty_today, qty_available_today, warehouse_id, qty_to_deliver, is_mto, display_qty_widget, name_short, linked_line_id, option_line_ids, is_apply_on_discount_amount, discount_type, discount_amt, is_delivery, product_qty, recompute_delivery_price, is_process_rma, margin, margin_percent, purchase_price, project_id, task_id, is_service, location_id, tick, warning_stock, qty_delivered_method, analytic_line_ids, remaining_hours_available, remaining_hours, discount_line, redeem_points, redeem_value, setting, is_single_warehouse, product_template_id_domain, customer_id, user_id, sequence_no, product_id, product_uom_qty, price_unit, customer_lead, company_id, name, last_sale_price, last_customer_sale_price, account_tag_ids, analytic_account_id, net_amount, location_dest_id, line_warehouse_id, line_warehouse_id_new, branch_id, delivery_address_id, multiple_do_date, multiple_do_date_new, multi_discount, discount_method, discount_amount, filter_delivery_address_id, hide_button_qa_sale, trigger, is_down_payment, product_template_id, product_uom, tax_id, res_product_uom, brand_ids, price_subtotal, price_total, tax_discount_policy, discounted_value, sale_line_sequence, reward_quantity, customer_voucher_id, bo_id, insert, parent_id, lot_id, pos_note, pos_branch_id, barcode, campaign_id, source_id, medium_id, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, access_url, access_token, access_warning, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What models are connected to account.tax.report?

Response: The account.tax.report model has 7 relational fields: country_id -> res.country; line_ids -> account.tax.report.line; root_line_ids -> account.tax.report.line; company_id -> res.company; branch_id -> res.branch; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


Describe the many2many relations for ir.property.

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


What models are connected to purchase.report?

Response: The purchase.report model has 16 relational fields: product_id -> product.product; partner_id -> res.partner; product_uom -> uom.uom; company_id -> res.company; currency_id -> res.currency; user_id -> res.users; category_id -> product.category; product_tmpl_id -> product.template; country_id -> res.country; fiscal_position_id -> account.fiscal.position; account_analytic_id -> account.analytic.account; commercial_partner_id -> res.partner; order_id -> purchase.order; team_id -> dev.purchase.team; picking_type_id -> stock.warehouse; branch_id -> res.branch. Many2many fields: none.


What operations can I perform on mail.mail?

Response: To use the mail.mail model, you need to provide values for required fields: mail_message_id, message_type. Readonly fields: references, state, failure_reason, fetchmail_server_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, description, needaction, has_error, starred, message_id, need_moderation, rating_value, has_sms_error, snailmail_error. The model supports standard CRUD operations through the ORM.


What are common use cases for recurring.move.line?

Response: To use the recurring.move.line model, you need to provide values for required fields: recurring_id, account_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


How to create records in ir.actions.server?

Response: To use the ir.actions.server model, you need to provide values for required fields: name, type, model_id, activity_user_type, usage, state, binding_type. Readonly fields: model_name, crud_model_name, mass_edit_apply_domain_in_lines, xml_id, website_url, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


What models are connected to report.equip3_pos_report.report_pos_payment?

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


How to query ir.actions.todo data?

Response: To use the ir.actions.todo model, you need to provide values for required fields: action_id, state. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


Describe the implementation of project.task.recurrence.

Response: The project.task.recurrence model is defined in module: project. It has 0 computed fields: . Stored computed fields: none.


What methods are available in confirm.stock.sms?

Response: The confirm.stock.sms model is defined in module: stock_sms. It has 0 computed fields: . Stored computed fields: none.


How does stock.warehouse.orderpoint relate to other models?

Response: The stock.warehouse.orderpoint model has 37 relational fields: product_tmpl_id -> product.template; product_id -> product.product; product_category_id -> product.category; product_uom -> uom.uom; group_id -> procurement.group; allowed_location_ids -> stock.location; rule_ids -> stock.rule; allowed_route_ids -> stock.location.route; route_id -> stock.location.route; bom_id -> mrp.bom; location_id -> stock.location; source_location_id -> stock.location; purchase_request_id -> purchase.request; purchase_order_id -> purchase.order; material_request_id -> material.request; internal_transfer_id -> internal.transfer; responsible_id -> res.users; branch_id -> res.branch; company_id -> res.company; warehouse_id -> stock.warehouse; filter_warehouse_id -> stock.location; notification_user_ids -> res.users; supplier_id -> res.partner; campaign_id -> utm.campaign; source_id -> utm.source; medium_id -> utm.medium; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: rule_ids, allowed_route_ids, responsible_id, filter_warehouse_id, notification_user_ids, message_partner_ids, message_channel_ids.


How do I use the ks.sales.forecast model?

Response: To use the ks.sales.forecast model, you need to provide values for required fields: ks_start_date, ks_end_date, ks_forecast_unit, ks_forecast_period. Readonly fields: ks_name, ks_default_forecast_method, ks_model, ks_is_predicted_method, ks_resp, ks_resd, ks_resq, ks_sp, ks_sd, ks_sq, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


Tell me about the export.efaktur model.

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


What are the available fields for mail.render.mixin?

Response: The mail.render.mixin model has 9 fields: lang, model_object_field, sub_object, sub_model_object_field, null_value, copyvalue, id, display_name, __last_update. Field types distribution: char: 4, many2one: 3, integer: 1, datetime: 1.


What operations can I perform on ir.cron?

Response: To use the ir.cron model, you need to provide values for required fields: ir_actions_server_id, user_id, nextcall, name, type, model_id, activity_user_type, usage, state, binding_type. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update, model_name, crud_model_name, mass_edit_apply_domain_in_lines, xml_id, website_url. The model supports standard CRUD operations through the ORM.


Which fields in account.fiscal.position.tax.template are computed?

Response: The account.fiscal.position.tax.template model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.


What foreign keys exist in account.keterangan.tambahan?

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


How is itr.approval.matrix.line used in the system?

Response: The itr.approval.matrix.line model represents Internal Approval Matrix Line in the ERP system. It contains 34 fields and is used to manage internal approval matrix line data. Key fields include: sequence, user_ids, minimum_approver, itr_approval_matrix, approved_users, state_char, time_stamp, feedback, last_approved, approved, sequence2, transfer_id, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Tell me about the gamification.karma.rank model.

Response: The gamification.karma.rank model represents Rank based on karma in the ERP system. It contains 18 fields and is used to manage rank based on karma data. Key fields include: name, description, description_motivational, karma_min, user_ids, rank_users_count, image_1920, image_1024, image_512, image_256, image_128, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What methods are available in account.payment.method?

Response: The account.payment.method model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.


What modules define stock.return.move.line?

Response: The stock.return.move.line model is defined in module: equip3_inventory_operation. It has 0 computed fields: . Stored computed fields: none.


Can you explain the purpose of ir.actions.report?

Response: The ir.actions.report model represents Report Action in the ERP system. It contains 30 fields and is used to manage report action data. Key fields include: name, type, binding_type, model, model_id, report_type, report_name, report_file, groups_id, multi, paperformat_id, print_report_name, attachment_use, attachment, encrypt, encrypt_type, manual_password, password_fields, password_sub_field, xml_id, help, binding_model_id, binding_view_types, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How is sh.qc.team.type implemented technically?

Response: The sh.qc.team.type model is defined in module: sh_inventory_mrp_qc. It has 0 computed fields: . Stored computed fields: none.


Show me the fields of report.equip3_pos_report.report_profit_loss.

Response: The report.equip3_pos_report.report_profit_loss model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.


Describe the field structure of account.move.reversal.

Response: The account.move.reversal model has 18 fields: move_ids, new_move_ids, date_mode, date, reason, refund_method, journal_id, company_id, residual, currency_id, move_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2many: 2, selection: 2, date: 1, char: 3, many2one: 5, monetary: 1, integer: 1, datetime: 3.


What are the technical details of replace.product.wizard?

Response: The replace.product.wizard model is defined in module: dev_rma. It has 0 computed fields: . Stored computed fields: none.


What are common use cases for project.task.type?

Response: To use the project.task.type model, you need to provide values for required fields: name, legend_blocked, legend_done, legend_normal. Readonly fields: disabled_rating_warning, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


What fields does pos.gift.card.type have?

Response: The pos.gift.card.type model has 9 fields: name, code, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, integer: 1, many2one: 2, datetime: 3.


Describe the field structure of mailing.mailing.

Response: The mailing.mailing model has 90 fields: active, subject, preview, email_from, sent_date, schedule_date, body_arch, body_html, attachment_ids, keep_archives, campaign_id, source_id, medium_id, state, color, user_id, mailing_type, reply_to_mode, reply_to, mailing_model_real, mailing_model_id, mailing_model_name, mailing_domain, mail_server_id, contact_list_ids, contact_ab_pc, unique_ab_testing, kpi_mail_required, mailing_trace_ids, total, scheduled, expected, ignored, sent, delivered, opened, clicked, replied, bounced, failed, received_ratio, opened_ratio, replied_ratio, bounced_ratio, clicks_ratio, next_departure, use_leads, crm_lead_count, sale_quotation_count, sale_invoiced_amount, rfm_segment_id, lang, model_object_field, sub_object, sub_model_object_field, null_value, copyvalue, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, name. Field types distribution: boolean: 10, char: 15, datetime: 6, html: 2, many2many: 4, many2one: 15, selection: 5, integer: 26, one2many: 5, date: 2.


What is the pos.cashier.change.wizard model?

Response: The pos.cashier.change.wizard model represents POS Cashier Change Wizard in the ERP system. It contains 10 fields and is used to manage pos cashier change wizard data. Key fields include: start_datetime, end_datetime, pos_branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What are the relationships in base.module.uninstall?

Response: The base.module.uninstall model has 5 relational fields: module_id -> ir.module.module; module_ids -> ir.module.module; model_ids -> ir.model; create_uid -> res.users; write_uid -> res.users. Many2many fields: module_ids, model_ids.


What is the usage.type model?

Response: The usage.type model represents Usage Type in the ERP system. It contains 48 fields and is used to manage usage type data. Key fields include: company_id, branch_id, name, account_id, filter_account_ids, usage_type, income_account_id, product_category_id, inv_val_account_id, filter_income_account_ids, campaign_id, source_id, medium_id, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, access_url, access_token, access_warning, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What methods are available in kpi.item?

Response: The kpi.item model is defined in module: kpi_scorecard. It has 0 computed fields: . Stored computed fields: none.


Describe the field structure of account.journal.group.

Response: The account.journal.group model has 11 fields: name, company_id, excluded_journal_ids, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 3, many2many: 1, integer: 2, datetime: 3.


What are the technical details of report.equip3_pos_report.report_sales_summary?

Response: The report.equip3_pos_report.report_sales_summary model is defined in module: equip3_pos_report. It has 0 computed fields: . Stored computed fields: none.


Tell me about the account.move.template.line model.

Response: The account.move.template.line model represents Journal Item Template in the ERP system. It contains 62 fields and is used to manage journal item template data. Key fields include: move_id, move_name, date, ref, parent_state, journal_id, company_id, company_currency_id, tax_fiscal_country_id, account_id, account_internal_type, account_internal_group, account_root_id, sequence, name, quantity, price_unit, discount, debit, credit, balance, cumulated_balance, amount_currency, price_subtotal, price_total, reconciled, blocked, date_maturity, currency_id, partner_id, product_uom_id, product_id, product_uom_category_id, reconcile_model_id, payment_id, statement_line_id, statement_id, tax_ids, tax_line_id, tax_group_id, tax_base_amount, tax_exigible, tax_repartition_line_id, tax_tag_ids, tax_audit, amount_residual, amount_residual_currency, full_reconcile_id, matching_number, analytic_account_id, analytic_tag_ids, recompute_tax_line, display_type, is_rounding_line, exclude_from_invoice_tab, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


List all fields in the acrux.chat.default.answer model.

Response: The acrux.chat.default.answer model has 17 fields: name, sequence, file_attach, file_attach_name, template_id, default_answer_type, text, ttype, res_model, res_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 4, integer: 3, binary: 1, many2one: 3, selection: 2, text: 1, datetime: 3.


Describe the many2many relations for account.pettycash.

Response: The account.pettycash model has 24 relational fields: cash_journal -> account.journal; custodian -> res.users; main_cash_account_id -> account.account; journal -> account.journal; company_id -> res.company; branch_id -> res.branch; create_uid -> res.users; move_id -> account.move; voucher_id -> account.pettycash.voucher.wizard; paid_voucher_ids -> account.pettycash.voucher.wizard; custodian_partner -> res.partner; campaign_id -> utm.campaign; source_id -> utm.source; medium_id -> utm.medium; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; write_uid -> res.users. Many2many fields: message_partner_ids, message_channel_ids.


What methods are available in sh.account.period?

Response: The sh.account.period model is defined in module: sh_sync_fiscal_year. It has 0 computed fields: . Stored computed fields: none.


Can you explain the purpose of intrawarehouse.transfer?

Response: The intrawarehouse.transfer model represents Intrawarehouse Transfer in the ERP system. It contains 8 fields and is used to manage intrawarehouse transfer data. Key fields include: interawarehouse_transfer_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What business logic is in sh.top.vendor.excel.extended?

Response: To use the sh.top.vendor.excel.extended 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. The model supports standard CRUD operations through the ORM.


Describe the partner.opening.balance model in Odoo.

Response: The partner.opening.balance model represents partner.opening.balance in the ERP system. It contains 12 fields and is used to manage partner.opening.balance data. Key fields include: partner_id, account_receivable_id, account_payable_id, payable_opening_balance_ids, receivable_opening_balance_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What foreign keys exist in ai.memory.export.import.wizard?

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


How to create records in pos.voucher?

Response: To use the pos.voucher model, you need to provide values for required fields: start_date, end_date. Readonly fields: user_id, pos_order_id, pos_order_line_id, use_history_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


Describe the many2many relations for ks_ninja_dashboard.item_action.

Response: The ks_ninja_dashboard.item_action model has 5 relational fields: ks_dashboard_item_ids -> ks_dashboard_ninja.item; ks_dashboard_ninja_id -> ks_dashboard_ninja.board; ks_dashboard_ninja_ids -> ks_dashboard_ninja.board; create_uid -> res.users; write_uid -> res.users. Many2many fields: ks_dashboard_item_ids, ks_dashboard_ninja_ids.


What business logic is in payment.icon?

Response: To use the payment.icon 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. The model supports standard CRUD operations through the ORM.


Which fields in sh.mrp.qc.alert are computed?

Response: The sh.mrp.qc.alert model is defined in module: sh_inventory_mrp_qc. It has 0 computed fields: . Stored computed fields: none.


What modules define kpi.period.value?

Response: The kpi.period.value model is defined in module: kpi_scorecard. It has 0 computed fields: . Stored computed fields: none.


What is the purchase.agreement.legal.document model?

Response: The purchase.agreement.legal.document model represents Purchase Agreement Legal Document in the ERP system. It contains 15 fields and is used to manage purchase agreement legal document data. Key fields include: legal_document_id, partner_id, nomor_induk_berusaha, salinan_anggaran_dasar, surat_persetujuan_dirjen_ahu, akta_perubahan_pengurus_terakhir, surat_keterangan_tidak_kena_pajak, surat_pernyataan_dan_kuasa, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How is customer.degree.trust used in the system?

Response: The customer.degree.trust model represents Customer Degree Trust in the ERP system. It contains 12 fields and is used to manage customer degree trust data. Key fields include: name, overdue_day, no_of_overdue_invoices, index, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How does hr.employee.base relate to other models?

Response: The hr.employee.base model has 12 relational fields: department_id -> hr.department; job_id -> hr.job; company_id -> res.company; address_id -> res.partner; user_id -> res.users; resource_id -> resource.resource; resource_calendar_id -> resource.calendar; parent_id -> hr.employee; coach_id -> hr.employee; goal_ids -> gamification.goal; badge_ids -> gamification.badge.user; direct_badge_ids -> gamification.badge.user. Many2many fields: none.


What are the relationships in sh.send.notification?

Response: The sh.send.notification model has 4 relational fields: specific_ids -> sh.push.notification; log_historys -> sh.notification.logger; create_uid -> res.users; write_uid -> res.users. Many2many fields: specific_ids.


What foreign keys exist in create.purchase.request.direct?

Response: The create.purchase.request.direct model has 6 relational fields: supplier_id -> res.partner; item_ids -> create.purchase.request.direct.lines; journal_id -> account.journal; purchase_order_id -> purchase.order; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What methods are available in stock.scrap?

Response: The stock.scrap model is defined in module: stock. It has 0 computed fields: . Stored computed fields: none.


How is account.voucher.line used in the system?

Response: The account.voucher.line model represents Accounting Voucher Line in the ERP system. It contains 21 fields and is used to manage accounting voucher line data. Key fields include: name, sequence, voucher_id, product_id, uom_id, account_id, price_unit, price_subtotal, quantity, account_analytic_id, analytic_tag_ids, company_id, tax_ids, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What are common use cases for pos.combo.item?

Response: To use the pos.combo.item model, you need to provide values for required fields: product_id, product_combo_id, quantity. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


What business logic is in restaurant.table?

Response: To use the restaurant.table model, you need to provide values for required fields: name, shape. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


What models are connected to report.sh_purchase_reports.sh_po_product_indent_doc?

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


What are the available fields for ir.actions.todo?

Response: The ir.actions.todo model has 11 fields: action_id, sequence, state, name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, integer: 2, selection: 1, char: 2, datetime: 3.


How is snailmail.letter.format.error implemented technically?

Response: The snailmail.letter.format.error model is defined in module: snailmail. It has 0 computed fields: . Stored computed fields: none.


What are the relationships in ks_ninja_dashboard.item_action?

Response: The ks_ninja_dashboard.item_action model has 5 relational fields: ks_dashboard_item_ids -> ks_dashboard_ninja.item; ks_dashboard_ninja_id -> ks_dashboard_ninja.board; ks_dashboard_ninja_ids -> ks_dashboard_ninja.board; create_uid -> res.users; write_uid -> res.users. Many2many fields: ks_dashboard_item_ids, ks_dashboard_ninja_ids.


Describe the implementation of purchase.quotation.excel.extended.

Response: The purchase.quotation.excel.extended model is defined in module: sh_all_in_one_purchase_tools. It has 0 computed fields: . Stored computed fields: none.


How do I use the generate.closing.entries model?

Response: To use the generate.closing.entries model, you need to provide values for required fields: fiscal_year_id, closing_entry_date, journal_id, description, summary_account_id, retained_earnings_account_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


Can you explain the purpose of ir.qweb.field.float?

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


How to query pos.bus.log data?

Response: To use the pos.bus.log 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. The model supports standard CRUD operations through the ORM.


How is pos.tag implemented technically?

Response: The pos.tag model is defined in module: equip3_pos_masterdata. It has 0 computed fields: . Stored computed fields: none.


What business logic is in purchase.agreement.approval.matrix?

Response: To use the purchase.agreement.approval.matrix model, you need to provide values for required fields: name, company_id, branch_id. Readonly fields: company_id, is_good_services_order, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, access_url, access_warning, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


What methods are available in restaurant.floor?

Response: The restaurant.floor model is defined in module: pos_restaurant. It has 0 computed fields: . Stored computed fields: none.


What foreign keys exist in milestone.contract.template.line?

Response: The milestone.contract.template.line model has 4 relational fields: template_id -> milestone.contract.template; checklist_template_id -> purchase.custom.checklist.template; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What operations can I perform on choose.delivery.package?

Response: To use the choose.delivery.package model, you need to provide values for required fields: none. Readonly fields: weight_uom_name, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


Which fields in wizard.product.bundle.bi are computed?

Response: The wizard.product.bundle.bi model is defined in module: dynamic_product_bundle. It has 0 computed fields: . Stored computed fields: none.


Describe the stock.scrap.request.matrix.reject model in Odoo.

Response: The stock.scrap.request.matrix.reject model represents Stock scrap Matrix Reject in the ERP system. It contains 8 fields and is used to manage stock scrap matrix reject data. Key fields include: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Which fields in sh.qc.team are computed?

Response: The sh.qc.team model is defined in module: sh_inventory_mrp_qc. It has 0 computed fields: . Stored computed fields: none.


What business logic is in report.accounting_pdf_reports.report_general_ledger?

Response: To use the report.accounting_pdf_reports.report_general_ledger model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.


What data can be stored in asset.modify?

Response: The asset.modify model has 12 fields: name, method_number, method_period, method_end, asset_method_time, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 1, integer: 3, date: 1, char: 2, many2one: 2, datetime: 3.


What is the purchase.request.wizard.line model?

Response: The purchase.request.wizard.line model represents purchase.request.wizard.line in the ERP system. It contains 17 fields and is used to manage purchase.request.wizard.line data. Key fields include: mr_id, no, product_id, description, uom_id, qty_purchase, request_date, mr_pr_wizard, mr_line_id, dest_warehouse_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What methods are available in budget.change.req.wizard?

Response: The budget.change.req.wizard model is defined in module: equip3_accounting_budget. It has 0 computed fields: . Stored computed fields: none.


What are the available fields for setu.inventory.xyz.analysis.bi.report?

Response: The setu.inventory.xyz.analysis.bi.report model has 16 fields: product_id, product_category_id, company_id, current_stock, stock_value, stock_value_per, cum_stock_value_per, analysis_category, wizard_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 6, float: 4, char: 2, integer: 1, datetime: 3.


How to query restaurant.floor data?

Response: To use the restaurant.floor model, you need to provide values for required fields: name. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


Tell me about the journal.entry.report model.

Response: The journal.entry.report model represents journal.entry.report in the ERP system. It contains 15 fields and is used to manage journal.entry.report data. Key fields include: company_id, journal_ids, account_ids, display_account, target_move, date_from, date_to, move_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What modules define pos.category?

Response: The pos.category model is defined in module: point_of_sale. It has 0 computed fields: . Stored computed fields: none.


What is the stock.day.average model?

Response: The stock.day.average model represents Stock Day Average in the ERP system. It contains 45 fields and is used to manage stock day average data. Key fields include: name, product_id, action_type, branch_id, company_id, users_ids, start_date, end_date, periode, cluster_id, is_itr_created, transfer_count, warehouse_line, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What fields does assembly.safety.stock.line have?

Response: The assembly.safety.stock.line model has 10 fields: stock_id, product_id, product_qty, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, float: 1, integer: 1, char: 1, datetime: 3.


How is report.equip3_accounting_reports.debt_collection implemented technically?

Response: The report.equip3_accounting_reports.debt_collection model is defined in module: equip3_accounting_reports. It has 0 computed fields: . Stored computed fields: none.


What modules define digest.tip?

Response: The digest.tip model is defined in module: digest. It has 0 computed fields: . Stored computed fields: none.


What data can be stored in lost.customer?

Response: The lost.customer model has 9 fields: name, top_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 3, integer: 1, datetime: 3.


List all fields in the website.published.mixin model.

Response: The website.published.mixin model has 7 fields: website_published, is_published, can_publish, website_url, id, display_name, __last_update. Field types distribution: boolean: 3, char: 2, integer: 1, datetime: 1.


What operations can I perform on project.tags?

Response: To use the project.tags model, you need to provide values for required fields: name. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


Show me the relational structure of account.invoice.exchange.approval.wizard.

Response: The account.invoice.exchange.approval.wizard model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


Show me the relational structure of ks.message.wizard.

Response: The ks.message.wizard model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


How is gamification.karma.tracking used in the system?

Response: The gamification.karma.tracking model represents Track Karma Changes in the ERP system. It contains 12 fields and is used to manage track karma changes data. Key fields include: user_id, old_value, new_value, consolidated, tracking_date, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Describe the implementation of account.tax.map.purchase.line.

Response: The account.tax.map.purchase.line model is defined in module: equip3_accounting_masterdata. It has 0 computed fields: . Stored computed fields: none.


Tell me about the assign.pr.wizard model.

Response: The assign.pr.wizard model represents Assign PR Wizard in the ERP system. It contains 9 fields and is used to manage assign pr wizard data. Key fields include: pr_ids, line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How does account.pettycash.voucher.wizard relate to other models?

Response: The account.pettycash.voucher.wizard model has 10 relational fields: fund -> account.pettycash; partner_id -> res.users; ba_ca_journal_id -> account.journal; submitter_id -> res.users; currency_id -> res.currency; company_id -> res.company; voucher_line -> account.pettycash.voucher.wizard.line; move_id -> account.move; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What fields does account.common.journal.report have?

Response: The account.common.journal.report model has 14 fields: amount_currency, journal_ids, date_from, date_to, target_move, report_currency_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 1, many2many: 1, date: 2, selection: 1, many2one: 4, integer: 1, char: 1, datetime: 3.


How to query purchase.detail.excel.extended data?

Response: To use the purchase.detail.excel.extended 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. The model supports standard CRUD operations through the ORM.


What data can be stored in account.journal.group?

Response: The account.journal.group model has 11 fields: name, company_id, excluded_journal_ids, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 3, many2many: 1, integer: 2, datetime: 3.


Show me the relational structure of report.equip3_accounting_reports.debt_collection.

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


How is mrp.workcenter.group used in the system?

Response: The mrp.workcenter.group model represents Work Center Group in the ERP system. It contains 28 fields and is used to manage work center group data. Key fields include: code, name, company_id, branch_id, workcenter_ids, is_branch_required, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Show me the fields of efaktur.export.

Response: The efaktur.export model has 13 fields: partner_id, tax_report_id, date_from, date_to, company_id, unduh, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, selection: 1, date: 2, binary: 1, integer: 1, char: 1, datetime: 3.


Tell me about the product.template.attribute.value model.

Response: The product.template.attribute.value model represents Product Template Attribute Value in the ERP system. It contains 20 fields and is used to manage product template attribute value data. Key fields include: ptav_active, name, product_attribute_value_id, attribute_line_id, price_extra, currency_id, exclude_for, product_tmpl_id, attribute_id, ptav_product_variant_ids, html_color, is_custom, display_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What foreign keys exist in account.reconcile.model.line?

Response: The account.reconcile.model.line model has 9 relational fields: model_id -> account.reconcile.model; company_id -> res.company; account_id -> account.account; journal_id -> account.journal; tax_ids -> account.tax; analytic_account_id -> account.analytic.account; analytic_tag_ids -> account.analytic.tag; create_uid -> res.users; write_uid -> res.users. Many2many fields: tax_ids, analytic_tag_ids.


Show me the relational structure of res.partner.type.

Response: The res.partner.type model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What foreign keys exist in mrp.production?

Response: The mrp.production model has 43 relational fields: product_id -> product.product; allowed_product_ids -> product.product; product_tmpl_id -> product.template; product_uom_id -> uom.uom; lot_producing_id -> stock.production.lot; product_uom_category_id -> uom.category; picking_type_id -> stock.picking.type; location_src_id -> stock.location; location_dest_id -> stock.location; bom_id -> mrp.bom; move_raw_ids -> stock.move; move_finished_ids -> stock.move; move_byproduct_ids -> stock.move; finished_move_line_ids -> stock.move.line; workorder_ids -> mrp.workorder; move_dest_ids -> stock.move; user_id -> res.users; company_id -> res.company; procurement_group_id -> procurement.group; orderpoint_id -> stock.warehouse.orderpoint; scrap_ids -> stock.scrap; production_location_id -> stock.location; picking_ids -> stock.picking; sh_mrp_quality_check_ids -> sh.mrp.quality.check; sh_mrp_quality_alert_ids -> sh.mrp.quality.alert; sh_mrp_pass_fail_ids -> sh.mrp.pass.fail; sh_mrp_pics_ids -> sh.mrp.pics; sh_mrp_measurement_ids -> sh.mrp.measurement; sh_mrp_qc_measurement_ids -> sh.mrp.qc.measurement; attachment_ids -> ir.attachment; sh_mrp_quality_point_id -> sh.qc.point; partner_id -> res.partner; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: allowed_product_ids, picking_ids, attachment_ids, message_partner_ids, message_channel_ids.


What operations can I perform on pos.promotion.gift.condition?

Response: To use the pos.promotion.gift.condition model, you need to provide values for required fields: product_id, minimum_quantity, promotion_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


What business logic is in mail.thread.phone?

Response: To use the mail.thread.phone model, you need to provide values for required fields: none. Readonly fields: phone_sanitized, phone_sanitized_blacklisted, phone_blacklisted, mobile_blacklisted, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.


What methods are available in mail.followers?

Response: The mail.followers model is defined in module: mail. It has 0 computed fields: . Stored computed fields: none.


Which fields in ir.ui.menu.category are computed?

Response: The ir.ui.menu.category model is defined in module: equip3_hashmicro_ui. It has 0 computed fields: . Stored computed fields: none.


Describe the field structure of approval.matrix.direct.purchase.

Response: The approval.matrix.direct.purchase model has 46 fields: name, company_id, branch_id, minimum_amt, maximum_amt, approval_matrix_direct_purchase_line_ids, is_good_services_order, order_type, 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. Field types distribution: char: 7, many2one: 10, float: 2, one2many: 5, boolean: 6, selection: 3, date: 2, many2many: 2, integer: 5, text: 1, datetime: 3.


How is return.reason used in the system?

Response: The return.reason model represents Return Reason in the ERP system. It contains 8 fields and is used to manage return reason data. Key fields include: name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How is pos.loyalty.category implemented technically?

Response: The pos.loyalty.category model is defined in module: equip3_pos_membership. It has 0 computed fields: . Stored computed fields: none.


What foreign keys exist in uom.conversion.history?

Response: The uom.conversion.history model has 10 relational fields: product_id -> product.product; location_id -> stock.location; prod_lot_id -> stock.production.lot; package_id -> stock.quant.package; partner_id -> res.partner; uom_id -> uom.uom; uom_conversion -> uom.uom; si_uom_id -> stock.inventory; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What is the service.work.order.checklist model?

Response: The service.work.order.checklist model represents Service Work Order Checklist in the ERP system. It contains 12 fields and is used to manage service work order checklist data. Key fields include: swo_id, name, desc, state, state2, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What are common use cases for base_import.tests.models.m2o.required.related?

Response: To use the base_import.tests.models.m2o.required.related 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. The model supports standard CRUD operations through the ORM.


Describe the many2many relations for generate.closing.entries.

Response: The generate.closing.entries model has 6 relational fields: fiscal_year_id -> sh.fiscal.year; journal_id -> account.journal; summary_account_id -> account.account; retained_earnings_account_id -> account.account; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What methods are available in product.template.attribute.line?

Response: The product.template.attribute.line model is defined in module: product. It has 0 computed fields: . Stored computed fields: none.


Describe the field structure of account.common.journal.report.

Response: The account.common.journal.report model has 14 fields: amount_currency, journal_ids, date_from, date_to, target_move, report_currency_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 1, many2many: 1, date: 2, selection: 1, many2one: 4, integer: 1, char: 1, datetime: 3.


Show me the fields of split.pr.line.wizard.

Response: The split.pr.line.wizard model has 14 fields: wizard_id, pr_line_id, name, user_id, new_user_id, product_id, product_qty, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 7, char: 2, float: 1, integer: 1, datetime: 3.


What are the technical details of untaken.stock?

Response: The untaken.stock model is defined in module: equip3_inventory_control. It has 0 computed fields: . Stored computed fields: none.


What does the product.brand model represent?

Response: The product.brand model represents Product Brand in the ERP system. It contains 42 fields and is used to manage product brand data. Key fields include: brand_name, short_name, product_count, active, campaign_id, source_id, medium_id, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, access_url, access_token, access_warning, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How is sh.commision.detail implemented technically?

Response: The sh.commision.detail model is defined in module: sh_sales_commission_target. It has 0 computed fields: . Stored computed fields: none.


Show me the relational structure of mail.thread.phone.

Response: The mail.thread.phone model has 6 relational fields: message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message. Many2many fields: message_partner_ids, message_channel_ids.


What methods are available in monthly.account.budget?

Response: The monthly.account.budget model is defined in module: equip3_accounting_budget. It has 0 computed fields: . Stored computed fields: none.


How do I use the product.supplierinfo model?

Response: To use the product.supplierinfo model, you need to provide values for required fields: name, min_qty, price, currency_id, product_tmpl_id, delay. Readonly fields: access_url, access_warning, product_uom, product_uom_category_id, product_variant_count, state1, state2, vendor_pricelist_approval_matrix, current_user, is_vendor_pricelist_approval_matrix, approval_matrix_line_id, is_approve_button, product_uom_old, edit_button_state, last_price, last_update_price, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


Describe the budget.purchase.wizard model in Odoo.

Response: The budget.purchase.wizard model represents Purchase Change Request Wizard in the ERP system. It contains 8 fields and is used to manage purchase change request wizard data. Key fields include: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Describe the implementation of credit.limit.approval.

Response: The credit.limit.approval model is defined in module: equip3_sale_other_operation. It has 0 computed fields: . Stored computed fields: none.


What are the available fields for purchase.excel.extended?

Response: The purchase.excel.extended model has 9 fields: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, char: 2, integer: 1, many2one: 2, datetime: 3.


Show me the fields of pos.config.

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


Describe the many2many relations for cancel.tender.memory.

Response: The cancel.tender.memory model has 3 relational fields: tender_id -> purchase.agreement; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What methods are available in purchase.request?

Response: The purchase.request model is defined in module: purchase_request. It has 0 computed fields: . Stored computed fields: none.


Can you explain the purpose of report.sh_sale_reports.sh_payment_report_doc?

Response: The report.sh_sale_reports.sh_payment_report_doc model represents payment report abstract model in the ERP system. It contains 3 fields and is used to manage payment report abstract model data. Key fields include: id, display_name, __last_update.


What are the available fields for res.users.identitycheck?

Response: The res.users.identitycheck model has 8 fields: password, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 1, many2one: 2, datetime: 3.


How do I use the approval.matrix.vendor.line model?

Response: To use the approval.matrix.vendor.line model, you need to provide values for required fields: user_ids, minimum_approver. Readonly fields: company_id, branch_id, sequence2, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


How does approval.matrix.accounting relate to other models?

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


What are common use cases for efaktur.export?

Response: To use the efaktur.export model, you need to provide values for required fields: none. Readonly fields: company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


How is ir.qweb.field.image used in the system?

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


List all fields in the base.import.module model.

Response: The base.import.module model has 11 fields: module_file, state, import_message, force, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, selection: 1, text: 1, boolean: 1, integer: 1, char: 1, many2one: 2, datetime: 3.


Show me the relational structure of coupon.coupon.

Response: The coupon.coupon model has 14 relational fields: partner_id -> res.partner; program_id -> coupon.program; discount_line_product_id -> product.product; order_id -> sale.order; sales_order_id -> sale.order; pos_order_id -> pos.order; redeem_history_ids -> pos.order.line; pos_create_uid -> res.users; pos_config_id -> pos.config; pos_orderline_id -> pos.order.line; purchase_id -> purchase.order; purchases_order_id -> purchase.order; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


Describe the field structure of purchase.detail.excel.extended.

Response: The purchase.detail.excel.extended model has 9 fields: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, char: 2, integer: 1, many2one: 2, datetime: 3.


Show me the fields of sh.tv.top.vendor.wizard.

Response: The sh.tv.top.vendor.wizard model has 17 fields: type, date_from, date_to, date_compare_from, date_compare_to, no_of_top_item, amount_total, currency_id, company_ids, branch_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: selection: 1, datetime: 7, integer: 2, monetary: 1, many2one: 3, many2many: 2, char: 1.


What does the mr.internal_transfer_line model represent?

Response: The mr.internal_transfer_line model represents mr.internal_transfer_line in the ERP system. It contains 22 fields and is used to manage mr.internal_transfer_line data. Key fields include: mr_id, no, product_id, description, uom_id, source_location, source_warehouse_id, current_qty, virtual_available, qty_transfer, mr_ir_wizard, mr_line_id, filter_warehouse_ids, filter_location_ids, dest_warehouse_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Show me the fields of budget.carry.over.lines.

Response: The budget.carry.over.lines model has 27 fields: budget_carry_over_id, date_from, date_to, analytic_account_id, paid_date, parent_analytic_account_id, general_budget_id, reserve_amount, currency_id, account_tag_ids, filtered_budget_line, company_id, practical_amount, theoritical_amount, planned_amount, practical_budget_amount, percentage, is_above_budget, carry_over_amount, final_planned_amount, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 8, date: 3, monetary: 7, many2many: 2, float: 1, boolean: 1, integer: 1, char: 1, datetime: 3.


Show me the relational structure of account.deposit.reconcile.

Response: The account.deposit.reconcile model has 3 relational fields: allocation_line_ids -> invoice.deposit.line.reconcile; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What business logic is in inter.transfer.company?

Response: To use the inter.transfer.company model, you need to provide values for required fields: none. Readonly fields: sale_count, invoice_count, bill_count, purchase_count, return_count, name, state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


What models are connected to purchase.report.representative.xls?

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


What does the asset.asset.report model represent?

Response: The asset.asset.report model represents Assets Analysis in the ERP system. It contains 21 fields and is used to manage assets analysis data. Key fields include: name, date, depreciation_date, asset_id, asset_category_id, partner_id, state, installment_value, move_check, installment_nbr, depreciation_nbr, gross_value, posted_value, unposted_value, company_id, depreciation_value, salvage_value, value_residual, id, display_name, __last_update.


How do I use the debt.collection.report model?

Response: To use the debt.collection.report model, you need to provide values for required fields: journal_ids, target_move, company_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


What operations can I perform on stock.track.line?

Response: To use the stock.track.line model, you need to provide values for required fields: none. Readonly fields: product_id, tracking, wizard_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


Can you explain the purpose of stock.return.move.line?

Response: The stock.return.move.line model represents Stock Return Move Line in the ERP system. It contains 12 fields and is used to manage stock return move line data. Key fields include: product_id, return_id, lot_id, qty, uom_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Show me the fields of purchase.agreement.legal.document.

Response: The purchase.agreement.legal.document model has 15 fields: legal_document_id, partner_id, nomor_induk_berusaha, salinan_anggaran_dasar, surat_persetujuan_dirjen_ahu, akta_perubahan_pengurus_terakhir, surat_keterangan_tidak_kena_pajak, surat_pernyataan_dan_kuasa, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, boolean: 6, integer: 1, char: 1, datetime: 3.


How to create records in approval.matrix.sale.order.lines?

Response: To use the approval.matrix.sale.order.lines model, you need to provide values for required fields: user_name_ids, sequence, minimum_approver. Readonly fields: sequence2, signature, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


Describe the export.retur.pajak.masukan model in Odoo.

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


What data can be stored in account.move.line?

Response: The account.move.line model has 140 fields: asset_category_id, asset_start_date, asset_end_date, asset_mrr, purchase_line_id, purchase_order_id, period_id, fiscal_year, is_anglo_saxon_line, product_type, is_landed_costs_line, discount_method, discount_type, discount_amount, discount_amt, branch_id, repair_line_ids, repair_fee_ids, is_down_payment, move_id, move_name, date, ref, parent_state, journal_id, company_id, company_currency_id, tax_fiscal_country_id, account_id, account_internal_type, account_internal_group, account_root_id, sequence, name, quantity, price_unit, discount, debit, credit, balance, cumulated_balance, amount_currency, price_subtotal, price_total, reconciled, blocked, date_maturity, currency_id, partner_id, product_uom_id, product_id, product_uom_category_id, reconcile_model_id, payment_id, statement_line_id, statement_id, tax_ids, tax_line_id, tax_group_id, tax_base_amount, tax_exigible, tax_repartition_line_id, tax_tag_ids, tax_audit, amount_residual, amount_residual_currency, full_reconcile_id, matched_debit_ids, matched_credit_ids, matching_number, analytic_line_ids, analytic_account_id, analytic_tag_ids, recompute_tax_line, display_type, is_rounding_line, exclude_from_invoice_tab, is_fiscal_book_exclude, price_tax_discount, is_update_disc_line, price_tax, unit_price_fnct, disc_percentage_rel, date_id, is_discount_line, is_interest_line, is_analytic_tags, total_qty_price_unit, multi_discount, is_intercompany_transaction, customer_deposit_id, vendor_deposit_id, tax_ids_ppn, price_total_ppn, amount_ppn, taxes_ppn, sale_line_ids, is_down_payment_discount, res_dp_amount, is_purchase_order, is_sales_order, sequence2, pos_branch_id, approval_code, check_reconcile, check_reconcile_done, check_reconcile_flag, check_payment, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 35, date: 7, float: 9, boolean: 26, selection: 9, one2many: 9, char: 11, integer: 7, monetary: 16, many2many: 7, html: 1, datetime: 3.


How does account.trial.balance relate to other models?

Response: The account.trial.balance model has 5 relational fields: journal_ids -> account.journal; report_currency_id -> res.currency; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: journal_ids.


How do I use the x.report.wizard model?

Response: To use the x.report.wizard model, you need to provide values for required fields: pos_session_ids. Readonly fields: report_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


What does the uom.uom model represent?

Response: The uom.uom model represents Product Unit of Measure in the ERP system. It contains 19 fields and is used to manage product unit of measure data. Key fields include: name, category_id, factor, factor_inv, rounding, active, uom_type, timesheet_widget, is_pos_groupable, is_custom_uom, product_ratio_line, is_external_link, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Describe the field structure of board.board.

Response: The board.board model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.


What are the relationships in pos.order.location?

Response: The pos.order.location model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


Describe the account.ebupot model in Odoo.

Response: The account.ebupot model represents Account E-Bupot in the ERP system. It contains 18 fields and is used to manage account e-bupot data. Key fields include: year, name, is_used, invoice_ids, tax_report_id, date_from, date_to, partner_id, company_id, ebupot_template, tahun_pajak, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Describe the many2many relations for inter.transfer.company.

Response: The inter.transfer.company model has 11 relational fields: sale_id -> sale.order; invoice_id -> account.move; purchase_id -> purchase.order; return_id -> return.inter.transfer.company; from_warehouse -> stock.warehouse; currency_id -> res.currency; to_warehouse -> stock.warehouse; pricelist_id -> product.pricelist; product_lines -> inter.transfer.company.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: invoice_id.


What modules define project.task.type.delete.wizard?

Response: The project.task.type.delete.wizard model is defined in module: project. It has 0 computed fields: . Stored computed fields: none.


How to query stock.immediate.transfer data?

Response: To use the stock.immediate.transfer 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. The model supports standard CRUD operations through the ORM.


Show me the relational structure of mrp.bom.line.

Response: The mrp.bom.line model has 19 relational fields: product_tmpl_id -> product.template; company_id -> res.company; product_uom_category_id -> uom.category; bom_id -> mrp.bom; parent_product_tmpl_id -> product.template; possible_bom_product_template_attribute_value_ids -> product.template.attribute.value; bom_product_template_attribute_value_ids -> product.template.attribute.value; allowed_operation_ids -> mrp.routing.workcenter; operation_id -> mrp.routing.workcenter; child_bom_id -> mrp.bom; child_line_ids -> mrp.bom.line; branch_id -> res.branch; product_id -> product.product; alternative_component_ids -> product.product; operation_two_ids -> mrp.bom.operation; operation_two_id -> mrp.bom.operation; product_uom_id -> uom.uom; create_uid -> res.users; write_uid -> res.users. Many2many fields: possible_bom_product_template_attribute_value_ids, bom_product_template_attribute_value_ids, allowed_operation_ids, alternative_component_ids, operation_two_ids.


How is picking.return.line used in the system?

Response: The picking.return.line model represents picking.return.line in the ERP system. It contains 14 fields and is used to manage picking.return.line data. Key fields include: name, product_id, picking_id, purchase_id, sale_id, currency_id, price, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Show me the fields of sh.tsp.top.purchasing.product.

Response: The sh.tsp.top.purchasing.product model has 9 fields: product_id, qty, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, float: 1, integer: 1, char: 1, datetime: 3.


What does the product.expire.report model represent?

Response: The product.expire.report model represents product.expire.report in the ERP system. It contains 8 fields and is used to manage product.expire.report data. Key fields include: report_selection, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Tell me about the ai.data.cleanup model.

Response: The ai.data.cleanup model represents AI Data Cleanup Scheduler in the ERP system. It contains 23 fields and is used to manage ai data cleanup scheduler data. Key fields include: name, active, cleanup_interval_days, last_run, next_run, cleanup_old_sessions, session_age_days, cleanup_few_message_sessions, few_message_session_age_days, cleanup_orphaned_messages, cleanup_uploaded_attachments, uploaded_attachments_age_days, cleanup_old_generated_files, generated_files_age_days, cleanup_old_sandbox_folders, sandbox_folders_age_days, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What foreign keys exist in sh.mrp.qc.alert.line?

Response: The sh.mrp.qc.alert.line model has 5 relational fields: alert_id -> sh.mrp.qc.alert; product_id -> product.product; partner_id -> res.partner; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What business logic is 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. The model supports standard CRUD operations through the ORM.


What are the technical details of sh.stock.move.pics?

Response: The sh.stock.move.pics model is defined in module: sh_inventory_mrp_qc. It has 0 computed fields: . Stored computed fields: none.


How is ir.model.constraint implemented technically?

Response: The ir.model.constraint model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.


What methods are available in sh.purchase.bill.summary.wizard?

Response: The sh.purchase.bill.summary.wizard model is defined in module: sh_purchase_reports. It has 0 computed fields: . Stored computed fields: none.


How to create records in pos.payment.wizard?

Response: To use the pos.payment.wizard model, you need to provide values for required fields: start_dt, end_dt. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


Which fields in warehouse.capacity.excel.report are computed?

Response: The warehouse.capacity.excel.report model is defined in module: equip3_inventory_reports. It has 0 computed fields: . Stored computed fields: none.


What models are connected to pos.gift.card.type?

Response: The pos.gift.card.type model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


How is product.ratio.line implemented technically?

Response: The product.ratio.line model is defined in module: equip3_inventory_masterdata. It has 0 computed fields: . Stored computed fields: none.


What operations can I perform on mrp.bom.tools?

Response: To use the mrp.bom.tools model, you need to provide values for required fields: bom_id, product_id, quantity, uom_id. Readonly fields: company_id, workorder_id, allowed_operation_ids, operation_two_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


What operations can I perform on acrux.chat.select.conversation.wizard?

Response: To use the acrux.chat.select.conversation.wizard model, you need to provide values for required fields: conversation_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


Show me the relational structure of pos.promotion.multi.buy.

Response: The pos.promotion.multi.buy model has 4 relational fields: product_ids -> product.product; promotion_id -> pos.promotion; create_uid -> res.users; write_uid -> res.users. Many2many fields: product_ids.


What models are connected to blacklist.partner.wiz?

Response: The blacklist.partner.wiz model has 4 relational fields: partner_id -> res.partner; user_id -> res.users; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


Show me the fields of accounting.report.

Response: The accounting.report model has 20 fields: enable_filter, account_report_id, label_filter, filter_cmp, date_from_cmp, date_to_cmp, debit_credit, journal_ids, date_from, date_to, target_move, report_currency_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 2, many2one: 5, char: 2, selection: 2, date: 4, many2many: 1, integer: 1, datetime: 3.


What methods are available in account.common.journal.report?

Response: The account.common.journal.report model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.


How is approval.matrix.direct.purchase.line implemented technically?

Response: The approval.matrix.direct.purchase.line model is defined in module: equip3_purchase_other_operation_cont. It has 0 computed fields: . Stored computed fields: none.


Show me the relational structure of format.address.mixin.

Response: The format.address.mixin model has no explicit relational fields defined in its field metadata.


Can you explain the purpose of vendor.evaluation.rating?

Response: The vendor.evaluation.rating model represents vendor.evaluation.rating in the ERP system. It contains 9 fields and is used to manage vendor.evaluation.rating data. Key fields include: partner_id, fulfillment_avg, on_time_rate_avg, final_point_avg, vendor_evaluation_count, branch_id, id, display_name, __last_update.


What are the available fields for sale.order.alternative.product?

Response: The sale.order.alternative.product model has 11 fields: alter_product_ids, product_id, sale_line_id, selected_product_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2many: 1, many2one: 5, integer: 1, char: 1, datetime: 3.


Describe the field structure of all.loyalty.history.

Response: The all.loyalty.history model has 19 fields: order_id, pos_order_id, partner_id, date, generated_from, transaction_type, points, amount, currency_id, company_id, check_state, state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 7, datetime: 4, selection: 3, integer: 2, char: 2, boolean: 1.


What models are connected to sh.purchase.tags?

Response: The sh.purchase.tags model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What fields does stock.move have?

Response: The stock.move model has 237 fields: name, sequence, priority, create_date, date, date_deadline, company_id, description_picking, product_qty, product_uom_qty, product_uom, product_uom_category_id, product_tmpl_id, location_id, location_dest_id, partner_id, move_dest_ids, move_orig_ids, picking_partner_id, note, state, price_unit, backorder_id, origin, procure_method, scrapped, scrap_ids, group_id, rule_id, propagate_cancel, delay_alert_date, picking_type_id, inventory_id, move_line_ids, move_line_nosuggest_ids, origin_returned_move_id, returned_move_ids, availability, restrict_partner_id, route_ids, warehouse_id, has_tracking, show_operations, show_details_visible, show_reserved_availability, additional, is_locked, is_initial_demand_editable, is_quantity_done_editable, reference, has_move_lines, package_level_id, picking_type_entire_packs, display_assign_serial, next_serial_count, orderpoint_id, forecast_availability, forecast_expected_date, lot_ids, created_production_id, production_id, raw_material_production_id, unbuild_id, consume_unbuild_id, allowed_operation_ids, operation_id, workorder_id, bom_line_id, byproduct_id, unit_factor, is_done, order_finished_lot_ids, should_consume_qty, use_expiration_date, to_refund, account_move_ids, stock_valuation_layer_ids, is_reconstruct_svl, scrap_return_move_id, purchase_line_id, created_purchase_line_id, sh_quality_point, sh_quality_point_id, sh_last_qc_date, sh_last_qc_state, number_of_test, created_purchase_request_line_id, purchase_request_allocation_ids, purchase_request_ids, requisition_line_ids, sale_line_id, branch_id, weight, product_description, qty_pack, is_pack, repair_id, sh_stock_move_barcode_mobile, sh_stock_move_bm_is_cont_scan, length, width, height, product_id, is_adjustable_picking, package_measure_selection, picking_state, is_existing_package, move_package_id, filter_move_package_ids, mr_line_id, move_line_sequence, serial_no, export_file, export_name, next_serial, next_serial_not_autogenerate, next_lot_not_autogenerate, is_import, is_record_confirm, product_type, is_serial_number, next_lot, qty_per_lot, is_autogenerate, picking_code, is_product_service_operation, is_product_service_operation_delivery, is_product_service_operation_receiving, serial, initial_demand, move_progress, analytic_account_group_ids, remaining, fulfillment, current_qty, scheduled_date, responsible, late_time, late_time_hours, process_status, process_time, process_time_hours, package_type, qty_in_pack, packaging_ids, package_quant_ids, measure_ids, product_id_domain, source_picking_id, source_move_id, is_batch_shipping_packing, is_batch_shipping_delivery, created_assembly_id, assembly_finished_id, assembly_component_id, assembly_unit_factor, assembly_should_consume_qty, assembly_product_free_qty, description, created_kitchen_id, kitchen_finished_id, kitchen_component_id, kitchen_unit_factor, kitchen_should_consume_qty, kitchen_product_free_qty, asp_asm_stock_id, bom_product_uom_qty, sub_total, finish_good_rework_id, type_product_bom, finish_good_rework_finished_id, finish_good_rework_created_kitchen_id, finish_good_rework_by_product_id, assembly_record_type, assembly_confirm_date, assembly_product_id, assembly_bom_id, assembly_svl_value, assembly_difference, exp_date, qty_bundle, id_bundle, package_barcode, kitchen_confirm_date, kitchen_product_id, kitchen_bom_id, kitchen_svl_value, kitchen_difference, product_warehouse, product_location, expired_date, product_barcode, vendor_id, state_expired, state_check, picking_type_code, reserved_by_id, reserved_availability, is_reserved, picking_id, origin_src_location, origin_dest_location, picking_reference, is_transit, date_done, return_reason, action, is_transfer_in, is_transfer_out, quantity_done, volume, movement_type, cost, combo_item_id, pos_branch_id, pos_order_line_id, so_antar_badan, po_antar_badan, sale_order_id, purchase_order_id, date_done_real, taxes_id, price_subtotal, price_tax, price_total, price_untaxed_amount, discount_amount, price_discount, currency_id, returned_qty, remaining_checked_qty, id, display_name, create_uid, write_uid, write_date, __last_update. Field types distribution: char: 23, integer: 10, selection: 17, datetime: 14, many2one: 71, text: 2, float: 39, many2many: 12, boolean: 34, one2many: 9, binary: 1, date: 1, monetary: 4.


What data can be stored in kitchen.production.record?

Response: The kitchen.production.record model has 79 fields: name, company_id, is_branch_required, product_id, product_tmpl_id, product_qty, rejected_qty, product_uom_id, product_uom_category_id, bom_id, branch_id, confirm_date, state, move_raw_ids, move_finished_ids, move_byproduct_ids, location_src_id, location_dest_id, picking_type_id, date_planned_start, date_planned_finished, date_deadline, procurement_group_id, move_dest_ids, production_location_id, warehouse_id, product_tracking, account_move_ids, purchase_request_ids, internal_transfer_count, expiry_days, product_use_expiration_date, finished_lot_ids, byproduct_lot_ids, rejected_lot_ids, show_submit_button, is_autogenerate, default_finished_lot_qty, default_rejected_lot_qty, show_byproduct_lot_tab, byproduct_manual_product_ids, default_byproduct_lot_qty, default_next_byproduct_product_id, any_byproduct_is_autogenerate, all_byproduct_is_autogenerate, component_consumed_qty, svl_value, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 5, many2one: 19, boolean: 12, float: 6, datetime: 7, selection: 4, one2many: 13, integer: 7, many2many: 3, text: 1, date: 2.


Describe the many2many relations for crm.phonecall.

Response: The crm.phonecall model has 17 relational fields: team_id -> crm.team; user_id -> res.users; partner_id -> res.partner; company_id -> res.company; tag_ids -> crm.tag; opportunity_id -> crm.lead; campaign_id -> utm.campaign; source_id -> utm.source; medium_id -> utm.medium; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: tag_ids, message_partner_ids, message_channel_ids.


Describe the account.group model in Odoo.

Response: The account.group model represents Account Group in the ERP system. It contains 13 fields and is used to manage account group data. Key fields include: parent_id, parent_path, code_prefix_start, code_prefix_end, company_id, name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How do I use the pos.payment.edc model?

Response: To use the pos.payment.edc model, you need to provide values for required fields: none. Readonly fields: pos_branch_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


Can you explain the purpose of res.users.tag?

Response: The res.users.tag model represents User Tag in the ERP system. It contains 8 fields and is used to manage user tag data. Key fields include: name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What are the relationships in product.pricelist.change?

Response: The product.pricelist.change model has 4 relational fields: pricelist_id -> product.pricelist; currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


How does account.invoice.exchange.approval.wizard relate to other models?

Response: The account.invoice.exchange.approval.wizard model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What is the dynamic.balance.sheet.report model?

Response: The dynamic.balance.sheet.report model represents Balance Sheet Report in the ERP system. It contains 17 fields and is used to manage balance sheet report data. Key fields include: company_id, journal_ids, account_ids, account_tag_ids, analytic_ids, analytic_tag_ids, display_account, target_move, date_from, date_to, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Describe the close.fiscal.year model in Odoo.

Response: The close.fiscal.year model represents Close Fiscal Year in the ERP system. It contains 8 fields and is used to manage close fiscal year data. Key fields include: fiscal_year_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What fields does product.template.attribute.exclusion have?

Response: The product.template.attribute.exclusion model has 10 fields: product_template_attribute_value_id, product_tmpl_id, value_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, many2many: 1, integer: 1, char: 1, datetime: 3.


How to create records in bus.bus?

Response: To use the bus.bus model, you need to provide values for required fields: none. Readonly fields: channel, message, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


List all fields in the account.resequence.wizard model.

Response: The account.resequence.wizard model has 15 fields: sequence_number_reset, first_date, end_date, first_name, ordering, move_ids, new_values, preview_moves, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, date: 2, selection: 1, many2many: 1, text: 2, integer: 1, many2one: 2, datetime: 3.


What are common use cases for setu.inventory.overstock.bi.report?

Response: To use the setu.inventory.overstock.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. The model supports standard CRUD operations through the ORM.


Can you explain the purpose of im_livechat.channel?

Response: The im_livechat.channel model represents Livechat Channel in the ERP system. It contains 30 fields and is used to manage livechat channel data. Key fields include: name, button_text, default_message, input_placeholder, header_background_color, title_color, button_background_color, button_text_color, web_page, are_you_inside, script_external, nbr_channel, image_128, user_ids, channel_ids, rule_ids, website_published, is_published, can_publish, website_url, website_description, rating_ids, rating_percentage_satisfaction, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Describe the ir.http model in Odoo.

Response: The ir.http model represents HTTP Routing in the ERP system. It contains 3 fields and is used to manage http routing data. Key fields include: id, display_name, __last_update.