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

Similar Messages

Error: "posting period is not defined for fiscal year variant" in FBICS3

Hi,
I got error "posting period is not defined for fiscal year variant" when I execute t code FBICS3.
I checked in OB29 & t code FBIC010 & noted that the fiscal year variant had ben maintained.
Please advice.

HI,
It was noted that the mentioned t code had been maintain but below mentioned error appear:
Posting period is not defined for fiscal year variant
Message no. GU506
Diagnosis
You have tried to determine a posting date in fiscal year variant for period , fiscal year , but this period is not defined for the variant.
Procedure
You maintain fiscal year variants in table T009.
It was referring to t code OB29. I have checked the detail, in OB29 also details maintain.
Please advice why the error still prompt.

Error saying 'Posting period 000 is not defined for fiscal year variant K4'

Hi All,
   When I try to add a new entry in the transaction OB52, I get an error message saying 'Posting period 000 is not defined for fiscal year variant K4'. The entry that I add is,
Variant           : 0001
Account Type: +
From Period    : 1
Year               : 1995
To Period        : 12
Year               : 2010
From Period2 : 13
Year               : 2000
To period2      : 16
Year               : 2010
Please let me know what customising needs to be done to solve this issue.
Thanks a ton.
Best Regards,
Jeff

Hi,
Hava you checked in OB52 screen, by default 0001 posting period variant will be there for +, A, D, K, S account types.
If it is already existed in your OB52 screen, you won't create one more record with the same name. You have to edit the existing 0001 posting period with new values.
Thanks
Chandra

Error in the source system for fiscal year variant K4 Period 00

We are experiencing the following issue when loading data from module Flexible real estate RE-FX CASHFLOW CUBE OREFX_C06 Error in source system Fiscal year variant K4 is not defined for the period 00.

Hi,
You need to check in your source whether you have maintained Fiscal Yr Variant or not? Talk to you Functional person before you do the BI Extraction.
In Table T009B
You can check Fields
MANDAT - client
PERIV - Fiscal Year Variant
BDATJ - Posting date YYYY
BUMON - Posting date calendar month
Check Table T009B and see if you fiscal variant is maintained for all periods of Years (as per error its not). maintain the same in Source system and transfer Global settings in BW to copy the same into BW system.
@AK

Fiscal Year Variant (OB29)

I am trying to copy over a fiscal year variant's periods from one year, to the next. However, I am running into the error "Financial year variant periods MI are not in increasing order". This exact setup of periods is saved in prior years, but it will not let me save it in the current year. Any suggestions? (T-Code OB29)
Month     Day     Period     Year Shift
1             3          3             0
1             31        4             0
2             28        5             0
4             4          6             0
5             2          7             0
5             30        8             0
7             4          9             0
8             1          10           0
8             29        11           0
9             30        12           0
10           1          1             -1
11           29        2             -1
12           31        3             -1

Try pasting the below data
If the fiscal is Jan - Dec ie calendar year, just create the fincal year variant and select the option Calendar year in the third column.
If the fisacl year is Apr - March
Month     Days     Period     Year Shift
4     30     1     0
5     31     2     0
6     30     3     0
7     31     4     0
8     31     5     0
9     30     6     0
10     31     7     0
11     30     8     0
12     31     9     0
01     31     10     -1
02     28     11     -1
03     31     12     -1
If the fiscal is for calendar year, just create the fincal year varient and select the option Calendar year in the third column.
It is always better to copy standard (V3 for apr-march or K4 for Jan-Dec)
Edited by: JithuMat on Dec 1, 2011 2:20 PM

Delta Fail - Fiscal year variant FP is not maintained for fiscal year 2011

Afternoon all,
One of our overnight deltas failed with the error msg
"Fiscal year variant FP is not maintained for calendar year 2011"
I've since in SPRO under Maintain fiscal year variant created the correct entry for 2011 which mirrors the R3 source system. However when i run a repeat delta the same error occurs.
Thinking i may have missed a setting i have since transferred the global settings for fiscal year variants from the source system in RSA1 and again ran a repeat delta...same error.
On the advice from other threads in the forums i've checked in OB29 and it appears fine, and also checked tables T009 and T009b again without success.
Does anyone know of anything else i can try?

