How do I use the internal.transfer model?

Response: To use the internal.transfer model, you need to provide values for required fields: requested_by, scheduled_date. Readonly fields: name, source_document, state1, state2, state3, operation_type_in_id, operation_type_out_id, operation_count, internal_transfer_line_total, itr_approval_matrix_id, is_itr_approval_matrix, approved_matrix_ids, approval_matrix_line_id, is_approve_button, is_reset_to_draft, is_product_lines, company_id, filter_source_warehouse_id, filter_destination_warehouse_id, get_warehouse, is_mbs_on_transfer_operations, branch_id, domain_warehouse_source_id, domain_warehouse_destination_id, sh_it_bm_is_cont_scan, source_location_id, destination_location_id, create_date, 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, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


What business logic is in order.picking?

Response: To use the order.picking 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.


List all fields in the acrux.chat.message.wizard model.

Response: The acrux.chat.message.wizard model has 20 fields: text, partner_id, conversation_id, connector_id, sale_id, message_mass_id, phone, is_crm, opportunity_id, whatsapp_template_id, crm_message_mass_id, mobile, attachment_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 1, many2one: 10, char: 3, boolean: 1, many2many: 1, integer: 1, datetime: 3.


What are the available fields for vendor.payment.request?

Response: The vendor.payment.request model has 16 fields: name, user_id, description, company_id, branch_id, component_line_id, state, amount_total, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, many2one: 6, one2many: 1, selection: 1, float: 1, integer: 1, datetime: 3.


What modules define rma.report?

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


How does inter.transfer.company.line relate to other models?

Response: The inter.transfer.company.line model has 4 relational fields: internal_id -> inter.transfer.company; product_id -> product.product; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What models are connected to phone.blacklist.remove?

Response: The phone.blacklist.remove model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


Describe the field structure of report_excel_import_wizard.

Response: The report_excel_import_wizard model has 8 fields: data, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, integer: 1, char: 1, many2one: 2, datetime: 3.


What business logic is in replenishment.history.wizard?

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


List all fields in the stock.return.picking.inter.company model.

Response: The stock.return.picking.inter.company model has 12 fields: product_id, quantity, uom_id, wizard_id, move_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 6, float: 1, integer: 1, char: 1, datetime: 3.


Can you explain the purpose of hide.chatter?

Response: The hide.chatter model represents Chatter Rights in the ERP system. It contains 13 fields and is used to manage chatter rights data. Key fields include: access_management_id, model_id, hide_chatter, hide_send_mail, hide_log_notes, hide_schedule_activity, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Show me the relational structure of mrp.bom.

Response: The mrp.bom model has 22 relational fields: bom_line_ids -> mrp.bom.line; byproduct_ids -> mrp.bom.byproduct; product_uom_category_id -> uom.category; operation_ids -> mrp.routing.workcenter; picking_type_id -> stock.picking.type; product_id -> product.product; company_id -> res.company; product_uom_id -> uom.uom; branch_id -> res.branch; create_uid -> res.users; tool_ids -> mrp.bom.tools; operation_two_ids -> mrp.bom.operation; product_tmpl_id -> product.template; product_tmpl_ids -> product.template; product_ids -> product.product; 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: operation_two_ids, product_tmpl_ids, product_ids, message_partner_ids, message_channel_ids.


List all fields in the calendar.event model.

Response: The calendar.event model has 99 fields: name, attendee_status, display_time, start, stop, allday, start_date, stop_date, duration, description, privacy, location, show_as, res_id, res_model_id, res_model, activity_ids, message_ids, user_id, partner_id, active, categ_ids, attendee_ids, partner_ids, alarm_ids, is_highlighted, recurrency, recurrence_id, follow_recurrence, recurrence_update, rrule, rrule_type, event_tz, end_type, interval, count, mo, tu, we, th, fr, sa, su, month_by, day, weekday, byday, until, opportunity_id, phonecall_id, sign_in_location, sign_out_location, sign_in_date, sign_out_date, sign_in, sign_out, note_field, team_id, state, state_1, state_2, cancel_reason, opportunity_name, res_name, res_loc, meeting_salesperson_ids, is_hide_salesperson, dummy_boolean, user_ids, mandatory, partner_attendees_ids, reasons_reschedule, cancelled_reasons, meeting_overview, stage_id, meeting_count, quotation, final_quotation, message_is_follower, message_follower_ids, 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_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: 13, selection: 14, datetime: 7, boolean: 22, date: 3, float: 1, text: 2, integer: 11, many2one: 12, one2many: 5, many2many: 8, html: 1.


How to query hr.plan.activity.type data?

Response: To use the hr.plan.activity.type model, you need to provide values for required fields: responsible. 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 methods are available in account.pettycash.fund.change?

Response: The account.pettycash.fund.change model is defined in module: equip3_accounting_pettycash. It has 0 computed fields: . Stored computed fields: none.


Show me the relational structure of queue.job.channel.

Response: The queue.job.channel model has 4 relational fields: parent_id -> queue.job.channel; job_function_ids -> queue.job.function; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What fields does account.internal.transfer have?

Response: The account.internal.transfer model has 68 fields: request_partner_id, bank_from_journal_id, bank_to_journal_id, transfer_in_transit, account_in_transit, transfer_desc, transfer_amount, currency_id, transfer_date, create_date, create_uid, company_id, branch_id, state, filter_branch_ids, administration, administration_account, administration_fee, has_reconciled_entries, approval_matrix_id, is_internal_approval_matrix, approved_matrix_ids, approval_matrix_line_id, is_approve_button, state1, state2, analytic_group_ids, apply_manual_currency_exchange, manual_currency_exchange_rate, manual_currency_exchange_inverse_rate, type_curr, name, 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, write_uid, write_date, __last_update. Field types distribution: many2one: 18, boolean: 11, text: 2, monetary: 2, date: 3, datetime: 3, selection: 6, many2many: 4, one2many: 5, float: 2, char: 7, integer: 5.


Show me the relational structure of salesperson.tracking.history.

Response: The salesperson.tracking.history model has 3 relational fields: tracking_history_id -> crm.sales.tracking.history; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


Describe the implementation of report.excel.section.

Response: The report.excel.section model is defined in module: report_excel. It has 0 computed fields: . Stored computed fields: none.


Tell me about the global.search model.

Response: The global.search model represents Global Search in the ERP system. It contains 11 fields and is used to manage global search data. Key fields include: model_id, field_ids, main_field_id, global_field_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How is vendor.evaluation implemented technically?

Response: The vendor.evaluation model is defined in module: vendor_evaluation. It has 0 computed fields: . Stored computed fields: none.


What operations can I perform on resource.resource?

Response: To use the resource.resource model, you need to provide values for required fields: name, resource_type, time_efficiency, calendar_id, tz. 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 field structure of partner.blacklist.history.

Response: The partner.blacklist.history model has 12 fields: user_id, type, reason, date, partner_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, selection: 1, char: 2, date: 1, integer: 1, datetime: 3.


How is receipt.voucher.line implemented technically?

Response: The receipt.voucher.line model is defined in module: equip3_accounting_operation. It has 0 computed fields: . Stored computed fields: none.


What are the available fields for res.currency.rate?

Response: The res.currency.rate model has 13 fields: name, currency_id, company_id, rate, conversion, mr_rate, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: date: 1, many2one: 4, float: 3, integer: 1, char: 1, datetime: 3.


What does the approval.matrix.sale.reject model represent?

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


What are the technical details of base.module.update?

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


How to create records in ir.model.fields.selection?

Response: To use the ir.model.fields.selection model, you need to provide values for required fields: field_id, value, 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.


How is purchase.request.allocation implemented technically?

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


How is account.cash.flow.statement used in the system?

Response: The account.cash.flow.statement model represents account.cash.flow.statement in the ERP system. It contains 21 fields and is used to manage account.cash.flow.statement data. Key fields include: date_from, date_to, today, levels, account_ids, company_ids, comparison, previous, comp_detail, type_report, journal_ids, target_move, report_currency_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What modules define tax.report?

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


What are the relationships in invoice.template.footer?

Response: The invoice.template.footer model has 4 relational fields: template_id -> invoice.templates; field_id -> ir.model.fields; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What models are connected to acrux.chat.message.wizard?

