Fiscal year variants in co.code have inconsistent start date.Msg no AC531

Hi Experts
We went with 24 periods after Go live. I am trying to assign the TAX basis fiscal year variant(TX) at Depreciation area level. But it's not letting to add with the following error message.
Fiscal year variants in co.code have inconsistent start date
Message no. AC531
Diagnosis
The first day of the fiscal year for variant TX (24periods) in company code in Asset Accounting differs from the first day of the fiscal year for variant D1(12 periods) in General Ledger Accounting.
However, both variants must have the same start and end date! Only the periods within the fiscal year can be different in the two variants.
Please guide me how to fix this error message.
Thanks in advance
Meenakshi.N
Edited by: Meenakshi.Nakshatrula on May 3, 2010 5:45 AM

Hi,
Message no. AC531 says:
The first day of the fiscal year for variant K4 in company code in Asset
Accounting differs from the first day of the fiscal year for variant NL
in General Ledger Accounting.
However, both variants must have the same start and end date! Only the
periods within the fiscal year can be different in the two variants.
The error is described in note 844029 :-
In the NewGL in Asset Accounting, it is still not possible for
depreciation areas to have fiscal year variants with different start and
finish dates. If you try to assign a fiscal year variant to an area,
whereby the fiscal year variant infringes this restriction, the system
issues error message AC 531.
Regards Bernhard

Similar Messages

Assigning Different Fiscal Year Variants between comapny codes

Folks,
We have 2 company codes 1000 and 1010 both are assigned to controlling area 2000. I want to know what are the impacts of assigning company 1000 and 1010 to different fiscal year variants. I get this warning message when i try to save.
Please advice if this is advisable to do? and what are the impacts.
Message no. KT297
Diagnosis
Fiscal year variant K4, controlling area 2000, does not agree with fiscal year variant V9, company code 1010.
The following entries must agree:
Same number of posting periods (the number of special periods may vary)
Same period limits
Procedure
Ensure that the fiscal year variants of the controlling area and the assigned company codes agree. If necessary, maintain the fiscal year variants.

Dear Zaid Azam,
you have assigned 1000 and 1010 to one controlling area 2000,
To assign more than one company code to one controlling area the below are conditions
1) The Operative fiscal year variants in the company codes must match the fiscal year variant in controlling area.
2) The company codes must use the same chart of accounts.
So if you are assigning other fiscal year variant where the number of posting periods are different, hece system giving an error.
Thanks and Regards
A.Rama Krishna

Fiscal year variant V3 not defined or maintained for date 01.01.2011

Hi Team,
While doing "ABUMN" we are getting below error message"
Fiscal year variant V3 not defined or maintained for date 01.01.2011
Message no. GMMASTERDATA108
if we change asset value date 02.01.2011, there is no error message.
we are getting error message only when asset value date is 01.01.2011.
Please let us know is there any problem 01.01.?
Thanks and Regards,
Ram

Hi Ashwin,
Yes I have maintained 31 days for JAN in OB29. Even though I'm getting the same information.
Could you give some other solution.
Thanks & Regards
SK.

Different fiscal year variants

Our client follows two fiscal year variants. For global reporting purpose they follow a different convention 445. For meeting local reporting requirements at subsidiaries in different countries calendar year Jan to Dec is followed. Both the fiscal year variants will have different start and end dates for any fiscal year. As far as GL reporting is concerned we could achieve this by using new ledger solution.
I am facing a challenge while configuring these two different fiscal year variants in asset accounting. I am planning to use 445 for my 01 area and I want to create another depreciation area for the calendar year reporting, but I am not able to do it.
I am getting the below error message
AC539 :Fiscal year variants in co.code have inconsistent start date
Diagnosis
The first day of the fiscal year for variant K4 in company code in Asset Accounting differs from the first day of the fiscal year for variant SD in General Ledger Accounting.
However, both variants must have the same start and end date! Only the periods within the fiscal year can be different in the two variants.
Does any body have come across similar situation and what would be the solution to achieve this ?

Hello Reuta Kulkarni,
there is no standard functionality available to cover your requirement. Still, a customer specific project solution for a workaround can be offered by SAP Custom Development. Please note, that such a solution requires detailed analysis of the customer requirements and is chargeable.
If you are interested you will find details in note 1175751.
Best regards,
Andreas

Multiple Fiscal Year Variant in the same client in SEM-BCS...

