How do I use the product.product model?

Response: To use the product.product model, you need to provide values for required fields: product_tmpl_id, name, uom_id, uom_po_id, product_variant_ids, tracking, purchase_line_warn, sale_line_warn, type. Readonly fields: price_extra, code, partner_ref, combination_indices, is_product_variant, pricelist_item_count, image_variant_1024, image_variant_512, image_variant_256, image_variant_128, can_image_variant_1024_be_zoomed, image_1024, image_512, image_256, image_128, can_image_1024_be_zoomed, sh_qr_code_img, qty_available, virtual_available, free_qty, incoming_qty, outgoing_qty, nbr_reordering_rules, reordering_min_qty, reordering_max_qty, image_chat, bom_count, used_in_bom_count, mrp_product_qty, date_from, date_to, invoice_state, sale_avg_price, purchase_avg_price, sale_num_invoiced, purchase_num_invoiced, sales_gap, purchase_gap, turnover, total_cost, sale_expected, normal_cost, total_margin, expected_margin, total_margin_rate, expected_margin_rate, purchased_product_qty, value_svl, quantity_svl, valuation, cost_method, product_cost_ids, sales_count, purchase_price_history_line_ids, website_url, near_expire, expired, id, warranty_sale_config, cart_qty, is_generate_product, category_prefix_preference, is_secret_product, variant_short_name, is_variants, purchase_price, purchase_price_totals, assembly_inventory_quantity, assembly_safety_stock_qty, assembly_to_produce_qty, assembly_outgoing_qty, product_display_name, kitchen_inventory_quantity, kitchen_safety_stock_qty, kitchen_to_produce_qty, kitchen_outgoing_qty, is_pos_bom, purchase_req_line_ids, is_gift_product, warehouse_price_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, display_name, create_uid, create_date, write_uid, write_date, __last_update, currency_id, cost_currency_id, volume_uom_name, weight_uom_name, uom_name, valid_product_template_attribute_line_ids, product_variant_id, product_variant_count, has_configurable_attributes, rating_last_value, rating_last_feedback, rating_last_image, rating_count, rating_avg, has_available_route_ids, is_seo_optimized, can_publish, categ_costing_method, visible_expense_policy, visible_qty_configurator, brand_attribute_id, company_id_domain, group_stock_ids, reordering_rules_ids, hide, brand_setting, uom_categ_id, is_approve, template_purchase_price_history_line_ids, is_vendor_pricelist, is_from_assembly, url_pic, is_from_kitchen, combo_option_items, uom_ids, is_cost_per_warehouse. The model supports standard CRUD operations through the ORM.


How is report_excel_gen implemented technically?

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


How is ir.actions.server implemented technically?

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


Which fields in report.equip3_accounting_reports.cash_flow_statement are computed?

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


How is base_import.tests.models.m2o used in the system?

Response: The base_import.tests.models.m2o model represents Tests : Base Import Model, Many to One in the ERP system. It contains 8 fields and is used to manage tests : base import model, many to one data. Key fields include: value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How is stock.move.line used in the system?

Response: The stock.move.line model represents Product Moves (Stock Move Line) in the ERP system. It contains 64 fields and is used to manage product moves (stock move line) data. Key fields include: picking_id, move_id, company_id, product_id, product_uom_id, product_uom_category_id, product_qty, product_uom_qty, qty_done, package_id, package_level_id, lot_id, lot_name, date, owner_id, location_id, location_dest_id, lots_visible, picking_code, picking_type_use_create_lots, picking_type_use_existing_lots, state, is_initial_demand_editable, is_locked, consume_line_ids, produce_line_ids, reference, tracking, origin, picking_type_entire_packs, description_picking, workorder_id, production_id, expiration_date, scrap_return_move_id, is_double_product_usage, sale_price, sequence, move_line_sequence, product_type, quant_package_ids, result_package_id, is_quant_update, force_to_reserve_qty, source_picking_id, source_move_id, is_batch_shipping_packing, is_batch_shipping_delivery, assembly_id, scrap_sale_price, is_low_stock, description, kitchen_id, finish_good_rework_id, exp_date, remark, pos_branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What business logic is in internal.transfer?

Response: To use the internal.transfer model, you need to provide values for required fields: requested_by, scheduled_date. Readonly fields: name, source_document, state1, state2, state3, operation_type_in_id, operation_type_out_id, operation_count, internal_transfer_line_total, itr_approval_matrix_id, is_itr_approval_matrix, approved_matrix_ids, approval_matrix_line_id, is_approve_button, is_reset_to_draft, is_product_lines, company_id, filter_source_warehouse_id, filter_destination_warehouse_id, get_warehouse, is_mbs_on_transfer_operations, branch_id, domain_warehouse_source_id, domain_warehouse_destination_id, sh_it_bm_is_cont_scan, source_location_id, destination_location_id, create_date, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, access_url, access_warning, id, display_name, create_uid, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


How to create records in hr.plan.activity.type?

Response: To use the hr.plan.activity.type model, you need to provide values for required fields: responsible. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


What are common use cases for invoice.template.table?

Response: To use the invoice.template.table model, you need to provide values for required fields: template_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 does the res.partner.rfm.segment.history model represent?

Response:
The res.partner.rfm.segment.history model represents
    Customer RFM segment history table will automatically add records in the table when the customer RFM score will be changed to another one and if the segment value has been changed
     in the ERP system. It contains 16 fields and is used to manage
    customer rfm segment history table will automatically add records in the table when the customer rfm score will be changed to another one and if the segment value has been changed
     data. Key fields include: 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.


Describe the many2many relations for stock.warn.insufficient.qty.repair.

Response: The stock.warn.insufficient.qty.repair model has 6 relational fields: repair_id -> repair.order; product_id -> product.product; location_id -> stock.location; quant_ids -> stock.quant; create_uid -> res.users; write_uid -> res.users. Many2many fields: quant_ids.


