The part is chosen in the editor. That puts it in your ERP as well.
You settle on a part in the editor, and it appears as an item in your ERP, be it SAP, Odoo or Dynamics: manufacturer, part number, package and procurement data, without anyone keying them in a second time. The released bill of materials follows as a new revision, with its changes, and the approved alternate for a discontinued part lands where your purchasing looks for it: in the item master.
Decided once, keyed in twice
Your engineers pick a part by datasheet, package and availability. Then someone creates the same item in the ERP by hand, with part number, manufacturer and package taken from a list that has already been copied once. Every new BOM revision repeats this, and so does every discontinuation. The result is items that exist twice, BOMs in the ERP that carry an older revision than the layout, and approved alternates that live in an e-mail instead of on the item. Your PLM keeps the design in careful order, but that care does not reach the ERP on its own.
From the editor into the item master
- 1
Pick the part in the editor
You choose the part where you already work, with price, stock and lifecycle status next to it. Manufacturer, part number and package are settled before anyone opens an input form in the ERP.
- 2
Match or create the item
If the part is already in your ERP, it is matched to the existing item instead of being created a second time. If it is not, the item is created from your choice. Old item rows whose descriptions have drifted apart over the years are cleaned as a batch and matched to the actual part.
- 3
Hand over the BOM as a released revision
The BOM goes into the ERP only once you release it, and then as a new revision. What changed against the previous revision comes with it, so your purchasing does not have to lay two lists side by side.
- 4
Approved alternate into the item master
When a part is discontinued and you release an electrically equivalent alternative, it sits on the item in your ERP. Your purchasing then orders what engineering released, not whatever happens to look available.
What you gain
Your ERP stays the system where orders, stock and bookings live. It receives the data that was already right in your engineering, at the moment you release it.
One part, one item
Matching runs on manufacturer and part number, not on how a description happens to be spelled. The same capacitor is therefore not created twice, and your warehouse keeps one stock level per part, not two.
The ERP holds the released revision
The BOM in the ERP is the one you released, with revision and date. Whether purchasing orders against the current layout is visible at a glance instead of being settled in a meeting.
Changes arrive as changes
Between two revisions your purchasing sees which lines were added or removed and where a quantity changed. It orders the difference, not the whole list again.
Approved alternates where orders are placed
A released alternative sits on the item and not in an engineering log. If the original part runs short, the decision has already been made and does not have to be dug up first.
Your PLM stays where it is
Teamcenter or Windchill keep managing your design, your revisions and your releases. PCBoffer sits between that PLM and manufacturing and adds what is missing there: price, availability and lifecycle status per line, and the route of the released revision into your item master.
Odoo in both directions, SAP and Dynamics through the same model
With Odoo, the adapter synchronises items and master data in both directions. SAP and Dynamics attach to the same data model for item, BOM and approved alternate, so your data has the same shape whichever ERP receives it.
- 1
- choice in the editor that your ERP item is created from
- 0
- second entries of part number, manufacturer and package
- 3
- engineering results in the ERP: item, released BOM, approved alternate
- 2
- directions in which the Odoo adapter synchronises items and master data
What belongs next to it
The item master is the end of a chain. These three pages describe what happens before it.
Bills of material for development teams
Resolve every line and see the material cost at your own quantity before the BOM goes into the ERP as a released revision.
Obsolescence in your own design
Lifecycle status per line and electrically equivalent alternatives that you release before they reach the item master.
DFM analysis for development teams
What your layout triggers in a specific factory: the rule violation with limit and location, plus the share a design decision has in the price.
Frequently asked questions
- Does PCBoffer replace our PLM system?
- No. Teamcenter, Windchill or whichever PLM you run keeps managing design, revisions and releases. PCBoffer sits in between: it adds price, availability and lifecycle status per line and brings the released revision into your ERP as items and a BOM. You do not get a second home for your design, you get a route from the design into procurement.
- Which ERP systems are connected?
- SAP, Odoo and Microsoft Dynamics, and further systems through the same data model. With Odoo, the adapter synchronises items and master data in both directions. Because every system attaches to the same model for item, BOM and approved alternate, your data has the same shape whichever ERP receives it.
- What happens to items that are already in our ERP?
- They are matched, not created again. Item rows whose descriptions have drifted apart over the years are cleaned as a batch and matched to the actual part. Afterwards your warehouse keeps one stock level per part, not two.
- Does every change to the BOM go straight into the ERP?
- Only what you release. While you are working on the design, the ERP stays untouched and your purchasing does not order against an unfinished draft. On release, the BOM goes across as a new revision, together with what changed against the previous one.
- How does the approved alternate for a discontinued part get into the ERP?
- Through the same release. The platform proposes electrically equivalent alternatives over the electrical values, the tolerance and the package, and a person decides. What you release then sits on the item as an alternative, and your purchasing finds the decision where it places orders.
See PCBoffer in action: book a demo
30 minutes with founder Dr. Josip Strutz, on your own bill of materials: what PCBoffer calculates from it and where it takes work off your hands.
- 30-minute live session via Google Meet
- Tailored to your parts and your BOM
- No commitment required
Google Meet demo
Google Calendar