SAP ABAP IMG Activity HRPAYAT_KSB_MAT_GRTX (BAdI: Adjustment of Text for Conflict Types in Comparison)
Hierarchy
☛ SAP_HRCAT (Software Component) Sub component SAP_HRCAT of SAP_HR
   ⤷ PY-AT (Application Component) Austria
     ⤷ P03C (Package) HR Customizing: Austria
IMG Activity
ID HRPAYAT_KSB_MAT_GRTX BAdI: Adjustment of Text for Conflict Types in Comparison  
Transaction Code S_L4H_49002692   (empty) 
Created on 20120313    
Customizing Attributes HRPAYAT_KSB_MAT_GRTX   BAdI: Adjustment of Text for Conflict Types in Comparison 
Customizing Activity HRPAYAT_KSB_MAT_GRTX   BAdI: Adjustment of Text for Conflict Types in Comparison 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name HRPAYAT_KSB_MAT_GRTX    

Use

This Business Add-In (BAdI) is used in the Payroll Austria (PY-AT) component. You can use this BAdI to change the node texts for various conflict types that are output by comparison report RPCKSBA0_MAT.

You can use method SET_USER_GRPTXT to override the individual node texts for the various conflict types.

Requirements

Standard settings

The default implementation returns the node texts for the conflict types in accordance with the conflict resolution functions proposed by the system:

  • Nothing to do
    This group contains all employees for which the absences fully match the ELDA sick leave notifications. From a technical perspective, the group contains all conflicts for which the system cannot generate proposals.
  • Enter or Extend
    This group contains all employees for which an ELDA sick leave notification exists in a period in which there is no absence record. The system proposes inserting an absence record into IT 2001 for the period in question in this case.
  • Adjust
    This group contains all employees with absences that match the ELDA sick leave notifications from a time perspective, but for which the absence types do not match the reason for the incapacity to work in the ELDA sick leave notification. For example, the absence notification in IT 2001 indicates an illness, whereas the ELDA sick leave notification indicates an industrial accident. The system proposes adjusting the absence type in IT 2001 in this case.
  • Convert
    This group contains all employees with absences for which ELDA sick leave notifications (illness/industrial accident) would typically exist, but for which there is no corresponding record in infotype 3248. In this case, the system proposes converting the absence type into another absence type (usually unpaid leave or vacation) that does not require a sick leave notification.
  • Complex Situation
    This group contains all employees for which there are multiple overlaps in times between infotypes 2001 and 3248, resulting in a combination of the situations outlined above. Again, the system proposes a solution, but this requires careful examination.

Activities

After you call the IMG activity, the system displays a dialog box where you enter a name for the implementation.

If implementations of this Business Add-In have already been created, the system displays them in a dialog box. You then choose one of them by choosing Create, and continue as follows:

  1. In the dialog box, enter a name for the implementation of the Add-In and choose Create.
    The system displays the initial screen for creating Business Add-In implementations.
  2. On this screen, enter a short description for your implementation in the Implementation Short Text field.
  3. If you choose the Interface tab, you will notice that the system has populated the Name of the Implementing Class field automatically, by assigning a class name based on the name of your implementation.
  4. Save your entries and assign the Add-In to a package.
  5. To edit a method, double-click its name.
  6. Enter your implementation code between the method <Interface Name>~<Name of Method>. and endmethod. statements.
  7. Save and activate your code. Navigate back to the Change Implementation screen.
    Note: You can also create an implementation for an Add-In and not activate it until later. If you want to do this, do not perform the following step:
  8. Choose Activate.
    When the application program is executed, the code you created is run through.

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
HRPAYAT_KSB_MAT_GRTX AT Austria
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG HRPAYAT_KSB_MAT_GRTX 0 HLA0003815 Subsequent Activities 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20130206 
SAP Release Created in