(2311) Release notes

Owned by Marian Vidra
Last updated: Dec 04, 2023
2 min read

Improvements

Writer

Performance: Loaded data is now filtered based on all key fields of the offloading condition, ensuring improved efficiency. Previously the filtering was done only if the offloading condition was set using all key fields.

DataProvider Wizard

Offloading condition refinement: The offloading condition for the ADSO Data Acquisition Layer can also be defined based on the REQTSN field, providing more logical control of data offloading for this type of ADSOs.

Updates

Offloading analysis

Size statistics and query usage enhancement: Size statistics and query usage were not collected during the offloading analysis. This has been corrected to ensure accurate data analysis.

“Refresh results” enhancement: The results of the offloading analysis were not refreshed after the timestamp range of the analyzed data was changed. This issue has been resolved.

Aggregation job optimization: The aggregation job was ignoring the timestamp range defined for the default offloading variant and aggregating data without any time restriction, leading to incorrect results. This has been corrected.

KPI collection improvement: KPIs were not being collected for InfoProviders that had 0CALWEEK as the split characteristic with initial values. This behavior was optimized so no initial values are brought to the analysis output.

ADSO type alignment: ADSO's types did not match between the Offloading analysis and the Outboard Datatiering. This has been aligned.

Writer

Repeated DTP load activation: Previously, if a repeated DTP load activation failed during the deletion phase and had already deleted some records from the archive, it would encounter an inconsistent index. This issue has been addressed.

DTP load optimization: DTP loads on a BW/4HANA system were failing in cases where the source object was not an InfoProvider or Datasource. This functionality has been corrected.

Lookup analysis

Correctness improvement: The lookup analysis was displaying inaccurate results about the support status of the lookups. This has been corrected.