Configaration of fiscol year variant ?

Hi,
this is prabhakar,
I very much new to the sap,Now i am learnig SAP FICO .
i have not clarified on fiscol year variant both short end & non shortened.
can any one assist me
          Thanking you,
                       Have a nice day.
                              PRABHAKAR

Fiscal Year and Calendar Year  
You have the following options for defining your fiscal year variants in relation to the calendar year:
Fiscal year same as calendar year
Fiscal year differs from calendar year (non-calendar fiscal year). The posting periods can also be different to the calendar months.
Your fiscal year is year-dependent. This means that the fiscal year only applies to a specific calendar year.
Fiscal Year Same as Calendar Year
If your fiscal year is the same as the calendar year, the following specifications apply:
The fiscal year begins on January 1.
Twelve posting periods are available.
The periods correspond to calendar months. You do not have to define the individual periods. The system automatically uses the calendar months.
Non-Calendar Fiscal Year
If your fiscal year differs from the calendar year, you must specify:
How many posting periods you require
How the system should determine the posting period and fiscal year from the posting date during posting:
Posting Periods
To enable the system to determine the posting period, specify month and day limits for the end of each period.
Enter 29 as the day limit for February. This ensures that the system can also determine the posting period correctly in a leap year. If you enter 28 as the day limit for February, transaction figures posted on 29 February will be updated in the next period. If the next period is not open, the system issues an error message.
Fiscal Year
Since your fiscal year is not the same as the calendar year, you have to specify the year displacement for each posting period. You can use the entries -1, 0, and +1 for this.
In the illustration that follows, your fiscal year begins on April 1 and ends on March 31. The period limits correspond to the beginning and end of the calendar months.
Since the fiscal year does not correspond to the calendar year, you specify how the fiscal year is to be determined by entering the year displacement. If you post with a posting date of 02/03/99, the system uses your definition of the fiscal year variant to determine that posting period 11 is in fiscal year 1998.
Posting Periods Do Not Correspond To Calendar Months
If you are using a non-calendar fiscal year, and your posting periods do not correspond to the calendar months, define the difference by specifying the day of the period end.
Your fiscal year begins on April 16 and ends on April 15. The start and end of your posting periods do not correspond to the start and end of a calendar month.
You must split the period 12/16 to 01/15 in two posting periods, since you require different specifications for the year displacement. This means that for posting period 9, you have to define two posting periods (with year displacements 0 and -1).
In the example given, the system would determine the following posting periods and fiscal years from the posting dates given:
Posting Date
Year Displacement
Period
Fiscal Year
20.12.1998
0
9
1998
13.01.1999
-1
9
1998
Year-Dependent Fiscal Year Variants
You can define a year-dependent fiscal year variant. This is a fiscal year variant that only applies to a specific calendar year.
To do this, select the field Year-dependent when you define your fiscal year variants. You then have to enter the period ends, defined by month and day limits, for each calendar year.
In this case, the year displacement specifications refer to the calendar year for which you have defined posting periods. The year is displayed when you maintain the period ends.
Shortened Fiscal Year  
Definition
Fiscal year that contains less than twelve months.
A shortened fiscal year could be necessary in the following cases, for example:
Establishment of a company
Changeover from a calendar year to a non-calendar fiscal year, or vice versa.
Use
When you define a shortened fiscal year, you have to make the following specifications:
A shortened fiscal year must always be defined as year-dependent, since it can only apply to a specific year and must be followed by a complete fiscal year.
You define a shortened fiscal year and the following or previous complete fiscal year in one fiscal year variant.
You define a shortened fiscal year in Customizing for Financial Accounting as follows: Financial Accounting Global Settings ® Fiscal Year ® Maintain Fiscal Year Variant (Maintain Shortened Fiscal Year)
Integration
The options available for defining a shortened fiscal year depend on whether you are using Financial Accounting with or without Asset Accounting.
If you are using Financial Accounting without Asset Accounting, each fiscal year can start with any period.
If you use Financial Accounting with Asset Accounting, each fiscal year must start with period 001, so that the depreciation can be calculated correctly.
For more information, see the Asset Accounting documentation under  Shortened Fiscal Years
This link will help you
http://help.sap.com/erp2005_ehp_03/helpdata/EN/96/8b2fd543ce11d189ee0000e81ddfac/frameset.htm
http://help.sap.com/erp2005_ehp_03/helpdata/EN/96/8b2fd543ce11d189ee0000e81ddfac/frameset.htm
http://help.sap.com/erp2005_ehp_03/helpdata/EN/96/8b2fd543ce11d189ee0000e81ddfac/frameset.htm
Regards
Odaiah