Response: The acrux.chat.message.wizard model has 11 relational fields: partner_id -> res.partner; conversation_id -> acrux.chat.conversation; connector_id -> acrux.chat.connector; sale_id -> sale.order; message_mass_id -> send.message.mass; opportunity_id -> crm.lead; whatsapp_template_id -> whatsapp.template; crm_message_mass_id -> crm.send.message.mass; attachment_ids -> ir.attachment; create_uid -> res.users; write_uid -> res.users. Many2many fields: attachment_ids.


How do I use the pos.generate.efaktur.invoice model?

Response: To use the pos.generate.efaktur.invoice model, you need to provide values for required fields: none. Readonly fields: l10n_id_tax_number, 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 stock.inventory.wizard have?

Response: The stock.inventory.wizard model has 8 fields: wizard_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: one2many: 1, integer: 1, char: 1, many2one: 2, datetime: 3.


Show me the relational structure of account.loan.generate.wizard.

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


How to query remove.pos.order data?

Response: To use the remove.pos.order 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 models are connected to ks_dashboard_ninja.board_custom_filters?

Response: The ks_dashboard_ninja.board_custom_filters model has 5 relational fields: ks_dashboard_board_id -> ks_dashboard_ninja.board; ks_model_id -> ir.model; ks_domain_field_id -> ir.model.fields; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


How does sale.margin.report.wizard relate to other models?

Response: The sale.margin.report.wizard model has 5 relational fields: partner_ids -> res.partner; company_ids -> res.company; branch_id -> res.branch; create_uid -> res.users; write_uid -> res.users. Many2many fields: partner_ids, company_ids.


What business logic is in base.geocoder?

Response: To use the base.geocoder 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.


How is account.unreconcile implemented technically?

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


What are the available fields for ir.qweb.field.integer?

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


What methods are available in ir.actions.server?

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


Describe the many2many relations for mail.shortcode.

Response: The mail.shortcode model has 3 relational fields: message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


How does base_import.tests.models.o2m relate to other models?

Response: The base_import.tests.models.o2m model has 3 relational fields: value -> base_import.tests.models.o2m.child; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


Tell me about the order.picking model.

Response: The order.picking model represents Order Picking in the ERP system. It contains 9 fields and is used to manage order picking data. Key fields include: move_id, order_picking_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Tell me about the pos.sync.session.order model.

Response: The pos.sync.session.order model represents Pos Sync Session Order in the ERP system. It contains 17 fields and is used to manage pos sync session order data. Key fields include: uid, data, name, database, state, line_ids, pos_config_id, pos_session_id, branch_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What business logic is in crm.lead.scoring.frequency?

Response: To use the crm.lead.scoring.frequency model, you need to provide values for required fields: none. Readonly fields: variable, value, won_count, lost_count, team_id, 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 mrp.production.backorder?

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


How is mrp.bom.line implemented technically?

Response: The mrp.bom.line model is defined in module: mrp. It has 0 computed fields: . Stored computed fields: none.


What modules define res.users.qiscuss?

Response: The res.users.qiscuss model is defined in module: equip3_crm_whatsapp. It has 0 computed fields: . Stored computed fields: none.


Describe the implementation of target.activity.line.

Response: The target.activity.line model is defined in module: equip3_crm_operation. It has 0 computed fields: . Stored computed fields: none.


How to create records in receipt.voucher?

Response: To use the receipt.voucher model, you need to provide values for required fields: name, partner_ids, voucher_date, bank_id, customer_invoice_ids, currency_id, company_id, branch_id. Readonly fields: payment_count, name, state, amount, customer_allowed_ids, is_cutoff_date, 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, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


Can you explain the purpose of extract.rfq.wizard?

Response: The extract.rfq.wizard model represents Extract Rfq Wizard in the ERP system. It contains 8 fields and is used to manage extract rfq wizard data. Key fields include: purchase_order_extract_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What are common use cases for account.efaktur?

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


Describe the barcode.labels model in Odoo.

Response: The barcode.labels model represents Barcode Labels in the ERP system. It contains 8 fields and is used to manage barcode labels data. Key fields include: product_get_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What modules define res.country.group?

Response: The res.country.group model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.


How do I use the report.equip3_pos_report.report_top_selling model?

Response: To use the report.equip3_pos_report.report_top_selling 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.


Show me the fields of pos.zone.

Response: The pos.zone model has 9 fields: name, company_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.


What methods are available in ir.model.constraint?

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


List all fields in the ir.module.module.exclusion model.

Response: The ir.module.module.exclusion model has 11 fields: name, module_id, exclusion_id, state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 4, selection: 1, integer: 1, datetime: 3.


What modules define asset.asset.revalue?

Response: The asset.asset.revalue model is defined in module: equip3_accounting_asset. It has 0 computed fields: . Stored computed fields: none.


What is the product.template.create.variant.line model?

Response: The product.template.create.variant.line model represents Product Template Create Variant in the ERP system. It contains 11 fields and is used to manage product template create variant data. Key fields include: variant_id, attribute_id, value_ids, filter_value_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What are the available fields for mass.editing.line?

Response: The mass.editing.line model has 13 fields: sequence, server_action_id, model_id, field_id, widget_option, apply_domain, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 2, many2one: 5, char: 2, boolean: 1, datetime: 3.


What foreign keys exist in account.invoice.to.draft?

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


Describe the implementation of report.sh_po_tender_management.report_analyze_quotations.

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


Which fields in product.warehouse.price are computed?

Response: The product.warehouse.price model is defined in module: allfresh_mod_costperwh. It has 0 computed fields: . Stored computed fields: none.


What foreign keys exist in sh.model.fields.purchase.order.selection?

Response: The sh.model.fields.purchase.order.selection model has 3 relational fields: sh_field_po_id -> sh.custom.model.purchase.order; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


How is sh.custom.field.model implemented technically?

Response: The sh.custom.field.model model is defined in module: sh_global_custom_fields. It has 0 computed fields: . Stored computed fields: none.


Describe the purchase.product.template.line model in Odoo.

Response: The purchase.product.template.line model represents Purchase Product Template Line in the ERP system. It contains 14 fields and is used to manage purchase product template line data. Key fields include: name, description, ordered_qty, unit_price, product_uom, purchase_template_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How is base_import.tests.models.char implemented technically?

Response: The base_import.tests.models.char model is defined in module: base_import. It has 0 computed fields: . Stored computed fields: none.


What are the technical details of nsfp.registration?

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


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

Response: The setu.inventory.turnover.analysis.report model has 15 fields: stock_file_data, start_date, end_date, product_category_ids, product_ids, warehouse_ids, company_id, company_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, date: 2, many2many: 4, many2one: 3, integer: 1, char: 1, datetime: 3.


What is the pos.session model?

Response: The pos.session model represents Point of Sale Session in the ERP system. It contains 101 fields and is used to manage point of sale session data. Key fields include: company_id, config_id, name, user_id, currency_id, start_at, stop_at, sequence_number, cash_control, cash_journal_id, cash_register_id, cash_register_balance_start, cash_register_balance_end, cash_register_difference, cash_real_difference, cash_real_transaction, cash_real_expected, order_ids, order_count, statement_ids, failed_pickings, picking_count, picking_ids, rescue, move_id, payment_method_ids, total_payments_amount, is_in_company_currency, update_stock_at_closing, move_id_old, orderline_checked, crm_team_id, required_reinstall_cache, backup_session, pos_branch_id, employee_id, lock_state, order_log_ids, opened_at, opened_uid, last_login_time, login_number, state, cash_opening_balance, cash_closing_balance, is_closing_wizard, pos_config_cashbox_lines_ids, pos_config_cashbox_clsosing_line_ids, cash_register_balance_end_real, cashier_id, total_invoice_count, total_faktur_count, log_cashier_ids, is_multi_session, order_with_receivable_invoice_ids, pos_config_uuid, pos_session_cashbox_wizard_ids, cash_management_ids, cash_history_ids, gain_loss_move_id, is_pos_config_save_order_history_local, scheduler_invoice_finish_date, void_ids, bank_register_total_entry_encoding, cash_register_total_entry_encoding, bank_closing_balance, pos_session_bank_cashbox_wizard_ids, to_recompute, is_invoice_recreate, 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 are the available fields for z.report.wizard?

Response: The z.report.wizard model has 11 fields: pos_session_ids, report_type, company_id, branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2many: 1, char: 2, many2one: 4, integer: 1, datetime: 3.


