Generic Hints for 'Enable Snapshot' in Cash Management

[Hongjun_Qian]

In the General Settings of Cash Management, it is one checkbox named 'Enable Snapshot' (in English environment) to switch on Snapshot functionality.

With official documentation for 'Enable Snapshot':

Flows are then segmented by the time when flows are built in One Exposure from Operations. You can then take a snapshot of the cash flows with a different time and different versions.

 

Here comes the list of generic hints which need be revisited before switch on 'Enable Snapshot'.

 

Hint 1. Business need of snapshot flows' lifetime

By enabling snapshot functionality, the end user can choose another snapshot time in Fiori apps, like 'Cash Flow Analyzer' to check the flows which valid with inputted snapshot time.

 

The key business need is: how long does the end user need to recheck the 'snapshot' flows? Or, what's the business need of snapshot flows' lifetime?

 

The answer shall be provided by business user who really use this functionality. And please be aware that:

The longer the snapshot flows' lifetime is, the bigger data volume it could be;

 

Hint 2. Delete out-of-dated snapshot flows in time

With respect to that there will be an answer of how long the snapshot flows' need be, those out-of-dated snapshot flows need be deleted in time..

Program: FQM_DELETE

Deletion type: Snapshot Cleanup (with a timestamp point)

Based on the data volume of real system, this program shall be executed daily or weekly.

For instance, if the business need is keep 1 week's snapshot flows, execute that program daily or weekly with a proper timestamp.

 

Hint 3. Delete Redundant Snapshot Flow.

Program FQM_DELETE.

Deletion Type: Delete Redundant Snapshot Flow

 

Note 2944767 - One Exposure: Delete Redundant Snapshot Flows, Part VI

 

Currently the snapshot flows are generated when flow are rebuilt. For instance, one flow generated three times and generated two snapshot flows. If the those two snapshot flows are the same business value, we call those two snapshot flows are redundant snapshot flows. Using this deletion type can identify those flows and perform the deletion.

This deletion type will compare the data and perform the deletion. It is a time-cost activity and it shall be executed in background mode.

 

Hint 4. Delete Historical FI Actual Flows.

Program FQM_DELETE.

Deletion Type: Delete Histor. FI Actual Flows

Note 2987792 - FQM Deletion: Delete All Historical Cash Flows with Certainty Level ACTUAL from Accounting

 

The entries of the historical versions, especially the flows coming from Accounting, could be significant and unexpectedly make the size of the database table FQM_FLOW large. Using this deletion type to delete historical versions for Actual flows only.

 

Additional Hint. Data volume analysis of FQM_FLOW

Note 2891515 - One Exposure: Data Volume Analysis

Program: FQM_DATAVOLUME_ANALYSIS

This program will give you an overview about data volume, especially the snapshot flows in the system, which may help on decision about the snapshot flows' lifecycle.

 

Warning: mark 'Simulate Snapshot Compression' may result in very long runtime time (even timeout) to give you a simulated result of 'Delete Redundant Snapshot Flows'.