Describe the field structure of pos.config.

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


How to query return.inter.transfer.company data?

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


Can you explain the purpose of ks_dashboard_ninja.item_action?

Response: The ks_dashboard_ninja.item_action model represents Dashboard Ninja Items Action Lines in the ERP system. It contains 17 fields and is used to manage dashboard ninja items action lines data. Key fields include: ks_item_action_field, ks_item_action_field_type, ks_item_action_date_groupby, ks_chart_type, ks_dashboard_item_id, ks_model_id, sequence, ks_record_limit, ks_sort_by_field, ks_sort_by_order, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


List all fields in the ir.http model.

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


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

Response: The setu.inventory.fsn.xyz.analysis.bi.report model has 19 fields: product_id, product_category_id, company_id, average_stock, sales, turnover_ratio, current_stock, stock_value, fsn_classification, xyz_classification, combine_classification, wizard_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 6, float: 5, char: 4, integer: 1, datetime: 3.


Describe the many2many relations for debt.collection.report.

Response: The debt.collection.report model has 7 relational fields: partner_ids -> res.partner; user_ids -> res.users; journal_ids -> account.journal; report_currency_id -> res.currency; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: partner_ids, user_ids, journal_ids.


What are the technical details of res.partner.type?

Response: The res.partner.type model is defined in module: equip3_pos_masterdata. It has 0 computed fields: . Stored computed fields: none.


How do I use the product.pricelist.item model?

Response: To use the product.pricelist.item model, you need to provide values for required fields: base, pricelist_id, compute_price, applied_on. Readonly fields: company_id, currency_id, active, price, uom_ids, name, 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.indent.xls?

Response: The sh.sale.product.indent.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.


Describe the many2many relations for base_import.tests.models.o2m.

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


What methods are available in recurring.move.line?

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


How to query report.equip3_accounting_reports.equity_move data?

Response: To use the report.equip3_accounting_reports.equity_move 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 models are connected to account.deposit.return?

Response: The account.deposit.return model has 6 relational fields: journal_id -> account.journal; diff_amount_account_id -> account.account; customer_deposit_id -> customer.deposit; vendor_deposit_id -> vendor.deposit; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What are the available fields for whatsapp.template.message.variable?

Response: The whatsapp.template.message.variable model has 10 fields: wa_id, name, description, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, char: 3, integer: 1, datetime: 3.


What models are connected to pos.payment.installment.tenor?

Response: The pos.payment.installment.tenor model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What models are connected to res.branch?

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


What fields does project.delete.wizard have?

Response: The project.delete.wizard model has 10 fields: project_ids, task_count, projects_archived, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2many: 1, integer: 2, boolean: 1, char: 1, many2one: 2, datetime: 3.


What foreign keys exist in hour.group?

Response: The hour.group model has 3 relational fields: company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What are the available fields for uom.uom?

Response: The uom.uom model has 19 fields: name, category_id, factor, factor_inv, rounding, active, uom_type, timesheet_widget, is_pos_groupable, is_custom_uom, product_ratio_line, is_external_link, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, many2one: 3, float: 3, boolean: 4, selection: 1, one2many: 1, integer: 1, datetime: 3.


Describe the implementation of account.payment.register.

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


How do I use the pos.sale.summary.wizard model?

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


What are the available fields for bus.bus?

Response: The bus.bus model has 9 fields: channel, message, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, integer: 1, many2one: 2, datetime: 3.


How to query mrp.immediate.production.line data?

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


Show me the relational structure of ir.qweb.field.many2one.

Response: The ir.qweb.field.many2one model has no explicit relational fields defined in its field metadata.


What business logic is in intrawarehouse.transfer.line?

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


Describe the implementation of list.customer.compare.

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


List all fields in the project.task.recurrence model.

Response: The project.task.recurrence model has 28 fields: task_ids, next_recurrence_date, recurrence_left, repeat_interval, repeat_unit, repeat_type, repeat_until, repeat_number, repeat_on_month, repeat_on_year, mon, tue, wed, thu, fri, sat, sun, repeat_day, repeat_week, repeat_weekday, repeat_month, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: one2many: 1, date: 2, integer: 4, selection: 8, boolean: 7, char: 1, many2one: 2, datetime: 3.


What are the relationships in sh.correct.qc.measurement?

Response: The sh.correct.qc.measurement 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.


Which fields in account.debt.collection are computed?

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


How to create records in mail.bot?

Response: To use the mail.bot 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 models are connected to stock.picking.batch.validate.line?

Response: The stock.picking.batch.validate.line model has 6 relational fields: line_id -> stock.picking.batch.validate; product_id -> product.product; transfer_id -> stock.picking; location_id -> stock.location; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What methods are available in res.partner.rfm.segment.history?

Response: The res.partner.rfm.segment.history model is defined in module: setu_rfm_analysis. It has 0 computed fields: . Stored computed fields: none.


List all fields in the warranty.claim.category model.

Response: The warranty.claim.category model has 9 fields: name, team_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 3, integer: 1, datetime: 3.


How is account.multipayment used in the system?

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.


How do I use the sh.purchase.analysis.xls model?

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


What are the available fields for list.order?

Response: The list.order model has 28 fields: order_dic_id, order_number, order_date, total, due_amount, cust_dic_id, invoice_number, invoice_date, invoice_currency_id, salesperson, sale_currency_id, sale_amount, paid_amount, balance_amount, product, customer, qty, cost, sale_price, profit, margin, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, char: 6, datetime: 5, float: 10, integer: 3.