How to query pos.order.line.promotion data?

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


List all fields in the store.filters.groups model.

Response: The store.filters.groups model has 11 fields: model_id, node_option, attribute_name, attribute_string, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, selection: 1, char: 3, integer: 1, datetime: 3.


Describe the report.equip3_accounting_reports.cash_flow_statement model in Odoo.

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


What foreign keys exist in purchase.team.analysis?

Response: The purchase.team.analysis model has 5 relational fields: user_id -> res.users; purchase_ids -> purchase.order; branch_id -> res.branch; create_uid -> res.users; write_uid -> res.users. Many2many fields: purchase_ids.


Describe the field structure of res.company.

Response: The res.company model has 428 fields: name, sequence, child_ids, report_header, report_footer, logo, logo_web, user_ids, street2, zip, city, state_id, bank_ids, country_id, website, paperformat_id, external_report_layout_id, base_onboarding_company_state, favicon, font, primary_color, secondary_color, nomenclature_id, resource_calendar_ids, resource_calendar_id, catchall_email, catchall_formatted, email_formatted, hr_presence_control_email_amount, hr_presence_control_ip_list, kpi_history_tolerance, show_kpi_help, 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, company_name_logo, enable_menu_search, enable_web_push_notification, api_key, vapid, config_details, sh_multi_barcode_unique, message_has_sms_error, snailmail_color, snailmail_cover, snailmail_duplex, sh_product_stock, sh_product_attribute, sh_product_image, sh_product_category, sh_product_code, sh_product_barcode, sh_product_sale_price, sh_product_sale_description, sh_touch_kyboard, sh_welcome_message, sh_message, sh_company_logo, sh_display, sh_display_view, sh_display_landscape, sh_display_portrait, sh_delay_screen, fiscalyear_last_day, fiscalyear_last_month, period_lock_date, fiscalyear_lock_date, tax_lock_date, transfer_account_id, expects_chart_of_accounts, chart_template_id, bank_account_code_prefix, cash_account_code_prefix, default_cash_difference_income_account_id, default_cash_difference_expense_account_id, account_journal_suspense_account_id, transfer_account_code_prefix, account_sale_tax_id, account_purchase_tax_id, tax_calculation_rounding_method, currency_exchange_journal_id, income_currency_exchange_account_id, expense_currency_exchange_account_id, anglo_saxon_accounting, property_stock_account_input_categ_id, property_stock_account_output_categ_id, property_stock_valuation_account_id, bank_journal_ids, tax_exigibility, account_tax_fiscal_country_id, incoterm_id, qr_code, invoice_is_email, invoice_is_print, account_opening_move_id, account_opening_journal_id, account_opening_date, account_setup_bank_data_state, account_setup_fy_data_state, account_setup_coa_state, account_onboarding_invoice_layout_state, account_onboarding_create_invoice_state, account_onboarding_sale_tax_state, account_invoice_onboarding_state, account_dashboard_onboarding_state, invoice_terms, account_setup_bill_state, account_default_pos_receivable_account_id, expense_accrual_account_id, revenue_accrual_account_id, automatic_entry_default_journal_id, country_code, tax_cash_basis_journal_id, account_cash_basis_base_account_id, internal_transit_location_id, stock_move_email_validation, stock_mail_confirmation_template_id, website_theme_onboarding_done, account_check_printing_layout, account_check_printing_date_label, account_check_printing_multi_stub, account_check_printing_margin_top, account_check_printing_margin_left, account_check_printing_margin_right, account_bank_reconciliation_start, vat_check_vies, picking_operation_type, sh_it_barcode_mobile_type, sh_it_bm_is_cont_scan, sh_it_bm_is_notify_on_success, sh_it_bm_is_notify_on_fail, sh_it_bm_is_sound_on_success, sh_it_bm_is_sound_on_fail, sh_it_bm_is_add_product, project_time_mode_id, timesheet_encode_uom_id, manufacturing_lead, payment_acquirer_onboarding_state, payment_onboarding_payment_method, po_lead, po_lock, po_double_validation, po_double_validation_amount, sh_invoice_online_signature, sh_enable_approval, sh_restrict_for_close_period, invoice_is_snailmail, stock_move_sms_validation, stock_sms_confirmation_template_id, has_received_warning_stock_sms, account_edi_proxy_client_ids, inv_cost, point_of_sale_update_stock_quantities, days_to_purchase, portal_confirmation_sign, portal_confirmation_pay, quotation_validity_days, sale_quotation_onboarding_state, sale_onboarding_order_confirmation_state, sale_onboarding_sample_quotation_state, sale_onboarding_payment_method, po_operation_type, cancel_receipt, cancel_bill, purchase_show_signature, chk_sign_confirm, purchase_enable_other_sign_option, sh_expiry_notification, sh_is_notify_vendor, sh_on_date_notify, enter_before_first_notify, enter_before_second_notify, enter_before_third_notify, enter_after_first_notify, enter_after_second_notify, enter_after_third_notify, attachment_email, sh_pmps_pro_field_ids, sh_pmps_pro_attr_ids, sh_purchase_configuration_limit, item_limit_purchase, record_based_on_purchase, purchase_order_information_in_message, purchase_product_detail_in_message, purchase_signature, purchase_display_in_message, po_send_pdf_in_message, sh_auto_add_followers, sh_portal_user_create, sh_tender_document_manage, sh_purchase_revision, sale_order_template_id, security_lead, sh_manage_tender_doc_portal, lc_journal_id, website_sale_onboarding_payment_acquirer_state, intercompany_warehouse_id, validate_picking, create_invoice, validate_invoice, allow_auto_intercompany, use_sale_order_note, sale_order_note, keep_name_so, sh_sale_bm_is_cont_scan, sh_sale_bm_is_notify_on_success, sh_sale_bm_is_notify_on_fail, sh_sale_bm_is_sound_on_success, sh_sale_bm_is_sound_on_fail, sh_purchase_barcode_mobile_type, sh_purchase_bm_is_cont_scan, sh_purchase_bm_is_notify_on_success, sh_purchase_bm_is_notify_on_fail, sh_purchase_bm_is_sound_on_success, sh_purchase_bm_is_sound_on_fail, sh_invoice_barcode_mobile_type, sh_invoice_bm_is_cont_scan, sh_invoice_bm_is_notify_on_success, sh_invoice_bm_is_notify_on_fail, sh_invoice_bm_is_sound_on_success, sh_invoice_bm_is_sound_on_fail, sh_bom_barcode_mobile_type, sh_bom_bm_is_cont_scan, sh_bom_bm_is_notify_on_success, sh_bom_bm_is_notify_on_fail, sh_bom_bm_is_sound_on_success, sh_bom_bm_is_sound_on_fail, sh_stock_barcode_mobile_type, sh_stock_bm_is_cont_scan, sh_stock_bm_is_notify_on_success, sh_stock_bm_is_notify_on_fail, sh_stock_bm_is_sound_on_success, sh_stock_bm_is_sound_on_fail, sh_stock_bm_is_add_product, sh_inventory_adjt_barcode_mobile_type, sh_inventory_adjt_bm_is_cont_scan, sh_inventory_adjt_bm_is_notify_on_success, sh_inventory_adjt_bm_is_notify_on_fail, sh_inventory_adjt_bm_is_sound_on_success, sh_inventory_adjt_bm_is_sound_on_fail, sh_product_barcode_mobile_type, sh_product_bm_is_cont_scan, sh_product_bm_is_notify_on_success, sh_product_bm_is_notify_on_fail, sh_product_bm_is_sound_on_success, sh_product_bm_is_sound_on_fail, sh_product_bm_is_default_code, sh_product_bm_is_lst_price, sh_product_bm_is_qty_available, sh_product_bm_is_virtual_available, sh_global_document_search_is_enable, sh_global_document_search_is_sale, sh_global_document_search_is_purchase, sh_global_document_search_is_picking, sh_global_document_search_is_invoice, sh_global_document_search_is_product, sh_global_document_search_is_lot, sh_global_document_search_is_location, sh_global_document_search_action_target_type, sale_credit_limit_email_alerts, sale_email_specific_user_id, quot_to_po, so_to_po, down_payment_product_id, implementor_setting, general, purchase, sales, inventory, manufacturing, central_kitchen, human_resource, pos, simple_manufacturing, assembly, cutting, mining, agriculture, show_branch, branch_ids, theme_color, theme_text_color, text_color, company_color, customer_color, company_address_color, customer_address_color, odd_party_color, even_party_color, report_template_id1, report_template_id, report_sale_template_id1, report_sale_template_id, report_po_template_id1, report_po_template_id, report_rfq_template_id, report_delivery_template_id1, report_delivery_template_id, report_picking_template_id, invoice_logo, is_description, watermark_logo, is_company_bold, is_customer_bold, standard_template, add_product_image, add_amount_in_words, is_show_watermark, watermark, watermark_text, watermark_text_color, watermark_text_font_size, report_footer_selection, font_id, font_size, is_show_signature, signature, logo_footer, is_show_bank_details, report_bank_id, is_show_notes, is_show_payment_notes, is_show_payment_description, is_show_barcode, is_inverse_rate, is_taxes_rate, unrealized_exchange_journal_id, income_unrealized_exchange_account_id, expense_unrealized_exchange_account_id, tax_discount_policy, sale_account_id, purchase_account_id, interest_income, interest_expense, deposit_account_id, post_discount_account, partner_id, street, phone, email, vat, company_registry, currency_id, parent_id, social_twitter, social_facebook, social_github, social_linkedin, social_youtube, social_instagram, city_id, manufacturing_plan_conf, manufacturing_order_conf, mrp_plan_partial_availability, production_record_conf, mrp_production_partial_availability, mrp_submit_purchase_request, mrp_submit_material_request, mrp_force_done, mo_force_done, mo_auto_reserve_availability_materials, mp_auto_reserve_availability_materials, send_wa_approval_notification_mrp, send_wa_approval_notification_mp, send_wa_approval_notification_mpr, manufacturing_mps, manufacturing_period, manufacturing_period_to_display, sh_sale_barcode_mobile_type, accounting, bom_tools, company_delivery_rate, company_delivery_product, mr_show_analytic_account, brand_setting, short_name, is_message_rn, send_notification_users_ids, pjap_x_token, npwp, is_centralized_efaktur, sh_sale_pro_field_ids, sh_sale_pro_attr_ids, product_pricelist_default, owner, report_pr_template_id, contact_address, is_order_rounding, order_rounding_type, rounding_multiplier, apply_rounding_type, rounding_method_id, pos_def_receipt_template_id, is_pos_receivable, pos_product_discount1_id, is_post_closing_cashbox_value_in_session, is_pos_use_deposit, membership_pluspoint_rounding, membership_pluspoint_rounding_type, membership_pluspoint_rounding_multiplier, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 50, integer: 22, one2many: 10, text: 5, binary: 8, many2many: 8, many2one: 74, selection: 53, boolean: 179, date: 7, float: 8, monetary: 1, datetime: 3.


