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.

Similar Messages

  • 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

  • SAP BW DTP error: Fiscal year variant is not maintained for calendar year

    Hi experts,
    Running DTP for loading 2LIS_12_VCITM results in following error "Fiscal year variant A2 is not maintained for calendar year 2012".
    I have already done following checks:
    - the fiscal variant A2 exists for the fiscal year 2012 in the BW system (T009 tables)
    - the DTP does only give this error for 2 company codes, and works fine for other company codes
    - in our R3 system, the fiscal year variant A2 is assigned to all the company codes, how or where can I check this assignment in the BW system ?
    Kind regards, Guy Verschueren

    Hi
    Please check the following threads
    "Fiscal year variant V3 is not maintained for calendar year 2011" (OAOB)
    Error FGV002: Fiscal year variant & is not maintained for calendar year &
    Hope it helps.
    Thanks,
    Rajesh.
    Please assign points to answers if you find them heplful

  • 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

  • Error FGV002: Fiscal year variant & is not maintained for calendar year &

    Hi all,
    I am facing a unique problem in BW production. This is not happeneing in my Development.
    Whenever I goto table    "/BI0/SFISCPER" or do F4 on any Fiscal Year / Peiod field, I get the message " Error FGV002: Fiscal year variant R1 is not maintained for calendar year 2005"  . In my client R1 is Shortened Fiscal Year.  But we are not using this for year 2005 and most years. And the message is Type Error. I tried to debug but the code enters in 100 odd Function Modules and does not give any answer.
    My Finance Person has checked the settings in transaction SPRO > SAP Reference IMG > BW Customizing Implementation Guide > Business Information Warehouse > General BW Settings > Maintain Fiscal Year Variant). They are exactly identical to R/3 production setting.
    I have already done rebuild of Fiscal Year Variant from Source System by right clicking and loading data again.
    I am using BW 3.0B with Bi Content 3.1 . Please advise urgently.

    Hi TCS
    Please check these SAP notes in advance:
    1619823
    1835628
    Please advice if this helps.
    Regards
    PC

  • "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

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

  • Maintaining Fiscal year variant

    Friends,
    Can someone explain to me this structure of the fiscal year variant.
    As can be seen, there are 2 periods for each quarter...I dont understand why is this. Also, There is period '1' again in the end for Month 12 with Yera shift as +1.
    Can someone explain this please.
    Month  Day  Period  Year Shift
    1         27     1         0
    3          3       2         0
    3          31     3         0
    4          28    4         0
    6          2       5        0
    6
    7
    9
    9
    10
    12         1       11         0
    12       29        29        0
    12       31        1        +1

    Hi,
    In fiscal year variant your are define the periods under different types. one period means it is not a month. it may be one day also. it is not standard one . for Further reference please see the standard ones namely, F1 this is also like one of the customization and standard one.
    Coming to year shift. For example according to india the accounting year is April to march. so the First month is according to accounting transactions April and the last month March. But our calendar shows from January to december. That is the reason we are specify Jan to March as -1. See V3 standard one.
    IF the accounting year start from May to April. then From Jan to april the year shift will be -1.
    Hope this clear, if yes assign points.
    Regards,
    Sankar

  • In DTP Detailed fiscal year variant not processed

    Hi All,
    I installed and activated CUBE 0IC_C03,
    now while executing the DTP  2LIS_03_UM / LOGSYSDEV -> 0IC_C03 it throws Error 'Detailed fiscal year variant not processed'
    then in sdn i searched they told that i have to maintain variant in SPRO TC or OB29
    IN SPRO ---> SAP Reference IMG ---> SAP NetWeaver ---> Business Intelligence ---> Setting's for BI Content ---> Trade Industries ---> Retailing ---> Set Fiscal Year Variant.
    i think we can change, so usually who will maintain those variants ? pls tell.
    can i change?
    Edited by: Ranga123 on Aug 10, 2009 12:43 AM

    The Best Practice for getting the Fiscal Year Variants identified is to extract and load from the source system and not maintain them directly in SAP BW.
    To get the Fiscal Year Variants, go to RSA and then select Source System on the left navigation bar. From there, go to the SAP source environment and right-click on that. Select Transfer Global Settings. In the selection screen, select the Fiscal Year Variant checkbox, select the Update radio button and then execute. This will update the Fiscal Year Variant tables in BW.
    If, for any reason, the Fiscal Year Variant being loaded doesn't exist after that, you have a couple of options:
    1) Have your business or business analyst for the SAP source system maintain it in the source system and then transfer the Global Settings as described above (this is the most preferred way to handle it).
    2) Update the Fiscal Year Variant directly in BW via the means you outlined in your post.

  • 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

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

  • Fiscal year variant is incorrect

    Dear all,
    we have an additional daily ledger and daily fiscal year variant related to each other.
    While trying to see line items by double-clicking, for example, cumulative balance line in FAGLB03 transaction I get the following error:
    "Fiscal year variant XX is incorrect."
    When determining the posting period, a period was found that is not in the permitted area 1 - 16.
    Procedure Correct the fiscal year variant.
    I have checked settings for the daily fiscal year variant and see no mistakes there.
    I should mention that daily ledger and daily fiscal year variant had been set 2 years ago and worked without any problems.
    Regards,
    Stanislav.

    Hello,
    Check the customizing of LR variant in OB29
    select the LR and double click the folder for period on the left.
    enter then the year and continue
    you will see a list of periods (hopefully, if not you have to maintain the Periods, better ask the FI colleague to do it).
    Thanks
    sapman man

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

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

Maybe you are looking for