Kontakt

Ansicht
Dokumentation

FDT_MARK_FOR_DELETE - BRFplus: Mark Objects for Deletion

FDT_MARK_FOR_DELETE - BRFplus: Mark Objects for Deletion

Vendor Master (General Section)   BAL Application Log Documentation  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

With this report, you can flag BRFplus objects as being marked for deletion. Objects in that state remain visible as well as functional, but they can neither be changed nor newly be assigned to any other objects. The marked objects are subject to logical as well as physical deletion as soon as the respective report is run.

The scope for objects to be marked for deletion is based on application level. This means that when you run the report, entire applications are marked for deletion, including all objects that belong to the selected applications. However, you can also choose to set the flag for all objects in a software component or application component (or even a list of such components).

Integration

Prerequisites

Features

The report offers two modes of operation: Normally, you use this report to mark all objects contained in the selected applications for deletion. However, if you realize that objects have been marked by accident, or if you find many of such marked objects in an application where they should not have been marked for deletion, you can also use the report to revert all deletion marks for all objects in an application. You can control the report behavior with the Revert Mark for Deletion checkbox.

Selection

  • 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, Deployable, 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. Note that Customizing Objects and Deployable Objects are mutually exclusive, while all other storage types can be freely combined.
  • Application Transported / Not Transported: Indicates whether objects shall be included whose application have 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.
  • Revert Marked for Deletion: Indicates if the objects in the selected applications are marked for deletion during the run, or if already existing deletion marks are reverted.
  • 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 the objects that have been marked for deletion.

Activities

Example






General Data in Customer Master   General Material Data  
This documentation is copyright by SAP AG.

Length: 4495 Date: 20240520 Time: 054400     sap01-206 ( 104 ms )