Alternate Financial year(AFY) in Indian Payroll

Hi All,
I am facing a strange problem in my payroll configuration. I activated business function for AFY and now Income tax should get calculated from March to Feb. I have necessary config for AFY including payroll period & control record. Now in my system period 1 of 2013 is equal to 01.03.2013 to 31.03.2013 & period 12 is 01.02.2014 to 28.02.2014.
I hired an employee on 01.03.2013 & trying to run payroll for whole financial year i.e. march 2013 to Feb 2014.
I noticed a discrepancy while calculating gross salary & professional tax while it calculates IT.
In March 2013 (012013) payslip monthly gross & Ptax are getting multiplied by 12
In April 2013 (022013) payslip monthly gross & Ptax are getting multiplied by 12. In March & April there is no issue.
But after that from May 2013 (032013) onward monthly gross & Ptax are getting multiplied by 11 for calculating IT which is very strange & I am not able to find the issue.
I also checked projection factor and /401 is giving accurate value only.
Pls help me with this as this highly important for my project.
Thanks & regards,
Arka

Hi Arka,
I think you are saying wrong.
In the March/2013---/401 will be hold the value 11
in the April/2013----/401 will be hold the value 10
in the May/2013----/401 will be hold the value 9.
Check and tell me.
Regards,
Sankarsan

