Key Points
- SAP master data archiving only succeeds after every order, invoice and stock record that references a material, customer or vendor is archived first.
- Material masters use MM_MATNR, vendors use FI_ACCPAYB and customers use FI_ACCRECV, while S/4HANA adds CA_BUPA, which runs after both partner objects.
- Archiving obsolete customers and vendors before an S/4HANA conversion keeps them from becoming business partners that someone then has to map and govern.
- SAP ILM blocks personal data in customer, vendor and business partner records once its purpose ends, then destroys it after the retention period expires.
- A master record should be retained as long as the longest-lived invoice, contract or ledger entry that references it, because retention follows the transactions.
- Archiving SAP master data in Archon keeps vendors, customers and materials in the same archive as their invoices, readable without an SAP license.
A global chemicals company finished rolling out SAP HANA across every country it operates in. That left more than 11 legacy ERP systems to retire. They ranged from SAP ECC 6 to Oracle E-Business Suite, Microsoft Dynamics, Great Plains and Navision. The business still needed every year of their history.
Each archived invoice in those systems carries a vendor number. Each sales order carries a customer number and a material number. Without the master records behind them, those numbers are just digits.
That is the job of SAP master data archiving, and SAP makes it harder by design. A material, customer or vendor can only be archived after every document that references it is gone. Master data is the last thing to leave the database. It is also the one thing the archive cannot afford to lose.
The window to get this right is closing. Mainstream maintenance for SAP ECC ends in 2027, with optional extended maintenance to 2030. Meanwhile, 59% of companies are already fully or partially live on SAP S/4HANA. Every customer and vendor carried into S/4HANA becomes a business partner, whether anyone has used it in a decade or not.
Getting it right comes down to four decisions:
- Which archiving object handles each type of master record
- What order the records leave in
- Which records to archive and which to block under SAP ILM
- Where the archive lives once SAP is switched off
What Is SAP Master Data Archiving?
SAP master data archiving moves flagged master records out of the live database and into archive files. Materials, customers, vendors, and business partners are the usual candidates. The records stay available for audits and reporting, but they no longer sit in production tables.
Master data describes the things a business deals with: what it buys and sells, who it buys from and who it sells to. Transactional data records what happened to them: purchase orders, invoices, deliveries and postings.
Transactions point to master records. Master records never point back. That one-way link is why the order of archiving matters so much.
It also explains why archiving is only one of three ways a master record can leave active use:
| Lifecycle Action | Archive | Block | Destroy |
|---|---|---|---|
| What happens | The record moves from database tables into an archive file | The record stays in the database, but normal users can no longer see or use it | The record is permanently removed |
| Typical trigger | Residence time has passed and no open documents reference it | Its business purpose has ended, but a legal retention period still applies | The retention period has expired and no legal hold applies |
| Main SAP tool | Archive Administration (SARA) with an archiving object, such as MM_MATNR | SAP ILM, after an end of purpose check | SAP ILM data destruction |
| Who can still read it | Users with archive access, through the SAP Archive Information System or an external archive | Only users with special authorization | No one |
Master data is one slice of SAP archiving as a whole, which also covers transactional data, documents, and attachments. It is the slice that decides whether the rest of the archive can be read.
Why Obsolete Records Should Leave Before S/4HANA
Master records are small next to transactional data. Storage savings alone rarely justify archiving them. The case rests on what dormant records do to an S/4HANA move, to data quality and to privacy obligations.
The conversion is the clearest example. In an ERP to S/4HANA conversion, all customer and vendor master records have to be converted to business partners. A vendor nobody has paid in ten years gets the same treatment as the largest supplier.
Teams that archive dormant customers and vendors first never have to convert, map or govern them. It also shortens the work of deduplicating customers and vendors before CVI mapping, the customer-vendor integration step that creates the business partners.
The benefits of SAP master data archiving show up in six places:
| Benefit | What Changes | Who Notices |
|---|---|---|
| Cleaner S/4HANA migration | Fewer customers and vendors to convert into business partners, map and validate | S/4HANA program team |
| Data quality | Fewer dead and duplicate records in searches, value helps and reports | Procurement, sales and master data owners |
| Data volume management | Master data closes out a chain that moves its transactions out first, and the transactions are where teams reduce SAP database size | Basis team, finance |
| System performance | Mass runs and searches work through fewer records | Business users and batch operations |
| Privacy compliance | Personal data in customer, vendor and contact records stops sitting in production indefinitely | Data protection officer |
| Decommissioning readiness | Archived transactions keep the master records they reference | Audit, legal and IT leadership |
Expect system performance optimization from master data alone to be modest. The larger gains come from the transactions archived ahead of it. That is why master data belongs inside archiving before an S/4HANA move, not after it.
Privacy adds pressure of its own. GDPR’s storage limitation principle allows personal data to be kept only as long as its purpose requires. Customer, vendor and contact person records often hold names, addresses and bank details.
The migration path decides how much of this travels. A brownfield conversion carries existing data into S/4HANA. A selective data transition lets teams choose which history moves. Either way, someone has to decide which master records go with it. That decision depends on how SAP releases a master record in the first place.
How Master Data Archiving Works in SAP, Step by Step
The SAP master data archiving process follows the same write, store and delete pattern as any SAP archiving object. The difference sits at the front. Dependency checks decide whether a record can leave at all.
- Identify obsolete master data. Look for materials with no stock and no open documents, and for customers and vendors with no recent postings. When flagging materials, SAP can propose a list of materials without stock.
- Archive the dependent documents first. Purchasing documents, sales documents, material documents, FI documents and transaction figures that reference the record must leave before it can.
- Set the deletion flag. Use MM06 for materials, XK06 for vendors and XD06 for customers. In S/4HANA, flags for customers and suppliers are set on their roles in transaction BP. Flagging a material also creates a change document, so the deletion request leaves a trail.
- Run the write job in SARA. Archive Administration runs the archiving object’s write program, which checks each flagged record before writing it to an archive file. For material masters, the write program is MMREO050N.
- Store the archive files. The files move to a content repository, such as SAP Content Server, certified storage or Archon. Storing before deleting means no record leaves the database until its file is safe.
- Run the delete job. The delete program removes the archived records from tables such as MARA, LFA1 and KNA1.
- Make archived records findable. The SAP Archive Information System, transaction SARI, searches archived data through infostructures. Customer masters use SAP’s standard field catalogs SAP_FI_ACCREC_1 or SAP_FI_ACCREC_2, and business partners need the CA_BUPA_ALL infostructure activated.
SARA and SARI are the two SAP archiving transactions most master data teams use. The archive files they manage are ADK files that are read back through SAP. That dependency on a running SAP system turns into a problem the day the system is retired.
Each type of master record runs through its own archiving object, with its own prerequisites.
SAP Archiving Objects for Material, Vendor and Customer Masters
SAP groups the tables that make up one business object into an archiving object. These SAP archiving objects cover master data in SAP ERP and S/4HANA:
| Archiving Object | Master Data | Main Tables | Notes |
|---|---|---|---|
| MM_MATNR | Material master | MARA, MARC, MARD | Needs a deletion flag. Write program MMREO050N. |
| FI_ACCPAYB | Vendor master | LFA1, LFB1, LFM1 | Three write runs: purchasing, company code and general data |
| FI_ACCRECV | Customer master | KNA1, KNB1, KNVV | Three write runs: sales, company code and general data |
| CA_BUPA | Business partner | BUT000 and related tables | Archives whole records only. Runs last in S/4HANA. |
| FI_ACCKNVK | Contact persons | KNVK | Covered by SAP ILM blocking for personal data |
| MM_EINA | Purchasing info records | EINA, EINE | Can be displayed after archiving, but not reloaded |
| MM_ASMD | Service master records | ASMD | Can be displayed after archiving, but not reloaded |
| FI_TF_CRE, FI_TF_DEB | Vendor and customer transaction figures | LFC1, KNC1 | Clear these before the vendor and customer masters |
Table lists vary by release, so transaction DB15 is the final word for any given system.
Material Master Data in SAP MM
To archive material master data in SAP, start with the documents. Purchasing documents that refer to a material must be archived before the material can go. The same logic applies to other documents that use it, such as material documents in MM_MATBEL, which also covers the MATDOC table in S/4HANA.
Then flag the material in MM06. A client-level flag removes the whole record. A plant-level flag removes plant data and anything below it, such as storage locations, but leaves the client-level record in place.
SAP MM master data archiving reaches beyond materials. Purchasing info records (MM_EINA) and service master records (MM_ASMD) have their own objects, and both can be displayed after archiving but not reloaded. Source lists and quota arrangements cannot be archived at all. They can only be deleted.
Vendor Master Data
Archiving vendor master data in SAP runs through FI_ACCPAYB. The object needs three write runs, one for each layer of the record. They cover purchasing organization data (LFM1), company code data (LFB1) and general data (LFA1).
Before any of them succeeds, the vendor’s purchasing documents, FI documents and transaction figures (FI_TF_CRE) need to be archived. Deletion flags must also be set at each level being removed. In SAP ECC, transaction XK06 sets them.
In practice, many teams use FI_ACCPAYB mainly for vendors created by mistake. A vendor with years of postings has so many dependencies that clearing them takes a full archiving program, not a cleanup task. In S/4HANA, every vendor is a supplier role on a business partner, so FI_ACCPAYB runs before CA_BUPA.
Customer Master Data and Other Objects
Customer master data follows the same pattern through FI_ACCRECV. Its three write runs cover sales data (KNVV), company code data (KNB1) and general data (KNA1). The object spans both accounts receivable and sales, and it has a reload program for emergencies. Contact persons have their own object, FI_ACCKNVK.
SAP TM master data archiving has its own home. SAP Transportation Management documents it in a section titled “Archiving for Master Data Objects.” That section sits beside separate archiving and ILM objects for TM business documents, such as freight settlement documents. The general SAP rule holds there too: master data waits until the documents that use it are archived.
Knowing the object for each record is the easy part. The order in which those objects run is where most projects lose time.
Why Master Data Always Goes Last
SAP enforces a sequence. An archiving object cannot run while its preceding objects still have data in the database. In financial accounting, SAP documents the order directly, and it runs in three stages:
- Documents and transaction figures
- Customer and vendor master data
- Bank master data
Materials follow the same principle. Purchasing documents and other records that use a material go before the material master does.
The network graphic in SARA shows which objects precede the one you want to run. SAP describes it as an orientation aid, not a complete map of every dependency, so test runs still matter.
S/4HANA adds a second sequence. Every customer, vendor and contact person is also a business partner. SAP’s documented order runs FI_ACCPAYB, then FI_ACCRECV, then CA_BUPA. An SAP guide to this scenario puts it plainly: “The order of archiving objects is critical.”
Inside a running system, SAP enforces all of this. Nothing enforces it once the system is gone. An archive that holds invoices but not the vendor records behind them passes every technical check. It still fails the first question an auditor asks: who was paid?
Business Partner Archiving and SAP ILM in S/4HANA
S/4HANA changes master data archiving in two ways. The business partner becomes the central record, and SAP ILM sets the rules for personal data.
Business partner archiving runs through CA_BUPA. Three rules shape it:
- Flag first. A business partner must be flagged for archiving before the write run picks it up.
- Whole records only. SAP archives and deletes business partner data as a complete record. Partial archiving is not possible.
- Roles first. The vendor and customer objects run before CA_BUPA.
In SAP S/4HANA Cloud, the archiving variant also needs General Data selected. Without it, the job stops with the error “Select at least one data area.”
Information lifecycle management adds a second path for records that hold personal data. SAP’s rule is direct. Personal data whose original purpose has ended is deleted, unless another retention period applies. If one does, the data is blocked until it can be deleted.
Four points on that timeline decide what happens to a customer, vendor or business partner record:
- End of business. The last activity on the record, such as a final invoice or payment.
- Residence period. A grace period before the record is treated as finished.
- End of purpose. SAP’s end of purpose check confirms the business purpose is over. The record is then blocked: it stays in the system, but only users with special authorization can see it.
- End of retention. Once the legal retention period runs out, a data destruction run removes the record, unless a legal hold is in place.
Business partners follow one extra rule. A business partner is blocked once all its business purposes are complete. It is destroyed only after every document that references it has been destroyed. In S/4HANA, customers and vendors are destroyed before the business partner, the reverse of the ERP order.
SAP ILM reaches master data through the same objects used for archiving: FI_ACCRECV, FI_ACCPAYB, CA_BUPA and FI_ACCKNVK. Destruction under ILM is also the starting point for defensible deletion, where every removal traces back to a rule and an approval.
The business partner shift is one of several differences between SAP ECC and S/4HANA that change how archiving is planned:
| Topic | SAP ECC | SAP S/4HANA |
|---|---|---|
| Customer and vendor records | Separate customer and vendor masters | Every customer, vendor and contact person is also a business partner |
| Where deletion flags are set | XD06, XK06 and MM06 | Customer and supplier roles in transaction BP; MM06 for materials |
| Archiving order for partners | FI_ACCPAYB and FI_ACCRECV | FI_ACCPAYB, then FI_ACCRECV, then CA_BUPA |
| Destruction order under SAP ILM | The reverse of the S/4HANA order | Customers and vendors before the business partner |
| Material documents | MM_MATBEL covers MKPF and MSEG | MM_MATBEL also covers MATDOC |
| Batches and special stock | MM_SPSTOCK | MM_SPSTOCK is obsolete |
Blocking and destruction both depend on one number: how long the record must be kept.
How Long SAP Master Data Must Be Retained
Master data retention requirements rarely name master data at all. Laws set retention periods for books, invoices, tax records and contracts. Master records inherit those periods from the documents that point to them.
SAP ILM follows the same logic, since a business partner is destroyed only after its documents are. A practical rule for SAP master data retention follows from it: keep each master record as long as the longest-lived document that references it.
For SAP historical data retention, the clock usually starts late. German rules, for example, start counting at the end of the calendar year of the last entry. A vendor’s retention period therefore runs from its last invoice, not from the day it was created.
Typical retention periods for the records that point to master data:
| Records That Reference Master Data | Rule | Retention Period |
|---|---|---|
| US records that support tax returns | IRS period of limitations | 3 years in most cases. 7 years for bad debt or worthless securities claims. |
| US employment tax records | IRS | At least 4 years after the tax is due or paid, whichever is later |
| German books and annual financial statements | HGB §257 and AO §147 | 10 years |
| German booking vouchers, such as invoices | Same rules, as shortened from 2025 | 8 years |
| German business letters | Same rules | 6 years |
| Personal data in customer, vendor and contact records (EU) | GDPR storage limitation | No longer than the purpose requires, unless another law requires longer |
Periods can be extended, for example by an ongoing tax audit, and sector rules for banks and insurers can differ. Legal and tax teams should confirm the periods for each country.
These periods belong in written SAP data retention policies that map each master data type to the longest-lived document behind it.
SAP Master Data Archiving Best Practices
A sound SAP archiving strategy treats master data as the final step in a chain, not as a standalone cleanup. Each practice below applies general data archiving best practices to that chain.
- Start from the dependency chain. Archive documents and transaction figures first. Check the network graphic in SARA before any master data run.
- Let the business define “obsolete.” Procurement, sales and finance should agree on the criteria, such as no stock, no postings in a set number of years and no open contracts. Basis then configures what they decide.
- Archive before CVI. Flag and archive redundant customers and suppliers before they are converted to business partners. Archon Analyzer’s reporting on redundant, obsolete and trivial data helps surface them early. Cleaning up afterward means working inside S/4HANA’s stricter model.
- Flag at the right level. A plant-level flag on a material removes plant data only. A client-level flag removes the whole record.
- Separate archiving from blocking. Records created by mistake can be archived and deleted. Records with personal data whose purpose has ended belong in SAP ILM blocking until their retention period ends.
- Activate infostructures before the first productive run. Archived master records that no infostructure indexes are hard to find in SARI.
- Tell connected systems. If SAP Master Data Governance or ALE distributes master data, plan how receiving systems learn that a record was archived.
- Store before you delete, and test first. Run every variant in test mode in a quality system and compare record counts before production.
- Keep masters with their transactions. Archive master data into the same place as the documents that reference it, such as Archon, so neither depends on the system that created them.
Where These Projects Stall
The SAP side of master data archiving is well documented. Most delays come from the gaps around it.
| Challenge | Why It Happens | What to Do |
|---|---|---|
| Records refuse to archive | A document still references the record, or a deletion flag is missing at one level | Archive the dependents, check flags at every level and use the network graphic |
| Duplicates multiply after acquisitions | Each acquired business brings its own vendors, customers and materials | Consolidate and archive duplicates before CVI, and repeat after each deal |
| Connected systems keep stale copies | Archiving a customer or vendor master creates no change pointer, so receiving systems are not informed (SAP KBA 1795412) | Plan downstream updates in SAP Master Data Governance or ALE before the run |
| Archived masters cannot be found | No infostructure indexes the archive files | Create and activate infostructures in SARJ before the first run |
| Custom tables hold master data references | Standard archiving objects cover standard SAP tables only | Inventory Z-tables that store material, vendor or customer numbers, and plan for them |
| The archive loses meaning after retirement | Transactions were archived and the masters left behind, or the archive can only be read through SAP | Archive masters with their transactions into an archive that reads them independently |
Data quality problems surface here first. A global apparel group runs on frequent acquisitions and divestitures, so every deal adds systems and records. A previous vendor’s archive project had failed. Archon rebuilt the program and set up an archival factory, a repeatable pipeline that absorbs future systems without bespoke work. Teams facing the same pattern in SAP mergers and acquisitions need master data rules that survive each new deal.
Custom development adds to the load. An aerospace and aviation group had more than 100 custom objects to assess before it cut its SAP database by 35% and unblocked its S/4HANA migration.
Archiving SAP Master Data in Archon
SAP master data archiving before decommissioning has a different goal from routine housekeeping. Housekeeping aims for a leaner database. Before decommissioning, the aim is an archive that still makes sense once SAP is gone. Either way, archived master data needs a home.
SAP’s own retrieval tools need a running system. SARI and the display transactions read archive files through SAP itself. Once an SAP system decommissioning project switches the system off, archived master data goes dark. So does every archived transaction that depends on it.
Archiving SAP master data in Archon solves both problems. Master records land in the same archive as the invoices, orders and postings that reference them. They stay readable without SAP.
Archon works with SAP’s archiving objects, not around them. On a running system, SAP’s own delete programs still remove the rows, because that is where SAP checks dependencies and keeps the database consistent. Archon is where the archived records go and where people read them.
There are two routes, depending on whether SAP keeps running:
| Route | When It Fits | How Master Data Reaches Archon | What SAP Still Does |
|---|---|---|---|
| Live system | Housekeeping and cleanup before an S/4HANA conversion | Archon Analyzer flags obsolete records. SARA writes them to archive files with MM_MATNR, FI_ACCPAYB, FI_ACCRECV or CA_BUPA and stores the files in Archon. | Runs the dependency checks and the delete job |
| Retirement | The SAP system is being switched off | Archon extracts master data together with the transactions that reference it, straight from the source system. A reconciliation report shows the archive matches the source. | Nothing after cutover. The system can be retired. |
The retirement route also removes the sequencing problem. When the whole system leaves, no live document is left for a master record to wait on, so masters and transactions move together.
That is the requirement the chemicals company faced. Its 11+ legacy ERPs spanned SAP and non-SAP platforms. Archon delivered one centralized archive for all of them, with stronger archive governance and a forward-looking retention and disposition strategy.
Planning SAP data archiving and decommissioning together keeps master data from becoming an afterthought. Once master records are in Archon’s SAP archiving solution, they get:
- No SAP dependency. Archived SAP data, including ADK archive files, stays readable after SAP is switched off, with no SAP license or SAP GUI.
- Familiar screens. Archived records appear in screens that mirror familiar SAP transactions, and Archon ArchiveLink keeps predefined ECC transaction screens available after decommissioning.
- One search. A single search runs across archiving objects and every source system, so an invoice and the vendor behind it turn up together.
- Privacy controls. Pseudonymization at ingestion, plus masking, tokenization and role-based access, protect personal data in customer, vendor and contact records.
- Retention that outlasts SAP. Retention rules and legal holds persist beyond the source system.
Non-SAP systems can sit in the same archive, which matters when legacy ERPs from other vendors retire alongside ECC. For teams moving to cloud-based archiving for SAP, Archon ArchiveLink archives historical SAP ECC data and documents to a scalable, lakehouse-based archive.
Results from full SAP archiving programs:
| Organization | Starting Point | Result |
|---|---|---|
| Aerospace and aviation group | No archiving baseline, 80 GB monthly growth, 100+ custom objects | 35% smaller database, S/4HANA migration unblocked |
| Global apparel and accessories enterprise | Historical data from acquisitions and divestitures across FI and CO, MM, SD and PP | 40% smaller database, $1.3M saved in storage, 65% less audit preparation time |
| Global logistics company | 45+ TB across ECC, BW and SOFFCONT1 | About 37 TB removed, zero data loss |
These results cover entire archiving programs, not master data alone.
Teams comparing SAP ADK with Archon for ECC decommissioning can settle it with one test. Can an auditor open an archived invoice, and the vendor behind it, with SAP switched off? Master data is one workstream inside application decommissioning and retirement, and it decides whether everything else in the archive can be read.
An archived invoice is only as useful as the vendor record behind it. Archive the vendor last, and archive it into the same place as its invoices.