What are common use cases for purchase.bill.union?

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


What does the pos.payment.edc model represent?

Response: The pos.payment.edc model represents Pos Payment EDC in the ERP system. It contains 44 fields and is used to manage pos payment edc data. Key fields include: name, payment_state, payment_type, order_number, resp_data, pos_order_id, edc_type, version, trans_type, trans_amount, other_amount, pan, expiry_date, resp_code, rrn, approval_code, date, time, merchant_id, terminal_id, offline_flag, cardholder_name, pan_cashier_card, invoice_number, batch_number, issuer_id, installment_flag, dcc_flag, reedem_flag, info_amount, dcc_decimal_place, dcc_currency_name, dcc_exchange_rate, coupon_flag, filler, pos_branch_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What modules define mrp.workcenter?

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


Describe the field structure of account.asset.fiscal.line.

Response: The account.asset.fiscal.line model has 14 fields: name, sequence, asset_id, amount_fiscal, remaining_value_fiscal, depreciated_value_fiscal, depreciation_date_fiscal, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 2, many2one: 3, float: 3, date: 1, datetime: 3.


How is whatsapp.template implemented technically?

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


What operations can I perform on qiscus.template?

Response: To use the qiscus.template model, you need to provide values for required fields: none. Readonly fields: activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


What are common use cases for create.purchase.request.direct.lines?

Response: To use the create.purchase.request.direct.lines model, you need to provide values for required fields: wiz_id, name, product_uom_id. Readonly fields: wiz_id, rem_qty, 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 forecast.quantity?

Response: The forecast.quantity model has 11 fields: schedule_date, reference, product_id, source_location, destination_location, forecast_qty, product_uom, state, id, display_name, __last_update. Field types distribution: datetime: 2, many2one: 2, char: 4, float: 1, selection: 1, integer: 1.


What models are connected to checklist.reason?

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


What are the available fields for resource.test?

Response: The resource.test model has 12 fields: name, resource_id, company_id, resource_calendar_id, tz, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 5, selection: 1, integer: 1, datetime: 3.


Tell me about the account.ebupot model.

Response: The account.ebupot model represents Account E-Bupot in the ERP system. It contains 18 fields and is used to manage account e-bupot data. Key fields include: year, name, is_used, invoice_ids, tax_report_id, date_from, date_to, partner_id, company_id, ebupot_template, tahun_pajak, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What is the base.geo_provider model?

Response: The base.geo_provider model represents Geo Provider in the ERP system. It contains 9 fields and is used to manage geo provider data. Key fields include: tech_name, name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What are the available fields for pos.global.discount?

Response: The pos.global.discount model has 14 fields: name, amount, product_id, reason, type, branch_ids, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, float: 1, many2one: 4, selection: 1, many2many: 1, integer: 1, datetime: 3.


How does pos.generate.efaktur relate to other models?

Response: The pos.generate.efaktur model has 8 relational fields: invoice_ids -> pos.generate.efaktur.invoice; digunggung_ids -> pos.generate.efaktur.digunggung; gabungan_ids -> pos.generate.efaktur.gabungan; other_ids -> pos.generate.efaktur.other; branch_id -> res.branch; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What are common use cases for res.city?

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


How is purchase.order.split implemented technically?

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


Describe the report.equip3_pos_general.pos_sale_report_template model in Odoo.

Response: The report.equip3_pos_general.pos_sale_report_template model represents Template Report of sale in the ERP system. It contains 3 fields and is used to manage template report of sale data. Key fields include: id, display_name, __last_update.


Tell me about the account.multipayment.credit model.

Response: The account.multipayment.credit model represents   in the ERP system. It contains 22 fields and is used to manage   data. Key fields include: line_id, currency_id, invoice_id, account_id, invoice_date, invoice_date_due, original_amount, base_amount, original_unreconcile, base_unreconcile, is_full_reconcile, amount, payment_id, account_reverse_ids, account_reverse_total, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How is stock.picking.type used in the system?

Response: The stock.picking.type model represents Picking Type in the ERP system. It contains 43 fields and is used to manage picking type data. Key fields include: name, color, sequence, sequence_id, sequence_code, default_location_src_id, default_location_dest_id, return_picking_type_id, show_entire_packs, warehouse_id, active, use_create_lots, use_existing_lots, show_operations, show_reserved, count_picking_draft, count_picking_ready, count_picking, count_picking_waiting, count_picking_late, count_picking_backorders, rate_picking_late, rate_picking_backorders, barcode, company_id, code, count_mo_todo, count_mo_waiting, count_mo_late, use_create_components_lots, branch_id, is_transit, filter_location_ids, stock_picking_dasboard_id, picking_ids, pos_branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How does delivery.carrier relate to other models?

Response: The delivery.carrier model has 8 relational fields: company_id -> res.company; product_id -> product.product; country_ids -> res.country; state_ids -> res.country.state; price_rule_ids -> delivery.price.rule; website_id -> website; create_uid -> res.users; write_uid -> res.users. Many2many fields: country_ids, state_ids.


How does sh.mrp.pass.fail relate to other models?

Response: The sh.mrp.pass.fail model has 6 relational fields: product_id -> product.product; sh_quality_point_id -> sh.qc.point; mrp_id -> mrp.production; workorder_id -> mrp.workorder; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What business logic is in res.users.qiscuss?

Response: To use the res.users.qiscuss model, you need to provide values for required fields: email, password. 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.payment.request model.

Response: The vendor.payment.request model represents Vendor Payment Request in the ERP system. It contains 16 fields and is used to manage vendor payment request data. Key fields include: name, user_id, description, company_id, branch_id, component_line_id, state, amount_total, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What are the technical details of stock.warn.insufficient.qty.repair?

