# Engineering change record chain: linking keys | SourceX

Canonical: https://refer.sourcex.si/guides/engineering-change-to-effectivity-record-linkage
Last updated: 2026-11-04

A change can be traced from the customer's request to the valves actually built only if every handoff passes along a reference to the step before it. The request number rides into the change form, the change number rides onto the new drawing revision and its serial cut-in, the same number rides into the manufacturing bill, and each shop order records which bill it was built from. Drop one reference and the chain falls apart into pieces nobody can reassemble with confidence.

This record chain is part of [engineering change order process records](/data-types/engineering-change-order-process), which explains ECRs, ECOs and ECNs. This page follows one change through every link and shows which links snap.

## The chain in seven links

Illustrative case, invented for this page. A 340-person maker of hydraulic control valves logs customer requests in Jira, handles drawing changes in PTC Windchill and builds in its ERP. A tractor customer asks for a spool coating that survives a new biodegradable fluid. Here is how that one request travels.

1. **Request.** REQ-1182 captures the customer's fluid, the failed bench test and the request.
2. **Design review.** A linked task records the choice of coating revision C after salt-spray and wear trials.
3. **Change request.** CR-0457 quotes REQ-1182 in a text box and clears the change review board.
4. **Change notice.** CN-0391 lists the tasks and sets the cut-in at valve serial 24-0815.
5. **Drawing revision.** The spool drawing steps from B to C under CN-0391.
6. **Manufacturing bill.** The valve's bill gets a new valid-from state under ERP change 500211.
7. **Shop order.** Order 5003318 is released and records the bill state it used.

Links 3, 6 and the disposition after link 7 cross a boundary between tools or teams, and that is where references go missing.

## Step, record, key and system

Each row is one record in the chain, including the disposition that closes it. The key column is what the next record must carry for the join to hold.

| Step | Record | Key carried forward | System | How the key gets there |
|---|---|---|---|---|
| 1 | Requirement | Issue key REQ-1182 | Jira | Created by Jira |
| 2 | Design review task | Issue link to REQ-1182 | Jira | Linked by the engineer |
| 3 | Change request | REQ-1182 typed into a field | Windchill | Manual entry |
| 4 | Change notice | CR-0457 and CN-0391 | Windchill | System relationship |
| 5 | Part revision and effectivity | CN-0391 on revision C, serial 24-0815 | Windchill | System relationship |
| 6 | ERP BOM state | ERP change 500211, ideally citing CN-0391 | ERP | Interface message or manual entry |
| 7 | Production order | BOM version stamped at release | ERP | Stamped by the ERP, if configured |
| 8 | Rework or disposition order | CN-0391 cited on the order | ERP and quality | Manual entry |

SAP documents that, in its standard model, a change's effectivity depends on its valid-from date, and that a BOM changed under a change number is stored as a pre-change state ending at that date and a post-change state starting there. If the ERP change number does not cite the Windchill notice, step 6 can only be joined to step 5 by matching dates and part numbers, which is a guess rather than a key.

Links 4 and 5 are the strong middle because PTC documents both inside Windchill: change requests flow to change notices and tasks, and planned effectivities on a change notice become actual when the notice is approved.

## Where the chain usually snaps

Links that cross a system boundary break far more often than links inside one tool. Three are worth asking about at every company.

- **Jira to Windchill (step 2 to 3).** The issue key is often typed by hand into a free-text field, or left out when the change starts from a phone call. A required field for the issue key is the usual repair. Atlassian documents that Jira Cloud exports search results to CSV with all fields, so the requirement side is easy to describe, but only if the key exists on the change side too.
- **Windchill to ERP (step 5 to 6).** Serial effectivity in the PLM has to be translated into a date or serial validity in the ERP. When the interface is down or not built, a planner keys the BOM change days later, and the ERP change number cites nothing.
- **Order to outcome (step 7 to 8).** A rework order raised for units built before the cut-in often names the defect but not the change notice, so the cost of the change cannot be tied back to it.

The pattern is consistent: the closer a key is to manual entry, the more likely it is missing in older records.

## Testing the chain on an order released under the old revision

The hardest case for any chain is a production order that starts under the old revision after the change was approved. In the Illustrative case, CN-0391 is approved on May 6 with effectivity from serial 24-0815, but order 5003318 for serials 24-0790 to 24-0829 is released on May 8 against the old BOM, because ERP change 500211 is not keyed until May 13.

| Question | Link that answers it | Holds in this case? |
|---|---|---|
| Why did the coating change? | Steps 1 to 3 | Yes, if REQ-1182 is on CR-0457 |
| Which serials should have used revision C? | Step 5 | Yes, serial 24-0815 onward |
| Which order built those serials? | Step 7 | Yes, order 5003318 |
| Did the order use revision B or C? | Step 6 to 7 | Only if the BOM version was stamped at release |
| What happened to serials 24-0815 to 24-0829? | Step 8 | Only if the rework order cites CN-0391 |

Fifteen valves fall between the effectivity serial and the end of the order. Whether anyone can say what happened to them depends on two links, not on how complete any single system is. That is why a joined chain says more than the strongest single export; the related page on [missing context](/guides/engineering-change-to-effectivity-missing-context) shows the same contrast from the other side, and the [completeness checklist](/resources/engineering-change-to-effectivity-completeness-checklist) turns these links into checks.

## What a partner notes about the chain

A partner never opens drawings, BOMs or exports. The job is to describe the chain at metadata level and introduce the right person.

- **Which records exist:** tracker, PLM change objects, ERP BOM history, production and rework orders, and years covered.
- **Which keys are carried:** for each of the eight rows above, whether the key is system-generated, typed by hand or absent.
- **Who owns each link:** engineering usually owns steps 1 to 5; the IT integration team owns step 6; production and quality own steps 7 and 8.
- **Who can authorize a licensing discussion:** the CEO (in an owner-run company, usually the owner), not the PLM administrator. Running a system is not authority over its records.
- **What stays unknown until SourceX reviews it:** customer ownership of designs, export-control status, SourceX's current data needs and whether the records fit any proposed use.

The introduced company also needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. For platform projects where links are rebuilt, the [PLM migration consultant guide](/guides/plm-migration-consultant) shows how integrators raise the question, and the [Jira export page](/systems/jira-service-management-export-tickets) covers the tracker side. More system guides are on the [systems hub](/systems).

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If a manufacturer you work with can name the key behind each link from requirement to production order, [register as a partner](/register), confirm the company against [who qualifies](/who-qualifies), and read the [program terms](/terms) before introducing its decision-maker.

## Sources

- https://support.ptc.com/help/windchill/cloud/r12.0.2.0/en/Windchill_Help_Center/CCMOviewChangeMgmtIntro.html
- https://support.ptc.com/help/windchill/cloud/r12.0.2.0/en/Windchill_Help_Center/ChgMgmtEffectivityAbout.html
- https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/18ee18df146f46e9a7738186eebceaa7/5e07c453f57eb44ce10000000a174cb4.html
- https://support.atlassian.com/jira/kb/how-to-export-issues-from-jira-cloud-in-csv-format/
- https://refer.sourcex.si/terms