How does ir.http relate to other models?

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


How does report.sh_sale_reports.sh_salesperson_report_doc relate to other models?

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


How to query gamification.badge data?

Response: To use the gamification.badge model, you need to provide values for required fields: name, rule_auth. Readonly fields: granted_count, granted_users_count, unique_owner_ids, stat_this_month, stat_my, stat_my_this_month, stat_my_monthly_sending, remaining_sending, granted_employees_count, can_publish, website_url, image_1024, image_512, image_256, image_128, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


Describe the pos.account.cashbox.line model in Odoo.

Response: The pos.account.cashbox.line model represents CashBox Line in the ERP system. It contains 11 fields and is used to manage cashbox line data. Key fields include: coin_value, number, subtotal, pos_config_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What models are connected to gamification.goal?

Response: The gamification.goal model has 6 relational fields: definition_id -> gamification.goal.definition; user_id -> res.users; line_id -> gamification.challenge.line; challenge_id -> gamification.challenge; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What does the report.equip3_accounting_reports.balance_sheet model represent?

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


What business logic is in base.module.update?

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


What business logic is in account.group.template?

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


Tell me about the vendor.delay.report model.

Response: The vendor.delay.report model represents Vendor Delay Report in the ERP system. It contains 10 fields and is used to manage vendor delay report data. Key fields include: partner_id, product_id, category_id, date, qty_total, qty_on_time, on_time_rate, id, display_name, __last_update.


Which fields in report.accounting_pdf_reports.report_tax are computed?

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


What are common use cases for product.public.category?

Response: To use the product.public.category model, you need to provide values for required fields: name. Readonly fields: parents_and_self, amount_footer, image_1024, image_512, image_256, image_128, is_seo_optimized, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


What business logic is in ir.sequence.date_range?

Response: To use the ir.sequence.date_range model, you need to provide values for required fields: date_from, date_to, sequence_id, number_next. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


How to create records in invoice.templates?

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


Show me the relational structure of setu.inventory.turnover.analysis.report.

Response: The setu.inventory.turnover.analysis.report model has 7 relational fields: product_category_ids -> product.category; product_ids -> product.product; warehouse_ids -> stock.warehouse; company_id -> res.company; company_ids -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: product_category_ids, product_ids, warehouse_ids, company_ids.


How does sh.qc.alert.tags relate to other models?

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


List all fields in the sale.advance.payment.inv model.

Response: The sale.advance.payment.inv model has 20 fields: advance_payment_method, deduct_down_payments, has_down_payments, product_id, count, amount, currency_id, fixed_amount, deposit_account_id, deposit_taxes_id, date_start_invoice_timesheet, date_end_invoice_timesheet, invoicing_timesheet_enabled, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: selection: 1, boolean: 3, many2one: 5, integer: 2, float: 1, monetary: 1, many2many: 1, date: 2, char: 1, datetime: 3.


What are the available fields for account.account.tag?

Response: The account.account.tag model has 14 fields: applicability, color, active, tax_report_line_ids, tax_negate, country_id, name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: selection: 1, integer: 2, boolean: 2, many2many: 1, many2one: 3, char: 2, datetime: 3.


What data can be stored in calendar.alarm?

Response: The calendar.alarm model has 12 fields: name, duration, interval, duration_minutes, alarm_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 3, selection: 2, many2one: 2, datetime: 3.


How is pos.product.bom.line implemented technically?

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


What business logic is in restore.lead.type?

Response: To use the restore.lead.type 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 methods are available in analytic.priority?

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


What foreign keys exist in product.warehouse.cost.line?

Response: The product.warehouse.cost.line model has 6 relational fields: prod_wh_cost_id -> product.warehouse.cost; warehouse_id -> stock.warehouse; company_id -> res.company; currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What fields does res.currency.rate have?

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


Describe the field structure of res.users.apikeys.show.

Response: The res.users.apikeys.show model has 4 fields: key, id, display_name, __last_update. Field types distribution: char: 2, integer: 1, datetime: 1.


Describe the many2many relations for mr.approval.matrix.line.

Response: The mr.approval.matrix.line model has 13 relational fields: user_ids -> res.users; mr_approval_matrix -> mr.approval.matrix; approved_users -> res.users; last_approved -> res.users; mr_matrix_id -> material.request; 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: user_ids, approved_users, message_partner_ids, message_channel_ids.


What data can be stored in pos.promotion.gift.free?

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


How to create records in crm.merge.opportunity?

Response: To use the crm.merge.opportunity 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 ir.rule?

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


How does account.account.map relate to other models?

Response: The account.account.map model has 7 relational fields: company_id -> res.company; line_ids -> account.account.map.line; child_company_id -> res.company; sales_line_ids -> account.tax.map.sales.line; purchase_line_ids -> account.tax.map.purchase.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What does the service.work.order.checklist model represent?

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


What models are connected to report.excel.param?

Response: The report.excel.param model has 5 relational fields: report_excel_id -> report.excel; param_ir_model_id -> ir.model; wizard_param_ir_model_field_id -> ir.model.fields; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


List all fields in the module.advanced.upgrade model.

Response: The module.advanced.upgrade model has 17 fields: module_id, module_shortdesc, module_name, module_author, module_installed_version, module_latest_version, module_state, children_ids, parent_id, selected, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, char: 6, selection: 1, one2many: 1, boolean: 1, integer: 1, datetime: 3.


What models are connected to report.equip3_kitchen_reports.report_kitchen_production?

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


What methods are available in budget.carry.over?

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