Response: The stock.warn.insufficient.qty.repair model is defined in module: repair. It has 0 computed fields: . Stored computed fields: none.


Show me the relational structure of stock.scrap.approval.matrix.

Response: The stock.scrap.approval.matrix model has 18 relational fields: company_id -> res.company; warehouse_id -> stock.warehouse; branch_id -> res.branch; sc_approval_matrix_line_ids -> stock.scrap.approval.matrix.line; campaign_id -> utm.campaign; source_id -> utm.source; medium_id -> utm.medium; 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: message_partner_ids, message_channel_ids.


What modules define currency.log.api?

Response: The currency.log.api model is defined in module: equip3_accounting_multicurrency. It has 0 computed fields: . Stored computed fields: none.


What operations can I perform on ir.module.module.exclusion?

Response: To use the ir.module.module.exclusion model, you need to provide values for required fields: none. Readonly fields: exclusion_id, state, 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 sh.tc.top.customer.wizard?

Response: The sh.tc.top.customer.wizard model has 11 relational fields: team_id -> crm.team; currency_id -> res.currency; company_ids -> res.company; company_id -> res.company; top_customer_ids -> list.customer; top_customer_compare_ids -> list.customer.compare; lost_cust_ids -> lost.customer; new_cust_ids -> new.customer; sale_currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: company_ids.


What modules define res.company?

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


How does report.equip3_pos_report.report_pos_payment relate to other models?

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


How to query change.production.qty data?

Response: To use the change.production.qty model, you need to provide values for required fields: mo_id, product_qty. 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 pos.order?

Response: To use the pos.order model, you need to provide values for required fields: name, amount_tax, amount_total, amount_paid, amount_return, company_id, pricelist_id, session_id. Readonly fields: name, date_order, amount_tax, amount_total, amount_paid, amount_return, lines, company_id, pricelist_id, session_id, account_move, picking_count, failed_pickings, nb_print, pos_reference, sale_journal, fiscal_position_id, payment_ids, session_move_id, is_invoiced, is_tipped, tip_amount, cashier, currency_rate, receivable_invoice_count, payment_paid, total_before_discount, total_discount, total_after_discount, total_after_discount_w_o_tax, pos_coupon_id, is_past_date, self_order_id, statement_ids, signature, parent_id, sale_id, margin, booking_id, pos_branch_id, is_paid_full, currency_id, state, removed_user_id, receipt_count, return_order_id, return_order_state, ean13, is_show_pos_payment, customer_deposit_amount, plus_point, redeem_point, redeem_point_refund, location_id, date_order_str, amount_sales, amount_discount, amount_payment, amount_ppn, amount_nett_sales, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


List all fields in the asset.asset.revalue model.

Response: The asset.asset.revalue model has 22 fields: reason, asset_id, remaining_value, amount, journal_id, method_number, method_period, user_id, date, prev_method_number, prev_method_period, dispose_price, company_id, company_currency_id, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 8, monetary: 2, integer: 5, date: 1, float: 1, datetime: 3.


How to create records in product.removal?

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


What fields does account.loan.post have?

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


What are common use cases for stock.scrap?

Response: To use the stock.scrap model, you need to provide values for required fields: name, company_id, product_id, scrap_location_id, product_uom_id, location_id, scrap_qty. Readonly fields: name, product_uom_category_id, tracking, move_id, state, filter_location_ids, filter_product_ids, product_usage_state, analytic_tag_ids, filter_lot_ids, filter_package_ids, filter_owner_ids, product_state, usage_type, warehouse_id, date_done, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


Describe the field structure of stock.location.tag.

Response: The stock.location.tag model has 10 fields: name, color, opacity, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 3, many2one: 2, datetime: 3.


How is bus.bus used in the system?

Response: The bus.bus model represents Communication Bus in the ERP system. It contains 9 fields and is used to manage communication bus data. Key fields include: channel, message, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How to query sale.order.option data?

Response: To use the sale.order.option model, you need to provide values for required fields: name, product_id, price_unit, uom_id, quantity. Readonly fields: is_present, product_uom_category_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


What models are connected to approval.request.reject?

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


What are the relationships in mail.blacklist.remove?

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


How does auth_totp.wizard relate to other models?

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 to query warehouse.capacity.excel.report data?

Response: To use the warehouse.capacity.excel.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.


Can you explain the purpose of sh.payment.report.wizard?

Response: The sh.payment.report.wizard model represents payment report wizard model in the ERP system. It contains 17 fields and is used to manage payment report wizard model data. Key fields include: date_start, date_end, state, user_ids, company_ids, company_id, currency_precision, user_data_dic, grand_journal_dic, branch_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What business logic is in ir.server.object.lines?

Response: To use the ir.server.object.lines model, you need to provide values for required fields: col1, value, evaluation_type. 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.product.bom.line.

Response: The pos.product.bom.line model has 11 fields: pos_bom_id, product_id, product_qty, product_uom_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.


Describe the list.pay model in Odoo.

Response: The list.pay model represents list.pay in the ERP system. It contains 16 fields and is used to manage list.pay data. Key fields include: order_dic_id, cash, bank, total, invoice, customer, invoice_date, payments_date, salesperson, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Show me the relational structure of mail.template.

Response: The mail.template model has 10 relational fields: model_id -> ir.model; attachment_ids -> ir.attachment; report_template -> ir.actions.report; mail_server_id -> ir.mail_server; ref_ir_act_window -> ir.actions.act_window; model_object_field -> ir.model.fields; sub_object -> ir.model; sub_model_object_field -> ir.model.fields; create_uid -> res.users; write_uid -> res.users. Many2many fields: attachment_ids.


What foreign keys exist in project.sale.line.employee.map?

