CC2014 Improvements Overview EN PDF

Customer Connection Real Estate 2014
Franz Kehrein, Anke Koeppe
Public
Overview
 Miscellaneous
 Master Data
 Contracts
 Reporting and Correspondence
 Accounting
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 2

Miscellaneous
 D6384 Customizing: Validity of data

 D6436 Groups of responsible persons
 D6318 Improvement Error Log
 D6349 Additional notice at resubmission

Request D6384
Customizing: Validity of data
In the current situation there is no possibility to give a validity to customized data.

In some cases though it is important to block the option of creating new
documents or data.
For different objects a validity should be possible.
Extra info:
The option to give a validity should be possible to all customized data. It is
particularly important not to differ because the data can become not applicable or
valid for many reasons. Some of which are unforeseeable, for example change of
management or changes in laws and regulations.

Solution Summary
For a series of customizing entries the flag “Obsolete” is introduced. Existing data
records which contain “obsolete” customizing entries are no longer valid. If new
data records are be created, those entries flagged as obsolete are no longer
offered as selection options.
Releases: mostly EhP4 for SAP ERP 6.0 and higher
SAP Notes: Collective SAP Note 2108370

Solution Summary
Theme SAP Note
Notice, Renewal 2085841
User Status 2080073, 2093766
Regional Locations, District Locations,

2093170
etc.
Tax Codes 2074351, 2103246
main usage type, condition of building,

2104775
land lease right, etc.

Notice and Renewal
Now it will be possible to flag the

following customizing entries as
"Obsolete"
 Reasons for notice
 Reasons for rejection
 Notice procedures
 Notice rules
 Renewal rules
It will no longer be possible to use
obsolete Customizing entries for
creation or reassignment (during the
changing of existing data).

Notice and Renewal

User Status
User statuses that should be no more used can be hidden using a BAdI.
From EhP 606 the BAdI-solution is supported by a RE-specific template so that the
maintenance is possible within customizing.
Solution SAP Note Release What must be done?

Standard BAdI 2080073 From Create a customer
SAP_ABA 700 implementation, programming
(EA_APPL 600) the method, reject obsolete
entries by programming
RE specific template 2093766 EhP 606 and Create customer implementation

for the Standard- higher as a copy of the RE-template,
BAdI with maintenance of the obsolete
customizing table entries in Customizing

User Status:
Standard BAdI (all Object Types)
For the BAdI

BSV_STATUS_PROFILE we
provide a new method which
allows to mark user statuses
as “obsolete".

User Status:
Customizing Solution: Template Class and Customizing
One time task:

First copy all of the class
CL_EXM_RE_BSV_STATUS_PROFILE
in the customer namespace. Create a
BAdI implementation for
BSV_STATUS_PROFILE and specify
this copy as implementing class for your
BAdI implementation. Activate your
implementation.
On demand:
Maintain the corresponding entries in the
customizing for obsolete user statuses.

User Status:
Customizing Solution: Additional Notes
Please consider with the identification of obsolete user statuses, that:
• For user statuses with status number that are flagged as an initial value in the Customizing
of the status schema, the identification as obsolete user status cannot be considered.
• An user status flagged in the Customizing as obsolete which is still assigned to a RE-object
keeps on being visible in the status information of the RE-object. For this reason, such user
statuses should get an additionally note in their name that they are not supposed to be used
in future.
• User statuses marked as obsolete are not visible in the status information of the RE-object,
if such a status is not assigned to a RE-object at the moment but the status was assigned at
a former time.

Tax Codes
Tax code can now marked as

"inactive" (see SAP Note 2074351
from FI).
Transaction FTXP under “Properties"

Tax Codes: RE-FX Customizing
The maintenance dialogs in RE-FX

were enhanced by an “inactive”
indicator. The search helps were
also adjusted (see SAP Note
2103246).

Main Usage Types
The Main Usage

Types can be
marked as
“obsolete“. Once
marked, they are not
available for selection
in the maintenance
dialog.

Request D6436
Assigning a group of users as „Person Responsible
Currently just one individual user can be assigned to “Person Responsible”. It is

not possible to assign a group of users to “Person Responsible”.
The “Person Responsible” plays a significant role in the Information System, e.g.
in reports concerning master data of usage and architecture, contracts, contract
offers and in the definition and monitoring of “Reminders”.
With just one individual user as “Person Responsible” it is not possible
 to represent a team structure, e.g. object-teams,
 to delegate responsibility in case of an employee´s unplanned absence
 to monitor the dates of reminders together in a team.
Suggestion for improvement: Create the option to choose
 •one individual user or
 •a group of users
as “Person Responsible”.

Solution Summary
It’s now possible to define responsibility groups in which a user can belong to
multiple user groups. The selection via responsibility groups is possible within the
information system, in RE80 and for resubmissions (follow-up dates).
Currently, an individual user is stored as responsible within the master data.
Access is also possible via groups.
Releases: EhP7 for SAP ERP 6.0 and higher
SAP Notes: 2131103

Maintenance of Groups: RECARESPGROUP
The maintenance of “responsibility groups” could be done in Customizing as well as in the

application menu under Current Settings.

Maintain the groups in the User Maintenance: SU01
The assignment to
“Responsibility Groups" can
also be maintained directly in
SU01 on the User Maintenance:
Tab title “Personalization",
double-click on
RECA_RESP_USERGROUP.

Information System
In the information system it’s

now possible to select using a
responsibility group.
All objects will be determined to which one of the group

members is assigned as responsible.

RE-Navigator (RE80)
In the RE Navigator there is an additional

option "Group of Responsible” available.
If the user belongs to only one group, this
group is proposed.
If the user belongs to several groups, the
search help is restricted first to those
groups to which the user belongs. After
cancelling this restriction, all groups are
displayed.

Resubmission
Responsible for Contract
Responsible for Termin
In the resubmission, it’s possible to select via

responsibility group for the appointments and/or for
objects (e.g. contract).
In the RE Navigator, an additional function provides
the further restriction of reminder dates on a
responsibility group.

Request: D6318 Improvement Error Log
Problem: In the lower overview of the error log (see attachment) contracts with
error messages gets a green message-type icon. If you want to filter all contracts
with errors
a) It is not possible in the top overview (contract has the red message-type icon,
but there’s no filter)
b) In the lower overview it is possible to filter, but you see only the lines with the
error message and not the line with the contract number.
In my opinion it is necessary to set the message-type icon of the object (contract,

rental object, business entity and so on) in the lower overview like in the top
overview. Means contract gets the red message-type icon, if there exists
messages to this contract with errors and/or warnings and/or information. Contact
gets the yellow message-type icon, if there exists messages to this contract with
warnings and/or information and only there are information lines the contract gets
the green message-type icon.

Solution Summary
The severity of a message-type (like warning, error and so on) should be

inherited, from the lower to the top overview of the error log. This means
that a node receives the highest severity of its sub nodes.
The message type icon of the object (contract, rental object, business
entity and so on) in the lower overview is set like in the top overview.
SAP Notes: 2059105

Before: Messages have different types in the lists
If you use the filter