Can you explain the purpose of customer.category?

Response: The customer.category model represents Customer Category in the ERP system. It contains 9 fields and is used to manage customer category data. Key fields include: name, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


List all fields in the report.pos.order model.

Response: The report.pos.order model has 36 fields: date, order_id, partner_id, product_id, product_tmpl_id, state, user_id, price_total, price_sub_total, total_discount, average_price, company_id, nbr_lines, product_qty, journal_id, delay_validation, product_categ_id, invoiced, config_id, pos_categ_id, pricelist_id, session_id, employee_id, pos_branch_id, promotion_count, promotion_id, hour_group_id, zone_id, voucher_id, voucher_count, voucher_value, analytic_account_id, cashier_id, id, display_name, __last_update. Field types distribution: datetime: 2, many2one: 20, selection: 1, float: 5, integer: 6, boolean: 1, char: 1.


What modules define ai.chat.job?

Response: The ai.chat.job model is defined in module: ai_chat_agent. It has 0 computed fields: . Stored computed fields: none.


What are the available fields for update.customer.segment?

Response: The update.customer.segment model has 10 fields: date_begin, date_end, note, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: date: 2, text: 1, integer: 1, char: 1, many2one: 2, datetime: 3.


What modules define analytic.sale.order.line?

Response: The analytic.sale.order.line model is defined in module: contract_recurring_invoice_analytic. It has 0 computed fields: . Stored computed fields: none.


What foreign keys exist in purchase.order.line?

Response: The purchase.order.line model has 38 relational fields: taxes_id -> account.tax; product_uom -> uom.uom; product_uom_category_id -> uom.category; product_id -> product.product; order_id -> purchase.order; account_analytic_id -> account.analytic.account; company_id -> res.company; invoice_lines -> account.move.line; currency_id -> res.currency; product_template_attribute_value_ids -> product.template.attribute.value; product_no_variant_attribute_value_ids -> product.template.attribute.value; move_ids -> stock.move; orderpoint_id -> stock.warehouse.orderpoint; move_dest_ids -> stock.move; agreement_id -> purchase.agreement; picking_type_id -> stock.picking.type; purchase_request_lines -> purchase.request.line; purchase_request_allocation_ids -> purchase.request.allocation; sale_order_id -> sale.order; sale_line_id -> sale.order.line; branch_id -> res.branch; purchase_budget_lines -> budget.purchase; branch_ids -> res.branch; available_product_ids -> product.template; destination_location_id -> stock.location; destination_warehouse_id -> stock.warehouse; request_line_id -> purchase.request.line; partner_id -> res.partner; route_id -> stock.location.route; analytic_tag_ids -> account.analytic.tag; payment_term_id -> account.payment.term; product_template_id -> product.template; purchase_order_id -> purchase.order; requisition_line_id -> purchase.requisition.line; agreement_line_id -> purchase.agreement.line; merchendise_id -> merchendise.code; create_uid -> res.users; write_uid -> res.users. Many2many fields: taxes_id, product_template_attribute_value_ids, product_no_variant_attribute_value_ids, purchase_request_lines, branch_ids, available_product_ids, analytic_tag_ids.


How is purchase.order.split used in the system?

Response: The purchase.order.split model represents purchase.order.split in the ERP system. It contains 19 fields and is used to manage purchase.order.split data. Key fields include: tick, sequence, product_template_id, name, date_planned, product_qty, price_unit, destination_warehouse_id, split_id, purchase_line_id, product_uom, product_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What fields does generate.opening.entries have?

Response: The generate.opening.entries model has 12 fields: name, old_fiscal_year_id, new_fiscal_year_id, journal_id, period_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 6, integer: 1, datetime: 3.


What are the available fields for sh.sale.analysis.wizard?

Response: The sh.sale.analysis.wizard model has 18 fields: sh_end_date, sh_status, report_by, sh_product_ids, company_ids, sh_partner_ids, company_id, sale_analysis_dic, sale_currency_id, sh_status_ids, sh_start_date, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: datetime: 5, selection: 3, many2many: 3, many2one: 3, one2many: 1, integer: 2, char: 1.


How do I use the stock.inventory.approval.matrix model?

Response: To use the stock.inventory.approval.matrix model, you need to provide values for required fields: name, company_id, warehouse_id. Readonly fields: company_id, branch_id, approval_line_count, 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 are the available fields for extract.rfq.wizard?

Response: The extract.rfq.wizard model has 8 fields: purchase_order_extract_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: one2many: 1, integer: 1, char: 1, many2one: 2, datetime: 3.


Describe the res.config model in Odoo.

Response: The res.config model represents Config in the ERP system. It contains 7 fields and is used to manage config data. Key fields include: id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What methods are available in res.users.log?

Response: The res.users.log model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.


List all fields in the sh.purchase.report.representative.wizard model.

Response: The sh.purchase.report.representative.wizard model has 13 fields: date_start, date_end, user_ids, state, company_ids, branch_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: datetime: 5, many2many: 3, selection: 1, integer: 1, char: 1, many2one: 2.


How is account.loan.pay.amount used in the system?

Response: The account.loan.pay.amount model represents Loan pay amount in the ERP system. It contains 13 fields and is used to manage loan pay amount data. Key fields include: loan_id, currency_id, cancel_loan, date, amount, fees, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How do I use the ir.http model?

Response: To use the ir.http 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 fields does return.approval.matrix.line have?

Response: The return.approval.matrix.line model has 19 fields: sequence, sequence1, approver, minimal_approver, approval_status, time_stamp, last_approved, approved, return_approval_matrix_id1, picking_id, approved_users, dev_rma_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 4, many2many: 2, text: 1, datetime: 4, many2one: 6, boolean: 1, char: 1.


What operations can I perform on auditlog.log.line?

Response: To use the auditlog.log.line model, you need to provide values for required fields: none. Readonly fields: field_name, field_description, name, model_id, model_name, model_model, res_id, user_id, method, http_session_id, http_request_id, log_type, 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 sh.stock.move.global.check model.

Response: The sh.stock.move.global.check model has 16 fields: product_id, sh_message, sh_quality_point_id, picking_id, sh_measure, text_message, attachment_ids, type, move_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 6, text: 2, float: 1, many2many: 1, selection: 1, integer: 1, char: 1, datetime: 3.


How to create records in report.equip3_pos_report.report_closed_session?

Response: To use the report.equip3_pos_report.report_closed_session 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 does the sh.mrp.quality.alert model represent?

Response: The sh.mrp.quality.alert model represents Mrp Quality Alert in the ERP system. It contains 47 fields and is used to manage mrp quality alert data. Key fields include: name, title, product_id, lot_id, user_id, team_id, sh_priority, tag_ids, color, sh_description, partner_id, stage_id, mrp_id, workorder_id, company_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, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Which fields in sh.sale.invoice.summary.xls are computed?

Response: The sh.sale.invoice.summary.xls model is defined in module: sh_sale_reports. It has 0 computed fields: . Stored computed fields: none.


What data can be stored in mrp.workcenter?

Response: The mrp.workcenter model has 72 fields: active, note, sequence, color, routing_line_ids, order_ids, workorder_count, workorder_ready_count, workorder_progress_count, workorder_pending_count, workorder_late_count, time_ids, working_state, blocked_time, productive_time, oee, performance, workcenter_load, costs_hour_account_id, name, location_id, location_finished_id, location_rejected_id, location_byproduct_id, oh_time, ov_material, costs_hour, branch_id, create_uid, alternative_workcenter_ids, code, company_id, time_efficiency, capacity, oee_target, time_start, time_stop, is_branch_required, resource_id, resource_calendar_id, tz, 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_date, write_uid, write_date, __last_update. Field types distribution: boolean: 7, text: 1, integer: 13, one2many: 9, selection: 4, float: 10, many2one: 14, char: 6, many2many: 3, date: 2, datetime: 3.


What methods are available in account.loan.line?

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


What does the account.balance.report model represent?

Response: The account.balance.report model represents Trial Balance Report in the ERP system. It contains 14 fields and is used to manage trial balance report data. Key fields include: journal_ids, display_account, date_from, date_to, target_move, report_currency_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How is cancel.credit.limit used in the system?

Response: The cancel.credit.limit model represents cancel.credit.limit in the ERP system. It contains 9 fields and is used to manage cancel.credit.limit data. Key fields include: limit_id, reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Describe the implementation of account.analytic.group.

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


