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_TIVMIUSGTYPE | Rental Object Master Data: Specify Different Usage Types |
| Transaction Code | S_AER_95000026 | (empty) |
| Created on | 20051026 | |
| Customizing Attributes | REFXV_TIVMIUSGTYPE | Specify Different Usage Types for RE-FX |
| Customizing Activity | REFXV_TIVMIUSGTYPE | Specify Different Usage Types for RE-FX |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | REFXV_TIVMIUSGTYPE |
Use
You use this table so that you can have different usage types for rental objects in RE-FX than you used in Classic RE.
It makes it possible to group together various usage types of Classic RE under one usage type in RE-FX.
Before you can create new usage types, you have to define them in Customizing. Keep in mind that some settings are dependent on the usage type, and these settings must have been made consistently (for example, rental object types for usage type, screen sequences for usage type, option rate methods for usage type).
In addition, you can specify that additional fixtures and fittings characteristics are created for rental units with a given usage type in RE-FX.
Here there are two options. One is to enter a specific characteristic for apportionment loss risk (ALR) for apartments that are publicly subsidized. The system then sets this characteristic if the rental unit being migrated is publicly subsidized (based on the usage type and/or the "time-period for public subsidy"). If this characteristic is not set here, then, in the case of such publicly subsidized apartments, the system sets the characteristic that was entered in the Global Settings dialog.
The other option: You can enter a fixtures and fittings characteristic that the system always sets in addition, if the rental object being migrated had the specified usage type in Classic RE.
Example
There are two different usage types defined for apartments in standard Customizing of Classic RE:
0001 Privately financed accommodation
0002 Publicly subsidized accommodation
Based on the assigned usage type, Classic RE is able to recognize that, according to German tenancy law, an apportionment loss risk is calculated.
In RE-FX, the system no longer calculates the apportionment loss risk solely based on the usage type. Instead, the calculation is also dependent on a fixtures and fittings characteristic on the rental object. The fixtures and fittings characteristic is time-dependent, so you can set this fixtures and fittings characteristic for the specific time period during which the apartment is actually publicly subsidized.
This means that you can combine the two Classic RE usage types into one usage type "Apartment" during the migration (we recommend re-using usage type 0001). You can change the text of the usage type to "Apartment."
In this table, you assign usage types 0001 and 0002 of Classic RE to usage type 0001 of RE-FX. And for usage type 0002, you also specify the fixtures and fittings characteristic that is generated on the rental object. You first have to create the fixtures and fittings characteristic (PUBL in standard Customizing ) in Customizing. In order for the service charge settlement to run correctly, you also have to define the surcharge schema before the first settlement. Surcharge schema "DE" is predefined in standard Customizing. You can use it as a template and copy it.
If you do not enter new usage types, the system uses the usage types from Classic RE in RE-FX.
Requirements
Standard settings
In the first step, the system analyzed the usage types that are used in rental objects in Classic RE, and entered these in the first column.
Activities
Assign a different usage type, and possibly a fixtures and fittings characteristic, where it seems appropriate (see above).
Note
Do not, under any circumstances, delete usage types you no longer need! Otherwise you can no longer display your Classic RE data.
Business Attributes
| ASAP Roadmap ID | 252 | Prepare Data Transfer Fields |
| Mandatory / Optional | 2 | Optional 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_TIVMIUSGTYPE | 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_TIVMIUSGTYPE | V - View | SM30 |
History
| Last changed by/on | SAP | 20051026 |
| SAP Release Created in | 700 |
