Hierarchy

⤷

⤷

Basic Data
Data Element | UC_REPORTINGCUBE |
Short Description | InfoCube for Reporting (Delta Load) |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | RSINFOCUBE | |
Data Type | CHAR | Character String |
Length | 30 | |
Decimal Places | 0 | |
Output Length | 30 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Rep.Cube |
Medium | 20 | Reporting InfoCube |
Long | 40 | InfoCube for Reporting (Delta Load) |
Heading | 20 | Reporting InfoCube |
Documentation
Definition
A reporting InfoCube is a conventional basic InfoCube used to store the totals records in a format suitable for reporting.
Use
The reporting InfoCube is used in the delta load scenario. In a delta load scenario, a data mart interface is used to pass the totals data from the transactional InfoCube into the reporting InfoCube. The data mart interface prepares the data for reporting.
Reporting functions have direct access to the data in the reporting InfoCube. This speeds up queries to the reporting InfoCube as opposed to queries to the virtual InfoProvider because reports that access the virtual InfoProvider need to first prepare the totals records from the transactional InfoCube for reporting output.
Dependencies
Realtime reporting is generally not achievable with queries to the reporting InfoCube. Such queries disregard the most current data that has not yet been transferred from the transactional InfoCube.
If you want to have realtime reporting in the delta load scenario, you need to define queries to a MultiProvider. A MultiProvider is comprised of the virtual InfoProvider and the reporting InfoCube.
Example
History
Last changed by/on | SAP | 20060208 |
SAP Release Created in |