Describe the field structure of sale.order.

Response: The sale.order model has 289 fields: origin, client_order_ref, reference, is_expired, require_signature, require_payment, create_date, user_id, pricelist_id, currency_id, invoice_count, invoice_ids, invoice_status, amount_by_group, currency_rate, fiscal_position_id, team_id, signature, signed_by, signed_on, amount_undiscounted, type_name, transaction_ids, authorized_transaction_ids, show_update_pricelist, tag_ids, applied_coupon_ids, generated_coupon_ids, reward_amount, no_code_promo_program_ids, code_promo_program_id, promo_code, sale_order_option_ids, purchase_order_count, incoterm, picking_policy, picking_ids, delivery_count, procurement_group_id, effective_date, expected_date, json_popover, show_json_popover, website_order_line, cart_quantity, only_services, is_abandoned_cart, cart_recovery_email_sent, website_id, conversation_id, internal_id, inter_transfer_count, client_order_id, discount_amt, discount_amt_line, warranty_sale, recurring_rule_type, recurring_interval, delivery_message, delivery_rating_success, delivery_set, recompute_delivery_price, is_all_service, is_process_rma, merged, name, parent_saleorder_id, order_revised_count, so_number, margin, margin_percent, mrp_production_count, note, report_grids, grid_product_tmpl_id, grid_update, grid, tasks_ids, tasks_count, visible_project, project_ids, sh_sale_barcode_mobile, sh_sale_bm_is_cont_scan, partner_credit_conform, sh_purchase_count, sh_so_po_is_show_so_to_po_btn_flag, apply_manual_currency_exchange, manual_currency_exchange_rate, company_currency_id, active_manual_currency_rate, warning_stock, opportunity_id, report_template_id1, report_template_id, amount_to_text, timesheet_ids, timesheet_count, project_id, timesheet_encode_uom_id, timesheet_total_duration, rfm_segment_id, amount_delivery, order_credit_points, order_redeem_points, redeem_value, is_from_website, loyalty_point_credit, order_source, driver_id, order_driver_message_ids, payment_status_with_driver, latitude, longitude, distance_btn_2_loc, sale_order_comm_ids, commission_calc, commission_pay_on, stage_id, order_line_count, date_order, validity_date, payment_term_id, sale_order_template_id, sale_state, delivered_state, sale_state_1, state_2, revised_state, approval_matrix_state, approval_matrix_state_1, branch_id, account_tag, account_tag_ids, analytic_account_id, approving_matrix_sale_id, approved_matrix_ids, is_customer_approval_matrix, hide_proforma, is_approval_matrix_filled, is_approve_button, approval_matrix_line_id, is_quotation_cancel, company_id, deduction_ids, analytic_accounting, terms_conditions_id, group_multi_do, is_single_warehouse, is_single_delivery_date, commitment_date, revised_sale_order_ids, revised_sale_order_id, is_revision_so, is_print_report, qty_delivered, count_delivered, multilevel_disc, multi_discount, discount_method, discount_amount, date_confirm, is_sale_order, partner_name, is_hidden_button, lock_sale_order, readonly_disc, readonly_multi, brand, partner_invoice_id, partner_shipping_id, reject_reason, sale_fully_delivered, sale_partially_delivery, sale_fully_paid, sale_partially_paid, sale_hidden_compute_field, date_kanban, is_down_payment, down_payment_amount, total_amount_without_dp, carrier_id, amount_untaxed, amount_tax, amount_total, order_line, discount_type, city_id, state_id, show_mobile, is_external_link, tax_discount_policy, discount_amt_before, discount_amt_line_before, amount_subtotal, warehouse_id, warehouse_new_id, delivery_state, payment_status_driver, approving_matrix_limit_id, approved_matrix_limit_ids, is_over_limit_validation, is_limit_matrix_filled, is_direct_confirm, limit_approval_matrix_line_id, is_approve_button_limit, limit_matrix_state, limit_matrix_state_1, limit_matrix_state_2, sale_limit_state, sale_limit_state_1, sale_limit_state_2, sale_limit_state_3, sale_limit_state_4, sale_limit_state_5, approval_matrix_state_2, approval_matrix_state_3, approval_matrix_state_4, approval_matrix_state_5, approval_matrix_state_6, approval_matrix_state_7, approval_matrix_state_8, approval_matrix_state_9, creditlim, hide_button_revise, lock_order_line, have_available_customer_voucher, customer_voucher_used_ids, cashback_line_ids, show_cashback, cn_cashback_ids, cn_cashback_count, title, partner_id, book_order, ean13, pos_config_id, pos_location_id, delivery_date, delivered_date, delivery_address, delivery_phone, payment_partial_amount, payment_partial_method_id, insert, state, pos_branch_id, pos_order_id, is_self_pickup, is_dropship, purchase_request_ids, purchase_request_count, remark, campaign_id, source_id, medium_id, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, access_url, access_token, access_warning, id, display_name, create_uid, write_uid, write_date, __last_update. Field types distribution: char: 32, boolean: 66, datetime: 10, many2one: 55, integer: 25, many2many: 15, selection: 37, binary: 2, float: 14, one2many: 18, date: 4, monetary: 9, text: 2.


Tell me about the ir.ui.view model.

Response: The ir.ui.view model represents View in the ERP system. It contains 41 fields and is used to manage view data. Key fields include: name, model, key, priority, arch, arch_base, arch_db, arch_fs, arch_updated, arch_prev, inherit_id, inherit_children_ids, field_parent, model_data_id, xml_id, groups_id, mode, active, customize_show, is_seo_optimized, website_meta_title, website_meta_description, website_meta_keywords, website_meta_og_img, seo_name, website_id, page_ids, first_page_id, track, visibility, visibility_password, visibility_password_display, theme_template_id, type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What is the generate.pos.voucher model?

Response: The generate.pos.voucher model represents Generate POS voucher in the ERP system. It contains 35 fields and is used to manage generate pos voucher data. Key fields include: customer_id, code, start_date, end_date, maximum_discount_amount, minimum_purchase_amount, limit_restrict_product_ids, pos_category_ids, state, value, apply_type, method, use_date, user_id, source, use_history_ids, name, company_id, no_of_usage, no_of_used, minimum_spend, is_customize_sequence, sequence_generate_method, manual_input_sequence, running_number_prefix, running_number_digit, running_number_current_sequence, brand_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What data can be stored in customer.statement?

Response: The customer.statement model has 47 fields: name, partner_ids, overdue_template, company_ids, report_currency_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, sequence_prefix, sequence_number, journal_ids, date_from, date_to, target_move, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 3, many2many: 5, many2one: 7, one2many: 4, selection: 3, char: 7, date: 4, boolean: 5, integer: 6, datetime: 3.


How to create records in pos.generate.efaktur.other?

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


Show me the fields of account.fiscal.year.

Response: The account.fiscal.year model has 11 fields: name, date_from, date_to, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, date: 2, many2one: 3, integer: 1, datetime: 3.


Describe the implementation of report.point_of_sale.report_invoice.

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


What are the available fields for nsfp.registration?

Response: The nsfp.registration model has 15 fields: record_id, fiscal_year, start, end, last_number, registration_date, is_use, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 2, many2one: 4, char: 5, boolean: 1, datetime: 3.


Describe the field structure of stock.package.destination.

Response: The stock.package.destination model has 11 fields: picking_id, move_line_ids, location_dest_id, filtered_location, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, many2many: 1, one2many: 1, integer: 1, char: 1, datetime: 3.


How do I use the account.account.map.line model?

Response: To use the account.account.map.line model, you need to provide values for required fields: map_id, child_company_id. Readonly fields: company_id, target_company, target_account, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


What are the available fields for account.pettycash.fund.reconcile?

Response: The account.pettycash.fund.reconcile model has 14 fields: fund, date, payable_account, reconciled_amount, move, vouchers, is_pettycash_voucher_approved, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, date: 1, float: 1, many2many: 1, boolean: 1, integer: 1, char: 1, datetime: 3.


Describe the field structure of replenish.wizard.

Response: The replenish.wizard model has 11 fields: fund_id, effective_date, replenish_account_id, replenish_amount, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, date: 1, float: 1, integer: 1, char: 1, datetime: 3.


Show me the fields of purchase.order.line.

Response: The purchase.order.line model has 130 fields: name, product_qty, product_uom_qty, taxes_id, product_uom, product_uom_category_id, product_id, price_unit, price_tax, order_id, account_analytic_id, company_id, state, invoice_lines, qty_invoiced, qty_received, qty_received_manual, qty_to_invoice, currency_id, date_order, display_type, is_configurable_product, product_template_attribute_value_ids, product_no_variant_attribute_value_ids, qty_received_method, move_ids, orderpoint_id, move_dest_ids, product_description_variants, propagate_cancel, tick, status, agreement_id, cancel_lines, sh_tender_note, picking_type_id, purchase_request_lines, purchase_request_allocation_ids, sale_order_id, sale_line_id, discount_method, discount_type, discount_amount, discount_amt, branch_id, is_down_payment, purchase_req_budget, realized_amount, confirm_purchase_req_budget, confirm_realized_amount, confirm_budget_data, purchase_budget_lines, planned, is_vendor_pricelist_line, branch_ids, gross_total, price_unit_uom, available_product_ids, last_purchased_price, last_customer_purchase_price, destination_location_id, destination_warehouse_id, date_planned, delivery_ref, vendor_bills_ref, request_line_id, readonly_price, sequence, sequence2, avg_price, current_qty, incoming_stock, actual_progress, remaining_progress, progress_paid, date_received, reference_purchase_price, purchase_line_cost_saving, total_cost_saving, cost_saving_percentage, partner_id, price_subtotal, price_total, total_price, discounted_value, state_delivery, state_inv, multi_discount, product_type, virtual_available_at_date, scheduled_date, forecast_expected_date, free_qty_today, qty_available_today, qty_to_deliver, is_mto, display_qty_widget, route_id, analytic_tag_ids, bid, cost_saving, payment_term_id, base_price, update_base, lead_time, feedback, company_size, capital_revenue, base_quantity, product_template_id, purchase_order_id, is_goods_orders, is_services_orders, requisition_line_id, agreement_line_id, sh_product_description, dp_line, is_reward_line, price_reduce, is_assets_orders, barcode, merchendise_id, persentase_antar_badan, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 2, float: 40, many2many: 7, many2one: 26, selection: 9, one2many: 5, datetime: 8, boolean: 16, char: 10, date: 1, integer: 3, monetary: 3.


What is the payment.token model?

Response: The payment.token model represents Payment Token in the ERP system. It contains 16 fields and is used to manage payment token data. Key fields include: name, short_name, partner_id, acquirer_id, company_id, acquirer_ref, active, payment_ids, verified, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Describe the mailing.trace.report model in Odoo.

Response: The mailing.trace.report model represents Mass Mailing Statistics in the ERP system. It contains 15 fields and is used to manage mass mailing statistics data. Key fields include: name, mailing_type, campaign, scheduled_date, state, email_from, sent, delivered, opened, replied, clicked, bounced, id, display_name, __last_update.


What are the technical details of overhead.material?

Response: The overhead.material model is defined in module: equip3_manuf_masterdata. It has 0 computed fields: . Stored computed fields: none.


What models are connected to stock.assign.serial?

Response: The stock.assign.serial model has 4 relational fields: product_id -> product.product; move_id -> stock.move; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What does the fast.financial.report.query model represent?

Response: The fast.financial.report.query model represents Query for Financial Report in the ERP system. It contains 3 fields and is used to manage query for financial report data. Key fields include: id, display_name, __last_update.


How do I use the asp.asm.stock model?

Response: To use the asp.asm.stock model, you need to provide values for required fields: warehouse_id, company_id. Readonly fields: inv_ref, state, company_id, branch_id, domain_warehouse_id, product_ids, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


Describe the field structure of res.partner.rfm.segment.history.

Response: The res.partner.rfm.segment.history model has 16 fields: partner_id, history_date, old_rfm_segment_id, new_rfm_segment_id, old_rfm_score_id, new_rfm_score_id, old_segment_rank, new_segment_rank, engagement_direction, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 7, date: 1, integer: 4, char: 1, datetime: 3.


Show me the relational structure of report.dynamic_accounts_report.cash_flow.

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


Show me the relational structure of pos.gift.card.use.

Response: The pos.gift.card.use model has 5 relational fields: card_id -> pos.gift.card; customer_id -> res.partner; pos_order_id -> pos.order; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


Tell me about the access.group model.

Response: The access.group model represents Access Group in the ERP system. It contains 10 fields and is used to manage access group data. Key fields include: name, user_ids, access_management_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How does ir.cron relate to other models?

Response: The ir.cron model has 18 relational fields: ir_actions_server_id -> ir.actions.server; user_id -> res.users; create_uid -> res.users; write_uid -> res.users; model_id -> ir.model; child_ids -> ir.actions.server; crud_model_id -> ir.model; link_field_id -> ir.model.fields; fields_lines -> ir.server.object.lines; groups_id -> res.groups; mass_edit_line_ids -> mass.editing.line; partner_ids -> res.partner; channel_ids -> mail.channel; template_id -> mail.template; activity_type_id -> mail.activity.type; activity_user_id -> res.users; sms_template_id -> sms.template; binding_model_id -> ir.model. Many2many fields: child_ids, groups_id, partner_ids, channel_ids.


What operations can I perform on account.account.map.line?

Response: To use the account.account.map.line model, you need to provide values for required fields: map_id, child_company_id. Readonly fields: company_id, target_company, target_account, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


Describe the bve.view.line model in Odoo.

Response: The bve.view.line model represents BI View Editor Lines in the ERP system. It contains 27 fields and is used to manage bi view editor lines data. Key fields include: name, sequence, bve_view_id, model_id, model_name, table_alias, join_model_id, field_id, field_name, ttype, description, relation, join_node, left_join, row, column, measure, in_list, list_attr, view_field_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


List all fields in the stock.move model.

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


How does setu.rfm.score relate to other models?

Response: The setu.rfm.score model has 4 relational fields: rfm_segment_id -> setu.rfm.segment; partner_ids -> res.partner; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


Which fields in sh.payment.report.wizard are computed?

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


What operations can I perform on pos.promotion.discount.apply?

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


What business logic is in report.account.report_journal?

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


What data can be stored in base.geocoder?

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


What models are connected to mailing.list?

