Kontakt

Ansicht
Dokumentation

REEDMPROFILEIMPLOGDEL - Profile Values Import: Delete Logs

REEDMPROFILEIMPLOGDEL - Profile Values Import: Delete Logs

BAL Application Log Documentation   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

You can use this program to delete logs that were generated when the profile values were imported.

Integration

You can use BAPIs to import profile values to SAP EDM:

  • BAPI_ISUPROFILE_IMPORT
  • BAPI_ISUPROFILE_UPLOAD

When the profile value import is executed, the system lists the logs in various tables. This program deletes the historical logs from the following tables:

  • EEDMIMPORTLOG_DB - EDM import logs
  • EEDMCONSLOGH_DB - EDM profile import consistency log - Header data
  • EEDMCONSLOGP_DB - EDM profile import consistency log - Attribute values

Entries in these tables are linked by the key field ' LOGBELNR'. The deletion process starts with the table EEDMIMPORTLOG_DB and uses the linked key field to delete the entries in the other tables.

The field 'EXTLOGNUMBER' in the table EEDMIMPORTLOG_DB also links the application log and the log for Enhanced Message Management. These logs are not automatically deleted during the deletion process, since they may be required by other applications (such as the business process analysis and processing of clarification cases. The user can decide how these logs are to be handled. The following actions are possible:

  • Delete the application log using the transaction Delete Expired Logs (transaction SLG2)
  • Archive the Log for Enhanced Message Management

Prerequisites

Features

Selection

Select the logs that are to be deleted by specifying the following information, which refers to the import date for the profile values:

  • Retention period in days: The number of days you enter here is deducted from the current date. All logs with an import date that is earlier than the date calculated here are included in the deletion run.
  • Date of import: Enter an interval here (from-to). All logs with an import 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 log.

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 checkbox Check Runtime.

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.

Output

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

Activities

Example

Example






CPI1466 during Backup   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 3628 Date: 20240520 Time: 123037     sap01-206 ( 54 ms )