Similar Messages

  • PY-India: What are the implications of changing the financial year?

    Hi All,
    I am working on Payroll India.
    the client i am working for has a financial yr from March to Feb.
    What would be the implications in terms of changes required if I change the usually followed Apr - Mar financial year in SAP to Mar - Feb in Payroll? And what implication will this have on all the legal reports provided by SAP like form 16 etc.
    Specifically I wish to ask should I ask the client to change his financial yr to Apr - Mar or should I change financial year in SAP to Mar - Feb?
    Amit Upadhyay

    it would be better to go for mar to feb as per our inidan fin year
    there will be implications in tax related issues pls check those things before changes the fin year
    Edited by: Sikindar on Jan 25, 2008 4:22 PM

  • Resetting a clearing document from a previous financial year - Vendor Payment

    Finance team needs to reset a cleared item from a previous financial year. The cheque was
    never presented.  They are unable to create a new invoice to pay the vendor without this cheque going
    through and being processed.
    However, when using transaction code FBRA they receive an error message
    "clearing document from alternative fiscal year-. Message no F5A258".

    There are two option
    1. You Open the Close Period, or change the reversal code, which can allow alternative posting in the current period.
    2. Go to the IMG - Controling - General Controlling - Change Message control. Give the message application area and then the number and turn it off. (Tcode : OBA5)
    With regards,
    Uttam Maity

  • Error while saving FYV : Gaps in financial year variant periods

    Hello Experts,
    We are getting an error while saving  a new FYV as:
    Gaps in financial year variant periods XY
    Message no. FGV556
    Diagnosis
    The period specification has gaps. The periods must be sequentially numbered without any gaps.
    System Response
    Only a correctly defined period assignment can be saved.
    Procedure
    Define the periods with consecutive numbers.
    Details: The new FYV has 52/53 weeks as posting periods depending on calendar year.
    For example, we are trying to define Fisc 2009 as follows. (Fiscal year 2009 = Nov 01 2008 to Oct 31 2009).
    Month-Day-Period-Yearshift
    11     ---     7     ---     1     ---     +1
    11     ---     14     ---     2     ---     +1
    11     ---     21     ---     3     ---     +1
    11     ---     28     ---     4     ---     +1
    12     ---     5     ---     5     ---     +1
    12     ---     12     ---     6     ---     +1
    12     ---     19     ---     7     ---     +1
    12     ---     26     ---     8     ---     +1
    12     ---     31     ---     9     ---     +1
    1     ---     3     ---     9     ---     0
    1     ---     10     ---     10     ---     0
    1     ---     17     ---     11     ---     0
    1     ---     24     ---     12     ---     0
    1     ---     31     ---     13     ---     0
    2     ---     7     ---     14     ---     0
    2     ---     14     ---     15     ---     0
    2     ---     21     ---     16     ---     0
    2     ---     28     ---     17     ---     0
    3     ---     7     ---     18     ---     0
    3     ---     14     ---     19     ---     0
    3     ---     21     ---     20     ---     0
    3     ---     28     ---     21     ---     0
    4     ---     4     ---     22     ---     0
    4     ---     11     ---     23     ---     0
    4     ---     18     ---     24     ---     0
    4     ---     25     ---     25     ---     0
    4     ---     2     ---     26     ---     0
    5     ---     9     ---     27     ---     0
    5     ---     16     ---     28     ---     0
    5     ---     23     ---     29     ---     0
    5     ---     30     ---     30     ---     0
    6     ---     6     ---     31     ---     0
    6     ---     13     ---     32     ---     0
    6     ---     20     ---     33     ---     0
    6     ---     27     ---     34     ---     0
    7     ---     4     ---     35     ---     0
    7     ---     11     ---     36     ---     0
    7     ---     18     ---     37     ---     0
    7     ---     25     ---     38     ---     0
    8     ---     1     ---     39     ---     0
    8     ---     8     ---     40     ---     0
    8     ---     15     ---     41     ---     0
    8     ---     22     ---     42     ---     0
    8     ---     29     ---     43     ---     0
    9     ---     5     ---     44     ---     0
    9     ---     12     ---     45     ---     0
    9     ---     19     ---     46     ---     0
    9     ---     26     ---     47     ---     0
    10     ---     3     ---     48     ---     0
    10     ---     10     ---     49     ---     0
    10     ---     17     ---     50     ---     0
    10     ---     24     ---     51     ---     0
    10     ---     31     ---     52     ---     0
    The above entries cover all the dates in calendar year 2009, that is, Jan 2009 to Oct 2009  is covered by periods 10 to 52 and Nov 01 2009 to Dec 31 2009 is covered by period 1 to 9 of the following fiscal year 2010.
    Inspite of making sure that all the days of 2009 are covered by periods 1 to 52. We are still unable to save the FYV.
    Please help!
    Susan

    Hello, I am getting this error while saving the FSV. My FSV is based on Weeks. Below is what I am inputting for this. Other details are Calender Year -  2017, No. of posting periods - 53, checked year dependent. Also, I have FSV for previous years also where weeks are 52 but configured as 53. So, hope that this is not creating this issue. Solicit your early response.
    Month
    Day
    Period
    Year Shift
    1
    7
    1
    0
    1
    14
    2
    0
    1
    21
    3
    0
    1
    28
    4
    0
    2
    4
    5
    0
    2
    11
    6
    0
    2
    18
    7
    0
    2
    25
    8
    0
    3
    4
    9
    0
    3
    11
    10
    0
    3
    18
    11
    0
    3
    25
    12
    0
    4
    1
    13
    0
    4
    8
    14
    0
    4
    15
    15
    0
    4
    22
    16
    0
    4
    29
    17
    0
    5
    6
    18
    0
    5
    13
    19
    0
    5
    20
    20
    0
    5
    27
    21
    0
    6
    3
    22
    0
    6
    10
    23
    0
    6
    17
    24
    0
    6
    24
    25
    0
    7
    1
    26
    0
    7
    8
    27
    0
    7
    15
    28
    0
    7
    22
    29
    0
    7
    29
    30
    0
    8
    5
    31
    0
    8
    12
    32
    0
    8
    19
    33
    0
    8
    26
    34
    0
    9
    2
    35
    0
    9
    9
    36
    0
    9
    16
    37
    0
    9
    23
    38
    0
    9
    30
    39
    0
    10
    7
    40
    0
    10
    14
    41
    0
    10
    21
    42
    0
    10
    28
    43
    0
    11
    4
    44
    0
    11
    11
    45
    0
    11
    18
    46
    0
    11
    25
    47
    0
    12
    2
    48
    0
    12
    9
    49
    0
    12
    16
    50
    0
    12
    23
    51
    0
    12
    30
    52
    0
    12
    31
    1
    +1
    Thanks
    Deepankar

  • RetrorespectiveActivation of Multiple Form 16 in mid- of the financial year

    Hi All,
    We have mainatined TAN as per the company Code in feature 40ECC. Now we want to have multiple Form 16 if there is change in company Code of an employee for the financial year 2009.
    We have not activated Multiple Form 16 Switch so far. Now in the last month of financial Year 2009 that in March'2010 (period 12/2009) we want to activate Multiple Form 16 switch from 01.04.2009. After activation Multiple form 16 Switch, we are planning to trigger retro for all employees from 01.04.2009.
    But we are not very much sure what will be the impact of activating Multiple Form 16 switch now in the last period of the financial year.
    Required your valuable inputs on this.
    Thanks,
    Ravinder

    Hi,
    Check whether multiple Form 16 switch is active or not.
    In case this is active, then the Form 16 will be generated as under:
    Company A - showing earnings from 01.04.08 to 31.12.08 only
    Company B - showing earnings from 01.01.09 to 31.03.09 as current earnings and from 01.04.08 to 31.12.08 as income from previous employment.
    In case multiple Form 16 is not active, then the Form 16 that you are getting is correct. However, in this case you need not print the Form 16 of company A. Only the Form 16 from the company code where the employee belongs to as on 31.03.2009 (i.e. last day of the FY) will be printed. And in this case the Form 16 will include complete earnings from 01.04.2008 to 31.03.2009 as current earnings.
    Hope this clarifies your query.
    VK

  • Mid Year Go Live  us Payroll

    Dear All,
    Could you give me step for going MID YEAR GO LIVE US PAYROLL ? What are the things to be taken care for going mid year go live us payroll ?

    hi,
    you have to upload the YTD data of WT like /101, /401, /403, /405, etc into tables T558B, T558C and
    T5U8C against the last payroll period before the go live payroll period. then you have to run the the payroll driver with schema ULK9 to upload the data to the cluster and then setting the earliest retro accounting date to the go live date or the date given by the client.
    this is a high level picture of mid year go-live for US payroll.
    hope this helps.
    reward points if helpful.
    regards,
    salman.

  • Open PO's after new financial year ??

    hii
    If we have some open PO's after year end .(New financial year got opened )
    In this case , we ahve to open new MM period using MMPV.
    What are the impacts will be there in SAP system, how to proceed further.
    Thanks

    hii
    Can u tel me , the steps has to be carried out in MMPV and OMSY.
    Once the new Period got opened in MMPV , how to proceed furthere with ur solution.
    Anthony said , there is no problem .
    can soem bosy explain me the step in MMPV and OMSY??
    Thanks

  • Is there a way of adjusting WEEKNUMs to match a financial year?

    Hi
    I am wondering if there is a way to have Numbers 09 adjust the WEEKNUMs so that they match the financial year, starting in the first week of April (UK). Given that I will have to do tax returns which match the financial year, it makes sense to match my accounts/Numbers files with the financial year.
    Thanks
    Nick

    nick_harambee wrote:
    I am wondering if there is a way to have Numbers 09 adjust the WEEKNUMs so that they match the financial year, starting in the first week of April (UK). Given that I will have to do tax returns which match the financial year, it makes sense to match my accounts/Numbers files with the financial year.
    I guess the place to start here is 'Which numbering system do you want to modify for this?'
    1) ISO Week: The International Organization for Standardization (ISO) ISO8601:2000 Standard
    All weeks begin on a Monday. Week one starts on Monday of the first week of the calendar year with a Thursday.
    2) (Not included as week starts on Sunday. Otherwise same as #3)
    3) Excel(and Numbers) WEEKNUM function with an optional second argument of 2.
    Week one begins on January 1st; week two begins on the following Monday.
    4) Simple week numbering.
    Week one begins on January 1st, week two begins on January 8th, and week 53 has only one or two days(for leap years).
    For modified system 1 (ISO), replace "calendar year" with "financial year". For modified WEEKNUM and Simple Week Numbering systems, replace "January" with "April"
    The nice thing about #4 is that it is "simple", and that simplicity extends to the ease of starting with any specific date. No correction factor is needed for the transition from one calendar year to the next.
    The shifting start dates of Week 1 of #1 and of Week 2 of #3 add a complication, but if these can be determined, the rest of the year can easily be numbered using the same formula as #4.
    Here are the three choices, with formulas below.
    SWN
    Start Date: April 1, constructed from A1.
    Table 1::B2: =INT(DATEDIF(DATE($A$1,4,1),A, "D")/7)+1
    (Results modeled on) WEEKNUM
    Start Date: Monday preceeding April 2
    Table 2::B2: =(DATE(Table 1 :: $A$1,4,1)-WEEKDAY(DATE(Table 1 :: $A$1,4,1),3))
    Table 1::C2: =INT(DATEDIF(Table 2 :: $B$2,A, "D")/7)+1
    (Modeled on) ISO
    Start Date: Monday preceeding first Thursday in April
    Table 2::B2: =IF(WEEKDAY(DATE(Table 1 :: $A$1,4,1),3)<4,(DATE(Table 1 :: $A$1,4,1)-WEEKDAY(DATE(Table 1 :: $A$1,4,1),3)),(DATE(Table 1 :: $A$1,4,1)+7-WEEKDAY(DATE(Table 1 :: $A$1,4,1),3)))
    Table 1::D2: =IFERROR(INT(DATEDIF(Table 2 :: $C$2,A, "D")/7)+1,53)
    Note: IFERROR traps the error that occurs when April 1 falls on a Friday, Saturday or Sunday, and assigns the days before the first Monday to Week 53. You may prefer to consider (and label) this Week 0. To do so, replace the 53 at the end of the formula with 0 (zero).
    None of the formulas will give 'correct' results beyond one year after the starting date.
    Regards,
    Barry
    EDIT: Noting your newest post, I think you may want to consider the Simple Week Numbering system, using a starting date of April 6.
    Barry
    Message was edited by: Barry

  • Date Range according to Financial year-end

    Hi
    I'm building this Discoverer report and one of my parameters is a LoV date field, which gives me a date range from Jan to Dec each year. Now my problem is, I want my date range to be as per our Financial Year End, which is from 01-Oct-03 to 30-Sep-04.
    You'd find "<All>" amongst the range. This "All" currently indicates date between Jan 2003 - Dec 2003. Now I need to write a query/trigger that will put my date range to be between 01-Oct-02 to 30-Sep-03 recurring automatically after each Financial year-end.
    Thanks

    Hi,
    Although I haven't tried it, you should be able to use a combination of hierarchies and alternative sorts to accomplish this.
    How have you created your list of values? If your LOV is a list of months and years e.g. JAN-2003, FEB-2003 etc, you can create a alternative sort which will make OCTOBER the first month of the year - i.e. with value 1, and NOVEMBER = 2 and so on...
    Sorry this is a bit vague. I will try and test tomorrow and see if it works, but this should be enough to give you an idea of how to progress.

  • Financial Year-End date range

    Hi
    I'm building this Discoverer report and one of my parameters is a LoV date field, which gives me a date range from Jan to Dec each year. Now my problem is, I want my date range to be as per our Financial Year End, which is from 01-Oct-03 to 30-Sep-04.
    You'd find "<All>" amongst the range. This "All" currently indicates date between Jan 2003 - Dec 2003. Now I need to write a query/trigger that will put my date range to be between 01-Oct-02 to 30-Sep-03 recurring automatically after each Financial year-end.
    Thanks

    Hi,
    You might want to post the Q on Discoverer Forum also
    Discoverer
    Navneet.

  • Customer Exit Variable Period 000 is not valid in financial year variant Z2

    Hi all,
    I am trying to get the week number from a particular posting period. But I get this error when I execute the Query:
    Error Group
    RFC_ERROR_SYSTEM_FAILURE
    Message
    SYST: Period 000 is not valid in financial year variant Z2
    I checked in "FIRST_DAY_IN_PERIOD_GET" FM and it is not accpting period 000 for PERIV Z2. It works fine for all other periods.
    Does anyone have an idea on this?
    Thanks.

    Simon,
    So do you think that there is a problem in my Query restrictions? You ask me to restrict from 0 - 12, but this period is calculated based on the SY_DATUM in a cust. exit variable. And this period is being used to pull week number. So, do I need to change the code?
    But I already have another query which is similar to this, only ready for input options are missing in the new one. The older one is working fine but the I have problem with this.
    Any more ideas?
    Thanks!!

  • Create asset-error"E003 SYST: Period 000 is not valid in financial year var

    Error during Asset Creation: E003
    AS01: Create asset was executed. During saving the asset got an error
    E003 SYST: Period 000 is not valid in financial year variant
    Following are the Depr keys assigned;
    LINA is being used for Book Depreciation
    MSTL Depreciation key is being used for ACRES, ALT MIN, ACE, E&P.
    Asset Class is Buildings

    Hello!
    I had the same problem a few month ago. There is a SAP note about this. Run the Asset Year end technical proces in ARJW. Try again your asset creation.
    Greetings,
    Stéphane

  • FGV003 - SYST: Period 000 is not valid in financial year variant K4

    Hello,
    I am getting the error below when trying to bring Period 000/2008 from our BCS cube into a basic cube.  I've run the "Transfer Global Settings" for our R/3 system but am still getting this error.  The BCS does have Period 000 Yr 2008 with FYV K4 and is showing in the master data for fiscal period.  Any ideas??
    SYST: Period 000 is not valid in financial year variant K4
    Thanks,
    Senthil

    Dear colleagues:
    The same problem is appearing to me. I am trying to run a job in background but the following error appears to me>
    SYST: Period 000 is not valid in financial year variant 36
    Do you know what I have to do to suprime the error?
    The job I am trying to run is for creating an evaluation in order to run the report S ALR 87012167
    Your Sincerely
    Leonardo López
    FI Consultant

  • SYST Period 012 is not valid in financial year variant R2 Msg no;FGV003

    Hi SAP Gurus,
    I have encountered with an error as following :
    SYST: Period 012 is not valid in financial year variant R2
    Message no. FGV003
    Our client following calendar year till December 2009.  They want to change to April to March , from April 2010 . So we need to define a shortened fiscal year for January to March 2010 for 3 months.
    One important thing is Depreciation should be calculated only for 3 months ie., from January 2010 to March 2010 for year 2010. For year 2011 u2013 April 2010 to March 2011 be calculated.
    I have done the following settings :
    Current fiscal year variant = K4, i.e. the standard variant with 12 periods (calendar year)
    -the current fiscal year must be closed on 31.12.2009
    -this change have to be done in the next month, i.e. on 01.01.2010
    -on 1.1..2010 starts the new fiscal year 2010
    -the fiscal year 2010 ends on 31.03.2010 and have 3 posting periods
    1) Create a new Fiscal Year Variant for the shortened fiscal year u2013 e.g. "R2" (OB29).
    2) R2 to be made Year Dependent. Current Period Configuration
    Month Days Period Year Shift
    1 31 1 0      
    2 28 2 0
    3 31 3 0
    4 30 4 0
    5 31 5 0
    6 30 6 0
    7 31 7 0
    8 31 8 0
    9 30 9 0
    10 31 1 +1
    11 30 2 +1
    12 31 3 +1
    3) Company Code assignment (OB37): K4 to be replaced with R2 .
    4) Controlling Area (OKKP): K4 to be replaced with R2.
    5) Fiscal Year to be shortened for Depreciation Areas in Asset Accounting customization (OAYP).
    6) Table T093C to be viewed to check whether the field XRUMPF (Shortened Fiscal Year) has been activated with u201CXu201D..(SE 11 Check Table) Done manually
    Other Problem : 1. The system calculates deprecation for period 3 ( Full year deprecation) as seen from AW01n for one asset.
    2. When I run AFAB for 2010 period 1 the error is displayed
    SYST: Period 012 is not valid in financial year variant R2
    Message no. FGV003
    Please anybody help me in this issue .
    Subbu

    Have you maintained the Year Shift Properly in OB29
    For e.g if Financial Year is from July to June, year shift will be as follows:
    Month      Days        Period       Year Shift
    1     31     7     0
    2     29     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
    Check also FI period and aseet periods are open through OB52 and AJAB

  • SYST: Period 012 is not valid in financial year variant V3 Message no. FGV0

    Hi!
    While I am going to create Asset it is giving me following error :
    SYST: Period 012 is not valid in financial year variant V3
    Message no. FGV003
    I checked in OB29, I have maintained 12 period,
    can you please tell me what will be the problem.
    Rakesh

    Have you maintained the Year Shift Properly in OB29
    For e.g if Financial Year is from July to June, year shift will be as follows:
    Month      Days        Period       Year Shift
    1     31     7     0
    2     29     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
    Check also FI period and aseet periods are open through OB52 and AJAB