Response: The project.sale.line.employee.map model has 8 relational fields: project_id -> project.project; employee_id -> hr.employee; sale_line_id -> sale.order.line; company_id -> res.company; timesheet_product_id -> product.product; currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What does the website model represent?

Response: The website model represents Website in the ERP system. It contains 64 fields and is used to manage website data. Key fields include: name, domain, country_group_ids, company_id, language_ids, default_lang_id, auto_redirect_lang, cookies_bar, logo, social_twitter, social_facebook, social_github, social_linkedin, social_youtube, social_instagram, social_default_image, has_social_default_image, google_analytics_key, google_management_client_id, google_management_client_secret, google_search_console, google_maps_api_key, user_id, cdn_activated, cdn_url, cdn_filters, partner_id, menu_id, homepage_id, custom_code_head, custom_code_footer, robots_txt, favicon, theme_id, specific_user_account, auth_signup_uninvited, channel_id, is_enable_vendor_notification, user_ids, is_enable_auto_portal_user, is_enable_company_portal_user, is_enable_company_contact_portal_user, crm_default_team_id, crm_default_user_id, karma_profile_min, pricelist_id, currency_id, salesperson_id, salesteam_id, pricelist_ids, all_pricelist_ids, cart_recovery_mail_template_id, cart_abandoned_delay, shop_ppg, shop_ppr, shop_extra_field_ids, warehouse_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What are the relationships in ir.qweb.field.date?

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


Describe the implementation of base.language.install.

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


How to create records in apply.voucher?

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


What are the technical details of mail.moderation?

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


Tell me about the limit.approval.matrix model.

Response: The limit.approval.matrix model represents Limit Approval Matrix in the ERP system. It contains 45 fields and is used to manage limit approval matrix data. Key fields include: name, company_id, branch_id, config, minimum_amt, maximum_amt, approver_matrix_line_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.


How does product.supplierinfo relate to other models?

Response: The product.supplierinfo model has 36 relational fields: purchase_requisition_id -> purchase.requisition; purchase_requisition_line_id -> purchase.requisition.line; name -> res.partner; product_uom -> uom.uom; product_uom_category_id -> uom.category; product_uom_new -> uom.uom; company_id -> res.company; currency_id -> res.currency; product_id -> product.product; product_tmpl_id -> product.template; request_partner_id -> res.partner; vendor_pricelist_approval_matrix -> vendor.pricelist.approval.matrix; approval_ids -> product.supplierinfo.approval; user_approval_ids -> res.users; current_user -> res.users; branch_id -> res.branch; approval_matrix_line_id -> product.supplierinfo.approval; name_old -> res.partner; branch_id_old -> res.branch; product_id_old -> product.product; product_tmpl_id_old -> product.template; product_uom_old -> uom.uom; company_id_old -> res.company; currency_id_old -> res.currency; vendor_pricelist_approval_matrix_old -> vendor.pricelist.approval.matrix; 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: user_approval_ids, message_partner_ids, message_channel_ids.


What modules define coupon.coupon?

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


What are the technical details of bill.payment.report.xls?

Response: The bill.payment.report.xls model is defined in module: sh_purchase_reports. It has 0 computed fields: . Stored computed fields: none.


What data can be stored in invoice.template.table?

Response: The invoice.template.table model has 10 fields: template_id, field_id, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, integer: 2, char: 1, datetime: 3.


What methods are available in crm.salesperson.tracking?

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


How is account.asset.asset used in the system?

Response: The account.asset.asset model represents Asset/Revenue Recognition in the ERP system. It contains 86 fields and is used to manage asset/revenue recognition data. Key fields include: entry_count, name, code, value, currency_id, note, category_id, date, active, partner_id, method_number, method_period, method_end, method_progress_factor, value_residual, method_time, prorata, depreciation_line_ids, salvage_value, invoice_id, type, account_analytic_id, analytic_tag_ids, first_depreciation_manual_date, user_id, is_monthly_depreciation, is_reset_january, months_remaining, method, cut_off_asset_date, date_first_depreciation, fiscal_category_id, method_fiscal, asset_type, asset_type_1, sub_asset_type, non_building_type, is_monthly_depreciation_fiscal, is_reset_january_fiscal, months_remaining_fiscal, method_number_fiscal, method_period_fiscal, method_end_fiscal, depreciation_line_ids_fiscal, asset_history_lines_ids, asset_value_residual, account_cip_id, state, state1, state2, approval_matrix_id, approved_matrix_ids, is_approval_matrix, is_approve_button, approval_matrix_line_id, request_partner_id, company_id, branch_id, asset_sequence, product_id, fiscal_prorata_temporis, location, po_ref, asset_post_entries_count, 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.


Tell me about the website.mass_mailing.popup model.

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


How do I use the base.geo_provider model?

Response: To use the base.geo_provider model, you need to provide values for required fields: none. Readonly fields: tech_name, name, 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.internal.transfer?

Response: To use the account.internal.transfer model, you need to provide values for required fields: none. Readonly fields: currency_id, create_date, create_uid, filter_branch_ids, approval_matrix_id, is_internal_approval_matrix, approval_matrix_line_id, is_approve_button, state1, state2, analytic_group_ids, name, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, access_url, access_warning, id, display_name, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


What fields does base_import.tests.models.char.stillreadonly have?

Response: The base_import.tests.models.char.stillreadonly 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 data can be stored in account.journal?