to display errors or
warnings only, the
header lines with
the contract
information
disappears.

After: Messages have the same type in the lists
Text
If you now use the
filter to display
errors or warnings
only, the header
lines with the
contract information
disappears no
longer.

Request D6349
Additional Notice at Resubmission
At the moment there is only the possibility to post a notice at single date of
the resubmission. It would be helpful to have a notice for the total
resubmission, too.

Solution Summary
Now you can create a memo for the resubmission rule (header data). This
memo will also be shown for each subordinate critical date (item for
submission rule).
SAP Notes: 1371399, 2078678

Create a memo
It’s possible to create a

memo for a resubmission
rule (header data).

Display memo
You can display the full memo by using the respective button. Moreover it’s now
possible to display the first 60 letters of the memo as part of the header list.

List processing resubmission dates
Reports for processing resubmission dates (transactions RECARS, RECARSCN,

RECARSBD) also contain a column with the first 60 characters of the resubmission
rule memo.

List processing resubmission dates
The complete memo can be displayed by using the respective list function.

In case that the field is not visible…
In case that the memo field is not

visible, you have to change the ALV
layout. Choose the field “Memo for
Resubmission Rule” and move it to the
area of ‘Displayed Columns’ and save
your layout.

Master Data
 D6398 Two records with the same value

 D6454 Vacancy reason and account determination
 D6321 Check Account Symbol for Settlement Units with data exchange
 D6452 Display of points in fixtures/fittings screen
 D6513 and D6441 Harmonization of usage and architectural views

Requests: D6398 Measurements: two records for the same
value with different validity period
If the value of a measurement is the same for two periods, the values are
combined in one record. The request is to display the value separately
Example:
• Government valuation 01.01.2010 EUR 197.000,00
• Government valuation 01.01.2011 EUR 197.000,00
Displayed in SAP currently:

• EUR 197.000,00 from 01.01.2010 to 31.12.9999
Requested:
• EUR 197.000,00 from 01.01.2010 to 31.12.2010
• EUR 197.000,00 from 01.01.2011 to 31.12.9999

Solution Summary
It‘s now possible to restrict the compression of measurements with the same
values and adjacent periods.
SAP Note: 2095959

Behavior Before Changing
Input:
Two adjacent intervals with the
same measurement value
Display and storage:

Merged into one period

Customizing: No Compression of Measurements
Measurement types
which shouldn’t be
compressed in one
record must be defined
in customizing

Behavior After Changing
After changing the measurement type configuration, the system prevents the
compression of measurements with the same measurement amounts and
adjacent periods.

Request D6454:
Vacancy reason and account determination
When a rental object is vacant, the vacancy reason may be changed at a certain
point in time. When a new vacancy reason is added to the rental object, only the
account determination of this new vacancy reason is taken into account during
periodic processing. This means that for periods where the previous vacancy
reason was valid, the system still selects the G/L accounts of the new vacancy
reason. This behavior is not correct.
NL:
Voor leegstaande huurobjecten komt het voor dat de leegstandsreden wordt
gewijzigd. Indien de leegstandsreden wordt gewijzigd, wordt in de huidige situatie
alleen de rekeningbepaling behorend bij de nieuwe leegstandsreden in
beschouwing genomen tijdens boekingen. Dit betekent dat voor voorgaande
perioden waarin een andere leegstandsreden geldig was, SAP toch de
rekeningbepaling van de nieuwe leegstandsreden gebruikt voor boekingen. Dit is
niet correct.

Solution Summary
Currently: You create an additional vacancy reason with a new validity period for
the frequency term, so the original cash flow item will be split into different cash
flow items. If the second period has a different account determination the periodical
posting run (vacancy posting) won’t use it because the key date to find the posting
term is the due date. In most cases the due date is the same for both cash flow
items, causing both cash flow items to be posted with the same (old) account
determination.
New: Vacancy postings no longer use the due date as a key date. The valid-from
date of the cash flow item will not be utilized. This enables the new account
determination to be used for the second cash flow item.

SAP Notes: 2109018 (1981099, 1983982 required)

Vacancy reason and cash flow split
The vacancy reason was changed during a cash flow period. An additional validity period for
the posting term was created automatically. At the same point of time, an additional validity
period for the frequency term was created (manually). The result is that the cash flow item is
now split into two items.

Periodical Posting vacancy until now
The posting term for the new period contains another account determination “FM” than the
period before (SPACE). The new account determination isn’t taken into account for the
periodic posting run.

Periodical posting vacancy now
The posting term for the new period with account determination “FM” is now taken into
account for the periodic posting run.

Request: D6321
Check Account Symbol for Settlement Units with data exchange
In RE-FX-Customizing you have to input a clearing account to each service

charge keys with data exchange. It is possible to create service charge
units with data exchange to all service charge keys. An error occurs very
late while the service charge settlement, if there is a settlement unit with a
service charge key without a clearing account in customizing. We need a
check if user wants to save a new or changed settlement unit with
customizing. If there is no clearing account for the used service charge key,
a message (error or warning - changeable) should occurs.

Solution Summary
Now we provide the new configurable message RESCSU 118 "No account
symbol for cost account for ext. settlement for SC key …“.
This message is switched off in the standard.
If the message is activated as errors or warning, the message is processed in the
following cases:
• in the master data dialog, if the ICON "Check" was pressed
• while executing the Mass Check: Settlement Units RESCSUCHECK
• with Collective Entry of Settlement Units RESCSUBYBE
SAP Note: 2089413

What is checked?
Settlement units can participate

only in the data exchange if a
account symbol is maintained for
the service charge key.

What is checked?

Customizing: Configurable Messages
In order to activate the checking,

you should set the message control
so that the message RESCSU 118
is created as errors or warning
(Transaction OBA5)

Request D6452
Display of points in fixtures/fittings screen
In the Dutch enhancement for RE-FX, as from ECC enhancement package 5 an

extra tab is available on the Fixtures/Fittings screen in transaction REBDRO.
However, the fields in this tab can’t be selected in the above part of the split
screen. As a result of that the screen doesn’t provide the data to view the object
points according to Dutch regulations.
We would like the possibility to add the fields of the Enhancements tab to the
results part of the screen: Fixtures/ Fittings in transaction REBDRO. Especially we
need the “Total No. of Points” field. In SAP presentations, this field is present in
the results screen. However, we have no possibility to select and add this field in
the layouts of our own system.

Solution Summary
If you use the country-specific (Netherlands, NL) enhancement of fixtures

and fittings characteristics, the system now displays the additional fields in
the overview list.
SAP Notes: 2058695

Example
The missed fields can be

displayed in the upper part of the
screen after implementing the
SAP note. If the fields are not
visible – please change the list
layout of the ALV list.

Requests D6441 und D6513
Architectural and usage view are linked in our system. While creating a business
entity, a building or a land, only the following data are copied with those of the
equivalent objects in the architectural view:
• Name of the objet
• Address
• Measurements
We also need that behavior for following data:

• Function
• Partners
• Validity dates
• Authorization Group

Requests D6441 und D6513
While modifying an architectural object, only measurements are synched with of

