Ansicht
Dokumentation

REAARCH_ANALYSE_EXRESP - Archiving Analysis of TOU Exception Responses for Contracts

ROGBILLS - Synchronize billing plans   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Purpose

This report is the first step in archiving TOU exception responses: Analysis for the archivability of TOU exception responses:

Integration

REAARCH_ANALYSE_EXRESP

First step in the data archiving process for TOU exception responses: Analysis of TOU exception responses with regard to potential archiving.

REAARCH_ARCH_EXRESP

Second step: Archive the TOU exception responses selected in the first step.

REAARCH_DEL_EXRESP

Third step: Delete TOU exception responses from the database on the basis of the previously created archive.

REAARCH_REL_EXRESP

Use this report to reload data that has been archived and already deleted. Note that you cannot reload individual TOU exception responses, but must always reload the entire archiving run. This procedure should not normally be used and should be limited to extreme problem cases (for example, incorrect retention period in Customizing).

REAARCH_READ_ARCHIVE_EXRESP

You can use this report to read a TOU exception response from the archive before the deletion program has been run, and display it in a list. It displays the data in a technical view.

Prerequisites

Features

The analysis for the archivability of TOU exception responses runs as follows:

1. Selection
   First you have to restrict the archiving volume. To do this, enter the contract and/or TOU exception program for which you want the associated TOU exception responses to be archived.

1. Determine final date for archiving
   The retention period in days in defined in Customizing for SAP Utilities under Tools → Archiving → Define Retention Period for Archiving Objects. The system determines the limit date for archiving from this retention period. You can only archive documents whose existence exceeds the retention period defined in Customizing.
   The retention period of archiving object ISU_BILL (billing document header) is used to help determine the final date for archiving TOU exception responses.

1. Determine the TOU exception responses
   All associated TOU exception responses are determined for each contract and/or TOU exception program up to the final date.

1. Determine and check the associated billing documents for the period of the corresponding TOU exception
   TOU exception responses can only be archived if the respective billing document, whose billing period is found during the period for the corresponding TOU exception, has been archived.

1. Write temporary index
   The system writes the contract and the TOU exception program to the index table ETOUEXCEPTRESPAR for the TOU exception responses that can be archived. This index table is used as the basis for archiving. Once data has been successfully archived and deleted, the system deletes the respective index entry from the database.

Activities

Example

CL_GUI_FRONTEND_SERVICES - Frontend Services   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 3674 Date: 20240601 Time: 195503     sap01-206 ( 58 ms )