What does the purchase.agreement model represent?

Response: The purchase.agreement model represents Purchase Agreement in the ERP system. It contains 100 fields and is used to manage purchase agreement data. Key fields include: name, rfq_count, order_count, sh_vender_id, user_id, sh_agreement_deadline, sh_source, sh_purchase_agreement_line_ids, compute_custom_boolean, sh_manage_tender_document, document_count, is_goods_orders, is_services_orders, purchase_request_id, sh_purchase_user_id, sh_agreement_type, partner_ids, days_left, analytic_accounting, account_tag_ids, branch_id, destination_warehouse_id, set_single_delivery_destination, set_single_delivery_date, comparison_ids, tender_scope, tender_name, company_id, currency_id, amount_total, is_price_ratting_rfq_tender, show_analytic_tags, sh_order_date, sh_delivery_date, state, state1, state4, state2, pt_state, state3, state5, approval_matrix, amount, approval_matrix_line_ids, user_approval_ids, current_user, partner_id, approver, line_approve, is_approve_button, approval_matrix_line_id, sh_bid_agreement_deadline, sh_bid_selection_agreement_deadline, is_purchase_tender_approval_matrix, term_condition, term_condition_box, sh_notes, sh_partner_id, vendor_names, purchase_order_ids, is_assets_orders, legal_documents_ids, campaign_id, source_id, medium_id, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, access_url, access_token, access_warning, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


