Programme SAP REAR_DEL_BBP_ILM - Delete archived budget billing plans

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 previouslygenerated.
The archiving object related to the archiving of budget billing plans iscalled ISU_BBP. It encompasses the following budget billing plan data:

  • Header data

  • Items

    • When budget billing plans are processed statistically the budget billingplan items are archived by FI-CA document archiving and not togetherwith the ISU_BBP archiving object.
    INCLUDE ISU_ARCHIVE_TRANS OBJECT DOKU ID TX

    Integration

    • REAR_ANALYSE_BBP

      • First step in archiving budget billing plans: analyzing budget billingplans with a view to possibly archiving them.
      • REAR_ARCH_BBP

        • Second step: archiving the budget billing plans selected in the firststep.
        • 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.
          • REAR_READ_ARCHIVE_BBP

            • This report allows you to read a budget billing plan 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

            Features
            The deletion report reads the budget billing plans from the archivewhere they are stored and deletes them from the database along with anyrelated item data.
            Commits are carried out according to the settings for the deletionprogram in Customizing (transaction AOBJ).
            When the budget billing plans are deleted, an archive index is writtento the database, to allow access to budget billing plans that havealready been archived.

            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 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 theADMI_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 willnot be proposed for selection.

                • Program stop: error opening the archive file

                  • The archive file from which the data was to be reloaded could not beopened.
                  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 thefile. In this case this was not possible.
                    Get rid of the reason for the error message and restart the deletionreport.
                    • 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 tozero.
                      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 archivingobject.
                        Restart the deletion report.
                        • Program stop: error deleting records from the EABP table

                          • A list of budget billing plan documents is displayed with this errormessage. At least one of these documents could not be deleted from theEABP table.
                          Find out which document it was and remove the cause of the errormessage. 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 errormessage. At least one of these documents could not be deleted from theEJVL table.
                            Find out which document it was and remove the cause of the errormessage. 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 errormessage. At least one of these budget billing plans could not be deletedfrom the DFKKMOP table.
                              Find out which document it was and remove the cause of the errormessage. 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 errormessage. At least one of these budget billing plans could not be deletedfrom the DFKKMOPW table.
                                Find out which document it was and remove the cause of the errormessage. Then restart the deletion report.
                                • Program stop: Error transferring statistical data

                                  • An unexpected error has occured during the transfer of statistical datato the ADK.
                                  (*): This error message cannot occur when a statistical budget billingplan procedure is used.