Kontakt

Ansicht
Dokumentation

REAMIEM_EVENT_ARCH - IS-U Archiving: Archive AMI Event Management

REAMIEM_EVENT_ARCH - IS-U Archiving: Archive AMI Event Management

ABAP Short Reference   General Data in Customer Master  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

This report is the first step in the process of archiving events in the AMI environment. It includes the following steps:

  1. Analysis of events with regard to possible archiving
  2. Writing of messages in an archive file

The archiving object consists of the following data:

  • TEAMI_EM_EVTS (Smart Meter Events)
  • TEAMI_EM_EVTATTR (Attributes for Smart Meter Events)
  • TEAMI_EM_EVTRES (Results for Smart Meter Events)
  • TEAMI_EM_EVTMSG(Messages for Smart Meter Events)

The archiving object related to the archiving of log messages is called ISU_AMIEVT.

Integration

The archiving of events includes the following reports:

  1. Archiving report (REAMIEM_EVENT_ARCH)
    The system analyzes the events and writes archivable entries in the archive file.
  2. Deletion report (REAMIEM_EVENT_DELETE)
    The system deletes the entries based on the previously created archive file from the database tables.

Prerequisites

Features

The archiving report selects events whose residence time has expired. The residence time refers to the creation date of events.

You define the residence time in Customizing under:

SAP Utilities → Tools → Archiving →Define Retention Period for Archiving Objects.

In addition, only the following status records can be archived:

  • 02 COMPLETED

  • 05 CANCELLED

  • 06 REJECTED

  • 07 FEH

Selection

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

Equipment: Limits the equipment data to be analyzed or archived

Event Type Code: Limits the event type code data to be analyzed or archived

Event Status: Limits the event status data to be analyzed or archived: only the COMPLETED (02), CANCELLED (05), REJECTED (06) and FEH (07) status are selected.

Test Mode: Starts the report as a test run; the system does not make any changes in the database.

Production Mode: Starts the report as a production run; the system makes changes in the database.

Detail Log: Displays a log containing extensive data for every analyzed data record.

Note: The log may be hard to read as it contains large amounts of data.

Archiving Session Note

In variant maintenance for the write program the following actions from SAP NetWeaver Information Lifecycle Management are available:

  • Archiving
With this action, you can archive the data of closed business objects. The system performs archivability checks to check if the data can be archived. In this respect, this function corresponds to the function of standard data archiving that you are used to. By means of the ILM enhancements, the system evaluates the rules maintained in the Information Retention Manager (IRM) for each object instance during the write phase, and thereby determines the retention period and the storage location for the object. This information is persisted on the database as part of the management data and is later interpreted when the data is stored.
  • Snapshot
Snapshots represent archiving runs that extract data from the database, but do not delete this data from the database. Except for considering the restrictions in the selection variant, the system does not perform any additional checks. Using this option, therefore, you can also write data from current, not yet completed business transactions to the archive. To exclude the possibility of losing data, runs of this type are not offered for deletion. With snapshots therefore, you always create redundant copies of data from the database. This function is especially useful for system decommissioning in conjunction with the ILM component Retention Warehouse.
  • Destruction of Data
The destruction of data from the database takes place using an archiving write run followed by a deletion run. During this process, temporary archive files are created that are then deleted again after the deletion phase is completed. The system automatically deletes these files along with the file-related management data. The technical classification of a run as a destruction run is made using the parameter DESTROY. If an archiving object is not registered in IRM, the parameter DESTROY is completely ignored, and a normal archiving run takes place.

Standard Variants

Output

Activities

Example






Fill RESBD Structure from EBP Component Structure   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 5943 Date: 20240601 Time: 024920     sap01-206 ( 96 ms )