Ledger 0 has fiscal year variant instead of V3 - Message - GI174

Hi all,
i am geting below message when i am doing KP06 for cost center planning
Ledger 0 has fiscal year variant instead of V3
Message no. GI174
Diagnosis
When transferring planning data, the receiver ledgers must have the same fiscal year variant as the sender system, since all planned periods are transferred and not just one period with a posting date. Therefore, the period cannot be converted.
Procedure
Compare the fiscal year variant of the sender system with the FI-SL fiscal year variant.
You can access this in FI-SL Customizing by choosing Basic Settings Master Data -> Ledger (select the ledger specified in this message) -> Assign Comp.Cd/Comp. -> After selecting the company code, the system displays the assigned fiscal year variant.
Kindly do the needful.
Regards,
TDK

Hi,
The message means you need to change fiscal year variant of ledger 0 to V3. I guess your fiscal year variant of controlling area is V3. Both of them should have same fiscal year variant. So change it may be solve the problem.

Similar Messages

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.

Fiscal year variant Incorrect

Hi All,
Our period closed on 25th december and we are in the period one of 2011. When we are trying to run the cycle count using MICN for the plant we are getting error saying:
*Fiscal year variant W1 is incorrect
Message no. F5234
Diagnosis
When determining the posting period, a period was found that is not in the permitted area 1 - 16.
Procedure
Correct the fiscal year variant.
We are not sure as what the issue is here....can someone please guide us through?
Note: W1 is the accounting period.
Thanks.

Try
Tcode - OB29 for Maintaining FIscal yr Variant.
In Tcode OB37 - Assign Company code to the variant
OB52 for open and close posting period

Fiscal Year Variant Error

Hi All
we are getting the below error when trying to post the transaction MICN :
Fiscal year variant T2 is incorrect
Message no. F5234
However, i have checked OB29, OMSY, OB37 & OB52 - all are correctly set up...
can anyone guide me as to how I can correct this error
Thank you
Rukshana

Hi Christian
Thank you for the response...
yes I have checked all of them and none of them are giving me a solution.
SAP OSS notes too are not much of a help....
Thats why I am trying to pick someone's brain to see if they have encountered a similiar error and what they did to rectify it..
Thanks again
Rukshana

Error in Data loading - The source of the fiscal year variant has changed

Hi All,
Need your kind suggestions to solve the issue.
I am trying gto load data from one cube to another. the base cube has data with 0CALDAY. in the next cube I am trying to derive 0FISCPER from 0CALDAY. But while loading I am getting this error.
The source of the fiscal year variant has changed
Could someone guide me.
Thanks in advance.

Hi Saugata,
nice to exchange views after a long time.
well, if u are sending data to the target cube which contains data for the separate financial entity of different finacial parameters like fiscal varient then u need to update global transfer settings, and then load data.
parhaps u also need to check the value of the Fiscal year varient to the target cube.
hope this helps.

Data load : The source of the fiscal year variant has changed

I am loading some sales data from BW to APO and I keep getting this message .
The source of the fiscal year variant has changed
I am not sure how to resolve it because the help also does not give much info on the solution.
Thanks

Hi
it may be becoz
In R3 the Fiscal year variat has been changed .. Check the Fiscal year variant for ur precious data..and talk to ur functional team abt variant...
Normally for a comapny Fiscal year variant will be unique. I will change when there are some huge changes happend Merger,acqucsition etc..
hope it helps
regards
AK

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

Use of Different Fiscal Year Variant-Statistical Depreciation Area Postings

