SAP ABAP IMG Activity OHAKREPEEABADI01 (Substitute standard salary calculation, contract code and other EEA data)
Hierarchy
☛ SAP_HRCCA (Software Component) Sub component SAP_HRCCA of SAP_HR
   ⤷ PY-CA (Application Component) Canada
     ⤷ P07C (Package) HR customizing: Canada
IMG Activity
ID OHAKREPEEABADI01 Substitute standard salary calculation, contract code and other EEA data  
Transaction Code S_SL0_21000009   (empty) 
Created on 20040420    
Customizing Attributes OHAKREPEEABADIS   Business Add-Ins (BAdIs) for Employment Equity Act (EEA) Reporting 
Customizing Activity OHAKREPEEABADI01   Substitute standard salary calculation, contract code and other EEA data 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name OHAKREPEEABADI01    

Use

This step describes how to set up customer-specific enhancements using the optional Business Add-In (BAdI) HRPADCA_RPLEEAK0_001, which features five methods, each of which can be used to fulfill a distinct business purpose. Each of the five methods delivered with this Business Add-In is listed below, along with its corresponding business purpose.

  1. GET_CONTRACT_PERIODS
    Apply this method if you wish to maintain or modify the standard contract periods pertaining to temporary employees. As delivered, the standard system stores these contract periods in the Contract Elements or Actions infotypes (0016 or 0000, respectively). Apply this method if you wish to maintain or modify contract periods elsewhere.
  2. CHANGE_EEA_BUFFER
    Apply this method to change the values in the standard buffer that is used to contain the EEA information that has currently been extracted for the employee.
  3. GET_EMPLOYEE_CONTRACT
    Apply this method to substitute the contract code that is stored within the employee's Organizational Assignment infotype (0001) record with a different contract code of your choosing.

    In the standard system, employee contract types are defined within the Organizational Assignment infotype (0001). However, the collective agreements that some enterprises make with labour unions may cause employee contracts to change during the year, depending on their tenure of employment. To facilitate reporting for enterprises with this business requirement, this user exit has been provided to enable the work contracts of employees in labour unions to be recorded and reported with greater ease.
  4. GET_EEA_SALARY
    Apply this method to substitute standard EEA salary calculation with an alternative calculation method of your choosing.
  5. EXPORT_EECRS_FILES
    Apply this method to modify the extracted contents of any or all of the following files for subsequent submission to EECRS:
    1. employee.txt
    2. promo.txt
    3. term.txt

Requirements

You wish to substitute the corresponding standard process that is delivered with the standard system with a process of your own and understand that BAdI implementation HRPADCA_RPLEEAK0_001 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 HRPADCA_RPLEEAK0_001.

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 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20051107 
SAP Release Created in