What are the relationships in report.point_of_sale.report_saledetails?

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


How does reset.view.arch.wizard relate to other models?

Response: The reset.view.arch.wizard model has 4 relational fields: view_id -> ir.ui.view; compare_view_id -> ir.ui.view; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What are the relationships in kpi.item?

Response: The kpi.item model has 18 relational fields: category_id -> kpi.category; line_ids -> kpi.scorecard.line; currency_id -> res.currency; parent_id -> kpi.item; all_parent_ids -> kpi.item; child_ids -> kpi.item; measures_ids -> kpi.measure.item; constant_ids -> kpi.constant; kpi_ids -> kpi.item; company_id -> res.company; user_ids -> res.users; user_group_ids -> res.groups; access_user_ids -> res.users; edit_user_ids -> res.users; edit_user_group_ids -> res.groups; edit_access_user_ids -> res.users; create_uid -> res.users; write_uid -> res.users. Many2many fields: all_parent_ids, measures_ids, constant_ids, kpi_ids, user_ids, user_group_ids, access_user_ids, edit_user_ids, edit_user_group_ids, edit_access_user_ids.


How to query sh.account.period data?

Response: To use the sh.account.period model, you need to provide values for required fields: name, date_start, date_end, company_id. Readonly fields: name, code, date_start, date_end, fiscal_year_id, special, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


What are the relationships in pos.keyboard.shortcuts?

Response: The pos.keyboard.shortcuts model has 3 relational fields: payment_methods -> pos.payment.method.key; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What are common use cases for export.efaktur?

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


How to query ir.qweb.field.selection data?

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


What does the sh.mpo.merge.purchase.order.wizard model represent?

Response: The sh.mpo.merge.purchase.order.wizard model represents Merge Purchase Order Wizard in the ERP system. It contains 12 fields and is used to manage merge purchase order wizard data. Key fields include: partner_id, purchase_order_id, purchase_order_ids, merge_type, merge_option, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What business logic is in sh.qc.alert?

Response: To use the sh.qc.alert model, you need to provide values for required fields: team_id, user_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


Can you explain the purpose of purchase.agreement.type?

Response: The purchase.agreement.type model represents Purchase Agreement Type in the ERP system. It contains 8 fields and is used to manage purchase agreement type data. Key fields include: name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Show me the fields of account.bank.statement.line.wizard.

Response: The account.bank.statement.line.wizard model has 7 fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 1, char: 1, many2one: 2, datetime: 3.


What business logic is in recurring.move.line?

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


What are the technical details of account.analytic.new?

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


Show me the relational structure of pos.promotion.

Response: The pos.promotion model has 34 relational fields: product_id -> product.product; discount_order_ids -> pos.promotion.discount.order; discount_category_ids -> pos.promotion.discount.category; discount_quantity_ids -> pos.promotion.discount.quantity; gift_condition_ids -> pos.promotion.gift.condition; gift_free_ids -> pos.promotion.gift.free; discount_condition_ids -> pos.promotion.discount.condition; discount_apply_ids -> pos.promotion.discount.apply; multilevel_condition_ids -> pos.promotion.multilevel.condition; multilevel_gift_ids -> pos.promotion.multilevel.gift; price_ids -> pos.promotion.price; special_category_ids -> pos.promotion.special.category; multi_buy_ids -> pos.promotion.multi.buy; promotion_specific_product_ids -> pos.promotion.specific.product; tebus_murah_product_ids -> pos.promotion.tebus.murah; product_ids -> product.product; special_customer_ids -> res.partner; promotion_group_ids -> res.partner.group; pos_branch_ids -> res.branch; payment_method_ids -> pos.payment.method; pos_apply -> pos.config; card_payment_id -> card.payment; card_payment_ids -> card.payment; branch_id -> res.branch; promotion_based_on_brand_ids -> pos.promotion.selected.brand; tebus_murah_selected_brand_ids -> pos.promotion.tebus.murah.selected.brand; tebus_murah_brand_ids -> product.brand; promotion_product_discount_id -> product.product; company_id -> res.company; currency_id -> res.currency; pos_loyalty_category_ids -> pos.loyalty.category; pos_branch_id -> res.branch; create_uid -> res.users; write_uid -> res.users. Many2many fields: product_ids, special_customer_ids, promotion_group_ids, pos_branch_ids, payment_method_ids, pos_apply, card_payment_ids, tebus_murah_brand_ids, pos_loyalty_category_ids, pos_branch_id.


What fields does pos.combo.limit have?

Response: The pos.combo.limit model has 11 fields: product_tmpl_id, pos_categ_id, quantity_limited, default_product_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, integer: 2, many2many: 1, char: 1, datetime: 3.


What foreign keys exist in quality.alert.report?

Response: The quality.alert.report model has 5 relational fields: product_ids -> product.product; user_ids -> res.users; stage_id -> sh.qc.alert.stage; create_uid -> res.users; write_uid -> res.users. Many2many fields: product_ids, user_ids.


How does account.account relate to other models?

Response: The account.account model has 23 relational fields: move_line_ids -> account.move.line; parent_id -> account.account; child_ids -> account.account; currency_id -> res.currency; user_type_id -> account.account.type; tax_ids -> account.tax; company_id -> res.company; tag_ids -> account.account.tag; group_id -> account.group; root_id -> account.root; allowed_journal_ids -> account.journal; branch_id -> res.branch; 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: tax_ids, tag_ids, allowed_journal_ids, message_partner_ids, message_channel_ids.


Describe the many2many relations for crossovered.budget.wizard.

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


