Address Management

Copyright(c) 2018 by Nixon Vunganai.
All rights reserved.
Neither this document nor any part of it may be copied or reproduced in any form or by any
means or translated into another language, without the prior consent of Nixon Vunganai. The
information contained in this document is subject to change without notice.
WHATSAPP +255738656506
INTRODUCTION 8
ADDRESS MANAGEMENT 8
Maintain Address and Person Number Range 8
International Settings 9
Choose Address Screen Layout 9
Activate International Address Versions 10
Set Layout of Address Screen for International Address Versions 12
Activate Regional Structure Check for International Address Versions 12
Forms of Address and Name Components 13
Maintain Forms of Address 13
Maintain Academic Titles 14
Maintain Name Prefixes 15
Maintain Titles and Name Supplements 15
Maintain Name Formatting Rules 16
Maintain Reason for Non-Delivery 17
Define pager services 18
Maintain Transport Zones 18
Duplicate Check 19
Activate Duplicate Check and Determine Limit for BAPIs 19
Set Limit for Duplicate List in SAP Dialog Boxes 20
Regional Structure/City File 20
Import Reference Data 21
Postal Codes 21
Maintain Number Ranges for Postal Codes 21
Create Postal Codes Individually 22
Change Postal Codes Individually 22
Display Postal Codes Individually 22
Cities 22
Maintain Number Ranges for Cities 23
Create Cities Individually 23
Change cities individually 23
Display Cities Individually 24
Streets 24
Maintain Number Ranges for Streets 24
Maintain Street Type 25
Create Streets Individually 25
Change Streets Individually 25
Display Streets Individually 25
Define Regional Structure Groups 26
MASTER DATA 26
Master Data 26
Basic Settings 26
Measurements 26
Define Measurement Types 26
Define Total Measurements 28
Define Derivable Measurements 30
Implement Enhancements ( BAdI ) 32
Define Allowability of Measurements by Object Type 32
Prevent Overwriting of Total Measurements 33
Define Tenancy Law 33
Usage View 33
Usage View 33
General Settings for Multiple Object Types of the Usage View Fixtures and Fittings Characteristics 34
Define Fixt./Fittings Characteristics for Buildings, ROs, and Parcels 34
Specify Structure of Fixt./Fittings Characteristics Independent of RLR 35
Infrastructure Characteristics 37
Define Infrastructure Characteristics 37
Specify Basis for Measuring Distance as Time 37
Neighborhood: Define Preferred Values 38
Suppress Leading Zeros in Object Keys 38
Define Functions of Objects 39
Business Entity 39
Number Range for Business Entity 39
Regional Locations 40
Layer 40
District Locations 40
Transport Connection 40
Maintenance Areas 41
Dialog 41
Change Screen Layout 41
Screen Layout 41
Field Groups 41
Views 42
Sections 42
Screens 43
Screen Sequences 43
Events 44
Tables 44
Number Assignment, Validation, Substitution 44
Implement Enhancements (BAdI): "Overviews" - Own 45
Building 45
Building Number Range 45
Building Condition 46
Building Types 46
Main Usage Types 46
Dialog 48
Screen Layout 49
Field Groups 49
Views 50
Sections 50
WHATSAPP +255738656506
Screens 51
Screen Sequences 51
Events 52
Tables 52
Land 53
Number Range for Properties 53
Municipality Key 54
Local Subdistricts 54
Property types 54
Location Qualities 54
Ground Types 54
Statuses 54
Usage Types in Development Plan 55
Usage Types in Land Use Map 55
Heritable Building Right Types 55
Dialog 55
Screen Layout 55
Field Groups 55
Views 57
Sections 57
Screens 58
Screen Sequences 58
Events 59
Tables 59
Rental Object 60
Number Range for Rental Objects 60
Usage Types 61
Usage Types 61
Usage Type per Rental Object Type 62
Usage Types Allowed for Rental Spaces per Pooled Space 62
Measurement Types Allowed per Rental Object Type 63
Measurement Types per Usage Type 64
Attributes 65
Parts of building 65
Locations on Floor 65
Floor Descriptions 65
Reasons for different rent increase 68
Account Determination Values 68
Vacancy 68
Define Vacancy Reasons 68
Determine Vacancy Reason Based on Vacancy Event 69
Determine Vacancy Reason Based on Notice Reason 70
Dialog 70
Screen Layout 71
Field Groups 71
Views 72
Sections 73
Screens 74
Screen Sequences 74
Events 75
Tables 75
Architectural View 76
Architectural View 76
Architectural Object Type 77
Create Architectural Object Types 77
Assign Icons to Architectural Object Types 79
Define Allowed Object Type Hierarchy 79
Specify Rule for Determining Object ID 80
Define Possible Functions per Architectural Object Type 81
Specify Measurement Types per Architectural Object Type 82
Limit Measurement Types by Function 82
Specify Fixt/Fittings Characteristics for Architectural Objects 83
PM Integration 84
Make Settings per Architectural Object Type 84
Define PM Notifications per Object Type 84
Dialog 85
Screen Layout 85
Field Groups 85
Field Groups 85
Field Status 86
Field Status per Architectural Object Type 86
Views 87
Sections 87
Screens 88
Screen Sequences 88
Events 89
Tables 89
Synchronization of Architecture and Usage 89
Rules for Synchronization of Architecture and Usage 89
Implement Enhancements (BAdI): Create Usage Object for 90
Implement Enhancements (BAdI): Change Usage Object for 91
Enhancements 92
Implement Enhancements (BAdI): Validation and Substitution 92
WHATSAPP +255738656506
Implement Enhancements (BAdI): Number Assignment 92
Implement Enhancements (BAdI): Create Usage Object for 93
Graphic: SAP 3D Visual Enterprise 94
Overview: Integration Visual Enterprise 94
Define BADI_RECA_CAD_SERVICES 95
Define BADI_RECA_CAD_PROCESS_SYNC 96
Define BADI_REEX_ACTIONS_VE 97
CONTRACT 99
Number Assignment 99
Number Range for Contracts 99
Automatically Generate Contract Number 99
Contract Type 99
Define Contract Types 99
Objects 102
Permitted Object Types per Contract Type 102
Define Contract Types to Propose for Usage Type 103
Renewal 104
Renewal Rules 104
Notice 105
Notice 105
Notice Rules: Period Regulations 106
Notice Rules: Deadline Regulations 106
Notice Procedures 107
Notice Reasons 108
Reasons for Rejection 108
Attributes 109
Account Determination Values 109
Industry System and Industry 109
Define Measurements for Contract 110
Security Deposit Agreement 110
Security Deposit 110
Contract Types for Security Deposit Agreement 111
Security Deposit Type 111
Dialog 112
Screen Layout 112
Field Groups 112
Field Groups 112
Field Status 112
Field Status per Contract Type 113
Views 114
Sections 114
Screens 114
Screen Sequences 115
Events 116
Tables 116
Contracts: Number Assignment, Validation, Substitution 116
Implement Enhancements (BAdI): "Overviews" - Own Evaluations 117
GENERAL SETTINGS FOR MASTER DATA AND CONTRACT 117
Assignment of Objects from Other Components 117
Assign Functional Locations/Fixed Assets/Projects/CO Orders 117
PM Integration 119
PM Integration: Make Settings per Object Type 119
Define PM Notifications per Object Type 120
Implement Enhancements for PM Integration ( BAdI ) 120
Terms 121
Specify Default Text for Naming Terms 121
Resubmission 122
Define Resubmission Reasons 122
Define Resubmission Rules 122
Make Settings per Object Type 123
Set Default Values for Reminder Rules and Enter Automatically in Contracts 124
Authorizations 127
Define Authorization Groups 127
User Status 128
User Status and Activity Control 128
Obsolete User Status 132
Document Management 132
Document Management 132
Records Management 133
Make Basic Settings for Records Management 133
Implement Enhancement for Records Management ( BAdI ) 134
Document Management System 136
Define Document Types 136
Assign Screen for Object Link 137
Additional Texts 137
Define Categories for Additional Texts 137
Enhancements 139
Implement Enhancements (BAdI): "Overviews" - Own Evaluations 139
Implement Enhancements (BAdI): Default Values for Assigned Assets 139
Implement Enhancements (BAdI): Default Values for Functional Location 140
Implement Enhancements (BAdI): Search Help 141
WHATSAPP +255738656506
INTRODUCTION
Welcome to the fascinating world of SAP. This book helps you crack the tricks of mastering SAP HANA
Customization
Address Management
Business Address Services (BAS) maintain and manage addresses for various business objects
using a uniform maintenance interface. Knowledge Warehouse documentation
Maintain Address and Person Number Range
The addresses used in SAP applications are primarily stored in the tables of the Business
Address Services (BAS). Addresses are identified by an internal number, assigned by the SAP number
assignment.
The same number range is used for the Business Address Services tables from Release 4 (ADRC, ADRP,
etc.) as for addresses in the tables SADR/SADRP in previous releases.
Standard settings
Number ranges "01" and "10" are delivered. Number range "10" is needed for some areas in SD and
must not be changed.
Recommendation
You can change the number range "01" if required, but see the note under "Further notes".
You may not change the characteristic of the number range interval "01" to "external number assignment.
The system does not support external number assignment for addresses.
Activities
To change the number range for Business Address Services, proceed as follows:
1. Call the number range maintenance transaction by choosing "Execute".

2. Choose Change interval.
3. Maintain the interval values (from number, to number) for the number range "01".
(number range "10" must not be changed)
4. Save the entries.
Further notes
The following notes were valid until Release 4; from Release 4 the changed transport methods should
resolve the problems mentioned. The organizational measures for separating number ranges are only
needed for transports between 4 and 4 systems.
If you work in several systems or clients and want to transport address data - for instance with the
organizational units in Customizing - note that inconsistencies can occur when transporting addresses:
Problem
The key for the address file is an internal number which is assigned sequentially per system and
client. Problems can occur if the same number was assigned in the source system and in the target
system for two different addresses. The address from the source system is then not inserted in the
address file in the target system; the existing address in the target system ( with the same internal
number) is "changed", that is, it is overwritten with the data of the transported address and is no
longer available.
Solution
See OSS note 25182.
International Settings
Choose Address Screen Layout
The layout of the Business Address Services address maintenance screens can be configured globally.
You can currently choose between the variants:

001 Europe/standard
004 USA
005 Canada
013 Japan
In the variants for the USA and Canada, for example, the postal code is after the city and the house
number before the street, whereas in the standard variant, the fields are in the opposite order.
The value applies to all Business Address Services screens.
The settings apply to all applications in which Business Address Services are integrated, for example,
the Customer master, Vendor master, SAP Business partners, SD documents, Purchasing and Service
Management.
If you choose the 013 screen variant for Japan, you also have to change the "Key for Address
Formatting" for Japan in the country customizing function from 013 to 113.
The print format 113 corresponds to the Japanese address screen with the variant 013.
To access the country customizing function in ERP systems, call transaction OY01. In other SAP
systems, call transaction OY07.
WHATSAPP +255738656506
Standard settings
Europe/standard.
Activities
Choose the address layout according to the country-specific assignment.

Further notes
The setting can be overriden by users. To do so, users have to set the parameter
ADDRESS_SCREEN in their master record to 001 for Europe/standard, to 004 for USA, to 005 for
Canada, or to 013 for Japan.
Activate International Address Versions
You can maintain more than one version of an address at the same time, so an address can be held in
various character sets, such as Kanji characters and latin letters. For example, versions of customer
addresses are maintained in the the customer master data screen using Extras -> Address versions....
The character sets must be activated in the system.
Example
- The addresses are normally maintained in Japanese format (Kanji) in Japanese systems. The
addresses of foreign business partners (e.g. USA) are also entered or printed in the English
(international) format.
- In an American system all addresses are entered in English format . The addresses of Japanese
business partners or subsidiaries are also either also maintained and printed in Kanji format, or
maintained mainly in Kanji and also in English format.
Requirements
Different address versions can be maintained if the application uses the central SAP address management
(SAP address book) dialog functions.
This is the case, e.g. for customer and vendor master data in Release 4.
Address versions are not yet available for personnel master addresses (module HR), because they do
not use the central SAP address management (SAP address book) functions in Release 4.
Standard settings
SAP delivers the following version keys:

As of 4:
I International
K Kanji ( Japanese )
R Cyrillic
N Katakana (
Japanese ) H Hangul (
Korean ) As of 4C: A
Arabic
B Hebre
w
C Chine
se G
Greek
M Chinese trad.
As of SAP Web Application Server Release 60: T
Thai
The version keys are delivered inactive.
Recommendation
Activate the version keys required in your system.
If you need other versions not provided by SAP, you can create and activate your own entries in the
customer name space (keys 0 - 9).
Activities
To activate delivered version keys, proceed as follows:
1. Choose "Execute" to call the maintenance transaction.

2. Select active for the versions which are to be used in your system.
3. Save
To create version keys in the customer name space, proceed as follows:
1. Call transaction SM30.

2. Enter view name V_SAPTSADV and choose Maintain.
3. Do not change the entries delivered by SAP.
4. To create new entries, choose New entries.
5. Make the desired entries in the customer name space.
6. Mark active for the versions which are to be used in your system.
7. Save.
Further notes
The maintenance function for address versions is not intended for different spellings in just two
languages (city names, for example).
Instead, the maintenance function aims to enable different formats in different character sets (above all,
for extended or double-byte code pages).
WHATSAPP +255738656506
Set Layout of Address Screen for International Address Versions
Use
In addition to the setting "Select Layout of Address Screen", you can select for each
international address version which screen variant is used to display or maintain the address version.
For each international address version you can also determine whether this setting has priority over the
individual user parameter ADDRESS_SCREEN.
Requirements
This setting is taken into account only if the relevant international address version has been activated.
Standard settings
If no settings have been made, the settings apply that are described in the activity "Select Layout of
Address Screen".
Activities
Assign the layout of your choice to the international address versions that are used in your system.
Example
If you use the address version 'K' (Kanji), we recommend that you assign the layout '013' for Japanese
addresses. This is only necessary if you have not already selected '013' as the global setting.
Activate Regional Structure Check for International Address Versions
Use
As well as the City File Active setting that you can set in the general country settings, you can also
specify for which international address versions you want to activate the regional structure check (city
file check) for each country.
Requirements
This setting is evaluated only if the regional structure check is activated for the relevant country. The
setting for each country is made in the country settings (under General Settings in the IMG).
A prerequisite for the regional structure check is the existence of suitable reference data in the system.
Standard settings
If no settings are made for a particular country, then the following applies to checks made on addresses
for this country (provided the checks are activated in the general country settings):
The regional structure check is active for the SPACE address version.
The regional structure check is not active for address version other than SPACE.
Activities
For each country that has the regional structure check activated in the general country settings, proceed
as follows:
Activate the check for address versions other than SPACE for which you want it to run.
Deactivate the check for address version SPACE if the check is required for another version only, and
not for SPACE.
Example
1. For country Japan, you use the version SPACE for displaying the addresses in English, and
version 'K' (Kanji) for the Japanese display.
You have entered reference data in the Japanese display (Kanji) and want to check the Japanese
addresses against this reference data in version 'K' only.
a) For country Japan, in the general country settings, activate the flag "City file active" and the
flag "Postal codes on street level" if required. This activates the check for Japan in general.
b) In this activity, insert the following entry:
Country: Japan
Version: K
Active: Yes
This activates the check for version K for Japanese addresses.
c) In this activity, insert the following entry:

Country: Japan
Version: SPACE (type a blank character and choose ENTER)
Active: No
This deactivates the check for version SPACE for Japanese addresses, since you have only
entered the reference data for the Japanese display.
The check for version SPACE for other countries in unaffected by this, if the regional
structure check is also activated for other countries.
2. For country Japan, you use the version SPACE for displaying the proposal in Japanese, and
version 'I' (International) for the English display.
You have entered reference data in the Japanese display and want to check only the Japanese
addresses in the Japanese display against this reference data.
a) For country Japan, in the general country settings, activate the flag "City file active" and the
flag "Postal codes on street level" if required.
This activates the check for Japan in general.
The check is then active for version SPACE and inactive for version 'I' by default.
b) Further settings in this activity are not required in this example.

Forms of Address and Name Components
Maintain Forms of Address
The form-of-address texts of the Business Address Business standard are stored for each address in the
form of a language-independent key. For each key and each language a 30- character form-of-address
text can be stored centrally.
These form-of-address keys are also used for the SAP business partner.
WHATSAPP +255738656506
Use the "Person" and "Organization" indicators to determine which form of address is available for use in
which context.
Standard settings
All usual form-of-address texts are supplied. If you installed your system in several languages, you also
receive the translations in the respective languages.
Activities
1. Check the standard form-of-address texts for completeness

2. Maintain the necessary form-of-address texts if required:
a) Choose New entries.
b) Enter the key and the form-of-address texts. Set the "Person" or "Organization" indicator as
appropriate for the form of address.
c) Save your entries.
3. Translate the texts you maintained into the foreign languages available for the system:
a) Choose Edit -> Translation
b) Translate the required texts and save your work.
Further notes
The special forms of address for natural persons (for example, academic title or similar) in Business
Address Services and the SAP business partner are maintained separately and should not therefore be
mixed with the pure form-of-address texts in this activity.
Maintain Academic Titles
Name elements for natural persons (for example users, external correspondents) are held in several
separate fields in Business Address Services.
One of these is for all valid academic titles.
You can control how a name is composed from the elements.
Name format rules
Example
- Dr.
- Prof.
Standard settings
The standard system includes some academic titles.

Activities
Create the required academic titles.
Maintain Name Prefixes
Name elements for natural persons (for example users, external correspondents) are held in several
separate fields in Business Address Services.
One of these is for all valid name prepositions (such as "van" in names of Dutch origin).
Maintain rules for name composition
Example
- van
- von
- von der
Standard settings
The standard system includes some name prepositions.
Activities
Create the required name prepositions.
Maintain Titles and Name Supplements
Name elements for natural persons (for example users, external correspondents) are held in
several separate fields in Business Address Services. One of these is for all valid styles, ranks,
or titles.
Maintain rules for name composition
Example
- Viscount
- Baronet
WHATSAPP +255738656506
Standard settings
The standard system includes some styles, ranks, and titles.
Activities
Create the required styles, ranks, and titles.
Maintain Name Formatting Rules
The name components of natural persons are stored in several separate fields.
You can control how the name is formatted from out of the components according to country-specific
rules. If you do not specify any rules, the system uses a standard setting.
Example
The name composition format DE 01 is defined as follows:
US 01 1 TITLE ( form-of-address )
US 01 2 NAME_FIRST (first name)
US 01 3 PREFIX1 (name preposition) US 01 4
NAME_LAST (last name)
The following fields are used for a business partner: Form-of-address:

Mr
First name: Rene
Name preposition: van de
Last name: Kerkhoff
Country for name format DE
Name format 01
Using the rule DE 01, two formats are derived from these fields:
With form-of-address (TITLE): Mr Rene van de Kerkhoff

(The form-of-address text is language-dependent in this case; the language depends on the context)
Without form-of-address: Rene van de Kerkhoff ( languag-independent

)
The version without form-of-address is stored redundantly by the Business Address Services.
The version without the form-of-address is used for name formatting for print. In addition, the form-
of-address is issued according to country-dependent criteria in the address format, regardless of
whether or where the form-of-address is entered in the name format rule.
The format with form-of-address defined here, is intended for list output.
Standard settings
The standard system includes some name composition format templates.
Recommendation
In addition, enter the format that is the default format for your country in the field "Default Name
Format" in the country settings.
When you maintain master data, the country for the name format is not taken from the address because
an SAP business partner, for example, can have more than one address or even none
at all.
Instead, you have to enter the country in the field "Country for Name Format" in the name fields of the
person.
We recommend that you assign the users the user parameter NAMEFORMAT_COUNTRY. If this
parameter is filled in the user master data, the corresponding country is then proposed in the field
"Country for Name Format" when you create personal data (for SAP business partners, consumers in
the customer master record, users, and so on).
Activities
Create the required name composition formats.
Maintain Reason for Non-Delivery
You can record the reasons for non-delivery to street addresses and postal code addresses in Business
Address Services.
Applications can then analyze this information and react to it with application-specific measures.
An assignment table is required in application Customizing in order to control the analysis measures on
the part of the application.
The reasons for which the measure "Resend" is to be executed, for example, are stored in such an
application table.
Example of an application table:
Measure Measure text Reason for non-delivery Non-delivery text