List all fields in the salesperson.tracking.history model.

Response: The salesperson.tracking.history model has 11 fields: name, marker, history_data, tracking_history_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, binary: 1, html: 1, many2one: 3, integer: 1, datetime: 3.


What does the report.membership model represent?

Response: The report.membership model represents Membership Analysis in the ERP system. It contains 17 fields and is used to manage membership analysis data. Key fields include: start_date, date_to, num_waiting, num_invoiced, num_paid, tot_pending, tot_earned, partner_id, associate_member_id, membership_id, membership_state, user_id, company_id, quantity, id, display_name, __last_update.


Show me the fields of ir.server.object.lines.

Response: The ir.server.object.lines model has 12 fields: server_id, col1, value, evaluation_type, resource_ref, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, text: 1, selection: 1, reference: 1, integer: 1, char: 1, datetime: 3.


What fields does pos.loyalty have?

Response: The pos.loyalty model has 24 fields: name, rule_ids, reward_ids, product_redeem_ids, reward_redeem_ids, count_product_redeem, state, type, product_loyalty_id, rounding, rounding_down, config_ids, pos_config_ids, period_expired, start_date, end_date, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, one2many: 5, integer: 3, selection: 2, many2one: 4, float: 1, boolean: 1, many2many: 1, datetime: 5.


Describe the purchase.request.warning.line model in Odoo.

Response: The purchase.request.warning.line model represents Purchase Request Line Warning in the ERP system. It contains 11 fields and is used to manage purchase request line warning data. Key fields include: warning_id, product_id, purchase_req_budget, realized_amount, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


List all fields in the kpi.period.value model.

Response: The kpi.period.value model has 10 fields: period_id, constant_id, target_value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, float: 1, integer: 1, char: 1, datetime: 3.


Show me the fields of payment.voucher.

Response: The payment.voucher model has 63 fields: create_by, name, partner_id, partner_ids, date, bank_id, cheque_number, cheque_date, vendor_bill_ids, remarks, company_id, request_partner_id, currency_id, line_ids, branch_id, state, amount, amount_text, payment_ids, payment_count, approval_matrix_id, is_payment_voucher_approval_matrix, approved_matrix_ids, approval_matrix_line_id, is_approve_button, state1, state2, amount_to_text, invoice_cutoff_date, vendor_allowed_ids, is_cutoff_date, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 14, char: 8, many2many: 5, date: 5, text: 1, one2many: 7, selection: 5, monetary: 1, integer: 6, boolean: 8, datetime: 3.


What are the relationships in report.reordering?

Response: The report.reordering model has 4 relational fields: warehouse_id -> stock.warehouse; location_ids -> stock.location; create_uid -> res.users; write_uid -> res.users. Many2many fields: location_ids.


How is customer.target used in the system?

Response: The customer.target model represents Customer Target in the ERP system. It contains 32 fields and is used to manage customer target data. Key fields include: name, res_name, company_id, applied_to, customer_categ_id, partner_ids, target_amount, currency_id, start_date, end_date, reward_type, disc_type, disc_amount, disc_percentage, product_id, quantity, discount_line_product_id, customer_voucher_ids, customer_voucher_count, apply_cashback, percentage, fixed_amount, voucher_type, voucher_expiration, free_product_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Can you explain the purpose of pos.top.selling.wizard?

Response: The pos.top.selling.wizard model represents POS Top Selling Wizard in the ERP system. It contains 14 fields and is used to manage pos top selling wizard data. Key fields include: start_dt, end_dt, report_type, no_product, top_selling, branch_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Which fields in multiple.rfq are computed?

Response: The multiple.rfq model is defined in module: equip3_purchase_operation. It has 0 computed fields: . Stored computed fields: none.


How is sms.api used in the system?

Response: The sms.api model represents SMS API in the ERP system. It contains 3 fields and is used to manage sms api data. Key fields include: id, display_name, __last_update.


What models are connected to mail.message.subtype?

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


What modules define sh_barcode_scanner_adv.search.document?

Response: The sh_barcode_scanner_adv.search.document model is defined in module: sh_all_in_one_mbs. It has 0 computed fields: . Stored computed fields: none.


What fields does account.vendor.deposit.reconcile have?

Response: The account.vendor.deposit.reconcile model has 9 fields: date, allocation_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: date: 1, one2many: 1, integer: 1, char: 1, many2one: 2, datetime: 3.


What business logic is in sh.custom.tab.purchase?

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


How is payment.voucher.matrix.reject used in the system?

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


What are the relationships in web.environment.ribbon.backend?

Response: The web.environment.ribbon.backend model has no explicit relational fields defined in its field metadata.


What are common use cases for auditlog.autovacuum?

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


How does mrp.production relate to other models?

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


How do I use the sale.order.template.line model?

Response: To use the sale.order.template.line model, you need to provide values for required fields: sale_order_template_id, name, product_uom_qty. Readonly fields: company_id, product_uom_category_id, 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 sale.data.margin.line?

Response: To use the sale.data.margin.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.


Which fields in pos.loyalty.reward are computed?

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


What are the available fields for res.config.settings?

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


What does the res.branch model represent?

