Title
Reload archived billing document headers.

Purpose
The REAARCH_RELOAD_HEAD report reloads data that has been archived andalready deleted, and has the effect that all changes made to thedatabase by the deletion program are undone. The archive indexesupdated by the deletion program are also deleted.
You can only use the reload program to reload complete archiving runs.You cannot reload individual documents.
The archiving object related to the archiving of billing documents iscalled ISU_BILL. It encompasses the following print document data:

• Billing document


• Outsorting data for a billing document


• Link data for the corresponding print document


• Analysis periods of dynamic period control


• Consumption data for a billing document

Using the AOBJ transaction, you will find the definition of theISU_BILL 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 Utilities Industry menu, you will find theaccounting view of an archived billing document.

Integration


• REAARCH_ANALYSE_HEAD

First step to archiving billing document headers: analysing thebilling documents with a view to possibly archiving them.

• REAARCH_READ_HEAD

Second step: archiving the billing document headers selected inthe first step.

• REAARCH_DELETE_HEAD

Third step: deleting the billing document headers in thedatabase on the basis of the previously created archive.

• REAARCH_BILL_READ_ARCHIVE_HEAD

This report allows you to read a billing document header archive and todisplay parts of the data in a list before the deletion program hasbeen executed. It displays the data in a technical view.

Features

Starting the program
When you start the report you can make various settings on the initialscreen:


• Log type: general statistical data or detail log with detailed data for
each analysed record (can become confusing with large amounts of data).

• Test run: If you start the report as a test run, no changes are made to
the database (updating the archiving indicator in the print documentheader).

Error messages specific to the report (for system administrators)
If one of the following system messages occurs while the program isrunning, proceed as follows:
Whenever you are asked to restart the reload report, first check in theADMI_FILES table to see if the status of the archive (field:ADMI_FILES-STATUS_FIL) was reset to reload. If so, then set it back to3 (deletion completed). Otherwise the archive file will not be proposedfor selection.


• Program stop: error reading archive information

After the system opens a new archive file, it reads system data fromthe file. In this case this was not possible. Get rid of the reason forthe error message and 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 and restart the archiving report.

• Program stop: the commit counter set in Customizing is invalid

A commit counter was specified in Customizing that is less than orequal to zero. Enter a value greater than zero and restart the deletionreport.

• Program stop: error opening the archive file

The system could not open a new archive file. Get rid of the reason forthe error message and restart the archiving report.

• Program stop: error inserting records in a table

A list of print document numbers is displayed with this error message.At least one of these documents could not be inserted in the ERDKtable. Find out which document this is and get rid of the reason forthe error. Restart the reload report.