0001 Resend 0003 Incomplete address
0001 Resend 0004 Illegible address
0002 Telephone information 0001 Unknown
0002 Telephone information 0002 Moved - address unknown
0003 Trace successor 0008 Deceased
Example
Examples of reasons for non-delivery include:
- Moved - address unknown
WHATSAPP +255738656506
- Deceased
- Company dissolved
Standard settings
The SAP standard setting contains some common reasons for non-delivery.
Activities
Create the required reasons for non-delivery. If necessary, maintain appropriate assignments in
application Customizing.
Define pager services
To transfer short messages to mobile devices (communication type PAG), you can define various
services within the Business Address Services.
Example
Pager services can be SMS (Short Message Service) or or RPA (Radio Page America), for example.
Activities
Maintain the pager services that are required for your system.
Maintain Transport Zones
In this activity, you can define transportation zones according to country and depending on your
company's needs. Transportation zones represent delivery recipient (ship-to party) regions or delivery
shipper (vendor) regions.
Use
After taking into account the ship-to party's transportation zone and other factors such as:
- Country of origin
and country of
destination
- Shipping
conditions -
Transportatio
n group,
the system automatically suggests a suitable route during sales order and outbound delivery processing.
Example
You can define transportation zones according to a country's zip code system.
Activities
Define the transportation zones you need for each country and enter the corresponding description.
Duplicate Check
Activate Duplicate Check and Determine Limit for BAPIs
In Business Address Services, there are interfaces for partner products for the attachment of tools for
duplicate check and error tolerant searches.
Depending on the SAP System, this function is available within the business partner management or the
customer and vendor master.
For this purpose, the partner product builds index pools (search pools) - mostly outside of the SAP
System - , with which the search then takes place.
In this activity, you can activate the duplicate check at the level of the index pools.
Additionally, you can enter for each index pool, from what level of similarity a record is to be valuated as
a duplicate for processing without dialog.
Example
Example: For SAP business partner 95, set 0 as the threshold if you want a business partner that has a
95% match with another record to be rejected as a duplicate (when processing without dialog).
Requirements
The prerequisite for the duplicate check is that a solution of a third-party provider is used and the
implementations for the Business-Add-Ins ADDRESS_UPDATE and ADDRESS_SEARCH are active
(transaction SE19).
Standard settings
WHATSAPP +255738656506
The duplicate check is not active in the presetting.
Further notes
For more information, see SAP Note 176559.
Set Limit for Duplicate List in SAP Dialog Boxes
Use
As of SAP Web AS 60, the SAP application can implement the SAP GUI dialog (display of hit list) for
the duplicate check itself.
Previously, the hit list was displayed in dialog boxes within the BAdI implementation (of a third-party
provider, for example).
For the SAP applications that implement the display of the hit list, all hits are displayed whose match
with the specified data record is larger than a certain threshold. The threshold is defined as a
percentage.
The same applies to the people-centric UI. This threshold is the basis for the hit list of the duplicate
check.
In this activity you determine for the objects of an index pool which threshold applies for the duplicate
list displayed by SAP.
This setting does not count as the threshold value for the dialog boxes that the third-party provider
sends. The provider has to implement suitable values or offer them as a Customizing setting.
Requirements
You have activated the duplicate check for this index pool.
Standard settings
If you do not make a setting, the default value is 90%. However, this is a fallback only and is not a
recommendation for the threshold value.
A threshold value can lead to varying results by the third-party providers because the scaling depends on
the individual implementation.
Regional Structure/City File
The regional structure (city file) is integrated into Business Address Services but can be called on its
own.
It can be activitated for each country in Customizing under "Set Country-Specific Checks".
SAP ships the regional structure without content.
You can fill the regional structure with data yourself, for example using an interface and new files from
a postal service provider.
Import Reference Data
Copy postal reference data into the regional structure tables.
Use the program RSADRLSM02.

Read the program documentation.
See note 132948.

Postal Codes
You can maintain number ranges for postal codes and create, change or display individual postal codes.
Maintain Number Ranges for Postal Codes
Maintain number ranges for postal codes

The postal codes for the address check against the regional structure are held in a table. The postal codes
are identified by a country code and a number. These numbers can be assigned externally or internally,
although internal assignment does not arise in practice.
Standard settings
In the standard system, Number Range 01 is for external assignment.
Recommendation
You can change the number range or add one for internal assignment.
Activities
To change a postal code number range:
1. Choose "Execute" to open the transaction for maintaining number ranges.

3. Maintain interval values From number and To number for the number range interval concerned.
4. Save your work.
WHATSAPP +255738656506
Further notes
When you create a postal code using Transaction SR30, the system always uses the first suitable
external or internal number range. Other number ranges can be used when you create postal codes
with function module SZRS_S_ADRPSTCODE_CREATE (for example to import data).
Create Postal Codes Individually
Create individual postal codes
Change Postal Codes Individually
Change individual postal codes
Display Postal Codes Individually
Display individual postal codes
Cities
You can maintain number ranges for cities and create, change or display individual cities.
Maintain Number Ranges for Cities
Maintain number ranges for cities

The postal cities for the address check against the regional structure are held in a table. The cities are
identified by a country code and a number. These numbers can be assigned externally or internally.
Standard settings
In the standard system, Number Range 01 is for external assignment and Number Range 02 is for
internal assignment.
Recommendation
You can change the number ranges.
Activities
To change a city code number range:

4. Save your work.
Further notes
When you create a city using Transaction SR10, the system always uses the first suitable external or
internal number range. Other number ranges can be used when you create cities with function module
SZRS_S_ADRCITY_CREATE (for example to import data).
Create Cities Individually
Create individual cities

Change cities individually
Change individual cities
WHATSAPP +255738656506
Display Cities Individually
Display individual cities
Streets
You can maintain number ranges for streets, define street types and create, change or display individual
streets.
Maintain Number Ranges for Streets
Maintain number ranges for streets

The streets for the address check against the regional structure are held in a table. The streets are
identified by a country code and a number. These numbers can be assigned externally or internally.
Standard settings
In the standard system, Number Range 01 is for external assignment and Number Range 02 is for
internal assignment.
Recommendation
You can change the number ranges.
Activities
To change a street number range:

4. Save your work.
Further notes
When you create a street using Transaction SR20, the system always uses the first suitable external or
internal number range. Other number ranges can be used when you create streets with function module
SZRS_S_ADRSTREET_CREATE (for example to import data).
Maintain Street Type
Maintain street types

You can create abbreviations for street types (for example street, road, avenue). Abbreviations are
used, for example in Spain, for messages to/from postal authorities by data media exchange.
Activities
If you need street types, choose "Execute" to maintain the table.
Create Streets Individually
Create individual streets
Change Streets Individually
Change individual streets
Display Streets Individually
Display individual streets
WHATSAPP +255738656506
Define Regional Structure Groups
Maintain regional structure groups

Regional structure grouping combines elements of the regional structure (cities, streets, street sections)
and is used for clerk determination, for example.
Standard settings
There are no regional structure groupings in the standard system.
Activities
If you need regional structure groupings, choose "Execute" to maintain the table.
Master Data
Master Data
Use
In this section, you make settings for the master data of real estate objects. There are two different views
of real estate master data:
a) Architectural view:
Use of the architectural view is optional. You only need to make these settings if you use the
architectural view.
b) Usage view:
Use of the usage view is mandatory, and therefore making settings for it is also mandatory.
Basic Settings
Measurements
Define Measurement Types
Use
In this section, you define measurement types for:

Architectural objects1.
Usage objects (business 2. entity, building, property, rental object)
Contracts (for service 3. charge settlement)
Measurements are used to record measurable traits of objects. The measurement type indicates the
type of trait that is being measured. Area measurements are also recorded as measurements. There is a
special indicator that identifies area measurements. This makes it possible to run special reports on
areas and for the system to check the unit of measurement for area.
The measurements of a rental object are used for example in service charge settlement for
determinining apportionment, and in option rate determination for determining the option rate. You
specify the measurement type that plays a role in these calculations in the settlement unit or in the
option rate method. Measurements are also the basis for the calculation of condition amounts.
Activities
Choose New Entries.

On the detail screen, you can specify the Real Estate object for which the measurement type is
allowed. If you want a measurement type to be proposed as the default in the application, choose
Criterion is default for object (on screen) for the object type. To ensure that the measurement type is
not deleted, choose Criterion for object is required entry (on screen) . The settings Default or
required entry are recommended for measurements that are needed for subsequent processes.
- For rental objects, you can also specify per usage type if a measurement type is allowed or not.
For measurement types that you want to allow for all rental objects, you enter the following in
the Allowed for RO field:
- Criterion permitted for object

- Required entry, or
- Default
Set the No Exception indicator. The system then ignores the differentiation by usage type.
- The same procedure applies for architectural objects. You can also specify per architectural
object type if a measurement type is allowed or not. If you set the No Exception indicator, the
system also ignores the differentiation by architectural object type.
For contracts you specify in addition the contract reference. You can also define per contract type
whether a measurement type is allowed or not and whether there is to be an object reference. If you set
the No Exception indicator, the system also ignores the differentiation by contract type.
Properties of service charge settlement
The system applies these settings only if the For Apport. (for apportionment) indicator is set. For more
information on the individual indicators, refer to the help documentation for these indicators.
If you use external heating expense settlement, then you have to assign either no or one basic component
for heating to exactly one measurement type. (You may have to do the same for the basic components for
Hot water and for Other.)
Measurement types in Customizing:
- A = Area: such as floor area

- M = Measurement: other measurements, such as number of parking spaces - U
= Usage: consumption, such as water consumption
WHATSAPP +255738656506
Define Total Measurements
Use
In this step, you can specify how measurements are derived from other measurements.
For measurement types that appear at least once in the Total Measurement Type column, you can no
longer enter the value for the measurement manually. Instead, their value is determined from the
measurements specified by the Source Measurement Type. These total measurement types are
designated by @3Z@ in the application. To see how the value for the measurement was calculated,
you can click on this icon, in other words, you see what settings were made for the measurement type
here in Customizing.
When should you use total measurements?
They are useful for differentiating between measurement types for reporting purposes, while at the
same time making measurement types more uniform for processes.
Example
In real estate objects with mixed usage, you can use the measurement type A004 Residential Space for
residential usage and the measurement type A003 Usable Space for commercial usage, in order to
distinguish between the two. For service charge settlement by area, however, you can combine these
two measurements together in the A200 Residential/Usable Space measurement type.
Entering Numerator and Denominator
Used when certain areas cannot be counted fully.
Example
In Germany, one half of the area of a balcony or terrace belonging to an apartment is included in the
calculation of the residential space, if certain conditions are met (minimum width).
If you want to enter these two types of area separately, then you make the following settings in
Customizing:
Source Meas. Type Total Meas. Type

Numerator Denominator
A004 Res.Space(w/o balcony) A010 Res.Space
1 1
A008 Balcony Area A010 Res.Space
1 2
If you have more that one summation level, note that each addend can only be included once in the
total measurement type.
Example
Source Meas. Type Denominator Total Meas. Type Numerator
A003 Usable Space 1 A200 Res./Usable Space 1

A004 Residential Space 1 A200 Res./Usable Space 1
A005 Secondary space A001 Total Space 11

A100 Retail Space A003 Usable Space1 1
A101 Office Space A003 Usable Space1 1
A102 Parking Space A001 Total Space 1
1
A200 Res./Usable Space A001 Total Space 1
1
M005 No.Parking Spaces M007 Covered parking space
1 1
M006PGarage Spaces M007 Covered parking space
1 1
Here the total space consists of Residential/Usable Space, Secondary
Space, and Parking Space together. If you also add the following row to this table:
A100 Retail Space A001 Total Space 1 1
then Retail Space is contained twice in the Total Space, once as a component of the Usable Space and
thereby of Residential/Usable Space, and once assigned explicitly.
The system is not able to recognize these kinds of situation (since, particularly when other numerators
and denominators are used, this could be intentional). Therefore, you have to make sure yourself in
Customizing that the settings are correct. In addition to the procedure described here, you can also do
so by limiting yourself to working with only two summation levels. This means that measurement
types, which are used as total measurement types, should not be used in turn as source measurement
types. The above table would then look like this:
Source Meas. Type Total Meas. Type Numerator

Denominator
A003 Usable Space A001 Total Space 1 1
A003 Usable Space 1 A200 Res./Usable Space 1
A004 Residential Space ,A001 Total Space 1 1

A004 Residential Space 1 A200 Res./Usable Space 1
A005 Secondary space A001 Total Space 1 1

A100 Retail Space A001 Total Space 1 1
A100 Retail Space A003 Usable Space1 1
A100 Retail Space 1 A200 Res./Usable Space 1
A101 Office Space A001 Total Space 1 1

A101 Office Space A003 Usable Space1 1
A101 Office Space 1 A200 Res./Usable Space 1
A102 Parking Space A001 Total Space 1 1
WHATSAPP +255738656506
Disadvantage: When you add new measurements, you have to make more entries. ( The measurement is
not, for example, automatically included in the Total Space by being added to Residential/UsableSpace).
Define Derivable Measurements
Use
In this activity, you can define how the measurement amounts of a rental object (for example, when a
rental space is extracted) should be derived from other measurement amounts. The derived value can
be changed when the rental object is processed. As long as no manual changes are made, the value for
the derived measurement type is updated automatically each time the basis measurement is changed.
It is possible to derive measurement amounts for the following rental object types:
- All rental object types from the same object or from subordinate/superordinate architectural objects
If a subordinate object type is involved, the source measurement type is summarized.
- For rental spaces from a superordinate pooled space

For example, you want to occupy available office space based on number of persons. You want to
proportionally calculate the occupied office space that is relevant for service charge settlement.
The system determines the measurement amount for the measurement type to be derived on the rental
object as follows:
MA = (MB/SB) * SA
The variables in this formula are explained below:
MA = Measurement amount to be derived for rental object
MB = Basis measurement amount (source measurement type) of the object, for which the derivation is
made
SB = Basis measurement amount (source measurement type) of the source object
SA = Measurement amount of the derived measurement type of the source object

Note:
If you want to define a straightforward transfer or summation of the measurement amounts, you do not
use this activity. Instead, you do this by allowing the same measurement type on the relevant objects or
by using Total Measurements.
Derivable measurements can be used, for example, for the proportional distribution of specific
measurement amounts.
Activities
Make all settings you need for each measurement type to be derived (see Examples 1 und 2).
Example 1
Different derivation levels can be defined for the same derivable measurement type and the same
object to be derived. In such cases, the number indicates the sequence in which the derivation
strategies are to be performed. For example, the following entry can be added to the above-mentioned
entry:
This requires the following entries:

Derivable Meas.Type: M005 Parking Space
Rental Object Type: RS Rental Space

Usage Type: 0005 Office
Derivation Source: Architecture ( A )
Arch. Object Type: 04FL Room
Sequence Number: 1
SrcMeasTyp: A101 Office Space
Derivation Source: M005 Parking Space
Rounding Category: Round Down
Decimal Places: 0
The number of the above entry must be set to a value greater than 1. The system first tries to derive the
number of parking spaces for the rental space from the office space for the floors to which the rental
space is assigned and from any parking spaces already assigned to these floors. If this attempt proves
unsuccessful (for example, because the rental space is not divided up any further for architectural
reasons or because no parking spaces are assigned to the floors), derivation is made on the basis of the
office space and the number of parking spaces for the pooled space.
Example 2
100 parking spaces (M005) are assigned to a pooled space of 1000 m2 office space (A101). Rental
spaces are extracted from the office space, and the parking spaces on the rental space should be
distributed proportionately to the area.
This requires the following entries:

Derivable Meas.Type: M005 Parking Space
Rental Object Type: RS Rental Space
Usage Type: 0005 Office
Derivation Source: Usage
Sequence Number: Any
SrcMeasTyp: A101 Office Space
Derivation Source: MP05 Parking Space
Rounding Category: Round Down Decimal
Places: 0
If a rental space of 253 m2 office space is extracted from the pooled space, then the value 253 / 1000 *
100 = 25 (rounded off) is derived for measurement type M005 Number of Parking Spaces. This value
can be overwritten manually.
WHATSAPP +255738656506
Implement Enhancements ( BAdI )
Define Allowability of Measurements by Object Type
Use
Using this BAdI, you can change the allowed measurements that are entered in Customizing, with the
change dependent on the data of the given business object.
Activities
Implement the following method of the BAdI.
- CHANGE_MEAS_CUST_LIST
Then activate the Business Add-In implementation.
Method description
- CHANGE_MEAS_CUST_LIST
@78@ IO_OBJECT Reference to business object
@78@ IF_ONLY_ALLOWED measurements be returned? Should only allowed
@7A@ CT_LIST Measurements, and if allowed

or not
Example
You want to limit the measurements that are allowed on architectural objects by using the "Function"
attribute.
First check if the object is an architectural object, and then get the data of the object.
Modify or add to the measurements in CT_LIST by setting the value of the USAGEFORAO field:
- ' ' Attribute Is Not Allowed for Object
- '1' Attribute Is Allowed for Object
- '2' Attribute Is Default for Object
- '3' Attribute Is Required Entry for Object (on Screen)
If the IF_ONLY_ALLOWED indicator is set, you have to remove all measurements from the list that are
not allowed.
Note the following:

- Do not directly access the database (SELECT statements) on tables where the data could be being
processed. Use only the API_RE_xx_GET_DETAIL function module for data retrieval. (Here xx
stands for the English abbreviation for the object type, for instance CN for the real estate contract.)
- Do not use statements that execute actions on the interface, for example, MESSAGE without
RAISING, CALL SCREEN and so on. Do not use COMMIT WORK or ROLLBACK WORK. Notes
for Developers
Prevent Overwriting of Total Measurements
Use
You can use this Business Add-In (BAdI) if you want to prevent measurements calculated by the
system (total measurements) from being manually overwritten.
Notes for Developers

Define Tenancy Law
Use
You specify here which tenancy laws you want to use in the system. You can specify for the business
entity, the contract and the settlement unit which tenancy law covers the relevant object (in the case of
the business entity also the dependent objects).
The tenancy law is actually used for the service charge settlement. In Customizing, you can define for
each tenancy law whether heating value days are allowed, and whether the tenants of the leased out
object are responsible in whole or in part for the costs of vacancies.
You can, for example, make customer-defined checks and derivations dependent on the tenancy law
(for instance, by using a BAdI to specify that particular adjustment rules should only be used for a
particular tenancy law).
For Italy: Italian tenancy law is used to activate fields used for administering Italian registration tax.
Activities
Define all tenancy laws that you want to differentiate between. In the Specific. field, enter the key of the
country for which special rules should apply.
Usage View
Usage View
Use
Using the usage view is mandatory. In this section, you make settings for master data of the usage
view, and for integration of Plant Maintenance with the usage view (PM integration). SAP provides
the following master data:
WHATSAPP +255738656506
- Business entity
- Building - Property
- Rental object
Note
Keep in mind that settings for PM integration can be made in the usage view and/or in the architectural
view. If you are using the architectural view, SAP recommends that you enter links to plant maintenance
only in the architectural view (see the PM Integration: Settings per Architectural Object Type IMG
activity).
General Settings for Multiple Object Types of the Usage View Fixtures and
Fittings Characteristics
Define Fixt./Fittings Characteristics for Buildings, ROs, and Parcels
Use
You specify here which fixtures and fittings characteristics are to be available when processing the
rental object, building, parcel, and architectural object. The fixtures and fittings characteristics that
you define here can be assigned to a representative list of rents (see Define Representative List of
Rents: Characteristic Categories --> Surcharge/Reduction Characteristics).
For fixtures and fittings characteristics that are not relevant for the representative list of rents, you can
define a structure using the Specify Structure of Fixtures and Fittings Characteristics Independent of
Representative List of Rents IMG activity.
Activities
- Define all required fixtures and fittings characteristics.

