PTC Windchill SAP Integration

Connect engineering to SAP without rebuilding the BOM by hand. We integrate Windchill with SAP S/4HANA and ECC so part masters, BOMs, change effectivity and documents flow from release to production — fitted to how your SAP is actually configured, not to how a connector assumes it is.

Talk to a consultant

The problem we solve

Windchill is your engineering system of record. SAP is your manufacturing and cost system of record. Between them sits someone re-keying part masters into MM01, rebuilding BOMs in CS01, and hoping the effectivity date they typed matches the one engineering meant.

That gap is where the cost hides: production running on a superseded revision because the ECO never made it across, MRP trying to buy a phantom assembly because it wasn't flagged, every plant carrying its own version of the BOM, and no clean trace from a shop-floor part back to the engineering change that drove it.

Windchill-to-SAP is the most common PLM–ERP integration in discrete manufacturing. Getting it to hold — through changes, across plants, under audit — is what we do.

Still deciding how SAP compares with Oracle, Dynamics 365 or Infor as the ERP side? Our Windchill ERP integration guide compares all four.

What we actually do

01
Part master and BOM transfer
Windchill release triggers material master creation in SAP and a plant-specific BOM that matches your structure, unit-of-measure and item-category rules — including phantoms flagged correctly so MRP treats them as phantoms.
02
Change effectivity that survives the crossing
Windchill date- and serial-based effectivity mapped to SAP BOM alternates and change master records, so a released ECO changes what production builds on the date engineering intended.
03
MPMLink to SAP routing
If you plan processes in MPMLink, we move the manufacturing BOM and routing into SAP with it, so operations, work centers and standard times aren't re-entered.
04
Document links
Windchill documents referenced from SAP Document Info Records, so the drawing on the floor is the released one.
05
Feedback from SAP
Approved supplier, standard cost and procurement status flowing back into Windchill where engineering can see it.
06
Rescue and re-integration
Already integrated and it's fragile, slow, or quietly wrong? We diagnose the mapping and effectivity logic and rebuild what needs rebuilding — without a full re-implementation.

a very large array of electronic components

How the integration actually works

We don't sell a connector. We fit the integration to your Windchill and your SAP, using whichever approach the configuration warrants:

PTC Windchill ESI / SAP connector — Both systems close to standard. Pre-built part master and BOM mappings, effectivity handling, bi-directional procurement feedback.
Middleware — MuleSoft, Boomi, Azure Integration Services — Complex BOM transformation (eBOM structure ≠ SAP structure), multiple targets, or SAP with Z-tables that need populating.
Custom API — Windchill REST + SAP BAPIs / IDocs — Maximum flexibility for organizations with strong internal development capacity. Highest maintenance burden; we recommend it least often.

Where Windchill–SAP integrations fail

Unit of measure. Windchill says EA, SAP says PC. Unmapped, every part transfer fails.

Plant assignment. SAP BOMs are plant-specific. Multi-plant organizations need routing logic in the integration layer or BOMs land in the wrong plant.

Phantom handling. MPMLink phantoms not flagged as SAP item category P become real inventory items that MRP tries to purchase.

Effectivity conflicts. Windchill date effectivity that doesn't translate cleanly to SAP alternates means production builds the wrong revision.

Large BOM performance. 5,000-plus-line BOMs need asynchronous, delta-change transfer. Synchronous real-time transfers time out.

(Each of these is a design decision, not a defect. We make them before the first part crosses.)

Why Element?

Process and people first, technology second. Integration fails when engineering and manufacturing haven't agreed on what "the BOM" means, which system owns which attribute, and who resolves a failed transfer at 4pm on a Friday. That agreement is the work we lead — the mapping is the easy part.

We've done it 100+ times. Across 100+ successful PLM implementations, the order has never changed, and it's why our integrations keep running instead of becoming the thing everyone routes around.

PTC-certified, A&D-grade. PTC Certified Windchill Implementation Practitioners working in the industries where a wrong BOM revision reaching production isn't a rework cost — it's a compliance event. Aerospace and defense, medical devices, automotive, industrial equipment. Onshore U.S. team, ITAR-compliant delivery.

Who does this work. Senior consultants who have run Windchill–ERP integrations end to end. Our approach is in the Windchill ERP integration guide.

Talk to a consultant

FAQ

Does PTC provide a native Windchill-to-SAP integration?

Yes — Windchill ESI and PTC's SAP connector cover part master and BOM transfer for both ECC and S/4HANA. Most organizations supplement it with custom mappings for company-specific fields. We use it where it fits and build around it where it doesn't.

Do we need a middleware platform?

Not necessarily. If both systems are close to standard, PTC's connector is enough. Middleware earns its place when BOM transformation is complex, when you're integrating more than two systems, or when SAP is heavily customized.

Which system should own the BOM?

Windchill owns the engineering BOM. SAP owns the manufacturing BOM and everything downstream of it — cost, MRP, production. The integration transfers at release events; it doesn't make both systems the source of truth.

How long does it take?

Typically four to nine months depending on BOM complexity, plant count and how much of your SAP is customized. Historical BOM migration is usually the highest-risk element, and we scope it separately.

We tried this before and it broke. Why would this be different?

Almost always because one of the five failure points above was never designed for — most often unit of measure, phantom handling or effectivity. We start by finding which one.

+64%

User adoption improvement in 6-month PLM rescue program for aerospace manufacturer.

-81%

Change order cycle time reduction through automated PLM-ERP integration.

67%

Reduction in manufacturing errors after implementing digital work instructions and change management.

*Results reflect specific project implementations and may vary based on organizational factors and scope.