on 2025 Feb 10 3:08 PM
Hi SAP,
We have recently implemented Automated DVM report generation for all our SAP Productions systems from our Solman System. SAP standard KBA is followed for the same.
An issue is observed for the periodic batch job for TAANA ANALYSIS in our Prod system. The job is long running for 50k+ sec and is also affecting the system performance during business hours.
As we have selected "Top 30 Objects" for processing mode in Solman Setup for DVM Automated Self Service.
Earlier we use to trigger this job manually through DVM Workcenter and it took ~10k sec for completion and no issue observed with the system as the job gets finished in non business hours. Here in manual execution, we had selected "SAP PROPOSED OBJECTS"
The "SAP-Proposed Basis & Cross Application Objects" option proposes tables/objects that are automatically identified by the system. - In particular, this means: Five tables/objects will be selected automatically by the data collection job. The selection of these objects is based on the evaluation of the current table sizes. Typically, the object list is populated with objects that are considered to be "easy to implement". Based on our general experience, these tend to be objects from the BC (Basis Component) or CA (Cross Application) areas. DVM measures such as archiving and deletion of such objects can normally be implemented by the IT department in isolation from and without negatively impacting the business departments. The list of proposed objects will change over time as you implement the relevant DVM measures. Application-related data objects will enter the list of proposed objects once the overall portion and potential of the "easy to implement" objects reduces in size.
Now we want to setup this "SAP Proposed Objects" processing mode in Solman Setup for DVM Automated Self Service. But we couldn't find that option in selection criteria.
Kindly help us to setup "SAP Proposed Objects" processing mode in Solman Setup for DVM Automated Self Service.
Request clarification before answering.
Dear Customer,
I have taken a detailed look at your query regarding the TAANA ANALYSIS job running for an extended period when the "Top 30 Objects" option is selected. The reason for this is that the job processes a significantly larger amount of data with the "Top 30 Objects" processing mode compared to when you manually create the analysis in "SM_WORKCENTER" using the "SAP Proposed Objects" option.
The latter option only includes five tables/objects selected by the data collector job. Given this, it is expected for the TAANA job to take a longer time to run when the "Top 30 Objects" option is selected. I understand that this might not be the answer you were hoping for, but it's a result of the larger data processing involved.
Alternatively, as the duration of the TAANA ANALYSIS job is influenced by the size of the table/database in your system. The only method to decrease the runtime is by limiting the scope of the DVM Analysis. Since you have selected the 'Top 30 Objects' as the Processing Mode, you could consider reducing the number of objects in scope to decrease the job's runtime. The options available in DVM Setup are pre-set for automated self-service.
However, if you wish to proceed with a custom scope, you will need to manually create the analysis. I hope this information helps you in managing the runtime of your TAANA ANALYSIS job more effectively.
I hope this answers your query on this topic. Thanks.
Best regards,
Luiza
SAP Support
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 17 | |
| 8 | |
| 7 | |
| 6 | |
| 4 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.