Why do we need to?

Post SAP HR module Implementation especially when it is first go live for the client it is always recommendable to have few programs or shortcuts handy in SAP which would help get over very critical issues faced mainly due to Improper data loads of Legacy data to SAP during cut over phase. One of the programs I strongly recommend would be the program which can manipulate or change the data in payroll cluster tables.

Generally when business is very new to SAP HR there will be many issues during payroll runs due to below reasons

1) Improper maintenance of master data

2) Ignoring the warning messages

3) Running payroll without proper prior data verification

4) Improper data loads of Legacy data to SAP

After payroll is run for an employee, and payments are also processed now during the subsequent jobs i.e. in third party remittances and FICO live runs employee ends up in many cost center errors and ‘V0 split doesn’t exist’ errors during Third party remittance job. This is a situation where we cant delete the employee’s payroll results and correct the data and re run the payroll but neither we cant go ahead with third party and FICO jobs. This is the perfect example where we can use this program and use it to correct the data in payroll clusters and go ahead with the jobs.Other than mentioned, there will be many scenarios in which this program will be handy during very few months post go live.

How is it done?

This program uses a file (employee and SEQNR) as input and changes the payroll cluster table with the correct data and outputs a success or failure message after update.

If you already know the purpose or the correct data to be populated we can write it in the code directly otherwise we can just write code for changing the payroll cluster and then change the data by debugging this program.

Here are the brief steps which describe the program skeleton: Complete code is attached for reference

1)               Open the input file through function module GUI_UPLOAD and convert it to internal table

2)               Loop through this internal table and read the employee and get the payroll results of this employee for the Sequence number through two function modules CU_READ_RGDIR and PYXX_READ_PAYROLL_RESULT

3)               Now in this step it is up to our requirement where we can code the correct data changing steps or leave it blank for us to put it in debugging

4)               After above step we have to call function module PYXX_WRITE_PAYROLL_RESULT to save the data in internal table to clusters

5)               Function module HR_FLUSH_BUFFER_UPDATE_PCLX is used to update the database from buffer.

6)               Finally we can populate the success or failure messages depending on the output of these functional modules.

When is it useful and handy?

Would like to state few scenarios in which this program would be handy

1)   Few employees who gets retired and if his/her cost center was not maintained in IT0027, therefore WPBP or C0 cluster was not updated during payroll run which causes many errors in FICO as below

2)   Few employee's V0 cluster is not updated for third party remittance wage types due to an issue in data loads to IT0221 info type during an payroll adjustment run, hence subsequent payroll results had wrong data which caused errors in Third party remittance job

This is a collection of the most useful SuccessFactors resources: documents, blogs, reports, and videos. This includes links that will cover an introduction to SuccessFactors, the acquisition by SAP, SAP's strategy, the SuccessFactors HCM suite, integration, and other related documents and resources. It is also recommended to join the SAP and SuccessFactors group on LinkedIn or on Google Plus, as this is the leading community for the latest and greatest information on SuccessFactors.

Overview

SAPexperts in-depth Special Report: SAP and SuccessFactors - An Overview (SAPexperts)

SuccessFactors with SAP ERP HCM - SAP PRESS Bookstore (SAP PRESS)

SuccessFactors Terminology and Abbreviations

Market, Customer, and Consultant-related

How to Transition from an SAP HCM to a SuccessFactors Consultant

SuccessFactors Training and Certification FAQ

SuccessFactors and SAP HCM consulting: The Wild West of 2013

The Future of SAP HCM and SuccessFactors Consulting - 2013 : CloudAve (Cloud Avenue)

Future of SAP HCM (SAP HCM Insights Podcast)

The state of Talent Management in SAP HCM & Impact of SuccessFactors - With Thomas Otter (SAP HCM Insights Podcast)

SuccessFactors, The Future of SAP HCM Consulting, Project Execution, Training & more! (SAP HCM Insights Podcast)

Cloud: When & Why Whitepaper (SuccessFactors)

Business Execution for Dummies (SuccessFactors)

SAP Forum: Life after Lars (diginomica.com)

How Siemens took its HR IT into the cloud (ZD Net)

Impact of DevOps and Cloud on SAP and ERP System Administrators (YouTube)

How significant is SAP’s on-premise and Cloud licensing swap announcement?

Magic Quadrant for Talent Management Suites 2013 (Gartner)

New IDC MarketScapes Show Client Satisfaction Is On The Rise In Worldwide Integrated Talent Management Market (IDC)

SuccessConnect 2013: Wrap-up and 5 Key Takeaways

SuccessFactors Talent Management Seminar 2013 Wrap Up (Jeremy Masters)

SAP and China Telecom Expand Strategic Partnership to Provide SAP Cloud Portfolio to Customers and Partners in Chin… (SuccessFactors)

Charting Your Course in 2014: SAP HR and SuccessFactors [podcast] (SAP Insider)

Journal on Product Design and Development (Prashanth Padmanabhan blog)

Stages In The Decision Making Phase Of Your Journey To The Cloud (Prashanth Padmanabhan blog)

Solutions: Employee Central

Employee Central handbooks from SAP [s-user required]

SuccessFactors Employee Central - list of countries with Localizations

SuccessFactors Employee Central - list of languages

What’s New in SuccessFactors 1302 release for Employee Central, Platform and Admin Tools

SuccessFactors Employee Central – Time Off and other new features in the 1308 release

SuccessFactors November Release: Employee Central

Implementing SuccessFactors Employee Central with a SAP background

SAP HANA Cloud Platform: Turbocharge SuccessFactors Applications (YouTube)

Eat like never before: SAP Networking Lunch

Manage Mass Changes in SuccessFactors Employee Central [registration required] (SAPexperts)

My Thoughts on SuccessFactors Employee Central

Employee Central Is Not A User Interface for SAP ERP HCM OnPremise (Prashanth Padmanabhan)

SuccessFactors Employee Central Time Off - Made for You! - YouTube (YouTube)

Time Off in SuccessFactors Employee Central: demonstration

Enhancing SuccessFactors Employee Central v12 Home Page - to HCP or not?

Here’s to 2013 and Employee Central !!!

Solutions: Employee Central Payroll

Employee Central handbooks from SAP [s-user required]

SuccessFactors Employee Central Payroll - list of supported countries

New SAP and SuccessFactors Cloud Payroll Offering

EPI-USE Announces Its SAP-Qualified EPI-USE U.S./U.K./Australia Payroll Rapid-Deployment Solutions for SuccessFactors Employee Central Payroll | SuccessFactors (SuccessFactors)

Solutions: Talent and Analytics

Employee Onboarding: Taking a Fresh Approach to Employee Engagement and Retention (SuccessFactors)

Calibrate Employee Performance Through SuccessFactors [registration required] (SAPexperts)

SuccessFactors LMS vs SAP LSO – Some observations | NTT DATA Business Solutions | Australia (NTT Data Solutions)

SuccessFactors LMS: Power in Assignment Profiles

Comparison Between SAP ERP HCM E-Recruiting and SuccessFactors Recruiting [registration required] (SAPexperts)

SuccessFactors Workforce Analytics or SAP Business Intelligence for Human Resources?

SuccessFactors August Release: Faster, easier adoption of the latest innovations

SuccessFactors Salary Budgeting based on the Custom Fields

