Object-based valuation:

User guide (Version 1.42)

Attachment to SAP note 2660070

TABLE OF CONTENTS
PURPOSE OF THIS DOCUMENT ............................................................................................................... 3
PREREQUISITES........................................................................................................................................ 6
USER GUIDE .............................................................................................................................................. 6
Understanding the data flow ..................................................................................................................... 6
Object-based foreign currency valuation (transaction OBJVAL) ............................................................ 6
Selection screen ........................................................................................................................................ 6
Output......................................................................................................................................................... 8
Posting scheme ........................................................................................................................................10
Valuation reset ..........................................................................................................................................12
Posting detail ............................................................................................................................................12
Object-based regrouping (transaction OBJREG) ....................................................................................13
Selection screen .......................................................................................................................................13
Output........................................................................................................................................................14
Posting scheme ........................................................................................................................................16
Posting detail ............................................................................................................................................16
Special ledger Balance Carryforward (transaction GVTR)......................................................................18
HOW TO ANALYZE ISSUES......................................................................................................................19
Ensure that all RE-FX valuations have been posted and transferred to FI ............................................19
Check if valuation postings have been updated in FI-SL........................................................................19
Check FI-SL totals records .......................................................................................................................20
Display FI-SL totals records (transaction GD13) .....................................................................................20
Drill-down from GD13 ...............................................................................................................................23
Compare figures OBJVAL with FI-SL totals and RE-FX ..........................................................................25
Check OBJECT_VAL.................................................................................................................................26
Compare figures OBJREG with FI-SL totals and RE-FX .........................................................................27
QUESTIONS AND ANSWERS ...................................................................................................................28
OBJVAL .....................................................................................................................................................28
OBJVAL and OBJREG ..............................................................................................................................29

2
User guide for object-based valuation (version 1.42) - Attachment to SAP note 2660070

PURPOSE OF THIS DOCUMENT

This document describes how the new transactions for
 Object-related foreign currency valuation and
 Object-related regrouping
work in cooperation with RE-FX leasing.

The relevant configuration steps are described and detailed help for checking and reconciling data is
provided.

Target audiences are

 end users who run the closing activities and
 project team members who are responsible for configuration and testing of this new functionality.

Special ledger (FI-SL) should be configured as a basis for valuation processes on lease liabilities/receivables
posted by RE-FX Leasing according to SAP note 2624449.

The valuation processes for lease liabilities/receivables are designed on contract and valuation rule level.
Therefore, we need balances on this level at the end of the accounting period.

It would be too slow to do an aggregation of all postings on the lease liabilities/receivables accounts during
period end processing. For performance reasons an aggregate structure is needed in SAP ERP. This is the
function of special ledger in this scenario.

As SAP assumes that not all customers running RE-FX leasing are already familiar with special ledger
technology this guide is provided to facilitate the configuration.

At this point of time not all settings had been translated in SAP’s development system, so some screen
captures contain a mixture of English and German language. This will be updated in a later revision.

Starting with document revision 1.3 the configuration and the user guide have been split into separate
documents.

3
User guide for object-based valuation (version 1.42) - Attachment to SAP note 2660070

DOCUMENT HISTORY

Version Date Change in chapter Change

th
1.0 (included in December 7 , 2018
configuration guide)
1.1 (included in December 14th, 2018 Minor optimizations in
configuration guide) wording.
View V_FAGL_FCBAL New chapter
How to analyze issues New chapter

1.2 (included in December 21st, 2018 PREREQUISITES Notes added.

configuration guide)
REQUIRED SETTINGS New dedicated chapter
FOR DOCUMENT
TYPES USED FOR
VALUATION POSTING
1.3 (first separate January 16th, 2019 Minor clarifications
version of user guide) (specifically for classic
GL customers)
Document split:
Chapters
- User guide
- How to analyze issues
- questions and answers
are now in the separate
user guide.
1.31 May 20th, 2019 Posting detail (OBJVAL) More specific wording:
“posting lines”