Response: The res.branch model represents Branch of shops, like a multi company in the ERP system. It contains 50 fields and is used to manage branch of shops, like a multi company data. Key fields include: analytic_tag_ids, name, company_id, telephone, address, street, street_2, city, state_id, country_id, zip_code, active_company_sequence, npwp, user_id, user_ids, is_external_link, config_ids, branch_code, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What does the stock.picking.batch.line model represent?

Response: The stock.picking.batch.line model represents stock.picking.batch.line in the ERP system. It contains 18 fields and is used to manage stock.picking.batch.line data. Key fields include: sequence, transfer_id, product_id, name, location_id, demand_qty, reserved_qty, done_qty, uom_id, picking_batch_id, origin, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Show me the relational structure of gamification.karma.tracking.

Response: The gamification.karma.tracking model has 3 relational fields: user_id -> res.users; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


List all fields in the allfresh.consignment.report model.

Response: The allfresh.consignment.report model has 15 fields: date_order, pos_ref, pos_branch_id, barcode, product_id, qty, price, margin, total_margin, consignment_move_id, currency_id, company_id, id, display_name, __last_update. Field types distribution: datetime: 2, char: 3, many2one: 5, float: 1, monetary: 3, integer: 1.


Describe the implementation of account.print.journal.

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


What are the technical details of stock.package_level?

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


What foreign keys exist in stock.move?

Response: The stock.move model has 92 relational fields: company_id -> res.company; product_uom -> uom.uom; product_uom_category_id -> uom.category; product_tmpl_id -> product.template; location_id -> stock.location; location_dest_id -> stock.location; partner_id -> res.partner; move_dest_ids -> stock.move; move_orig_ids -> stock.move; picking_partner_id -> res.partner; backorder_id -> stock.picking; scrap_ids -> stock.scrap; group_id -> procurement.group; rule_id -> stock.rule; picking_type_id -> stock.picking.type; inventory_id -> stock.inventory; move_line_ids -> stock.move.line; move_line_nosuggest_ids -> stock.move.line; origin_returned_move_id -> stock.move; returned_move_ids -> stock.move; restrict_partner_id -> res.partner; route_ids -> stock.location.route; warehouse_id -> stock.warehouse; package_level_id -> stock.package_level; orderpoint_id -> stock.warehouse.orderpoint; lot_ids -> stock.production.lot; created_production_id -> mrp.production; production_id -> mrp.production; raw_material_production_id -> mrp.production; unbuild_id -> mrp.unbuild; consume_unbuild_id -> mrp.unbuild; allowed_operation_ids -> mrp.routing.workcenter; operation_id -> mrp.routing.workcenter; workorder_id -> mrp.workorder; bom_line_id -> mrp.bom.line; byproduct_id -> mrp.bom.byproduct; order_finished_lot_ids -> stock.production.lot; account_move_ids -> account.move; stock_valuation_layer_ids -> stock.valuation.layer; scrap_return_move_id -> stock.move.line; purchase_line_id -> purchase.order.line; created_purchase_line_id -> purchase.order.line; sh_quality_point_id -> sh.qc.point; created_purchase_request_line_id -> purchase.request.line; purchase_request_allocation_ids -> purchase.request.allocation; purchase_request_ids -> purchase.request; requisition_line_ids -> purchase.requisition.line; sale_line_id -> sale.order.line; branch_id -> res.branch; repair_id -> repair.order; product_id -> product.product; move_package_id -> stock.quant.package; filter_move_package_ids -> stock.quant.package; mr_line_id -> material.request.line; analytic_account_group_ids -> account.analytic.tag; responsible -> res.users; package_type -> product.packaging; packaging_ids -> product.packaging; package_quant_ids -> stock.quant; measure_ids -> measure.for.packaging; source_picking_id -> stock.picking; source_move_id -> stock.move; created_assembly_id -> assembly.production.record; assembly_finished_id -> assembly.production.record; assembly_component_id -> assembly.production.record; created_kitchen_id -> kitchen.production.record; kitchen_finished_id -> kitchen.production.record; kitchen_component_id -> kitchen.production.record; asp_asm_stock_id -> asp.asm.stock; finish_good_rework_id -> finish.good.rework; finish_good_rework_finished_id -> finish.good.rework; finish_good_rework_created_kitchen_id -> finish.good.rework; finish_good_rework_by_product_id -> finish.good.rework; assembly_product_id -> product.product; assembly_bom_id -> mrp.bom; kitchen_product_id -> product.product; kitchen_bom_id -> mrp.bom; product_warehouse -> stock.location; product_location -> stock.warehouse; vendor_id -> res.partner; reserved_by_id -> res.users; picking_id -> stock.picking; return_reason -> return.reason; combo_item_id -> pos.combo.item; pos_branch_id -> res.branch; pos_order_line_id -> pos.order.line; sale_order_id -> sale.order; purchase_order_id -> purchase.order; taxes_id -> account.tax; currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: move_dest_ids, move_orig_ids, route_ids, lot_ids, allowed_operation_ids, order_finished_lot_ids, filter_move_package_ids, analytic_account_group_ids, packaging_ids, package_quant_ids, measure_ids, taxes_id.


Describe the field structure of auditlog.http.request.

Response: The auditlog.http.request model has 13 fields: display_name, name, root_url, user_id, http_session_id, user_context, log_ids, id, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 4, many2one: 4, one2many: 1, integer: 1, datetime: 3.


List all fields in the sh.sale.category.xls model.

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


What models are connected to acrux.chat.connector?

Response: The acrux.chat.connector model has 6 relational fields: company_id -> res.company; team_id -> crm.team; sale_report_id -> ir.actions.report; qc_template_ids -> qiscus.template; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


Tell me about the mail.tracking.value model.

Response: The mail.tracking.value model represents Mail Tracking Value in the ERP system. It contains 25 fields and is used to manage mail tracking value data. Key fields include: field, field_desc, field_type, field_groups, old_value_integer, old_value_float, old_value_monetary, old_value_char, old_value_text, old_value_datetime, new_value_integer, new_value_float, new_value_monetary, new_value_char, new_value_text, new_value_datetime, mail_message_id, tracking_sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What is the kpi.item model?

