Ansicht
Dokumentation

FQM_DELETE - Delete Data from One Exposure from Operations Hub

ABAP Short Reference   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Purpose

With this activity, you can delete transactional data in One Exposure from Operations to ensure data protection and privacy. The deleted data will no longer be displayed in cash management reports that consume data stored in One Exposure from Operations.

Features

You can use the following deletion types:

• Flag for Deletion

You use this deletion type to flag the data that you filter for deletion. The flagged entries will be permanently deleted after you choose the type Delete Flagged Entries Only. The deletion flags cannot be removed.

• Delete

You use this deletion type to delete all the data that you filter. Data will be permanently deleted.

• Delete Flagged Entries Only

You use this deletion type to delete only the flagged data that you filter. Data will be permanently deleted.

• Delete Redundant Snapshot Flow

You use this deletion type to delete redundant snapshots. With this deletion type, you can use the allowed list. For more information, please refer to Delete Redundant Snapshot Flow.

• Snapshot Cleanup

You use this deletion type to directly delete snapshots by timestamp.

• Delete Historical FI Actual Flows

You use this deletion type to set the deleted fields to the status 'X' for the snapshots you select in FQM_FLOW.

• Mass Delete Memo Records

You use this deletion type to mass delete memo records you select in FQM_FLOW. It checks the configuration of the snapshots to decide how to delete.

The following selections are available for you to filter the data you want to delete:

• Source Application

• Company Code

• Transaction Date

Activities

You can use the following source applications with different system behaviors.

Source Application,,Source Application Description,,System Scenario Available,,Rebuild Tool

AGG,,Aggregation Flows,,one-system scenario,,No

BKPF,,Financial Operations,,one-system scenario,,Yes

BS,,Bank Statement,,one-system scenario,,No

CMRRD,,Memo Record,,one-system scenario,,No

IBU,,Initial Balance via Excel,,one-system scenario,,Yes

MM,,Materials Management,,one-system scenario,,Yes

REFX,,Contract and Lease Management,,one-system scenario,,Yes

SDCM,,Sales and Distribution (CM),,one-system scenario,,Yes

TRM,,Treasury and Risk Management,,one-system scenario,,Yes

The One Exposure from Operations hub can receive operational data from sources within the system in which it runs itself (one-system scenario), as well as from external sources (side-by-side scenario).

• For source applications that are stored in the same system (one-system scenario), update of source applications are triggered in the same system.

• For source applications that are stored in the remote systems (side-by-side scenario), update of source applications is triggered in the remote system.

Note:

For the source application CMMRD (Memo Record), the deletion type Delete is not supported. You need to set the Flag for Deletion, and then choose Delete Flagged Entries Only.

For the source application AGG (Aggregation Flows), BS (Bank Statement), CMMRD (Memo Record), and MEBAC (Manual Entry of Bank Cash Balance), there are no rebuild tools available.

CPI1466 during Backup   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 4615 Date: 20240520 Time: 065311     sap01-206 ( 60 ms )