SAP data archiving objects: A quick guide to knowing all about it

06 November 2025 | 6 min read | SAP Data Archiving, SAP Data Management

The IT landscape is undergoing a paradigm shift, thanks to digitalisation and the rapid adoption of AI and automation. Consequently, these modern-age growth has led to an exponential increase in data volume, estimating a global data creation of more than 180 zettabytes by the end of 2025. While data growth cannot be stopped or slowed down as such, it can surely be managed accurately with processes like SAP data archiving. In fact, archiving helps ensure legal and regulatory compliance while enabling organisations to achieve their sustainability goals. By archiving historical or inactive data, organisations achieved major benefits like reduced HANA database, enhanced data security, faster disaster recovery and business continuity, and so on. Yielding remarkable results with data archiving is a well anticipated thing. However, have you ever thought about the several behind-the-scenes factors that archiving comprises of?

One such aspect of archiving are the archiving objects, which help moves data no longer needed in the system, but must be retained in an archive file. When archiving, the file is saved in a separate storage location to reduce the load in the database. Additionally, the archived gets deleted from the main database, further reducing the load and optimising the system performance.

In fact, when embarking on an SAP data archiving project, you must take a look at the SAP archiving objects. As defined by SAP, “an archiving object helps accurately specify which data is archived and how. Moreover, it describes database objects that must be handled together as a single business object.”

For archiving an SAP system, there are predefined objects that helps determine the data to be archived. Each of these objects, furthermore, frameworks the related tables, selection criteria, and programs for writing and deleting the archived files. As a matter of fact, understanding these objects is quintessential to managing the lifecycle of data more efficiently. A few standard and commonly used SAP archiving objects are listed below –

  • Purchase orders: MM_EKKO
  • Financial documents: FI_DOCUMNT
  • Sales documents: SD_VBAK
  • For SAP BP archiving: CA_BUPA
  • For SAP IDoc archiving: IDOC

For organisations planning to implement SAP data archiving, you must make the following settings in customising for the category of the data selected for archiving –

  • Customise cross-archiving object
  • Create logical file path
  • Customising specific to archiving objects
  • Activate archive information structures

Moreover, defining the residence time for the SAP archiving objects in customising for the respective category under –

For all data archiving processes, you must assign the required authorisation to the users of the system for programs based on the object S_ARCHIVE.

Necessary enhancements in all the required archiving object can be made to manage the following cases –

  • SAP data archiving and/or deletion of additional database tables
  • If additional checks are needed to meet business requirements
  • If additional condition fields are needed during retention rule evaluation

The preprocessing phase: Data objects are checked by the system to determine if they qualify for archiving.

The write phase: Data that can be archived are moved from the main operational system to archive files.  

The delete phase: The system reads data saved in the archive files and then, deletes their content from the main operational system.

Once the data is completely archived, it is saved in a separate storage location, with defined retention periods.

SAP Information Lifecycle Management or SAP ILM is an SAP solution designed to manage data throughout its entire lifecycle. ILM starts from creation to storage, retention, and eventual deletion, in a way that balances business needs, compliance requirements, and IT efficiency. So, when ILM is activated in the system, a lot of SAP archiving objects can be used in the following ways –

  • Object for data archiving: where the archived data remains available
  • Object for data destruction: where the archived data is destroyed

However, in both the cases, data is processes in two steps –

  • First, data is read from the database, then written in archive files.
  • Second, data is read from archive files, then deleted in the database.

Furthermore, when ILM gets activated in the system, there are three types of archiving objects one can consider –

  • Standard objects for archiving: This one can only archive data.
  • ILM objects: With this object, you can archive and/or destroy data.
  • HR ILM objects: With this object, you can only run data destruction.

Bear in mind that these three types of objects use archiving techniques. Whether the object performs both archiving and destruction or only archiving or destruction is defined by SAP. It may change over time.

Interestingly, there also is a fourth object types, known as the data destruction, which can be used when ILM is activated. With this object, you can process data for which an SAP archiving object does not exist; process data that does not use archive files but directly data from the database in a single step, like a classical housekeeping process. However, unlike housekeeping jobs, the data destruction object needs an ILM customising while a trace of data destruction runs remains logged in the system  

If you look deeper into archiving, you will see there are 100s of archiving objects and a lot more complex process involved. Data archiving is a recurrent manual process requiring a series of jobs that must be reviewed and executed regularly. Manual processes are always tedious and time-consuming, and here’s when automation comes into play.

Moreover, by automating the entire archiving process, organisations can ensure lower total costs of ownership (TCOs), more accurate data compliance in their systems, and so on. Having said that, with S/4HANA migration, cutting down on the cost and migration time by archiving obsolete data becomes a necessity. Having an archiving process backed by automation comes in handy here as it can archive data seamlessly, further, helping achieve a time-effective migration.

Introducing the Archiving Sessions Cockpit (ASC) from TJC Group that serves as a powerful data archiving solution designed to optimise and automate the entire archiving process. Not just that, with ASC, you can also enjoy an automated data destruction process. Developed by TJC Group, certified by SAP, the Archiving Sessions Cockpit gives you full control of your archiving runs from a single, centralised interface while meeting SAP’s standard principles.

From SAP archiving objects to deletion of the archived files, the Archiving Sessions Cockpit streamlines the complete data archiving and ILM lifecycle, removing the need for repetitive manual intervention. Moreover, ASC ensures all SAP ILM processes are executed flawlessly, freeing up your internal teams to focus on more strategic initiatives that drive greater ROI.

By leveraging our automated SAP data archiving software, your organisation can achieve significant savings in database storage costs during S/4HANA migration, keep data growth under control post-migration, and seamlessly enforce privacy policy compliance.

With ASC, you get the following benefits –

  • It can automate mass data archiving, including initial, regular, and selected dates.
  • ASC can schedule archiving sessions in sync with the IT and business calendars.
  • It manages all the jobs and archiving runs from start till its completion.
  • It automatically recovers and restarts the sessions in case of any disruptions.
  • ASC can manage detailed archiving variants, allowing for fine archiving granularity.
  • ASC allows the continuity of end-user access, even if the data is archived.

As the blog concludes, you need to understand that archiving objects are one of the most important factors of data archiving. While financial documents, purchase orders, sales documents, etc., are some of the standard objects; there are several hundred others like production planning, human resources, and so on. That said, there are also technical SAP archiving objects, which you will learn about in our upcoming blogs.

For now, if you are ready to automate your SAP data archiving process, get in touch with us today!


Commonly asked questions

Q1. What are SAP archiving objects and why are they important?

Answer:

SAP archiving objects are predefined components that specify which data is archived and how the archiving process works. They describe database objects that must be handled together as a single business object during the archiving process. These objects provide the necessary provide a structured framework for determining what data can be archived, the related tables, selection criteria, and the programs needed for writing and deleting archived files. Without properly configured archiving objects, organisations cannot effectively manage their data lifecycle or optimise system performance through archiving.

Q2. What are the most commonly used SAP archiving objects?

Answer:

The most commonly used SAP archiving objects include purchase orders (MM_EKKO), financial documents (FI_DOCUMNT), sales documents (SD_VBAK), SAP Business Partner archiving (CA_BUPA), and SAP IDoc archiving (IDOC). These standard objects are frequently used because they represent core business data that tends to accumulate rapidly in SAP systems. Each object is specifically designed to handle related tables and business processes, ensuring that when archiving occurs, data integrity is maintained whilst reducing database size and improving system performance.

Q3. What are the prerequisites for using SAP archiving objects?

Answer:

Before implementing SAP archiving objects, several prerequisites must be met. First, proper customising must be completed, including cross-archiving object configuration, logical file path creation, object-specific customising, and activation of archive information structures. Second, residence time for archiving objects must be defined in the system. Third, appropriate authorisations must be assigned to users based on the S_ARCHIVE object. Finally, any necessary enhancements should be implemented to handle additional database tables, business requirement checks, or condition fields for retention rule evaluation.

Q4. What are the three phases of the SAP data archiving process?

Answer:

The SAP data archiving process consists of three distinct phases. The preprocessing phase involves the system checking data objects to determine if they qualify for archiving based on defined criteria. The write phase moves eligible data from the main operational system to archive files in a separate storage location. Finally, the delete phase involves the system reading data saved in the archive files and then deleting that content from the main operational system. This three-step approach ensures data integrity whilst reducing database size and optimising system performance.

Q5. How do archiving objects work when SAP ILM is activated?

Answer:

When SAP Information Lifecycle Management (ILM) is activated in the system, archiving objects can be used in two ways: for data archiving (where archived data remains available) or for data destruction (where archived data is destroyed). In both cases, data is processed in two steps: first reading from the database and writing to archive files, then reading from archive files and deleting from the database. With ILM activated, there are three types of archiving objects: standard archiving objects (archive only), ILM objects (archive and/or destroy), and HR ILM objects (destruction only).

Q6. What is the difference between standard archiving objects and ILM objects?

Answer:

Standard archiving objects can only archive data, maintaining data availability while reducing database load. In contrast, ILM objects can perform both archiving and data destruction functions, offering more comprehensive data lifecycle management. This distinction is important because ILM objects provide additional capabilities for enforcing data retention policies and compliance requirements. The functionality of each object type is predefined by SAP and may change over time as the software evolves. Organisations should carefully evaluate which object type best suits their specific data management needs and compliance requirements.

Q7. What is data destruction in SAP and how does it differ from archiving?

Answer:

Data destruction in SAP is a process used when ILM is activated to permanently remove data for which an archiving object doesn’t exist. Unlike traditional archiving, data destruction processes data directly from the database in a single step (similar to housekeeping processes) rather than using archive files. The key difference is that data archiving preserves data in archive files whilst removing it from the database, whereas data destruction permanently eliminates the data. Additionally, data destruction requires ILM customising and maintains logs of destruction runs in the system, providing audit trails for compliance purposes.

Q8. Why should organisations consider automating the SAP data archiving process?

Answer:

Organisations should consider automating SAP data archiving because manual archiving is tedious, time-consuming, and prone to errors. Automation streamlines the recurrent process that requires numerous jobs to be reviewed and executed regularly. By automating archiving, organisations can achieve lower total costs of ownership, ensure more accurate data compliance, reduce storage costs (especially during S/4HANA migrations), control post-migration data growth, and enforce privacy policies more effectively. Automation also frees up internal IT teams to focus on more strategic initiatives that drive greater ROI rather than managing repetitive archiving tasks.

Q9. What is the Archiving Sessions Cockpit (ASC) and how does it help with SAP archiving objects?

Answer:

The Archiving Sessions Cockpit (ASC) is an SAP-certified automated data archiving solution developed by TJC Group that optimises and streamlines the entire archiving process. It helps manage SAP archiving objects by providing a centralised interface to control archiving runs from start to completion. ASC can automate mass data archiving (including initial, regular, and selected dates), schedule archiving sessions in sync with IT and business calendars, manage all archiving jobs, automatically recover from disruptions, manage detailed archiving variants, and maintain end-user access to archived data. This comprehensive tool eliminates the need for repetitive manual intervention in the archiving process.

Q10. How does SAP data archiving support S/4HANA migration projects?

Answer:

SAP data archiving significantly supports S/4HANA migration projects by reducing the volume of data that needs to be migrated, which cuts both migration time and costs. By archiving obsolete or rarely accessed data before migration, organisations can streamline the transition process and minimise the size of the HANA database, which uses in-memory technology where storage is more expensive. Automated archiving solutions like ASC can seamlessly archive data as part of the migration preparation, ensuring a more time-effective and cost-efficient migration. Additionally, proper archiving helps organisations start with an optimised S/4HANA system, preventing performance issues from the outset.