Configuring And/Or Prerequisites in SuccessFactors Learning

What I Like about SuccessFactors b1311 - Recruiting Management

SuccessFactors Release Management: Four Tips from Talisman Energy

SuccessFactors November Release: Reporting and Analytics

SuccessFactors November Release: Empowering Managers to Build Robust Bench Strength 

SuccessFactors November Release: Onboarding - New Hires On The Go

Solutions: SAP Jam

SAP Jam - Useful Resources and Documents

Technical, data model, and configuration

Mapping SAP OM objects to SuccessFactors For a Hybrid Model

SuccessFactors: The X Factor of Data Models

Employee Central Entities and Interfacing

Extending SuccessFactors with the Metadata Framework

Rules and Picklists in the SuccessFactors Metadata Framework

Configuring SAP HCM & SuccessFactors: A Comparison

Picklists Management and Cascading Picklists in SuccessFactors [registration required] (SAPexperts)

Integration Strategy

SAP and SuccessFactors talent hybrid model: what lies ahead, plus a few small hidden jewels

SAP HCM and SuccessFactors Integration Packages: an overview

The Real Truth about SAP and SuccessFactors Integration

SAP and SuccessFactors - "Proven" Integration is Hype

Middleware Technology Options for Integrating SuccessFactors (Prashanth Padmanabhan)

Integration and Integration Packages

SAP HCM and SuccessFactors Integration Packages: an overview

Integration Add-on 1.0 for SAP HCM and SuccessFactors

Integration Add-on 1.0 for SAP HCM and SuccessFactors: Support Package 2

Integration Add-on 2.0 for SAP HCM and SuccessFactors

Integration add-on 2.0 for SAP ERP HCM and SuccessFactors BizX – SAP Help Portal Page (help.sap.com)

Integration Packages Administration Guide on SAP Service Marketplace [S-user required]

Pilot Test of the Integration add-on for SAP ERP HCM & SuccessFactors BizX

Integration Q&A: Managing employee compensation using SAP HCM and SuccessFactors

Integration Q&A: Real-World Impressions on SAP and SuccessFactors Integration Add-On’s

SAP HCM and SuccessFactors Biz X Employee Basic Data Integration RDS Demo - YouTube (YouTube)

SAP HCM and SuccessFactors Biz X Compensation Integration RDS Demo - YouTube (YouTube)

Employee Central – Employee Mini-Master Add-on Available

Dell Boomi AtomSphere for SuccessFactors (Dell Boomi)

How to integrate SuccessFactors talent data into SAP NetWeaver Business Warehouse?

SAP Jam ABAP Integration - Configuration Guide for SP Level 5

SAP Jam ABAP Integration - Configuration Guide for SP Level 6

LSO-to-SuccessFactors LMS RDS | hyperCision, Inc. [HyperCision]

PI Configuration Example (NWPI 1.0 SP2-4 & 2.0 SP0) [S-user required]

PI Configuration Example (NWPI 1.0 SP6 & 2.0 SP2) [S-user required]

Tips and Tricks

Tip: Creating a single URL for logging directly into SuccessFactors BizX demo instance

Single Sign-On to SuccessFactors from SAP HCM

Single Sign-On between SAP Portal and SuccessFactors

Acquisition by SAP and Roadmap

Thoughts on SuccessFactors, Holiday Wish Lists for SAP HCM, and UNICEF [podcast] (SAP HCM Insights Podcast)

SAP and SuccessFactors Acquisition Q&A (Cloud Avenue)

News Analysis: SAP Buys SuccessFactors for $3.4B Signals SAP's Commitment To Cloud, HCM, and Social (Constellation Research)

SAP to Buy Into Software as a Service With SuccessFactors Deal [PDF] (Garnter)

SAP To Buy SuccessFactors: Major Shift In Talent Management Market (updated) (Bersin by Deloitte)

SAP and SuccessFactors Roadmap Analysis (Cloud Avenue)

SAP and SuccessFactors HCM Roadmap - With Amy Thistle [podcast] (SAP HCM Insights Podcast)

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

As per new legal change, for Professional Tax calculation for state of Bihar and Orissa, Perquisites and Bonus amount needs to be added into Professional Tax Basis .

For reference:

Consider that a person is employed in Bihar and has a salary of Rs. 40000.00 per month and perquisites of Rs. 50,000 annuallly is given to him,  in the current financial year 2013-14. Annual basis for PTax will be calculated as 5,30,000.00 (12*40000 + 50,000) in the month of  September. As per the slabs, PTax deduction will be Rs. 2000/-

CourtesySAP

.........................................................................................................................................................

You are executing Payroll driver program HINCALC0 (TCode:PC00_M40_CALC_SIMU) to run payroll for employees working in your organization.

While you are executing payroll retrospectively, the ESI employee contribution gets reverted for earlier periods. This behavior is inconsistent.

CourtesySAP

.........................................................................................................................................................

While generating Form PT-IV for region bihar (Tcode: PC00_M40_PTX) for employees working in your organization, basis for ptax is blank even though ptax amount has been deducted for the employee. The basis amount does not appear on the report in case, there is a retrospective run performed for September period.

For reference:
Employee 'X' has his ptax basis as 30,000 per month. In the month of September, his annual ptax basis is determined and ptax amount is deducted. In October, due to certain reason, a retrospective run has been performed effective April. Now, when ptax report (Tcode: PC00_M40_PTX) is executed for generating Form PT-IV for employee 'X', basis amount displayed is blank, however, ptax amount deducted is displayed. This is incorrect.

CourtesySAP

.........................................................................................................................................................

You are executing t-code PC00_M40_CALC for the employees in your organisation. Alv is genearated for the employees and you have downloaded the E-file for validating with FVU 4.0 . When you validate the file for mid-year joinee employees then the validation utility throws an error.

Example :

If you have an employee hired on 12.04.2013 and you have downloaded the E-file for the employee using F24q utility report. You validate the E-file with FVU 4.0 then the system throws an error

CourtesySAP

.........................................................................................................................................................

If retroactive payroll is executed for a period for which no original pay results exists, then superannuation contribution is inconsistance

CourtesySAP

.........................................................................................................................................................

You are exectuing t-code PC00_M40_ESI for employees in your company.
In a scenario where you generate the New Form 6 for all employees based on the payroll area then employees are repeated in the ALV display. This behavior of the report is inconsistent.

CourtesySAP

.........................................................................................................................................................

The inconsistency described under Symptom is resolved.

To get the changes,apply the HR Support Package(s) indicated for your release in the 'Reference to Support Packages' section of this note.

Alternatively, apply the correction instructions attached to this note

CourtesySAP

.........................................................................................................................................................

This note contains changes related to Form 217.

The existing system behavior for form 217 report involves all the wage types that form 217 basis. Evaluation class '11' is set for all the wage types which forms 217 basis. With this setup the system checks for all the wage types in the cluster for each period of the run. This is creating long time exection of the re

Automate_calculation.pdf

Manual_Instruction_217.pdf

New :  PCR – IN38 , IN39, Z217

Wage Types - /A38 , /Z38, M38B  

Change : Schema - ZNNR   PCR- IN44  IN54

CourtesySAP

.........................................................................................................................................................

As per legal, bonuses/perquisites need to be included for basis calculation for the state of Orissa.