Valuation reset New dedicated chapter

OBJREG: Selection SAP note 2781030
screen
OBJREG: Posting detail FBB1 type posting
explained.
Special ledger Balance Error code GU 732
Carryforward explained.
(transaction GVTR)

Typo fixed:
1.32
BSEG-DMBE2/BSEG-
DMBE3 instead of
BSEG-DMBT1/BSEG-
DMBT2
1.4 Jan 9th, 2020 Posting logic Renamed to
Posting scheme

Delta valuation for

OBJVAL added

4
User guide for object-based valuation (version 1.42) - Attachment to SAP note 2660070

1.41 March 3rd, 2020 OBJVAL Output Clarification on

exchange rates
1.42 November 20th, 2021 Minor clarifications and
additions.

5
User guide for object-based valuation (version 1.42) - Attachment to SAP note 2660070

PREREQUISITES
For prerequisites see configuration guide.

USER GUIDE

Understanding the data flow

To familiarize yourself with the functionality it is important to understand the data flow:
 RE-FX posts RE-FX documents which trigger the FI postings.
 According to special ledger settings these postings are also updated in special ledger. The only
purpose of this special ledger in this process is to provide an aggregate structure per valuation
(sub)object.
 The new object-based FI valuation functionality selects these values per valuation object from the
special ledger and calculates and posts the foreign currency valuation.
Furthermore the valuations are stored in the new table OBJECT_VAL.
 The new object-based FI regrouping functionality selects these values per valuation object from the
special ledger, calls RE-FX to get the reclassification percentage and posts the reclassification.

Object-based foreign currency valuation (transaction OBJVAL)

Selection screen
The handling is like existing foreign currency valuation for open items and GL accounts.

6
User guide for object-based valuation (version 1.42) - Attachment to SAP note 2660070

The major difference for the users is the tab strip “Valuation Objects”:

Important parameters on this screen are:

 Valuation Key Date: This date is used to determine the period. Balances per valuation object/
valuation sub object (see below) get selected from special ledger per period. So, it only makes sense
to use period end dates here.

 Flag: Valuate object balances

 Aggregation ledger: the special ledger where the values for this valuation area are stored.
(In the config guide attached to SAP note 2624449 we recommend having one special ledger for
each valuation area, so users can easily use it.)
 Relevant valuation objects:
o Lease Liabilities (Valuation object type RECL)
o Lease Receivables (Valuation object type RECR)
 G/L Account: The functionality is currently designed to be used for lease liabilities/receivables
accounts only. Please select these accounts here only!
 Currency: only required if you want to have separate runs for each currency.
(This only creates more jobs but brings the same result in the end, so we do not recommend it.)
 Identifier of the valuation object
This identifies the RE-FX contract and is composed like this
IS <Company code><contract number>, e.g.
ISLEFW2000000000126 (Company code LEFW, contract 2000000000126)

 Identifier of the valuation sub object:

Number of the valuation rule within the contract

 If you want to post foreign currency valuation with consolidation transaction types (often also called
flow types) you can enter these here and the field (BSEG-BEWAR) will be filled in the postings.

7
User guide for object-based valuation (version 1.42) - Attachment to SAP note 2660070

Output
The output is like existing foreign currency valuation for open items and GL accounts. But here the valuation
type, valuation object and valuation sub-object are the key:

 The revaluation rate (e.g. /1,150000 in the first row) is taken from exchange rate table TCURR
according to the settings of the valuation area/method.
 The exchange rate (e.g. /1,10000 in the first row) is calculated as relation of the balances in
transaction currency and company code currency. As the balance shown is aggregated from all
postings for one valuation object the exchange rate shown here is a weighted average exchange
rate of these postings. You will usually not find it in the related postings.
It is shown for informational purposes only and does not affect calculation/posting of foreign currency
valuation.

The other amounts do not need further explanation:

The button “Postings” shows you the postings (also available in simulation run).