the equivalent objects in the usage view. While modifying an object, the user is
given the choice to synchronize the measurements immediately from the
transaction or later using the RECARG transaction. We would like to have the
same mechanisms of synchronizations for the following data:
• Name of the object
• Function
• Partners
• Address
• Validity dates
• Authorization Group
When you create a usage view object from an architectural view object, there are
fields of data copied over. However, upon change of the architectural object - the
changes are not automatically pushed to the linked usage object. Just as with
Business Partners you can influence if a change happens in RE it is reflected in FI
and vice versa, we would like the same ability to keep the 2 views in RE aligned.
Solution Summary
The following two-step solution is provided:

– BAdIs allow a customer to fully define the harmonization of usage and architectural data
by:
• Creating usage objects from architectural objects - enhancement of an existing BAdI
• Changing architecture objects - new exit to define customer specific harmonization rules
o Default-implementation of these BAdIs allow the management of harmonization rules
by SAP standard customizing tables
SAP Notes: 2092527 and 2121084

Customizing
The view V_TIVDBSYNCHRULE (transaction SM30 or via IMG) can be

used to define synchronization rules. If the defined rules in this view meet
the requirements, it is not necessary to have a customer defined
implementation.
This example shows a

rental object where the
business partner with
role TR0998 has to be
defaulted to the rental
object.

BadI: Harmonization usage view from architectural view
during creation
BADI_REBD_AO_CLONE contains a method for each object type there the

customer can decide which data should be copied.
The sample class CL_EXM_IM_REBD_AO_CLONE can be used as a

template for a customer implementation

BadI: Harmonization of Usage View after Changing
Architectural View
The harmonization of usage objects with architectural objects is based on the

technique of registration.
Step 1: Registration
If you change an architectural object that is linked to an usage object, the
registration is called. The registration tool saves information the usage object has to
adopt.
Step 2: User decision
The user receives a popup to decide whether the usage object should be adopted
immediately or harmonized later.
Step 3: Adaption of usage object
The attributes of the usage object will be adopted - immediately or later – but
always based on the registration entry.
Die Beispielklasse CL_EXM_IM_REBD_AO_CLONE kann als Vorlage fürPublic

© 2014 SAP AG or an SAP affiliate company. All rights reserved. 58
BADI_RECA_RG
To influence the harmonization of usage objects from architectural objects in

change mode, methods of BADI_RECA_RG are called. You need to implement
these methods in your BAdI implementation:
Step 1: Method CREATE_REGISTRATIONS
If you want to harmonize data of the usage object you need to create a
registrations entry. This step is also necessary in the case where the user decides
(step 2) to update the usage object immediately.
Step 3: Method UPDATE_RECEIVER
You need to read the changed data from the architectural object and update these
data in the usage objects. This method is also called in case of “update
immediately”.

BADI_RECA_RG: Special advice
Method READ_INITIAL_DATA
This method is called when changing an architectural object. At this point
of time you can preserve the data at the beginning (before change) –
especially such data, there the original state is not available after changing
(e.g. address data).
You can use sample class CL_EXM_IM_RECA_RG as a template for your

implementation.

Contracts
 D6337 Mass change posting term

 D6414, D6525, D6456 and D6451 Change tracking for contracts
 D6449 and D6383 contracts with multiple objects
 D6423 Default values for contract type
 D6413 Security deposit
 D6388 Use quarter days with sales based rent

Request D6337
Mass change posting term
At moment there is no tool for mass changes of the posting terms of

contracts.
But there is a tool for mass changes of the organizational assignment of

contracts and RE objects. This tool should be adapted for the posting
term.

Solution Summary
Transaction REMCPYCN is provided to mass change the posting terms for

contracts.
Releases: open
SAP Notes: 2131104

Overview selection screen REMCPYCN
Selection of contracts
(logical data base)
Control parameter of report
Field from posting term for

selecting and changing

Control Parameters I
Simulation: If this indicator is set, the proposed change will only be simulated.
Set Execute as Default: The system changes entries in the results list only if the
Make Change field was set for the row. Using this function you can control the
setting of a default value for this field.
Output List in Background: If you set this indicator, when the report is executed in
the background, the system provides a results list in addition to the logs.
ID: The system saves the selection and execution log under this ID.

Control Parameters II
The Relationship Valid From date specifies the date from when the new
relationship is valid. If you also choose Delete Relationship as a change activity,
then this date has to agree exactly with the start of the existing time slot.
Using the value in the If following time slots field, you decide how the system
proceeds if following time slots already exist on the Relationship Valid From date.
The following scenarios are possible:
Change Relationship is selected

• Do not Change
• Add New Time Slot or Change Existing One
• Delete Additional Following Time Slots
Delete Relationship is selected

• Do not Change
• Delete Current Time Slot Only
• Delete Additional Following Time Slots

Parameters posting term I
You can influence the relevance of the characteristic for the selection or change
using the following four fields, which exist for each possible characteristic:
Relevance Indicator: If this indicator is set, then the system uses the
characteristic, depending on its change type, for the selection and/or for the
change.
Selection Value: Only those time slots are selected that have this value in the
given characteristic.
Target Value (to): The system copies this value to the time slot being changed.

Parameter posting term II
Change Relationship is selected:

Keep: The characteristic is used only for selection. The system selects those time
slots that have the Selection Value in the corresponding characteristics.
Overwrite: The Selection Value is used for selection; the system copies the value
of the Target Value to the corresponding characteristic in the time slot.
Use Target Value Only: The Selection Value is not relevant for selection. The
system copies the value of the Target Value to the corresponding characteristic in
the time slot.
Use Target Value Only (overwrite only if initial): The Selection Value is not
relevant for selection. The system copies the value of the Target Value to the
corresponding characteristic in the time slot, but only if it had no value up to now.

Parameter posting term III
Delete Relationship is selected:
Not Relevant for Deletion Comparison : The Selection Value is not relevant for
selection.
Relevant for Deletion Comparison : The Selection Value is relevant for selection.
This means that the system deletes only those time slots, in which the
corresponding characteristics have the value of the Selection Value.
Note
The selection log lists those objects that were found by the object selection but do
not conform to the characteristic selection.
The system copies locked objects to the target list but cannot be processed further.

Interactive Report
• Report with selected contracts with change proposal

• Simulation is possible, for execution run: flag contracts and save
• It’s possible to edit target values for marked lines
• Simulation / error log is available

Change Tracking for Contracts
D6414: No Report to Track Unlock/Lock Contract Activity
D6525: Report to Track Unlocked and Locked Contract Activity
D6456: Report to show the change history for payment impacted

transactions
D6451: Report change documents from users

Solution Summary
The change document update and the display of the change documents were
completely revised so that the changes on contracts are displayed more
clearly.
Now we provide a transaction REISCHGDOCCN which enables the reporting
of change documents of contracts.
Releases: EhP4 for SAP ERP 6.0 or higher for change documents
EhP6 for SAP ERP 6.0 or higher for REISCHGDOCCN
SAP Notes: 2096938, 2103761, 2131582

Change of conditions I
A new condition was created.

