Scribd
Upload
84 views4 pages

FI-FC reval relation between KDF and KDB

FX revaluation - relation between KDF and KDB transaction types

Uploaded by

Arseny Shachin
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
84 views4 pages

FI-FC reval relation between KDF and KDB

FX revaluation - relation between KDF and KDB transaction types

Uploaded by

Arseny Shachin
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

How does the account determination works for Exchange Rate Differences

posting?

Image/data in this KBA is from SAP internal systems, sample


data, or demo systems. Any resemblance to real data is purely
coincidental.

Environment

 Financial Accounting (FI)

 SAP R/3

 SAP R/3 Enterprise 4.7

 SAP ERP Central Component

 SAP ERP

 SAP enhancement package for SAP ERP

 SAP enhancement package for SAP ERP, version for SAP HANA

 SAP S/4HANA Finance

 SAP S/4HANA

Reproducing the Issue

Execute the transaction F.05 or FAGL_FC_VAL or FAGL_FCV for Open Items


or Balances in different company codes.

Cause

In both company codes the account determination will be taken from KDF
(OBA1).

Resolution

OBA1 Settings and checking of the account determination in case of non


open item managed accounts (balance valuation):

1. KDF first (on valuation area):

Table: T030HB with valuation area:

step #1.1.: checking table T030HB for matching entry with key
fields Valuation area (BWBER)+Transaction currency key (WAERS)
+GL account number (HKONT).

step #1.2.: if no items found tchecking table T030HB with key


fields Valuation area (BWBER) + GL account number (HKONT) - i.e.
without transaction currency key.
If no matching entry was found in T030HB the second step is checking:

2. KDB (with valuation area):

Table: T030S with valuation area:

step #2.: checking table T030S based on exchange rate


difference key (KDFSL)+Valuation area (BWBER).

If no mathcing entry was found per valuation area the 3rd step is
checking:

3. KDF (without valuation area):

Table: T030H:

step #3.1: checking table T030H for matching entry with key
fields Transaction currency key (WAERS) + GL account number
(HKONT) + Currency Type (CURTP).

step #3.2: checking table T030H for matching entry with key
fields Transaction currency key (WAERS)+ GL account
number (HKONT) .

step #3.3: checking table T030H for matching entry with key
fields GL account number (HKONT).

If no matching entry was found in step 3 the next step is checking:

4. KDB (without valuation area):

Table: T030S (without valuation area):

step #4:checking table T030S based on exchange rate


difference key (KDFSL) without valuation area.

In case of open item managed accounts cheking is done first:

1. in KDF (on valuation area):

Table:T030HB with valuation area:

step #1.1.: checking table T030HB for matching entry with key fields
Valuation area (BWBER)+Transaction currency key (WAERS)+GL
account number (HKONT).

step #1.2.: if no items found tchecking table T030HB with key fields
Valuation area (BWBER) + GL account number (HKONT) - i.e.
without transaction currency key.

2. KDF (without valuation area):


Table: T030H:

step #3.1: checking table T030H for matching entry with key fields
Transaction currency key (WAERS) + GL account number
(HKONT) + Currency Type (CURTP).

step #3.2: checking table T030H for matching entry with key fields
Transaction currency key (WAERS)+ GL account number (HKONT) .

step #3.3: checking table T030H for matching entry with key fields
GL account number (HKONT).

If you have an account in company code A with open item management


and in other company code B non open item management, you may set
the selection parameter NO_T030H = 'X' in order to make the
program ignore the settings of KDF for the valuation of G/L account
balances (non-OI-managed accounts) but only retrieves the target account
from KDB.

For this purpose, since NO_T030H is a hidden parameter, you may define
a corresponding parameter in table TVARV with value 'X' and assign this
variable in a a corresponding report variant of valuation program by
opening all selection criteria (button 'Display all selection criteria' in the
variant maintenance screen) and setting selection parameter NO_T030H
with flag'Selection variable' checked.

For further help with parameter activation please review the


KBA 2061774.

Please also review the note 548946.

See Also

2061774 - How to use parameter NO_T030H to avoid read table T030H


548946 - FAQ: SAPF100 Account Determination

1523296 - FAGL_FC_VAL, FAGL_FCV and SAPF100 Account determination


KDB or KDF - SAP for Me

You might also like