SAP S/4HANA Administration · Data Archiving

In the three-step archiving process, why does the write program deliberately NOT delete records, and what guarantees data is safe before deletion?

Answer locked. Get the free KnowCard app to reveal it — plus spaced-repetition review so it actually sticks.

This is one card from the KnowCard library — thousands more across SAP, Linux, Python and more. In the app you get the answer, AI explanations, and cards that come back right before you would forget them. Free to start on iOS, Android or the web.

More in Data Archiving

What is the Archive Development Kit (ADK), and what does it already give you out of the box?

A delete run partially failed and you must re-process what was written. Why can't you act on individual archive files, and what is the unit you address instead?

Users expect an application transaction to transparently show archived data alongside live data. What must be in place, or the archived rows simply won't appear?

ADK offers sequential access and direct access (via an index table) to archived data. When is direct access the wrong default, and why?

You can delete after writing or delete in parallel with writing. Parallel is faster — so when would you deliberately choose delete-after-writing instead?

An archiving session was created without descriptive notes (org unit, document number ranges, fiscal year). What problem surfaces only later, and where can it still be fixed?

Start learning today

Free to start — download the app or use it in your browser.