Title
Archive Installation Facts

Purpose
This report is the first step when archiving installation facts. Itincorporates:
The analysis of installation facts with a view to a possible archiving
The writing of installation facts in an archive file, based on theanalysis executed in the first step
The optional deletion of inactive installation facts from the database,based on the analysis executed in the first step.
RESET N1
The archiving object comprises the following installation fact data:

• ETTIFN: Installation facts (normal)


• ETTIFB: Installation facts (reference values)

The archiving object for archiving installation facts is ISU_FACTS.
You use transaction AOBJ to find the definition of the archiving objectand the corresponding Customizing.
You use transaction SARA to find the archive administration and thecorresponding Customizing.
You use transaction SARI to find the technical view for the archivedinstallation facts.

Integration
INCLUDE ISU_ARCH_FACTS_INTEGRATION OBJECT DOKU ID TX LANGUAGE EN

Features
Th archiving report is used to select the following installation facts:


• Installation facts, whose installations lie within the specified
selection area

• Installation facts, whose retention periods have expired

You can define the retention period in Customizing, under SAPUtilities -> Tools -> Define Retention Period for Archiving Objects.
You can use the ISU_FACTS_ARCHIVE BAdI in a subsequent analysis processto define additional checks for the archivability of installation facts.For more information, see the documentation on the BAdI
All installation facts that are selected and have the status 'INACTIVE'are indicated as deletable by the system. All other facts, whichcorrespond to the selection criteria and do not have the status'INACTIVE', are marked as archivable.
Archivability Checks:

• You can only archive an active entry if there is no older, active entry
in the same logical unit* (sequence check).
,,The sequence check does not apply to inactive entries.

• You can only archive an entry if the TO date lies before the defined
retention period (retention period check). If the installation has notyet been billed at the time of the defined retention period, then onlyinstallation facts up to the end of the last billing period arearchived.

• Values that are updated (or changed) automatically can only be archived
if the billing document, which was marked in BELNR (or MBELNR) hasalready been archived (document check).
* Logical unit: Entries in ETTIFN for a combination of client,installation, operand, and season (first four key fields in the databasetable)

Selection
You can make the following settings when you start the report:


• Installation: Restrict data quantity to be analyzed to certain
installations

• Test run: No changes are made in the database if you start the
report as a test run

• Update run: Changes are made in the database


• Detail log: Activate a detail log with detailled data on each
analyzed data record (can become unclear in cases with large quantitiesof data)

• Comments of archiving run: Here, you can enter an individual
comment on an archiving run