What data types are used in purchase_order_line? or Describe the columns of purchase_order_line.

Response: Columns in purchase_order_line: id (integer) [NOT NULL] [DEFAULT: nextval('purchase_order_line_id_seq'::regclass)] [PRECISION: 32]; name (text) [NOT NULL] [COMMENT: Description]; sequence (integer) [PRECISION: 32] [COMMENT: Sequence]; product_qty (numeric) [NOT NULL] [COMMENT: Quantity]; product_uom_qty (double precision) [PRECISION: 53] [COMMENT: Total Quantity]; date_planned (timestamp without time zone) [COMMENT: Delivery Date]; product_uom (integer) [PRECISION: 32] [COMMENT: Unit of Measure]; product_id (integer) [PRECISION: 32] [COMMENT: Product]; price_unit (numeric) [NOT NULL] [COMMENT: Unit Price]; price_subtotal (numeric) [COMMENT: Subtotal]; price_total (numeric) [COMMENT: Total]; price_tax (double precision) [PRECISION: 53] [COMMENT: Tax]; order_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Order Reference]; account_analytic_id (integer) [PRECISION: 32] [COMMENT: Analytic Account]; company_id (integer) [PRECISION: 32] [COMMENT: Company]; state (character varying) [COMMENT: Status]; qty_invoiced (numeric) [COMMENT: Billed Qty]; qty_received_method (character varying) [COMMENT: Received Qty Method]; qty_received (numeric) [COMMENT: Received Qty]; qty_received_manual (numeric) [COMMENT: Manual Received Qty]; qty_to_invoice (numeric) [COMMENT: To Invoice Quantity]; partner_id (integer) [PRECISION: 32] [COMMENT: Partner]; currency_id (integer) [PRECISION: 32] [COMMENT: Currency]; display_type (character varying) [COMMENT: Display Type]; 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]; orderpoint_id (integer) [PRECISION: 32] [COMMENT: Orderpoint]; product_description_variants (character varying) [COMMENT: Custom Description]; propagate_cancel (boolean) [COMMENT: Propagate cancellation]; sale_order_id (integer) [PRECISION: 32] [COMMENT: Sale Order]; sale_line_id (integer) [PRECISION: 32] [COMMENT: Origin Sale Item]; discount_method (character varying) [COMMENT: Discount Method]; discount_amount (double precision) [PRECISION: 53] [COMMENT: Discount Amount]; discount_amt (double precision) [PRECISION: 53] [COMMENT: Discount Final Amount]; branch_id (integer) [PRECISION: 32] [COMMENT: Branch]; is_down_payment (boolean) [COMMENT: Advance Payment]; confirm_purchase_req_budget (double precision) [PRECISION: 53] [COMMENT: Confirmed Purchase Request Budget]; confirm_realized_amount (double precision) [PRECISION: 53] [COMMENT: Confirmed Realized Budget]; confirm_budget_data (boolean) [COMMENT: Confirm Budget Data]; tick (boolean) [COMMENT: Select Product]; picking_type_id (integer) [PRECISION: 32] [COMMENT: Deliver To]; status (character varying) [COMMENT: State]; agreement_id (integer) [PRECISION: 32] [COMMENT: Purchase Tender]; cancel_lines (boolean) [COMMENT: Cancel Lines]; sh_tender_note (character varying) [COMMENT: Note/Comment]; planned (date) [COMMENT: Planned Date]; gross_total (double precision) [PRECISION: 53] [COMMENT: Gross Total]; price_unit_uom (double precision) [PRECISION: 53] [COMMENT: Price Unit UoM]; last_purchased_price (double precision) [PRECISION: 53] [COMMENT: Last Purchased Price]; last_customer_purchase_price (double precision) [PRECISION: 53] [COMMENT: Last Purchase Price Of Vendor]; is_goods_orders (boolean) [COMMENT: Goods Orders]; is_services_orders (boolean) [COMMENT: Services Orders]; destination_location_id (integer) [PRECISION: 32] [COMMENT: Destination Location]; destination_warehouse_id (integer) [PRECISION: 32] [COMMENT: Destination]; request_line_id (integer) [PRECISION: 32] [COMMENT: Purchase Request Line]; sequence2 (integer) [PRECISION: 32] [COMMENT: No]; avg_price (double precision) [PRECISION: 53] [COMMENT: Average Price]; current_qty (double precision) [PRECISION: 53] [COMMENT: Current Qty in Warehouse]; incoming_stock (double precision) [PRECISION: 53] [COMMENT: Incoming Stock]; actual_progress (double precision) [PRECISION: 53] [COMMENT: Actual Progress]; remaining_progress (double precision) [PRECISION: 53] [COMMENT: Remaining Progress]; progress_paid (double precision) [PRECISION: 53] [COMMENT: Progress Paid]; date_received (timestamp without time zone) [COMMENT: Received Date]; reference_purchase_price (double precision) [PRECISION: 53] [COMMENT: Reference Price]; purchase_line_cost_saving (double precision) [PRECISION: 53] [COMMENT: Cost Savings]; total_cost_saving (double precision) [PRECISION: 53] [COMMENT: Total Cost Savings]; cost_saving_percentage (double precision) [PRECISION: 53] [COMMENT: Cost Savings (%)]; total_price (numeric) [COMMENT: Total Price]; discounted_value (double precision) [PRECISION: 53] [COMMENT: Discounted Value]; state_delivery (character varying) [COMMENT: Status Delivery]; state_inv (character varying) [COMMENT: Status Invoice]; multi_discount (character varying) [COMMENT: Multi Discount]; virtual_available_at_date (numeric) [COMMENT: Virtual Available At Date]; scheduled_date (timestamp without time zone) [COMMENT: Scheduled Date]; forecast_expected_date (timestamp without time zone) [COMMENT: Forecast Expected Date]; free_qty_today (numeric) [COMMENT: Free Qty Today]; qty_available_today (double precision) [PRECISION: 53] [COMMENT: Qty Available Today]; qty_to_deliver (numeric) [COMMENT: Qty To Deliver]; is_mto (boolean) [COMMENT: Is Mto]; display_qty_widget (boolean) [COMMENT: Display Qty Widget]; route_id (integer) [PRECISION: 32] [COMMENT: Route]; bid (numeric) [COMMENT: Vendor Bid]; cost_saving (numeric) [COMMENT: Cost Saving]; base_price (numeric) [COMMENT: Base Price]; update_base (boolean) [COMMENT: Update Base Price]; feedback (character varying) [COMMENT: Feedback]; company_size (character varying) [COMMENT: Company Size]; base_quantity (double precision) [PRECISION: 53] [COMMENT: Base Quantity]; purchase_order_id (integer) [PRECISION: 32] [COMMENT: Purchase Order]; requisition_line_id (integer) [PRECISION: 32] [COMMENT: Requisition Line]; agreement_line_id (integer) [PRECISION: 32] [COMMENT: Agreement Line]; sh_product_description (text) [COMMENT: Product Description]; is_reward_line (boolean) [COMMENT: Reward Line]; price_reduce (numeric) [COMMENT: Price Reduce]; is_assets_orders (boolean) [COMMENT: Assets Orders]; barcode (character varying) [COMMENT: Barcode]; merchendise_id (integer) [PRECISION: 32] [COMMENT: Merchendise Code]. Total columns: 99. Statistics: 94 nullable, 1 with defaults, 0 with length constraints.


What one2many fields are in mrp.consumption.warning? or What are the relationships in mrp.consumption.warning?

Response: The mrp.consumption.warning model has 4 relational fields: mrp_production_ids -> mrp.production; mrp_consumption_warning_line_ids -> mrp.consumption.warning.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: mrp_production_ids. One2many fields: mrp_consumption_warning_line_ids.


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

