Ansicht
Dokumentation

REL_DELETE_EABLDEL - Delete Reversed Meter Reading Documents

REL_DELETE_EABLDEL - Delete Reversed Meter Reading Documents

PERFORM Short Reference   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

You can use this program to delete reversed meter reading documents.

Integration

You can use the transaction Reverse Meter Reading (EL37) to delete meter reading documents (meter reading orders or meter reading results) from the database tables for meter readings. If the switch ISU_MR_EHP6 (Meter Reading Documents) has been activated, the system also copies meter reading documents into the following database tables:

  • EABLDEL - Meter reading documents
  • EABLGDEL - Meter reading reasons for meter reading document
  • EABLQDCONVDEL - Conversion history for quantity determination during meter reading

These copies are used for verification purposes during the data exchange (for example market communication).

You can use this program to delete copies that have reached a specific retention period and are no longer required from the database tables, and therefore reduce pressure on your database.

Prerequisites

The switch ISU_MR_EHP6 (Meter Reading Documents) must be assigned to an active business function.

Features

Selection

You select the reversed meter reading documents that are to be deleted by specifying the following information, which refers to the planned meter reading date for these documents:

  • Retention period in days (scheduled MR date): The number of days you enter here is deducted from the current date. All reversed meter reading documents with a planned meter reading date that is earlier than the current date are included in the deletion run.
  • Scheduled meter reading date: Enter an interval here (from-to). All reversed meter reading documents with a planned meter reading date that is found during this time period are included in the deletion run.

If you make an entry for both criteria, the system links these with a logical 'AND'. This means that deletion is only possible if both criteria are met for a meter reading document.

By specifying a restricted runtime, you can define the latest end for a deletion run by entering an end date, end time and selecting the corresponding checkbox.

Under flow control, you define whether the program is to be executed in the test mode or the production mode. In the test mode, you can for example define how many table entries can be deleted with these selection criteria.

You use additional parameters to define the log depth and the output device for the log created. Logged data can be written to the list (or spool for a background job) or the application log.

Standard Variants

Output

The system uses these entries to create a results list and/or an application log that displays information about deleted meter reading documents. You can display the application log using the transaction Analyze Application Log (SLG1) (object ARCHIVING).

Activities

Example






BAL_S_LOG - Application Log: Log header data   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 3649 Date: 20240601 Time: 061737     sap01-206 ( 63 ms )