An existing Company Code in SAP is going to have Fixed Assets implemented. This Company Code is setup just like the others in our SAP instance: Same Chart of Accounts, Same Fiscal Year Variant, Fixed Asset procedures, etc. For purposes of this question our company's Fiscal Year is from August 1st to July 31st. In addition, this Company Code will post Fixed Assets just like the other SAP enabled Company Codes into Book Depreciation Area 01. The company I work with is on ECC 6 but we use the Classic Ledger for Financials, and the Special Ledger is posted to but not really utilized.
For the Country Specific/Tax Reporting purposes within Fixed Asset Accounting we have created a Statistical Depreciation Area 03 (I will call it Tax) with its own Life and Depreciation Key assignments with a setting of 0 in OADB-No Posting in GL for this Fixed Asset go-live, so I think we are set there. The tricky part comes in the reporting. The country in question requires information to be generated on a Calendar Year basis, which is obviously different than the Fiscal Year outlined above. To my knowledge we would have to assign Tax Depreciation Area 03 to the Calendar Fiscal Year Variant: Financial Accounting>>Asset Accounting>>Valuation>>Fiscal Year>>Fiscal Year Variants>>Specify Other Versions on Depreciation Area Level.
The other piece of this is to get the Fixed Asset Reporting for Tax Depreciation Area 03 to work on a Calendar Year basis for the Company Code in question. When I did some research I stumbled upon the link below. In summary it says that you have to manipulate the standard Fixed Assets reports in Excel for Asset Acquisitions and Depreciation, and setup a new Retirement routine/transaction for posting into the Special Depreciation Area.
http://help.sap.com/saphelp_46c/helpdata/en/05/bc0bf3d8f811d1953e0000e82debf7/content.htm
My questions are:
1) Besides assigning a different Fiscal Year Variant for Tax Depreciation Area 03, is there anything else I need to worry about on the setup end?
2) Is the article I posted accurate when it comes to how the reporting works and the need for setting up a Calendar Year specific Asset Retirement Routine? If so, what are the configuration steps for setting up a Calendar Year specific Asset Retirement Routine?
3) Is there anything else that I need to consider for enabling Fixed Assets at an existing Company Code with different Reporting requirements for Book/Tax purposes?
Thanks in advance for all responses. I am willing to answer any other questions on this subject if needed.
Roman

Hello Rio. In our scenario, we still had to load assets in the legal entity with this issue. When we loaded the fixed asset data into SAP we did with data accurate as of December 31, 2011; which for book purposes is 5 months into our company's fiscal year, and for tax purposes is the end of the 2011 calendar year. The calendarized reporting for the tax depreciation will need to be pieced together manually using the SAP recommended methodology of combining report values, which I have pasted below.
Since this is the only SAP-enabled entity that has this scenario right now we are in wait and see mode to see if this sufficient. In the end the SAP path for Dual Calendar was too much of a risk.
I hope this helps.
Roman
Asset Acquisitions
Run the acquisitions list. Report date: 7/31/2012. Posting Date: 1/1/2012 to 7/31/2012. Export the report to MS Excel.
Run the acquisitions list. Report date: 7/31/2013. Posting Date: 8/1/2012 to 12/31/2012. Export the report to MS Excel.
Add the values of both reports together, using MS Excel.
Asset Retirements
Run the retirements list. Report date: 7/31/2012. Posting Date: 1/1/2012 to 7/31/2012. Export the report to MS Excel.
Run the retirements list. Report date: 7/31/2013. Posting Date: 8/1/2012 to 12/31/2012. Export the report to MS Excel.
Add the values of both reports together, using MS Excel.
Depreciation
Run the depreciation list. Report date: 7/31/2012. Export the report to MS Excel.
Run the depreciation list. Report date: 12/31/2011. Export the report to MS Excel.
Run the depreciation list. Report date: 12/31/2012. Export the report to MS Excel.
Using MS Excel functions, subtract the second report from the first, and then add the third report (I - II + III).

"No Fiscal Year Variant assinged to consolidation unit" error for 3EC_CS_1A

Hi,
I'm getting following extraction error using RSA3 for datasource 3EC_CS_1A in R3 (4.7) system. Could someone shed some ideas on how to fix it.
No fiscal year variant assigned to consolidation unit 0000000000000000XX.
same error is coming for all consolidation units.
I checked ECMCT table and it has records in it.
I went to "Consolidation unit change" using CX1N and found out that above consolidation unit has our customer defined "standard fiscal year variant assigned" for the corresponding ledger listed in ECMCT.
What else might be missing & how to fix it. same error in both DEV & QAS. Appreciate any inputs
Hari Immadi
http://immadi.com
SEM BW Analyst