What are common use cases for overhead.time?

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


Describe the implementation of stock.package.destination.

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


What foreign keys exist in report.equip3_accounting_reports.pettycash_analysis?

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


How to query stock.move.line data?

Response: To use the stock.move.line model, you need to provide values for required fields: company_id, product_uom_id, product_uom_qty, date, location_id, location_dest_id. Readonly fields: company_id, product_uom_category_id, lots_visible, picking_code, picking_type_use_create_lots, picking_type_use_existing_lots, state, is_locked, tracking, origin, picking_type_entire_packs, is_double_product_usage, sale_price, product_type, quant_package_ids, source_picking_id, is_batch_shipping_packing, is_batch_shipping_delivery, description, pos_branch_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 repair.fee?

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


What foreign keys exist in nsfp.registration?

Response: The nsfp.registration model has 4 relational fields: fiscal_year -> sh.fiscal.year; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


How is stock.warehouse implemented technically?

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


Which fields in account.deposit.reconcile are computed?

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


Describe the many2many relations for hr.employee.

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


What are the available fields for pos.loyalty.reward.product?

Response: The pos.loyalty.reward.product model has 14 fields: gift_reward_id, product_id, redeem_point, default_code, list_price, uom_id, sh_qr_code, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, integer: 2, char: 3, float: 1, datetime: 3.


How to create records in crm.team?

Response: To use the crm.team model, you need to provide values for required fields: name, alias_id, alias_model_id, alias_defaults, alias_contact. Readonly fields: currency_id, dashboard_button_name, dashboard_graph_data, lead_unassigned_count, lead_all_assigned_month_count, opportunities_count, opportunities_amount, opportunities_overdue_count, opportunities_overdue_amount, invoiced, quotations_count, quotations_amount, sales_to_invoice_count, abandoned_carts_count, abandoned_carts_amount, rma_draft_count, rma_confirm_count, rma_process_count, rma_close_count, rma_reject_count, pos_sessions_open_count, pos_order_amount_total, company_id, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, alias_domain. The model supports standard CRUD operations through the ORM.


How is product.product implemented technically?

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


What models are connected to mail.thread.cc?

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


What is the report_excel_gen model?

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


Describe the many2many relations for receipt.payment.line.credit.

Response: The receipt.payment.line.credit model has 7 relational fields: line_id -> receipt.payment; currency_id -> res.currency; invoice_id -> account.move; account_id -> account.account; payment_id -> account.payment; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


Describe the field structure of limit.approval.matrix.sale.reject.

Response: The limit.approval.matrix.sale.reject model has 8 fields: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 1, integer: 1, char: 1, many2one: 2, datetime: 3.


What are the relationships in mass.editing.wizard?

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


Describe the many2many relations for auth_totp.wizard.

Response: The auth_totp.wizard model has 3 relational fields: user_id -> res.users; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


How do I use the report.dev_rma.report_rma_template model?

Response: To use the report.dev_rma.report_rma_template 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 sale.order.deduction?

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


What models are connected to sh.purchase.product.profit.xls?

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


What fields does cashback.line have?

Response: The cashback.line model has 16 fields: sequence, product_id, name, product_uom_qty, price_unit, total, customer_voucher_id, order_id, invoice_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 2, many2one: 6, char: 2, float: 3, datetime: 3.


What are common use cases for crm.quotation.partner?

Response: To use the crm.quotation.partner model, you need to provide values for required fields: action, lead_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 data can be stored in account.analytic.default?

Response: The account.analytic.default model has 43 fields: sequence, analytic_id, analytic_tag_ids, product_id, user_id, company_id, date_start, partner_id, account_id, date_stop, branch_id, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 6, many2one: 12, many2many: 3, date: 4, one2many: 4, selection: 2, char: 4, boolean: 5, datetime: 3.


List all fields in the sequence.mixin model.

Response: The sequence.mixin model has 5 fields: sequence_prefix, sequence_number, id, display_name, __last_update. Field types distribution: char: 2, integer: 2, datetime: 1.


What fields does tax.adjustments.wizard have?

Response: The tax.adjustments.wizard model has 17 fields: reason, journal_id, date, debit_account_id, credit_account_id, amount, adjustment_type, tax_report_line_id, company_currency_id, report_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 8, date: 1, monetary: 1, selection: 1, integer: 1, datetime: 3.


Which fields in generate.closing.entries are computed?

Response: The generate.closing.entries model is defined in module: equip3_accounting_operation. It has 0 computed fields: . Stored computed fields: none.


How is product.brand implemented technically?

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


Describe the implementation of cust.credit.limit.xls.

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


Show me the fields of milestone.contract.template.

Response: The milestone.contract.template model has 11 fields: name, checklist_template_id, line_ids, checklist_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 3, one2many: 2, integer: 1, datetime: 3.


How to query tax.sale.details.report data?

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.


How to query pos.order.log data?

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


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

Response: The mrp.bom.operation model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


Describe the field structure of internal.transfer.

