What does the sale.adv.wizard.product.line model represent?

Response: The sale.adv.wizard.product.line model represents Sale Multi Product Selection Advanced Wizard Product Line in the ERP system. It contains 13 fields and is used to manage sale multi product selection advanced wizard product line data. Key fields include: sale_adv_wizard_id, product_id, default_code, standard_price, uom_po_id, qty, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How is limit.request implemented technically?

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


Show me the fields of account.petty.cash.report.

Response: The account.petty.cash.report model has 16 fields: name, custodian_id, main_cash_account_id, journal_id, amount, balance, virtual_balance, company_id, branch_id, effective_date, create_uid, create_date, expense_amount, id, display_name, __last_update. Field types distribution: char: 2, many2one: 6, float: 4, date: 1, datetime: 2, integer: 1.


What are the technical details of report.sale.report_saleproforma?

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


How do I use the report.sh_sale_reports.sh_top_selling_product_doc model?

Response: To use the report.sh_sale_reports.sh_top_selling_product_doc 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 methods are available in account.unreconcile?

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


Show me the relational structure of auditlog.http.request.

Response: The auditlog.http.request model has 5 relational fields: user_id -> res.users; http_session_id -> auditlog.http.session; log_ids -> auditlog.log; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


How does sale.adv.wizard relate to other models?

Response: The sale.adv.wizard model has 5 relational fields: product_ids -> sale.adv.wizard.product.line; product_attr_ids -> product.attribute.value; specific_product_ids -> sale.adv.wizard.product.line.specific; create_uid -> res.users; write_uid -> res.users. Many2many fields: product_attr_ids.


Describe the gamification.karma.tracking model in Odoo.

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.


What does the res.partner.category model represent?

Response: The res.partner.category model represents Partner Tags in the ERP system. It contains 14 fields and is used to manage partner tags data. Key fields include: name, color, parent_id, child_ids, active, parent_path, partner_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Describe the field structure of purchase.team.analysis.

Response: The purchase.team.analysis model has 20 fields: days_to_approve, purchase_order_duration_to_confirm, amount_saved_from_cost_savings, number_of_successful_cost_savings, avg_amount_saved_from_cost_savings, avg_number_of_successful_cost_savings, user_id, purchase_ids, kpi_target, cost_saving_percentage, amount_purchased, cost_saving, branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: float: 10, many2one: 4, many2many: 1, integer: 1, char: 1, datetime: 3.


What fields does link.tracker.click have?

Response: The link.tracker.click model has 13 fields: campaign_id, link_id, ip, country_id, mailing_trace_id, mass_mailing_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 7, char: 2, integer: 1, datetime: 3.


How to create records in project.create.invoice?

Response: To use the project.create.invoice model, you need to provide values for required fields: project_id, sale_order_id. Readonly fields: _candidate_orders, amount_to_invoice, currency_id, 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 pos.order.line.promotion?

Response: The pos.order.line.promotion model has 4 relational fields: pos_order_line_id -> pos.order.line; promotion_id -> pos.promotion; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What is the inter.transfer.company.line model?

Response: The inter.transfer.company.line model represents inter.transfer.company.line in the ERP system. It contains 11 fields and is used to manage inter.transfer.company.line data. Key fields include: internal_id, product_id, quantity, price_unit, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What methods are available in account.ebupot?

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


How is report.equip3_inventory_reports.expiring_product_calendar used in the system?

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


What models are connected to picking.order.line?

Response: The picking.order.line model has 4 relational fields: picking_order_id -> picking.order; product_id -> product.product; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What operations can I perform on sms.template.preview?

Response: To use the sms.template.preview model, you need to provide values for required fields: sms_template_id. Readonly fields: model_id, body, no_record, 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 pos.promotion.discount.order model.

Response: The pos.promotion.discount.order model represents Promotion each total order in the ERP system. It contains 15 fields and is used to manage promotion each total order data. Key fields include: active, minimum_amount, discount, discount2, multi_discount, max_discount_amount, discount_fixed_amount, promotion_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What business logic is in account.deposit.reconcile?

Response: To use the account.deposit.reconcile 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 opening.balance.line?

Response: The opening.balance.line model represents opening.balance.line in the ERP system. It contains 15 fields and is used to manage opening.balance.line data. Key fields include: move_id, company_id, account_id, partner_id, company_currency_id, debit, credit, date_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Show me the relational structure of kpi.measure.

Response: The kpi.measure model has 7 relational fields: model_id -> ir.model; date_field_ids -> ir.model.fields; measure_field_id -> ir.model.fields; company_field_id -> ir.model.fields; item_ids -> kpi.measure.item; create_uid -> res.users; write_uid -> res.users. Many2many fields: date_field_ids.


