SAP ABAP IMG Activity OHACN_TX207 (BAdI: Adjusting the format for the Individual Income Tax Report)
Hierarchy
SAP_HRCCN (Software Component) Sub component SAP_HRCCN of SAP_HR
   PY-CN (Application Component) China
     P28C (Package) HR Customizing: China
IMG Activity
ID OHACN_TX207 BAdI: Adjusting the format for the Individual Income Tax Report  
Transaction Code S_SL0_21000004   (empty) 
Created on 20040401    
Customizing Attributes OHACN_TX207   BAdI: Adjusting the format for the Individual Income Tax Report 
Customizing Activity OHACN_TX207   BAdI: Adjusting the format for the Individual Income Tax Report 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name OHACN_TX207    

Use

This step describes how to set up customer-specific enhancements using the optional Business Add-In (BAdI) PC280001, which can be used to adjust the format for the Individual Income Tax Report (HCNCTAX0) that is delivered with the standard system with a format of your own. The method ADJUST_TAX_FORMAT within this BAdI consists of the following parameters:

  • PAYTY
  • PAYID
  • BONDT
  • IPERM
  • INPER
  • EETYP
  • SPCRL
  • TOTAL
  • DOWNLOAD_TAX_TITLE
  • DOWNLOAD_TAX

Requirements

You wish to substitute the format that is delivered with the standard system with a format of your own and understand that BAdI implementation PC280001 is provided as an example to achieve this goal. This example is provided "as is" to illustrate how a BAdI implementation along these lines could be developed. You should not use this implementation yourself, but rather copy it to the customer name range and maintain it to meet your specific requirements.

Standard settings

The information explained below applies to all methods of BAdI PC280001.

Activities

  1. Execute this IMG step. On the subsequent screen, enter a name for the implementation you wish to create. (Alternatively, if you have already used this BAdI to create other implementations, a dialog box appears, displaying the implementations that have already been created.)
  2. Choose Create. (Or, alternatively, Edit. The remainder of the documentation for this activity describes the steps to be performed when you create a new implementation.)

    Caution
    If you have already implemented this BAdI, then you must re-activate your current implementation. Otherwise, the report will issue error messages or short dumps as it processes employee data.
  3. Enter a short text for the implementation in the Implementation name field, then choose Continue.
  4. On the subsequent screen, specify an Implementation short text, then choose the Interface tabstrip. The name of the implemented class fields are already found in this tabstrip.
  5. Save your entries and assign the implementation to a development class.
  6. Place the cursor on the method, then double-click to initiate method processing.
  7. Enter the code for the implementation between the statements method <Interface name> ~ <Name of method> and endmethod.
  8. Save and implement your code.
  9. Return to the Edit Implementation screen, then save your entries there.
  10. If you wish to activate the implementation you have created at a later date, then exit the Edit Implementation screen without activating the implementation. Otherwise, choose Activate from this screen to activate the implementation for immediate use.

Once you have completed these activities, the source code that you stored in the method will be run when the associated application is executed.

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
OHACN_TX207 CN China
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG OHACN_TX207 0 JD10000020 Payroll Data 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20040421 
SAP Release Created in 500