Left (until now): The change document shows that a new condition was created,
but it shows no details.
Right (now): Additional change documents were created that show the details of
the condition – here you can see e.g. the condition amount.

Change of conditions II
The calculation formula for the condition was changed from „Fixed amount“ to
„based on residential/usable space“. The unit price was set to 8,10 Euro, so that the
condition amount increased from 800 to 810 Euro.
Left (until now): The change document didn‘t show the new condition amount, it
shows only the new unit price.
Right (now): It‘s shown now that the condition amount was changed to 810 Euro.
The details of the calculation like the measurement factor were shown.

Change of conditions III
The basis data for the calculation of a condition was changed (measurement of the
rental object). This results in a decrease of the condition amount.
Left (until now): The change of the condition amount is not shown with the change
documents of the contract.
Right (now): The change documents of the contract now show the change of the
calculation basis and the changed condition amount.

REISCHGDOCCN: Information System Change Documents
• Select the change documents according

to date, user and type of the change.
• Report also shows status changes of the
contract.
• The report is embedded into "overviews"
tab in the contract.

Request: D6449
REISCNOA: contracts with multiple objects
Report to make a list of contracts with multiple objects. We need a

report where we can select the contracts with multiple objects
(output: only contracts with multiple objects including all objects).
NL:
Rapportage(s) voor bulkcontracten (contracten waaraan meerdere
huurobjecten toegewezen zijn)

Request: D6383
Master data: contracts with multiple objects
Better reorganization of contracts with multiple objects trough transaction

RECN. If the contract has multiple objects there will be no indication of the
object address. We suggest in such cases a more clear indication as
‘multiple objects available’.
NL:
Het is gewenst om bulkcontracten op het overzichtsscherm sneller te kunnen
herkennen. Bulkcontracten zijn contracten, waaraan meerdere objecten
toegewezen zijn. Dit is op het overzichtsscherm alleen maar herkenbaar door het
volgende icon en dit blijkt in de praktijk niet voldoende te zijn.
Daarnaast wordt in het scherm het adres van het eerste object getoond direct
boven de tabbladen bijv.:
Dit is misleidend. Wanneer twee of meer objecten actief zijn binnen een contract
moet de adresaanduiding via de inrichting zijn in te stellen op bijv. BULKCONTRACT.

Solution Summary
Transaction REISCNOA already displays the objects for contracts. In this report,
an additional icon will highlight the contract has more than one object assigned in
the corresponding time period.
The contract tab "objects" is now enhanced with an additional icon when multiple
objects are assigned. There is also a reference to additional objects on the
“General Date with Fast Entry" screen.
SAP Notes: 2072368, 2090560

Customizing: Choose Icon
It is now possible to determine in

Real Estate Customizing, which icons
should be used to indicate contracts
with multiple objects:
In icon for: Other and Key for Area
Icons Belong To: MOBJ – you are
able to assign a user specific.

Master Data Dialog
The tab "objects" is

marked with the
defined icon if
multiple objects
exist.
On the screen "
General Date with
Fast Entry"
corresponding text
is displayed.

Contracts with Multiple Objects in Report (REISCNOA)
Start the report ‘REISCNOA’.

Change the layout so the new
column "Multiple objects“ is
displayed and save the layout.

Contracts with Multiple Objects in Report (REISCNOA)
The periods in
which multiple
objects are
simultaneously
assigned are
flagged with the
defined icon.

Request D6423
Default Values for Contract Type
It should be possible to define default values per contract type for most (or all)
fields available on contract.
Examples:
 Should be able to define default resubmissions that would be automatically added to a
contract (e.g. 6 month before contract term ends)
 Should be able to define a default Status Profile per contract type
 Should be able to define default values for posting terms (e.g. make “exact days”
default)
Describe current pain points and obstacles
For every new contract, these defaults have to be entered manually. This is not
user friendly and may produce data input errors.

Solution Summary
It is now possible to define default values in the Customizing for the frequency
term and for reminder (resubmission) dates. These default values could be used
for example during lease abstraction.
The pre-assignment of the status schema can now be done for all object types via
a BAdI implementation.
SAP Notes: 2110873

Frequency Term: Customizing I
• Definition of templates
for frequency terms:
SM30 view
V_TIVTMRHTMPLTM
• The template contains

specifications for the
fields of the frequency
term

Frequency Term: Customizing II
• Assignment of the template to contract types, contract offers and rental objects for
which they should be used: SM30 view V_TIVTMRHTMPL
• Frequency term can automatically be created ("initial data creation") or used as
template during the manual creation
In the example, a clause

which corresponds "to
TemplateS" is automatically
defined for contracts of the
contract type CU03 during
creation.
“YearlyRent" and
"MonthlyRen“ are available
as templates for adding
frequency clauses.

Frequency Term: Application
The term "Default pre-assignment

contract" is automatically created (to
the left).
The templates assigned for this
contract type, are offered for the
selection while adding manually new
frequency terms (below).

Status Schema
The BAdI BADI_RECA_STATUS with an example class is provided.

Resubmission – Reminders
• Definition of resubmission rules which should be created during the creating of

contracts
• Differentiation per contract type is possible
• Maintenance of the rules: SM34 view cluster VC_TIVCARSRULPTM

Request D6413
Security Deposit not Linked to Contracts
Security deposits are not linked to contracts in ECC REFX. In addition security
deposits are not set up on the subordinate object level of the contracts. Because
the security deposits are not linked to the contracts, it causes additional manual
effort to track them.
Suggested Change Request
We recommend that security deposits are linked to contracts in ECC REFX and
that security deposits are set up on the subordinate object level of the contracts.
Benefits of implementing suggested change to the Standard SAP ECC REFX
module:
 Increases efficiency by eliminating the process of having to manually track security
deposits and the contracts they are linked to
 Provides for more accuracy in managing security deposits
 Many other retailers and customers would benefit from this change

Solution Summary
Now it is possible to see the link between the security deposit contract from the
covered contract. You have the possibility to jump into the security deposit
contract. This solution is based on the fact that the link between both contracts is
available through the main contract number (fields RECNBUKRSCOLLECT and
RECNNRCOLLECT).
SAP Note: 2100322

Basis Data of the Covered Contract
Currently, you are able to

get information about a
security deposit within the
covered contract. This
information only appears if
a security deposit contract
exists.

Customizing: Contract Type and Screen Sequence
The dialog for this contract type is based

on a standard screen sequence. If you
use a customer defined screen sequence,
it must be changed accordingly.

Customizing: Screen Sequence
Please check which screens belong to the

screen sequence and select the screen
which should be enhanced by the security
deposit fields.

Customizing: Alternatives for Displaying Security Deposit
There are two options for displaying the additional fields:

They could be displayed either within an additional frame or embedded in an existing
frame.
You‘ll get a new frame if you define an The fields will be embedded in an existing
additional BDT section for the security frame if you insert a BDT view for the
deposit contract and add this new section to security deposit contract into an existing
an existing screen. BDT section.

Customizing: View
In both cases you need a new

BDT view, that contains field
group 22 „security deposit“.