I have already looked at some earlier threads relating to this but didn't get a convincing answer to what I would like to know.
We have had a working SEM-BCS system with fiscal year variant K4. There was no need for defining leading fiscal year variant and none was defined. SAP, by default takes, K4 as the leading fiscal year variant.
Now there is a requirement for going on a different fiscal year variant for which we have created another databasis (there were a few other reasons besides these) with the same InfoObjects that we used earlier but with different fixed parameters, one of which is fisc year variant V9. Soon, we started experiencing bizarre dumps in the configuration which ultimately convinced me to define a leading fiscal year variant. I was reluctant to do so because there is a lot of old data (which will become 'historical' from new data basis point of view) from the working system on K4 that would still need to be reported on even when we have new BCS solution in the new fiscal year variant V9. That is not going away. There is a need to keep the old data for reporting (hence the rationale for a different data basis among a few others).
Since earlier Master Data was configured in the old fisc year variant K4, now I have defined the leading fiscal year variant as V9 so that MDF can appropriately identify the period dependency.
I would like to know if any of you have had an unexpected behavior from the system going forward. Does the system dump out when you try to read the old data (from earlier K4).
I have tried to explain the dilemma as clearly and succinctly as possible but if you need more clarifications, please do let me know.
I would really appreciate your help in this.

Is your requirement is that K4 to be changed to Z5.
The best way you can do it is in the transformation. Instead of directmapping,
Write a code like this in the trransformation to the cube
If SOURCE FIELD - 0FISCVAR eq 'k4'.
SOURCE FIELD - 0FISCVAR = 'Z5'.
I dont think we can change th data in the query being displayed. we can change the keyfigure values in query by frmulas etc...
but for a characteristic, i think we will be able to restrict bt not change the value.
to obtain the requirement, w have to get the data change before query designer that is in the cube leve.
Hope this helps,
Sri...

Use of different fiscal year variant in leading&non leading ledgers and Asset closing&Reporting