Response: The kpi.item model represents KPI in the ERP system. It contains 36 fields and is used to manage kpi data. Key fields include: name, category_id, formula, formula_warning, line_ids, result_type, result_appearance, result_suffix, result_preffix, currency_id, result_rounding, parent_id, all_parent_ids, child_ids, measures_ids, constant_ids, kpi_ids, company_id, active, description, sequence, user_ids, user_group_ids, access_user_ids, edit_user_ids, edit_user_group_ids, edit_access_user_ids, help_notes, kpi_help_dummy, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What fields does import.record.data have?

Response: The import.record.data model has 46 fields: name, state, record_type, created_date, partner_id, warehouse_id, location_id, no_return, sheet_number, error_message, product_list, file, file_name, filter_location_ids, 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: 7, selection: 4, date: 3, many2one: 8, integer: 6, text: 1, html: 1, binary: 1, many2many: 3, one2many: 4, boolean: 5, datetime: 3.


Describe the implementation of purchase.agreement.legal.document.

Response: The purchase.agreement.legal.document model is defined in module: equip3_purchase_masterdata_indonesia. It has 0 computed fields: . Stored computed fields: none.


What are common use cases for ir.qweb.field.many2many?

Response: To use the ir.qweb.field.many2many 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 technical details of import.record.data?

Response: The import.record.data model is defined in module: import_data_modifier. It has 0 computed fields: . Stored computed fields: none.


What foreign keys exist in sh.top.customers.xls?

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


What are the relationships in crm.phonecall2phonecall?

Response: The crm.phonecall2phonecall model has 6 relational fields: user_id -> res.users; tag_ids -> crm.tag; team_id -> crm.team; partner_id -> res.partner; create_uid -> res.users; write_uid -> res.users. Many2many fields: tag_ids.


How is mr_line.internal_transfer used in the system?

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


Tell me about 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.


What are the relationships in report.account.report_journal?

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


Describe the pos.loyalty model in Odoo.

Response: The pos.loyalty model represents Loyalties Program, on this object we define loyalty program, included rules of plus points and rules of redeem points in the ERP system. It contains 24 fields and is used to manage loyalties program, on this object we define loyalty program, included rules of plus points and rules of redeem points data. Key fields include: name, rule_ids, reward_ids, product_redeem_ids, reward_redeem_ids, count_product_redeem, state, type, product_loyalty_id, rounding, rounding_down, config_ids, pos_config_ids, period_expired, start_date, end_date, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What are the available fields for purchase.order.line.wizard?

Response: The purchase.order.line.wizard model has 14 fields: name, wizard_id, product_id, product_qty, price_unit, product_uom, price_subtotal, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 1, many2one: 5, float: 3, integer: 1, char: 1, datetime: 3.


How to create records in account.fiscal.position.tax?

Response: To use the account.fiscal.position.tax model, you need to provide values for required fields: position_id, tax_src_id. 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 operations can I perform on ks_dashboard_item.multiplier?

Response: To use the ks_dashboard_item.multiplier model, you need to provide values for required fields: none. Readonly fields: ks_model_id, 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 crm.lead2opportunity.partner.mass?

Response: The crm.lead2opportunity.partner.mass model is defined in module: crm. It has 0 computed fields: . Stored computed fields: none.


What methods are available in customer.order.dic?

Response: The customer.order.dic model is defined in module: equip3_sale_report. It has 0 computed fields: . Stored computed fields: none.


What business logic is in 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 methods are available in report.sh_sale_reports.sh_top_selling_product_doc?

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


Describe the setu.rfm.segment model in Odoo.

Response:
The setu.rfm.segment model represents
        The  idea is to segment customers based on when their last purchase was,
        how often they’ve purchased in the past, and how much they’ve spent overall.
        All three of these measures have proven to be effective predictors of a customer's willingness to engage in marketing messages and offers.
     in the ERP system. It contains 31 fields and is used to manage
        the  idea is to segment customers based on when their last purchase was,
        how often they’ve purchased in the past, and how much they’ve spent overall.
        all three of these measures have proven to be effective predictors of a customer's willingness to engage in marketing messages and offers.
     data. Key fields include: name, segment_description, actionable_tips, rfm_score_ids, rfm_score_syntax, rfm_score_condition, segment_rank, partner_ids, order_ids, mailing_ids, total_mailing, total_customers, total_orders, total_revenue, team_customer_segment_ids, open_lead_count, open_rfq_count, total_customers_ratio, total_orders_ratio, total_revenue_ratio, from_date, to_date, calculated_on, desc, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What are the relationships in ks.custom.query.report.column?

Response: The ks.custom.query.report.column model has 3 relational fields: ks_cr_model_id -> ks_custom_report.ks_report; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


Which fields in report.dynamic_accounts_report.balance_sheet are computed?

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


Describe the field structure of account.payment.term.line.

Response: The account.payment.term.line model has 14 fields: value, value_amount, days, day_of_the_month, option, payment_id, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: selection: 2, float: 1, integer: 4, many2one: 3, char: 1, datetime: 3.


Describe the many2many relations for report.coupon.report_coupon.

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


Describe the implementation of crm.salesperson.tracking.report.

Response: The crm.salesperson.tracking.report model is defined in module: equip3_crm_tracking. It has 0 computed fields: . Stored computed fields: none.


What are common use cases for sh.sale.analysis.wizard?

Response: To use the sh.sale.analysis.wizard model, you need to provide values for required fields: sh_end_date, sh_partner_ids, sh_start_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.


How is order.picking implemented technically?

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


How do I use the res.users.apikeys model?

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 operations can I perform on format.address.mixin?

Response: To use the format.address.mixin 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 mrp.immediate.production.line?

