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
Thanks
Anup

Hi,
the best documentation is the <a href="http://help.sap.com/erp2005_ehp_02/helpdata/en/da/6ada3889432f48e10000000a114084/frameset.htm">online documentation at help.sap.com</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
Csaba

Similar Messages

  • Funds Management and Fiscal Year Variant Change

    Hello !
    We are configuring a new fiscal year variant.
    Currently, the system is on a CALENDAR YEAR FY variant and we are doing the following:
    1. creating a shortened FY of Jan 2009 - Mar 2009
    2. new fiscal year from April 2009 - Mar 2010
    We are trying to change the FY variant for Funds Management via OF15 but receive the error FI674.
    FI674:
    You must not change the fiscal year variant in Cash Budget Management or Funds Management for FM area FM01 if actual data already exists for FM area FM01, or if one or more of the company codes assigned to FM area FM01 is active.
    We have found oss note 719597 which details how to change the FY variant for Cash Budget Mgmt, but it does not apply to Funds management.
    I could find no other supporting documentation.
    Can anyone guide us as to how to deal with this issue?
    Thank=you !

    Hello Patti,
    The point is that it is not possible to change fiscal year variant if actual values exists.
    You are trying to do a change in January. You probably have some postings in 2009 already.
    In the area of PSM-FM there is no note like 719597 of TR-CB.
    Only if no actual values exist, this customizing change would be possible and reasonable.
    If you are doing this setting in your customizing client, you can delete the postings (please DO NOT do it if you are in production) that exist in 2009 and try again.
    SAP do not recommend to change a Fiscal Year Variant that has already been assigned to a company code and has already some postings. This may  create database inconsistencies.
    You can create another Fiscal Year Variant with the information that you want to be customize, and this variant you will be able to assign to a company code. Before you assign this new variant to a company
    code please be sure that none of the information that you already posted in this company code will be affected, this information you may review it with your consultant on-site.
    Also please review/apply note 173636, 202687, 10945, 193713, 123026, 210861 which may happen in your system.
    The fiscal period is related to the posting date via the fiscal year variant. E.g.: I you do a posting on 5.5.2009 it will be posted e.g. in period 5 for fiscal year variant 'A'. This period is not only used in the document header table (BKPF,VBRK,MKPF ...) but also in several balance table (GLT0, KNC1 ...) not only in FI but also in SD, MM, CO .... If in the new  fiscal year variant 'B' this posting date is related to another period e.g. 7 the relation between documents and Periods and balances will be destroyed.
    The problem will be enhanced if the posting-date would be related to diffrent fiscal years.
    In addition several reports in AP/AR and GL reread period-depend data by selecting the posting-date regardless of the period in the document because it's not normal practise to change the fiscal year variant of a company code.
    Some of the involved issues are:
    - FM actuals and commitments may need to be reconstructed if their period- (or even fiscal year-) assignments is changed.
    - FM actuals/commitments can not be reconstructed if fiscal year change activities have already been performed (commitment carry forward, FMJ1, FMJ2).
    - Budgeting data and assigned values may principally be concerned as well, especially if you are working with period values in budgeting.
    The change of fiscal year variant has several implications and should be analyzed very carefully.
    Please check note below for more information:
    Note 672255 Shortened fiscal year / changing fiscal periods
    I hope it helps you and good luck
    Best Regards,
    Vanessa.

  • 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

  • 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

  • How To Customise Fiscal Year Variant

    Dear SAP Gurus,
    I have attempted to create a new FI Posting Period where the first day of the period is on the 16th of the month while the
    last day of the period is on the 15th of the next month.
    For example, my first day of the 1st period is on 16th March and last day of the 1st period is on 15th of April.
    For this, I have configured as follows:
    Month : 4
    Day : 15
    Period : 1
    Year Shift : 0
    I configured the rest of the periods with similar attributes and for the12th period, I configured as follows:
    Month : 3
    Day : 15
    Period : 12
    Year Shift : -1
    However upon saving the Customised Fiscal Year Variant, there is an error message that prompts the vairaint is incomplete
    and that the last day of the posting period is not specified.
    Kindly advise how can this be done, dear Gurus out there.
    Thanks~!

    Hi,
    Please check the below link:
    http://help.sap.com/saphelp_46c/helpdata/en/96/8b2fc843ce11d189ee0000e81ddfac/content.htm
    Thanks
    Neel

  • Interpretation of Fiscal year variant

    Hello Experts,
    Ok, using the Tcode OB29, I could see the fiscal year variant K4, K6,  K7 as follows:
    Variant----Yr Dependent--Calendar Yr--Posting Periods----Special Per.
    K4----
    Unchecked----
    Checked----
    4----
    2        
    K6----
    checked----
    Unchecked-----4--
    2        
    K7----
    Unchecked----
    Unchecked-----4--
    2        
    In went into the details of the “Change View” of K6  and K7 and it shows:
    Month----
    Day----
    Period----
    Year Shift
    1----
    31----
    7----
    0
    2----
    28----
    8----
    0
    3----
    31----
    9----
    0
    4----
    30----
    10----
    0
    5----
    31----
    11----
    0
    6----
    30----
    12----
    0
    7----
    31----
    1----
    +1
    8----
    31----
    2----
    +1
    9----
    30----
    3----
    +1
    10----
    31----
    4----
    +1
    11----
    30----
    5----
    +1
    12----
    31----
    6----
    +1
    1. Can you help me interpret the second table and how it relates to the K6 row in the first table?
    2. In particular, I will appreciate some clarification on the Year shift and in the column period, why it started from 7; and why after 12, it switched to 1.
    4. Can you give a reason why in some cases K6 will be used while in others K7  or K4 will be used.
    3. Also, some help I’ve gotten so far were suggesting that to modify the variant I go to:
    AC Financials ® FI Financial Accounting &#61614; General Ledger Accounting ® FI - Closing and Reporting ® Fiscal Year.
    I could not find this instruction under BW. Was it some R3 instruction of BW?

    Hi,
    I believe the "year shift" column is meant for the non-calendar fiscal year.
    eg in a Calender year  
    Jan  Feb  Mar  Apr  May  Jun
    Fiscal year definition
    Period
    10   11   12   1    2    3
    Year Displacement
    -1   -1   -1   0    0    0
    It is just telling the system that when it is eg 21 Jan 2006, the fiscal year to be captured will be FY 2005.  When it turns 01 Apr 2006, the FY will be 2006.
    In your eg, it is following the logic that when it is 01 June 2006 the FY will be 2006. But when it turns 01 July 2006 the FY will be captured as 2007.
    By the way, the special periods are meant for capturing adjustment.
    For more information on the year shift, please see
    http://help.sap.com/saphelp_46c/helpdata/en/96/8b2fc843ce11d189ee0000e81ddfac/content.htm
    In BW, these are considered the basic settings, alongside with the currency definition.  Go into SBIW in BW to see the basic settings for currencies and fiscal variant defined.  Usually when the BW system is set up, these 2 settings will be read into the system as part of the initial configuration.
    Cheers,
    Gim