Response: Columns in account_report_partner_ledger: id (integer) [NOT NULL] [DEFAULT: nextval('account_report_partner_ledger_id_seq'::regclass)] [PRECISION: 32]; amount_currency (boolean) [COMMENT: With Currency]; reconciled (boolean) [COMMENT: Reconciled Entries]; company_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Company]; date_from (date) [COMMENT: Start Date]; date_to (date) [COMMENT: End Date]; target_move (character varying) [NOT NULL] [COMMENT: Target Moves]; result_selection (character varying) [NOT NULL] [COMMENT: Partner's]; 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]; report_currency_id (integer) [PRECISION: 32] [COMMENT: Report Currency]. Total columns: 13. Statistics: 9 nullable, 1 with defaults, 0 with length constraints.


Which fields are stored computed fields in product.product? or Which fields in product.product are computed?

Response: The product.product model is defined in module: product. It has 322 computed fields: price, price_extra, lst_price, code, partner_ref, combination_indices, is_product_variant, pricelist_item_count, image_variant_1024, image_variant_512, image_variant_256, image_variant_128, can_image_variant_1024_be_zoomed, image_1920, image_1024, image_512, image_256, image_128, can_image_1024_be_zoomed, sh_qr_code_img, qty_available, virtual_available, free_qty, incoming_qty, outgoing_qty, nbr_reordering_rules, reordering_min_qty, reordering_max_qty, image_chat, bom_count, used_in_bom_count, mrp_product_qty, date_from, date_to, invoice_state, sale_avg_price, purchase_avg_price, sale_num_invoiced, purchase_num_invoiced, sales_gap, purchase_gap, turnover, total_cost, sale_expected, normal_cost, total_margin, expected_margin, total_margin_rate, expected_margin_rate, purchased_product_qty, value_svl, quantity_svl, valuation, cost_method, sales_count, purchase_price_history_line_ids, website_id, website_url, near_expire, expired, warranty_sale_config, cart_qty, is_generate_product, category_prefix_preference, is_secret_product, variant_short_name, is_variants, purchase_price_totals, assembly_inventory_quantity, assembly_safety_stock_qty, assembly_to_produce_qty, assembly_outgoing_qty, product_display_name, kitchen_inventory_quantity, kitchen_safety_stock_qty, kitchen_to_produce_qty, kitchen_outgoing_qty, is_pos_bom, is_gift_product, warehouse_price_count, standard_price, 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, name, sequence, description, description_purchase, currency_id, cost_currency_id, list_price, volume_uom_name, weight_uom_name, sale_ok, purchase_ok, pricelist_id, uom_id, uom_name, uom_po_id, seller_ids, variant_seller_ids, color, attribute_line_ids, valid_product_template_attribute_line_ids, product_variant_ids, product_variant_id, product_variant_count, has_configurable_attributes, rating_ids, rating_last_value, rating_last_feedback, rating_last_image, rating_count, rating_avg, taxes_id, property_account_income_id, property_account_expense_id, responsible_id, property_stock_production, property_stock_inventory, sale_delay, tracking, description_picking, description_pickingout, description_pickingin, location_id, warehouse_id, has_available_route_ids, route_from_categ_ids, is_seo_optimized, website_meta_title, website_meta_description, website_meta_keywords, website_meta_og_img, seo_name, is_published, can_publish, website_published, membership, membership_date_from, membership_date_to, bom_ids, produce_delay, deferred_revenue_category_id, email_template_id, use_expiration_date, property_account_creditor_price_difference, purchase_method, purchase_line_warn, purchase_line_warn_msg, categ_costing_method, available_in_pos, to_weight, pos_categ_id, purchase_requisition, route_ids, sale_line_warn, sale_line_warn_msg, visible_expense_policy, visible_qty_configurator, invoice_policy, is_consignment, consignment_partner_id, purchase_request, optional_product_ids, service_to_purchase, landed_cost_ok, split_method_landed_cost, website_description, accessory_product_ids, website_size_x, website_size_y, website_ribbon_id, website_sequence, public_categ_ids, product_template_image_ids, subscription_product, recurring_rule_type, recurring_interval, hs_code, cal_pack_price, bi_pack_ids, product_add_mode, inventory_availability, available_threshold, custom_message, service_type, project_template_id, multi_companies_all, product_brand_id, category_sequence, tax_code, doc_code, overhead_cost, is_pack, description_sale, service_policy, service_tracking, project_id, expense_policy, brand_attribute_id, brand_ids, company_id_domain, branch_id, secondary_uom_id, multi_warehouses_all, product_brand_ids, is_sn_autogenerate, is_use_product_code, sn_prefix, suffix, digits, current_sequence, is_product_service_operation, is_product_service_operation_receiving, is_product_service_operation_delivery, is_in_autogenerate, is_in_use_product_code, in_prefix, in_suffix, in_digits, in_current_sequence, selected_barcode_in_pl_report, barcode_labels_line_data, def_packaging_id, group_stock_ids, reordering_rules_ids, length, width, height, variant_attribute_value_ids, hide, expiration_time, use_time, removal_time, alert_time, brand_setting, domain_uom_id, product_ratio_line, uom_categ_id, merchendise_id, pirt, product_halal_certify, type, asset_category_id, asset_entry_perqty, use_on_petty_cash, company_id, sell_ids, is_approve, template_purchase_price_history_line_ids, is_vendor_pricelist, product_limit, min_val, max_val, is_external_link, is_from_assembly, url_pic, produceable_in_kitchen, is_from_kitchen, is_combo_product, combo_option_id, combo_option_items, pos_combo_item_ids, is_combo, is_combo_item, combo_limit, multi_category, pos_categ_ids, multi_uom, price_uom_ids, multi_variant, cross_selling, cross_ids, supplier_barcode, pos_sequence, is_voucher, pizza_modifier, price_unit_each_qty, product_price_quantity_ids, qty_warning_out_stock, combo_price, combo_limit_ids, name_second, special_name, uom_ids, note_ids, tag_ids, pos_branch_id, commission_rate, cycle, discountable, refundable, open_price, default_time, is_employee_meal, is_can_be_po, produceable_in_assembly, not_returnable, can_be_direct, is_for_cash_management, is_cost_per_warehouse, supplier_taxes_id. Stored computed fields: combination_indices, image_variant_1024, image_variant_512, image_variant_256, image_variant_128, can_image_variant_1024_be_zoomed, image_chat, purchase_price_totals, product_display_name. Related fields: image_variant_1024 -> image_variant_1920, image_variant_512 -> image_variant_1920, image_variant_256 -> image_variant_1920, image_variant_128 -> image_variant_1920, valuation -> categ_id.property_valuation, cost_method -> categ_id.property_cost_method, website_id -> product_tmpl_id.website_id, is_generate_product -> categ_id.is_generate_product_code, category_prefix_preference -> categ_id.category_prefix_preference, is_secret_product -> product_tmpl_id.is_secret_product, is_pos_bom -> product_tmpl_id.is_pos_bom, is_gift_product -> product_tmpl_id.is_gift_product, 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, name -> product_tmpl_id.name, sequence -> product_tmpl_id.sequence, description -> product_tmpl_id.description, description_purchase -> product_tmpl_id.description_purchase, currency_id -> product_tmpl_id.currency_id, cost_currency_id -> product_tmpl_id.cost_currency_id, list_price -> product_tmpl_id.list_price, volume_uom_name -> product_tmpl_id.volume_uom_name, weight_uom_name -> product_tmpl_id.weight_uom_name, sale_ok -> product_tmpl_id.sale_ok, purchase_ok -> product_tmpl_id.purchase_ok, pricelist_id -> product_tmpl_id.pricelist_id, uom_id -> product_tmpl_id.uom_id, uom_name -> product_tmpl_id.uom_name, uom_po_id -> product_tmpl_id.uom_po_id, seller_ids -> product_tmpl_id.seller_ids, variant_seller_ids -> product_tmpl_id.variant_seller_ids, color -> product_tmpl_id.color, attribute_line_ids -> product_tmpl_id.attribute_line_ids, valid_product_template_attribute_line_ids -> product_tmpl_id.valid_product_template_attribute_line_ids, product_variant_ids -> product_tmpl_id.product_variant_ids, product_variant_id -> product_tmpl_id.product_variant_id, product_variant_count -> product_tmpl_id.product_variant_count, has_configurable_attributes -> product_tmpl_id.has_configurable_attributes, rating_ids -> product_tmpl_id.rating_ids, rating_last_value -> product_tmpl_id.rating_last_value, rating_last_feedback -> product_tmpl_id.rating_last_feedback, rating_last_image -> product_tmpl_id.rating_last_image, rating_count -> product_tmpl_id.rating_count, rating_avg -> product_tmpl_id.rating_avg, taxes_id -> product_tmpl_id.taxes_id, property_account_income_id -> product_tmpl_id.property_account_income_id, property_account_expense_id -> product_tmpl_id.property_account_expense_id, responsible_id -> product_tmpl_id.responsible_id, property_stock_production -> product_tmpl_id.property_stock_production, property_stock_inventory -> product_tmpl_id.property_stock_inventory, sale_delay -> product_tmpl_id.sale_delay, tracking -> product_tmpl_id.tracking, description_picking -> product_tmpl_id.description_picking, description_pickingout -> product_tmpl_id.description_pickingout, description_pickingin -> product_tmpl_id.description_pickingin, location_id -> product_tmpl_id.location_id, warehouse_id -> product_tmpl_id.warehouse_id, has_available_route_ids -> product_tmpl_id.has_available_route_ids, route_from_categ_ids -> product_tmpl_id.route_from_categ_ids, is_seo_optimized -> product_tmpl_id.is_seo_optimized, website_meta_title -> product_tmpl_id.website_meta_title, website_meta_description -> product_tmpl_id.website_meta_description, website_meta_keywords -> product_tmpl_id.website_meta_keywords, website_meta_og_img -> product_tmpl_id.website_meta_og_img, seo_name -> product_tmpl_id.seo_name, is_published -> product_tmpl_id.is_published, can_publish -> product_tmpl_id.can_publish, website_published -> product_tmpl_id.website_published, membership -> product_tmpl_id.membership, membership_date_from -> product_tmpl_id.membership_date_from, membership_date_to -> product_tmpl_id.membership_date_to, bom_ids -> product_tmpl_id.bom_ids, produce_delay -> product_tmpl_id.produce_delay, deferred_revenue_category_id -> product_tmpl_id.deferred_revenue_category_id, email_template_id -> product_tmpl_id.email_template_id, use_expiration_date -> product_tmpl_id.use_expiration_date, property_account_creditor_price_difference -> product_tmpl_id.property_account_creditor_price_difference, purchase_method -> product_tmpl_id.purchase_method, purchase_line_warn -> product_tmpl_id.purchase_line_warn, purchase_line_warn_msg -> product_tmpl_id.purchase_line_warn_msg, categ_costing_method -> product_tmpl_id.categ_costing_method, available_in_pos -> product_tmpl_id.available_in_pos, to_weight -> product_tmpl_id.to_weight, pos_categ_id -> product_tmpl_id.pos_categ_id, purchase_requisition -> product_tmpl_id.purchase_requisition, route_ids -> product_tmpl_id.route_ids, sale_line_warn -> product_tmpl_id.sale_line_warn, sale_line_warn_msg -> product_tmpl_id.sale_line_warn_msg, visible_expense_policy -> product_tmpl_id.visible_expense_policy, visible_qty_configurator -> product_tmpl_id.visible_qty_configurator, invoice_policy -> product_tmpl_id.invoice_policy, is_consignment -> product_tmpl_id.is_consignment, consignment_partner_id -> product_tmpl_id.consignment_partner_id, purchase_request -> product_tmpl_id.purchase_request, optional_product_ids -> product_tmpl_id.optional_product_ids, service_to_purchase -> product_tmpl_id.service_to_purchase, landed_cost_ok -> product_tmpl_id.landed_cost_ok, split_method_landed_cost -> product_tmpl_id.split_method_landed_cost, website_description -> product_tmpl_id.website_description, accessory_product_ids -> product_tmpl_id.accessory_product_ids, website_size_x -> product_tmpl_id.website_size_x, website_size_y -> product_tmpl_id.website_size_y, website_ribbon_id -> product_tmpl_id.website_ribbon_id, website_sequence -> product_tmpl_id.website_sequence, public_categ_ids -> product_tmpl_id.public_categ_ids, product_template_image_ids -> product_tmpl_id.product_template_image_ids, subscription_product -> product_tmpl_id.subscription_product, recurring_rule_type -> product_tmpl_id.recurring_rule_type, recurring_interval -> product_tmpl_id.recurring_interval, hs_code -> product_tmpl_id.hs_code, cal_pack_price -> product_tmpl_id.cal_pack_price, bi_pack_ids -> product_tmpl_id.bi_pack_ids, product_add_mode -> product_tmpl_id.product_add_mode, inventory_availability -> product_tmpl_id.inventory_availability, available_threshold -> product_tmpl_id.available_threshold, custom_message -> product_tmpl_id.custom_message, service_type -> product_tmpl_id.service_type, project_template_id -> product_tmpl_id.project_template_id, multi_companies_all -> product_tmpl_id.multi_companies_all, product_brand_id -> product_tmpl_id.product_brand_id, category_sequence -> product_tmpl_id.category_sequence, tax_code -> product_tmpl_id.tax_code, doc_code -> product_tmpl_id.doc_code, overhead_cost -> product_tmpl_id.overhead_cost, is_pack -> product_tmpl_id.is_pack, description_sale -> product_tmpl_id.description_sale, service_policy -> product_tmpl_id.service_policy, service_tracking -> product_tmpl_id.service_tracking, project_id -> product_tmpl_id.project_id, expense_policy -> product_tmpl_id.expense_policy, brand_attribute_id -> product_tmpl_id.brand_attribute_id, brand_ids -> product_tmpl_id.brand_ids, company_id_domain -> product_tmpl_id.company_id_domain, branch_id -> product_tmpl_id.branch_id, secondary_uom_id -> product_tmpl_id.secondary_uom_id, multi_warehouses_all -> product_tmpl_id.multi_warehouses_all, product_brand_ids -> product_tmpl_id.product_brand_ids, is_sn_autogenerate -> product_tmpl_id.is_sn_autogenerate, is_use_product_code -> product_tmpl_id.is_use_product_code, sn_prefix -> product_tmpl_id.sn_prefix, suffix -> product_tmpl_id.suffix, digits -> product_tmpl_id.digits, current_sequence -> product_tmpl_id.current_sequence, is_product_service_operation -> product_tmpl_id.is_product_service_operation, is_product_service_operation_receiving -> product_tmpl_id.is_product_service_operation_receiving, is_product_service_operation_delivery -> product_tmpl_id.is_product_service_operation_delivery, is_in_autogenerate -> product_tmpl_id.is_in_autogenerate, is_in_use_product_code -> product_tmpl_id.is_in_use_product_code, in_prefix -> product_tmpl_id.in_prefix, in_suffix -> product_tmpl_id.in_suffix, in_digits -> product_tmpl_id.in_digits, in_current_sequence -> product_tmpl_id.in_current_sequence, selected_barcode_in_pl_report -> product_tmpl_id.selected_barcode_in_pl_report, barcode_labels_line_data -> product_tmpl_id.barcode_labels_line_data, def_packaging_id -> product_tmpl_id.def_packaging_id, group_stock_ids -> product_tmpl_id.group_stock_ids, reordering_rules_ids -> product_tmpl_id.reordering_rules_ids, length -> product_tmpl_id.length, width -> product_tmpl_id.width, height -> product_tmpl_id.height, variant_attribute_value_ids -> product_tmpl_id.variant_attribute_value_ids, hide -> product_tmpl_id.hide, expiration_time -> product_tmpl_id.expiration_time, use_time -> product_tmpl_id.use_time, removal_time -> product_tmpl_id.removal_time, alert_time -> product_tmpl_id.alert_time, brand_setting -> product_tmpl_id.brand_setting, domain_uom_id -> product_tmpl_id.domain_uom_id, product_ratio_line -> product_tmpl_id.product_ratio_line, uom_categ_id -> product_tmpl_id.uom_categ_id, merchendise_id -> product_tmpl_id.merchendise_id, pirt -> product_tmpl_id.pirt, product_halal_certify -> product_tmpl_id.product_halal_certify, type -> product_tmpl_id.type, asset_category_id -> product_tmpl_id.asset_category_id, asset_entry_perqty -> product_tmpl_id.asset_entry_perqty, use_on_petty_cash -> product_tmpl_id.use_on_petty_cash, company_id -> product_tmpl_id.company_id, sell_ids -> product_tmpl_id.sell_ids, is_approve -> product_tmpl_id.is_approve, template_purchase_price_history_line_ids -> product_tmpl_id.template_purchase_price_history_line_ids, is_vendor_pricelist -> product_tmpl_id.is_vendor_pricelist, product_limit -> product_tmpl_id.product_limit, min_val -> product_tmpl_id.min_val, max_val -> product_tmpl_id.max_val, is_external_link -> product_tmpl_id.is_external_link, is_from_assembly -> product_tmpl_id.is_from_assembly, url_pic -> product_tmpl_id.url_pic, produceable_in_kitchen -> product_tmpl_id.produceable_in_kitchen, is_from_kitchen -> product_tmpl_id.is_from_kitchen, is_combo_product -> product_tmpl_id.is_combo_product, combo_option_id -> product_tmpl_id.combo_option_id, combo_option_items -> product_tmpl_id.combo_option_items, pos_combo_item_ids -> product_tmpl_id.pos_combo_item_ids, is_combo -> product_tmpl_id.is_combo, is_combo_item -> product_tmpl_id.is_combo_item, combo_limit -> product_tmpl_id.combo_limit, multi_category -> product_tmpl_id.multi_category, pos_categ_ids -> product_tmpl_id.pos_categ_ids, multi_uom -> product_tmpl_id.multi_uom, price_uom_ids -> product_tmpl_id.price_uom_ids, multi_variant -> product_tmpl_id.multi_variant, cross_selling -> product_tmpl_id.cross_selling, cross_ids -> product_tmpl_id.cross_ids, supplier_barcode -> product_tmpl_id.supplier_barcode, pos_sequence -> product_tmpl_id.pos_sequence, is_voucher -> product_tmpl_id.is_voucher, pizza_modifier -> product_tmpl_id.pizza_modifier, price_unit_each_qty -> product_tmpl_id.price_unit_each_qty, product_price_quantity_ids -> product_tmpl_id.product_price_quantity_ids, qty_warning_out_stock -> product_tmpl_id.qty_warning_out_stock, combo_price -> product_tmpl_id.combo_price, combo_limit_ids -> product_tmpl_id.combo_limit_ids, name_second -> product_tmpl_id.name_second, special_name -> product_tmpl_id.special_name, uom_ids -> product_tmpl_id.uom_ids, note_ids -> product_tmpl_id.note_ids, tag_ids -> product_tmpl_id.tag_ids, pos_branch_id -> product_tmpl_id.pos_branch_id, commission_rate -> product_tmpl_id.commission_rate, cycle -> product_tmpl_id.cycle, discountable -> product_tmpl_id.discountable, refundable -> product_tmpl_id.refundable, open_price -> product_tmpl_id.open_price, default_time -> product_tmpl_id.default_time, is_employee_meal -> product_tmpl_id.is_employee_meal, is_can_be_po -> product_tmpl_id.is_can_be_po, produceable_in_assembly -> product_tmpl_id.produceable_in_assembly, not_returnable -> product_tmpl_id.not_returnable, can_be_direct -> product_tmpl_id.can_be_direct, is_for_cash_management -> product_tmpl_id.is_for_cash_management, is_cost_per_warehouse -> product_tmpl_id.is_cost_per_warehouse, supplier_taxes_id -> product_tmpl_id.supplier_taxes_id. Original module methods: _populate_factories, _compute_can_image_variant_1024_be_zoomed, _compute_image_1920, _set_image_1920, _compute_image_1024, _compute_image_512, _compute_image_256, _compute_image_128, _compute_can_image_1024_be_zoomed, init, _get_invoice_policy, _compute_combination_indices, _compute_is_product_variant, _compute_product_price, _set_product_price, _set_product_lst_price, _compute_product_price_extra, _compute_product_lst_price, _compute_product_code, _compute_partner_ref, _compute_variant_item_count, _onchange_uom_id, _onchange_uom, create, write, unlink, _filter_to_unlink, _unlink_or_archive, copy, _search, _compute_display_name, name_get, _name_search, view_header_get, open_pricelist_rules, open_product_template, _prepare_sellers, _select_seller, price_compute, get_empty_list_help, get_product_multiline_description_sale, _is_variant_possible, toggle_active.


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

Response: Columns in res_users_website_rel: website_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 field types are used in stock.scrap.approval.matrix? or What computed fields exist in stock.scrap.approval.matrix?

Response: The stock.scrap.approval.matrix model has 44 fields. Field types distribution: char: 7, many2one: 11, integer: 6, one2many: 5, selection: 2, date: 2, boolean: 5, many2many: 2, text: 1, datetime: 3. Computed fields: 26. Field details: name (char) [required] [module: equip3_inventory_masterdata]; company_id (many2one) [required] [readonly] -> res.company [module: equip3_inventory_masterdata]; warehouse_id (many2one) [required] -> stock.warehouse [module: equip3_inventory_masterdata]; branch_id (many2one) [readonly] -> res.branch [compute: <bound method Field._compute_related of stock.scrap.approval.matrix.branch_id>] [not stored] [module: equip3_inventory_masterdata] [related: warehouse_id.branch_id]; approval_line_count (integer) [readonly] [compute: approval_line_calc] [not stored] [module: equip3_inventory_masterdata]; sc_approval_matrix_line_ids (one2many) -> stock.scrap.approval.matrix.line [module: equip3_inventory_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 stock.scrap.approval.matrix.activity_user_id>] [not stored] [module: mail] [related: activity_ids.user_id] [inverse: <bound method Field._inverse_related of stock.scrap.approval.matrix.activity_user_id>]; activity_type_id (many2one) -> mail.activity.type [compute: <bound method Field._compute_related of stock.scrap.approval.matrix.activity_type_id>] [not stored] [module: mail] [related: activity_ids.activity_type_id] [inverse: <bound method Field._inverse_related of stock.scrap.approval.matrix.activity_type_id>]; activity_type_icon (char) [readonly] [compute: <bound method Field._compute_related of stock.scrap.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 stock.scrap.approval.matrix.activity_summary>] [not stored] [module: mail] [related: activity_ids.summary] [inverse: <bound method Field._inverse_related of stock.scrap.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].


What columns does pos_order_line have? or Describe the pos_order_line table structure.

Response: The pos_order_line table has 76 columns and 21 foreign key relationships. It stores data related to pos order line in the system. The table has 2 indexes for performance optimization. Column types: integer: 23, character varying: 9, numeric: 14, timestamp without time zone: 2, boolean: 12, double precision: 12, text: 4. Nullable columns: 69, columns with defaults: 1.


How does purchase.change.request relate to other models? or Describe the many2many relations for purchase.change.request.

Response: The purchase.change.request model has 13 relational fields: requested_id -> res.users; budget_std_id -> budget.purchase; company_id -> res.company; branch_id -> res.branch; pur_change_req_ids -> purchase.change.request.line; budget_line -> budget.change.req.line; approval_matrix -> approval.matrix.accounting; approved_matrix_ids -> approval.matrix.accounting.lines; approval_matrix_line_id -> approval.matrix.accounting.lines; currency_id -> res.currency; request_partner_id -> res.partner; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: pur_change_req_ids, budget_line, approved_matrix_ids.


How does account.fiscal.position relate to other models? or Describe the many2many relations for account.fiscal.position.

Response: The account.fiscal.position model has 9 relational fields: company_id -> res.company; account_ids -> account.fiscal.position.account; tax_ids -> account.fiscal.position.tax; country_id -> res.country; country_group_id -> res.country.group; state_ids -> res.country.state; branch_id -> res.branch; create_uid -> res.users; write_uid -> res.users. Many2many fields: state_ids. One2many fields: account_ids, tax_ids.


What are the foreign keys in ir_exports_line? or List all constraint names in ir_exports_line.

Response: Foreign keys in ir_exports_line: create_uid -> res_users.id [constraint: ir_exports_line_create_uid_fkey]; export_id -> ir_exports.id [constraint: ir_exports_line_export_id_fkey]; write_uid -> res_users.id [constraint: ir_exports_line_write_uid_fkey]. Total foreign key relationships: 3. Referenced tables: ir_exports, res_users.


What are the available fields for setu.stock.movement.report? or Show me the fields of setu.stock.movement.report.

Response: The setu.stock.movement.report model has 19 fields. Field types distribution: boolean: 3, binary: 1, date: 3, many2many: 4, many2one: 3, integer: 1, char: 1, datetime: 3. Computed fields: 2. Field details: get_report_from_beginning (boolean) [module: setu_advance_inventory_reports]; stock_file_data (binary) [module: setu_advance_inventory_reports]; start_date (date) [module: setu_advance_inventory_reports]; end_date (date) [module: setu_advance_inventory_reports]; upto_date (date) [module: setu_advance_inventory_reports]; company_ids (many2many) -> res.company [module: setu_advance_inventory_reports]; product_category_ids (many2many) -> product.category [module: setu_advance_inventory_reports]; product_ids (many2many) -> product.product [module: setu_advance_inventory_reports]; warehouse_ids (many2many) -> stock.warehouse [module: setu_advance_inventory_reports]; company_id (many2one) [readonly] -> res.company [module: equip3_inventory_reports]; is_product_daily (boolean) [module: equip3_inventory_reports]; is_movement_daily (boolean) [module: equip3_inventory_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].


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

Response: Foreign keys in res_branch: company_id -> res_company.id [constraint: res_branch_company_id_fkey]; country_id -> res_country.id [constraint: res_branch_country_id_fkey]; create_uid -> res_users.id [constraint: res_branch_create_uid_fkey]; message_main_attachment_id -> ir_attachment.id [constraint: res_branch_message_main_attachment_id_fkey]; state_id -> res_country_state.id [constraint: res_branch_state_id_fkey]; user_id -> res_users.id [constraint: res_branch_user_id_fkey]; write_uid -> res_users.id [constraint: res_branch_write_uid_fkey]. Total foreign key relationships: 7. Referenced tables: res_country, res_company, res_country_state, ir_attachment, res_users.


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

Response: The setu_rfm_segment table has 14 columns and 2 foreign key relationships. It stores data related to setu rfm segment in the system. The table has 1 indexes for performance optimization. Column types: integer: 4, character varying: 1, text: 4, date: 3, timestamp without time zone: 2. Nullable columns: 13, columns with defaults: 1.


How do I use the account.bank.statement.cashbox model? or What fields are readonly in account.bank.statement.cashbox?

Response: To use the account.bank.statement.cashbox model, you need to provide values for required fields: none. Readonly fields: total, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: total [readonly] [computed] [no_copy]; currency_id [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.


How does mrp.document relate to other models? or List all relational fields in mrp.document.

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


What relationships exist for pos_order_line_promotion? or Describe the relational structure of pos_order_line_promotion.

Response: Foreign keys in pos_order_line_promotion: create_uid -> res_users.id [constraint: pos_order_line_promotion_create_uid_fkey]; pos_order_line_id -> pos_order_line.id [constraint: pos_order_line_promotion_pos_order_line_id_fkey]; promotion_id -> pos_promotion.id [constraint: pos_order_line_promotion_promotion_id_fkey]; write_uid -> res_users.id [constraint: pos_order_line_promotion_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: res_users, pos_promotion, pos_order_line.


What tables does res_company_sh_sale_product_indent_wizard_rel reference? or Describe the relational structure of res_company_sh_sale_product_indent_wizard_rel.

Response: Foreign keys in res_company_sh_sale_product_indent_wizard_rel: sh_sale_product_indent_wizard_id -> sh_sale_product_indent_wizard.id [constraint: res_company_sh_sale_product_i_sh_sale_product_indent_wizar_fkey]; res_company_id -> res_company.id [constraint: res_company_sh_sale_product_indent_wizard_r_res_company_id_fkey]. Total foreign key relationships: 2. Referenced tables: sh_sale_product_indent_wizard, res_company.


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

Response: Columns in purchase_agreement_line: id (integer) [NOT NULL] [DEFAULT: nextval('purchase_agreement_line_id_seq'::regclass)] [PRECISION: 32]; agreement_id (integer) [PRECISION: 32] [COMMENT: Purchase Tender]; sh_product_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Product]; sh_qty (double precision) [PRECISION: 53] [COMMENT: Quantity]; sh_price_unit (double precision) [PRECISION: 53] [COMMENT: Unit Price]; company_id (integer) [PRECISION: 32] [COMMENT: Company]; 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]; schedule_date (date) [COMMENT: Scheduled Date]; sequence (integer) [PRECISION: 32] [COMMENT: Sequence]; sequence2 (integer) [PRECISION: 32] [COMMENT: No.]; sh_product_description (text) [COMMENT: Description]; sh_product_uom_id (integer) [PRECISION: 32] [COMMENT: UoM]; dest_warehouse_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Destination]; request_line_id (integer) [PRECISION: 32] [COMMENT: Purchase Request Line]; branch_id (integer) [PRECISION: 32] [COMMENT: Branch]. Total columns: 18. Statistics: 15 nullable, 1 with defaults, 0 with length constraints.


