What field types are used in pos.promotion.selected.brand? or List all fields in the pos.promotion.selected.brand model.

Response: The pos.promotion.selected.brand model has 16 fields. Field types distribution: boolean: 1, many2many: 3, selection: 2, float: 2, many2one: 3, integer: 1, char: 1, datetime: 3. Computed fields: 2. Field details: active (boolean) [module: equip3_pos_masterdata]; brand_ids (many2many) -> product.brand [module: equip3_pos_masterdata]; type_apply (selection) [required] [module: equip3_pos_masterdata]; gift_based_on (selection) [required] [module: equip3_pos_masterdata]; min_amount_qty (float) [module: equip3_pos_masterdata]; qty_qift (float) [module: equip3_pos_masterdata]; product_ids (many2many) -> product.product [module: equip3_pos_masterdata]; brand_gift_ids (many2many) -> product.brand [module: equip3_pos_masterdata]; promotion_id (many2one) [required] -> pos.promotion [module: equip3_pos_masterdata]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


Describe the whatsapp.template model in Odoo. or Can you explain the purpose of whatsapp.template?

Response: The whatsapp.template model represents whatsapp.template in the ERP system. It contains 10 fields and is used to manage whatsapp.template data. Defined in module: equip3_crm_masterdata. Key fields include: name, message, is_default, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What are common use cases for res.partner.title? or How to create records in res.partner.title?

Response: To use the res.partner.title model, you need to provide values for required fields: name. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [required]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


What are common use cases for res.currency.rate? or What operations can I perform on res.currency.rate?

Response: To use the res.currency.rate model, you need to provide values for required fields: name, currency_id. Readonly fields: currency_id, rate, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [required] [has_default]; currency_id [required] [readonly]; rate [readonly] [computed] [has_default] [no_copy]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


Describe the implementation of stock.quant.package. or What is the module hierarchy for stock.quant.package?

Response: The stock.quant.package model is defined in module: stock. It has 17 computed fields: location_id, company_id, owner_id, weight, weight_uom_name, qty, uom_id, package_weight, maximum_length, maximum_width, maximum_height, maximum_volume, max_weight, package_status, filter_location_id_new, display_name, __last_update. Stored computed fields: location_id, company_id, qty, uom_id, package_weight, package_status. Related fields: maximum_length -> packaging_id.maximum_length, maximum_width -> packaging_id.maximum_width, maximum_height -> packaging_id.maximum_height, maximum_volume -> packaging_id.maximum_volume, max_weight -> packaging_id.max_weight. Original module methods: _compute_package_info, name_get, _compute_complete_name, _search_owner, unpack, action_view_picking, _get_contained_quants, _allowed_to_move_between_transfers.


What are the technical details of ir.actions.act_window? or What methods are available in ir.actions.act_window?

Response: The ir.actions.act_window model is defined in module: base. It has 5 computed fields: views, search_view, xml_id, display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: _check_model, _compute_views, _check_view_mode, _compute_search_view, read, create, unlink, exists, _existing, _get_readable_fields, _compute_xml_id, write, _get_eval_context, get_bindings, _for_xml_id.


Show me the fields of stock.return.picking. or What field types are used in stock.return.picking?

Response: The stock.return.picking model has 20 fields. Field types distribution: many2one: 8, one2many: 2, boolean: 2, text: 1, selection: 2, integer: 1, char: 1, datetime: 3. Computed fields: 5. Field details: picking_id (many2one) -> stock.picking [module: stock]; product_return_moves (one2many) -> stock.return.picking.line [module: stock]; move_dest_exists (boolean) [readonly] [module: stock]; original_location_id (many2one) -> stock.location [module: stock]; parent_location_id (many2one) -> stock.location [module: stock]; company_id (many2one) [readonly] -> res.company [compute: <bound method Field._compute_related of stock.return.picking.company_id>] [not stored] [module: stock] [related: picking_id.company_id]; location_id (many2one) -> stock.location [module: stock]; return_reason (many2one) -> return.reason [module: equip3_inventory_operation]; return_reason_info (text) [module: equip3_inventory_operation]; is_return_possible (boolean) [readonly] [compute: _compute_is_return_possible] [not stored] [module: equip3_inventory_operation]; action (selection) [module: equip3_inventory_operation]; return_line_ids (one2many) -> stock.return.move.line [module: equip3_inventory_operation]; picking_type_code (selection) [readonly] [compute: <bound method Field._compute_related of stock.return.picking.picking_type_code>] [not stored] [module: equip3_inventory_operation] [related: picking_id.picking_type_code]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


Show me the column structure of purchase_order. or What data types are used in purchase_order?

