Compressing Real Time BCS cube - Postprocessing consequences
We are considering the option of compressing the cube, a BCS real time acquisition data cube. This option was tried in the past, but eventhoug the compression was technically successful we did find many troubles on the BCS side.
The problem occurred in the customized task in BCS. Such task is accessing to reading the data from the BCS cube using method read of class cl_rsdri_infoprov. Such method only treats data which RequestID is filled; so once compressed becomes useless for our current purposes.
We have been looking for an alternative standard method, but all forums are recommending using the mentioned one.
Is there an alternative solution for another standard method or all the methods related to reading data from the cube are reading data only which request ID is filled?
Thanks in advance.