Fiscal Year Change

RAJAWE00

Renate Lamparter-Kost
SAP AG
SAP AG 1999 RAJAWE (Renate Lamparter-Kost) / 1

Motives
The values of an asset are managed and stored for a particular
year. Therefore, a fiscal year change has to be carried out at the
beginning of a new fiscal year for technical reasons.
The fiscal year change is the precondition for carrying out
postings to the asset in the new fiscal year. In other words, you
have to carry out the fiscal year change before you can make
the first posting to an asset in the new year.
Remark!

Naturally you can still post to the prior fiscal year

even after the fiscal year change has taken place.
If you do so, values from the prior year are still
carried forward to the new fiscal year.

SAP AG 1999 RAJAWE (Renate Lamparter-Kost) / 2

Involved Tables
Table ANLC:
ANLC

ANLC is the table for the sum of all the asset

values per fiscal year and depreciation area for
each asset.

Table ANLB:
ANLB

ANLB contains (apart from the depreciation

parameters) for each asset and per depreciation
area the highest fiscal year that can be posted for
this asset (ANLB-LGJAN).

Table T093C

T093C

T093C contains per company code the current

fiscal year (T093C-LGJAHR), e.g. the highest
fiscal year to which you can post per company
code.

SAP AG 1999 RAJAWE (Renate Lamparter-Kost) / 3

Changes to the Database

Table T093C:
T093C

Before the fiscal year change

BUKRS LGJAHR
1000
2000

After the fiscal year change to 2001

BUKRS LGJAHR
1000
2001

An update for table T093C is carried out.

SAP AG 1999 RAJAWE (Renate Lamparter-Kost) / 4

Changes to the Database

Table ANLC

ANLC

Before the fiscal year change to 2001

BUKRS ANLN1
1000
4711

ANLN2
0000

KNAFA NAFAP
0
120,00-

NAFAG ANSWL NAFAV

0
1200,00 0

SAP AG 1999 RAJAWE (Renate Lamparter-Kost) / 5

GJAHR AFABE
2000
01

KANSW
0
NAFAL
0

Changes to the Database

Table ANLC
After the fiscal year change to 2001
BUKRS ANLN1
1000
4711
1000
4711

ANLN2
0000
0000

GJAHR AFABE
2000
01
2001
01

KNAFA NAFAP
0
120,00120,00- 120,00-

NAFAG ANSWL NAFAV

0
1200,00 0
0
0
0

KANSW
0
1200,00
NAFAL
0
0

For each depreciation area and each asset a new entry in ANLC
is inserted.
SAP AG 1999 RAJAWE (Renate Lamparter-Kost) / 6

Changes to the Database

Table ANLC

A new entry for each depreciation area for the new fiscal
year is created per each asset.
The cumulated values are calculated the following way:

KANSW (CY) = KANSW(PY) + ANSWL(PY)

KNAFA (CY) = KNAFA(PY) + NAFAP(PY) +
NAFAL(PY) + NAFAV(PY)
and accordingly for other fields.

(CY means current fiscal year)

(PY means previous fiscal year)

SAP AG 1999 RAJAWE (Renate Lamparter-Kost) / 7

Changes to the Database

Table ANLB:
Before the fiscal year change to 2001
BUKRS AFABE
1000
01

LGJAN
2000

LGJAN has to be the highest fiscal year entered

for each asset and depreciation area in table
ANLC.

SAP AG 1999 RAJAWE (Renate Lamparter-Kost) / 8

Changes to the Database

Table ANLB:
After the fiscal year change to 2001
BUKRS AFABE
1000
01

LGJAN
2001

ANLB is updated, e.g. LGJAN is adjusted to the

new fiscal year of table T093C.

SAP AG 1999 RAJAWE (Renate Lamparter-Kost) / 9

Changes to the Database

Sequence of the changes
First table T093C is updated.
Then the ANLB-LGJAN fields are updated.
Afterwards the new entries in ANLC are inserted, if ANLBLGJAN before the fiscal year change was lower than the new
fiscal year.

If LGJAN is lower than the highest fiscal year in

ANLC for one asset the fiscal year change will
dump with INSERT_DUPREC.
Note 162756 implemented with release 46B is
able to manage the fiscal year change without a
dump.

SAP AG 1999 RAJAWE (Renate Lamparter-Kost) / 10

Without a Fiscal Year Change

Without a fiscal year change
No postings are possible
Assets that are not changed do not show up in reporting.

Thus the end values of the asset history sheet for the
previous
fiscal year do not correspond to the start values of the new fiscal
year.

SAP AG 1999 RAJAWE (Renate Lamparter-Kost) / 11

Assets Affected by the Fiscal Year Change

Assets which are affected by the fiscal year change
only assets that are capitalized are changed (because they
show ANLC-values)
No deactivated assets are changed.
Example: Asset A is deactivated in 1998.
Thus the last entry in ANLC would be for 1998.
The fiscal year change up to 2000 is done.
The customer takes off manually the deactivation date. (No
more possible in new releases)
Asset is not yet changed to 2000.

If the fiscal year change to 2001 is

performed but the fiscal year 1998 is
already closed in FI or/and AA, the error
message, that 1998 is closed will appear.

SAP AG 1999 RAJAWE (Renate Lamparter-Kost) / 12

Limitations of the Fiscal Year Change

The fiscal year change cannot be done
only for single assets.
only for single depreciation areas.

The fiscal year change can

be repeated as often as wanted
(only not yet changed assets are considered)

be done for several subsequent years

(only practible if single assets were not changed during the
last fiscal year change.

SAP AG 1999 RAJAWE (Renate Lamparter-Kost) / 13

When is the Fiscal Year Change to be Done?

For a productive company code (T093C-XANUEB = )
the fiscal year change can only be done in the last period of
the fiscal year (to avoid long processing times and too
much data)
For a calendar fiscal year the fiscal year can
be done in december the soonest.
For test company codes (T093C-XANUEB = 2) the fiscal
year change can always be performed.

Dangerous for Euro Conversion !

SAP AG 1999 RAJAWE (Renate Lamparter-Kost) / 14