Response: Columns in purchase_order: id (integer) [NOT NULL] [DEFAULT: nextval('purchase_order_id_seq'::regclass)] [PRECISION: 32]; access_token (character varying) [COMMENT: Security Token]; message_main_attachment_id (integer) [PRECISION: 32] [COMMENT: Main Attachment]; name (character varying) [NOT NULL] [COMMENT: Order Reference]; priority (character varying) [COMMENT: Priority]; origin (character varying) [COMMENT: Source Document]; partner_ref (character varying) [COMMENT: Vendor Reference]; date_order (timestamp without time zone) [NOT NULL] [COMMENT: Order Deadline]; date_approve (timestamp without time zone) [COMMENT: Confirmation Date]; partner_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Vendor]; dest_address_id (integer) [PRECISION: 32] [COMMENT: Drop Ship Address]; currency_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Currency]; state (character varying) [COMMENT: Status]; notes (text) [COMMENT: Terms and Conditions]; invoice_count (integer) [PRECISION: 32] [COMMENT: Bill Count]; invoice_status (character varying) [COMMENT: Billing Status]; date_planned (timestamp without time zone) [COMMENT: Receipt Date]; date_calendar_start (timestamp without time zone) [COMMENT: Date Calendar Start]; amount_untaxed (numeric) [COMMENT: Untaxed Amount]; amount_tax (numeric) [COMMENT: Taxes]; amount_total (numeric) [COMMENT: Total]; fiscal_position_id (integer) [PRECISION: 32] [COMMENT: Fiscal Position]; payment_term_id (integer) [PRECISION: 32] [COMMENT: Payment Terms]; incoterm_id (integer) [PRECISION: 32] [COMMENT: Incoterm]; user_id (integer) [PRECISION: 32] [COMMENT: Purchase Representative]; company_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Company]; currency_rate (double precision) [PRECISION: 53] [COMMENT: Currency Rate]; mail_reminder_confirmed (boolean) [COMMENT: Reminder Confirmed]; mail_reception_confirmed (boolean) [COMMENT: Reception Confirmed]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]; picking_count (integer) [PRECISION: 32] [COMMENT: Picking count]; picking_type_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Deliver To]; group_id (integer) [PRECISION: 32] [COMMENT: Procurement Group]; effective_date (timestamp without time zone) [COMMENT: Effective Date]; report_grids (boolean) [COMMENT: Print Variant Grids]; requisition_id (integer) [PRECISION: 32] [COMMENT: Purchase Agreement]; apply_manual_currency_exchange (boolean) [COMMENT: Apply Manual Currency Exchange]; manual_currency_exchange_rate (double precision) [PRECISION: 53] [COMMENT: Manual Currency Exchange Rate]; active_manual_currency_rate (boolean) [COMMENT: active Manual Currency]; internal_id (integer) [PRECISION: 32] [COMMENT: Internal]; inter_transfer_count (integer) [PRECISION: 32] [COMMENT: Internal Transfer]; client_order_id (integer) [PRECISION: 32] [COMMENT: Sale Order Inter Transfer]; discount_method (character varying) [COMMENT: Discount Method]; discount_amount (double precision) [PRECISION: 53] [COMMENT: Discount Amount]; discount_amt (numeric) [COMMENT: - Discount]; discount_type (character varying) [COMMENT: Discount Applies to]; discount_amt_line (double precision) [PRECISION: 53] [COMMENT: - Line Discount]; branch_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Branch]; down_payment_by (character varying) [COMMENT: What do you want to bill?]; amount (double precision) [PRECISION: 53] [COMMENT: Amount]; dp_journal_id (integer) [PRECISION: 32] [COMMENT: Journal]; down_payment_amount (double precision) [PRECISION: 53] [COMMENT: Down Payment]; total_down_payment_amount (double precision) [PRECISION: 53] [COMMENT: Total]; is_down_payment (boolean) [COMMENT: Is Down Payment Invoice]; report_template_id (integer) [PRECISION: 32] [COMMENT: Purchase Template]; sh_purchase_barcode_mobile (character varying) [COMMENT: Mobile Barcode]; sh_purchase_bm_is_cont_scan (character varying) [COMMENT: Continuously Scan?]; merged (boolean) [COMMENT: Merged]; active (boolean) [COMMENT: Active]; product_template_id (integer) [PRECISION: 32] [COMMENT: Product Template]; sign_by (character varying) [COMMENT: Signed By]; designation (character varying) [COMMENT: Designation]; sign_on (timestamp without time zone) [COMMENT: Sign on]; order_report_id (integer) [PRECISION: 32] [COMMENT: Purchase Order Template]; rfq_report_id (integer) [PRECISION: 32] [COMMENT: RFQ Template]; purchase_url (text) [COMMENT: Url]; report_token (character varying) [COMMENT: Access Token]; po_extract_id (integer) [PRECISION: 32] [COMMENT: Extracted From]; po_split_id (integer) [PRECISION: 32] [COMMENT: Splited From]; sh_po_number (integer) [PRECISION: 32] [COMMENT: PO Number]; sh_purchase_order_id (integer) [PRECISION: 32] [COMMENT: PurchaseOrder]; sh_fully_ship (boolean) [COMMENT: Fully Shipped]; sh_partially_ship (boolean) [COMMENT: Partially Shipped]; sh_fully_paid (boolean) [COMMENT: Fully Paid]; sh_partially_paid (boolean) [COMMENT: Partially Paid]; team_id (integer) [PRECISION: 32] [COMMENT: Purchase Team]; agreement_id (integer) [PRECISION: 32] [COMMENT: Purchase Tender]; cancel_lines (boolean) [COMMENT: Cancel Lines]; selected_order (boolean) [COMMENT: Selected Orders]; sh_sale_order_id (integer) [PRECISION: 32] [COMMENT: Sale Order]; po_expiry_date (timestamp without time zone) [COMMENT: PO Expiry Date]; po (boolean) [COMMENT: PO]; exp_po (boolean) [COMMENT: EXP PO]; sent (boolean) [COMMENT: Sent]; is_goods_orders (boolean) [COMMENT: Goods Orders]; is_services_orders (boolean) [COMMENT: Services Orders]; approval_matrix_id (integer) [PRECISION: 32] [COMMENT: Approval Matrix]; destination_location_id (integer) [PRECISION: 32] [COMMENT: Destination Location]; is_delivery_receipt (boolean) [COMMENT: Delivery With Receipt Date]; destination_warehouse_id (integer) [PRECISION: 32] [COMMENT: Destination]; is_single_delivery_destination (boolean) [COMMENT: Single Delivery Destination]; analytic_accounting (boolean) [COMMENT: Analyic Account]; is_revision_po (boolean) [COMMENT: Revison PO]; is_revision_created (boolean) [COMMENT: Revison Created]; revision_order_id (integer) [PRECISION: 32] [COMMENT: Revison Order]; timezone_date (character varying) [COMMENT: Date]; request_partner_id (integer) [PRECISION: 32] [COMMENT: Requesting Partner]; date_order_assets (timestamp without time zone) [COMMENT: RFQ Expiry Date]; name2 (character varying) [COMMENT: RFQ Reference]; is_assets_orders (boolean) [COMMENT: Assets Orders]; milestone_template_id (integer) [PRECISION: 32] [COMMENT: Milestone and Contract Terms]; actual_progress (character varying) [COMMENT: Actual Progress]; remaining_progress (character varying) [COMMENT: Remaining Progress (%)]; progress_paid (numeric) [COMMENT: Progress Paid (%)]; paid_swo (double precision) [PRECISION: 53] [COMMENT: SWO Paid]; partner_invoice_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Vendor Bill Address]; is_product_service_operation_receiving (boolean) [COMMENT: Product Service Operation Receiving]; is_service (boolean) [COMMENT: Service]; show_analytic_tags (boolean) [COMMENT: Show Analytic Tags]; client_order_ref (character varying) [COMMENT: Reference]; discount_amt_before (numeric) [COMMENT: - Discount]; discount_amt_line_before (numeric) [COMMENT: - Line Discount]; amount_subtotal (numeric) [COMMENT: Subtotal]; tax_discount_policy (character varying) [COMMENT: Tax Applies on]; dp (boolean) [COMMENT: Direct Purchase]; list_available_products (character varying) [COMMENT: Available Products]; from_purchase_request (boolean) [COMMENT: from purchase request]; term_condition (integer) [PRECISION: 32] [COMMENT: Terms and Conditions: ]; term_condition_box (text) [COMMENT: Terms and Conditions]; multi_discount (character varying) [COMMENT: Multi Discount]; vendor_payment_terms (character varying) [COMMENT: Vendor Payment Terms]; service_level_agreement_id (integer) [PRECISION: 32] [COMMENT: Service Level Agreement]; service_level_agreement_box (text) [COMMENT: Agreement]; down_payment_discount_amount (double precision) [PRECISION: 53] [COMMENT: Down Payment Discount Amount]; tender_scope (character varying) [COMMENT: Tender Scope]; is_submit_quotation (boolean) [COMMENT: Submit Quotation]; not_editable (boolean) [COMMENT: Not Editable]; is_editable (boolean) [COMMENT: Is Editable]; from_bo (boolean) [COMMENT: RFQ/PO from BO]; open_tender (boolean) [COMMENT: Open Tender]; journal_id (integer) [PRECISION: 32] [COMMENT: Journal]; name_dp (character varying) [COMMENT: DP]; direct_approval_matrix_id (integer) [PRECISION: 32] [COMMENT: Direct Purchase Approval Matrix]; control (boolean) [COMMENT: Control]; qty_limit (double precision) [PRECISION: 53] [COMMENT: Qty Limit]; budget_limit (double precision) [PRECISION: 53] [COMMENT: Budget Limit]; days_to_approve (double precision) [PRECISION: 53] [COMMENT: Days to Approve]; purchase_order_duration_to_confirm (double precision) [PRECISION: 53] [COMMENT: Purchase Order Duration to Confirm]; amount_saved_from_cost_savings (double precision) [PRECISION: 53] [COMMENT: Amount Saved from cost savings]; number_of_successful_cost_savings (double precision) [PRECISION: 53] [COMMENT: Number of successful cost savings]; is_valid_coupon (boolean) [COMMENT: Valid Coupon]; code_promo_program_id (integer) [PRECISION: 32] [COMMENT: Applied Promo Program]; is_dropship (boolean) [COMMENT: Is Dropship]; is_sale_order (boolean) [COMMENT: Is Sale Order]; customer_partner_id (integer) [PRECISION: 32] [COMMENT: Customer]; customer_location_partner_id (integer) [PRECISION: 32] [COMMENT: Customer Location]; is_report_purchaseorder_printed (boolean) [COMMENT: Is Report Purchase Order Copy?]; is_report_purchasequotation_printed (boolean) [COMMENT: Is Report Purchase Quotation Copy?]; import_reference (character varying) [COMMENT: Import Reference]; rfq_type (character varying) [COMMENT: Rfq Type]; discount_promotions_amount (numeric) [COMMENT: Discount Promotions]; remark (text) [COMMENT: Remark]. Total columns: 155. Statistics: 146 nullable, 1 with defaults, 0 with length constraints.


What columns does mail_shortcode have? or What is stored in mail_shortcode?

Response: The mail_shortcode table has 8 columns and 2 foreign key relationships. It stores data related to mail shortcode in the system. The table has 3 indexes for performance optimization. Column types: integer: 3, character varying: 2, text: 1, timestamp without time zone: 2. Nullable columns: 5, columns with defaults: 1.


What computed fields exist in access.rights.profile? or Describe the field structure of access.rights.profile.

Response: The access.rights.profile model has 9 fields. Field types distribution: char: 2, many2many: 1, integer: 1, many2one: 2, datetime: 3. Computed fields: 2. Field details: name (char) [module: equip3_general_features]; group_ids (many2many) -> res.groups [module: equip3_general_features]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


What one2many fields are in account.equity.move? or Show me the relational structure of account.equity.move.

Response: The account.equity.move 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. One2many fields: none.


What are the foreign keys in customer_target? or What tables are connected to customer_target?

Response: Foreign keys in customer_target: company_id -> res_company.id [constraint: customer_target_company_id_fkey]; create_uid -> res_users.id [constraint: customer_target_create_uid_fkey]; customer_categ_id -> customer_category.id [constraint: customer_target_customer_categ_id_fkey]; discount_line_product_id -> product_product.id [constraint: customer_target_discount_line_product_id_fkey]; product_id -> product_product.id [constraint: customer_target_product_id_fkey]; write_uid -> res_users.id [constraint: customer_target_write_uid_fkey]. Total foreign key relationships: 6. Referenced tables: product_product, customer_category, res_users, res_company.


Tell me about the remove_action_view_data_rel_ah table. or How many columns are in remove_action_view_data_rel_ah?

Response: The remove_action_view_data_rel_ah table has 2 columns and 2 foreign key relationships. It stores data related to remove action view data rel ah in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


What methods are available in hr.plan.wizard? or What modules define hr.plan.wizard?

Response: The hr.plan.wizard model is defined in module: hr. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: action_launch, _alias_get_error_message.


What are common use cases for account.common.partner.report? or What operations can I perform on account.common.partner.report?

Response: To use the account.common.partner.report model, you need to provide values for required fields: result_selection, journal_ids, target_move, company_id. Readonly fields: result_selection, journal_ids, date_from, date_to, target_move, report_currency_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: result_selection [required] [readonly] [has_default]; journal_ids [required] [readonly] [has_default]; date_from [readonly]; date_to [readonly]; target_move [required] [readonly] [has_default]; report_currency_id [readonly]; company_id [required] [readonly] [has_default]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


How to query allfresh.consignment.report data? or How to create records in allfresh.consignment.report?

Response: To use the allfresh.consignment.report model, you need to provide values for required fields: none. Readonly fields: date_order, barcode, product_id, qty, price, margin, total_margin, consignment_move_id, currency_id, company_id, id, display_name, __last_update. Field usage details: date_order [readonly]; barcode [readonly]; product_id [readonly]; qty [readonly]; price [readonly]; margin [readonly]; total_margin [readonly]; consignment_move_id [readonly]; currency_id [readonly]; company_id [readonly]; id [readonly]; display_name [readonly] [computed] [no_copy]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