What are the relationships in sh.mpo.merge.purchase.order.wizard?

Response: The sh.mpo.merge.purchase.order.wizard model has 5 relational fields: partner_id -> res.partner; purchase_order_id -> purchase.order; purchase_order_ids -> purchase.order; create_uid -> res.users; write_uid -> res.users. Many2many fields: purchase_order_ids.


List all fields in the hide.field model.

Response: The hide.field model has 16 fields: access_management_id, model_id, field_id, invisible, readonly, required, external_link, create_option, edit_option, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, many2many: 1, boolean: 6, integer: 1, char: 1, datetime: 3.


What models are connected to product.template.create.variant?

Response: The product.template.create.variant model has 3 relational fields: variant_ids -> product.template.create.variant.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


List all fields in the pos.cashier.change.wizard model.

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 fields does report.equip3_pos_report.report_pos_payment have?

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


What data can be stored in sms.resend?

Response: The sms.resend model has 12 fields: mail_message_id, recipient_ids, has_cancel, has_insufficient_credit, has_unregistered_account, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, one2many: 1, boolean: 3, integer: 1, char: 1, datetime: 3.


List all fields in the account.multipayment.credit model.

Response: The account.multipayment.credit model has 22 fields: line_id, currency_id, invoice_id, account_id, invoice_date, invoice_date_due, original_amount, base_amount, original_unreconcile, base_unreconcile, is_full_reconcile, amount, payment_id, account_reverse_ids, account_reverse_total, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 7, date: 2, monetary: 5, boolean: 1, many2many: 1, float: 1, integer: 1, char: 1, datetime: 3.


What business logic is in website.track?

Response: To use the website.track model, you need to provide values for required fields: visitor_id, visit_datetime. Readonly fields: visitor_id, page_id, visit_datetime, product_id, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.


What are the relationships in queue.job.channel?

Response: The queue.job.channel model has 4 relational fields: parent_id -> queue.job.channel; job_function_ids -> queue.job.function; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


How does all.loyalty.setting relate to other models?

Response: The all.loyalty.setting model has 5 relational fields: product_id -> product.product; redeem_ids -> all.redeem.rule; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


Which fields in return.approval.matrix.line are computed?

Response: The return.approval.matrix.line model is defined in module: allfresh_mod_inventory. It has 0 computed fields: . Stored computed fields: none.


How is report_excel_export_gen used in the system?

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


How to query mrp.immediate.production data?

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


What foreign keys exist in picking.return.line?

Response: The picking.return.line model has 7 relational fields: product_id -> product.product; picking_id -> stock.picking; purchase_id -> purchase.order; sale_id -> sale.order; currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


List all fields in the kpi.category model.

Response: The kpi.category model has 22 fields: name, active, parent_id, child_ids, company_id, description, sequence, user_ids, user_group_ids, access_user_ids, edit_user_ids, edit_user_group_ids, edit_access_user_ids, help_notes, kpi_help_dummy, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, boolean: 2, many2one: 4, one2many: 1, text: 1, integer: 2, many2many: 6, html: 1, datetime: 3.


Which fields in purchase.request.line are computed?

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


What are common use cases for account.account.type?

Response: To use the account.account.type model, you need to provide values for required fields: name, type, company_id. Readonly fields: company_id, 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.


What methods are available in blanket.approval.matrix?

Response: The blanket.approval.matrix model is defined in module: equip3_sale_other_operation_cont. It has 0 computed fields: . Stored computed fields: none.


How does account.bank.statement.line.wizard relate to other models?

Response: The account.bank.statement.line.wizard model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


Show me the relational structure of _unknown.

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


What data can be stored in report.reordering?

Response: The report.reordering model has 9 fields: warehouse_id, location_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, many2many: 1, integer: 1, char: 1, datetime: 3.


What is the rating.parent.mixin model?

Response: The rating.parent.mixin model represents Rating Parent Mixin in the ERP system. It contains 5 fields and is used to manage rating parent mixin data. Key fields include: rating_ids, rating_percentage_satisfaction, id, display_name, __last_update.


How to create records in hr.employee?

Response: To use the hr.employee model, you need to provide values for required fields: company_id, resource_id. Readonly fields: user_partner_id, is_address_home_a_company, private_email, subordinate_ids, currency_id, image_1024, image_512, image_256, image_128, 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, hr_presence_state, last_activity, last_activity_time, hr_icon_display, goal_ids, badge_ids, has_badges, child_all_count, 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 accounting.matrix.reject.

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


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

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


How to create records in stock.assign.serial?

Response: To use the stock.assign.serial model, you need to provide values for required fields: product_id, move_id. Readonly fields: product_id, picking_type_code, serial_no, next_serial_number, is_serial_number, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


How to query ks_dashboard_ninja.board data?

Response: To use the ks_dashboard_ninja.board 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.


How to create records in account.tax.report.wizard?

Response: To use the account.tax.report.wizard 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 are the relationships in stock.quant.package?

Response: The stock.quant.package model has 13 relational fields: quant_ids -> stock.quant; packaging_id -> product.packaging; location_id -> stock.location; company_id -> res.company; owner_id -> res.partner; uom_id -> uom.uom; move_location_id -> stock.location; warehouse_id -> stock.warehouse; owner_id_stock -> res.partner; location_id_new -> stock.location; filter_location_id_new -> stock.location; create_uid -> res.users; write_uid -> res.users. Many2many fields: filter_location_id_new.


Tell me about the sh.push.notification model.

Response: The sh.push.notification model represents Web Push Notification in the ERP system. It contains 11 fields and is used to manage web push notification data. Key fields include: user_id, user_type, datetime, register_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What does the purchase.quotation.excel.extended model represent?

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


What does the hide.chatter model represent?

Response: The hide.chatter model represents Chatter Rights in the ERP system. It contains 13 fields and is used to manage chatter rights data. Key fields include: access_management_id, model_id, hide_chatter, hide_send_mail, hide_log_notes, hide_schedule_activity, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What data can be stored in base_import.tests.models.char.readonly?

Response: The base_import.tests.models.char.readonly 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.


What are the technical details of ir.mail_server?

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


How do I use the receipt.voucher model?

Response: To use the receipt.voucher model, you need to provide values for required fields: name, partner_ids, voucher_date, bank_id, customer_invoice_ids, currency_id, company_id, branch_id. Readonly fields: payment_count, name, state, amount, customer_allowed_ids, is_cutoff_date, 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, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


What foreign keys exist in whatsapp.template?

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


Show me the relational structure of account.cashbox.wizard.bank.line.

Response: The account.cashbox.wizard.bank.line model has 8 relational fields: account_cashbox_wizard_bank_id -> account.cashbox.wizard; payment_method_id -> pos.payment.method; cashbox_id -> account.bank.statement.cashbox; currency_id -> res.currency; pos_config_id -> pos.config; pos_session_id -> pos.session; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What business logic is in generate.pos.voucher?

Response: To use the generate.pos.voucher model, you need to provide values for required fields: start_date, end_date. Readonly fields: user_id, use_history_ids, no_of_used, 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 acrux.chat.connector model represent?

Response: The acrux.chat.connector model represents Connector Definition in the ERP system. It contains 38 fields and is used to manage connector definition data. Key fields include: name, sequence, message, company_id, team_id, verify, source, channel, endpoint, apikey, sandbox, uuid, time_to_respond, time_to_reasign, border_color, ca_app_name, ca_status, ca_status_txt, ca_qr_code, sale_report_id, connector_type, qc_app_name, qc_status, qc_status_txt, qc_qr_code, qc_channel, qc_channel_id, qc_sdk_token, qc_template_ids, qc_webhook_url, connection_status, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What modules define repair.order.make_invoice?

Response: The repair.order.make_invoice model is defined in module: repair. It has 0 computed fields: . Stored computed fields: none.


Describe the implementation of access.rights.profile.

Response: The access.rights.profile model is defined in module: equip3_general_features. It has 0 computed fields: . Stored computed fields: none.


What is the dev.rma.rma model?

