What flows back, and why it is read-only
Engineers make decisions that cost money, and the numbers live somewhere else. Reading them back is easy; the discipline is rendering them so nobody edits a value the next sync will replace.
Field map — object by object
| Manufacturing PLM object | Lands as | Master | Direction | On conflict |
|---|---|---|---|---|
| Standard cost | Item cost / valuation | ERP | ERP → Manufacturing PLM | Display only — Manufacturing PLM never writes a cost |
| On-hand & committed | Inventory records | ERP | ERP → Manufacturing PLM | Cached with an as-of stamp |
| Open purchase orders | PO lines | ERP | ERP → Manufacturing PLM | Read as impact-analysis context only |
| Lead time | Item planning fields | ERP | ERP → Manufacturing PLM | Display only |
| Supplier record | Vendor master | ERP | ERP → Manufacturing PLM | Manufacturing PLM adds AML approval state only |
What it is, and what it is not
The inbound half of the connector: cost, inventory, open demand, lead time and supplier records read back from your ERP so engineering decisions can be made with the operational consequence visible.
It is not a copy of your ERP. Only the fields in the published map cross, they cross on a schedule you set, and every one of them renders as owned by the system it came from.
It is also not a costing capability. Manufacturing PLM sums your ERP's figures over a resolved structure; it does not calculate standard cost, allocate overhead or model labour rates. Those are accounting operations built on transactions Manufacturing PLM never sees.
The mechanism: read-only is a rendering decision
The technically easy part is fetching the values. The part that decides whether the integration is trusted is what the interface does with them.
Fields the matrix marks as ERP-mastered render greyed, labelled with the owning system, and are not editable by anyone — including an administrator. There is no permission that unlocks them, because the next sync would replace whatever was typed and the person who typed it would be right to conclude the system is broken.
Every value carries an as-of stamp, because it is a cached read rather than a live query. An unstamped number implies currency it does not have, and the difference matters most in exactly the decisions people want to automate: a cost figure eleven months old is not wrong, it is stale, and only the stamp distinguishes the two.
Where a connector supports events, updates stream rather than polling. Where it does not, the schedule is yours and the staleness is visible rather than assumed.
The failure it prevents
An engineer opens a BOM, sees a cost column, and corrects a figure that is obviously wrong for a component they buy regularly. It takes ten seconds and feels like housekeeping.
The nightly sync replaces it. Next week they correct it again. The third time, they conclude the system does not save their work and stop using the cost column — and, more damagingly, tell colleagues the tool is unreliable, which is a reasonable inference from what they observed.
Nothing failed. The value was never theirs to edit, and the interface should have said so before they typed. Rendering ownership is not a cosmetic decision; it is what stops a correct system from looking broken.
How it meets the rest of the product
Rollups sum ERP figures over resolved structures, so a cost total is arithmetic over your numbers against Manufacturing PLM's configuration — which is why it matches what procurement sees rather than being a second, divergent cost model in a spreadsheet.
Impact analysis is where this earns most of its value. An affected part with sixteen weeks of stock and two purchase orders in flight is a different proposition from one that never left engineering, and a reviewer approving a change sees both facts on the same screen.
Search covers the cached fields, so “fasteners with more than twelve weeks lead time used in shipping products” is a query rather than an export and a spreadsheet. The values carry their source and stamp in results as they do everywhere else.
Agents cite ERP values differently from things Manufacturing PLM owns — source system and as-of stamp attached — because a cached read of somebody else's master record is weaker evidence than a resolution Manufacturing PLM can reproduce byte for byte.
How it meets your ERP
Reads are targeted queries rather than full extracts. A nightly sweep of an entire item master is how integrations end up throttled during month-end close, and it produces staleness that is uniform rather than proportional to what people actually look at.
Nothing is written back through this path at all. It is a read connection by construction rather than by configuration, which means there is no setting somebody can get wrong and no permission escalation that turns it into a write.
The supplier record is the one field group where both systems have something to say. Your ERP owns the commercial relationship — terms, pricing, the vendor part number a buyer transacts against. Manufacturing PLM owns which manufacturer parts engineering has approved and qualified. Those are two different questions, and a single supplier field has never answered both.
Where the boundary is
Manufacturing PLM does not become a reporting layer over your ERP. Cost and inventory appear where an engineering decision needs them — on a BOM, in an impact set, in a rollup — and not as dashboards competing with the ones your finance and operations teams already have.
It also cannot show what the connector does not expose. Tooling amortisation, freight, duty and yield loss are frequently the gap between unit cost and landed cost, and where they sit outside the field map the interface reports the boundary rather than quietly understating a total.
Facts
| Reads | Cost · on-hand & committed · open orders · lead time · supplier |
| Rendering | Greyed, labelled with the owner, not editable by anyone |
| Every value | Carries an as-of stamp — it is a cached read |
| Transport | Events where supported, targeted queries otherwise |
| Writes | None — a read connection by construction |
| Used by | Rollups · impact analysis · search · agent citations |
| Supplier split | ERP owns the relationship; Manufacturing PLM owns the AML |
| Not offered | Costing calculation · dashboards · landed cost |
Frequently asked
Why can nobody edit a cost in Manufacturing PLM?
Because the next sync would replace it, and the person who typed it would reasonably conclude the system is broken. Fields the matrix marks ERP-mastered render greyed and labelled with their owner, with no permission that unlocks them — including for administrators.
How current are the numbers?
As current as the last read, and every value carries an as-of stamp saying so. An unstamped figure implies currency it does not have, and a cost eleven months old is not wrong — it is stale, and only the stamp lets a reader tell those apart.
Does Manufacturing PLM ever write back through this?
No. It is a read connection by construction rather than by configuration, so there is no setting to get wrong and no permission escalation that turns it into a write. Outbound publication is an entirely separate path with its own trigger and rules.
Do you pull our whole item master every night?
No. Reads are targeted queries, because a nightly sweep of an entire item master is how integrations end up throttled during a month-end close. It also produces uniform staleness across everything, rather than staleness proportional to what people are actually looking at.
Who owns the supplier record?
Your ERP owns the commercial relationship — terms, pricing, and the vendor part number a buyer actually transacts against. Manufacturing PLM owns which manufacturer parts engineering has approved and qualified for a given internal part. Two different questions that one supplier field has never answered well.
Will this replace our operations dashboards?
No, and it should not try. Cost and inventory appear where an engineering decision needs them — on a BOM, in an impact set, in a rollup — rather than as reporting competing with what finance and operations already run on their own data.
What about freight, duty and tooling cost?
Only where your connector exposes them. Those are frequently the gap between unit cost and landed cost, and where they sit outside the field map the interface reports the boundary rather than quietly understating a total somebody is about to act on.