Experts,
Need one clarification on using different fiscal year variants for Leading(0L)&non Leading(NL) Ledgers and impact on Fixed Asset Accounting.If I use say V6(Jan2013-Dec2013) for Leading Ledger and April2013-March2014 for non leading Ledger,(local GAAP)-please clarify the following.
1.Does Asset Accounting gives all standard reports as expected in both(Leading&Locals) the Depreciation areas?Do we need to any settings specially for in the above scenario?(I am assuming point#4 given below may not help for this as system gives an error if both the fiscal year variants have different start&end dates)
2.How is Year end in Asset Accounting handled?If I close the year end in Asset Accounting for Company Code as per Leading Ledger i.e say by Dec 2013,can I still post the asset entries in non leading ledger?Because Financial year for Leading ledger will be 2014 and non leading will be still 2013(in Jan2014).
3.I am aware SAP has some restrictions way back in 2005-2007 (SAP note 844029) for different fiscal year variants in Leading&Non Leading Ledgers,Does SAP come out with any solution later?
4.What is the exact use of the settings at Asset Accounting>>Valuation>>>Fiscal year>>Fiscal year variants at company code level or Depreciation area level?My understanding here is,they are not meant for using different fiscal year variant with different start&end dates but they are meant for using different fiscal year variant with same START&END DATES and have different number of posting periods i.e 1 can have 12 and other can have 13.
Please can you give your comments?
regards
hinfi

Hi Hinfi,
It seems standard SAP does not manage different fiscal year variants (at least with different start/end dates) in different depreciation areas.
However, they came up with an add-on solution called Multiple Calendar Tool and based on a mirroring solution that synchronizes asset transactions in a mirror company code.
It's all explained in following notes:
Note 1175751 - Project solution for alternative fiscal year variant
Note 1636025 - Asset acctg multi calendar tool 1.0_ SP Note
Note 1658489 - Installation of Asset acctg multi calendar 1.0 software
Note 1658714 - Asset acctg multi calendar tool_ Overview Note
Note 1691481 - Release strategy_ Asset acctg multi calendar tool
Note 1951069 - Different fiscal year variants in General Ledger Accounting (New) (NewGL) under the new Asset Accounting (FIN_AA_PARALLEL_VAL)
I don't know if it's commonly used and personnaly have no feedback on it. I was curious to check how to manage a depreciation area 01 posted in a leading ledger in US GAAP (FYV january to december) and another depreciation posted in a non leading ledger in Indian GAAP (FYV april to march).
BR
Gregory

Fiscal year variant V3 is not maintain for calender year

Hi,
when i was entered capitalization date in asset master (t.code AS01) the system given error message
(Fiscal year variant V3 is not maintain for Calender year) message No FGV002
I cheked the fiscal year setting and also assign the fiscal year variant to company code.
Its very urgent.
thanks
Kareem

hi
Check your FYV settings. some inconsistency might be there
refer at
http://help.sap.com/saphelp_40b/helpdata/es/95/e42c7dd435d1118b3f0060b03ca329/content.htm
regards
Srilakshmi

No Fiscal year variant specified

Hi All,
When im trying to exceute funcation module "FKK_FM_GET_FISCAL_YEAR" im encountring with error" No Fiscal year variant specified".
Anyone have idea

The fiscal year is alreay assigned we doing postings also.
Note: Other than TH country company codes it working fine.
Please advise.....
Regards

One Controlling Area for Two CoCds with different Fiscal Year variant

Hi,
I have a Company code with FYV "A1" with 12 Periods (Apr - Mar) - Fiscal year start at Apr-01 and ends Mar-31 of the next year.
I have another company code with FYV "B1" with 12 Periods (Jan-Dec). - Fiscal year start at Jan-01 and ends Dec-31.
Chart of Accounts for both the company code is same.
Can I assign these two company codes to one Controlling Area?
When I try to assign the company codes, I got the following warning message.
Differing fiscal year variants: A1 - B1
Message no. KT297
Diagnosis
Fiscal year variant A1, controlling area 1000, does not agree with fiscal year variant B1, company code 5001.
The following entries must agree:
- Same number of posting periods (the number of special periods may vary)
- Same period limits
Procedure
Ensure that the fiscal year variants of the controlling area and the assigned company codes agree. If necessary, maintain the fiscal year variants.
1. What is the meaning of "Same period limits"?
2. Does it mean the fiscal year start and end date must be same?
3. What is the impact of the warning message?
Thanks
Palani

Having same fiscal year variant is one of the requirements for different company codes to be under one controlling area.
The FYV for the company codes and the controlling area can have a different number of special periods. The number of posting periods must be the same.
Impact of warning message: You cannot create one controlling area for both company codes (1:n assignment).
If you like, you can create one controlling area for one compnay code with FYV A1 and another controlling area for another company code with FYV B1.
PS: Please reward the points if you find the answer as useful and rewarding points is a way of saying thanks.

Fiscal Year Variant for non calendar year

Dear Experts,
The fiscal year for my client is as follows:
     Start Date     -
     End Date
Month 1     -
     21-Mar     -
     20-Apr
Month 2     -
     21-Apr     -
     21-May
Month 3     -
     22-May     -
     21-Jun
Month 4     -
     22-Jun     -
     22-Jul
Month 5     -
     23-Jul     -
     22-Aug
Month 6     -
     23-Aug     -
     22-Sep
Month 7     -
     23-Sep     -
     22-Oct
Month 8     -
     23-Oct     -
     21-Nov
Month 9     -
     22-Nov     -
     21-Dec
Month 10     -
     22-Dec     -
     20-Jan
Month 11     -
     21-Jan     -
     19-Feb
Month 12     -
     20-Feb     -
     20-Mar
Accordingly i have created a fiscal year variant with following details:
Month     -
     Date     -
     Period     -
     Year Shift
4     -
     20     -
     1     -
     0
5     -
     21     -
     2     -
     0
6     -
     21     -
     3     -
     0
7     -
     22     -
     4     -
     0
8     -
     22     -
     5     -
     0
9     -
     22     -
     6     -
     0
10     -
     22     -
     7     -
     0
11     -
     21     -
     8     -
     0
12     -
     21     -
     9     -
     0
1     -
     31     -
     10     -
     -1
1     -
     20     -
     10     -
     -1
2     -
     21     -
     11     -
     -1
3     -
     20     -
     12     -
     -1
But when i try to save the above periods for the variant it gives an error as
"Financial year variant periods T1 incomplete (31.12 missing)".
Can you help me know where am I going wrong in this?
Regards
Amar
Edited by: Z_Amarendra on Dec 7, 2009 9:52 AM

Dear Experts,
Solved the problem myself. Thank you
Regards
Amar

Fiscal Year Variants

Hi All
Please could someone briefly explain how I manage Fiscal Year Variants in a BI system?
I ran trans OB29 to see what has been set-up in the ECC. I ran the option 'Transfer Global Settings' to transfer the Fiscal Year Variants to the BI system, and verified that they are present.
I have installed the DSO 0FI_GL_10 and the necessary data transfer objects. In the PSA the data all has Fiscal Year Variant 'K4', but when I transfer the data to the DSO and activate I get an error: "No Fiscal Year Variant specified". If I look in the DSO table /BI0/AFIGL_O1040 I can see there there is no entry in field FISCVARNT.
I tried manually updating the FISCVARNT field (just to test) and activate the DSO and I see an error updating the SIDs on the Fiscal Year field as it seems to append the Fiscal Year Variant to the Fiscal Year field (e.g. K41994123). Where is it doing that?
Any help greatly appreciated?
Thanks
Al.

Thanks Simon
Now I have looked - I can see the compounding in the 0FISCPER InfoObject. (Points Awarded.)
When I look into the contents of 0FISCPER InfoObject, the PERIV field is the Fiscal Year Variant and does not include any 'K4' entries (the value being passed from ECC). How do I update this table? My upderstanding is that I cannot set transformations to update it, is that right?
Thanks
Al.

Error :No fiscal year variant specified

hi all,
I have created a generic datacource using a Ztable.Have mapped these fields to the infosource of bw and loaded the data.
when loading i got an error
Record 1 :No fiscal year variant specified
see i have fiscal year in my table but no fiscal year variant.
when i dropped the fiscal year in time dimension ,the fiscal year variant automatically added with it in the time dimen.
Is this fiscal year varieat is needed ,if so how can i map this as it is not there in the datasource(ztable).
Plz giv me solution for this .its urgent.points will be rewarded.
Thanks
Satish.

hi raghvendra,
thanx for the quick reply.
i have tried as u said,but the its sayisg A is invalid as an error.
Here are the values in the f4 help of the fiscal year variant.....
Not assigned
24 Half periods
C1 1st period (calendar year)
K0 Calendar year, 0 spec. period
K1 Calendar year, 1 spec. period
K2 Calendar year, 2 spec. periods
K3 Calendar year, 3 spec. periods
K4 Calendar year, 4 spec. periods
R1 Shortened fisc.year Jan-Sep'94
V3 Apr.- March, 4 special periods
V6 July - June, 4 special periods
V9 Oct.- Sept., 4 special periods
WK Calendar weeks
i have selected WK but its throwing an error...
Record 1 :Fiscal year variant WK is not maintained for calendar year 2007
so which value should be selected from the above list.

Multiple Fiscal year variant

For global consolidaiton I have all company with same fiscal year variant.
For 2 regional consolidation I have different kind of fiscal year variant.
Do we handle different fiscal year variant thru different consolidation area or different data basis.
What is better approach.

Colin,
Could you please explain more how this is accomplished?
I have not seen this before.
Thanks.

CK40N with V3 fiscal year variant

Hello dear SAP experts,
Please help. We are on ECC 6.0 and the fiscal year variant is V3. I have tried releasing the std cost estimates on several periods but its saying the "release is too early". The MM period is already 04/2009 because I've already tested several periods but to no avail. The FI period is open and there are no locked periods in OKP1.
Thanks and regards,
Thess

Hi Thess,
"Release is too early" means, the "Costing Date From" which you have not selected is not reached yet. It has nothing to do with Fiscyal Year Variant, MM/FI/CO period locks.
Let us say, You are doing the Costing run on 15th of March and you have selected the "Costing Date From" as 15th of March only. In this case, you will be able to Save, Mark and Release the Cost Estimate immediately because the date on which you are running the Cost Estimate and the date from the released Std Cost to be effecive ("Costing Date From") are same.
In the same example, your are running the Cost Estimate on 15th of March, where as the "Costing Date From" is given as 1st of April, then, you will be able to Run/Save/Mark the Standard Price on 15th of March itself and the Price will be appearing as "Future Std Price" in Material Master, but, you will be able to Release it only on 1st of April (then the Std Price will move from "Future Std Price" to "Current Price" in Material Master).
I hope it is clear...Pls revert back for further explanation...
Srikanth Munnaluri

Fiscal year variant Z1 is not maintained for calendar year 9006

Hello Experts ,
I am tring to load data into Cube from ECC datasource. The load till PSA is fine but during DTP load I am getting the followig error .
"Fiscal year variant Z1 is not maintained for calendar year 2009006"
I tried to reload "Global settings from System system " But did't worked . Just to let u know our client is retail client and using 4-4-5 fiscal year .
Pls help what should I do.
I saw 0FISCPER AND 0FISCYER Infoobjects in BI but could not find thing .
Your Help will be Highly Appreciated .
Thanks
Pankaj

You have a few choices on how to handle this:
1. Have a functional person update the Fiscal Year Variant in your ECC source system to include periods for Fiscal Year 9006. Then update Global Settings.
2. Update the Fiscal Year Variant in your BW environment, in the IMG (SPRO > SAP Customizing Implementation Guide > SAP NetWeaver > Business Intelligence > General BI Settings > Maintain fiscal year variant).
3. Filter out the data for that Fiscal Year in your DTP.
4. Modify the Transfer Rules / Transformation to change this date to an acceptable Fiscal Year/Period.
These are in order of preference (best practice) on how to handle this.

Fiscal year variants in co.code have inconsistent start date.Msg no AC531

Similar Messages

Maybe you are looking for