- For each fixtures and fittings characteristic, specify the objects on which the characteristic is
visible: rental object, building, and/or parcel. You can then process these fixtures and fittings
characteristics on the rental object or building by choosing the Fixtures/Fittings tab page. For
parcels, you see the fixtures and fittings characteristics by choosing the Development tab page.
If you need fixtures and fittings characteristics in architectural objects, you define them here.
Then you assign them to architectural objects in the Specify Fixt/Fittings Characteristics for
Architectural Objects IMG activity.
When adjusting conditions using the representative list of rents procedure (according to the
representative list of rents), you can use fixtures and fittings characteristics and their evaluations for
the calculation of the comparative rent.
The fixtures and fittings characteristics of the rental object and those of the assigned building
(provided that this is defined for the representative list of rents) are used in this calculation of the
comparative rent. If you indicate that a fixtures and fittings characteristic is permitted for both
object types, you can define the general validity of this characteristic at the building. For the
rental objects to which the building attribute does not apply, you can then make a different setting
in the application (see example).
- Also define for each fixtures and fittings characteristic whether it is relevant for the representative
list of rents, that is, whether it should be included in the rent adjustment according to the
representative list of rents.
- You can define that a specific fixtures and fittings characteristic should only be visible for objects
of this category (derived from the usage type of the rental object) using the usage category. If you
do not enter anything here, the fixtures and fittings characteristic can be selected regardless of the
usage type of the rental object.
Example
For example, if all apartments of a house are equipped with oil central heating, you could define the
fixtures and fittings characteristic Oil Central Heating for the building instead of separately
for each apartment. If electric heating is installed in the top-floor apartment ( that was subsequently
added), then when you process this apartment, you can select the Oil Central Heating
characteristic as not appropriate and instead specify a fixtures and fittings characteristic Electric
Heating.
Specify Structure of Fixt./Fittings Characteristics Independent of RLR
Use
For rental objects and buildings for which a representative list of rents is defined, the structure of
fixtures and fittings characteristics (hierarchy of characteristic categories, characteristic groups, and the
individual characteristics that are displayed in the processing dialog, for example, to define new
characteristics for an object) is determined using the representative list of rents structure.
You can also define a structure for characteristics that are not dependent on the representative list of
rents in this dialog. This structure has the following effects on the display of characteristics in the
processing dialog:
- If no representative list of rents is specified for a building or rental object on the relevant
business entity, then the characteristics are displayed according to the structure defined here
when you add new characteristics. This also applies to parcels, if you are using Land Use
Management (country-specific for Germany).
- If a representative list of rents is specified for a building or rental object, then in the processing
dialog you can switch to representative-list-of-rents-independent display to use the structure
defined here.
When you have switched, the system saves this setting and uses the representative-list-of-rents-
independent display the next time for processing.
During Maintenance of the Structure ofFixtures and Fittings Chraracteristics for Individual List
ofRepresentative Rents, you can also determine how the individual characteristics are to be evaluated
(dependent on the respective representative list of rents).
The structure specified here is stored technically under Representative list of rents <empty>.
WHATSAPP +255738656506
Activities
- Select the only line of the characteristic structure (representative list of rents <empty>) and
define which characteristic categories should be distinguished between.
- Define characteristic groups if necessary. Characteristic groups are cross-category. You can use
the defined characteristic groups within a category to structure the characteristic assignment
further. You can also define how many characteristics of a group can be assigned to a category
for each group.
- Assign the characteristics that should appear under this category to each characteristic category.
Each characteristic can be assigned to a maximum of one category. Assign the fixtures and
fittings characteristics of this category to each characteristic category. Define the characteristic
group if necessary. If you select Superimpose then this characteristic is superimposed when
creating an object and only needs to be selected as Applicable. You can only assign
characteristics for which the Use Only if Relevant to Representative List of Rents indicator is not
set.
Use
The Business Add-In (BAdI) can be used to control checks of fixtures and fittings characteristics.
In the standard system, all characteristics are always checked, regardless of whether or not they are
relevant to the representative list of rents. The system checks in particular if the rules entered in
Customizing for the fixtures and fittings characteristics regarding the necessity and number of the
individual characteristics are met. However, if you want, for example, to use characteristics dependent
on the usage type, and these characteristics can be relevant to the representative list of rents or not,
then the system checks all rules, even if a rule from a "Characteristic must exist" representative list of
rents is neither useful nor necessary for objects of a certain usage type.
To allow you to control the checks, you can use the method
CONTROL_CHARACT_BEHAVIOR . The method has the following parameters:
- Import: IO_OBJECT - Object for which the fixtures and fittings are checked
- Changing:
- CF_ONLY_CHECK_RLRA - Check only one area
- CF_HIDE_RLRA_NOT_RELEVANT - The area "independent of representative list of rents"
is not used and is therefore not to be checked
- CF_HIDE_RLRA_RELEVANT - The area "dependent on representative list of rents" is not
used and is therefore not to be checked
Example
For an example implementation, see the class CL_EXM_IM_REBD_CHARACT_BEHAV. Notes

for Developers
Infrastructure Characteristics
Define Infrastructure Characteristics
Use
When processing master data, you can specify how far the real estate object is from given geographical
points. You define these points using infrastructure characteristics.
Activities
Here you specify the infrastructure characteristics for which entries related to distance are possible.
You can also specify the unit of distance and the time (with the basis for the time measurement) that
is preferred for entries related to distance. These specifications are optional. The system then proposes
this unit as a default value.
Example
You can enter the following infrastructure characteristics for the real estate search:
- Kindergarten
- Elementary school
- Supermarket
- Train station
- Airport
- Bus stop
- Recreation area/park
You can enter the following infrastructure characteristics for Land Use Management:
- Road/street
- High-tension tower
Specify Basis for Measuring Distance as Time
Use
When processing master data, you can enter the distance to given infrastructure characteristics.
You can specify the distance either in the form of a measurement of distance (such as, miles) or as a
time.
WHATSAPP +255738656506
If you choose infrastructure characteristics for which the time entry could be based on different
assumptions (such as different modes of transportation), then you should specify the basis for the
time entry here.
Requirements
You defined infrastructure characteristics infrastructure characteristics.
Example
In your infrastructure characteristics, you defined the distance to the elementary school as a time in
minutes. In that case, you should distinguish between "Minutes on foot" and "Minutes by bus."
Neighborhood: Define Preferred Values
Use
You can enter up to three values for a neighborhood on the business entity and on the rental object. This
allows you to classify real estate objects further, regardless of their actual postal data.
In the RE search request, you can enter several values for the neighborhood that the prospect prefers.
(You enter them in a string with each neighborhood separated by spaces.)
In both these master data objects and in the RE search request, you can enter values that were not
explicitly entered in Customizing. However, to increase the likelihood of hits, you should enter values
here that you search for frequently.
If you enter a neighborhood in an RE search request, then the standard search only finds those rental
objects where at least one of the neighborhoods being searched for is entered on the rental object or
the business entity it belongs to.
Activities
Enter the neighborhoods here that you search for frequently.
Suppress Leading Zeros in Object Keys
Use
You can set for which object types the system should suppress leading zeros here.
Standard settings
The default setting is that the system suppresses leading zeros for all object keys during input and
output.
Activities
Set the indicator for object types for which you want the system to suppress leading zeros.
- Input:
If you set the indicator for input, a purely numerical key is always saved technically in the database
with leading zeros. Therefore, the system saves the key of a business entity for which you have
entered the number 1 as 00000001.
We recommend that you use this setting for all keys. In this way, you make sure that in all lists in
which the numbers appear sorted, the sort sequence is the one you expected. If you do not set the
indicator then the keys are saved left-aligned alphanumerically. For example, if you have created
a business entity with number 9 and one with number 12, then business entity 12 appears before
business entity 9 if the indicator is not set and the list is sorted ascending.
Note that leading zeros can only be added if the key entered only consists of numbers (and if
necessary spaces before and after it but not between the numbers).
- Output:
If you set the indicator for output then the system does not display saved leading zeros for purely
technical keys in the appropriate field in the database. For example, the system displays a business
entity that has the number 00000007 in the database as 7. The list is still sorted in the numerical
sequence.
Note
Note that setting the indicator subsequently for input can mean that you can no longer access objects
that were created at a time when the indicator was not set. Therefore, the indicator should never be set
subsequently for input in a production client. However, subsequently setting or resetting the indicator
for output is uncritical since this only influences the display of the key.
Define Functions of Objects
Use
In this activity, you define functions of objects in the usage view. These functions provide information
only.
Business Entity
Number Range for Business Entity
Use
WHATSAPP +255738656506
Here you can specify how number assignment is handled for this usage object. The specification applies
uniformly for the company code. Note that the system only takes the setting for interval "01" into
account.
For external number assignment, you can specify the number range that is available when you create the
usage object.
For internal number assignment, the system counts upward sequentially starting from the number shown
in the Number level field.
For buildings, properties and rental objects, the system assigns the number per business entity when
internal number assignment is used. This number is unique within the business entity. The next assigned
number for these objects is therefore not identical with the number that is shown here in Customizing.
For more information, refer to Notes for General Number Assignment.
Regional Locations
Create the locations you need with the required amount of detail.
Layer
Create the necessary locations of business entities with the amount of detail you need, and
enter a name for the location.
District Locations
Create the district locations of business entities in the amount of detail you need, and enter
descriptions for them.
Transport Connection
Create the necessary transport connections for business entities in the amount of detail
you require, and enter names for them.
Example
Bus/streetcar
Subway/commuter train
Multiple connections
Maintenance Areas
Create the maintenance areas you need.
Dialog
Change Screen Layout
For more information on using the Business Data Toolset, refer to the SAP Library. Choose SAP
NetWeaver Components --> Cross-Application Functions --> Business Data Toolset.
Screen Layout
Field Groups
Field Groups
Use
These are the specifications for how the fields are grouped into field groups for the Business Data
Toolset.
Standard settings
Do not change the standard settings.
Exception
You should make changes only if you want to add your own new fields to the master data dialog.
Activities
In that case, copy an existing field group to the customer name range. (Enter a number between 600
and 799 in the Field Group field.)
Change the properties of the field group accordingly in the detail screen. Then assign the new fields to
the field group.
Field Status
Use
Here you can set up the field modification for field groups. Proceed as follows:
1. Enter the activities for which the setting should apply (if not already displayed).
WHATSAPP +255738656506
2. Select the row and choose Field Modification.
The system displays all field groups that know the given application. In order to display the
fields of a field group, position the cursor on the field group and choose Environment -> Field
check.
3. Now you can, for example, suppress field groups that are not needed or define other field groups as
"Required entry" fields. If you choose the "Not specified" setting, then the system itself determines
how the field is treated. (Usually these fields are optional entry fields in create and change mode,
and display fields in display mode.) If it is not possible to make a setting for a field group, then the
system determines how the field is treated (usually dependent on the situation, or on the contents of
other fields).
Note
Before you suppress multiple field groups of a view, a section or a screen sequence, you should
consider if it makes more sense to remove the view, section or screen completely from the screen
sequence.
Views
Use
Here you specify which field groups are grouped together into a view (part of a screen, technically a
subscreen). You should group together the field groups that necessarily belong together during a check.
Example
If you have a field group with a valid-from date and a field group with a valid-to date, and these should
be checked against each other in a module, then you should group them together into a view.
The check module is in the detailed data under "Function Module After Entry".
Standard settings
SAP recommends that you not change the standard settings. It is only necessary to make changes if
you want to add your own new fields to the master data dialog.
In that case, copy an existing view to the customer namespace (Y* or Z*) and modify the properties of
the view accordingly (consider the detail screen). Then assign the field groups to the view. You can
assign your own field groups, as well as those delivered by SAP.
Sections
Use
Here you specify which views are grouped together into sections. You can recognize a section because it
is surrounded by a frame. Fields that logically belong together should be grouped together in sections.
Standard settings
SAP recommends that you not change the standard settings.

It could be necessary to define new sections, either to arrange views delivered by SAP differently or to
add your own fields to the master data dialog.
In that case, copy an existing section to the customer namespace (Y* or Z*) and assign the views you
want to this section. The item number specifies the sequence in which the views are arranged in the
section. For technical reasons, if you make your own assignments from sections to views, the item
numbers have to be in the customer namespace (that is, they are not allowed to end in '00').
This makes it possible for you to also include your own views in SAP sections. Select a section, and
choose Section -> Views in the dialog tree, and assign the view to a section using a corresponding
item number.
Screens
Use
Here you specify which tab pages appear in the dialog, and which sections make up these tab pages.
Standard settings
SAP recommends that you do not change the standard tab pages.
If you want to change a tab page, copy the standard tab page that is closest to the tab page you have in
mind, and give it a name in the customer name range (Y* or Z*). Then assign the sections you want.
The position number for user-specific entries also has to be other than 00 here.
Screen Sequences
Use
Here you specify which screen sequences should appear in dialog. A screen sequence consists of
different screens, and each screen is equivalent to a tab page.
Standard settings
SAP recommends that you leave the standard screen sequences unchanged. If you have to define other
screen sequences, copy a standard screen sequence to the customer name range (Y* or Z*) and then
assign the screens you want. The position number for user-specific entries also has to be different
from 00 here.
Note
You have to assign the new screen sequences to the standard screen sequence category. Choose Screen
Sequence Categories or Screen Sequence Category -> Screen Sequences.
Where does changing the screen sequence make sense?

WHATSAPP +255738656506
For applications that can relate to different object types or contract types:
- Architectural object (locality, land, building, floor, space, and so on):

Here you can define the new screen sequence dependent on the architectural object type. If a new
screen sequence is not entered, then the system uses the standard screen sequence. This allows
you, for example, to hide the Land tab page when processing an architectural object of the type
Building, and vice versa.
- Rental object:
You can define the screen sequence to be dependent on the type of rental object ( rental unit,
pooled space, rental space).
- Contract:
You can define the screen sequence to be dependent on the contract type. If a new screen
sequence is not defined per contract type, or it cannot be defined (for business entity, building
and land, for example), then the system uses the screen sequence that is designated as
"Standard."
- RE search request:
For normal entry, you use the standard screen sequence. For fast entry (ad hoc search) the
RERRFE screen sequence is used. (This cannot be changed.)
Events
You need this dialog only if you want to make complex modifications to the standard dialog.
SAP recommends that you leave the settings delivered here unchanged.
Tables
Number Assignment, Validation, Substitution
Use
This Business Add-In supports enhancements of the standard functions of business entities. For an
overview of the possible enhancement methods, see this text.
Activities
Create a BAdI implementation and implement the methods needed for your particular enhancement.
Then activate the BAdI implementation.
For a description of the methods that are available in all Business Add-Ins for master data objects and
the real estate contract, refer to Methods and Events.
For an overview of the programming interfaces for RE-FX, see this text.
Example
There is a sample implementation for each of the following in the BAdI Builder: business entity,
rental object and real estate contract.
Choose the menu path: Goto -> Sample Code -> Display.
Enhancements of the user interface using the Business Data Toolset are explained in more
detail in Enhance BDT Applications Notes for Developers
Implement Enhancements (BAdI): "Overviews" - Own

Evaluations
Use
There is an Overviews tab page on the processing screen for contracts and real estate object master
data. Some overview lists are predefined in the system. You can enhance the existing lists for each
object type to suit your needs or add your own lists. The procedure is described here using an
example.
Building
Building Number Range
Use
account.
usage object.
WHATSAPP +255738656506
Building Condition
Enter descriptions for the conditions of buildings.

The characteristic is informational only.
Building Types
Enter building types. This table is used in the "Loans" application.

Main Usage Types
Use
Here you specify the main usage type of the building. This attribute is of a purely documentary nature:
controlling the account assignment or the connection to Asset Accounting (as in Classic RE) no longer
exists.
Use
Activities
Example
Heating.
Use
processing dialog:
WHATSAPP +255738656506
defined here.
Activities
for each group.
set.
Dialog
Screen Layout
Field Groups
Field Groups
Use
These are the specifications for how the fields are grouped into field groups for the Business
Data Toolset.
Standard settings
Exception
Activities
the field group.
Field Status
Use
Use
WHATSAPP +255738656506
check.
system determines how the field is treated
(usually dependent on the situation, or on the contents of other fields).
Note
sequence.
Views
Use
Example
Standard settings
Sections
Use
Standard settings
item number.
Screens
Use
Standard settings
Screen Sequences
Use
Standard settings
from 00 here.
Note
WHATSAPP +255738656506

- Rental object:
- Contract:
"Standard."
For business entities, the system always uses the screen sequence category that is defined as
"Standard".
Events
Tables
Use
This Business Add-In supports enhancements of the standard functions of buildings. For an
Activities
Example
Enhancements of the user interface using the Business Data Toolset are explained in more detail in
Enhance BDT Applications

Evaluations
Use
example.
Land
Number Range for Properties
Use
account.
usage object.
WHATSAPP +255738656506

Municipality Key
Create the municipality keys that you need.

This characteristic is informational only.
Local Subdistricts
Create names for local subdistricts.

This characteristic is informational only.
Property types
This property type is a described property characteristic that does not have a functional application.
Location Qualities
Enter the key for the description of the location quality of the properties, for example located on
the outskirts.
Ground Types
Specify the possible ground types for properties, such as, rectangular.
Statuses
Enter short texts for characterization of the overall condition of properties.

The function of this characteristic is not used.
Usage Types in Development Plan
Enter the usage types specified in the development plans. These can then be entered as
characteristics in properties.
Usage Types in Land Use Map
Create the usage types used in land use maps for your properties.
Heritable Building Right Types
In this step you define types of heritable building rights.

You can thereby indicate if a building was constructed on land subject to heritable rights.
Dialog
Screen Layout
Field Groups
Field Groups
Use
Toolset.
Standard settings

WHATSAPP +255738656506
Exception
Activities
the field group.
1 Field Status
Use
Use
check.
other fields).
Note
sequence.
Views
Use
Example
Standard settings
In that case, copy an existing view to the customer namespace (Y* or Z*) and modify the
properties of the view accordingly (consider the detail screen). Then assign the field groups to the
view. You can assign your own field groups, as well as those delivered by SAP.
Sections
Use
Standard settings
WHATSAPP +255738656506
item number.
Screens
Use
Standard settings
Screen Sequences
Use
Standard settings
from 00 here.
Note

- Rental object:
- Contract:
"Standard."
For business entities, the system always uses the screen sequence category that is defined as
"Standard".
Events
Tables
Use
This Business Add-In supports enhancements of the standard functions of land. For an
Activities
WHATSAPP +255738656506
For a description of the methods that are available in all Business Add-Ins for master data
objects and the real estate contract, refer to Methods and Events.
Example

Evaluations
Use
example.
Rental Object
Number Range for Rental Objects
Use
account.
For external number assignment, you can specify the number range that is available when you
create the usage object.
For more information, refer to Notes for General Number Assignment. Note
The settings you make here apply for pooled spaces, rental units, and rental spaces.
Usage Types
Usage Types
Use
In this section, you specify the external usage types for rental objects and assign internal usage type to
them. In addition, you can already specify here if a usage type should participate in settlement or not.
The usage type specifies:
- Which screen sequence is used for master data maintenance of the rental object
- Which rental object types (rental unit or pooled space/rental space) are allowed
- Which condition types are allowed for the rental object (by assigning a condition group per usage
type)
- Which option rate method is defaulted
- Which adjustment rule is defaulted for a condition type
- Whether or not a rental object can participate in service charge settlement
Although assigning an internal usage type is mandatory, the assignment is informational only. The
internal usage types for publicly-subsidized apartments or privately financed apartments serve as a
good example. In RE-FX, there is no longer a difference in programming between these two internal
usage types (which was not the case in Classic RE).
Instead, where it is necessary to distinguish between these two types in the system, you have to make the
required settings in Customizing. The following processes are affected:
- Service charge settlement: apportionment loss risk
In this case, you have to define the usage type and fixtures and fittings characteristic in the
surcharge schema.
- Real estate search: accommodation entitlement certificate

Here you have to make explicit settings in the fixtures and fittings characteristics.
- Rent adjustment procedure

Here you have to assign adjustment rules, for example for the representative list of rents, only to
privately financed apartments in the contract.
WHATSAPP +255738656506
Note
Depending on the usage type and type of rental object you can specify which screen sequence is to be
used under Usage Type per Rental Object Type.
Usage Type per Rental Object Type
Use
In this section, you specify which usage types can be used exclusively for which rental object types
Prerequisites
You created the necessary usage types in the Usage Types IMG activity.
Activities
Assign usage types to rental types as needed.
Note that a usage type that is not assigned to all rental object types is not valid for the other rental object
types. If you want a usage type to be valid for all rental object types, then you either have to assign it to
all rental object types or to none.
Note
You might have a need to extract multiple rental spaces from a pooled space that has a given usage
type, and you want the rental spaces to have different usage types, or more specific settings for the
usage type. In that case, you can assign these usage types to the usage type of the pooled space in the
Allowed Usage Types for Rental Spaces per Pooled Space IMG activity.
Usage Types Allowed for Rental Spaces per Pooled Space
Use
In this activity, you can assign multiple usage types for rental spaces that are extracted from pooled
spaces. You assign these to the usage type of the pooled space.
Requirements
You created the necessary usage types in the Usage Types IMG activity. If you want a usage type to be
allowed only for the Rental space rental object type, define this in addition in the Usage Type per
Rental Object Type IMG activity.
Standard settings
In the standard system, rental spaces have the same usage type as the pooled space they belong to. This
means that when the usage type of the pooled space is Office space, for example, the rental spaces you
extract from it are also office space. However, you might need different types of offices at the rental
space level (single office, common office, and so on). You can create these usage types in the Usage
Types IMG activity mentioned above, and assign them to the usage type of the pooled space in this
activity.
Example
An airport terminal is a large pooled space with the usage type defined as 0040 Terminal .
When you extract rental spaces, however, you want to be able to distinguish among the following
usage types:
0041 - Terminal-Airline Counter

0042 - Terminal-Waiting Area
0043 - Terminal-Retail Space
Make the following settings:

Pooled Space Usage Type Rental Space Usage Type
0040 Terminal 0041 Terminal-Airline Counter
0040 Terminal 0042 Terminal-Waiting Area
0040 Terminal 0043 Terminal-Retail Space
Note
Now it is no longer possible to extract rental spaces with the 0040 - Terminal usage type from this
pooled space. If you want this usage type to also be available, you have to make the following additional
entry:
0040 Terminal 0040 Terminal
Measurement Types Allowed per Rental Object Type
Use
In this step, you can make specifications for measurement types for rental objects that apply per rental
object type.
Requirements
You have defined which measurement types are allowed in general for rental objects in the Measurement
Types IMG activity.
You assigned external usage types to the rental object types in the Usage Type per Rental Object Type
IMG activity.
Example
The "number of persons" measurement type is allowed for rental objects. You now want to specify,
dependent on the rental object type, that the measurement type should
- Be a default value for rental spaces and rental units

- Not be allowed for pooled spaces
WHATSAPP +255738656506
RO Type Meas.Tp Meas. Type - Use

Rental unit No. of Persons Criterion is default for object
Rental Space No. of Persons Criterion is default for object
Pooled space No. of Persons Criterion not permitted for object
Measurement Types per Usage Type
Use
In this step, you can make specifications for measurement types for rental objects that apply for
individual usage types. SAP recommends that you exclude measurement types such as "Room
Capacity in Numberof Persons" for the pooled space rental object type, since it is not possible to enter
a capacity in this case.
Requirements
You have defined which measurement types are allowed in general for rental objects in the Measurement
Types IMG activity.
You assigned external usage types to the rental object types in the Usage Type per Rental Object Type
IMG activity.
Process
The system checks:
1. If a measurement type is defined as allowed in general for a measurement type

2. If special specifications were made for the rental object type and measurement type
3. If a special specification was made for the usage type
If the settings are contradictory on these three different levels, then the applicable setting is the last one in
this sequence.
Example
The "residential space" measurement type is allowed for rental objects. You now want to specify for
the usage type, that it should
- Be a default value for apartments

- Not be allowed for offices
Usage type Meas.Tp Meas. Type - Use

Priv. Fin.accomm. Resident.Space Criterion is default for object
Office Resident.Space Criterion not permitted for object
Attributes
Parts of building
In this activity, you define the building wings or parts in which rental objects are located. The entries are
informational only.
Activities
Check the standard settings and change them if needed.
Example
- Front-facing house
- Back-facing house
- Main building
- ...
Locations on Floor
Use
Here you can enter possible floor locations. The information helps in distinguishing rental objects
from one another, especially for large buildings.
Example
- Front left
- Back left
- Middle
- Front right
- Back right - ...
Floor Descriptions
In this section, you create the storey names for buildings and define a number for each storey.
Activities
Check the standard settings and change them, if necessary.
The storey names must be unique. For technical reasons, an entry with an initial key has to exist.
WHATSAPP +255738656506
Use
Activities

Example
Heating.
Use
processing dialog:
defined here.
Activities
for each group.
set.
WHATSAPP +255738656506
Reasons for different rent increase
In this step you determine reasons for alternative rent increases, which can be defined as attribute of
the rental unit.
These reasons describe why the percentage rate of increase defined in the rental unit applies.
Account Determination Values
Use
In addition to account symbols, you can define account determination values. You enter them in
posting rules on the contract or rental object, and they control account determination for automatic
postings.
Vacancy
Define Vacancy Reasons
Use
You define the possible reasons why a rental object is vacant here.
Activities
Define all vacancy reasons that you want. Depending on the vacancy reason, you can set the following:
- That for vacancy postings you want to take account of a separate cost center and/or a separate
account using the account determination value.
- Whether follow-up postings should be generated for changes to the rental object or contract that
affect existing postings.
- Whether and which posting term should already be generated when creating a rental object.
- How the vacancy period influences further rental:
- No Influence
- Warning Before Automatic Overwrite
- Error Before Automatic Overwrite
- Whether the vacancy reason is allowed to be entered or changed manually in the application.
Standard settings
Standard Customizing is set up with the following vacancy reasons:
- No Particular Reason
- Contract Expired/Notice Given
- Modernization Measure
- Reservation
The account assignment only changes if the vacancy exists due to a modernization measure. The account
assignment reference FM (Facility Management) is used in this case instead of the normal account
assignment. Account determination is set up for all vacancy-relevant flow types for this account
assignment reference. Instead of the account symbol 108 with account 470700, the account symbol 118
with account 451000 (maintenance costs buildings) is used on the cost side.
When you rent the object there is a warning if the vacancy reason modernization measure is set and an
error if it is a reservation.
You can only set the vacancy reason modernization manually. The vacancy reason reservation can
either be set manually or by a renewal option of a fixed-term contract.
You define when which vacancy reason is set automatically in the Determine Vacancy Reason Based on
Vacancy Event IMG activity.
Determine Vacancy Reason Based on Vacancy Event
Use
The vacancy reason in the master data of a rental object explains why the rental object is not occupied.
You can enter the vacancy reason manually in the rental object.
However, the vacancy of a rental object is usually caused by changes in the assigned occupancy
contract. In this activity, you specify which changes to the occupancy contract result in which vacancy
reasons in the rental object. A vacancy reason that was set automatically can be changed manually.
Activities
Assign a vacancy reason to each event for which a specific vacancy reason is to be set automatically.
The possible events are predefined in the system. To see the available events, use the input help.
0 Default Vacancy Reason

If a vacancy is caused by an event for which a vacancy reason has not yet been defined here, the system
sets the vacancy reason to event 00 (Default Vacancy Reason). If there is no entry for event 00, the
system does not set a vacancy reason.
1 Rental Object Created New

If a new rental object is created, a vacancy with the vacancy reason defined here is generated for the
specified lifetime of the rental object.
2 Contract Start Date Shifted Backward

If the start date of an occupancy contract is shifted backward, the vacancy reason specified here
is used for the resulting vacancy period.
WHATSAPP +255738656506
3 Contract End Date Shifted Forward
If the end date of an occupancy contract is shifted forward, the vacancy reason specified here is used for
the resulting vacancy period.
4 Start Date of RO Assignment to Contract Shifted Backward

If the rental object assignment to an occupancy contract is shifted backward, the vacancy reason defined
here is assigned to the corresponding vacancy record in the rental object.
5 End Date of RO Assignment to Contract Shifted Forward

If the rental object assignment to an occupancy contract is shifted forward, the vacancy reason defined
here is assigned to the corresponding vacancy record in the rental object.
8 Regular Notice Given on Contract

You do not specify the vacancy reason here in the case of notice (notice being given on an occupancy
contract for a rental object). Instead, the vacancy reason is specified based on the notice reason. (Refer to
Determine Vacancy Reason Based on Notice Reason.)
9 Reservation
If a vacancy period is reserved by a contract offer, the vacancy reason assigned to this event is displayed.
10 Renewal Option Not Accepted

This vacancy reason is used if a renewal option is rejected and a corresponding vacancy record is
generated as a result.
11 Renewal Option Ends Earlier

If the renewal option in the occupancy contract is replaced by a shorter renewal option, the vacancy
reason defined here is assigned to the new vacancy record.
Determine Vacancy Reason Based on Notice Reason
Use
When notice is given on a rental object, a notice reason has to be entered. For each notice reason, you
specify which vacancy reason is set on the rental object when this notice reason is used.
Requirements
You have to define notice reasons before you can make settings here.
For more information, refer to the documentation for the Define Notice Reasons. IMG activity.
Dialog
Screen Layout
Field Groups
Field Groups
Use
Toolset.
Standard settings
Exception
Activities
In that case, copy an existing field group to the customer name range. (Enter a number
between 600 and 799 in the Field Group field.)
the field group.
Field Status
Use
check.
WHATSAPP +255738656506
other fields).
Note
sequence.
Field Status per Usage Type
Use
In this section, you specify per usage type how and if fields are displayed in dialog. Fields can be:
- Hidden
- Optional entry
- Required entry
Activities
The dialog is different depending on the origin of the rental object to which the usage type is assigned.
Since externally created objects are not supported, leave the Field status purpose field blank. To go to
the field selection screen, position the cursor on a row of the table and choose Field selection. Make your
settings for each field group.
@0S@ Fields for which you set the Non-spec. indicator are always available for input.
Note
For more information on the relationships with settings per activity, see Linking of Read Field
Modifications per Activity and the Read Field Modifications per Usage Type.
Views
Use
Example
Standard settings
Sections
Use
Standard settings
item number.
WHATSAPP +255738656506
Screens
Use
Here you specify which tab pages appear in the dialog, and which sections make up these tab
pages.
Standard settings
Screen Sequences
Use
Standard settings
from 00 here.
Note

- Rental object:
- Contract:
"Standard."
Events
Tables
Use
This Business Add-In supports enhancements of the standard functions of rental objects. For an
Activities
Example
WHATSAPP +255738656506

Evaluations
Use
example.
Architectural View
Architectural View
Use
In this section you make the settings for the master data of the architectural view. These settings are
optional, since using the architectural view in Flexible Real Estate Management is not mandatory.
When should you use the architectural view?
- You want to store information about the architectural structure of your real estate objects in the
system.
- You have detailed information on measurements for your real estate objects, for example for each
floor or room in a building, and want to have this information available in the usage view.
- You want to define information on a level below the rental object (such as, for rooms). This is
only possible when you use the architectural view.
- You want to use functions for room reservations and long-term seating arrangements and you
want to generate reservation objects from architectural object types.
- You want to link to graphical systems.

When is it not necessary to use the architectural view?
- You have rental processes only (creating rentable and rented spaces, also in the form of pooled
spaces).
- You want to be able to extract rental spaces from a pooled space.
Architectural Object Type
Create Architectural Object Types
Use
In this step, you define your allowed architectural object types.
By defining architectural object types, you define the different, distinct architectural levels you wish to
have in the system and their relationship to each other. An architectural object of the type Building and
an architectural object of the type Room are the same object from a technical perspective, and both are
processed in the same "Process Architectural Object" master data dialog. However, you can make your
settings so that different fields and screens are available for rooms than for buildings (Screen Sequence
field). In addition, you can specify, for example, that rooms can only be created as subobjects of
buildings.
@0S@ We recommend that you enter only a small number of object types that you really need. For
example, you should avoid creating different architectural object types for different types of rooms. You
can make this kind of distinction instead at the function of the architectural object level.
If you use the functions for room reservations and continuous occupancy, then you can generate
reservation objects from the architectural object types you enter here. However, to be able to use these
objects for reservations or planning occupancy, you have to make additional settings in Customizing
for room reservations.
Requirements
The same attributes exist in the architectural view as in the usage view, which enables you to derive
the usage view from the architectural view, if you want. For this to be possible, you have to assign the
master data of business entities, land, and buildings in the usage view to the corresponding
architectural object types.
WHATSAPP +255738656506
Activities
1.Assign the master data of business entities, land, and buildings in the usage view to architectural
object types by setting the appropriate indicator (for example, AO = BU).
2. Top Level
You have to set the Top Level indicator for the object type that will be the highest node in the
architectural hierarchy. To make it possible to reflect the architectural view in the usage view, you have
to choose an object type that is assigned to the business entity as the Top Level node. It is possible to
define more than one architectural object type as the Top Level.
@0S@ Assume you want a particular object type in the architectural view (such as a building) to be
available both as a Top Level node and as a subordinate object type. In that case, you have to create
two different object types (for example, building 1 as Top Level node and building 2 as subordinate
node).
Reason: If both the "locality" and "building" architectural object types are designated as Top Level
nodes, then it is not possible to insert a building in the hierarchy below the locality.
3. Number Assignment
@0S@ Set the Global NA (global number assignment) indicator, if you want number assignment for
the object type to be unique, regardless of the hierarchical level. Number assignment is automatically
global for the top-level object. However, if you create a building within the locality, the number of the
building only has to be unique within the locality. If you have two localities, A1 and A2, then building
B1 can exist in both of them. If instead you also want the building number to be unique, then set the
Global NA indicator for the Building. The system then ensures that each building number is unique in
the entire client, across all localities.
4. In the HiLev.Obj.Type (higher-level object type) field, you can enter object types for which you do
not want global number assignment. Here you enter for these objects at which higher level in the
hierarchy number assignment should be unique. For rooms, for example, this could be the floor, the
building or the locality.
5. Screen Sequence
SAP supplies a standard screen sequence. You can define additional screen sequences ( for instance per
architectural object type) in this IMG activity.
Example
@0S@ The actual hierarchical relationship between architectural objects with different object types is
not actually specified until you create their master data. However, in Customizing you can already
define the relationships that should be possible in the Define Allowed Object Type Hierarchy IMG
activity. Examples of these relationships are:
Building # Wing of Building - Floor - Room
Building # Floor - Wing of Building - Room

Assign Icons to Architectural Object Types
Use
You have to modify the icons for architectural object types to agree with the settings you made for
architectural object types. You have to create new entries in the table for this. We recommend using a
different icon for each object type, so that you can more easily distinguish the objects from one another.
Activities
Choose an icon using the input help. The field remains empty. The number of the icon is
displayed in the next field, followed by the icon itself in the following field.
Save.
Define Allowed Object Type Hierarchy
Use
Architectural Hierarchy
In this step, you define which architectural object types can be assigned as higher-level object types
(parent object types) within the hierarchy, per architectural object type.
Note: The settings you make here have to agree with the settings for the assignment of usage objects, as
well as with the highest-level hierarchy object and with number assignment (see also: Process
Architectural Object Types ).
Requirements
In the Process Architectural Object Types, IMG activity, you have to have defined the architectural
object types that can be used.
Example
Arch.Object Type Parent Object Type

1.
Floor Part of building
Floor Building
2.
WHATSAPP +255738656506
Room Building
Room Floor
Room Part of building
Examples for Hierarchy

1st Locality 01
Building G1
Part of building C
Floor 1
Room
C12
Since the room can also be directly assigned to the building, the "part of building" and "floor" levels
can actually be omitted. They could also, depending on your settings, be switched with one another:
2nd Locality 01
Building G2
Floor 1
Part of building
C
Room
C12
Specify Rule for Determining Object ID
Use
Here you set up the rules to be used for generating a system-wide, unique architectural object ID from
the architectural object code (AOID code). The settings depend on the object type. The architectural
object ID is assigned hierarchically. This means that a new architectural object ID contains the
architectural object ID of the object above it in the hierarchy. The architectural object code of the new
object is added to this architectural object ID. This code can be separated by a separator (such as a
slash or hyphen, if one was specified on the superordinate object, or here in Customizing).
Activities
For each object type, specify:
- The maximum length of the AOID code

- The default length (this length is used as the default when the AOID code is derived from the
number of the architectural object)
- If the architectural object ID of objects that have this object type is used for assigning the
architectural object ID of subordinate objects
- If a separator is used to separate the AOID of the object from the code of the subordinate object
- If the AOID code should be generated from the number of the architectural object
Example
The following was specified in the Customizing table for automatic assignment of the architectural
object ID ( AOID ):
Name of AO Type Max.Length DefLength Use Separator From AONR

Locality 3 X
Bldg complex 13
Building 2 X - X
Part of building 1 X X
Floor 2 1 X . X
Room 3 2 X X
The system assigns the following architectural object IDs based on these object numbers and codes:
Name of Arch. Object Type

AO Number AOID Code Generated AOID
Locality WALLDORFWDF (manual) WDF
Bldg complex 1 COM1 (manual) WDFCOM1
Building 2 02 (automatic) WDF02
Part of building A A (automatic) WDF02-A
Floor 4 4 (automatic)WDF02-A4
Room 56 56 WDF02-A46
Explanation:
- Where the Use in Subordinate Objects indicator is set, the codes are used as part of the AOID
in the next level.
- If a separator was specified, then this is added after the AOID of the object on the previous level.
If the indicator is not set (in the example this applies to the building complex), then the code is
only used for assigning the AOID of the current object itself (WDFCOM1 in the example).
- If the From AONR indicator is set, then the AOID code is derived from the number. In this case,
the system uses the number of places specified in the DefLength field to create the AOID code.
In doing so, the system starts from right to left, and adds leading zeros if needed. If there is no
value specified for this Def.Length, the system uses the value in the Max.Length field instead.
Define Possible Functions per Architectural Object Type
Use
In this section, you specify the functions of architectural objects for each architectural object type.
The function allows you to categorize your architectural objects. For example, you can use this function
to define the types of buildings or rooms that you have.
WHATSAPP +255738656506
Using this function along with the architectural object types, you can have the system derive
reservation objects. However, to be able to use these objects for reservations, you have to make
additional settings in Customizing under Room Reservations and Long-Term Seating Arrangements.
Activities
Define functions only for object types where you need to make a distinction between different uses. For
any other object types, you can hide this field using the field selection control.
You can enter the function of an architectural object in the master data dialog and use it for selecting data
in reports.
The function has control functions only for room reservations. In all other cases it serves to provide
information only.
Specify Measurement Types per Architectural Object Type
Use
In this step, you specify if a measurement type is allowed or not per architectural object type.
Requirements
You have created measurement types in the Measurement Types IMG activity, and in the Restrictions
screen area you entered Criterion permitted for object for architectural objects. The measurement type
then applies for all architectural objects.
Activities
You can define exeptions here for individual architectual object types. However, the system ignores
these exceptions if the No Exception indicator is set in the activity mentioned above.
Enter the measurement type and the architectural object type. Set the MM indicator if the measurement
type should be the main measurement.
Limit Measurement Types by Function
Use
In this activity, you can specify whether or not assigning a measurement type for each architectural
object type and function is allowed.
Requirements
You created measurement types in the Define Measurement Types IMG activity. In the group box for
restrictions, you chose Attribute Allowed for Object for architectural objects. This setting applies for all
architectural object types.
In the Define Possible Functions per Architectural Object Type IMG activity, you specified the possible
functions for each architectural object type.
Activities
Here you can define exceptions for combinations of architectural object types and functions. However,
the system ignores these exceptions if you set the No Exception indicator in the activity mentioned
above.
The system takes the restrictions you make here into account in addition to the settings you make in
the Specify Measurement Types per Architectural Object Type IMG activity.
Specify Fixt/Fittings Characteristics for Architectural Objects
Use
In this section you can
- Specify, dependent on the architectural object type if a fixtures and fittings characteristic is allowed
- Specify which fixtures and fittings characteristics are allowed for land
Requirements
You defined the fixtures and fittings characteristics in the Customizing activity Define Fixt./Fittings
Characteristics for Buildings, ROs, and Parcels.
Activities
- For fixtures and fittings characteristics that you want to be allowed for all architectural objects
regardless of their object type, you make entries with the type I0, leave the Differentiation
Criterion field blank, and enter the fixtures and fittings characteristics.
- For fixtures and fittings characteristics that you only want to be allowed for certain architectural
object types, enter the architectural object type in the Differentiation Criterion field for the fixtures
and fittings characteristic.
You can enter fixtures and fittings characteristics for land in the master data dialog for land only if the
business function RE_GEN_CI_1 and the subfunction XX01 are active.
WHATSAPP +255738656506
PM Integration
Make Settings per Architectural Object Type
Use
In this section, you specify for each architectural object type how functional locations are created.
They can be
- Created automatically
- Created automatically and updated (when changes are made)
- Not created automatically (no automatic integration with Plant Maintenance).
Activities
1. Choose New Entries.

2. Specify the architectural object type and choose the setting you need in the Aut. FL
(automatic functional location) field. If you do not choose to have the system automatically
create functional locations, you can manually create functional locations for architectural objects
of this type. Or you can link existing functional locations with architectural objects of this type.
3. In the Object Type ID field, you can specify the prefix that functional locations for this architectural
object type receive.
4. In the StrIndicator (structure indicator) field and FuncLocCat (functional location category) field,
you enter the traits that the functional locations for this object type have.
Define PM Notifications per Object Type
Use
Functional locations can be assigned to Real Estate master data either manually or automatically (see PM
Integration: Define Settings per Object Type.
While processing master data, you can create notifications for these functional locations. Here you
specify what type of PM notification you can create for each object type.
Activities
For each object type, for which you want to create notifications in the master data dialog, specify
which notification categories should be available. For architectural objects, rental objects and
contracts, you can use a differentiation criterion to make even finer distinctions about notification
categories.
You can also enter the transaction that is used for entering the notifications. If you did not define your
own entry screens for notifications in Customizing for Plant Maintenance (PM), then enter the standard
transaction FOIW21 that is supplied by RE-FX. You use this transaction for entering notifications
within RE master data.
For more information, refer to Customizing of notification categories for Plant Maintenance, for example
Allocate Start Values for Transactions.
Dialog

Screen Layout
Field Groups
Field Groups
Use
Toolset.
Standard settings
Exception
Activities
WHATSAPP +255738656506
the field group.
Field Status
Use
check.
other fields).
Note
sequence.
The settings that you make here apply for all architectural objects. You can refine the settings for
each architectural object type in the Field Status per Architectural Object Type IMG activity.
For more information on the relationships between these settings, see Linking of Read Field
Modifications per Activity and the Read Field Modifications per Architectural Object Type.
Field Status per Architectural Object Type
Use
In this section, you specify for each object type how and if fields are displayed in dialog screens. Fields
can be:
- Hidden
- Optional entry
- Required entry
Activities
The Field Status Purpose field is no longer valid and has no meaning. However, it has to have the value
1 = Object originated in SAP System for technical reasons.
To go to the field selection screen, position the cursor on a row of the table and choose Field
Modification. Make your settings for each field group.
@0S@ Fields for which you set the Non-spec. indicator are always available for input.
Note
For more information on the relationships with the settings for each activity, see Linking of Read Field
Modifications per Activity and the Read Field Modifications per Architectural Object Type.
Views
Use
Example
Standard settings
Sections
Use
Standard settings
WHATSAPP +255738656506
item number.
Screens
Use
Standard settings
If you want to change a tab page, copy the standard tab page that is closest to the tab page
you have in mind, and give it a name in the customer name range (Y* or Z*). Then assign the
sections you want. The position number for user-specific entries also has to be other than 00 here.
Screen Sequences
Use
Standard settings
from 00 here.
Note

