Title
Delete archived billing document line items

Purpose
This report covers the third step in archiving billing documentline items: deleting line item data on the basis of the archivepreviously generated. The first step, analyzing the billing documentline items, is carried out using the REAARCH_ANALYSE_LINE report. Inthe second step the billing document line items selected by theanalysis report are archived using the REAARCH_READ_LINES report.
Using the AOBJ transaction, you will find the definition of theISU_BILLZ archiving object and the related Customizing.
Using the SARA transaction, you will find archiving administration andthe related Customizing.
Using the SARI transaction, you will find the technical view of anarchive.
Using the standard IS-U transaction SISU, you will find the accountingview of an archived billing document.

Integration

• REAARCH_ANALYSE_LINES

First step in archiving billing document line items: analyzingbilling documents with a view to possibly archiving them.

• REAARCH_READ_LINES

Second step: archiving the billing document line items selectedin the first step.

• REAARCH_RELOAD_LINES

Use this report to reload data that has been archived and alreadydeleted. Note that you cannot reload individual documents. You have toreload the entire archiving run. This procedure should not normally beused and should be limited to extreme problem cases (for example,incorrect retention period in Customizing).

• REAARCH_READ_ARCHIVE_LINES

This report allows you to read a billing document line item archive andto display parts of the data in a list before the deletion program hasbeen executed. It displays the data in a technical view.

Prerequisites

Features
The deletion report reads billing document line items previouslyarchived in an archiving run from the archive and deletes thecorresponding entries in the database tables.
If you start the report in simulation mode, the following is done foreach document read from the archive:


• the archive status is checked


• the number of lines in each archive file is verified

Starting the program
When you start the report you can make various settings on the initialscreen:
Test run: if you start the report as a test run, no changes are made tothe database (updating the archiving indicator in the print documentheader, deleting data).
Log type: general statistical data or detail log with detailed data foreach analyzed record (can become confusing with large amounts of data).

Error messages specific to the report (for system administrators)
If one of the following system messages appears while the program isrunning, proceed as follows:


• Program stop: error opening the archive file

The system could not open a new archive file. Get rid of the reason forthe error message. Restart the analysis report.

• Program stop: error reading archiving information

After a new archive is opened, system data is read from it. This wasnot possible in the present case. Get rid of the reason for the errormessage. Restart the archiving report.

• Program stop: Error closing the archive file

The system could not close the archive file. Get rid of the reason forthe error message. Restart the archiving report.

• Program stop: The CommitConter specified in Customizing is not valid

A CommitCounter less than or equal to zero was specified inCustomizing. Enter a value greater than zero and restart the deletionreport.

• Program stop: Error deleting the archiving indicator in the ERCHARC
table
A list of billing document numbers is displayed with this errormessage. The line could not be deleted in one of these billingdocuments.
Find out for which billing documents the archiving indicator could notbe deleted and get rid of the reason for the error message. Restart theanalysis report.