If you position the cursor on a posting and press (will not show up in test runs) you can
navigate to the FI posting.

8
User guide for object-based valuation (version 1.42) - Attachment to SAP note 2660070

Please be aware that the foreign currency valuation postings are in transaction currency but update field
BSEG-WRBTR (here in CHF) with value 0 and update field amount in local currency (BSEG-DMBTR) with
the valuation amount. You can identify such postings in the document header as they are posted by
transaction FBB1 (field BKPF-TCODE).

If you look at the documents using a layout which only contains the column transaction currency this might
look strange at the first moment. Consequently, please use an ALV layout which includes amount in local
currency (BSEG-DMBTR). If used also additional local currencies (BSEG-DMBE2, BSEG-DMBE3).

9
User guide for object-based valuation (version 1.42) - Attachment to SAP note 2660070

Posting scheme

Postings are by default done in a reversal scheme:

Valuation posting typically at the last day of an accounting period.

Reversal posting at the first day of the next period.

After SAP note 2871569 has been implemented the tab strip “Valuation Objects” is enhanced by a section
“Delta logic”.

Both checkboxes here can only be used in if the valuation area is configured as delta valuation area (see
configuration guide).

 Year-End Valuation (No Reversal)

Specifies that a remeasurement posting is not reversed.

 Mid-year valuation (With Reversal)

Reverses the remeasurement posting with the reversal date specified on the selection screen.

You cannot set this indicator for the final valuation run of the fiscal year.

The system only considers valuations that have not been reversed (for example valuations at the end of
the year) when determining the amount to be remeasured when delta valuation is used.

The next page shows an example which explains the effects of the settings:

We have a lease liability of USD 1.000.00 (initially translated to local currency EUR at rate 1:1).

The T-charts show the postings for valuations end of October/November/December.

For simplification reasons we omit interest and amortization postings in this example.

10
Reversal posting scheme

Exchange
rate
Date USD/EUR Lease Liability P&L: FX loss
Transaction
Transaction Local Transaction Local Local Transaction Local
currency currency currency currency currency currency currency currency

1-Oct 1,00 1.000,00 USD 1.000,00 EUR

31-Oct 1,10 100,00 EUR 100,00 EUR Valuation posting

1-Nov 100,00 EUR 100,00 EUR Reversal postings

30-Nov 1,15 150,00 EUR 150,00 EUR

1-Dec 150,00 EUR 150,00 EUR

31-Dec 1,12 120,00 EUR 120,00 EUR

1-Jan 120,00 EUR 120,00 EUR

Delta posting scheme

Exchange
rate
Date USD/EUR Lease Liability P&L: FX loss P&L: FX gain
Transaction Transaction
Transaction Local Transaction Local Local Transaction Local Local Transaction Local
currency currency currency currency currency currency currency currency currency currency currency currency

1-Oct 1,00 1.000,00 USD 1.000,00 EUR

31-Oct 1,10 100,00 EUR 100,00 EUR

30-Nov 1,15 50,00 EUR 50,00 EUR

31-Dec 1,12 30,00 EUR 30,00 EUR

Delta posting scheme at year-end, reversal posting scheme used for mid-year valuations

Exchange
rate
Date USD/EUR Lease Liability P&L: FX loss P&L: FX gain
Transaction Transaction
Transaction Local Transaction Local Local Transaction Local Local Transaction Local
currency currency currency currency currency currency currency currency currency currency currency currency

1-Oct 1,00 1.000,00 USD 1.000,00 EUR

31-Oct 1,10 100,00 EUR 100,00 EUR

1-Nov 100,00 EUR 100,00 EUR

30-Nov 1,15 150,00 EUR 150,00 EUR

1-Dec 150,00 EUR 150,00 EUR

31-Dec 1,12 120,00 EUR 120,00 EUR

11
Valuation reset

In special situations it might be required to reset valuations.

Please pay attention to the restrictions for these cases:

