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.

Similar Messages

  • MIR4 - Fiscal year change

    Hello All,
    We have a reuirement to differentiate the SAP deleted MM Invoices (when fiscal year changed) and manually deleted MM invoices by user.
    CASE1: When an MM Invoice is subjected to fiscal year change, SAP automatically creates a new document, deleting the original one. In RBKP, we can see boht the invoices, with status as "Deleted" for original invoice.
    CASE2: When the original document is deleted by user, status gets updated as "Deleted" in RBKP.
    Our requirement is to find out which one is deleted by SAP. Also, does SAP log this automatic deletion (document referenaces) in any tables?
    Any pointers would be helpful.
    Thanks,
    Pavan

    Hi,
    I don't know how feasible is this solution.. Can we differenciate the records by the ERNAME or ERFNAM ? For automatically deleted Documents may have the SAP Internal User id.
    Regards
    Vinod

  • Capturing previous year invoice document in current fiscal year

    Dear All,
    One of my client requirement is that have posted invoice in previous year and they are making payment in current fiscal year, this scenario they want to capture in payment advice. When am checking all the table with the input as payment document number and fcleared fiscal year system not showing the invoice reference against which it is cleard. For current year cleared documents we can extract the invoice reference where as for previous year system not picking that invoice number.
    Have checked in all the table entries, kindly suggest me is there any other alternative way to do this...
    Regards,
    Balaji.c

    Dear All,
    The problem is resolved since by giving the input as previous fiscal year and then system able to show the invoice number even if its cleared in current year. Invoice belongs to preious year and cleared documen in current year in that case we have to give the input parameter as previous fiscal year against that document number.
    Thanks for all the inputs.
    Regards,
    Balaji.c

  • Mass change of posting date/fiscal year in LIV parked invoices

    Hi,
    We have OSS note 99775 (program ZFSAP2_B) for mass changing posting date and fiscal year for FI parked documents but I can not use this to change posting date for LIV parked invoices.
    Did anyone have any idea how to mass change the posting date of LIV invoices? any NOTE or PROGRAM?
    I tried to create a BDC using FBV4, which in turn calls MIR4, but system is over writing  initial line item amount and qty from PO. 
    I can read initial invoice line item values and over write again but I dont think this is how I should do.
    Please advice.
    Thank you all and best Regards
    Vijay Goli

    Hi
    Thank you very much for your input.I modified the program ZFSAP2_B given by sap and it worked fine for LIV invoices also.
    When I used this program  in 2007 for FV60 documents the document key was changed without raising the event FIPP.CHANGED. But this year when we changed the posting date the system triggered the CHANGED event and as a result of this event the workflow came to the starting point. We did not make any chages to workflow template during 2007. Any idea what could have casued this event to trigger?
    Thanks
    Vijay

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

  • Excise Invoice Posting in Last Fiscal Year.

    Hi,
    Can excise invoice be posted in fiscal year 2011 for fiscal year 2010 if period of fiscal year 2010 & 2011 are open and  number ranges have been not maintained for fiscal year 2011 but number ranges are available for fiscal year 2010?
    Is there any system bug that excise invoice can not be posted for last fiscal year if number ranges are not available for current fiscal year?
    Regards,
    Suman.

    Hi,
    I clarifies my issue in more simpler way as follows.
    I have heard that if we post excise invoice as posting date 31-03-2011 (For last fiscal year. Number range available) on 01-04-2011 (Current fiscal year. Number range not available) then system will not allow for posting for posting date 31.03.2011 as a system bug. System will allow posting for 31-03-2011 (For last fiscal year) if number ranges are available for current fiscal year ( For 01-04-2011).
    Is it true ?
    Regards,
    Suman.

  • 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

  • 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

  • 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

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

  • Issues during F110 - Payment of invoice posted last year

    Hi gurus,
    Last month we had some problems during the payment of several invoices because they have been posted last year. When the user is trying to pay it, the system shows the following message: u201CFI234 u2013 Different FM fiscal years: Invoice XXXX for paymentu201D
    To solve this problem we run two transactions, FMJ2 (Year-End Closing: Carryforward of Open Items), to carry open items from 2011 to 2012 and the transaction FMAVCREINIT (Re-Initialize Availability Control Ledgers (FM), to reinitialize the ledgers.
    With this procedure we solve the problem for several invoices, but, for some reason, some invoices remain with this problem even though doesnu2019t exist open item last year (2011) anymore.
    Does anyone know if is there any step during carry forwarding open items that weu2019re skipping to solve this kind of issue?
    Best Regards,
    Amorim, Rodrigo

    HI
    you need to apply follwoing note
    Note 411323 - Profile 500: Payment for previous-year invoice
    Note 533106 - RFFMS200: Error message of FI234
    Note 535525 - RFFMS200: Error message FI234 (2)
    It will resolves your issue
    Reg
    Vishnu

  • Different fiscal year for extended withholding tax

    Hi All SAP Gurus,
    I have configured the extended withholding tax as per the Indian requirement.But I am unable to meet the following to requirement as per client's need.Can anybody help me out please?
    1) My client is following Calander year ( Jan to Dec.) for Global ledger and it is assinged to Company code Global setting.For Local reporting in India, we are using Non-leading ledger L1 and fiscal year V3 ( April to march) is assignd to it.Now the problem comes when we perform the TDS process.
    a) We assigned the number range etc. for Internal challan number and TDS certificate.When we run J1INCHLN and J1INCERT, system is picking the number as per the calalnder year and not as per the April to march fiscal yearThis creates problem for the priod of next year (say jan to march 2010).Can anybody worked on such a senario. Please help me out.
    b) Second requirement is client wants lower rate deduction of TDS. I really don,t know much but I wonder that how we can set lower rate deducation in SAP as it is linked to the total Invoice amount and from and to period. I could not find anything in the vendor master where we can assign period as well as total turnover amount for lower dedcution.
    Please helpme out.
    Thnaks in advance.

    Hi, Ekta
    For lower deduction of Tax you will have to do the following Config:
    1.In SPRO Extended WTD --> Basic Settings --> Define Reasons for Exemption:
    Reason for exemption
    Indicator used to classify different types of exemption from liability
    to a particular withholding tax.
    Enter Text field such as Concessional Rate of Vendor Name
    2.Extended WTD --> Calculation --> India --> Settings for Annual Returns --> Assign Exemption Reasons to Withholding Tax Codes:
    Mantain Country, WTH Tax Type, WTH Tax, Exemption reason creatd above.
    3. In the vendor Master enter the following details:
    Exemtion Number - Certificate no. recd.from Income Tax dept.specifying reduced rate of TDS
    Exemption % : 25
    Exemption Reason: One created by you.
    Exemption From Date:
    Exe,ption To Date:
    This should resolve part of your issue.
    Thank You.

  • RV_BELEG depending on: fiscal year, sales organization, month

    Hi everyone.
    We are facing an issue involving SD invoices numbering:
    we are currently using 3 numberings: one for receipts, one for invoices, and another one for cancelling invoices.
    The request is: this numbering should depend on fiscal year AND sales organization AND month (i.e. period).
    The problem is: we have sort of 30 sales organizations. Which yields 30 (sales orgs.) * 12 (months) * 3 (numberings) = sort of 1000 ranges EACH YEAR.
    But range RV_BELEG does not depend on anything, we can only define range numbers with a two-character string. If we used 0-9,A-Z coding we can use 36*36 = 1296 ranges.
    Which means: OK for the first year, but we cannot extend all these ranges for the 2nd and subsequent years.
    Anyone can help. Kind regards.
    Alvaro

    Hi all,
    I understand the requirements of Alvaro, he's spanish, as me, and it is a frequent requirement by spanish managers.
    First, try to understand the reason of this requirement. Perhaps the end users have the habit to know in which year and month was created the invoice by the ID (ie: VBRK-VBELN). You have a lot of fields for this in the interface to FI (check Note 301077 - User exits for the interface to accounting), after you can view this fields in FBL5N or other reports (you can enhance FBLXN tcodes, see SAP Note 215798 - FBL*N: Special fields are not displayed and related notes if the field populated is not in the standard). For instance, in field BSEG-SGTXT you have 50 characters to concatenate year, month, sales org and so on.
    Finally, explain to your client or to your boss that it's impossible. Think that by tax authority requirements in Spain, you can delete or archive invoices after 5 years, and field VBELN is a key of VBRK. And of course, it's not in legal requirements.
    I hope this helps you
    Regards
    Eduardo

Maybe you are looking for