Multiple Fiscal year variant

For global consolidaiton I have all company with same fiscal year variant.
For 2 regional consolidation I have different kind of fiscal year variant.
Do we handle different fiscal year variant thru different consolidation area or different data basis.
What is better approach.

Colin,
Could you please explain more how this is accomplished?
I have not seen this before.
Thanks.

Similar Messages

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

Use of different fiscal year variant in leading&non leading ledgers and Asset closing&Reporting

Experts,
Need one clarification on using different fiscal year variants for Leading(0L)&non Leading(NL) Ledgers and impact on Fixed Asset Accounting.If I use say V6(Jan2013-Dec2013) for Leading Ledger and April2013-March2014 for non leading Ledger,(local GAAP)-please clarify the following.
1.Does Asset Accounting gives all standard reports as expected in both(Leading&Locals) the Depreciation areas?Do we need to any settings specially for in the above scenario?(I am assuming point#4 given below may not help for this as system gives an error if both the fiscal year variants have different start&end dates)
2.How is Year end in Asset Accounting handled?If I close the year end in Asset Accounting for Company Code as per Leading Ledger i.e say by Dec 2013,can I still post the asset entries in non leading ledger?Because Financial year for Leading ledger will be 2014 and non leading will be still 2013(in Jan2014).
3.I am aware SAP has some restrictions way back in 2005-2007 (SAP note 844029) for different fiscal year variants in Leading&Non Leading Ledgers,Does SAP come out with any solution later?
4.What is the exact use of the settings at Asset Accounting>>Valuation>>>Fiscal year>>Fiscal year variants at company code level or Depreciation area level?My understanding here is,they are not meant for using different fiscal year variant with different start&end dates but they are meant for using different fiscal year variant with same START&END DATES and have different number of posting periods i.e 1 can have 12 and other can have 13.
Please can you give your comments?
regards
hinfi

Hi Hinfi,
It seems standard SAP does not manage different fiscal year variants (at least with different start/end dates) in different depreciation areas.
However, they came up with an add-on solution called Multiple Calendar Tool and based on a mirroring solution that synchronizes asset transactions in a mirror company code.
It's all explained in following notes:
Note 1175751 - Project solution for alternative fiscal year variant
Note 1636025 - Asset acctg multi calendar tool 1.0_ SP Note
Note 1658489 - Installation of Asset acctg multi calendar 1.0 software
Note 1658714 - Asset acctg multi calendar tool_ Overview Note
Note 1691481 - Release strategy_ Asset acctg multi calendar tool
Note 1951069 - Different fiscal year variants in General Ledger Accounting (New) (NewGL) under the new Asset Accounting (FIN_AA_PARALLEL_VAL)
I don't know if it's commonly used and personnaly have no feedback on it. I was curious to check how to manage a depreciation area 01 posted in a leading ledger in US GAAP (FYV january to december) and another depreciation posted in a non leading ledger in Indian GAAP (FYV april to march).
BR
Gregory

Fiscal year variant not maintain issue

Hi Gurus,
I am loading data from DSO to Cube. But I amgetting an issue "Fiscal year variant V9 is not maintained for calendar year 0001". Please let me know how to resolve this issue.
Thanks
Liza

This looks like a data quality error.
The years maintained in your source system probably does not have a year 0001. If that data record is corrected and the correct year entered in the data record, this error should go away.
You may have mapped a date in the DSO to fiscal period in the InfoCube. That date may be incorrect for year 0001 which does not make sense.
You can identify this record in the DTP monitor by clicking on the magnifying glass icon which will show you all the records in that data package which has the error record.
And then click on the field header for status and click on sort ascending icon. It will quickly show you which record is failing by bringing the failed status record to the top of your list.
Once you have identified the record that has this bad data, you can ask the functional team who owns that data and ask them to fix it.
Or you can fix this record in your PSA. Or you can exclude that record in your DTP filter. There could be multiple records with the data quality error in which case you should filter out those records to be able to load data to the cube successfully.
These records may also be in your error stack. You can click on the error stack icon at the top of the window in your DTP monitor view. This will show you only the error records.
Hope this helps.
Good Luck.
MP.

Can you have more than one Fiscal Year Variant

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

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

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

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

Multiple Fiscal year variant

Similar Messages

Maybe you are looking for