SAP ABAP Data Element ROSTOCK (DataSource generates an initial non-cumulative)
Hierarchy
☛
PI_BASIS (Software Component) Basis Plug-In
⤷ BC-BW (Application Component) BW Service API
⤷ RSUM (Package) BW Service API: Metadata
⤷ BC-BW (Application Component) BW Service API
⤷ RSUM (Package) BW Service API: Metadata
Basic Data
Data Element | ROSTOCK |
Short Description | DataSource generates an initial non-cumulative |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | ROFLAG | |
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 | Ini. N.C |
Medium | 15 | Init. Non.-Cum. |
Long | 30 | Initial Non-Cumu. DataSource |
Heading | 40 | DataSource Generates Init.Non-Cumulative |
Documentation
Definition
This field shows that the DataSource constructs an initial non-cumulative. A non-cumulative value in BW is a key figure that ensures that the OLAP includes in calculations, certain 'virtual records' from the fact table together. A typical example of a non-cumulative is an account balance. To supply an InfoCube containing a non-cumulative, with data, you require at least two DataSources. One, to construct the non-cumulative (meaning to deliver the initial account balance), and one to deliver the cumulative value for this non-cumulative (meaning the crediting and debiting of the account).
The following extraction methods can be combined with a DataSource for the opening balance:
- 'V' - Extraction using a view
- 'F1' - Extraction using a function module
- 'F2' - Extraction using a function module (simplified interface)
History
Last changed by/on | SAP | 20080415 |
SAP Release Created in |