Fiscal Year Variant change

Hello,
We are being asked to switch our fiscal year variant from 445 to calendar month based beginning 1/1/2010. I am curious as to how to approach this change from the BW perspective.
I first did a quick look at the system to see how and where fiscal year variant is used.
What i found is that:
1. Fiscal year variant is used in our cubes as part of the transaction data
2. Almost all the queries have the FYV as part of the query definition. (won't be able to restrict to just 1 FYV since it will rule out many records since FYV is part of transaction data in our cubes)
3. Many queries compare current Fiscal periods to prior fiscal periods and and ranges too. This is enabled by using variable exits for 0FISCPER etc.
4. There are some Restricted Key Figures that have the FYV as part of thier definition.
5. Many DSO objects have the FYV as a key field.
What do you recommend from your own experience with regards to how to handle this change. I am curious what the impacts will be and what I should be prepared for. I am guessing that data in our DSO's will pile up since starting 1/1/2010 every record will have a new FYV (remember FYV is a key field), also I am curious how time based variable exits will work, since I think they depend to some extent on a single FYV.
Any advice or recommendations on how to approach this change is appreciated. Also what decisions have to be made if any...
Thanks!
Nick
Edited by: Nick Bertz on Dec 3, 2009 3:17 PM

Hello,
Okay here is one thing that i have run across that i do not understand. I am using Offsets in a query. Everything works fine with regards to these offsets, except for when i introduce 2 Fiscal Year Variants.
Once there are 2 fiscal year variants, the offsets are completely ignored.
Does anyone have an explanation why variable offsets would no longer work when there are 2 fiscal year variants on the same report?
When i launch this query in the web browser from Analyzer I get the following error message:
Diagnosis
Variable ZS_FPER2 contains a fiscal year period which is to be moved by 10 periods. Before this can occur, the fiscal year variant must first be specified clearly so that the number of periods in the fiscal year can be determined.
System Response
Procedure
If the fiscal year variant exists as a variable, enter a value for this variable. If the fiscal year variant is not specified in the query, you must include it in the query.
You can specify the fiscal year variant either globally or for the InfoProvider specifically.
Procedure for System Administration
Notification Number BRAIN 618
Thanks,
Nick
Edited by: Nick Bertz on Dec 29, 2009 4:15 PM

Similar Messages

Funds Management and Fiscal Year Variant Change

Hello !
We are configuring a new fiscal year variant.
Currently, the system is on a CALENDAR YEAR FY variant and we are doing the following:
1. creating a shortened FY of Jan 2009 - Mar 2009
2. new fiscal year from April 2009 - Mar 2010
We are trying to change the FY variant for Funds Management via OF15 but receive the error FI674.
FI674:
You must not change the fiscal year variant in Cash Budget Management or Funds Management for FM area FM01 if actual data already exists for FM area FM01, or if one or more of the company codes assigned to FM area FM01 is active.
We have found oss note 719597 which details how to change the FY variant for Cash Budget Mgmt, but it does not apply to Funds management.
I could find no other supporting documentation.
Can anyone guide us as to how to deal with this issue?
Thank=you !

Hello Patti,
The point is that it is not possible to change fiscal year variant if actual values exists.
You are trying to do a change in January. You probably have some postings in 2009 already.
In the area of PSM-FM there is no note like 719597 of TR-CB.
Only if no actual values exist, this customizing change would be possible and reasonable.
If you are doing this setting in your customizing client, you can delete the postings (please DO NOT do it if you are in production) that exist in 2009 and try again.
SAP do not recommend to change a Fiscal Year Variant that has already been assigned to a company code and has already some postings. This may create database inconsistencies.
You can create another Fiscal Year Variant with the information that you want to be customize, and this variant you will be able to assign to a company code. Before you assign this new variant to a company
code please be sure that none of the information that you already posted in this company code will be affected, this information you may review it with your consultant on-site.
Also please review/apply note 173636, 202687, 10945, 193713, 123026, 210861 which may happen in your system.
The fiscal period is related to the posting date via the fiscal year variant. E.g.: I you do a posting on 5.5.2009 it will be posted e.g. in period 5 for fiscal year variant 'A'. This period is not only used in the document header table (BKPF,VBRK,MKPF ...) but also in several balance table (GLT0, KNC1 ...) not only in FI but also in SD, MM, CO .... If in the new fiscal year variant 'B' this posting date is related to another period e.g. 7 the relation between documents and Periods and balances will be destroyed.
The problem will be enhanced if the posting-date would be related to diffrent fiscal years.
In addition several reports in AP/AR and GL reread period-depend data by selecting the posting-date regardless of the period in the document because it's not normal practise to change the fiscal year variant of a company code.
Some of the involved issues are:
- FM actuals and commitments may need to be reconstructed if their period- (or even fiscal year-) assignments is changed.
- FM actuals/commitments can not be reconstructed if fiscal year change activities have already been performed (commitment carry forward, FMJ1, FMJ2).
- Budgeting data and assigned values may principally be concerned as well, especially if you are working with period values in budgeting.
The change of fiscal year variant has several implications and should be analyzed very carefully.
Please check note below for more information:
Note 672255 Shortened fiscal year / changing fiscal periods
I hope it helps you and good luck
Best Regards,
Vanessa.

Change in Fiscal Year Variant Causes Cube to become inactive

In Maintain Fiscal Year variant, we attempted to change the Fiscal Periods to reflect the 2007 Fiscal Calendar. When we saved it, it caused the Update Rules for our Infocube to become inactive. I need to know how to reactivate them or what to do. The Error message is saying that there is no routine created for the object. How do I recreate the routine and reactive the Update Rules?
We are using BW 3.1

Hi David,
Whenever you change a MetaData Object, BW will automatically deactivate everything that relies on that object to prevent system instability. In this case, your Update Rules and InfoCube (and MultiProviders if you use them) were deactivated. In most cases, simply reactivating them will correct the problem.
Judging from your post, this isn't the case. What did you do to the InfoObject that required reactivation of the InfoObject? You may want to check inside the Update Rules to see if BW removed the connection that you had before. I've seen that happen as well.
Adam

Change future periods for Fiscal year variant-OB29

Hi experts,
We are using 4-4-5 rule, Fiscal year variant is M1, Future Periods for FY variant M1 is not maintained correctly. Our year end is on 6/25/2011 but in our variant M1 it is defined as 7/2/2011 and periods following that are defined incorrectly.
Company - US (4-4-5 rule)
FY variant - M1
Period - P12/2011 and following periods are not defined correctly
1.     There are risks involved if you change the fiscal year in Live SAP system. What is the risks for changing future periods - 2 months from now.
2.     Posting are not carried out for the periods we are changing. We need to check plan data if any
3.     Impact on other modules, organization structure, master data, transaction data
4.     How intense the testing needs to be.
Any help will be appreciated and point will be assigned.
Thanks
Monica

Hello,
If you change the Fiscal year period in the live system the following problems may come as per my understanding.
For Costing Module Planning would have already been carried our at the start of the year,
similarly for CS, PP and PS modules if they are implemented in your company the planning data will be effected.
If there is any Budjet posted even you have to consider how to change the budget and reaccolation
Best Regards,
Ravi

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

APO-DP : Change in Fiscal Year Variant for the year 2008

As per earlier Fiscal Year variant configuration, the data has been forecasted in APO system till the end of Year 2008. But recently the fiscal year variant configuration modified in R/3 which has been impacting APO-DP storage buckets which are not matching with that of earlier fiscal year variant. So, there is a mismatch in the storage bucket profile where in the data already stored in Weekly, Monthly and Posting Period based on the earlier Fiscal year 2008 configuration.
Now the system is not allowing to do any Interactive Planning.
The business would like to use the latest fiscal calendar and also not ready to loose the forecasted data for the year 2008. So, we are not in a position to deactivate and reactivation of Planning Area and also we are not using back-up infocubes functionality.
Please update me if anybody experienced this type of situation or know the solution.

I think your suggestion should work but it takes more resource time and need more database size.
I am thinking to retain some important forecast keyfigures data in the following workaround method;
1) Now the Planning Area Initialized for 2yrs historical + 1Yr forecast horizon
2) Run first set of new macros to copy from year (say 2008) to year (say 2006)
3) Re-initialize the Planning Area (Jan'2006 to Dec'2007)
4) Re-build the New Fiscal Calendar from R/3
5) Re-initialize the Planning Area for history and forecast horizon (ex: from Jan'2006 to Jan'2009)
6) Run second set of new macros to copy back ( ex: from 2006 to Year 2008) and wipeout the duplicate records in 2006
7) The above macros can be utilized to run every year end when ever the new fiscal calendar introduced
Suggestions are welcome

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