Response: The internal.transfer model has 84 fields: name, description, source_document, state, state1, state2, state3, product_line_ids, operation_type_in_id, operation_type_out_id, is_transit, operation_count, expiry_date, is_source_loc, is_destination_loc, internal_transfer_line_total, operations, 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, source_warehouse_id, destination_warehouse_id, company_id, filter_source_warehouse_id, filter_destination_warehouse_id, requested_by, get_warehouse, is_mbs_on_transfer_operations, branch_id, domain_warehouse_source_id, domain_warehouse_destination_id, sh_it_barcode_mobile, sh_it_bm_is_cont_scan, mr_id, average_id, is_outlet_order, analytic_account_group_ids, is_expired_tranfer, arrival_date, source_location_id, destination_location_id, scheduled_date, create_date, campaign_id, source_id, medium_id, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, access_url, access_token, access_warning, id, display_name, create_uid, write_uid, write_date, __last_update. Field types distribution: char: 12, text: 3, selection: 6, one2many: 6, many2one: 20, boolean: 16, integer: 7, datetime: 6, many2many: 6, date: 2.


Show me the relational structure of all.loyalty.history.

Response: The all.loyalty.history model has 7 relational fields: order_id -> sale.order; pos_order_id -> pos.order; partner_id -> res.partner; currency_id -> res.currency; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


Show me the relational structure of ir.config_parameter.

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


Can you explain the purpose of account.internal.transfer?

Response: The account.internal.transfer model represents Account Internal Transfer in the ERP system. It contains 68 fields and is used to manage account internal transfer data. Key fields include: request_partner_id, bank_from_journal_id, bank_to_journal_id, transfer_in_transit, account_in_transit, transfer_desc, transfer_amount, currency_id, transfer_date, create_date, create_uid, company_id, branch_id, state, filter_branch_ids, administration, administration_account, administration_fee, has_reconciled_entries, approval_matrix_id, is_internal_approval_matrix, approved_matrix_ids, approval_matrix_line_id, is_approve_button, state1, state2, analytic_group_ids, apply_manual_currency_exchange, manual_currency_exchange_rate, manual_currency_exchange_inverse_rate, type_curr, name, campaign_id, source_id, medium_id, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, access_url, access_token, access_warning, id, display_name, write_uid, write_date, __last_update.


How does base.module.update relate to other models?

Response: The base.module.update model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What models are connected to stock.return.picking?

Response: The stock.return.picking model has 10 relational fields: picking_id -> stock.picking; product_return_moves -> stock.return.picking.line; original_location_id -> stock.location; parent_location_id -> stock.location; company_id -> res.company; location_id -> stock.location; return_reason -> return.reason; return_line_ids -> stock.return.move.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


Tell me about the all.loyalty.history model.

Response: The all.loyalty.history model represents all loyalty history in the ERP system. It contains 19 fields and is used to manage all loyalty history data. Key fields include: order_id, pos_order_id, partner_id, date, generated_from, transaction_type, points, amount, currency_id, company_id, check_state, state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What are the available fields for o2m.global.search.fields?

Response: The o2m.global.search.fields model has 14 fields: sequence, name, field_id, global_o2m_search_id, model_id, related_model_id, ttype, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 2, char: 3, many2one: 5, selection: 1, datetime: 3.


What are common use cases for stock.location.tag?

Response: To use the stock.location.tag 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 foreign keys exist in o2m.global.search.fields?

Response: The o2m.global.search.fields model has 5 relational fields: field_id -> ir.model.fields; global_o2m_search_id -> global.search.fields; model_id -> ir.model; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


How is calendar.event.type implemented technically?

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


List all fields in the cust.credit.limit.data.line model.

Response: The cust.credit.limit.data.line model has 13 fields: cust_credit_id, partner_id, cust_credit_limit, customer_credit_limit, balance_due, aval_credit, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, float: 4, integer: 1, char: 1, datetime: 3.


How is wizard.ir.model.menu.create used in the system?

Response: The wizard.ir.model.menu.create model represents Create Menu Wizard in the ERP system. It contains 9 fields and is used to manage create menu wizard data. Key fields include: menu_id, name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What fields does multiple.rfq have?

Response: The multiple.rfq model has 9 fields: vendor_ids, product_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2many: 2, integer: 1, char: 1, many2one: 2, datetime: 3.


How to create records in material.request?

Response: To use the material.request model, you need to provide values for required fields: name, requested_by, schedule_date, analytic_account_group_ids. Readonly fields: create_date, create_uid, company_id, branch_id, status_1, status_2, status_3, check_product, mr_approval_matrix_id, is_material_request_approval_matrix, approved_matrix_ids, approval_matrix_line_id, is_approve_button, is_reset_to_draft, pr_count, ir_count, itr_war_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, id, display_name, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


Describe the account.cashbox.wizard.validate model in Odoo.

Response: The account.cashbox.wizard.validate model represents account.cashbox.wizard.validate in the ERP system. It contains 9 fields and is used to manage account.cashbox.wizard.validate data. Key fields include: pin, account_cashbox_wizard_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Describe the many2many relations for pos.voucher.

Response: The pos.voucher model has 15 relational fields: customer_id -> res.partner; user_id -> res.users; pos_order_id -> pos.order; pos_order_line_id -> pos.order.line; use_history_ids -> pos.voucher.use.history; generated_source_id -> generate.pos.voucher; limit_restrict_product_ids -> product.product; pos_category_ids -> pos.category; company_id -> res.company; receipt_template_id -> pos.receipt.template; source_document_id -> generate.pos.voucher; brand_ids -> product.brand; member_type_ids -> pos.loyalty.category; create_uid -> res.users; write_uid -> res.users. Many2many fields: limit_restrict_product_ids, pos_category_ids, brand_ids, member_type_ids.


What does the barcode.product.lines model represent?

Response: The barcode.product.lines model represents barcode.product.lines in the ERP system. It contains 13 fields and is used to manage barcode.product.lines data. Key fields include: product_id, lot_id, wizard_id, qty, is_multi_barcode, barcode, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What methods are available in ks_custom_report.ks_report?

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