- Rental object:
- Contract:
"Standard."
Events
Tables
Synchronization of Architecture and Usage
Rules for Synchronization of Architecture and Usage
Use
In this menu option, you control which data is to be copied to the assigned usage objects when you create
usage objects from architectural objects or when you change architectural objects.
You can control the rules so that they apply:
- For specific object types only

- For complete or partial assignment
- When objects are created or changed
- For specific subobjects (such as business partner roles) in some cases
WHATSAPP +255738656506
The following considerations must be taken into account when objects are created:
- Only the entries for the complete assignment are evaluated.

- The address and object name for the usage object are always populated from the architectural
object.
The table is evaluated using default implementations of the BADI_REBD_AO_CLONE and
BADI_RECA_RG BAdIs. It is therefore only:
- Taken into account upon creation if there is no active customer implementation for
BADI_REBD_AO_CLONE
- Taken into account for changes if there is no active customer implementation for
BADI_RECA_RG
This does not apply if the customer implementation also uses this table.
Implement Enhancements (BAdI): Create Usage Object for

Architecture
Use
The BADI_REBD_AO_CLONE BAdI makes it possible to intervene in the creation of usage objects
from architectural objects. You can use the following methods:
COMPLETE_DATA_BE: Complete data for business entity
COMPLETE_DATA_BU: Complete data for building
COMPLETE_DATA_PR: Complete data for land
COMPLETE_DATA_RO: Complete data for rental object
Standard settings
Fallback class CL_IM_REBD_AO_CLONE provides a default implementation for the BAdI.
The fallback class is controlled using the entries to be maintained in the Rules for Synchronization of
Architecture and Usage menu option. The default implementation becomes inactive as soon as you
create and activate your own BAdI implementation.
Activities
If you create usage objects from architectural objects and you want to use data according to rules other
than those supported in this standard implementation, implement the BAdI to reflect your
requirements.
Implement Enhancements (BAdI): Change Usage Object for
Architecture
Use
If changes are made to architectural objects, these are not transferred to the assigned usage objects. The
BADI_RECA_RG BAdI is used to ensure that data in the usage objects is kept synchronized with the
architectural view data.
Standard settings
Fallback class CL_IM_RECA_RG provides a default implementation for the BAdI.
The fallback class is controlled using the entries to be maintained in the Rules for Synchronization of
Architecture and Usage menu option. The default implementation becomes inactive as soon as you
create and activate your own BAdI implementation.
Activities
If you want to synchronize data from the usage view with architectural view data, which applies other
rules, create a BAdI implementation and implement the synchronization according to your requirements.
The usage objects are synchronized in the following steps:
Step 1: Registration
If an architectural object that is assigned a usage object is changed, the fact that the usage object needs
to be changed must first be registered. BAdI method CREATE_REGISTRATIONS is relevant for
this step.
If you want to adjust the data in the usage object when it is changed in the architectural view, you need
to use this method to write a registration entry, assuming the corresponding data was changed in the
architectural view. This step is also required if "update immediately" is selected in step 2.
The method is called before the architectural object is saved. The registrations are created here.
Parameter IO_OBJECT contains the instance of the architectural object, CT_RECEIVER contains the
registrations to be created, and CT_MESSAGE contains the error messages.
Step 2: User Decision

In the dialog box displayed, the user can specify whether the usage object is to be changed immediately
or later. If the object cannot be changed immediately (because the target object is currently locked, for
example), a registration is written.
Step 3: Change to Usage Object

The change is made to the usage object: either immediately or based on the registration by processing the
worklist. In this step (processing of registrations), BAdI method UPDATE_RECEIVER is executed and
the usage objects are changed.
Parameter IO_OBJECT contains the instance of the architectural object, ID_RGGUID contains the
GUID of the registration, IS_DETAIL_X contains the registration, IF_SIMULATE contains the
WHATSAPP +255738656506
indicator for the simulation run, CT_ALSO_PROCESSED_RGGUID contains the GUIDs for the
registrations, which are then also completed, and CS_INFO_MSG contains the information message
from the update. Special Feature
Method READ_INITIAL_DATA
This method is called when an architectural object is called in change mode. The original values
(such as an address), which are no longer available later after the change, can be imported here.
Parameter IO_BUSOBJ contains the instance for the architectural object.
Example
Class CL_EXM_IM_RECA_RG contains an implementation example.
Enhancements
Implement Enhancements (BAdI): Validation and Substitution
Use
This Business Add-In supports enhancements of the standard functions of architectural objects. For an
Activities
Example
Enhancements of the user interface using the Business Data Toolset are explained in more detail in
Enhance BDT Applications
Implement Enhancements (BAdI): Number Assignment
Use
You can use this BAdI to control number assignment for architectural objects.
Implement the following methods:
- IS_INT_NUMBER_ASSIGNMENT: Set the flag CD_ISINTERNAL to ABAP_TRUE,

if you want to automatically assign a number for the architectural object using your own
BAdI implementation.
- GET_NUMBER: In this method, assign the number for the architectural object. Notes for
Developers
Implement Enhancements (BAdI): Create Usage Object for

Architecture
Use
The BADI_REBD_AO_CLONE BAdI makes it possible to intervene in the creation of usage objects
from architectural objects. You can use the following methods:
COMPLETE_DATA_BE: Complete data for business entity
COMPLETE_DATA_BU: Complete data for building
COMPLETE_DATA_PR: Complete data for land
COMPLETE_DATA_RO: Complete data for rental object
Standard settings
Fallback class CL_IM_REBD_AO_CLONE provides a default implementation for the BAdI.
The fallback class is controlled using the entries to be maintained in the Rules for
Synchronization of Architecture and Usage menu option. The default implementation becomes inactive
as soon as you create and activate your own BAdI implementation.
Activities
If you create usage objects from architectural objects and you want to use data according to rules other
than those supported in this standard implementation, implement the BAdI to reflect your
requirements.
WHATSAPP +255738656506
Graphic: SAP 3D Visual Enterprise
Overview: Integration Visual Enterprise
Use
RE-FX supports the storage of SAP 3D Visual Enterprise plans using DMS. The plans can be displayed
on the CAD tab page provided for SAP RE-FX master data. It is also possible to synchronize the RE-FX
master data with the plans in SAP 3D Visual Enterprise. Options are provided that allow you to make use
of graphical reporting using the CAD plans displayed.
BAdIs need to be implemented (programmed) to make these functions available and to associate the
attributes in SAP 3D Visual Enterprise with those from RE-FX.
Technical Requirements
Installation of SAP 3D Visual Enterprise Link Tool ( Author )

To be able to convert the plans (from Autodesk), SAP 3D Visual Enterprise Link version 8 , SP04 or
higher must be installed locally. The import settings for SAP 3D Visual Enterprise Link need to be
defined.
Installation of SAP 3D Visual Enterprise Viewer

To display the plans on the CAD tab page in SAP RE-FX, SAP 3D Visual Enterprise Viewer version 8,
SP04 or higher must be installed locally.
Configuring Document Management

SAP 3D Visual Enterprise is connected using document management. For more information, see the
Customizing documentation for Document Management.
- Set up a content repository and connect it to document management.

- Define the workstation application VRE with the following properties:
Description: Visual REFX Document
Archive identification: *
File suffix for application: cgm
File format: *.cgm
MIME type: application/cgm
Appl. icon: @DE@
Start authorization: Yes
Additional files: Yes
In the same dialog box, create the properties for the workstation application VRE in the network.
- Use transaction CT04 to create characteristic VRE_VALIDFROM with the following properties:
Name: Valid from
Status: Released
Data type: Date format
Valuation: Single value
- Use transaction CL02 to create class type VRE for class type 017 (document management) with the
following properties: Do not check
Characteristic: VRE_VALIDFROM
- Set up the document type VRE with the following properties:

Document type text: Visual REFX Document
Use KPro: Yes
Version assignment: Yes
Archiving authorization: Yes
Change documents: Yes
Number assignment: 1
Internal number range: 02
Class type: 017
Class: VRE
- Define the search sequence for viewable files as follows:

SAP application: DRAW
Display application: Viewer
Use: ( blank )
Seq. no.: 0
Document type: VRE
If you also want to create XML files, create the following additional entry:
SAP application: DRAW
Display application: Viewer
Use: XML
Seq. no.: 4
Document type: VRE
Workstation application: XML
Define BADI_RECA_CAD_SERVICES
Use
This BAdI provides service methods in relation to the CAD integration with RE-FX.
Standard settings
- Method GET_CAD_OBJTYPE
Changing parameter CD_OBJTYPE (object type) is used to define whether the RE-FX object
linked to the CAD plan exists in the usage (for example "IM") or in the architectural view ("I0").
This setting is defined for an implementation and cannot be defined for each object.
- Method GET_AOFUNCTION_NOT_AVAIL
Changing parameter: CD_AOFUNCTION
If objects are to be classified as not available temporarily for the occupancy, this can be done by
defining the Function field accordingly in the master data. This method returns the value that is
used in your system for objects that are not available.
-Method GET_TASK_PARAM
Changing parameter: CS_TASK_PARAM (parameter for parallel processing),
CD_OBJ_PER_TASK (number of objects per task)
If parallel processing is to be used for performance reasons, the fields for changing structure
CS_TASK_PARAM need to be filled. These are the following fields: SERVERGRP (server
group for parallel processing), MAXTASKS (max. no. of parallel tasks), SINGLETASKMODE
(generate tasks on local server only)
Parameter DD_OBJ_PER_TASK determines the number of objects per task (package size). When
hierarchical objects are being created, it is important to ensure that the objects are also created
correctly in the hierarchy as failing to do so may result in errors.
WHATSAPP +255738656506
- Method IS_OBJECT_ZOOMABLE
Import parameter: IO_BUSOBJ
Changing parameter: CD_IS_ZOOMABLE
This method is used to specify whether zooming is to be possible for the object in the CAD plan.
A prerequisite for this is that it has a corresponding representation in the CAD plan and can be
accessed from the metatdata with any ID.
- Method GET_ERROR_STOPS_SYNC
Changing parameter: CD_STOPS_SYNC
If synchronization is not to be carried out in the event of an error, you need to select this parameter.
Define BADI_RECA_CAD_PROCESS_SYNC
Use
This BAdI controls the synchronization of master data for RE-FX with the data from CAD plans.
Requirements
- Method ADD_CUST_FIELDS_TO_MAP_TABLE
Changing parameter: CT_MAPPING (mapping table)
A mapping between the RE-FX data and the metadata for the CAD plans serves as the basis for
the synchronization. This method adds user-defined fields to the mapping table. This allows
customer-specific structures to be created that are used as the basis for the entire synchronization
logic. The following standard fields are always part of the mapping structure and must not be
changed:
BUSTYPE (object type), BUSKEY (object key), OBJID (object identification in the CAD plan),
CHANGEIND (change indicator)
Add more fields by specifying the structure (field: structure) and field (field: field) or by specifying
the data element (only field: field). The field name (fieldname) can be selected freely.
- Method GET_OBJECT_VALUES_CAD
Import parameter: IO_OBJECT (business object of the object linked to the CAD plan),
IO_CAD_PROVIDER (CAD provider), IO_MSGLIST (message collector), ID_KEYDATE
(key date)
Changing parameter: CS_BUSOBJ_CAD (dynamic structure of the CAD object) In this
method, the individual fields of the dynamic structure must be filled based on the CAD data
on the key date.
- Method GET_OBJECT_VALUES_SAP
Import parameter: IO_MSGLIST (message collector), ID_KEYDATE (key date)
Changing parameter: CS_BUSOBJ_SAP (dynamic structure of SAP object) In this method,
the individual fields of the dynamic structure must be filled based on the SAP data on the key
date.
- Method CHANGE_STATUS_TAB
Import parameter: IO_OBJECT (business object of the object linked to the CAD plan)
Changing parameter: CT_TABLE_SAP (dynamic table of SAP objects), CT_TABLE_ALL
(dynamic table of all objects)
This method allows both the values of the table of SAP objects and the status table to be adjusted
again following the comparison.
- Method CREATE_UPDATE_OBJECTS
Import parameter: IO_OBJECT (business object of the object linked to the CAD plan),
IO_CAD_PROVIDER (CAD provider), ID_KEYDATE (key date), ID_TESTRUN (test run
indicator), IO_MSGLIST (message collector), IS_TABLE_ALL (dynamic structure of an object)
The object in question needs to be updated or created in this method. This method is executed both
in standard processing and in parallel processing (multiple processes on the application server).
Define BADI_REEX_ACTIONS_VE
Use
Implement this BAdI if you want to display and synchronize CAD plans from SAP 3D Visual Enterprise
in RE-FX. The methods are used to control interaction for specific objects in RE-FX with objects in SAP
3D Visual Enterprise.
Requirements
For more information about the settings required, see here.
- Method CREATE_ID_FROM_METADATA
Import parameter: IO_OBJECT (any object with the object linked to the CAD plan),
IT_METADATA (metadata of the CAD plan)
Changing parameter: CD_OBJECT_TYPE (object type), CD_OBJECT_ID (object ID) Using
the import parameter of the object linked with the CAD plan and the corresponding metadata,
the changing parameter must return the object type (IO for architecture or IM for usage view)
and the object ID, such as the AOID.
- Method GET_METADATA_IDENTIFIER
Changing parameter: RF_IDENTIFIER (ID field in the viewer)
This returns the ID of the metadata table in SAP 3D Visual Enterprise (such as '\ID'). This field
must be centrally defined within the CAD plan and is used for communication between the plan
and the application.
- Method GET_ACTION_TABLE
Import parameter: IO_OBJECT (any object with the object linked to the CAD plan)
Changing parameter: RT_ACTION (table for interaction)
This method returns the table of interaction for the context menu (accessed by right-clicking the
mouse). To be able to control the context menu for specific objects, the object linked to the
CAD plan is transferred as the import parameter. The entries from table RT_ACTION have the
following fields: ACTID (action ID), DESCRIPTION (description), RETURN_DATA (return
data values for action in SAP 3D Visual Enterprise
Viewer)
The value of ACTID can be any number. The description (DESCRIPTION) is displayed as
an entry in the context menu. Select '02' as the value for RETURN_DATA.
WHATSAPP +255738656506
- Method GET_MARKTYPE_TABLE
Import parameter: ID_QUERYID (ID of report)
Changing parameter: CT_LEGEND (legend with marking types for graphic),
CT_MARKTYPE_MAP (table of marking types)
For the query function (thematic report), the colors to be used for each thematic report are
specified here. The table of marking types has the following fields: MARKTYPE (value from
the legend), STYLE (such as 'background-color:#D02434'),
COLOR (such as '#D02434'), OPACITY (such as '0')
STYLE is the color for the legend and the color for the CAD plan must also be specified in
COLOR in a similar way. OPACITY indicates the level of transparency.
- Method GET_TITLEINFO_FROM_METADATA
Import parameter: IT_METADATA ( metadata )
Changing parameter: CD_OBJECT_TYPE (business object type of the object),
CD_OBJECT_ID (ID of object), CD_KEYDATE (key date)
For the purposes of the upload function on the CAD tab page, whether the corresponding plan
header information from the CAD plan is read and is to be used for further processing is
specified here. If the object (CD_OBJECT_TYPE and CD_OBJECT_ID) is returned, for
example, this is checked in the standard logic against the object for which a CAD plan is
currently being uploaded. If these do not match, an error message is displayed. If the
CD_KEYDATE field is returned, the CAD plan is created automatically as a DMS document
for the key date. If the value is not read from the plan header information, this is to be entered
manually by the user.
- Method GET_LABELLING_PARAM
Changing parameter: CD_FONT (font), CD_FONT_SIZE (font size), CD_TEXT_COLOR
(text color), CD_BG_COLOR (background color), CD_FRAME_COLOR (frame color),
CD_OPACITY (opacity value for color rule), CD_DL_SIZE (scaling factor),
CD_LABEL_POSITION (offset of dynamic label), CD_PIVOT_POINT (coordinate for dynamic
label), CD_MARGIN (text filling), CD_ALIGNMENT ( alignment )
This method returns the parameters for the label function that is called for thematic reporting. If
the first four parameters are not filled, a label is not written to the fields for
the thematic report. For information about how the individual parameters are to be filled, see the
documentation for class CL_GUI_VIEWER_CONTROL ( method SET_DYNAMIC_LABEL).
- Method CHANGE_METADATA
Import parameter: ID_KEYDATE
Changing parameter: CT_METADATA
This method allows the metadata read from the CAD plan to be adjusted individually to reflect
customer needs.
- Method GET_DMS_UPLOAD_INFO
Changing parameter: CD_DOCTYPE (document type), CD_FILEEXTENSION_SOURCE (file
extension of source file), CD_FILEEXTENSION_TARGET (file extension of target file),
CD_DOCSTATUS (document status), CD_STORAGE_CAT (storage category for original
files), CD_ADDITIONAL_XML (should an additional XML file be generated?),
CD_CONVERSION_SECONDS (waiting time until the conversion is completed) This method
returns the parameters required for the upload function on the CAD tab page. For information
about setting the document type, see . Parameter CD_ADDITIONAL_XML allows you to create
an additional XML file in the document management system. Parameter
CD_CONVERSION_SECONDS specifies how long (in seconds) the system is to wait for the
conversion to be completed in the background for the files using the SAP 3 D Visual Enterprise
Link tool. If a value is not provided, a default waiting time of 60 seconds applies.
- Method DO_ACTION
Import parameter: IS_ACTION (structure for interaction), IO_OBJECT (business object) In this
method, the interaction specified in the GET_ACTION_TABLE method is executed. The
objects selected in the CAD plan are provided in structure IS_ACTION for this purpose.
- Method GET_TOOLTIP_IDENTIFIER
Changing parameter: RF_IDENTIFIER
The initial tooltip can be provided in this method.
Contract
Number Assignment
Number Range for Contracts
Use
In this activity, you specify how number assignment is to be handled for your contracts. The specification
applies for one company code. You can assign number range intervals to the individual contract types.
For external number assignment, you can specify the number range for the contract.
in the "Number Range Level" field.
If you want the system to generate the number automatically based on the objects in the contract, you
can use a BadI. Go to the Contracts: Number Assignment, Validation Substitution Customizing
activity. If you use this option, set number assignment to "internal" here.
Automatically Generate Contract Number
Use
In Release 10 this point related to Business Transaction Event (BTE) 00708001 Lease-In: Number
Assignment. To check if the BTE was implemented, use transaction FIBF.
This BTE is no longer called. Instead, use the GET_NUMBER method of Business Add-In
RECN_CONTRACT.
Contract Type
Define Contract Types
Use
WHATSAPP +255738656506
In this section, you specify the contract types. The contract type indicates the purpose for which the
contract is used. Possible contract types include:
- Lease-in
- Lease-out
- Administration
- Assessment contract ( COA )
- Purchase
- Sale
- Service contract
- Security deposit agreement
- Internal right of use
- Lease
The contract type uses the following parameters to influence how the contract behaves during various
processes:
Contract category
Specifies:
- External contract:
The main contractual partner is a customer or vendor with an account reflecting this status
(customer/vendor account or FI-CA account).
- Internal contract:
The contract allows costs or revenue to be posted regularly to a cost center, order, or project.
- G/L account contract:

The contract is used for repetitive postings to a G/L account (for example, for accrual or deferral
postings).
Offerer/User indicator
Specifies, from the point of view of the company code for which the contract is created, whether an
object or service is being offered or used. For example, you should choose Offerer for assessment
contracts (company code: COA, contractual partner: owner) and lease-outs (company code: object
company code, partner: tenant). This setting ensures, for example, that the system finds the correct
contracts during service charge settlement and COA settlement. For contracts, for example, where
the company code leases-in an object, you should set this indicator to "User".
Contract Reference
Specifies how the assignment of objects to a contract affects these objects. Along with the Offerer/User
indicator, this indicator controls certain processes, such as settlement processes ("leased out",
"assessment contract") and option rate determination ("leased out").
@0S@ If you choose Objects Are Leased-Out in this field, you can only assign object groups and
rental objects to the contract in the user dialog. This applies regardless of which object types
(buildings, rental object, business entity, and so on) you have assigned to the contract type in the
Permitted Object Types per Contract Type Customizing activity.
Contract Type - Security Deposit Agreement

You can create a security deposit agreement for a contract. Here you specify the contract type for this
security deposit agreement. Choose the contract type using the input help. The system only offers
contract types that are intended for security deposit agreements.
Recommendation:
Create at least one contract type for security deposit agreements. If you want to use security deposit
agreements for objects that are leased-in as well as those that are leased-out, you should create different
contract types for each.
Influence Holdings
This indicator is only relevant for land use management contracts. It controls how the assigned parcels
are considered in the area analysis for the respective parcel.
Screen Sequence
Here you can enter a screen sequence that has already been defined. This allows you to specify which
screens appear in which order in the maintenance dialog for this contract type (transactions RECN and
RE80).
For transaction RECECN for balance sheet valuation of contracts, you can specify an alternative screen
sequence.
SAP provides screen sequences in the standard system. The following can be used for normal contract
maintenance:
- SAP Contract: Contract Maintenance

This is the standard screen sequence.
- Like the standard screen sequence, but with a quick overview:

Compared to the standard screen, the view of the objects, the term, and assignment of profit
center and business area are displayed in a more simplified form on the first screen. This screen
sequence is best suited for contracts to which normally only one rental object is assigned (that is,
residential lease-outs).
- SAP Contract: Security deposit agreement

This screen sequence offers only screens that are relevant for security deposit agreements. Assign
this screen sequence to all security deposit agreements.
Condition Group
You can assign contracts only conditions with condition types from the condition group entered here for
the contract type. Choose an appropriate condition group, or create a new condition group and assign
the required condition types to it. In the CF Period field, you specify how far in advance cash flow
records are to be generated by entering the number of years.
Partner Management
In this area, you can specify one or two roles for the main business partner. You cannot activate a
contract until it has exactly one business partner with this role.
Object Groups
In this area, you specify how numbers for object groups are to be automatically generated.
Number Range
In this area, you specify the number range interval that provides the numbers for this contract type.
Additional Parameters
WHATSAPP +255738656506
Certain default values (condition group, option rate method) depend on the contract type. Therefore,
SAP recommends that you create different contract types for commercial contracts and residential
contracts.
Activities
Check the standard settings and change them as needed. To do so, select the contract type and choose
@16@ Details.
To define new contract types, choose New Entries. Enter a name for the contract type and make the
specifications described above.
@0S@ Customizing for Flexible Real Estate Management is already fully set up for four-character
contract types beginning with CO, CU, and CX. The other contract types are used in Classic RE. If
you do not already have contracts in the system that use the Classic RE contract types, you can delete
Classic RE contract types.
Objects
Permitted Object Types per Contract Type
Use
Here you specify for each contract type (differentiation criterion) which objects can be assigned to
contracts of this type. Here you can also assign real estate objects (in contrast to master data objects) as
Assignment Objects. In addition, you can specify that these objects can be grouped together into object
groups.
The objects that you assign the contracts to can be used as distribution objects. In addition to real estate
object types, the following objects are allowed: orders, cost centers and WBS elements. However, it is
not possible to assign fixed assets or functional locations to contracts.
Activities
1. Specify the object types that you want to assign to each other.
2. Specify if costs and revenues are allowed to be distributed to the assigned objects.
3. Specify if assigning the object to an object group is allowed.
4. Specify how the Informational Assignment indicator should apply for the objects of the given object
type:
- Custom
Any type of assignment can be used (Informational and Informational Not Allowed).
- Informational
The object is only allowed to be assigned for informational purposes, for example, so that
maintenance, cleaning, or advertising costs can be distributed to it. In occupancy contracts,
this setting makes sense for all object types except the rental object.
- Informational Not Allowed

The object can only be assigned as not for informational purposes. In occupancy contracts,
this setting is only useful for rental objects. The rental object is then not allowed to be
assigned to any other occupancy contract during the period of the assignment.
- Lower-Level Objects
If there are subordinate objects for the assignment object type, and the objects types of this
object are allowed to be assigned, then you can set the Lower-Level Objects indicator.
Then the system offers another function in the context menu. You can use it to display the
lower-level objects (in the next level) of one or more selected objects. If you choose, you
can also assign these objects.
Define Contract Types to Propose for Usage Type
Use
Here you can specify which contract types are allowed for which usage types of a rental object.
Activities
You do not have to make a specification here for contract types that are not for rental objects.
You should use this step to enter contract types that are solely for commercial rental or solely for
residential rental. This assignment is only a means of assisting you when you enter the contract. The
system checks if all rental objects for the contract have the correct contract type. If they do not, the
system normally issues message RECN043 as a warning. You can suppress this warning message, or
have the system issue an error message (see reference).
When you create a contract from the processing screen of the rental object (choose Rental Object ->
Create Contract or Rental Object -> Create Next Contract), then the system proposes only the
contract types that agree with the usage type. If the system finds only one contract type, then the
dialog box for entering the contract type is not called.
The system acts in a similar way when you create a contract offer for a rental object or RE search
request. In this case, the selection is also limited to the contract types that agree with the usage type of
the offered object.
If you use different contract types for leasing commercial objects than you do for leasing apartments,
then you should assign these usage types to the contract types accordingly.
WHATSAPP +255738656506
Renewal
Renewal Rules
Use
In this step, you specify the rules for renewal of real estate contracts. There are two types of contracts in
this respect:
1. Without fixed term (no renewals, since

there is no defined contract end)
2. With fixed term (renewal rules used)
There are two variants of renewal rules:
a) Renewal
Renewals define how the contract term is extended after the contract end is reached, for example, by
one year. In contrast to options, renewals always take effect automatically. If a renewal should not
take effect, then it has to be rejected in writing by either the contractee (such as the tenant) or
contractor (such as the landlord).
b) Option
The contractee has the option to extend the contract while retaining the current conditions. Options
have to be accepted by the contractee in writing ("express statement") before they take effect. When
there is more than one option, each one has to be accepted in writing individually. The acceptance of
the option results in the extension of the contract term. If the date for the acceptance passes without
this express statement being made in writing, then all subsequent options for the contract are also
invalid.
You can define both variants of renewal rules on one contract, for example two options and a renewal. In
such cases, the options always take precedence over the renewal.
Activities
If you want to define new renewal rules, choose New Entries. Enter an internal number and a
name for the renewal rule. When you create a renewal, you can choose from three different types of
automatic renewal rules in the Aut.Renew.Type (automatic renewal type) field:
- One or More Repetitions (for example, extension of 3 years with a 6 month period for submitting
rejection)
- Repetition of Last Rule (for example, the contract is extended repeatedly by 1 year, with a
6 month period for submitting rejection)
- Unlimited after This Point (after the contract end date or the acceptance of prior options and
renewals, the contract changes over to an unlimited term, and notice can be given within the legally
defined notice period at the end of the year)
You can also enter a long text description of each rule by choosing the @0Q@ Editor. This text can
then be called in the application.
Save.
Select one of the rules, double click on Extension Periods in the dialog structure, and choose New
Entries. In this table you can define one or more extension periods for renewal rules.
Number = Number of options or renewals (for example, 2 options with 1 year term means that the
contract can be extended twice by one year)
RnwYrs, RnwMos, RnwDys = Number of years/months/days in the extension period
Rounding = For the contract end, you can round to the first or last day of the month. If you leave this
field blank, then the system uses the actual date of the contract end (for example, th of the month).
NtfY, NtfM, NtfW, NtfD = Date (years/months/weeks/days) notice has to be given ( for example, 6
months before end of contract)
Choose @38@ Check to have the system check if the extension periods are valid with the automatic
renewal rule.
Notice
Notice
Use
In this section, you make settings for giving notice and for processing notice periods in a contract.
1. Notice Rules
You can enter the following notice rules:
a) Contracts without a notice period

b) Contracts with period regulations, for example, notice can be given on the contract within a
period of 3 months before contract end, at the end of the month
You can either create period regulations separately in the contract (free period regulations) or
set them up in Customizing with a key so they can be used in multiple contracts. In the second
case, you can call the period regulation when you create the contract.
c) The contract has a deadline regulation. This means that notice can only be given at certain
intervals, such as the end of the quarter.
You can either create deadline regulations separately in the contract (free deadline regulations) or
set them up in Customizing with a key so they can be used in multiple contracts. In the second
case, you can call the deadline regulation when you create the contract.
2. Notice Procedures
You can enter notice procedures, for example, in order to be able to enter different notice rules for
the contractee and contractor in the same contract.
3. Notice Reasons
You can enter notice reasons when notice is given. The notice reason also contains a record of
whether notice was given by the contractee or contractor. With the exception of the vacancy
reason, these entries are for information only.
4. Reasons for Rejection

WHATSAPP +255738656506
You can also enter reasons for rejection, as additional information.
Notice Rules: Period Regulations
Use
In this step, you specify various period regulations for automatic calculation of notice dates for real estate
contracts.
These regulations are defined dependent on the contract term. You can specify notice periods that are
calculated based on months (that is, monthly, quarterly, semi-annually), but you can still make the
calculation of the notice date dependent on the exact day that the written notice is received. You
simulate this calculation by choosing @8Z@ Simulate.
In the contract in the application, you can also define indidual period regulations. You can specify there
if the period regulation is valid for the contractee (tenant), contractor (landlord) or both.
Activities
Choose New Entries. Enter a short name and a long name for the period regulation. Return to the initial
screen. To enter one or more periods for a rule, select the rule, and double click on Periods in the dialog
structure. Choose New Entries.
Enter a sequential number for each period. Enter the notice date (for example, End of Quarter) and the
notice period (for example, 3 months). You can also enter a number of days for a grace period, and if
this refers to calendar days or business days.
Save.
Notice Rules: Deadline Regulations
Use
In this step, you specify deadline regulations for automatic calculation of notice dates for real estate
contracts.
These regulations are defined with dependency on the contract term. For example, you can define four
notice dates per year (at the end of each quarter). You can make the calculation of the notice date
dependent on the exact date on which notice is received. You simulate this calculation by choosing
@8Z@ Simulate.
In the contract in the application, you can define individual deadline regulations. You can specify
there if the deadline regulation is valid for the contractee (tenant), contractor ( landlord ) or both.
Standard settings
Activities
Choose New Entries. Enter a short name and a long name for the deadline regulation. Return to the
initial screen. To enter one or more deadlines for a rule, select the rule, and double click on Dates in
the dialog structure.
Choose New Entries.

Enter a sequential number for each date. Enter the notice day and month (for example, 31 and 06) and
the date the notice has to be received. Specify if this refers to business days or calendar days.
Save.
Notice Procedures
Use
In this step, you can create notice procedures with multiple notice rules. This applies, for example, to
contract terms in which different periods of notice apply for the contractee ( tenant ) and contractor (
landlord ).
Requirements
You have to have specified the necessary notice rules in the following IMG activities:
1. Notice Rules: Define Period Regulations

2. Notice Rules: Define Deadline Regulations
Activities
If you want to define notice procedures in addition to the standard notice procedure ( see : example),
choose New Entries on the initial screen. Enter a sequential number and a unique name for the notice
procedure.
Editor: Here you can enter notes for your notice procedure. You can call this text in the contract by
choosing Display Note.
Return to the initial screen. Select the notice procedure, double click on Rules in the dialog structure.
Choose New Entries. Choose the notice rule you want using the input help, and define the party it
applies to. Choose @38@ Check. The rule appears in the table.
Save. You can simulate the calculation of the notice date by choosing @8Z@ Simulate.
Example
Standard Notice Procedure for Residential Rental:

Notice period for the tenant is a constant 3 months.
Notice period for the landlord is:
a) For a term up to 5 years, 3 months

b) For a term up to 8 years, 6 months
c) For a term of 8 years or more, 9 months
WHATSAPP +255738656506
Notice Reasons
Use
You can enter reasons for notice. You enter, for example, if notice was given by the the contractor
(landlord) or the contractee (tenant). With the exception of the vacancy reason, these entries are for for
informational purposes only.
Activities
- Choose New Entries.

- Enter an internal number and a name for the notice reason (for instance, 01 rent increase). Choose
the party that initiated the notice. If applicable, set the Extraord. ( Extraordinary ) indicator.
- Specify the vacancy reason that should be set on the rental object as a result of notice being given.
Reasons for Rejection
Use
You can enter short texts containing the notice reasons.
If necessary, you can assign these texts to a notice.
Use
The Business Add-In ( BAdI )
- makes it possible to enhance the standard behavior when saving a notice and -
to change the reason for notice for already active notices.
Activities
You can implement the following methods of the BAdI using transaction SE19:
- AFTER_STORE (Perform additional actions after saving) Parameters:

IO_OBJECT Generic object reference
IT_OLD_LIST Notice - old status
IT_INSERT_LIST Notice - new
IT_UPDATE_LIST Notice - changed
IT_DELETE_LIST Notice - deleted
IT_OLD_OBJREL Assigned contract objects of the notice - old
status
IT_INSERT_OBJREL Assigned contract objects of the notice - new
IT_UPDATE_OBJREL Assigned contract objects of the notice - changed
IT_DELETE_OBJREL Assigned contract objects of the notice - deleted
When a notice is saved, this method is called exactly once in order to perform its own additional
actions.
- GET_BEHAVIOR_CONTEXT (Gets the behavior context of the notice)

Parameters:
IO_OBJECT Reference of the real estate contract
IS_NOTICE Entry to be changed in the table of notices
IT_NOTICE_DB All notices saved on the database ( table
VICNNT)
CF_CHANGE_NTREASON Allow change of notice reason?
Using this method, you can allow a change of the notice reason for already activated notices. Set
the changing parameter CF_CHANGE_NTREASON = 'X'.
Within this method, it is imperative that you do not issue a message directly using MESSAGE (without
addition of RAISING ERROR), nor are you allowed to use the COMMIT WORK and ROLLBACK
WORK statements, since this could cause data inconsistencies.

Attributes
Account Determination Values
Use
In addition to account symbols, you can define account determination values. You enter them in
posting rules on the contract or rental object, and they control account determination for automatic
postings.
Industry System and Industry
Use
In processing of contract master data, you can assign an industry to the contract. This industry can be
used in reporting. This attribute is informational only.
In the RE context, the system always uses the standard industry system.
WHATSAPP +255738656506
For more information on the individual settings, refer to this text.
@1A@ Note that the settings you make here affect other applications (for example, central business
partner management).
Define Measurements for Contract
Use
Here you can limit or allow specific measurement types for contract types, and also specify the reference
to the differing measurement You need these settings for the service charge settlement, for example, if
you have defined measurements as an apportionment criterion in the activity measurement types.
Requirements
You have defined the measurement types.
Activities
Enter the following for each measurement type and contract type:
- Allow measurement types for the contract type.

- The reference to the contract types
Security Deposit Agreement
Security Deposit
Use
The security deposit agreement is created as a separate contract.
Activities
In Customizing, define contract types for security deposit agreements in the "Contract Types" IMG
activity. Assign these contract types in another step to contract types that are used for security deposit
agreements.
You also have to define security deposit types.

Contract Types for Security Deposit Agreement
Use
Define the contract types you need for your security deposit agreements. Use contract type Customizing.
Assign the newly defined contract types to those contract types that will need security deposit
agreements.
Security Deposit Type
Use
You define security deposit types here.

For the agreed security deposit, which is usually specified before the contract is signed, you have to
enter a security deposit type. The amounts of the actual security deposit (= security deposit actually
paid) can be distributed in different ways.
Activities
Create the security deposit types you need and assign the form of security deposit to each one. The forms
of security deposit are predefined and fixed. Using the form of security deposit, the system checks if your
entries are consistent.
Entering a business partner role that is relevant for this security deposit type is optional. If you do enter
a partner, the system then assigns the actual security deposit, which has this security deposit type,
automatically to the partner that has this role (from the partners assigned to this security deposit
agreement).
If you do not enter any roles here in Customizing, you have to assign the partner manually, if you need
one.
Enter only roles that are assigned to the application TR0036 - Real Estate Contract, since it is not
possible to assign partners with other roles to the contract. The input help shows all applicable roles. If
you need different roles, assign them to the application TR0036 first.
WHATSAPP +255738656506
Dialog

Screen Layout
Field Groups
Field Groups
Use
Toolset.
Standard settings
Exception
Activities
the field group.
Field Status
Use
check.
other fields).
Note
sequence.
The settings that you make here apply for all contracts. You can refine the settings for each contract type
in the Field Status per Contract Type IMG activity.
For more information on the relationships between these settings, see Linking of Read Field
Modifications per Activity and the Read Field Modifications per Contract Type.
Field Status per Contract Type
Use
In this step, you specify, per contract type, the fields that are:
- Hidden
- Optional entries
- Required entries
Activities
To reach the field selection, select a contract type and choose Field Modification. Make the settings you
want for each field group.
Fields for which the Not spec. indicator is set are always available for input.
Note
For more information on the relationships with settings per activity, see Linking of Read Field
Modifications per Activity and the Read Field Modifications per Contract Type.
WHATSAPP +255738656506
Views
Use
Example
Standard settings
Sections
Use
Standard settings
item number.
Screens
Use
Standard settings
If you want to change a tab page, copy the standard tab page that is closest to the tab page
you have in mind, and give it a name in the customer name range (Y* or Z*). Then assign the
sections you want. The position number for user-specific entries also has to be other than 00 here.
Screen Sequences
Use
Standard settings
from 00 here.
Note

- Rental object:
- Contract:
"Standard."
WHATSAPP +255738656506
Events
Tables
Contracts: Number Assignment, Validation, Substitution
Use
The Business Add-In assists you in enhancing the standard functions of real estate contracts. For an
Activities
Please note that the method SUBSTITUTE is not processed for contracts if the user is only authorized to
maintain the valuation for contracts (authorization objects F_RECE_TM and F_RECE_PR.) and not
authorized to maintain contracts (authorization object F_RECN). Display authorization for contracts is
not sufficient here.
Example
Implement Enhancements (BAdI): "Overviews" - Own Evaluations
Use
example.
General Settings for Master Data and Contract
Assignment of Objects from Other Components
Assign Functional Locations/Fixed Assets/Projects/CO Orders
Use
You specify here which assignments are allowed between real estate objects, and which assignments are
allowed from master data of other components to real estate objects. Not all object assignments are
supported in the standard system. There are options for making enhancements, but these involve writing
programming code.
Assignment of Real Estate Objects to Real Estate Objects
Assignments from real estate objects to real estate objects are generally for informational purposes
only.
In the COA company code, you can assign real estate objects from other company codes. The
assignment of rental objects from other company codes to the COA rental objects (condominiums)
forms the basis for tenant settlement.
Assignment of Assets
Asset assignments are always treated as informational only. Assignments of assets to contracts cannot be
used for distribution postings.
Assignment of Functional Locations to Real Estate Objects
WHATSAPP +255738656506
It is possible to assign functional locations to real estate objects. This assignment is informational
only. When you assign functional locations, you can also create malfunction reports for the functional
location directly from the real estate object. You assign PM transactions in the Define PM
Notifications per Object Type IMG activity.
Assignments to Contracts
Here you specify for each contract type (differentiation criterion) which objects can be assigned to
contracts of this type. Here you can also assign real estate objects (in contrast to master data objects) as
Assignment Objects. In addition, you can specify that these objects can be grouped together into object
groups.
The objects that you assign the contracts to can be used as distribution objects. In addition to real estate
object types, the following objects are allowed: orders, cost centers and WBS elements. However, it is
not possible to assign fixed assets or functional locations to contracts.
Assignment to Correction Objects
In correction objects, you can use assignments from other objects for the following purposes:
- Determining the option rate: The rental objects that are assigned directly or indirectly using other
real estate objects (such as buildings or participation groups) are used for determining the option
rate of the correction object.
- Allowed original account assignments: Documents with account assignments of entered objects
(assignable real estate objects except for settlement units, cost centers, orders, WBS elements,
assets) are allowed for the assignment to a correction object.
- Account Assignment: You can make account assignment of the revenue or cost items of the input
tax correction posting using these object types.
Activities
- To each object type, assign the object type of the object that you are allowed to assign to it.
- Use the Differentiating Criterion to make additional differentiations for the assignment of contracts,
architectural objects, and rental objects.
- For contracts, also specify the following:
1. Specify the object types that you want to assign to each other.
2. Specify if costs and revenues are allowed to be distributed to the assigned objects.
3. Specify if assigning the object to an object group is allowed.
4. Specify how the Informational Assignment indicator should apply for the objects of the given object
type:
- Custom
Any type of assignment can be used (Informational and Informational Not Allowed).
- Informational
The object is only allowed to be assigned for informational purposes, for example, so that
maintenance, cleaning, or advertising costs can be distributed to it. In occupancy contracts,
this setting makes sense for all object types except the rental object.
- Informational Not Allowed
The object can only be assigned as not for informational purposes. In occupancy contracts,
this setting is only useful for rental objects. The rental object is then not allowed to be
assigned to any other occupancy contract during the period of the assignment.
- Lower-Level Objects
If there are subordinate objects for the assignment object type, and the objects types of this
object are allowed to be assigned, then you can set the Lower-Level Objects indicator.
Then the system offers another function in the context menu. You can use it to display the
lower-level objects (in the next level) of one or more selected objects. If you choose, you
can also assign these objects.
PM Integration
PM Integration: Make Settings per Object Type