Response: The mailing.list model has 5 relational fields: contact_ids -> mailing.contact; subscription_ids -> mailing.contact.subscription; website_popup_ids -> website.mass_mailing.popup; create_uid -> res.users; write_uid -> res.users. Many2many fields: contact_ids.


What are the available fields for payment.icon?

Response: The payment.icon model has 11 fields: name, acquirer_ids, image, image_payment_form, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2many: 1, binary: 2, integer: 1, many2one: 2, datetime: 3.


Can you explain the purpose of sh.stock.move.text?

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


What are the technical details of vendor.pricelist.approval.matrix.line?

Response: The vendor.pricelist.approval.matrix.line model is defined in module: equip3_purchase_masterdata. It has 0 computed fields: . Stored computed fields: none.


What is the weight.scale.barcode.format model?

Response: The weight.scale.barcode.format model represents weight.scale.barcode.format in the ERP system. It contains 10 fields and is used to manage weight.scale.barcode.format data. Key fields include: name, line_ids, total_digit, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What fields does pos.promotion.specific.product have?

Response: The pos.promotion.specific.product model has 13 fields: active, type_apply, qty_free, product_id, product_ids, promotion_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 1, selection: 1, float: 1, many2one: 4, many2many: 1, integer: 1, char: 1, datetime: 3.


What are common use cases for report.sh_purchase_reports.sh_tv_top_vendors_doc?

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


What are the available fields for budget.budget?

Response: The budget.budget model has 31 fields: name, complete_name, parent_id, user_id, date_from, date_to, state, budget_budget_line, company_id, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, many2one: 6, date: 2, selection: 1, one2many: 4, boolean: 5, many2many: 2, integer: 5, datetime: 3.


How is budget.scurve used in the system?

Response: The budget.scurve model represents budget.scurve in the ERP system. It contains 33 fields and is used to manage budget.scurve data. Key fields include: name, budget_to_analyze, crossovered_budget, budgetary_position, period_start_date, period_end_date, crossovered_purchase_budget, product_purchase_budget, crossovered_acount_budget, acount_account_budget, project_id, job_cost_sheet, work_orders_ids, account_tag_ids, start_date, end_date, contract_amount, method, ks_chart_data, ks_graph_view, crossovered_budget_line_ids, purchase_budget_line_ids, acount_account_budget_ids, crossovered_budget_line_count, from_menu, budget_scurve_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What are common use cases for budget.budget.budget.line?

Response: To use the budget.budget.budget.line model, you need to provide values for required fields: budget_budget_id, date_from, date_to, planned_amount. Readonly fields: name, analytic_group_id, currency_id, practical_amount, theoritical_amount, percentage, company_id, is_above_budget, budget_budget_state, 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 web.environment.ribbon.backend?

Response: The web.environment.ribbon.backend model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.


What are the relationships in budget.scurve.line?

Response: The budget.scurve.line model has 3 relational fields: scurve_id -> budget.scurve; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


How is report.dynamic_accounts_report.general_ledger implemented technically?

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


What methods are available in pos.promotion.discount.category?

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


Can you explain the purpose of account.tax.map.sales.line?

Response: The account.tax.map.sales.line model represents Account Tax Map Sales Line in the ERP system. It contains 17 fields and is used to manage account tax map sales line data. Key fields include: company_id, sales_tax_id, target_company, target_sales_tax, map_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, line_ids, child_company_id, ownership, sales_line_ids, purchase_line_ids.


List all fields in the order.driver.message model.

Response: The order.driver.message model has 11 fields: order_id, message, send_to_driver, partner_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, char: 2, boolean: 1, integer: 1, datetime: 3.


What modules define crossovered.budget?

Response: The crossovered.budget model is defined in module: om_account_budget. It has 0 computed fields: . Stored computed fields: none.


How is report.sh_sale_reports.sh_sales_product_profit_doc implemented technically?

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


Can you explain the purpose of pos.promotion.discount.condition?

Response: The pos.promotion.discount.condition model represents Promotion discount condition in the ERP system. It contains 11 fields and is used to manage promotion discount condition data. Key fields include: active, product_id, minimum_quantity, promotion_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How is report.dynamic_accounts_report.cash_flow used in the system?

Response: The report.dynamic_accounts_report.cash_flow model represents Cash Flow Report in the ERP system. It contains 3 fields and is used to manage cash flow report data. Key fields include: id, display_name, __last_update.


What does the acrux.chat.message.wizard model represent?

Response: The acrux.chat.message.wizard model represents ChatRoom Message in the ERP system. It contains 20 fields and is used to manage chatroom message data. Key fields include: 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.


What are the relationships in multiple.rfq?

Response: The multiple.rfq model has 4 relational fields: vendor_ids -> res.partner; product_ids -> product.product; create_uid -> res.users; write_uid -> res.users. Many2many fields: vendor_ids, product_ids.


What modules define lost.product?

Response: The lost.product model is defined in module: equip3_sale_report. It has 0 computed fields: . Stored computed fields: none.


Describe the field structure of purchase.product.template.line.

Response: The purchase.product.template.line model has 14 fields: 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. Field types distribution: many2one: 6, char: 2, float: 2, integer: 1, datetime: 3.


What is the equip3.pos.membership.report model?

Response: The equip3.pos.membership.report model represents POS Membership Report in the ERP system. It contains 10 fields and is used to manage pos membership report data. Key fields include: name, member_code, company_id, date_joined, year_joined, member_point, total_order, id, display_name, __last_update.


Show me the fields of sale.adv.wizard.product.line.

Response: The sale.adv.wizard.product.line model has 13 fields: sale_adv_wizard_id, product_id, default_code, standard_price, uom_po_id, qty, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, char: 2, float: 2, integer: 1, datetime: 3.


How is pos.gift.card.exchange.history implemented technically?

Response: The pos.gift.card.exchange.history model is defined in module: equip3_pos_masterdata. It has 0 computed fields: . Stored computed fields: none.


Tell me about the assets.approval.matrix.line model.

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


Describe the many2many relations for assign.pr.line.wizard.

Response: The assign.pr.line.wizard model has 7 relational fields: wizard_id -> assign.pr.wizard; pr_line_id -> purchase.request.line; user_id -> res.users; new_user_id -> res.users; product_id -> product.product; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


How to create records in report.stock.demand?

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


What operations can I perform on warranty.renew?

Response: To use the warranty.renew model, you need to provide values for required fields: product_id, serial_no, partner_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


How to create records in intrawarehouse.transfer?

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


Describe the field structure of purchase.order.