This note includes changes for Orissa Professional Tax with inclusion of bonus/perquisites.

CourtesySAP

.........................................................................................................................................................

If an individual declares investment towards the  payment of health insurance premiums, he/she qualify for the tax deduction under section 80D in infotype 0585.

Following are the possible senarios under which one can show his/her investments :

1. Medical Insr Premium (Non-Senior Citizen) Employee : self, spouse and children

2. Medical Insr Premium (Senior Citizen) Employee : self, spouse and children

3. Medical Insr Premium(Payment on behalf of parents non-senior Citz) : Parents

4. Medical Insr Premium(Payment on behalf of parents senior Ctz) : Parents

As per the  Government of India, an individual can not declare the investment towards senario 1 and senario 2 together i.e an individual can declare investment either towards "Medical Insr Premium (Non-Senior Citizen) Employee" or towards "Medical Insr Premium (Senior Citizen) Employee". But declaration towards any one of these to is allowed.

Similarly an individual can not declare the investment towards senario 3 and senario 4 together i.e an individual can declare investment either towards " Medical Insr Premium(Payment on behalf of parents non-senior Citizen)" or towards "Medical Insr Premium(Payment on behalf of parents senior Ctz)". But declaration towards any one of these to is allowed.

Currently there is no such validation in infotype 0585 , which is incorrect.

CourtesySAP

.........................................................................................................................................................

You are executing payroll driver program HINCALC0 (TCode: PC00_M40_CALC_SIMU) to run payroll for the employees working in your organization.

In case of cross financial retro, the value of /3I1 and /3I2 in section 89 calculation is found inconsistent

CourtesySAP

.........................................................................................................................................................

For the employees in your organisation you have maintianed the infotype IT0582. Now you have set the lock indiactor for the records maitained in the infotype. When you open the data in View mode to check the data, lock indicator symbol is not being displayed. The system behaves inconsistently.

CourtesySAP

.........................................................................................................................................................

Aadhaar is a 12 digit individual unique identification number issued by the Unique Identification Authority of India on behalf of the Government of India.

Till now in SAP system this information cannot be stored in SAP system.

CourtesySAP

.........................................................................................................................................................

You are executing payroll driver program HINCALC0(TCode: PC00_M40_CALC_SIMU) for the employees working in your organization.

In case of retrospective run across financial year, inconsistency is observed in /432 calculation.

CourtesySAP

.........................................................................................................................................................

While you are terminating an employee through termination workbench (Tcode: PC00_M40_TERM), the date on which employee has resigned is not included in the notice period. Due to this the 'Notice Pay' calculated for the employee becomes incorrect.

For reference:
Employee 'X' resigns the organization on 31.05.2013. Notice period for the employee is 30 days. When employee is terminated through termination workbench, the actual leaving date for employee is determined as 30.06.2013, however, it should be 29.06.2013 (including the day on which employee resigns). Due to this, notice pay is calculated incorrectly.

CourtesySAP

.........................................................................................................................................................

A new File Validation Utility (FVU) version 4.0 has been released by the Government of India, for validating the e-files generated through Form 24Q.

The FVU version 4.0 needs to be used effective October 2013.

Following changes have been incorporated as per the features of FVU version 4.0:

1. 'Token No. of Prev. Statement' field has been provided on the selection screen of report, so as to enter the 'Token no. of previous regular statement (Form no. 24Q)' provided to the employers, whenever necessary.

2.'Whether regular statement for Form 24Q filed for earlier period' field will be populated with value either 'N' or 'Y'.

CourtesySAP

.........................................................................................................................................................

Currently, in the standard system, if you execute correction payroll run for employees with   

•   Correction run functionality switched on
•     Multiple Form 16 switched off

there is an inconsistency in payroll results.

CourtesySAP

.........................................................................................................................................................

While generating Form 24Q (Tcode: PC00_M40_F24Q) for employees working in your organization, batch header details, challan details and deductee details are not being displayed in the downloaded file. The values are not displayed in the 'Display e-file' tab as well.

Note: This inconsistency is observed only for ECC 6.0 release.

CourtesySAP

.........................................................................................................................................................

The Government of India, Ministry of Finance, (Department of Revenue), (Central Board of Direct Taxes), has introduced the new version (3.9) of File Validation Utility ( FVU). Due to which modifications are done in form 24Q for ANNEXURE I.

This note delivers the changes needed to address the legal changedescribed in symptom section.

Note : Field Monthly Taxable Amount" is now changed to "Monthly Amount Paid/Credited", in order to incorporate same in Form 24Q, changes are done in the calculation logic of wage type /4MI.

Changes are done behind constant 'INMWT'. As per standard SAP delivery value '0' is being used for /4MI recalculation and the same is being used in other reports as well.

Prerequisite Support Package.

604 -  SAPK-60459INSAPHRCIN

600 -  SAPK-60093INSAPHRCIN

CourtesySAP

.........................................................................................................................................................

Government of India has release a new File Validation Utility version 3.9 to validate the new Form 24Q file format. According to this it has been established that in the Annexure I of Form 24Q, "Amount paid/Credited" has to be reported against "Taxable amount of which tax deducted"

Solution

The Annexure I of Form 24Q was reporting total taxable income. NSDL has released an FVU 3.9, according to which it has been establised that the for the deductee details (Form 24Q - Annexure I), name of the field "Taxable amount of which tax deducted" has been changed to "Amount paid/Credited".

Therefore SAP will now report the Gross income (/416) of the employee in Annexure I instead of the total taxable income (/434) NSDL has also clarified that the "Taxable amount on which tax deducted" in Deductee details in all four quarters need not match with the "Total Taxable income" figure shown in the Annexure II (salary details)

CourtesySAP

.........................................................................................................................................................

Previous employment data in SAP is reported in IT0580 and this infotype is primarily used when the employee is reporting income from previous employer with whom he was employed previously but within the same financial year.

If an employee is hired in 1st of Financial year/ he is an exsiting employee then IT0580 does not allow you maintian the Previous employment details. In such an scenario if any bonus payment coming from across financial year needs to be reported in current financial year needs to be captured and stored for payroll processing.

CourtesySAP

.........................................................................................................................................................

You are executing t-code PC00_M40_F24Q for employees in your company.

In a scenario where you have maintained the Sec80C entries for multiple employees and you executing the 4th quarter. Then the Sec80C values displayed in Annuxure II (Salary and Details) tab under the column head 'Ded sec 80C,80CCC,80CCD(1)' is getting repeated.

CourtesySAP

.........................................................................................................................................................

While you are trying to generate ECR (Transaction PC00_M40_EPF) for employees in your organization, if employee is contributing towards an Exempted Trust, only pension details need to be displayed on ECR. PF details are to be left blank for such cases.

For referance

Employee 'X' in contributing towards an exempted trust. While you generate ECR for such an employee, only pension details need to be displayed on ECR,  PF details are to be left blank in such case.

CourtesySAP

.........................................................................................................................................................

While executing payroll (TCode: PC00_M40_CALC) for employees working in your organization, if the employee has died before completing senior or very senior citizen age, income tax is getting calculated incorrectly.

For senior and very senior citizens, separate income tax slabs apply for tax calculation. However, these slabs are applicable in case employee reaches a certain age as defined by the Government. If an employee dies before he reaches the senior/ very senior citizen age, the system still calculates tax as per senior/ very senior slabs. This behavior is incorrect.

