Solution : https://service.sap.com/sap/support/notes/333260 (SAP Service marketplace login required)
Key words :
terms business information warehouse, functional module rsapo_close_trans_request adopts, solution import support package 07, longer completely identical, possibly immediately read, current write request, data mart scenario, data request exceeds, traditional bw users, sem-bps reason
Related Notes :
| 613512 | Writing new characteristic values via SEM write interface |
| 564769 | BW 2.x: Transactional InfoCube incorrect data loading |
| 538565 | Automatic compression does not work with trans. cubes |
| 447636 | Import reported financial data from the BW System |
| 411725 | Questions regarding transactional InfoCubes |
| 408258 | Query with variable 0S_RQMRC displays no data |
| 406625 | Data extraction from a transactional InfoCube |
| 389529 | NORMAL instead of BITMAP indexes on E fact table |
| 385812 | Real-time-update into BW: Transactional InfoCubes |
| 385163 | Partitioning on ORACLE since BW 2.0 |
| 382744 | Bex and SEM-BPS display different data |
| 364598 | Loading data into transactional InfoCubes |
| 356333 | BW: ORA-28604 during query execution |
| 351107 | BPS0: Transactional InfoCubes |
| 339812 | Incorrect indexing of F-fact table on Oracle |