Response: The account.journal model has 92 fields: kanban_dashboard, kanban_dashboard_graph, json_activity_data, show_on_dashboard, color, check_manual_sequencing, check_sequence_id, check_next_number, check_printing_payment_method_selected, edi_format_ids, compatible_edi_ids, sequence_id, sequence_number_next, refund_sequence_id, refund_sequence_number_next, pos_payment_method_ids, name, code, active, type_control_ids, account_control_ids, default_account_type, default_account_id, payment_debit_account_id, payment_credit_account_id, suspense_account_id, restrict_mode_hash_table, sequence, invoice_reference_type, invoice_reference_model, currency_id, company_id, country_code, refund_sequence, sequence_override_regex, inbound_payment_method_ids, outbound_payment_method_ids, at_least_one_inbound, at_least_one_outbound, profit_account_id, loss_account_id, company_partner_id, bank_account_id, bank_statements_source, bank_acc_number, bank_id, sale_activity_type_id, sale_activity_user_id, sale_activity_note, alias_id, alias_domain, alias_name, journal_group_ids, secure_sequence_id, use_reconcile, branch_id, type, is_fiscal_book_exclude, pos_method_type, decimal_rounding, 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: text: 5, boolean: 15, integer: 10, many2one: 25, char: 11, many2many: 9, one2many: 5, selection: 7, date: 2, datetime: 3.


What operations can I perform on ir.model.access?

Response: To use the ir.model.access model, you need to provide values for required fields: name, model_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 report.equip3_pos_report.report_open_session?

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


How to create records in crm.phonecall2phonecall?

Response: To use the crm.phonecall2phonecall model, you need to provide values for required fields: name, action. Readonly fields: name, user_id, contact_name, phone, tag_ids, date, team_id, action, partner_id, note, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


Describe the many2many relations for account.deposit.reconcile.

Response: The account.deposit.reconcile model has 3 relational fields: allocation_line_ids -> invoice.deposit.line.reconcile; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


How to query report.equip3_inventory_masterdata.report_product_tmpl_forecast data?

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


How to query website.mass_mailing.popup data?

Response: To use the website.mass_mailing.popup 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 common use cases for budget.change.req?

Response: To use the budget.change.req model, you need to provide values for required fields: requested_id, budget_std_id, date, state, company_id. Readonly fields: name, state, approval_matrix, is_allowed_to_approval_matrix, approval_matrix_line_id, is_approve_button, company_id, currency_id, state1, state2, 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 hr.employee.public model in Odoo.

Response: The hr.employee.public model represents Public Employee in the ERP system. It contains 42 fields and is used to manage public employee data. Key fields include: create_date, name, active, department_id, job_id, job_title, company_id, address_id, mobile_phone, work_phone, work_email, work_location, user_id, resource_id, resource_calendar_id, tz, color, child_ids, image_1920, image_1024, image_512, image_256, image_128, parent_id, coach_id, user_partner_id, subordinate_ids, hr_presence_state, last_activity, last_activity_time, hr_icon_display, goal_ids, badge_ids, has_badges, direct_badge_ids, child_all_count, id, display_name, create_uid, write_uid, write_date, __last_update.


What methods are available in z.report.wizard?

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


What operations can I perform on account.payment.reconcile.line?

Response: To use the account.payment.reconcile.line model, you need to provide values for required fields: currency_id, payment_type. Readonly fields: currency_id, payment_type, partner_id, amount_due, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


Show me the fields of report.accounting_pdf_reports.report_journal.

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


What models are connected to cancel.supplier.memory?

Response: The cancel.supplier.memory model has 3 relational fields: supplier_id -> product.supplierinfo; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What are common use cases for ir.model.access?

Response: To use the ir.model.access model, you need to provide values for required fields: name, model_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 foreign keys exist in mrp.document?

Response: The mrp.document model has 8 relational fields: ir_attachment_id -> ir.attachment; create_uid -> res.users; write_uid -> res.users; company_id -> res.company; original_id -> ir.attachment; website_id -> website; theme_template_id -> theme.ir.attachment; partner -> res.partner. Many2many fields: none.


What is the mail.message.subtype model?

Response: The mail.message.subtype model represents Message subtypes in the ERP system. It contains 16 fields and is used to manage message subtypes data. Key fields include: name, description, internal, parent_id, relation_field, res_model, default, sequence, hidden, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Which fields in gamification.goal.definition are computed?

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


What foreign keys exist in purchase.agreement.approval.matrix?

Response: The purchase.agreement.approval.matrix model has 17 relational fields: company_id -> res.company; branch_id -> res.branch; approval_matrix_purchase_agreement_line_ids -> approval.matrix.purchase.agreement.line; campaign_id -> utm.campaign; source_id -> utm.source; medium_id -> utm.medium; 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: message_partner_ids, message_channel_ids.


What foreign keys exist in report.stock.quantity?

Response: The report.stock.quantity model has 5 relational fields: product_tmpl_id -> product.template; product_id -> product.product; move_ids -> stock.move; company_id -> res.company; warehouse_id -> stock.warehouse. Many2many fields: none.


Describe the account.invoice.report model in Odoo.

Response: The account.invoice.report model represents Invoices Statistics in the ERP system. It contains 28 fields and is used to manage invoices statistics data. Key fields include: move_id, journal_id, company_id, company_currency_id, partner_id, commercial_partner_id, country_id, invoice_user_id, move_type, state, payment_state, fiscal_position_id, invoice_date, quantity, product_id, product_uom_id, product_categ_id, invoice_date_due, account_id, analytic_account_id, price_subtotal, price_average, team_id, branch_id, pos_branch_id, id, display_name, __last_update.


What methods are available in warehouse.capacity.report?

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


Tell me about the ctm.dynamic.balance.sheet.report model.

Response: The ctm.dynamic.balance.sheet.report model represents ctm.dynamic.balance.sheet.report in the ERP system. It contains 29 fields and is used to manage ctm.dynamic.balance.sheet.report data. Key fields include: company_id, journal_ids, account_ids, account_tag_ids, analytic_ids, analytic_tag_ids, display_account, target_move, date_from, date_to, analytic_group_ids, comparison, previous, report_currency_id, book, consolidate, comp_detail, filter_budget, budget, debit_credit, entities_comparison, all_account, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What are the technical details of mrp.bom.tools?

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