How do I use the warranty.claim.stage model?

Response: To use the warranty.claim.stage 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 business logic is in queue.job.function?

Response: To use the queue.job.function model, you need to provide values for required fields: channel_id. Readonly fields: channel, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.


What data can be stored in rn.approval_matrix_detail?

Response: The rn.approval_matrix_detail model has 11 fields: location_name, usage, company_id, rn_approval_matrix_id2, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2many: 1, selection: 1, many2one: 4, integer: 1, char: 1, datetime: 3.


Show me the fields of pos.voucher.

Response: The pos.voucher model has 39 fields: active, customer_id, code, start_date, end_date, state, value, apply_type, method, use_date, user_id, source, pos_order_id, pos_order_line_id, use_history_ids, number, maximum_discount_amount, minimum_purchase_amount, is_generate_voucher, generated_source_id, limit_restrict_product_ids, pos_category_ids, company_id, receipt_template_id, source_document_id, is_customize_sequence, sequence_generate_method, manual_input_sequence, running_number_prefix, running_number_digit, brand_ids, member_type_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 3, many2one: 10, char: 6, datetime: 6, selection: 4, float: 3, one2many: 1, many2many: 4, integer: 2.


What is the report.sh_purchase_reports.sh_po_product_profit_doc model?

Response: The report.sh_purchase_reports.sh_po_product_profit_doc model represents Purchase Product Profit report abstract model in the ERP system. It contains 3 fields and is used to manage purchase product profit report abstract model data. Key fields include: id, display_name, __last_update.


Show me the fields of sale.margin.report.wizard.

Response: The sale.margin.report.wizard model has 12 fields: partner_ids, start_date, end_date, company_ids, branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2many: 2, datetime: 5, many2one: 3, integer: 1, char: 1.


What foreign keys exist in report.stock.report_product_product_replenishment?

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


What are the available fields for vendor.deposit?

Response: The vendor.deposit model has 77 fields: name, is_deposit, amount, remaining_amount, communication, return_deposit, payment_date, deposit_reconcile_journal_id, journal_id, deposit_account_id, company_id, currency_id, state, is_show_cancel, invoice_count, reconcile_count, reconcile_deposit_ids, invoice_deposit_ids, filter_deposit_account_ids, approval_matrix_id, is_vendor_deposit_approval_matrix, approved_matrix_ids, approval_matrix_line_id, is_approve_button, state1, state2, request_partner_id, deposit_history, add_amount_approver, approve_add_amount, deposit_count, description, partner_id, employee_id, branch_id, filter_branch_ids, move_id, is_cash_advance, return_cash_advance_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. Field types distribution: char: 9, boolean: 11, monetary: 3, many2one: 21, date: 3, selection: 5, integer: 8, many2many: 8, one2many: 5, text: 1, datetime: 3.


Which fields in ir.qweb.field.contact are computed?

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


List all fields in the product.ribbon model.

Response: The product.ribbon model has 11 fields: html, bg_color, text_color, html_class, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 5, integer: 1, many2one: 2, datetime: 3.


What business logic is in pos.details.wizard?

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


What are the technical details of sale.order.option?

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


What are the relationships in mail.compose.message?

Response: The mail.compose.message model has 13 relational fields: parent_id -> mail.message; template_id -> mail.template; attachment_ids -> ir.attachment; author_id -> res.partner; subtype_id -> mail.message.subtype; mail_activity_type_id -> mail.activity.type; partner_ids -> res.partner; mail_server_id -> ir.mail_server; mass_mailing_id -> mailing.mailing; campaign_id -> utm.campaign; mailing_list_ids -> mailing.list; create_uid -> res.users; write_uid -> res.users. Many2many fields: attachment_ids, partner_ids, mailing_list_ids.


Show me the fields of pmps.adv.wizard.

Response: The pmps.adv.wizard model has 10 fields: product_ids, product_attr_ids, specific_product_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: one2many: 2, many2many: 1, integer: 1, char: 1, many2one: 2, datetime: 3.


Can you explain the purpose of base.language.import?

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


What is the report.equip3_pos_report.report_pos_payment model?

Response: The report.equip3_pos_report.report_pos_payment model represents POS Payment Report in the ERP system. It contains 3 fields and is used to manage pos payment report data. Key fields include: id, display_name, __last_update.


What are common use cases for account.petty.cash.report?

Response: To use the account.petty.cash.report model, you need to provide values for required fields: none. Readonly fields: name, custodian_id, main_cash_account_id, amount, balance, virtual_balance, company_id, branch_id, effective_date, create_uid, create_date, expense_amount, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.


Show me the fields of mail.resend.cancel.

Response: The mail.resend.cancel model has 9 fields: model, help_message, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, integer: 1, many2one: 2, datetime: 3.


What business logic is in pos.tracking.client?

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


What models are connected to report.mrp.report_bom_structure?

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


What models are connected to team.customer.segment?

Response: The team.customer.segment model has 4 relational fields: team_id -> crm.team; rfm_segment_id -> setu.rfm.segment; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


Describe the field structure of customer.order.dic.

Response: The customer.order.dic model has 10 fields: report_id, list_order, saleperson, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, one2many: 1, char: 2, integer: 1, datetime: 3.


Describe the field structure of ir.demo_failure.

Response: The ir.demo_failure model has 10 fields: module_id, error, wizard_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, char: 2, integer: 1, datetime: 3.


Describe the field structure of queue.jobs.to.done.