thanks for your post.
I checked T009 and see that fiscal year variants are maintained. K4 as well as "customer defined standard fiscal year variant". what else might be missing.
Hari Immadi
http://immadi.com
SEM BW Analyst

Company codes with different fiscal year variants in a controlling area

Hi all,
When I try to assign a company code with different fiscal year variant than controlling area I get error. It is ok so far.
However, after assigning company with same fsv to controlling area the system lets me to change company code's fsv in company code global settings and I can even save it.
So I wonder how it would be possible ? Why do I get just a warning instead of an error and save ?
Thanks and regards.
M.Yusuf Dogan

Hi Bulut,
There are 12 normal and 3 special periods in the fsv of the company code which i'm trying to assign. However, controlling area's fsv has 12 normal and 4 special periods. I get an error message "KT297".
Actually, my point is that if the company code's fsv is same with co's I can assign but the system lets me change cc's fsv after assignment.
M. Yusuf Dogan

Can you have more than one Fiscal Year Variant

I know each Company Code can have only one Fiscal Year variant. But what if you have multiple ocmpany codes and one company code is in a country that has to use the calendar year as the fiscal year while the second company has a fiscal year that runs from April through March? Can this exist and you can still produce Consolidated Financial Statements?

You can't assign more than one Fiscal Year Variant to a Company Code up to Version 4.7
You can however create a Special Purpose Ledger and have a different
fiscal year variant assigned to it and you can assign the company code
to that ledger.

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...

Turkey: year end close RFSUMB00 / fiscal year variant

Hello guys,
I am wondering if anyone of you have had this requirement before.
Running RFSUMB00 on a Turkish company code will blow away the balances from all G/L accounts so that each individual account has a balance of 0.
Questions:
1. How do you manage revenue accounts (cost element categories 11 and 12). A pure cost centre is not enough as CO account assignment. You can switch off error message KI 166 (so that no COPA documents are then created), but is this really wanted?
2. If each individual account has a balance of 0 at year end, how to create a B/S and P/L for that year? Especially, for previous years? The only thing that comes to my mind is using special periods (13 to 16), but.... -->
3. ...in our system, the FI fiscal year variant is not K4, but a custom variant. The fiscal year (of the group) does not end on 31st December. I have a small FI-SL application running in the background (with K4 assigned there), and I could change the FI-SL period to 13 during the document transfer easily, but I ask myself why I do not post all of these funny closing documents directly in FI-SL then? This would save me from the usage of dummy assets/customers/vendors and the continous changes made to the "automatic postings only" flag (SKB1-XINTB).
Turkey experts, any hints welcome. What are your best practices?
Thank you,
Csaba

Yes frank,
GL closing should be carried only after all the sub ledgers are closed
for asset closing
you should open the new fiscal year first (AJRW) and then close the existing fiscal year. (AJAB)
otherwise FI-AA and Fi-GL may not reconcile (use tcode ABST2 to check this)
Regards
Sach!n
Edited by: Sachin Bhutani on Jan 30, 2010 3:32 AM

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

Fiscal year variant is not maintained for calendar year 2009

Hi,
After upgrade to BI 7.0 we are getting error: "Fiscal year variant & is not maintained for calendar year 2009" while opening a query through Bex Analyzer.
Basically it is happening like when we open a particular query, the Variable selection screen comes up, then on clicking the exection button (after selection) it shows SYSTEM_FAILURE exception & clicking the details button, shows the message ""Fiscal year variant is not maintained for calendar year 2009"
Please provide some information/resolution to this.
Thanks,
Shantanu.

HI,
Please ensure that you have defined your fiscal year variant in OB29
correctly. It is necessary that:
1. the previous year has been maintained,
2. an entry for Dec 31 exists in each fiscal year,
3. the following fiscal year has been maintained.
Hope this helps.
Regards,
Nitin

Ledger 0 has fiscal year variant instead of V3 - Message - GI174

Similar Messages

Maybe you are looking for