SAP ABAP IMG Activity PAY_BR_GRN402 (Generate wage types)
Hierarchy
☛ SAP_HRCBR (Software Component) Sub component SAP_HRCBR of SAP_HR
   ⤷ PY-BR (Application Component) Brazil
     ⤷ P37C (Package) Customizing HR Brazil
IMG Activity
ID PAY_BR_GRN402 Generate wage types  
Transaction Code S_L6B_69000226   (empty) 
Created on 20021029    
Customizing Attributes PAY_BR_GRN402   Generate wage types 
Customizing Activity PAY_BR_GRN402   Generate wage types 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name HR_BR_GARN_GENWGTYP    

Use

To handle correctly alimony payments in income tax calculation and in the remuneration statement,it is necessary to generate additional wage types.

To generate these wage types, you must read the alimony wage types of the current and the previous payroll result. The previous result is read in two steps: first, determine which previous result is to be read; then, which wage types must be read from that result.

The alimony function has a standard customizing for the above-mentioned wage types by using the reading procedures for the previous current result. This customizing is available in the implementation guide (IMG), following the step Payroll -> Alimony -> Debits -> Generate wage types. The standard customizing may not be flexible enough for some customers. Then, this BAdI can be used to expand the scope of the function.

This activity is divided in three BAdI methods:

  1. The first BAdI method is processed if the GRNY area is customized by the customer. In that case, additional wage types will be generated from the current results table. The import parameters for this method are the directory entry of the current payroll, the current results table and the customizing of the 'GRNY' area. The customer must return, as export parameter, the wage types that must be created in the internal table IT.
  2. The second BAdI method is processed if the GRNZ area is customized by the customer. In that case, the customer must specify, from the start, which previous results should be read. The import parameters of this method are the directory entry of the current payroll and the directory entries of the previous payrolls to be read. The customer must return, as export parameter, the directory entries of the previous payrolls that must be read.
  3. The third BAdI method is processed after the second method, if the GRNZ area is customized by the customer. This method generates wage types from the previous payrolls results table, which have been previously selected by the second method. This method's import parameters are the directory entry of the current payroll and the directory entries of previous payrolls that must be read. The customer must return, as export parameters, the wage types that must be saved in the internal table IT.

Recommendation

This BAdI should only be implemented if:

  • the standard SAP method does not meet your requirements;       
  • the user has enough knowledge of ABAP programming;       
  • this BAdI will only be used for the above-mentioned purpose, since any other use does not guarantee correct system results.    If you use this BAdI:
  • DO NOT CHANGE the default coding.       

Recommendation: create an implementation, copy the default coding for the new implementation and make changes only on the copy.

Activities

Once the BAdI has been implemented and the default coding has been copied, it is possible to change this copy in the corresponding section. Then, you should activate the changes.

To implement a business add-in, proceed as follows:

After calling up the IMG activity, a dialog box appears, in which you can enter a name for the implementation.

If you have already made other implementations for this BAdI, another dialog box appears, in which the existing implementations are displayed. In this case, choose Create, and proceed as follows:

  1. In the dialog box, enter a name for the BAdI implementation in the Implementation field, and choose Create.

    The screen for creating BAdI implementations is now displayed.

  2. Enter a short text for the implementation in the Short text for implementation field.
  3. 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.

  4. Save your entries, and assign the implementation to a development class.
  5. Place the cursor on the method, and double-click to enter method processing.
  6. Enter the code for the implementation between the statements method <Interface name> ~ <Name of method> and endmethod.
  7. Save and implement your code. Return to the Edit Implementation screen.
  8. 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.

  9. Choose Activate

    The code you stored in the method will be run when the application program 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
PAY_BR_GRN402 BR Brazil
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20030408 
SAP Release Created in 470