Response: The queue.jobs.to.done model has 8 fields: job_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2many: 1, integer: 1, char: 1, many2one: 2, datetime: 3.


What models are connected to mail.bot?

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


What are the available fields for intrawarehouse.transfer?

Response: The intrawarehouse.transfer model has 8 fields: interawarehouse_transfer_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: one2many: 1, integer: 1, char: 1, many2one: 2, datetime: 3.


What modules define stock.production.lot?

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


Tell me about the account.invoice.exchange.approval.wizard model.

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


How to query sh.tv.top.vendor.wizard data?

Response: To use the sh.tv.top.vendor.wizard model, you need to provide values for required fields: date_from, date_to, no_of_top_item, currency_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 fields does base_import.tests.models.char.readonly have?

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


What operations can I perform on base_import.tests.models.m2o.related?

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


What operations can I perform on repair.order.make_invoice?

Response: To use the repair.order.make_invoice 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 pos.coupon.apply.code relate to other models?

Response: The pos.coupon.apply.code model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


How do I use the setu.rfm.score model?

Response: To use the setu.rfm.score model, you need to provide values for required fields: none. Readonly fields: total_customers, 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 pos.product.attribute model.

Response: The pos.product.attribute model has 9 fields: sequence, product_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 2, many2one: 3, char: 1, datetime: 3.


What operations can I perform on cust.credit.limit.report.wizard?

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


Show me the relational structure of account.setup.bank.manual.config.

Response: The account.setup.bank.manual.config model has 10 relational fields: res_partner_bank_id -> res.partner.bank; linked_journal_id -> account.journal; branch_id -> res.branch; create_uid -> res.users; write_uid -> res.users; partner_id -> res.partner; bank_id -> res.bank; currency_id -> res.currency; company_id -> res.company; journal_id -> account.journal. Many2many fields: none.


How to query mr_line.internal_transfer_line data?

Response: To use the mr_line.internal_transfer_line model, you need to provide values for required fields: qty_transfer. Readonly fields: no, virtual_available, filter_warehouse_ids, filter_location_ids, dest_warehouse_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


List all fields in the project.sale.line.employee.map model.

Response: The project.sale.line.employee.map model has 14 fields: project_id, employee_id, sale_line_id, company_id, timesheet_product_id, price_unit, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 8, float: 1, integer: 1, char: 1, datetime: 3.


What methods are available in project.task.type.delete.wizard?

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


Can you explain the purpose of hour.group?

Response: The hour.group model represents Hour Group in the ERP system. It contains 12 fields and is used to manage hour group data. Key fields include: name, start_hour, end_hour, active, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What are the relationships in sale.data.margin.line?

Response: The sale.data.margin.line model has 4 relational fields: margin_id -> sale.data.margin; product_id -> product.product; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


Can you explain the purpose of initial.balance.line?

Response: The initial.balance.line model represents initial Balance Sheet in the ERP system. It contains 17 fields and is used to manage initial balance sheet data. Key fields include: name, report_name, account_id, company_id, currency_id, debit_amount, credit_amount, balance_amount, period_id, valid_value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Describe the implementation of stock.backorder.confirmation.line.

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


What business logic is in project.tags?

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


List all fields in the pos.tag model.

Response: The pos.tag model has 12 fields: name, color, is_return_reason, branch_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, boolean: 1, many2one: 4, integer: 1, datetime: 3.


What are the available fields for restaurant.table?

Response: The restaurant.table model has 17 fields: name, floor_id, shape, position_h, position_v, width, height, seats, color, active, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, many2one: 3, selection: 1, float: 4, integer: 2, boolean: 1, datetime: 3.


What data can be stored in crm.phonecall?

Response: The crm.phonecall model has 46 fields: date_action_last, date_action_next, create_date, team_id, user_id, partner_id, company_id, description, state, email_from, date_open, name, active, duration, tag_ids, partner_phone, partner_mobile, priority, date_closed, date, opportunity_id, direction, campaign_id, source_id, medium_id, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, write_uid, write_date, __last_update. Field types distribution: datetime: 8, many2one: 11, text: 1, selection: 3, char: 5, boolean: 6, float: 1, many2many: 3, one2many: 3, integer: 5.


Can you explain the purpose of product.public.category?

Response: The product.public.category model represents Website Product Category in the ERP system. It contains 29 fields and is used to manage website product category data. Key fields include: name, parent_id, parent_path, child_id, parents_and_self, sequence, website_description, product_tmpl_ids, Minimum_amount, amount_footer, image_1920, image_1024, image_512, image_256, image_128, is_seo_optimized, website_meta_title, website_meta_description, website_meta_keywords, website_meta_og_img, seo_name, website_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Show me the fields of sale.order.repair.line.

Response: The sale.order.repair.line model has 11 fields: repair_id, product_id, quantity, location_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.


Which fields in wizard.scrap.order.report are computed?

Response: The wizard.scrap.order.report model is defined in module: eq_scrap_order_report. It has 0 computed fields: . Stored computed fields: none.


What operations can I perform on mail.alias?

Response: To use the mail.alias model, you need to provide values for required fields: alias_model_id, alias_defaults, alias_contact. Readonly fields: alias_domain, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


What business logic is in customer.voucher?

Response: To use the customer.voucher model, you need to provide values for required fields: none. Readonly fields: name, state, start_date, end_date, reward_type, discount_line_product_id, expired_date, expiration_period, customer_voucher_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


Can you explain the purpose of ir.qweb?

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


How is print.purchase.tender.report used in the system?