Response: The purchase.order model has 266 fields: priority, origin, partner_ref, date_approve, dest_address_id, order_line, notes, invoice_count, invoice_ids, invoice_status, date_calendar_start, fiscal_position_id, payment_term_id, product_id, user_id, currency_rate, mail_reminder_confirmed, mail_reception_confirmed, receipt_reminder_email, reminder_date_before_receipt, team_id, report_grids, grid_product_tmpl_id, grid_update, grid, requisition_id, is_quantity_copy, incoterm_id, picking_count, picking_ids, picking_type_id, default_location_dest_id_usage, group_id, is_shipped, effective_date, on_time_rate, active, complete_state, custom_checklist_ids, custom_checklist, product_template_id, digital_sign, purchase_show_signature, chk_sign_confirm, purchase_show_enable_other_sign, sign_by, designation, sign_on, document_count, order_history_line, order_report_id, rfq_report_id, purchase_tag_ids, purchase_url, report_token, text_message, po_extract_id, po_split_id, po_extract_count, po_split_count, sh_fully_ship, sh_partially_ship, sh_fully_paid, sh_partially_paid, sh_hidden_compute_field, agreement_id, cancel_lines, selected_order, sh_msg, sh_po_number, sh_purchase_order_id, sh_revision_po_id, po_count, sh_purchase_revision_config, visible_eval, mrp_production_count, sale_order_count, internal_id, inter_transfer_count, client_order_id, discount_method, discount_amount, discount_amt, discount_amt_line, merged, sh_purchase_barcode_mobile, sh_purchase_bm_is_cont_scan, sh_sale_order_id, apply_manual_currency_exchange, manual_currency_exchange_rate, active_manual_currency_rate, total_invoices_amount, down_payment_by, amount, dp_journal_id, hide_create_bill, payment_status, down_payment_amount, total_down_payment_amount, is_down_payment, report_template_id1, report_template_id, amount_to_text, is_vendor_pricelist, name, currency_id, po_expiry_date, po, exp_po, sent, is_goods_orders, is_services_orders, is_hold_purchase_order, approval_matrix_id, is_approval_matrix, state1, po_state, approved_matrix_ids, is_approve_button, approval_matrix_line_id, analytic_account_group_ids, company_id, branch_id, destination_location_id, is_delivery_receipt, destination_warehouse_id, discount_type, is_single_delivery_destination, analytic_accounting, is_revision_po, is_revision_created, revision_order_id, custom_checklist_template_ids, readonly_price, timezone_date, request_partner_id, date_order_assets, name2, date_order, milestone_template_id, milestone_purchase_ids, is_group_good_services_order, have_product_service, swo_ids, swo_count, is_taxes, actual_progress, remaining_progress, progress_paid, paid_swo, partner_invoice_id, available_partner_invoice_ids, product_brand_ids, is_product_brand_filter, is_service_work_order, is_purchase_vendor_rating_warning, is_product_service_operation_receiving, is_service, show_analytic_tags, amount_untaxed, amount_tax, amount_total, discount_amt_before, discount_amt_line_before, amount_subtotal, tax_discount_policy, list_available_products, from_purchase_request, term_condition, term_condition_box, bo_count, blanket_ids, multilevel_disc, multi_discount, vendor_payment_terms, service_level_agreement_id, service_level_agreement_box, user_request_ids, vendor_invoice_documents_count, down_payment_discount_amount, tender_scope, is_submit_quotation, price_rating, not_editable, is_editable, tender_order_line, from_bo, is_btn_approval_matrix, state, is_blanket_cancel, open_tender, days_to_approve, purchase_order_duration_to_confirm, amount_saved_from_cost_savings, number_of_successful_cost_savings, partner_id, dp, journal_id, name_dp, direct_approval_matrix_id, is_approval_matrix_direct, approved_matrix_direct_ids, approved_matrix_direct_id, state_direct_on, state_direct_off, is_approve_button_direct, control, qty_limit, budget_limit, is_valid_coupon, applied_coupon_ids, generated_coupon_ids, no_code_promo_program_ids, code_promo_program_id, promo_code, client_order_ref, is_dropship, is_sale_order, customer_partner_id, customer_location_partner_id, branch_ids, is_assets_orders, import_reference, is_report_purchaseorder_printed, is_report_purchasequotation_printed, remark, rfq_type, discount_promotions_amount, date_planned, persentase_antar_badan, form_view_opened, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, access_url, access_token, access_warning, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: selection: 19, char: 30, datetime: 11, many2one: 49, one2many: 15, text: 5, integer: 19, many2many: 13, float: 21, boolean: 72, binary: 1, monetary: 7, html: 2, date: 2.


What are common use cases for approval.matrix.sale.order.lines?

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


Show me the relational structure of pos.config.

Response: The pos.config model has 97 relational fields: journal_id -> account.journal; invoice_journal_id -> account.journal; currency_id -> res.currency; iface_start_categ_id -> pos.category; selectable_categ_ids -> pos.category; sequence_id -> ir.sequence; sequence_line_id -> ir.sequence; session_ids -> pos.session; current_session_id -> pos.session; last_session_closing_cashbox -> account.bank.statement.cashbox; pricelist_id -> product.pricelist; available_pricelist_ids -> product.pricelist; allowed_pricelist_ids -> product.pricelist; company_id -> res.company; barcode_nomenclature_id -> barcode.nomenclature; tip_product_id -> product.product; fiscal_position_ids -> account.fiscal.position; default_fiscal_position_id -> account.fiscal.position; default_cashbox_id -> account.bank.statement.cashbox; payment_method_ids -> pos.payment.method; current_user_id -> res.users; rounding_method -> account.cash.rounding; discount_product_id -> product.product; employee_ids -> hr.employee; floor_ids -> restaurant.floor; printer_ids -> restaurant.printer; crm_team_id -> crm.team; group_pos_manager_id -> res.groups; group_pos_user_id -> res.groups; pos_receipt_template_id -> pos.receipt.template; weight_scale_barcode_format_id -> weight.scale.barcode.format; pos_config_cashbox_lines_ids -> account.cashbox.line; pos_config_cashbox_clsosing_line_ids -> account.cashbox.line; cashbox_lines_ids -> account.cashbox.line; pos_cashbox_lines_ids -> pos.account.cashbox.line; printer_id -> pos.epson; coupon_program_ids -> coupon.program; coupon_giftcard_ids -> coupon.program; user_id -> res.users; pos_allowed_return_category_ids -> pos.category; allow_pos_categories_out_of_stock -> pos.category; voucher_sequence_id -> ir.sequence; sync_to_pos_config_ids -> pos.config; internal_transfer_picking_type_id -> stock.picking.type; discount_ids -> pos.global.discount; return_method_id -> pos.payment.method; return_coupon_program_id -> coupon.program; payment_journal_ids -> account.journal; customer_default_id -> res.partner; multi_stock_operation_type_ids -> stock.picking.type; update_tax_ids -> account.tax; default_seller_id -> res.users; seller_ids -> res.users; qrcode_ids -> pos.qrcode; stock_location_ids -> stock.location; assigned_user_ids -> res.users; manager_ids -> res.users; stock_location_id -> stock.location; stock_location_dest_id -> stock.location; discount_global_id -> product.product; analytic_account_id -> account.analytic.account; iface_available_categ_ids -> pos.category; service_charge_ids -> pos.service.charge; assign_orders_to_config_ids -> pos.config; product_category_ids -> product.category; hidden_product_ids -> product.product; custom_sale_product_id -> product.product; multi_currency_ids -> res.currency; allowed_employee_ids -> hr.employee; fire_appetizer -> pos.category; fire_main_course -> pos.category; fire_dessert -> pos.category; promotion_ids -> pos.promotion; zone_id -> pos.zone; product_voucher_service_id -> product.product; product_coupon_service_id -> product.product; product_categ_ids -> pos.category; user_ids -> res.users; void_order_pin_ids -> res.users; void_order_line_pin_ids -> res.users; advertisement_image_ids -> advertisement.images; warehouse_id -> stock.warehouse; picking_type_id -> stock.picking.type; pos_branch_id -> res.branch; gift_card_account_id -> account.account; gift_card_product_id -> product.product; gift_payment_method_id -> pos.payment.method; cashbox_payment_method_id -> pos.payment.method; product_exchange_pin_ids -> res.users; select_shortcut -> pos.keyboard.shortcuts; pos_loyalty_id -> pos.loyalty; pos_loyalty_ids -> pos.loyalty; customer_deposit_account_id -> account.account; customer_deposit_reconcile_journal_id -> account.journal; analytic_group_ids -> account.analytic.tag; create_uid -> res.users; write_uid -> res.users. Many2many fields: selectable_categ_ids, available_pricelist_ids, allowed_pricelist_ids, fiscal_position_ids, payment_method_ids, employee_ids, printer_ids, coupon_program_ids, coupon_giftcard_ids, pos_allowed_return_category_ids, allow_pos_categories_out_of_stock, sync_to_pos_config_ids, discount_ids, payment_journal_ids, multi_stock_operation_type_ids, update_tax_ids, seller_ids, stock_location_ids, assigned_user_ids, manager_ids, iface_available_categ_ids, service_charge_ids, assign_orders_to_config_ids, product_category_ids, hidden_product_ids, multi_currency_ids, allowed_employee_ids, fire_appetizer, fire_main_course, fire_dessert, promotion_ids, product_categ_ids, user_ids, void_order_pin_ids, void_order_line_pin_ids, advertisement_image_ids, product_exchange_pin_ids, pos_loyalty_ids, analytic_group_ids.


