Hierarchy
⤷ RE-FX (Application Component) Flexible Real Estate Management
⤷ RE_CA_CU (Package) RE: Customizing (IMG) and Area Menu
IMG Activity
ID | REFXV_TIVOROOUPDATE | Specify Control Parameters for Updating Offered Objects |
Transaction Code | S_AEN_10000221 | (empty) |
Created on | 20050105 | |
Customizing Attributes | REFXV_TIVOROOUPDATE | Specify Control Parameters for Updating Offered Objects |
Customizing Activity | REFXV_TIVOROOUPDATE | Specify Control Parameters for Updating Offered Objects |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | REFXV_TIVOROOUPDATE |
Use
Here you specify the basic settings for how the system generates offered objects for rental objects.
Requirements
Standard settings
Activities
The settings you make are for combinations of Rental Object Type and Usage Type that you want to search for using the real estate search. For example, you might not want to rent out vacant rental spaces again in exactly the same form. (You might only want to rent them out again from the pooled space, after the rental space has been returned to it.) In that case, you do not make any settings for the Rental Space object type.
You specify the following for each combination of rental object type and usage type:
- Consideration Period
Here you enter the number of months in advance of its becoming vacant that a rental object should be available in the real estate search.Example:
Notice is given on an apartment in January 2005. The notice date is June 30, 2005. If you enter a consideration period of at least 6, then the system already generates an offered object for the apartment when the notice is activated. Any real estate searches looking for an apartment starting from July 1, 2005 will then find this apartment immediately. If you enter a smaller number of months for the consideration period, then a search in January cannot find the apartment that is becoming vacant in July.
The system uses the number of months you enter for the consideration period to determine when offered objects are generated for the rental objects. The offered objects are generated using the RFREOROFFEROBJECTSCREATE report. (We recommend you schedule this report as a monthly batch job.)
If you do not enter a consideration period, then the system generates offered objects as soon as the vacancy becomes known, no matter how far in the future the vacancy is. In that case, you do not have to run the update report RFREOROFFEROBJECTSCREATE regularly. - Vacant Days
Here you enter the minimum number of days a rental object has to be vacant before the system generates an offered object for it. If you leave this field blank, the system creates an offered object for a rental object even if it is vacant for only one day.Example:
You enter a consideration period of 5 months for the apartment on which notice was given in January for June 30, 2005. In January a new lease beginning on August 1, 2005 is signed for the apartment.
At the beginning of February, the RFREOROFFEROBJECTSCREATE report updates the offered objects.
If you entered a value between 1 and 31 days for the vacant days, then the system creates an offered object for this apartment for the period from July 1, 2005 to July 31. 2005. The search, however, only finds this object if you search explicitly for an apartment for a limited time period in July 2005.
If you enter a value greater than 31, then the system assumes that it is not beneficial to lease for this short period, and does not create an offered object for this apartment. In that case, you would not find this apartment during the search, even if you explicitly search for an apartment for this limited time period.Recommendation:
For each usage type, set the number of vacant days to the minimum number of days that a fixed-term lease should have in order for the rental to be cost effective. - Key Date Data
Certain data that is time-dependent on the rental object (conditions, measurements, fixtures and fittings characteristics) is not managed as time-dependent on the offered object. The purpose is to improve performance and increase clarity. Therefore, the system needs to know the key date up to which you want the data of the offered object to be valid. If you leave the Key Date Data field blank, then the system uses the first day of the vacancy period as the key date. This may not be accurate, if renovations are regularly done at the beginning of the vacancy period and these renovations change the fixtures and fittings, the measurements, and conditions of the rental object. To address this problem, you can enter the number of days that are added to the start of the vacancy period in order to determine the key date.
When renovations are planned, you should enter the planned changes on the rental object with a valid-from date that, at the latest, is the same as the resulting key date, so that the changes are already available in the search. - Min. Meas. %
Here you enter the minimum percentage of the measurement of a pooled space that has to be available in order for an offered object to be generated. For other rental object types, the system ignores the value.
Since the pooled space itself can never be leased out, the generation of an offered object for a pooled space is not triggered by the start of the vacancy period for the pooled space. Instead, generation of an offered object is triggered when this minimum percentage of available measurement values is exceeded.
Example
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-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_TIVOROOUPDATE | 0 | AEN0000003 | Offer and Rental Request |
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_TIVOROOUPDATE | V - View | SM30 |
History
Last changed by/on | SAP | 20050105 |
SAP Release Created in | 600 |