Response: The print.purchase.tender.report model represents Purchase Tender Pdf/XLS Report in the ERP system. It contains 9 fields and is used to manage purchase tender pdf/xls report data. Key fields include: selection, purchase_agreement_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What are the relationships in account.move.template.line?

Response: The account.move.template.line model has 26 relational fields: move_id -> account.move.template; journal_id -> account.journal; company_id -> res.company; company_currency_id -> res.currency; tax_fiscal_country_id -> res.country; account_id -> account.account; account_root_id -> account.root; currency_id -> res.currency; partner_id -> res.partner; product_uom_id -> uom.uom; product_id -> product.product; product_uom_category_id -> uom.category; reconcile_model_id -> account.reconcile.model; payment_id -> account.payment; statement_line_id -> account.bank.statement.line; statement_id -> account.bank.statement; tax_ids -> account.tax; tax_line_id -> account.tax; tax_group_id -> account.tax.group; tax_repartition_line_id -> account.tax.repartition.line; tax_tag_ids -> account.account.tag; full_reconcile_id -> account.full.reconcile; analytic_account_id -> account.analytic.account; analytic_tag_ids -> account.analytic.tag; create_uid -> res.users; write_uid -> res.users. Many2many fields: tax_ids, tax_tag_ids, analytic_tag_ids.


Show me the relational structure of website.sale.extra.field.

Response: The website.sale.extra.field model has 4 relational fields: website_id -> website; field_id -> ir.model.fields; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


Tell me about the overhead.time model.

Response: The overhead.time model represents Overhead Time Management in the ERP system. It contains 10 fields and is used to manage overhead time management data. Key fields include: product, cost_hr, mrp_workcenter_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What is the mailing.mailing model?

Response: The mailing.mailing model represents Mass Mailing in the ERP system. It contains 90 fields and is used to manage mass mailing data. Key fields include: active, subject, preview, email_from, sent_date, schedule_date, body_arch, body_html, attachment_ids, keep_archives, campaign_id, source_id, medium_id, state, color, user_id, mailing_type, reply_to_mode, reply_to, mailing_model_real, mailing_model_id, mailing_model_name, mailing_domain, mail_server_id, contact_list_ids, contact_ab_pc, unique_ab_testing, kpi_mail_required, mailing_trace_ids, total, scheduled, expected, ignored, sent, delivered, opened, clicked, replied, bounced, failed, received_ratio, opened_ratio, replied_ratio, bounced_ratio, clicks_ratio, next_departure, use_leads, crm_lead_count, sale_quotation_count, sale_invoiced_amount, rfm_segment_id, lang, model_object_field, sub_object, sub_model_object_field, null_value, copyvalue, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, name.


What does the ir.actions.act_window_close model represent?

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


How is setu.rfm.segment used in the system?

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.


List all fields in the intrawarehouse.transfer model.

Response: The intrawarehouse.transfer model has 8 fields: interawarehouse_transfer_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: one2many: 1, integer: 1, char: 1, many2one: 2, datetime: 3.


List all fields in the calendar.alarm_manager model.

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


What are the technical details of hr.employee.base?

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


How do I use the sh.purchase.bill.summary.wizard model?

Response: To use the sh.purchase.bill.summary.wizard model, you need to provide values for required fields: sh_start_date, sh_end_date, sh_partner_ids. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


Describe the field structure of pos.promotion.discount.order.

Response: The pos.promotion.discount.order model has 15 fields: active, minimum_amount, discount, discount2, multi_discount, max_discount_amount, discount_fixed_amount, promotion_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 1, float: 5, char: 2, many2one: 3, integer: 1, datetime: 3.


What are common use cases for cancel.credit.limit?

Response: To use the cancel.credit.limit model, you need to provide values for required fields: limit_id, reason. 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 lost.product implemented technically?

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


What are the technical details of account.report.partner.ledger?

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


What operations can I perform on generate.closing.entries?

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


What modules define pos.promotion.discount.order?

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


Tell me about the account.reconcile.model.line model.

Response: The account.reconcile.model.line model represents Rules for the reconciliation model in the ERP system. It contains 24 fields and is used to manage rules for the reconciliation model data. Key fields include: model_id, match_total_amount, match_total_amount_param, rule_type, company_id, sequence, account_id, journal_id, label, amount_type, show_force_tax_included, force_tax_included, amount, amount_string, tax_ids, analytic_account_id, analytic_tag_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Describe the field structure of all.redeem.rule.

Response: The all.redeem.rule model has 12 fields: name, min_amt, max_amt, reward_amt, loyality_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 4, many2one: 3, datetime: 3.


What models are connected to analytic.sale.order.line?

Response: The analytic.sale.order.line model has 9 relational fields: product_id -> product.product; product_uom -> uom.uom; analytic_tag_ids -> account.analytic.tag; tax_ids -> account.tax; subscription_product_line_id -> account.analytic.account; not_subscription_product_line_id -> account.analytic.account; currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: analytic_tag_ids, tax_ids.


How is cust.credit.limit.data used in the system?

Response: The cust.credit.limit.data model represents cust.credit.limit.data in the ERP system. It contains 11 fields and is used to manage cust.credit.limit.data data. Key fields include: company_id, branch_id, partner_id, cust_credit_line, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What does the account.analytic.tag model represent?

Response: The account.analytic.tag model represents Analytic Tags in the ERP system. It contains 39 fields and is used to manage analytic tags data. Key fields include: color, active, active_analytic_distribution, analytic_distribution_ids, name, company_id, branch_id, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.