What is the project.task.type model?

Response: The project.task.type model represents Task Stage in the ERP system. It contains 21 fields and is used to manage task stage data. Key fields include: active, name, description, sequence, project_ids, legend_blocked, legend_done, legend_normal, mail_template_id, fold, rating_template_id, auto_validation_kanban_state, is_closed, disabled_rating_warning, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How to query purchase.request.allocation data?

Response: To use the purchase.request.allocation model, you need to provide values for required fields: purchase_request_line_id, product_uom_id. Readonly fields: company_id, product_id, product_uom_id, open_product_qty, purchase_state, 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 pos.loyalty.history.update.point?

Response: The pos.loyalty.history.update.point model represents POS Loyalty History Update Point in the ERP system. It contains 12 fields and is used to manage pos loyalty history update point data. Key fields include: type_apply, total_orders, total_point, pos_order_ids, parent_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How does setu.inventory.outofstock.bi.report relate to other models?

Response: The setu.inventory.outofstock.bi.report model has 7 relational fields: product_id -> product.product; product_category_id -> product.category; warehouse_id -> stock.warehouse; company_id -> res.company; wizard_id -> setu.inventory.outofstock.report; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What is the pos.voucher.report model?

Response: The pos.voucher.report model represents POS Voucher Report in the ERP system. It contains 14 fields and is used to manage pos voucher report data. Key fields include: name, used_date, number, code, pos_order_id, config_id, session_id, apply_type, amount, pos_branch_id, company_id, id, display_name, __last_update.


How does sh.purchase.product.profit.xls relate to other models?

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


How do I use the rfm.yearly.analysis.by.segment model?

Response: To use the rfm.yearly.analysis.by.segment 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.


List all fields in the mail.activity model.

Response: The mail.activity model has 31 fields: res_model_id, res_model, res_id, res_name, activity_type_id, activity_category, activity_decoration, icon, summary, note, date_deadline, automated, user_id, request_partner_id, state, recommended_activity_type_id, previous_activity_type_id, has_recommended_activities, mail_template_ids, force_next, can_write, calendar_event_id, attachment_ids, is_attachment_required, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 9, char: 5, many2one_reference: 1, selection: 3, html: 1, date: 1, boolean: 5, many2many: 2, integer: 1, datetime: 3.


What modules define queue.job.dashboard?

Response: The queue.job.dashboard model is defined in module: queue_job. It has 0 computed fields: . Stored computed fields: none.


What does the account.cashbox.wizard model represent?

Response: The account.cashbox.wizard model represents account.cashbox.wizard in the ERP system. It contains 14 fields and is used to manage account.cashbox.wizard data. Key fields include: pos_session_id, line_ids, amount_total, is_closing_wizard, is_validate, is_return, line_bank_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What fields does customer.deposit.report have?

Response: The customer.deposit.report model has 16 fields: name, partner_id, amount, currency_id, remaining_amount, communication, move_id, return_deposit, payment_date, deposit_reconcile_journal_id, journal_id, deposit_account_id, used_amount, id, display_name, __last_update. Field types distribution: char: 3, many2one: 7, monetary: 3, date: 1, integer: 1, datetime: 1.


How is dev.credit.note.wizard implemented technically?

Response: The dev.credit.note.wizard model is defined in module: dev_rma. It has 0 computed fields: . Stored computed fields: none.


Describe the many2many relations for stock.inventory.line.

Response: The stock.inventory.line model has 21 relational fields: inventory_id -> stock.inventory; partner_id -> res.partner; product_id -> product.product; product_uom_id -> uom.uom; categ_id -> product.category; package_id -> stock.quant.package; prod_lot_id -> stock.production.lot; company_id -> res.company; location_id -> stock.location; adjustment_account_id -> account.account; filtered_adjustment_account_id -> account.account; analytic_tag_ids -> account.analytic.tag; uom_id -> uom.uom; category_uom_id -> uom.category; wizard_id -> stock.inventory.wizard; currency_id -> res.currency; user_id_1 -> res.users; user_id_2 -> res.users; current_user_id -> res.users; create_uid -> res.users; write_uid -> res.users. Many2many fields: filtered_adjustment_account_id, analytic_tag_ids.


Which fields in account.equity.move are computed?

Response: The account.equity.move model is defined in module: equip3_accounting_reports. It has 0 computed fields: . Stored computed fields: none.


Describe the implementation of queue.job.channel.

Response: The queue.job.channel model is defined in module: queue_job. It has 0 computed fields: . Stored computed fields: none.


Describe the implementation of target.kpi.

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