What foreign keys exist in tax.adjustments.wizard?

Response: The tax.adjustments.wizard model has 8 relational fields: journal_id -> account.journal; debit_account_id -> account.account; credit_account_id -> account.account; tax_report_line_id -> account.tax.report.line; company_currency_id -> res.currency; report_id -> account.tax.report; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What foreign keys exist in sh.sale.category.wizard?

Response: The sh.sale.category.wizard model has 6 relational fields: sh_category_ids -> product.category; company_ids -> res.company; company_id -> res.company; category_order_dic -> user.order.dic; create_uid -> res.users; write_uid -> res.users. Many2many fields: sh_category_ids, company_ids.


How to query portal.wizard data?

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


What are the technical details of calendar.attendee?

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


How is portal.share used in the system?

Response: The portal.share model represents Portal Sharing in the ERP system. It contains 13 fields and is used to manage portal sharing data. Key fields include: res_model, res_id, partner_ids, note, share_link, access_warning, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What operations can I perform on asset.depreciation.confirmation.wizard?

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


What operations can I perform on target.kpi?

Response: To use the target.kpi model, you need to provide values for required fields: user_id, target_based_on_ids, from_date, to_date, target_on. Readonly fields: name, purchase_team_id, user_id, company_id, target_based_on_ids, main_target, from_date, to_date, target_on, target_left, kpi_progress, current_achievement, 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 account.move?

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


How is kitchen.safety.stock used in the system?

Response: The kitchen.safety.stock model represents Safety Stock Management in the ERP system. It contains 13 fields and is used to manage safety stock management data. Key fields include: name, company_id, is_branch_required, branch_id, warehouse_id, stock_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What are common use cases for account.payment.register.payment.difference.line?

Response: To use the account.payment.register.payment.difference.line model, you need to provide values for required fields: name, account_id, payment_amount, company_id. Readonly fields: currency_id, payment_difference, company_id, 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 pos.promotion.price?

Response: The pos.promotion.price model has 12 fields: active, product_id, minimum_quantity, price_down, promotion_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 1, many2one: 4, float: 2, integer: 1, char: 1, datetime: 3.


What is the res.users.identitycheck model?

Response: The res.users.identitycheck model represents Password Check Wizard in the ERP system. It contains 8 fields and is used to manage password check wizard data. Key fields include: password, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What modules define ks.sales.forecast?

Response: The ks.sales.forecast model is defined in module: ks_sales_forecast. It has 0 computed fields: . Stored computed fields: none.


What are common use cases for res.currency.rate?

Response: To use the res.currency.rate model, you need to provide values for required fields: name, currency_id. Readonly fields: currency_id, rate, 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 limit.request?

Response: The limit.request model has 66 fields: name, partner_id, limit_type, limit_type_old, limit_type_new, credit_amount, last_credit_limit, open_inv_no, last_open_inv_no, new_max_invoice, last_max_invoice, description, state, state1, state2, branch_id, limit_approval_matrix, approval_ids, approval_matrix_line_id, user_approval_ids, current_user, approval, approval2, new_amount, last_amount, is_approve_button, user_id, is_credit_limit_brand, product_brand_ids, brand_ids, company_id, 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, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 5, many2one: 15, selection: 8, float: 8, text: 1, one2many: 6, many2many: 4, boolean: 9, date: 2, integer: 5, datetime: 3.


Describe the field structure of base_import.tests.models.m2o.required.

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


Describe the assets.approval.matrix.line model in Odoo.

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


Show me the fields of product.public.category.

Response: The product.public.category model has 29 fields: name, parent_id, parent_path, child_id, parents_and_self, sequence, website_description, product_tmpl_ids, Minimum_amount, amount_footer, image_1920, image_1024, image_512, image_256, image_128, is_seo_optimized, website_meta_title, website_meta_description, website_meta_keywords, website_meta_og_img, seo_name, website_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 7, many2one: 4, one2many: 1, many2many: 2, integer: 4, html: 1, binary: 5, boolean: 1, text: 1, datetime: 3.


What models are connected to customer.voucher?

Response: The customer.voucher model has 7 relational fields: customer_id -> res.partner; customer_target_id -> customer.target; discount_line_product_id -> product.product; sale_order_line_ids -> sale.order.line; cashback_line_ids -> cashback.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


Tell me about the restaurant.printer model.

Response: The restaurant.printer model represents Restaurant Printer in the ERP system. It contains 12 fields and is used to manage restaurant printer data. Key fields include: name, proxy_ip, product_categories_ids, printer_type, epson_printer_ip, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What are common use cases for membership.invoice?

Response: To use the membership.invoice model, you need to provide values for required fields: product_id, member_price. 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 hr.employee?

Response: The hr.employee model has 32 relational fields: user_id -> res.users; user_partner_id -> res.partner; company_id -> res.company; address_home_id -> res.partner; country_id -> res.country; country_of_birth -> res.country; bank_account_id -> res.partner.bank; child_ids -> hr.employee; category_ids -> hr.employee.category; message_main_attachment_id -> ir.attachment; subordinate_ids -> hr.employee; currency_id -> res.currency; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; website_message_ids -> mail.message; department_id -> hr.department; job_id -> hr.job; address_id -> res.partner; resource_id -> resource.resource; resource_calendar_id -> resource.calendar; parent_id -> hr.employee; coach_id -> hr.employee; goal_ids -> gamification.goal; badge_ids -> gamification.badge.user; direct_badge_ids -> gamification.badge.user; create_uid -> res.users; write_uid -> res.users. Many2many fields: category_ids, message_partner_ids, message_channel_ids.


Show me the fields of x.report.wizard.

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


What foreign keys exist in res.branch?