Response: The mrp.immediate.production.line model has 10 fields: immediate_production_id, production_id, to_immediate, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, boolean: 1, integer: 1, char: 1, datetime: 3.


How do I use the pos.login.history model?

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.


Which fields in purchase.order.report are computed?

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


How is res.users.log used in the system?

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


List all fields in the sh.qc.alert.tags model.

Response: The sh.qc.alert.tags model has 10 fields: name, color, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 3, many2one: 2, datetime: 3.


What models are connected to stock.valuation.adjustment.lines?

Response: The stock.valuation.adjustment.lines model has 7 relational fields: cost_id -> stock.landed.cost; cost_line_id -> stock.landed.cost.lines; move_id -> stock.move; product_id -> product.product; currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


Show me the fields of product.warranty.

Response: The product.warranty model has 30 fields: partner_id, phone, email, comment, accept1, product_id, serial_no, warranty_end_date, merchant, renew_no, warranty_create_date, product_serial_id, warranty_history_ids, warranty_type, warranty_team, tags_w, model_no, warranty_cost, warranty_claim_ids, warranty_sales_person, state, so_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 9, char: 6, text: 1, boolean: 1, date: 2, integer: 2, one2many: 2, selection: 2, many2many: 1, float: 1, datetime: 3.


What are the technical details of crm.activity.report?

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


What modules define auditlog.rule?

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


What foreign keys exist in print.prenumbered.checks?

Response: The print.prenumbered.checks model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What are the technical details of barcode.nomenclature?

Response: The barcode.nomenclature model is defined in module: barcodes. It has 0 computed fields: . Stored computed fields: none.


What models are connected to delivery.price.rule?

Response: The delivery.price.rule model has 3 relational fields: carrier_id -> delivery.carrier; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What models are connected to account.cashbox.line?

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


What is the assets.approval.reject model?

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


How to create records in voucher.matrix.reject?

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


How is invoice.template.footer used in the system?

Response: The invoice.template.footer model represents Invoice Template Footer in the ERP system. It contains 10 fields and is used to manage invoice template footer data. Key fields include: template_id, field_id, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How to create records in report_excel_gen?

Response: To use the report_excel_gen 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 account.analytic.tag?

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


What are the relationships in sh.stock.move.pass.fail?

Response: The sh.stock.move.pass.fail model has 5 relational fields: product_id -> product.product; sh_quality_point_id -> sh.qc.point; picking_id -> stock.picking; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What is the sh.tc.top.customer.wizard model?

Response: The sh.tc.top.customer.wizard model represents Top Customers in the ERP system. It contains 23 fields and is used to manage top customers data. Key fields include: type, date_to, date_compare_from, date_compare_to, no_of_top_item, amount_total, team_id, currency_id, company_ids, company_id, top_customer_ids, top_customer_compare_ids, lost_cust_ids, new_cust_ids, sale_currency_id, date_from, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What is the open.stock.series model?

Response: The open.stock.series model represents Calculate trend and forecast in the ERP system. It contains 25 fields and is used to manage calculate trend and forecast data. Key fields include: stats_type, stats_for, product_id, template_id, location_id, include_children, date_start, date_end, predicted_periods, interval, forecast_method, seasons, p_coefficient, d_coefficient, q_coefficient, seasonal_p_coefficient, seasonal_d_coefficient, seasonal_q_coefficient, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How is pos.payment.installment.tenor used in the system?

Response: The pos.payment.installment.tenor model represents Pos Payment Installment Tenor in the ERP system. It contains 9 fields and is used to manage pos payment installment tenor data. Key fields include: name, value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Describe the implementation of crm.lead.scoring.frequency.

Response: The crm.lead.scoring.frequency model is defined in module: crm. It has 0 computed fields: . Stored computed fields: none.


Describe the pos.service.charge model in Odoo.

Response: The pos.service.charge model represents Management Service Charge in the ERP system. It contains 15 fields and is used to manage management service charge data. Key fields include: name, product_id, type, amount, distance_from, distance_to, branch_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What modules define hide.view.nodes?

Response: The hide.view.nodes model is defined in module: simplify_access_management. It has 0 computed fields: . Stored computed fields: none.


How is pos.login.history used in the system?

Response: The pos.login.history model represents Pos Login History in the ERP system. It contains 13 fields and is used to manage pos login history data. Key fields include: user_id, pos_config_id, pos_branch_id, checkin_datetime, checkout_datetime, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Describe the field structure of sh.top.purchasing.excel.extended.

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


What are the available fields for untaken.stock.line?

Response: The untaken.stock.line model has 11 fields: product_id, quantity, product_unit_measure, untaken_stock_id, 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 fields does sh.notification.logger have?

Response: The sh.notification.logger model has 12 fields: name, error, datetime, base_config_id, status, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, datetime: 4, many2one: 3, selection: 1, integer: 1.


How to create records in snailmail.letter.format.error?

Response: To use the snailmail.letter.format.error 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 confirm.stock.sms?

Response: The confirm.stock.sms model has 3 relational fields: pick_ids -> stock.picking; create_uid -> res.users; write_uid -> res.users. Many2many fields: pick_ids.


What operations can I perform on credit.limit.product.brand?

Response: To use the credit.limit.product.brand model, you need to provide values for required fields: none. Readonly fields: customer_avail_credit_limit, sequence2, brand_ids, 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 milestone.contract.template?

Response: To use the milestone.contract.template 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.


What methods are available in stock.warehouse.driver?

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


What methods are available in pos.coupon?

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


What data can be stored in warehouse.capacity.report?

Response: The warehouse.capacity.report model has 12 fields: company_id, warehouse_ids, location_ids, filter_location_ids, hide_location, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, many2many: 3, boolean: 1, integer: 1, char: 1, datetime: 3.


What are the technical details of queue.jobs.kill?

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


What are the technical details of report.sh_sale_reports.sh_sales_product_profit_doc?

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.


How to query res.partner data?