As valuation postings contain posting lines for several valuation (sub)objects it is not possible to reset only
selected contracts on the level of "Identifier of the Valuation Object" and/or "Identifier of the Valuation Sub
object". So, these fields become inactive as soon as the flag „reset valuation“ is set:

Reversals for transaction OBJVAL are carried out via BAPI. In some situations, the use of BAPIs does not
work. In these cases, all reversals will then be put into a Batch-Input-file which has to be executed (logic
added with SAP note 2775867).

Example for such cases: You are running special ledgers without line items.
Due to missing line items BAPI reversal does not work here and you must use Batch-Input.

Posting detail

Postings are merged per account and currency. The posting lines get the same account assignments as
defined in View V_FAGL_FCBAL.

If a P&L account for currency gains/losses is configured as cost element the CO object is retrieved from the
RE-FX contract’s valuation rule.

The documents consider the currency assigned to the valuation area (in our example the local currency) and
currencies which are translated based on the valuation.

12
User guide for object-based valuation (version 1.42) - Attachment to SAP note 2660070

Object-based regrouping (transaction OBJREG)

Selection screen
The selection screen is very similar to OBJVAL – only the sort method is specific here.

For all other settings see detailed information in chapter OBJVAL.

New feature (see SAP note 2781030): If you want to post foreign currency valuation with consolidation
transaction types (often also called flow types) you can enter these here and the field (BSEG-BEWAR) will
be filled in the postings.

This feature was primarily implemented for technical reasons as some customers had a field status setting
on lease liabilities/receivables account which required consolidation transaction types. These customers
requested that all processes posting on these accounts should enable transaction type.
On the regrouping account(s) you will find only one transaction type so analysis of these accounts by
consolidation transaction types does not really make sense.

13
User guide for object-based valuation (version 1.42) - Attachment to SAP note 2660070

Output

We see more contracts here than in OBJVAL as contract in valuation area currency (EUR) did not appear in
OBJVAL (e.g. ISLEFW2000000000135).

Let us check the figures:

 Non-Valuated Base Amount in Object Currency: this is the value in contract currency (CHF) – this
is the only value which can be reconciled with the sender application RE-FX.
 The valuated base amount in valuation currency (currency of the valuation area) is the sum of:
o Non-Valuated Base Amount in Valuation Currency: the balances of the postings
translated in valuation area currency (EUR)
o Valuation Amount in Valuation Currency: The valuation fraction of the base amount in
valuation currency (currency of the valuation area). This valuation fraction is automatically
determined from previous valuation steps (foreign currency valuation) from table
OBJECT_VAL.
 Posted amount in valuation currency (currency of the valuation area): this is the amount which will be
posted by the system.

 Percentage Share of Sorted List (Rounded): This field with two digits (rounded) shows you the
reclassification percentage which was calculated in RE-FX.
The calculation of the values is based on the more precise field “Share of the Sorted List in Decimal
Format”. Note that the rounded values might not sum up to 100,00 % due to rounding differences.

The report delivers all the values you need to understand the values:

The default layout does not show all these values, but you can easily include them in your layout by pressing

button .
Then mark the lines and use the arrow button to push them to the left side. Press ‘copy’ to active it.

14
User guide for object-based valuation (version 1.42) - Attachment to SAP note 2660070

You can navigate to RE-FX via double click and see how the reclassification percentage was calculated
there (like transaction RECEISRECLASSIFY).

As mentioned above only

 Non-Valuated Base Amount in Object Currency and
 Share of the Sorted List in Decimal Format
can be reconciled with the sender application because RE-FX does not get any information about the
currency valuation posted in FI.

15
User guide for object-based valuation (version 1.42) - Attachment to SAP note 2660070

The button “Postings” shows you the postings (also available in simulation run).

Posting scheme

Postings are done in a reversal scheme:

Regrouping posting typically at the last day of an accounting period.

Reversal posting at the first day of the next period.

