Use of half months in the company code configuration after Go Live

Question

Hi,
Our client has a requirement to activate the functionality of u201CUse of
half months in the company code configuration in Asset accounting after 3 month of Go live.
For the above purpose, we enabled the same in our Development server
(DE5) after Go Live and we are getting some Errors at the time of Asset
posting in F-90 and Asset Explore AW01N and even depreciation Run.
Already we ran 3 months depreciation without enabling this
functionality and now the client requires this in our Production server
before running the 4 period depreciation.
We are using the same Fiscal year variant (V3) at Depreciation area
level for all our company codes. All other company codes enabled this
functionality except one company code (NOPE) .
So the client requires this Half month depreciation calculation
Functionality in company code NOPE too.
Please advice to resolve this issue at the earliest and its quit urgent.We are using the same depreciation key, asset class in all company codes.
Thanks
Man
Error details,
SYST: You cannot change the depreciation periods
Message no. AA662
Asset affected: 000016000025-0000
Diagnosis
Processing terminated because the number of depreciation periods in
company code NOPE has been changed. However, you cannot change the
number of periods in your live (productive) system.
Procedure
Change the depreciation periods back to the original value in company
code NOPE. The number of depreciation periods is determined by the
fiscal year version and the use of half-periods. At least one of these
parameters was changed.
If you want to change your system so that you can now work with half-
periods, you have to use depreciation keys with time-dependent period
control in that company code.
If you need to make general changes to the number of periods for
calculating depreciation per fiscal year, you will have to consult your
system administrator

Answer 1

hi
If you refer to SAP Note 2993, it is not possible to change to/from half
period. This is because the expired useful life are based on 12 periods
and the system is not able to change this to 24 periods.
To be able to change this settings under:
Asset Accounting>Valuation>Fiscal Year>Use of Half Months in the
Company Code.
Company code must be in status  2 (Test company code with data transfer)
Once you have finished your legacy data transfer you should set company
code as productive to avoid this changes.
Regarding error AA662,  it occurs if you change the number of period
in the fiscal year version or the use of half-periods, after you have
already posted to assets.
The cause is a different value in field ANLB-PERFY which
is the number of periods in the fiscal year.  If the number
entered here does not correspond to the number of posting periods
of the fiscal year used, the system raises error AA662 (except
for none posted areas for which ANLB-PERFY = 000 or areas
with depreciation to the date for which ANLB-PERFY = 365)
If T093C-MONMIT = 15 (half periods), ANLB-PERYF = 012 is not
correct. It should be 24.
Please note that changing the PERFY value will not be sufficient because
the expired useful life is calculated on base of PERFY. Thus PERFY has
to be adjusted and the expired useful life also.
Blaz.