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

Similar Messages

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

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

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

  • Multiple Fiscal year variant

    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.

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

  • How to enable multiple users logging in to the same client machine?

    We have our home directories shared from the server (using AFP) and this allows our users to log in to any machine via the normal console login.
    But if you try to remotely login to a machine with ssh, and another user is already logged in at the machine, then you get the error message:
    Could not chdir to home directory /Network/Servers/machinename/Users/keith: No such file or directory
    I can connect (via) ssh, only if no user is logged in at the console. If I connect with ssh when no users are logged in, and then a user logs in at the console, then this unmounts the home directory for the ssh user.
    I have read about the mnthome command, and if I try running this (from my ssh login whilst there is a console login) then I get the error message:
    Error: Mount failed with error 1 Operation not permitted
    I'm assuming that multiple ssh logins must be allowed somehow? Can you only do this if you share your home directories with NFS (in this case, I understand that all home directories always appear mounted on each client)???
    Any help appreciated,
    Server and all clients running 10.4.3
    iBook & PowerMac G5   Mac OS X (10.4.3)  

    Thanks for the info. I really thought that this would be a fixable problem. I also thought that it might work when two different users both logged in using ssh only (i.e. when there is no console login). But this also causes problems for the second ssh login.
    What practical work-arounds have people tried? The respondent to your other post (linked to above) suggested that NFS sharing might work, only that ssh logins still don't mount the home directory. Is this the case?
    Thanks for the speedy answer.

  • Fiscal Year Variant change

    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...
    Edited by: Nick Bertz on Dec 3, 2009 3:17 PM

    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:
    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
    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 
    Edited by: Nick Bertz on Dec 29, 2009 4:15 PM

  • Defining the Fiscal Year Variant

    Would someone explain the procedure for setting up the Fiscal year variant in the current version please.
    The version I had used was 3.1h and the screens are now different. In 3.1h one simply copied the fiscal year variant (T.code OB29) using the copy command and one got a copy fiscal year dialog box in which one entered the data into the four fields.  But none of this now happens.
    In both the current version and the old version (3.1h) I select in column FV "V3" ( the Fiscal year variant I want ) copy V3 and now I want to create a new Fiscal Variant with my own company two letter designation (e.g. YZ) taking the V3 copy as the model to use.  But I can't because nothing then happens.
    In v3.1h a small sub window appeared when doing the copy ("copy icon") and in the first line was the copied designation code V3 with the description in the 2nd line and in the 3rd line one enterd one's own two letter company designation (e.g. YZ) plus the discription on line 4, click the tick and it was done.
    How do I do that part now?  Because this sub screen does not now appear when trying to do a copy and create a copy designation.

    Hi Ton,
    In transaction code <b>OB29</b> for the later versions of SAP (i.e. 4+), you don't get a pop-up window. The system just copy the selected Fiscal Year Variant. That is the only one you would see once you have highlighted the year variant you want to copy from and you hit the "<b>Copy</b>" icon. All the fields you need to change would still be open. In the <b>FV</b> column, just change it from <b>V3</b> to your new one <b>YZ</b>. Do the same for the description and the rest of the field you need to change and hit "<b>Enter</b>" on your keyboard. A diaglog box "Specify object to be copied" would appear. You can then "<b>Copy All</b>" or "<b>only Copy Entry</b>" depending on your need. If you select "Copy All", you would get a dialog box informing you of the <b>number of dependent entries copied</b>. You can then save your entries and carry out the rest of the set-up for "<b>Periods</b>", "<b>Period Texts</b>" and "<b>Shortened Fiscal Years</b>" as required by you.
    I hope the above helps.
    Do not forget to award the points please.

  • Controlling area & operating concern must have same fiscal year variant

    Dear Experts,
    Whether i can assign two controlling area with different fiscal year variant to one operating concern.
    Getting error 'Controlling area & operating concern must have same fiscal year variant'
    Fiscal year variant must be same or Number of posting period must be same.
    Moderator: Please, search before posting

    Hi ajay,
    I did the testing also,
    System is showing error msg' Controlling area & operating concern must have same fiscal year variant'
    But someone told me. number of Posting period must be same not fiscal year variant.That why i am confused.
    I assigned all company code same posting period variant in different controlling area.Still facing same error.
    That why i have posted in SDN.

  • You have not maintained a rule for the fiscal year variant

    1) I have Fiscal Year Variant in the Cube ( it got added along with fiscal year ) but there is no Fiscal year variant in the datasource & when I dont map it Transformation activation prompts error " You have not maintained a rule for the fiscal year variant ".
    Can I just delete Fiscal year variant from the cube..does it matter?
    2) Fiscal year & Posting Period can be populated from Fiscal Period, is the vice versa possible..? Does the sytem will take care of the conversion..?

    1. no, you should not delete and you cannot delete fiscal year variant from cube, it's required by fiscal year/ period (compound infoobject), you should add it in your datasource, or you can map with a constant value e.g K4
    2. yes, fiscal period can be populated by posting period
    some info on time characteristic relationtionship
    hope this helps.

  • Fiscal Year Variant in Controlling Area

    Hi All,
    Scenario 1:
    I have a Company code with FYV  "A" with 12 Normal Periods and 4 Special Periods(Apr - Mar), and I have another company code with FYV "B" with 12 Normal Periods and 4 Special Periods(Apr-Mar).
    Can I assign these two company codes on Controlling Area?
    Scenario 2:
    I have a Company code with FYV  "A" with 12 Normal Periods and 4 Special Periods(Apr - Mar), and I have another company code with FYV "B" with 12 Normal Periods and 4 Special Periods(Jan-Dec).
    Can I assign these two company codes on Controlling Area?
    Thanks for your help
    Best Regards

    Dear Ranga,
    I thought i will give more information.
    The fiscal year variants for the company code and the controlling area can have a different number of special periods, but must have the same number of posting periods. The period limits for the fiscal year variants must also match up. In FI, special periods are used for adjustment postings at year-end closing, or for revaluation. If FI has been set up with four special periods, but CO with only one, then the postings for the second, third, and fourth special periods in FI are posted to the first special period in CO. If there is no special period in CO, the FI postings in the special period are posted to the last posting period in CO.
    Assign points

  • Ledger 0 has fiscal year variant instead of V3 - Message - GI174

    Hi all,
    i am geting below message when i am doing KP06 for cost center planning
    Ledger 0 has fiscal year variant instead of V3
    Message no. GI174
    When transferring planning data, the receiver ledgers must have the same fiscal year variant as the sender system, since all planned periods are transferred and not just one period with a posting date. Therefore, the period cannot be converted.
    Compare the fiscal year variant of the sender system with the FI-SL fiscal year variant.
    You can access this in FI-SL Customizing by choosing Basic Settings Master Data -> Ledger (select the ledger specified in this message) -> Assign Comp.Cd/Comp. -> After selecting the company code, the system displays the assigned fiscal year variant.
    Kindly do the needful.

    The message means you need to change fiscal year variant of ledger 0 to V3. I guess your fiscal year variant of controlling area is V3. Both of them should have same fiscal year variant. So change it may be solve the problem.

  • Period indicator with Fiscal Year Variant in MRP3

    Hi  SAP Gurus,
    I donu2019t know the use of Period indicator with Fiscal Year Variant in MRP3 view.
    For some material  is maintain as
    1. Period indicator u201CMu201D & Fiscal Year Variant as blank.
    & for other materials it is maintain as
    2. Period indicator u201CPu201D & Fiscal Year Variant as V3
    What is the meaning of maintaining those different values ?
    as per my understanding I only know that as per those indicator consumption data is store in table MVER.
    Is there any other table /  data gets affected due to this indicator.
    Plz help.
    Best Regards,
    Parag Save.

    Nomally,  period of  12 months, for which the company produces financial statements or analyse inventory.Under certain circumstances, fiscal years containing fewer than 12 months are also permitted (short fiscal year
    When defining your fiscal year, you have the following options:
    Your fiscal year is the calendar year
    In this case, you must only select the Calendar year field.
    Your fiscal year is not the same as the calendar year and is not year-dependent
    Your fiscal year is not the same as the calendar year and is year-dependent.
    In customizing (spro), you make these setting in transaction OB29.

  • Diffrent Fiscal year Variant ?

    Hello Friends
    For the different company codes using the same controlling area must have same fiscal year variant.
    But in my scenario 1 company code having period from jan to dec and another having period from April to march
    Pls suggest me how we can do that?If not is there any otherway of solving this issue?
    I need your suggestions

    the best documentation is the <a href="">online documentation at</a>
    From your point of view, the most important things are:
    1. Define a table group in transaction GCIN. Include all fields in object table 1 that you want to report on (with the different fiscal year variant). If this is a legal requirement as I suppose, then you probably only need the GL account (RACCT) field. You may require other fields as well, depending on your requirements.
    2. After the table group is defined, you have to check and install it. Installation means here the new table group is added to the Special Ledger environment, i.e., it is added to many customizing tables + lots of standard ABAP code is regenerated.
    3. Now you can create a ledger for your new summary table (this is one of the 4 or 5 tables in your new table group). in transaction GCL1. You should assign the company code where the alternate fiscal year variant must be used to the new ledger. Obviously, you should change the fiscal year variant in the assignment screen to the alternate one (the default would be tha FYV that you have assigned to your company code in OBY6  , this is the controlling area's FYV as well).
    4. Then you have to asign "activities", or "business transactions" to the ledger/company code combination. Use the button "Activities like GL" here to make sure all relevant items are transferred to your ledger. That would be about 30 activities. Each of them require a "field movement rule" assigned, but the same rule can be used for all, so you have to create it only once. The best way to do it directly from here (you are still in GCL1), by clicking F4 and when the message comes, no entries found, you can start creating it. The field movement rule is nothing else than the rules how fields of the original (FI, MM, SD) documents are transferred to the fields in your FI-SL table. You can check out the proposal button here. RACCT should be populed from HKONT, the rest is I think obvious.
    Back to GCL1, you have to set the posting indicator for each activity (business transaction) to 3. This makes sure online data transfer and subsequent data transfer both are possible.
    5. Save your work.
    6. Then you can start transaction GCU1 and take over all documents available in FI to your special ledger (if you have some postings already)  . Or you can post a new document and check if it was transferred (it should). Example: in FI (fiscal year variant April to March) you post a document with posting date 01.April 2007.  This is period 1 in FI then. The same document is transferred for period 4 in the SPL.
    7. You can use the Report Painter / Report Writer tools to report your data. ALso you can consider report RFBILA10, which is almost the same as well-known RFBILA00, only that it can display data from a special purpose ledger.
    Hope that helps, points welcome

  • Assigning Different Fiscal Year Variants between comapny codes

    We have 2 company codes 1000 and 1010 both are assigned to controlling area 2000. I want to know what are the impacts of assigning company 1000 and 1010 to different fiscal year variants. I get this warning message when i try to save.
    Please advice if this is advisable to do? and what are the impacts.
    Message no. KT297
    Fiscal year variant K4, controlling area 2000, does not agree with fiscal year variant V9, company code 1010.
    The following entries must agree:
    Same number of posting periods (the number of special periods may vary)
    Same period limits
    Ensure that the fiscal year variants of the controlling area and the assigned company codes agree. If necessary, maintain the fiscal year variants.

    Dear Zaid Azam,
    you have assigned 1000 and 1010 to one controlling area 2000,
    To assign more than one company code to one controlling area the below are conditions
    1) The Operative fiscal year variants in the company codes must match the fiscal year variant in controlling area.
    2) The company codes must use the same chart of accounts.
    So  if you are assigning other fiscal year variant where the number of posting periods are different, hece system giving an error.
    Thanks and Regards
    A.Rama Krishna

  • One Controlling Area for Two CoCds with different Fiscal Year variant

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

    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.

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

    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

Maybe you are looking for