Title

Archive Budget Billing Plans

Description
This report is the second step in the process of archiving budgetbilling plans: The writing of budget billing plans to an archive file,based on the analysis carried out in the first step.
The archiving object related to the archiving of budget billing plans iscalled ISU_BBP. It encompasses the following budget billing data:

• Budget billing plan header data


• Budget billing plan items

When budget billing plans are processed statistically the budget billingplan items are archived by contract accounting document archiving andnot together with the ISU_BBP archiving object.
You can use the AOBJ transaction to access the definition of the ISU_BBParchiving object and the corresponding Customizing settings.
You can use the SARA transaction to access archiving administration andthe corresponding Customizing settings.
You can use the SARI transaction to access the technical view of anarchive.
You can use the standard IS-U transaction SISU to access the accountingview of an archived budget billing plan.

Integration


• REAR_ANALYSE_BBP

First step in the process of archiving budget billing plans: Analysis ofbudget billing plans with regard to potential archiving.

• REAR_DEL_BBP

In the third step the budget billing plans are deleted from the databaseusing this report, on the basis of the previously created archive.

• REAR_REL_BBP

Use this report to reload data that has been archived and alreadydeleted. Note that you cannot reload individual budget billing plans.You have to reload the entire archiving run.

• REPDAR_READ_ARCHIVE_HEAD

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

Prerequisites
Before you start this archiving report, you have to carry out at leastone analysis with the REAR_ANALYSE_BBP report.

Features
The archiving report selects the budget billing plans that weretemporarily saved in a table by the analysis report. They are then w
ritten to an archive file and the temporary entry in the table isdeleted. If you started the report in test mode, the database changesdescribed above are not carried out and only a detailed overview (youcan set the level of detail) of the documents that can be archived isprovided.

Notes on 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 analyzed data record (can become confusing with large amounts ofdata).

• Run time restriction: If you activate the run time restriction, the
analysis report terminates when the end date and end time is reached.This means that you can let the analysis report run as a job duringshort time frames.

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

• Comment on archive run: Here you can enter an individual comment for an
archiving run.

Error Messages Specific to the Report (for System Administrators)
If one of the following system messages occurs while the program isrunning, proceed as described:


• Program stop: error opening the archive file

The system could not open a new archive file.
Get rid of the reason for the error message and restart the archivingreport.

• Program stop: error reading archive information

After the system opens a new archive file, it reads system data from thefile. In this case this was not possible.
Get rid of the reason for the error message and restart the archivingreport.(*)

• Program stop: error reading from the EABP/EJVL tables

An unexpected error occured while reading from the EABP and/or EJVLtables.
Get rid of the cause of the error and restart the archiving report.(**)

• Program stop: error reading from the DFKKMOP table

An unexpected error occured while reading from the DFKKMOP table.
Get rid of the cause of the error and restart the archiving report.(**)

• Program stop: error reading from the DFKKMOPW table

An unexpected error occured while reading from the DFKKMOPW table.
Get rid of the cause of the error and restart the archiving report.(**)

• Program stop: error deleting in the EABPARCH table

A list of budget billing plan numbers is provided with this errormessage. For at least one of the budget billing plans in the list thecorresponding entry in the EABPARCH table could not be deleted.
Check all the listed budget billing plan numbers and delete thecorresponding entries in the EABPARCH table if necessary. Determine thecause of the error and get rid of it. Restart the report.

• Program stop: error closing the archive file

(*): When the report is restarted a new archive file is created. You candelete the old file if it does not contain any data yet (check thisusing the REAR_READ_ARCHIVE_BBP report).
(**): When the report is restarted a second archive file is created.