Documentos de Académico
Documentos de Profesional
Documentos de Cultura
Public
Overview
Miscellaneous
Master Data
Contracts
Reporting and Correspondence
Accounting
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.
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.
On demand:
Maintain the corresponding entries in the
customizing for obsolete user statuses.
• 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.
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.
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.
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.
Text
If you now use the
filter to display
errors or warnings
only, the header
lines with the
contract information
disappears no
longer.
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.
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).
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.
The complete memo can be displayed by using the respective list function.
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
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
It‘s now possible to restrict the compression of measurements with the same
values and adjacent periods.
Input:
Two adjacent intervals with the
same measurement value
Measurement types
which shouldn’t be
compressed in one
record must be defined
in customizing
After changing the measurement type configuration, the system prevents the
compression of measurements with the same measurement amounts and
adjacent periods.
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.
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.
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.
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.
The posting term for the new period with account determination “FM” is now taken into
account for the periodic posting run.
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
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.
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
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.
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 54
Solution Summary
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.
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”.
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).
Releases: open
Selection of contracts
(logical data base)
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.
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:
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.
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.
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.
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
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.
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.
NL:
Rapportage(s) voor bulkcontracten (contracten waaraan meerdere
huurobjecten toegewezen zijn)
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.
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.
The periods in
which multiple
objects are
simultaneously
assigned are
flagged with the
defined icon.
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.
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.
• Definition of templates
for frequency terms:
SM30 view
V_TIVTMRHTMPLTM
• 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
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
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).
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.
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 100
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? …
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 101
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
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 102
Example
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 103
Sales Based Rent Agreement
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 104
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.
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 105
Sales Rule – Frequency
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 106
If the field “fixed periods” is missing …
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 107
If the field “fixed periods” is missing …
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 108
Example
The system generates now reporting periods which are following the periods for
quarter days.
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 109
Result of SBR Settlement
The sales based settlement of the example delivers the following results:
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 110
Reporting and Correspondence
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 111
Request: D6382
Reporting: Better performance
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 112
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
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 113
Prerequisites: Customizing
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 114
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.
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 115
Examples in the Development System
(Measurement by using transaction SAT, not representative)
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 116
Request: D6421
Reporting: Selection for Account Assignment (Posting Term)
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.
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 117
Solution Summary
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 118
Additional Selection for Internal Partners
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 119
Posting Term as Basis of Report Selection
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 120
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.
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 121
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.
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 122
Create Sets of Architectural Objects
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 123
Create Sets of Architectural Objects
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 124
Usage of sets
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 125
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.
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 126
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
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 127
Additional Selection Fields
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 128
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.
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 129
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)
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 130
Display Contract
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 131
Create and print invoice
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 132
Request: D6448
Reporting: Choice of Address Type
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.
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 133
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.
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 134
Example: Partner with Multiple Addresses
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 135
Reporting
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 136
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.
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 137
Accounting
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 138
Request: D6319
Reverse Service Charge Settlement – Reset Cleared Items
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 139
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.
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 140
Example: Reversal of service charge settlement
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 141
Reset clearing
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 142
Reset Clearing: Calls from the menu
*processes: periodical posting, one-time posting, sales based settlement, service charge settlement; COA settlement,
tenant settlement
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 143
Request: D6450
Register of changes of the rent
NL:
Controlereport voor huurmutatie / huurmutatie register
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 144
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.
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 145
Solution Summary
• 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
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 146
Selection Screen: RERAPPCMP
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 147
Selection Screen: RERAPPCMP
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 148
RERAPPCMP Document List / Error Log
Change categories:
Amounts, Control Data, Organizational
Membership, Posting Dates, Accounts
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 149
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.
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 150
Solution Summary
Within the room reservation, it’s now possible to create one-time postings which
will be executed directly in FI-CA
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 151
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.
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 152
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".
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 153
One-Time Posting
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 154
One-Time Posting: Log and BP-Overview
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 155
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.
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 156
Rechnungsdruck (RERAIVRS)
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 157
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.
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 158
Request D6465
Analyses made by earmarked funds without RE-objects
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
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 159
Solution Summary
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 160
Earmarked Funds Journal: Select options for Real Estate
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 161
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.
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 162
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.
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 163
Example: Without summarization
Standard behavior:
Each condition type
(cash flow record) leads
to a separate item on
customer account/
vendor account.
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 164
Customizing I: Activate summarization
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 165
Customizing II: Summarization flow type
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 166
Customizing II: Summarization Flow Type
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 167
Customizing III: Tolerances and control of due dates
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 168
Example: Summarization I
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 169
Summarization for different tax codes
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 170
Summarization for different tax codes
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.
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 171
Example: Summarization with different tax codes
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 172
Overview prerequisites
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 173
Limitations
• Items must have the same payment and dunning dates, account, account
assignment and tax data
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 174
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.
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 175
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.
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 176
Account sheet in overviews to the contract
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 177
Thank You!
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.
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 or an SAP affiliate company. All rights reserved. Public 179
© 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.
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.
© 2014 SAP AG or an SAP affiliate company. All rights reserved. Public 180