What foreign keys exist in return.approval.matrix.line?

Response: The return.approval.matrix.line model has 8 relational fields: approver -> res.users; last_approved -> res.users; return_approval_matrix_id1 -> return.approval.matrix; picking_id -> stock.picking; approved_users -> res.users; dev_rma_id -> dev.rma.rma; create_uid -> res.users; write_uid -> res.users. Many2many fields: approver, approved_users.


What modules define image.mixin?

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


What data can be stored in account.cash.flow.statement?

Response: The account.cash.flow.statement model has 21 fields: date_from, date_to, today, levels, account_ids, company_ids, comparison, previous, comp_detail, type_report, journal_ids, target_move, report_currency_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: date: 3, selection: 4, many2many: 3, integer: 2, boolean: 1, many2one: 4, char: 1, datetime: 3.


What is the pos.payment.method model?

Response: The pos.payment.method model represents Point of Sale Payment Methods in the ERP system. It contains 54 fields and is used to manage point of sale payment methods data. Key fields include: name, receivable_account_id, is_cash_count, cash_journal_id, split_transactions, open_session_ids, config_ids, company_id, use_payment_terminal, hide_use_payment_terminal, active, apply_charges, fees_amount, fees_type, fees_product_id, optional, shortcut_key, jr_use_for, fullfill_amount, shortcut_keyboard, cheque_bank_information, discount, discount_type, discount_amount, discount_product_id, is_bank, generate_invoice, invoice_partner_id, able_use_card, is_mdr, is_mdr_discount, mdr_paid_by, mdr_intermediary_account_id, mdr_ids, is_receivables, account_journal_id, is_receivables_show, is_deposit_payment, is_edc_bca, is_edc_manual_input, edc_port, trans_type, trans_type_code, is_payment_edc, payment_edc_url, installment_tenor_ids, installment_plan, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How do I use the stock.warn.insufficient.qty model?

Response: To use the stock.warn.insufficient.qty model, you need to provide values for required fields: product_id, location_id, quantity, product_uom_name. Readonly fields: product_id, location_id, quant_ids, quantity, product_uom_name, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.


What are the available fields for repair.line?

Response: The repair.line model has 26 fields: name, repair_id, company_id, currency_id, type, product_id, invoiced, price_unit, price_subtotal, tax_id, product_uom_qty, product_uom, product_uom_category_id, invoice_line_id, location_id, location_dest_id, move_id, lot_id, state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 1, many2one: 13, selection: 2, boolean: 1, float: 3, many2many: 1, integer: 1, char: 1, datetime: 3.


Describe the many2many relations for product.margin.

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


What are the relationships in gamification.challenge.line?

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


Show me the fields of sh.custom.model.tab.

Response: The sh.custom.model.tab model has 18 fields: name, label, groups, sequence, view_id, tab_list, invisible_tab, sh_position, parent_view_id, parent_model, parent_model_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 5, many2many: 1, integer: 2, many2one: 4, selection: 2, boolean: 1, datetime: 3.


Describe the warranty.settings model in Odoo.

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


What is the payment.voucher.line model?

Response: The payment.voucher.line model represents Payment voucher Line in the ERP system. It contains 18 fields and is used to manage payment voucher line data. Key fields include: invoice_number_id, invoice_date, currency_id, untaxed_amount, tax_amount, total_invoice_amount, amount_due, amount, voucher_id, state, voucher_state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How does res.branch relate to other models?

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


What does the web_editor.converter.test model represent?

Response: The web_editor.converter.test model represents Web Editor Converter Test in the ERP system. It contains 18 fields and is used to manage web editor converter test data. Key fields include: char, integer, float, numeric, many2one, binary, date, datetime, selection_str, html, text, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What modules define uom.category?

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


How to create records in list.category?

Response: To use the list.category 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 stock.warehouse?

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


Tell me about the stock.scrap.approval.matrix model.

Response: The stock.scrap.approval.matrix model represents Stock Scrap Approval Matrix in the ERP system. It contains 44 fields and is used to manage stock scrap approval matrix data. Key fields include: name, company_id, warehouse_id, branch_id, approval_line_count, sc_approval_matrix_line_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.


How do I use the service.work.order.line model?

Response: To use the service.work.order.line model, you need to provide values for required fields: product_id. Readonly fields: sequence2, product_id, description, initial_demand, remaining, quantity_done, account_analytic_tag_ids, state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


How is asset.cip.line used in the system?

Response: The asset.cip.line model represents asset.cip.line in the ERP system. It contains 15 fields and is used to manage asset.cip.line data. Key fields include: product_id, label, account_id, amount, cip_id, move_id, move_check, move_posted_check, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


List all fields in the replace.product.wizard model.

Response: The replace.product.wizard model has 11 fields: product_id, replace_product_id, replace_qty, is_same_product, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, float: 1, boolean: 1, integer: 1, char: 1, datetime: 3.


What does the res.users.apikeys.show model represent?

Response: The res.users.apikeys.show model represents res.users.apikeys.show in the ERP system. It contains 4 fields and is used to manage res.users.apikeys.show data. Key fields include: key, id, display_name, __last_update.


What are the technical details of sale.summary.commission.report?

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


What models are connected to field.conditional.access?

Response: The field.conditional.access model has 6 relational fields: access_management_id -> access.management; model_id -> ir.model; attrs_field_id -> ir.model.fields; domain_field_id -> ir.model.fields; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


What are the available fields for vendor.evaluation?