Response: The dev.rma.rma model represents RMA in the ERP system. It contains 84 fields and is used to manage rma data. Key fields include: name, date, deadline_date, user_id, team_id, email, phone, notes, rma_lines, priority, tags, reject_reason, incoming_id, delivery_id, new_sale_id, invoice_id, is_rma_due, subject, partner_id, warehouse_id, location_id, sale_id, purchase_id, branch_id, filter_location_ids, operation_type_id, picking_type_code, new_purchase_id, receipt_id, is_po, return_possible_date, is_return_order, picking_id, analytic_group_ids, action_type, reason, company_id, is_done_bill, invoice_ids, picking_ids, remark, amount_total, company_currency_id, amount_total_untaxed, tax_amount, return_approval_matrix_id, rma_approval_matrix, return_approval_matrix_line_id, state, is_approve_matrix, is_request_for_approval_show, is_approve_button_show, 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.


How to create records in report.excel.param?

Response: To use the report.excel.param model, you need to provide values for required fields: name, code, type_param. 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 base.partner.merge.line model in Odoo.

Response: The base.partner.merge.line model represents Merge Partner Line in the ERP system. It contains 10 fields and is used to manage merge partner line data. Key fields include: wizard_id, min_id, aggr_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Describe the quality.alert.report model in Odoo.

Response: The quality.alert.report model represents Quality Alert Report in the ERP system. It contains 12 fields and is used to manage quality alert report data. Key fields include: date_from, date_to, product_ids, user_ids, stage_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How is o2m.global.search.fields used in the system?

Response: The o2m.global.search.fields model represents o2m.global.search.fields in the ERP system. It contains 14 fields and is used to manage o2m.global.search.fields data. Key fields include: sequence, name, field_id, global_o2m_search_id, model_id, related_model_id, ttype, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


List all fields in the field.conditional.access model.

Response: The field.conditional.access model has 18 fields: access_management_id, model_id, model_name, attrs_field_id, domain_field_id, domain_field_relation, attrs_type, field_attrs, field_domain, apply_attrs, apply_field_domain, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 6, char: 5, selection: 1, boolean: 2, integer: 1, datetime: 3.


What is the cancel.supplier.memory model?

Response: The cancel.supplier.memory model represents cancel.supplier.memory in the ERP system. It contains 9 fields and is used to manage cancel.supplier.memory data. Key fields include: supplier_id, reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What business logic is in service.level.agreement?

Response: To use the service.level.agreement 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.


Tell me about the mrp.bom model.

Response: The mrp.bom model represents Bill of Material in the ERP system. It contains 53 fields and is used to manage bill of material data. Key fields include: active, bom_line_ids, byproduct_ids, product_uom_category_id, sequence, operation_ids, ready_to_produce, picking_type_id, consumption, sh_bom_barcode_mobile, sh_bom_bm_is_cont_scan, code, type, product_id, product_qty, company_id, product_uom_id, branch_id, create_uid, forecast_cost, tool_ids, bom_tools, next_new_sequence, operation_two_ids, is_branch_required, use_operations, equip_bom_type, product_tmpl_id, type_product_bom, product_tmpl_ids, product_ids, product_name_display, 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_date, write_uid, write_date, __last_update.


What models are connected to recurring.move.line?

Response: The recurring.move.line model has 6 relational fields: partner_id -> res.partner; recurring_id -> invoice.recurring; account_id -> account.account; analytic_group_ids -> account.analytic.tag; create_uid -> res.users; write_uid -> res.users. Many2many fields: analytic_group_ids.


How to create records in pos.combo.limit?

Response: To use the pos.combo.limit model, you need to provide values for required fields: product_tmpl_id, pos_categ_id, quantity_limited. 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 field structure of res.config.settings.

