Kontakt

Ansicht
Dokumentation

REAR_DEL_BBP - Delete archived budget billing plans

REAR_DEL_BBP - Delete archived budget billing plans

Vendor Master (General Section)   Vendor Master (General Section)  
This documentation is copyright by SAP AG.
SAP E-Book

Title

Delete archived budget billing plans

Purpose

This report covers the third step in archiving budget billing plans: deleting the budget billing plans on the basis of the archive previously generated.

The archiving object related to the archiving of budget billing plans is called ISU_BBP. It encompasses the following budget billing plan data:

  • Header data
  • Items
When budget billing plans are processed statistically the budget billing plan items are archived by FI-CA 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_REL_BBP
Use this report to reload data that has been archived and already deleted. Note that you cannot reload individual budget billing plans. You have to reload the entire archiving run.
  • 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

The deletion report reads the budget billing plans from the archive where they are stored and deletes them from the database along with any related item data.

Commits are carried out according to the settings for the deletion program in Customizing (transaction AOBJ).

When the budget billing plans are deleted, an archive index is written to the database, to allow access to budget billing plans that have already been archived.

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 (deleting the data).

Error messages specific to the report (for system administrators)

Whenever you have to restart the deletion report, first check the ADMI_FILES table to see if the status of the archive (field: ADMI_FILES-STATUS_FIL) was set to deletion completed. If so, reset it to archiving 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 cause of the error and restart the deletion report.
  • Program stop: error reading archive information
After the system opens the 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 deletion report.
  • Program stop: error closing the archive file
  • Program stop: the commit counter set up in Customizing is invalid
A commit counter was set up in Customizing 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 for an archiving object
An unexpected error occured while reading a new record for an archiving object.
Restart the deletion report.
  • Program stop: error deleting records from the EABP table
A list of budget billing plan documents is displayed with this error message. At least one of these documents could not be deleted from the EABP table.
Find out which document it was and remove the cause of the error message. Then restart the deletion report.
  • Program stop: error deleting records from the EJVL table
A list of budget billing plan documents is displayed with this error message. At least one of these documents could not be deleted from the EJVL table.
Find out which document it was and remove the cause of the error message. Then restart the deletion report.
  • Program stop: error deleting records from the DFKKMOP table (*)
A list of budget billing plan documents is displayed with this error message. At least one of these budget billing plans could not be deleted from the DFKKMOP table.
Find out which document it was and remove the cause of the error message. Then restart the deletion report.
  • Program stop: error deleting records from the DFKKMOPW table (*)
A list of budget billing plan documents is displayed with this error message. At least one of these budget billing plans could not be deleted from the DFKKMOPW table.
Find out which document it was and remove the cause of the error message. Then restart the deletion report.
  • Program stop: Error transferring statistical data
An unexpected error has occured during the transfer of statistical data to the ADK.

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

Example






Addresses (Business Address Services)   General Material Data  
This documentation is copyright by SAP AG.

Length: 6163 Date: 20240520 Time: 124811     sap01-206 ( 74 ms )