Kontakt

Ansicht
Dokumentation

FDT_DELETE - BRFplus: Logical and Physical Deletion Run

FDT_DELETE - BRFplus: Logical and Physical Deletion Run

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

With this report, you can carry out a mass deletion run for unused rule objects of all kinds that have been created with BRFplus. The report offers numerous options that help you fine-tune the scope of affected objects. These options go far beyond the settings that you can make in the application administration tool that is offered in the web-based BRFplus workbench and include, among others, the possibility of performing a system-wide, cross-application deletion run.

Integration

Prerequisites

  • For logical deletion:
    The BRFplus applications defined in the selection scope contain objects that are marked for deletion (unless you explicitly choose to delete all objects regardless of them being marked for deletion or not).
  • For physical deletion:
    The BRFplus applications defined in the selection scope contain objects that are logically deleted.
  • During run execution, none of the objects within the selection scope are locked. Otherwise, report execution stops with an error message.

Features

The report offers two modes of operation:

  • Delete logically: In this mode, the report collects all objects within the scope of selection that have been marked for deletion and deletes them logically. This means that after the run, the deleted objects still exist physically in the system but are completely hidden for the user and cannot be used anymore.
  • Delete physically: In this mode, the report collects all objects within the scope of selection that have been logically deleted and deletes them physically. After that, there is no way of undeleting the objects (unless you have saved them in a system backup that could be restored).

Depending on the selected objects, the report determines which type of transport request is needed for recording the changes. If no suitable request has been entered, the report stops and let you enter the required transport. After that, execution continues.

Selection

  • Retention Time: Defines for how many days a selected object must have been in a state that can trigger a deletion to be actually deleted by the report (default: 90 days). These trigger states are "marked for deletion" (triggers logical deletion) and "deleted" (triggers physical deletion).
  • Software Component, Application Component: Defines the component scope of the selection (software component for a technical view or application component for a function-oriented view). The relationship between a component and a BRFplus object is established via the BRFplus application to which an object belongs.
  • Application Name, ID, and creator: Defines a BRFplus application scope by name, UUID, or the user who created the application.
  • System, Customizing, and Master Data Objects: Defines which object storage types shall be included in the selection. The storage type is set for a BRFplus application at creation time and is inherited by all objects within an application.
  • Application Transported / Not Transported: Indicates whether objects shall be included whose application has already been transported, not yet transported, or both. It is advisable to delete only objects of applications that have not yet been transported to avoid any consistency problems that could arise with future updates in subsequent systems.
  • Objects Transported / Not Transported: Indicates whether objects shall be included that have already been transported, not yet transported, or both. It is advisable to delete only objects that have not yet been transported to avoid any consistency problems that could arise with future updates in subsequent systems.
  • Local / Transportable Objects: Indicates whether objects shall be included that are local to the current system (that is, not to be transported), transportable objects, or both.
  • Delete Logically - Marked: Collects all objects in the selection that are marked for deletion and deletes them logically, but not physically.
  • Delete Physically - LogicDel.: Collects all objects in the selection that are logically deleted and deletes them physically.
  • Delete Logically - All: Collects all objects in the selection and deletes them logically. Note that this operation mode does not make any difference between objects that are marked for deletion and objects that are not.
  • Test Mode: Tick this checkbox to let the report perform all actions according to the selection, but without writing any permanent changes to the database.
  • Workbench / Customizing Request: Depending on the objects in the selection that are to be changed during report execution, you need to enter an open transport request of the appropriate type. If system objects as well as customizing objects are to be changed, you need to enter a transport request for each of the two request types. If the objects to be changed are all local to the current system, no transport request is needed.

Standard Variants

Output

The report generates a log of all processing steps. The log contains aggregated information about the number of deleted objects.

Activities

Example






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

Length: 5827 Date: 20240520 Time: 065554     sap01-206 ( 118 ms )