SAP AS ABAP Administration · Data Archiving (ADK/SARA)

A write run for a massive object must not spill past the nightly window. How do you make it stop cleanly and resume later without losing what it already wrote?

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 (ADK/SARA)

When configuring the delete step, what is the difference between delete after closing the archive file and delete after transfer to the storage system, and which is safer?

You want CCMS alerting and an access check to apply to every archiving object at once rather than object by object. Which Customizing area sets that, and what does it control?

Reads and access checks against archived data are suddenly very slow once an external storage system is involved. Which two Customizing settings cause the long response times?

Before the first production delete run, how do you prove the delete program selects the right data without actually removing anything, and where is that set?

You need to map the logical name ARCHIVE_DATA_FILE to a physical path. When do you use transaction FILE versus SF01?

A write job dies halfway through a run. What is the correct recovery sequence, and what must you do with the half-written file?

Start learning today

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