Interpretation of Fiscal year variant

Hello Experts,
Ok, using the Tcode OB29, I could see the fiscal year variant K4, K6, K7 as follows:
Variant----Yr Dependent--Calendar Yr--Posting Periods----Special Per.
K4----
Unchecked----
Checked----
4----
2
K6----
checked----
Unchecked-----4--
2
K7----
Unchecked----
Unchecked-----4--
2
In went into the details of the Change View of K6 and K7 and it shows:
Month----
Day----
Period----
Year Shift
1----
31----
7----
0
2----
28----
8----
0
3----
31----
9----
0
4----
30----
10----
0
5----
31----
11----
0
6----
30----
12----
0
7----
31----
1----
+1
8----
31----
2----
+1
9----
30----
3----
+1
10----
31----
4----
+1
11----
30----
5----
+1
12----
31----
6----
+1
1. Can you help me interpret the second table and how it relates to the K6 row in the first table?
2. In particular, I will appreciate some clarification on the Year shift and in the column period, why it started from 7; and why after 12, it switched to 1.
4. Can you give a reason why in some cases K6 will be used while in others K7 or K4 will be used.
3. Also, some help Ive gotten so far were suggesting that to modify the variant I go to:
AC Financials ® FI Financial Accounting  General Ledger Accounting ® FI - Closing and Reporting ® Fiscal Year.
I could not find this instruction under BW. Was it some R3 instruction of BW?