List all columns in sparse_fields_test. or What fields are available in sparse_fields_test?

Response: Columns in sparse_fields_test: id (integer) [NOT NULL] [DEFAULT: nextval('sparse_fields_test_id_seq'::regclass)] [PRECISION: 32]; data (text) [COMMENT: Data]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 6. Statistics: 5 nullable, 1 with defaults, 0 with length constraints.


What models are connected to s.curve.budget? or What one2many fields are in s.curve.budget?

Response: The s.curve.budget model has 8 relational fields: crossovered_budget -> crossovered.budget; budgetary_position -> account.budget.post; crossovered_purchase_budget -> budget.purchase; product_purchase_budget -> product.product; crossovered_acount_budget -> monthly.account.budget; acount_account_budget -> account.account; create_uid -> res.users; write_uid -> res.users. Many2many fields: budgetary_position, product_purchase_budget, acount_account_budget. One2many fields: none.


Describe the mailing_mailing_schedule_date table structure. or How many columns are in mailing_mailing_schedule_date?

Response: The mailing_mailing_schedule_date table has 7 columns and 3 foreign key relationships. It stores data related to mailing mailing schedule date in the system. The table has 1 indexes for performance optimization. Column types: integer: 4, timestamp without time zone: 3. Nullable columns: 5, columns with defaults: 1.


What does the pos.details.wizard model represent? or Describe the pos.details.wizard model in Odoo.

Response: The pos.details.wizard model represents Point of Sale Details Report in the ERP system. It contains 10 fields and is used to manage point of sale details report data. Defined in module: point_of_sale. Key fields include: start_date, end_date, pos_config_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Which fields are required in sale.order.repair? or Show me the fields of sale.order.repair.

Response: The sale.order.repair model has 11 fields. Field types distribution: selection: 1, one2many: 1, boolean: 1, many2one: 3, integer: 1, char: 1, datetime: 3. Computed fields: 2. Field details: repair_type (selection) [module: equip3_inventory_operation]; repair_line_ids (one2many) [readonly] -> sale.order.repair.line [module: equip3_inventory_operation]; is_return_required (boolean) [module: equip3_inventory_operation]; return_sale_order_id (many2one) -> dev.rma.rma [module: equip3_inventory_operation]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


Show me the column structure of sh_tsp_top_purchasing_product. or What are the column types in sh_tsp_top_purchasing_product?

Response: Columns in sh_tsp_top_purchasing_product: id (integer) [NOT NULL] [DEFAULT: nextval('sh_tsp_top_purchasing_product_id_seq'::regclass)] [PRECISION: 32]; product_id (integer) [PRECISION: 32] [COMMENT: Product]; qty (double precision) [PRECISION: 53] [COMMENT: Qty Purchased]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 7. Statistics: 6 nullable, 1 with defaults, 0 with length constraints.


What columns does report_fonts have? or Explain the report_fonts table schema.

Response: The report_fonts table has 9 columns and 2 foreign key relationships. It stores data related to report fonts in the system. The table has 3 indexes for performance optimization. Column types: integer: 3, character varying: 4, timestamp without time zone: 2. Nullable columns: 4, columns with defaults: 1.


Which fields in opening.balance.line are computed? or What is the module hierarchy for opening.balance.line?

Response: The opening.balance.line model is defined in module: equip3_accounting_opening_balance. It has 4 computed fields: company_id, company_currency_id, display_name, __last_update. Stored computed fields: none. Related fields: company_id -> move_id.company_id, company_currency_id -> company_id.currency_id. Original module methods: .


Tell me about the service_work_order table. or Explain the service_work_order table schema.

Response: The service_work_order table has 18 columns and 8 foreign key relationships. It stores data related to service work order in the system. The table has 2 indexes for performance optimization. Column types: integer: 9, character varying: 3, timestamp without time zone: 4, double precision: 1, boolean: 1. Nullable columns: 17, columns with defaults: 1.


What methods are available in vendor.evaluation? or What are the technical details of vendor.evaluation?

Response: The vendor.evaluation model is defined in module: vendor_evaluation. It has 30 computed fields: is_manager, user_id, on_time_rate, fulfillment, on_time_rate_res, fulfillment_res, vendor_res, final_point_res, 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_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, display_name, __last_update. Stored computed fields: none. Related fields: on_time_rate -> vendor.on_time_rate, on_time_rate_res -> on_time_rate, fulfillment_res -> fulfillment, vendor_res -> vendor, final_point_res -> final_point, activity_user_id -> activity_ids.user_id, activity_type_id -> activity_ids.activity_type_id, activity_type_icon -> activity_ids.icon, activity_summary -> activity_ids.summary. Original module methods: draft_request, request_draft, request_approved, request_rejected, approved_cancelled, _get_current_user, check_manager, onchange_vendor_email, check1_price_factor, check2_delivery_factor, check3_quality_factor, check4_document_factor, check5_commitment_factor, check6_dependability_factor, check7_dependability_factor, check8_support_factor, check9_support_factor, check9a_other_factor, calculate, unlink, create, write.


How does account_loan_generate_wizard relate to other tables? or What are the foreign keys in account_loan_generate_wizard?

Response: Foreign keys in account_loan_generate_wizard: create_uid -> res_users.id [constraint: account_loan_generate_wizard_create_uid_fkey]; write_uid -> res_users.id [constraint: account_loan_generate_wizard_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


List all constraint names in budget_purchase_lines. or Describe the relational structure of budget_purchase_lines.

Response: Foreign keys in budget_purchase_lines: analytic_account_id -> account_analytic_account.id [constraint: budget_purchase_lines_analytic_account_id_fkey]; company_id -> res_company.id [constraint: budget_purchase_lines_company_id_fkey]; create_uid -> res_users.id [constraint: budget_purchase_lines_create_uid_fkey]; parent_analytic_account_id -> account_analytic_account.id [constraint: budget_purchase_lines_parent_analytic_account_id_fkey]; product_budget -> account_budget_post.id [constraint: budget_purchase_lines_product_budget_fkey]; product_id -> product_product.id [constraint: budget_purchase_lines_product_id_fkey]; purchase_budget_id -> budget_purchase.id [constraint: budget_purchase_lines_purchase_budget_id_fkey]; purchase_order_line_budget_id -> purchase_order_line.id [constraint: budget_purchase_lines_purchase_order_line_budget_id_fkey]; write_uid -> res_users.id [constraint: budget_purchase_lines_write_uid_fkey]. Total foreign key relationships: 9. Referenced tables: product_product, budget_purchase, purchase_order_line, account_budget_post, res_company, res_users, account_analytic_account.


What columns does hour_group have? or How many columns are in hour_group?

Response: The hour_group table has 10 columns and 3 foreign key relationships. It stores data related to hour group in the system. The table has 1 indexes for performance optimization. Column types: integer: 4, character varying: 1, double precision: 2, boolean: 1, timestamp without time zone: 2. Nullable columns: 9, columns with defaults: 1.


Tell me about the sale_report_salesperson_xls table. or How many columns are in sale_report_salesperson_xls?

Response: The sale_report_salesperson_xls table has 6 columns and 2 foreign key relationships. It stores data related to sale report salesperson xls in the system. The table has 1 indexes for performance optimization. Column types: integer: 3, character varying: 1, timestamp without time zone: 2. Nullable columns: 5, columns with defaults: 1.


Which columns are nullable in sh_mrp_pass_fail? or List all columns in sh_mrp_pass_fail.

Response: Columns in sh_mrp_pass_fail: id (integer) [NOT NULL] [DEFAULT: nextval('sh_mrp_pass_fail_id_seq'::regclass)] [PRECISION: 32]; product_id (integer) [PRECISION: 32] [COMMENT: Product]; sh_message (text) [COMMENT: Measurement Message]; sh_quality_point_id (integer) [PRECISION: 32] [COMMENT: Quality Control Point]; mrp_id (integer) [PRECISION: 32] [COMMENT: Manufacturing]; workorder_id (integer) [PRECISION: 32] [COMMENT: Work Order]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 10. Statistics: 9 nullable, 1 with defaults, 0 with length constraints.


How does purchase.target.based.on relate to other models? or Show me the relational structure of purchase.target.based.on.

Response: The purchase.target.based.on model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


What is stored in pos_gift_card_recharge? or What indexes exist on pos_gift_card_recharge?

Response: The pos_gift_card_recharge table has 10 columns and 5 foreign key relationships. It stores data related to pos gift card recharge in the system. The table has 1 indexes for performance optimization. Column types: integer: 6, date: 1, double precision: 1, timestamp without time zone: 2. Nullable columns: 9, columns with defaults: 1.


What is stored in bve_view_res_users_rel? or How many columns are in bve_view_res_users_rel?

Response: The bve_view_res_users_rel table has 2 columns and 2 foreign key relationships. It stores data related to bve view res users rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


What are common use cases for crm.tag? or What business logic is in crm.tag?

Response: To use the crm.tag model, you need to provide values for required fields: name. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [required]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


How is sh.custom.model.tab used in the system? or Describe the sh.custom.model.tab model in Odoo.

Response: The sh.custom.model.tab model represents Custom Model Tab in the ERP system. It contains 18 fields and is used to manage custom model tab data. Defined in module: sh_global_custom_fields. Key fields include: 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.


What are the available fields for target.activity.line.res? or What computed fields exist in target.activity.line.res?

Response: The target.activity.line.res model has 13 fields. Field types distribution: many2one: 5, integer: 3, datetime: 4, char: 1. Computed fields: 2. Field details: activity_id (many2one) -> target.activity [module: equip3_crm_operation]; user_id (many2one) -> res.users [module: equip3_crm_operation]; activity_type (many2one) -> mail.activity.type [module: equip3_crm_operation]; activity_done (integer) [module: equip3_crm_operation]; target_activity (integer) [module: equip3_crm_operation]; date (datetime) [module: equip3_crm_operation]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


Show me the fields of itr.matrix.reject. or What data can be stored in itr.matrix.reject?

Response: The itr.matrix.reject model has 8 fields. Field types distribution: text: 1, integer: 1, char: 1, many2one: 2, datetime: 3. Computed fields: 2. Field details: reason (text) [module: equip3_inventory_operation]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


How is ir.demo_failure used in the system? or What does the ir.demo_failure model represent?

Response: The ir.demo_failure model represents Demo failure in the ERP system. It contains 10 fields and is used to manage demo failure data. Defined in module: base. Key fields include: module_id, error, wizard_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


List all columns in target_activity_line. or Describe the columns of target_activity_line.

Response: Columns in target_activity_line: id (integer) [NOT NULL] [DEFAULT: nextval('target_activity_line_id_seq'::regclass)] [PRECISION: 32]; activity_id (integer) [PRECISION: 32] [COMMENT: Target Activity]; activity_type (integer) [PRECISION: 32] [COMMENT: Follow Ups Type]; activity_target (integer) [PRECISION: 32] [COMMENT: Follow Ups Target]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 8. Statistics: 7 nullable, 1 with defaults, 0 with length constraints.


What are the column types in invoice_approved_user_rel? or What fields are available in invoice_approved_user_rel?

Response: Columns in invoice_approved_user_rel: account_move_id (integer) [NOT NULL] [PRECISION: 32]; res_users_id (integer) [NOT NULL] [PRECISION: 32]. Total columns: 2. Statistics: 0 nullable, 0 with defaults, 0 with length constraints.


What fields are available in account_account_type_account_partner_ledger_rel? or What are the column types in account_account_type_account_partner_ledger_rel?

Response: Columns in account_account_type_account_partner_ledger_rel: account_partner_ledger_id (integer) [NOT NULL] [PRECISION: 32]; account_account_type_id (integer) [NOT NULL] [PRECISION: 32]. Total columns: 2. Statistics: 0 nullable, 0 with defaults, 0 with length constraints.


What fields does barcodes.barcode_events_mixin have? or What are the available fields for barcodes.barcode_events_mixin?

Response: The barcodes.barcode_events_mixin model has 4 fields. Field types distribution: char: 2, integer: 1, datetime: 1. Computed fields: 2. Field details: _barcode_scanned (char) [readonly] [module: barcodes]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field] [not stored] [module: None].