For reference:Employee 'X' reaches 60 years (Sr. citizen) of age on 01.09.2013 and he dies on 31.05.2013. In this case, when payroll is run for May 2013, income tax is being calculated with slabs used for senior citizen. This is incorrect, as the employee died before he completed 60 years of age.

CourtesySAP

.........................................................................................................................................................

You are executing payroll driver program HINCALC0 (TCode: PC00_M40_CALC_SIMU), for the employees working in your organization.

Inconsistent professional tax deduction is observed in case of retrospective run when there is a change in organizational assignment from the past periods.

Reference:

Employee's payroll has been run till August month. In the month of September there is an organizational change in IT0001, effective from August. When September's payroll is run, the professional tax deduction for the month of august is found inconsistent.

CourtesySAP

.........................................................................................................................................................

You are executing payroll driver program HINCALC0 (TCode: PC00_M40_CALC_SIMU), for the employees working in your organization.

Inconsistent professional tax deduction is observed in case of retrospective run when there is a change in organizational assignment from the past periods.

Reference:

Employee's payroll has been run till August month. In the month of September there is an organizational change in IT0001, effective from August. When September's payroll is run, the professional tax deduction for the month of august is found inconsistent.

CourtesySAP

.........................................................................................................................................................

When you execute the t-code PC00_M40_CMAP for employees of your organisation, and if you are using subtypes which are of character type. Then on executing the challan mapping program, system displays a short dump.

CourtesySAP

.........................................................................................................................................................

Professional Tax for the state of Sikkim has been introduced. The professional tax liability is computed on monthly basis and the deduction by the employer happens on a monthly basis.

For Professional Tax computation, new slabs and corresponding deduction amounts have been introduced by the Sikkim Government. Professional Tax basis is computed monthly and subsequently, Professional Tax deductions are made in each month. Professional Tax slab for Sikkim are as follows:

CourtesySAP

.........................................................................................................................................................

Professional Tax for the state of Manipur has been introduced effective from April 2013. The professional tax liability is computed on an annual basis and the deduction by the employer happens on a monthly basis.

For Professional Tax computation, new slabs and corresponding deduction amounts have been introduced by the Manipur Government. Professional Tax Basis is computed annually (using projection) and Professional Tax deductions are made in each month.

Professional Tax slab for Manipur are as follows:

CourtesySAP

.........................................................................................................................................................

While generating electronic challan *** return (ECR) for EPFO (TCode: PC00_M40_EPF), in case employee have certain negative arrears following inconsistencies have been observe

1. Negative arrears are also displayed as positive arrear

2. No way to determine which of the arrears are positive or which are negative

For reference:
Employee 'X' had certain PF contribution of INR 1500 in the month of April. Due to certain retrospective run, it comes out that PF contribution for the month of April should have been INR 1400. For, such cases there is a delta of INR 100 (negative), which is displayed on ECR as INR 100 (positive). This is incorrect

CourtesySAP

.........................................................................................................................................................

In order to record income from other sources for an employee, subtype 0002 of infotype 0584 is maintained. However the following were not available:

1. In 'TDS on other income' field it is not possible to maintain amount more than 99 lacs.

2. There is no field to capture 'Short Term Capital gains from listed securities

CourtesySAP

.........................................................................................................................................................

You are using Employee Self Service (ESS) based Loans application for employees in your organization.

However, it is being observed that while the approver tries to open the application from Universal work list, dump occurs.

CourtesySAP

.........................................................................................................................................................

You are executing payroll (TCode:PC00_M40_CALC_SIMU) for the employees working in your organization who are eligible for new pension scheme having Provident Fund Contribution infotype (IT0587) maintained accordingly.

You are having Nominal Basis of projection for your payroll calculation.On execution of payroll, it is observed that the NPS amount is not getting considered for projection and hence there is inconsistency in tax computation.

CourtesySAP

.........................................................................................................................................................

You are updating Dearness allowance details for the employees (using transaction PC00_M40_DAB). In such a case, the DA amounts are incorrectly getting calculated.

CourtesySAP

.........................................................................................................................................................

A new version (version 3.8), of File Validation Utility (FVU) has been released by the Government of India on 29th June 2013. There has been changes to the format of the e-filling format for 1st to 3rd Quarter and 4th Quarter.

CourtesySAP

.........................................................................................................................................................

You are executing Form 24Q report HINCF24Q (TCode: PC00_M40_F24Q) for the employees working in your organization.

While execution, a runtime error occurs with the following message 'Period parameters for payroll area not available'.

CourtesySAP

.........................................................................................................................................................

You have activated deferred loans functionality in your system by activating switch HRLOCIN_SFWS_SC_03.

While executing payroll for employees having loan record a short dump is being observed in last period of loan recovery.

CourtesySAP

.........................................................................................................................................................

A new version (version 3.8), of File Validation Utility (FVU) has been released by the Government of India on 29th June 2013. File Validation Utility version 3.8 has to be used effective 1st July 2013 for validating all the quarterly files being generated through Form 24Q report (TCode: PC00_M40_F24Q).

Pre-Requisite Notes : 1863154  and 1878839

There is one file for Manual Changes

CourtesySAP

.........................................................................................................................................................

This SAP Note corrects the following symptoms:

• You use transaction PA30 ("Maintain Master Data"infotype 0007 ("Planned Working Time") to change the "employment percentage" for one of your rs . However,as a result of the changes, the "Work hour day/week/month/year" are not adjusted to the new employment percentage.
• You use transaction PA40 ("Personnel Actions") to perform an organizational reassignment for an employee. During the maintenance of infotype 0001 ("Organizational Assignment", you select "Organizational Unit" in the position dialog box for copying the organizational assignment, and you enter an organizational unit. However, this organizational unit is not displayed on the detail screen of infotype 0001, and it is not saved either.
• You perform a leaving action for one of your employees, where the "Employment status" (STAT2) should be changed to 0 ("Left"). However,the "Employment status" retains the value 3

CourtesySAP

.........................................................................................................................................................

You are executing Payroll driver program HINCALC0 (TCode:PC00_M40_CALC_SIMU) to run payroll for employees working in your organization.

When you are running payroll for employees across financial year, the following section 89 wage types are found inconsistent.

1.  /616 - Gross taxable income arrears

2.  /650 - Net tax difference

3.  /622 - Professional tax amount difference

4.  /6I2 - Chapter VIA deduction amount difference

CourtesySAP

.........................................................................................................................................................

Employees of your organization are working in North-East states where Income tax exemption under Section 10(26) is applicable.Mentioned functionality is already enabled in your system but the system is behaving incorrectly in case of some cases. for example consider the following scenarios:

1. ST Employee of any notified NE tribal area, posted in other notified tribal area will be eligible for NE Exemption only if the tribe to which employee belongs is also recognized as Scheduled Tribe (ST) in the posted area also.

2. It is not always the case, that all the ST employees of one tribal area, working in the same tribal area are eligible for NE Tax exemption.(For example all the ST employee of Assam is not eligible for NE Tax exemption).

CourtesySAP

.........................................................................................................................................................

You are executing the ESI report HINCESI0 for the employees working in your organization.

When an employee is on unpaid leave (LOP) for an entire month, the particular employee's record is not shown in the record output. The employee record should be shown in the output.

CourtesySAP

.........................................................................................................................................................

The Government of India, Ministry of Finance, (Department of Revenue), (Central Board of Direct Taxes), has introduced the new version (3.7) of File Validation Utility ( FVU) on February 19, 2013. Due to which some modifications are done in E-file of form 24Q.

CourtesySAP

.........................................................................................................................................................

You are trying to display the section 80 deductions details using transaction PZ80.
However, the declared amount in infotype 0585 ( Section 80 Deductions ) for an employee is not showing on screen and the field is appearing blank for recently introduced sub-sections.

CourtesySAP

.........................................................................................................................................................

You are using report(HINUACRP)to display the details of Income Tax declaration requests created via ESS Income Tax declaration application.When displaying the request, requested and approved amount is not displayed consistently in the detailed screen.

CourtesySAP

.........................................................................................................................................................

While generating ECR (TCode: PC00_M40_EPF) for employees who are contributing towards Provident Fund, following inconsistencies have been observed:

1. Joining Date of EPF & EPS is not coming correct.

2. In 'Relationship with the member' field, for Husband 'S' should be displayed. Currently it is being displayed as 'H'.

3. In case employee is more that 58 years, pension wages shall not appear not ECR. Currently it is displayed in few cases. This is incorrect.

Employee 'X' joined the EPF trust in April 2008. However, the data is present outside SAP system. You are going live in April 2012. So, the first payroll result present in system is of April 2012. When ECR is generated for 01/2012, even though employee has joined the PF trust in April 2008, date of joining is displayed as 01.04.2012. This is incorrect. The joining details for employee shall not be displayed.

CourtesySAP

.........................................................................................................................................................

You are executing ESI report (Transaction Code:PC00_M40_ESIF) for generating ESI New Form 5.

In the output form layout, there are some inconsistencies noted in both PDF and SAPSCRIPT forms in comparison with the standard form provided by Employee State Insurance Corparation.

CourtesySAP

.........................................................................................................................................................

While generating ESI Form 5 (TCode: PC00_M40_ESIF) for employees working in your organization who are contributing towards ESI, the Contribution dates are coming blank.

For Reference:
You have not activated Alternate Financial Year (AFY) functionality at your organization. Employee 'X' is contributing towards ESI. When you try to generated ESI Form 5 (Tcode: PC00_M40_ESIF), contribution dates present on the Form 5 are displayed as Blank.

Note: Symptom occurs only when AFY has not been activated.

CourtesySAP

.........................................................................................................................................................

You are executing claims disbursement program HINCREMP (Tcode: PC00_M40_REMP) to disburse claims for employees working in your organization.

You have disbursed certain amount & payroll has been run for that period. However, you want to disburse some more amount after the payroll has been run. When you try to disburse on the last day of such a period, the report does not allow disbursing any amount and throws an error message. This behavior is inconsistent.

Also, when the employee claims from ESS and when the admin executes the report to update infotypes (HINUINFU) after the payroll is run and the control record is in correction mode, the system does not update the infotype and throws an error. This is also found inconsistent.

For reference:
Employee is eligible for INR 10,000 in period April 2012 for a certain reimbursement. INR 5000 had been disbursed using the disbursement program. The amount is also paid to the employee when payroll is run. However, it is required to disburse another INR 5000 for period April 2012 after the payroll is run. When disbursement program is now run for last day of April 2012, an error message appears & amount would not be disbursed. This behavior is inconsistent.

CourtesySAP

.........................................................................................................................................................

Claim eligibility amount is incorrect in case of change in the allowance grouping of the employee within period

CourtesySAP

.........................................................................................................................................................

When you execute the T-code, PC00_M40_F16 for the employees of your company the Form 16 is generated for all of the employees. It consists of the form 12BA also.

There some alignment issues in the layout of the script for Form 12BA.

CourtesySAP

.........................................................................................................................................................

You are executing the Form 16 (TCode:PC00_M40_F16) for the employees working in your organization and you have maintained a higher range of values for number field of  wagetypes.

On executing the Form 16, system displays a short dump

CourtesySAP

.........................................................................................................................................................

When you execute the T-code, PC00_M40_F16 for the employees of your company for few eligible employees Form 16AA is generated.

Then the PAN, PERNR and Employee name in Form 16AA is not being displayed in the same way that is being displayed in Form 16

CourtesySAP

.........................................................................................................................................................

When you execute the T-code, PC00_M40_F16 for the employees of your company the Form 16 is generated for all of the employees.

When you enter the form name in the Customer Layout selection and execute the same, the Sec 80C values getting duplicated and repeated in  the form Layout.

CourtesySAP

.........................................................................................................................................................

With the new legislative changes (announced via Note 1843575), it is mandatory to generate Part A of Form No. 16 through TRACES Portal only.

These downloaded Form 16 Part A has to be then sent to employees.

There is an option required on Standard Form 16 program to send TRACES generated Form 16 Part A and the SAP system generated Form 16 Part B, in a single mail to employees.

CourtesySAP

.........................................................................................................................................................

As per the notification by the Government of India, Ministry of Finance, (Department of Revenue), (Central Board of Direct Taxes) dated February 19, 2013, the format of Annexure I & II on Form 24Q has undergone few modifications.

CourtesySAP

.........................................................................................................................................................

When you execute the T-code, PC00_M40_F16 for the employees of your company the Form 16 is generated for all of the employees.

There some alignment issues in the layout of the script

CourtesySAP

.........................................................................................................................................................

You are using Employee Self Service (ESS) based IT Declaration application for employees in your organization.

However, it is being observed that while updating infotype 0586 for Section 80c deductions approved requests, using report 'HINUINFU' system throws a dump 'CX_HRPA_INVALID_BUFFER_STACK'.

CourtesySAP

.........................................................................................................................................................

While generating Annex-II of Form 24Q (TCode: PC00_M40_F24Q) for quarter 4, the following inconsistencies have been observed:

1. When TAN based reporting has been activated and there are splits in 'Actions' (IT0000), 'Organizational Assignment' (IT0001) infotypes of employees, the system computes the end date of employment incorrectly.
2. Medical exemption & section 10 exemptions from the previous employment, are getting deducted from current employment taxable income as well. This is reducing the overall tax liability for current employment, which is incorrect.

Consider that TAN based reporting has been activated at your organization. Employee 'X' joins the organization on 01.01.2011. Employee is active for whole of the duration; however, there are certain splits in 'Actions' & 'Organizational Assignment' infotypes. Suppose the splits are as below:
01.01.2011 - 20.08.2012 & 21.08.2012 - 31.12.9999. In such cases, 'Date Upto' field on Annex-II is being displayed as 20.08.2012. This is incorrect.

CourtesySAP

.........................................................................................................................................................

You are executing e-file consolidation program (TCode:PC00_M40_F24C) for consolidating the different e-files generated using form 24Q report (TCode:PC00_M40_F24Q) into a single e-file for submitting the returns to Income Tax authorities.

While trying to consolidate e-files through the e-file consolidation program for form 24Q, a runtime error is being encountered.

CourtesySAP

.........................................................................................................................................................

Multiple Form 16 switch has not been activated at your organization. While generating Form 24Q of quarter 4(TCode: PC00_M40_F24Q) the following inconsistencies were observed.

1. While executing for separated employees, the 'Date From' field is not displayed correctly

2. While executing for employees that joined in the month of January, the results are not displayed in the output of the report

3. While executing for re-hired employees, salary & tax details before rehiring are not being displayed in the output of the report

Multiple Form 16 switch has been activated at your organization.

While generating Form 24Q of quarter 4(TCode: PC00_M40_F24Q) the following inconsistencies were observed.

4. Tax payable is not rounded before being displayed on output

5.  While executing for employees having certain previous employment details, chapter VI deductions are coming incorrect

For Reference:

• Employee 'X' joins the organization on 01.04.2011. This employee gets separated in middle of FY 2012 say, in September 2012. Multiple Form 16 switch has also not been activated at your organization. In such a case, the 'Date From' field on 'Salary & Tax Details' is being displayed as quarter begin date. However, it should be displayed as the start of FY 2012.
• Employee 'Y' joins the organization in the month of January 2013, where no previous payroll result exists. The employee is not liable to pay tax as his income does not fall under any tax slab rate. In this case, while executing form 24Q, the report does not pick the results of employee for the fourth quarter. The details should have been displayed in the report output.
• Employee 'Z' joins the organization on 01.04.2012. This employee gets separated in middle of FY 2012 say, in September 2012. In November 2012 employee is re-hired in the same organization. In such cases, salary and tax details from April 2012 to September 2012 is not being displayed in the output.

CourtesySAP

.........................................................................................................................................................

As per the legal changes announced by the central government for financial year 2012-2013, a new layout for Form 16 has been introduced. The new layout comprises of Part A & Part B respectively.

Prerequisite: SAP Note No. 1835787. Ensure that you read and implement the manual steps and correction instructions of Note 1835787 before applying this Note.

CourtesySAP

.........................................................................................................................................................

As per the Union Budget 2013 - 2014, for individuals having a taxable income less than 5 Lac, a tax credit of INR 2,000 would be given. While executing payroll (TCode: PC00_M40_CALC_SIMU) for employees, when a cross financial year retro is triggered from previous year, tax credit amount is being generated. However, it is not reducing the overall tax liability of the employee. This behavior is incorrect.

For an employee 'X' a cross financial retro is triggered. After considering the cross FY arrears, employees' taxable income comes out to be less than 5 Lac. In this case, a tax credit of INR 2,000 is generated. Suppose, the overall tax liability of employee 'X' was INR 10,000, then even after tax credit his liability remains 10,000. Tax liability for employee shall become INR 8,000 (10,000 - 2,000).

CourtesySAP

.........................................................................................................................................................

Loan Interest Amount is not getting calculated correctly in the payroll.

This inconsistency occurs if repayment of loan is done by employee in the middle of the month or the pay date for payroll is Middle of the month

CourtesySAP

.........................................................................................................................................................

If you are executing payroll for an employee who is eligible for tax credit  as per Section 87A, the system computes the net pay of the employee incorrectly.

CourtesySAP

.........................................................................................................................................................

This Note delivers the changes related to the Union Budget for 2013

This note include changes regards

1. Introduction of new section 87A (Tax Credit)
2. Introduction of new section 80EE
3. Amendment to Rajiv Gandhi Equity Saving Scheme (80CCG)
4. Introduction of 10% Surcharge for Individuals Earning Income over 1 Crore
5. Introduction of New Division under Section 80G

Manual steps also attached with this Note

CourtesySAP

.........................................................................................................................................................

This Note delivers the corrections related to marginal relief for 10% of surcharge for Individuals earnings more than 1 Crore.

CourtesySAP

.........................................................................................................................................................

Union Budget Changes 2013

Other terms

Surcharge, Tax credit, Rajiv Gandhi Equity Savings Scheme, Housing loan for first timers, Long term infrastructure bonds

CourtesySAP

.........................................................................................................................................................

You are executing payroll driver HINCALC0 (Tcode:PC00_M40_CALC_SIMU) for employees working in your organization in the region of Jharkhand.

While you are executing payroll, an inconsistent amount of ptax is been deducted in case of employee joining Jharkhand region in mid-year.

For Reference:

Consider a scenario, where the employee is transfered to Jharkhand region in October and is liable to pay PTax of Rs.1800 professional tax. When the payroll is run, the amount that the employee is liable to pay, gets reduced to 900 as the employee is transfered to Jharkhand in October.

So in this case, the ptax amount gets calculated as = 900 / 6 = 150.
This is observed as inconsistent behaviour. The PTax liability is dependent of the return value of the feature 40PTB.

CourtesySAP

.........................................................................................................................................................

You are executing Form 16 (TCode:PC00_M40_F16) for the employees working in your organization.

As per new legal changes for Form 16, for financial year 2012-13, the system must also display 80TTA in the Form 16 in point 9 (Deduction under chapter VIA) under "B". This Note delivers the changes needed to address this requirement/change.

CourtesySAP

.........................................................................................................................................................

Consider that you have activated Alternate Finacial Year (AFY) at your organization. When you try to create Section 80 and section 80C details through the IT Declaration solution of Employee Self Service (ESS) Portal,  after approval, the Infotype Update Report for Advanced Claims(HINUINFU) report does not consistently update the master data. This results in the generation of an error message.

For Reference:

You have activated AFY at your organization. While you are trying to create Section 80 & Section 80C through ESS portal, IT0585 & IT0586 are not getting updated. This is happening since begin & end dates are entered as 01.03.XXXX and 28.02.XXXX through ESS, however in R/3 the dates are getting entered as 01.04.XXXX and 31.03.XXXX. As per the standard behavior, dates shall be entered as 01.04.XXXX and 31.03.XXXX through ESS as well.

CourtesySAP

.........................................................................................................................................................

The act of Jharkhand Professional Tax has been introduced under which any person who is employed in that state is liable to pay professional tax.

Report to be delivered as part of standard solution is: FORM JPT-201

Jharkhand Professional Tax (JPT-201)is a quarterly report.

This report is used for quarterly and annual reporting of Professional Tax for state of Jharkhand.

Other terms

Jharkhand Professional Tax report, HINCPTX0 , India Professional Tax
reporting , PC00_M40_PTX - Professional Tax Reports, PCPTXIN4,PCSAPIN0 PCPTXIN1, PCEXTIN1, HR_IN_PTX_JH3_00, PCPTXIN6_PDF, T596F,

Reason and Prerequisites

The Act of Professional Tax for the state of Jharkhand has been introduced under which any person who is employed in that state is liable to pay professional tax. This is as per the legal change.

Solution

Apply the HR Support Package(s) indicated for your release in the 'Reference to Support Packages' section of this Note.

Note below points:

    o  Region code used for Jharkhand is '34'.

    o  This Note provides changes related to reporting part of the solution.

    o  In challan details, you need to select the quarter and as per the requirement enter the challans detials to be displayed in the form layout.

    o  The views V_T7INP1 and V_T7INP4 are needed to be customized as per the requirement.

CourtesySAP

.........................................................................................................................................................

While executing Professional tax report (HINCPTX0) for employees working in Tamil Nadu region, professional tax basis amount displayed is incorrect.

An employee is working in Tamil Nadu region & is eligible for professional tax deduction. However, when professional tax report is generated for such an employee for a period, the professional tax basis amount displayed is incorrect.

For reference:

An employee is working in Tamil Nadu and has ptax basis as INR 10,000. His professional tax has been deducted & now ptax report is being executed. If report is being run for period 04/2012 i.e. July 2012, then basis is shown as INR 40,000. This is incorrect. Since for ptax computation, basis of April to September is considered, same shall be displayed as basis in report also. Hence, INR 60,000 shall be displayed as ptax basis for above scenario.

CourtesySAP

.........................................................................................................................................................

Consider that you are using the Tax Simplifier Statement application in the Employee-Self Services for your organization. Currently, when the value in the field Long Term Capital Gains of subtype Other Sources for IT0584, is not maintained, the data related to Income from Other Sources is appearing

incorrectly. Also, the name of the payslip attached to the form is incorrect for the months of January, February and March, if payslips are being derived from the Business Add In.

CourtesySAP

.........................................................................................................................................................

Currently, when using the E-Separation solution in the Employee Self Service in your organization, if you try to create a separation request and  save the same, then the system generates an error "No valid target content area found Message no. APB_FPM_CORE112 "

CourtesySAP

.........................................................................................................................................................

You use the  Tax Simplifier Statement application in the Employee-Self services for your organization and you have provided additional payments option to

your employees. When you try to filter the additional payments by implementing the BAdI HRESSIN_FILTER_ADDPY,the BAdI is not getting triggered.

CourtesySAP

.........................................................................................................................................................

You are executing payroll driver program HINCALC0 (Tcode: PC00_M40_CALC_SIMU) for employees working in your organization in the region of Madhya Pradesh.

While you are executing payroll, it is observed that annual professional tax liability /422, is calculated incorrectly.

CourtesySAP

.........................................................................................................................................................

You are executing Payroll driver program HINCALC0 (TCode:PC00_M40_CALC_SIMU) to run payroll for employees working in your organization.

While you execute, the following inconsistencies are observed.

• For the employees working in the state of Jharkhand, the annual professional tax is not completely deducted in case the employee leaves in the middle of a financial year.

• In case of any adjustment to professional tax made by the wage type MP00, there is an inconsistency observed with the professional tax amount deducted. This happens irrespective of the professional tax state/region.

Note: If any custom wage type is being used besides standard wage type 'MP00', a custom PCR should be written to populate the payroll variable 'MP00' with the amount in custom wage type.

CourtesySAP

.........................................................................................................................................................

You are executing Payroll (TCode:PC00_M40_CALC) for the employees working in your organization.

It is observed that employees for whom negative values are passed in the Adjustment Wage Type system gives the DUMP error.

CourtesySAP

.........................................................................................................................................................

Following inconsistency was observed while generating Form 16 (Tcode:PC00_M40_F16) for employees of your organization:

If you have provided the File Path of Tax details while executing the Form 16 at your organization, the Form 16 DETAILS OF TAX DEDUCTED AND DEPOSITED will be inconsistent when executed for multiple employees.

The Form 16 output will show consistent details for first employee, whereas for rest of the employees DETAILS OF TAX DEDUCTED AND DEPOSITED was not shown in Form 16 but Blank value was displayed which is inconsistent.

CourtesySAP

.........................................................................................................................................................

You are executing Claims status report HINCREMS (T-Code - PC00_M40_REMS) to view the claims status of employees working in your organization, the following inconsistencies were observed.

1. In case of claims with carry forward frequency of more than one month, the amount is being carried forward for future months if not claimed in any period. When balance amount is being claimed in certain period, the claimed amounts are being carried forward further. This is inconsistent, since amount once claimed should not be carried forward further

2. When the status report is run for past periods after the amounts being carried forward, there are repetitive numbers of entries. This is also been observed as inconsistent.

For reference

a) For certain reimbursements, carry forward frequency is '11'. Employee has carried forward the amount for April & keeps carrying forward till February. Employee is currently in the month of March and whole amount is paid to him. Even after this, carried forward amount is being displayed in April month of next year as well.

b) For certain reimbursement, employee has carried forward the amount for April. Employee is currently in the month of August and still the amounts are not claimed. In this case, when the employee executes the status report for April, there are multiple carry forward entries. This is inconsistent