In our example only the non-current portion (> 1 year) will be posted according to our customizing. The current
portion remains on the lease liability account.

We recommend this configuration as it significantly reduces the number of reclassification postings.

Posting detail

The postings get the same account assignments as updated in the special ledger (e.g., profit center,
segment, business area).

The indicators "Inter-company posting" (T003-XGSUB) and "Trading partner can be entered manually"
(T003-XMGES) must be set for the document types used here for the regrouping postings. Please check this
setting in transaction OBA7.

The documents consider the currency assigned to the valuation area (in our example the local currency) and
currencies which are translated based on the valuation currency.

16
User guide for object-based valuation (version 1.42) - Attachment to SAP note 2660070

Please be aware that the reclassification postings are composed in the same way as foreign currency
valuation postings: field BSEG-WRBTR (here in CHF) has always value 0 and only amount fields in local
currency (BSEG-DMBTR) or additional local currencies (BSEG-DMBE2, BSEG-DMBE3) contain values. You
can identify such postings in the document header as they are posted by transaction FBB1 (field BKPF-
TCODE).

If you look at the documents using a layout which only contains the column transaction currency this might
look strange at the first moment. Consequently, please use an ALV layout which includes amount in local
currency (BSEG-DMBTR). If used also additional local currencies (BSEG-DMBE2, BSEG-DMBE3). See
picture for OBJVAL postings above.

If you want to have transaction currency amount filled, you must activate checkbox „Fill Transaction Currency
Amount“ (P_XTCAMT). If the checkbox is missing, please implement SAP note 3224629 first. You must
ensure that this option is only used for one valuation area. Otherwise, transaction currency would be
reclassified more than one time which does not make sense.

17
User guide for object-based valuation (version 1.42) - Attachment to SAP note 2660070

Special ledger Balance Carryforward (transaction GVTR)

Like for general ledger it is required to run a carryforward for special ledger when a new fiscal year begins.
The procedure is the same as for general ledger.

Transaction GVTR

If you get error code GU 732 „No valid versions found for ledger“, please check ledger version in transaction
GCL2 or GCL3.

18
User guide for object-based valuation (version 1.42) - Attachment to SAP note 2660070

HOW TO ANALYZE ISSUES

This chapter provides detailed guidance on how to analyze issues. Please check the prerequisites and
posted data in detail before creating support incidents.

Ensure that all RE-FX valuations have been posted and transferred to FI

We assume that all valuation postings for the period have been done. You can ensure this by running
transaction RECEEP: there should be nothing to post (message RERACA049).

Check if valuation postings have been updated in FI-SL

You can navigate from FI posting (e.g., in transaction FB03) to further accounting documents or to document
relationship browser (DRB) via menu:

There might be more special ledgers (e.g., for other purposes like costs of goods sold reporting) here and
you do not see to which special ledger the posting goes to.

Therefore, we suggest choosing the document relationship browser (DRB) which also shows the special
ledger (e.g., ledger LE for our scenario) ins such cases:

19
User guide for object-based valuation (version 1.42) - Attachment to SAP note 2660070

Here we see that the initial posting for the lease liability has been posted to special ledger LE.

Please check that accounts for lease liabilities or lease receivables are shown in FI-SL document.

Please be aware the FI-SL document will not always show the same posting lines as FI document. FI-SL
allows postings which contain only one line and does not enforce a balance zero per document as FI does.

If you apply a ledger selection rule filtering by accounts as described as an alternative approach in the FI-SL
configuration guide (see SAP note 2624449) you will see less lines in the FI-SL document than in the FI
document. This is OK as we only need the lines lease liabilities or lease receivables in FI-SL.

In our example this means that there would not be a posting line for asset account 2005.

You can also navigate to the originating application RE-FX.

Error handling:
 If your posting does not show up in FI-SL please check FI-SL configuration according to SAP note
2624449.
 If the lines for lease liabilities or lease receivables are missing, check FI-SL ledger selection rule
according to SAP note 2624449.