Response: The res.branch model has 18 relational fields: analytic_tag_ids -> account.analytic.tag; company_id -> res.company; state_id -> res.country.state; country_id -> res.country; user_id -> res.users; user_ids -> res.users; config_ids -> pos.config; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: analytic_tag_ids, user_ids, message_partner_ids, message_channel_ids.


What does the repair.line model represent?

Response: The repair.line model represents Repair Line (parts) in the ERP system. It contains 26 fields and is used to manage repair line (parts) data. Key fields include: name, repair_id, company_id, currency_id, type, product_id, invoiced, price_unit, price_subtotal, tax_id, product_uom_qty, product_uom, product_uom_category_id, invoice_line_id, location_id, location_dest_id, move_id, lot_id, state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Describe the many2many relations for report.sh_sale_reports.sh_sale_details_report_doc.

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


What foreign keys exist in _unknown?

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


What foreign keys exist in mass.editing.wizard?

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


What fields does payment.link.wizard have?

Response: The payment.link.wizard model has 18 fields: res_model, res_id, amount, amount_max, currency_id, partner_id, partner_email, link, description, access_token, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 6, integer: 2, monetary: 2, many2one: 5, datetime: 3.


What is the account.multipayment model?

Response: The account.multipayment model represents Multipayment in the ERP system. It contains 90 fields and is used to manage multipayment data. Key fields include: name, partner_id, amount, journal_id, currency_id, date, ref, memo, line_credit_ids, line_debit_ids, diff_amount, partner_type, total_amount_credit, total_amount_debit, payment_id_count, company_id, branch_id, create_uid, create_date, different_move_id, request_partner_id, payment_method, multipul_payment_approval_matrix_id, is_multi_payment_approval_matrix, is_approve_button, approved_matrix_ids, approval_matrix_line_id, action_validate_boolean, action_draft_boolean, action_cancel_boolean, request_for_approval_boolean, action_approved_rp_boolean, rp_reject_boolean, state_boolean, state1_boolean, state2_boolean, difference_ids, payment_difference_amount, writeoff_account_id, writeoff_label, payment_type, clearing_account_id, move_id, due_date, receive_date, clearing_date, is_vendor, state, state1, state2, payment_ids, invoice_cutoff_date, is_cutoff_date, is_check_all, 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.


Show me the fields of account.automatic.entry.wizard.

Response: The account.automatic.entry.wizard model has 22 fields: action, move_data, preview_move_data, move_line_ids, date, company_id, company_currency_id, percentage, total_amount, journal_id, account_type, expense_accrual_account, revenue_accrual_account, destination_account_id, display_currency_helper, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: selection: 2, text: 2, many2many: 1, date: 1, many2one: 8, float: 1, monetary: 1, boolean: 1, integer: 1, char: 1, datetime: 3.


What models are connected to quotation.amount?

Response: The quotation.amount model has 4 relational fields: order_id -> sale.order; currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


List all fields in the auditlog.log.line model.

Response: The auditlog.log.line model has 25 fields: field_id, log_id, old_value, new_value, old_value_text, new_value_text, 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. Field types distribution: many2one: 8, text: 4, char: 7, integer: 2, selection: 1, datetime: 3.


What are the available fields for crossovered.budget.wizard?

Response: The crossovered.budget.wizard model has 8 fields: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 1, integer: 1, char: 1, many2one: 2, datetime: 3.


How to create records in sms.api?

Response: To use the sms.api 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 business logic is in kpi.period.value?

Response: To use the kpi.period.value model, you need to provide values for required fields: period_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 methods are available in account.incoterms?

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


Show me the fields of ir.autovacuum.

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


Describe the field structure of sale.report.

Response: The sale.report model has 45 fields: name, date, product_id, product_uom, product_uom_qty, qty_delivered, qty_to_invoice, qty_invoiced, partner_id, company_id, user_id, price_total, price_subtotal, untaxed_amount_to_invoice, untaxed_amount_invoiced, product_tmpl_id, categ_id, nbr, pricelist_id, analytic_account_id, team_id, country_id, industry_id, commercial_partner_id, weight, volume, discount, discount_amount, campaign_id, medium_id, source_id, order_id, warehouse_id, website_id, branch_id, state, margin, city_id, state_id, untaxed_amount, total_amount, grand_total_order, id, display_name, __last_update. Field types distribution: char: 2, datetime: 2, many2one: 22, float: 16, integer: 2, selection: 1.


Can you explain the purpose of warehouse.capacity.excel.report?

Response: The warehouse.capacity.excel.report model represents Warehouse Capacity Excel Report in the ERP system. It contains 9 fields and is used to manage warehouse capacity excel report data. Key fields include: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Show me the fields of ks_dashboard_ninja.child_board.

Response: The ks_dashboard_ninja.child_board model has 14 fields: name, ks_dashboard_ninja_id, ks_gridstack_config, ks_active, ks_dashboard_menu_name, board_type, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 4, many2one: 4, boolean: 1, selection: 1, integer: 1, datetime: 3.


Which fields in sale.report are computed?

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


How does account.cashbox.wizard relate to other models?

Response: The account.cashbox.wizard model has 5 relational fields: pos_session_id -> pos.session; line_ids -> account.cashbox.wizard.line; line_bank_ids -> account.cashbox.wizard.bank.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What modules define base.automation?

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


How is ks_to.do.description implemented technically?

Response: The ks_to.do.description model is defined in module: ks_dashboard_ninja. It has 0 computed fields: . Stored computed fields: none.


What modules define credit.note.product.lines?

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


What fields does setu.stock.movement.report have?

Response: The setu.stock.movement.report model has 19 fields: get_report_from_beginning, stock_file_data, start_date, end_date, upto_date, company_ids, product_category_ids, product_ids, warehouse_ids, company_id, is_product_daily, is_movement_daily, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 3, binary: 1, date: 3, many2many: 4, many2one: 3, integer: 1, char: 1, datetime: 3.


How to query mrp.quality.alert.report data?

Response: To use the mrp.quality.alert.report model, you need to provide values for required fields: date_from, date_to, stage_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.


Describe the field structure of report.stock.excel.

Response: The report.stock.excel model has 12 fields: datas, datas_fname, product_ids, categ_ids, location_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, char: 2, many2many: 3, integer: 1, many2one: 2, datetime: 3.


What are common use cases for kpi.item?

Response: To use the kpi.item model, you need to provide values for required fields: name, category_id, result_type, result_appearance. Readonly fields: formula_warning, all_parent_ids, measures_ids, constant_ids, kpi_ids, access_user_ids, edit_access_user_ids, help_notes, 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 mrp.bom.byproduct?

Response: The mrp.bom.byproduct model has 20 fields: product_id, company_id, product_qty, product_uom_id, bom_id, allowed_operation_ids, operation_id, allocated_cost, cost, operation_two_ids, operation_two_id, assembly_allocated_cost, kitchen_allocated_cost, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 8, float: 5, many2many: 2, integer: 1, char: 1, datetime: 3.


What data can be stored in res.partner.bank?

Response: The res.partner.bank model has 25 fields: active, acc_type, acc_number, sanitized_acc_number, acc_holder_name, partner_id, bank_id, bank_name, bank_bic, sequence, currency_id, company_id, journal_id, aba_routing, acc_holder_email, acc_holder_type, acc_holder_resident, acc_holder_address, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 1, selection: 3, char: 9, many2one: 6, integer: 2, one2many: 1, datetime: 3.