CourtesySAP

.........................................................................................................................................................

While downloading the Electronic Challan *** Return (Tcode: PC00_M40_EPF)file as a worksheet to local systems, the system does not displays certain headings.

You have generated Electronic Challan *** Return (TCode: PC00_M40_EPF)for employee's provident fund organization and that you are downloading the generated file to local systems in worksheet format. However, after downloading, certain headings are not getting displayed

CourtesySAP

.........................................................................................................................................................

You are exectuing t-code PC00_M40_F24Q for employees in your company.You have processed off-cycle payroll runs for the employee for some period.In the same period you have executed the off-cycle two times to make some payments to the employee.

In such a scenario you are using the payroll identifier to distinguish between the two offcycle runs for the same day payment. The challan mapping has been done for the employee, still when F24q report is executed all the results of the period are not displayed, for the particular quarter with offcycle runs.

In such scenario the results displayed are inconsistent in F24Q.

For Example:

1. You are using offcycle payroll type for some payments to be made in May period dated on 26.5.2012 using Wagetype X.

2. In the same period you want to run the offcycle twice on the same date,i.e., 26.05.2012

3. For the second offcycle run on the same day 31.05.2012 you are usingWagetype Y. In such scenario you want the second payroll run should have

separate record in the payroll cluster.

4. In such a scenario you enter '1' in the payroll identifier to separate both the payroll runs, during the payroll is being processed.The second offcycle run is stored with an unique identifier for same day payment and generates a separate record for the same. By default for the first offcycle run 'space' is stored as an identifier.