Use
In this section you specify how functional locations are treated. They can be
- Created automatically
- Created and updated automatically
- Not created automatically
You make the settings separately for each company code in which you want to manage real estate
objects. If you do not make settings for a company code, then the No Automatic Maintenance setting
applies automatically.
Activities
1. Choose New Entries.

2. Enter a company code and the object type of the usage view, and choose the setting you need in the
Aut. FL (automatic functional location) field.
If you do not choose not to have the system create functional locations automatically, you can
manually create functional locations for usage objects of this type in master data processing. Or
you can link existing functional locations with usage objects of this type.
3. In the Object Type ID field, you can specify the prefix that functional locations for this object type
receive.
4. In the StrIndicator (structure indicator) field and FuncLocCat (functional location category) field,
you enter the traits that the functional locations for this object type have.
WHATSAPP +255738656506
5. For architectural objects, make the necessary settings in the Make Settings per Architectural Object
Type.
Define PM Notifications per Object Type
Use
Functional locations can be assigned to Real Estate master data either manually or automatically (see PM
Integration: Define Settings per Object Type.
While processing master data, you can create notifications for these functional locations. Here you
specify what type of PM notification you can create for each object type.
Activities
For each object type, for which you want to create notifications in the master data dialog, specify
which notification categories should be available. For architectural objects, rental objects and
contracts, you can use a differentiation criterion to make even finer distinctions about notification
categories.
You can also enter the transaction that is used for entering the notifications. If you did not define your
own entry screens for notifications in Customizing for Plant Maintenance (PM), then enter the standard
transaction FOIW21 that is supplied by RE-FX. You use this transaction for entering notifications
within RE master data.
For more information, refer to Customizing of notification categories for Plant Maintenance, for example
Allocate Start Values for Transactions.
Implement Enhancements for PM Integration ( BAdI )
Use
The Business Add-In supports enhancements to the standard functions of the Integration with Plant
Maintenance (Automatic Creation of Functional Location).
For an overview of the possible enhancement methods, see this text.
Activities
Create a BAdI implementation and implement the methods you require for your enhancement. Then
activate the BAdI implementation.
The following methods exist:
- GENERATE_LABEL - Generates the name of the automatically created functional location

- ADAPT_DATA - Adjusts the data of the functional location that was generated in RE-FX
- UPDATE_CLASSIFICATION - Allows updating of the classification of the functional location
that was generated in RE-FX
These methods are called automatically when the functional location is created or changed. If an
implementation exists, the methods are always called in addition to standard system behavior.
The implementation of the methods has to be independent of the interface. It must not contain any
COMMIT WORK or ROLLBACK WORK statements.
For example, direct output of messages using the MESSAGE statement is not allowed.
Method description
- GENERATE_LABEL
The generated name of the automatically created functional location can be changed here. The
IO_OBJECT parameter contains the real estate object for which the functional location is created.
CD_LABEL contains the name that was generated by RE-FX for the functional location. At this
position, the name can be generated again using a separate logic.
- ADAPT_DATA
This method is used to fill the data of the functional location that was created in RE-FX. It is
called during both creation and updating (depending on the Customizing settings for the functional
location). The IO_OBJECT parameter contains the real estate object for which the functional
location is created or updated. CS_FUNC_LOC contains the current data of the functional location,
with RE standard logic already added. Notes for Developers
Terms
Specify Default Text for Naming Terms
Use
The system creates certain terms automatically in the case of certain events, such as creation of a rental
object. The system then automatically creates a posting term with an <initial> key. Here you specify
names for these automatically created terms.
Example
The texts of the default terms of vacancy posting rules are particularly important. There can be several
automatically created terms, and it has to be possible to distinguish them from one another. The term
is automatically generated when the object is created, if you set this up in the Vacancy Reason IMG
activity (also refer to the Generate at Creation indicator). For example, there could be two cost centers
- the one responsible in the case of normal vacancy, and one that is responsible for the object during
renovations.
In this case, Customizing should be set up so that when an object is created, the default term named
<Renovation> is automatically created with the number 20.
Here you enter that the text <Renovation> applies for term number 20 for object type IM (rental
object) and term category 1190 (default posting term for vacancy). The term that is automatically created
WHATSAPP +255738656506
for the rental object then receives this name, and the real estate specialist working on the object only has
to enter the responsible cost center.
Resubmission
Define Resubmission Reasons
Use
In this activity, you create your own user-defined resubmission reasons. Resubmission dates can only be
generated for an object if a resubmission reason is entered.
In the resubmission function in the navigation area of the RE Navigator, you can also filter the list by
resubmission reason.
Activities
Here you define your resubmission reasons independently of the object type.
Then assign the resubmission reasons to the object types in the Make Settings per Object Type IMG
activity.
Define Resubmission Rules
Use
In this activity, you create your own custom rules for generating the dates on which you want to be
reminded that objects may need further processing.
Prerequisites
SAP provides the following resubmission rules in the standard system:
- A01 - One-Time Occurrence

- A02 - &1 Months/&2 Days Before &3
- C01 - As of date &1 every &2 months
- P01 - &1 Months/&2 Days Before End of Term
- P02 - &1 Months/&2 Days Before 1st Contract End (Initial Term)
- P11 - &1 Months/&2 Days Before Notification of Renewal Option
- P12 - &1 Months/&2 Days Before Renewal Option
- P21 - &1 Months/&2 Days Before Notification of Automatic Renewal
- P22 - &1 Months/&2 Days Before Automatic Renewal
- P31 - &1 Months/&2 Days Before Notice Date
@1A@ If you want to program new rules, make sure that the names are in the customer name range
(starting with Y or Z)!
Activities
Resubmission rules first have to be programmed, then they can be assigned and given parameters in
this activity. For the rules to be available in the application, you have to assign them to object types,
along with one or more resubmission reasons, in the Define Settings per Object Type IMG activity.
It is then possible to assign a resubmission rule, process and even change it (for instance the
resubmission reason) in the application, such as processing a rental object.
For more information on programming new resubmission rules, refer to . Implement Enhancements
(BAdI).
SAP provides these parameter types: Date, Number (4 Characters) and Yes/No. In addition to these, you
can define your own parameters that the system uses to generate dates. These parameters are then
required entry fields in the application.
You can set the Start Date, End Date, and Periodic indicators here, but they are not required entry fields
in the application.
Example
Rule Parameter Type Parameters

A01 One-Time Occurrence Date Start Date
C01 As of date &1 every &2 months Date Start Date
Number (4 Characters) Interval in Months
P01 &1 Months/&2 Days Before
Contract End Number (4 Characters) Number of Months
Number (4 Characters) Number of Days
P02 &1 Months/&2 Days Before
Notice Date Number (4 Characters) Number of Months
Number (4 Characters) Number of Days
Yes/No Inactive Notice
Also
@0S@ The Yes/No parameter type appears in the application as a checkbox in the application. You have
to enter your own text for it in Customizing (see the example).
Make Settings per Object Type
Use
In this activity you assign resubmission rules and resubmission reasons to individual object types.
These are the resubmission rules and resubmission reasons that you want to be available in these
object types.
You can also deactivate the Resubmission function separately for each object type. The Resubmission tab
page does not appear in the application in that case.
Requirements
You created the necessary resubmission reasons in the Resubmission Reasons IMG activity.
WHATSAPP +255738656506
SAP provides resubmission rules in the standard system. If you want to a) change these resubmission
rules or b) create additional resubmission rules, read the documentation for these activities:
a) Define Resubmission Rules

b) Implement Enhancements (BAdI).
Standard settings
The Resubmission function is available for these object types:
- Architectural object
- Business entity
- Building - Property
- Rental object
- Real estate contract
Activities
Assign the necessary resubmission rules and reasons for each object type, for which you want to use
resubmission. Set the WF indicator if you want a workflow event to be sent.
If you want to use the Appointment Calendar Generic Business Tool, set theCal. ( calendar ) indicator
and specify the appointment type.
You enter appointment types in Customizing for the appointment calendar.
Set Default Values for Reminder Rules and Enter Automatically in Contracts
Use
In this Customizing activity, you can specify for specific contract types which reminder rules are to be
inserted into the contract automatically when a new real estate contract is created. At the same time,
you define which reminder reason and which reminder parameters are to be entered by default.
Requirements
You have defined reminder rules.
You have defined reminder categories.
In the Customizing activity Make Settings per Object Type, you have assigned the reminder rules and
reminder categories to the Contract object type.
Activities
1. Select the object type (IS - Contract), a differentiation criterion (optional), and the reminder rule
and confirm your entries by choosing Continue (ENTER key). The Reminder Category field is
defaulted to the value assigned to the selected reminder rule for the Contract object type in the
Customizing activity Make Settings per Object Type. You can change the reminder category
proposed.
Other fields such as the End Date are shown according to the settings made in Define Reminder
Rules.
2. Enter a number for the identification. This number is used in the contract to identify the
reminder rule. For this reason, the reminder rule numbers must differ and be sequential for each
combination of object type and differentiation criterion (that is, for each contract type).
Example:
Object Type Differentiation Criterion Reminder Rule ID

Contract <blank> A01 10
Contract Commercial Lease-Out A02 20
Contract Residential Lease-OutC01 20
3. Choose the Define Reminder Parameters subdialog. The possible parameters are predefined
based on the settings made in Define Reminder Rules. Select these and enter the values for the
parameters.
4. Save your entries.
Example
Object type: IS (Real Estate Contract)
Differentiation criterion: CO02 (Residential Lease-Out)
Reminder rule: C01 (As of date &1 every &2 months)

Identification: 20
After reminder rule C01 is selected, the Reminder Category field contains the default value 10
(General Reminder). The system determines this default value from the Customizing activity Make
Settings per Object Type.
Reminder category: 10 (General Reminder)
End date: 312016
In the Customizing activity Define Reminder Rules, the End Date indicator was set for rule C01,
which is why the End Date field is displayed and can be specified.
The following parameters have been defined for reminder rule C01 in the Customizing activity Define
Reminder Rules.
No. Type Name of

Parameter
1 Date Start Date
2 Number (4-digit) Interval in Months
You can set default values for exactly these parameters for inserting reminder rule C01 in contracts of
type Residential Lease-Out:
No. (Name) Type Date No.

Start Date 1 Date 011016 0
Interval in Months 5 Number (4-digit) 5
Result:
WHATSAPP +255738656506
When you create a new contract of type Residential Lease-Out, the system automatically inserts the
reminder rule As of date 011016 every 5 months with the reminder category 10 General Reminder,
identification 20, and end date 312016.
Use
The primary task of this Business Add-In (BAdI) is to determine the list of dates for user-specific
reminder rules. Implementing this Business Add-In is mandatory for every reminder rule specified in
the Customizing activity Define Reminder Rules. You can process all required user-specific rules
within the same Business Add-In implementation. That means that it is not necessary to create a
separate implementation of RECA_RESUBMISSION for each reminder rule.
The BAdI method CHANGE_ATTR_OBJ_DATE makes it possible to influence the determination of

the person responsible for a reminder date. In the standard system, the system enters the person
responsible for the assigned object as the person responsible for the reminder date. The following
parameters are available as IMPORTING parameters: IO_PARENT (object with reminder), IS_RULE
(reminder rule for object) and IS_RS_OBJ_DATE (reminder date for object). You can influence the
person responsible using the CHANGING parameter CD_RESPONSIBLE (person responsible).
The BAdI method CHANGE_OUTPUT_DATA_OBJ_DATE makes it possible to change the output

attributes of a reminder date. The following parameters are available as IMPORTING parameters:
IO_OBJECT (object with reminder) and IS_OBJ_DATE_X (reminder date and additional fields). You
can use the CHANGING parameter CD_RSICONSTATUS to change the icon for the processing
status.
The BAdI method GET_BEHAVIOR_CONTEXT makes it possible to allow changing the person
responsible using the function key 'Change Further Attributes'. It also allows you to control whether the
reminder category should be changed for completed or fixed dates, if the assigned reminder rule was
changed.
The following parameters are available as IMPORTING parameters: IO_PARENT (object with
reminder), IT_OBJ_DATE_X (reminder dates for object and additional fields), IS_RULE (reminder
rule for object) and IS_RS_OBJ_DATE (reminder date for object). You can allow changing the
person responsible using the CHANGING parameter
CF_CHANGE_RESPONSIBLE. You can control the adjustment of the reminder category using the
CHANGING parameter CF_UPDATE_REASON_AT_FIXED_DONE. Note that the
IMPORTING parameter IO_PARENT only contains a valid reference during processing of a single
object.
You can also define additional fields for overviews of the reminder dates. You can then use these
fields in the RE Navigator (left-hand part of the screen) and in the mass-processing transactions for
reminder dates (RECARS and RECARSCN). First use the APPEND. technique to insert the additional
fields into DDIC structure RECA_RS_OBJ_DATE_MASS_L. Then implement method
CHANGE_OUTPUT_DATA and populate the additional fields with the data required. You can use
existing data from standard fields to derive your own data.
Requirements
First specify the general attributes and parameters of the reminder rules in the Define Reminder Rules
Customizing activity.
Using this parameter definition, the system automatically generates the input screen when the rule is
used within RE Navigator. You are not allowed to create your own screens for the input screen. The
parameters entered by the user for the reminder rule (such as, number of months, date, and so on) are
available in technical form as IMPORTING parameters during the implementation of the BAdI
method. The system uses them to calculate the list of dates for the reminder.
Activities
Create a Business Add-In implementation and define the CALCULATE_DATE_LIST method. Then
activate the Business Add-In implementation.
Example
The reminder rules provided by SAP (such as A01) are defined by the RECA_RESUBMISSION
BAdI implementation of the same name. You can use these standard rules for orientation when defining
you own rules.
Note the following:
- The CALCULATE_DATE_LIST method is called for each of your active BAdI implementations, if
the system has to determine the list of dates for a reminder rule. Make sure that you process only the
rules you want and do so in only one BAdI implementation. The typical structure of the method is:
CASE is_rule-rsrule.
WHEN 'Y01'.
"Calculation of the list of dates for rule Y01
WHEN 'Y02'.
"Calculation of the list of dates for rule Y02
...
ENDCASE.
- Do not directly access databases (SELECT statements) on tables where the data could be being
processed. For example, if you tried to retrieve data for the contract term in this way and there are
unsaved changes, you do not get the current processing status, and can thereby generate errors in the
list of dates.
Use only the API_RE_xx_GET_DETAIL function module for data retrieval. (Here xx stands
for the English abbreviation for the object type, for instance CN for the real estate contract.)
- Do not use statements that execute actions on the interface, for example, MESSAGE without
RAISING, CALL SCREEN and so on. Also, do not use COMMIT WORK or ROLLBACK WORK.
Authorizations
Define Authorization Groups
Use
The authorization objects for real estate master data and the authorization object for the real estate
contract contain the Authorization Group field. This field can be entered on the master data (or derived
automatically by implementing an appropriate BAdI).
You enter the authorization groups that you want to differentiate. These values for the field only
serve as input help in the application, that is, there is no check if the values are allowed.
WHATSAPP +255738656506
The users need to be informed of the authorization groups to be used.
User Status
User Status and Activity Control
Use
In this section, you can enter your own user status in addition to the system status of SAP Status
Management.
This status applies for the following objects. (In parentheses you see the name of the status profile that
the object type is assigned to in standard Customizing):
- Business entity ( IS_RE_ 01)

- Building ( IS_RE_ 02)
- Property ( IS_RE_ 03)
- Rental object ( IS_RE_ 04)
- Real estate contract ( RE_CN )
- Settlement unit ( RE_SC )
- Participation group ( RE_PG )
- Cost collector ( RE_CC )
- Architectural object ( RE_AO )
Note:
When you create a real estate object, the system checks if status profiles are allowed for the object
type. If only one status profile is allowed for an object, then it is assigned to the object automatically.
If more than one status profile is allowed for the object, then the system does not make an automatic
assignment. Before setting a user status, the user then has to decide which status profile is valid for
the object.
Steps for Defining the Status Profile:
In this IMG activity you define status profiles.
Activities
1. Enter a Status Profile.

2. Assign the status profile to an Object Type.
3. Define the User Status.
4. Assign Business Transactions to user statuses.
5. Translate the status profile and user statuses.
Defining a status profile.
To define a status profile, proceed as follows:
Create status profile

To create a status profile, proceed as follows:
1. Select "Edit -> New entry".

2. Enter a name for the status profile.
3. Enter a description.
4. Enter a maintenance language for the status profile.
Changes and supplements to the status profile can only be made in the maintenance language, and
must then be translated into the respective foreign languages. This guarantees that the entries in
the status profile are complete and unambiguous.
5. Choose "Enter" to include the new status profile in the list.

6. Choose "Save".
Assign status profile to an object type

To be able to use a status profile for objects of a certain object type, you need to assign the profile
to the corresponding object type:
1. In the screen "Change Status Profile: Overview", position the cursor on the status profile you want
to assign.
2. Choose Goto -> Object types.
3. Select the object types for which the status profile is valid.
Note that there are four object types relevant for the Project System:
- Project definition
- WBS element
- Network header - Network activity
4. Choose Save.
Define user status

To define user status for a status profile, proceed as follows:
1. In the screen "Change Status Profile: Overview", position the cursor on the status profile you want
to maintain.
2. Choose Goto -> User status.
3. For each user status you must enter a four-digit, language- specific key to identify the status.
4. For each user status you can enter the following:
a) In "Stat. no." field, enter a status number
The sequence number determines the sequence in which the statuses contained in a status
profile can be set.
b) Specify a lowest and highest sequence number in the "Low" and "High" columns.
c) Enter a short text.
The short text contains a short description of the status.
d) Enter a long text for the user status. Choose Goto -> Long text.
WHATSAPP +255738656506
e) Select a user status as an initial status, if necessary.
If you select a user status as an initial status, it is set automatically when you create a cost
object. Within a status profile, you can define only one initial status with a sequence
number, but as many as you require without a sequence number.
f) You use "Position" to specify the position in which the status is displayed in the order header.
g) You use "Priority" to specify which priority the user status has on a particular position if the
same position is defined for more than one active status.
Assign business transactions to a user status

To assign business transactions to your user statuses, proceed as follows:
1. Position the cursor on the desired user status.

2. Choose Goto -> Business transaction control.
3. Choose Edit -> New lines to display a list of the existing business transactions.
4. Assign the corresponding transactions to your user status.
5. You use "Influencing" to activate the following fields for each transaction:
a) "No influence"
The business transaction is not influenced by the current user status.
b) "Allowed"
The business transaction is allowed by the current user status.
c) "Warning"
The business transaction is allowed by the current user status but a warning message is
displayed. You can decide whether to heed the warning or not.
d) "Disalld"
The business transaction is not allowed by the current user status.
To use a business transaction, the following is required:
- At least one active status must allow the business transaction.

- No active status may disallow the business transaction.
6. You use "Next action" to specify what effect a particular business transaction has on the respective
statuses:
a) "No action"
The status is neither set nor deleted by the business transaction.
b) "Set"
The business transaction sets the respective status.
c) "Delete"
The business transaction deletes the respective status. However, you cannot use this to delete a
user status that has a sequence number.
These statuses can only be deleted by setting a subsequent status, which also has a sequence
number.

Translate status profile and user status
You can translate the status profile and the user statuses assigned to it into other languages.
If you wish to translate, note the following:
- User statuses can only be created, changed, and deleted in the original maintenance language.
- Unless all the user statuses within a status profile are translated, the system shows them all in the
original maintenance language.
If you wish to translate a status profile, proceed as follows:
1. Choose Extras -> Profile translation in the status profile overview.