Maybe you are looking for

  • Legacy Data Migration - GL Open Items

    Source : SAP R/3 Target : SAP ECC Data to be moved : GL Open Items We need to migrate our Legacy data into SAP ECC. Tel me the efficient way to do data transfer. Any standard programs available for this ? Or any technique should I have to follow for

  • Naming of my SOA Composite Application ? (EBF, ABCS...)

    Hi all I have created a SOA composite application that uses a dbAdapter to poll data from a database and that processes these data in a BPEL process. The BPEL process transforms the data, then calls other dbAdapters to perform business tasks. I'd lik

  • When I back up on my exertnal HD drive with time machine can I erase what on my computer HD for more space?

    When I back up files on my exertnal HD drive with time machine can I erase what's on my Mac HD for space without losing what's on external HD?

  • Address change to trigger new price in Sales Order

    I need to have a re-price triggered every time an address has been changed in the sales order.  The userexits in MV45AFZB USEREXIT_NEW_PRICING_VBAP and USEREXIT_NEW_PRICING_VBKD aren't triggered when an address is changed, only when the partner itsel

  • VGA Display problem on Mac 10.6.8

    I have Mac 10.6.8 and I'm trying to play a powerpoint slideshow on a tv. The VGA cable is setup but whenever I try to start slideshow both screens go blue and I have to restart my computer. This also happened when I tried to change the display settin