Customizing: Section
Furthermore, you must have a BDT

section that contains this new view. If
you want to have an additional frame,
you must create a new section. In case,
the field should appear in an exiting
frame, you need to assign the new view
to an existing section.

Customizing: Screen
If you already created a new section

you have to assign it to a screen.

Screen Generation
Call transaction RECN for a contract which is linked to a security deposit

contract and check whether the new fields are now displayed. In case the fields
are not displayed, call transaction BUSP for application RECN to start the
generation of the BDT sub-screen containers again.
Request D6388
Use Quarter Days with Sales Based Rent
We have used Quarter Day/Fixed Period functionality to set payment periods for
fixed period conditions. We need to use these same unique calendars to calculate
Sales-based Rents (sales report and sales frequencies). Current Sales-based
functionality only supports recurring Day/Week/Month periods (all based on
standard calendar periods. I foand the following in OSS Note 914067:
6. Limitations
a) Sales-Based Rent
Where Sales-Based Rent is used, it is not currently possible to enter a sales report with a
reporting rule for a quarter day period. Sales reports can be entered for multiples of days,
months or years only.
Has Quarter Day functionality been released for Sales-based Rents yet? If not,
can this functionality be extended to Sales-Based Rents? …
Solution Summary
Within the sales based rent agreement, it is now possible to use quarter days as
periods for sales reports (reporting rule) and for the calculation/settlement of sales
based rent (sales rule)
Note: 2085960
Example
Use the button “+” to create

a new reporting rule.
Capture the “Fixed Periods”
in the list and “1” for the
frequency field.
Sales Based Rent Agreement
The “Fast entry”

functionality could also be
used to create a new sales
based agreement. But it’s
not directly possible to
capture “fixed periods”.
Here you should enter
1 month as frequency. Then
you have to change it
separately within the
reporting rule and the sales
rule (see next slides).
Reporting Rule: Set Fixed Periods
Maintain the
reporting rule by
marking it in the
upper part of the
screen:
Set “Fixed Periods”
in each rule where
it was needed.
Sales Rule – Frequency
Maintain the sales

rule by marking it in
the upper part of the
screen:
Set “Fixed Periods”
in the
“Frequencies” – Tab.
If the field “fixed periods” is missing …
If the field “fixed

periods” is not
visible in the
reporting or sales
rule, you should
change the layout of
the corresponding
grid.
If the field “fixed periods” is missing …
Mark the column “Fixed

Periods”, and move it to the
left hand side and save the
layout. Don’t forget to mark
the “default setting”.
Example
The system generates now reporting periods which are following the periods for
quarter days.
Result of SBR Settlement
The sales based settlement of the example delivers the following results:
Reporting and Correspondence
 D6382 Reporting: Performance

 D6421 Reporting: Selection for Account Assignment (Posting Term)
 D6326 Reporting: Sets for architectural objects
 D6453 Selection of multiple settlement ID’s for printing (SCS)
 D6463 Creating single invoices direct from a contract
 D6448 Reporting: Choice of address type
Request: D6382
Reporting: Better performance
Better performance for several reports of the Information System (REIS-reports)

especially the condition reports.
Solution Summary
For the following real estate reports, the possibility of parallel processing is
combined with a higher-performance data retrieval:
RFREISCDCN, RFREISAOOA, RFREUSBDOA, RFREISBPBD, RFREUSBPOBJREL,
RFREISCDBD, RFREISCDCF, RFREISCDCFOBJ, RFREISCDCNAJ, RFREISCN,
RFREISCNOA, RFREISMSAO, RFREISMSBD
Releases: mostly from EhP4 for SAP ERP 6.0 and higher
SAP Notes: 2129264 (Collective Note)
Prerequisites: Customizing
• SAP Note 2109561:

Customizing table
TIVISREPPP
• Define the number of the
parallel processes per
report and determine
package sizes for the data
to be procured
• Maintenance via SM30
(View V_TIVISREPPP) or
Transaction REISREPPP
• Maintenance is also
allowed in the production
system (current settings)
Customizing
Make settings for the number of processes and the size of the data packages for
reports which often have large quantities of data. For optimal setting, first gather
values based on experience.
Recommendation:
• Depending on the available resources, 2 and 6 processes are recommendable. The value
1 means sequential processing (current processing setting).
• The maximum package size should be set according to the dataset to be processed:
• Package size 300 with large datasets
• Package size 50 with small datasets
Remark:
• The "crippling" of the system by too many parallel processes is prevented in the reporting
program.
• The “paralyses" of the system by too many parallel processes is prevented in the reporting
program.
Examples in the Development System
(Measurement by using transaction SAT, not representative)
Report Data records Runtime for Runtime for

in the report 1 Process 4 processes
REISCDCN 13.000 140 seconds 35 seconds
REISCDCN with 13.000 190 seconds 45 seconds
Business Partner
REISCDCF 24.000 36 seconds 20 seconds
REISCN 2.800 14 seconds 6 seconds
REISMSBD 26.000 83 seconds 27 seconds
REISBPBD 35 33 seconds 15 seconds
Request: D6421
Reporting: Selection for Account Assignment (Posting Term)
In the reports REISCN, REISCOLICN and REISCDCF there is no possibility to

select for the allocation to an account (e.g. cost center, order). Especially for
internal contracts.
Although these data fields are part of the reports REISCN and REISCDCF they
can't be selected before.
The selection possibility for the allocation to an account may also be provided in
the free selection zone.
Solution Summary
In the relevant reports, we now provide an additional selection option which

enables the selection of contracts based on account assignment objects in the
posting term.
SAP Notes: 2084466
Additional Selection for Internal Partners
In contract reports which

use the selection parameter
internal partners (Cost
center, order, WBS element)
is now possible.
The selection works similar
to the ‚external‘ partner
selection.
Posting Term as Basis of Report Selection
Similar to the selection

for partners – all
contracts are selected
which have the chosen
account assignment
element in the posting
term at a special time.
Request D6326
Reporting: Sets for architectural objects
RE-FX currently does not support sets for Architectural Objects. For users
who use only the architectural view, this functionality would be desirable.
Solution Summary
It’s now possible to create sets for architectural objects. You can use architectural
sets for all reports based on the logical data base for architectural objects.
SAP Notes: 2093647, 2082369, 2106813
Create Sets of Architectural Objects
To generate sets of architectural objects, you can now use transaction

REEXSETGENAO.
Create Sets of Architectural Objects
Mark all entries in the list

which are to be included
in the set(s).
Save the set(s).
Usage of sets
You can use the sets