5. Then the described example displays inconsistency in F24Q reporting.

CourtesySAP

.........................................................................................................................................................

You have executed the report HINCPTX0 (HR-India Professional tax reporting) for West Bengal state.

Once the ALV list is displayed with relevant PTax details, you are trying to view the Adobe layout using 'PRINT FORM' option. On trying to check 'PRINT PREVIEW', system throws a short dump

CourtesySAP

.........................................................................................................................................................

Change in Form 16 report texts.

CourtesySAP

.........................................................................................................................................................

Change in Labour Welfare Fund report texts.

CourtesySAP

.........................................................................................................................................................

Change in Employee State Insurance report texts

CourtesySAP

.........................................................................................................................................................

Your are executing payroll (TCode:PC00_M40_CALC_SIMU) for employees working in your organization.

On executing the payroll for employees, it is observed that the Professoinal Tax is inconsistent due to splits in Infotype 0007. System considers the last split and calculates the Ptax for the last split and not for the entire month, even if the employee is ellible for entire month.

CourtesySAP

.........................................................................................................................................................

Change in Provident Fund report texts.

Code changes have been done in Provident Fund report for the above symptom.

These changes are available with the mentioned HR Support Package.

If you need these changes immediately then Apply the Correction Instructions attached with this Note

CourtesySAP

.........................................................................................................................................................

Currently in the standard system, when you update dearness allowance details for employee (Using transaction PC00_M40_DAB), the system incorrectly calculates DA amount, in case you have enabled 'Incremental CPI slab Based calculation'.

CourtesySAP

.........................................................................................................................................................

In case, previous employment details are maintained for an employee through IT0580 (Previous Employment Details), the system incorrectly calculates monthly taxable income while executing payroll (Tcode: PC00_M40_CALC).