How does website.sale.payment.acquirer.onboarding.wizard relate to other models?

Response: The website.sale.payment.acquirer.onboarding.wizard model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What operations can I perform on sh.quality.alert?

Response: To use the sh.quality.alert model, you need to provide values for required fields: product_id, user_id, team_id. Readonly fields: name, 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 models are connected to crm.lost.reason?

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


How to query base.module.upgrade data?

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


Which fields in whatsapp.message.wizard are computed?

Response: The whatsapp.message.wizard model is defined in module: ss_whatsapp_connector. It has 0 computed fields: . Stored computed fields: none.


What are common use cases for res.users.apikeys?

Response: To use the res.users.apikeys model, you need to provide values for required fields: name, user_id. Readonly fields: name, user_id, scope, create_date, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.


What is the create.recurring.invoice model?

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


How does ks_dashboard_ninja.board_custom_filters relate to other models?

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.


What are the available fields for wizard.scrap.order.report?

Response: The wizard.scrap.order.report model has 13 fields: company_id, start_date, end_date, state, name, data, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, date: 2, selection: 1, char: 2, binary: 1, integer: 1, datetime: 3.


What are the relationships in report.equip3_crm_tracking.crm_sales_tracking_visit_report?

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


Show me the fields of receipt.payment.

Response: The receipt.payment model has 63 fields: name, partner_id, amount, journal_id, currency_id, clearing_account_id, move_id, date, payment_ref, memo, due_date, receive_date, clearing_date, company_id, branch_id, diff_amount, writeoff_acc_id, naration, create_uid, create_date, partner_type, line_credit_ids, line_debit_ids, state, total_amount_credit, total_amount_debit, payment_id_count, 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: char: 9, many2one: 16, monetary: 4, date: 3, datetime: 6, text: 2, selection: 4, one2many: 6, integer: 6, boolean: 5, many2many: 2.


What are common use cases for res.partner.title?

Response: To use the res.partner.title 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.


Describe the field structure of ks_dashboard_ninja.board_defined_filters.

Response: The ks_dashboard_ninja.board_defined_filters model has 16 fields: name, ks_dashboard_board_id, ks_model_id, ks_domain, ks_domain_temp, ks_model_name, display_type, sequence, ks_is_active, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 5, many2one: 4, selection: 1, integer: 2, boolean: 1, datetime: 3.


How do I use the sparse_fields.test model?

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


Describe the field structure of ks_dashboard_item.multiplier.

Response: The ks_dashboard_item.multiplier model has 11 fields: ks_dashboard_item_id, ks_model_id, ks_multiplier_value, ks_multiplier_fields, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, float: 1, integer: 1, char: 1, datetime: 3.


What data can be stored in wizard.vendor.deposit?

Response: The wizard.vendor.deposit model has 9 fields: reason, add_amount, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 1, boolean: 1, integer: 1, char: 1, many2one: 2, datetime: 3.


Show me the relational structure of ks_to.do.description.

Response: The ks_to.do.description model has 3 relational fields: ks_to_do_header_id -> ks_to.do.headers; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What business logic is in mr.approval.matrix?

Response: To use the mr.approval.matrix model, you need to provide values for required fields: name, company_id, warehouse_id. Readonly fields: company_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.


How is kitchen.production.record implemented technically?

Response: The kitchen.production.record model is defined in module: equip3_kitchen_operations. It has 0 computed fields: . Stored computed fields: none.


How is pos.order.log implemented technically?

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


What modules define sh.purchase.analysis.wizard?

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


Tell me about the portal.wizard model.

Response: The portal.wizard model represents Grant Portal Access in the ERP system. It contains 9 fields and is used to manage grant portal access data. Key fields include: user_ids, welcome_message, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What foreign keys exist in sh.report.section?

Response: The sh.report.section model has 4 relational fields: type_id -> sh.report.template; check_ids -> sh.edit.title; create_uid -> res.users; write_uid -> res.users. Many2many fields: check_ids.


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

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


What are common use cases for sh.tsp.top.purchasing.product?

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


What data can be stored in stock.lot.serialize.line?

Response: The stock.lot.serialize.line model has 13 fields: stock_move_id, sequence, move_id, product_id, demand_qty, qty_per_lot, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, char: 2, float: 1, integer: 2, datetime: 3.


What modules define report.account.report_hash_integrity?

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


What models are connected to crm.lead2opportunity.partner.mass?

Response: The crm.lead2opportunity.partner.mass model has 9 relational fields: lead_id -> crm.lead; lead_tomerge_ids -> crm.lead; user_ids -> res.users; duplicated_lead_ids -> crm.lead; partner_id -> res.partner; user_id -> res.users; team_id -> crm.team; create_uid -> res.users; write_uid -> res.users. Many2many fields: lead_tomerge_ids, user_ids, duplicated_lead_ids.


What are the available fields for report.sh_purchase_reports.sh_po_product_indent_doc?

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


What are the available fields for res.currency?

Response: The res.currency model has 51 fields: 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, display_rounding_warning, name, symbol, rate, conversion, rate_ids, rounding, decimal_places, active, position, date, currency_unit_label, currency_subunit_label, tax_rate_ids, tax_rate, tax_conversion, is_taxes_rate, company_id, converted_currency, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: one2many: 6, selection: 3, many2one: 6, char: 8, date: 3, boolean: 8, many2many: 2, integer: 6, float: 6, datetime: 3.


What models are connected to approval.matrix.purchase.order.line?

Response: The approval.matrix.purchase.order.line model has 7 relational fields: user_ids -> res.users; approval_matrix_purchase_order -> approval.matrix.purchase.order; approved_users -> res.users; last_approved -> res.users; order_id -> purchase.order; create_uid -> res.users; write_uid -> res.users. Many2many fields: user_ids, approved_users.


What operations can I perform on budget.scurve.line?

Response: To use the budget.scurve.line model, you need to provide values for required fields: none. Readonly fields: sr_no, contract_amount, method, 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 sale.excel.report.

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


How is sh.stock.move.text implemented technically?

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


How to query budget.purchase data?

Response: To use the budget.purchase model, you need to provide values for required fields: name, date_from, date_to, state, company_id. Readonly fields: state, state1, state2, approval_matrix, is_allowed_to_approval_matrix, approval_matrix_line_id, is_approve_button, currency_id, purchase_line_subtotal, date_today, is_use_theoretical_achievement, 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 modules define account.bank.statement.integrate?

Response: The account.bank.statement.integrate model is defined in module: equip3_accounting_bank_integration. It has 0 computed fields: . Stored computed fields: none.


Which fields in sh.purchase.bill.summary.wizard are computed?

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


What business logic is in account.payment.reconcile?

Response: To use the account.payment.reconcile model, you need to provide values for required fields: payment_type. Readonly fields: payment_type, partner_id, payment_amount, limit_amount, 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 base.module.upgrade model represent?

Response: The base.module.upgrade model represents Upgrade Module in the ERP system. It contains 8 fields and is used to manage upgrade module data. Key fields include: module_info, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Which fields in stock.day.average are computed?

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


What business logic is in stock.inventory.approval.matrix?

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.


Describe the portal.wizard.user model in Odoo.