Similar Messages

  • FISCOL YEAR VARIENT

    Hi this is Prabhakar,
    I am not clarified that for short end fiscal year
    I want create a fiscal year as six months for six periods (from October to March)
    Shall I prepare like this suggest me.
    FISCOL YEAR (2007-2008)
    F.V     DISC          YEAR DE     CLDR YER     NORM POS       SPECIAL POSTING
    PY     OCT-MAR     YES               NO          6          2          
         Month          Day          Periods                              
         1          31          0     JAN-08
         2          29          0     FEB-08          
         3          31          0     MAR-08
         4          31          +1     OCT-07
         5          30          +1     NOV-07
         6          31          +1      DEC-07
    PLEASE CURRECT ME
    THANKS

    Hi Prabhakar,
    Your configuration should be:
    Month____Day______Period____Year shif
    10_______31________1________0
    11_______30________2________0
    12_______31________3________0
    1  _______31________4________-1
    2  _______29________5________-1
    3  _______31________6________-1
    Please also see the documentation about Fiscal Year Variant:
    http://help.sap.com/erp2005_ehp_04/helpdata/EN/c5/da683859cf3b45e10000009b38f8cf/frameset.htm
    When you define a shortened fiscal year, you have to make the following specifications:
    - A shortened fiscal year must always be defined as year-dependent, since it can only apply to a     specific year and must be followed by a complete fiscal year.
    - You define a shortened fiscal year and the following or previous complete fiscal year in one fiscal year variant.
    Kind regards,
    Cintia.
    Edited by: Cintia Marangon on Dec 3, 2008 3:02 PM
    Edited by: Cintia Marangon on Dec 3, 2008 3:06 PM
    Edited by: Cintia Marangon on Dec 3, 2008 3:08 PM

  • Error while saving FYV : Gaps in financial year variant periods

    Hello Experts,
    We are getting an error while saving  a new FYV as:
    Gaps in financial year variant periods XY
    Message no. FGV556
    Diagnosis
    The period specification has gaps. The periods must be sequentially numbered without any gaps.
    System Response
    Only a correctly defined period assignment can be saved.
    Procedure
    Define the periods with consecutive numbers.
    Details: The new FYV has 52/53 weeks as posting periods depending on calendar year.
    For example, we are trying to define Fisc 2009 as follows. (Fiscal year 2009 = Nov 01 2008 to Oct 31 2009).
    Month-Day-Period-Yearshift
    11     ---     7     ---     1     ---     +1
    11     ---     14     ---     2     ---     +1
    11     ---     21     ---     3     ---     +1
    11     ---     28     ---     4     ---     +1
    12     ---     5     ---     5     ---     +1
    12     ---     12     ---     6     ---     +1
    12     ---     19     ---     7     ---     +1
    12     ---     26     ---     8     ---     +1
    12     ---     31     ---     9     ---     +1
    1     ---     3     ---     9     ---     0
    1     ---     10     ---     10     ---     0
    1     ---     17     ---     11     ---     0
    1     ---     24     ---     12     ---     0
    1     ---     31     ---     13     ---     0
    2     ---     7     ---     14     ---     0
    2     ---     14     ---     15     ---     0
    2     ---     21     ---     16     ---     0
    2     ---     28     ---     17     ---     0
    3     ---     7     ---     18     ---     0
    3     ---     14     ---     19     ---     0
    3     ---     21     ---     20     ---     0
    3     ---     28     ---     21     ---     0
    4     ---     4     ---     22     ---     0
    4     ---     11     ---     23     ---     0
    4     ---     18     ---     24     ---     0
    4     ---     25     ---     25     ---     0
    4     ---     2     ---     26     ---     0
    5     ---     9     ---     27     ---     0
    5     ---     16     ---     28     ---     0
    5     ---     23     ---     29     ---     0
    5     ---     30     ---     30     ---     0
    6     ---     6     ---     31     ---     0
    6     ---     13     ---     32     ---     0
    6     ---     20     ---     33     ---     0
    6     ---     27     ---     34     ---     0
    7     ---     4     ---     35     ---     0
    7     ---     11     ---     36     ---     0
    7     ---     18     ---     37     ---     0
    7     ---     25     ---     38     ---     0
    8     ---     1     ---     39     ---     0
    8     ---     8     ---     40     ---     0
    8     ---     15     ---     41     ---     0
    8     ---     22     ---     42     ---     0
    8     ---     29     ---     43     ---     0
    9     ---     5     ---     44     ---     0
    9     ---     12     ---     45     ---     0
    9     ---     19     ---     46     ---     0
    9     ---     26     ---     47     ---     0
    10     ---     3     ---     48     ---     0
    10     ---     10     ---     49     ---     0
    10     ---     17     ---     50     ---     0
    10     ---     24     ---     51     ---     0
    10     ---     31     ---     52     ---     0
    The above entries cover all the dates in calendar year 2009, that is, Jan 2009 to Oct 2009  is covered by periods 10 to 52 and Nov 01 2009 to Dec 31 2009 is covered by period 1 to 9 of the following fiscal year 2010.
    Inspite of making sure that all the days of 2009 are covered by periods 1 to 52. We are still unable to save the FYV.
    Please help!
    Susan

    Hello, I am getting this error while saving the FSV. My FSV is based on Weeks. Below is what I am inputting for this. Other details are Calender Year -  2017, No. of posting periods - 53, checked year dependent. Also, I have FSV for previous years also where weeks are 52 but configured as 53. So, hope that this is not creating this issue. Solicit your early response.
    Month
    Day
    Period
    Year Shift
    1
    7
    1
    0
    1
    14
    2
    0
    1
    21
    3
    0
    1
    28
    4
    0
    2
    4
    5
    0
    2
    11
    6
    0
    2
    18
    7
    0
    2
    25
    8
    0
    3
    4
    9
    0
    3
    11
    10
    0
    3
    18
    11
    0
    3
    25
    12
    0
    4
    1
    13
    0
    4
    8
    14
    0
    4
    15
    15
    0
    4
    22
    16
    0
    4
    29
    17
    0
    5
    6
    18
    0
    5
    13
    19
    0
    5
    20
    20
    0
    5
    27
    21
    0
    6
    3
    22
    0
    6
    10
    23
    0
    6
    17
    24
    0
    6
    24
    25
    0
    7
    1
    26
    0
    7
    8
    27
    0
    7
    15
    28
    0
    7
    22
    29
    0
    7
    29
    30
    0
    8
    5
    31
    0
    8
    12
    32
    0
    8
    19
    33
    0
    8
    26
    34
    0
    9
    2
    35
    0
    9
    9
    36
    0
    9
    16
    37
    0
    9
    23
    38
    0
    9
    30
    39
    0
    10
    7
    40
    0
    10
    14
    41
    0
    10
    21
    42
    0
    10
    28
    43
    0
    11
    4
    44
    0
    11
    11
    45
    0
    11
    18
    46
    0
    11
    25
    47
    0
    12
    2
    48
    0
    12
    9
    49
    0
    12
    16
    50
    0
    12
    23
    51
    0
    12
    30
    52
    0
    12
    31
    1
    +1
    Thanks
    Deepankar

  • 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

  • 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

  • Customer Exit Variable Period 000 is not valid in financial year variant Z2

    Hi all,
    I am trying to get the week number from a particular posting period. But I get this error when I execute the Query:
    Error Group
    RFC_ERROR_SYSTEM_FAILURE
    Message
    SYST: Period 000 is not valid in financial year variant Z2
    I checked in "FIRST_DAY_IN_PERIOD_GET" FM and it is not accpting period 000 for PERIV Z2. It works fine for all other periods.
    Does anyone have an idea on this?
    Thanks.

    Simon,
    So do you think that there is a problem in my Query restrictions? You ask me to restrict from 0 - 12, but this period is calculated based on the SY_DATUM in a cust. exit variable. And this period is being used to pull week number. So, do I need to change the code?
    But I already have another query which is similar to this, only ready for input options are missing in the new one. The older one is working fine but the I have problem with this.
    Any more ideas?
    Thanks!!

  • 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

  • Fiscal year variant- WK : posting date from 29 to 28

    Dear Gurus,
    Customer wants FI posting period starts from 29 to next 28, that is
    period 1: Jan 1st ~Jan 28th;
    period 2: Jan 29th ~Feb 28th;
    period 3: Feb 29th~March 28th
    period 4: March 29th ~April 28th
    period 5: April 9th~May 28th
    I created a new fiscal year variant, check year-dependant, uncheck calendar year .
    and it works when posting FI document, however, when posting good issue documents,
    system generates error message that material posting period is March and April.
    so I try to use MMPV to open posting period May, and still system doesn't allow to do that.
    Message as follows:
    Mode: Check and close period
    Client:500
    Period entered (month/year):052009
    Invalid period for company code 1000; no conversion here.
    Period closing complete; log issued.
    What should I do ?
    Thanks Gurus!
    Lynn
    E N D

    Hi,
    Firs check the current status of period in MMRV
    And use MMPV transaction and enter the following details -
    Company code - 1000
    Period - 03
    Fiscal year 2009
    Then
    Company code - 1000
    Period - 04
    Fiscal year 2009
    Now try to psot the entry.
    ~Thanks!
    Rajesh

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

  • Fiscal year variant Z1 is not maintained for calendar year 2012

    I am getting this error while scheduling infopackage for 2lis_02_HDR.
    Fiscal year variant Z1 is not maintained for calendar year 2012
    PLease let me know how to solve thhe issue.
    Thanks,
    harika.

    Hi,
    Where are you geting error, before execution or duing execution of DTP in the log.
    Check if you have transferred fiscal year variants from source system to BW. Then trigger DTP.
    Regards,
    Pravin Karkhanis.
    Edited by: Pravin Karkhanis on Oct 18, 2011 4:15 AM
    Edited by: Pravin Karkhanis on Oct 18, 2011 4:15 AM

  • Fiscal year variant Z1 is not maintained for calendar year 2012 when loadin

    Dear Experts,
    We are working on BI7.0 extracting data from ECC 6.0.
    I am trying to load data from 0HR_PY_PP_1 which is a Self DataSource in our BW System (extracts data from 0EMPLOYEE and 0PERSON) to load into ZPA_C50 which is a copy of BCT InfoCube 0PAPA_C02 (Headcount).
    The data has come through into the PSA very well.
    However, DTP is throwing an error while loading 32242 records of data from PSA into ZPA_C50 InfoCube. The error details as below:
    Error while updating to target ZPA_C50 (type INFOCUBE)
    Fiscal year variant Z1 is not maintained for calendar year 2012     FGV     2
    Messages for 1 data records saved; request is red acc. to configuration
    Processing Terminated
    We are actually doing a Re-implementation of BW 3.0b in BI 7.0 Ehp1. We have imported Maintenance of Fiscal Year Variant from the BW 3.0b Production System. So this shouldn't be a problem I guess since I have also checked the setting in SPRO in BI 7.0 Development (New) System and they are looking good.
    Also, when I do a Filter on 0CALDAY in DTP from 01.01.1900 to 31.12.2010, the loads are working fine. I want the load to run without any Filters on 0CALDAY.
    Has anyone been in similar situation. How did you resolve this issue? Your time is very much appreciated.
    Thanks in advance.
    Chandu

    Dear Experts
    Thanks for your time.
    We have resolved this issue ourselves. We have maintained 'Shortened Fiscal Years' for 'Z1' and it is working fine now. Steps are as below:
    In BI Dev System -> SPRO -> SAP Reference IMG -> SAP Customizing Implementation Guide -> SAP NetWeaver -> Business Intelligence -> General BI Settings -> Maintain fiscal year variant -> Select 'Z1' Fiscal Year Variant and then DoubleClick on 'Shortened Fiscal Years' to set the Fisc Year Variant -> Save.
    The dataload should work fine now.
    Cheers,
    Chandu

  • Regarding Rough FISCAL YEAR VARIANT NOT PROCESSED

    Hi Experts,
    I am loading data from 2lis_03_um to 0IC_C03,While executing DTP i am getting error as Rogh FISCAL YEAR VARIANT NOT PROCESSED.
    Can anyone please suggest me how to resolve the issue.
    Thanks
    Laxman

    Hi,
    Use the settings here:
    transaction code SPRO
    SAP Netweaver
    Business Intelligence
    Settings for BI content
    Trande Industries
    Retailing
    => set fiscal year variant
    regards,
    pascal

Maybe you are looking for