Hi,
I believe the "year shift" column is meant for the non-calendar fiscal year.
eg in a Calender year
Jan Feb Mar Apr May Jun
Fiscal year definition
Period
10   11   12   1    2    3
Year Displacement
-1   -1   -1   0    0    0
It is just telling the system that when it is eg 21 Jan 2006, the fiscal year to be captured will be FY 2005. When it turns 01 Apr 2006, the FY will be 2006.
In your eg, it is following the logic that when it is 01 June 2006 the FY will be 2006. But when it turns 01 July 2006 the FY will be captured as 2007.
By the way, the special periods are meant for capturing adjustment.
For more information on the year shift, please see
http://help.sap.com/saphelp_46c/helpdata/en/96/8b2fc843ce11d189ee0000e81ddfac/content.htm
In BW, these are considered the basic settings, alongside with the currency definition. Go into SBIW in BW to see the basic settings for currencies and fiscal variant defined. Usually when the BW system is set up, these 2 settings will be read into the system as part of the initial configuration.
Cheers,
Gim

While activation of DSO error SID genarati No fiscal year variant specified

Hi all,
While activationg the DSO i am getting error called SIDgenaration " No fiscal year variant specified"
I have checked the PSA fiscal year variant is avilable..
How to solve this error please somebody let me know ASAP
Regards
Kiran