What foreign keys exist in approval.matrix.accounting? or Describe the many2many relations for approval.matrix.accounting.

Response: The approval.matrix.accounting model has 18 relational fields: company_id -> res.company; branch_id -> res.branch; filter_branch_ids -> res.branch; approval_matrix_line_ids -> approval.matrix.accounting.lines; 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: filter_branch_ids, message_partner_ids, message_channel_ids. One2many fields: approval_matrix_line_ids, activity_ids, message_follower_ids, message_ids, website_message_ids.


Tell me about the sale_order_cancel table. or Describe the sale_order_cancel table structure.

Response: The sale_order_cancel table has 6 columns and 3 foreign key relationships. It stores data related to sale order cancel in the system. The table has 1 indexes for performance optimization. Column types: integer: 4, timestamp without time zone: 2. Nullable columns: 4, columns with defaults: 1.


What tables are connected to approved_users_sale_patner_rel? or What tables does approved_users_sale_patner_rel reference?

Response: Foreign keys in approved_users_sale_patner_rel: order_id -> approval_matrix_sale_order_lines.id [constraint: approved_users_sale_patner_rel_order_id_fkey]; user_id -> res_users.id [constraint: approved_users_sale_patner_rel_user_id_fkey]. Total foreign key relationships: 2. Referenced tables: res_users, approval_matrix_sale_order_lines.


What foreign keys exist in mrp.consumption.warning.line? or What are the relationships in mrp.consumption.warning.line?

Response: The mrp.consumption.warning.line model has 6 relational fields: mrp_consumption_warning_id -> mrp.consumption.warning; mrp_production_id -> mrp.production; product_id -> product.product; product_uom_id -> uom.uom; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


What indexes exist on pos_config_advertisement_rel? or What is the pos_config_advertisement_rel table?

Response: The pos_config_advertisement_rel table has 2 columns and 2 foreign key relationships. It stores data related to pos config advertisement rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


How is invoice.recurring.line used in the system? or Tell me about the invoice.recurring.line model.

Response: The invoice.recurring.line model represents Invoice Recurring Line in the ERP system. It contains 22 fields and is used to manage invoice recurring line data. Defined in module: sh_invoice_recurring. Key fields include: invoice_recurring_id, product_id, account_id, tax_ids, product_uom_category_id, product_uom_id, name, price_unit, discount, quantity, company_id, journal_id, analytic_group_ids, subtotal, price_tax, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What field types are used in account.multipayment.credit? or Show me the fields of account.multipayment.credit.

Response: The account.multipayment.credit model has 22 fields. Field types distribution: many2one: 7, date: 2, monetary: 5, boolean: 1, many2many: 1, float: 1, integer: 1, char: 1, datetime: 3. Computed fields: 4. Field details: line_id (many2one) [readonly] -> account.multipayment [module: equip3_accounting_operation]; currency_id (many2one) -> res.currency [module: equip3_accounting_operation]; invoice_id (many2one) [readonly] -> account.move [module: equip3_accounting_operation]; account_id (many2one) [readonly] -> account.account [module: equip3_accounting_operation]; invoice_date (date) [readonly] [module: equip3_accounting_operation]; invoice_date_due (date) [readonly] [module: equip3_accounting_operation]; original_amount (monetary) [readonly] [module: equip3_accounting_operation]; base_amount (monetary) [readonly] [module: equip3_accounting_operation]; original_unreconcile (monetary) [readonly] [module: equip3_accounting_operation]; base_unreconcile (monetary) [readonly] [module: equip3_accounting_operation]; is_full_reconcile (boolean) [module: equip3_accounting_operation]; amount (monetary) [module: equip3_accounting_operation]; payment_id (many2one) -> account.payment [module: equip3_accounting_operation]; account_reverse_ids (many2many) [readonly] -> account.move [compute: _compute_account_reverse_ids] [not stored] [module: allfresh_mod_account_move]; account_reverse_total (float) [readonly] [compute: _compute_account_reverse_ids] [not stored] [module: allfresh_mod_account_move]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


What indexes exist on account_fiscal_position_template? or Tell me about the account_fiscal_position_template table.

Response: The account_fiscal_position_template table has 15 columns and 5 foreign key relationships. It stores data related to account fiscal position template in the system. The table has 1 indexes for performance optimization. Column types: integer: 7, character varying: 3, text: 1, boolean: 2, timestamp without time zone: 2. Nullable columns: 12, columns with defaults: 1.


What columns does sh_sale_report_salesperson_wizard have? or What indexes exist on sh_sale_report_salesperson_wizard?

Response: The sh_sale_report_salesperson_wizard table has 10 columns and 3 foreign key relationships. It stores data related to sh sale report salesperson wizard in the system. The table has 1 indexes for performance optimization. Column types: integer: 5, timestamp without time zone: 4, character varying: 1. Nullable columns: 7, columns with defaults: 1.


What fields are available in product_variant_combination? or Which columns are nullable in product_variant_combination?

Response: Columns in product_variant_combination: product_product_id (integer) [NOT NULL] [PRECISION: 32]; product_template_attribute_value_id (integer) [NOT NULL] [PRECISION: 32]. Total columns: 2. Statistics: 0 nullable, 0 with defaults, 0 with length constraints.


How to query mail.shortcode data? or How to create records in mail.shortcode?

Response: To use the mail.shortcode model, you need to provide values for required fields: source, substitution. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: source [required]; substitution [required]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


What data can be stored in kpi.period? or List all fields in the kpi.period model.

Response: The kpi.period model has 20 fields. Field types distribution: char: 2, date: 2, one2many: 1, float: 2, many2one: 5, selection: 1, datetime: 4, html: 1, boolean: 1, integer: 1. Computed fields: 6. Field details: name (char) [required] [module: kpi_scorecard]; date_start (date) [required] [module: kpi_scorecard]; date_end (date) [required] [module: kpi_scorecard]; line_ids (one2many) -> kpi.scorecard.line [module: kpi_scorecard]; period_length (float) [readonly] [compute: <function kpi_period._compute_period_length at 0x2f197e280>] [stored] [module: kpi_scorecard]; period_passed (float) [readonly] [compute: <function kpi_period._compute_period_passed at 0x2f197e310>] [not stored] [module: kpi_scorecard]; parent_id (many2one) [readonly] -> kpi.period [compute: <function kpi_period._compute_parent_id at 0x2f197e1f0>] [not stored] [module: kpi_scorecard]; state (selection) [module: kpi_scorecard]; template_id (many2one) -> kpi.period [module: kpi_scorecard] [inverse: <function kpi_period._inverse_template_id at 0x2f197e3a0>]; company_id (many2one) [required] -> res.company [module: kpi_scorecard]; last_recalculation_date (datetime) [module: kpi_scorecard]; help_notes (html) [readonly] [compute: <function kpi_help._compute_show_kpi_help at 0x2f195ae50>] [not stored] [module: kpi_scorecard]; kpi_help_dummy (boolean) [module: kpi_scorecard]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


