Kontakt

Ansicht
Dokumentation

FDT_TRUNCATE_VERSIONING - BRFplus: Discard Old Versions

FDT_TRUNCATE_VERSIONING - BRFplus: Discard Old Versions

CPI1466 during Backup   Vendor Master (General Section)  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

With this report, you can cleanup the BRFplus database by removing old unused versions of objects of all kinds. This is useful not only for keeping the database growth speed low but also to help avoid unproductive object references that could interfere with your current developments.

For example, an expression E has an old version containing a reference to data object D1. This reference E->D1 has been replaced in the current active version of E by a new reference E->D2. Also, D1 is not used by any other objects and therefore a candidate for deletion. However, due to the existing reference in the older version of E, D1 cannot be deleted as long as this outdated reference exists. This deadlock situation can only be solved by discarding the old version of E so that there is no usage of D1 in the system, and D1 can be deleted.

Integration

Prerequisites

Features

The report follows the strategy "discard as many versions as possible according to the selection criteria, but preserve all versions that are used by other objects". For a version that is used by other objects, this is accomplished by automatically adjusting the version timestamp of the referenced version such that the report cannot discard it.

If the discarding date derived from the given retention time lies within the lifetime of a particular version, the system lets the user still access this version but modifies the start date of that version according to the discarding date.

Selection

  • Retention Time: Defines the number of days counted backwards from report execution time. Object versions that have been created during this period, or for which a usage relationship has been established during this period, remain untouched by the report. All older versions are discarded.
  • 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.
  • 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.
  • Discard Logically: All object versions matching the selection criteria are logically discarded. Versions that are older than the given retention time are no longer visible for the user.
  • Discard Physically: All object versions matching the selection criteria are physically removed from the database and cannot be retrieved after report execution.
  • 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.

Standard Variants

Output

Activities

Example






Fill RESBD Structure from EBP Component Structure   General Material Data  
This documentation is copyright by SAP AG.

Length: 3367 Date: 20240531 Time: 145549     sap01-206 ( 73 ms )