Ansicht
Dokumentation

HRPAYAT_KSB_MAT_GRTX - BAdI: Adjustment of Text for Conflict Types in Comparison

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

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.

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.

After you have called the IMG activity, proceed as follows:

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

If implementations have already been created for the BAdI, a dialog box with the existing implementations will be displayed. In this dialog box, choose Create.

1. In the corresponding field, enter a short text for implementation .
2. In the tab Propertiesenter filter properties - if this is a filter-dependent BAdI.
3. Choose the tab Interface.

The name of the implementing class is generated by the system based on the name of your impmlementation. You can change the name.

If the BAdI is a menu exit, the tab FCodes also appears.Enter a function here and, if necessary, additional data.

1. Save your entries and assign a package.
2. Position the cursor on a method. Call up the Class Builder by double-clicking it.
3. Between the statements method <Interface-Name>~<Name of Method>. and endmethod, enter the coding you request for the implementation.
4. Save and activate your coding, and navigate back to the screen Change Implementation.
5. Save on the screen Change Implementation.

Note: You can first create an implementation for the BAdI and then activate this later on. In this case, close the processing function at this time.

1. Choose Activate.

When the application program is executed, the coding you have created will be run.

General Data in Customer Master   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Length: 4583 Date: 20240523 Time: 185020     sap01-206 ( 82 ms )