What are the technical details of sale.adv.wizard.product.line.specific?

Response: The sale.adv.wizard.product.line.specific model is defined in module: equip3_sale_operation. It has 0 computed fields: . Stored computed fields: none.


What are common use cases for rating.mixin?

Response: To use the rating.mixin model, you need to provide values for required fields: none. Readonly fields: rating_ids, rating_last_value, rating_last_feedback, rating_last_image, rating_count, rating_avg, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.


What modules define report.sh_sale_reports.sh_salesperson_report_doc?

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


What is the ks.parameter.tuning.wizard model?

Response: The ks.parameter.tuning.wizard model represents Parameter Tuner in the ERP system. It contains 21 fields and is used to manage parameter tuner data. Key fields include: ks_forecast, ks_forecast_method, min_p, max_p, min_d, max_d, min_q, max_q, min_sp, max_sp, min_sd, max_sd, min_sq, max_sq, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What are the relationships in approval.matrix.accounting.lines?

Response: The approval.matrix.accounting.lines model has 18 relational fields: user_ids -> res.users; approval_matrix_id -> approval.matrix.accounting; approved_users -> res.users; last_approved -> res.users; move_id -> account.move; receipt_id -> account.payment; multi_receipt_id -> account.multipayment; voucher_id -> account.voucher; payment_voc_id -> payment.voucher; acc_internal_transfer_id -> account.internal.transfer; account_budget_request_id -> budget.change.req; account_budget_id -> crossovered.budget; budget_purchase_id -> budget.purchase; account_budget_req_id -> purchase.change.request; customer_deposit_id -> customer.deposit; acc_vendor_deposit_id -> vendor.deposit; create_uid -> res.users; write_uid -> res.users. Many2many fields: user_ids, approved_users.


How is purchase.down.payment implemented technically?

Response: The purchase.down.payment model is defined in module: dev_purchase_down_payment. It has 0 computed fields: . Stored computed fields: none.


What foreign keys exist in budget.budget?

Response: The budget.budget model has 12 relational fields: parent_id -> budget.budget; user_id -> res.users; budget_budget_line -> budget.budget.budget.line; company_id -> res.company; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: message_partner_ids, message_channel_ids.


List all fields in the force.done.memory model.

Response: The force.done.memory model has 11 fields: blanket_id, qty, remaining_qty, reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, float: 2, text: 1, integer: 1, char: 1, datetime: 3.


Can you explain the purpose of sh.purchase.bill.summary.wizard?

Response: The sh.purchase.bill.summary.wizard model represents Purchase Bill Summary Wizard in the ERP system. It contains 13 fields and is used to manage purchase bill summary wizard data. Key fields include: sh_start_date, sh_end_date, sh_partner_ids, sh_status, company_ids, branch_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What modules define stock.location.tag?

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


List all fields in the setu.inventory.fsn.analysis.bi.report model.

Response: The setu.inventory.fsn.analysis.bi.report model has 18 fields: product_id, product_category_id, warehouse_id, company_id, opening_stock, closing_stock, average_stock, sales, turnover_ratio, stock_movement, wizard_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 7, float: 5, char: 2, integer: 1, datetime: 3.


Describe the wizard.vendor.deposit model in Odoo.

Response: The wizard.vendor.deposit model represents Wizard Vendor Deposit in the ERP system. It contains 9 fields and is used to manage wizard vendor deposit data. Key fields include: reason, add_amount, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What data can be stored in pos.cashier.change.wizard?

Response: The pos.cashier.change.wizard model has 10 fields: start_datetime, end_datetime, pos_branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: datetime: 5, many2one: 3, integer: 1, char: 1.


What are common use cases for ks_dashboard_ninja.child_board?

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


How is report.project.task.user used in the system?

Response: The report.project.task.user model represents Tasks Analysis in the ERP system. It contains 23 fields and is used to manage tasks analysis data. Key fields include: name, user_id, date_assign, date_end, date_deadline, date_last_stage_update, project_id, working_days_close, working_days_open, delay_endings_days, nbr, priority, state, company_id, partner_id, stage_id, hours_planned, hours_effective, remaining_hours, progress, id, display_name, __last_update.


How do I use the restaurant.floor model?

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.


List all fields in the base_import.tests.models.char model.

Response: The base_import.tests.models.char model has 8 fields: value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 1, many2one: 2, datetime: 3.


Describe the many2many relations for pmps.adv.wizard.product.line.specific.

Response: The pmps.adv.wizard.product.line.specific model has 5 relational fields: pmps_adv_wizard_id_specific -> pmps.adv.wizard; product_id -> product.product; uom_po_id -> uom.uom; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.