Response: The res.config.settings model has 849 fields: user_default_rights, external_email_server_default, module_base_import, module_google_calendar, module_microsoft_calendar, module_google_drive, module_google_spreadsheet, module_auth_oauth, module_auth_ldap, module_base_gengo, module_account_inter_company_rules, module_pad, module_voip, module_web_unsplash, module_partner_autocomplete, module_base_geolocalize, module_google_recaptcha, report_footer, group_multi_currency, paperformat_id, external_report_layout_id, show_effect, company_count, active_user_count, language_count, company_name, company_informations, app_default_superbar_lazy_search, geoloc_provider_id, geoloc_provider_techname, geoloc_provider_googlemap_key, recaptcha_public_key, recaptcha_private_key, recaptcha_min_score, fail_counter, alias_domain, unsplash_access_key, app_system_name, app_show_lang, app_show_debug, app_show_documentation, app_show_documentation_dev, app_show_support, app_show_account, app_show_enterprise, app_show_share, app_show_poweredby, group_show_author_in_apps, module_odoo_referral, app_documentation_url, app_documentation_dev_url, app_support_url, app_account_title, app_account_url, app_enterprise_url, app_ribbon_name, auth_signup_reset_password, auth_signup_template_user_id, resource_calendar_id, module_hr_presence, module_hr_skills, hr_presence_control_login, hr_presence_control_email, hr_presence_control_ip, module_hr_attendance, hr_presence_control_email_amount, hr_presence_control_ip_list, hr_employee_self_edit, kpi_company_id, kpi_history_tolerance, show_kpi_help, group_discount_per_so_line, group_uom, group_product_variant, module_sale_product_configurator, module_sale_product_matrix, group_stock_packaging, group_product_pricelist, group_sale_pricelist, product_pricelist_setting, product_weight_in_lbs, product_volume_volume_in_cubic_feet, enable_menu_search, enable_web_push_notification, api_key, vapid, config_details, sh_multi_barcode_unique, is_sh_product_qrcode_generator_when_create, snailmail_color, snailmail_cover, snailmail_duplex, digest_emails, digest_id, company_id, sh_product_stock, sh_product_attribute, sh_product_image, sh_product_category, sh_product_code, sh_product_barcode, sh_product_sale_price, sh_product_sale_description, sh_touch_kyboard, sh_welcome_message, sh_message, sh_company_logo, sh_display, sh_display_view, sh_display_landscape, sh_display_portrait, sh_delay_screen, has_accounting_entries, currency_id, has_chart_of_accounts, chart_template_id, purchase_tax_id, tax_calculation_rounding_method, module_account_accountant, group_analytic_accounting, group_warning_account, group_cash_rounding, group_show_line_subtotals_tax_excluded, group_show_line_subtotals_tax_included, group_show_sale_receipts, group_show_purchase_receipts, show_line_subtotals_tax_selection, module_account_budget, module_account_payment, module_account_reports, module_account_check_printing, module_account_batch_payment, module_account_sepa, module_account_sepa_direct_debit, module_account_plaid, module_account_yodlee, module_account_bank_statement_import_qif, module_account_bank_statement_import_ofx, module_account_bank_statement_import_csv, module_account_bank_statement_import_camt, module_currency_rate_live, module_account_intrastat, module_product_margin, module_l10n_eu_service, module_account_taxcloud, module_account_invoice_extract, module_snailmail_account, tax_exigibility, tax_cash_basis_journal_id, account_cash_basis_base_account_id, qr_code, invoice_is_print, invoice_is_email, incoterm_id, invoice_terms, use_invoice_terms, country_code, crm_alias_prefix, generate_lead_from_alias, group_use_lead, group_use_recurring_revenues, module_crm_iap_lead, module_crm_iap_lead_website, module_crm_iap_lead_enrich, module_mail_client_extension, lead_enrich_auto, lead_mining_in_pipeline, predictive_lead_scoring_start_date, predictive_lead_scoring_start_date_str, predictive_lead_scoring_fields, predictive_lead_scoring_fields_str, group_mass_mailing_campaign, mass_mailing_outgoing_mail_server, mass_mailing_mail_server_id, show_blacklist_buttons, module_project_forecast, module_hr_timesheet, group_subtask_project, group_project_rating, group_project_recurring_tasks, module_product_expiry, group_stock_production_lot, group_lot_on_delivery_slip, group_stock_tracking_lot, group_stock_tracking_owner, group_stock_adv_location, group_warning_stock, group_stock_sign_delivery, module_stock_picking_batch, module_stock_barcode, stock_move_email_validation, stock_mail_confirmation_template_id, module_stock_sms, group_stock_multi_locations, website_id, website_name, website_domain, website_country_group_ids, website_company_id, website_logo, language_ids, website_language_count, website_default_lang_id, website_default_lang_code, specific_user_account, website_cookies_bar, google_analytics_key, google_management_client_id, google_management_client_secret, google_search_console, cdn_activated, cdn_url, cdn_filters, social_twitter, social_facebook, social_github, social_linkedin, social_youtube, social_instagram, has_social_network, favicon, social_default_image, google_maps_api_key, group_multi_website, has_google_analytics, has_google_analytics_dashboard, has_google_maps, has_google_search_console, has_default_share_image, account_check_printing_layout, account_check_printing_date_label, account_check_printing_multi_stub, account_check_printing_margin_top, account_check_printing_margin_left, account_check_printing_margin_right, vat_check_vies, group_show_form_view, picking_operation_type, sh_it_barcode_mobile_type, sh_it_bm_is_cont_scan, sh_it_bm_is_notify_on_success, sh_it_bm_is_notify_on_fail, sh_it_bm_is_sound_on_success, sh_it_bm_is_sound_on_fail, sh_it_bm_is_add_product, module_project_timesheet_synchro, module_project_timesheet_holidays, project_time_mode_id, timesheet_encode_uom_id, timesheet_min_duration, timesheet_rounding, is_encode_uom_days, manufacturing_lead, use_manufacturing_lead, group_mrp_byproducts, module_mrp_mps, module_mrp_plm, module_mrp_workorder, module_quality_control, module_mrp_subcontracting, group_mrp_routings, group_locked_by_default, group_expiry_date_on_delivery_slip, lock_confirmed_po, po_lock, po_order_approval, po_double_validation, po_double_validation_amount, company_currency_id, default_purchase_method, group_warning_purchase, module_account_3way_match, module_purchase_requisition, module_purchase_product_matrix, po_lead, use_po_lead, group_send_reminder, module_sg_bank_reconcile, module_sg_dbs_giro, sh_invoice_online_signature, sh_enable_approval, sh_restrict_for_close_period, invoice_is_snailmail, module_stock_landed_costs, stock_qty_forecast_method, stock_qty_forecast_interval, stock_qty_predicted_periods, stock_move_sms_validation, stock_sms_confirmation_template_id, channel_id, group_enable_discuss, group_disable_poll, app_stop_subscribe, inv_cost, is_cost_price_per_warehouse, fiscalyear_last_day, fiscalyear_last_month, period_lock_date, fiscalyear_lock_date, group_fiscal_year, sale_tax_id, module_pos_mercury, module_pos_adyen, module_pos_six, update_stock_quantities, module_stock_dropshipping, days_to_purchase, is_installed_sale, group_auto_done_setting, module_sale_margin, quotation_validity_days, use_quotation_validity_days, group_warning_sale, portal_confirmation_sign, portal_confirmation_pay, group_sale_delivery_address, group_proforma_sales, default_invoice_policy, deposit_default_product_id, auth_signup_uninvited, module_delivery, module_delivery_dhl, module_delivery_fedex, module_delivery_ups, module_delivery_usps, module_delivery_bpost, module_delivery_easypost, module_product_email_template, module_sale_coupon, module_sale_amazon, automatic_invoice, template_id, confirmation_template_id, sh_group_enable_report_section, group_enable_merge_purchase_order, po_operation_type, cancel_receipt, cancel_bill, group_enable_purchase_checklist, group_enable_purchase_custom_product_template, purchase_show_signature, chk_sign_confirm, purchase_enable_other_sign_option, sh_expiry_notification, sh_is_notify_vendor, sh_on_date_notify, enter_before_first_notify, enter_before_second_notify, enter_before_third_notify, enter_after_first_notify, enter_after_second_notify, enter_after_third_notify, attachment_email, group_enable_purchase_multi_product_adv, sh_purchase_configuration_limit, group_enable_purchase_order_history, item_limit_purchase, record_based_on_purchase, group_enable_purchase_price_history, purchase_order_information_in_message, purchase_product_detail_in_message, purchase_signature, purchase_display_in_message, po_send_pdf_in_message, sh_auto_add_followers, sh_portal_user_create, sh_tender_document_manage, sh_purchase_revision, is_enable_vendor_notification, user_ids, is_enable_auto_portal_user, is_enable_company_portal_user, is_enable_company_contact_portal_user, crm_default_team_id, crm_default_user_id, l10n_id_tax_address, l10n_id_tax_name, reminder_frequency, group_sale_order_template, company_so_template_id, module_sale_quotation_builder, security_lead, group_display_incoterm, group_lot_on_invoice, use_security_lead, default_picking_policy, sh_manage_tender_doc_portal, lc_journal_id, salesperson_id, salesteam_id, module_website_sale_delivery, sale_delivery_settings, group_delivery_invoice_address, module_website_sale_digital, module_website_sale_wishlist, module_website_sale_comparison, module_website_sale_stock, module_account, cart_recovery_mail_template, cart_abandoned_delay, mailsend_check, email_notification_days, res_user_ids, validate_picking, create_invoice, validate_invoice, allow_auto_intercompany, ks_forecast_method, use_sale_order_note, sale_order_note, keep_name_so, sh_sale_barcode_mobile_type, sh_sale_bm_is_cont_scan, sh_sale_bm_is_notify_on_success, sh_sale_bm_is_notify_on_fail, sh_sale_bm_is_sound_on_success, sh_sale_bm_is_sound_on_fail, sh_purchase_barcode_mobile_type, sh_purchase_bm_is_cont_scan, sh_purchase_bm_is_notify_on_success, sh_purchase_bm_is_notify_on_fail, sh_purchase_bm_is_sound_on_success, sh_purchase_bm_is_sound_on_fail, sh_invoice_barcode_mobile_type, sh_invoice_bm_is_cont_scan, sh_invoice_bm_is_notify_on_success, sh_invoice_bm_is_notify_on_fail, sh_invoice_bm_is_sound_on_success, sh_invoice_bm_is_sound_on_fail, sh_bom_barcode_mobile_type, sh_bom_bm_is_cont_scan, sh_bom_bm_is_notify_on_success, sh_bom_bm_is_notify_on_fail, sh_bom_bm_is_sound_on_success, sh_bom_bm_is_sound_on_fail, sh_stock_barcode_mobile_type, sh_stock_bm_is_cont_scan, sh_stock_bm_is_notify_on_success, sh_stock_bm_is_notify_on_fail, sh_stock_bm_is_sound_on_success, sh_stock_bm_is_sound_on_fail, sh_stock_bm_is_add_product, sh_inventory_adjt_barcode_mobile_type, sh_inventory_adjt_bm_is_cont_scan, sh_inventory_adjt_bm_is_notify_on_success, sh_inventory_adjt_bm_is_notify_on_fail, sh_inventory_adjt_bm_is_sound_on_success, sh_inventory_adjt_bm_is_sound_on_fail, sh_product_barcode_mobile_type, sh_product_bm_is_cont_scan, sh_product_bm_is_notify_on_success, sh_product_bm_is_notify_on_fail, sh_product_bm_is_sound_on_success, sh_product_bm_is_sound_on_fail, sh_product_bm_is_default_code, sh_product_bm_is_lst_price, sh_product_bm_is_qty_available, sh_product_bm_is_virtual_available, sh_global_document_search_is_enable, sh_global_document_search_is_sale, sh_global_document_search_is_purchase, sh_global_document_search_is_picking, sh_global_document_search_is_invoice, sh_global_document_search_is_product, sh_global_document_search_is_lot, sh_global_document_search_is_location, sh_global_document_search_action_target_type, sale_credit_limit_email_alerts, sale_email_specific_user_id, quot_to_po, so_to_po, inventory_availability, available_threshold, website_warehouse_id, down_payment_product_id, implementor_setting, general, purchase, sales, inventory, manufacturing, central_kitchen, human_resource, pos, simple_manufacturing, assembly, cutting, mining, agriculture, show_branch, past_x_days_sales, currency_exchange_journal_id, income_currency_exchange_account_id, expense_currency_exchange_account_id, unrealized_exchange_journal_id, income_unrealized_exchange_account_id, expense_unrealized_exchange_account_id, is_inverse_rate, is_taxes_rate, tax_discount_policy, sale_account_id, purchase_account_id, interest_income, interest_expense, deposit_reconcile_journal_id, journal_id, deposit_account_id, petty_cash_expense_account_id, overdue_template, tax_rounding_type, accounting, is_credit_note_approval_matrix, is_refund_approval_matrix, is_customer_deposit_approval_matrix, is_vendor_deposit_approval_matrix, is_receipt_giro_approval_matrix, is_payment_giro_approval_matrix, is_purchase_currency_approval_matrix, is_budget_approval_matrix, is_budget_change_req_approval_matrix, is_purchase_budget_approval_matrix, is_purchase_budget_change_req_approval_matrix, is_internal_transaction, is_analytic_groups_balance_sheet, is_assets_approving_matrix, is_cash_advance_approving_matrix, is_invoice_approval_matrix, is_bill_approval_matrix, is_other_income_approval_matrix, is_other_expense_approval_matrix, is_customer_multi_receipt_approval_matrix, is_vendor_multipayment_approval_matrix, is_receipt_approval_matrix, is_payment_approval_matrix, is_payment_voucher_approval_matrix, group_is_credit_note_approval_matrix, group_is_refund_approval_matrix, group_is_customer_deposit_approval_matrix, group_is_vendor_deposit_approval_matrix, group_is_receipt_giro_approval_matrix, group_is_payment_giro_approval_matrix, group_is_internal_transfer_approval_matrix, group_is_purchase_currency_approval_matrix, group_is_budget_approval_matrix, group_is_budget_change_req_approval_matrix, group_is_purchase_budget_approval_matrix, group_is_purchase_budget_change_req_approval_matrix, group_account_asset_category_fiscal, group_assets_approving_matrix, group_cash_advance_approval_matrix, group_is_invoice_approval_matrix, group_is_bill_approval_matrix, group_is_other_income_approval_matrix, group_is_other_expense_approval_matrix, group_is_customer_multi_receipt_approval_matrix, group_is_vendor_multipayment_approval_matrix, group_is_receipt_approval_matrix, group_is_payment_approval_matrix, group_is_payment_voucher_approval_matrix, module_om_account_budget, Use_received_date, customer_availability, automated_invoice_followup, followup_sending_date, reminder_interval_before, reminder_interval_before_unit, reminder_notification_before, reminder_interval_after, reminder_interval_after_unit, reminder_notification_after, invoice_bill_reminder, reminder_interval_before_invoice, reminder_interval_after_invoice, reminder_interval_before_unit_invoice, eminder_interval_after_unit_invoice, reminder_notification_before_invoice, reminder_notification_after_invoice, days_bill_before, days_bill_after, days_invoice_before, days_invoice_after, sending_date_bill_before, sending_date_bill_after, sending_date_invoice_before, sending_date_invoice_after, date_last_reminder_due_date, date_last_reminder_after_due_date, date_last_reminder_bill_due_date, date_last_reminder_bill_after_due_date, date_last_reminder_bill_before_due_date, is_invoice_cutoff_date, invoice_cutoff_date, post_discount_account, prefix_limit, is_material_request_approval_matrix, is_internal_transfer_approval_matrix, is_stock_count_approval, is_product_usage_approval, is_return_orders, return_type, is_inventory_adjustment_with_value, putaway_max_capacity, set_warehouse_sublevel, warehouse_sublevel_zone, warehouse_sublevel_shelf, warehouse_sublevel_rack, warehouse_sublevel_bin, group_is_three_dimension_warehouse, is_mbs_on_transfer_operations, is_mbs_on_product_usage, is_mbs_on_stock_count_and_inventory_adjustment, outgoing_routing_strategy, sort_quants_by, routing_order, is_receiving_notes_approval_matrix, is_adj_picking, is_delivery_order_approval_matrix, brand_setting, is_manufacturing_plan, allow_submit_purchase_request, allow_submit_material_request, mo_force_done, manufacturing_plan_conf, manufacturing_order_conf, mrp_plan_partial_availability, mp_auto_reserve_availability_materials, mo_auto_reserve_availability_materials, production_record_conf, mrp_production_partial_availability, mrp_submit_purchase_request, mrp_submit_material_request, mrp_force_done, manufacturing_mps, manufacturing_period, manufacturing_period_to_display, autogenerated_based_methods, send_wa_approval_notification_mrp, send_wa_approval_notification_mp, send_wa_approval_notification_mpr, is_vendor_approval_matrix, is_purchase_order_approval_matrix, is_purchase_request_approval_matrix, is_vendor_pricelist_approval_matrix, is_purchase_tender_approval_matrix, purchase_approval_matrix, is_blanket_order_approval_matrix, is_good_services_order, is_purchase_tender, is_blanket_order, is_direct_purchase_approval_matrix, is_pr_department, is_price_ratting_rfq_tender, retail, module_equip3_purchase_rental, is_product_brand_filter, is_product_vendor_pricelist_filter, is_service_work_order, is_purchase_request_assign_user, group_create_purchase_request_direct, is_customer_approval_matrix, is_customer_limit_matrix, is_over_limit_validation, is_bo_approval_matrix, show_sale_barcode_mobile_type, sh_sale_barcode_mobile_type_new, group_om_account_budget, credit_note_expiry_date, bom_tools, sale_order_multiple_pricelist, automatic_confirm_saleorder, automatic_invoice_create, is_delivery_acknowledgement, is_broadcast_order, module_pragmatic_portal_user, module_pragmatic_delivery_acknowledgement, module_pragmatic_website_cash_on_delivery, commission_pay_on, commission_calc, commission_pay_by, is_message_rn, send_notification_users_ids, bank_integrate_url, bank_integrate_username, bank_integrate_password, validate_api, accounting_budget_use_theoretical_achievement, is_pajak_express_integration, pajak_express_url, pajak_express_transaction_url, pajak_express_username, pajak_express_password, validate_api_first, validate_api_express, validate_api_express_fail, group_is_pajak_express_integration, is_call_bi_api, is_call_kemenkeu_api, token_kemenkeu_api, internal_type, ex_period, material_request, is_product_service_operation, is_product_service_operation_delivery, mr_expiry_days, itr_expiry_days, is_return_limit_policy, return_policy_days, is_display_warehouse_address, module_procurement_jit, is_warehouse_shipments, qty_can_minus, is_vendor_approval_email, is_vendor_approval_whatsapp, is_vendor_pricelist_approval_email, is_vendor_pricelist_approval_whatsapp, sale_matrix_config, is_total_amount, total_sequence, total_sequence_select, is_margin_amount, margin_sequence, margin_sequence_select, is_discount_amount, discount_sequence, discount_sequence_select, expired_date, multilevel_disc_sale, is_wa_so_approval, is_email_so_approval, show_select_product_button, lock_sale_order, product_pricelist_default, auto_mail, group_multi_do, whatsapp_instance_id, whatsapp_token, qr_code_image, whatsapp_authenticate, product_expiry, expiry_days_select, group_analytic_tags, pu_barcode_mobile_type, pu_bm_is_cont_scan, pu_bm_is_notify_on_success, pu_bm_is_notify_on_fail, pu_bm_is_sound_on_success, pu_bm_is_sound_on_fail, pu_bm_is_add_product, pr_expiry_notification, pr_on_date_notify, pr_enter_before_first_notify, pr_enter_after_first_notify, pr_expiry_date, pr_expiry_date_goods, pr_expiry_date_services, rfq_exp_date, po_exp_date, rfq_exp_date_goods, rfq_exp_date_services, po_exp_date_goods, po_exp_date_services, max_percentage, pr_qty_limit, multilevel_disc, is_email_notification_req, is_whatsapp_notification_req, vendor_purchase_limit, is_email_notification, is_whatsapp_notification, pr_order_average_price, is_purchase_vendor_rating_warning, is_product_service_operation_receiving, customer_credit_limit, customer_max_invoice_overdue_days, customer_open_invoice_limit, is_over_credit_limit, over_credit_limit_sequence, over_credit_limit_sequence_select, is_invoice_overdue, invoice_overdue_sequence, invoice_overdue_sequence_select, open_invoice_limit, open_invoice_limit_sequence, open_invoice_limit_sequence_select, is_wa_overlimit_approval, is_email_overlimit_approval, is_email_notification_customer_credit, is_whatsapp_notification_customer_credit, group_use_multi_salesperson_on_leads, is_auto_follow_up, interval_number, interval_type, number_of_repetition, expired_lot_serial_no, is_auto_validate, scrap_income_id, scrap_expense_id, pt_expiry_notification, pt_on_date_notify, pt_enter_before_first_notify, pt_enter_after_first_notify, pt_expiry_date, bo_expiry_notification, bo_enter_before_first_notify, bo_enter_after_first_notify, pt_goods_order_expiry_date, pt_service_order_expiry_date, bo_goods_order_expiry_date, bo_service_order_expiry_date, is_email_notification_tender, is_whatsapp_notification_tender, is_email_notification_bo, is_whatsapp_notification_bo, notifications_expiry_voucher, notifications_time, bo_expiry_date, bo_before_exp_notify, bo_days_before_exp_notify, bo_on_date_notify, bo_approval_email_notify, bo_approval_wa_notify, is_order_rounding, order_rounding_type, rounding_multiplier, pos_product_discount1_id, apply_rounding_type, rounding_method_id, pos_def_receipt_template_id, is_pos_receivable, direct_control, qty_limit, budget_limit, is_email_notification_direct_purchase, is_whatsapp_notification_direct_purchase, is_post_closing_cashbox_value_in_session, allow_create_member_in_pos_screen, pkp_customer, membership_pluspoint_rounding, membership_pluspoint_rounding_type, membership_pluspoint_rounding_multiplier, is_pos_use_deposit, is_return_request_approval_matrix, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 535, text: 7, many2one: 61, integer: 71, char: 52, float: 16, selection: 85, date: 8, many2many: 6, binary: 4, monetary: 1, datetime: 3.