hi,
hope run the delta after the attribute change run could solve the issue.
hope u may have the below posts already if not chk out
Fiscal variant maintence
Maintaining Fiscal Variant Between R3 and BW
Fiscal variant not maintained for Calender year
Ramesh

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.

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.

DETAILED FISCAL YEAR VARIANT NOT PROCESSED error for 2lis_03_UM DS

Hi Guru's,
Note: Im trying to implement the SNAPSHOT process for the Inventory load.
Im loading data from 2lis_03_UM to cube 0IC_C03 through an infosource generated by me (7.0 version infosource).
The data is loaded successfully upto PSA.
While loading data through DTP i'm getting this error:
"DETAILED FISCAL YEAR VARIANT NOT PROCESSED".
Even i didn't mapped any Fiscal Year variant or there is no field for fiscal year variant in the cube.
Did anyone faced this type of error.
Please guide me.

dear shiv,
the same error in same same scenario. can you please tell me the solution for this error. ef you dont mine can you please give me a call or miss call for that error. so i can resolve on phone.
my no.9769497378
thanks
Anil

Sugestion required for Fiscal Year scenario

Hi Gurus,
I need your suggestion for the below scenario
One of our client going to change the Fiscal period from (Jan - dec ) to (Sep - Oct). We have nearly 5 years of records as on date based on the (Jan-Dec) fiscal period.
Requirement: If new fiscal peirod will come in active , they want to view all the data ( Including historical records)based on the both the fiscal period based on the selection in the query.
Technical requirement: Dynamic switching is requried for Fiscal Year Variant in the query level.
Suggestion Required for below point:
1. Is it required to maintain two Fiscal year variant ?
2.How do we maintain the new fiscal year period for historical record ?
3. Is it any posibilities their with out major disturbance of the existing query ?
4. Is it possible to do in query level with minor impact of performance ?
5. Is it possible to do in back end side with out redundancy of the records ?
6.I have a solution to use multiprovider on top of two infoprovides which are maintain the fiscal period based on two fiscal year variant. If I realize this it would lead major back end work.
7. I have another solution to add another two fields in the existing structure to hold new variant and fiscal period. If I do this How dynamically I can change the structure of the query for to view the different fiscal period information.
Anticipate your reply eagerly
With Regards
Siva

Hi,
1. Is it required to maintain two Fiscal year variant ?
Yes, You will need to have another Fiscal Year variant for Sep to Oct.
2.How do we maintain the new fiscal year period for historical record ?
To do this at the BI Level, You can have a routine to convert the Fiscal Year Period according to the new Variant.
You will have to get the help of a functional consultant in order to understand the logic of opening and closing balance. According to the new variant the current Fisc Period 009.2009(Sep 2009) will become 001.2010 and so on. Apart form just converting the period, you will also have to take care of carrying over the balances.
3. Is it any posibilities their with out major disturbance of the existing query ?
Once you implement the above logic, you can just include the New Fiscal variant into the query.
4. Is it possible to do in query level with minor impact of performance ?
Yes, as mentioned above.
5. Is it possible to do in back end side with out redundancy of the records ?
Not sure about this.
6.I have a solution to use multiprovider on top of two infoprovides which are maintain the fiscal period based on two fiscal year variant. If I realize this it would lead major back end work.
This seems to be the best way. You will not have to touch the existing cube. Only your reports will have to be copied to the New MultiCube. The logic in the 2nd Q above will be for the new cube.
Regards,
Gaurav

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

For the k4 fiscal year variant,no period is defined 26-03-2010

Dear all,
Please explain thes eterms.
this error comes during making of purchage order.
why this error is coming and what i have to do???
Thanks and regards,
Baiju

Hi
Check what fiscal year variant is assigned to your company code in OB37 and check its validtiy in OB29
Regards
Antony

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

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

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.

Change future periods for Fiscal year variant-OB29

Similar Messages

Maybe you are looking for