Ansicht
Dokumentation
OHAGOSP00109B - Open End Absence Processing Limit
rdisp/max_wprun_time - Maximum work process run time CPI1466 during BackupThis documentation is copyright by SAP AG.
Use
In this step, you decide how far into the future an open-ended absence is processed during the absence entry check [infotype Absences(2001)].
Requirements
Standard settings
The payroll constant for open-ended absence checking (HRPSG ABSMN in table T77S0) is set to a number of months. This is the processing limit.
You must not increase this limit. If absence entry checking is active, then saving open-ended absences will be very slow.
Activities
If an open-ended absence has no end date or the end date is 12/31/9999, a date will be derived (as follows) and used as the end date of the absence for checking band changes, entitlements used, and absence splits: the processing limit is added to the start date and the most recent valid date is used as the end date.
For example, if the start date is 12/31/06 and the processing limit is set to four months, the end date is calculated as follows: 12/31/06 + 4 months = 04/31/07, so 04/30/07 is used as the end date of the open-ended absence.
If an absence is entered with an end date far into the future (but not 12/31/9999), the whole absence will be checked. This will take a very long time and probably fail due to ungenerated personnel work schedules.
Example
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.
Length: 1430 Date: 20240523 Time: 213225 sap01-206 ( 38 ms )