Hierarchy
⤷ EC-CS (Application Component) Consolidation
⤷ FC00_UC (Package) Cons: General consolidation (cannot be assign.to FC01-FC09)
Basic Data
Data Element | FC_REF_RVERS |
Short Description | Reference version |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | FC_REF_RVERS | |
Data Type | CHAR | Character String |
Length | 3 | |
Decimal Places | 0 | |
Output Length | 3 | |
Value Table |
Further Characteristics
Search Help: Name | FC_RVERS | |
Search Help: Parameters | RVERS | |
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 | RefVersion |
Medium | 15 | Refer. version |
Long | 20 | Reference version |
Heading | 4 | RVer |
Documentation
Definition
The reference version in a report is the version for which the system determines the composition of consolidation units a given consolidation group has for a certain date when the transaction data is selected. If the organizational units (consolidation unit, partner unit or investee unit) have version and date sensitive attributes, the reference version also determines the version for the attributes of an organizational unit.
In addition to the reference version, consolidation version can also be specified. The characteristic "consolidation version" determines the consolidation version to be used to read the transaction data, whereas the reference version determines the version to be used to read the consolidation group hierarchy and the attributes. The consolidation group hierarchy and the attributes are the basis for interpreting the transaction data.
If no reference version is specified, then the characteristic "consolidation version" is used for the hierarchy breakdown and the attribute determination. In the case, the consolidation version must be clearly defined for each cell (or entire row or column) of the report; it also always determines the version of the transaction data to be selected.
The reference version may be used in a report only if the consolidation group, the totals consolidation group or a version- and date-sensitive attribute exists. If the reference version is not defined in the general selection condition in a form definition, but instead is defined in the cell definition, then the reference version must be specified in all cells.
Characteristics related to the reference version are reference fiscal year and reference period.
Example
Version Comparison: Versional Restatement via Reporting
You define a form with a coordinate, in which you specify a single value in the general selections for each of the following parameters: Dimension, Totals Consolidation Group, Fiscal Year, and Reference Version. You define two columns which use the same key figure. In the first column you specify the consolidation version "100", in the second column you specify a different consolidation version of "200". The report then shows in both columns the transaction data for both consolidation versions; however, the report uses the reference version as the basis for the composition of the consolidation group. If you specify as the reference period the consolidation version of the first column ("100"), then the data of the second column is "re-interpreted" by the report. This means that the data of the second column is selected for consolidation version "200". But the composition of the consolidation group is based on version "100". Thus, the report is able to show a breakdown by the characteristic consolidation group using a hierarchy for consolidation version "100".
History
Last changed by/on | SAP | 19990520 |
SAP Release Created in |