Hi.......
For some particular value of Fiscal variant it is failing............ in ODS activation.......in the log it will not show that value...........but if load fails due to SID issue then log generally shows the particular value.......
You load the master data for fiscal year varinat .........then activate it.......using program.......RSDDS_AGGREGATES_MAINTAIN..........then tepeat the ODS activation.......this is to run attribute change run.............you can also do it from RSA1........
You can also change the said settings in the above post..........but it should'nt done in PROD........
Hope this helps.....
Regards,
Debjani.........

What is the difference between Fiscal year variant, Fiscal year and Calyear

hi,,
What is the difference between
1. Fiscal Year Variant (0FISCVARNT)
2. Fiscal Year (0FISCYEAR)
3. Calendar Year (0CALYEAR)
In what scenarios they should be used. If we are getting 0FISCVARNT data from ODS. Can we change into other in cube at update rules level or some other level?
How can we get factory calendar????
Message was edited by:
Avneet M

Hi Gurus
I was going through this thread and came up some more questions in my mind.
1. Do we need to set Fiscal Year, Fiscal Varient settings once for all in BW ? ( The path is given in one of the thread above ) need to know if this is one time setting / rebuilding the tables. what will happen when we select and execute factory calender and Fiscal Varient and Rebuild tables in transfer global setting ? Is this one time we have to do for whole BW system?
2. when we go to SCAL t-code what we need to do and what it do in the system ? I know its for Factory calender but just want to know what it does. It it also for one time during BW build phase ?
3. How can we link Factory calender and Fiscal year? IS it thro Fiscal varient ?
Pl help me to clear this doubt,thanks in advance.

Fiscal Year Variance Change affected AA Balance and Recalculation of Values

Hi Experts,
I have a scenario where we change the Fiscal Year Variance on certain Company Codes. The Fiscal Year Changes were on Period 12 from Nov 26th to Dec 31st (last Fiscal Year Var was until Dec 25th), and Period 1 of next Year will already start at 1st of Jan (Last Fiscal Year Variance was from Dec 26th) until 26th of Jan.
We encountered a discrepancy on some reports especially on the FI-AA Balance Report, where as some posted entries for the Assets were not included.
Then I investigated. I found out that the Recalcualtion of Values is always based on the entries of table ANEP where the fiscal period 2011 did not include some postings done on th 30th of Dec because of fiscal year variance change.
In the Asset Values of the asset, it shows no discrepancy there although the info-dialogue box is appearing to recalculate the values of the asset. They already posted in Period 11 of this year after the changed fiscal year variance without recalculating and currently the planned values are different. The users are okay with the posted depreciation run since the asset balance per year is still correct. But if we recalculate the posted entries for asset acquisition on Dec 30th, the acq amount/asset balance will already be incorrect.
My Current solution is to enhance the function module FIRST_DAY_IN_PERIOD_GET to show that if the values of Fiscal Year = 2011 and Period = 1, then it will get the date 26th of December 2010. I know that this Function Module is widely used for all modules but since we already changed Fiscal Variances maybe this will also correct some reports or functions that includes Fiscal Starting Dates.
Or are there any solution for this scenario? Is this solution advisable?
Edited by: Cecilio Cruz II on Dec 6, 2011 8:32 AM

Have you done the impact analysis of changing the fiscal year variant directly? I would suggest you may need to raise an OSS note with SAP. The change must have affected different areas.

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.

F-58 - GMMASTERDATA035, Invalid Fiscal Year Variant

Greetings,
When creating a posting using F-58 in our Venezuela client, we get this error message, GMMASTERDATA035, Invalid Fiscal Year Variant. I have looked under message control in config. for both GM and GMCUSTOM and message 035 does not exist. I want to change the message so it no longer appears.
Any experience with this would be great.
Thanks,
Jim

Check applicability of note 793116 for a program error. When you extend an existing grant validty period or insert a new budget validity period, the FY is not updated. In some cases, this makes budgeting impossible.

Fiscal Year Variant change

Similar Messages

Maybe you are looking for