What tables are connected to ir_config_parameter? or What tables does ir_config_parameter reference?

Response: Foreign keys in ir_config_parameter: create_uid -> res_users.id [constraint: ir_config_parameter_create_uid_fkey]; write_uid -> res_users.id [constraint: ir_config_parameter_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


What relationships exist for import_pricelist_wizard? or How does import_pricelist_wizard relate to other tables?

Response: Foreign keys in import_pricelist_wizard: create_uid -> res_users.id [constraint: import_pricelist_wizard_create_uid_fkey]; write_uid -> res_users.id [constraint: import_pricelist_wizard_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


Which fields are required in account.analytic.default? or Describe the field structure of account.analytic.default.

Response: The account.analytic.default model has 43 fields. Field types distribution: integer: 6, many2one: 12, many2many: 3, date: 4, one2many: 4, selection: 2, char: 4, boolean: 5, datetime: 3. Computed fields: 22. Field details: sequence (integer) [module: account]; analytic_id (many2one) -> account.analytic.account [module: account]; analytic_tag_ids (many2many) -> account.analytic.tag [module: account]; product_id (many2one) -> product.product [module: equip3_accounting_analytical]; user_id (many2one) -> res.users [module: equip3_accounting_analytical]; company_id (many2one) -> res.company [module: equip3_accounting_analytical]; date_start (date) [module: equip3_accounting_analytical]; partner_id (many2one) -> res.partner [module: equip3_accounting_analytical]; account_id (many2one) -> account.account [module: equip3_accounting_analytical]; date_stop (date) [module: equip3_accounting_analytical]; branch_id (many2one) -> res.branch [module: equip3_accounting_masterdata]; activity_ids (one2many) -> mail.activity [module: mail]; activity_state (selection) [readonly] [compute: _compute_activity_state] [not stored] [module: mail]; activity_user_id (many2one) -> res.users [compute: <bound method Field._compute_related of account.analytic.default.activity_user_id>] [not stored] [module: mail] [related: activity_ids.user_id] [inverse: <bound method Field._inverse_related of account.analytic.default.activity_user_id>]; activity_type_id (many2one) -> mail.activity.type [compute: <bound method Field._compute_related of account.analytic.default.activity_type_id>] [not stored] [module: mail] [related: activity_ids.activity_type_id] [inverse: <bound method Field._inverse_related of account.analytic.default.activity_type_id>]; activity_type_icon (char) [readonly] [compute: <bound method Field._compute_related of account.analytic.default.activity_type_icon>] [not stored] [module: mail] [related: activity_ids.icon]; activity_date_deadline (date) [readonly] [compute: _compute_activity_date_deadline] [not stored] [module: mail]; my_activity_date_deadline (date) [readonly] [compute: _compute_my_activity_date_deadline] [not stored] [module: mail]; activity_summary (char) [compute: <bound method Field._compute_related of account.analytic.default.activity_summary>] [not stored] [module: mail] [related: activity_ids.summary] [inverse: <bound method Field._inverse_related of account.analytic.default.activity_summary>]; activity_exception_decoration (selection) [readonly] [compute: _compute_activity_exception_type] [not stored] [module: mail]; activity_exception_icon (char) [readonly] [compute: _compute_activity_exception_type] [not stored] [module: mail]; message_is_follower (boolean) [readonly] [compute: _compute_is_follower] [not stored] [module: mail]; message_follower_ids (one2many) -> mail.followers [module: mail]; message_partner_ids (many2many) [readonly] -> res.partner [compute: _get_followers] [not stored] [module: mail]; message_channel_ids (many2many) [readonly] -> mail.channel [compute: _get_followers] [not stored] [module: mail]; message_ids (one2many) -> mail.message [module: mail]; message_unread (boolean) [readonly] [compute: _get_message_unread] [not stored] [module: mail]; message_unread_counter (integer) [readonly] [compute: _get_message_unread] [not stored] [module: mail]; message_needaction (boolean) [readonly] [compute: _get_message_needaction] [not stored] [module: mail]; message_needaction_counter (integer) [readonly] [compute: _get_message_needaction] [not stored] [module: mail]; message_has_error (boolean) [readonly] [compute: _compute_message_has_error] [not stored] [module: mail]; message_has_error_counter (integer) [readonly] [compute: _compute_message_has_error] [not stored] [module: mail]; message_attachment_count (integer) [readonly] [compute: _compute_message_attachment_count] [not stored] [module: mail]; message_main_attachment_id (many2one) -> ir.attachment [module: mail]; website_message_ids (one2many) -> mail.message [module: portal]; message_has_sms_error (boolean) [readonly] [compute: _compute_message_has_sms_error] [not stored] [module: sms]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


List all fields in the stock.package.destination model. or What computed fields exist in stock.package.destination?

Response: The stock.package.destination model has 11 fields. Field types distribution: many2one: 4, many2many: 1, one2many: 1, integer: 1, char: 1, datetime: 3. Computed fields: 4. Field details: picking_id (many2one) [required] -> stock.picking [module: stock]; move_line_ids (many2many) [required] [readonly] -> stock.move.line [compute: _compute_move_line_ids] [not stored] [module: stock]; location_dest_id (many2one) [required] -> stock.location [module: stock]; filtered_location (one2many) [readonly] -> stock.location [compute: _filter_location] [not stored] [module: stock]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


Describe the product_ratio_line table structure. or What is stored in product_ratio_line?

Response: The product_ratio_line table has 10 columns and 5 foreign key relationships. It stores data related to product ratio line in the system. The table has 1 indexes for performance optimization. Column types: integer: 6, boolean: 1, numeric: 1, timestamp without time zone: 2. Nullable columns: 6, columns with defaults: 1.


What is stored in ir_model_data? or What indexes exist on ir_model_data?

Response: The ir_model_data table has 10 columns and 2 foreign key relationships. It stores data related to ir model data in the system. The table has 5 indexes for performance optimization. Column types: integer: 4, timestamp without time zone: 2, boolean: 1, character varying: 3. Nullable columns: 6, columns with defaults: 4.


What relationships exist for product_product_setu_inventory_age_breakdown_report_rel? or List all constraint names in product_product_setu_inventory_age_breakdown_report_rel.

Response: Foreign keys in product_product_setu_inventory_age_breakdown_report_rel: setu_inventory_age_breakdown_report_id -> setu_inventory_age_breakdown_report.id [constraint: product_product_setu_inventor_setu_inventory_age_breakdown_fkey]; product_product_id -> product_product.id [constraint: product_product_setu_inventory_age_brea_product_product_id_fkey]. Total foreign key relationships: 2. Referenced tables: setu_inventory_age_breakdown_report, product_product.


Describe the relational structure of res_company_setu_inventory_fsn_xyz_analysis_report_rel. or What tables are connected to res_company_setu_inventory_fsn_xyz_analysis_report_rel?

Response: Foreign keys in res_company_setu_inventory_fsn_xyz_analysis_report_rel: setu_inventory_fsn_xyz_analysis_report_id -> setu_inventory_fsn_xyz_analysis_report.id [constraint: res_company_setu_inventory_fs_setu_inventory_fsn_xyz_analy_fkey]; res_company_id -> res_company.id [constraint: res_company_setu_inventory_fsn_xyz_analysis_res_company_id_fkey]. Total foreign key relationships: 2. Referenced tables: setu_inventory_fsn_xyz_analysis_report, res_company.


Which columns are nullable in account_tax_template? or List all columns in account_tax_template.

Response: Columns in account_tax_template: id (integer) [NOT NULL] [DEFAULT: nextval('account_tax_template_id_seq'::regclass)] [PRECISION: 32]; chart_template_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Chart Template]; name (character varying) [NOT NULL] [COMMENT: Tax Name]; type_tax_use (character varying) [NOT NULL] [COMMENT: Tax Type]; tax_scope (character varying) [COMMENT: Tax Scope]; amount_type (character varying) [NOT NULL] [COMMENT: Tax Computation]; active (boolean) [COMMENT: Active]; sequence (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Sequence]; amount (numeric) [NOT NULL] [COMMENT: Amount]; description (character varying) [COMMENT: Display on Invoices]; price_include (boolean) [COMMENT: Included in Price]; include_base_amount (boolean) [COMMENT: Affect Subsequent Taxes]; analytic (boolean) [COMMENT: Analytic Cost]; tax_group_id (integer) [PRECISION: 32] [COMMENT: Tax Group]; tax_exigibility (character varying) [COMMENT: Tax Due]; cash_basis_transition_account_id (integer) [PRECISION: 32] [COMMENT: Cash Basis Transition Account]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 20. Statistics: 13 nullable, 1 with defaults, 0 with length constraints.


Can you explain the purpose of budget.carry.over.lines? or What is the budget.carry.over.lines model?

Response: The budget.carry.over.lines model represents Budget Carry Over Lines in the ERP system. It contains 27 fields and is used to manage budget carry over lines data. Defined in module: equip3_accounting_budget. Key fields include: budget_carry_over_id, date_from, date_to, analytic_account_id, paid_date, parent_analytic_account_id, general_budget_id, reserve_amount, currency_id, account_tag_ids, filtered_budget_line, company_id, practical_amount, theoritical_amount, planned_amount, practical_budget_amount, percentage, is_above_budget, carry_over_amount, final_planned_amount, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What field types are used in account.debit.note? or List all fields in the account.debit.note model.

Response: The account.debit.note model has 14 fields. Field types distribution: many2many: 1, date: 1, char: 4, many2one: 3, boolean: 1, integer: 1, datetime: 3. Computed fields: 4. Field details: move_ids (many2many) -> account.move [module: account_debit_note]; date (date) [required] [module: account_debit_note]; reason (char) [module: account_debit_note]; journal_id (many2one) -> account.journal [module: account_debit_note]; copy_lines (boolean) [module: account_debit_note]; move_type (char) [readonly] [compute: _compute_from_moves] [not stored] [module: account_debit_note]; journal_type (char) [readonly] [compute: _compute_from_moves] [not stored] [module: account_debit_note]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


What business logic is in sh.top.selling.products? or How do I use the sh.top.selling.products model?

Response: To use the sh.top.selling.products 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. Field usage details: id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


Explain the digest_tip_res_users_rel table schema. or What is stored in digest_tip_res_users_rel?

Response: The digest_tip_res_users_rel table has 2 columns and 2 foreign key relationships. It stores data related to digest tip res users rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


Describe the rma.report model in Odoo. or How is rma.report used in the system?

Response: The rma.report model represents RMA Statistics in the ERP system. It contains 22 fields and is used to manage rma statistics data. Defined in module: dev_rma. Key fields include: name, sale_id, picking_id, date, deadline_date, user_id, team_id, partner_id, company_id, state, product_id, product_tmpl_id, categ_id, delivered_qty, return_qty, replace_product_id, replace_qty, country_id, commercial_partner_id, id, display_name, __last_update.


What computed fields exist in crossovered.budget.lines? or Show me the fields of crossovered.budget.lines.

Response: The crossovered.budget.lines model has 32 fields. Field types distribution: char: 2, many2one: 9, date: 3, monetary: 8, boolean: 1, selection: 1, many2many: 2, float: 2, integer: 1, datetime: 3. Computed fields: 18. Field details: name (char) [readonly] [compute: _compute_line_name] [not stored] [module: om_account_budget]; crossovered_budget_id (many2one) [required] -> crossovered.budget [module: om_account_budget]; analytic_account_id (many2one) -> account.analytic.account [module: om_account_budget]; analytic_group_id (many2one) [readonly] -> account.analytic.group [compute: <bound method Field._compute_related of crossovered.budget.lines.analytic_group_id>] [not stored] [module: om_account_budget] [related: analytic_account_id.group_id]; date_from (date) [required] [module: om_account_budget]; date_to (date) [required] [module: om_account_budget]; paid_date (date) [module: om_account_budget]; currency_id (many2one) [readonly] -> res.currency [compute: <bound method Field._compute_related of crossovered.budget.lines.currency_id>] [not stored] [module: om_account_budget] [related: company_id.currency_id]; planned_amount (monetary) [required] [module: om_account_budget]; company_id (many2one) [readonly] -> res.company [compute: <bound method Field._compute_related of crossovered.budget.lines.company_id>] [stored] [module: om_account_budget] [related: crossovered_budget_id.company_id]; is_above_budget (boolean) [readonly] [compute: _is_above_budget] [not stored] [module: om_account_budget]; crossovered_budget_state (selection) [readonly] [compute: <bound method Field._compute_related of crossovered.budget.lines.crossovered_budget_state>] [stored] [module: om_account_budget] [related: crossovered_budget_id.state]; parent_analytic_account_id (many2one) -> account.analytic.account [module: equip3_accounting_budget]; general_budget_id (many2one) -> account.budget.post [module: equip3_accounting_budget]; reserve_amount (monetary) [readonly] [compute: _get_reserve_amount] [not stored] [module: equip3_accounting_budget]; account_tag_ids (many2many) [readonly] -> account.analytic.tag [compute: <bound method Field._compute_related of crossovered.budget.lines.account_tag_ids>] [not stored] [module: equip3_accounting_budget] [related: crossovered_budget_id.account_tag_ids]; filtered_budget_line (many2many) [readonly] -> account.budget.post [compute: _get_budget_line] [not stored] [module: equip3_accounting_budget]; practical_budget_amount (monetary) [readonly] [compute: _compute_budget_practical_amount] [not stored] [module: equip3_accounting_budget]; practical_temp_budget (monetary) [module: equip3_accounting_budget]; remaining_amount (monetary) [readonly] [compute: _compute_remaining_amount] [stored] [module: equip3_accounting_budget]; theoritical_amount_2 (monetary) [readonly] [compute: _compute_theoretical_amount_2] [not stored] [module: equip3_accounting_budget]; percentage_2 (float) [readonly] [compute: _compute_percentage_2] [not stored] [module: equip3_accounting_budget]; theoritical_amount (monetary) [readonly] [compute: _compute_theoritical_amount] [stored] [module: equip3_accounting_reports]; practical_amount (monetary) [readonly] [compute: _compute_practical_amount] [stored] [module: equip3_accounting_reports]; percentage (float) [readonly] [compute: _compute_percentage] [stored] [module: equip3_accounting_reports]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


What field types are used in cust.credit.limit.data? or What data can be stored in cust.credit.limit.data?

Response: The cust.credit.limit.data model has 11 fields. Field types distribution: many2one: 5, one2many: 1, integer: 1, char: 1, datetime: 3. Computed fields: 2. Field details: company_id (many2one) -> res.company [module: equip3_sale_other_operation]; branch_id (many2one) -> res.branch [module: equip3_sale_other_operation]; partner_id (many2one) -> res.partner [module: equip3_sale_other_operation]; cust_credit_line (one2many) -> cust.credit.limit.data.line [module: equip3_sale_other_operation]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


What one2many fields are in sh.top.vendor.excel.extended? or Describe the many2many relations for sh.top.vendor.excel.extended.

Response: The sh.top.vendor.excel.extended model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


What operations can I perform on mrp.workcenter.group? or What fields are readonly in mrp.workcenter.group?

Response: To use the mrp.workcenter.group model, you need to provide values for required fields: code, name, company_id. Readonly fields: is_branch_required, 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. Field usage details: code [required]; name [required]; company_id [required] [has_default]; is_branch_required [readonly] [computed] [no_copy]; message_is_follower [readonly] [computed] [no_copy]; message_partner_ids [readonly] [computed] [no_copy]; message_channel_ids [readonly] [computed] [no_copy]; message_unread [readonly] [computed] [no_copy]; message_unread_counter [readonly] [computed] [no_copy]; message_needaction [readonly] [computed] [no_copy]; message_needaction_counter [readonly] [computed] [no_copy]; message_has_error [readonly] [computed] [no_copy]; message_has_error_counter [readonly] [computed] [no_copy]; message_attachment_count [readonly] [computed] [no_copy]; message_has_sms_error [readonly] [computed] [no_copy]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


Which fields in sale.order.repair are computed? or Describe the implementation of sale.order.repair.

Response: The sale.order.repair model is defined in module: equip3_inventory_operation. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: action_confirm.


What models are connected to account.cashbox.line? or What are the relationships in account.cashbox.line?

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


Which columns are nullable in product_template_create_variant? or Show me the column structure of product_template_create_variant.

Response: Columns in product_template_create_variant: id (integer) [NOT NULL] [DEFAULT: nextval('product_template_create_variant_id_seq'::regclass)] [PRECISION: 32]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 5. Statistics: 4 nullable, 1 with defaults, 0 with length constraints.


Show me the foreign key constraints of report_paperformat. or What relationships exist for report_paperformat?

Response: Foreign keys in report_paperformat: create_uid -> res_users.id [constraint: report_paperformat_create_uid_fkey]; write_uid -> res_users.id [constraint: report_paperformat_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


List all constraint names in product_product_setu_inventory_fsn_xyz_analysis_report_rel. or What tables are connected to product_product_setu_inventory_fsn_xyz_analysis_report_rel?

Response: Foreign keys in product_product_setu_inventory_fsn_xyz_analysis_report_rel: setu_inventory_fsn_xyz_analysis_report_id -> setu_inventory_fsn_xyz_analysis_report.id [constraint: product_product_setu_inventor_setu_inventory_fsn_xyz_analy_fkey]; product_product_id -> product_product.id [constraint: product_product_setu_inventory_fsn_xyz__product_product_id_fkey]. Total foreign key relationships: 2. Referenced tables: product_product, setu_inventory_fsn_xyz_analysis_report.


Tell me about the pos.promotion.discount.order model. or What is the pos.promotion.discount.order model?

Response: The pos.promotion.discount.order model represents Promotion each total order in the ERP system. It contains 15 fields and is used to manage promotion each total order data. Defined in module: equip3_pos_masterdata. Key fields include: active, minimum_amount, discount, discount2, multi_discount, max_discount_amount, discount_fixed_amount, promotion_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What tables are connected to invoice_printout_editor_header_rel? or How does invoice_printout_editor_header_rel relate to other tables?

Response: Foreign keys in invoice_printout_editor_header_rel: invoice_printout_editor_id -> invoice_printout_editor.id [constraint: invoice_printout_editor_header__invoice_printout_editor_id_fkey]; ir_model_fields_id -> ir_model_fields.id [constraint: invoice_printout_editor_header_rel_ir_model_fields_id_fkey]. Total foreign key relationships: 2. Referenced tables: invoice_printout_editor, ir_model_fields.


What are the available fields for account.pettycash.analysis? or Describe the field structure of account.pettycash.analysis.

Response: The account.pettycash.analysis model has 22 fields. Field types distribution: many2many: 3, selection: 5, date: 2, char: 2, integer: 2, boolean: 1, many2one: 4, datetime: 3. Computed fields: 2. Field details: journal_ids (many2many) [required] -> account.journal [module: equip3_accounting_reports]; account_ids (many2many) -> account.account [module: equip3_accounting_reports]; display_account (selection) [module: equip3_accounting_reports]; branch_ids (many2many) -> res.branch [module: equip3_accounting_reports]; top_expenses (selection) [module: equip3_accounting_reports]; date_from (date) [module: equip3_accounting_reports]; date_to (date) [module: equip3_accounting_reports]; titles (char) [module: equip3_accounting_reports]; entities_comparison (selection) [module: equip3_accounting_reports]; period (integer) [module: equip3_accounting_reports]; years_prev (boolean) [module: equip3_accounting_reports]; filter_period (selection) [module: equip3_accounting_reports]; target_move (selection) [required] [module: account]; report_currency_id (many2one) -> res.currency [module: equip3_accounting_reports]; company_id (many2one) [required] -> res.company [module: equip3_accounting_reports]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


Describe the field structure of assets.approval.matrix. or Show me the fields of assets.approval.matrix.

Response: The assets.approval.matrix model has 43 fields. Field types distribution: char: 7, many2one: 10, one2many: 5, boolean: 6, selection: 2, date: 2, many2many: 2, integer: 5, text: 1, datetime: 3. Computed fields: 25. Field details: name (char) [required] [module: equip3_accounting_masterdata]; company_id (many2one) [required] [readonly] -> res.company [module: equip3_accounting_masterdata]; branch_id (many2one) [required] -> res.branch [module: equip3_accounting_masterdata]; assets_approval_matrix_line_ids (one2many) -> assets.approval.matrix.line [module: equip3_accounting_masterdata]; is_assets_approval (boolean) [readonly] [compute: _compute_is_assets_approval] [not stored] [module: equip3_accounting_masterdata]; campaign_id (many2one) -> utm.campaign [module: utm]; source_id (many2one) -> utm.source [module: utm]; medium_id (many2one) -> utm.medium [module: utm]; activity_ids (one2many) -> mail.activity [module: mail]; activity_state (selection) [readonly] [compute: _compute_activity_state] [not stored] [module: mail]; activity_user_id (many2one) -> res.users [compute: <bound method Field._compute_related of assets.approval.matrix.activity_user_id>] [not stored] [module: mail] [related: activity_ids.user_id] [inverse: <bound method Field._inverse_related of assets.approval.matrix.activity_user_id>]; activity_type_id (many2one) -> mail.activity.type [compute: <bound method Field._compute_related of assets.approval.matrix.activity_type_id>] [not stored] [module: mail] [related: activity_ids.activity_type_id] [inverse: <bound method Field._inverse_related of assets.approval.matrix.activity_type_id>]; activity_type_icon (char) [readonly] [compute: <bound method Field._compute_related of assets.approval.matrix.activity_type_icon>] [not stored] [module: mail] [related: activity_ids.icon]; activity_date_deadline (date) [readonly] [compute: _compute_activity_date_deadline] [not stored] [module: mail]; my_activity_date_deadline (date) [readonly] [compute: _compute_my_activity_date_deadline] [not stored] [module: mail]; activity_summary (char) [compute: <bound method Field._compute_related of assets.approval.matrix.activity_summary>] [not stored] [module: mail] [related: activity_ids.summary] [inverse: <bound method Field._inverse_related of assets.approval.matrix.activity_summary>]; activity_exception_decoration (selection) [readonly] [compute: _compute_activity_exception_type] [not stored] [module: mail]; activity_exception_icon (char) [readonly] [compute: _compute_activity_exception_type] [not stored] [module: mail]; message_is_follower (boolean) [readonly] [compute: _compute_is_follower] [not stored] [module: mail]; message_follower_ids (one2many) -> mail.followers [module: mail]; message_partner_ids (many2many) [readonly] -> res.partner [compute: _get_followers] [not stored] [module: mail]; message_channel_ids (many2many) [readonly] -> mail.channel [compute: _get_followers] [not stored] [module: mail]; message_ids (one2many) -> mail.message [module: mail]; message_unread (boolean) [readonly] [compute: _get_message_unread] [not stored] [module: mail]; message_unread_counter (integer) [readonly] [compute: _get_message_unread] [not stored] [module: mail]; message_needaction (boolean) [readonly] [compute: _get_message_needaction] [not stored] [module: mail]; message_needaction_counter (integer) [readonly] [compute: _get_message_needaction] [not stored] [module: mail]; message_has_error (boolean) [readonly] [compute: _compute_message_has_error] [not stored] [module: mail]; message_has_error_counter (integer) [readonly] [compute: _compute_message_has_error] [not stored] [module: mail]; message_attachment_count (integer) [readonly] [compute: _compute_message_attachment_count] [not stored] [module: mail]; message_main_attachment_id (many2one) -> ir.attachment [module: mail]; website_message_ids (one2many) -> mail.message [module: portal]; message_has_sms_error (boolean) [readonly] [compute: _compute_message_has_sms_error] [not stored] [module: sms]; access_url (char) [readonly] [compute: _compute_access_url] [not stored] [module: portal]; access_token (char) [module: portal]; access_warning (text) [readonly] [compute: _compute_access_warning] [not stored] [module: portal]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


Explain the res_company_sale_margin_report_wizard_rel table schema. or Describe the res_company_sale_margin_report_wizard_rel table structure.

Response: The res_company_sale_margin_report_wizard_rel table has 2 columns and 2 foreign key relationships. It stores data related to res company sale margin report wizard rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


What fields are available in credit_approval_credit_rel? or What are the column types in credit_approval_credit_rel?

Response: Columns in credit_approval_credit_rel: credit_limit_approval_id (integer) [NOT NULL] [PRECISION: 32]; res_users_id (integer) [NOT NULL] [PRECISION: 32]. Total columns: 2. Statistics: 0 nullable, 0 with defaults, 0 with length constraints.


Can you explain the purpose of report.equip3_inventory_masterdata.report_product_tmpl_forecast? or How is report.equip3_inventory_masterdata.report_product_tmpl_forecast used in the system?

Response: The report.equip3_inventory_masterdata.report_product_tmpl_forecast model represents Equip Stock Replenishment Report in the ERP system. It contains 3 fields and is used to manage equip stock replenishment report data. Defined in module: equip3_inventory_masterdata. Key fields include: id, display_name, __last_update.


What are the length constraints in pos_promotion_pos_loyalty_category_rel? or Show me the column structure of pos_promotion_pos_loyalty_category_rel.

Response: Columns in pos_promotion_pos_loyalty_category_rel: promotion_id (integer) [NOT NULL] [PRECISION: 32]; loyalty_category_id (integer) [NOT NULL] [PRECISION: 32]. Total columns: 2. Statistics: 0 nullable, 0 with defaults, 0 with length constraints.


Show me the foreign key constraints of generate_closing_entries_confirmation_wizard. or What are the foreign keys in generate_closing_entries_confirmation_wizard?

Response: Foreign keys in generate_closing_entries_confirmation_wizard: retained_earnings_account_id -> account_account.id [constraint: generate_closing_entries_conf_retained_earnings_account_id_fkey]; summary_account_id -> account_account.id [constraint: generate_closing_entries_confirmation_w_summary_account_id_fkey]; fiscal_year_id -> sh_fiscal_year.id [constraint: generate_closing_entries_confirmation_wizar_fiscal_year_id_fkey]; create_uid -> res_users.id [constraint: generate_closing_entries_confirmation_wizard_create_uid_fkey]; journal_id -> account_journal.id [constraint: generate_closing_entries_confirmation_wizard_journal_id_fkey]; write_uid -> res_users.id [constraint: generate_closing_entries_confirmation_wizard_write_uid_fkey]. Total foreign key relationships: 6. Referenced tables: account_account, sh_fiscal_year, res_users, account_journal.


What tables does purchase_agreement_res_partner_rel reference? or How does purchase_agreement_res_partner_rel relate to other tables?

Response: Foreign keys in purchase_agreement_res_partner_rel: purchase_agreement_id -> purchase_agreement.id [constraint: purchase_agreement_res_partner_rel_purchase_agreement_id_fkey]; res_partner_id -> res_partner.id [constraint: purchase_agreement_res_partner_rel_res_partner_id_fkey]. Total foreign key relationships: 2. Referenced tables: res_partner, purchase_agreement.


What columns have default values in wizard_report_menu_create? or What fields are available in wizard_report_menu_create?

Response: Columns in wizard_report_menu_create: id (integer) [NOT NULL] [DEFAULT: nextval('wizard_report_menu_create_id_seq'::regclass)] [PRECISION: 32]; menu_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Parent Menu]; name (character varying) [NOT NULL] [COMMENT: Menu Name]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 7. Statistics: 4 nullable, 1 with defaults, 0 with length constraints.


What is the sh_mrp_pass_fail table? or How many columns are in sh_mrp_pass_fail?

Response: The sh_mrp_pass_fail table has 10 columns and 6 foreign key relationships. It stores data related to sh mrp pass fail in the system. The table has 1 indexes for performance optimization. Column types: integer: 7, text: 1, timestamp without time zone: 2. Nullable columns: 9, columns with defaults: 1.


What are common use cases for vendor.evaluation.rating? or How to work with vendor.evaluation.rating fields?

Response: To use the vendor.evaluation.rating model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. Field usage details: id [readonly]; display_name [readonly] [computed] [no_copy]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


What does the payment.voucher.line model represent? or How is payment.voucher.line used in the system?

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. Defined in module: equip3_accounting_operation. 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.


Describe the mail_channel_moderator_rel table structure. or What indexes exist on mail_channel_moderator_rel?

Response: The mail_channel_moderator_rel table has 2 columns and 2 foreign key relationships. It stores data related to mail channel moderator rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


List all columns in opening_balance_line. or Show me the column structure of opening_balance_line.

Response: Columns in opening_balance_line: id (integer) [NOT NULL] [DEFAULT: nextval('opening_balance_line_id_seq'::regclass)] [PRECISION: 32]; move_id (integer) [PRECISION: 32] [COMMENT: Journal Entry]; account_id (integer) [PRECISION: 32] [COMMENT: Account]; partner_id (integer) [PRECISION: 32] [COMMENT: Partner]; debit (numeric) [COMMENT: Debit]; credit (numeric) [COMMENT: Credit]; date_id (date) [COMMENT: Due Date]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 11. Statistics: 10 nullable, 1 with defaults, 0 with length constraints.


What fields are readonly in account.tax.group? or How to work with account.tax.group fields?

Response: To use the account.tax.group model, you need to provide values for required fields: name. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [required]; property_tax_payable_account_id [computed] [has_default] [no_copy]; property_tax_receivable_account_id [computed] [has_default] [no_copy]; property_advance_tax_payment_account_id [computed] [has_default] [no_copy]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


Tell me about the product.template.attribute.line model. or What is the product.template.attribute.line model?

Response: The product.template.attribute.line model represents Product Template Attribute Line in the ERP system. It contains 12 fields and is used to manage product template attribute line data. Defined in module: product. Key fields include: active, product_tmpl_id, attribute_id, value_ids, product_template_value_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What relationships exist for res_company_sh_tsp_top_purchasing_product_wizard_rel? or How does res_company_sh_tsp_top_purchasing_product_wizard_rel relate to other tables?

Response: Foreign keys in res_company_sh_tsp_top_purchasing_product_wizard_rel: sh_tsp_top_purchasing_product_wizard_id -> sh_tsp_top_purchasing_product_wizard.id [constraint: res_company_sh_tsp_top_purcha_sh_tsp_top_purchasing_produc_fkey]; res_company_id -> res_company.id [constraint: res_company_sh_tsp_top_purchasing_product_w_res_company_id_fkey]. Total foreign key relationships: 2. Referenced tables: sh_tsp_top_purchasing_product_wizard, res_company.


Describe the asset.cip.line model in Odoo. or What is the asset.cip.line model?

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. Defined in module: equip3_accounting_asset. 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.


How does gamification_badge_rule_badge_rel relate to other tables? or What relationships exist for gamification_badge_rule_badge_rel?

Response: Foreign keys in gamification_badge_rule_badge_rel: badge1_id -> gamification_badge.id [constraint: gamification_badge_rule_badge_rel_badge1_id_fkey]; badge2_id -> gamification_badge.id [constraint: gamification_badge_rule_badge_rel_badge2_id_fkey]. Total foreign key relationships: 2. Referenced tables: gamification_badge.


What relationships exist for payment_sale_details_report? or What tables does payment_sale_details_report reference?

Response: Foreign keys in payment_sale_details_report: create_uid -> res_users.id [constraint: payment_sale_details_report_create_uid_fkey]; details_id -> sh_sale_details_report_wizard.id [constraint: payment_sale_details_report_details_id_fkey]; write_uid -> res_users.id [constraint: payment_sale_details_report_write_uid_fkey]. Total foreign key relationships: 3. Referenced tables: sh_sale_details_report_wizard, res_users.


What are common use cases for hr.employee.category? or What fields are readonly in hr.employee.category?

Response: To use the hr.employee.category model, you need to provide values for required fields: name. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [required]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


How does merchendise.code relate to other models? or What are the relationships in merchendise.code?

Response: The merchendise.code model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


What methods are defined in sh.wqm.quick.menu original module? or Which fields are stored computed fields in sh.wqm.quick.menu?

Response: The sh.wqm.quick.menu model is defined in module: sh_backmate_theme_adv. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: set_quick_menu, is_quick_menu_avail, is_already_have_in_quick_menu, get_quick_menu_data, remove_quick_menu_data.


What methods are available in account.analytic.account? or How is account.analytic.account implemented technically?

Response: The account.analytic.account model is defined in module: analytic. It has 27 computed fields: balance, debit, credit, currency_id, project_count, journal_id, invoice_count, stage, sub_amount_untaxed, sub_amount_tax, sub_amount_total, sale_amount_untaxed, sale_amount_tax, sale_amount_total, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, display_name, __last_update. Stored computed fields: sub_amount_untaxed, sub_amount_tax, sub_amount_total, sale_amount_untaxed, sale_amount_tax. Related fields: currency_id -> company_id.currency_id. Original module methods: read_group, _compute_debit_credit_balance, name_get, _name_search.


What data types are used in base_import_tests_models_char? or Which columns are nullable in base_import_tests_models_char?

Response: Columns in base_import_tests_models_char: id (integer) [NOT NULL] [DEFAULT: nextval('base_import_tests_models_char_id_seq'::regclass)] [PRECISION: 32]; value (character varying) [COMMENT: Value]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 6. Statistics: 5 nullable, 1 with defaults, 0 with length constraints.


What indexes exist on vendor_evaluation? or What is the vendor_evaluation table?

Response: The vendor_evaluation table has 73 columns and 8 foreign key relationships. It stores data related to vendor evaluation in the system. The table has 3 indexes for performance optimization. Column types: integer: 22, character varying: 30, date: 3, boolean: 12, double precision: 4, timestamp without time zone: 2. Nullable columns: 68, columns with defaults: 1.


What are the column types in ks_dn_measure_field_rel_2? or What data types are used in ks_dn_measure_field_rel_2?

Response: Columns in ks_dn_measure_field_rel_2: measure_field_id_2 (integer) [NOT NULL] [PRECISION: 32]; field_id (integer) [NOT NULL] [PRECISION: 32]. Total columns: 2. Statistics: 0 nullable, 0 with defaults, 0 with length constraints.


What indexes exist on mrp_production_mrp_production_backorder_rel? or Tell me about the mrp_production_mrp_production_backorder_rel table.

Response: The mrp_production_mrp_production_backorder_rel table has 2 columns and 2 foreign key relationships. It stores data related to mrp production mrp production backorder rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


Which fields are required in account.tax.report.line? or What computed fields exist in account.tax.report.line?

Response: The account.tax.report.line model has 18 fields. Field types distribution: many2many: 1, many2one: 5, one2many: 1, integer: 2, char: 6, datetime: 3. Computed fields: 2. Field details: tag_ids (many2many) -> account.account.tag [module: account]; report_action_id (many2one) -> ir.actions.act_window [module: account]; children_line_ids (one2many) -> account.tax.report.line [module: account]; parent_id (many2one) -> account.tax.report.line [module: account]; sequence (integer) [required] [module: account]; parent_path (char) [module: account]; report_id (many2one) [required] -> account.tax.report [module: account]; code (char) [module: account]; formula (char) [module: account]; name (char) [required] [module: l10n_multilang]; tag_name (char) [module: l10n_multilang]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


How many columns are in sh_pwa_config? or Describe the sh_pwa_config table structure.

Response: The sh_pwa_config table has 16 columns and 3 foreign key relationships. It stores data related to sh pwa config in the system. The table has 1 indexes for performance optimization. Column types: integer: 4, character varying: 10, timestamp without time zone: 2. Nullable columns: 12, columns with defaults: 1.


What columns have default values in sh_mrp_pics? or What are the column types in sh_mrp_pics?

Response: Columns in sh_mrp_pics: id (integer) [NOT NULL] [DEFAULT: nextval('sh_mrp_pics_id_seq'::regclass)] [PRECISION: 32]; product_id (integer) [PRECISION: 32] [COMMENT: Product]; sh_message (text) [COMMENT: Measurement Message]; sh_quality_point_id (integer) [PRECISION: 32] [COMMENT: Quality Control Point]; mrp_id (integer) [PRECISION: 32] [COMMENT: Manufacturing]; workorder_id (integer) [PRECISION: 32] [COMMENT: Work Order]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 10. Statistics: 9 nullable, 1 with defaults, 0 with length constraints.


Show me the foreign key constraints of product_product_sh_sale_product_profit_wizard_rel. or List all constraint names in product_product_sh_sale_product_profit_wizard_rel.

Response: Foreign keys in product_product_sh_sale_product_profit_wizard_rel: sh_sale_product_profit_wizard_id -> sh_sale_product_profit_wizard.id [constraint: product_product_sh_sale_produ_sh_sale_product_profit_wizar_fkey]; product_product_id -> product_product.id [constraint: product_product_sh_sale_product_profit__product_product_id_fkey]. Total foreign key relationships: 2. Referenced tables: sh_sale_product_profit_wizard, product_product.