SAP data archiving readiness: what “ready” actually includes
Ready is not a license
Teams say they are ready to archive when a repository purchase order is approved. That is procurement readiness. It is not archiving readiness.
SAP data archiving readiness is a checklist of people and objects. It says which table-backed business objects will leave the online database, under which rules, with whose sign-off, and how you will prove you can read them back. Buying OpenText Archive Center (or another store) is one line on that list. It is not the list.
Two jobs that get glued together
Many programs stall because they treat two different jobs as one “archive project.”
SAP data archiving (ADK, and ILM where you use it) is about database volume, residence times, and structured business objects. It is table and process work.
Document archiving is about images and files linked through ArchiveLink (or CMIS on S/4HANA Cloud Public Edition), usually into Archive Center or another content store. It is content work.
Both may use OpenText. Both may appear in the same steering committee. They still need separate scopes, owners, and test plans. When they share one vague milestone called “go archive,” nobody knows which risk just moved.
What “ready” actually includes
Write these down before you schedule production runs:
Named archive objects. Not “FI stuff.” Object names your functional owners recognize.
Residence vs retention. How long data stays in the database before archive, and how long the archive must keep it. Those are different clocks.
Legal and tax hold. Who can freeze destruction, and how that is enforced.
Business owner for each object. Sign-off is a name, not a department noun.
ILM / policy if used. If policy management is in scope, say so. If it is not, do not pretend.
Custom tables. Z-tables that quietly became the unofficial archive are clean-core debt. Decide whether they are in scope, redesigned, or explicitly out.
Read-back and test. A successful write with a failed read is a future audit story you do not want.
Volume. Orders of magnitude beat vibes. Approximate is fine. Silence is not.
Store identified. OpenText Archive Center or another agreed repository, with Basis able to operate jobs and connections.
Roles. Basis (jobs, store, technical run), functional (objects, process read-back), records / legal (retention and hold), business owner (sign-off).
Who carries what should be boringly clear. If “the archive team” is three people with no object list, you are not ready.
Clean core and the unofficial archive
A common failure mode is leaving custom Z-tables as the place “we keep everything forever” while calling the program an archiving initiative. That inverts the goal. Archiving should reduce online clutter under policy. It should not invent a second database with worse governance.
Document side: ArchiveLink remains supported for S/4 on-prem and private cloud. CMIS is the path commonly called out for S/4HANA Cloud Public Edition. Do not claim ArchiveLink is dead for on-prem or private. Do not claim you must move to CMIS this quarter. Name the link technology that matches your edition, then test it.
A readiness conversation that fits in one meeting
Bring Basis, one functional lead per major object family, records or legal, and the business owners who will sign. Walk the checklist. Mark gaps. Do not schedule production archive jobs against gaps you politely ignored.
Savings stories can wait until you have measured volume and residence. This article invents none.
Why combined "archive projects" stall
Steering committees like one workstream. Archiving resists that. Data archiving needs functional object experts and Basis batch discipline. Document archiving needs content administration, link technology, and process owners who care about images. Records needs retention language that may not match residence times. When one project manager is told to "deliver archive" without those splits, the first delay looks technical. The real delay is ownership.
A healthier shape:
Data archiving workstream with object backlog and residence rules.
Document archiving / ArchiveLink (or CMIS) workstream with repository operations and retrieval tests.
Records overlay that sets retention and hold rules both streams must respect.
They can share a steering date. They should not share a single undifferentiated RAID log where "archive failed" means everything and nothing.
Custom code deserves a special mention. If posting or reporting still reads large historical tables that should have been archived, fix the consumer or keep the data online on purpose. Silent dependence on "everything forever in the DB" is how archive runs get vetoed the night before.
Read-back tests should include a business user, not only a Basis log. If AP or the functional owner cannot find the archived object the way they will during audit or dispute, the technical job is unfinished.
McCloy Data is a small Charlotte and Waxhaw, North Carolina firm. We implement and optimize OpenText archive and content platforms next to SAP, and we help teams separate data archiving from document archiving before the combined project stalls. If you want a readiness pass that ends with named owners and a real object list, that is a useful Thursday conversation.