Hierarchy
⤷ BW-WHM-MTD (Application Component) Metadata (Repository)
⤷ RSD (Package) BW: Data Basis InfoObjects and Core Services
Basic Data
Data Element | RSDTRANSACT |
Short Description | Real Time / Direct Update |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | RS_BOOL | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
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 | Real Time |
Medium | 15 | Direct Update |
Long | 25 | For Direct Update |
Heading | 10 | Dir.Update |
Documentation
Definition
Real-time InfoCubes differ from standard InfoCubes in their ability to support parallel write accesses. Standard InfoCubes are technically optimized for read accesses to the detriment of write accesses.
Real-time InfoCubes are used when creating planning data. The data is simultaneously written to the InfoCube by multiple users. Standard InfoCubes are not suitable for this. They should be used if you only need read access (such as for reading reference data).
Real-time InfoCubes can be filled with data using two different methods: Using the BW-BPS transaction for creating planning data and using BW Staging. You have the option to switch the real-time InfoCube between these two methods. From the context menu for your real-time InfoCube in the InfoProvider tree, choose Switch Real-Time InfoCube. If Real-Time InfoCube Can Be Planned, Data Loading not Allowed is selected by default, the Cube is filled using BW-BPS functions. If you change this setting to Real-Time InfoCube Can Be Loaded with Data; Planning Not Allowed, you can then fill the Cube using BW Staging.
For real-time InfoCubes, a reduced read performance is compensated for by the option to read in parallel (transactionally) and an improved write performance.
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 20B |