Consider that you are executing payroll for an employee working in your organization. The employee has certain previous employment details maintained through infotype IT0580. Employee has certain Profits in lieu of salary u/s 17(3), perquisites u/s 17(2) & medical reimbursement components also in his previous employment. Hence, the same has been maintained in IT0580. In such a case, the computed monthly taxable income is incorrect.

Monthly Taxable Income should be calculated as follows:

[Total income on which tax is computed - previous employment gross salary - previous profits in lieu of salary u/s 17(3) previous perquisites u/s 17(2) + previous employment exemptions (under section10, PF contributed, professional tax, medical reimbursement)- already computed monthly taxable income (/4MI)] / number of remaining months

CourtesySAP

.........................................................................................................................................................

You are using Tamil Nadu Profession Tax with Profession Tax region code as '22'.

When you are executing the Profession Tax report for an employee who belongs to region Tamil Nadu, Professional Tax basis displayed in report output has inconsistency where as Profession Tax paid is consistent.

CourtesySAP

.........................................................................................................................................................

You have implemented Loan functionality through ESS. The maximum loan eligibility amount for an employee is calculated based on the wagetypes maintained in IT0008 (Basic Pay).

While calculating the maximum loan eligibility based on the non indirectly valuated wagetypes maintained in IT0008 (Basic Pay), the calculated eligibilty amount is inconsistent

CourtesySAP

.........................................................................................................................................................

You are using TamilNadu Profession Tax with Profession Tax region code as '22'. When you are executing the Profession Tax report for an employee who belongs to region TamilNadu, Prosession Tax basis displayed in report output has inconsistency where as Profession Tax paid is

consistent.

CourtesySAP

.........................................................................................................................................................

You are using Employee Self Service (ESS) based IT Declaration application for employees in your organization.

However, it is being observed that while updating infotype 0585 for Section 80 deductions approved requests, using report 'HINUINFU' system throws a dump 'CX_HRPA_INVALID_BUFFER_STACK'.

CourtesySAP

.........................................................................................................................................................

Consider that an organization follows the practice where retrospective payment and the tax on retroactively paid amount needs to be accounted

to the same company code ,which is then also submitted to Government by the same company code.

In such situations if an employee is withdrawn ( Employment status '0') has a retro respective payment in spite of no company code change, the system generates /A60 wagetype.

This leads to inconsistency in the payroll results.

CourtesySAP

.........................................................................................................................................................

You are executing payroll driver HINCALC0 (Tcode:PC00_M40_CALC_SIMU) for employees working in your organization in the region of Jharkhand.

While you are executing payroll, following inconsistencies have been observed:

1. Annual professional tax liability /422, is calculated incorrectly.

2. Wagetypes being used for one-time payments are same for different regions. Due to this, these one-time payments, e.g. bonus, are being considered for professional basis formation of all the regions. This is incorrect. One-time payments are considered for professional tax basis formation only for certain regions.

Click for FAQ on Jharkhand Professional Tax

CourtesySAP

.........................................................................................................................................................

You are implementing ESS-Income Tax Declaration application and you are facing the below issue:

BAdI: HR_IN_ESS_ACTPROP (Actual and Proposed Column Visibility

You have implemented the above BAdI for enabling and disabling the actual and proposed amount column fields in the application.However even after implemention, the instance of the BAdI is not returned and hence the method READ_ACT_PRO_VIS is not executed.

CourtesySAP

.........................................................................................................................................................

You are using advanced claims application in employee self service scenario for employees in your organization.

However, on the approver overview Screen, while loading the requests for approvers of the claim requests, the eligibility data is being fetched for all the reimbursement types which is resulting in reducing the performance of the application.

CourtesySAP

.........................................................................................................................................................

You are executing a cross Financial Year retroactive payroll run (TCode:PC00_M40_CALC_SIMU) for the employees working in your organization.

On execution, it has been observed that Section 89 calculations are happening inconsistently.

Consider a case where an employee is being paid an arrear amount retrospectively for the year 2010. The difference between the original /416 amount and the /416 in the current run would form /616 in the difference table (DT). While section 89 calculation is processed, the previous retrospective payments for the same year are adjusted with the /616 in the current payroll run, which is not happening. This is found inconsistent

Note: This note is valid for SAP-HR release 4.7 only.

CourtesySAP

.........................................................................................................................................................

Change in Form 24Q report output ALV column header text.

CourtesySAP

.........................................................................................................................................................

You are using TamilNadu Profession Tax with Profession Tax region code as '22'. When you are executing the Profession Tax report for an employee who belongs to region TamilNadu, Prosession Tax basis displayed in report output has inconsistency where as Profession Tax paid is consistent.

CourtesySAP

.........................................................................................................................................................

When you execute the T-code, PC00_M40_F24q for the employees of your company the Form 24q is generated for all of the employees.When you try to execute the F27A tab during reporting of F24Q the organisation name displayed on the Form 27A is incorrect.The organisation name gets truncated.

CourtesySAP

.........................................................................................................................................................

You are creating a loan for an employee from transaction 'PA30' in Loan infotype (IT0045).After inputing the necessary details in the screen, on press of 'Enter' button, you see that eligible loan amount is getting doubled everytime on press of 'Enter' button.

CourtesySAP

.........................................................................................................................................................

India Professional Tax reporting form provides detailed information as per the statutory format required to submit the profession tax paid by the employees.

The system generates a list with the employees' basic details corresponding to the form that is selected, where the details for "Employees Whose Monthly salary or wages are" is not displayed as per the slabs maintained.

CourtesySAP

.........................................................................................................................................................

The Validity dates for each entry in V_T7INI8 should be properly maintained in V_T7INI9 & V_T77WWW_GAHLP for 'Section 80' scenario and

similarly for 'Section 80 C' for each investment code in T7INI3 the validity dates should be maintained consistently in V_T7INI4 and V_T77WWW_GAHLP

CourtesySAP

.........................................................................................................................................................

You are executing T-Code 'P16B' for salary packaging.

As per the configuration in Feature '16UPD', when the return value is 'X', the request does not require an approval from manager.

However, while requesting the salary package, the information text 'After you are sure that the package is assembled the way you want, please press REQUEST to request it from your manager' gets displayed on the screen.

Note: This change is only related to Payroll India (PY-IN)

CourtesySAP

.........................................................................................................................................................

While generating the Electronic Challan *** Return (Tcode: PC00_M40_EPF) for employee's provident fund organization certain data on ECR is inconsistent.

You are generating Electronic Challan *** Return (TCode: PC00_M40_EPF) for employee's provident fund organization. Following inconsistencies are observed:

• Employee Number is being displayed in the 'Member ID' field. This is incorrect. System must ideally display the employee's PF account number in 'Member ID' field.

• When the system generates ECR for multiple employees, if any employee has certain number of 'Non Contribution Period days' (NCP Days), then all subsequent employees being processed after this employee would also have the same number of NCP days displayed on respective ECR.

• 'Diff EPF and EPS Contribution (Due)' & 'Diff EPF and EPS Contribution (Rem)' fields are displayed incorrectly.

• When ECR is downloaded to local systems in the form of worksheets, certain headings were not getting displayed.

CourtesySAP

.........................................................................................................................................................