Ansicht
Dokumentation

OHAGOSP00109D - Activate the Customer Exit for Manual Absence Splitting

General Material Data   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

In this step, you create the code to perform manual splitting of absences during absence entry.

Manual splitting and absence entry checking must be active.

Only use this customer exit if you are performing manual splitting of absences and you wish to perform absence entry checking.

There are five options:

1. Operate absence splitting manually without absence entry checking.

There is no benefit doing this. The absence entry clerk is unaware that a split may be necessary without doing extensive checking or running a report outside absence entry.

1. Operate absence splitting manually with absence entry checking.
1. Using the standard absence evaluation Customizing and routines.

The information stored in the database will slowly diverge from the absence entries entered during absence entry. This is because the data in structure "COVER" will exactly follow the scheme rules, whereas the absence data splits will be manual.

If this is activated, extra processing for splitting the absence table in payroll (table AB) is unnecessary and so omitted but the rest of the checking is performed. This will make payroll faster. The manual splits could be kept in line with the automatic ones using the Override OSP Scheme (0572) infotype.

1. Using a BESPOKE report.

Use the provided customer exit "EXIT_SAPLHRGPBS_OSP_OMP_MAN" to perform the calculation of your BESPOKE report that covers your scheme rules and then this code can action the clerk to split the absence manually.

To activate the use of this customer exit, set the manual splitting switch to "R" for report.

To make payroll quicker, the function GPNAB should be commented out from the schema as manual splitting is active.

1. Operate absence splitting automatically without absence entry checking.

The absence entry clerk will be unaware that a split will occur during the absence and so a standard report will have to be run periodically to find out whether or not an employee's entitlements should be overridden using the Override OSP Scheme (0572) infotype.
Also any errors in the employee's data or in the scheme set up will only occur during payroll and so can only be solved retrospectively, instead of proactively.

1. Operate absence splitting automatically with absence entry checking.

The standard setting will split automatically and perform checking.

Make sure the central code of your BESPOKE report is modular enough that it can be called simply in this customer exit. The output of the report must only be error/warning messages that will be displayed as the absence data is saved during absence entry (infotype 2001).

You wish to have strict manual control over which employees move to lower rates of payment due to prolonged absence.

As absence data is saved during absence entry (infotype 2001).

Most necessary infotypes have been read and stored in internal tables which are passed to the customer exit.

A "pseudo" infotype 2001, with the data from the screen included, has been generated and passed to the customer exit.

The Error table passed out of the customer exit will be displayed as error or warning mesages.

This customer exit is one of seven available as part of the absence evaluation and payment scheme functionality. They are ordered from the most likely to be used to the least likely:

1. EXIT_SAPLHRGPBS_OSP_OMP_CVR

Derive a employee's scheme according to client specific rules.

1. EXIT_SAPLHRGPBS_OSP_OMP_MIN

Define a part day absence as entitlement in minutes.

1. EXIT_SAPLHRGPBS_OSP_OMP_SEN

Define the seniority time unit parameters.

1. EXIT_SAPLHRGPBS_OSP_OMP_ENT

Adjust the employee's entitlement.

1. EXIT_SAPLHRGPBS_OSP_OMP_LEN

Define a time unit length in days.

1. EXIT_SAPLHRGPBS_OSP_OMP_MTD

Define a rollback method.

1. EXIT_SAPLHRGPBS_OSP_OMP_MAN

Perform customer-specific processing for manual splitting.

These are the only customer exits provided to supplement the GB functionality. Before using any of the customer exits make sure you have consulted with SAP. This will ensure the changes you need are necessary (cannot be fulfilled elsewhere in Customizing) and that the changes you are about to make will have the desired results with little impact on performance.

All seven customer exits have the following fields:
IMPORTING
VALUE(P_PERNR) LIKE PERNR-PERNR
VALUE(P_CHECK_DATE) LIKE SY-DATUM
TABLES
P_P0000 STRUCTURE P0000
P_P0001 STRUCTURE P0001
P_P0002 STRUCTURE P0002
P_P0004 STRUCTURE P0004
P_P0007 STRUCTURE P0007
P_P0008 STRUCTURE P0008
P_P0016 STRUCTURE P0016
P_P0041 STRUCTURE P0041
P_P2001 STRUCTURE P2001
P_ERROR STRUCTURE EDIMESSAGE

Do not change the data in the infotype tables.

"P_ERROR" has the fields msgid, msgty, msgno, msgv1, msgv2, msgv3, and msgv4. This table should not be refreshed as it may contain "warning" messages that have not halted processing previously.

If an error happens in this function, then fill the record "P_ERROR" and append the record to the table. Do not perform any error handling in this function as it is used in payroll, dialog, and reporting (for example, statement "MESSAGE" etc.)

This customer exit should only be used as an alternative to automatic absence processing, not as a combination.

Vendor Master (General Section)   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 6425 Date: 20240523 Time: 195059     sap01-206 ( 96 ms )