Ansicht
Dokumentation

REWA_ARCHIVE_SERVFQ - Write Archive File for Service Frequencies

ROGBILLS - Synchronize billing plans   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Purpose

Archiving object ISU_SERVFQ with which you can archive the time slices of the services.

Integration

You can use this archiving object in Information Lifecycle Management. A prerequisite is that you have activated the associated business functions. The system then also displays the ILM actions group box. You can use these actions to perform archiving in which the retention periods defined in the Information Retention Manager are evaluated. You can also make snapshots (copies) of data and destroy data that meets the appropriate criteria. For more information, see the ILM Actions in the Write Program section of ILM Enhancements for Data Archiving.

Prerequisites

Table

Archiving object ISU_SERVFQ uses the following tables:

,,,,,,,,Table,,,,,,Description

Main Table ,,,,,,EWAOBJH,,,,,,Service frequency > services (history for EWAOBJ)

Additional Data,,,,EWAOBJH_AAT,,,,Waste billing categories for the service of the service frequency

,, ,,,,,,EWAOBJH_AAT_HIST,,History and evaluation of the WBCs for the service of the service frequency ,,,,EWAOBJH_DATES,,,,Append table of the modified data for the service frequency ,,,,EWAOBJH_DIFFCULT,,Notes on Service Frequency

,, ,,,,,,EWAOBJH_SDSHARE,,Sales Document Sub-Items for Activity Type

,,,,,,,,EWAOBJH_SEQUENCE ,,Route Sequence per EWAOBJH

,,,,,,,,EWAOBJH_UPOS ,,,,Sales Document Sub-Items for Activity Type

Programs

The following programs are available for archiving object ISU_SERVFQ:

Program ,,,,,,,,,,,,Function

REWA_ARCHIVE_SERVFQ_PRERUN,,,,Preprocessing program

REWA_ARCHIVE_SERVFQ,,,,,,Write program

REWA_ARCHIVE_SERVFQ_DELETE,,,,Deletion program

The object ISU_SERVFQ for archiving time slices of the services reduces the datasets and improves access times significantly. You can use this archiving object to first archive time slices of services that are no longer required or are out of date and then delete them from the system.

The following functions are available for the archiving object:

Preprocessing

The archiving process is started with the PRERUN report.

The system summarizes the data based on the selection criteria, checks whether it can be archived, and sets the status of the service frequency time slices to "For Archiving". Only service frequency time slices for which the retention period has been exceeded are marked for archiving. In PRERUN, there are two options for the existence of corresponding waste disposal orders:

o,,The default setting is that there should be no waste disposal order items for these services when archiving is run.

o,,Any waste disposal orders that exist are "decoupled" such that there are no longer references to the waste disposal orders for the service frequencies to be archived. (The system searches for waste disposal orders for the service frequencies in question and the relevant reference to the service in the waste disposal order item is removed.)

All service frequency headers for which the time slices have been fully archived are also marked for archiving. This is done by adding a deletion flag to the service frequency header.

Write

This write program writes the result set from the PRERUN program from the database to an archive file. The write program supports the ADK suspension concept, which means that you can suspend the write phase and resume it at a later stage. You can also suspend the write program indirectly by making certain settings in Customizing (see Customizing below). In the write program, only those service frequency time slices or headers are selected for which deletion is planned or a deletion flag has been set in advance.

You can enter a short text for the archiving run in the notes about the archiving run field that is used for identification purposes and to make it easier to relocate archive files.

Delete

Once archiving has been completed successfully, the data in the system can be deleted. The deletion program first reads the data in the archive file and deletes the corresponding data from the database.

You can define restrictions on the selection screen for the variants of the archiving program (transaction: SARA).

Certain conditions must be fulfilled to ensure that only services that are no longer required are archived from the system.

The following criteria must be met before the weighing transaction can be archived:

o,,The status of the service frequency time slice must be switched to 'For Archiving'.

o,,The deletion flag of the service frequency header must be set to allow the header to also be archived.

o,,The minimum retention period must have expired.

You define retention periods in Customizing for the Utilities Industry. To make these settings in Customizing for SAP Utilities, choose Tools -> Archiving.

You can start the actual archiving process in the SARA transaction. You can execute the individual steps in the archiving process, such as the preprocessing program and write program as long as no automatic start has been defined for the deletion program in the technical settings in the archive-object-specific Customizing. You can also define the technical values for archiving, such as the name, path, maximum size of the archive file and define the residence times.

Features

Selection

Standard Variants

Output

Activities

Example

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 6225 Date: 20240520 Time: 130545     sap01-206 ( 111 ms )