Hierarchy
EA-FIN (Software Component) EA-FIN⤷
RE-FX-MI (Application Component) Migration⤷
RE_MI_CL (Package) RE: Migration RE Classic => RE-FX
IMG Activity
| ID | REFXV_TIVMISETMEAS | Master Data: Define Measurement Types for Area Type and Apportionment Unit |
| Transaction Code | S_XEN_65000026 | (empty) |
| Created on | 20050718 | |
| Customizing Attributes | REFXV_TIVMISETMEAS | Master Data: Define Measurement Types for Area Type and Apportionment Unit |
| Customizing Activity | REFXV_TIVMISETMEAS | Master Data: Define Measurement Types for Area Type and Apportionment Unit |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | REFXV_TIVMISETMEAS |
Use
In Classic RE, the system recognizes the area type and the apportionment unit. For rental units, the system can automatically copy the value of one or more area types to an apportionment unit. In addition, you can define per usage type which area types are included in the calculation of the reference area. The reference area is used whenever the size of the rental object is needed but no distinction was made as to which area type is meant. For example, you can define the area type "usable area" as the reference area for the usage type "Store," whereas you can define the area type "residential area" as the reference area for apartments.
In RE-FX, the system no longer recognizes the area type and the apportionment unit. Instead the system uses measurement types, to which measurement values are assigned for given time periods.
In addition to these measurement types, you can define total measurement types. For these measurements, the system automatically totals the values of the assigned individual measurements, taking into account the time-dependence of the values.
Since in RE-FX there is no longer a reference area defined in relation to the usage type, you have to specify a total measurement type to replace it (see below, under "Option Rate Determination").
The measurements in RE-FX are used for the following, for example:
- Service charge settlement
On the settlement unit, you define which measurement type is used for apportioning the values. (You could also define several measurement types with different percentages.)
Normally you use a total measurement type for this (such as, Residential/usable space, A200 in standard Customizing).
This corresponds to assigning the same apportionment unit to different area types in Classic RE (in standard Customizing, apportionment unit 12). - Option rate determination
On each object, for which an option rate can be determined, you defined which option rate method is used for calculating the option rate. The option rate method can be assigned to a measurement type. Then the system determines the option rate from the ratio of the measurements for this measurement type of the opting and non-opting rental objects that are subordinate to the object.
For determining the option rate according to area ratio, you would normally use the same total measurement type that is also used for service charge settlement.
Caution
Define a new total measurement type in Customizing for RE-FX in the following case: In your system you currently have reference areas that are not synchronous with an apportionment unit, and you need objects with the corresponding usage types in option rate determination.
After the Customizing conversion is complete, assign the individual measurement types, which arose from the area types comprising the reference area, to this total measurement type.
Change the option rate method according to area ratio so that it relates to the newly defined total measurement. - Calculation of conditions
For calculating conditions, you can enter a unit price for each measurement. The basis can be any measurement you choose.
Unlike the area-based conditions in Classic RE, conditions in RE-FX automatically reflect time-dependent changes to the measurement value. Therefore, if the measurement of a contract object changes, then the system automatically charges a higher price to the tenant in the next periodic posting run.
The migration assumes that all conditions flagged as area-based are to be migrated in this manner. If you do not want this, you either have to adjust the migrated contracts after the migration, or you have to remove the area-based indicator from the Classic RE contracts before the migration. - Reporting
We recommend creating a report profile so that you can display the measurements of your objects in columns in your reports. You can create report profiles after the conversion of Customizing is completed.
Requirements
Standard settings
Activities
In the previous step, the system analyzed which area types and which apportionment units are contained in your Classic RE data. It then filled the table, which you process in this step, with those values.
- For area types, to which an apportionment unit is not assigned in Classic RE Customizing, the system fills the area type, but not the apportionment unit (shown as "0").
- For area types, to which an apportionment unit is assigned to in Classic RE Customizing, the system fills the area type and the apportionment unit. Keep in mind that the same apportionment unit can be assigned to multiple area types. In the case of multiple assignment, the system creates a total measurement for RE-FX. This total measurement is shown in an additional row (in which the apportionment unit, but not the area type, is entered). The Total Measurement indicator is set there. In standard Customizing, for example, this is the case for apportionment unit 12, to which the area types living area and usable area are assigned.
- For apportionment units, to which no area type is assigned, the area type is empty (shown as "0").
For all area types and apportionment units that you want to copy to RE-FX, enter the key of the measurement type in the Measurement Type column (or leave the proposed value). You can also change the texts.
Note that a given key for a measurement type can only appear in one row. Otherwise the system cannot make the conversion.
The ForApport. (for apportionment) indicator shows that an apportionment unit is used on settlement units. For these apportionment units, it is mandatory that you enter a measurement type.
It is advisable to enter a target measurement type for all rows in which the area type or apportionment unit is entered for at least one object. The exception is if you no longer need apportionment units (because they were entered twice, or are no longer needed for settlement, for instance).
Set the Area ratio indicator for at most one measurement type and the For cubic ratio indicator for at most one measurement type. The basic components (shares) for external heating expenses settlement (copied from Classic RE Customizing) are each also allowed to be assigned to only one measurement type.
In the Convert Customizing step, the system automatically creates the measurement types and their texts. The measurement types, for which the Total Measurement indicator is set, are defined as total measurement types. The system assigns the individual measurement types of the same apportionment unit to these total measurement types.
During the conversion of the application data, the areas and apportionment factors are migrated to the measurement values. For measurement types that are not defined, the value is not copied.
Note that the migration ignores the Area type total indicator from Classic RE. This indicator was only used for checks in Classic RE. In RE-FX, this is no longer necessary. You can define a measurement type as a total measurement type and allow manual changes. You would have to do this after the migration, if needed.
Example
Business Attributes
| ASAP Roadmap ID | 152 | Design data acquisition |
| Mandatory / Optional | 1 | Mandatory activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | REFXV_TIVMISETMEAS | 0 | ALN0000041 | Migration |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| V_TIVMISETMEAS | V - View | SM30 |
History
| Last changed by/on | SAP | 20050718 |
| SAP Release Created in | 600 |