for all reports based on
the logical data base
for architectural
objects, e.g.
REISAODT.
Request: D6453
Selection of multiple settlement ID’s for printing
During the execution of the settlement run, several run ID’s are created. At
the moment it is only possible to print one settlement ID at the time with
the correspondence transaction RECPA550. We would like to have the
possibility to select multiple entries or a range of settlement ID’s, which
makes it possible to print multiple settlement runs in one print run.
NL:
Tijdens uitvoering van de afrekeningsprocedure worden meerdere
afrekeningsruns gecreëerd. Momenteel is het niet mogelijk deze runs
tegelijk te printen met transactie RECPA550. Wij zouden graag de
mogelijkheid hebben om meerdere runs of een range van afreken runs te
selecteren, waardoor het mogelijk wordt om meerdere afrekenruns te
printen in één printrun.
Solution Summary
We now provide the possibility to select multiple settlement runs for printing of
correspondence for service charge settlement, COA settlement, tenant settlement
and COA annual budget.
The following new selection fields are available now:
• Settlement ID
• Entered by
• First Entered on
With multiple selection it is possible to create the correspondence for multiple

settlements in one print run.
SAP Notes: 2097403
Additional Selection Fields
The additional selection fields

becomes visible after pressing the
arrow key.
Request: D6463
Creating single invoices direct from a contract
Currently generating and printing of invoices is only possible with the mass
transactions RERAIV and RECPA520. This process is not designed for single
invoices. Hence, there should be a printing possibility directly out of a contract.
Solution Summary
It is now possible to create and print a single invoice directly from the contract
dialogue (in display mode).
• Additional menu item in “Extras” menu
• Authority check for transaction RERAIV_SINGLE
• Method SUPPRESS_DIRECT_INVOICING for BADI_RERA_INVOICE can be used to
suppress the menu item (e.g. for some contract types or users)
SAP Notes: 2085047
Display Contract
Call function “invoice

for Contract” in
display mode
Create and print invoice
Selections screen and list are

analogous to transaction
RERAIV.
The contract ID is predefined
in the selection screen and
not modifiable.
Request: D6448
Reporting: Choice of Address Type
At the moment it isn’t possible to choose between standard or

correspondence addresses. Besides that it is important you can select,
display or download the address data. Address data must be complete (for
instance house number supplement).
NL:
Keuzemogelijkheid standaard- en correspondentieadressen: het is van
belang dat de relevante adresgegevens geselecteerd en getoond /
gedownload kunnen worden. Daarnaast moeten de adresgegevens
volledig zijn, dus alle adresgegevensvelden moeten in de rapportages ook
beschikbaar zijn.
Solution Summary
Reports that display the main contractual partners are extended so that it can be
decided which address type should be displayed in the list.
The default behavior of the information system is changed so that the default
address is no longer displayed. However, the address type assigned in the
corresponding object or contract will be shown. Therefore, the default behavior in
reporting is adjusted to the behavior of the correspondence transactions.
SAP Notes: 2075458
Example: Partner with Multiple Addresses
The partner has multiple

addresses.
If the assignment of partners
in the contract is captured, the
address type ‘XXDEFAULT’
should be used.
Reporting
When starting a report with the

selection “Display Main
Contractual Partners” it can be
decided which address type
should be used in the report.
The default address type "as in
the contract", is in our example
‘XXDEFAULT’ address.
Reporting
Depending on the selection for displaying the main contractual partner, the
corresponding address type will be used in the report. If the chosen address
type doesn’t exist, the standard address will be used.
Accounting
 D6319 Reset Cleared Items

 D6450 and D6442 RERAPP - Delta compare this run to last run
 D6464 Book external postings of Room Reservation directly in FI-CA
 D6465 Analyses made by earmarked funds without RE-objects
 D6362 Summarization of customer line items
 Vendor Account Sheet
Request: D6319
Reverse Service Charge Settlement – Reset Cleared Items
If you want to reverse a service charge settlement, at first there is a check

about all posted documents. If there are cleared documents, an error
message like “Reveres not possible, please reset cleared items first”
occurs.
The user gets no more information (e.g. number of the cleared

documents). We need a report with all documents to a service-charge-
settlement-ID. In this report we need the possibility to reset cleared item.
Solution Summary
A report is provided that resets cleared items from a process - not only for service
charge settlement, but also for other RE processes. The selection of the relevant
documents can be done by process ID, document number or contract number.
Furthermore, if during a reversal process an error message is sent (“document
…contains cleared items”), the long text of the message contains a link to start this
report directly.
Releases: EhP4 for SAP ERP 6.0 or higher
SAP Notes: 2063700, 2078535 and 2099417
Example: Reversal of service charge settlement
Reset clearing
It is possible to reset the

clearing directly by using the
link to transaction
REEXRESETCLEARPROC.
The process ID will be taken
over in this case.
Reset Clearing: Calls from the menu
The function “Reset

Clearing” is available in
the submenu
“Accounting” for Flexible
Real Estate. It works for
all real estate processes*
where documents are
posted.
*processes: periodical posting, one-time posting, sales based settlement, service charge settlement; COA settlement,
tenant settlement
Request: D6450
Register of changes of the rent
Register of changes of the rent. We need a report to control the

financial changes / differences from one to another month.
NL:
Controlereport voor huurmutatie / huurmutatie register
Request: D6442
RERAPP - Delta compare this run to last run
RERAPP reports to include delta logic between this posting and the
last posting. Some of our reports are thousands of lines of posting
detail. We need a report to highlight what changed so we can focus
on validating the changes. This is impossible in the current RERAPP
reports. We are always creating a variance report using cash flows
to say what contracts are new this month (posting going from zero to
$x), what contracts terminated (postings going from $x to zero) and
then which contract simply have a different amount (up or down) from
last month.
Solution Summary
A new transaction RERAPPCMP: "Periodic Posting: Compare Previous Periods“ is

provided which allows:
• To simulate or execute periodic postings and to compare the cash flow items to
be posted with posted items from previous periods (or former posting runs)
• To compare already posted entries within the cash flow from previous periods
(or former posting run) with each other
SAP Notes: 2110932
Selection Screen: RERAPPCMP
Comparison mode: “Only Comparison”

Cash flow items of two periods which
are already posted could be selected
and compared.
There is an optional election possible:
• Calculation period
(Calculation Date from)
• Process ID (Accounting Reference
Number)
No simulation or posting takes places.
Selection Screen: RERAPPCMP
Comparison mode: “Comparison and

Posting”
Already posted records of the cash flow
will be selected for a comparison
period and compared with the current
simulation/posting items.
There is an optional election possible:
• Calculation period
(Calculation Date from)
• Process ID (Accounting Reference
Number)
There takes place a simulation or
posting run.
The selection of the items is possible
analogous to the RERAPP.
RERAPPCMP Document List / Error Log
Switch to error log, document list, cash flow

Changed amount with difference field
log
Posting status: Posting successful ?
Change categories:
Amounts, Control Data, Organizational
Membership, Posting Dates, Accounts
Request D6464
Book external postings of Room Reservation directly in FI-CA
At the moment there is no direct integration of the room reservation in FI-CA. All our
customers in Public Sector will use FI-CA as accounting system and they require full
integration from Room Reservation and Long-Term Seating Arrangement in FI-CA.
Solution Summary
Within the room reservation, it’s now possible to create one-time postings which
will be executed directly in FI-CA
Releases: EhP7 (617) for SAP ERP 6.0 and higher
SAP Notes: 2128745
Accounting Assignment Data of Reservation Object:
Company Code
Prerequisite:
The company code must be captured on the reservation object (Field: CoCd. (Invoice Res.)
on the tab “Account Assignment Data’).
In this company code FI-CA was determined as the accounting system.
Room Reservation with Partner Role MKK
The posting takes place onto the partner,
which is entered in field “Bill-To Party“ *
If no “Bill-To Party” recipient exists in the
reservation, it must be entered manually in
the posting dialogue.
An invoice recipient in the MKK role can be
defined either by company code of the
reservation object or if all company codes are
assigned (on the debit side) to the FI-CA
accounting system.
Choose “Ext. Reservation” and as billing type
"one-time posting".
*) The field “Bill-To Party“ will be visible if the flag “create