Check FI-SL totals records

Display FI-SL totals records (transaction GD13)

FI special ledger totals records can be analyzed using transaction GD13.

In the first screen you choose the special ledger

then you can enter selections:

20
User guide for object-based valuation (version 1.42) - Attachment to SAP note 2660070

For the leasing use case you will typically select data by

 Record type: always 0 (actuals)

 Version: always 1
 Fiscal year
 Company Code
 Account number(s) of lease liabilities/receivables accounts
 Type of the valuation object:
o RECL for lease liabilities
o RECR for lease receivables

 Identifier of the valuation object:

This identifies the RE-FX contract and is composed like this
IS <Company code><contract number>, e.g.,
ISLEFW2000000000120 (Company code LEFW, contract 2000000000120)

 Identifier of the valuation sub object:

Number of the valuation rule within the contract

 Posting period (for balance accounts the system will automatically calculate the balances at the end
of the period (including carryforward).

Note that the fields available are depending on the special ledger configuration (see SAP note 2624449).

We recommend using variants here.

Please be aware that the special ledger (LE in this case) is also saved in the variant, so it makes sense to
save separate variants for each special ledger.

21
User guide for object-based valuation (version 1.42) - Attachment to SAP note 2660070

As GD13 is quite technical the standard layout might look confusing at the first glance

but you can define a suitable layout by pressing button :

Defining ALV layout: sort criteria/subtotals

The subtotals per contract/valuation rule might look more familiar as the values in transaction currency are
identical to the values in RE-FX:

Transaction GD13 with specific layout

As there are separate totals records for debit and credit (S/H) and each reference transaction (technical
fieldname AWTYP, REACI identifies postings from RE-FX leasing) business users should focus on subtotals
per contract/valuation rule here.

Reference transaction BKPFO identifies adjustment postings by OBJRECON which became necessary after
certain changes in contract data or master data (e.g. Profit Center adjusments on lease liability account after
account assignments are changed in the contract. This functionality was introduced with SAP note 2927516.

22
User guide for object-based valuation (version 1.42) - Attachment to SAP note 2660070

After foreign currency valuation (OBJVAL) or reassignment postings caused by organizational changes
(OBJRECON) have been posted new reference transactions (technical fieldname AWTYP) will show up
here:
BBKPF: Foreign currency valuation postings (direct postings)
BKPF: Foreign currency valuation postings (postings by batch input)
BKPFO: Reassignment postings for organizational changes

Transaction GD13 with specific layout including foreign currency valuation postings (BBKPF)

The values in company code currencies cannot be reconciled with RE-FX when contract valuation rule posts
in foreign currency.

Error handling:
 If your posting does not show up in FI-SL please check FI-SL configuration according to SAP note
2624449.
 If values of foreign currency valuation rules show up in the company code as transaction currency
here, please check the flag “Balances in local currency only” (SKB1-XSALH) in the GL master
record.
 If the lines for lease liabilities or lease receivables are missing, check FI-SL ledger selection rule
according to SAP note 2624449.
 If you see only debit (S) or credit (H) lines here, you might have forgotten to run the carryforward.
You can check this by running GD13 for period 0 (carryforward).

Drill-down from GD13

For detailed analysis you can klick on single lines in GD13,

23
User guide for object-based valuation (version 1.42) - Attachment to SAP note 2660070

another klick navigates to the FI-SL line items

FI-SL line items document

and the next klick calls transaction FB03 to show the FI posting:

FI document (FB03)

You can navigate from FI posting to further accounting documents or to document relationship browser
(DRB) via menu which was shown above in chapter Check if valuation postings have been updated in FI-
SL.

24
User guide for object-based valuation (version 1.42) - Attachment to SAP note 2660070

Compare figures OBJVAL with FI-SL totals and RE-FX

The figures in OBJVAL

OBJVAL

are selected from FI-SL

Transaction GD13 with specific layout

… and should match with valuation in RE-FX:

RECN: valuation

25
User guide for object-based valuation (version 1.42) - Attachment to SAP note 2660070

Check OBJECT_VAL

The valuations of OBJVAL are stored in table OBJECT_VAL:

SE16N: table OBJECT_VAL

Method 1 is fixed value for foreign currency valuation. These valuations will be considered by OBJREG.

26
User guide for object-based valuation (version 1.42) - Attachment to SAP note 2660070

Compare figures OBJREG with FI-SL totals and RE-FX

The procedure here is very similar as for OBJVAL:

The figures in OBJREG

OBJREG

are selected from FI-SL (reference transaction REACI only),

Transaction GD13 with specific layout

consider the valuations of OBJVAL stored in table OBJECT_VAL

Transaction SE16N: table OBJECT_VAL

… and should match with valuation in RE-FX:

Transaction RECN: valuation

You can navigate to RE-FX via double click and see how the reclassification percentage was calculated
there (like transaction RECEISRECLASSIFY).

As mentioned above only

 Non-Valuated Base Amount in Object Currency and
 Share of the Sorted List in Decimal Format
can be reconciled with the sender application because RE-FX does not get any information about the
currency valuation posted in FI.

27
User guide for object-based valuation (version 1.42) - Attachment to SAP note 2660070

QUESTIONS AND ANSWERS

OBJVAL

Q: I get small foreign currency differences in OBJVAL even if everything was posted with the same exchange
rate as used for valuation. How can this happen?

A: FI translates the currency for each posting. OBJVAL aggregates the balance for each valuation object ID/
valuation sub object ID in transaction currency and translates this balance. This different calculation can
cause minor differences. See example:

Foreign Currency Rate Valuation area Currency

Liability -100,10 1,1 -110,11
Amortization 5,05 1,1 5,56
-104,55 Posted value in FI

Total -95,05 1,1 -104,56 Translated from total in foreign currency

-0,01 Posting

Q: I do not understand the exchange rates used by OBJVAL.

A: Check valuation method in customizing.

If you have problems understanding the exchange rates which are used by the valuation program it is often
helpful to check transaction EWCT to understand how the rates are derived.

Transaction EWCT

28
User guide for object-based valuation (version 1.42) - Attachment to SAP note 2660070

Checking exchange rates in transaction S_BCE_68000174 (table TCURR) might be misleading if you do not
know the currency customizing in detail. In this example you see that exchange rate type M is pointing to
exchange rate type EURX so you would have to look for EURX entries in TCURR.

OBJVAL and OBJREG

Q: In the output of OBJVAL or OBJREG there is more than one line some contract / valuation rule (valuation
object ID, valuation sub object ID). How can this happen?

A: Please check SL totals records using transaction GD13 for the same valuation object ID/valuation sub
object ID. You will also see several lines here which will only differ in some account assignments (e.g., profit
center or partner).

Example: GD13 showing inconsistencies caused by customizing issue in RE-FX

This is typically caused by inconsistent customizing (like different trading partner settings in document types
for right-of-use asset posting and amortization postings) or subsequent changes in account assignments in
the sender application RE-FX. The problem is not within OBJVAL or OBJREG. But OBJVAL or OBJREG
reveal the existing inconsistency which should be fixed as soon as possible.

If you want to post leasing related postings with trading partner assignment (BSEG-VBUND) please ensure
that settings have been made according to SAP note 2704490. Inconsistent settings cause similar issues for
trading partners as shown for profit centers.

SAP notes 2729894 to 2730951 implement new checks in RE-FX for ensuring data consistency.

29
www.sap.com/contactsap

© 2018 SAP SE 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 SE or an SAP affiliate company.

The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable
for errors or omissions with respect to the materials. The only warranties for SAP 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 SE 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 SE’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 SE 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 undue reliance on these forward-looking statements, and they should not be relied upon in making purchasing decisions.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other
countries. All other product and service names mentioned are the trademarks of their respective companies. See http://www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark
information and notices.