2. You can call up a list of foreign language ID codes using the F4 key.
3. Select one using the F2 key.
4. Choose "Enter".
5. Translate the name of your status profile into the foreign language.
6. Save your translation.
To translate user statuses, proceed as follows:
1. Position the cursor on the status profile in question.

2. Choose Goto -> User status.
The system lists all user statuses in the profile.
3. Choose Goto -> Status translation.

4. You can call up a list of foreign language ID codes using the F4 key.
5. Select a list using the F2 key.
6. Choose "Enter".
7. Translate the key, the description and, if necessary, the long text in the required language.
8. Save your translation. Additional information
Status simulation
You use this to simulate the status development for a particular object.
Place the cursor on a status profile, use the function Goto -> Object types, and position the cursor on one
of the allowed object types.
- Choose Extras -> Status simulation to simulate the status changes that would result if you were to
use the relevant business transactions, or maintain the status manually.
- From the simulation, you can go directly to the status maintenance screen for each object type,
where you can call up more detailed information on the allowed and disallowed transactions.
- Each step you simulate is recorded by the system in a log displayed online. This enables you to
trace the status development at all times.
Status profile information
Using this function on the screen "Change Status Profile: Overview" you can call up a list which
summarizes the specifications in your status profile.
WHATSAPP +255738656506
The list is structured as follows:
- The first section contains the object types allowed for this status profile.
- The second section contains the user statuses that are defined for this profile.
- In the third section, the system lists for each user status that business transactions are:
- Allowed
- Allowed, with warning message - Disallowed.
Object type info

Using this function on the screen "Change Status Profile: Object Types Allowed", you can call up a list
that summarizes all the specifications on system statuses for a particular object type.
The list is structured as follows:
- The first section contains the valid system statuses for this object type.
- The second section contains the allowed business transactions for this object type.
Obsolete User Status
Use
User statuses that are no longer to be used can be marked as obsolete.
Requirements
This function is only available when you create a BAdI implementation for BAdI
BSV_STATUS_PROFILE:
- Start by copying class CL_EXM_RE_BSV_STATUS_PROFILE to the customer namespace.

- Create a BAdI implementation for BSV_STATUS_PROFILE and define this copy as the
implementing class for your BAdI implementation.
- Activate your implementation.
- In Customizing, maintain the relevant entries for the obsolete user statuses in the menu option.
Document Management
Document Management
Use
For real estate objects, there are three options for storing and managing documents:
- SAP Records Management

- Document Management ( DMS )
- Business Document Navigator
The strategy you choose for storing your documents is dependent on your specific needs related to the
process, and the number of documents involved.
- Records Management is particularly able to support a record-oriented and process-oriented view

of documents. For more information on this component (BC-SRV-SRM), see the SAP
Library. Choose Application Platform (SAP Web Application Server) -> Business Services ->
SAP Records Management. Also see the Implementation Guide. Choose SAP NetWeaver ->
Application Server -> Basis Services -> Records Management.
- The Document Management (DMS) component supports a document-centered view. For more
information on this component (CA-DMS), see the Implementation Guide. Also see SAP Library.
Choose SAP ERP Central Component -> Cross Application Components -> Document
Management.
- The Business Document Navigator (BDN) is suitable if you do not need a record-oriented or
process-oriented view, and only need to store small numbers of documents. You do not need to
make any additional Customizing settings to use the Business Document Navigator. Storage is
based on Business Document Service (BDS). For more information on this component (BC-SRV-
BDS), see the Implementation Guide. Also see the SAP Library. Choose Application Platform
(SAP Web Application Server) -> Business Services -> Business Document Navigator.
You can configure these three tools separately for each real estate object type. For example, you could
use records in Records Management for managing real estate contracts, while you use the Business
Document Navigator to store and display documents for business entities and buildings.
In the RE Navigator, you can go to the document management type for the given object by choosing
@FT@ with the quick info text Document Management. The system determines which tool is
displayed (Records Management, DMS or BDN) dependent on the configuration of the real estate
object, and using the following sequence:
1. If Records Management was set to active in Customizing, then the system displays the Records
Organizer.
2. If the document management component was configured in Customizing , then the system displays
it.
3. If no settings were made on this subject in Customizing, then the system displays the Business
Document Navigator.
Standard settings
In the standard system, Records Management and document management (DMS) are not configured, so
that the Business Document Navigator is used.
Records Management
Make Basic Settings for Records Management
Use
WHATSAPP +255738656506
SAP Records Management is a system for electronic record management. Records Management
does not influence the storage location or storage process for outgoing correspondence for real estate
objects (SAP forms or office documents). So using the Records Management component is optional and
can also if necessary be implemented later.
Records Management has the following advantages:
- You can create and manage an electronic record for each real estate object.
- You can specify the structure of these records using record models.
- You can edit and search for records using the Records Organizer.
- You can initiate workflow-controlled processes from the records.
For more information on this component (BC-SRV-SRM), see the SAP Library. Choose
Application Platform (SAP Web Application Server -> SAP Records Management. And in the
Implementation Guide choose SAP NetWeaver -> Application Server -> Basis Services -> Records
Management.
Here you can activate the connection to the Records Management component for different object types of
Flexible Real Estate Management and make further settings for creating records.
Standard settings
You make separate settings for all real estate object types.
Activities
- Set up for each object type whether you want to use Records Management using the Active
indicator.
- Define whether the system should automatically create the records.
- Determine the storage location and the structure of the record using the following fields:
- RMS ID
- Element Type ID of Record
- Element Type ID of Record Model
- Record Model ID
Implement Enhancement for Records Management ( BAdI )
Use
By implementing this Business Add-In (BAdI) you can replace the standard system procedure for
creating a record. You can use this Business Add-In only if you want to use SAP Records
Management to manage your documents. For more information about this, and about activating the
creation of records, see Customizing under Make Basic Settings for Records Management.
If you do not implement this BAdI, then the default implementation is used (global class
CL_DEF_IM_REIS_RM).
The implementation of the Business Add-In is based on the object type (filter value of the BAdI).
When you create an implementation, you define for which object types (for example, contract, rental
object, or building) your implemented method is to be applied. If you create an implementation for
multiple object types, then the filter value (parameter FLT_VAL) that contains the current object type
must always be considered in the code. Therefore, for the sake of transparency, it is better to create
separate implementations for each object type.
Activities
You can use the following methods, which are called automatically by the system and used to create or
process a record.
- CREATE_RECORD
An implementation of this method has to create precisely one record for the real estate object.
However, the method must not call COMMIT WORK or ROLLBACK WORK, since these controls
are the responsibility of the standard program. If an error occurs during the creation process, then
trigger the exception ERROR with the statement MESSAGE
...RAISING error.
To create the record, you then use only the BAPI function modules from Records
Management. The names of these function modules are prefixed by BAPI_RECORD_*, and the
function modules are documented. You can also use the default implementation in class
CL_DEF_IM_REIS_RM, method CREATE_RECORD as a guide.
The standard setting is for the record to be created on the basis of the folder model defined in
Customizing. This setting is dependent on the object type. The four key fields that are required
are populated with values from Customizing and transferred as parameters:
- ID_RMS_ID: ID from the Records Management system
- ID_SPS_ID: Element type of the record that is to be created
- ID_MODEL_SPS_ID: Element type of the record model
- ID_MODEL: ID of the record model

If, however, you want to use multiple record models within one object type, when you create
the record, do not use the parameter ID_MODEL according to Customizing. Instead, use the
ID of a different record model that is already defined. In this way, you can, for example, have
different record structures for customer and vendor contracts. To read the data of the current
real estate object (such as the contract type), in the BAdI implementation, call function module
API_RE_xx_GET_DETAIL with the parameter IO_OBJECT = IO_OBJECT . Replace xx
with the English abbreviation for the relevant object type, for example
API_RE_CN_GET_DETAIL for the real estate contract. For examples relating to this, see the
various methods of the default implementation. If you want to create the new record on the
basis of the underlying record model, or if you want to use additional properties for the record,
then you need to use an implementation of this method.
- GET_RECORD
The default implementation of this method in class CL_DEF_IM_REIS returns a list of the records
found for a real estate object. If you have changed the properties of the records in the method
CREATE_RECORD, then you need this method to be able to find the records.
- IS_PROPERTY_SELECTION: Search criteria for records for BOR object key of the real
estate object
WHATSAPP +255738656506
- CT_RESULTING_LIST: List of the records found
- CF_PROCESSED: Indicator that BAdI was executed. Set the indicator when you have
implemented the method.
- DISPLAY_RECORD
The default implementation of this method in class CL_DEF_IM_REIS shows the record found for
a real estate object using GET_RECORD. If you want to use a display different from the standard
display, you need this method.
- IS_RECORD: Record to be displayed
- IF_MODIFY: Change mode indicator
- CF_PROCESSED: Indicator that BAdI was executed. Set the indicator when you have
implemented the method.
Note that when implementing the BAdI you are not allowed to use statements that affect the interface,
such as direct output of messages using MESSAGE without the addition RAISING. Notes for
Developers
Document Management System
Define Document Types
Use
In this section, you make the necessary settings for document types of the document management
(DMS) component. Here you assign real object types that you want to use for document management.
Standard settings
In the standard system, only entries for the key fields of the individual real estate object types are
provided. However, no document types are delivered, and no settings for assigning real estate object
types to document types.
Activities
To be able to assign DMS document types to real estate objects, you have to make the following
settings for each document type:
- Specify the object links (always enter 500 as the screen number for real estate object types).
- Enter a text for the object links.
For more information, see Customizing for Document Management. Choose Document Types.
For Flexible Real Estate Management, use the following DMS object types for the configuration:
RE Object Type Key for DMS Object Type

Architectural object VIBDAO
Business entity VIBDBE
Land VIBDPR
Building VIBDBU
Rental object VIBDRO
Real estate contract VICNCN
Participation group VISCPG
Settlement unit VISCSU
Adjustment measure VIAJAT
Mandate VIMMMN
Offered object VIOROO
RE search request VIORRR
Contract offer VIOROF
Parcel VILMPL
Parcel update VILMRC
Land register VILMLR
Joint liability VILMJL
Other public register VILMPE
Notice of assessment VILMNA
Assign Screen for Object Link
Use
The screen number is required so that the system can display and change the assignment of real estate
objects in the transactions of document management.
The integration of document management (DMS) with Flexible Real Estate Management is based on
an implementation of the DOCUMENT_OBJ Business Add-In. Therefore, you do not enter the actual
screen number. Instead you always enter 500.
Activities
Make exactly one entry for the desired real estate object types, and enter screen number 500 for each
of them.
Additional Texts
Define Categories for Additional Texts
Use
In this activity, you create your own user-defined categories for additional texts. You can include
these additional texts in PDF-based forms or Smart Forms using correspondence functions. You can
WHATSAPP +255738656506
enter only one text of each category in a real estate object. You enter additional texts in the RE
Navigator.
The additional texts are available for these object types:
- Real estate contract

- Contract offer
- Offered object
- Business entity
- Land
- Building
- Rental object
- Architectural object
- Parcel
- Parcel update
- Land register
- Other public register
- Notice of assessment
Activities
For each object type, you define your categories for additional texts. You can create a standard text that
is automatically copied to the real estate object when the given category is used.
Note: The standard texts are client-dependent SAPscript texts with the key:
- Text object = RE - Text ID = CAAS
To edit and transport text modules, use the Manage Text Modules IMG activity.
Use
You can define categories for additional texts in Customizing. You can specify which categories are
allowed for each real estate object type (contract, building, rental object, and so on). These text
categories are then available for selection when you are maintaining a real estate object. The BAdI
method CHANGE_CATEGORIES_FOR_INSERT allows you to further restrict the category
selection by object type defined in Customizing.
If you create additional texts for a real estate object, the texts specified in Customizing are only used
as templates but are saved for the individual object. The key of the text object contains the reference to
the real estate object and the language key of the logon language. The BAdI method
CHANGE_LANGUAGE allows you to maintain the additional texts independently of the logon
language.
Example
CHANGE_CATEGORIES_FOR_INSERT Method
You have allowed the categories A1, A2, B1, and B2 for contracts. However, only categories A1 and
A2 are intended to be used for contract type A while categories B1 and B2 are intended to be used for
contract type B. Implement the BAdI method CATEGORIES_FOR_INSERT so that the allowed
categories read from Customizing
(CT_TEXT_CATEGORY_X) are restricted based on the object properties (IO_OBJECT) by deleting
the relevant rows. Only the categories for additional text that remain in the table are then offered for
insertion on the "Additional Text" tab page in the contract dialog.
CHANGE_LANGUAGE Method
You have created an additional text for an object while logged on in German. The text object created
for the real estate object is stored in a file whose key contains the logon language. If you now log on in
English, the system informs you that an additional text exists but does not display the text that you
created when you were logged on in German. You can now create a text in English (the logon
language) for the same text category that differs from the German text. This should generally be
avoided.
Therefore, we recommend that you implement this BAdI method to ensure that text modules can be
saved and accessed independently of the logon language. You specify this by setting the CD_LANGU
parameter to the required (single) language. The language key you choose is used as the key for saving
the text module and accessing existing text modules independently of the logon language. Although it
is possible to restrict the language selection to specific object types (as demonstrated in the example
implementation), this is not generally advisable.
Enhancements
Implement Enhancements (BAdI): "Overviews" - Own Evaluations
Use
example.
Implement Enhancements (BAdI): Default Values for Assigned Assets
Use
WHATSAPP +255738656506
Default values for data for creating assets
Requirements
You are processing a real estate object (land, building) in dialog mode and create an asset on the
"Assignments" tab page. The BAdI makes it possible to provide default data for the asset.
Implement Enhancements (BAdI): Default Values for Functional Location
Use
The Business Add-In supports enhancements to the standard functions of the Integration with Plant
Maintenance (Automatic Creation of Functional Location).
For an overview of the possible enhancement methods, see this text.
Activities
Create a BAdI implementation and implement the methods you require for your enhancement. Then
activate the BAdI implementation.
The following methods exist:
- GENERATE_LABEL - Generates the name of the automatically created functional location

- ADAPT_DATA - Adjusts the data of the functional location that was generated in RE-FX
- UPDATE_CLASSIFICATION - Allows updating of the classification of the functional location
that was generated in RE-FX
These methods are called automatically when the functional location is created or changed. If an
implementation exists, the methods are always called in addition to standard system behavior.
The implementation of the methods has to be independent of the interface. It must not contain any
COMMIT WORK or ROLLBACK WORK statements.
For example, direct output of messages using the MESSAGE statement is not allowed.
Method description
- GENERATE_LABEL
The generated name of the automatically created functional location can be changed here. The
IO_OBJECT parameter contains the real estate object for which the functional location is created.
CD_LABEL contains the name that was generated by RE-FX for the functional location. At this
position, the name can be generated again using a separate logic.
- ADAPT_DATA
This method is used to fill the data of the functional location that was created in RE-FX. It is
called during both creation and updating (depending on the Customizing settings for the functional
location). The IO_OBJECT parameter contains the real estate object for which the functional
location is created or updated. CS_FUNC_LOC contains the current data of the functional location,
with RE standard logic already added. Notes for Developers
Implement Enhancements (BAdI): Search Help
Use
You have special requirements related to the way search helps function, for example you want to use
search helps that
- Display only those objects for which the user has authorization
- Do not display objects that are no longer valid
- Do not display objects that are flagged for deletion or for which the deletion indicator is set
Requirements
You are using a search help that calls the BAdI, that is, a search help that uses a search help exit that calls
the module RECA_SEARCH_HELP_CALL_BADI. This could be, for example,
the exit module RECA_SEARCH_HELP_F4UT_OPT_COLW or
RECA_SEARCH_HELP_OUT_AGREEMENT.
Activities
If you want to use the BAdI, first determine if the BAdI is called in the search helps that are involved.
That is, you have to determine if the individual search helps use an appropriate search help exit. If
this is the case, implement the BAdI. The following example implementations are available:
CL_EXM_IM_RECA_SEARCH_HELP_VAL
CL_EXM_IM_RECA_SEARCH_HELP
If a suitable search help is not available in the standard system, you can create your own customer-
specific individual search help. The prerequisite for using the modification-free enhancement described
is that the search help you use is a collective search help.
- Create an elementary search help, such as ZREBDBUNOA, in the customer name space.
Creating the search help is easiest if you use an existing elementary search help as a template,
such as REBDBUNOA (example for buildings) and copy the template ( SE 11). Change the
descriptive text in your copy. Make sure that your search help contains the technical field
OBJNR (object number). As the search help exit, enter one of the function modules that call the
BAdI: RECA_SEARCH_HELP_F4UT_OPT_COLW (BAdI call and column optimization) or
direct RECA_SEARCH_HELP_CALL_BADI (call of BAdI only), as an alternative for contracts
also RECA_SEARCH_HELP_OUT_AGREEMENT. Activate your search help.
- Now enhance the collective search help so that your new search help is called: Call the collective
search help using SE12 (example for buildings: REBDBUNO) and choose Goto -> Append
Search Help. Assign a (new) name in the customer namespace, for example, ZZREBDBUNOA.
WHATSAPP +255738656506
Enter your newly created search help ZREBDBUNOA as included search help in
ZZREBDBUNOA. Assign the parameters. Activate the collective search help.
You can now test this search help. As long as you only copied the search help and did not
change it, and the BAdI is also not implemented, then your search help works the same as the
template.
- To implement the BAdI, call transaction SE18 for the BAdI BADI_RECA_SEARCH_HELP and
create an implementation. For example, in your search help ZREBDBUNOA, if you want to
display only buildings that are not flagged for deletion and where the validity
ended 6 months ago, you can copy the example class
CL_EXM_IM_RECA_SEARCH_HELP_VAL.
- Change the code of your implementation to meet your requirements. Be aware that the BAdI is
called in all search helps that possess one of the search help exits mentioned above. That means,
you have to ensure that the implementation contains appropriate queries of those search help
names for which it works, in order to prevent terminations in object types that are not covered by
your implementation. In the case of the implementation class
CL_EXM_IM_RECA_SEARCH_HELP_VAL, different objects can be handled with the same
code, since the validity check functions not only for buildings, but also, for example, for rental
objects, contracts and so on.
- Activate your BAdI implementation and test if the F4 help works correctly.
Tip
If you want to deactivate elementary standard search helps, then enter their names as included search
help in the append, and set the "Hide" indicator. In this way, you can replace standard search helps with
your own customer-specific search helps.

WHATSAPP +255738656506

Address Management

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Address Management

Uploaded by

Copyright:

Available Formats

Copyright(c) 2018 by Nixon Vunganai.

All rights reserved.

Maintain Address and Person Number Range

1. Call the number range maintenance transaction by choosing "Execute".

4. Save the entries.

See OSS note 25182.

Choose Address Screen Layout

You can currently choose between the variants:

The value applies to all Business Address Services screens.

Choose the address layout according to the country-specific assignment.

Activate International Address Versions

The character sets must be activated in the system.

SAP delivers the following version keys:

The version keys are delivered inactive.

Activate the version keys required in your system.

To activate delivered version keys, proceed as follows:

1. Choose "Execute" to call the maintenance transaction.

1. Call transaction SM30.

Activate Regional Structure Check for International Address Versions

c) In this activity, insert the following entry:

b) Further settings in this activity are not required in this example.

Maintain Forms of Address

1. Check the standard form-of-address texts for completeness

One of these is for all valid academic titles.

You can control how a name is composed from the elements.

Name format rules

The standard system includes some academic titles.

Create the required academic titles.

Maintain Name Prefixes

You can control how a name is composed from the elements.

Maintain rules for name composition

The standard system includes some name prepositions.

Create the required name prepositions.

Maintain Titles and Name Supplements

You can control how a name is composed from the elements.

Maintain rules for name composition

The standard system includes some styles, ranks, and titles.

Create the required styles, ranks, and titles.

Maintain Name Formatting Rules

The name composition format DE 01 is defined as follows:

The following fields are used for a business partner: Form-of-address:

With form-of-address (TITLE): Mr Rene van de Kerkhoff

Without form-of-address: Rene van de Kerkhoff ( languag-independent

The standard system includes some name composition format templates.

Create the required name composition formats.

Maintain Reason for Non-Delivery

Example of an application table:

Measure Measure text Reason for non-delivery Non-delivery text

Examples of reasons for non-delivery include:

- Moved - address unknown

Define pager services

Maintain Transport Zones

Activate Duplicate Check and Determine Limit for BAPIs

For more information, see SAP Note 176559.

Set Limit for Duplicate List in SAP Dialog Boxes

Regional Structure/City File

SAP ships the regional structure without content.

Import Reference Data

Copy postal reference data into the regional structure tables.

Use the program RSADRLSM02.

See note 132948.

Maintain Number Ranges for Postal Codes

Maintain number ranges for postal codes

In the standard system, Number Range 01 is for external assignment.