Introduction to Data Volume Management #ASUG Webcast Summary
This was an ASUG webcast last month.
Don’t forget to register for tomorrow’s webcast : The New Client Copy Tool
Abstract (from the webcast).
Fine-tune your SAP ECC or prepare for SAP S/4HANA by learning more about SAP Data Volume Management. Learn what the application is and why it is needed. See an overview of the five data volume management methodologies, plus more details on archiving. Check out what’s new in SAP S/4HANA for the use of the Data Volume Management Cloud Solution and dashboard, and learn how SAP can assist with this application and the Data Volume Management value map. (Source: SAP/ASUG)
What is DVM?
Defined on screen
DVM – balance needs of business and IT
Reduce volumes of data
Focus on daily operations but also help if migrating to a HANA system
Why is DVM needed?
Business and infrastructure side
IT – better performance, less use of resources, shorter down times for migration projects are possible
Analyze areas of growth, age of data
Only want to keep recent data
Don’t want to keep legacy data if not needed
In memory costs money
Some transactions will have better performance – e.g. MB51 – does a full table scan
Remove data in safe and quick manner
Usually done using Solution Manager – DVM work center in 7.2
Provides good monitoring, Fiori Apps
S/4HANA – DVM Cloud Application
These methodologies have been available for some time
Do you need data, can you summarize data
Opportunity to delete Basis/technical data in system
Data Aging – feature with SAP HANA, move from hot memory to cold memory, started with Basis
Also see SAP Note https://launchpad.support.sap.com/#/notes/781433
Question – do you need to write all the database?
Some opportunities to avoid data – customizing error could cause volume – DBTABLOG – see SAP Notes to change table logging
Account Interface documents, especially for retail (subsequent postings)
100 lines in finance document with 1 material – perhaps just interested in total by material
In controlling, table COEP
Data deletion – fastest, but may not be best
Spool data, application logs, IDOCs – deletion report
Spool data is stored in table TST03 – this does not need to stay in system as long as application data
From my own notes: program RSTBPDEL deletes entries in DBTABLOG, “Log Records of Table Changes”
Need a BW housekeeping data strategy
In the long run, more likely face data archiving, most beneficial in long run
Access data periodically
Archived data cannot be changed
2 phases – create archive file
Covered in another blog
Statement from SAP in September regarding data aging
Once move to S/4HANA, DVM doesn’t stop
Clear up data before migration to S/4HANA
Only migrate data you really want to use
New tool in One Support Launchpad
Top left of One Support Launchpad – personalize
Type in Data Volume Management
Add to your home page
Put in system ID of where done system analysis
Landing page – 2 parts – upper and lower
Upper part – memory usage breakdown
Disk usage breakdown
Optimized memory usage – residence times
See replay at Introduction to SAP Data Volume Management
See link to slides here which contains the links on the slides
Question & Answer:
Q: is there separate license for DVM?
Q: Is SAP Data Volume Management a part of SAP Information Lifecycle Management?
A: SAP ILM can be used in conjunction with DVM
Q: Is the data from the readiness check that calls out open aged data elements. Is that something that date of a volume management takes care of or is it a different topic entirely
A: DVM – assumes completion; business process optimization – value map for that
Q: IS DVM available for ECC systems as help to down-size our system prior to moving to S4 HANA?
Q: How can we tell if we have a DVM issue?
A: SAP Note – check – red rating in early watch report; value map has details of note
Q: What are the best practice residence times you mentioned during the webcast?
A: anything older than 2 years old; Basis – spool – 10 days, app logs – 6 months, work items, 18 months
Q: is the expert guided session no cost?
A: Enterprise support customers – contingency #
Q: Is DVM cloud application is Licensed separately from on premise SolMAN?
A: no license for support launchpad
Q: Do you know how long Data Aging will be supported?
A: cannot give a date
Q: Can data archived in ECC still be accessed in SAP S/4HANA?
A: yes, it can; see that in FI areas, audit related transactions
Q: Who can join the DVM Value Map?
A: any customer with an Enterprise Support Contract; check link
What do you think? I implemented the Cloud DVM application following this webcast; I encourage you do the same. Thanks to Damian McCarthy, SAP, for this presentation.