What does the untaken.stock.line model represent?

Response: The untaken.stock.line model represents Untaken Stock Line in the ERP system. It contains 11 fields and is used to manage untaken stock line data. Key fields include: product_id, quantity, product_unit_measure, untaken_stock_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


List all fields in the account.journal.group model.

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 common use cases for saleblanket.saleblanket?

Response: To use the saleblanket.saleblanket model, you need to provide values for required fields: name, expiry_date, branch_id. Readonly fields: name, sale_order_count, creation_date, user_id, order_line_count, state, currency_id, state1, state2, state3, bo_state, bo_state_1, company_id, approving_matrix_bo_sale_id, is_bo_approval_matrix, is_approval_matrix_filled, is_approve_button, approval_matrix_line_id, approved_matrix_ids, amount_untaxed, amount_tax, amount_total, analytic_accounting, is_product_filled, max_line_sequence, report_template_id1, amount_to_text, 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.


How is hr.employee.public implemented technically?

Response: The hr.employee.public model is defined in module: hr. It has 0 computed fields: . Stored computed fields: none.


What are the technical details of itr.approval.matrix?

Response: The itr.approval.matrix model is defined in module: equip3_inventory_masterdata. It has 0 computed fields: . Stored computed fields: none.


Describe the implementation of setu.stock.movement.report.