Response: To use the res.partner model, you need to provide values for required fields: property_account_payable_id, property_account_receivable_id. Readonly fields: display_name, parent_name, active_lang_count, tz_offset, same_vat_partner_id, email_formatted, partner_share, contact_address, commercial_partner_id, commercial_company_name, self, country_enforce_cities, im_status, signup_valid, signup_url, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, email_normalized, is_blacklisted, 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, phone_sanitized, phone_sanitized_blacklisted, phone_blacklisted, mobile_blacklisted, message_has_sms_error, credit, debit, total_invoiced, currency_id, journal_item_count, has_unreconciled_entries, last_time_entries_checked, invoice_ids, contract_ids, bank_account_count, opportunity_count, meeting_count, task_count, is_seo_optimized, can_publish, website_url, phonecall_count, membership_state, membership_start, membership_stop, membership_cancel, payment_token_count, purchase_order_count, supplier_invoice_count, pos_order_count, on_time_rate, sale_order_count, visible_eval, country_code, last_website_so_id, report_template_id1, report_sale_template_id1, report_po_template_id1, report_delivery_template_id1, loyalty_points, visible_vat_bp, visible_nin, visible_doc_number, visible_other_tax, visible_desc_other_tax, visible_date, visible_country, visible_all, customer_sequence, debtor_id, customer_creation_date, bank_info, vendor_sequence, state1, state2, state3, is_approving_matrix_vendor, approving_matrix_vendor_id, approved_matrix_ids, is_approve_button, approval_matrix_line_id, is_similiar, similiar_partner_count, vendor_creation_date, vendor_available_purchase_limit, customer_credit_limit, is_over_credit_limit, is_invoice_overdue, open_invoice_limit, avl_open_inv_limt, filter_brand_ids, lead_sequence, pos_order_ids, pos_total_amount, pos_partner_type_id, customer_target_id, customer_voucher_count, target_amount_customer_target, pos_loyalty_point, order_count, pos_loyalty_point_available, image_1024, image_512, image_256, image_128, id, 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.financial.year.op?

Response: The account.financial.year.op model has 12 fields: company_id, opening_move_posted, opening_date, fiscalyear_last_day, fiscalyear_last_month, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, boolean: 1, date: 1, integer: 2, selection: 1, char: 1, datetime: 3.


What are the technical details of board.board?

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


List all fields in the hr.employee.public model.

Response: The hr.employee.public model has 42 fields: create_date, name, active, department_id, job_id, job_title, company_id, address_id, mobile_phone, work_phone, work_email, work_location, user_id, resource_id, resource_calendar_id, tz, color, child_ids, image_1920, image_1024, image_512, image_256, image_128, parent_id, coach_id, user_partner_id, subordinate_ids, hr_presence_state, last_activity, last_activity_time, hr_icon_display, goal_ids, badge_ids, has_badges, direct_badge_ids, child_all_count, id, display_name, create_uid, write_uid, write_date, __last_update. Field types distribution: datetime: 3, char: 8, boolean: 2, many2one: 12, selection: 3, integer: 3, one2many: 5, binary: 5, date: 1.


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

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


What are common use cases for mail.thread.blacklist?

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


How is bank.account.account implemented technically?

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


How is purchase.request.line.make.purchase.order implemented technically?

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


Describe the implementation of purchase.down.payment.

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


What methods are available in account.multipayment?

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


Show me the fields of sh.correct.qc.measurement.

Response: The sh.correct.qc.measurement model has 13 fields: product_id, sh_measure, sh_message, sh_text, sh_quality_point_id, picking_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, float: 1, text: 2, integer: 1, char: 1, datetime: 3.


What fields does journal.entry.report have?

Response: The journal.entry.report model has 15 fields: company_id, journal_ids, account_ids, display_account, target_move, date_from, date_to, move_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, many2many: 3, selection: 2, date: 2, integer: 1, char: 1, datetime: 3.


What operations can I perform on tax.sale.details.report?

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


What data can be stored in sh.sale.product.profit.xls?

Response: The sh.sale.product.profit.xls model has 9 fields: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, char: 2, integer: 1, many2one: 2, datetime: 3.


Show me the relational structure of recurring.move.line.

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


How to query purchase.bill.union data?

Response: To use the purchase.bill.union model, you need to provide values for required fields: none. Readonly fields: name, reference, partner_id, date, amount, currency_id, company_id, vendor_bill_id, purchase_order_id, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.


What does the pos.payment.installment.tenor model represent?

Response: The pos.payment.installment.tenor model represents Pos Payment Installment Tenor in the ERP system. It contains 9 fields and is used to manage pos payment installment tenor data. Key fields include: name, value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Which fields in close.fiscal.year are computed?

Response: The close.fiscal.year model is defined in module: sh_sync_fiscal_year. It has 0 computed fields: . Stored computed fields: none.


What methods are available in account.payment.register?

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


What foreign keys exist in full.inv.adjustment.import?

Response: The full.inv.adjustment.import model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


Describe the many2many relations for ir.exports.line.

Response: The ir.exports.line model has 3 relational fields: export_id -> ir.exports; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


How does pos.config relate to other models?

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.


Describe the field structure of basemodel.extend.

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


What are the technical details of ir.translation?

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


How does advertisement.images relate to other models?

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


What does the website.mass_mailing.popup model represent?

Response: The website.mass_mailing.popup model represents Mailing list popup in the ERP system. It contains 10 fields and is used to manage mailing list popup data. Key fields include: mailing_list_id, website_id, popup_content, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What are the relationships in auditlog.log?

Response: The auditlog.log model has 7 relational fields: model_id -> ir.model; user_id -> res.users; line_ids -> auditlog.log.line; http_session_id -> auditlog.http.session; http_request_id -> auditlog.http.request; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What foreign keys exist in mrp.workcenter.productivity.loss.type?

Response: The mrp.workcenter.productivity.loss.type model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.