invoice” is active in customizing dialog: recacust Room
Reservations and Long-Term Seating Arrangements 
Room Reservations  Make General Settings for
Reservations (View V_TIVORRSSET).
One-Time Posting
When clicking the "one-

time posting“ button, an
input template appears
where required posting
data can be entered.
One-Time Posting: Log and BP-Overview
User Support: Default Data
If you want to set default values for further fields within the one-time posting
dialogue, you should use the BAdI BADI_REXA_OP (Method
PREDEFINE_DATA). This BAdI also allows you to complete data (Method
COMPLETE_DATA ) or validate data (Method CHECK_DATA).
Example:
You can use the posting activity parameter defined in the Customizing-view
V_TIVORRSSET for BADI_REXA_OP. Within FI-CA this posting activity has only
an informational character. No derivations of characteristics take place due to this
field. However, it is possible to use the customizing settings within the posting
activity as a basis for pre-assignment (default values) via BAdI. The example
implementation CL_EXM_IM_REXA_OP demonstrates such a possibility.
Rechnungsdruck (RERAIVRS)
Printing of invoices for room reservations

is possible via one-time postings with
SAP note 1971517.
Restrictions
• The specification of a contract account is necessary for the posting into FI-CA
accounting. The contract account must be created prior to the first posting and
it is not possible to create a contract account from the room reservation
dialogue.
• Only a double-line document (plus a possible tax line) can be created.
• Only local currency can be posted.
• Only FI-CA documents are supported. The generation of billing documents is
not supported.
Billing documents are defined in the Real Estate customizing under recacust  Accounting 
Integration PSCD  Billing Documents. For document types with an entry in this Customizing view
(V_TIVXABILLDOCTY – Specify Document Types Relevant for Billing) one-time postings can not
be created.
Request D6465
Analyses made by earmarked funds without RE-objects
In transaction S_P99_41000147 - - Earmarked Funds we need in the

selection screen additional selection fields.
We need following selection/input fields for RE-objects also for the output
in the journal we also need additional columns:
 Business Entity
 Building
 Property
 Rental Unit
 Real Estate Contract
 Service Charge Key
 Settlement Unit
Solution Summary
Within the earmarked funds journal (Transaction S_P99_41000147, report

RFFMRE10) additional selection fields are now provided for SAP Real Estate
Management.
An additional column is provided in the list for the real estate account assignment
(IMKEY).
SAP Note: 2105449
Earmarked Funds Journal: Select options for Real Estate
Request D6362
Summarization of customer line items
In SAP Flexible Real Estate (RE-FX) every condition flow type will generate separate
customer line items. In customizing, several settings for summarization can be made to
summarize customer line items during periodic processing. But the functionality of
summarization of customer line items has some limitations.
The system summarizes the line items in the document where the following fields have the
same content:
• Account type and account (customer account, vendor account)
• CO account assignment
• Special G/L indicator
• Currency
• Summarization flow type
• Due date (dependent on the indicator in the flow type)
• Posting term data for payment and dunning
• Withholding tax codes
• Tax data
• Advance payments and basic rent
• References, note to payee
The request: Items should be summarized also if they have different tax codes.
Solution Summary
The summarization of line items even in case of different tax codes is possible by
using a BAdI implementation. A sample implementation is available via SAP note.
The following slides demonstrate the possibilities and restrictions associated with
the BAdI implementation.
SAP Notes: 1577032, 1765810, 1975712, 2065829
Example: Without summarization
Standard behavior:
Each condition type
(cash flow record) leads
to a separate item on
customer account/
vendor account.
Customizing I: Activate summarization
General prerequisite for summarization:

The flag “Item Summarization” must be set
to “active” for the company code.
Customizing II: Summarization flow type
You have to decide

which items (flow
types) should be
summarized.
It’s not possible to

summarize
advanced payments
postings with
Special G/L
Indicator.
Customizing II: Summarization Flow Type
To summarize line items you have to assign the

same summarization flow type to the relevant
flow types. The summarization flow type can be a
new special flow type for summarization purposes
only or a flow type that is in use for a condition type.
Please take into account that follow-up postings
(e.g. credit memos) should be summarized by using
the same summarization flow type.
Customizing III: Tolerances and control of due dates
Make the following settings for each

summarization flow type:
Control of Due Dates:

How should the due date of the summarized
line item be entered?
Tolerances:
Tolerances in days for the summarization of
credit memos/receivables with different due
dates.
Settling receivable/credit memo:
Set this indicator to settle receivables and
credit memos with each other.
Example: Summarization I
After defining the

summarization flow type,
summarization will be
done for all flow types that
utilize the same
summarization flow type
- but only if the items have
the same tax code.
In this example the first

and the second line are
not summarized even
though both have the
same summarization flow
type due to different tax
codes.
Summarization for different tax codes
If you want to summarize in cases of

different tax codes, create an
implementation for BADI_RERA_DOC
based on the sample implementation
CL_EXM_IM_RERA_DOC_TAXCOMPRESS.
Summarization for different tax codes
The relevant method is BEFORE_POST.

By implementing this method, the line items of the
RE document can be changed. In this special case
the tax code is switched to “**”.
Please check:
• This BAdI is able to change the RE document
before posting. It is processed during each RE
process that creates postings.
• It is essential to check whether other
implementations of this BAdI are active in
your system.
In this case you have to insure that all these
implementations work together properly.
• Test all follow-up processes: periodical
posting, tax reporting, invoicing, service charge
settlement, sales based settlement,
correspondence, reversals, account sheet,
installment posting etc.
Example: Summarization with different tax codes
In this example, all rows are

summarized (except advance
payments) – in spite of having
different tax codes.
Overview prerequisites
• Allow summarization of partner items in general for a company code:

V_TIVCACCSET-CNDSPOS
• Define summarization flow types:

• Create new flow type if necessary as a summarization flow type:
V_TIVCDFLOWTYPE
• Assign summarization flow type to the relevant flow types:
V_TIVCDFLOWTYPE-FLOWTYPECNDS
• Define rules for due dates and tolerances: V_TIVRAFLOWTPCND
• Create a BAdI implementation to allow summarization in case of different
tax codes by copying the sample class
CL_EXM_IM_RERA_DOC_TAXCOMPRESS (BADI_RERA_DOC method
BEFORE_POST )
Limitations
• Summarization for advance payments