Response: The portal.wizard.user model represents Portal User Config in the ERP system. It contains 14 fields and is used to manage portal user config data. Key fields include: wizard_id, partner_id, email, in_portal, user_id, is_customer, is_vendor, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Can you explain the purpose of product.warehouse.cost.wizard.line?

Response: The product.warehouse.cost.wizard.line model represents Product Warehouse Cost in the ERP system. It contains 12 fields and is used to manage product warehouse cost data. Key fields include: prod_wh_cost_id, warehouse_id, cost, company_id, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How is bo.request.matrix.reject implemented technically?

Response: The bo.request.matrix.reject model is defined in module: equip3_purchase_other_operation. It has 0 computed fields: . Stored computed fields: none.


What does the user.order.dic model represent?

Response: The user.order.dic model represents user.order.dic in the ERP system. It contains 20 fields and is used to manage user.order.dic data. Key fields include: report_id, list_order, saleperson, payment_report_id, list_pay, list_product, sale_analysis_id, prduct_profit_id, product, sale_categ_id, categ, product_indent_id, category_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What data can be stored in nsfp.registration?

Response: The nsfp.registration model has 15 fields: record_id, fiscal_year, start, end, last_number, registration_date, is_use, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 2, many2one: 4, char: 5, boolean: 1, datetime: 3.


How to query list.top.product data?

Response: To use the list.top.product 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 relationships in base_import.tests.models.o2m?

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.


Describe the field structure of ks.message.wizard.

Response: The ks.message.wizard model has 8 fields: name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 1, integer: 1, char: 1, many2one: 2, datetime: 3.


How is report.reordering implemented technically?

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


How is base.language.import used in the system?

Response: The base.language.import model represents Language Import in the ERP system. It contains 12 fields and is used to manage language import data. Key fields include: name, code, data, filename, overwrite, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What operations can I perform on approval.matrix.vendor.reject?

Response: To use the approval.matrix.vendor.reject 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 account.general.ledger model.

Response: The account.general.ledger model represents General Ledger Report in the ERP system. It contains 22 fields and is used to manage general ledger report data. Key fields include: journal_ids, account_ids, account_tag_ids, analytic_ids, analytic_tag_ids, display_account, titles, target_move, all_account, filter_detail, expand, date_from, date_to, report_currency_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What foreign keys exist in ir.actions.todo?

Response: The ir.actions.todo model has 3 relational fields: action_id -> ir.actions.actions; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


Can you explain the purpose of accounting.flow.wizard?

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


How to query pos.login.history data?

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


Can you explain the purpose of payment.acquirer.onboarding.wizard?

Response: The payment.acquirer.onboarding.wizard model represents Payment acquire onboarding wizard in the ERP system. It contains 19 fields and is used to manage payment acquire onboarding wizard data. Key fields include: payment_method, paypal_user_type, paypal_email_account, paypal_seller_account, paypal_pdt_token, stripe_secret_key, stripe_publishable_key, manual_name, journal_name, acc_number, manual_post_msg, _data_fetched, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What does the repair.order.make_invoice model represent?

Response: The repair.order.make_invoice model represents Create Mass Invoice (repair) in the ERP system. It contains 8 fields and is used to manage create mass invoice (repair) data. Key fields include: group, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Tell me about the warranty.tag model.

Response: The warranty.tag model represents Warranty Tag in the ERP system. It contains 9 fields and is used to manage warranty tag data. Key fields include: tag_name, tag_desc, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What are common use cases for report.stock.report_product_template_replenishment?

Response: To use the report.stock.report_product_template_replenishment 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.


Can you explain the purpose of qiscus.wa.template?

Response: The qiscus.wa.template model represents qiscus.wa.template in the ERP system. It contains 37 fields and is used to manage qiscus.wa.template data. Key fields include: name, namespace, qiscus_template_id, content_ids, category, 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 sh.purchase.payment.report.wizard?

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


Which fields in base_import.tests.models.m2o.required are computed?

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


List all fields in the res.partner.group model.

Response: The res.partner.group model has 13 fields: name, pricelist_applied, pricelist_id, image, height, width, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, boolean: 1, many2one: 3, binary: 1, integer: 3, datetime: 3.


How to query void.order.line data?

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


Show me the relational structure of mailing.trace.

Response: The mailing.trace model has 6 relational fields: mail_mail_id -> mail.mail; mass_mailing_id -> mailing.mailing; campaign_id -> utm.campaign; links_click_ids -> link.tracker.click; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


Show me the fields of acrux.chat.select.conversation.wizard.

Response: The acrux.chat.select.conversation.wizard model has 8 fields: conversation_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, integer: 1, char: 1, datetime: 3.


Show me the fields of pos.gift.card.use.

Response: The pos.gift.card.use model has 12 fields: card_id, customer_id, pos_order_id, order_date, amount, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, date: 1, float: 1, integer: 1, char: 1, datetime: 3.


What does the product.template.attribute.value model represent?

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


How does sale.adv.wizard.product.line.specific relate to other models?

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


What foreign keys exist in stock.lot.serialize?

Response: The stock.lot.serialize model has 4 relational fields: picking_id -> stock.picking; stock_move_line_ids -> stock.lot.serialize.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What business logic is in sh.purchase.category.xls?

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


What are common use cases for customer.category?

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


What fields does account.tax.report.line have?

Response: The account.tax.report.line model has 18 fields: tag_ids, report_action_id, children_line_ids, parent_id, sequence, parent_path, report_id, code, formula, name, tag_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2many: 1, many2one: 5, one2many: 1, integer: 2, char: 6, datetime: 3.


What are common use cases for ir.actions.server?

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


What are common use cases for approval.matrix.blanket.order?

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


List all fields in the export.product.csv model.

Response: The export.product.csv model has 40 fields: name, product_id_attachment_id, product_id_csv_created, 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, sequence_prefix, sequence_number, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 8, many2one: 6, boolean: 6, one2many: 4, selection: 2, date: 2, many2many: 2, integer: 6, text: 1, datetime: 3.


What models are connected to purchase.custom.checklist.template?

Response: The purchase.custom.checklist.template model has 3 relational fields: checklist_template -> purchase.custom.checklist; create_uid -> res.users; write_uid -> res.users. Many2many fields: checklist_template.


How do I use the iap.account model?

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


How is replace.product.wizard used in the system?

Response: The replace.product.wizard model represents Replace Product in the ERP system. It contains 11 fields and is used to manage replace product data. Key fields include: product_id, replace_product_id, replace_qty, is_same_product, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Describe the ir.actions.actions model in Odoo.

Response: The ir.actions.actions model represents Actions in the ERP system. It contains 14 fields and is used to manage actions data. Key fields include: name, type, xml_id, help, binding_model_id, binding_type, binding_view_types, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What methods are available in link.tracker?

Response: The link.tracker model is defined in module: link_tracker. It has 0 computed fields: . Stored computed fields: none.


How is internal.transfer.line implemented technically?

Response: The internal.transfer.line model is defined in module: equip3_inventory_operation. It has 0 computed fields: . Stored computed fields: none.


What are the technical details of snailmail.confirm.invoice?

Response: The snailmail.confirm.invoice model is defined in module: snailmail_account. It has 0 computed fields: . Stored computed fields: none.


Which fields in stock.valuation.layer.revaluation are computed?

Response: The stock.valuation.layer.revaluation model is defined in module: stock_account. It has 0 computed fields: . Stored computed fields: none.