Response: The vendor.evaluation model has 108 fields: name, state, vendor, period_start, period_end, manager, is_manager, user_id, price_check, price_factor, price, price_cmt, delivery_check, delivery_factor, delivery, delivery_cmt, quality_check, quality_factor, quality, quality_cmt, document_check, document_factor, document, document_cmt, commitment_check, commitment_factor, commitment, commitment_cmt, dependability_check, dependability_factor, dependability, dependability_cmt, skill_check, skill_factor, skill, skill_cmt, support_check, support_factor, support, support_cmt, relation_check, relation_factor, relation, relation_cmt, other_check, other_factor, other, other_cmt, final_point, final_rate, on_time_rate, on_time_rate_check, on_time_rate_factor, on_time_rate_star, on_time_rate_cmt, fulfillment, fulfillment_check, fulfillment_factor, fulfillment_star, fulfillment_cmt, fulfillment_avg, on_time_rate_avg, final_point_avg, vendor_evaluation_count, evaluation_template_id, evaluation_eval_ids, email, business, date, final_cmt, branch_id, company_id, on_time_rate_res, fulfillment_res, vendor_res, final_point_res, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 20, selection: 16, many2one: 12, date: 5, boolean: 18, integer: 18, float: 9, one2many: 5, many2many: 2, datetime: 3.


What operations can I perform on purchase.request.line.make.purchase.order?

Response: To use the purchase.request.line.make.purchase.order model, you need to provide values for required fields: supplier_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.


Tell me about the mailing.contact.subscription model.

Response: The mailing.contact.subscription model represents Mass Mailing Subscription Information in the ERP system. It contains 13 fields and is used to manage mass mailing subscription information data. Key fields include: contact_id, list_id, opt_out, unsubscription_date, message_bounce, is_blacklisted, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Describe the account.move.reversal model in Odoo.

Response: The account.move.reversal model represents Account Move Reversal in the ERP system. It contains 18 fields and is used to manage account move reversal data. Key fields include: move_ids, new_move_ids, date_mode, date, reason, refund_method, journal_id, company_id, residual, currency_id, move_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How does analytic.sale.order.line relate to other models?

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.


Show me the fields of pos.remote.session.

Response: The pos.remote.session model has 10 fields: message, config_ids, action, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 1, many2many: 1, selection: 1, integer: 1, char: 1, many2one: 2, datetime: 3.


What foreign keys exist in ks.sales.forecast.report?

Response: The ks.sales.forecast.report model has 3 relational fields: binding_model_id -> ir.model; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


Show me the relational structure of ir.http.

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


How do I use the report.equip3_accounting_reports.debt_collection model?

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


How do I use the hide.filters.groups model?

Response: To use the hide.filters.groups model, you need to provide values for required fields: model_id. Readonly fields: model_name, 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 limit.request.

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


What are the relationships in dev.credit.note.wizard?

Response: The dev.credit.note.wizard model has 8 relational fields: rma_id -> dev.rma.rma; product_line_ids -> credit.note.product.lines; sale_id -> sale.order; purchase_id -> purchase.order; purchase_ids -> purchase.order; sale_ids -> sale.order; create_uid -> res.users; write_uid -> res.users. Many2many fields: purchase_ids, sale_ids.


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

Response: The acrux.chat.message model has 23 fields: name, msgid, contact_id, connector_id, date_message, from_me, company_id, error_msg, user_id, ttype, event, template_id, is_direct, text, res_model, res_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 5, many2one: 7, datetime: 4, boolean: 2, selection: 2, text: 1, integer: 2.


What are the technical details of sh.mrp.text?

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


What business logic is in acrux.chat.default.answer?

Response: To use the acrux.chat.default.answer model, you need to provide values for required fields: name, default_answer_type, ttype. Readonly fields: res_model, res_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


What fields does dev.credit.note.wizard have?

Response: The dev.credit.note.wizard model has 14 fields: rma_id, product_line_ids, picking_type_code, sale_id, purchase_id, purchase_ids, sale_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, one2many: 1, selection: 1, many2many: 2, integer: 1, char: 1, datetime: 3.


List all fields in the sh.top.customers.xls model.

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


What operations can I perform on acrux.chat.connector?

Response: To use the acrux.chat.connector model, you need to provide values for required fields: name, sequence, company_id, endpoint, apikey, uuid, border_color, sale_report_id, connector_type, qc_channel. Readonly fields: qc_webhook_url, connection_status, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.


How does budget.purchase.lines relate to other models?

Response: The budget.purchase.lines model has 12 relational fields: purchase_budget_id -> budget.purchase; analytic_account_id -> account.analytic.account; analytic_group_id -> account.analytic.group; product_budget -> account.budget.post; currency_id -> res.currency; company_id -> res.company; parent_analytic_account_id -> account.analytic.account; account_tag_ids -> account.analytic.tag; product_id -> product.product; purchase_order_line_budget_id -> purchase.order.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: account_tag_ids.


What foreign keys exist in report.sh_po_tender_management.report_analyze_quotations?

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


How to create records in mail.alias.mixin?

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


What fields does blanket.approval.matrix.lines have?

Response: The blanket.approval.matrix.lines model has 20 fields: approval_matrix, user_name_ids, sequence, sequence2, order_id, minimum_approver, state_char, time_stamp, feedback, last_approved, approved, approved_users, approval_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, many2many: 2, integer: 4, text: 1, datetime: 4, char: 2, boolean: 1, selection: 1.


What foreign keys exist in crm.phonecall2phonecall?

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


How does account.balance.report relate to other models?

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


Describe the many2many relations for kpi.category.

