SAP Program REA_EANL_ARCHIVE - Report REA_EANL_ARCHIVE

Purpose
This report is the first step for archiving installations. It includes:

  • The analysis of installations with regard to a possible archiving

  • The writing of installations in an archive file, based on the
  • analysis carried out in the first step.
    The archiving object comprises data for the installation from thefollowing tables:
    • EANL:,,Table for installations

    • EANLH:,,Table for installation time slices

    • The archiving of archiving objects belonging to the installation iscalled ISU_EANL.
      You use transaction AOBJ to determine the definition of thearchiving object and the corresponding Customizing.
      Use transaction SARA to determine the archive administration andthe corresponding Customizing.
      Use transaction SARI to determine the technical view for archivedprofile values.

      Integration
      Installation archiving includes the following reports:
      1. Archiving report
      All specified installations are analyzed with regard to a possiblearchiving. The installations that can be archived, are archived.
      You can use BAdI ISU_EANL_ARCHIVE to define additional checks on whetherinstallations can be archived.
      2. Deletion report
      The installations written in the archive file are deleted from thecorresponding database tables.
      3. Evaluation report
      The archived installations are displayed.

      Features
      The following installations are selected with the evaluation report:

      • Those within the specified installation number range

      • Those in table EANL that are marked for deletion

      • In a subsequent analysis process you can use BAdI ISU_EANL_ARCHIVE todefine additional checks on the archivability of installations. See thedocumentation for the BAdI for further information.

        Selection
        You can make various settings in the initial screen when you start thereport:

        • Installation number: Restrict data quantity to be analyzed to
        • certain installations
          • Test run: When you start the report as a test run, no changes are
          • made in the database
            • Update run: Changes are made in the database

            • Detail log: Switch on log with detailed data for each data record
            • analyzed (for large quantities of data, this can cease to be anoverview)
              • Comment for archiving run: Here, you can enter a comment on the
              • archiving run