Narayan Jyotiraditya Bala Banik Configuration Steps: Main Customizing Activities
Narayan Jyotiraditya Bala Banik Configuration Steps: Main Customizing Activities
Configuration steps
Main customizing activities
SPRO path:
Financial Accounting > General Ledger Accounting > Periodic Processing > Valuate > Define
Valuation Methods
Define a Valuation Method Valuation procedure or rule to be used such as “Lowest Value
Principle” or “Always Valuate”.
Financial Accounting > General Ledger Accounting > Periodic Processing > Valuate > Define
Valuation Areas
A Valuation Area is associated to a Valuation Method from the previous step, which later on be
used in transaction FAGL_FCV.
A new column with a 3rd currency type was added. However, I have not found any differences
while running FAGL_FCV even when the Company Code had 2 or 3 main currencies.
Similar to ECC with New GL with an extra currency type but no visible impact.
Financial Accounting > General Ledger Accounting > Periodic Processing > Valuate > Check
Assignment of Accounting Principle to Ledger Group
This configuration is part of the configuration of Ledger Groups (SPRO: Financial Accounting >
Financial Accounting Global Settings > Ledgers > Parallel Accounting > Assign Accounting
Principle to Ledger Groups) and although it is not directly connected to transaction FAGL_FCV, it
must be configured before any postings are made into it. This is because trying to change the
Target Ledger Group after postings is not possible.
“Postings already exist with ledgergroup XX
Message no. FINS_ACDOC_CUST368
DiagnosisPostings were already done with ledgergroup XX.”
Financial Accounting > General Ledger Accounting > Periodic Processing > Valuate > Assign
Valuation Areas and Accounting Principles
The Valuation Area created in step 2 is now connected to an Accounting Principle and also,
to Simulation Ledger/s.
For example, choosing a Valuation Area associated to the Accounting Principle “0L” will bring
connected Simulation Ledgers from transaction FINSC_LEDGER.
Choosing a Valuation Area associated to an Accounting Principle (e.g. “ZCL”) not connected to
any Simulation Ledger will result in “No values found”.
A delta logic can be applied in which the system instead of reversing the currency valuation
posting on the next month, it will post the difference between the last exchange rate valuation
with the exchange rate at the key date or new valuation date.
Financial Accounting > General Ledger Accounting > Periodic Processing > Valuate > Prepare
Automatic Postings for Foreign Currency Valuation
Setting up accounts that will be used when a Valuation Loss or Gain (P&L accounts) happens
and against which Balance Sheet account (BS account).
The P&L accounts to be set as GL Account Type “Nonoperating Expense or Income”, which is a
new option in S/4, inside transaction FS00 – GL account mainteinance. No Cost Elements are
created because of this.
Regarding more options for determining the account, OSS note 2577796 has a guided-answer
explanation on how it works.
https://launchpad.support.sap.com/#/notes/2577796
Financial Accounting > General Ledger Accounting > Periodic Processing > Valuate > Foreign
Currency Valuation > Foreign Currency Valuation: Assignment of ECS Environment
In case the ECS Environment “FAGL_FCV” does not exist, to check the “Define ECS
Environments” activity described below.
Transaction FAGL_FCV_SNRO
Create a counter that will be use during a Foreign Currency Valuation productive run execution.
Financial Accounting > Financial Accounting Global Settings > Document > Error Correction and
Suspense Accounting > General Settings > Define ECS Environments
Financial Accounting > Financial Accounting Global Settings > Ledgers > Ledger > Define
Settings for Ledgers and Currency Types
Transaction GD22
4. Tables of documents already processed > Foreign Currency Valuation: Real run vs
Simulation Ledger run
Table FAGL_BSBW_HISTRY is filled with documents that were considered in a Real/ Productive
run.
Impression
a) The Simulation Ledger seems to be a good idea from a database perspective but is not fully
mature considering the errors described above:
Although FAGLL03H already has its limitations (e.g. Fiscal Years with Archived documents not
showing a proper total), it is interesting that it is not considering these simulation documents at
all.