Response: The kpi.category model has 11 relational fields: parent_id -> kpi.category; child_ids -> kpi.category; 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: user_ids, user_group_ids, access_user_ids, edit_user_ids, edit_user_group_ids, edit_access_user_ids.


Describe the implementation of account.bank.statement.import.

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


What are common use cases for approval.matrix.purchase.request?

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


What does the purchase.request.allocation model represent?

Response: The purchase.request.allocation model represents Purchase Request Allocation in the ERP system. It contains 17 fields and is used to manage purchase request allocation data. Key fields include: purchase_request_line_id, company_id, stock_move_id, purchase_line_id, product_id, product_uom_id, requested_product_uom_qty, allocated_product_qty, open_product_qty, purchase_state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How is kpi.category implemented technically?

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


Which fields in sh.top.selling.products are computed?

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


What modules define warranty.claim.stage?

Response: The warranty.claim.stage model is defined in module: bi_warranty_registration. It has 0 computed fields: . Stored computed fields: none.


List all fields in the repair.line model.

Response: The repair.line model has 26 fields: name, repair_id, company_id, currency_id, type, product_id, invoiced, price_unit, price_subtotal, tax_id, product_uom_qty, product_uom, product_uom_category_id, invoice_line_id, location_id, location_dest_id, move_id, lot_id, state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 1, many2one: 13, selection: 2, boolean: 1, float: 3, many2many: 1, integer: 1, char: 1, datetime: 3.


Show me the fields of pos.order.log.

Response: The pos.order.log model has 45 fields: name, order_json, action, create_date, write_date, config_id, session_id, branch_id, company_id, campaign_id, source_id, medium_id, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, access_url, access_token, access_warning, id, display_name, create_uid, write_uid, __last_update. Field types distribution: char: 8, text: 2, datetime: 3, many2one: 12, one2many: 4, selection: 2, date: 2, boolean: 5, many2many: 2, integer: 5.


What fields does stock.location.route have?

Response: The stock.location.route model has 22 fields: name, active, sequence, rule_ids, product_selectable, product_categ_selectable, warehouse_selectable, supplied_wh_id, supplier_wh_id, company_id, product_ids, categ_ids, warehouse_domain_ids, warehouse_ids, sale_selectable, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, boolean: 5, integer: 2, one2many: 2, many2one: 5, many2many: 3, datetime: 3.


What are the available fields for replenishment.history.wizard?

Response: The replenishment.history.wizard model has 8 fields: html_field, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: html: 1, integer: 1, char: 1, many2one: 2, datetime: 3.


What are common use cases for assign.pr.line.wizard?

Response: To use the assign.pr.line.wizard model, you need to provide values for required fields: none. Readonly fields: name, user_id, product_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 field structure of ai.chat.session.

Response: The ai.chat.session model has 34 fields: name, user_id, config_id, state, session_summary, session_summary_message_count, session_summary_last_updated, auto_compress_enabled, compression_threshold, trim_ratio, message_count, last_activity, total_tokens_used, last_tokens_used, message_ids, job_ids, last_job_id, has_running_job, is_ai_renamed, is_quick_chat, quick_chat_model, quick_chat_res_id, cached_user_message_hash, cached_relevant_memories, cached_system_prompt, thinking_chain, last_frequent_actions_query, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 4, many2one: 5, selection: 1, text: 5, integer: 7, datetime: 5, boolean: 4, float: 1, one2many: 2.


Which fields in report.dynamic_accounts_report.cash_flow are computed?

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


How do I use the acrux.chat.pop.message model?

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


Show me the relational structure of account.bank.statement.line.

