Kontakt

Ansicht
Dokumentation

REAR_REL_BBP - Reload archived budget billing plans

REAR_REL_BBP - Reload archived budget billing plans

rdisp/max_wprun_time - Maximum work process run time   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.
SAP E-Book

Title

Reload archived budget billing plans

Purpose

This report allows you to reload data that has been archived and already deleted and therefore to undo any changes made to the database by the deletion program. The archive indices updated by the deletion program are also deleted again.

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 budget billing plans is called ISU_BBP. It encompasses the following billing document data:

  • Header data
  • Items
Note: If budget billing plans are processed statistically, the budget billing plan items are archived using contract accounting document archiving and not together with the ISU_BBP archiving object.

Integration

  • REAR_ANALYSE_BBP
First step in archiving budget billing plans: analyzing budget billing plans with a view to possibly archiving them.
  • REAR_ARCH_BBP
Second step: archiving the budget billing plans selected in the first step.
  • REAR_DEL_BBP
Third step: deleting the budget billing plans in the database on the basis of the previously created archive.
  • REAR_READ_ARCHIVE_BBP
This report allows you to read a budget billing plan archive and to display parts of the data in a list before the deletion program has been executed. It displays the data in a technical view.

Prerequisites

Features

Starting the program

When you start the report you can make various settings on the initial screen:

  • Log type: general statistical data or detail log with detailed data for each analyzed 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.

Error messages specific to the report (for system administrators)

If you restart the reload program, first check in the ADMI_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 to deletion completed. Otherwise the archive file will not be proposed for selection.

  • Program stop: error opening the archive file
The archive file from which the data was to be reloaded could not be opened.
Get rid of the reason for the error message and restart the reload report.
  • Program stop: error reading archive information
After the system opens a new archive file, it reads system data from the file. In this case this was not possible.
Get rid of the reason for the error message and restart the archiving report.
  • Program stop: error closing the archive file
  • Program stop: error reading a new object from the archive
An error occured while reading a new object from the archive.
Get rid of the reason for the error message and restart the archiving report.
  • Program stop: the commit counter set in Customizing is invalid
A commit counter was set up in Customizing for the archiving object that is less than or equal to zero.
Enter a value greater than zero and restart the deletion report.
  • Program stop: error reading a record in an archiving object
An unexpected error occured while reading a new record in an archiving object.
Restart the reload report.
  • Program stop: error inserting records in the EABP table
A list of budget billing plan numbers is displayed with this error message. At least one of these budget billing plans could not be inserted in the EABP table.
Find out which document this is and remove the cause of the error. Restart the reload report.
  • Program stop: error inserting records in the EJVL table
A list of budget billing plan numbers is displayed with this error message. At least one of these budget billing plans could not be inserted in the EJVL table.
Find out which document this is and remove the cause of the error. Restart the reload report.
  • Programmstop: error inserting records in the DFKKMOP table (*)
A list of budget billing plan numbers is displayed with this error message. At least one of these budget billing plans could not be inserted in the DFKKMOP table.
Find out which document this is and remove the cause of the error. Restart the reload report.
  • Programmstop: error inserting records in the DFKKMOPW table (*)
A list of budget billing plan numbers is displayed with this error message. At least one of these budget billing plans could not be inserted in the DFKKMOPW table.
Find out which document this is and remove the cause of the error. Restart the reload report.
  • Program stop: Error transferring statistical data
An unexpected error has occurred during the transfer of statistical data to the ADK.

(*): This error message cannot occur if the statistical budget billing plan procedure is used.

Example






BAL_S_LOG - Application Log: Log header data   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 6071 Date: 20240601 Time: 062045     sap01-206 ( 72 ms )