Response: The setu.stock.movement.report model is defined in module: setu_advance_inventory_reports. It has 0 computed fields: . Stored computed fields: none.


What models are connected to queue.jobs.to.done?

Response: The queue.jobs.to.done model has 3 relational fields: job_ids -> queue.job; create_uid -> res.users; write_uid -> res.users. Many2many fields: job_ids.


What modules define ir.ui.view.custom?

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


Describe the many2many relations for asset.cip.line.

Response: The asset.cip.line model has 6 relational fields: product_id -> product.template; account_id -> account.account; cip_id -> asset.cip; move_id -> account.move; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What are the technical details of pos.combo.item?

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


What business logic is in base_import.tests.models.m2o.required?

Response: To use the base_import.tests.models.m2o.required model, you need to provide values for required fields: value. 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 utm.source?

Response: To use the utm.source 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 fields of setu.inventory.overstock.bi.report.

Response: The setu.inventory.overstock.bi.report model has 31 fields: product_id, product_category_id, warehouse_id, company_id, sales, ads, qty_available, incoming, outgoing, forecasted_stock, demanded_qty, coverage_days, overstock_qty, overstock_value, wh_overstock_qty_per, wh_overstock_value_per, turnover_ratio, stock_movement, last_purchase_date, last_purchase_qty, last_purchase_price, currency_name, vendor_name, wizard_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 7, float: 15, char: 4, date: 1, integer: 1, datetime: 3.


Show me the relational structure of sh.purchase.report.representative.wizard.

Response: The sh.purchase.report.representative.wizard model has 5 relational fields: user_ids -> res.users; company_ids -> res.company; branch_ids -> res.branch; create_uid -> res.users; write_uid -> res.users. Many2many fields: user_ids, company_ids, branch_ids.


How to query term.condition data?

Response: To use the term.condition 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 does x.report.wizard relate to other models?

Response: The x.report.wizard model has 5 relational fields: pos_session_ids -> pos.session; branch_id -> res.branch; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: pos_session_ids.


What modules define sh.top.customers.xls?

Response: The sh.top.customers.xls model is defined in module: sh_sale_reports. It has 0 computed fields: . Stored computed fields: none.


What operations can I perform on ir.actions.act_window_close?

Response: To use the ir.actions.act_window_close model, you need to provide values for required fields: type, name, binding_type. Readonly fields: xml_id, 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 product.pricelist.item model.

Response: The product.pricelist.item model has 39 fields: product_tmpl_id, product_id, categ_id, min_quantity, base, base_pricelist_id, pricelist_id, price_surcharge, price_discount, price_round, price_min_margin, price_max_margin, company_id, currency_id, active, date_start, date_end, compute_price, fixed_price, percent_price, price, minimum_price, maximum_price, new_price, pricelist_uom_id, uom_id, uom_ids, applied_on, pos_category_id, min_price, max_price, name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 12, float: 12, selection: 3, boolean: 1, datetime: 5, char: 4, many2many: 1, integer: 1.


What fields does pos.account.cashbox.line have?

Response: The pos.account.cashbox.line model has 11 fields: coin_value, number, subtotal, pos_config_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: float: 2, integer: 2, many2one: 3, char: 1, datetime: 3.


What are the relationships in expiry.picking.confirmation?

Response: The expiry.picking.confirmation model has 6 relational fields: lot_ids -> stock.production.lot; picking_ids -> stock.picking; production_ids -> mrp.production; workorder_id -> mrp.workorder; create_uid -> res.users; write_uid -> res.users. Many2many fields: lot_ids, picking_ids, production_ids.


What are the available fields for ir.qweb.field.float_time?

Response: The ir.qweb.field.float_time model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.


What are the available fields for account.loan.post?

Response: The account.loan.post model has 10 fields: loan_id, journal_id, account_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, integer: 1, char: 1, datetime: 3.


What fields does setu.inventory.fsn.analysis.report have?

Response: The setu.inventory.fsn.analysis.report model has 16 fields: stock_file_data, start_date, end_date, product_category_ids, product_ids, warehouse_ids, stock_movement_type, company_id, company_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, date: 2, many2many: 4, selection: 1, many2one: 3, integer: 1, char: 1, datetime: 3.


List all fields in the ir.translation model.

Response: The ir.translation model has 12 fields: name, res_id, lang, type, src, value, module, state, comments, id, display_name, __last_update. Field types distribution: char: 3, integer: 2, selection: 3, text: 3, datetime: 1.


Describe the field structure of report.stock.report_product_template_replenishment.

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


What are the available fields for report.excel.aggregate?

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


What are common use cases for payment.sale.details.report?

Response: To use the payment.sale.details.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.


What are the available fields for project.task.type.delete.wizard?

Response: The project.task.type.delete.wizard model has 11 fields: project_ids, stage_ids, tasks_count, stages_active, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2many: 2, integer: 2, boolean: 1, char: 1, many2one: 2, datetime: 3.


How to create records in pos.promotion?

Response: To use the pos.promotion model, you need to provide values for required fields: name, end_date, type, tebus_murah_brand_gift_based_on, start_date. Readonly fields: currency_id, no_of_used, 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 pos.receipt.template?

Response: The pos.receipt.template model has 28 fields: name, is_default, size, custom_size, is_need_header, receipt_header_text, is_need_footer, receipt_footer_text, is_receipt_disc_in_orderline, is_receipt_tax_include_orderline, is_receipt_serial_lot_info, is_receipt_savings_summary, savings_summary_text, is_receipt_product_code, preview_receipt, company_id, voucher_receipt_display, generate_voucher_id, is_voucher_receipt, is_show_discount_detail, is_receipt_member_info, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, boolean: 11, selection: 2, float: 1, text: 3, html: 1, many2one: 4, integer: 1, datetime: 3.