产品详细信息以英文显示。翻译即将推出。
速览
- 价格
- $249.00 USD
- Odoo 版本
- 17, 18, 19
- 设置时间
- 21分钟
- 许可证
- 一次永久
- 语言
- 11 语言
一次性购买
Multi-Level BOM & Where-Used Explorer
Visual multi-level BOM tree with cost roll-up, where-used reverse lookup, and mass component replacement for Odoo 17/18/19.
$249.00USD
现在无需付款。此操作会向我们的团队发送报价请求——我们会通过邮件跟进价格和后续步骤。
核心功能
Indented multi-level BOM tree view that recursively expands every sub-assembly and phantom (kit) BOM down to raw-material leaves in one collapsible OWL widget
Roll-up cost aggregation across all BOM levels, summing component cost, operation cost, and sub-assembly cost bottom-up so the top-level total is always reconciled
Where-used (reverse BOM) lookup: pick any component and instantly list every parent BOM and finished product it feeds into, at direct and indirect levels
Mass component replace wizard that swaps one product for another across every BOM line it appears in, with a preview-and-confirm step before writing changes
BOM cost simulation: enter hypothetical purchase-price or standard-cost changes on components and see the recalculated rolled-up cost of affected finished goods before committing
Per-level cost breakdown showing material vs. operation vs. sub-assembly contribution at each node, so you can see exactly where cost concentrates
Cost variance highlighting that flags nodes where the rolled-up cost diverges from the stored product standard price, surfacing stale costings
Depth and quantity awareness: the tree multiplies quantities correctly through each level and respects unit-of-measure conversions on every BOM line
Version and variant support: explore BOMs per product variant and per active BOM version, honoring Odoo's attribute-based variant BOM selection
Export the expanded tree and roll-up to XLSX/CSV for offline costing reviews, tenders, and audits
Printable QWeb cost report of the full indented BOM with per-line and rolled-up totals, ready for engineering sign-off
Access control via ir.model.access.csv and record rules so only costing/engineering groups can run simulations or execute mass replacements
Multi-company and multi-warehouse safe: cost roll-ups respect company-specific costs and the active company context
Optional XML-RPC/JSON-RPC endpoints so external PLM, ERP, or BI tools can pull the where-used graph and rolled-up cost programmatically
关于此产品
Deep BOM structures are where Odoo's standard Manufacturing app runs out of road. Native mrp.bom shows one level at a time, cost is only computed on demand per variant, and there is no built-in way to ask "which finished goods use this raw material?" When engineering revises a component or a supplier hikes a price, costing and planning teams are left clicking through nested sub-assemblies by hand — slow, error-prone, and impossible to audit.
为什么选择 Multi-Level BOM & Where-Used Explorer
Indented multi-level BOM tree view that recursively expands every sub-assembly and phantom (kit) BOM down to raw-material leaves in one collapsible OWL widget
Roll-up cost aggregation across all BOM levels, summing component cost, operation cost, and sub-assembly cost bottom-up so the top-level total is always reconciled
Where-used (reverse BOM) lookup: pick any component and instantly list every parent BOM and finished product it feeds into, at direct and indirect levels
Mass component replace wizard that swaps one product for another across every BOM line it appears in, with a preview-and-confirm step before writing changes
BOM cost simulation: enter hypothetical purchase-price or standard-cost changes on components and see the recalculated rolled-up cost of affected finished goods before committing
Per-level cost breakdown showing material vs. operation vs. sub-assembly contribution at each node, so you can see exactly where cost concentrates
The Multi-Level BOM & Where-Used Explorer is a build-to-order Odoo module that ECOSIRE designs, builds, installs, and supports for your database. It gives engineering and costing teams a single indented tree that expands every sub-assembly down to raw materials, a live cost roll-up that aggregates standard or purchase cost across all BOM levels, a reverse "where-used" lookup that answers component-impact questions in one click, and a guided mass-replace wizard that swaps a component across every BOM it appears in — all inside your existing Odoo Manufacturing workflow.
This is not a one-size-fits-all download from apps.odoo.com. It is a scoped engagement: we start from your BOM depth, your costing method (standard vs. average vs. FIFO), your Community or Enterprise edition, and your Odoo version (17, 18, or 19), then deliver a module tailored to those realities. Under the hood it is clean, upgrade-safe Odoo — new models extending mrp.bom and product.template, computed fields driven by @api.depends, ir.model.access.csv plus record rules for security, OWL/QWeb views for the tree and simulator, and a printable QWeb cost report. Typical delivery is 2 to 4 weeks depending on scope.
你得到什么
- Complete, installable Odoo module (source code) packaged for your target version — 17.0, 18.0, or 19.0 — with a clean __manifest__.py and dependency declaration on mrp
- Installation and configuration on your environment (or a staging database first), including security-group setup and menu placement inside the Manufacturing app
- Configuration tuned to your costing method (standard/average/FIFO) and your Community vs. Enterprise edition
- Technical documentation covering the data model, computed fields, wizards, and how the roll-up and where-used algorithms work
- End-user guide and a live training session for your engineering and costing teams on the tree, where-used lookup, simulation, and mass-replace wizard
- Post-go-live support window (bug fixes and adjustments) for a defined period after handover, with a clear escalation path
- UAT sign-off on a staging copy of your database before anything touches production, plus a documented rollback plan
- Source ownership and a git repository handover so your team can maintain or extend the module later
这是给谁的
Costing & Cost Accountant
Owns product standard costs and margin accuracy. Needs a trustworthy rolled-up cost across every BOM level and wants to simulate the margin impact of supplier price changes before they land in the ledger.
Manufacturing / Product Engineer
Maintains BOMs and drives engineering change orders. Needs to see the full indented structure at a glance and to replace a superseded component across dozens of BOMs without hand-editing each one.
Supply Chain & Procurement Analyst
Assesses the blast radius of a component shortage, price hike, or supplier switch. Relies on where-used lookup to know exactly which finished goods and customer orders a single part affects.
Operations / Plant Manager
Wants a defensible, auditable view of product cost build-up and change impact for pricing, tenders, and continuous-improvement decisions, exported cleanly for review meetings.
安装概述
从ECOSIRE下载
在 ecosire.com 上购买许可证并从您的帐户仪表板下载 Multi-Level BOM & Where-Used Explorer 模块 ZIP。
上传至Odoo
将 ZIP 解压到服务器上的 Odoo 自定义插件文件夹中（或通过“应用程序”>“从 Odoo.sh / runbot 上的文件安装”上传）。
安装模块
激活开发者模式，打开应用程序，单击更新应用程序列表，搜索 Multi-Level BOM & Where-Used Explorer，然后按安装。
配置设置
打开新菜单，粘贴您的 ECOSIRE 许可证密钥，连接任何外部凭据（Shopify、Amazon、Stripe 等），然后保存。
验证并上线
运行内置连接测试，同步前 10 条记录，并安排定期 cron。如果出现任何问题，请联系支持人员。
Multi-Level BOM & Where-Used Explorer 如何比较
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| Multi-level indented BOM tree in one view | Full recursive tree down to raw materials, collapsible per node | Possible but you build and maintain the recursion yourself | Varies; many show limited depth or a flat popup | |
| Cost roll-up across all BOM levels | Automatic bottom-up roll-up via @api.depends computed fields | Hand-coded aggregation, prone to depth/UoM bugs | Some offer it; accuracy and UoM handling vary | |
| Where-used (reverse BOM) lookup | One-click direct and indirect parent lookup for any component | Requires custom reverse-traversal code and a UI | Rare; usually a paid add-on if present | |
| Mass component replace across BOMs | Guided preview-and-confirm wizard, security-gated | Manual script or per-BOM edits, no safe preview | Occasionally offered without a preview/rollback step | |
| Cost simulation on price changes | Simulate hypothetical costs and see rolled-up impact before committing | Would need a bespoke simulation model | Seldom included | |
| Fit to your Odoo version, edition & costing method | Built for your exact 17/18/19, Community/Enterprise, and costing method | Fully custom but at full in-house build cost and time | Generic; may not match your version or costing method | |
| Support, source ownership & rollback plan | Support window, git handover, staging UAT, documented rollback | Depends entirely on internal team availability | Vendor support varies; source often obfuscated |
关于Multi-Level BOM & Where-Used Explorer的常见问题
+How long until the module is delivered and installed?
This is a build-to-order module, not an instant download. Typical delivery is 2 to 4 weeks from a confirmed scope, depending on your BOM depth, costing method, and any custom requirements. We begin with a short scoping call, build on your target Odoo version, deliver to a staging database for UAT, and only then install on production. If you have an urgent deadline, tell us up front and we will confirm whether an accelerated timeline is feasible.
+What support and updates do I get after delivery?
Every engagement includes a post-go-live support window for bug fixes and adjustments after handover, with a defined escalation path. You also receive the full source and a git repository, so your team can maintain the module independently. For Odoo major-version upgrades (for example 18 to 19) or new feature requests beyond the original scope, we offer a separate maintenance/upgrade agreement — we will scope and quote that when you need it.
+Which Odoo versions and editions does this work with?
We build for Odoo 17.0, 18.0, and 19.0, on both Community and Enterprise. The module depends on the standard Manufacturing (mrp) app, which exists in Community, so Enterprise is not required. We confirm your exact version and edition during scoping and package the module accordingly so it installs cleanly and stays upgrade-safe.
+Will this conflict with our existing MRP setup or other custom modules?
No. The module extends standard models (mrp.bom, product.template) with new computed fields and dedicated wizards rather than overriding core behavior, so your existing manufacturing, inventory, and costing flows keep working. We install to a staging copy of your database first, run UAT against your real BOMs, and check for interactions with any custom modules before touching production. A documented rollback plan is part of every delivery.
+How does the cost roll-up and where-used lookup actually work under the hood?
The roll-up walks each BOM recursively, multiplying quantities and applying unit-of-measure conversions at every level, then aggregates component, operation, and sub-assembly cost bottom-up using computed fields declared with @api.depends so totals recalculate automatically when inputs change. The where-used lookup is the inverse traversal: it indexes every BOM line referencing a component and returns the direct and indirect parents. Both respect company-specific costs and active BOM/variant selection.
+Can external systems read the BOM tree and rolled-up costs?
Yes. On request we expose the where-used graph and rolled-up cost through Odoo's standard XML-RPC/JSON-RPC API, so your PLM, BI, or external ERP can pull the data programmatically. Access is governed by the same security groups and record rules as the in-app views, so external calls only return what the calling user is permitted to see.
为什么客户信任 ECOSIRE
SOC 2 对齐
符合 GDPR
安全条纹支付
30 天退款
终身更新
LGPL-3.0 许可证
相关模块
申请报价
Multi-Level BOM & Where-Used Explorer
Visual multi-level BOM tree with cost roll-up, where-used reverse lookup, and mass component replacement for Odoo 17/18/19.
- Indented multi-level BOM tree view that recursively expands every sub-assembly and phantom (kit) BOM down to raw-material leaves in one collapsible OWL widget
- Roll-up cost aggregation across all BOM levels, summing component cost, operation cost, and sub-assembly cost bottom-up so the top-level total is always reconciled
- Where-used (reverse BOM) lookup: pick any component and instantly list every parent BOM and finished product it feeds into, at direct and indirect levels
- Mass component replace wizard that swaps one product for another across every BOM line it appears in, with a preview-and-confirm step before writing changes