• Summarization of basic rent and advance payments is possible for advance payments
which are posted as revenue
• Summarization for advance payments that are not posted as revenue (but with special
G/L indicator) can be summarized with other advance payments of the same type as
long as they share the same settlement period and will be settled together (during the
same settlement run)
• Items must have the same payment and dunning dates, account, account
assignment and tax data
• Summarization of different tax codes by using the BAdI Implementation may

influence follow-up processes – you have to test them!
• Additional summarizations are possible by BAdI implementations e.g. based on
customer defined rules for payment or dunning information
• Do not use the BAdI Implementation to summarize advance payments
• Test follow-up processes
Request
Vendor Account Sheet
The so-called "tenant account sheet" is available for customer contracts. With this
account sheet it is possible to display optionally open and cleared items as well as
balances for the tenant account. For vendor contracts a comparable function
wasn’t available so far. Many Customers wanted to provide a corresponding
function in the standard.
Solution Summary
An vendor account sheet which is analogous to the tenant account sheet is now
provided. The account sheet is available in the "overviews" tab of the contract
screen. The display of the vendor based items was also integrated into reporting
transaction REISRADOCITEM.
SAP Notes: 2110070
Account sheet in overviews to the contract
Thank You!
Franz Wilhelm Kehrein Dr. Anke Köppe

Product Manager Development Manager
SAP Real Estate Management SAP Real Estate Management
Finance, GRC & Insurance IMS Application FIN1
SAP SE SAP SE
Dietmar-Hopp-Allee 16 SAP-Allee 27-29
69190 Walldorf 68789 St.Leon-Rot
Germany Germany
franz.wilhelm.kehrein@sap.com Anke.Koeppe@sap.com
© 2014 SAP AG or an SAP affiliate company. All rights reserved.

© 2014 SAP AG or an SAP affiliate company.
All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG or an
SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG
(or an SAP affiliate company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional
trademark information and notices.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP AG or an SAP affiliate company for informational purposes only, without representation or warranty of any kind,
and SAP AG or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP AG or
SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an additional warranty.
In particular, SAP AG or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related
presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP AG’s or its affiliated
companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be
changed by SAP AG or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment,
promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties
that could cause actual results to differ materially from expectations. Readers are cautioned not to place andue reliance on these forward-looking
statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.
© 2014 SAP AG oder ein SAP-Konzernunternehmen.
Alle Rechte vorbehalten.
Weitergabe and Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck and in welcher Form auch immer, ohne die
ausdrückliche schriftliche Genehmigung durch SAP AG oder ein SAP-Konzernunternehmen nicht gestattet.
SAP and andere in diesem Dokument erwähnte Produkte and Dienstleistungen von SAP sowie die dazugehörigen Logos sind Marken oder
eingetragene Marken der SAP AG (oder von einem SAP-Konzernunternehmen) in Deutschland and verschiedenen anderen Ländern weltweit.
Weitere Hinweise and Informationen zum Markenrecht finden Sie unter http://global.sap.com/corporate-de/legal/copyright/index.epx.
Die von SAP AG oder deren Vertriebsfirmen angebotenen Softwareprodukte können Softwarekomponenten auch anderer Softwarehersteller enthalten.
Produkte können länderspezifische Unterschiede aufweisen.
Die vorliegenden Unterlagen werden von der SAP AG oder einem SAP-Konzernunternehmen bereitgestellt and dienen ausschließlich zu Informations-
zwecken. Die SAP AG oder ihre Konzernunternehmen übernehmen keinerlei Haftung oder Gewährleistung für Fehler oder Unvollständigkeiten in
dieser Publikation. Die SAP AG oder ein SAP-Konzernunternehmen steht lediglich für Produkte and Dienstleistungen nach der Maßgabe ein, die in der
Vereinbarung über die jeweiligen Produkte and Dienstleistungen ausdrücklich geregelt ist. Keine der hierin enthaltenen Informationen ist als zusätzliche
Garantie zu interpretieren.
Insbesondere sind die SAP AG oder ihre Konzernunternehmen in keiner Weise verpflichtet, in dieser Publikation oder einer zugehörigen Präsentation
dargestellte Geschäftsabläufe zu verfolgen oder hierin wiedergegebene Funktionen zu entwickeln oder zu veröffentlichen. Diese Publikation oder
eine zugehörige Präsentation, die Strategie and etwaige künftige Entwicklungen, Produkte and/oder Plattformen der SAP AG oder ihrer Konzern-
unternehmen können von der SAP AG oder ihren Konzernunternehmen jederzeit and ohne Angabe von Gründen unangekündigt geändert werden.
Die in dieser Publikation enthaltenen Informationen stellen keine Zusage, kein Versprechen and keine rechtliche Verpflichtung zur Lieferung von
Material, Code oder Funktionen dar. Sämtliche vorausschauenden Aussagen unterliegen unterschiedlichen Risiken and Unsicherheiten, durch die
die tatsächlichen Ergebnisse von den Erwartungen abweichen können. Die vorausschauenden Aussagen geben die Sicht zu dem Zeitpunkt wieder,
zu dem sie getätigt wurden. Dem Leser wird empfohlen, diesen Aussagen kein übertriebenes Vertrauen zu schenken and sich bei Kaufentscheidungen
nicht auf sie zu stützen.

CC2014 Improvements Overview EN PDF

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

CC2014 Improvements Overview EN PDF

Загружено:

Авторское право:

Доступные форматы

Customer Connection Real Estate 2014

Franz Kehrein, Anke Koeppe

© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 2

 D6384 Customizing: Validity of data

© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 3

In the current situation there is no possibility to give a validity to customized data.

© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 4

Releases: mostly EhP4 for SAP ERP 6.0 and higher

SAP Notes: Collective SAP Note 2108370

© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 5

Theme SAP Note

Notice, Renewal 2085841

User Status 2080073, 2093766

Regional Locations, District Locations,

Tax Codes 2074351, 2103246

main usage type, condition of building,

© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 6

Now it will be possible to flag the

© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 7

© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 8

Solution SAP Note Release What must be done?

RE specific template 2093766 EhP 606 and Create customer implementation

© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 9

For the BAdI

© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 10

One time task:

© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 11

Please consider with the identification of obsolete user statuses, that:

© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 12

Tax code can now marked as

© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 13

The maintenance dialogs in RE-FX

© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 14

The Main Usage

© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 15

Currently just one individual user can be assigned to “Person Responsible”. It is

© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 16

Releases: EhP7 for SAP ERP 6.0 and higher

SAP Notes: 2131103

© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 17

The maintenance of “responsibility groups” could be done in Customizing as well as in the

© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 18

© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 19

In the information system it’s

All objects will be determined to which one of the group

© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 20

In the RE Navigator there is an additional

© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 21

Responsible for Contract

Responsible for Termin

In the resubmission, it’s possible to select via

© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 22

In my opinion it is necessary to set the message-type icon of the object (contract,

© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 23

The severity of a message-type (like warning, error and so on) should be

Releases: EhP2 for SAP ERP 6.0 and higher

SAP Notes: 2059105

© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 24

If you use the filter

© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 25

© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 26

© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 27

Releases: EhP4 for SAP ERP 6.0 and higher