Maybe you are looking for

  • Planned Order to STR Conversion - incorrect Valuation Price

    Hi Experts Not sure if you've encountered this before:- Material A in Requesting Plant has Valuation Price of USD10. Material A in Supplying Plant has Valuation Price of USD20. Material A is planned through MRP in Requesting Plant with Planned Order

  • Quartz Extreme not showing up on stock Mac Pro and card

    I have purchased a new Mac Pro and LED Cinema Display from the Apple store last month. Safari Top Sites is not working and the "help" stated I need Quartz Extreme. Looked in the profile, but it is not listed in the list on the right at all. It is a s

  • Configuration of Deffered Tax Procedure, please help?

    Hi Experts, I am working on a project. please help me to configure Deffered Tax procedure. So far I have configured regular Tax codes & replica of the same as target tax code. Please advice how to : 1. what special should i mention to in target tax c

  • Project Server 2010 permissions granted through RBS are not flowing through to Project Sites.

    Hi, I have configured RBS as "The Project Owner is a descendant of the user via RBS"  its working fine for Projects. But users are  facing access denied issue when working with project sites RBS is not working for project sites. Can any  one Help me

  • Adding multiple fields

    Hi, I am pretty new to Adobe Designer and was just wondering if anyone can tell me how to add multiple number fields in form. I took one of the blank template (expense claim) and customized to fit our needs. However, in the template they don't have a