Production schedule recovery records retention timeline: what disappears first when a scheduling tool is replaced

Short answer

Before a scheduling tool or MES is replaced, inventory each record class behind a recovery: what it is, the years it covers, who owns the system, and the real date access changes. The order matters, because records disappear at different times. On-screen alerts and availability logs often vanish immediately, chat and leavers' mailboxes go under retention rules, scenario runs go when the old license ends, and downtime history goes when the old database is switched off. Closed ERP orders usually survive longest, often in an archive.

Visual briefFull-size diagram
A horizontal timeline from today to month 18 with six record types; availability check logs fade at once, chat at month 3, scenario runs at the old license end in month 9, leaver mailboxes at month 12 and MES downtime at decommission in month 18, while closed orders stay as archived and retrievable.
Illustrative timeline for a fictional plant. Real dates come from the company's own contracts and retention policy.

This retention timeline is part of the guide on production schedule change logs. The system map shows where each record sits; this page shows when each one is at risk.

The timeline: what disappears first

Illustrative timeline, invented for this page. A 450-person maker of agricultural implements signs for a new advanced planning and scheduling tool. Go-live is in month 6, the old tool's license ends in month 9 and the old MES database is decommissioned in month 18. Every date below is fictional; real ones come from the company's own contracts and policies.

WhenRecord typeWhat happens to itWhy at that point
Already goneAvailability check logsNot stored after the planner leaves the orderSystem behavior, not policy
Month 3Planner chat messagesDeleted under a 90-day chat retention ruleCompany retention setting
Month 9Scenario runs and sequence history in the old toolUnreadable when the license endsVendor contract
Month 12Mailboxes of planners who leftPurged a year after departureCompany retention setting
Month 18MES downtime and piece-count historyLost when the old database is switched offIT decommission plan
RetainedClosed production orders and confirmationsArchived and retrievableERP archiving process

The first row is the surprise for most people. SAP documents that a failed availability check sets a missing part status in the order header, but the availability log itself is not kept after the user exits the order; the missing parts overview shows only the last check, and a check at release is written to the release log. So in plants that work this way, the moment an alert was raised was never kept at all, and only the status and the release log survive.

How each record class tends to be kept

Retention varies by company, contract and law, so there are no standard periods to quote. What tends to be true is the mechanism, which a partner can ask about.

Record classWhat usually governs how long it lastsWho can sayQuestion to ask
Shortage statuses and release logsERP configuration and archivingERP administratorAre release logs archived with the order?
Rescheduled dates and scenario runsThe old tool's license and any migration scopePlanning manager, vendor contract ownerDoes history migrate, or only open orders?
Downtime and fault eventsThe MES database's decommission planManufacturing systems leadWill the old database stay read-only, and until when?
Maintenance work ordersMaintenance system retentionMaintenance managerIs the maintenance system changing too?
Confirmations with yield and scrapERP archiving residence timesPlant controllerCan archived orders be retrieved after cutover?
Reasons in email and chatCompany retention policyIT, under policy set by legalWhat happens to leavers' mailboxes?

SAP documents that production orders are archived in stages: a deletion flag, then a deletion indicator after a residence time, then an archiving run that removes them from the database, with a retrieval function to display them later. That is why closed orders tend to outlast everything else on the timeline. ISA-95 Part 4 defines object models for exchanging scheduling, performance and work-record data between systems, but it does not decide whether closed history moves to a new tool; that is a separate decision in the migration scope.

Six dates to pin down before the cutover

Ask for each date in writing. If a date is not documented, write "unknown"; there is then no deadline to mention.

  1. Contract signature for the new tool. Starts the clock.
  2. Migration scope sign-off. Decides whether closed orders and history move.
  3. Go-live. After this, the old tool is rarely updated.
  4. Old license end. Scenario runs and sequence history become unreadable.
  5. Old database decommission. MES downtime history goes unless retained.
  6. Next retention purge. Chat and leavers' mailboxes, under the company's policy.

Who must approve keeping anything

Keeping records beyond their normal life is a company decision, not a partner's or a consultant's. It needs someone with authority over the records, acting within the company's retention policy, customer agreements and applicable law.

DecisionWho usually approvesWho advises
Extend the old license read-onlyCFO or COOPlanning manager, IT
Keep the old MES database read-onlyCIO or IT directorManufacturing systems lead
Include closed history in the migrationProject sponsor, often the COOIntegrator, planning manager
Change mailbox or chat retentionLegal and IT under company policyCompliance
Discuss licensing any of the recordsCEO, COO or CFOPlant operations director

The last row is separate from the others. Preserving records for operations does not mean the company has agreed to discuss licensing them; see who can license these records.

What a partner notes, and what it never does

A partner notes record classes, years covered, system owners, the documented dates above and who sponsors the conversation. A partner never recommends keeping data the company has not authorized, never copies or handles records, and never presents a retention date as urgency unless it is documented. What stays unknown until SourceX reviews it: rights in customer designs inside orders, employee data in email, SourceX's current data needs and any offer. The introduced company 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.

The manufacturing screening worksheet covers the size and history checks that come first. If the system change is part of a closure, the plant closure page covers the different timeline, and lean manufacturing consultants explains how improvement advisors often see these projects first.

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 plant facing a scheduling or MES replacement can document its access dates and name who owns each record class, register as a partner, confirm the company against who qualifies, and read the program terms before introducing its decision-maker.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Should a partner tell the company to export its old scheduling data?

No. A partner can point out a documented access date. Whether to keep, archive or copy anything is the company's decision under its own retention policy and customer agreements.

What if nobody knows when the old license ends?

Then there is no deadline to mention. Note it as unknown and ask who holds the vendor contract.

Do archived ERP orders still count as history?

Often yes, if they can be retrieved with their dates and quantities. Ask whether the archive can be read after the cutover and who controls it.

Sources

  1. help.sap.com/docs/PRODUCT_ID/34de0103497c4b80a7c7fbf6952f…
  2. help.sap.com/saphelp_46C/helpdata/EN/b1/c04f06439a11d1894…
  3. isa.org/products/ansi-isa-95-00-04-2018-enterprise-c…
  4. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment