Too often, testing for an archiving project is limited to running the job in a test system and seeing if the database size shrinks. A truly robust test plan, as outlined in best-practice guides like the *Archiving SAP Data Practical Guide*, must go much further to cover data retrieval, interfaces, and security.
AREA 1: FUNCTIONAL TESTING (THE BASICS)
This is the starting point to ensure the core mechanics of the archiving object are working as expected.
- Test Case: Correct Data Selection. Verify that the `SARA` write job, using your defined variant, correctly selects only the data that meets the residence time and other business criteria. Check the job log for any skipped documents and understand why they were skipped.
- Test Case: Successful Deletion. Confirm that after a successful and verified write job, the corresponding delete job physically removes the correct data from the primary database tables.
AREA 2: DATA RETRIEVAL TESTING (THE MOST CRITICAL PART)
This is where you involve your business users to alleviate their primary fear: losing access to data.
- Test Case: Single Document Display. Can users still display single archived documents via their standard transactions (e.g.,
FB03,VA03,ME23N)? This is a critical test of your Archive Information System (`SARI`) setup. - Test Case: List Reporting via `SARI`. Can users search and generate reports on archived data using the flexible search criteria provided by the Archive Information System?
- Test Case: Business Process Integrity via `DRB`. Can users navigate the complete business process chain (e.g., from an archived sales order to its delivery) using the Document Relationship Browser (
ALO1)?
User Acceptance Testing (UAT) is Non-Negotiable
You must have documented proof that business users have performed these retrieval tests and have formally signed off, confirming that the access methods meet their daily operational and audit needs.
AREA 3: INTERFACE AND CUSTOM CODE TESTING
This is the most frequently overlooked area of testing. Data archiving can have a significant impact on any process that directly reads the affected tables.
- Test Case: External Interfaces. Do any external systems (e.g., a 3rd party logistics system, a tax engine, a data warehouse) read directly from the tables being archived? These interfaces must be tested end-to-end to ensure they do not fail.
- Test Case: Custom Reports and Programs. Identify all custom "Z-reports" or programs that reference the target tables. Each one must be tested to see if it needs to be adapted to read from the archive.
AREA 4: AUTHORIZATION TESTING
Ensure that your security concept is working as designed.
- Test Case: End-User Role. Log in as a standard business user. Confirm they can *only* display archived data and cannot run administrative archiving jobs in `SARA`.
- Test Case: Administrator Role. Log in as the Basis or DVM administrator. Confirm they have the necessary authorizations to schedule, monitor, and troubleshoot the archiving jobs.