What operations can I perform on pos.generate.efaktur.digunggung? or What are common use cases for pos.generate.efaktur.digunggung?

Response: To use the pos.generate.efaktur.digunggung model, you need to provide values for required fields: none. Readonly fields: no_of_invoice, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: no_of_invoice [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.


What are common use cases for invoice.recurring.line? or What operations can I perform on invoice.recurring.line?

Response: To use the invoice.recurring.line model, you need to provide values for required fields: invoice_recurring_id, account_id, name, price_unit, quantity, analytic_group_ids. Readonly fields: product_uom_category_id, journal_id, subtotal, price_tax, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: invoice_recurring_id [required] [no_copy]; account_id [required]; product_uom_category_id [readonly] [computed] [no_copy]; name [required]; price_unit [required] [has_default]; quantity [required] [has_default]; journal_id [readonly] [computed] [no_copy]; analytic_group_ids [required]; subtotal [readonly] [computed] [no_copy]; price_tax [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.


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

Response: The product_product_setu_inventory_age_breakdown_report_rel table has 2 columns and 2 foreign key relationships. It stores data related to product product setu inventory age breakdown report rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


What columns have default values in stock_route_warehouse? or Show me the column structure of stock_route_warehouse.

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


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

Response: Foreign keys in receivable_flow_wizard: create_uid -> res_users.id [constraint: receivable_flow_wizard_create_uid_fkey]; write_uid -> res_users.id [constraint: receivable_flow_wizard_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


Describe the columns of res_company_sh_sale_product_profit_wizard_rel. or What columns have default values in res_company_sh_sale_product_profit_wizard_rel?

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


List all relational fields in account.loan.pay.amount. or What one2many fields are in account.loan.pay.amount?

Response: The account.loan.pay.amount model has 4 relational fields: loan_id -> account.loan; currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


Describe the implementation of account.asset.asset. or Which fields are stored computed fields in account.asset.asset?

Response: The account.asset.asset model is defined in module: om_account_asset. It has 28 computed fields: entry_count, value_residual, type, months_remaining, months_remaining_fiscal, asset_value_residual, state1, state2, approval_matrix_id, approved_matrix_ids, is_approval_matrix, is_approve_button, approval_matrix_line_id, branch_id, asset_post_entries_count, 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: approval_matrix_id, approved_matrix_ids. Related fields: type -> category_id.type, state1 -> state, state2 -> state, branch_id -> user_id.branch_id. Original module methods: unlink, _cron_generate_entries, compute_generated_entries, _compute_board_amount, _compute_board_undone_dotation_nb, compute_depreciation_board, validate, _return_disposal_view, _get_disposal_moves, set_to_close, set_to_draft, _amount_residual, onchange_company_id, onchange_date_first_depreciation, _entry_count, _check_prorata, onchange_category_id, onchange_category_id_values, onchange_method_time, copy_data, _compute_entries, create, write, open_entries.


What fields are available in full_inv_adjustment_import? or What data types are used in full_inv_adjustment_import?

Response: Columns in full_inv_adjustment_import: id (integer) [NOT NULL] [DEFAULT: nextval('full_inv_adjustment_import_id_seq'::regclass)] [PRECISION: 32]; import_type (character varying) [COMMENT: For Adjustment]; import_name (character varying) [LENGTH: 64] [COMMENT: Import Name]; export_name (character varying) [LENGTH: 64] [COMMENT: Export Name]; is_export (boolean) [COMMENT: Export]; 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: 9. Statistics: 8 nullable, 1 with defaults, 2 with length constraints.


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

Response: The account_tax_template_filiation_rel table has 2 columns and 2 foreign key relationships. It stores data related to account tax template filiation 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 the foreign keys in faktur_message? or How does faktur_message relate to other tables?

Response: Foreign keys in faktur_message: create_uid -> res_users.id [constraint: faktur_message_create_uid_fkey]; write_uid -> res_users.id [constraint: faktur_message_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


What methods are available in stock.landed.cost.lines? or Which fields are stored computed fields in stock.landed.cost.lines?

Response: The stock.landed.cost.lines model is defined in module: stock_landed_costs. It has 3 computed fields: currency_id, display_name, __last_update. Stored computed fields: none. Related fields: currency_id -> cost_id.currency_id. Original module methods: onchange_product_id.


Describe the many2many relations for pos.promotion.discount.order. or How does pos.promotion.discount.order relate to other models?

Response: The pos.promotion.discount.order model has 3 relational fields: promotion_id -> pos.promotion; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


What does the sh.mrp.text model represent? or Can you explain the purpose of sh.mrp.text?

Response: The sh.mrp.text model represents Mrp Quality Measurement Text in the ERP system. It contains 13 fields and is used to manage mrp quality measurement text data. Defined in module: sh_inventory_mrp_qc. Key fields include: product_id, sh_message, mrp_quality_point_id, mrp_id, workorder_id, text_message, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What foreign keys exist in report.dynamic_accounts_report.partner_ageing? or Describe the many2many relations for report.dynamic_accounts_report.partner_ageing.

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


Describe the implementation of account.bank.statement.closebalance. or What methods are available in account.bank.statement.closebalance?

Response: The account.bank.statement.closebalance model is defined in module: account. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: validate.


Can you explain the purpose of sh.tsp.top.selling.product? or Tell me about the sh.tsp.top.selling.product model.

Response: The sh.tsp.top.selling.product model represents Top selling product persistence model to  used in snippet or any other places in the ERP system. It contains 9 fields and is used to manage top selling product persistence model to  used in snippet or any other places data. Defined in module: sh_sale_reports. Key fields include: product_id, qty, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Which fields are stored computed fields in digest.tip? or Describe the implementation of digest.tip.

Response: The digest.tip model is defined in module: digest. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: .


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

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


What methods are defined in ks.sales.forecast.result original module? or What modules define ks.sales.forecast.result?

Response: The ks.sales.forecast.result model is defined in module: ks_sales_forecast. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: .


Tell me about the pos_loyalty_category table. or What is stored in pos_loyalty_category?

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


List all columns in res_branch_sh_purchase_details_report_wizard_rel. or What are the length constraints in res_branch_sh_purchase_details_report_wizard_rel?

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


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

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


Show me the fields of gamification.challenge. or What field types are used in gamification.challenge?

Response: The gamification.challenge model has 47 fields. Field types distribution: char: 3, text: 1, selection: 5, many2one: 10, many2many: 4, date: 4, one2many: 4, boolean: 7, integer: 6, datetime: 3. Computed fields: 14. Field details: name (char) [required] [module: gamification]; description (text) [module: gamification]; state (selection) [required] [module: gamification]; manager_id (many2one) -> res.users [module: gamification]; user_ids (many2many) -> res.users [module: gamification]; user_domain (char) [module: gamification]; period (selection) [required] [module: gamification]; start_date (date) [module: gamification]; end_date (date) [module: gamification]; invited_user_ids (many2many) -> res.users [module: gamification]; line_ids (one2many) [required] -> gamification.challenge.line [module: gamification]; reward_id (many2one) -> gamification.badge [module: gamification]; reward_first_id (many2one) -> gamification.badge [module: gamification]; reward_second_id (many2one) -> gamification.badge [module: gamification]; reward_third_id (many2one) -> gamification.badge [module: gamification]; reward_failure (boolean) [module: gamification]; reward_realtime (boolean) [module: gamification]; visibility_mode (selection) [required] [module: gamification]; report_message_frequency (selection) [required] [module: gamification]; report_message_group_id (many2one) -> mail.channel [module: gamification]; report_template_id (many2one) [required] -> mail.template [module: gamification]; remind_update_delay (integer) [module: gamification]; last_report_date (date) [module: gamification]; next_report_date (date) [readonly] [compute: _get_next_report_date] [stored] [module: gamification]; challenge_category (selection) [required] [module: gamification]; 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].


What models are connected to report_excel_import_wizard? or Describe the many2many relations for report_excel_import_wizard.

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


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

Response: The asset_asset_revalue_wizard table has 16 columns and 6 foreign key relationships. It stores data related to asset asset revalue wizard in the system. The table has 1 indexes for performance optimization. Column types: integer: 9, character varying: 1, numeric: 2, double precision: 1, date: 1, timestamp without time zone: 2. Nullable columns: 9, columns with defaults: 1.


Describe the field structure of account.account.map.line. or What data can be stored in account.account.map.line?

Response: The account.account.map.line model has 17 fields. Field types distribution: many2one: 8, integer: 1, char: 1, datetime: 3, one2many: 3, float: 1. Computed fields: 9. Field details: company_id (many2one) [readonly] -> res.company [compute: <bound method Field._compute_related of account.account.map.line.company_id>] [not stored] [module: equip3_accounting_masterdata] [related: map_id.company_id]; account_id (many2one) -> account.account [module: equip3_accounting_masterdata]; target_company (many2one) [readonly] -> res.company [compute: <bound method Field._compute_related of account.account.map.line.target_company>] [not stored] [module: equip3_accounting_masterdata] [related: map_id.child_company_id]; target_account (many2one) [readonly] -> account.account [module: equip3_accounting_masterdata]; map_id (many2one) [required] -> account.account.map [module: equip3_accounting_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]; line_ids (one2many) -> account.account.map.line [compute: <bound method Field._compute_related of account.account.map.line.line_ids>] [not stored] [module: None] [related: map_id.line_ids] [inverse: <bound method Field._inverse_related of account.account.map.line.line_ids>]; child_company_id (many2one) [required] -> res.company [compute: <bound method Field._compute_related of account.account.map.line.child_company_id>] [not stored] [module: None] [related: map_id.child_company_id] [inverse: <bound method Field._inverse_related of account.account.map.line.child_company_id>]; ownership (float) [compute: <bound method Field._compute_related of account.account.map.line.ownership>] [not stored] [module: None] [related: map_id.ownership] [inverse: <bound method Field._inverse_related of account.account.map.line.ownership>]; sales_line_ids (one2many) -> account.tax.map.sales.line [compute: <bound method Field._compute_related of account.account.map.line.sales_line_ids>] [not stored] [module: None] [related: map_id.sales_line_ids] [inverse: <bound method Field._inverse_related of account.account.map.line.sales_line_ids>]; purchase_line_ids (one2many) -> account.tax.map.purchase.line [compute: <bound method Field._compute_related of account.account.map.line.purchase_line_ids>] [not stored] [module: None] [related: map_id.purchase_line_ids] [inverse: <bound method Field._inverse_related of account.account.map.line.purchase_line_ids>].


What is the account_journal_accounting_report_rel table? or Describe the account_journal_accounting_report_rel table structure.

Response: The account_journal_accounting_report_rel table has 2 columns and 2 foreign key relationships. It stores data related to account journal accounting report rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


Can you explain the purpose of project.create.sale.order? or What is the project.create.sale.order model?

Response: The project.create.sale.order model represents Create SO from project in the ERP system. It contains 16 fields and is used to manage create so from project data. Defined in module: sale_timesheet. Key fields include: project_id, company_id, partner_id, commercial_partner_id, pricing_type, link_selection, sale_order_id, line_ids, info_invoice, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Show me the column structure of account_unreconcile. or Describe the columns of account_unreconcile.

Response: Columns in account_unreconcile: id (integer) [NOT NULL] [DEFAULT: nextval('account_unreconcile_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.


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

Response: The product_category_sh_purchase_category_wizard_rel table has 2 columns and 2 foreign key relationships. It stores data related to product category sh purchase category 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 data types are used in sh_report_section? or Which columns are nullable in sh_report_section?

Response: Columns in sh_report_section: id (integer) [NOT NULL] [DEFAULT: nextval('sh_report_section_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [NOT NULL] [COMMENT: Section Title]; type (character varying) [NOT NULL] [COMMENT: Section Type]; content_text (text) [COMMENT: Text]; content_html (text) [COMMENT: HTML]; type_id (integer) [PRECISION: 32] [COMMENT: Type]; text_size (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Text Size]; color (character varying) [COMMENT: Background Color]; borders (boolean) [COMMENT: Border]; border_size (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Border Size]; border_style (character varying) [NOT NULL] [COMMENT: Border Type]; border_color (character varying) [NOT NULL] [COMMENT: Border Color]; 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: 16. Statistics: 9 nullable, 1 with defaults, 0 with length constraints.


How is sh.sale.details.report.wizard used in the system? or Can you explain the purpose of sh.sale.details.report.wizard?

Response: The sh.sale.details.report.wizard model represents sh sale details report wizard model in the ERP system. It contains 19 fields and is used to manage sh sale details report wizard model data. Defined in module: sh_sale_reports. Key fields include: start_date, end_date, team_ids, company_ids, company_id, state, total_paid, payments, company_name, taxes, products, currency_precision, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: The pos_config_settings table has 13 columns and 3 foreign key relationships. It stores data related to pos config settings in the system. The table has 1 indexes for performance optimization. Column types: integer: 5, character varying: 1, boolean: 5, timestamp without time zone: 2. Nullable columns: 11, columns with defaults: 1.


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

Response: Foreign keys in pos_promotion_res_branch_rel: pos_promotion_id -> pos_promotion.id [constraint: pos_promotion_res_branch_rel_pos_promotion_id_fkey]; res_branch_id -> res_branch.id [constraint: pos_promotion_res_branch_rel_res_branch_id_fkey]. Total foreign key relationships: 2. Referenced tables: res_branch, pos_promotion.


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

Response: Foreign keys in invoice_deposit_line_reconcile: create_uid -> res_users.id [constraint: invoice_deposit_line_reconcile_create_uid_fkey]; deposit_reconcile_id -> account_deposit_reconcile.id [constraint: invoice_deposit_line_reconcile_deposit_reconcile_id_fkey]; invoice_id -> account_move.id [constraint: invoice_deposit_line_reconcile_invoice_id_fkey]; write_uid -> res_users.id [constraint: invoice_deposit_line_reconcile_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: account_deposit_reconcile, res_users, account_move.


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

Response: The ks_dashboard_ninja_item_action table has 13 columns and 5 foreign key relationships. It stores data related to ks dashboard ninja item action in the system. The table has 1 indexes for performance optimization. Column types: integer: 8, character varying: 3, timestamp without time zone: 2. Nullable columns: 12, columns with defaults: 1.


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

Response: The cust_credit_limit_xls table has 6 columns and 2 foreign key relationships. It stores data related to cust credit limit 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.


What fields does product.expiry.config have? or List all fields in the product.expiry.config model.

Response: The product.expiry.config model has 12 fields. Field types distribution: char: 5, boolean: 1, integer: 1, many2one: 2, datetime: 3. Computed fields: 3. Field details: name (char) [readonly] [compute: _change_name] [stored] [module: aspl_product_expiry_alert]; no_of_days (char) [module: aspl_product_expiry_alert]; active (boolean) [module: aspl_product_expiry_alert]; block_color (char) [module: aspl_product_expiry_alert]; text_color (char) [module: aspl_product_expiry_alert]; 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 account.payment.register model in Odoo. or What does the account.payment.register model represent?

Response: The account.payment.register model represents Register Payment in the ERP system. It contains 73 fields and is used to manage register payment data. Defined in module: account. Key fields include: payment_date, amount, communication, group_payment, currency_id, journal_id, company_currency_id, line_ids, payment_type, partner_type, source_amount, source_amount_currency, source_currency_id, can_edit_wizard, can_group_payments, company_id, partner_id, payment_method_id, available_payment_method_ids, hide_payment_method, payment_difference, payment_difference_handling, writeoff_account_id, writeoff_label, show_partner_bank_account, require_partner_bank_account, country_code, is_prepayment, prepayment_journal_id, start_date, end_date, recurring_interval, recurring_interval_unit, stop_recurring_interval, stop_recurring_interval_unit, revenue_account, move_type, is_show_prepayment, payment_token_id, suitable_payment_token_partner_ids, payment_method_code, apply_manual_currency_exchange, manual_currency_exchange_rate, active_manual_currency_rate, receipt_approval_matrix_id, is_receipt_approval_matrix, difference_ids, payment_difference_amount, partner_bank_id, administration, analytic_group_ids, administration_account, administration_fee, current_rate_id, current_inverse_rate_id, is_same_main_currency, inverse_rate, estimasi_transfer, is_vendor_deposit, validated_move_ids, available_partner_bank_ids, pos_validate_file, pos_validate_filename, validate_data, validated_line_ids, branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What does the qiscus.wa.template.content model represent? or Describe the qiscus.wa.template.content model in Odoo.

Response: The qiscus.wa.template.content model represents qiscus.wa.template.content in the ERP system. It contains 13 fields and is used to manage qiscus.wa.template.content data. Defined in module: equip3_general_features. Key fields include: template_id, name, language, content_id, content, category, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What indexes exist on product_variant_combination? or How many columns are in product_variant_combination?

Response: The product_variant_combination table has 2 columns and 10 foreign key relationships. It stores data related to product variant combination in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


Describe the res_groups_sh_custom_model_tab_rel table structure. or What columns does res_groups_sh_custom_model_tab_rel have?

Response: The res_groups_sh_custom_model_tab_rel table has 2 columns and 2 foreign key relationships. It stores data related to res groups sh custom model tab rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


What is the res.partner.category model? or Tell me about the res.partner.category model.

Response: The res.partner.category model represents Partner Tags in the ERP system. It contains 14 fields and is used to manage partner tags data. Defined in module: base. Key fields include: name, color, parent_id, child_ids, active, parent_path, partner_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: The base_import_tests_models_m2o_required_related table has 6 columns and 2 foreign key relationships. It stores data related to base import tests models m2o required related in the system. The table has 1 indexes for performance optimization. Column types: integer: 4, timestamp without time zone: 2. Nullable columns: 5, columns with defaults: 1.


List all constraint names in debt_collection_report. or What tables does debt_collection_report reference?

Response: Foreign keys in debt_collection_report: company_id -> res_company.id [constraint: debt_collection_report_company_id_fkey]; create_uid -> res_users.id [constraint: debt_collection_report_create_uid_fkey]; report_currency_id -> res_currency.id [constraint: debt_collection_report_report_currency_id_fkey]; write_uid -> res_users.id [constraint: debt_collection_report_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: res_currency, res_users, res_company.


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

Response: The sh_custom_model_purchase_order table has 56 columns and 11 foreign key relationships. It stores data related to sh custom model purchase order in the system. The table has 10 indexes for performance optimization. Column types: integer: 14, character varying: 27, text: 3, boolean: 10, timestamp without time zone: 2. Nullable columns: 48, columns with defaults: 1.


List all fields in the report.sh_sale_reports.sh_sale_by_category_doc model. or What fields does report.sh_sale_reports.sh_sale_by_category_doc have?

Response: The report.sh_sale_reports.sh_sale_by_category_doc model has 3 fields. Field types distribution: integer: 1, char: 1, datetime: 1. Computed fields: 2. Field details: 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].


How to query reference.purchase.price data? or What operations can I perform on reference.purchase.price?

Response: To use the reference.purchase.price model, you need to provide values for required fields: product_id, product_tmpl_id, available_product_id, reference_purchase_price, currency_id. Readonly fields: available_product_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: product_id [required]; product_tmpl_id [required]; available_product_id [required] [readonly] [computed] [no_copy]; reference_purchase_price [required]; currency_id [required] [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.


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

Response: The product_variant_attribute_value_rel table has 2 columns and 2 foreign key relationships. It stores data related to product variant attribute value 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 fields in the ks_ninja_dashboard.item_action model. or What are the available fields for ks_ninja_dashboard.item_action?

Response: The ks_ninja_dashboard.item_action model has 12 fields. Field types distribution: char: 2, many2many: 2, selection: 1, many2one: 3, integer: 1, datetime: 3. Computed fields: 2. Field details: name (char) [module: ks_dashboard_ninja]; ks_dashboard_item_ids (many2many) -> ks_dashboard_ninja.item [module: ks_dashboard_ninja]; ks_action (selection) [module: ks_dashboard_ninja]; ks_dashboard_ninja_id (many2one) -> ks_dashboard_ninja.board [module: ks_dashboard_ninja]; ks_dashboard_ninja_ids (many2many) -> ks_dashboard_ninja.board [module: ks_dashboard_ninja]; 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 inter.transfer.company.line. or What field types are used in inter.transfer.company.line?

Response: The inter.transfer.company.line model has 11 fields. Field types distribution: many2one: 4, integer: 2, float: 1, char: 1, datetime: 3. Computed fields: 3. Field details: internal_id (many2one) -> inter.transfer.company [module: bi_inter_company_transfer]; product_id (many2one) [required] -> product.product [module: bi_inter_company_transfer]; quantity (integer) [required] [module: bi_inter_company_transfer]; price_unit (float) [readonly] [compute: <bound method Field._compute_related of inter.transfer.company.line.price_unit>] [not stored] [module: bi_inter_company_transfer] [related: product_id.lst_price]; 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 foreign key constraints of efaktur_export. or What relationships exist for efaktur_export?

Response: Foreign keys in efaktur_export: company_id -> res_company.id [constraint: efaktur_export_company_id_fkey]; create_uid -> res_users.id [constraint: efaktur_export_create_uid_fkey]; partner_id -> res_partner.id [constraint: efaktur_export_partner_id_fkey]; write_uid -> res_users.id [constraint: efaktur_export_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: res_partner, res_users, res_company.


List all columns in account_cash_rounding. or What columns have default values in account_cash_rounding?

Response: Columns in account_cash_rounding: id (integer) [NOT NULL] [DEFAULT: nextval('account_cash_rounding_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [NOT NULL] [COMMENT: Name]; rounding (double precision) [NOT NULL] [PRECISION: 53] [COMMENT: Rounding Precision]; strategy (character varying) [NOT NULL] [COMMENT: Rounding Strategy]; rounding_method (character varying) [NOT NULL] [COMMENT: Rounding Method]; 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: 9. Statistics: 4 nullable, 1 with defaults, 0 with length constraints.


Which fields are stored computed fields in account.move.line? or What are the technical details of account.move.line?

Response: The account.move.line model is defined in module: account. It has 65 computed fields: asset_start_date, asset_end_date, asset_mrr, purchase_order_id, period_id, fiscal_year, product_type, discount_type, move_name, date, ref, parent_state, journal_id, company_id, company_currency_id, tax_fiscal_country_id, account_internal_type, account_internal_group, account_root_id, balance, cumulated_balance, reconciled, product_uom_category_id, payment_id, statement_line_id, statement_id, tax_line_id, tax_group_id, tax_audit, amount_residual, amount_residual_currency, matching_number, analytic_account_id, analytic_tag_ids, is_fiscal_book_exclude, price_tax, unit_price_fnct, is_analytic_tags, total_qty_price_unit, is_intercompany_transaction, tax_ids_ppn, pos_branch_id, check_reconcile, 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: asset_start_date, asset_end_date, asset_mrr, period_id, fiscal_year, move_name, date, ref, parent_state, journal_id, company_id, company_currency_id, account_root_id, balance, reconciled, payment_id, statement_line_id, statement_id, tax_line_id, tax_group_id, tax_audit, amount_residual, amount_residual_currency, matching_number, analytic_account_id, analytic_tag_ids, total_qty_price_unit, pos_branch_id. Related fields: purchase_order_id -> purchase_line_id.order_id, period_id -> move_id.period_id, fiscal_year -> period_id.fiscal_year_id, product_type -> product_id.type, discount_type -> move_id.discount_type, move_name -> move_id.name, date -> move_id.date, ref -> move_id.ref, parent_state -> move_id.state, journal_id -> move_id.journal_id, company_id -> move_id.company_id, company_currency_id -> company_id.currency_id, tax_fiscal_country_id -> move_id.company_id.account_tax_fiscal_country_id, account_internal_type -> account_id.user_type_id.type, account_internal_group -> account_id.user_type_id.internal_group, account_root_id -> account_id.root_id, product_uom_category_id -> product_id.uom_id.category_id, payment_id -> move_id.payment_id, statement_line_id -> move_id.statement_line_id, statement_id -> statement_line_id.statement_id, tax_group_id -> tax_line_id.tax_group_id, is_fiscal_book_exclude -> move_id.is_fiscal_book_exclude, is_intercompany_transaction -> move_id.is_intercompany_transaction, pos_branch_id -> move_id.pos_branch_id, 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: _get_default_line_name, _get_default_tax_account, _get_computed_name, _get_computed_price_unit, _get_computed_account, _get_computed_taxes, _get_computed_uom, _set_price_and_tax_after_fpos, _compute_analytic_account, _get_price_total_and_subtotal, _get_price_total_and_subtotal_model, _get_fields_onchange_subtotal, _get_fields_onchange_subtotal_model, _get_fields_onchange_balance, _get_fields_onchange_balance_model, _onchange_mark_recompute_taxes, _onchange_mark_recompute_taxes_analytic, _onchange_product_id, _onchange_uom_id, _onchange_account_id, _onchange_balance, _onchange_debit, _onchange_credit, _onchange_amount_currency, _onchange_price_subtotal, _onchange_currency, _compute_matching_number, _compute_balance, search_read, _compute_cumulated_balance, _compute_amount_residual, _compute_tax_line_id, _compute_tax_audit, _get_refund_tax_audit_condition, _check_constrains_account_id_journal_id, _check_off_balance, _affect_tax_report, _check_tax_lock_date, _check_reconciliation, init, create, write, _valid_field_parameter, unlink, default_get, name_get, _get_formated_values, _get_tracking_field_string, _prepare_reconciliation_partials, _create_exchange_difference_move, reconcile, remove_move_reconcile, _copy_data_extend_business_fields, copy_data, _get_analytic_tag_ids, create_analytic_lines, _prepare_analytic_line, _prepare_analytic_distribution_line, _query_get, _reconciled_lines, open_reconcile_view, action_automatic_entry, _get_suspense_moves_domain, _get_attachment_domains, _convert_tags_for_cash_basis, _revert_signed_tags, _message_post_process_attachments.


How to create records in pos.bus.log? or What are common use cases for pos.bus.log?

Response: To use the pos.bus.log 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.


What fields are readonly in assets.approval.matrix? or How to work with assets.approval.matrix fields?

Response: To use the assets.approval.matrix model, you need to provide values for required fields: name, company_id, branch_id. Readonly fields: company_id, is_assets_approval, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, access_url, access_warning, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [required]; company_id [required] [readonly] [has_default]; branch_id [required]; is_assets_approval [readonly] [computed] [no_copy]; activity_state [readonly] [computed] [no_copy]; activity_user_id [computed] [no_copy]; activity_type_id [computed] [no_copy]; activity_type_icon [readonly] [computed] [no_copy]; activity_date_deadline [readonly] [computed] [no_copy]; my_activity_date_deadline [readonly] [computed] [no_copy]; activity_summary [computed] [no_copy]; activity_exception_decoration [readonly] [computed] [no_copy]; activity_exception_icon [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]; access_url [readonly] [computed] [no_copy]; access_warning [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.


Tell me about the report.excel model. or Can you explain the purpose of report.excel?

Response: The report.excel model represents Report Excel in the ERP system. It contains 28 fields and is used to manage report excel data. Defined in module: report_excel. Key fields include: name, active, out_file_name, data, doc_count, datas_fname, template_name_id, sheet_reference, description, description_report, root_model_id, ir_values_id, show_level, show_autofilter, report_excel_param_ids, report_id, report_excel_param_content, report_excel_section_ids, send_email, email_template_id, report_lang_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How is pos.promotion.discount.category used in the system? or What is the pos.promotion.discount.category model?

Response: The pos.promotion.discount.category model represents Promotion each product categories in the ERP system. It contains 17 fields and is used to manage promotion each product categories data. Defined in module: equip3_pos_masterdata. Key fields include: active, category_id, category_ids, discount, min_qty, discount2, multi_discount, promotion_id, discount_fixed_amount, max_discount_amount, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How to work with project.task.create.sale.order fields? or What are common use cases for project.task.create.sale.order?

Response: To use the project.task.create.sale.order model, you need to provide values for required fields: link_selection, task_id, partner_id, product_id. Readonly fields: commercial_partner_id, info_invoice, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: link_selection [required] [has_default]; task_id [required]; partner_id [required]; product_id [required]; currency_id [computed] [no_copy]; commercial_partner_id [readonly] [computed] [no_copy]; info_invoice [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.


What is the module hierarchy for pos.payment.wizard? or How is pos.payment.wizard implemented technically?

Response: The pos.payment.wizard model is defined in module: equip3_pos_report. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: pos_payment_report, generate_report, print_excel_report.


What are the foreign keys in bus_bus? or What relationships exist for bus_bus?

Response: Foreign keys in bus_bus: create_uid -> res_users.id [constraint: bus_bus_create_uid_fkey]; write_uid -> res_users.id [constraint: bus_bus_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


What operations can I perform on pos.promotion.discount.apply? or How to create records in pos.promotion.discount.apply?

Response: To use the pos.promotion.discount.apply model, you need to provide values for required fields: product_id, promotion_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: product_id [required]; promotion_id [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 internal.transfer.line? or What business logic is in internal.transfer.line?

Response: To use the internal.transfer.line model, you need to provide values for required fields: product_id, uom, description. Readonly fields: transfer_qty, return_qty, total_trf, filter_source_loc, filter_dest_loc, current_qty, filter_available_product_ids, status, itr_in_progress_qty, itr_remaining_qty, current_dest_qty, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: product_id [required]; uom [required]; transfer_qty [readonly]; return_qty [readonly] [computed] [no_copy]; total_trf [readonly] [computed] [no_copy]; filter_source_loc [readonly] [computed] [no_copy]; filter_dest_loc [readonly] [computed] [no_copy]; current_qty [readonly] [computed] [no_copy]; filter_available_product_ids [readonly] [computed] [no_copy]; status [readonly] [computed] [no_copy]; description [required]; itr_in_progress_qty [readonly] [computed] [no_copy]; itr_remaining_qty [readonly] [computed] [no_copy]; current_dest_qty [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.


List all constraint names in account_analytic_account. or How does account_analytic_account relate to other tables?

Response: Foreign keys in account_analytic_account: branch_id -> res_branch.id [constraint: account_analytic_account_branch_id_fkey]; company_id -> res_company.id [constraint: account_analytic_account_company_id_fkey]; create_uid -> res_users.id [constraint: account_analytic_account_create_uid_fkey]; group_id -> account_analytic_group.id [constraint: account_analytic_account_group_id_fkey]; message_main_attachment_id -> ir_attachment.id [constraint: account_analytic_account_message_main_attachment_id_fkey]; order_invoice_currency_id -> res_currency.id [constraint: account_analytic_account_order_invoice_currency_id_fkey]; partner_id -> res_partner.id [constraint: account_analytic_account_partner_id_fkey]; write_uid -> res_users.id [constraint: account_analytic_account_write_uid_fkey]. Total foreign key relationships: 8. Referenced tables: res_partner, res_company, ir_attachment, res_currency, res_users, res_branch, account_analytic_group.


Tell me about the followup.invoice.tmp model. or What does the followup.invoice.tmp model represent?

Response: The followup.invoice.tmp model represents   in the ERP system. It contains 45 fields and is used to manage   data. Defined in module: equip3_accounting_operation. Key fields include: name, date, partner_id, company_id, currency_id, overdue_template, move_id, total_overdue, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, access_url, access_token, access_warning, sequence_prefix, sequence_number, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What computed fields exist in kpi.period.value? or What data can be stored in kpi.period.value?

Response: The kpi.period.value model has 10 fields. Field types distribution: many2one: 4, float: 1, integer: 1, char: 1, datetime: 3. Computed fields: 2. Field details: period_id (many2one) [required] -> kpi.period [module: kpi_scorecard]; constant_id (many2one) -> kpi.constant [module: kpi_scorecard]; target_value (float) [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 methods are defined in approval.matrix.direct.purchase.line original module? or What are the technical details of approval.matrix.direct.purchase.line?

Response: The approval.matrix.direct.purchase.line model is defined in module: equip3_purchase_other_operation_cont. It has 3 computed fields: sequence2, display_name, __last_update. Stored computed fields: sequence2. Related fields: sequence2 -> sequence. Original module methods: default_get, unlink, create.


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

Response: Columns in purchase_requisition_type: id (integer) [NOT NULL] [DEFAULT: nextval('purchase_requisition_type_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [NOT NULL] [COMMENT: Agreement Type]; sequence (integer) [PRECISION: 32] [COMMENT: Sequence]; exclusive (character varying) [NOT NULL] [COMMENT: Agreement Selection Type]; quantity_copy (character varying) [NOT NULL] [COMMENT: Quantities]; line_copy (character varying) [NOT NULL] [COMMENT: Lines]; 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: 5 nullable, 1 with defaults, 0 with length constraints.


What is the pos_config_pos_loyalty_rel table? or What is stored in pos_config_pos_loyalty_rel?

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


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

Response: Columns in stock_return_picking: id (integer) [NOT NULL] [DEFAULT: nextval('stock_return_picking_id_seq'::regclass)] [PRECISION: 32]; picking_id (integer) [PRECISION: 32] [COMMENT: Picking]; move_dest_exists (boolean) [COMMENT: Chained Move Exists]; original_location_id (integer) [PRECISION: 32] [COMMENT: Original Location]; parent_location_id (integer) [PRECISION: 32] [COMMENT: Parent Location]; location_id (integer) [PRECISION: 32] [COMMENT: Return Location]; 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]; return_reason (integer) [PRECISION: 32] [COMMENT: Reason]; return_reason_info (text) [COMMENT: Product Return Details]; action (character varying) [COMMENT: Action]. Total columns: 13. Statistics: 12 nullable, 1 with defaults, 0 with length constraints.


What methods are defined in setu.inventory.turnover.analysis.report original module? or What methods are available in setu.inventory.turnover.analysis.report?

Response: The setu.inventory.turnover.analysis.report model is defined in module: setu_advance_inventory_reports. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: onchange_product_category_id, onchange_company_id, get_file_name, create_excel_workbook, create_excel_worksheet, set_column_width, set_format, set_report_title, get_inventory_turnover_ratio_data, prepare_data_to_write, download_report, download_report_in_listview, create_data, write_report_data_header, write_data_to_worksheet.


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

Response: The account_partner_ageing table has 13 columns and 4 foreign key relationships. It stores data related to account partner ageing in the system. The table has 1 indexes for performance optimization. Column types: integer: 7, date: 2, character varying: 2, timestamp without time zone: 2. Nullable columns: 8, columns with defaults: 1.