Hierarchy
⤷ PY-IN (Application Component) India
⤷ P40C (Package) HR customizing: India
IMG Activity
ID | PAY_IN_TAX_700 | BAdI: Tax on Non Monetary Perk Paid by Employer for Form 16 Reporting |
Transaction Code | S_L6B_69000508 | (empty) |
Created on | 20030331 | |
Customizing Attributes | PAY_IN_TAX_700 | BAdI: Tax on Non Monetary Perk Paid by Employer for Form 16 Reporting |
Customizing Activity | PAY_IN_TAX_700 | BAdI: Tax on Non Monetary Perk Paid by Employer for Form 16 Reporting |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | HR_IN_TAX_EMPLOYER |
Use
This Business Add-In (BAdI) is used in the Tax (PY-IN) component.
You must implement this BAdI to capture the tax on non-monetary perquisites if the employer pays this tax on behalf of the employee. This tax amount is printed on Form 16 under point 16b (Tax paid by the employer on non-monetary perquisites u/s 192(1A) on perquisites u/s 17(2)).
- You have been provided with a standard method of determining the tax paid by the employer:
- The system calculates the average tax rate for the employee for the financial year.
- Average tax rate = (Income tax computed on the basis of rate in force for the financial year) / (Income chargeable under the head salaries including the value of perquisites for which tax has been paid by the employer) * 100
- The system multiplies this average tax rate with the value of non-monetary perquisites. The standard system considers the value of Annual Perk Wage Type (/413) as the value of non-monetary perquisites.
- Tax paid by employer = Average tax rate * Value of non-monetary perquisites
- If you are computing the tax paid by the employer outside the payroll and refunding the amount to the employee outside the payroll, you can capture the amount directly through this BAdI.
- If you are refunding the amount of tax paid by the employer to the employee through a customer wage type, the system can read the value of the customer wage type through the BAdI.
Requirements
You should only carry out this step if both of the following points apply:
- The SAP standard processes do not suit your needs.
- You are a competent ABAP/4 programmer.
Standard settings
In the standard system, the Business Add-In is not activated.
Activities
After calling up the IMG activity, a dialog box appears, in which the existing implementations are displayed. Choose Change, and proceed as follows:
- From the tab index, choose Interface.
The Name of implemented class field is already filled on the tab page, as a class name was automatically assigned to the implementation when you named it.
- Save your entries, and assign the implementation to a development class.
- Place the cursor on the method, and double-click to enter method processing.
- Enter the code for the implementation between the statements
method <Interface name> ~ <Name of method>
andendmethod
. - Save and implement your code. Return to the Edit Implementation screen.
- Save the entries on the Edit Implementation screen.
Note: You can also create an implementation, and then activate it at a later time. In such a case, end the processing stage at this point.
- Choose Activate
The code you stored in the method will be run when the application program is executed.
Example
Business Attributes
ASAP Roadmap ID | 257 | Create User Exits |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | I | Valid for countries specified |
Customizing Attributes | Country Key | Country Name |
---|---|---|
PAY_IN_TAX_700 | IN | India |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20030331 |
SAP Release Created in | 470 |