Solution : https://service.sap.com/sap/support/notes/1009987 (SAP Service marketplace login required)
Summary :
When executing queries in a MultiProvider setup, it's observed that the MultiProvider may only read part of the data from the underlying part providers. This occurs mainly when there is a mismatch in characteristics between the MultiProvider and part provider, specifically in scenarios involving compounded characteristics. For instance, if characteristic C in the MultiProvider is compounded with V, but the part provider identifies only V and not C, under filters, part providers return partial data, reflecting the subset that aligns with queried conditions. This was handled improperly in earlier SAP versions (SAP NetWeaver 3.x), assigning an incorrect SID of zero in such mismatch areas which lead to data inconsistencies manifested as hash symbols (##) under compound characteristics. From SAP NetWeaver 2004s onward, stricter data consistency requirements necessitated corrections, ensuring correct SIDs and comprehensive data retrieval across version relaunches.
Key words :
transaction rsrt -> technical information -> query definition processor -> n_sx_report-sfc[, part provider returns data records, writing back data records, part provider pcenter delivers, 0costelmnt yields correct results, query definition, part provider returns, data manager returns, sap netweaver 2004s, pcenter part provider
Related Notes :
| 1624731 | Query termination: CL_RSDRC_MULTIPROV, _COLLECT_SFC_RETFL-03 |
| 1045683 | Compounding problem in MultiProvider (CMP problem) |
| 1011927 | No data in MultiProviders that have a compounding problem |
| 1011277 | No data in a very specific situation - MultiProviders |
| 955990 | BI in SAP NetWeaver 7.0: Incompatibilities with SAP BW 3.x |