Response: The account.bank.statement.line model has 133 relational fields: move_id -> account.move; statement_id -> account.bank.statement; foreign_currency_id -> res.currency; currency_id -> res.currency; partner_id -> res.partner; payment_ids -> account.payment; branch_id -> res.branch; pos_branch_id -> res.branch; voucher_id -> pos.voucher; pos_session_id -> pos.session; pos_statement_id -> pos.order; create_uid -> res.users; write_uid -> res.users; suitable_journal_ids -> account.journal; company_id -> res.company; user_id -> res.users; invoice_user_id -> res.users; preferred_payment_method_id -> account.payment.method; debit_origin_id -> account.move; debit_note_ids -> account.move; edi_document_ids -> account.edi.document; loan_line_id -> account.loan.line; loan_id -> account.loan; journal_bank_id -> account.journal; tax_payment_move_id -> account.move; asset_depreciation_ids -> account.asset.depreciation.line; transaction_ids -> payment.transaction; authorized_transaction_ids -> payment.transaction; purchase_vendor_bill_id -> purchase.bill.union; purchase_id -> purchase.order; sh_invoice_recurring_order_id -> invoice.recurring; period_id -> sh.account.period; fiscal_year -> sh.fiscal.year; stock_move_id -> stock.move; stock_valuation_layer_ids -> stock.valuation.layer; auto_reverse_journal_id -> account.journal; pos_order_ids -> pos.order; team_id -> crm.team; partner_shipping_id -> res.partner; consignment_pos_ids -> pos.order; l10n_id_attachment_id -> ir.attachment; landed_costs_ids -> stock.landed.cost; website_id -> website; discount_account_id -> account.account; warranty_reg_id -> product.warranty; related_project_id -> account.analytic.account; repair_ids -> repair.order; target_commission_id -> sh.target.commision; down_payment_purchase_id -> purchase.order; report_template_id1 -> ir.actions.report; report_template_id -> ir.actions.report; timesheet_ids -> account.analytic.line; approval_matrix_id -> approval.matrix.accounting; approved_matrix_ids -> approval.matrix.accounting.lines; approval_matrix_line_id -> approval.matrix.accounting.lines; analytic_group_ids -> account.analytic.tag; invoice_origin_id -> account.move; request_partner_id -> res.partner; journal_id -> account.journal; company_currency_id -> res.currency; line_ids -> account.move.line; commercial_partner_id -> res.partner; partner_bank_id -> res.partner.bank; payment_id -> account.payment; statement_line_id -> account.bank.statement.line; tax_cash_basis_rec_id -> account.partial.reconcile; tax_cash_basis_move_id -> account.move; reversed_entry_id -> account.move; reversal_move_id -> account.move; fiscal_position_id -> account.fiscal.position; invoice_payment_term_id -> account.payment.term; invoice_line_ids -> account.move.line; invoice_incoterm_id -> account.incoterms; invoice_vendor_bill_id -> account.move; invoice_cash_rounding_id -> account.cash.rounding; bank_partner_id -> res.partner; journal_entries_template -> account.move.template; analytic_tag_dynamic -> account.analytic.tag; approvers_ids -> res.users; approved_user_ids -> res.users; internal_tf_id -> account.internal.transfer; new_invoice_id -> account.move; account_asset_id -> account.asset.asset; customer_deposit_ids -> customer.deposit; vendor_deposit_ids -> vendor.deposit; nomor_seri -> account.efaktur; ebupot_id -> account.ebupot; nomor_seri_bupot -> account.ebupot; l10n_id_replace_invoice_id -> account.move; keterangan_tambahan -> account.keterangan.tambahan; signature_country_id -> res.country; signature_city_id -> res.country.city; currency_revaluation_id -> account.move; children_ids -> account.move; currency_revaluation_ref_id -> account.move; pettycash_id -> account.pettycash; sale_order_reference_id -> sale.order; filter_sale_order_reference_ids -> sale.order; exchange_id -> account.invoice.exchange; assembly_id -> assembly.production.record; stock_scrap_id -> stock.scrap.request; kitchen_id -> kitchen.production.record; purchase_order_id -> purchase.order; swo_ids -> service.work.order; finish_good_rework_id -> finish.good.rework; sale_order_ids -> sale.order; filter_sale_order_ids -> sale.order; purchase_order_ids -> purchase.order; filter_purchase_order_ids -> purchase.order; picking_ids -> stock.picking; filter_picking_ids -> stock.picking; cashback_line_ids -> cashback.line; so_cashback_id -> sale.order; return_picking_ids -> stock.picking; picking_id -> stock.picking; rma_id -> dev.rma.rma; account_invoice_ids -> account.invoice.exchange; pos_order_id -> pos.order; deposit_account_journal_id -> account.journal; create_from_session_id -> pos.session; inventory_id -> stock.inventory; campaign_id -> utm.campaign; source_id -> utm.source; medium_id -> utm.medium; 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. Many2many fields: payment_ids, suitable_journal_ids, transaction_ids, authorized_transaction_ids, analytic_group_ids, analytic_tag_dynamic, approvers_ids, approved_user_ids, customer_deposit_ids, vendor_deposit_ids, filter_sale_order_reference_ids, sale_order_ids, filter_sale_order_ids, purchase_order_ids, filter_purchase_order_ids, picking_ids, filter_picking_ids, return_picking_ids, account_invoice_ids, message_partner_ids, message_channel_ids.


What are common use cases for ms.query?

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


Show me the relational structure of stock.orderpoint.snooze.

Response: The stock.orderpoint.snooze model has 3 relational fields: orderpoint_ids -> stock.warehouse.orderpoint; create_uid -> res.users; write_uid -> res.users. Many2many fields: orderpoint_ids.


How do I use the generate.pos.voucher.wizard model?

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


How to create records in link.tracker.code?

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


How to query report.equip3_accounting_reports.journal_entry_report data?

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


How to create records in crm.lead.product?

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


What are the relationships in efaktur.export?

Response: The efaktur.export model has 4 relational fields: partner_id -> res.partner; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.


Describe the field structure of account.loan.generate.wizard.

Response: The account.loan.generate.wizard model has 9 fields: date, loan_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: date: 1, selection: 1, integer: 1, char: 1, many2one: 2, datetime: 3.


List all fields in the pos.profit.loss.wizard model.

Response: The pos.profit.loss.wizard model has 10 fields: start_dt, end_dt, pos_branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: date: 2, many2one: 3, integer: 1, char: 1, datetime: 3.


How is sh.mrp.qc.alert used in the system?

Response: The sh.mrp.qc.alert model represents MRP Quality Alert Wizard in the ERP system. It contains 11 fields and is used to manage mrp quality alert wizard data. Key fields include: team_id, user_id, sh_priority, alert_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What fields does crm.lead.lost have?

Response: The crm.lead.lost model has 8 fields: lost_reason_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, integer: 1, char: 1, datetime: 3.


What models are connected to account.petty.cash.report?

Response: The account.petty.cash.report model has 6 relational fields: custodian_id -> res.users; main_cash_account_id -> account.account; journal_id -> account.journal; company_id -> res.company; branch_id -> res.branch; create_uid -> res.users. Many2many fields: none.


What modules define queue.jobs.to.done?

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


How is salesperson.tracking.history implemented technically?

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


Describe the many2many relations for mailing.mailing.

Response: The mailing.mailing model has 24 relational fields: attachment_ids -> ir.attachment; campaign_id -> utm.campaign; source_id -> utm.source; medium_id -> utm.medium; user_id -> res.users; mailing_model_id -> ir.model; mail_server_id -> ir.mail_server; contact_list_ids -> mailing.list; mailing_trace_ids -> mailing.trace; rfm_segment_id -> setu.rfm.segment; model_object_field -> ir.model.fields; sub_object -> ir.model; sub_model_object_field -> ir.model.fields; 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: attachment_ids, contact_list_ids, message_partner_ids, message_channel_ids.