Planning Fiscal Year Problem

Hi All,
Our Fiscal Year starting from Apr(Q1) to Mar(Q4), our forecast is actual+estimated
i.e., Forecast of YearTotal=Jan->&LastYr + Feb->&LastYr + Mar->&LastYr + Apr + May + Jun + Jul + Aug + Sep + Oct + Nov + Dec of Actual+Estimated
How to handle the situtaion.
Thanks in Advance,

Here you go:
Rolling Forecast Form Designing (column Duplication in Data form)
Re: Rolling forecast
Cheers,
Alp

Similar Messages

  • Due to shortend fiscal year problem in depre amounts.

    Dear All,
    Due to shortend fiscal year (apr07-mar08)  we are facing Depre calculation problem.
    1)       There are no errors in AFAB & AW01N.  Itu2019s showing   balance 3 (jan07,feb07,mar07)months depre in AFAB u201CTo Postu201D column.
    2)  User doesnu2019t want to post the balance 3 months depre and they wants to carry forward for the next financial years continuously. But here the problem is before recalculate assets the difference is only 35 $, but after SAP suggested to Recalculate assets before depre run that is run AFAR then run AFAB they found that the amount is 31000+. Which canu2019t carry forward such a big amount? 
    Pls help us to resolve this issue.
    Thanks & Regards,
    Usha

    Since you are on BPC 5.1, I don't believe you can take advantage of multiple hierarchies within the Time Dimension.  So, I would create a report rendering the information you need, with the columns being fixed using properties and EVTIM.  The values for the quarterly and yearly levels would be sums instead of retrievals from the database.

  • Fiscal year problem

    hi kings
    we are using payroll add on. query generator parameter field have problem.when i run the query for last year April(2008) to this year march(2009).its retrieve the o records..
    here i paste my query
    SELECT T0.[U_Year], T0.[U_Month] FROM [dbo].[@BIZ_PSAL]  T0 WHERE T0.[U_Month] >=[%0] and  T0.[U_Month] <=[%1] and T0.[U_Year] >=[%2] and  T0.[U_Year] <=[%3]
    first parameter field passing month---- 4
    second parameter field passing month---- 3
    Third parameter field passing month---- 2008
    fourth parameter field passing month---- 2009
    Thanks & Best Regards
    B.Lakshmi Narayanan

    hi lakshmi naryanan,
    Run this query with input parameters firstly (due to selection creteria with >= and <=)
    first parameter field passing month---- 4
    second parameter field passing month---- 12
    Third parameter field passing month---- 2008
    fourth parameter field passing month---- 2008
    Run this query with input parameters secondly
    first parameter field passing month---- 1
    second parameter field passing month---- 3
    Third parameter field passing month---- 2009
    fourth parameter field passing month---- 2009
    Edited by: Jeyakanthan A on May 25, 2009 10:59 AM

  • The error showing as Fiscal year change has not carried out for the coCd

    Hi all,
    I am facing a very critical situation. My client has the last closed fiscal year as 2006(from 2006 april to 2007 march).For the fiscal yr. 2007(2007april to 2008 march) they have already finalised and submitted the reports made from some parallel software.They now want to tally this report with SAP system and to adjust the SAP system entries as per this report.This work was running fine.But on 01.04.2009 none of the asset reports are running.The error it's throwing is as-
    Fiscal year change not yet made for company code PWAL
    Message no. AB059
    Diagnosis
    You have not yet carried out a fiscal year change for company code PWAL, although the current system date is in the new fiscal year.
    Procedure
    Carry out the fiscal year change for company code PWAL.
    Proceed
    The error is quite understandable.We have to close 2007 and then perform the fiscal year change.But the problem is that the adjustment for the year 2007 is not yet complete.Is it the only solution with me that I should close the yr.2007 and again open it after the fiscal yr. change? If that is done can I take care of the adjustment in the posted depreciation? Or is it possible that the system date can be made back to 31.03.2009(very stupid ask!). The real problem is that my client has mistakely created some assets in the year 2007(by AS91 after changing the take over date) those should have been shown in the next year and also some assets are creted in the year 2008 by the same strange method those should be shown in the year 2007.What I am doing now is deleting these legacy assets and creating the new assets in the correct year.And this process is not yet complete.If I close the year 2007, then the depreciation of these legacy assets will also be posted.Later how can I reverse the effect?Also without seeing the reports I can't make the adjustments.Please suggest/advice.
    Debabrata

    Hi Debabrata,
    You have to do all fiscal year closing steps for 2007. When you reopen it you can do a repeat run for 2007. (You can do the reapeat run only for the new/ changed assets.)
    Try first to test this in an actual test system (document it and do the same in production). Perhaps as you know when 2009 is open I want to close 2008 in one week.  All changes they make in the asset system (change depreciation keys, recalulating,...) can result in postings in 2007 / 2008 what they don't want and later fiscal year problems. You will found a lot off masages about this on the form.

  • Asset still showing planned  value for closed fiscal year.

    *We have a situation:-  After we ran depreciation for Dec 2009, there was a credit memo posting done in the system for a particular asset.  Now, the fiscal year has been closed for 2009 and 2010 is opened. Jan and Feb depreciation posting has been done for the asset for year 2010, but the credit memo posting is still stuck as planned value in the 12th period of 2009. How can we take care of that?  I canu2019t run unplanned depreciation for 2009. Is there a better way to take care of this?  I thought about opening year 2009 for the asset (ccode) and then running unplanned depreciation. Will that be a problem? If yes, what other solution can be proposed.*
    *Appreciate the response.*

    Hi,
    If it is not possible to open the fiscal year because audit          
    has already been completed we have a workaround which is not quite   
    correct from the legal side ist thereport RACORR20_A from note 29694.
    If in table ANLC there are differences between posted and planed     
    depr. the report simply makes: planed = posted.  
    The correct way would be:
    ->  Reopen your GL for FY 2008 via OB52.      
    ->  Recalculate values  (RAAFAR00)                                  
    ->  RAPOST2000                                
    ->  RAPERB2000                                
    ->  RAJABS00                                  
    Regards Bernhard

  • Planned dep in closed fiscal year

    Hi
    We have done a change(reduced the useful life) in the useful life of the asset in the Fiscal year 2009 in the  month of June,which impacted the  previous year depreciation amount.The planned  dep value got increased in december 2008 .In the posted value tab in asset explorer for year 2008 it displays the planned dep in dec 2008 which is not yet posted.We donot need this depreciation to be posted.We need to delete the planned dep.Financial year and Asset year till 2009 are closed.
    Please advice how to get the planned dep line removed from year 2008 which effects the net book value.

    Hi,
    Are you absolutely sure the changes were made when the fiscal year was closed. Maybe you need to also check if the depreciation area(s) affected was/were open at the time (OAAR). It should not be possible: if the fiscal year and all depreciation areas are closed, changing the useful life should not affect these closed years/depr.areas.
    Changes to depreciation conditions (e.g.useful life, dep.key) only affect the planned depreciation in open fiscal years. There is no specific transaction.
    The adjustment for the depreciation of the closed fiscal year will be reflected in an adjustment posting in the next period due for depreciation posting in a catch-up posting (or smoothing if indicated). For the open fiscal years the newly calculated depreciation will be distributed equally over the remaining useful life.
    Therefore it sound to me very peculiar that planned depreciation should have been created in your closed fiscal year due to a change of useful life. Please review your change documents to ensure depreciation areas and fiscal  years were closed at time of change u2013 and have not been reopened either via OAAR or OAAQ.
    To answer your last question regarding if change of useful life will affect deprecation in 2010:  provided that it is the only open fiscal year and is in fact the current fiscal year, then yes, it will affect the planned depreciation in 2010 and in the remaining useful life.
    Kind regards,
    Brigitte

  • Validation(in the planning function) is failing to read fiscal year

    Gurus,
    We created a fox formula in the planning function for validating budget data so that users do not profile above the allowed budget. We declared variables correctly as follows:
    **Declare variables*
    **++++++++++++++++++++++*
    *DATA CURRBUD TYPE F.*
    *DATA DIFF TYPE F.*
    *DATA HEADF TYPE F.*
    *DATA FUNDF TYPE F.*
    *DATA FUNDFX TYPE F.*
    *DATA HEADF1 TYPE F.*
    *DATA HEADF2 TYPE F.*
    *DATA HEADF3 TYPE F.*
    *DATA HEADFX TYPE F.*
    *DATA FUNDF1 TYPE F.*
    *DATA FUNDF2 TYPE F.*
    *DATA FUNDF3 TYPE F.*
    *DATA FUNDF4 TYPE F.*
    *DATA FUNDF5 TYPE F.*
    *DATA FUNDF6 TYPE F.*
    *DATA FUNDF7 TYPE F.*
    *DATA FUNDF8 TYPE F.*
    *DATA FUNDF9 TYPE F.*
    *DATA FUNDF10 TYPE F.*
    *DATA FUNDF11 TYPE F.*
    *DATA FUNDF12 TYPE F.*
    *DATA KVERSION TYPE 0VERSION.*
    *DATA KYEAR TYPE 0FISCYEAR.*
    *DATA KGRZHEAD TYPE ZGRZ_HEAD.*
    *DATA PAREA TYPE AREA____.*
    *FOREACH KGRZHEAD, KYEAR.*
    **Original Budget*
    *HEADF1 = {0AMOUNT,KYEAR,CRBU,0,KGRZHEAD,FUNDPROF }.*
    **Supplementary Budget*
    *HEADF2 = {0AMOUNT,KYEAR,CRBU,SUP,KGRZHEAD,FUNDPROF }.*
    **Returns Budget*
    *HEADF3 = {0AMOUNT,KYEAR,CRBU,RET,KGRZHEAD,FUNDPROF }.*
        *HEADFX = HEADF1 + HEADF2 - HEADF3.*
      *FUNDFX =*
    *{0AMOUNT,KYEAR,HEAD,0,KGRZHEAD,FUNDPROF}.*
    FUNDFX = FUNDFX + FUNDF.**
    *ENDFOR.*
    **Calculate the Difference between the Approved budget*
    **And the Funding profile amount for the year*
    **++++++++++++++++++++++++++++++++++++++++++++++++++*
    *DIFF = HEADFX - FUNDFX.*
       *IF DIFF > 0.*
          *MESSAGE I025(ZGRZ) WITH  KGRZHEAD HEADFX FUNDFX DIFF.*
      *ELSEIF DIFF  < 0.*
         *MESSAGE E026(ZGRZ) WITH  KGRZHEAD DIFF HEADFX FUNDFX .*
      *ELSEIF DIFF = 0.*
         *MESSAGE W027(ZGRZ) WITH  KGRZHEAD HEADFX FUNDFX.*
      *ELSE.*
         *MESSAGE E028(ZGRZ)WITH KGRZHEAD.*
         *EXIT.*
    ENDIF.
    A variable FYEAR has been created for characteristic 0FISCYEAR. This formula has been working correctly last year but when we changed the variable to point to 2011, for this year, it refuses to read that variable. The system is giving the followign error message:
    Value of variable Fiscal year (FYEAR) cannot be determined
    This only experienced in production, but in Develoment and QAS the function is working properly.
    Kindly assist,
    Tatenda
    K
    Edited by: tatenda chigwedere on Jan 4, 2011 4:13 PM

    Hi,
    I think you are talking about IP / BPS. Please post your thread to the relevant forum. This forum is for BPC on NW platform.

  • Job gets cancelled - Plan version cannot be planned for fiscal year

    hello,
    In R/3, I am trying to delete data using KEPM TCODEand the job gets cancelled with message "Plan version cannot be planned for fiscal year".
    Does anyone know what I should do to resolve it.
    thanks,
    Bhat

    Hello,
    Thanks for your response.
    I have checked OKEQ and
    we have entries for fiscal year planning version and in operating concern the version is locked. I don't know if I should unlock the version and what will be the impact.
    thanks,
    Bhat

  • Problem in fiscal year

    Hi all,
    When i'm maintain material at company code using omsy transaction code, i unable to maintain the fiscal year of previous period like year and month in those fields and system showing those fields inactive(grey mode). Could you tell me how to maintain values in those fields. Please reply me as early as possible.
    Thanks & warm regards
    kesav

    Hi kesav
    You cannnot change directly in OMSY. It has to be in sync with MMRV/MMPV.
    First you check your current period in MMRV and accordingly open/close your
    period in MMPV. This way your fiscal  year issue will get solved. Hope it will
    help you.
    Thanks
    Sushant

  • Asset Aquisition report date problem in indian fiscal year style  (urgent)

    hi all genius there,
    i am developing asset aquisiton report in which i should get
    the record of asset depending on indian fiscal year (1st april to 31st march).
    so that means if i enter 31.03.2006 then i should get all the asset records
    from 01.04.2005 to 31.03.2006.
    how to do it. its very urgent. plz if aany one has done this scenario for
    asset aquisition report then plz send me the code.
    my id is- [removed by moderator]
    or otherwise i am sending my code plz check it and do the modification to get the above requirement.
    REPORT Z_FA_ACQ  NO STANDARD PAGE HEADING
                     LINE-SIZE 400
                     LINE-COUNT 65(3).
    TYPE-POOLS : SLIS.
    TABLES : ANLA,                         "ASSET MASTER RECORD-SEGMENT
             ANLZ,                         "time dependent asset allocations
             ANLC,
             ANEK.
    DATA : BEGIN OF T_ANLA OCCURS 0,
           BUKRS LIKE ANLA-BUKRS,
           ANLN1 LIKE ANLA-ANLN1,
           ANLN2 LIKE ANLA-ANLN2,
           AKTIV LIKE ANLA-AKTIV,
           TXT50 LIKE ANLA-TXT50,
           ZUGDT LIKE ANLA-ZUGDT,
           MENGE LIKE ANLA-MENGE,
           MEINS LIKE ANLA-MEINS,
           ANLKL LIKE ANLA-ANLKL,
           END OF T_ANLA.
    DATA : BEGIN OF T_ANLZ OCCURS 0,
           BUKRS LIKE ANLZ-BUKRS,
           ANLN1 LIKE ANLZ-ANLN1,
           ANLN2 LIKE ANLZ-ANLN2,
           GSBER LIKE ANLZ-GSBER,
           KOSTL LIKE ANLZ-KOSTL,
           STORT LIKE ANLZ-STORT,
           RAUMN LIKE ANLZ-RAUMN,
           KFZKZ LIKE ANLZ-KFZKZ,
           WERKS LIKE ANLZ-WERKS,
           END OF T_ANLZ.
    DATA : BEGIN OF T_ANEK OCCURS 0,
           BUKRS LIKE ANEK-BUKRS,
           ANLN1 LIKE ANEK-ANLN1,
           ANLN2 LIKE ANEK-ANLN2,
           BELNR LIKE ANEK-BELNR,
           BUDAT LIKE ANEK-BUDAT,
           XBLNR LIKE ANEK-XBLNR,
           SGTXT LIKE ANEK-SGTXT,
           GJAHR LIKE ANEK-GJAHR,
          pdate LIKE anek-budat, " modified by sanjeev for date logic
           END OF T_ANEK.
    DATA : BEGIN OF T_ANLC OCCURS 0,
           BUKRS LIKE ANLC-BUKRS,
           ANLN1 LIKE ANLC-ANLN1,
           ANLN2 LIKE ANLC-ANLN2,
           ANSWL LIKE ANLC-ANSWL,
           NAFAP LIKE ANLC-NAFAP,
           AAFAP LIKE ANLC-AAFAP,
           AFABE LIKE ANLC-AFABE,
           GJAHR LIKE ANLC-GJAHR,
           END OF T_ANLC.
    DATA : BEGIN OF IT_FINAL OCCURS 0,
            ANLN1 LIKE ANLA-ANLN1,
            ANLN2 LIKE ANLA-ANLN2,
            AKTIV LIKE ANLA-AKTIV,
            TXT50 LIKE ANLA-TXT50,
            ZUGDT LIKE ANLA-ZUGDT,
            MENGE LIKE ANLA-MENGE,
            MEINS LIKE ANLA-MEINS,
            GSBER LIKE ANLZ-GSBER,
            KOSTL LIKE ANLZ-KOSTL,
            STORT LIKE ANLZ-STORT,
            RAUMN LIKE ANLZ-RAUMN,
            KFZKZ LIKE ANLZ-KFZKZ,
            BELNR LIKE ANEK-BELNR,
            BUDAT LIKE ANEK-BUDAT,
          pdate LIKE anek-budat,
            XBLNR LIKE ANEK-XBLNR,
            SGTXT LIKE ANEK-SGTXT,
            ANSWL LIKE ANLC-ANSWL,
            NAFAP LIKE ANLC-NAFAP,
            AAFAP LIKE ANLC-AAFAP,
            GJAHR LIKE ANEK-GJAHR,
            ANLKL LIKE ANLA-ANLKL,
            END OF IT_FINAL.
    DATA: PDATE LIKE ANEK-BUDAT.
    PDATE = SY-DATUM.
    DATA:V_LOW LIKE SY-DATUM,
        V_HIGH LIKE SY-DATUM,
        V_DATE(04) TYPE N,
        V_YEAR(04) TYPE N.
    V_YEAR = V_DATE(04).
    V_YEAR = V_YEAR - 1.
    CONCATENATE V_YEAR '0401' INTO V_LOW.
    CLEAR V_YEAR.
    V_YEAR = V_DATE(04).
    CONCATENATE V_YEAR '0331' INTO V_HIGH.
    DATA : LINE_COLOR(4) TYPE C.
    DATA : FIELDCATALOG TYPE SLIS_T_FIELDCAT_ALV WITH HEADER LINE,
           GD_LAYOUT TYPE SLIS_LAYOUT_ALV.
    DATA: EVENT  TYPE SLIS_ALV_EVENT OCCURS 0 WITH HEADER LINE.
    SELECTION-SCREEN : BEGIN OF BLOCK B_FA WITH FRAME TITLE TEXT-001.
    SELECT-OPTIONS : S_BUKRS FOR ANLA-BUKRS DEFAULT 'ML',
                     S_ANLN1 FOR ANLA-ANLN1,
                     S_ANLN2 FOR ANLA-ANLN2,
                     S_ANLKL FOR ANLA-ANLKL,
                     S_AKTIV FOR ANLA-AKTIV,
                     S_GSBER FOR ANLZ-GSBER,
                     S_KOSTL FOR ANLZ-KOSTL,
                     S_WERKS FOR ANLZ-WERKS,
                     S_STORT FOR ANLZ-STORT,
                   S_BUDAT FOR ANEK-BUDAT,
                     S_GJAHR FOR ANEK-GJAHR.
    SELECTION-SCREEN : END OF BLOCK B_FA.
    *PARAMETERS : budat LIKE anek-budat.
    SET PF-STATUS '100'.
    SELECT BUKRS ANLN1 ANLN2 AKTIV TXT50 ZUGDT MENGE MEINS ANLKL
           FROM ANLA
           INTO CORRESPONDING FIELDS OF TABLE T_ANLA
           WHERE ANLN1 IN S_ANLN1
           AND   ANLN2 IN S_ANLN2
           AND   BUKRS IN S_BUKRS
           AND   ANLKL IN S_ANLKL
           AND   AKTIV IN S_AKTIV.
    CHECK : NOT T_ANLA[] IS INITIAL.
    SELECT BUKRS ANLN1 ANLN2 GSBER KOSTL STORT RAUMN KFZKZ
           FROM ANLZ
           INTO CORRESPONDING FIELDS OF TABLE T_ANLZ
           FOR ALL ENTRIES IN T_ANLA
           WHERE ANLN1 = T_ANLA-ANLN1
           AND   ANLN2 = T_ANLA-ANLN2
           AND   BUKRS = T_ANLA-BUKRS
           AND   GSBER NOT IN S_GSBER
           AND   KOSTL IN S_KOSTL
           AND   WERKS IN S_WERKS.
    SELECT BUKRS ANLN1 ANLN2 BELNR BUDAT XBLNR SGTXT GJAHR
           FROM ANEK
           INTO CORRESPONDING FIELDS OF TABLE T_ANEK
           FOR ALL ENTRIES IN T_ANLA
           WHERE ANLN1 = T_ANLA-ANLN1
           AND   ANLN2 = T_ANLA-ANLN2
           AND   BUKRS = T_ANLA-BUKRS
           AND   BUDAT >= V_LOW
           AND   BUDAT <= V_HIGH.
          AND  gjahr IN s_gjahr. " modified for date logic by Sanjeev
    SELECT BUKRS ANLN1 ANLN2 ANSWL NAFAP AAFAP AFABE GJAHR
           FROM ANLC
           INTO CORRESPONDING FIELDS OF TABLE T_ANLC
           FOR ALL ENTRIES IN T_ANLA
           WHERE ANLN1 = T_ANLA-ANLN1
           AND   ANLN2 = T_ANLA-ANLN2
           AND   BUKRS = T_ANLA-BUKRS
           AND   AFABE = '01'.
    LOOP AT T_ANLA.
      MOVE : T_ANLA-ANLN1 TO IT_FINAL-ANLN1,
             T_ANLA-ANLN2 TO IT_FINAL-ANLN2,
             T_ANLA-AKTIV TO IT_FINAL-AKTIV,
             T_ANLA-TXT50 TO IT_FINAL-TXT50,
             T_ANLA-ZUGDT TO IT_FINAL-ZUGDT,
             T_ANLA-MENGE TO IT_FINAL-MENGE,
             T_ANLA-MEINS TO IT_FINAL-MEINS.
      READ TABLE T_ANLZ WITH KEY BUKRS = T_ANLA-BUKRS
                                 ANLN1 = T_ANLA-ANLN1
                                 ANLN2 = T_ANLA-ANLN2 BINARY SEARCH.
      IF SY-SUBRC EQ 0.
        MOVE : T_ANLZ-GSBER TO IT_FINAL-GSBER,
               T_ANLZ-KOSTL TO IT_FINAL-KOSTL,
               T_ANLZ-STORT TO IT_FINAL-STORT,
               T_ANLZ-RAUMN TO IT_FINAL-RAUMN,
               T_ANLZ-KFZKZ TO IT_FINAL-KFZKZ.
      ENDIF.
      READ TABLE T_ANLC WITH KEY BUKRS = T_ANLA-BUKRS
                                 ANLN1 = T_ANLA-ANLN1
                                 ANLN2 = T_ANLA-ANLN2 BINARY SEARCH.
      IF SY-SUBRC EQ 0.
        MOVE : T_ANLC-ANSWL TO IT_FINAL-ANSWL,
               T_ANLC-NAFAP TO IT_FINAL-NAFAP,
               T_ANLC-AAFAP TO IT_FINAL-AAFAP.
      ENDIF.
    LOOP AT T_ANEK WHERE BUKRS = T_ANLA-BUKRS AND ANLN1 = T_ANLA-ANLN1 AND
        ANLN2 = T_ANLA-ANLN2 AND   BUDAT >= V_LOW
                                 AND   BUDAT <= V_HIGH AND BUDAT IN S_BUDAT.
        MOVE : T_ANEK-BELNR TO IT_FINAL-BELNR,
               T_ANEK-BUDAT TO IT_FINAL-BUDAT,
               T_ANEK-GJAHR TO IT_FINAL-GJAHR,
               T_ANEK-XBLNR TO IT_FINAL-XBLNR,
               T_ANEK-SGTXT TO IT_FINAL-SGTXT.
        APPEND IT_FINAL.
      ENDLOOP.
    ENDLOOP.
    PERFORM BUILD_FIELDCATALOG.
    PERFORM DISPLAY_ALV_REPORT.
    PERFORM BUILD_LAYOUT.
          FORM BUILD_FIELDCATALOG                                       *
    FORM BUILD_FIELDCATALOG.
      FIELDCATALOG-FIELDNAME = 'ANLN1'.
      FIELDCATALOG-SELTEXT_M = 'ASSET MAIN NO'.
      FIELDCATALOG-COL_POS   = 0.
      FIELDCATALOG-OUTPUTLEN = 14.
      FIELDCATALOG-EMPHASIZE = 'X'.
      FIELDCATALOG-KEY       = 'X'.
      APPEND FIELDCATALOG TO FIELDCATALOG.
      CLEAR FIELDCATALOG.
      FIELDCATALOG-FIELDNAME = 'ANLN2'.
      FIELDCATALOG-SELTEXT_M = 'SUB NO'.
      FIELDCATALOG-COL_POS   = 1.
      FIELDCATALOG-OUTPUTLEN = 7.
      APPEND FIELDCATALOG TO FIELDCATALOG.
      CLEAR FIELDCATALOG.
      FIELDCATALOG-FIELDNAME = 'AKTIV'.
      FIELDCATALOG-SELTEXT_M = 'CAP.DATE'.
      FIELDCATALOG-COL_POS   = 2.
      FIELDCATALOG-OUTPUTLEN = 10.
      APPEND FIELDCATALOG TO FIELDCATALOG.
      CLEAR FIELDCATALOG.
      FIELDCATALOG-FIELDNAME = 'TXT50'.
      FIELDCATALOG-SELTEXT_M = 'NAME'.
      FIELDCATALOG-COL_POS   = 3.
      FIELDCATALOG-OUTPUTLEN = 50.
      APPEND FIELDCATALOG TO FIELDCATALOG.
      CLEAR FIELDCATALOG.
      FIELDCATALOG-FIELDNAME = 'ZUGDT'.
      FIELDCATALOG-SELTEXT_M = 'POSTING DATE'.
      FIELDCATALOG-COL_POS   = 4.
      FIELDCATALOG-OUTPUTLEN = 10.
      APPEND FIELDCATALOG TO FIELDCATALOG.
      CLEAR FIELDCATALOG.
      FIELDCATALOG-FIELDNAME = 'MENGE'.
      FIELDCATALOG-SELTEXT_M = 'QTY'.
      FIELDCATALOG-COL_POS   = 5.
      FIELDCATALOG-OUTPUTLEN = 13.
      APPEND FIELDCATALOG TO FIELDCATALOG.
      CLEAR FIELDCATALOG.
      FIELDCATALOG-FIELDNAME = 'MEINS'.
      FIELDCATALOG-SELTEXT_M = 'UNITS'.
      FIELDCATALOG-COL_POS   = 6.
      FIELDCATALOG-OUTPUTLEN = 3.
      APPEND FIELDCATALOG TO FIELDCATALOG.
      CLEAR FIELDCATALOG.
      FIELDCATALOG-FIELDNAME = 'GSBER'.
      FIELDCATALOG-SELTEXT_M = 'BA'.
      FIELDCATALOG-COL_POS   = 7.
      FIELDCATALOG-OUTPUTLEN = 4.
      APPEND FIELDCATALOG TO FIELDCATALOG.
      CLEAR FIELDCATALOG.
      FIELDCATALOG-FIELDNAME = 'KOSTL'.
      FIELDCATALOG-SELTEXT_M = 'COST CENTER'.
      FIELDCATALOG-COL_POS   = 8.
      FIELDCATALOG-OUTPUTLEN = 13.
      APPEND FIELDCATALOG TO FIELDCATALOG.
      CLEAR FIELDCATALOG.
      FIELDCATALOG-FIELDNAME = 'STORT'.
      FIELDCATALOG-SELTEXT_M = 'LOCATION'.
      FIELDCATALOG-COL_POS   = 9.
      FIELDCATALOG-OUTPUTLEN = 10.
      APPEND FIELDCATALOG TO FIELDCATALOG.
      CLEAR FIELDCATALOG.
      FIELDCATALOG-FIELDNAME = 'RAUMN'.
      FIELDCATALOG-SELTEXT_M = 'ROOM'.
      FIELDCATALOG-COL_POS   = 10.
      FIELDCATALOG-OUTPUTLEN = 10.
      APPEND FIELDCATALOG TO FIELDCATALOG.
      CLEAR FIELDCATALOG.
      FIELDCATALOG-FIELDNAME = 'KFZKZ'.
      FIELDCATALOG-SELTEXT_M = 'LICENSE PLATE NO'.
      FIELDCATALOG-COL_POS   = 11.
      FIELDCATALOG-OUTPUTLEN = 20.
      APPEND FIELDCATALOG TO FIELDCATALOG.
      CLEAR FIELDCATALOG.
      FIELDCATALOG-FIELDNAME = 'BELNR'.
      FIELDCATALOG-SELTEXT_M = 'DOC NO'.
      FIELDCATALOG-COL_POS   = 12.
      FIELDCATALOG-OUTPUTLEN = 13.
      APPEND FIELDCATALOG TO FIELDCATALOG.
      CLEAR FIELDCATALOG.
      FIELDCATALOG-FIELDNAME = 'BUDAT'.
      FIELDCATALOG-SELTEXT_M = 'POSTING DATE'.
      FIELDCATALOG-COL_POS   = 13.
      FIELDCATALOG-OUTPUTLEN = 15.
      APPEND FIELDCATALOG TO FIELDCATALOG.
      CLEAR FIELDCATALOG.
      FIELDCATALOG-FIELDNAME = 'XBLNR'.
      FIELDCATALOG-SELTEXT_M = 'REF NO'.
      FIELDCATALOG-COL_POS   = 14.
      FIELDCATALOG-OUTPUTLEN = 25.
      APPEND FIELDCATALOG TO FIELDCATALOG.
      CLEAR FIELDCATALOG.
      FIELDCATALOG-FIELDNAME = 'SGTXT'.
      FIELDCATALOG-SELTEXT_M = 'TEXT'.
      FIELDCATALOG-COL_POS   = 15.
      FIELDCATALOG-OUTPUTLEN = 50.
      APPEND FIELDCATALOG TO FIELDCATALOG.
      CLEAR FIELDCATALOG.
      FIELDCATALOG-FIELDNAME = 'ANSWL'.
      FIELDCATALOG-SELTEXT_M = 'ACQ VAL'.
      FIELDCATALOG-COL_POS   = 16.
      FIELDCATALOG-OUTPUTLEN = 13.
      APPEND FIELDCATALOG TO FIELDCATALOG.
      CLEAR FIELDCATALOG.
      FIELDCATALOG-FIELDNAME = 'NAFAP'.
      FIELDCATALOG-SELTEXT_M = 'ORD.DEP'.
      FIELDCATALOG-COL_POS   = 17.
      FIELDCATALOG-OUTPUTLEN = 13.
      APPEND FIELDCATALOG TO FIELDCATALOG.
      CLEAR FIELDCATALOG.
      FIELDCATALOG-FIELDNAME = 'AAFAP'.
      FIELDCATALOG-SELTEXT_M = 'UNPLAN DEP'.
      FIELDCATALOG-COL_POS   = 18.
      FIELDCATALOG-OUTPUTLEN = 13.
      APPEND FIELDCATALOG TO FIELDCATALOG.
      CLEAR FIELDCATALOG.
    ENDFORM.
    PERFORM ALVDISPLAY.
    FORM ALVDISPLAY.
    EVENT-FORM = 'USERCOMMAND'(002).
    EVENT-NAME = 'USER_COMMAND'(001).
    APPEND EVENT.
    ENDFORM.
    FORM DOWNLOADEXCEL.
    DATA : B_FILE1 LIKE RLGRAP-FILENAME.
    ENDFORM.
          FORM BUILD_LAYOUT                                             *
    FORM BUILD_LAYOUT.
      GD_LAYOUT-ZEBRA = 'X'.
      GD_LAYOUT-INFO_FIELDNAME = 'LINE_COLOR'.
    ENDFORM.
          FORM DISPLAY_ALV_REPORT                                       *
    FORM DISPLAY_ALV_REPORT.
      CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
          EXPORTING
            I_INTERFACE_CHECK        = ' '
             I_CALLBACK_PROGRAM       = SY-REPID
            i_callback_pf_status_set = 100
            i_callback_user_command  = sy-ucomm
            I_STRUCTURE_NAME         =
             IS_LAYOUT                = GD_LAYOUT
               IT_FIELDCAT              = FIELDCATALOG[]
            IT_EXCLUDING             =
            IT_SPECIAL_GROUPS        =
            IT_SORT                  =
            IT_FILTER                =
            IS_SEL_HIDE              =
            I_DEFAULT                = 'X'
            I_SAVE                   = ' '
            IS_VARIANT               = ' '
            IT_EVENTS                =
            IT_EVENT_EXIT            = EVENT[]
            IS_PRINT                 =
            I_SCREEN_START_COLUMN    = 0
            I_SCREEN_START_LINE      = 0
            I_SCREEN_END_COLUMN      = 0
            I_SCREEN_END_LINE        = 0
       IMPORTING
            E_EXIT_CAUSED_BY_CALLER  =
            ES_EXIT_CAUSED_BY_USER   =
           TABLES
                T_OUTTAB                 = IT_FINAL
           EXCEPTIONS
                PROGRAM_ERROR            = 1
                OTHERS                   = 2.
    ENDFORM.
    Hi,
    we encourage open discussion and no emails, as the answer to your question shall be posted in the forum to be read by other users, who might be interested in it as well.
    Mario

    hi,
    i've tried to correct your code:
    -> v_year, v_low and v_high was not filled
    ...SELECTION-SCREEN : END OF BLOCK b_fa.
    PARAMETERS p_year LIKE anlc-gjahr DEFAULT sy-datum(4).
    *PARAMETERS : budat LIKE anek-budat.
    SET PF-STATUS '100'.
    v_year = p_year.
    v_year = v_year - 1.
    CONCATENATE v_year '0401' INTO v_low.
    CLEAR v_year.
    v_year = p_year.
    CONCATENATE v_year '0331' INTO v_high.
    SELECT bukrs anln1 anln2 aktiv txt50 zugdt menge meins anlkl
    FROM anla
    pls reward useful answers
    thx.
    Andreas

  • Invoice problem. Fiscal Year

    Hello,
    When a case lasts between two fiscal years (It begins before April 30th and ends after May 1st), It is generated two invoices: one dated on April 30th with the services provided until that day and another for the new fiscal year. We need to have only one invoice per case. We seached on the billing parameters and on the Customizing and can't find where to define this.

    Hi, Thanks for your help.
    My coworker found the solution. In order to have only one invoice per case, you have to go to customizing to Set billing parameters in Patient Accounting -> Billing and dismark the checks in Period Split and Revenue Assignment.

  • Asset Legacy dt upld-problem in uploading fiscal year assets without value

    Hi all ,
    I am trying to upload Assets which are pertaining to current Fiscal year and for which no depreciation run is taken place , using Tcode AS91,
    Initially I got error :
    Capitalization date must be earlier than or same as transfer date.
    Then I changed transfer date to  31.03.2009 .
    Now I am getting error  :
    Current fiscal year 2008 has to be after transfer date 31.03.2009 .
    How do I take these Assets with / without values ?
    and if without values , then how can I update Asset values ?
    Regards ,
    Pallavi .

    Hi Ramesh,
    I have same scenaio we are uploading the assets on 30.09.2008, so our data transfer date is same.
    The issue is
    1. When we start AS91 for current year, assets takeover values fields are in display mode.
    System configuration was:-
      A). Legacy data transfer date was 30.09.2008
    B). last period posted in previous system was 6th
    C). capitalized date taken by me is after 31.03.2008 (Note: - when I take capitalization date before 31.03.2008, than system show me take over tab in change mode)
    2). While doing AS92 also system shows me all takeover tab fields in display mode, when I select capitalization date after 31.03.2008.
    The thing is that how we can upload all those assets which we have purchased in the current year and how we will treat with the depreciation in the system
    up to which date we should take accumulated dep for previous year assets.
    please answer if u want i can raise a seprate question.
    Regards

  • Fiscal year /Varient  problem

    Hi All,
    In my query level fiscal year /Varient  showing 002/2010 , i want to modify the result for 002 . my in report level i want to display only period values like(002) how can i do this
    Thanks
    Praveen

    add a field in data model and populate it in field routine like source_fields-fiscper+4(3). You can then add this IO in query.
    or try this
    you can try out with formula variable on date characteristic.
    lets take an example: lets consider 0FISCPER
    drag and drop it into rows of query designer.
    now create a fomula variable (from context menu of KF structure >new formula->right click on formula variable tree-->new variable).
    Properties of formula variable:
    Processing type as 'replacement path',Characteristic:0FISCPER,Replace variable with 'Key',Offset start :4 ,Offset lenght: 3, Dimension ID :Number.
    here assumed that 0FISCPER's internal format is 1999.600 so formula variable returns 600.
    if  format is different,then u have to change offset lenght and offset start accordingly.
    Now create a new formula with this formula variable and set decimal places to 0 in properties.
    Edited by: Ananda Theerthan on Apr 12, 2010 8:58 PM

  • Problem with Fiscal Year/Period

    Hi Expert,
    I am facing an issue with Fiscal year/per in my query. User is running the report on web. When he enters Fiscal year and period in selection screen, the report fetches correct data, however if I go to the information tab, there the value of the fiscal year/per is wrong. e.g. The user enters 010 2007. The report fetches 010.2007 data only but in the information tab, the value of the variable is shown 010.2008
    Please help me in identifying the issue.

    There might be one more variable in the query which is not of type ready for input.
    Fiscal year/per  can be the name of two variables in the query.
    Check in the query if you have one more variable.
    Hope this helps.

  • Fiscal year in the columns outside the key figure structure

    Dear Experts
    I have a report requirement to show the keyfigures in the columns from year 1 to year 10 and in each year there are 4 keyfigures each restricted to 1 quarter for 4 quarters.
    So, there are too many keyfigures to create.
    I am using fiscal year in the columns outside the Key figure structure containing the keyfigures restricted at each of 4 quarters.
    So, when the report displays, all the 10 years will automatically be displayed.
    The problem is one of the 4 quarter level keyfigures needs to be restricted by calendar year.
    How can I read what is the fiscal year for each column at runtime so that I can reference this value to determine the calendar year ?
    As you know, each FY spans 2 Calendar Years. So, i need to restrict this on the 4th keyfigure by calendar year but while having the FY outside the keyfigure structure i can get all the FY, I am not sure how to access this value at runtime so that eg.
    if FY for column 1 is 2010, i can set calendar year to be 2010 to 2011.
    Hope you can give me some clues.
    Thanks you Gurus!
    Best regards
    John

    Dear Sunnybt
    Copy Riyes,  I find your response interesting. Please could you elaborate your idea of using condition in more detail.
    Sorry for my late response.
    Allow me to clarify my statement, which you are right, is unclear.
    By :
    "if the current QuarterFY is less than the current QuarterFY"
    I mean :
    eg. user enters FY range : 2009 to 20NN  (eg. 2017)
    KF_column1_FY2009_Q1______KF_column2_FY2009_Q2____KF_column3_FY2009_Q3______KF_column_FY2009_Q4______KF_column_FY2010_Q1______KF_column2_FY2010_Q2____KF_column3_FY2010_Q3______KF_column_FY2010_Q4_____KF_column_FY_NNNN_Q1
    For each column, where the FY can be any year range entered by user,
    the Text Description of the Column should show either 'Actual' or 'Plan' based on what is the current FY Quarter at runtime.
    If the FY Quarter (eg. 1st column is 200101) is before current FY Quarter (i.e 201103), then the Description of this column should be "Actual" , else "Plan".
    In my current design, I am unable to use customer exit text variable to meet this requirement.
    So, I like to check with you for fresher ideas.
    If not , I would use a workbook, which I am avoiding as the user needs to drilldown and I believe drilldown is not possible in workbooks where report layout needs to be rigid or cell positions fixed. Of course, unless there is a way out of this which I do not know.
    Best regards
    Bass

Maybe you are looking for